Study guide

6.5 Regulatory Compliance and Multicloud 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

6.5 Regulatory Compliance and Multicloud Posture

Key Takeaways Explain This Topic AI

The Defender for Cloud regulatory compliance dashboard maps continuous assessments to frameworks like ISO 27001, PCI DSS, and NIST.

The compliance dashboard is part of the paid Defender CSPM plan, although MCSB policy itself is free.

Controls that cannot be automatically assessed appear greyed out and require manual attestation.

Defender for Cloud connects AWS accounts and GCP projects agentlessly, extending posture and compliance views across Azure, AWS, and GCP.

Last updated: June 2026

The Regulatory Compliance Dashboard

Defender for Cloud includes a regulatory compliance dashboard built on its continuous assessment of cloud resources. Microsoft frames it as providing insight into compliance with the standards that matter to your organization. The key SC-900 phrase is compliance posture , not legal certification: Defender for Cloud helps you monitor and track controls, findings, and progress against assigned standards — it does not issue a certificate.

Because the same assessment engine feeds both security recommendations and compliance, a resource that fails an MCSB control can appear in recommendations and contribute to a framework's compliance view. The dashboard typically shows:

Compliance status for each assigned framework, with passing vs failing controls.

A compliance percentage / score per standard and visual progress over time.

Frameworks that require attention , and the ability to filter recommendations by framework.

Framework-specific recommendations and remediation progress.

  • Compliance term Meaning in Defender for Cloud
  • Assigned standard A benchmark or regulatory framework applied to a scope
  • Control A requirement or expected condition within a standard
  • Compliance posture Current assessment state against assigned standards
  • Framework-specific recommendation A remediation item tied to a compliance control
  • Greyed-out control A control Defender for Cloud cannot automatically assess
  • Compliance dashboard The view for tracking progress and attention areas
  • Built-in Standards, MCSB, and the Paid-Plan Boundary

The Microsoft Cloud Security Benchmark (MCSB) is the default standard, assigned automatically for Azure when Defender for Cloud is enabled, and it can extend to AWS and GCP. On top of MCSB you can add regulatory frameworks such as ISO/IEC 27001 , PCI DSS , NIST SP 800-53 , SOC 2 , CIS benchmarks , and others. You do not need to memorize the full list for SC-900 — only that Defender for Cloud assesses resources against these standards across connected clouds.

An important and frequently tested nuance: the regulatory compliance dashboard (with frameworks beyond the free baseline) is a capability of the paid Defender CSPM plan . The MCSB policy runs under free Foundational CSPM, but the broader, multi-framework compliance dashboard belongs to Defender CSPM. If a question contrasts free vs paid, place the regulatory compliance dashboard on the paid side.

Multicloud Posture and Assessment Limits

Multicloud is central to the story. Defender for Cloud connects Amazon Web Services (AWS) accounts and Google Cloud Platform (GCP) projects using agentless methods, then assesses those workloads against industry standards and reports posture. Secure score and compliance views can display posture by environment — Azure, AWS, and GCP — so a single pane covers all three.

There are limits to automation. Microsoft notes that if a compliance control cannot be automatically assessed , Defender for Cloud cannot decide whether a resource complies; that control appears greyed out and must be addressed through manual attestation or external evidence. This is a useful caution for exam wording: Defender for Cloud provides compliance monitoring and insight , but it does not automatically prove every requirement.

Finally, separate Defender for Cloud compliance from Microsoft Purview Compliance Manager . Defender for Cloud assesses cloud resource posture against security standards; Compliance Manager (a Microsoft compliance solution) manages assessments, improvement actions, and compliance score for organizational and data compliance. If the scenario says cloud resources, Azure/AWS/GCP, recommendations, or MCSB, choose Defender for Cloud; if it says data classification, retention, eDiscovery, audit, or Compliance Manager, choose Purview.

The regulatory compliance dashboard maps assessments to frameworks (ISO 27001, PCI DSS, NIST, and more).

MCSB is the free default; the multi-framework compliance dashboard is a Defender CSPM (paid) feature.

Multicloud posture spans connected Azure, AWS, and GCP.

Non-assessable controls are greyed out and need manual attestation.

Connecting AWS and GCP

Defender for Cloud onboards other clouds through connectors : an AWS connector (linking AWS accounts) and a GCP connector (linking GCP projects). These connectors use agentless methods to read configuration and posture, so Defender for Cloud can deliver CSPM insight and, when the relevant Defender plans are enabled, CWPP protection across all three clouds. After onboarding, AWS and GCP resources appear in the asset inventory , contribute to secure score , and are measured against standards — including a cloud-appropriate version of MCSB — in the regulatory compliance dashboard.

This unified, cross-cloud view is the heart of why Defender for Cloud is a multicloud CNAPP and not an Azure-only tool.

For SC-900 you should be able to answer 'which service gives one compliance and posture view across Azure, AWS, and GCP?' with Defender for Cloud , and to recognize that the connectors are the mechanism that makes multicloud assessment possible.

Compliance Posture Is Not Certification

A subtle but tested point: the regulatory compliance dashboard reports how your resources measure against a framework's controls — it does not grant or replace a formal audit or certification . Defender for Cloud automates the technical control checks it can evaluate, but many framework controls are organizational or procedural (policies, training, physical security) that no tool can verify automatically. Those appear as greyed-out or manual controls requiring attestation.

So the honest exam framing is: Defender for Cloud helps you monitor and improve compliance posture and prepare for audits, while the actual certification comes from an accredited auditor.

  • Concept What it means here
  • Automated control Defender for Cloud can technically assess and report pass/fail
  • Manual / greyed-out control Requires human attestation or external evidence
  • Compliance posture Current measured state against assigned frameworks
  • Certification A formal attestation issued by an auditor, not by the tool
  • Defender for Cloud vs Purview, One More Time

Because both products use the word compliance , keep the scope test handy. Defender for Cloud answers compliance questions about cloud resources and infrastructure (Azure/AWS/GCP, MCSB, recommendations, greyed-out controls). Microsoft Purview Compliance Manager answers compliance questions about the organization and its data (assessments, improvement actions, compliance score, and templates spanning Microsoft 365 and other services).

If the prompt centers on cloud subscriptions and resource hardening, it is Defender for Cloud; if it centers on data, records, eDiscovery, audit, or organizational improvement actions, it is Purview.