Azure Containers built-in role

Azure Kubernetes Service RBAC Admin

Azure Kubernetes Service RBAC Admin grants administrative access to most Kubernetes objects, including roles and role bindings, while excluding namespace and ResourceQuota writes on the AKS cluster. The effective workload authority is expressed as Kubernetes API DataActions under the Microsoft.ContainerService managed-cluster resource provider. The role also includes listClusterUserCredential, so the assignee can retrieve an AKS clusterUser kubeconfig; credential retrieval is not a separate assignment for this role.

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: 3498e952-d568-435e-9b2c-8d77e338d7f7

Control-plane actions (5)

Data-plane actions (1)

Excluded actions (4)

Assignable scopes (1)

Practical scope

Assign at the Kubernetes namespace sub-scope whenever the workflow is namespace-bound. Assigning at the the AKS cluster resource or an inherited parent Azure scope applies the Kubernetes API DataActions across all namespaces available through each inherited cluster.

Common use cases (1)

Prerequisites (2)

Best practices (2)

Security considerations (3)

Assignment guidance

Assign Azure Kubernetes Service RBAC Admin at the narrowest documented namespace scope to the principal that needs administrative access to most Kubernetes objects, including roles and role bindings, while excluding namespace and ResourceQuota writes. Treat the included kubeconfig retrieval as part of the grant, test both credential download and Kubernetes authorization, and protect downloaded credentials.

Editorial sources (6)

Official Microsoft Learn documentation →