Covering how to create an Azure Blob Storage Static Web Site. The second part shows how to configure https for a custom domain for the site.

  1. Create Blob Storage (djtemp in my case) Standard Performance, Hot Tier (you might want Cool later), Ignore Replication for now, Azure AD disabled, Data Lake Storage disabled (Some of these features are deafult but can be cahnged later through the Blob-Configuration page)
  2. In Storage account select Static Web site (on left)
  3. Enable it
  4. Set index and error pages (eg index.html and 404.html
  5. Save
  6. Note primary endpoint eg https://djtemp.z26.web.core.windows.net/
  7. Click on Blobs (on left) then select $web
  8. Create index.html and 404.html
  9. Open browser and enter the url from 6
    • eg https://djtemp.z26.web.core.windows.net/
    • eg https://djtemp.z26.web.core.windows.net/index.html
    • eg https://djtemp.z26.web.core.windows.net//404.html
    • eg https://djtemp.z26.web.core.windows.net/rubbish.html
  10. Go to your DNS provider and create a cname zone record for your custom domain, eg:djtemp.z26.web.core.windows.net

    DNS CNAME Entry

  11. Go back to the Storage Account (djtemp in this case)
  12. Click on Custom Domain (on left)
  13. Enter your custom domain (mysite.mydoain.com in my case)
  14. Use CNAME validation. Save (If that fails save without CNAME validation checked .. that worked for me).
  15. Test yhe custom domain in broswer eg http://mysite.mydomain.com Will get “The account being accessed does not support http”
  16. Test custom domain in broswer eg https://mysite.mydomain.com \ You will get certificate error warning but can click through this. Click on Details then on Go to the web page.

    Certificate error warning

You may experiment with the Configuration setting for the Blob Storage: Configuration- Secure transfer required:

  • Try disabling it and then try http with refresh, new browser etc.
  • The note says , “Because Azure Storage doesn’t support HTTPs for custom domains, this option is not applied when using a custom domain.
  • Try eg http://djtemp.z26.web.core.windows.net/ with it disabled that works
  • Also the Custom Domain does work for http with it is enabled, in my case http://mysite.mydomain.com works

My conclusions for the Static Web Site:

  1. The azure url for the site works with https regardless but http requires Secure transfer required to be disabled.
  2. http works for a Custom Domain if Secure transfer required is disabled.
  3. https works for a Custom Domain regardless but you wil get a certificate error warning, that can be ignored.

CDN Managed https on Azure

You can get https onAzure without purchasing an external SSL cert. You only pay for the volume of content transfers.
This makes it economic for early starters.

Nb: On Microsoft Docs it says:

Because Azure Storage doesn’t support HTTPS for custom domain names, this option is not applied when you’re using a custom domain name. And classic storage accounts are not supported. (Confusing)

But this is how I did it with an Azure CDN Standard Subscription!:

  1. Click Azure CDN (on left) to create a New Endpoint
  2. Give it a name, MySiteEP in my case (need some uniqueness here).
  3. Select Standard Microsoft
  4. Enter a CDN Enpoint name (make it up) , in my case MySiteEndpoint
  5. For Origin enter your Custom Domain from above, in case mysite.mydomain.com
  6. Click [Create]
  7. Once done, create a second CNAME entry for the Endpoint
    • Give it a name mysiteSSL in my case
    • Host is the Enpoint, MySiteEndpoint.azureedge.net in my case
  8. Try the new Url in a new browser, you will get a Certificate error at this stage. If you click through you will get “Our services aren’t available right now”

    New Endpoint

  9. Back in the Azure CDN click on the created endpoint
  10. Add the (+) Custom Domain, leave the Enpoint hostname, add the new Custom domain, mysiteSSL in my case.
  11. Click on [Add]
  12. When done click on the new custom domain, mysiteSSL.mysite.com in my case
  13. Turn on Custom domain HTTPS with CDN managed
  14. [Save]
  15. When done, step 2 onwards, in my case any way, take some time, an overnight job.
  16. So I leave it running (not the browser/porta!) and go to bed!
  17. At this stage 20 will work, but still with the cert error warning.
  18. Next morning: The process is complete and https now works without cert error warnings.

    CDN Done

About CDN Managed TLS/SSL

“Custom Domain HTTPS feature enables you to deliver content to your users securely over your own domain. This is done by encrypting the data between the CDN and your users’ clients (typically web browsers) via TLS protocol (which is a successor of the SSL protocol) using a certificate. Using our “CDN managed certificate” capability, you can enable this feature with just a few clicks and have Azure CDN completely take care of certificate management tasks such as its renewal. You can also bring your own certificate (stored in Azure Key vault ) or even purchase a new certificate through Key vault and have Azure CDN use that certificate for securing the content delivery.”

*More:*
[1] Integrate an Azure storage account with Azure CDN.
This article walks you through creating a storage account in the Azure portal, if you haven’t already done so.
Note
To add your storage web endpoint during the preview of static websites support in Azure Storage, select Custom origin in the Origin type drop-down list. In the Azure portal, you need to do this from your Azure CDN profile instead of directly in your storage account.
[2] Map Azure CDN content to a custom domain
[3] Enable HTTPS on an Azure CDN custom domain.





 TopicSubtopic
  Next: >  
<  Prev:    
This Category:Web Sites
  Next: > Jekyll Next and Previous Post Links 
<  Prev: