Thanks for submitting the idea! It’s currently in our backlog and prioritized with all the other features, so we don’t have an ETA at this point of time. For people who want to see this supported sooner, please don’t hesitate to give it a vote.
This would be just amazing. We desperately need this feature.
Thanks. This is something we are likely to do in the future.
This would be very helpful. When could we expect this?
Thanks for the request! Although there still is a storage account quota per subscription, we have increased it to 200 (250 with approval from the Azure Storage team) for users who need more accounts. Please refer to the Azure Subscription and Service Limits, Quotas, and Constraints page for some of the most common Microsoft Azure limits (including the maximum limit for storage accounts per subscription).
Sorry but 100 is not a good one anyways, perhaps 500? We are spawning a new site and storage for each customer for segregation of keys, data, and storage, which is a security requirement. 100 limit breaks all our limits and workflow.
Our apologies for not updating this ask earlier. We view this ask as a set of related features. Soft delete and automatic snapshots will help protect against accidental deletions and overwrites. Write Once Read Many (WORM) will disable modification (by anyone, including administrators and hackers) for a specified period of time.
This work is planned for the coming year, and we will be delivering it in multiple phases. As soon as we have progress to share, we will do so. We will continue to provide updates at least once per quarter. For any further questions, or to discuss your specific scenario, send us an email at firstname.lastname@example.org.
This should cover table storage and whatever backup option is planned, it should be able to survive a storage account delete.
Recovery vault enables snapshots on VMs why can't it include storage backup, too?
You can now use the Azure CDN to access blobs with custom domains over HTTPS. See the following article for instructions on how to do so: https://docs.microsoft.com/en-us/azure/storage/storage-https-custom-domain-cdn. Having talked to a number of customers, we concluded that this solution addresses many scenarios where the need for HTTPS access to blobs with custom domains exists.
Native Azure Storage support for using SSL to access blobs at custom domains is still on our backlog. We would love to hear about your scenarios where using the Azure CDN is not an acceptable solution, either by posting on this thread or sending us an email at email@example.com.
Sorry but offering enterprise software, we look like idiots when customer's sec team asks for the URLs they need to allow and we need to point them to blob urls among our application url.
Branding gives confidence to customers and this is still missing since 5 years after the initial request.
And what does backlog mean, another two years?