GoDaddy SSL to Azure but website is still unsecure

Hii @tim ellis ,

Thanks for reaching out. It sounds like you’ve successfully obtained an SSL certificate from GoDaddy, but your website hosted on Azure is still showing as Not Secure. Below are the recommended steps to confirm that the certificate has been properly received and configured in Azure.

• Please sign in to the Azure Portal and navigate to App Services, then select your application.
• Under Custom domains, verify that your custom domain is listed. If the status shows No binding, this indicates that the SSL certificate has not yet been applied to the domain.
• If the certificate is already uploaded, you can bind it by selecting Add binding next to the domain, choosing the appropriate SSL certificate, validating it, and completing the binding process.
• Please also confirm that your DNS settings are correct. Your domain’s A record or CNAME record must point to the Azure App Service endpoint. If you are using an IP‑based SSL, ensure that the A record points to the dedicated IP address provided by Azure after the SSL binding is created.
• Once the binding is complete, we recommend enabling HTTPS Only in the App Service settings to ensure all traffic is forced over a secure HTTPS connection.
• After making these changes, allow some time for DNS and SSL propagation. You can then test your site by visiting:https://yourdomain.com

Use Azure CLI: You can also use Azure CLI to check the SSL bindings. Run the following commands:

• To list the custom domains assigned to your app:

         az webapp config hostname list --resource-group <ResourceGroupName> --name <AppName>
  

• To list the SSL certificates available to your app:

         az webapp config ssl list --resource-group <ResourceGroupName> --name <AppName>
  

• To bind the certificate if it is not already bound:

         az webapp config ssl bind --certificate-thumbprint <Thumbprint> --ssl-type
  

• If the website is still showing as unsecure, here are a couple of troubleshooting points:
  • Make sure the certificate isn't self-signed or expired.
  • Ensure there are no issues with the DNS A or CNAME records.

Reference:
https://learn.microsoft.com/en-us/troubleshoot/azure/app-service/connection-issues-with-ssl-or-tls/troubleshoot-domain-and-tls-ssl-certificates
https://learn.microsoft.com/en-us/troubleshoot/azure/app-service/troubleshoot-azure-app-service-certificates#step-by-step-troubleshooting-flow
Kindly let us know you need further assistance on this issue.
Please "accept" if the information helped you. This will help us and others in the community as well.

To confirm that Azure has received your SSL certificate from GoDaddy, you can follow these steps:

1. Check SSL Binding: Ensure that your SSL certificate is correctly bound to your Azure App Service. You can do this by navigating to the TLS/SSL settings in the Azure portal for your web app. Verify that the certificate appears in the list and is bound to the correct custom domain.
2. Use Azure CLI: You can also use Azure CLI to check the SSL bindings. Run the following commands:
   • To list the custom domains assigned to your app:

          az webapp config hostname list --resource-group <ResourceGroupName> --name <AppName>
     

   • To list the SSL certificates available to your app:

          az webapp config ssl list --resource-group <ResourceGroupName> --name <AppName>
     

   • To bind the certificate if it is not already bound:

          az webapp config ssl bind --certificate-thumbprint <Thumbprint> --ssl-type SNI --name <AppName> --resource-group <ResourceGroupName>
     

3. Verify Domain Ownership: If your certificate is still in a Pending Issuance state, ensure that you have completed the domain verification process. This may involve adding a TXT record to your DNS settings to prove ownership of the domain.
4. Check for Errors: If the website is still showing as unsecure, check for any errors in the Azure portal regarding the SSL certificate, such as missing intermediate certificates or incorrect domain bindings.

If you continue to face issues, consider reaching out to Azure support for further assistance.

References:

• Troubleshoot domain and TLS/SSL certificate problems in Azure App Service
• Troubleshoot Azure App Service certificates