Azure managed HTTPS certificate stuck on domain validation

Jonah Foster 1

Hi, I've been stuck on the domain validation step of enabling HTTPS for 24 hours now. My domain CNAME is directed to my endpoint. I managed to restart it, but it remains stuck on Domain Validation.

Ravi Kanth Koppala 3,231 Reputation points Microsoft Employee

2022-12-19T03:31:40.843+00:00
@Jonah Foster ,

I'm sorry that you're having trouble with your Azure-managed HTTPS certificate. The domain validation process may be taking longer than expected due to issues on the Azure side or with your domain registrar.

In the meantime, you can try the following steps to troubleshoot the issue:

Check the certificate's status in the Azure portal to see if any errors or warning messages might indicate the cause of the issue.

Ensure the domain you're validating is configured to point to Azure. You can do this by checking the DNS records for your domain.

If using a custom domain for your Azure app, ensure you've added the required DNS records to your domain's DNS configuration.

If you're using a third-party DNS provider, check with them to see if any known issues or maintenance might affect the domain validation process.

If none helps, you may need to contact Azure support. They should be able to help you determine the cause of the issue and provide guidance on how to resolve it.

----------

Please "Accept as Answer" and Upvote if any of the above helped so that it can help others in the community looking for remediation for similar issues.
ChaitanyaNaykodi-MSFT 22,386 Reputation points Microsoft Employee

2022-12-19T21:18:59.88+00:00

@Jonah Foster ,

Welcome to the Microsoft Q&A forum.
If I understand it correctly your Custom Domain HTTPS process for your Azure CDN is stuck on domain validation step and you wish to stop this process and start it again.

To disable this process can you try running the Disable-AzCdnCustomDomainCustomHttps PowerShell command as shown here and see if it helps in disabling the Custom Domain HTTPS process. Please let us know if you get any errors after executing this command as the process might be stuck in the backend and might additional troubleshooting. You can execute this command via Azure Cloud Shell.

If you are successfully able to stop the process, as mentioned here please do not forget to validate if your custom domain's CNAME is mapped to the CDN Endpoint before restarting the process.

Hope this helps! Please let me know if you have any additional questions. Thank you!

Additional references:
AZ CLI command to disable https - https://learn.microsoft.com/en-us/cli/azure/cdn/custom-domain?view=azure-cli-latest#az-cdn-custom-domain-disable-https
ChaitanyaNaykodi-MSFT 22,386 Reputation points Microsoft Employee

2022-12-20T19:52:15.92+00:00

@Jonah Foster ,

Based on your recent edit to the question, I understand that your domain CNAME is directed to the endpoint and were able to restart Custom Domain HTTPS validation process, but the request is still stuck in Domain Validation.

I think to troubleshoot the exact issue here you will need to create a support ticket as support engineer can take a look at the backend logs and involve DigiCert if required as they verify the custom domain. If you have a support plan, I kindly request you to create a support request with us. If you do not have a support plan, can you please refer to my private message below. Thank you!
walt 0 Reputation points

2023-04-13T18:25:54.7933333+00:00

Hi, perhaps helpful: Also used (Static) App Service to add a custom domain - hosted by Azure DNS and registrar being Azure - only to discover the automated addition of such custom domain is STUCK for days..
Azure's own automation adds a TXT record of for name '@' with a generated value which is NOT what the domain validation logic is checking...

After adding a TXT record for name 'asuid' with the same generated value, the domain validation logic of the (Static) App Service flagged the custom domain almost immediately as Validated.

Brilliantly ironic, I came across the 'asuid' TXT record through old documentation trying to transfer out the domain to another registrar..