188 votes3 comments · Networking » Domain Name Service (DNS, Traffic Manager) · Flag idea as inappropriate… · Admin →
We’re tracking this on our long-term backlog. However, it’s unlikely that we’ll support this in the near future.
Thank you for the suggestion and please keep the votes and ideas coming.
Static websites is planned for the coming year! This feature will include more detailed error messages as well as support for a default Storage Blob. As soon as we have updates to share on Static Websites we will do so. For any further questions, or to discuss your specific scenario, send us an email at firstname.lastname@example.org.Anonymous commented
"Static websites is on our backlog" up to now I am waiting 7 years for default object and 404Error return custom object when not exists!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!.
I have 14 years until I got my pension.
Hope I do one project with Azure, I have already with Rackspace and Amazon
This is an interesting idea. The ask is currently on our backlog and will be prioritized accordingly. It is unlikely to happen in the coming year due to other priorities, however we will update when the status changes.
While this feature is under review, Shared Access Signatures (http://blogs.msdn.com/b/windowsazurestorage/archive/2012/06/12/introducing-table-sas-shared-access-signature-queue-sas-and-update-to-blob-sas.aspx) can be used to specify exact permissions for a table, partition, or entity, and distribute those to calling applications. Using this can reduce the risk of accidental deletions.
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.