Azure Static Web Apps – Custom Domain/Hostname Binding Stuck

Jithin P 0 Reputation points
2026-08-14T05:49:15.94+00:00

Azure Static Web Apps – Custom Domain/Hostname Binding Stuck

Hi Microsoft Support/Community,

I’m experiencing an issue with a custom domain hostname binding on Azure Static Web Apps that appears to be stuck and cannot be removed.

I have already tried removing the custom domain through the Azure Portal, Azure CLI, and PowerShell, but the hostname binding is still present/stuck and I cannot successfully clear it or add the domain again.

I have also checked and removed the relevant DNS records, but this has not resolved the issue.

Troubleshooting already attempted:

  • Removed the custom domain from the Azure Portal
  • Used az staticwebapp hostname delete
  • Tried the corresponding PowerShell cmdlet
  • Attempted the operation through Azure Resource Manager/REST API
  • Removed the related DNS records and waited for propagation
  • Retried the deletion multiple times

At this point, it appears that the custom-domain association may be stuck in the Azure Static Web Apps backend, rather than being an issue with my local configuration.

Could someone from the Azure Static Web Apps product team please help clear/reset the stale hostname binding from the backend?

I need the existing hostname association completely removed so that I can configure the custom domain again.

Thank you for helping investigate this. Since Portal, CLI, PowerShell, and REST attempts have all failed, I believe this may require a backend cleanup or manual intervention by the Azure Static Web Apps team.

Azure DNS
Azure DNS

An Azure service that enables hosting Domain Name System (DNS) domains in Azure.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. TP 163K Reputation points Volunteer Moderator
    2026-08-14T06:00:52.44+00:00

    Hi,

    Please retry deleting your custom domain(s) via the portal. The underlying issue has been mitigated. I retried deleting mine earlier and it successfully deleted after about 2-3 minutes. Previously it had been stuck for many hours.

    Below is excerpt from Post Incident Review (PIR) DZXC-65Z:

    What happened?

    Between 14:30 UTC on 11 August 2026 and 15:50 UTC on 13 August 2026, a platform issue resulted in an impact to the Azure Static Web Apps service in multiple regions. Impacted customers may have experienced failures or delays when deleting or adding custom domains for Azure Static Web Apps resources hosted in the affected regions. The impact was limited to a subset of customers.

    What went wrong, and why?

    A platform issue caused an increase in processing backlog for operations responsible for managing custom domain configuration changes. As a result, requests to delete or add custom domains were delayed or failed for a subset of Azure Static Web Apps customers. The issue was mitigated after service processing queues recovered to normal operating levels and pending operations were cleared.

    How did we respond?

    • 14:30 UTC on 11 August 2026 – Customer impact began.
    • 13:04 UTC on 12 August 2026 – The issue was identified through customer reports of failures and delays when deleting custom domains.
    • 23:28 UTC on 12 August 2026 – We identified elevated service processing queues as a contributing factor and initiated mitigation activities.
    • 15:50 UTC on 13 August 2026 – Service processing queues recovered to normal levels and the impact was mitigated. Customers were advised to retry previously failed operations.

    What happens next?

    • This Mitigation Statement is the final communication for this incident. For details about which Azure incidents qualify for which Post Incident Reviews (PIRs), refer to https://aka.ms/AzurePIRs
    • The impact times above represent the full incident duration, so are not specific to any individual customer. Actual impact to service availability may vary between customers and resources – for guidance on implementing monitoring to understand granular impact: https://aka.ms/AzPIR/Monitoring
    • To stay informed about future Azure service issues, make sure that you configure and maintain Azure Service Health alerts – these can trigger emails, SMS, push notifications, webhooks, and more: https://aka.ms/ash-alerts
    • For broader guidance on preparing for cloud incidents, refer to https://aka.ms/incidentreadiness

    Please click Accept Answer and upvote if the above was helpful.

    Thanks.

    -TP

    Was this answer helpful?

    0 comments

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.