How can we improve Azure Storage?

Static website hosting in Azure blob storage

This would require supporting default file to render and somekind of redirect from root to a particular container.

2,219 votes
Sign in
Sign in with: oidc
Signed in as (Sign out)
You have left! (?) (thinking…)
Abhay S shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

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


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

    Probably it is just nothing one can earn enough cash with. It's the absurdest missing feature I have ever occured. And it has not been fixed for years and years....

  • mattmazzola commented  ·   ·  Flag as inappropriate

    Also interested in the feature. Please send update on progress as soon as possible.

    Is there a recommended work-around to at least appease us until the feature is implemented?

  • Michael commented  ·   ·  Flag as inappropriate

    You can realize this with Azure Functions Proxies that route to the blob storage.

  • Anonymous commented  ·   ·  Flag as inappropriate

    "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

  • Darrell Enns commented  ·   ·  Flag as inappropriate

    Why does this need to depend on custom SSL domain support? Even without SSL, it would still allow serving unencrypted content, serving https using the azure domain name, or serving HTTPS with custom domain names by chaining it through CDN.

  • Free commented  ·   ·  Flag as inappropriate

    I was happy to see that https is supported by default (unlike AWS), but less happy to see that I cannot even set a default page (well... also unlike AWS).

    If you're not planning to implement this in the next few months, please do provide at least an explanation or a workaround to all the frustrated people here.

  • Steffen Gammelgård commented  ·   ·  Flag as inappropriate

    This is simply a necessary feature for costeffective hosting of singlepage applications. unless ofcourse we like **** routes like [blobaddress]/index.html/#/[Something]/[SomethingElse]

    Considering it's there in Google Cloud Storage AND Amazon AWS S3 it should make sense to make it here too.

    I did in fact look into altertative ways to get the functionality (through a CDN) but no luck.
    I guess there is no problem in hosting the singlepage application from Amazon or Google with a backend somewhere in Azure, but it just shouldn't be necessary

  • Roberto commented  ·   ·  Flag as inappropriate

    Seriously, nothing yet? I don't believe, I'm going to move my blobs to Google Cloud.

  • Nathan Evans commented  ·   ·  Flag as inappropriate

    Just asking again - when is this going to be added? Becoming unacceptable now. It is standard functionality of basically any HTTP document server since what 1994? Shall I open a priority support case since this is arguably a bug in Azure really?

Feedback and Knowledge Base