Blob storage is, in effect, a big massive scale static web server. THis makes it very suitale for directly serving certain types of static web sites that may be hit by a big spike in load. The one statis web server feature missing that is really hard to work around is a lack of a default document.

It should be possible to set a single blob in each container as the default blob and this should be returned if the HTTP GET request provides only the container name.

This would allow
http://myservice.blob.core.windows.net/
and
http://myservice.blob.core.windows.net/mycontainer/

I love that we added support for the $root container, but it would be even better if we could have a “root” blob in the root container (and others).

This would provide the logical equivalent of a default document (index.htm, etc.).

If I need to provide a user (or external system) some data (blob) which might be outcome of some processing (or other) and it has some expiration time I'd like to just put a new blob and set TTL property with TimeSpan (or set absolute DateTime). When the period is over my blob is deleted. So I don't have to pay for it and don't need to spin up some service for doing it myself.

I currently have a wildcard SSL certificate installed on Azure and works great with my web roles, however I currently have a custom domain on my Azure Storage and would like to also use my SSL certficate on the Storage. Thanks.

It is good have uage logs for blog or container so that we can have better billing system. And it is better to have an API system to access those logs as well

Right now the system sends xml to the user if a file isn't found. This isn't very friendly to someone browsing from the web. I would like to have a redirect to a custom url for 404 errors instead of xml.

I can see the need for the xml when using the API so perhaps the redirect can be turned off when making the API calls.

This is also important so I can track when files are missing.

Azure blob storage is great for hosting lots of small files like those needed to support DeepZoom or Pivot. However, uploading thousands of small files one-by-one is very slow. It would be great if I could upload a zip file and have Azure unzip it into blob storage. Zip compression might also help reduce the upload bandwidth in certain situations.

Think about the many customers that just want to upload lots of data to a cheap storage somewhere in the cloud by using FTP upload/download.

It's nearly impossible to backup azure storage.

Cerebrata has a PowerShell commandlet that can create a full backup, and also do incremental.

But it DOES NOT WORK. Because it only looks at the Timestamp for detecting changed rows. But this does NOT detect deleted rows.

I know everything is on 3 disks, but this does not protect against errors in my software.

Why pay for 3rd party tools when we could use a built-in Windows application? Windows Explorer is the most natural way to utilize the storage services of Windows Azure. Drag and drop files to copy them between the local file system and blob storage; use a custom view to display/edit tabular data in table storage and messages in queue storage.

I want to be able to set http headers to a specific file inside a blob container such aa "Cahe-Control" and P3P Headers...

With the shared key authentication scheme, one can allow anonymous access to blob data for specified durations, however what we really miss is the ability to track the users/ip from where these access happened. Adding event support would allow us to track all access to our blob data and provide a meaningful audit trail!

WebDAV and FTP (or similar web publishing protocols) support into Blob storage, and be able host static websites directly

This should also work across containers, as long as the user has sufficient permissions. It's not clear to me why this isn't already supported. I have a distributed file system application and rely on built-in blob copy for better copy performance.

Allow HTML forms' POST requests to write blobs directly to blob storage, removing the need to have compute roles receive the data and then move it to BLOB storage.

This can be done using the HTML5 files API (and using XHR2 PUT requests), but a method for older browsers without the files API (IE9 and lower) would be great.

The ability to hook into actions on blobs and container would allow external actions on storage changes.

For example, adding a new blob might trigger a search crawler or send an email.

A trigger could be attached to a container's hooks and would be configured to match the storage operation (e.g. regex on URL, method, headers, etc) and possibly against the existing blob (similar to a SQL trigger's concept of before and after).

On a matching trigger, an external resource could be called with a POST request representing the event.

-Need to back up for Blob Restoring
-Provide Sync framework to work for syncing the Azure tables of different storage accounts
- Recovery of Corrupted Azure Table back for given Partition Key.