Identity, Access & RBAC in Azure
AZ-900 AZ-900 · Describe Azure architecture and services
Identity is the control plane
In the cloud, identity is the new perimeter. There is no office wall to hide behind: users sign in from anywhere, on any device, to services that live on the internet. So the first question for any access is not "where are you?" but "who are you, and should you be allowed in?" Microsoft's identity service, Microsoft Entra ID (formerly Azure Active Directory), is the answer to that question for Azure. It is a cloud-based identity and access management service: it stores user accounts, groups, and application registrations, verifies sign-ins, and controls access to Azure resources, Microsoft 365, and thousands of other applications.
Entra ID is not the same as on-premises Active Directory. Traditional Active Directory (AD DS) is built around domain-joined machines on a corporate network, using protocols such as Kerberos and LDAP. Entra ID is built for the cloud: it uses modern web protocols (OAuth 2.0, OpenID Connect, SAML), works over the internet, and manages identities for cloud applications. Organisations commonly use both — on-premises AD for their internal network, Entra ID for the cloud, synchronised with Microsoft Entra Connect — and the exam expects you to know Entra ID is the cloud directory.
Microsoft Entra Domain Services fills the gap between the two: it provides managed domain services (domain join, group policy, LDAP, Kerberos) in the cloud, so virtual machines can join a domain without the organisation deploying and managing its own domain controllers. If a scenario describes VMs that need domain-join and group policy without running domain controllers, Entra Domain Services is the answer.
Authentication methods
Authentication is proving who you are. Entra ID supports several methods, and the exam names three. Single sign-on (SSO) lets a user sign in once and access many applications without signing in again — one identity, one password prompt, many apps. Multifactor authentication (MFA) requires two or more verification factors: something you know (password), something you have (phone, authenticator app, hardware key), or something you are (fingerprint, face). MFA is the single most effective defence against stolen passwords, and the exam treats it as the standard answer to "how do we protect accounts against password theft?" Passwordless authentication removes the password entirely, using the Microsoft Authenticator app, Windows Hello (face or fingerprint), or a FIDO2 security key. Passwordless is both more secure (nothing to phish) and more convenient (nothing to remember) — the exam presents it as the strongest authentication option.
External identities
Organisations do not only manage their own employees. External identities are people outside the organisation who need access: partners, suppliers, contractors, and customers. Microsoft Entra B2B (business-to-business) lets external users — partners and suppliers — sign in to your applications with their own credentials, as guest users in your directory. Microsoft Entra B2C (business-to-customer) provides identity for customer-facing applications, letting customers sign up and sign in with their own accounts (including social logins). The distinction is the audience: B2B is for business partners collaborating with you; B2C is for your customers using your apps. Both now sit under the Microsoft Entra External ID umbrella.
Conditional Access: access decisions based on signals
Microsoft Entra Conditional Access is the policy engine for sign-ins: if a sign-in matches certain conditions, then enforce certain controls. The conditions (signals) include who the user is, which group they belong to, what device they are on, where they are signing in from, and the assessed risk of the sign-in. The controls include requiring MFA, requiring a compliant or hybrid-joined device, blocking access entirely, or requiring a password change. The classic examples: "require MFA when signing in from outside the office", "block sign-ins from countries we do not operate in", "require a managed device to access financial data". Conditional Access turns a flat yes/no into a risk-based decision — and the exam tests it with exactly those "require MFA when..." scenarios. (Conditional Access requires a Microsoft Entra ID P1 licence or higher.)
Azure RBAC: who can do what to which resource
Azure role-based access control (RBAC) controls what a user, group, or application can do to Azure resources. A role assignment has three parts: a security principal (who — a user, group, service principal, or managed identity), a role definition (what — a set of permissions), and a scope (where — a management group, subscription, resource group, or single resource). Permissions flow down the hierarchy: a role assigned at the subscription applies to every resource group and resource beneath it.
The built-in roles to know are: Owner (full access, including managing access for others), Contributor (create and manage resources, but cannot grant access), Reader (view resources only), and User Access Administrator (manage access only). The exam's favourite RBAC distinction is Owner vs Contributor: both manage resources, but only Owner can grant access to others. RBAC follows least privilege: give each person the smallest role that lets them do their job, at the narrowest scope. A developer who needs to manage one application's resources gets Contributor on that resource group — not Owner on the subscription.
Worked example: securing a new project
A company starts a project with internal developers, an external contractor, and a finance reviewer. The design: developers get Contributor on the project's resource group; the contractor gets a B2B guest account with Reader on the same group; the finance reviewer gets Reader on the subscription's cost data only. Conditional Access requires MFA for everyone signing in from outside the office, and blocks sign-ins from high-risk locations. The contractor's guest account expires when the project ends. Four identity concepts — RBAC, B2B, Conditional Access, least privilege — in one design, and each decision maps to an exam objective.
Identities for applications, not just people
Users are not the only identities in Entra ID. Applications and services need identities too, so they can authenticate to other resources — a web application reading from a database, for example, needs to prove who it is. A service principal is an identity for an application: the application signs in with a secret or certificate, and RBAC controls what it can do, exactly as with a user. The problem with service principals is the secret: it must be stored, rotated, and protected, and a leaked secret is a breach. Managed identities solve this: Azure creates and manages the identity for an Azure resource (a VM, an App Service, a Function), rotates its credentials automatically, and the code never sees a secret at all. When a scenario describes an application needing to access another Azure service without storing credentials, the managed identity is the answer — it is the identity equivalent of the exam's recurring theme: let the platform manage what it can, and keep secrets out of your code.
Exam traps to watch for
- Calling Entra ID 'Azure Active Directory' on the exam. The service was renamed Microsoft Entra ID, and the current objectives use the new name.
- Confusing Owner with Contributor. Both manage resources, but only Owner can grant access to others; Contributor cannot.
- Assigning a role at the subscription when the need is one resource group. RBAC follows least privilege: the narrowest scope that covers the job.
- Mixing up B2B and B2C. B2B is for business partners collaborating as guests; B2C is for customers signing in to your applications.
Practice questions
Test yourself on this guide. Answers are checked instantly, with a full explanation for each question.
Q1.A company wants employees to sign in once in the morning and then access email, the HR system, and the project tool without signing in again to each one. Which authentication feature provides this?
Explanation: Single sign-on lets a user authenticate once and access multiple applications without signing in again. MFA adds extra verification factors; it does not reduce sign-in prompts. Conditional Access sets policy conditions on sign-ins. RBAC controls what a user can do to Azure resources, not how many times they sign in.
Exam objective: AZ-900 Describe Azure identity, access, and security: describe authentication methods in Azure, including single sign-on (SSO), multifactor authentication (MFA), and passwordless
Q2.After several phishing attacks stole employee passwords, a company wants to require a second verification step — an approval on the employee's phone — at every sign-in. Which method should it enable?
Explanation: MFA requires two or more factors — here, the password plus a phone approval — so a stolen password alone is not enough. SSO reduces sign-in prompts but does not add a second factor. Passwordless removes the password rather than adding a second factor to it (and the scenario keeps the password). Azure Policy governs resource configuration, not user sign-ins.
Exam objective: AZ-900 Describe Azure identity, access, and security: describe authentication methods in Azure, including single sign-on (SSO), multifactor authentication (MFA), and passwordless
Q3.A company wants to enforce this rule: 'Anyone signing in from outside the office must complete MFA, and sign-ins from countries where we have no staff are blocked.' Which Azure feature enforces this kind of rule?
Explanation: Conditional Access makes access decisions from signals (location, device, user, risk) and enforces controls such as requiring MFA or blocking access. Azure Policy governs resource configuration, not sign-ins. Resource locks prevent resource deletion or modification. Entra ID is the identity service itself; Conditional Access is its policy engine for these decisions.
Exam objective: AZ-900 Describe Azure identity, access, and security: describe Microsoft Entra Conditional Access
Q4.A developer needs to create and manage resources in one resource group, but must NOT be able to grant other people access to those resources. Which built-in RBAC role should be assigned, and at which scope?
Explanation: Contributor can create and manage resources but cannot grant access, and assigning it at the resource group follows least privilege (narrowest scope). Owner can grant access, which the requirement forbids — and the subscription scope is too broad. Reader can only view resources. User Access Administrator manages access only and cannot manage resources.
Exam objective: AZ-900 Describe Azure identity, access, and security: describe Azure role-based access control (RBAC)
Q5.A company wants its suppliers to access a shared project application using their own company credentials, without the company creating full employee accounts for them. Which Entra feature supports this?
Explanation: Entra B2B (business-to-business) lets external partners and suppliers sign in as guest users with their own credentials. B2C is for customer-facing applications, not business partners. Entra Domain Services provides managed domain-join services for VMs. Conditional Access sets sign-in policies; it does not invite external users.
Exam objective: AZ-900 Describe Azure identity, access, and security: describe external identities in Azure
Q6.A company runs virtual machines in Azure that need to join a domain and receive Group Policy settings, but the company does not want to deploy and manage its own domain controllers. Which service should it use?
Explanation: Entra Domain Services provides managed domain services — domain join, Group Policy, LDAP, Kerberos — without deploying domain controllers. Entra ID alone does not provide domain join or Group Policy for VMs. Azure Policy governs resource configuration. B2B is for external partner identities, not domain services.
Exam objective: AZ-900 Describe Azure identity, access, and security: describe directory services in Azure, including Microsoft Entra ID and Microsoft Entra Domain Services
Q7.A role assignment in Azure RBAC is made up of which three elements?
Explanation: An RBAC role assignment combines a security principal (who), a role definition (what permissions), and a scope (where). User/password/device describes authentication, not RBAC. Subscription/resource group/resource is the management hierarchy. Policy/initiative/assignment belongs to Azure Policy.
Exam objective: AZ-900 Describe Azure identity, access, and security: describe Azure role-based access control (RBAC)
Q8.Which authentication method removes the password entirely, using something like Windows Hello facial recognition or a FIDO2 security key?
Explanation: Passwordless authentication replaces the password with a stronger factor such as biometrics (Windows Hello) or a FIDO2 key — nothing to phish or forget. SSO reduces repeated sign-ins but still starts with a password. MFA adds a second factor alongside the password. Conditional Access is the policy engine that can require these methods, not a method itself.
Exam objective: AZ-900 Describe Azure identity, access, and security: describe authentication methods in Azure, including single sign-on (SSO), multifactor authentication (MFA), and passwordless