Study guide

9.4 Compliance Manager Assessments

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

9.4 Compliance Manager Assessments

Key Takeaways Explain This Topic AI

Compliance Manager (in Microsoft Purview) helps you assess and manage compliance across your tenant using templates, assessments, controls, and improvement actions.

An assessment groups controls for a specific regulation or standard (e.g., GDPR, ISO 27001, HIPAA, NIST CSF); every tenant starts with the Microsoft 365 Data Protection Baseline assessment.

Controls split into Microsoft-managed actions (Microsoft handles them) and your-controls / improvement actions (your responsibility) — the shared responsibility model in action.

Pre-built assessment templates exist for hundreds of regulations; you assign owners and evidence to improvement actions to track work.

Last updated: June 2026

Compliance Manager Building Blocks

Compliance Manager , found in the Microsoft Purview portal, helps your organization assess and manage compliance against regulations and standards. It is the SC-900 answer whenever a scenario describes structured, ongoing compliance work measured by a compliance score . Its building blocks are:

Element What it is

Template A pre-built blueprint for a regulation/standard (GDPR, ISO/IEC 27001, HIPAA, NIST CSF, SOC 2, and 300+ more). You use a template to create an assessment.

Assessment A grouping of controls for a specific regulation, scoped to a product or group of products in your tenant.

Controls The specific requirements in a regulation; each maps to one or more actions.

Improvement actions The concrete tasks you complete to satisfy controls and raise your score. Assignable, with evidence and review workflow.

Every tenant begins with a default Microsoft 365 Data Protection Baseline assessment . This baseline draws its controls primarily from the NIST Cybersecurity Framework (CSF) and ISO , with additional elements from FedRAMP and the EU GDPR . From the moment you open Compliance Manager it is already collecting signals from your Microsoft 365 solutions, so you see your initial standing and suggested actions without any setup.

Because every organization's obligations differ, Compliance Manager relies on you to add and manage further assessments (for instance, creating an ISO 27001 or HIPAA assessment from a template) so risk is covered as comprehensively as your regulatory environment requires.

What Compliance Manager is for

Microsoft summarizes Compliance Manager's value in four jobs you should be able to recite:

Take inventory of your data-protection risks against a regulation.

Manage the complexity of implementing controls through built-in, pre-mapped templates.

Stay current with evolving regulations and certifications as Microsoft updates templates.

Report to auditors and leadership with a clear, quantifiable compliance score and evidence.

The key SC-900 framing is that Compliance Manager turns an abstract regulation into a tracked backlog of concrete tasks . Instead of reading the GDPR text and guessing what to do, you create the GDPR assessment, get a list of mapped controls and improvement actions, and work through them with owners and evidence attached.

Shared Responsibility Inside Compliance Manager

A critical, frequently tested idea: improvement actions are split by who is responsible , mirroring the cloud shared responsibility model .

Microsoft-managed actions — controls Microsoft implements and maintains on the platform. You don't act on these; Compliance Manager shows their status and Microsoft's testing details so you can cite them as evidence.

Your controls (improvement actions managed by your organization) — controls you are responsible for implementing, testing, and documenting. These are the tasks you assign to owners.

This split is why Compliance Manager pairs naturally with the Service Trust Portal: the portal provides Microsoft's audit evidence, while Compliance Manager tracks the controls that fall on your side of the line.

How you work an assessment

Create an assessment from a template for the regulation you must meet.

Review the controls and the improvement actions beneath them.

Assign each of your improvement actions to an owner and gather evidence (you can upload files and store implementation/test notes).

Mark actions implemented and tested ; status updates flow to the dashboard (typically within 24 hours).

Watch the compliance score reflect your progress (covered in the next section).

Selection cues and traps

  • Scenario language Answer
  • "Assess our GDPR/HIPAA/ISO posture using a template and track tasks" Compliance Manager
  • "Show Microsoft's certification evidence" Service Trust Portal
  • "Detect privacy risks / handle subject rights requests" Microsoft Priva
  • "Search audit logs for an investigation" Audit (Purview)

Common trap: Compliance Manager is not a guarantee of compliance . Microsoft is explicit that its recommendations "should not be interpreted as a guarantee of compliance" — you must still validate controls for your regulatory environment. On SC-900, choose Compliance Manager for managing and tracking compliance, never as proof that you are compliant.

Worked assessment scenario

A healthcare provider must demonstrate progress toward HIPAA/HITECH compliance. The compliance lead opens Compliance Manager , creates a HIPAA assessment from the pre-built template, and reviews the resulting controls . Some controls show Microsoft-managed actions already satisfied by the platform (with Microsoft's testing evidence attached for the auditor); others are improvement actions the organization owns — for example, configuring audit logging or restricting access to records.

The lead assigns each of those actions to an owner, attaches implementation evidence , marks them tested , and watches the compliance score climb as high-impact actions are completed.

Distinguish this from neighbors: the auditor's request for Microsoft's SOC report still goes to the Service Trust Portal ; handling a patient's request to see their personal data goes to Priva Subject Rights Requests ; searching who accessed a record last Tuesday goes to Audit in Purview. Compliance Manager owns the assessment, control-tracking, and scoring layer — and only that layer. Whenever a scenario names a regulation and asks to track structured tasks toward it, Compliance Manager is the answer, even when the broader "Microsoft Purview portal" also appears as an option.