The final step now is to add the SSL certificate. Click Add custom domain to complete the change.Īzure Portal kindly suggests now would be a great time to add those missing SSL certificates: Adding a free SSL certificate for the web app Once Hostname availability and Domain ownership turn green, you’re good. Switching back to the Custom domains view for the web app, I can click on Validate to verify when the change is visible for Azure: I chose to use the default, a CNAME entry, and added the proposed entry to my record set: This needs to be validated, either via a CNAME record in my zone, or a regular A record. I could use Azure CLI for this, but since it’s a one-time change, I see little value in scripting this.įirst, I need to go to Web App > Custom domains, where I can add my custom domain for the web app: I have this zone hosted in Azure DNS already, so it’s only a matter of adding a new record set via Azure Portal. Usually this would be I chose to add a new sub-domain called freessl under my existing domain. Thankfully I have a ‘few’ spare domain names parked somewhere, so now it’s only a matter of picking one up, and adding two entries in DNS. Obviously, I cannot request an SSL certificate for. In order to try out the free SSL certificate capability, I need to create a custom domain and a sub-domain for the web app. To verify my web app works, I can simply call it with curl.exe from a Windows 10 command line: Preparing DNS for the web app and free SSL certificate I now have a web app, and a corresponding app plan provisioned: To see which app plans are supported, run: az webapp list-runtimes This differs depending on if you’re provisioning the web app on a Linux-based app plan, or a Windows-based app plan. Note, that I need to specify the runtime for the web app. This is the minimum pricing tier, that still allows SSL to be enabled.Īnd finally, all I need to do is provision the actual web app: az webapp create -name free-ssl-webapp -plan free-ssl-app-plan -resource-group free-ssl -runtime "DOTNETCORE|Latest" I chose to provision a Linux-hosted app plan, and the SKU is B1. To create my app plan, I need to type the following in Azure Cloud Shell: az appservice plan create -name free-ssl-app-plan -is-linux -location westeurope -sku B1 -resource-group free-ssl This is needed for the compute resources of the web app, as well as for defining the capabilities of my web app. Next, I’ll need to provision an app plan for the web app. This creates a new resource group named free-ssl. If you’re not familiar with Azure CLI, see my guide for getting started with Azure CLI here.įirst, I’ll create a new resource group: az group create -name free-ssl -location westeurope Opening Azure Cloud Shell from Azure Portal, I can provision this easily. And the web app requires a resource group, to begin with. In order to test this capability, I will need a web app. Setting up a test web app using Azure CLI So, I went on to try this new capability. I can finally secure all my web apps without paying hundreds of dollars to third-parties for SSL certificates. “ Wow, that’s beyond great!”, I remember thinking on my way to Orlando for Ignite at the time. One of the many announcements Microsoft made during Ignite 2019 was the capability to add free SSL certificates to Web Apps on Azure. Thanks for reading my blog! If you have any questions or need a second opinion with anything Microsoft Azure, security or Power Platform related, don't hesitate to contact me.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |