Azure Static Web Apps custom-domain child remains Deleting after terminal Failed DELETE — backend cleanup required

Question

Azure Static Web Apps custom-domain child remains Deleting after terminal Failed DELETE — backend cleanup required

D Currie 40

An Azure Static Web Apps DEVELOPMENT custom-domain child is stuck in Deleting after its single asynchronous DELETE reached terminal Failed.

TXT ownership validation had succeeded. Authoritative DNS, the DNS-only CNAME, and CAA are correct, and no competing Azure domain binding was found. Earlier create/update operations were accepted but ended Failed with Azure’s “unknown error.” The parent Static Web App and generated hostname remain healthy with trusted TLS and HTTP 200.

We submitted exactly one child-only DELETE at 2026-08-13T11:42:09Z. Its long-running operation is terminal Failed, while direct child GET and the Static Web Apps hostname list still show one matching child in Deleting. We have not repeated DELETE, submitted PUT, changed DNS, or modified the parent.

This now requires Azure Static Web Apps provider/backend reconciliation. Please escalate this through a private support channel and clear only the stuck custom-domain child and stale hostname claim while preserving the parent SWA, generated hostname, deployed content, and DNS. We can provide the subscription, resource ID, Activity Log, and complete correlation/operation IDs privately.

Golla Venkata Pavani 7,530 Reputation points Microsoft External Staff Moderator

2026-08-13T15:01:48.56+00:00

Hi @D Currie

Thank you for contacting Microsoft Support regarding the issue where the custom domain is stuck in the "Deleting" state.

We have started investigating the issue and are currently reviewing the configuration and backend status. We will keep you updated on our findings and share any recommendations or next steps as soon as possible.

If you have any additional details that may help with the investigation, please feel free to share them with us.

We appreciate your patience and understanding while we work on resolving this issue.
D Currie 40 Reputation points

2026-08-13T19:17:17.0166667+00:00

Thank you for applying the DZXC-65Z mitigation. We retried once as requested. The stuck Deleting child cleared: direct GET returned ResourceNotFound and the hostname list was empty after 33 seconds. We then recreated the same custom domain once with the existing dns-txt-token validation and unchanged DNS. After a bounded 15-minute observation, Azure still shows exactly one child in Validating and managed HTTPS is unavailable. We made no further DELETE or PUT, no DNS change, and no parent change; the generated hostname remains healthy with trusted TLS and HTTP 200. Please continue the provider/backend investigation and advise whether further reconciliation is required. We can provide identifiers privately.
TP 163.1K Reputation points Volunteer Moderator

2026-08-13T19:30:36.0666667+00:00

@D Currie TP here. Did you remove the old dns-txt-token from your DNS, add custom domain to your SWA, generate new token, and create new DNS txt record? Please note that depending on the TTL of your TXT record you may want to give it time to expire after deleting TXT record before generating new token.

I like to make TTL as low as possible (e.g. 1-5 minutes) for TXT record to aide with troubleshooting.

Answer accepted by question author

0 additional answers

Your answer

Golla Venkata Pavani 7,530 Reputation points Microsoft External Staff Moderator

2026-08-13T15:01:48.56+00:00

Hi @D Currie

Thank you for contacting Microsoft Support regarding the issue where the custom domain is stuck in the "Deleting" state.

We have started investigating the issue and are currently reviewing the configuration and backend status. We will keep you updated on our findings and share any recommendations or next steps as soon as possible.

If you have any additional details that may help with the investigation, please feel free to share them with us.

We appreciate your patience and understanding while we work on resolving this issue.
D Currie 40 Reputation points

2026-08-13T19:17:17.0166667+00:00

Thank you for applying the DZXC-65Z mitigation. We retried once as requested. The stuck Deleting child cleared: direct GET returned ResourceNotFound and the hostname list was empty after 33 seconds. We then recreated the same custom domain once with the existing dns-txt-token validation and unchanged DNS. After a bounded 15-minute observation, Azure still shows exactly one child in Validating and managed HTTPS is unavailable. We made no further DELETE or PUT, no DNS change, and no parent change; the generated hostname remains healthy with trusted TLS and HTTP 200. Please continue the provider/backend investigation and advise whether further reconciliation is required. We can provide identifiers privately.
TP 163.1K Reputation points Volunteer Moderator

2026-08-13T19:30:36.0666667+00:00

@D Currie TP here. Did you remove the old dns-txt-token from your DNS, add custom domain to your SWA, generate new token, and create new DNS txt record? Please note that depending on the TTL of your TXT record you may want to give it time to expire after deleting TXT record before generating new token.

I like to make TTL as low as possible (e.g. 1-5 minutes) for TXT record to aide with troubleshooting.

Answer 1

Golla Venkata Pavani 7,530 Microsoft External Staff Moderator

Hi @D Currie

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.

0 comments

Answer 2

Hi,

Can you retry deleting your custom domain now? I just retried mine and it successfully deleted after about 2-3 minutes. Previously it had been stuck for many hours.

Below is latest update from the Service issue DZXC-65Z:

Service: Static Web Apps

Region: Global

Event tags: --

Impact Statement: Starting at 14:30 UTC on 11 August 2026, you have been identified as an affected customer using Azure Static Web Apps in multiple regions who may experience failures or delays when deleting custom domains for resources hosted in the region. At this time, the impact is limited to a subset of customers.

Current Status: Our teams have completed mitigation actions and are currently monitoring recovery progress. The issue was attributed to a backlog in the job queue responsible for custom domain deletion operations, which caused deployment requests to time out. Mitigation efforts included reducing the batch size of operations and stopping specific operations to accelerate queue recovery. Current telemetry indicates that the queue backlog is decreasing rapidly and is expected to reach a healthy state shortly.

Initial assessments indicate that custom domain creation and update workflows remain healthy, with the impact limited to delayed or failed custom domain deletion requests while the backlog was present.

We are validating recovery by monitoring system performance and confirming successful retries from affected customers.

The next update will be provided in 02 hours, or as events warrant.

Thanks.

-TP

D Currie 40 Reputation points

2026-08-13T19:03:35.67+00:00

Thanks!
D Currie 40 Reputation points

2026-08-13T20:52:17.8866667+00:00

Your help was great and saved us a lot of time and head-scratching. Thanks a lot - much appreciated!