Azure Front Door Health Probe Intermittently Failing with CertificateError

Sanjay kumar 40 Reputation points
2026-10-29T10:54:38.5633333+00:00

We are experiencing intermittent Azure Front Door health probe failures with CertificateError. Azure Front Door sends HTTPS health probes to an Azure App Service configured as the origin. Both Front Door and App Service use Azure-managed certificates.

The issue started suddenly, with no recent changes to our environment. The origin health status fluctuates, with failures and recoveries occurring at inconsistent time intervals.

Checks performed:

Verified that the origin hostname and origin host header match.

Confirmed HTTPS on port 443 and certificate-name validation is enabled.

Tested TLS connectivity from a jump server; certificate validation succeeded with SSL policy errors: None.

Confirmed that normal Front Door requests reach the App Service and return HTTP 200 over TLS 1.2.

Checked Azure Service Health; no relevant outage was identified.

Despite these checks, health probe logs continue to report CertificateError.

Has anyone experienced a similar issue? What additional checks or troubleshooting steps would you recommend to identify the root cause? Any suggestions or help would be appreciated

Azure Front Door
Azure Front Door

An Azure service that provides a cloud content delivery network with threat protection.

0 comments No comments

1 answer

Sort by: Oldest
  1. Salamat Shah 990 Reputation points MVP
    2026-10-29T11:56:17.7866667+00:00

    Dear Kumar,

    CertificateError in Azure Front Door health probes usually means Front Door cannot consistently validate the SSL certificate presented by the origin, even if normal user traffic works.

    Temporarily disable and re-enable the origin or recreate the origin entry to force Front Door configuration refresh. If the issue persists and logs show intermittent failures despite valid certificates, open a Microsoft support ticket and provide Front Door health probe logs and timestamps for backend investigation. but before that check below:

    • Verify the origin certificate chain is complete (intermediate certificates included).
    • Ensure the certificate CN/SAN matches the Origin Host Header configured in Front Door.
    • Check for certificate renewal/rotation issues with Azure-managed certificates.
    • Confirm all App Service instances return the same certificate.
    • Review Front Door diagnostic logs and App Service TLS logs around probe failure times.
    • Test connectivity from different regions, as Front Door probes originate globally.

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.