trying to Enable enterprise-grade edge on a static web app but keep getting error failed to update Edge

Hello @Vic Johnston

As per the official documentation, Enterprise-grade edge only works on the Standard plan. The prerequisite is an application deployed with the Standard hosting plan. Please check your subscription plan.

https://learn.microsoft.com/da-dk/Azure/static-web-apps/enterprise-edge?tabs=azure-portal

Hello Vic Johnston.

Greetings! Thanks for raising this question in the Q&A forum.

A generic "failed to update Edge" message in the portal almost always hides the real cause, since the portal doesn't surface the underlying provisioning error from Azure Front Door, which is what powers enterprise-grade edge behind the scenes. The most reliable way to see what's actually failing is to reproduce the operation through the Azure CLI instead of the portal, since the CLI returns the specific error rather than a generic banner.

1. Retry the operation through Azure CLI to get the real error

az extension add --name enterprise-edge
az staticwebapp enterprise-edge enable --name <your-static-webapp-name> --resource-group <your-resource-group>

This surfaces the actual failure reason, such as a missing provider registration or a permission issue, instead of the generic portal message.

1. Confirm the Microsoft.CDN resource provider is registered

Enabling enterprise-grade edge provisions a managed Azure Front Door resource, which requires the Microsoft.CDN provider registered on your subscription. If it isn't, the operation can fail and silently revert.

az provider register --wait --namespace Microsoft.CDN

1. Verify your prerequisites are actually met

Enterprise-grade edge requires the Standard hosting plan, not Free, and requires a custom domain already configured and validated on the static web app with a DNS TTL under 48 hours. Also confirm you are not using Private Endpoints, since those are not supported alongside enterprise-grade edge and will block enablement.

1. Check for a leftover or conflicting Front Door resource on the same hostname

If the custom domain you're enabling this on was ever associated with a different Azure Front Door instance, even one you thought was cleaned up, the enable operation can fail to bind correctly or fail outright, since Front Door detects the hostname is already associated elsewhere. Check your subscription for any other Front Door resources referencing the same custom domain and remove that association first.

1. Check staticwebapp.config.json for unsupported cache-control directives

Enterprise-grade edge validates your cache configuration as part of setup, and unsupported or misconfigured cache-control headers in staticwebapp.config.json can cause the provisioning step to fail without a clear portal error. Review that file for anything nonstandard in the cache headers before retrying.

If this answer helps you kindly accept the answer which will help others who have similar questions.

Best Regards,

Jerald Felix.