Static Web Apps custom domains stuck in "Deleting" state for 24+ hours — DELETE operations fail, re-adding has no effect

Question

Hi,

I have two Azure Static Web Apps (Free tier, West Europe) in two different resource groups, and I'm trying to bind one custom domain to each:

PLL retirée et collée dans un message privé.

Both bindings have now been stuck in Deleting for more than 24 hours. az staticwebapp hostname list still reports status: Deleting with the original error message, and any new add attempt is absorbed by the stuck resource.

Questions:

It looks like the custom-domain state machine is wedged on the platform side for these two resources. Could someone unstick/purge these two customDomains resources so I can re-add the domains? I can share the full subscription ID privately if needed. Is there anything wrong with my setup that caused the initial failure, or was it a transient platform issue? (CNAME created and propagated first, then domain added with CNAME validation — my understanding is that this is the documented procedure.)

Thank you!

Answer 1

Hi @Praneeth Maddali

Confirming the mitigation worked — everything is now resolved. For the record, here is what I observed when retrying today (10 July, ~10:25 UTC):

1. DELETE now works: I re-issued the delete on both stuck bindings (az staticwebapp hostname delete). Unlike before the mitigation (where deletes silently failed after ~10 minutes and the resources stayed in Deleting), the purge was effective immediately — both customDomains resources disappeared from az staticwebapp hostname list right away.
2. Re-adding succeeded: I then re-created both bindings with CNAME validation (az staticwebapp hostname set --validation-method cname-delegation). Both went RetrievingValidationToken → Validating → Ready in about 2 minutes.
3. End-to-end verified: both domains serve HTTPS with the free managed certificate (issued with no noticeable delay), our Entra ID sign-in works on the custom URLs, and a subsequent ARM/Bicep deployment declaring the same Microsoft.Web/staticSites/customDomains resources completed successfully (idempotent PUT on the validated domains).

So the initial failure does appear to have been a transient platform issue rather than a configuration problem (the CNAMEs had been created and propagated before the first add attempt), and the stuck Deleting state machine was indeed unwedged by your mitigation.

Thanks a lot for the quick turnaround — from my side this case can be closed.

Answer 2

Hi @John Alinea

We have received confirmation that mitigation has been applied, and your custom domain issue should now be resolved. Could you please retry the operation and verify whether everything is working as expected?

If you are still experiencing any issues, please reply with an update and any relevant details. We will be happy to continue assisting you and investigate further if needed.

We look forward to hearing back from you. Si la réponse est utile, veuillez cliquer sur "Accepter la réponse" et oui, cela peut être bénéfique pour les autres membres de la communauté.

Si vous avez d'autres questions, faites-le moi savoir dans les "commentaires" et je serais heureux de vous aider.