11.5 Purview Playbook for Compliance, Data, and Risk

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, retention policies, retention labels, records management, eDiscovery, audit, insider risk management, content explorer, activity explorer, or Compliance Manager, start with Purview. The security word in a scenario does not always mean Defender; protecting sensitive information and proving compliance are Purview responsibilities.

The compliance domain also includes Microsoft Service Trust Portal and Microsoft Priva. Service Trust Portal is associated with Microsoft compliance resources and privacy principles. Microsoft Priva is associated with privacy capabilities. Those items are not interchangeable with Sentinel or Entra. They sit in the compliance and privacy lane.

Purview Elimination Rules

• If the scenario says classify, label, retain, discover, audit, or manage records, think Purview.
• If the scenario says sign in, access, role, or governance of identities, think Entra.
• If the scenario says incident, hunting, workbook, connector, or playbook, think Sentinel.
• If the scenario says endpoint, email, cloud app, cloud workload, vulnerability, or threat intelligence, think Defender.

Compliance Manager is a common distractor because the phrase compliance score can sound like a security score. For SC-900, compliance score is tied to Compliance Manager and improvement actions. Secure score and cloud posture recommendations are associated with Defender for Cloud. Do not swap them. One is about compliance assessment; the other is about cloud security posture.

Data loss prevention and sensitivity labels often appear together but are not the same concept. Labels identify or classify content and can drive protection behavior. Data loss prevention policies help prevent sensitive data from being shared or transmitted in ways that violate policy. Retention controls answer a different lifecycle question: how long content should be kept or when it can be deleted.

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. Once the verb is clear, product selection is usually obvious.