Azure Static Web Apps – custom domains stuck in “Deleting” after unknown error

Neil Meintjes 25 Reputation points
2026-08-12T09:53:30.02+00:00

Azure Static Web Apps custom domains stuck in “Deleting” after unknown error

I’m experiencing a custom-domain issue with an Azure Static Web App and would appreciate help clearing the stuck hostname bindings.

Resource

  • Static Web App: vf-capital-web
  • Resource Group: VF-Capital
  • Region: East US 2

Issue

The Static Web App itself is working correctly and GitHub Actions deployment succeeds. The autogenerated Azure URL loads the production landing page correctly.

However, adding either of these custom domains produces:

“An unknown error has occurred while adding your custom domain. Please try again later.”

The affected domains are:

  • vectorflowcapital.com
  • www.vectorflowcapital.com

I subsequently attempted to delete both custom-domain bindings through the Azure Portal and Azure CLI.

Both hostname resources have remained in Deleting state for more than 40 minutes.

Current CLI output

az staticwebapp hostname list --name vf-capital-web --resource-group VF-Capital -o table

Both domains show:

  • Status: Deleting
  • Error: An unknown error has occurred while adding your custom domain. Please try again later.
  • Validation token: null

DNS

DNS is hosted externally in AWS Route 53.

The DNS configuration has been checked and the required A/CNAME, TXT verification and CAA records have been configured as appropriate.

The issue persists despite the DNS configuration being in place.

What I need

Could someone from the Azure Static Web Apps team confirm whether these hostname resources are stuck in the backend and advise how they can be cleared/reset?

I do not want to delete/recreate the Static Web App because the GitHub/Azure deployment itself is working correctly.

This appears similar to recent Azure Static Web Apps cases involving custom domains becoming stuck in Deleting after an “unknown error” during creation.

Thank you.

Azure Static Web Apps custom domains stuck in “Deleting” after unknown error

I’m experiencing a custom-domain issue with an Azure Static Web App and would appreciate help clearing the stuck hostname bindings.

Resource

  • Static Web App: vf-capital-web
  • Resource Group: VF-Capital
  • Region: East US 2

Issue

The Static Web App itself is working correctly and GitHub Actions deployment succeeds. The autogenerated Azure URL loads the production landing page correctly.

However, adding either of these custom domains produces:

“An unknown error has occurred while adding your custom domain. Please try again later.”

The affected domains are:

  • vectorflowcapital.com
  • www.vectorflowcapital.com

I subsequently attempted to delete both custom-domain bindings through the Azure Portal and Azure CLI.

Both hostname resources have remained in Deleting state for more than 40 minutes.

Current CLI output

az staticwebapp hostname list --name vf-capital-web --resource-group VF-Capital -o table

Both domains show:

  • Status: Deleting
  • Error: An unknown error has occurred while adding your custom domain. Please try again later.
  • Validation token: null

DNS

DNS is hosted externally in AWS Route 53.

The DNS configuration has been checked and the required A/CNAME, TXT verification and CAA records have been configured as appropriate.

The issue persists despite the DNS configuration being in place.

What I need

Could someone from the Azure Static Web Apps team confirm whether these hostname resources are stuck in the backend and advise how they can be cleared/reset?

I do not want to delete/recreate the Static Web App because the GitHub/Azure deployment itself is working correctly.

This appears similar to recent Azure Static Web Apps cases involving custom domains becoming stuck in Deleting after an “unknown error” during creation.

Thank you.

Azure Static Web Apps
Azure Static Web Apps

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

Answer accepted by question author
TP 163.1K Reputation points Volunteer Moderator
2026-08-13T16:48:29.97+00:00

Hi Neil,

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.

Also, I just tested adding a custom domain and this time it succeeded. Before it failed, which led to delete failing, etc. Seemed to take a little longer for the process to complete, but it did work and I can view my static site using custom domain now.

Thanks.

-TP

Was this answer helpful?

1 person found this answer helpful.
0 comments

2 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Smith 0 Reputation points
    2026-08-13T06:59:04.85+00:00

    This is a known Azure Static Web Apps issue, a few things worth checking in order:

    1. Check your CAA record first. Azure Static Web Apps issues free certificates through DigiCert. If your domain has a CAA record that doesn't explicitly allow DigiCert, or restricts issuance to another CA, you'll get exactly this "unknown error" during custom domain creation. Add this to your Route 53 zone for the apex domain:

    0 issue "digicert.com"

    This is the single most common cause of this specific error message and isn't well documented on Microsoft's side.

    2. For the stuck "Deleting" state: This is a backend-level issue where Azure's system still thinks a deletion is in progress even after the Portal/CLI reports success. Try running the CLI delete command again, more than once, with 15-30 minute gaps between attempts:

    az staticwebapp hostname delete --name vf-capital-web --resource-group VF-Capital --hostname vectorflowcapital.com --yes

    It's common for this to return "OK" without actually clearing the binding on the first few tries.

    3. Check Azure Resource Explorer (resources.azure.com) → navigate to your subscription → VF-Capital resource group → vf-capital-web → custom domains. Sometimes the stuck hostname entry is visible and removable here even when Portal/CLI won't clear it.

    4. If none of the above works: This specific pattern (stuck in "Deleting" for 40+ minutes with a null validation token after an "unknown error") matches several other reported cases where only the Azure product/support team could manually clear the hostname binding on the backend. File a support ticket through the Azure Portal with your Static Web App name, resource group, and both hostnames, and explicitly mention it's stuck in "Deleting" with a null validation token, this phrasing tends to get it routed to the right team faster.

    You shouldn't need to delete/recreate the Static Web App itself, this is isolated to the hostname bindings.

    Was this answer helpful?

  2. Golla Venkata Pavani 7,530 Reputation points Microsoft External Staff Moderator
    2026-08-12T10:15:45.5566667+00:00

    Hi @Neil Meintjes

    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.