Study guide
4.6 Microsoft Entra ID Protection and Risk
Azure SC-900 Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Orientation: SC-900 Audience, Format, Scoring, Retakes, and Study Map
1.1 Credential Purpose and Audience 1.2 Exam Duration, Seat Duration, and Experience 1.3 Scoring, Scaled Score, and Pass-Rate Myths 1.4 Retake Policy and Certification Lifecycle 1.5 Scheduling, Price, and Delivery Options 1.6 Skills Measured and Study Map
2 Security, Compliance, and Identity Concepts: Zero Trust, Shared Responsibility, and GRC
2.1 Shared Responsibility Model 2.2 Defense in Depth and the CIA Triad 2.3 Zero Trust Model 2.4 Encryption, Hashing, and Data States 2.5 Governance, Risk, and Compliance 2.6 Identity Perimeter, Authentication, Authorization, and Federation
3 Microsoft Entra ID: Identities, Hybrid Identity, and Authentication
3.1 Microsoft Entra ID Foundations 3.2 Identity Types and Directory Objects 3.3 Hybrid Identity and Entra Connect Concepts 3.4 Authentication Methods and Sign-in Assurance 3.5 Multifactor Authentication 3.6 Password Protection, Self-Service Password Reset, and External Identities
4 Microsoft Entra Access Management, Governance, PIM, and Identity Protection
4.1 Conditional Access Purpose 4.2 Signals and Controls 4.3 Microsoft Entra Roles and Role-Based Access Control 4.4 Identity Governance, Entitlement Management, and Lifecycle Governance 4.5 Access Reviews and Privileged Identity Management 4.6 Microsoft Entra ID Protection and Risk
5 Azure Infrastructure Security: DDoS, Firewall, WAF, NSGs, Bastion, and Key Vault
5.1 Choose the Right Infrastructure Security Control 5.2 Azure DDoS Protection for Availability 5.3 Azure Firewall for Centralized Network Policy 5.4 Web Application Firewall for HTTP Workloads 5.5 Virtual Networks, Subnets, and Network Security Groups 5.6 Bastion and Key Vault for Administration and Secrets
6 Defender for Cloud: CSPM, Cloud Workload Protection, and Secure Score
6.1 Defender for Cloud Purpose and Exam Role 6.2 CSPM, Foundational Posture, and Defender CSPM 6.3 Policies, Standards, and Security Recommendations 6.4 Secure Score and Remediation Priority 6.5 Regulatory Compliance and Multicloud Posture 6.6 Cloud Workload Protection and Defender Plans
7 Microsoft Sentinel: SIEM, SOAR, Analytics, Hunting, Workbooks, and Playbooks
7.1 Sentinel as SIEM and SOAR 7.2 Data Connectors and Security Signals 7.3 Analytics Rules, Incidents, and Detection 7.4 Workbooks for Visual Review 7.5 Hunting, KQL Awareness, and Notebooks 7.6 Automation Rules and Logic Apps Playbooks
8 Microsoft Defender XDR: Office, Endpoint, Cloud Apps, Identity, Vulnerability, and Threat Intelligence
8.1 Defender XDR Suite and Microsoft Defender Portal 8.2 Defender for Office 365 8.3 Defender for Endpoint 8.4 Defender for Cloud Apps 8.5 Defender for Identity 8.6 Vulnerability Management and Threat Intelligence
9 Microsoft Purview, Service Trust, Privacy, Compliance Manager, and Compliance Score
9.1 Service Trust Portal and Assurance Resources 9.2 Privacy Principles and Microsoft Priva 9.3 Microsoft Purview Portal 9.4 Compliance Manager Assessments 9.5 Compliance Score and Improvement Actions 9.6 Scenario Selection for Trust, Privacy, and Compliance Manager
10 Microsoft Purview Data Classification, Labels, DLP, Retention, eDiscovery, and Audit
10.1 Data Classification Foundations 10.2 Content Explorer and Activity Explorer 10.3 Sensitivity Labels and Label Policies 10.4 Data Loss Prevention 10.5 Retention, Records Management, and Label Policies 10.6 eDiscovery, Audit, and Insider Risk Management
11 SC-900 Product Selection Playbooks and Common Microsoft Rebrand Traps
11.1 Read the Scenario Before Picking a Product 11.2 Entra Playbook for Identity, Access, and Governance 11.3 Defender Playbook for Protection, Detection, and Posture 11.4 Sentinel Playbook for SIEM, SOAR, and Hunting 11.5 Purview Playbook for Compliance, Data, and Risk 11.6 Renamed Products and Similar-Name Traps 11.7 Microsoft Learn Practice Assessment Review Loop
12 Final SC-900 Review, Timed Practice, Exam Day, and Next Certification Path
12.1 Domain-Weighted Final Review Plan 12.2 Timed Practice and Pacing 12.3 Exam Sandbox and Question Experience 12.4 Exam-Day Logistics and Boundaries 12.5 Scoring, Retakes, and After-Exam Decisions 12.6 Final Memory Check and Scenario Drills 12.7 Next Certification Path After SC-900
4.6 Microsoft Entra ID Protection and Risk
Key Takeaways Explain This Topic AI
Microsoft Entra ID Protection detects, investigates, and remediates identity-based risk using signals like leaked credentials, impossible travel, anonymous IP, and unfamiliar sign-in properties.
Sign-in risk is the probability that a given authentication is not the legitimate owner; user risk is the probability the account itself is compromised.
ID Protection feeds risk levels (low/medium/high) into Conditional Access, enabling risk-based policies such as require MFA on risky sign-in or force secure password change on risky user.
ID Protection is a Microsoft Entra ID P2 capability and is distinct from Defender for Identity, which protects on-premises Active Directory.
Users can self-remediate risk via MFA or self-service password reset, automatically lowering their risk level.
Last updated: June 2026
What ID Protection does
Microsoft Entra ID Protection automates the detection, investigation, and remediation of identity-based risk. Microsoft processes trillions of signals daily and uses machine learning to flag suspicious activity. ID Protection requires Microsoft Entra ID P2 — a key SC-900 licensing fact, since Conditional Access alone is only P1.
ID Protection surfaces its findings in three reports:
Risky users — accounts that may be compromised (user risk).
Risky sign-ins — individual authentications that look suspicious (sign-in risk).
Risk detections — the underlying detected events that feed the two risk scores.
It does not replace authentication, Conditional Access, or governance — it adds risk context to them. The data it produces can also be exported to Microsoft Sentinel or queried via the Microsoft Graph API for SOC investigation.
Sign-in risk vs. user risk
ID Protection calculates two risk types, and the exam expects you to tell them apart:
Risk type Question it answers
Sign-in risk Is this particular authentication request really from the legitimate owner?
User risk Has the account itself probably been compromised?
Each is scored low / medium / high . User risk accumulates from all active detections on the account — most notably leaked credentials (the username/password appeared in a breach dump). Sign-in risk is evaluated per logon from real-time and offline detections.
Common risk detections SC-900 may name include: leaked credentials , sign-in from an anonymous IP address (e.g., Tor), impossible travel / atypical travel , unfamiliar sign-in properties , malware-linked IP address , password spray , and anomalous token . You do not need every detection memorized, but recognize them as identity-risk signals.
Risk-based Conditional Access
The power of ID Protection comes from feeding its risk levels into Conditional Access . Two special conditions — sign-in risk and user risk — let an organization respond automatically:
Sign-in risk policy — if sign-in risk is medium or high, then require MFA (or block). This challenges the suspicious logon in real time.
User risk policy — if user risk is high, then require a secure password change (self-service password reset), which both verifies the user and resets the possibly-leaked credential.
Because these are risk conditions, they require P2 . Microsoft's recommended pattern is risk-based policies that allow self-remediation : a user who passes MFA clears their sign-in risk, and a user who completes a secure password change clears their user risk — lowering the risk level automatically without a help-desk call.
Risky sign-in → require MFA.
Risky user → require secure password change.
Self-remediation → risk level drops automatically.
Product boundary and the Entra decision map
The name resembles other products, so keep the boundary sharp. Microsoft Entra ID Protection handles cloud identity risk (Entra accounts). Microsoft Defender for Identity is a Defender XDR product that protects on-premises Active Directory by analyzing domain-controller signals. Microsoft Sentinel is the SIEM/SOAR. Microsoft Purview is compliance. A question about risky sign-ins to Entra is ID Protection; a question about lateral movement against an on-prem domain controller is Defender for Identity.
Use this map for the whole Entra objective:
- Problem Capability
- Store/manage identities Microsoft Entra ID
- Prove identity at sign-in Authentication / MFA
- Decide access by context Conditional Access
- Grant permissions Entra roles / Azure RBAC
- Keep access appropriate over time Governance, access reviews, PIM
- Detect and remediate identity risk Microsoft Entra ID Protection
If wording shifts to incidents, hunting, and automation across many sources, the scenario has moved into Microsoft Sentinel.
Detection, investigation, and remediation in detail
ID Protection's value is the full loop of detect, investigate, remediate . On detection , Microsoft classifies signals as real-time (evaluated during sign-in, like impossible travel or anonymous IP) or offline (calculated after the fact, like leaked credentials surfaced from breach intelligence). Each detection raises the sign-in or user risk level.
On investigation , security teams use the risky users, risky sign-ins, and risk detections reports to see the affected accounts, the detection types, and the timeline; they can confirm an account as compromised, confirm a sign-in as safe (suppressing the risk), or dismiss the risk. On remediation , the goal is to return the account to a known-good state.
Remediation can be automatic or manual . Automatic remediation is the recommended path: a risk-based Conditional Access policy forces the user to self-remediate — completing MFA clears sign-in risk, and a secure password change via self-service password reset clears user risk because it both proves identity and replaces a possibly-leaked password. Manual remediation is when an administrator intervenes: reset the password , require the user to re-register MFA , block the user, or dismiss/confirm the risk after investigation.
The exam framing is that self-remediation scales (no help-desk ticket) while admins handle the cases that automation cannot.
Keep three precision facts ready. First, leaked credentials is the classic driver of user risk and is an offline detection — it may appear after the breach data is processed, not at sign-in. Second, ID Protection requires P2 ; without it you can see only a limited risk view. Third, ID Protection does not block by itself — it produces risk signals; the actual enforcement (challenge, block, password change) happens through Conditional Access . Confusing "detects risk" with "enforces access" is a common trap.
Detect: real-time and offline detections raise risk levels.
Investigate: confirm compromised, confirm safe, or dismiss.
Remediate: self-service MFA / password change, or admin action.
Enforcement happens in Conditional Access, not ID Protection itself.