Identity for Microsoft Azures
Azure identity and governance is how access and order are controlled across a tenant. Microsoft Entra ID holds users, groups and applications, Azure RBAC grants roles at a scope, and governance tools such as Azure Policy, locks and management groups enforce standards. It is the first stage of the roadmap because every resource depends on it.
Stage: Identity and Governance · Part of the Microsoft Azure roadmap · Last reviewed 19 November 2026
What to learn in Identity
- Create users and groups in Microsoft Entra ID and assign licences
- Assign a built-in RBAC role at subscription, resource group or resource scope
- Explain the difference between Entra roles and Azure RBAC roles
- Apply Azure Policy to require tags or restrict allowed regions
- Use resource locks and management groups to protect and organise subscriptions
Identity interview questions
What is the difference between Entra ID roles and Azure RBAC roles?
Entra ID roles control directory tasks such as managing users or applications. Azure RBAC roles control access to Azure resources such as virtual machines and storage. They are separate systems, though a Global Administrator can elevate to manage Azure access.
What is the difference between Azure Policy and RBAC?
RBAC decides who can perform actions on resources. Azure Policy decides what state resources are allowed to be in, such as permitted regions or required tags, regardless of who creates them. A user can have permission yet still be blocked by a policy.
Where Identity fits in the Microsoft Azure roadmap
Identity belongs to the Identity and Governance stage (beginner level). Control access.
Back to the full Microsoft Azure roadmap