Study guide

11.5 Purview Playbook for Compliance, Data, and Risk

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.5 Purview Playbook for Compliance, Data, and Risk

Key Takeaways Explain This Topic AI

Microsoft Purview is the SC-900 product family for compliance and data governance; it absorbed Microsoft Information Protection (MIP).

Compliance Manager and compliance score handle assessment and improvement actions, not threat hunting; do not swap compliance score with Defender for Cloud secure score.

Sensitivity labels classify and can encrypt; DLP prevents leakage; retention and records management control lifecycle; eDiscovery and audit support investigation.

The Service Trust Portal (compliance resources) and Microsoft Priva (privacy) sit inside the compliance solutions boundary alongside Purview.

Last updated: June 2026

Choose Purview When the Asset Is Data or Compliance Evidence

Microsoft Purview is the SC-900 product family for compliance and data governance. If a scenario mentions data classification, sensitivity labels, data loss prevention (DLP), retention policies, retention labels, records management, eDiscovery, audit, insider risk management, content explorer, activity explorer, or Compliance Manager , start with Purview. The word "security" in a scenario does not always mean Defender; protecting sensitive information and proving compliance are Purview responsibilities.

Note the rebrand: Microsoft Information Protection (MIP) is now Microsoft Purview Information Protection , the classification and labeling layer of the suite.

The compliance domain also includes the Microsoft Service Trust Portal and Microsoft Priva . The Service Trust Portal hosts Microsoft's compliance resources, audit reports, and privacy principles. Microsoft Priva delivers privacy risk management and subject-rights-request capabilities. Neither is interchangeable with Sentinel or Entra — they sit firmly in the compliance and privacy lane.

Requirement Capability to recognize Why it fits

Assess compliance posture and improvement actions Compliance Manager and compliance score The task is compliance assessment.

Identify and classify sensitive information Data classification, content explorer, activity explorer The task is understanding data.

Mark content as confidential and optionally encrypt it Sensitivity labels and label policies The task is information protection.

Prevent sensitive data from leaving approved channels Data loss prevention (DLP) The task is data-protection policy.

Keep or delete content according to rules Retention policies, retention labels, records management The task is lifecycle management.

Find information for legal or investigation needs eDiscovery and audit The task is compliance investigation.

Identify risky insider activity Insider risk management The task is organizational risk review.

Purview Elimination Rules

A four-line lane check resolves most ambiguous compliance items:

If the scenario says classify, label, retain, discover, audit, or manage records, think Purview .

If it says sign in, access, role, or governance of identities, think Entra .

If it says incident, hunting, workbook, connector, or playbook, think Sentinel .

If it says endpoint, email, cloud app, cloud workload, vulnerability, or threat intelligence, think Defender .

The Score Trap and the Label/DLP/Retention Trio

Compliance Manager is a frequent distractor because the phrase "compliance score" can sound like a security score. For SC-900, compliance score is tied to Compliance Manager and its improvement actions, which measure progress against regulatory and standards-based controls. Secure score and cloud posture recommendations belong to Defender for Cloud . Do not swap them: one measures compliance assessment, the other measures cloud security posture. In final review, write the score's name next to its domain before answering.

Sensitivity labels, DLP, and retention often appear together but are distinct concepts. Sensitivity labels classify content and can drive protection actions such as encryption and visual marking. DLP policies prevent sensitive data from being shared or transmitted in ways that violate policy. Retention controls answer a lifecycle question: how long content must be kept and when it can be deleted. Mixing them up is a top SC-900 compliance error.

A strong final-review habit is to translate every compliance prompt into a verb. Classify maps to data classification. Label maps to sensitivity labels. Prevent leakage maps to DLP. Keep records maps to retention or records management. Search for legal evidence maps to eDiscovery. Review activity maps to audit. Assess posture maps to Compliance Manager. Manage privacy and subject rights maps to Priva. Once the verb is clear, the Purview capability is usually obvious, and the security or identity distractors fall away because they answer a different verb entirely.

Information Protection, Data Lifecycle, and Risk Inside Purview

Purview is best understood as three jobs working together. The first is information protection : discover and classify data with sensitive information types and trainable classifiers, then apply sensitivity labels that can mark documents, enforce encryption, and restrict access regardless of where the file travels. The second is data loss prevention , which uses those classifications to stop sensitive content from being shared through email, Teams, endpoints, or cloud apps in violation of policy.

The third is data lifecycle and records management , which uses retention labels and policies to keep content for a required period and dispose of it on schedule, and records management to declare immutable records for regulatory retention.

Purview job Core capabilities Question it answers

Information protection Data classification, sensitivity labels, encryption What is this data and how is it protected?

Data loss prevention DLP policies across Microsoft 365 and endpoints How do we stop it from leaking?

Data lifecycle / records Retention labels, retention policies, records management How long do we keep or delete it?

Discover and investigate eDiscovery, audit (Standard and Premium) How do we find and prove activity?

Risk and privacy Insider risk management, Communication Compliance, Priva Who is acting riskily and how do we manage privacy?

Compliance Posture and Trust Resources

The assessment and trust side rounds out the domain. Compliance Manager measures your posture against regulations and standards, expressing progress as a compliance score built from improvement actions you complete and controls Microsoft manages. The Service Trust Portal publishes Microsoft's own audit reports, certifications, and data-protection documentation so customers can evaluate Microsoft's compliance — it is a resource library, not a configuration tool. Microsoft Priva focuses on privacy: identifying personal data risk and automating data subject requests under regulations such as the GDPR.

Insider risk management and Communication Compliance detect risky internal activity and policy-violating communications respectively.

The exam habit that ties this together is domain discipline. Every capability above answers a compliance or data-governance question, never a SIEM, identity-access, or threat-protection question. When a four-option list pairs a Purview capability against a Defender or Sentinel option, ask whether the scenario is fundamentally about data, evidence, or obligation (Purview) or about threats, operations, or access (Defender, Sentinel, Entra). Naming the domain first, then the capability, is what keeps the compliance-solutions domain — roughly 25 to 30 percent of SC-900 — from turning into guesswork.