L1. Entra ID for the AZ-500
Course outlineLesson 1 of 18
Master the Microsoft Entra ID concepts tested on AZ-500: tenant architecture, B2B vs B2C federation, built-in admin roles, and the identity primitives that underpin every other exam domain.
Exam update: AZ-500 retired on August 31, 2026. Use this lesson for identity fundamentals and follow the current SC-500 course for the replacement certification.
What Is Microsoft Entra ID?
Microsoft Entra ID (formerly Azure Active Directory) is the cloud-based identity and access management service that sits at the heart of every Azure subscription. For the AZ-500 exam, you need to understand it not just as a login service but as the policy enforcement boundary for your entire environment.
A tenant is a dedicated instance of Entra ID that an organization receives when signing up for a Microsoft cloud service. Everything including users, groups, service principals, and applications lives inside a tenant. Each Azure subscription is linked to exactly one tenant, but a single tenant can manage multiple subscriptions.
B2B vs B2C
B2B (Business-to-Business): Used when external partner users need access to your internal resources. External users are invited as guests and represented by a guest object in your tenant. You control which resources they can reach via Conditional Access and RBAC. Customer identity: Microsoft Entra External ID external tenants provide customer identity for new customer-facing applications. Azure AD B2C is the legacy separate customer-identity service; it has not been available for new-customer purchases since May 1, 2025. Existing B2C customers can continue using it. Distinguish customer identity from workforce-tenant B2B collaboration.Built-in Admin Roles
The exam frequently tests the principle of least-privilege across admin roles. Key roles to know:
| Role | Scope |
|---|---|
| Global Administrator | Full tenant control: break-glass only |
| Security Administrator | Manage security policies, read security data |
| Security Reader | Read-only access to security features |
| User Administrator | Manage users and groups, reset passwords |
Directory vs Subscription RBAC
Entra ID roles (directory roles) are separate from Azure RBAC roles (subscription/resource roles). A Global Administrator does not automatically have Owner access to Azure subscriptions. The "Access management for Azure resources" toggle grants the Global Administrator User Access Administrator at root scope (/), allowing Azure role assignments across subscriptions. It does not directly grant Owner; assign only the needed resource role, then remove the elevation.
This distinction is a common exam trap.
References
- Azure AD B2C purchase restrictions
- Microsoft Entra built-in role permissions
- Global Administrator Azure elevation
- Microsoft Entra External ID overview
- AZ-500 retirement and legacy skills outline
Continue Learning
- ✓A tenant is a dedicated Entra ID instance: one subscription maps to one tenant, not the reverse
- ✓B2B collaboration uses the workforce tenant; External ID external tenants serve new customer identity scenarios, while Azure AD B2C is legacy
- ✓Global Administrator does not automatically have Azure subscription Owner rights: requires manual elevation
- ✓Security Administrator does not reset passwords; reset authority for other roles depends on the target role and the documented role matrix
- ✓Directory (Entra) roles and Azure RBAC roles are completely separate hierarchies
1. What distinguishes workforce B2B collaboration from legacy Azure AD B2C?
2. Which Entra ID admin role can manage security policies but cannot reset passwords for other administrators?
3. In Entra ID, what is the relationship between a tenant and a directory?