📂 Course: AB-650: Administering Microsoft 365 and AI Services 📦 Module: 4 of 9 🎯 Exam: AB-650 📑 Domain: 2 — Govern and Secure M365 Tenants & Workloads (40–45%) ⌛ Read time: ~28 min
AB-650 Exam Alignment AB-650
Domain 2 — Manage authentication and secure access: manage authentication methods and authentication method policies; configure Microsoft Entra Password Protection and SSPR; investigate and resolve sign-in and MFA issues; configure Conditional Access policies; manage Entra ID Protection risk policies; configure agent Conditional Access (new in AB-650).
Know the authentication methods available in Entra ID: FIDO2, Windows Hello for Business, Microsoft Authenticator, SMS, OATH hardware/software tokens, certificate-based authentication
Understand Conditional Access policy evaluation: conditions (user, device, location, app, risk) and grant controls (MFA, compliant device, approved app)
Know that Entra ID Protection risk levels (low, medium, high) can trigger Conditional Access policies automatically
Understand agent Conditional Access — new in AB-650 — applies Conditional Access to AI agent identities managed by Entra Agent ID
Exam Tip: AB-650 tests Conditional Access scenarios heavily. Know the order of evaluation: Named Locations and compliant device checks happen BEFORE MFA prompts. Know that “Report-only” mode lets you evaluate a CA policy impact without enforcing it — use this before enabling new policies in production.
Authentication is the first line of defence for Microsoft 365. In the AB-650 era, authentication includes not just users but also AI agents via Microsoft Entra Agent ID. This module covers authentication methods management, Conditional Access policy design, SSPR, Entra Password Protection, Entra ID Protection, and the new agent Conditional Access capability introduced with Agent 365.
🔐 Authentication Methods in Microsoft Entra ID
Microsoft Entra ID supports a range of authentication methods, managed via the Authentication methods policy (replacing the legacy per-method settings). AB-650 tests which methods are available and when each should be used.
Method
Phishing Resistant?
Licence Required
Best For
FIDO2 Security Key
✅ Yes
Entra ID Free+
High-security environments; passwordless for all users including shared devices
Windows Hello for Business
✅ Yes
Entra ID Free+ (with Entra join or hybrid join)
Corporate Windows devices — PIN or biometric replaces password
Microsoft Authenticator (Passwordless)
✅ Yes
Entra ID Free+
Passwordless sign-in via phone app — approves sign-in with biometric on phone
Microsoft Authenticator (TOTP/push)
❌ No (push hijackable)
Entra ID Free+
Standard MFA for most users — push notifications or TOTP codes
Certificate-Based Authentication (CBA)
✅ Yes
Entra ID P1+
Smart card / certificate authentication for regulated industries (government, finance)
SMS / Voice call
❌ No (SIM swap, interception)
Entra ID Free+
Legacy — use only when no other option. Microsoft recommends migrating away from SMS MFA.
Temporary Access Pass (TAP)
N/A — time-limited
Entra ID P1+
Onboarding new users, recovering locked-out accounts, registering passwordless methods
☰ Microsoft Entra admin center | Protection › Authentication methods
Protection
Authentication methods
Conditional Access
Identity Protection
Password protection
MFA
Identity Governance
Access reviews
Entitlement management
Authentication methods — Policies
Method
State
Target
Microsoft Authenticator
Enabled
All users
FIDO2 security key
Enabled
Security-Admins group
SMS
Enabled (legacy)
Specific users only
Temporary Access Pass
Enabled
Helpdesk-Admins group
🔓 Conditional Access Policies
Conditional Access is the primary tool for enforcing access controls in Microsoft 365. It evaluates signals (user, device, location, app, risk) and applies grant or session controls.
CA Component
What It Evaluates / Controls
Common Values
Assignments — Users
Who the policy applies to
All users, specific groups, directory roles, guest users. Exclude: break-glass accounts always.
Assignments — Target resources
Which apps the policy applies to
All cloud apps, Microsoft 365, specific apps (Exchange, SharePoint, Copilot)
Conditions — Device platform
Filter by OS
Windows, macOS, iOS, Android
Conditions — Location
Named locations (IP ranges) or countries
Trusted corporate networks, block access from high-risk countries
Conditions — Sign-in risk
Entra ID Protection risk level at sign-in
Low, Medium, High — require MFA or block for High risk
Grant — Require MFA
Enforce multi-factor authentication
Most common grant control — require Microsoft Authenticator or FIDO2
Grant — Require compliant device
Device must be Intune-compliant
Used with Microsoft 365 apps to ensure managed device access only
Grant — Terms of use
Require user to accept ToU before access
Used for guest users and B2B collaboration
🔥 New in AB-650: Agent Conditional Access
Agent Conditional Access extends Conditional Access policies to AI agent identities managed by Microsoft Entra Agent ID. Just as you enforce MFA and compliant device requirements on human users, you can enforce access restrictions on agents accessing M365 resources. For example: require that agents can only access SharePoint from trusted networks; block agents from accessing resources outside approved hours; or require agent access to sensitive data to go through an approval workflow. This is configured in Entra Admin Center → Protection → Conditional Access, targeting agent service principals registered in Entra Agent ID.
🔒 Entra Password Protection & SSPR
Feature
What It Does
Location
Microsoft Entra Password Protection
Blocks known weak passwords (global banned list) and custom banned passwords defined by the admin. Works for cloud accounts AND on-premises AD (via proxy agent). Enforces smart lockout.
Add company-specific terms to the banned list (company name, product names, city names commonly used in weak passwords)
Same — Password protection → Custom banned passwords
Self-Service Password Reset (SSPR)
Lets users reset their own passwords without contacting helpdesk. Requires ≥1 authentication method registered (Authenticator app, email, phone, security questions)
Entra Admin Center → Users → Password reset
SSPR writeback
For hybrid environments — writes password reset back to on-premises AD. Requires Entra Connect and P1 licence.
Entra Connect → Optional features → Password writeback
Microsoft Graph PowerShell — Authentication & Conditional Access
Connect-MgGraph-Scopes'Policy.Read.All','Policy.ReadWrite.ConditionalAccess','UserAuthenticationMethod.ReadWrite.All'# Get all Conditional Access policies and their stateGet-MgIdentityConditionalAccessPolicy | Select-Object DisplayName,State,Id | Format-Table-AutoSize# Create a Conditional Access policy requiring MFA for Exchange Online$Policy = @{
DisplayName = 'Require MFA for Exchange Online'
State = 'enabled'
Conditions = @{
Users = @{IncludeUsers = @('All')}
Applications = @{IncludeApplications = @('00000002-0000-0ff1-ce00-000000000000')}
}
GrantControls = @{
Operator = 'OR'
BuiltInControls = @('mfa')
}
}
New-MgIdentityConditionalAccessPolicy-BodyParameter$Policy# Issue a Temporary Access Pass for passwordless onboardingNew-MgUserAuthenticationTemporaryAccessPassMethod-UserId'carol@contoso.com'-StartDateTime (Get-Date) -LifetimeInMinutes 60
# Review high-risk sign-in detections (Entra ID Protection)Get-MgRiskDetection-Filter"riskLevel eq 'high'" | Select-Object UserDisplayName,RiskEventType,RiskLevel,DetectedDateTime | Format-Table-AutoSize
💡 Best Practices
Always create a break-glass emergency access account and exclude it from ALL Conditional Access policies — store credentials in a physical safe; this prevents full lockout if CA misconfiguration occurs
Use Report-only mode when creating new Conditional Access policies — monitor the impact in sign-in logs for 7–14 days before enabling enforcement
Migrate users from SMS MFA to Microsoft Authenticator or FIDO2 — SMS is vulnerable to SIM swap attacks and is not considered phishing-resistant
Enable SSPR before enabling Conditional Access MFA — users who cannot complete MFA need SSPR as a recovery path
Issue Temporary Access Passes (TAPs) to new hires for initial authentication and passwordless method registration — never email temporary passwords
Configure Entra Password Protection in Audit mode first to see which passwords would be blocked before switching to Enforced mode
🎓 Interview Q&A
Q: What is the difference between MFA enforced through Conditional Access vs legacy per-user MFA?
Conditional Access MFA is context-aware — MFA is triggered based on conditions (risky sign-in, accessing sensitive apps, untrusted network). A user signing in from a trusted corporate network with a compliant device might not be prompted for MFA, while the same user from a personal device on an untrusted network would be. Legacy per-user MFA (now deprecated) always requires MFA at every sign-in regardless of context, creating friction and poor user experience. Microsoft recommends all organisations migrate to Conditional Access-based MFA and disable legacy per-user MFA. Per-user MFA also doesn’t support modern authentication methods like FIDO2 as fully as Conditional Access.
Q: What is Entra ID Protection and how does it integrate with Conditional Access?
Microsoft Entra ID Protection uses machine learning to detect anomalous authentication events and assigns risk levels (low, medium, high) to sign-in attempts and user accounts. Sign-in risk detects real-time anomalies (atypical travel, unfamiliar location, impossible travel). User risk accumulates over time (leaked credentials, suspicious activity patterns). These risk signals integrate directly with Conditional Access — you can create policies that say: “If sign-in risk is High, block access” or “If user risk is Medium or above, require password change.” This creates an automated, risk-adaptive access control system. Entra ID Protection requires Entra ID P2 licence.
Q: What is a Temporary Access Pass and when should you use it?
A Temporary Access Pass (TAP) is a time-limited passcode issued by an admin that allows a user to sign in without their regular password. TAPs are used for: (1) New employee onboarding — allow the new hire to sign in and register their MFA method and passwordless authenticator without needing a temporary password emailed to them; (2) Account recovery — when a user has lost access to their MFA device and cannot complete verification; (3) Passwordless method registration — TAPs provide a trusted bootstrap mechanism to register FIDO2 keys or Windows Hello. TAPs can be one-time or multi-use, with configurable validity periods (1–30 days). Requires Entra ID P1+.
An organisation is rolling out phishing-resistant MFA. They want a method that works on Windows corporate devices without requiring a separate physical token. Which authentication method should they prioritise?
ASMS one-time passcode — phishing-resistant and widely compatible
BMicrosoft Authenticator push notification — most phishing-resistant method available
CWindows Hello for Business — phishing-resistant biometric or PIN tied to the corporate device
DOATH hardware token — phishing-resistant and works on all devices
✅ Correct: C.Windows Hello for Business is phishing-resistant, works on corporate Windows devices, and replaces passwords with a biometric (face/fingerprint) or PIN tied to the specific device via cryptographic keys. No separate token needed. SMS (A) is NOT phishing-resistant — it is vulnerable to SIM swap attacks. Microsoft Authenticator push (B) is NOT phishing-resistant (MFA fatigue / push hijacking attacks are possible; Authenticator passwordless is phishing-resistant, but push MFA is not). OATH hardware tokens (D) are phishing-resistant but require physical tokens.
Question 2 of 5
A new Conditional Access policy requiring MFA for all users has been created in the tenant. An administrator is locked out immediately after enabling it. What mistake was most likely made?
AThe policy was targeting the wrong cloud apps and should have been scoped to Exchange Online only
BThe policy was set to “Block” instead of “Require MFA” in the grant controls
CThe administrator’s MFA registration expired and they need to re-register
DThe break-glass emergency access account was included in the policy scope, locking out the recovery account along with all other users
✅ Correct: D. The most common lockout cause with CA policies is failing to exclude break-glass emergency accounts. Break-glass accounts must ALWAYS be excluded from every Conditional Access policy — they are the last resort for recovering from CA misconfigurations. The admin is locked out because their regular admin account cannot complete MFA (possibly due to a CA loop or MFA not being registered), and the break-glass account is also blocked. Resolution: use a break-glass account (if not excluded from CA) or contact Microsoft Support.
Question 3 of 5
An organisation wants to evaluate a new Conditional Access policy requiring compliant devices before applying it to production. Which CA policy state should they use first?
AReport-only — evaluates the policy and logs results in sign-in logs without enforcing it
BDisabled — creates the policy but prevents it from running at all
CEnabled — enforce immediately but monitor the Entra sign-in logs for failures
DPilot mode — enforce only for the Security group while reporting for all others
✅ Correct: A.Report-only mode evaluates the policy conditions and logs whether each sign-in would have been granted or blocked, without actually enforcing anything. This lets administrators see the real impact (how many users would be affected, which sign-ins would fail) before enabling enforcement. Monitor in Entra Admin Center → Monitoring → Sign-in logs and filter by Report-only results. There is no “Pilot mode” (D) — to pilot enforcement you would scope the policy to a specific user group and set it to Enabled.
Question 4 of 5
Entra ID Protection detects a high-risk sign-in for a user account (impossible travel from London and New York within 30 minutes). The organisation wants this to trigger automatic MFA challenge. How should this be configured?
AConfigure the user risk policy in Entra ID Protection to require MFA for high-risk users
BCreate a Conditional Access policy with Sign-in risk set to High and grant control set to Require MFA
CEnable Smart Lockout in Entra Password Protection to block high-risk sign-ins automatically
DCreate a Microsoft Sentinel alert rule to trigger MFA on high-risk detections from Entra ID Protection
✅ Correct: B. Creating a Conditional Access policy with Sign-in risk: High as a condition and Require MFA as the grant control is the correct approach for reacting to real-time sign-in risk. This is evaluated during the sign-in and triggers MFA immediately when the risk is detected. Option A (user risk policy) applies when user account risk accumulates over time — not real-time sign-in events. Smart Lockout (C) blocks accounts after failed password attempts — it doesn’t evaluate location/travel anomalies. Sentinel (D) is a SIEM and provides alerting, not automatic access control.
Question 5 of 5
A new employee has just started but cannot register their Microsoft Authenticator app because they don’t have any verified MFA method yet, and Conditional Access requires MFA before registering MFA methods. What should the administrator do?
ATemporarily disable Conditional Access MFA for the user until they register
BAdd the user to a group excluded from all Conditional Access policies permanently
CCreate a new Conditional Access policy allowing MFA registration without MFA for new users
DIssue a Temporary Access Pass (TAP) — the user uses the TAP to sign in and register their Authenticator without needing existing MFA
✅ Correct: D. A Temporary Access Pass (TAP) is specifically designed to bootstrap new user authentication and MFA registration. The admin generates a TAP (limited-use, time-limited code) and provides it to the new employee. The employee signs in using the TAP — which satisfies MFA requirements — and can then register their Microsoft Authenticator app or FIDO2 key. Once registered, the TAP is no longer needed. Options A and B create security gaps. Option C could work but adds complexity when TAP already solves this cleanly.
🔒
This module is lockedComplete Module 3 and pass its mock test to unlock this module.
🔒
Module 5 is locked
Score 70% or higher on the mock test above to unlock the next module.