- Phishing-Resistant First: Legacy SMS, voice, and even standard push MFA are vulnerable to Adversary-in-the-Middle (AiTM) token theft. Mandate Phishing-Resistant MFA (Passkeys/FIDO2 or Windows Hello for Business) for all privileged roles.
- Standing Privilege = Zero: Eliminate permanent Global Administrator and Exchange Administrator assignments using Entra Privileged Identity Management (PIM) with time-bound activation and MFA enforcement.
- Safe Rollout Pattern: Always deploy new Conditional Access policies in
enabledForReportingButNotEnforced(Report-Only) mode first, and always exclude your two cloud-only Break-Glass accounts.
In Chapter 2, we built an automated Joiner-Mover-Leaver lifecycle in Microsoft Entra ID. In this chapter, we lock down every authentication event using the three pillars of Zero Trust Identity Security:
- Conditional Access (CA) — the real-time policy decision engine.
- Phishing-Resistant Authentication Strengths (Passkeys / FIDO2) — defeating AiTM phishing kits.
- Privileged Identity Management (PIM) — eliminating standing administrative access.
1. Zero Trust Authentication Decision Flow
Every sign-in to Microsoft 365 should be evaluated dynamically across identity risk, device compliance, and authentication strength before a token is issued.
2. The 6 Foundational Conditional Access Policies Every Tenant Needs
Avoid sprawling 50-policy deployments that nobody understands. Start with this clean, persona-based baseline (and follow a strict naming convention like CA001-Global-...):
| Policy ID | Target | Conditions | Grant / Session Control |
|---|---|---|---|
CA001-Global-Block-LegacyAuth | All Users (excl. Break-Glass) | Exchange ActiveSync & Other Clients | Block Access |
CA002-Admins-Require-PhishingResistantMFA | All Directory Admin Roles | All Cloud Apps | Require Phishing-Resistant MFA + Sign-in frequency 4h |
CA003-AllUsers-Require-MFA | All Users (excl. Break-Glass) | All Cloud Apps | Require MFA (or Passkey Strength) |
CA004-AllUsers-Require-CompliantDevice | All Users | Office 365 / M365 Apps | Require Intune Compliant Device |
CA005-Global-Block-HighRiskSignIn | All Users | Sign-In Risk = High | Block Access (requires Entra ID P2) |
CA006-Admins-Block-DeviceCodeFlow | All Admin Roles | Authentication Flows: Device Code | Block Access (defeats OAuth device-code phishing) |
Audit Existing Conditional Access Policies & Break-Glass Exclusions via Graph
Connect-MgGraph -Scopes "Policy.Read.All"
$breakGlassGroupId = "<BREAK-GLASS-GROUP-OBJECT-ID>"
$policies = Get-MgIdentityConditionalAccessPolicy -All
$audit = $policies | ForEach-Object {
$excludedGroups = $_.Conditions.Users.ExcludeGroups
[PSCustomObject]@{
PolicyName = $_.DisplayName
State = $_.State
BreakGlassExcluded = ($excludedGroups -contains $breakGlassGroupId)
AuthStrengthApplied = ($null -ne $_.GrantControls.AuthenticationStrength)
ModifiedDateTime = $_.ModifiedDateTime
}
}
$audit | Format-Table -AutoSize
3. Enforcing Phishing-Resistant Passkeys (FIDO2) for Admins
Unlike Authenticator push notifications or SMS OTPs, FIDO2 security keys and device-bound Passkeys cryptographically bind the authentication response to the exact domain (login.microsoftonline.com). If an attacker lures an administrator to login-m365-secure.com, the passkey refuses to sign the challenge—stopping AiTM token theft cold.
For a deep dive into rolling out passkey registration campaigns, see Configure Entra ID Passkey (FIDO2) Registration Campaigns with Graph.
Deploy CA002 (Phishing-Resistant MFA for Admins) in Report-Only Mode
Connect-MgGraph -Scopes "Policy.ReadWrite.ConditionalAccess", "Policy.Read.All"
# Built-in Phishing-Resistant MFA Authentication Strength ID
$phishingResistantId = "00000000-0000-0000-0000-000000000004"
# Core Privileged Role Template IDs (Global Admin, Exchange Admin, SharePoint Admin, Security Admin, Intune Admin)
$adminRoleIds = @(
"62e90394-69f5-4237-9190-012177145e10",
"29232cdf-9323-42fd-ade2-1d097af3e4de",
"f28a1f50-f6e7-4571-818b-6a12f2af6b6c",
"194ae4cb-b126-40b2-bd5b-6091b380977d",
"3a2c62db-5318-420d-8d74-23affae5d460"
)
$policyParams = @{
DisplayName = "CA002-Admins-Require-PhishingResistantMFA"
State = "enabledForReportingButNotEnforced" # Switch to 'enabled' after 7-day validation
Conditions = @{
Users = @{
IncludeRoles = $adminRoleIds
ExcludeGroups = @("<BREAK-GLASS-GROUP-OBJECT-ID>")
}
Applications = @{
IncludeApplications = @("All")
}
ClientAppTypes = @("all")
}
GrantControls = @{
Operator = "OR"
AuthenticationStrength = @{
Id = $phishingResistantId
}
}
SessionControls = @{
SignInFrequency = @{
Value = 4
Type = "hours"
IsEnabled = $true
}
}
}
New-MgIdentityConditionalAccessPolicy -BodyParameter $policyParams
4. Eliminating Standing Privileges with Entra PIM
With Microsoft Entra Privileged Identity Management (PIM) (Entra ID P2), administrators operate as standard unprivileged users 95% of the day. When they need to modify Exchange transport rules or Entra policies, they elevate Just-In-Time (JIT) for a bounded window (e.g., 2–4 hours), with every elevation logged and alerted.
Audit Standing (Permanent) Privileged Role Assignments via Graph
Any permanent assignment outside your two break-glass accounts should be converted to Eligible in PIM:
Connect-MgGraph -Scopes "RoleManagement.Read.Directory", "User.Read.All"
$roleDefs = @{}
Get-MgRoleManagementDirectoryRoleDefinition -All | ForEach-Object { $roleDefs[$_.Id] = $_.DisplayName }
# Fetch active permanent role assignments (Schedule instances with AssignmentType = Assigned)
$activeAssignments = Get-MgRoleManagementDirectoryRoleAssignmentScheduleInstance -All |
Where-Object { $_.AssignmentType -eq "Assigned" -and $null -eq $_.EndDateTime }
$standingAdmins = foreach ($a in $activeAssignments) {
$principal = Get-MgDirectoryObject -DirectoryObjectId $a.PrincipalId -ErrorAction SilentlyContinue
[PSCustomObject]@{
RoleName = $roleDefs[$a.RoleDefinitionId]
PrincipalName = $principal.AdditionalProperties.displayName
UPN = $principal.AdditionalProperties.userPrincipalName
ObjectType = $principal.AdditionalProperties.'@odata.type' -replace '#microsoft.graph.', ''
}
}
Write-Host "Permanent (Standing) Privileged Assignments Found: $($standingAdmins.Count)" -ForegroundColor Yellow
$standingAdmins | Sort-Object RoleName | Format-Table -AutoSize
Chapter 3 Verification Checklist
Before moving on to Chapter 4 (Exchange Online Core: User, Shared, Resource & Archive Mailboxes + RBAC), verify:
- [ ] Two cloud-only Break-Glass Global Admin accounts exist with FIDO2 keys stored in physical safes and are excluded from all CA policies.
- [ ] Legacy Authentication (
CA001) and Device Code Flow (CA006) are blocked tenant-wide. - [ ] All privileged administrators are registered with Passkeys/FIDO2 or Windows Hello for Business and governed by Phishing-Resistant MFA.
- [ ] Zero human administrators hold permanent standing
Global AdministratororExchange Administratorassignments outside PIM.
💬 Reader Comments & Feedback
Did this runbook help, or did Microsoft change a cmdlet or UI menu? Share your feedback below.
Leave a Comment or Report an Update