Microsoft is retiring Purview Data Governance, so Microsoft data governance tools now split by job: Fabric governs data and Purview protects it. If you lead data governance on Azure, you have until November 12, 2027, when Microsoft’s announcement says support ends, to decide where your glossary, owners, and policies will live. After that date Microsoft no longer supports Purview Data Governance.
We ordered the tools below by job, not by rank. Affected teams can start with the retirement guide and the migration plan.
What changed for Microsoft data governance on November 12, 2026
Microsoft announced a new data governance strategy on that date, and Fabric is now its data governance solution. The OneLake catalog is “the single foundation for governing data across your entire estate.”
Purview Data Governance will be retired a year from the announcement. Support ends November 12, 2027. Purview stays focused on data security and compliance: classifying, labeling, and protecting sensitive data, and preventing data loss across your estate and AI. Microsoft calls the change “drawing a clearer line between protecting data and governing it.”
Microsoft Learn is specific about what retires. Unified Catalog and classic Purview data governance (formerly Azure Purview) are being retired. New accounts can no longer be created, and existing capabilities stay in maintenance mode through November 12, 2027. Maintenance mode means the product runs while Microsoft stops building on it.
Our retirement guide covers what to decide and when. The migration plan has five steps, from assessment to the switch date. Regulated companies and those with contract obligations should talk to their Microsoft account team early. Microsoft says detailed transition guidance is available.
The old answer to “which Azure data governance tool?” was Purview. The new answer depends on the job. Decide first whether you are protecting data or governing it.
Microsoft data governance tools compared: which ones are there now?
The table follows Microsoft’s split: protection, then governance in Fabric, then governance on Azure Databricks, then third-party catalogs in alphabetical order. It is not a ranking.
| Tool | Job after the announcement | What it covers | Source |
|---|---|---|---|
| Microsoft Purview (security and compliance) | Classifying, labeling, and protecting sensitive data. Preventing data loss across your estate and AI. Sensitivity labels and data loss prevention (DLP) stay here | Microsoft 365, Azure, and AI workloads | Microsoft announcement |
| Purview Data Governance (Data Map and Unified Catalog) | Retiring. No new accounts. Maintenance mode through November 12, 2027 | Data Map scans sources. Unified Catalog curates governance domains and data products | Microsoft Learn |
| Microsoft Fabric with the OneLake catalog | Microsoft’s data governance solution going forward | Explore, Govern, and Secure experiences. Domains, endorsements, metadata scanning (cataloging data about your data), policies, and governance insights. Embedded in Teams, Excel, and Copilot Studio | Microsoft Learn |
| Unity Catalog on Azure Databricks | The governance layer inside Azure Databricks | Access control, lineage (the path data takes from source to report), auditing, and data classification for data and AI assets in Databricks workspaces | Microsoft Learn |
| Third-party catalogs (Alation, Atlan, Collibra, Informatica) | Named by Microsoft as providers Fabric integrates with, so customers can pick what fits their governance needs | Each vendor’s own scope, set out in its documentation | Microsoft announcement |
Older names you may still see
Two older names still turn up in searches. Azure Data Catalog was retired on May 15, 2024. Microsoft pointed its users to Purview then, so 2026 is the second move for anyone who followed that advice.
Compliance Manager is a Purview solution that assesses compliance across multicloud environments.
Microsoft’s announcement does not say whether Compliance Manager stays, so ask your account team.
Pick the row that matches your job, then check the gaps between rows.
Microsoft Purview: security and compliance
Purview’s lasting job is data security and compliance. If you need to label sensitive data and stop leaks through email, files, or AI assistants, Purview is the tool.
The announcement changes none of that. Our guide to Purview’s controls for AI agents shows how those protections reach agents.
The governance half is what retires. Learn lists two solutions in Purview Data Governance, and both are covered.

Microsoft Purview Data Map - Image by Microsoft Purview.
- Data Map scans your assets and multicloud sources and captures their metadata. Metadata covers names, owners, definitions, and lineage.
- Unified Catalog is the searchable catalog of that scanned metadata. You curate data products, grant access, and track data quality in it.
Learn notes that Data Map and Unified Catalog hold metadata, not the data itself. A migration moves descriptions, owners, glossary terms, and lineage. Your tables stay where they are.
Read more about Purview Unified Catalog and what Microsoft Purview is.
Count what you use before you plan. If your Purview estate is mostly sensitivity labels and DLP policies, the retirement touches you little. If it holds your glossary, owners, and data products, start the move now.
Fabric and the OneLake catalog: where Microsoft now puts governance
The OneLake catalog is the central place in Fabric to find data, check governance status, and manage security. Its Govern tab shows governance health, recommended actions, and admin controls.
Microsoft adds three points in its announcement:
- The catalog governs data across Fabric, Azure, and third-party sources. It uses shortcuts, mirroring, and supported connectors, so no data is copied.
- It is embedded in Teams, Excel, and Foundry. Learn also lists Copilot Studio.
- Governance is included in Fabric capacity. Microsoft does not bill it through separate meters.
Microsoft Learn says administrative controls are moving from the Fabric admin portal into the Govern tab. Expect the screens to change during the year-long transition.
For a data governance lead, the practical effect is simple.
Governance sits with the platform your analysts already use. Discovery, endorsements, and domains live next to the data. Microsoft also says some organizations have needs that reach beyond what is in Fabric today. That is why it names third-party providers.
Read the OneLake catalog guide and Microsoft Fabric governance for detail. If you are weighing catalogs for Fabric, the best data catalogs for Microsoft Fabric page scores them on six criteria. For a Fabric-only estate, the OneLake catalog is the place to start.
Unity Catalog on Azure Databricks
Many Azure estates run Databricks next to Fabric. Microsoft describes Unity Catalog as the governance layer built into Azure Databricks.
It enforces access control when you query a table or call a model. It tracks lineage as assets are used and logs activity for auditing.
Every asset in Unity Catalog is a securable object, such as a table, view, volume, function, or model. You grant permissions on it through a three-level namespace: catalog, schema, then object. Access control covers privileges, row and column filters, and attribute-based policies. An open-source version of Unity Catalog exists too.
The announcement leaves Unity Catalog as it was.
What changes is the question beside it. Fabric’s OneLake catalog is where Microsoft expects governance for Fabric items to live. Unity Catalog keeps governing what runs in Databricks. Teams with both platforms end up with two governance surfaces unless a third layer joins them.
Purview vs. Unity Catalog compares the two. If Databricks holds most of your workloads, Unity Catalog stays your governance layer there.
How should you choose among Microsoft data governance tools?
Start from the job, not the product name. The table maps common needs to the tool that fits, using what Microsoft’s documentation says each one does.
| If your main need is… | Look at… | Why |
|---|---|---|
| Classifying and labeling sensitive data, and stopping data loss | Microsoft Purview | Microsoft keeps it focused on security and compliance |
| Finding Fabric items, endorsing them, and tracking governance health | Fabric with the OneLake catalog | Microsoft’s stated governance solution, included in Fabric capacity |
| Access control and lineage for Databricks workloads | Unity Catalog on Azure Databricks | Built into Azure Databricks and enforced at query time |
| One glossary and one lineage view across Fabric, Databricks, and other platforms | A third-party catalog | Microsoft says some needs reach beyond what is in Fabric today |
| Moving off Purview Data Governance before November 12, 2027 | The OneLake catalog, a third-party catalog, or both | Microsoft’s announcement names both routes |
Most Azure estates will land on a mix.
Purview protects data. The OneLake catalog governs Fabric. Unity Catalog governs Databricks. Sometimes a catalog joins them. Do not treat the retirement as a like-for-like swap.
AI agents raise the stakes. An agent needs the definitions, owners, and lineage behind the data it reads. Our Fabric governance evaluation questions give you 20 questions to put to any vendor. Decide early whether your catalog must serve agents too.
What does Microsoft data governance cost?
Microsoft says governance in the OneLake catalog is included in Fabric capacity rather than billed through separate meters. That covers the OneLake catalog only.
Purview’s security and compliance capabilities, Azure Databricks, and third-party catalogs each follow their own licensing. Microsoft Learn’s billing pages and each vendor’s own quote are the sources. Ask your Microsoft account team how a move off Purview Data Governance changes your agreement. Plan for the cost of the move itself, which depends on how many glossary terms, data products, and owners you carry over.
When does a third-party catalog belong on the list?
Microsoft says Fabric integrates with third-party providers such as Atlan, Alation, Collibra, and Informatica “so customers can decide what works best for their data governance requirements.” Four situations usually bring one into the evaluation:
- Your estate spans Fabric plus other platforms, such as Databricks or Snowflake. You want one glossary and one lineage view across them.
- You run Purview Data Governance and need a landing place before support ends on November 12, 2027.
- AI agents need governed context from sources outside Fabric.
- Your governance work has outgrown a single tool.
None of these means dropping Purview. Many teams keep it for sensitivity labels and DLP, and add a catalog for governance. That matches the split in Microsoft’s announcement.
The alternatives to Purview Data Governance page compares the options with a shortlist rule. Coexist, extend, or replace walks through keeping Purview alongside a catalog. If a third party fits your estate, list every platform you run before you compare vendors.
Where Atlan fits
Atlan is an AI Context Platform. For Microsoft estates, these pieces matter:
- Fabric connector. Generally available since version 2.0 shipped in August 2026. It catalogs workspaces, lakehouses, warehouses, semantic models, reports, dashboards, dataflows, and data pipelines down to column level, with end-to-end lineage, per the connector documentation.
- Context Lakehouse. Stores context as open Apache Iceberg tables in OneLake that Fabric can query directly.
- Reach. More than 100 sources, so one graph covers Databricks, Snowflake, and the rest of the estate.
- Where people work. Context reaches people in Microsoft Teams and agents in Copilot Studio.
- Purchasing. Available in Microsoft Marketplace.
For teams leaving Purview Data Governance, Migration Studio is in private preview.
It reads Purview Data Governance with read-only access and checks the plan against Atlan before writing. The governance lead approves where each object lands. A reconciliation report then compares what landed with the plan. The migration plan explains the steps, and how the two work side by side is covered separately.
How Tide handled a compliance problem
Tide, a financial services firm, needed to improve compliance with the GDPR right to erasure. It used automated lineage to find where personal data lived. It then used Atlan Playbooks, rule-based bulk automations, to identify, tag, and secure that data. Work Tide had estimated at 50 days took 5 hours.
That example is about compliance, not Microsoft. You will face a similar proof problem when you move governance assets out of Purview Data Governance. You will need to show nothing was dropped.
Go deeper on Purview and Microsoft governance
- Purview Data Governance retirement guide: the dates, what is affected, and what to decide first.
- Purview data governance coverage: where its coverage stops, source by source.
- Fabric governance evaluation questions: 20 questions to ask a vendor.
- Data governance on Azure and Power BI data governance.
- Setup guides: a data catalog for Microsoft SQL Server and a data catalog for Power BI.
The platform these tools govern is covered in the Microsoft Fabric guide.
Final thoughts
Microsoft has drawn a line: Purview protects data and Fabric governs it. If you used Purview for both, you now have a date, November 12, 2027, and a decision.
Move governance to the OneLake catalog, to a third-party catalog Microsoft names, or to a mix.
Start with two lists. First, every platform you run. Second, every Purview Data Governance asset you rely on: glossary terms, data products, owners, and access policies. Those two lists tell you most of what you need to know.
Sources
-
Learn about data governance with Microsoft Purview, Microsoft Learn
-
Introduction to Azure Data Catalog (retired May 15, 2024), Microsoft Learn
-
How Tide automated GDPR privacy requests with Atlan, Atlan customer story