L16. Defender XDR & the Unified Portal
Course outlineLesson 16 of 18
Microsoft Defender XDR unifies endpoint, identity, email, and cloud app protection into one portal. The AZ-500 tests the difference between XDR and SIEM, and which Defender product protects which surface.
Azure security background
AZ-500 retired on August 31, 2026. These concepts remain useful; for current exam preparation, continue with the SC-500 course.
XDR vs SIEM
| Dimension | SIEM (Sentinel) | XDR (Defender XDR) |
|---|---|---|
| Data source | Any log source | Microsoft security products |
| Detection | Built-in templates and custom KQL rules | Built-in correlations and custom detections |
| Response | Playbooks (Logic Apps) | Automated remediation built-in |
| Focus | Compliance, investigation | Endpoint plus identity plus email threat response |
Defender XDR Components
| Product | Protects |
|---|---|
| Defender for Endpoint (MDE) | Windows, macOS, Linux, Android, iOS devices |
| Defender for Identity (MDI) | AD DS, AD FS, AD CS and Microsoft Entra Connect infrastructure |
| Defender for Office 365 (MDO) | Exchange Online, SharePoint, Teams |
| Defender for Cloud Apps (MDCA) | SaaS apps, shadow IT, conditional access app control |
The Unified Security Portal (security.microsoft.com)
Microsoft Sentinel is generally available in the Microsoft Defender portal (security.microsoft.com), including without Defender XDR or an E5 license. After March 31, 2027, Sentinel in the Azure portal is unsupported and Sentinel is available only in the Defender portal. Plan the transition now. AZ-500 retired on August 31, 2026; use these lessons as Azure security background and the SC-500 course for current exam preparation.
Microsoft Defender for Identity (MDI)
MDI monitors on-premises Active Directory Domain Controllers for identity-based attacks:
- Pass-the-Hash, Pass-the-Ticket
- Kerberoasting, AS-REP Roasting
- Lateral movement via SMB
Deploy supported Defender for Identity sensors for the identity servers being monitored, including domain controllers and supported AD FS, AD CS and Microsoft Entra Connect servers. Verify version-specific prerequisites, event auditing and sensor health. Signals flow to Defender XDR for correlation. Exam tip: MDI detects on-premises AD attacks. Entra ID Protection detects cloud identity risks. For hybrid environments, you need both.
References
- Sentinel Defender portal transition
- Defender XDR Sentinel connector
- Defender for Identity sensor prerequisites
- Defender XDR custom detections
- AZ-500 official study guide
Continue Learning
- ✓Sentinel correlates broad telemetry with built-in and custom analytics; Defender XDR correlates integrated security signals and also supports custom detections
- ✓Sentinel and Defender XDR complement each other: Defender XDR data flows into Sentinel via connector
- ✓MDI detects on-premises AD attacks (Pass-the-Hash, Kerberoasting); Entra ID Protection covers cloud identity
- ✓MDI sensor deployment follows version-specific prerequisites for domain controllers and supported identity servers; verify auditing and sensor health
- ✓Unified portal (security.microsoft.com) now hosts both Defender XDR and Microsoft Sentinel
1. What is the primary distinction between SIEM and XDR in the Microsoft security stack?
2. Defender for Identity monitors which data source to detect lateral movement and credential attacks in hybrid environments?
3. In the Microsoft Defender XDR unified portal, what is an 'incident'?