The following forum(s) are migrating to a new home on Microsoft Q&A (Preview): Azure App Service - Web Apps!

Ask new questions on Microsoft Q&A (Preview).
Interact with existing posts until December 13, 2019, after which content will be closed to all new and existing posts.

Learn More

 none
D1 App Service Plan - custom domain requires SSL binding RRS feed

  • Question

  • Dear community,

    Would it be possible to verify and/or provide a solution for the following please?

    I created an Azure App Service, linked to the D1 App Service Plan, which allows me to connect a custom domain to the App Service.

    I've done that, but now I get the message saying "You have custom domains that are not secured and will cause browser warnings/errors when accessed over https. Click on "Add binding" to secure your custom domains.

    I had the setting for 'HTTPS Only' first configured to 'Yes', but now it's 'No'. So I should be able to access my website through HTTP at least. But whenever I browse to my site, it automatically changes the URL to https and I get to see a 'Privacy error: Your connection is not private'.

    Anyone got any experience with this? Right now I don't see any use for the D1 App Service Plan, and using the B1 plan costs like 6x as much per month, just to add an SSL binding.

    Is it an option to upscale to B1 > create and add SSL binding/certificate > downscale again to D1 and have my site working with https as well?

    Thank you for any feedback.

    Monday, June 10, 2019 7:38 PM

Answers

  • Thanks for your interest in Azure!

    If I have understood correctly you have created App Service in D1 App Service plan and taken custom domain. As  D1 Service plan is on shared infrastructure and included features in this plan is configuring and purchasing custom domain names only. You cannot secure your custom domain using D1 App service plan. Also, there is no such option to first upscale to B1 then creating SSL binding and then again downscale to D1 and have site running with https.

    Reference: https://docs.microsoft.com/en-us/azure/app-service/app-service-web-tutorial-custom-ssl

    About privacy errors Chrome follow securing links strictly while the other browsers are lenient about this.

     

    We are always looking to improve Azure and we try to incorporate customer feedback wherever we can. We kindly request that you share your product feedback at Azure User Voice. This site is viewed by the product group in order to help them determine what new features they can implement or what current features require enhancements.


    Tuesday, June 11, 2019 8:08 AM
    Moderator

All replies

  • About the 'privacy' error. This seems to be a browser based issue on my end.
    Google Chrome automatically redirects to 'https', Edge works fine with 'http'.

    Still looking for a way to get 'https' to work with the D1 App Service Plan. It's a really simple website I'm trying to host in Azure and paying like € 50 per month is way too much.

    Monday, June 10, 2019 7:49 PM
  • Thanks for your interest in Azure!

    If I have understood correctly you have created App Service in D1 App Service plan and taken custom domain. As  D1 Service plan is on shared infrastructure and included features in this plan is configuring and purchasing custom domain names only. You cannot secure your custom domain using D1 App service plan. Also, there is no such option to first upscale to B1 then creating SSL binding and then again downscale to D1 and have site running with https.

    Reference: https://docs.microsoft.com/en-us/azure/app-service/app-service-web-tutorial-custom-ssl

    About privacy errors Chrome follow securing links strictly while the other browsers are lenient about this.

     

    We are always looking to improve Azure and we try to incorporate customer feedback wherever we can. We kindly request that you share your product feedback at Azure User Voice. This site is viewed by the product group in order to help them determine what new features they can implement or what current features require enhancements.


    Tuesday, June 11, 2019 8:08 AM
    Moderator
  • I believe the issue, or somewhat the same issue, was already created at Azure User Voice.
    See: https://feedback.azure.com/forums/169385-web-apps/suggestions/36950533-add-support-for-free-tls-ssl-certificates

    This would probably also resolve the issue for a small startup company to host its website in Azure.

    Currently there are solutions on the market that provide a SSL certificate for 5x less the price it costs in Azure, even though that might be on shared storage, I'm sure many people don't mind sharing storage as long as https works.


    Tuesday, June 11, 2019 11:02 AM