An Azure event routing service designed for high availability, consistent performance, and dynamic scale.
How to remove resources stuck in Updating-state?
I have an event grid that is stuck in Updating-state and i cannot delete it. What can i do to get it deleted?
Azure Event Grid
-
Sai Prabhu Naveen Parimi • 3,970 Reputation points • Microsoft External Staff • Moderator
2025-07-03T15:20:57.52+00:00 It looks like you're having trouble deleting an Event Grid resource that is stuck in the "Updating" state. Here are some steps you can try to resolve this issue:
Check the Status: First, verify the current status of the Event Grid resource using Azure CLI or Azure Portal. If it's still in the "Updating" state, you may need to wait a bit before proceeding to the next steps.
Force Delete the Resource:
- You can try to force delete the Event Grid resource using Azure CLI:
az eventgrid event-subscription delete --name <your-event-subscription-name> --source-resource-id <your-event-grid-source-id> --yes - Replace
<your-event-subscription-name>and<your-event-grid-source-id>with the relevant details for your resource.
Using Resource Explorer:
- If CLI doesn’t work, you may want to use the Azure Resource Explorer. Navigate to your Event Grid resource and see if there’s an option to delete it directly from there.
Check Dependencies: Sometimes, other resources might be preventing the deletion. Review any dependent resources related to your Event Grid. You can find any references through the Azure Portal.
Retry & Wait: If the resource is stuck due to Azure's internal operations, sometimes it's just a matter of waiting for a little while before attempting to delete again.
- You can try to force delete the Event Grid resource using Azure CLI:
-
Klas Persson Signell • 5 Reputation points
2025-07-04T07:44:43.17+00:00 Hello,
Thanks for the response.
I dont think i have a subscription, just a namespace. I was not able to delete it using "az eventgrid namespace delete" due to the state.
Looked at the explorer but could not find any option to delete resources there.
-
Sai Prabhu Naveen Parimi • 3,970 Reputation points • Microsoft External Staff • Moderator
2025-07-04T08:54:32.5166667+00:00 your Event Grid namespace unstuck from the "Updating" state so you can delete it. Here are a few steps you can try:
Check the Status: Ensure the namespace is indeed stuck. You can use the Azure CLI command:
az eventgrid namespace show --name <your-namespace-name> --resource-group <your-resource-group-name>Delete with Force Option: You can try to forcefully delete the namespace using the Azure CLI:
az eventgrid namespace delete --name <your-namespace-name> --resource-group <your-resource-group-name> --yes --no-waitCheck Dependencies: Sometimes, dependent resources can block deletion. Ensure there are no other services or subscriptions linked to this namespace that need to be managed first. You can check for dependencies in the Azure Portal.
-
-
Sai Prabhu Naveen Parimi • 3,970 Reputation points • Microsoft External Staff • Moderator
2025-07-07T16:54:40.81+00:00 Just following up to see if you had a chance to review the information shared earlier. Please let me know if everything is working as expected or if you need any further assistance.
-
Sai Prabhu Naveen Parimi • 3,970 Reputation points • Microsoft External Staff • Moderator
2025-07-08T10:41:24.0733333+00:00 Just following up to see if you had a chance to review the information shared earlier. Please let me know if everything is working as expected or if you need any further assistance.
-
Jacob Lundberg • 0 Reputation points
2025-07-16T08:01:52.6866667+00:00 I work with Klas and unfortunately none of the provided suggestions have offered any way forward. The resource still remains stuck in the 'updating' state.
It is not possible to delete the EventGrid namespace using the Azure Portal, Azure CLI or Azure Resource Explorer. It always fails with some form of this error message:
Code: InvalidRequestMessage: Operation failed because namespace resource is in 'Updating' provisioning state while this operation is allowed only if the namespace resource is in 'Succeeded' provisioning state.
Sign in to comment