Courseiva
AZ-900Chapter 122 of 138Objective 3.2

Microsoft Purview (Data Governance)

This chapter covers Microsoft Purview, Azure's unified data governance service, in more depth than a brief mention. AZ-900 tests this under objective 3.2, as part of the broader governance and compliance tooling covered in this section.

9 min read
Intermediate
Updated Aug 21, 2026
Editorial oversight: Johnson Ajibi· Security Systems Architect · MSc IT Security · IEEE Senior Member

A simple way to picture Microsoft Purview (Data Governance)

A Catalog and Map of All Your Data

A large library doesn't just store books — it maintains a catalog describing what each book is about, where it's shelved, and who's allowed to check it out. Microsoft Purview plays that role for an organization's data estate: it discovers and catalogs data across an organization, classifies what's sensitive, and helps track how data is used and governed — regardless of whether that data lives in Azure, another cloud, or on-premises.

How It Actually Works

What Microsoft Purview does

Microsoft Purview provides unified data governance across an organization's data estate — discovering data sources, cataloging what data exists and where, classifying sensitive data types, and providing visibility into how data flows and is used across systems.

Data discovery and cataloging

Purview can scan and catalog data across many different sources — not limited to Azure alone, but potentially including other clouds and on-premises systems — building a searchable map of what data exists and where, which is often the first step in any serious governance or compliance effort.

Data classification

Purview can help classify data based on its sensitivity (for example, identifying data that contains personal or financial information), supporting compliance efforts and helping ensure sensitive data receives appropriate protection.

Why this matters for governance

Earlier chapters cover governance and compliance tools like Azure Policy (enforcing configuration rules) and Compliance Manager (tracking regulatory requirements). Purview complements these by focusing specifically on the data itself — understanding what data exists, where it lives, and how sensitive it is, which is foundational information for applying the right governance and compliance controls in the first place.

Scope beyond Azure

Because many organizations have data spread across multiple clouds and on-premises systems, not just Azure, Purview's ability to catalog and govern data across that broader estate — not Azure alone — is one of its more significant capabilities.

Walk-Through

1

Connect data sources

Purview is configured to scan and catalog data sources, which can span Azure, other clouds, and on-premises systems.

2

Build the data catalog

Discovered data is cataloged, creating a searchable map of what data exists and where it's located.

3

Classify sensitive data

Data is classified based on sensitivity, helping identify what needs stronger protection or specific compliance handling.

4

Use the catalog to inform governance decisions

The resulting visibility informs decisions about access control, protection, and compliance handling for specific data.

What This Looks Like on the Job

A large organization with data spread across Azure, another cloud provider, and legacy on-premises systems uses Microsoft Purview to build a single catalog of what data exists across all of those locations, discovering previously untracked sensitive data that needed stronger protection.

A separate organization preparing for a compliance audit uses Purview's classification capabilities to quickly identify where personal data is stored across their environment, rather than manually auditing every system one at a time.

How AZ-900 Actually Tests This

Objective 3.2 expects recognition of Microsoft Purview's role in data discovery, cataloging, and classification across an organization's broader data estate, complementing (not replacing) tools like Azure Policy and Compliance Manager.

A common wrong answer is confusing Purview with Azure Policy — Policy enforces configuration rules on resources; Purview focuses on discovering, cataloging, and classifying the data itself. Another common trap is assuming Purview only covers data within Azure — it's designed to span other clouds and on-premises systems too.

Stable terms: Microsoft Purview, data catalog, data classification. Memory trick: Purview = knowing what data you have and where it lives, across your whole estate, not just Azure — the foundation other governance tools build on.

Key Takeaways

Microsoft Purview provides unified data governance — discovery, cataloging, and classification — across an organization's data estate.

It's designed to span not just Azure, but other clouds and on-premises systems as well.

Data classification helps identify sensitive data needing stronger protection or specific compliance handling.

Purview complements tools like Azure Policy and Compliance Manager by focusing specifically on understanding the data itself.

Easy to Mix Up

These come up on the exam all the time. Here's how to tell them apart.

Azure Policy

Enforces configuration rules on resources

Focused on resource compliance

Microsoft Purview

Discovers, catalogs, and classifies data

Focused on understanding the data estate itself

Watch Out for These

Mistake

Microsoft Purview only covers data stored in Azure.

Correct

Purview is designed to discover and catalog data across a broader estate, including other clouds and on-premises systems, not Azure alone.

Mistake

Purview and Azure Policy serve the same purpose.

Correct

Azure Policy enforces configuration rules on resources. Purview focuses on discovering, cataloging, and classifying data itself — a complementary but distinct governance function.

Frequently Asked Questions

What is Microsoft Purview?

It's Azure's unified data governance service, providing discovery, cataloging, and classification of data across an organization's data estate — spanning Azure, other clouds, and on-premises systems, not just Azure alone.

How is Purview different from Azure Policy?

Azure Policy enforces configuration rules on resources — what's allowed to be deployed and how. Purview focuses on discovering, cataloging, and classifying the data itself, providing the visibility that informs governance decisions in the first place.

Does Purview only work with Azure data?

No — it's designed to discover and catalog data across a broader estate, including other cloud providers and on-premises systems, giving a unified view rather than an Azure-only one.

Terms Worth Knowing

Ready to put this to the test?

You've just covered Microsoft Purview (Data Governance) — now see how well it sticks with free AZ-900 practice questions. Full explanations included, no account needed.

Done with this chapter?