Thank you for your feedback. We would like to get more feedback about this item before we prioritize. Is the ask here to replicate a storage account on-demand ? Or have a mechanism to always keep two or more storage accounts in sync ?
Meanwhile, to unblock some of our users we have published a sample that copies blobs from an account to another account: https://docs.microsoft.com/en-us/azure/storage/scripts/storage-common-transfer-between-storage-accounts?toc=%2fpowershell%2fmodule%2ftoc.json
valid suggestion subject to upvote
Thank you for taking the time to vote for this item. We are glad to let you know that you can accomplish this today using Azure Blueprints locking mechanism. You can read about this here: https://docs.microsoft.com/en-us/azure/governance/blueprints/concepts/resource-locking
We encourage customers to use this path.
Rest assured we still have this request in mind and are continually reviewing it. Please keep your feedback coming!
At this point our recommendation is to move resources into a new Resource Group with the new name.Xavier Ronteix commented
4 years later and 2740 votes, can you update us on the progress?
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 firstname.lastname@example.org.
132 votesstarted · AdminAzure IaaS Engineering Team (Azure IaaS Engineering Team, Microsoft, Microsoft Azure) responded
Startup times for VMs continues to be a focus in Azure. I am leaving this item in the “Started” state because we still have work to be done, but the current deployment time we are seeing for Windows Server on average is 2 minutes (1 minute for Linux). We’ll continue to invest resources in driving down this number.
Thanks for your suggestion! The feature is currently in our backlog, but has to be prioritized with other ones. So we don’t have an ETA at this point of time. Please don’t hesitate to vote for it if you want to see it’s done sooner.Xavier Ronteix commented
Allow fine scheduling, start and stop and allow weekdays and weekend
- Monday-Friday start 8am stop 8pm
- Saturday-sunday keep off
This auto schedule does not prevent from manual start in case of need, but offer more flexibility and better usage of resources