make it possible to use SSL on blob storage using custom domains
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.
Thank you for the continued feedback on this request. We’re evaluating this support in the context of various storage services and connectivity mechanisms.
We have a requirement to generate a file during new customer onboarding process, which the customer has to download. This typically happens once for each customer.
We currently put this file in blob storage and send the customer a download link. Ideally we would like this link to have or domain name as our customers know our domain name and this also fits with our branding.
Having to set up a CDN to deliver one file to each customer once seems rather excessive.
Being able to specify a custom domain for the download link is all we require.
Kelly Lesperance commented
Hortonworks, not HortenWorks...
Azure, please implement this BASIC feature already. It's been years!!
Microsoft is still the arrogant Microsoft
Julien Cantinos commented
It's shame after 6years that this feature isn't implemented!
CDN solution is just a profitable workaround...
Once support for SSL and custom domains have been added, we also need automatic redirect from any http requests to https to provide the best possible experience for users that access static web sites hosted in storage (or the option to turn it on)
Jonas Feller commented
Static websites need definitely custom domains with SSL. They don't necessarily need CDN. For a small project/website CDN is just overkill
Michael Iantosca commented
We need a solution that supports HTTPS, Custom Domain and SAS tokens for private access to blobs - the CDN does not support the SAS requirement.
Chrome displays (the ever so subtle, and commonly missed by our users) pop-up blocker for cross domain file download requests.
I concur with the others; CDN is often an unnecessary expense, not just the billed cost but all the hidden costs as well (complexity, configuration, maintenance) for simpler setups.
It is very much a business requirement for many of our projects, so this is a priority 1 feature request on our side.
Please add as others had said i need it for my static website and dont have a need for a CDN.
Peter Lillevold commented
Native Azure Storage support for using SSL to access blobs at custom domains makes even more sense now, in combination with the static websites feature. We could use this as the primary serving point for many of our web sites.
Static websites need custom domains with SSL. They don't necessarily need CDN. My current project is for users in one city. CDN is an unnecessary expense. Please add the ability to use SSL with custom domains and static websites.
The amount of CDN's you can create per subscription is too limited, thus we would rather have custom domains with SSL support. Also, we have customers in mainly one country so a CDN is not useful.
Freek Van Mensel commented
This is a very important business requirement for our organization.
@MS: When will this feature request become available?
Static websites on Azure Storage without a custom domain and SSL is worthless.
Like mentionned by others here, we are in the situation where we don't want any cache on our files, but are constrained to use CDN just to get a freaking custom domain with SSL, so we have to pay twice for each download ... Fix this please !
Ben Coleman commented
Definitely much needed now with the static web hosting features coming to storage. CDN isn't a good alternative IMO
Dan Friedman commented
With static web hosting in preview, https://azure.microsoft.com/en-us/blog/azure-storage-static-web-hosting-public-preview/, this is needed even more.
Clint Mann commented
Looks like this ain’t happening. Microsoft obviously is going for big profits with this one since they are pushing their HIGH DOLLAR CDN instead of just implementing this feature request. This is one of the highest voted feature requests ever and its still just “under review”. WHATS THE POINT OF VOTING THEN??