An Azure service that provides a cloud content delivery network with threat protection.
Hi @Przemyslaw Giza
Welcome to Microsoft Q&A Platform.
When Front Door profiles get “zombified” it usually means there’s still a control-plane operation or a lock/dependency holding things up. Here’s what you can try before we escalate to a backend cleanup:
When Front Door profiles get “zombified” it usually means there’s still a control-plane operation or a lock/dependency holding things up. Here’s what you can try before we escalate to a backend cleanup:
- Check for Azure locks
az lock list --resource-group GKN
az lock list --ids /subscriptions/<sub>/resourceGroups/GKN/providers/Microsoft.Cdn/profiles/przemo-afd
Cancel or finish any pending operations: Check group deployments:
az group deployment operation list \
--resource-group GKN
If you spot a hung delete/update, you may need to cancel it via the portal or PowerShell.
- Re-attempt the Front Door delete
az network front-door delete \
--resource-group GKN \
--name przemo-afd \
--yes
You can also add --no-wait and then poll with az network front-door show until it vanishes.
- Review Activity Logs for conflicts
In the Azure portal, go to Monitor > Activity Log, filter on your Front Door resource and look for the conflict error details and the operationId. That will tell you what control-plane call is still running.
References: az network front-door delete: https://learn.microsoft.com/cli/azure/network/front-door?view=azure-cli-latest
Please
and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.