Front Door managed cert for apex domain stuck in PendingRevalidation, TXT record is correct, expires 2026-10-06. Can revalidation be re-run without regenerating the token?

NickG-6046 5 Reputation points
2026-10-02T19:05:17.29+00:00

Problem description

The Front Door-managed certificate for our apex custom domain (Premium profile) is in PendingRevalidation. It probably entered that state around 2026-08-22, 45 days before expiry. The certificate expires on 2026-10-06 19:59 UTC.

Environment

  • Azure Front Door Premium, managed certificate on an apex custom domain
  • The apex uses an A record to Front Door, not a CNAME
  • DNS is hosted by a third party, not Azure DNS
  • Validation by _dnsauth TXT record

What I've checked

  • The _dnsauth TXT record matches the current validationToken on the domain. It is served by all three authoritative nameservers and by public resolvers.
  • The portal diagnostic ("Azure Front Door Custom Domain not Validated") says the public TXT record "correctly matches the expected value".
  • There are no CAA records.
  • The domain's token shows an expiry date of 2026-04-13, which is in the past.

Why I can't regenerate the token

The docs say to click Regenerate and add the new TXT value. We can't do that in time. A new value needs a change by the third-party DNS owner, whose process will not finish before the certificate expires. Microsoft support (open case) also recommended not regenerating, because the published token is already correct.

What I need

  1. Can Front Door re-run revalidation and certificate rotation using the existing published token?
  2. Is there a supported way to re-run validation on the existing token? The docs mention an empty PATCH to the custom domain API (for BYOC-validated domains) and a RefreshValidation action in the FAQ. But the only CLI/PowerShell command I can find, az afd custom-domain regenerate-validation-token / Update-AzFrontDoorCdnCustomDomainValidationToken, issues a new token. Does either apply to a DNS-validated managed certificate?
  3. If not, is there a supported way to clear the stuck state without a new token?

This domain carries production traffic and we have about three business days.

Azure Front Door
Azure Front Door

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


3 answers

Sort by: Oldest
  1. Hemant Bharadwaj 375 Reputation points Microsoft Employee
    2026-10-25T20:18:28.8066667+00:00

    Hello Nick,

    For an Azure Front Door-managed certificate, certificate rotation depends on successful domain-ownership revalidation. There is no documented customer-facing operation that forces certificate renewal by reusing an expired validation token.

    • Refresh validation can make Front Door check DNS again, but it does not extend or reactivate an expired token.
    • An empty PATCH of the custom-domain resource is not a supported substitute for managed-certificate DNS revalidation.
    • The CLI and PowerShell regenerate-validation-token operations intentionally generate a new token.

    If Front Door considers the token expired, the supported self-service process is to regenerate it, replace the _dnsauth TXT value at the authoritative provider, wait for propagation, and refresh the domain and certificate status.

    Because the October 6, 2026 expiration date has passed, first check whether Front Door completed an automatic recovery. If it remains stuck, keep the existing custom-domain resource and support case open and ask Azure Support to inspect the backend domain-validation and certificate-deployment state. Do not delete and recreate the production custom domain unless Support recommends it.

    Documentation:

    If changing TXT requires an external process, the practical choices are to expedite that DNS change or have Support investigate the stuck backend state. The expired token itself cannot be extended from the customer side.

    Was this answer helpful?

    0 comments No comments

  2. Alex Burlachenko 26,135 Reputation points MVP Volunteer Moderator
    2026-10-26T07:51:56.5766667+00:00

    Hi NickG-6046 & thx for join me at Q&A platform,

    The key detail here is the validation token expiry date of April 13, 2026. Your DNS record matching the validationToken proves that the published TXT value is correct, but it doesn't prove that Front Door still considers that token valid for certificate renewal.

    For an apex domain using an A record, Azure Front Door can't rely on the usual direct CNAME validation path. That's why the managed certificate enters PendingRevalidation as renewal approaches.

    Regarding your specific questions, there's no documented customer-facing operation that renews an Azure Front Door-managed certificate by reactivating an expired DNS validation token.

    The RefreshValidation reference in the FAQ is a bit confusing. Refreshing validation can trigger another check, but it doesn't extend the token's validity or guarantee certificate rotation. The empty PATCH mentioned in the documentation relates to BYOC-based domain approval and isn't a supported workaround for an expired TXT token on a managed certificate.

    And yes, the CLI and PowerShell commands you found regenerate the token. They aren't equivalent to retrying validation with the existing value.

    I also noticed that the moderator's October 25 instructions assume Azure DNS is hosting the zone. That doesn't apply to your third-party DNS setup, where the new TXT value requires a separate change process.

    Given that Microsoft Support already advised you not to regenerate, I'd keep that support case open and request an escalation to the Azure Front Door certificate management team. They need to check the backend domain-validation state, token expiry, certificate issuance status, and whether a service-side recovery is possible without changing DNS. I wouldn't assume such a recovery is supported until engineering confirms it.

    There's also an important timing issue now: the October 6 certificate expiry date has already passed. I'd verify the certificate currently being served to clients, including its serial number and notAfter date, rather than relying only on the portal's certificate state. Front Door may have recovered in the meantime, but that needs to be confirmed.

    If the certificate is still expired, this should be treated as an active production incident. If it was renewed, I'd still ask Support to explain what cleared PendingRevalidation, particularly given the expired token.

    I wouldn't delete and recreate the custom domain, switch certificate types, or regenerate the token against Support's existing advice without an agreed recovery plan.

    The critical point is that correct DNS resolution and successful domain validation are not the same thing when the validation token has expired. At this stage, the existing support case is the right place to get a definitive answer about backend recovery.

    rgds,

    Alex

    p.s. if my answer is help - pls mark it as an answer

    Was this answer helpful?

    0 comments No comments

  3. Nick G 0 Reputation points
    2026-10-26T11:14:06.4733333+00:00

    Issue Resolved the hard way of coordinating new DNS records after regeneration.

    Was this answer helpful?

    1 person found 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.