Azure Containers built-in role
Azure Kubernetes Fleet Manager Hub Cluster User Role
Azure Kubernetes Fleet Manager Hub Cluster User Role authorizes retrieval of the hub-cluster kubeconfig for Fleet Manager hub 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: 850c5848-fc51-4a9a-8823-f220370626e3
Control-plane actions (2)
Microsoft.ContainerService/fleets/listCredentials/actionMicrosoft.ContainerService/fleets/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 Fleet Manager ARM resource. 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 Fleet Manager hub cluster.
Prerequisites (2)
- The Fleet Manager hub 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 Fleet Manager Hub Cluster User Role directly on the Fleet Manager ARM resource to the identity that must retrieve the hub-cluster kubeconfig. Add the appropriate Kubernetes API role separately and validate credential retrieval and Kubernetes authorization independently.
Related roles (2)
- Azure Kubernetes Fleet Manager RBAC Reader: Separate read-only Kubernetes API DataActions after connecting to the hub.
- Azure Kubernetes Fleet Manager Contributor Role: Manages Fleet Azure resources without serving as the hub Kubernetes authorization role.
Common questions
When should I assign the Azure Kubernetes Fleet Manager Hub Cluster User Role Azure role?
Assign Azure Kubernetes Fleet Manager Hub Cluster User Role when you need to: Allow an approved user or automation identity to obtain the user kubeconfig needed to connect to one Fleet Manager hub cluster.. Practical scope: Assign on the individual Fleet Manager ARM resource. 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 Fleet Manager Hub Cluster User Role Azure role grant?
The role definition grants 2 combined control-plane and data-plane actions. Representative operations include: Microsoft.ContainerService/fleets/listCredentials/action; and Microsoft.ContainerService/fleets/read. Review the permission sections above for the complete definition and exclusions.
What are the security risks of the Azure Kubernetes Fleet Manager Hub Cluster User Role Azure role?
Key considerations when assigning Azure Kubernetes Fleet Manager Hub 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 the Kubernetes API for an Azure Kubernetes Fleet Manager hub cluster →
Supports: Description, Practical scope, Common use cases, Prerequisites, Best practices, Security considerations, Assignment guidance, Related roles. Retrieved 2026-07-17.