Custom domain validation stuck in Pending 60+ hours

Question

Custom domain validation stuck in Pending 60+ hours

elliot nierman 0

My Front Door Standard profile has a custom domain stuck in domainValidationState: Pending / deploymentStatus: NotStarted since creation on 2026-08-02 (60+ hours).

The _dnsauth validation TXT record has been publicly resolvable since 2026-08-03 and is verifiably correct — the profile's own "Diagnose and solve problems" blade explicitly reports that the public DNS TXT record "correctly matches the expected value." Yet validation never advances (zone hosted on Cloudflare, record unproxied, TTL 300, no CAA restrictions on the domain, token not expired).

I attempted the documented remediation of sending an empty PATCH to the domain API to trigger revalidation (it returned 200). Since then, every write to the domain resource returns 409 Conflict — "The requested operation cannot be executed on the entity as another operation is in progress" for 12+ hours now, so an internal operation appears hung and is holding the entity lock. provisioningState shows Succeeded throughout.

I cannot use Regenerate: the DNS zone is administered by an external third party and re-issuing the TXT value isn't feasible. I also attempted to switch the domain to an Azure pre-validated domain referencing my Static Web App (whose binding for this hostname is Ready, and which the portal's pre-validated dropdown lists as eligible). Blocked by the same 409.

Can someone from the Front Door team advise how to get the hung operation cleared and/or the validation completed, given your own diagnostics confirm the record matches? I can share the subscription ID, domain name, resource names, screenshots, and the activity-log timeline through a private channel or support request if a team member picks this up.

Vinayteja Lellela 110 Reputation points Microsoft External Staff Moderator

2026-08-05T20:05:31.85+00:00
Hello elliot nierman,

What you’re describing (custom domain validation stuck at Pending even when the TXT record is publicly resolvable and “correct”) lines up with known Azure Front Door custom domain ownership validation behavior, but your additional symptom (409 Conflict: “another operation is in progress” plus the hang) suggests there may be a stuck backend operation/lock rather than a DNS/token mismatch.

**What to try
**

Confirm TXT validation mechanics and allow time for re-check

For Non-Azure validated custom domains, Azure Front Door validates ownership by checking the public DNS TXT record. Typical completion is a few minutes, but it can take up to ~24 hours in some cases. The key point from the guidance is:

After you add/update the TXT record, go back to the Azure Front Door portal so it can re-check automatically (status should move Pending → Validated).

If DNS is correct but validation stays Pending, use “Regenerate” (and then re-add TXT)

The documented remediation is:

Regenerate (refresh the TXT value Azure expects)

Then ensure the DNS TXT record is updated to match

Wait for validation to complete (up to 24 hours)

You mentioned you can’t practically re-issue the TXT value with your external DNS provider and also tried switching flows—totally understood. Still, this is the official path when “Pending” doesn’t clear after TXT is correct.

Consider certificate provisioning as a reason for long-lived Pending

When you’re using AFD-managed certificates, “Pending” can persist if the certificate issuance/provisioning is delayed. In that case, it’s not only the TXT ownership check; HTTPS/cert provisioning can hold the overall state.

Action: In the custom domain blade, check the certificate status. If it’s stuck, Azure guidance suggests:

Disable and re-enable the custom domain, then regenerate and re-add TXT (to restart the flow cleanly)

Can you please update us if the action plan provided was helpful?

Should there be any follow-up questions or concerns, please let us know and we shall try to address them.

If these answer your question, click "Upvote" which may be beneficial to other community members reading this thread.
Vinayteja Lellela 110 Reputation points Microsoft External Staff Moderator

2026-08-07T00:43:46.53+00:00

Hello **elliot nierman,

**following up to see if you had a chance to check the above response and if it was helpful. Please let me know if you have any questions.
Vinayteja Lellela 110 Reputation points Microsoft External Staff Moderator

2026-08-11T17:57:28.0633333+00:00

Hello elliot nierman,

Following up to see if you had a chance to check the above response and if it was helpful. Please let me know if you have any questions.

Your answer

Vinayteja Lellela 110 Reputation points Microsoft External Staff Moderator

2026-08-07T00:43:46.53+00:00

Hello **elliot nierman,

**following up to see if you had a chance to check the above response and if it was helpful. Please let me know if you have any questions.
Vinayteja Lellela 110 Reputation points Microsoft External Staff Moderator

2026-08-11T17:57:28.0633333+00:00

Hello elliot nierman,

Following up to see if you had a chance to check the above response and if it was helpful. Please let me know if you have any questions.