Azure App Service free Managed Certificate for SSL/TLS

Question

So free "Managed Certificate" is now available in Preview and it doesn't support naked/apex domains.
azure.microsoft.com/announcement

Now it's a SEO best practice to stick to either 'www' or no 'www' and do a 301 redirect.

How are we supposed to do a https://contoso.com to https://www.contoso.com redirect?

Seems we have to stick with Let's Encrypt for now.

Answer 1

For apex or wildcard you'd need to bring your own cert. LetsEncrypt is awesome.

To redirect from apex to www, you can bind the apex to the ip of a Function. Then inside the function do a redirect. Of course then the redirect Function App would need a cert.

Answer 2

For my understanding, supporting apex certificates is a quite basic feature that should be supported out-of-the box!

So basically, for now, Microsoft Managed Certificates are not very useful.

For reference, i'm using successfully https://github.com/shibayan/appservice-acmebot:

This function provide easy automation of Let's Encrypt for Azure App Service. This project started to solve some problems.

✔ Support multiple app services

✔ Simple deployment and configuration

✔ Robustness of implementation

✔ Easy monitoring (Application Insights, Webhook)

They can manage multiple App Service certificates with single Function App.

Answer 3

Hi @Martin Meixger , the product group is exploring supporting such a feature, but nothing definite at this point in time. I would advise submitting feedback.

Answer 4

Shameless plug, since it looks like Let's Encrypt is still needed, here's my solution (based on letsencrypt-siteextension): https://github.com/ohadschn/letsencrypt-webapp-renewer

Answer 5

@MartinMeixger-1476 While we’re working on supporting apex domain, a current tentative workaround we suggest is to forward apex domains to subdomain such as www. If you are using App Service Domain, you can forward your domain by going to Advanced Management portal of the domain resource.

Attached screenshots show the steps.