Study guide
8.1 Defender XDR Suite and Microsoft Defender Portal
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
8.1 Defender XDR Suite and Microsoft Defender Portal
Key Takeaways Explain This Topic AI
Microsoft Defender XDR was renamed from Microsoft 365 Defender; XDR stands for extended detection and response.
Defender XDR unifies signals from Endpoint, Office 365, Identity, and Cloud Apps into one correlated view in the Microsoft Defender portal (security.microsoft.com).
An incident is a container of related alerts, entities, and evidence stitched together by automatic correlation aligned to MITRE ATT&CK.
Defender XDR is the protection-and-incident suite; Microsoft Sentinel is the SIEM/SOAR that ingests data tenant-wide, including non-Microsoft sources.
Automatic attack disruption can contain a compromised user or device mid-attack using high-fidelity cross-signal correlation.
Last updated: June 2026
What Microsoft Defender XDR Is
Microsoft Defender XDR is Microsoft's extended detection and response (XDR) suite. It was renamed from Microsoft 365 Defender (which was itself previously Microsoft Threat Protection), and the rename is heavily tested on SC-900 — use Defender XDR as the current umbrella name. XDR means the platform detects and responds to threats across multiple domains rather than one. Defender XDR coordinates four pre-breach and post-breach protection services into a single experience:
- Component (current name) Protects / monitors Former name
- Defender for Office 365 Email and collaboration (Exchange, Teams, SharePoint, OneDrive) Office 365 ATP
- Defender for Endpoint Endpoint devices (Windows, macOS, Linux, mobile) Microsoft Defender ATP
- Defender for Identity On-premises Active Directory identity signals Azure ATP
- Defender for Cloud Apps SaaS apps / cloud-app usage (CASB) Microsoft Cloud App Security (MCAS)
The core idea Defender XDR adds on top of the individual products is correlation . Each service generates its own alerts, but Defender XDR automatically connects related alerts across services into a single incident so an analyst sees one attack story instead of dozens of disconnected signals.
The Unified Microsoft Defender Portal
All of this is operated from the Microsoft Defender portal at security.microsoft.com . The portal is the single pane of glass for the Defender family: incident and alert queues, advanced hunting (Kusto Query Language), the action center for remediation, threat analytics, secure score, and per-product settings. SC-900 expects you to know the portal is where you investigate Defender incidents — you do not bounce between separate consoles per product.
Key portal concepts:
Alert — a single detection of suspicious activity from one Defender service.
Incident — a collection of correlated alerts, plus the entities (users, devices, mailboxes, files, IPs) and evidence involved, representing one end-to-end attack. Correlation maps to the MITRE ATT&CK framework so the incident reads as a kill-chain story.
Advanced hunting — proactively query raw signal data across all Defender services with KQL.
Automatic attack disruption — using high-confidence correlated signals, Defender XDR can automatically contain an in-progress attack (for example, disable a compromised account or isolate a device) before an analyst manually intervenes.
Defender XDR vs. Microsoft Sentinel (the key trap)
The most-tested distinction in this domain is Defender XDR vs. Microsoft Sentinel :
Defender XDR is an XDR suite — it protects and correlates across the four Microsoft Defender workloads and is largely turnkey for Microsoft 365/Azure data.
Microsoft Sentinel is a cloud-native SIEM and SOAR — it ingests logs from any source (Microsoft and non-Microsoft, on-prem, multicloud, firewalls, third-party apps), scales for long-term analytics, and automates response with playbooks.
The two integrate: Sentinel can pull Defender XDR incidents in, and Microsoft now offers a unified security operations experience in the Defender portal. But for product-matching: broad SIEM/SOAR, tenant-wide log ingestion, hunting across non-Microsoft data, playbooks = Sentinel ; Defender portal incidents correlated across Microsoft 365 workloads = Defender XDR .
A helpful framing: Defender XDR is the native protection and detection layer that already understands Microsoft 365 and Azure deeply and ships ready to use, while Sentinel is the aggregation and orchestration layer that brings everything — including signals far outside Microsoft's own products — into one analytics workspace for long-term retention, custom analytics rules, and automated response.
How a Cross-Domain Incident Forms
Understanding why XDR exists makes the product choice obvious on exam day. Consider a realistic intrusion. An attacker sends a phishing email; Defender for Office 365 detects the malicious link and raises an alert. A user clicks before the block fully propagates and runs a malicious payload; Defender for Endpoint raises a device alert about suspicious process behavior. The attacker harvests credentials and attempts lateral movement against a domain controller; Defender for Identity raises an identity alert. Finally the attacker abuses a sanctioned SaaS app to exfiltrate data; Defender for Cloud Apps raises an anomaly alert.
Without XDR, those are four disconnected alerts in four queues, and a tired analyst might never connect them. With Microsoft Defender XDR , the correlation engine recognizes the shared entities (the same user, the same device, related timestamps and IPs) and stitches the four alerts into one incident that tells the whole story end to end. The analyst opens a single item, sees the full attack chain mapped to MITRE ATT&CK tactics, and can take coordinated action. This is the essence of extended detection and response : detection that spans domains and a response that is coordinated rather than siloed.
Choosing the Right Level
The exam often gives you a broad scenario and asks for the suite, or a narrow scenario and asks for the specific service. Decide by the surface named:
Broad wording — "a single portal to investigate incidents that span email, devices, and identities" — points to Microsoft Defender XDR .
A specific protected workload points to the specific Defender service (Office 365, Endpoint, Identity, or Cloud Apps).
SIEM, SOAR, ingest any log source, hunt across all data, playbooks points to Microsoft Sentinel .
Compliance, labels, DLP, retention, eDiscovery points to Microsoft Purview .
Conditional Access, MFA, roles, PIM, Identity Protection points to Microsoft Entra .
Quick decision path
Defender portal or cross-service incident wording → Defender XDR.
Named workload (email, device, AD, SaaS app) → the matching Defender service.
SIEM/SOAR/any-source logs → Microsoft Sentinel.
By auto-correlating alerts, Defender XDR shrinks the analyst's queue from many noisy alerts to fewer high-fidelity incidents, and automatic attack disruption can contain the attack while it is still unfolding. That cross-domain stitching is the value proposition SC-900 wants you to associate with Microsoft Defender XDR.