Study guide

10.1 Planning for Identity Protection

Microsoft 365 Administrator Expert MS-102

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

1.1 MS-102 Exam Facts & Blueprint 1.2 Registration, Retake & Renewal 1.3 Study Strategy & Using This Guide

2 Tenant Setup, Domains & Org Settings

2.1 Creating a Microsoft 365 Tenant 2.2 Implementing and Managing Domains 2.3 Configuring Org Settings: Security, Privacy & Profile

3 Service Health, Network & Software Updates

3.1 Monitoring Service Health & Notifications 3.2 Network Connectivity Insights 3.3 Configuring & Monitoring Software Updates

4 Adoption, Usage & Microsoft 365 Backup

4.1 Monitoring Adoption & Usage 4.2 Configuring & Managing Microsoft 365 Backup

5 Users, Contacts, Groups & Shared Mailboxes

5.1 Creating & Managing Users Including External Users 5.2 Creating & Managing Contacts 5.3 Managing Microsoft 365 Groups & Shared Mailboxes

6 Licensing & Bulk User Management

6.1 Managing & Monitoring Microsoft 365 Licenses 6.2 Bulk User Management with Graph & Entra PowerShell

7 Roles, Admin Units & Privileged Identity Management

7.1 Implementing & Managing Roles in M365 & Entra ID 7.2 Managing Permissions for Defender XDR, Purview & Workloads 7.3 Managing Delegation with Administrative Units 7.4 Managing Entra ID Roles in PIM

8 Identity Synchronization with Entra Connect

8.1 Preparing for Identity Synchronization & IdFix 8.2 Directory Sync with Entra Connect Sync & Cloud Sync 8.3 Monitoring Sync with Entra Connect Health 8.4 Troubleshooting Synchronization

9 Authentication, SSPR & Password Protection

9.1 Implementing & Managing Authentication Methods 9.2 Self-Service Password Reset (SSPR) 9.3 Microsoft Entra Password Protection 9.4 Investigating & Resolving Authentication Issues

10 Identity Protection, Conditional Access & MFA

10.1 Planning for Identity Protection 10.2 Implementing Entra Identity Protection 10.3 Planning & Implementing Conditional Access Policies 10.4 Managing MFA with Conditional Access

11 Defender XDR Posture, Incidents & Threat Intelligence

11.1 Security Exposure Management & Secure Score 11.2 Incidents, Alerts & Advanced Hunting 11.3 Reviewing Defender XDR Reports 11.4 Defender Threat Intelligence

12 Defender for Office 365: Policies, Alerts & Investigation

12.1 Threat Policies & Rules in Defender for Office 365 12.2 Configuring Alert Policies 12.3 Investigating & Responding to Email Threats

13 Attack Simulation & Restricted Entities

13.1 Managing Attack Simulations & Training 13.2 Managing Restricted Entities & Blocked Users

14 Defender for Endpoint

14.1 Onboarding Devices to Defender for Endpoint 14.2 Configuring Endpoint Settings 14.3 Defender Vulnerability Management Dashboard

15 Defender for Cloud Apps

15.1 Configuring the App Connector for Microsoft 365 15.2 Defender for Cloud Apps Policies & Alerts 15.3 Interpreting the Activity Log 15.4 Cloud App Discovery

16 Purview Information Protection & Data Lifecycle

16.1 Sensitive Information Types 16.2 Retention Labels & Policies 16.3 Sensitivity Labels & Policies 16.4 Monitoring Label Usage: Content & Activity Explorer

17 Purview Data Loss Prevention

17.1 DLP Policies for Microsoft 365 Workloads 17.2 Configuring Endpoint DLP 17.3 Reviewing & Responding to DLP Alerts, Events & Reports

18 Final Review & Exam Strategy

18.1 Exam-Day Strategy & Question Handling 18.2 Final Review Checklist & Next Steps

10.1 Planning for Identity Protection

Key Takeaways Explain This Topic AI

Microsoft Entra ID Identity Protection requires Entra ID P2 licensing for risk-based policies and the risky users/risky sign-ins/risk detections reports

Identity Protection derives user risk and sign-in risk signals from Microsoft's threat intelligence feed and machine-learning models, not from on-premises logs

Security Defaults and Conditional Access are mutually exclusive — enabling Conditional Access policies requires turning Security Defaults off

User risk reflects the probability that an identity is compromised; sign-in risk reflects the probability that a given sign-in is not the legitimate owner

Planning decisions center on which risk policies to enforce, which risk-level thresholds to trigger on, and how users remediate (SSPR or MFA)

Last updated: August 2026

Quick Answer: Entra ID Identity Protection turns Microsoft's threat intelligence and machine-learning signals into two risk scores — user risk (the probability the identity itself is compromised) and sign-in risk (the probability that a specific sign-in is not performed by the legitimate owner). Planning means deciding which risk-based policies to enforce, what thresholds to trigger on, and how users remediate. Risk-based policies and the Identity Protection reports require Entra ID P2 licensing for every user covered by a policy.

Microsoft Entra ID Identity Protection is a security service that detects identity-based risks and lets you automate a response. The MS-102 administrator plans it before configuring it: the planning choices determine what users experience and what the helpdesk has to support.

The Two Risk Scores

Identity Protection computes two distinct scores, and the distinction matters on the exam:

Score Meaning Typical Trigger

User risk Probability that the user's identity is compromised Leaked credentials, unfamiliar sign-in properties over time

Sign-in risk Probability that this specific sign-in is not the legitimate owner Impossible travel, anonymous IP, malware-linked IP

User risk is aggregated across detections tied to the user; sign-in risk is evaluated per authentication. A user can be high user risk with a low-risk sign-in (the identity is compromised but the attacker signs in from a familiar location), or low user risk with a high-risk sign-in (the legitimate user is on a new network). The two policies respond to these independently.

Licensing: Entra ID P2 Is Required

Identity Protection's risk-based policies (user risk policy and sign-in risk policy) and its three investigation reports (risky users, risky sign-ins, risk detections) are Entra ID P2 features. This means every user you include in a risk policy must be licensed for P2 — either directly, through Microsoft 365 E5, or through the Entra ID P2 add-on to a P1-based SKU like Microsoft 365 E3. Microsoft 365 E3 alone includes Entra ID P1, which is not sufficient. This licensing fact appears directly on MS-102.

Security Defaults vs Conditional Access

A core planning decision is which enforcement model you will use, because the two are mutually exclusive :

Security Defaults — a free, tenant-wide baseline that requires MFA registration for all users, blocks legacy authentication, and protects privileged operations. It is all-or-nothing and cannot be scoped to groups.

Conditional Access — licensed policies (Entra ID P1 minimum) that let you scope MFA, device compliance, and other controls to specific users, apps, and conditions.

If you plan to use Conditional Access — and you will, because Identity Protection risk-based policies are delivered as Conditional Access policies — you must turn Security Defaults off . Leaving Security Defaults on while trying to enforce Conditional Access is a common configuration error; the Entra admin center blocks creating Conditional Access policies while Security Defaults is enabled.

Risk Levels and Thresholds

Identity Protection classifies risk as Low , Medium , or High . When you plan a risk policy you choose which threshold triggers the policy:

  • High — most conservative on user friction; fewest users interrupted
  • Medium — balances detection and friction
  • Low — most aggressive; interrupts the most sign-ins

Microsoft's documented starting point is not the same threshold for both policies : set the user risk policy to High and the sign-in risk policy to Medium and above . The asymmetry is deliberate — a high user risk implies the credential itself is likely compromised and warrants the friction of a forced password reset, whereas sign-in risk is evaluated per authentication and an MFA challenge is cheap enough to justify firing at medium. Use Report-only mode (a Conditional Access capability) to assess impact before enforcing. The threshold is ultimately a business decision: too low and helpdesk volume rises; too high and real compromise slips through.

Integration with Conditional Access

Identity Protection is not a standalone enforcement engine. User risk and sign-in risk are exposed as conditions in Conditional Access. When you create a Conditional Access policy, under Conditions you can add User risk and Sign-in risk and select the levels that trigger the policy. The policy then grants or blocks access based on those risk levels — for example, "If sign-in risk is High or Medium, require MFA; if High, block."

This is why the planning phase must settle the Conditional Access vs Security Defaults question first: you cannot consume risk as a condition if Security Defaults is still on.

Planning Checklist

Confirm Entra ID P2 licensing for every user who will be in scope of a risk policy.

Decide whether to enforce user risk policy, sign-in risk policy, or both, and at which threshold — Microsoft's recommended starting point is user risk = High and sign-in risk = Medium and above .

Decide the remediation path — self-remediation via SSPR for user risk, MFA challenge for sign-in risk — and confirm SSPR and MFA registration are in place.

Plan to disable Security Defaults before enabling Conditional Access-based risk policies.

Identify break-glass / emergency access accounts and exclude them from every risk policy so a tenant-wide risk event does not lock out all admins.

Plan to run new policies in Report-only first, then flip to On after reviewing the impact.