Azure Websites Basic Pricing Tier (SSL Support)
So you now have an SSL Certificate? Lets install it to your Azure Website. I distinctly remember, in order for you to have a custom domain (without the .azurewebsite.net), you have to be in the D1 Shared instance in which I am right now.
So from D1 Shared, I upgraded to B1.
Once upgraded, you can now go the SSL settings. You can search it thru the web app settings and in there, click Upload Certificate.
Now remember the PFX file that we created on the earlier part? Use that and use the password that we added when we exported the PFX.
Still within SSL settings, we now have to bind the uploaded SSL with the domain that we want to secure. Click SSL Bindings.
Choose the SNI SSL after using the hostname and certificate name combination. Then click Add Binding.
So that’s it, in just 3 easy steps we already have a working SSL Certificate bound to our site.
Now to check, lets go to https://www.johndelizo.com/ using chrome and IE.
Valid certificate! Sweet!
But our old http only site is still active. So we may need to automatically redirect visitors from http to https. Rewrite should do this. Lets edit web.config!
So my TFS Online is linked to my Azure Websites. I already have a redirect before and should be a fairly easy web.config change, build deploy.
Oh no. I got a message: “We deprecated the hosted XAML build controller on July 1st 2017. We recommend that you migrate to our new build system. However if you still need to run XAML builds during the migration then you must set up a private XAML build controller now”.
I cant believe I never got around to update my own build! Okay, no time to waste, lets just create a new build definition. Stay tuned for part 4.