# Least privilege for human users in Azure means eligible role assignments to groups at narrow scopes

Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.

Human users in Azure get permissions from Entra users and groups through Azure RBAC role assignments at a scope. Microsoft's documentation, read 16 Nov 2026, names PIM, access reviews and Defender for Cloud recommendations as the provider tools. This guide gives the steps, the roles to avoid and the measures.

## People get Azure permissions from role assignments made to users and groups at a scope

An Azure RBAC role assignment ties a security principal, a role definition and a scope. Microsoft's RBAC best practices page says to grant users the least privilege to get their work done, to avoid broader roles at broader scopes even when that looks convenient, and to assign roles to groups rather than directly to users.

The page gives two reasons for groups. Assignments are easier to manage, and there is a limit on role assignments per subscription, which groups help stay under.

Microsoft Entra roles are a separate system from Azure RBAC roles. Entra roles such as Global Administrator control the directory; Azure roles control subscriptions and resources. Microsoft's access review documentation lists Global Administrators and Azure resource roles together as role assignments worth recertifying.

Privilege accumulates through [privilege creep](/privilege-creep/): a person joins a project, gets Contributor on a subscription, and keeps it after moving teams.

## Microsoft provides PIM, access reviews and Defender for Cloud recommendations

Microsoft Entra Privileged Identity Management (PIM) provides time-based and approval-based role activation for Entra roles and Azure resources. Microsoft lists time-bound assignments with start and end dates, approval to activate, multifactor authentication on activation, justification, notifications and audit history. Microsoft says an eligible role assignment gives the same access as a permanent one when activated; the difference is that access is not standing. Microsoft states that PIM requires licenses.

Access reviews in Microsoft Entra let reviewers approve or deny continued access for group memberships, enterprise applications and role assignments, recurring weekly, monthly, quarterly or annually. Microsoft notes the feature requires Microsoft Entra ID Governance or Microsoft Entra Suite subscriptions, with some capabilities available under Microsoft Entra ID P2.

Defender for Cloud includes cloud infrastructure entitlement management capabilities in its Defender Cloud Security Posture Management plan. Microsoft says it surfaces recommendations such as removing inactive, guest or blocked accounts with access, limiting administrative privileges to a defined set of users, and right-sizing permissions for overprovisioned identities based on actual usage.

Microsoft's RBAC page adds a monitored count: have a maximum of three subscription owners, a recommendation that Defender for Cloud monitors. It also says to check privileged administrator role assignments and, when you assign a role that can create role assignments, to consider a condition that constrains it.

## Steps to bring human access in Azure to least privilege

- List role assignments for every subscription and management group, filtered to privileged administrator roles, and record principal, scope and assignment date.
- Move direct user assignments to Microsoft Entra security groups, one group per role and scope.
- Convert standing assignments of Owner, User Access Administrator, Role Based Access Control Administrator and Contributor to eligible assignments in PIM, with activation requiring MFA and justification.
- Reduce subscription owners to three or fewer and narrow remaining privileged assignments to resource group or resource scope.
- Create recurring access reviews for the groups behind privileged roles, with the group owner or the manager as reviewer.
- Work through the Defender for Cloud recommendations on inactive accounts and overprovisioned permissions, starting with identities that can reach sensitive resources.
- Replace wildcard (*) custom roles with explicit Actions and DataActions, as Microsoft advises.
- Repeat the review on the cadence the access review sets. [The first 90 days](/first-90-days/) gives an order for these steps.

## Roles and assignments to avoid for human users

| Role or assignment | Documented reason (Microsoft, read 16 Nov 2026) | Use instead |
| --- | --- | --- |
| Owner | Microsoft describes it as full access to manage all resources, including the ability to assign roles in Azure RBAC. | A job-function role at resource group scope; Owner eligible through PIM. |
| User Access Administrator | Microsoft describes it as letting you manage user access to Azure resources. | Role Based Access Control Administrator with a condition, or an eligible assignment. |
| Contributor at subscription scope | Microsoft advises avoiding broader roles at broader scopes and prefers job-function roles to privileged administrator roles. | A narrower built-in role at resource group scope. |
| More than three subscription owners | Microsoft says to have a maximum of three, to reduce the chance of breach by a compromised owner. | Eligible owner assignments through PIM. |
| Custom roles with wildcard actions | Microsoft says future Actions or DataActions added under a wildcard may grant unwanted access. | Explicitly listed Actions and DataActions. |
| Roles assigned directly to individual users | Microsoft says to assign to groups to keep assignments manageable. | Security groups. |

## Measure standing privileged assignments and the share of permissions used

Count standing (permanent) assignments of privileged administrator roles against eligible ones. A move from standing to eligible is visible in PIM without any usage data. Count subscriptions with more than three owners, and count users with administrative roles who have not signed in during the review window.

For overprovisioning, use the Defender for Cloud right-sizing recommendations, which compare granted permissions with actual usage, and record their number over time. The [Access Debt Calculator](/) accepts granted and used counts, and the [policy template](/least-privilege-policy-template/) offers wording for the policy that sets these thresholds.

Related guides: [AWS human identities](/guides/aws-human-identities/) and [Google Cloud human identities](/guides/google-cloud-human-identities/).

## Related pages

- [Least privilege for service identities in Azure](/guides/azure-service-identities/)
- [Least privilege for workload identities in Azure](/guides/azure-workload-identities/)
- [Least privilege for third-party identities in Azure](/guides/azure-third-party-identities/)
- [All of them](/guides/)

## Sources

- Microsoft Learn: Best practices for Azure RBAC: https://learn.microsoft.com/en-us/azure/role-based-access-control/best-practices (read 16 Nov 2026)
- Microsoft Learn: Azure built-in roles for Privileged: https://learn.microsoft.com/en-us/azure/role-based-access-control/built-in-roles/privileged (read 16 Nov 2026)
- Microsoft Learn: What is Microsoft Entra Privileged Identity Management: https://learn.microsoft.com/en-us/entra/id-governance/privileged-identity-management/pim-configure (read 16 Nov 2026)
- Microsoft Learn: What are access reviews: https://learn.microsoft.com/en-us/entra/id-governance/access-reviews-overview (read 16 Nov 2026)
- Microsoft Learn: Permissions management (CIEM) in Defender for Cloud: https://learn.microsoft.com/en-us/azure/defender-for-cloud/permissions-management (read 16 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://leastprivilegeprinciple.com/guides/azure-human-identities/
