Azure Containers built-in role

Azure Container Storage Contributor

Installs and manages the Azure Container Storage Kubernetes extension and ARM deployments. It can create or delete role assignments only for Azure Container Storage Operator under the built-in condition. It has no Microsoft.ElasticSan or Microsoft.Storage Actions and no storage DataActions, so it does not itself manage Elastic SAN or Azure Storage resources.

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: 95dd08a6-00bd-4661-84bf-f6726f83a4d0

Control-plane actions (12)

Data-plane actions (0)

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

Excluded actions (0)

None

Conditions (1)

Assignable scopes (1)

Practical scope

Microsoft documents this role at subscription scope for installation, although the resulting Operator assignment can be narrowed to a resource group. Because Azure assignments inherit, subscription scope gives the contributor its published Container Storage management authority across that subscription.

Common use cases (1)

Prerequisites (2)

Best practices (2)

Security considerations (2)

Assignment guidance

Assign Azure Container Storage Contributor to the approved installer at the documented subscription scope only where it owns the extension deployment. Preserve the built-in condition and use its delegation solely to assign Operator to the AKS kubelet or agent-pool identity at the narrowest infrastructure scope.

Related roles (2)

Common questions

When should I assign the Azure Container Storage Contributor Azure role?

Assign Azure Container Storage Contributor when you need to: Allow a platform installer to deploy or maintain the Azure Container Storage extension and grant the AKS kubelet or agent-pool identity the constrained Operator role.. Practical scope: Microsoft documents this role at subscription scope for installation, although the resulting Operator assignment can be narrowed to a resource group. Because Azure assignments inherit, subscription scope gives the contributor its published Container Storage management authority across that subscription.

What permissions does the Azure Container Storage Contributor Azure role grant?

The role definition grants 12 combined control-plane and data-plane actions. Representative operations include: Microsoft.KubernetesConfiguration/extensions/write; Microsoft.KubernetesConfiguration/extensions/read; Microsoft.KubernetesConfiguration/extensions/delete; Microsoft.KubernetesConfiguration/extensions/operations/read; Microsoft.Authorization/*/read; and Microsoft.Resources/subscriptions/resourceGroups/read. Review the permission sections above for the complete definition and exclusions.

What are the security risks of the Azure Container Storage Contributor Azure role?

Key considerations when assigning Azure Container Storage Contributor: The role can install, update, or remove the Container Storage extension, create ARM deployments, and create or delete Azure Container Storage Operator assignments within the built-in condition.; and It cannot directly manage Elastic SAN or Azure Storage resources; the delegated Operator identity supplies the runtime infrastructure authority, so its identity and assignment scope are security-critical.. Follow the assignment guidance above and use the narrowest practical scope.

Editorial sources (7)

Official Microsoft Learn documentation →