How can we improve Azure Storage?

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.

4,531 votes
Sign in
Sign in with: oidc
Signed in as (Sign out)
You have left! (?) (thinking…)
Tobin Rysenga shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

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: 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


Sign in
Sign in with: oidc
Signed in as (Sign out)
  • Tim Getsch commented  ·   ·  Flag as inappropriate

    Blob storage is used to host files that will typically only be downloaded once. A CDN would be a waste.

  • Azure User commented  ·   ·  Flag as inappropriate

    Buuuuh! I don't need your CDN, I just want my static page work on SSL without browser-warnings! This really sucks.

  • M Jones commented  ·   ·  Flag as inappropriate

    As Azure does not support this functionality, we went with Amazon Web Services.

  • Dimka M commented  ·   ·  Flag as inappropriate

    Seriously it's been almost two years since last update? For shame! Your customers still need this feature!

  • Amit Thakur commented  ·   ·  Flag as inappropriate


    i m trying to host angular static website on Azure blob with custom Domain Name, its working fine with HTTPS but its not working with Http URL Error massage is :-
    The account being accessed does not support http.

    HttpStatusCode: 400
    ErrorCode: AccountRequiresHttps
    RequestId : 2b0b58d2-701e-000f-0a1d-e97166000000
    TimeStamp : 2019-04-02T06:32:45.4653343Z

    i have create Rule in CDN :-

    Source (.*)” and destination “https://%{host}/$1

    any one Can you Help me ? how to fix this

  • Danielek commented  ·   ·  Flag as inappropriate

    We're delivering video from our container and the CDN is far too much extra cost for our needs right now. We just need HTTPS, not CDN.

  • Jeff commented  ·   ·  Flag as inappropriate

    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.

  • Julien Cantinos commented  ·   ·  Flag as inappropriate

    It's shame after 6years that this feature isn't implemented!
    CDN solution is just a profitable workaround...

  • Bjørn commented  ·   ·  Flag as inappropriate

    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  ·   ·  Flag as inappropriate

    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  ·   ·  Flag as inappropriate

    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.

  • Claus commented  ·   ·  Flag as inappropriate

    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.

  • Alain commented  ·   ·  Flag as inappropriate

    It is very much a business requirement for many of our projects, so this is a priority 1 feature request on our side.

  • Anonymous commented  ·   ·  Flag as inappropriate

    Please add as others had said i need it for my static website and dont have a need for a CDN.

  • Peter Lillevold commented  ·   ·  Flag as inappropriate

    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.

← Previous 1 3 4 5 6 7

Feedback and Knowledge Base