Custom Domain Stuck in Validated-but-Unbound State for Azure Static Web Apps

Description:
My Azure Static Web App custom domain is stuck in a validated-but-unbound state. The TXT validation succeeded previously, and the portal shows “Validated,” but the binding never completes and the SSL certificate is not issued.

The “Generate Code” option is no longer available, and the domain cannot be revalidated or reset from the portal. The required TXT validation record is no longer present in my DNS zone (Bluehost), but Azure continues to show the domain as validated, preventing me from generating a new token.

This appears to be a known Azure Static Web Apps backend issue where the validation state becomes cached and cannot be cleared by the user.

Request:
Please reset the backend validation state for my custom domain so I can rebind it and generate a new TXT validation token. Once the backend state is cleared, I will re-add the TXT record and complete the binding.

Details:

Service: Azure Static Web Apps

Issue: Domain validation cached; binding cannot complete

Symptoms:

Portal shows “Validated”

No “Generate Code” option

SSL certificate not issued

Binding stuck

TXT record missing from DNS

Expected Action: Backend validation reset

Thank you — once the validation state is cleared, I can complete the binding normally.