Study guide

11.3 Defender Playbook for Protection, Detection, and Posture

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

11.3 Defender Playbook for Protection, Detection, and Posture

Key Takeaways Explain This Topic AI

Microsoft Defender is a product family, so the workload named in the scenario determines the specific Defender service.

Defender for Cloud protects cloud resources through posture management (secure score) and workload protection; Defender for Cloud Apps is a CASB for SaaS app discovery and control.

Defender for Identity detects attacks against on-premises Active Directory; Defender for Endpoint protects devices; Defender for Office 365 protects email and collaboration.

Microsoft Defender XDR (formerly Microsoft 365 Defender) correlates signals across Defender services in the unified Microsoft Defender portal.

Last updated: October 2026

Match Defender to the Protected Workload

Microsoft Defender is not one capability in SC-900. It is a security product family whose services protect different workloads and feed broader detection and response. When a question offers Defender answer choices, pause on the noun being protected. Is it a cloud resource, an endpoint device, an email message, a SaaS application, an on-premises identity system, a vulnerability exposure, or a threat-intelligence need? Naming the workload almost always selects the service.

The single biggest trap is Microsoft Defender for Cloud versus Microsoft Defender for Cloud Apps . Defender for Cloud is cloud security posture management (CSPM) plus cloud workload protection: recommendations, security standards, regulatory compliance views, secure score, and multicloud resource protection. It is the rebrand of Azure Security Center and Azure Defender . Defender for Cloud Apps is a cloud access security broker (CASB) for SaaS app discovery, app risk scoring, and session control; it is the rebrand of Microsoft Cloud App Security (MCAS) . "

Product or capability Scenario clues Frequently confused with

Microsoft Defender for Cloud Cloud resources, VMs, posture, standards, recommendations, secure score, workload protection Defender for Cloud Apps

Microsoft Defender for Endpoint Endpoint devices, device threats, on-device vulnerability exposure Network security groups

Microsoft Defender for Office 365 Email and collaboration threats, phishing, malicious attachments and links Purview retention labels

Microsoft Defender for Cloud Apps SaaS app discovery, app control, shadow IT, CASB Defender for Cloud

Microsoft Defender for Identity On-premises Active Directory signals, lateral movement, identity attacks Entra ID Protection / access reviews

Microsoft Defender Vulnerability Management Exposure, weaknesses, vulnerability prioritization Compliance Manager score

Microsoft Threat Intelligence Threat-actor context, indicators, intelligence enrichment Microsoft Priva

XDR Means Correlated Detection and Response

Above the individual workload services sits the correlation layer:

Microsoft Defender XDR is the current name for extended detection and response across Microsoft Defender services. It was formerly called Microsoft 365 Defender .

The Microsoft Defender portal is the unified console where XDR stitches endpoint, email, identity, and cloud-app signals into combined incidents.

A single Defender workload product is still the answer when the scenario narrows to one protected workload.

Microsoft Sentinel is a separate SIEM/SOAR product even though Sentinel's experience is converging into the Defender portal; XDR correlates Microsoft-native signals, while Sentinel ingests data from any source.

Defender for Cloud earns extra attention because it appears in both product-selection and cloud-posture review questions. If a scenario asks for recommendations, security policies, regulatory compliance posture, secure score , or cloud workload protection, Defender for Cloud is the strong candidate. If the scenario asks about Azure Firewall , Web Application Firewall , network security groups (NSGs) , Azure Bastion , or Azure DDoS Protection , those are Azure infrastructure controls rather than Defender services and are usually distractors.

Track the Workload, Avoid the Swap

Defender for Office 365 and Defender for Endpoint are easy to separate if you track the workload. Email, collaboration, phishing, and malicious-attachment scenarios point to Office 365 protection. Device compromise, endpoint investigation, and device-vulnerability language point to Endpoint . On-premises Active Directory attack detection (such as lateral movement or pass-the-hash) points to Defender for Identity — and note that this is on-premises AD signal analysis, distinct from Entra ID Protection, which scores cloud identity risk. SaaS app discovery and shadow-IT control point to Cloud Apps .

The exam may combine products in a realistic story. Defender for Endpoint can raise endpoint alerts, Defender XDR can correlate those alerts with email and identity signals into one incident, and Sentinel can ingest the data for SIEM analytics and SOAR playbooks. In a single-best-answer question, choose the product that owns the requested action . Detecting a threat on a device is not the same request as correlating multi-workload Microsoft signals, which is not the same request as automating an incident-response playbook across every source. Name the action, then pick the layer.

Posture Versus Protection, and Azure Infrastructure Distractors

Defender for Cloud splits into two ideas the exam loves to test side by side. Cloud security posture management (CSPM) is the preventive, always-on side: it continuously assesses configuration against security standards, raises recommendations, and rolls them into a secure score so teams can prioritize remediation. Cloud workload protection (CWP) , delivered through the Defender plans (for example Defender for Servers, Defender for Storage, Defender for SQL, and Defender for Containers), is the detective, threat-focused side that generates security alerts for active threats against those resources.

A prompt about "improving our security score" or "seeing recommendations against a standard" is CSPM; a prompt about "alerting on an attack against a SQL database or storage account" is CWP. Both live inside Defender for Cloud.

  • Need in the scenario Defender for Cloud side Signal phrase
  • See and fix misconfigurations, raise score CSPM (posture) Recommendations, standards, secure score
  • Detect active attacks on a workload CWP (Defender plans) Alert on threat to VM, SQL, storage, container
  • Open VM ports only on request Just-in-time VM access RDP/SSH, management ports
  • View regulatory compliance status Regulatory compliance dashboard PCI, ISO, CIS benchmark posture

The Azure infrastructure controls are the second big distractor set, and they are not Defender products. Azure Firewall is a managed, stateful network firewall. A network security group (NSG) filters traffic to and from Azure resources at the subnet or NIC level. Azure DDoS Protection defends against volumetric network attacks. Azure Bastion provides secure RDP/SSH connectivity without exposing public IPs. Web Application Firewall (WAF) , part of Application Gateway or Front Door, protects web apps from common exploits like SQL injection. These are defense-in-depth network and perimeter controls.

When a scenario describes a network control rather than posture assessment, workload threat detection, or identity, the answer is one of these Azure services — and a Defender option in the list is the trap. Knowing this clean split between Defender services (posture and threat protection) and Azure infrastructure security (network and perimeter) resolves a meaningful slice of the security-solutions domain, which carries roughly 25 to 30 percent of the exam.