Azure Static Web Apps — two custom domains stuck in "Deleting" state for 12+ hours, blocking parent resource and RG deletion (East US 2, Slice 7)

Summary

Two custom domains on my Azure Static Web App have been stuck in "Deleting" state for over 12 hours. The parent Static Web App and Resource Group cannot be deleted either, as they are blocked by the stuck child resources.

Environment

• Region: East US 2
• SKU: Free
• Slice: 7 (hostname pattern: *.7.azurestaticapps.net)
• Domains affected: apex domain and www subdomain

Timeline

1. Created a new Static Web App and deployed successfully
2. Attempted to add custom domains (www via CNAME, apex via dns-txt-token)
3. Both domains failed during validation with: "An unknown error has occurred while adding your custom domain. Please try again later."
4. Domains entered "Failed" status
5. Attempted deletion — both transitioned to "Deleting" and have been stuck there for 12+ hours

Troubleshooting completed

• Portal DELETE button: Error notification, no state change
• az staticwebapp hostname delete: Returns OK, domain remains in Deleting
• Direct ARM REST DELETE (api-version 2025-05-01): Returns 202 Accepted, async operation stuck in "InProgress"
• Remove ALL DNS records (CNAME, A, TXT) from DNS provider: Done, propagation confirmed via public DNS
• Wait 12+ hours: No state change
• Delete parent Static Web App: Blocked by stuck children
• Delete Resource Group (az group delete): Also stuck in Deleting
• Check resource locks: None found
• Check Service Health: No active incidents published

Async operation status (stuck)

{
  "status": "InProgress",
  "startTime": "2026-08-12T14:07:42.0021500Z",
  "endTime": null
}

Additional observations

I attempted creating new Static Web Apps in different regions (West US 2, Central US, East Asia) with both Free and Standard SKUs. All of them were assigned to slice 7, suggesting this may be a widespread issue affecting slice 7 specifically.

Context

• The www domain was previously bound to a different Static Web App in another tenant/subscription. That binding was properly removed before attempting to add it to the new resource.
• This matches the pattern of the July 2026 incident (question 5940933) which was resolved only after a backend mitigation applied by the SWA Product Group.
• I also see other reports from today (August 12) with the same symptoms on slice 7.

Request

Could the Static Web Apps Product Group please:

1. Inspect the custom-domain state in the backend for my resource
2. Force-complete/purge the stuck customDomains child resources
3. Release the stale hostname claims from slice 7

I can provide subscription ID, resource details, and correlation IDs via private message if needed.

Thank you.