Azure Containers built-in role
Azure Kubernetes Service Arc Cluster User Role
Azure Kubernetes Service Arc Cluster User Role authorizes retrieval of the Microsoft Entra user kubeconfig for AKS enabled by Azure Arc cluster through an Azure control-plane list-credential Action. The returned user kubeconfig establishes a connection and authentication context; Kubernetes authorization remains governed separately by Microsoft Entra, Azure RBAC, or Kubernetes RBAC.
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: 233ca253-b031-42ff-9fba-87ef12d6b55f
Control-plane actions (3)
Microsoft.HybridContainerService/provisionedClusterInstances/readMicrosoft.HybridContainerService/provisionedClusterInstances/listUserKubeconfig/actionMicrosoft.Kubernetes/connectedClusters/Read
Data-plane actions (0)
None — this role grants no data-plane (data access) actions.
Excluded actions (0)
None
Assignable scopes (1)
/
Practical scope
Assign on the individual AKS enabled by Azure Arc cluster. A resource-group or broader assignment is inherited by every matching resource below it and permits credential retrieval for each inherited cluster.
Common use cases (1)
- Allow an approved user or automation identity to obtain the user kubeconfig needed to connect to one AKS enabled by Azure Arc cluster.
Prerequisites (2)
- The AKS enabled by Azure Arc cluster must exist and the client must meet its network and Microsoft Entra authentication requirements.
- Assign an appropriate Kubernetes authorization role separately; credential retrieval alone does not define allowed Kubernetes API operations.
Best practices (2)
- Use Microsoft Entra user kubeconfig rather than shared local administrator credentials and keep the Azure assignment on the cluster resource.
- Protect kubeconfig files, avoid committing them to source control, revoke role or identity access when exposure is suspected, and remove temporary assignments promptly.
Security considerations (2)
- A kubeconfig can connect the holder to the cluster, but effective Kubernetes permissions depend on the platform authentication and Kubernetes authorization configuration.
- A broad inherited Azure assignment allows credential retrieval from multiple clusters.
Assignment guidance
Assign Azure Kubernetes Service Arc Cluster User Role directly on the AKS enabled by Azure Arc cluster to the identity that must retrieve the Microsoft Entra user kubeconfig. Add the appropriate Kubernetes API role separately and validate credential retrieval and Kubernetes authorization independently.
Related roles (2)
- Azure Arc Kubernetes Viewer: Separate Kubernetes API DataActions for read-only access after authentication.
- Azure Kubernetes Service Arc Cluster Admin Role: Retrieves sensitive administrator credentials instead of the user kubeconfig.
Common questions
When should I assign the Azure Kubernetes Service Arc Cluster User Role Azure role?
Assign Azure Kubernetes Service Arc Cluster User Role when you need to: Allow an approved user or automation identity to obtain the user kubeconfig needed to connect to one AKS enabled by Azure Arc cluster.. Practical scope: Assign on the individual AKS enabled by Azure Arc cluster. A resource-group or broader assignment is inherited by every matching resource below it and permits credential retrieval for each inherited cluster.
What permissions does the Azure Kubernetes Service Arc Cluster User Role Azure role grant?
The role definition grants 3 combined control-plane and data-plane actions. Representative operations include: Microsoft.HybridContainerService/provisionedClusterInstances/read; Microsoft.HybridContainerService/provisionedClusterInstances/listUserKubeconfig/action; and Microsoft.Kubernetes/connectedClusters/Read. Review the permission sections above for the complete definition and exclusions.
What are the security risks of the Azure Kubernetes Service Arc Cluster User Role Azure role?
Key considerations when assigning Azure Kubernetes Service Arc Cluster User Role: A kubeconfig can connect the holder to the cluster, but effective Kubernetes permissions depend on the platform authentication and Kubernetes authorization configuration.; and A broad inherited Azure assignment allows credential retrieval from multiple clusters.. Follow the assignment guidance above and use the narrowest practical scope.
Editorial sources (6)
- Azure built-in roles for Containers - Azure RBAC | Microsoft Learn →
Supports: Description, Practical scope, Security considerations. Retrieved 2026-07-17.
- Understand Azure role definitions →
Supports: Description, Security considerations. Retrieved 2026-07-17.
- Steps to assign an Azure role →
Supports: Assignment guidance. Retrieved 2026-07-17.
- Understand scope for Azure RBAC →
Supports: Practical scope, Assignment guidance. Retrieved 2026-07-17.
- Best practices for Azure RBAC →
Supports: Best practices, Assignment guidance. Retrieved 2026-07-17.
- Access and identity options for AKS enabled by Azure Arc →
Supports: Description, Practical scope, Common use cases, Prerequisites, Best practices, Security considerations, Assignment guidance, Related roles. Retrieved 2026-07-17.