Azure Static Web Apps custom domain permanently stuck in Deleting

Corey Wride 0 Reputation points
2026-08-12T20:16:37.4866667+00:00

The custom domain wwwXXXXXXXXXXXXXXXXXXth is permanently stuck in the Deleting state on the Azure Static Web App verifaxXXXXXXXXXXXXXeholder.

Multiple attempts to delete the custom-domain association and the parent Static Web App have failed with ResourceOperationFailure. A healthy replacement app, verifXXXXXXXr-v2, cannot bind the domain because the original app still claims it.

The replacement deployment works correctly at its default Azure hostname and returns HTTP 200. Public DNS also points www.xXXXXXXXXXXto the replacement hostname. This is not a deployment, application-configuration, or DNS propagation issue.

Please escalate this to the Azure Static Web Apps engineering team to force-delete the stale custom-domain association from the original app and release the domain claim for the replacement app.

Recent failed deletion correlation IDs:

  • 1f0XXXXXXXXXXXXXXXXX424446a5d9
  • 641f5d7XXXXXXXXXXXxxf-b4be6b3f088f
  • 5599cb0XXXXXXXXXXXXXXXXXXXXXXbe71c1
Azure Static Web Apps
Azure Static Web Apps

An Azure service that provides streamlined full-stack web app development.

0 comments

2 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Allan Solomon Mejia 7,915 Reputation points
    2026-08-12T20:22:25.4766667+00:00

    Hello @Corey Wride

    Based on the symptoms, this appears to be a stale custom-domain association on the Azure Static Web Apps backend, rather than a DNS or application deployment issue.

    Since the domain remains stuck in Deleting, deletion returns ResourceOperationFailure, and the original Static Web App still holds the domain claim, further DNS changes or repeated delete/recreate attempts are unlikely to resolve it.

    Similar Static Web Apps custom-domain cases have required Microsoft backend intervention to release the stale association.

    At this point, I recommend that a Microsoft moderator help escalate this to the Azure Static Web Apps engineering team. The correlation IDs you've already provided should be useful for tracing the failed operations.

    Keep the subscription/resource IDs and UTC timestamps available if requested through a private support channel.

    Please "Accept the Answer" if this information helped you. This will help us and others in the community as well.

    Was this answer helpful?

    0 comments
  2. Praneeth Maddali 12,670 Reputation points Microsoft External Staff Moderator
    2026-08-13T00:22:16.81+00:00

    Hi @Corey Wride

    Thank you for your patience while we looked into this.

    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.

    Please "accept" if the information helped you. This will help us and others in the community as well.

    Was this answer helpful?

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.