In Microsoft Entra, Role-Based Access Control (RBAC) is the framework that enforces precise, consistent permissions across identities, apps, and services. It is the core mechanism for defining who can do what, and it works at scale without sacrificing security.
Microsoft Entra RBAC assigns roles to users, groups, service principals, and managed identities. Each role carries a set of permissions that map directly to actions in Azure and connected resources. This separation of identity and privilege makes it possible to minimize attack surface, meet compliance rules, and keep operational control tight.
Roles are defined in two categories: built-in and custom. Built-in roles cover common scenarios—Owner, Contributor, Reader, and specialized roles like User Access Administrator. Custom roles allow precise tailoring of permissions by selecting specific actions from the Entra RBAC permission catalog. This flexibility lets teams enforce least privilege while still enabling necessary workflows.
RBAC in Microsoft Entra is entirely scope-aware. A role assignment can apply to a subscription, a resource group, or a single resource. Scoping determines the reach of permissions. Narrow scopes reduce risk. Wide scopes simplify management for trusted admin accounts. Understanding and using scopes correctly is central to secure cloud operations.