Static Web App stuck in enterpriseGradeCdnStatus = Disabling, never reaches Disabled — blocks Standard to Free downgrade

Nikola Cvitanovic 0 Reputation points
2026-06-23T19:48:45.4833333+00:00

My Static Web App's enterprise-grade edge (Azure Front Door integration) is stuck. After clicking Disable on Enterprise-grade edge, enterpriseGradeCdnStatus went to Disabling and has stayed there for 8+ hours — it never reaches Disabled.

Environment: Static Web App, Standard SKU, region West Europe, deployed via SWA CLI. Two custom domains, both Ready. No linked backends, managed functions, or private endpoints.

What I've tried:

  • az staticwebapp enterprise-edge disable -> returns success, status stays Disabling indefinitely.
  • Re-enabling goes to Enabled instantly; disabling again hangs in Disabling again (reproducible — enable is fine, disable always stalls).
  • Direct ARM PATCH of properties.enterpriseGradeCdnStatus to Disabled is silently coerced back to Disabling; setting it to null returns BadRequest: Unexpected token Null when parsing enum.
  • No Microsoft.Web/staticSites/write operation appears in the Activity Log driving the transition — the status looks orphaned with no running operation behind it.
  • The SKU downgrade Standard to Free is rejected while in this state: BadRequest: EnterpriseGradeCdnStatus is invalid.

Question: How can I force the edge teardown to complete (reach Disabled) so I can downgrade to Free? Is there a way to clear this orphaned Disabling state without a paid support plan? Anyone seen this and had it self-resolve?

Azure Static Web Apps
Azure Static Web Apps

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


1 answer

Sort by: Most helpful
  1. Alex Burlachenko 23,170 Reputation points MVP Volunteer Moderator
    2026-06-25T09:59:55.7633333+00:00

    hi Nikola Cvitanovic & thx for sharing urs issue here at Q&A portal,

    the SWA edge state got stuck in the Static Web Apps control plane.

    Since enable works but disable always lands back in Disabling, and ARM PATCH gets coerced back, this prob isn’t a client/CLI issue. The backend still thinks the enterprise edge teardown is pending or failed, but there’s no visible operation left for u to complete.

    I wouldn’t try to force enterpriseGradeCdnStatus with raw ARM anymore. That property is service-owned state, so ARM will just normalize it back or reject invalid enum values. Annoying, but expected.

    Best things to check before support: remove/verify custom domain edge config, confirm no Front Door/custom domain association is still pending, then retry disable once. If it still stays Disabling after hrs, it needs backend cleanup.

    Assume the useful docs will be next list

    https://learn.microsoft.com/en-us/azure/static-web-apps/enterprise-grade-edge

    https://learn.microsoft.com/en-us/azure/static-web-apps/plans

    https://learn.microsoft.com/en-us/azure/static-web-apps/custom-domain

    For the downgrade block, MS needs to clear the orphaned edge state or finish the teardown from the backend. Open a Static Web Apps support case w/ resource ID, region, UTC disable time, current enterpriseGradeCdnStatus, the failed downgrade error, and Activity Log showing no running write op.

    If u don’t have a paid plan, try a billing/subscription support path and explain this is blocking SKU downgrade/cost reduction due to a stuck platform state. Community can’t really reset that enum. It’s one of those ‘portal button says disable, backend says nah’ situations.

    rgds,

    Alex

    &

    If my answer was helpful pls mark it and additional thx if u follow me at Q&A portal 
    and at my blog https://ctrlaltdel.blog/
    

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No 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.