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.
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.
Lars Simonsen commented
I was just about to move my web site to blob, then I ran into this. I guess I'll have to find a different solution.
Chris Love commented
Can't believe it has taken this long. I moved everything to AWS last year and this was a big reason why. CloudFront + S3 and Free SSL make for a great Progressive Web App platform. Glad to see you are finally making some progress. PLEASE do not make it difficult to setup. AWS is super simple.
Ben Adams commented
Can also use Azure functions as a wrapper
Richard Gobbett commented
This is now beyond a joke. I have just spent an entire week waiting on the 4 hour publish times to test my CDN rewrite rules to get a simple angular2 SPA to work in a blob.
I have followed Hao's helpful post here: https://blog.lifeishao.com/2017/05/24/serving-your-static-sites-with-azure-blob-and-cdn but it does not work for me. All i want is https://myurl.azureedge.net/ is to resolve to https://myurl.azureedge.net/index.html.
It's sad that all the har dwork being done by the functions team is negated by a simple feature missing.
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....
John Petitte commented
CDN is great, but this is a necessary addition.
Leow Kah Man commented
Gleb Boushev commented
I am freaking puzzled, how is it possible that the Azure storage team is not aware of the fact that this is possible???
Itay Shakury commented
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?
Don't make me use S3 just for this. commented
Please. Surely it can't be that hard.
Hao Luo commented
There is a workaround using CDN. See Step 5 and 6 on https://blog.lifeishao.com/2017/05/24/serving-your-static-sites-with-azure-blob-and-cdn
You can realize this with Azure Functions Proxies that route to the blob storage.
Jerry O'Neal commented
We really need this feature.
Oleksiy Zelenyuk commented
do it finally!
"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
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.
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.
This feature is just 7 years late