Currently you can use SSL but you have to user the standard URL. You can create a CNAME to your storage account but most browsers complain that the traffic was rerouted and is possibly an attack. There should be a way to install a domain certificate to your containers.

Critical functions such as Select, Count and Contains are not currently available when querying TableStorage data.

If I only want a total number of rows that match a certain criteria I have no choice but to retrieve the data, count it and throw it away.

Adding support for Select would also help with heavy queries by only returning the data selected from a query.

Contains would be useful for searching. Using the Compare function is annoying.

Need to be able to sort on something other than the rowkey

Does what it says on the tin....really need better search capabilities over azure table storage.

I know that data is replicated but that doesn't protect against logical errors, accidental removal by admin or hacker screwing up the data.

So I really would like to see this done natively from Azure instead of building my own backup systems like these:
http://blogs.msdn.com/b/windowsazurestorage/archive/2010/04/30/protecting-your-blobs-against-application-errors.aspx

http://blogs.msdn.com/b/windowsazurestorage/archive/2010/05/03/protecting-your-tables-against-application-errors.aspx

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/

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.

Our application uses multi-tenant architecture. To provide better service/security to our customers we use one storage account per customer. Quota in 50 storage accounts per subscription makes difficulties to support such schema, because you need always to monitor the used number of accounts, ask support team to extend quota, in case when it is possible, if not then create new subscription for new ones.

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.

Using XDrive we can make a copy or backup from a VHD using blob capabilities instantly - in the same storage account, the same datacenter or a different datacenter.

Moving from XDrive to AzureFiles we are losing this capability. The VHDs may contain thousands of files. Copying those from an XDrive into a AzureFiles share or from one share to another takes a lot of time. Even when using AzCopy.

It would be great if there was a possibility to create copies of whole shares the same way.

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.

There is no good way to delete multiple entries in Table Storage. All you can do is delete one at a time. For logging tables this can become VERY expensive. It would be great if we had the ability to use Partitions as a way to delete logical groups of data in Table Storage in a single transaction.

This would allow for a partitioning scheme for grouping data in units that can easily be deleted. For example, logging data in WADLogsTable or rolling tables of data captured on a given partition can be archived easily and cleaned up.

I've started experimenting with Azure Files. One of the features I'm lacking is the fact that you cannot give access to Folders/Files on AzureFiles based on Active Directory credentials. If you setup a typical fileshare one would like to be able to grant/revoke access to folders and files based on information of users in AD.

Copying blobs in order to rename them is a heavy operation, especially when the blob is big, or when you need to change many files, such as when changing a directory name.

I understand that there are third party tools out there that can be used. Also Data Transfer tool (SQL Azure Labs) can be used - but it would be great if we could upload a file to Windows Azure blobs directly via Azure management portal

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.

For auditing purposes and to prevent data corruption, we want to give our support employees a user-centric, read-only access to Blob Containers in order to be able to investigate possible data corruptions (caused by bugs in systems).

This is not possible now because the security architecture of Blob Service does not even know the concept of users or roles.

SAS is not secure enough mechanism because it gives access to anyone by just sharing a link + you can't track who's actually using it.