Study guide
8.4 Defender for Cloud Apps
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.4 Defender for Cloud Apps
Key Takeaways Explain This Topic AI
Defender for Cloud Apps (formerly Microsoft Cloud App Security / MCAS) is Microsoft's Cloud Access Security Broker (CASB).
Its four CASB pillars are visibility (Shadow IT discovery), data security, threat protection (UEBA/anomaly detection), and compliance.
Cloud Discovery analyzes traffic logs to reveal unsanctioned 'Shadow IT' apps and rate their risk.
Do NOT confuse Defender for Cloud Apps (SaaS app usage/CASB) with Defender for Cloud (cloud resource posture and workload protection).
App connectors and Conditional Access App Control extend real-time session controls over sanctioned apps.
Last updated: June 2026
CASB and the Four Pillars
Microsoft Defender for Cloud Apps (formerly Microsoft Cloud App Security / MCAS ) is Microsoft's Cloud Access Security Broker (CASB) . A CASB sits between users and the cloud apps they use to give an organization visibility and control over SaaS application usage — both the apps IT sanctioned and the ones employees adopted on their own. This is one of the most important name-traps on SC-900: it is Cloud Apps (SaaS app usage), not Cloud (resources).
Defender for Cloud Apps is built on the four standard CASB pillars :
- Pillar What it delivers
- Visibility Discover all cloud apps in use, including unsanctioned Shadow IT ; assess each app's risk
Data security Find and protect sensitive data in SaaS apps (integrates with Purview information protection / DLP)
- Threat protection Detect compromised accounts, insider threats, and anomalies via UEBA and anomaly detection
- Compliance Assess apps against regulatory and internal governance requirements
- Shadow IT Discovery (Cloud Discovery)
The most distinctive Defender for Cloud Apps capability is Cloud Discovery / Shadow IT discovery . It analyzes traffic logs (from firewalls, proxies, or Defender for Endpoint) to reveal which cloud apps users are actually accessing — including apps IT never approved. Each discovered app gets a risk score drawn from a cloud app catalog of thousands of apps, so the organization can sanction, unsanction, or block apps. "An employee uploaded company data to an unapproved file-sharing site — how do we even know it's happening?" is a textbook Shadow IT / Defender for Cloud Apps scenario.
App Connectors and Session Control
Beyond discovery, Defender for Cloud Apps governs sanctioned apps using API app connectors (deep visibility into apps like Microsoft 365, Salesforce, Box, ServiceNow) and Conditional Access App Control — a reverse-proxy integration with Microsoft Entra Conditional Access that enforces real-time session controls (for example, block download of sensitive files to unmanaged devices, or monitor risky in-session actions).
The Cloud Apps vs. Cloud Trap
The near-identical names trip up candidates. Read the noun after "cloud" :
Product Protects Cue words
Defender for Cloud Apps SaaS app usage (CASB) Shadow IT, app discovery, sanction/unsanction apps, session control, UEBA on SaaS
Defender for Cloud Cloud resources & workloads Secure score, CSPM, recommendations, regulatory compliance dashboard, VM/container/SQL workload protection
If the scenario is about which cloud applications employees use and controlling that usage , choose Defender for Cloud Apps . If it is about the security posture of your Azure/AWS/GCP resources and protecting workloads , choose Defender for Cloud (covered in Chapter 6).
Also keep it separate from:
Defender for Office 365 — protects email/collaboration content, not general SaaS-app discovery.
Microsoft Purview — Purview classifies and governs data; Defender for Cloud Apps is a security service that can use Purview labels to protect SaaS data but is itself a CASB.
Quick cues
"Discover unsanctioned cloud apps from traffic logs" → Defender for Cloud Apps (Shadow IT) .
"Block downloads to unmanaged devices in a SaaS session in real time" → Conditional Access App Control in Defender for Cloud Apps.
"Improve the secure score / posture of cloud resources" → Defender for Cloud (not Cloud Apps).
How Defender for Cloud Apps Gains Visibility
Defender for Cloud Apps gets its visibility in three complementary ways, and recognizing them helps on scenario questions:
Cloud Discovery (log-based) — ingests traffic logs from firewalls, proxies, or the natively integrated Defender for Endpoint to map which cloud apps users touch, how much data flows, and how risky each app is. This is the Shadow IT engine.
App connectors (API-based) — connect via vendor APIs to sanctioned apps (Microsoft 365, Salesforce, ServiceNow, Box, Google Workspace, AWS, and more) for deep visibility into activities, files, and accounts, and to apply governance actions.
Conditional Access App Control (proxy-based) — integrates with Microsoft Entra Conditional Access as a reverse proxy to enforce real-time session controls , such as blocking downloads of sensitive files to unmanaged devices or requiring extra verification mid-session.
These map cleanly onto the four CASB pillars. Visibility comes from Cloud Discovery and connectors. Data security comes from connectors plus integration with Purview sensitive-information types and labels to find and protect data inside SaaS apps. Threat protection comes from UEBA and anomaly-detection policies that flag impossible-travel sign-ins, mass downloads, or unusual admin activity that suggest a compromised account or malicious insider. Compliance comes from assessing discovered apps against regulatory and internal standards.
Worked Selection Scenario
" Discovering unsanctioned apps from logs is Cloud Discovery / Shadow IT ; scoring and blocking risky apps is core CASB governance; and preventing sensitive downloads to unmanaged devices in real time is Conditional Access App Control — all delivered by Defender for Cloud Apps . The wrong-but-tempting answer is Defender for Cloud ; reread and you will see the scenario is about app usage , not resource posture .
A frequently tested distinction: Microsoft Defender for Cloud Apps is the Cloud Access Security Broker (CASB) that discovers and governs SaaS application use, whereas Microsoft Defender for Cloud protects the security posture of your Azure, AWS, and GCP infrastructure and workloads — the two sound alike but solve completely different problems.