Manage Azure identities and governance
Three areas: who exists; who may act; and what requests may do, how resources are organized and what they cost
An account that is Owner (the built-in Azure role that manages all resources and assigns roles) of every subscription still can't create a user, and while a CanNotDelete resource lock, which blocks deletion, sits on a resource group, that Owner's delete request fails like anyone else's. Both surprises have one cause: the three areas each answer their own question. Directory asks who exists: users, groups and guests live in a Microsoft Entra tenant, the directory in Microsoft Entra ID that each subscription trusts to supply the identities that receive access, and administrators change them through Microsoft Entra roles (formerly Azure AD roles). Access asks who may perform which operations, and where: Azure RBAC (Azure role-based access control) grants permissions only through role assignments, each naming a security principal (a user, group, service principal or managed identity), an Azure role and a scope. Governance asks what any request may do or create, and how resources are organized and what they cost: resource locks and Azure Policy assignments whose effect (what happens when its rule matches) is deny (blocks matching create or update requests) or denyAction (blocks matching delete requests) stop requests whatever the caller's role, while tags, budgets and Azure Advisor only label, notify or recommend. Governance also organizes resources into one scope hierarchy of management groups (containers for subscriptions), subscriptions, resource groups and resources: a role assignment, policy assignment or resource lock at one scope reaches everything beneath it, but resources don't inherit their resource group's or subscription's tags. The classic trap is a control from the wrong area: Azure role assignments grant no access to Microsoft Entra ID, and Microsoft Entra role assignments none to Azure resources, except that a Global Administrator (a Microsoft Entra role) who turns on Access management for Azure resources gets the Azure role User Access Administrator, which assigns roles, at root scope (/), covering every subscription and management group.
The domain unfolds in three steps: directory, access, governance
The steps follow the dependencies: a role assignment needs a principal from the directory, and Azure Policy and resource locks then limit what those role assignments allow. Manage Microsoft Entra users and groups covers the Directory area: creating users and groups, editing their properties, assigning licenses, inviting external users as guests and turning on self-service password reset (SSPR); reach for it whenever a requirement changes who exists in the directory or how users recover a forgotten password. For a user synchronized from on-premises Active Directory Domain Services (AD DS), which stays that user's source of authority, identity, contact and job information is edited on-premises, while Microsoft Entra ID attributes such as Usage location, required before a license can be assigned, can be edited in the cloud. Manage access to Azure resources covers the Access area: built-in Azure roles, role assignments at each of the four scope levels and reading a user's effective access; reach for it whenever someone, or something such as an application, needs permission to act on a resource. Manage Azure subscriptions and governance covers the Governance area: Azure Policy, resource locks, tags, resource groups, subscriptions, management groups, and cost control with budgets and Azure Advisor recommendations; reach for it whenever a rule must hold for every caller or the question is about organizing resources and their cost. The decision tree below sorts one requirement the same way.
When two answers both work, take the smallest grant that does the job, given to a group
Microsoft's guidance for both role systems is least privilege: grant the narrowest role at the narrowest scope that still covers the task, so User Administrator beats Global Administrator (both Microsoft Entra roles) for creating users, and the Azure role Virtual Machine Contributor on one resource group beats Contributor on the whole subscription. Assign Azure roles to groups rather than to individual users, which keeps assignments manageable and under the limit on role assignments per subscription, and let groups carry the routine directory work too, from dynamic membership rules that add and remove members automatically to group-based licensing. The instinct has one boundary: a requirement that must hold for everyone, Owners included, is never met by a smaller role, because role assignments only add up; that is a job for Governance, and within Governance for the controls that stop requests, Azure Policy and resource locks, rather than tags, budgets and Azure Advisor, which only label, notify or recommend.
Directory, Access and Governance: what each area decides
| Area | Decides | Key controls | Where it applies | Drill into |
|---|---|---|---|---|
| Directory | Who exists: users, groups and guests, and their licenses and password reset | Microsoft Entra ID objects, changed through Microsoft Entra roles | The Microsoft Entra tenant | Manage Microsoft Entra users and groups |
| Access | Who may perform which operations on Azure resources | Role assignments: security principal, Azure role and scope | Management group, subscription, resource group or resource, inherited downward | Manage access to Azure resources |
| Governance | What any request may do or create, how resources are organized and what they cost | Azure Policy (deny or denyAction effect) and resource locks stop requests; tags, budgets and Azure Advisor label, notify or recommend; management groups, subscriptions and resource groups organize resources | Same scope hierarchy; no resource locks or tags on management groups; tags aren't inherited | Manage Azure subscriptions and governance |