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.

Thise idea is a duplicate of https://feedback.azure.com/forums/217298-storage/suggestions/3007732-make-it-possible-to-use-ssl-on-blob-storage-using, which the Azure Team marked as Completed, because you can accomplish this using CDN. But we need the real thing where you can have read/write SAS links to blob using SSL and Custom Domains.

Today the maximum policy you can have is 5. This is way to low as we are using blob storage in a data sharing scenario between providers and consumers and we need to use policies to be able to revoke issued SAS tokens in this sharing scenario. 5 policies means that we can only control 5 SAS keys that can be revoked. We need a lot more.

This has been requested in other forms, but now that you have Managed Disks you're most of the way there. I would like to be able to say "I want a Managed Disk using standard storage, 1TB in size, with 2500 IOPS." Then you figure out how to configure storage to deliver those IOPS without me having to stripe disks, or whatever.
Or perhaps "I want a 1TB Managed Disk using premium storage with 15000 IOPS." Again, you figure out how to configure and provision that, so I don't have to. That would be awesome!

Momently its not possible to map a azure file storage share via GPO, because the two fields for username and password are greyed out.

Do we have a way to tag specific AD users to be allowed to access a blob? if not when can we expect this feature?

Currently there is not possible to switch on VT-x on VMs, so installtion on-premises Virtual Server solution are not possible.

In the portal I want to be able to set (or at least see) http headers like "Cache-Control" at blob containers. We had an issue with CDN not caching images from blob when Cache-Control was not set to public.

I know that connections to Azure AD for Azure File Storage is in the works but while that is happening, I would love the ability to choose (individually) what domain users can see certain shares.

To have a fast way of uploading a large amount of data to a storage table. Trying to upload 5M entries (4M distinct partition keys) takes 20 to 60 hours (depending on where I run it) to upload single threaded.
Batch operations don't help much as they are limited to one partition per batch. Relaxing the restriction on batches to allow multiple partition keys in one batch and making batches larger would both help.
Alternatively uploading a CSV or JSON file as a single operation. It would be acceptable for this to create a new table.

Hi there,

It would be great if I could do batch insert (add) of messages. Often times I need to add several hundred or thousands or messages to a queue, and today I have to add them one by one. This is also related to the small size limitation of each message.

We were creating a snapshot each time we updated a blob to preserve the version of the blob. However when we tried to delete the blob we received Error 409 Conflict (error msg did not tell us why). When we changed the delete statement from await blockBlob.DeleteIfExistsAsync() to await blockBlob.DeleteIfExistsAsync(DeleteSnapshotsOption.IncludeSnapshots, null, null, null) the delete worked. Apparently having snapshots associated to a blob causes a delete conflict. Makes sense but can we have a more descriptive error message? Thanks!

Right now there is no way to execute logic on the columns other than Row key and partition key. It would be great if we can write some logic using lua scrpts which can execute on the server itself and get the results.
Because it take lot of effort to get the result and filter out at client side.

As per subject, allow to ignore echo on upsert operations too. There are cases where echo is not important when performing the upsert operation itself even if a row has been modified/replaced (ex: the table row will be read back later by another component).

Provide a way to request a .zip file through a list of blobs, or indicate the best way to do this.

We are currently using Azure Media Services which creates a new blob container for each asset. We currently have 40,000 distinct assets. When attempting to search from the blob container level using the exact container id it can take 10+ minutes. This seams to be searching for content within the containers as well. In contrast if we search Azure Media Services Explorer by id it is instant. It would be good to be able to have more control over how it searches