Share via

Event subscriptions stuck in Creating/Deleting for 24+ hours, returning 409 Invalid ProvisioningState on all delete attempts (portal and CLI). System topic was deleted but subscriptions remain orphaned.

kunicki 20 Reputation points
2026-01-12T16:27:08.98+00:00

I have multiple Event Grid subscriptions on a storage account that are stuck in "Creating" state and cannot be deleted.

 

Stuck subscriptions (all on the same paxxxxxxxxbsdev storage account): - 5 subscriptions with various endpoint types (AzureFunction, WebHook, StorageQueue) - 4 show "Creating" provisioning state, 1 shows "Deleting - None are completing or becoming active

 

What I've tried: 1. Deleting via Azure Portal - delete fails with error code 409 and message: Invalid ProvisioningState 2. Deleting via Azure CLI - returns error: "The provisioning state of the resource is invalid for this operation" (409 Conflict) 3. Deleting the System Topic associated with the storage account 4. Verified Microsoft.EventGrid resource provider is registered 5. Waited over 24 hours - no change

 

CLI error example: When running az eventgrid event-subscription delete, I receive: "The provisioning state of the resource is invalid for this operation"

 

How can I force-delete these stuck Event Grid subscriptions so I can create new ones? Or can you delete these for us?

Azure Event Grid
Azure Event Grid

An Azure event routing service designed for high availability, consistent performance, and dynamic scale.

0 comments No comments

Answer accepted by question author
  1. Rakesh Mishra 7,215 Reputation points Microsoft External Staff Moderator
    2026-01-12T17:36:54.89+00:00

    Hi @kunicki , Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

    This can happen sometimes, especially if there are issues with provisioning states. Here’s what you can try to resolve the issue further:

    1. Confirm Subscription Status: Ensure you have checked whether the associated system topic was indeed deleted properly, as subscriptions can remain orphaned if their topics are deleted incorrectly.
    2. Use Azure CLI Commands: Since you're receiving a 409 error, you might want to try forcing the deletion using the Azure CLI commands mentioned in the documentation: To delete the event subscription:
         
         az eventgrid system-topic event-subscription delete --name <YourEventSubscriptionName> --resource-group <YourResourceGroupName> --system-topic-name <YourSystemTopicName>
         
      
      To delete the system topic (if it still exists):
         
         az eventgrid system-topic delete --name <YourSystemTopicName> --resource-group <YourResourceGroupName>
         
      
    3. PowerShell Commands: If CLI doesn’t work, consider using Azure PowerShell commands as another option: To delete an event subscription:
         
         Remove-AzEventGridSystemTopicEventSubscription -EventSubscriptionName <YourEventSubscriptionName> -ResourceGroupName <YourResourceGroupName> -SystemTopicName <YourSystemTopicName>
         
      
      To delete the system topic:
         
         Remove-AzEventGridSystemTopic -ResourceGroupName <YourResourceGroupName> -Name <YourSystemTopicName>
         
      
    4. Double-check Diagnostic Logs: Enable and check the diagnostic logs for your Event Grid to see if you get any insights about what's going wrong. You can find guidance on how to do that in the documentation below.
    5. Wait for Provisioning State Change: Occasionally, these issues can resolve themselves after some time—so it’s good to keep an eye on whether the provisioning state updates after some time.

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.