Static Web App "Enterprise-grade edge" stuck — "A create or update operation is currently in progress" blocks all updates

Question

Static Web App "Enterprise-grade edge" stuck — "A create or update operation is currently in progress" blocks all updates

Tako Verkroost 0

Enabling "Enterprise-grade edge" (Azure Front Door integration) on our Static Web App has failed to complete 4 times over 2 days (2026-08-31 to 2026-09-02). Each attempt shows "Enabling in progress" for many hours, then reverts to disabled without any error message in the Portal.

Resource details:

Subscription: Acceptance-drg
Resource group: acc-bzk
Resource name: TestPortaalTotaal
Resource type: Static Web App (Standard plan)

Activity Log shows multiple "Create or Update Static Site" operations stuck in status "Accepted" for 8 minutes to 19+ hours, never resolving to "Succeeded" or "Failed".

When attempting to trigger the operation again via Azure CLI (az staticwebapp enterprise-edge enable), we get:

ERROR: (Conflict) Cannot update Static Web App: A create or update operation is currently in progress for the static web app TestPortaalTotaal.
Code: Conflict

This confirms there's a stuck/hung operation on this resource blocking all further updates, with no way to cancel or retry it ourselves. We're on the Basic support plan so cannot open a paid technical ticket.

Has anyone encountered this, or does a Microsoft engineer know how to clear a stuck "Create or Update Static Site" operation on a Static Web App resource?

Tako Verkroost 0 Reputation points

2026-09-02T08:45:58.69+00:00

Update: After being stuck for 19+ hours across 4 attempts, the operation resolved itself without any action from our side — Enterprise-grade edge is now successfully enabled (confirmed via DNS: traffic now routes through *.azurefd.net, and IPv6 (AAAA record) is present). No root cause was ever identified; it appears to have just been a slow/stuck backend provisioning process that eventually completed on its own. Leaving this here in case others hit the same "stuck in Accepted" behavior — patience (or trying again after ~24h) may be the only fix.

Your answer

Tako Verkroost 0 Reputation points

2026-09-02T08:45:58.69+00:00

Update: After being stuck for 19+ hours across 4 attempts, the operation resolved itself without any action from our side — Enterprise-grade edge is now successfully enabled (confirmed via DNS: traffic now routes through *.azurefd.net, and IPv6 (AAAA record) is present). No root cause was ever identified; it appears to have just been a slow/stuck backend provisioning process that eventually completed on its own. Leaving this here in case others hit the same "stuck in Accepted" behavior — patience (or trying again after ~24h) may be the only fix.