Thank you for your feedback. We are currently in public preview of static website hosting for Azure Storage to enable this scenario. Check out the blog post here for more details: https://azure.microsoft.com/en-us/blog/azure-storage-static-web-hosting-public-preview. The feature set includes support for default documents and custom error documents for HTTP status code 404.
For any further questions, or to discuss your specific scenario, send us an email at firstname.lastname@example.org.
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.
8 votesAbhay S commented
Say I have a Azure website and I can link the CDN (just like I can link storage accounts). On an attempt to delete the CDN, I should get a warning suggesting that this is being used by the Azure Website so can't delete.
Just like a storage account cannot be deleted if it contains a vhd in use by a VM.
We need such dependency locks for CDNs as well. As number of resources being managed in a subscription grows, it becomes difficult to track linkages and might lead to accidental deletions.
43 votesunder review · 3 comments · Cloud Services (Web and Worker Role) · Flag idea as inappropriate… · Admin →
41 votesunder review · 2 comments · Cloud Services (Web and Worker Role) · Flag idea as inappropriate… · Admin →
42 votesunder review · 2 comments · Cloud Services (Web and Worker Role) · Flag idea as inappropriate… · Admin →
This will be possible via the Git support in the TFS Service (tfs.visualstudio.com) by the end of the year.
Thanks for the feedback.
Good feedback. No plans in this area, yet.
We have been considering all of the risks and investigating the steps required to ensure we implement this feature with high positive impact and low to no negative impact.
After this investigation we have decided we will enable Pay-As-You-Go customers the option to configure a spending limit on a Pay-As-You-Go subscription, with appropriate safeguards and measures to prevent both service abuse and production service failure.
We have not yet finished determining the details of what this feature will look like, nor do we have a timeline for release, but we have heard your voices and have added this feature to our backlog.
Thanks for your continued feedback,
-Adam (Azure Billing Team)
There are a couple factors that determine availability of Add-ons in a country.
First, Azure continues to expand which countries are supported in the Store. Currently most of Europe is supported.
Second, Store partners select which of the available countries from which they wish to allow purchases of their Add-on.
Which Add-on were you interested in purchasing?