Module 3: Identity Management with Microsoft Entra

🧠 AB-650 Course · Module 3 of 9

Identity Management with Microsoft Entra

AB-650
AB-650 Exam Alignment
AB-650

Domain 2 — Manage identities and access in Microsoft Entra: create and manage users and guest users; manage M365 Groups; manage admin roles and role assignments; configure Privileged Identity Management (PIM); manage administrative units; manage contacts and bulk operations using Microsoft Graph PowerShell.

  • Know the difference between M365 Groups, Security Groups, Distribution Groups, and Mail-enabled Security Groups
  • Understand Privileged Identity Management (PIM) — eligible vs active role assignments and the approval/justification workflow
  • Know what Administrative Units are and how they enable scoped delegation without administrative unit-level role limits
  • Know that bulk user operations (create, update, delete) can be done via CSV import in the M365 Admin Center or Microsoft Graph PowerShell
Exam Tip: AB-650 Domain 2 tests PIM heavily as a new topic for M365 administrators. Know the difference between an eligible assignment (user must activate the role to use it, with optional MFA/approval) vs an active assignment (role is always active). Eligible assignments are the recommended approach for privileged roles like Global Administrator.
Identity is the control plane of Microsoft 365. Every user, group, admin role, and external collaborator is managed through Microsoft Entra ID (formerly Azure Active Directory). Module 3 covers all the identity management skills tested in AB-650 Domain 2 — from day-to-day user and group management to advanced governance features like Privileged Identity Management and Administrative Units.

👤 User and Guest Account Management

User accounts in Microsoft 365 are stored in Microsoft Entra ID and accessed through the M365 Admin Center or the Entra Admin Center. AB-650 tests both internal user management and B2B guest user access.

User Type Account Format Authentication Managed In
Internal Member user@contoso.com (in tenant) Entra ID — password, MFA, SSPR M365 Admin Center or Entra Admin Center
B2B Guest user_domain.com#EXT#@contoso.onmicrosoft.com Their home organisation (federated) or one-time passcode (OTP) if no home IdP Entra Admin Center → External Identities or M365 Admin Center → Guest users
Entra B2B Direct Connect External user accesses resources directly without being added to the directory Home organisation authentication only Entra Admin Center → External Identities → Cross-tenant access
Entra Admin Center › Users › All users
☰
Microsoft Entra admin center
|
Users › All users
Identity
👤 Users
👥 Groups
External identities
Protection
Conditional Access
Identity Protection
PIM
Identity Governance
Access reviews
Administrative units

All users (5,240 total)
Display name UPN User type Licence
Alice Johnson alice@contoso.com Member M365 E5 + Copilot
Bob Partner bob_partner.com#EXT#@... Guest —
Carol Smith carol@contoso.com Member M365 E3

👥 Microsoft 365 Groups & Group Types

Group Type Use Case Supports Email Can Be Used for Licences
Microsoft 365 Group Team collaboration — shared mailbox, calendar, SharePoint site, Teams, Planner automatically created Yes — shared group mailbox Yes (group-based licensing)
Security Group Manage access to apps, resources, and M365 services. Used for RBAC and conditional access. No (unless mail-enabled) Yes (group-based licensing)
Distribution Group Email distribution only — send email to all members Yes — delivery only No
Mail-enabled Security Group Combines security group (resource access) with email distribution capability Yes No
Dynamic Group Membership managed automatically by Entra ID rules based on user attributes (e.g. department, jobTitle, location) Either (based on type) Yes (if security type)

🔐 Privileged Identity Management (PIM)

PIM provides just-in-time (JIT) privileged access for Entra ID roles and Azure resource roles. Instead of having permanent Global Admin rights, admins are eligible for the role and must activate it — reducing the attack surface from compromised admin accounts.

Assignment Type How It Works Best For
Eligible User is eligible for the role but must explicitly activate it. Activation can require MFA, justification, and manager approval. Active for a configurable duration (1–8 hours). All privileged roles — Global Admin, Privileged Role Admin, Security Admin
Active Role is permanently assigned — no activation required. Same as traditional role assignment. Break-glass emergency accounts only; service accounts that require constant role access
Time-bound Either eligible or active assignment with a defined start and end date/time Contractor access, project-based admin roles

🔥 PIM is New in AB-650 (Was Advanced/Optional in MS-102)

Privileged Identity Management is now explicitly tested in AB-650 Domain 2. Key facts: (1) PIM requires Microsoft Entra ID P2 licence (included in M365 E5 and EMS E5); (2) PIM generates audit logs for every role activation — who activated which role, when, and for how long; (3) PIM access reviews can be scheduled to periodically verify that eligible and active assignments are still needed; (4) The first Global Admin assigned eligible PIM must be done by a current permanent Global Admin before PIM can self-govern.

📇 Administrative Units

Administrative Units (AUs) enable scoped administration — restricting an admin’s scope to a subset of users, groups, or devices rather than the entire tenant. Essential for large organisations where regional IT teams manage their own users.

💡 Administrative Units — Key Facts for AB-650

  • An AU is a container that can hold users, groups, and/or devices
  • Assign roles to admins scoped to an AU — e.g. User Administrator for the “UK Staff” AU only
  • The scoped admin cannot manage objects outside their AU
  • AUs do NOT appear as containers in Microsoft 365 Groups or Teams — they are purely an administrative delegation boundary
  • Requires Microsoft Entra ID P1 or P2 licence
  • Objects can belong to multiple AUs simultaneously
Microsoft Graph PowerShell — Identity Management

Connect-MgGraph -Scopes 'User.ReadWrite.All','Group.ReadWrite.All','RoleManagement.ReadWrite.Directory'

# Create a new internal user
$PasswordProfile = @{Password = 'TempP@ssw0rd!'; ForceChangePasswordNextSignIn = $true}
New-MgUser -DisplayName 'Carol Smith' -UserPrincipalName 'carol@contoso.com' -PasswordProfile $PasswordProfile -AccountEnabled $true

# Invite a B2B guest user
New-MgInvitation -InvitedUserEmailAddress 'bob@partner.com' -InviteRedirectUrl 'https://myapps.microsoft.com' -SendInvitationMessage $true

# Create a dynamic security group (auto-membership by department)
New-MgGroup -DisplayName 'IT-Department' -GroupTypes @('DynamicMembership') -SecurityEnabled $true -MailEnabled $false -MembershipRule "(user.department -eq 'IT')" -MembershipRuleProcessingState 'On'

# View PIM eligible role assignments for the directory
Get-MgRoleManagementDirectoryRoleEligibilitySchedule -All | Select-Object PrincipalId,RoleDefinitionId,Status | Format-Table -AutoSize

# Create an Administrative Unit
$AU = New-MgDirectoryAdministrativeUnit -DisplayName 'UK Staff' -Description 'All UK-based users'

# Bulk create users from CSV
Import-Csv 'C:\users.csv' | ForEach-Object {
    $PP = @{Password = $_.TempPassword; ForceChangePasswordNextSignIn = $true}
    New-MgUser -DisplayName $_.DisplayName -UserPrincipalName $_.UPN -PasswordProfile $PP -AccountEnabled $true -UsageLocation 'GB'
}

💡 Best Practices

  • Enable PIM for all Global Administrator assignments immediately — permanently active Global Admin accounts are the highest-value target for attackers
  • Use dynamic group membership rules for licence assignment where possible — users automatically receive the correct licences when attributes like department or jobTitle are set
  • Require justification AND MFA for all PIM role activations — this provides an audit trail and prevents silent privilege escalation
  • Use Administrative Units for multi-region or multi-department organisations to delegate helpdesk teams to manage only their own users without tenant-wide admin rights
  • Set guest user access restrictions via Entra External Identities — by default, guests can enumerate all users and groups in the directory, which is a security risk
  • Schedule quarterly PIM access reviews for all privileged roles — automated reviews in Entra Identity Governance can email role holders to confirm whether they still need the access

🎓 Interview Q&A

Q: What is the difference between a PIM eligible and active role assignment?
A PIM eligible assignment means the user has the potential to use the role but must explicitly activate it through the PIM portal. Activation requires the user to authenticate with MFA, provide a justification, and optionally wait for manager approval. The role is then active for a limited duration (typically 1–8 hours) before expiring. An active assignment means the role is permanently on — equivalent to traditional role assignment. Microsoft recommends eligible assignments for all privileged roles because they reduce the window of exposure: if an admin account is compromised, the attacker does not have instant privileged access — they would still need to pass MFA and approval to activate the role.

Q: When should you use a dynamic group vs a static group for licence assignment?
Dynamic groups are ideal when group membership should automatically reflect HR data (department, job title, office location, employee type). For example, a dynamic group with rule (user.department -eq "Sales") automatically adds or removes users when their department attribute changes in Entra ID — no manual group management needed. Static groups are appropriate when membership doesn’t follow a consistent attribute pattern, or when you need precise control over who gets a licence (e.g. a Copilot pilot with specific approved users). Note: dynamic group membership can take up to 24 hours to reflect attribute changes for large tenants.

Q: What is the purpose of Administrative Units and when would you use them?
Administrative Units (AUs) restrict the scope of an admin’s permissions to a defined subset of users, groups, or devices. They’re used in large organisations where IT responsibility is divided by geography, business unit, or department. For example: assign the “User Administrator” role scoped to the “EMEA” AU to the EMEA helpdesk team — they can reset passwords and manage users in EMEA only, without affecting users in the US or APAC. Without AUs, there is no way to scope built-in Entra ID roles below the tenant level. AUs require at minimum Entra ID P1 and are configured in the Entra Admin Center under Identity → Administrative units.

🎯 AB-650 Mock Test
Module 3 — Identity Management with Microsoft Entra
5 questions · Scenario-based · AB-650 exam style · Pass mark: 70%

Question 1 of 5

An administrator wants Global Administrators to only have elevated access when actively needed, with all activations requiring MFA and a business justification. Which feature should be configured?

AConditional Access policy requiring MFA for all admin sign-ins
BPrivileged Identity Management (PIM) — assign Global Admin as eligible with MFA and justification required for activation
CAdministrative Units — scope the Global Admin role to specific user groups
DEntra ID Protection — enforce MFA on risky sign-ins for admin accounts

✅ Correct: B. PIM with eligible role assignment and MFA + justification requirements is the correct solution. Conditional Access (A) requires MFA at sign-in but does not prevent the role from being permanently active. Administrative Units (C) scope admin rights but don’t implement JIT access. Entra ID Protection (D) reacts to risk events but doesn’t provide JIT privileged access management. PIM requires Entra ID P2 licence.

Question 2 of 5

An organisation has 500 contractors who should automatically receive Microsoft 365 F3 licences when their EmployeeType attribute is set to “Contractor” in Entra ID, and lose them when it changes. What is the most efficient approach?

AManually assign F3 licences to each contractor account via the M365 Admin Center
BCreate a static security group and add contractors; assign the F3 licence to the group
CConfigure a Conditional Access policy that grants F3 access based on EmployeeType
DCreate a dynamic security group with rule (user.employeeType -eq “Contractor”) and assign the F3 licence to the group

✅ Correct: D. A dynamic security group with the membership rule (user.employeeType -eq "Contractor") automatically adds users when their EmployeeType becomes “Contractor” and removes them when it changes. Assigning the F3 licence to this group via group-based licensing automates the entire process. Options A and B require manual management. Conditional Access (C) manages authentication, not licence assignment.

Question 3 of 5

A regional IT team in Germany needs to reset passwords and manage user accounts for German employees only, without being able to modify any other users in the tenant. What is the correct configuration?

AAssign the German IT team the User Administrator role at tenant level with a location filter
BCreate a Conditional Access policy restricting the German IT team’s admin actions to German IP addresses
CCreate an Administrative Unit containing German employees, then assign the User Administrator role scoped to that AU to the German IT team
DGive the German IT team read-only access to the tenant and delegate password reset to users themselves via SSPR

✅ Correct: C. Administrative Units with scoped role assignments are the correct solution. Create an AU for “Germany”, add German employee accounts to it, and assign the User Administrator role scoped to the Germany AU. The German IT team can then manage only users within that AU. The User Administrator role at tenant level (A) would give them access to all users. Conditional Access IP restrictions (B) don’t limit administrative scope. SSPR (D) delegates to users, not to IT admins.

Question 4 of 5

A B2B guest user (bob@partner.com) reports they cannot access shared resources. Investigating, the admin finds the guest user’s account in Entra ID but their invitation status shows “PendingAcceptance.” What does this mean?

AThe guest has not yet clicked the invitation link in their email and completed the consent process
BThe guest’s home organisation has blocked B2B collaboration with this tenant
CThe guest account has been disabled by an administrator
DThe guest user needs a Microsoft 365 licence assigned before they can access shared resources

✅ Correct: A. “PendingAcceptance” means the B2B invitation email was sent but the guest has not yet clicked the invitation link and accepted the consent agreement. Until they do, the account exists in the directory but cannot be used. Resolution: ask the guest to check their email (including spam/junk) and click the invitation link. Alternatively, an admin can resend the invitation or generate a new invitation link from the Entra Admin Center.

Question 5 of 5

Which Microsoft 365 group type automatically creates a shared mailbox, SharePoint site, Teams workspace, and Planner board when the group is created?

ASecurity Group
BMicrosoft 365 Group
CDistribution Group
DMail-enabled Security Group

✅ Correct: B. A Microsoft 365 Group (formerly Office 365 Group) automatically provisions a suite of connected collaboration resources: a shared group mailbox, a shared calendar, a SharePoint team site, a Teams workspace (if Teams is connected), a Planner board, and a OneNote notebook. Security Groups (A) manage access and licences only — no collaboration resources. Distribution Groups (C) provide email delivery only. Mail-enabled Security Groups (D) combine email and security but don’t provision collaboration workspaces.

🔒

This module is lockedComplete Module 2 and pass its mock test to unlock this module.