Study guide

9.3 Microsoft Purview Portal

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.3 Microsoft Purview Portal

Key Takeaways Explain This Topic AI

The Microsoft Purview portal (purview.microsoft.com) is the unified hub for data security, data governance, and risk & compliance solutions across multicloud, SaaS, and on-premises data.

Microsoft Purview is the current name for the merged Microsoft 365 compliance/Information Protection and the former Azure Purview data-catalog families.

Purview solutions include Compliance Manager, data classification, sensitivity labels, DLP, retention/records management, eDiscovery, audit, insider risk management, and the Unified Catalog/Data Map.

When a question names a specific Purview solution (DLP, eDiscovery, labels), the named solution wins over the generic portal.

Last updated: June 2026

What the Microsoft Purview Portal Unifies

The Microsoft Purview portal (purview.microsoft.com) is the single, streamlined console where administrators discover and operate Microsoft's data security, data governance, and risk & compliance solutions across on-premises, multicloud, SaaS, and AI data estates. SC-900 tests Purview as the compliance and data-governance family — the counterpart to Microsoft Entra (identity & access), Microsoft Defender (threat protection & posture), and Microsoft Sentinel (SIEM/SOAR).

The name matters because Microsoft rebrands are heavily tested . "Microsoft Purview" is the current name that merged two older lineages:

  • Old name Current name
  • Microsoft Information Protection (MIP) Microsoft Purview (Information Protection)
  • Microsoft 365 compliance center / portal Microsoft Purview portal
  • Azure Purview (data catalog/map) Microsoft Purview (Unified Catalog / Data Map)

If an exam item still says "Microsoft 365 compliance center" or "Microsoft Information Protection," recognize that the modern answer is Microsoft Purview .

The solutions surfaced in the portal

The portal is not one feature — it is the home for many. For SC-900, associate Purview with this solution set:

Compliance Manager — assessments, improvement actions, and the compliance score .

Data classification — trainable classifiers, sensitive information types, Content explorer, Activity explorer.

Sensitivity labels and label policies — protect/govern documents and emails.

Data loss prevention (DLP) — stop sensitive data from leaving inappropriately.

Retention policies/labels and records management — keep or delete content for the right duration.

eDiscovery and Audit — find and preserve content; search activity logs for investigations.

Insider risk management — detect risky internal activity.

Unified Catalog / Data Map — govern and map data assets at scale.

Many of these are taught in detail in the next chapter; here the goal is recognizing that they all live under the Purview umbrella.

Three pillars of the portal

Microsoft groups the Purview portal's solutions into three high-level pillars. Knowing the grouping helps you place any unfamiliar solution:

  • Pillar Purpose Example solutions
  • Data Security Protect data from misuse and leakage Sensitivity labels, DLP, Insider Risk Management

Data Governance Discover, map, and manage data assets and lifecycle Unified Catalog, Data Map, retention/records management

Risk & Compliance Meet and prove regulatory obligations Compliance Manager, eDiscovery, Audit

The portal also spans beyond Microsoft 365 : it governs data across multicloud (Azure, AWS, GCP), SaaS apps, on-premises stores, and AI workloads , which is why Purview is described as a unified platform rather than a single-product compliance center. For SC-900 you don't need deep multicloud detail — just recognize that Purview is broad and data-centric, not identity- or threat-centric.

Portal Versus a Named Solution

A recurring SC-900 pattern offers both "Microsoft Purview portal" and a specific Purview solution in the same answer set. The rule: the most specific correct answer wins. The portal is the workspace; the solution does the job.

Read the noun and the verb

Many products touch "data," so the noun alone is not enough. The verb reveals the solution:

  • Verb / requirement Purview solution
  • Track assessments, improvement actions, score Compliance Manager
  • Classify / discover sensitive content Data classification, Content explorer
  • Label and protect documents/emails Sensitivity labels
  • Prevent sensitive data from being shared/exfiltrated Data loss prevention (DLP)
  • Keep or delete content for a set period Retention / records management
  • Find and preserve content for legal/HR cases eDiscovery
  • Search what users did and when Audit
  • Detect risky internal user activity Insider risk management
  • Worked selection scenarios

"The compliance team needs a single place to access data security, governance, and compliance solutions." → Microsoft Purview portal (the question is about the workspace family).

"Block credit-card numbers from being emailed externally." → DLP , not the generic portal — the verb is prevent sharing .

"Search who accessed a mailbox last week." → Audit , not the portal.

Common trap 1 — wrong family. Distractors pull from other families: Entra admin center (identity), a Sentinel workspace (SIEM/SOAR), or Defender for Cloud (security posture). If the scenario is about governing or complying with data and obligations , stay in Purview.

Common trap 2 — portal over-selection. When a precise solution matches the stated job, do not default to "Microsoft Purview portal" just because it sounds comprehensive. The portal is the correct answer only when the question is genuinely about the unified workspace, not a specific task.

Keeping the four families straight

The deepest source of confusion on SC-900 is mixing the four Microsoft solution families. A one-line mental map prevents most mistakes:

Microsoft Entra → who you are and what you can access (identity, authentication, Conditional Access, roles, governance).

Microsoft Defender → protect and detect threats (endpoints, email/Office, cloud apps, identity threats, cloud posture, vulnerability management).

Microsoft Sentinel → collect, correlate, and respond at scale (SIEM analytics, incidents, hunting, SOAR playbooks).

Microsoft Purview → govern, protect, and comply with your data and obligations (classification, labels, DLP, retention, eDiscovery, audit, Compliance Manager, insider risk).

When a question's answer set draws one option from each family, the family that matches the noun + verb wins. "Label and protect a contract" is Purview; "block a risky sign-in" is Entra; "quarantine a malicious attachment" is Defender; "automate an incident response across tools" is Sentinel. Purview's signature is always a data-governance or compliance verb acting on content or obligations , which is exactly why the Purview portal anchors this entire compliance domain.