Study guide

10.2 Implementing Entra 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.2 Implementing Entra Identity Protection

Key Takeaways Explain This Topic AI

Identity Protection exposes three policy types in the Entra admin center under Protection > Identity Protection: MFA registration policy, sign-in risk policy, and user risk policy

The three investigation reports are risky users, risky sign-ins, and risk detections; administrators can dismiss false positives or confirm risk to tune the ML models

User risk policy remediation is a secure password reset (via SSPR); sign-in risk policy remediation is an MFA challenge — the policy can also be configured to block access instead

Risk detections include impossible travel, anonymous IP, malicious IP, unfamiliar sign-in properties, leaked credentials, password spray, and token theft (preview)

Admins can manually dismiss risk on a user (confirm compromise vs confirm safe) when a detection is a known false positive

Last updated: August 2026

Quick Answer: In the Entra admin center, under Protection > Identity Protection , you configure three policies: the MFA registration policy (require users to register for MFA), the sign-in risk policy (require MFA or block based on sign-in risk level), and the user risk policy (require a secure password reset or block based on user risk level). You monitor through three reports — risky users , risky sign-ins , and risk detections — and you remediate through self-service password reset, MFA challenge, or manual admin dismissal.

The Three Policies

Identity Protection is implemented through three policy blades in the Entra admin center. Each is a Conditional Access policy under the hood but is surfaced with a simplified UI:

1. MFA Registration Policy

Requires users to register for MFA within a given number of days. It does not enforce MFA on sign-in — it only drives registration so that the other two policies can use MFA as a remediation. You scope it to users (typically all users except break-glass accounts) and set the registration window (default 14 days). Users see a banner at sign-in prompting them to register.

2. Sign-in Risk Policy

Triggers when a sign-in's risk level meets the threshold you set. The remediation options are:

  • Require MFA — let the user prove the sign-in is legitimate by completing an MFA challenge
  • Block access — deny the sign-in outright (use for High risk where MFA is not enough)

You choose the risk level threshold (Low/Medium/High) and the users in scope. A sign-in that passes MFA remediation is marked as risk-confirmed-safe; the user continues uninterrupted.

3. User Risk Policy

Triggers when a user's overall risk level meets the threshold. Because user risk implies the identity itself may be compromised, the remediation is stronger:

Require secure password reset — the user must perform a self-service password reset (SSPR), which requires SSPR to be configured and the user to be registered for it

Block access — deny sign-in until an admin investigates

A successful SSPR clears the user's risk so they can sign in normally afterward.

The Three Reports

Identity Protection gives you three investigation surfaces:

  • Report What it shows Action
  • Risky users Users with active user risk, ranked by risk level Remediate, dismiss risk, or block user
  • Risky sign-ins Sign-ins flagged with sign-in risk Confirm safe (dismiss) or confirm compromised

Risk detections Individual detections (impossible travel, leaked credentials, etc.) with timing and IP detail Investigate and link to a user

From Risky users you can choose Confirm user compromised (which blocks the user and requires admin reset) or Dismiss user risk (used when you have verified the activity was legitimate). Dismissing risk feeds back into Microsoft's models and tunes future detection for the tenant.

Risk Detections Identity Protection Surfaces

These are the conceptual detections you should recognize on the exam:

Impossible travel — sign-ins from geographically distant locations within a timeframe that real travel could not bridge

  • Anonymous IP — sign-in from an anonymizer, Tor, or VPN known to hide identity
  • Malicious IP — sign-in from an IP linked to known malware or botnet infrastructure

Unfamiliar sign-in properties — sign-in from a new location, device, or browser that does not match the user's baseline

  • Leaked credentials — Microsoft has evidence the user's credentials appear in a public breach dump
  • Password spray — many accounts attacked with a common password list; a successful spray raises user risk
  • Token theft (preview) — refresh or session tokens stolen and replayed from an attacker-controlled environment

Each detection contributes a probability weight to either user risk or sign-in risk. Leaked credentials and password spray most strongly raise user risk ; impossible travel and anonymous IP most strongly raise sign-in risk .

Remediation Paths

Remediation can be self-service or admin-driven:

Self-remediation (sign-in risk) — the user completes an MFA challenge at sign-in. On success the sign-in is allowed and the detection is marked safe.

Self-remediation (user risk) — the user performs SSPR, which requires SSPR to be enabled and the user registered for the required methods. On success, user risk is cleared.

Admin manual dismissal — when a detection is a confirmed false positive (for example, a legitimate new-office sign-in flagged as unfamiliar), an admin dismisses the risk from the risky users or risky sign-ins report. Dismissing helps Microsoft's models learn the tenant's normal patterns.

Admin confirmation of compromise — when compromise is real, the admin confirms the user compromised, which blocks the account and forces an admin-driven password reset.

Operational Workflow

Configure the MFA registration policy first so users are registered.

Configure the user risk policy at High and the sign-in risk policy at Medium and above , both in Report-only mode first.

Review the report-only results in the Conditional Access Insights and reporting workbook.

Flip the policies to On once impact is acceptable.

Monitor the risky users and risky sign-ins reports daily; tune thresholds based on noise.

Use the risk detections report to investigate patterns (for example, repeated impossible-travel from one country) and feed the findings back into named locations or policy exclusions.

Loading diagram... Identity Protection Risk Policy Flow