Study guide

8.5 Defender for Identity

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.5 Defender for Identity

Key Takeaways Explain This Topic AI

Defender for Identity (formerly Azure Advanced Threat Protection / Azure ATP) is a cloud service that uses on-premises Active Directory signals to detect identity threats.

Sensors installed on domain controllers and AD FS/AD CS servers monitor traffic and authentication, sending signals to the cloud.

It detects reconnaissance, compromised credentials, lateral movement, and domain dominance across the identity kill chain.

It protects on-prem AD identities — distinct from Microsoft Entra ID Protection, which protects cloud (Entra) identities.

It is a security/Defender service, not an access-management or governance feature.

Last updated: June 2026

Protecting On-Premises Active Directory Identities

Microsoft Defender for Identity (formerly Azure Advanced Threat Protection / Azure ATP ) is a cloud-based security solution that uses signals from your on-premises Active Directory to identify, detect, and investigate advanced identity threats and malicious insider actions. The product runs in the cloud, but its source of truth is the on-prem AD environment, where most credential-theft and lateral-movement attacks play out. When SC-900 describes detecting attacks against on-premises Active Directory — Pass-the-Hash, Pass-the-Ticket, reconnaissance, lateral movement, or domain dominance — the answer is Defender for Identity.

How It Works — Sensors

Defender for Identity collects telemetry through lightweight sensors installed directly on domain controllers (and optionally AD FS and AD CS servers). The sensors monitor domain-controller network traffic, Windows events, and authentication activity, then send parsed signals to the Defender for Identity cloud service for analysis. No separate port-mirroring appliance is required (the modern sensor sits on the DC itself).

The cloud service applies User and Entity Behavioral Analytics (UEBA) , threat intelligence, and known attack patterns to surface alerts, which flow into the Microsoft Defender portal as part of unified Defender XDR incidents.

What It Detects — the Identity Kill Chain

Defender for Identity maps detections to the stages of an identity-based attack:

  • Attack phase Example detections
  • Reconnaissance Account/group enumeration, SAM-R queries, DNS reconnaissance
  • Compromised credentials Brute force, suspicious authentications, abnormal sign-ins
  • Lateral movement Pass-the-Hash, Pass-the-Ticket, overpass-the-hash, lateral movement paths
  • Domain dominance DCSync, DCShadow, Golden Ticket, suspicious service creation

It also computes lateral movement paths showing how an attacker could pivot from a non-sensitive account to a privileged one, helping defenders close those paths proactively.

The "Identity" Word Trap

"Identity" appears all over SC-900, so the word alone is not enough. Separate Defender for Identity from the Microsoft Entra identity domain:

  • Concern Product Domain
  • Detect threats against on-premises AD Defender for Identity Security (Defender)
  • Detect risky cloud (Entra) sign-ins/users Microsoft Entra ID Protection Identity
  • Enforce Conditional Access / MFA Microsoft Entra Conditional Access Identity
  • Just-in-time privileged role activation Microsoft Entra PIM Identity
  • Access reviews / lifecycle governance Microsoft Entra ID Governance Identity

The sharpest distinction is Defender for Identity (on-prem AD) vs. Entra ID Protection (cloud Entra identities) — both are about identity threat detection , but on different surfaces. If the prompt asks to govern, review, or activate access, it is Entra governance/PIM, not Defender for Identity. If it asks to detect an attacker abusing on-prem AD , it is Defender for Identity.

Also keep it apart from the other Defender workloads: it is not Defender for Endpoint (devices), not Defender for Office 365 (email), and not Defender for Cloud Apps (SaaS apps).

Quick cues

"Detect Pass-the-Hash / lateral movement in on-prem Active Directory" → Defender for Identity .

"Risky cloud sign-in detected for an Entra user" → Entra ID Protection .

"Review who has access / activate an admin role just in time" → Entra ID Governance / PIM .

Why On-Premises AD Needs Its Own Defender

Most organizations still run on-premises Active Directory (often synchronized to the cloud via hybrid identity), and attackers love it because a single compromised account can be escalated to domain dominance — effective control of the whole directory. Traditional perimeter and antivirus tools are blind to the identity-layer techniques attackers use inside AD: enumerating accounts, replaying stolen tickets, abusing replication. Defender for Identity exists to watch exactly those signals, applying behavioral analytics to authentication and directory traffic that a domain controller sees but rarely scrutinizes.

Because it is cloud-managed , Defender for Identity needs no on-prem analytics infrastructure — the sensors on the domain controllers do lightweight collection and send signals up to the service, where machine learning baselines normal behavior per user and entity. Alerts arrive pre-correlated into the Microsoft Defender portal and become part of Defender XDR incidents, so an on-prem AD attack appears alongside the related endpoint, email, and SaaS-app activity in one story.

Defender for Identity vs. Entra ID Protection — the Sharpest Distinction

Both detect identity threats , but on different identity stores. The exam loves this pair:

  • Defender for Identity Microsoft Entra ID Protection
  • Identity store On-premises Active Directory Cloud Microsoft Entra ID
  • Detects Lateral movement, recon, domain dominance Risky sign-ins, leaked credentials, risky users
  • Domain on SC-900 Security (Defender) Identity (Entra)
  • Data source DC/AD FS sensors Cloud sign-in and user-risk signals

If the scenario mentions domain controllers, Kerberos/NTLM attacks, Pass-the-Hash, or on-prem AD , choose Defender for Identity . If it mentions cloud sign-in risk, leaked credentials in the cloud, or risk-based Conditional Access , choose Microsoft Entra ID Protection . And if it mentions managing access — reviews, role activation, entitlement management — that is Entra ID Governance / PIM , not a threat-detection product at all.

The single most reliable trigger word for Defender for Identity is on-premises Active Directory : whenever a scenario names the on-prem directory, domain controllers, or classic AD attack techniques, Defender for Identity is the intended answer, while every cloud-identity term routes to the Microsoft Entra family instead.