Can't disable enterprise-grade edge on static web app

Hi @Peter Szieben ,

Thank you for submitting your question on Microsoft Q&A.

It appears that you’re experiencing difficulty disabling Enterprise-grade edge for your Static Web App, possibly following a Front Door–related issue.

Disable Enterprise-Grade Edge using the Azure Portal

1. Sign in to the Azure Portal.
2. Search for and open your Static Web App resource.
3. In the left-hand menu, under Settings, select Enterprise-grade edge.
4. If the feature is currently enabled, toggle the switch to disable it or choose Disable.
5. Click Save to apply and confirm the change.

Disable Enterprise-Grade Edge using CLI

By using CLI Commands, you can disable the enterprise-grade edge on your static web app Install or update the Azure CLI if needed, then add the enterprise-edge extension

# Login and set the right subscription first if needed
az login
az account set --subscription "<SUBSCRIPTION_ID_OR_NAME>"

# Then disable enterprise-grade edge
az staticwebapp enterprise-edge disable \
  --name "<YOUR_SWA_NAME>" \
  --resource-group "<YOUR_RG_NAME>"

# Optional: check status until it becomes Disabled
az staticwebapp enterprise-edge show \
  --name "<YOUR_SWA_NAME>" \
  --resource-group "<YOUR_RG_NAME>"

Reference :

https://learn.microsoft.com/en-us/cli/azure/staticwebapp/enterprise-edge?view=azure-cli-latest#az-staticwebapp-enterprise-edge-disable

Kindly let us know if the above comment helps or you need further assistance on this issue.

Please "upvote" if the information helped you. This will help us and others in the community as well.

To disable the Azure Front Door CDN for your static web app, you can use the Azure CLI command:

az staticwebapp enterprise-edge disable --name <your-static-site-name> --resource-group <your-resource-group-name>

Make sure you replace <your-static-site-name> and <your-resource-group-name> with the actual names of your static site and resource group. If you are encountering issues creating a support ticket, ensure that your subscription is correctly set up and that you have the necessary permissions to submit support requests. If the problem persists, you may want to check your Azure subscription settings or consult with your organization's Azure administrator for assistance.