Share via

Event subscription managed identity type issue change from "None" to "System Assigned"

Janczewski, Michal 20 Reputation points
2026-02-06T08:49:19.2033333+00:00

Hi

I have an issue. When I'm trying to change existing event subcription Managed identity type from "None" into "System Assigned" I have a following error: "Managed Identity for XXXXX:YYYYY:ZZZZZ:TTTT (hiding for security) does not have permission to perform appropriate action on the destination resource. Managed identity for event subscription does not have authorization to deliver to the endpoint." However I have added "Storage Queue Data Contributor" to service principal associated with Event Grid Topic. What should I do to enable it?

Regards,

Azure Event Grid
Azure Event Grid

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

{count} votes

2 answers

Sort by: Most helpful
  1. Praveen Kumar Gudipudi 1,880 Reputation points Microsoft External Staff Moderator
    2026-02-06T09:07:32.9233333+00:00

    Hello Janczewski, Michal,

    Root Cause

    When the identity type is switched to System Assigned, Azure creates a new managed identity specifically for the Event Subscription. This identity must have the required data-plane permissions on the destination resource (for example, Storage Queue or Service Bus).

    In this scenario, the role was assigned to the Event Grid Topic service principal, but Event Grid validates permissions using the Event Subscription’s managed identity, which currently does not have sufficient authorization to deliver events to the endpoint.

    Resolution

    Please follow the steps below:

    Navigate to the Event Subscription → Identity blade.

    Copy the Principal (Object) ID of the System Assigned managed identity.

    1. Assign the appropriate RBAC role to this identity on the destination resource:
      • For Azure Storage Queue: Storage Queue Data Contributor also try with storage data contributor at the storage account scope.
      For Azure Service Bus: Grant Azure Service Bus Data Sender at the namespace scope. If the destination resource has network restrictions or firewall enabled, ensure: Allow trusted Microsoft services is enabled.
        System-assigned identity is being used.
      
        Wait a few minutes for RBAC propagation, then retry updating the Event Subscription.
      

    Expected Outcome

    After the correct role assignment to the Event Subscription managed identity, the identity type change to System Assigned should succeed and event delivery authorization will function as expected.

    Please accept as answer and do a Thumbs-up to upvote this response if you are satisfied with the community help. Your upvote will be beneficial for the community users facing similar issues.


  2. Q&A Assist
    2026-02-06T08:49:28.86+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    To resolve the issue of changing the managed identity type from "None" to "System Assigned" for your event subscription, ensure that the managed identity has the necessary permissions on the destination resource. Here are the steps you can follow:

    1. Check Role Assignments: Verify that the managed identity associated with your Event Grid topic has been assigned the appropriate roles on the destination resource (e.g., the Storage Queue). You mentioned adding "Storage Queue Data Contributor"; ensure that this role is correctly assigned to the managed identity and not just the service principal.
    2. Add Additional Roles: Depending on the endpoint you're using, you may need to add other roles as well. For example, if you're delivering events to a Service Bus queue, the managed identity must also have the "Azure Service Bus Data Sender" role on the Service Bus namespace.
    3. Allow Trusted Microsoft Services: Ensure that the setting "Allow trusted Microsoft services to bypass this firewall" is enabled on the destination resource, if applicable. This setting can help in scenarios where the managed identity needs to communicate with other Azure services securely.
    4. Reconfigure the Event Subscription: After ensuring that the managed identity has the correct permissions, try reconfiguring the event subscription to use the system-assigned identity again.

    If you continue to experience issues, check the Azure Activity Log for any additional error messages that might provide more context on the permissions issue.


    References:

    0 comments No comments

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.