Study guide
6.6 Cloud Workload Protection and Defender Plans
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
6.6 Cloud Workload Protection and Defender Plans
Key Takeaways Explain This Topic AI
Cloud Workload Protection Platform (CWPP) delivers threat detection and advanced defenses for protected cloud workloads, generating security alerts.
Defender plans are enabled per resource type: Servers, Storage, Databases, Containers, App Service, Key Vault, Resource Manager, DNS, APIs, and AI Services.
Defender for Servers integrates Microsoft Defender for Endpoint; Defender for Storage adds malware scanning and sensitive-data threat detection.
CWPP is protection-focused while CSPM is posture-focused; Defender for Cloud includes both, and alerts can be exported to Microsoft Sentinel.
Last updated: June 2026
CWPP and the Defender Plans
Cloud Workload Protection Platform (CWPP) is the workload-protection side of Defender for Cloud. Where CSPM asks whether resources are configured securely, CWPP asks whether workloads are protected against threats and generates security alerts for protected resources. Microsoft describes CWPP as providing workload-specific protections for workloads running on Azure, on-premises, and other clouds, with alerts that immediately indicate the nature and severity of a threat.
Protection is turned on by enabling Defender plans at the subscription (or connector) level — each plan targets a specific resource type. The current Defender plans are:
Defender plan What it protects
Defender for Servers Windows/Linux VMs on Azure, AWS, GCP, and on-premises; integrates Microsoft Defender for Endpoint, vulnerability assessment, just-in-time access, and file integrity monitoring
Defender for Storage Azure Blob, Files, and Data Lake; adds malware scanning and sensitive-data threat detection
Defender for Databases Azure SQL, SQL on machines, open-source relational databases, and Azure Cosmos DB
Defender for Containers Kubernetes hardening, image/registry vulnerability assessment, and run-time protection of nodes and clusters
- Defender for App Service Attacks targeting Azure App Service web apps and APIs
- Defender for Key Vault Unusual or harmful attempts to access or exploit Key Vault
- Defender for Resource Manager Suspicious resource-management (control-plane) operations
- Defender for DNS Anomalous DNS activity (for new subscriptions, now bundled into Defender for Servers Plan 2)
- Defender for APIs Visibility into and threat detection for business-critical APIs
- Defender for AI Services Threats to generative-AI applications, in real time
For SC-900 you should recognize that workload protection is plan-based and per-resource-type , and be able to map a workload (a VM, a database, a container cluster, a key vault) to the plan that protects it. You do not need to memorize every feature inside each plan.
Alerts, Incidents, and the Workload Dashboard
When Defender for Cloud detects a threat against a protected resource, it raises a security alert with details, a severity level, and suggested remediation; related alerts are correlated into security incidents . The workload protections dashboard gives a unified view of coverage (which eligible resources are protected), active alerts, advanced-protection status, and insights. Alerts and incidents can be exported to SIEM, SOAR, and ITSM systems — most importantly to Microsoft Sentinel — which is how posture and detection data reach the SOC.
A couple of details worth knowing: Defender for Servers comes in Plan 1 and Plan 2 (Plan 2 adds capabilities such as the bundled DNS alerts, just-in-time VM access, and file integrity monitoring). Defender for Databases is an umbrella over Azure SQL, SQL on machines, open-source relational DBs, and Cosmos DB. These nuances reinforce that CWPP is granular and resource-aware.
CWPP vs CSPM, Sentinel, and Infra Controls
CWPP and CSPM appear together because both live in Defender for Cloud, but they answer different questions:
CSPM → posture, hardening recommendations, secure score, compliance (pre-breach).
CWPP → workload threat detection, security alerts, Defender plans (active / post-breach).
A single resource can simultaneously have a CSPM recommendation (a misconfiguration to fix) and a CWPP alert (suspicious activity right now) — different views, not competing products.
Do not confuse Defender for Cloud CWPP with Microsoft Sentinel . Sentinel is the SIEM/SOAR that ingests and correlates security data across many sources (including Defender for Cloud alerts) and automates response with playbooks. Defender for Cloud generates the cloud workload alerts; Sentinel can centralize them. Likewise, do not confuse it with infrastructure controls — DDoS Protection, Azure Firewall, WAF, NSGs, Bastion, and Key Vault each address a specific network, admin, or secret need, while Defender plans add a detection and protection layer over the resources themselves.
CWPP = workload threat detection via per-resource Defender plans.
Plans cover Servers, Storage, Databases, Containers, App Service, Key Vault, Resource Manager, DNS, APIs, and AI.
Alerts and incidents can be exported to Microsoft Sentinel.
CSPM and CWPP are complementary halves of Defender for Cloud.
Mapping Workloads to Plans (Exam Drill)
The single most useful skill for CWPP questions is mapping a described workload to the right plan. Practice the mapping until it is automatic:
If the scenario protects... Enable...
- Windows/Linux VMs (any cloud or on-prem) Defender for Servers
- Azure Blob, Files, Data Lake (incl. malware scanning) Defender for Storage
- Azure SQL, SQL on machines, open-source DBs, Cosmos DB Defender for Databases
- Kubernetes clusters and container images Defender for Containers
- Azure App Service web apps and their APIs Defender for App Service
- Azure Key Vault access/exploit attempts Defender for Key Vault
- Suspicious control-plane (management) operations Defender for Resource Manager
- Anomalous DNS activity Defender for DNS (now bundled into Servers Plan 2 for new subs)
- Business-critical published APIs Defender for APIs
- Generative-AI applications Defender for AI Services
Notice that several plans protect things people forget are attack surfaces — the management plane (Resource Manager), DNS , key vaults , and APIs . The exam likes these because they test whether you understand that CWPP is granular and resource-aware rather than a single on/off switch.
Alerts, Severity, and the Response Path
When a Defender plan detects malicious activity, it raises a security alert carrying the threat description, a severity (informational, low, medium, high), the affected resource, and remediation guidance . Alerts about a single attack are correlated into a security incident so analysts see the whole campaign. From there alerts and incidents can be exported to a SIEM, SOAR, or ITSM system — in a Microsoft shop, Microsoft Sentinel , where playbooks automate containment.
This export relationship is the cleanest way to remember how Defender for Cloud (detection at the cloud-resource layer) and Sentinel (centralized correlation and automation) divide the work.
Final Boundaries to Keep Straight
Two last distinctions close out the chapter. First, CWPP is not CSPM : a resource can carry a CSPM recommendation (fix a misconfiguration) and a CWPP alert (respond to an active threat) at the same time — complementary views inside one product. Second, Defender for Cloud is not an infrastructure control : DDoS Protection, Azure Firewall, Web Application Firewall, NSGs, Bastion, and Key Vault each solve a narrow network, administrative, or secret need, whereas Defender plans add a detection and protection layer over the resources themselves.
When a prompt centers on protected cloud workloads, security alerts, and per-resource plans , the answer is Defender for Cloud cloud workload protection.