What is the practical consequence of enabling Azure AD integration with Azure RBAC for Kubernetes authorisation?
- A Kubernetes RBAC objects are ignored entirely
- B Access is granted through Azure role assignments instead of managing RoleBindings in-cluster (correct answer)
- C Only the admin kubeconfig can be used
- D Pods gain automatic Key Vault access
Shortcut: With Azure RBAC for Kubernetes, authorisation decisions are made from Azure role assignments scoped to the cluster or namespace, centralising access control in Azure AD rather than in-cluster manifests.