An Azure service that provides streamlined full-stack web app development.
Thanks for sharing the root cause.
Incorrect or unsupported cache directives in staticwebapp.config.json can interfere with Enterprise‑grade Edge provisioning. Enterprise‑grade Edge is powered by Azure Front Door, which evaluates routing and cache‑control configuration as part of setup. When cache headers are misconfigured or unsupported, Azure Front Door may be unable to complete validation, which can cause the enablement process to fail without an explicit portal error.
After correcting the cache configuration, Enterprise‑grade Edge was able to provision successfully, confirming the issue was configuration‑related rather than DNS or platform‑related.
reference:
https://learn.microsoft.com/en-us/azure/static-web-apps/configuration
https://learn.microsoft.com/en-us/azure/static-web-apps/enterprise-edge?tabs=azure-portal
Please do not forget to click "Accept the answer” and Yes, this can be beneficial to other community members.
If you have any other questions, let me know in the "comments" and I would be happy to help you