Azure Identity built-in role

Managed Identity Contributor

Creates, reads, updates, and deletes user-assigned managed identities. The built-in role also manages their federated identity credentials and can revoke their tokens; it does not attach an identity to a workload or grant that identity access to another resource.

Role-definition permissions are imported from Microsoft Learn. Practical scope, use cases, prerequisites, best practices, security considerations, assignment guidance, and relationships have been reviewed against the official sources below.

Role definition ID: e40ec5ca-96e0-45a2-b4ff-59039f2c2b59

Control-plane actions (12)

Data-plane actions (0)

None — this role grants no data-plane (data access) actions.

Excluded actions (0)

None

Assignable scopes (1)

Practical scope

The built-in definition is available throughout the Azure hierarchy. Effective access is limited to the selected assignment scope and inherited child scopes, normally the resource group containing the user-assigned identities. Its permissions are control-plane Actions and it has no DataActions.

Common use cases (2)

Prerequisites (2)

Best practices (3)

Security considerations (4)

Assignment guidance

Assign Managed Identity Contributor to the team that owns user-assigned identity lifecycle and federated credentials, not to every workload deployer. Scope it to the identity resource group or a narrower boundary. Use Managed Identity Operator for attachment-only workflows and a separate Azure RBAC role assignment to grant the managed identity its runtime resource access.

Related roles (2)

Common questions

When should I assign the Managed Identity Contributor Azure role?

Assign Managed Identity Contributor when you need to: Provision, tag, update, or delete user-assigned managed identities in an approved resource group.; and Manage federated identity credentials or revoke tokens for user-assigned managed identities.. Practical scope: The built-in definition is available throughout the Azure hierarchy. Effective access is limited to the selected assignment scope and inherited child scopes, normally the resource group containing the user-assigned identities. Its permissions are control-plane Actions and it has no DataActions.

What permissions does the Managed Identity Contributor Azure role grant?

The role definition grants 12 combined control-plane and data-plane actions. Representative operations include: Microsoft.ManagedIdentity/userAssignedIdentities/read; Microsoft.ManagedIdentity/userAssignedIdentities/write; Microsoft.ManagedIdentity/userAssignedIdentities/delete; Microsoft.ManagedIdentity/userAssignedIdentities/federatedIdentityCredentials/read; Microsoft.ManagedIdentity/userAssignedIdentities/federatedIdentityCredentials/write; and Microsoft.ManagedIdentity/userAssignedIdentities/federatedIdentityCredentials/delete. Review the permission sections above for the complete definition and exclusions.

What are the security risks of the Managed Identity Contributor Azure role?

Key considerations when assigning Managed Identity Contributor: The role can delete user-assigned identities, change federated identity credentials, and revoke existing tokens.; Deleting a user-assigned identity does not remove its reference from resources to which it was assigned, so deletion requires dependency review.; A federated identity credential establishes trust with an external identity provider and must be treated as a credential-boundary change.; and The role has no DataActions and does not itself grant access to the downstream services a managed identity will call.. Follow the assignment guidance above and use the narrowest practical scope.

Editorial sources (5)

Official Microsoft Learn documentation →