Microsoft Purview Data Governance Is Retiring. What Should You Do Next?
Microsoft is retiring Purview Data Governance, its Unified Catalog, Data Map and governance workflows, with support ending on November 12, 2027. Purview itself stays as Microsoft's data security and compliance product, and Microsoft Fabric with the OneLake catalog becomes its data governance solution. Every Purview Data Governance customer now has a year to decide where their glossary, data products and lineage will live, and whether that place should depend on one platform.
On November 12, 2026, Microsoft announced that Purview Data Governance will be retired, with support ending on November 12, 2027. The retirement covers the Unified Catalog, Data Map, Workflows and classic Azure Purview. Purview data security and compliance stays: sensitivity labels, classification and data loss prevention keep working. Microsoft points customers to Microsoft Fabric and the OneLake catalog, which governs Fabric items well. Microsoft's own transition guidance says not to claim full glossary or critical data element parity, and the OneLake catalog documentation does not describe data quality rules. Teams with Databricks, Snowflake, SAP or on-premises systems next to Fabric need a catalog that is not tied to one platform, and a year is just enough time to move.
What is Microsoft retiring in Purview Data Governance?
Microsoft is retiring the data governance half of Purview, and keeping the data security and compliance half. In its November 2026 partner notice, Microsoft says the retirement includes the Unified Catalog, Data Map, Workflows and the Microsoft Azure Purview solutions, while Purview Data Security and Compliance offerings are unchanged.
Microsoft Purview as a product continues. What it means for each part of Purview:
| Purview capability | After November 12, 2027 | What you need to do |
|---|---|---|
| Unified Catalog: glossary terms, governance domains, data products, critical data elements, OKRs, data quality rules | Retires | Move this content to a new catalog |
| Data Map: source scanning, technical assets, scanned lineage | Retires | Rescan your sources in the new tool |
| Workflows: approvals and access requests | Retires | Rebuild your approval and access flows |
| Classic Azure Purview data governance | Retires | Same as above |
| Sensitivity labels and information protection | Stays | Nothing, keep using Purview |
| Data loss prevention across the data estate and AI | Stays | Nothing, keep using Purview |
| Compliance capabilities | Stays | Nothing, keep using Purview |
In short: the security team keeps working in Purview as today. The data office has to find a new home for the glossary, domains, data products and quality rules it built by hand, before November 12, 2027.
Purview Data Governance retirement timeline
Customers have twelve months, and the product is frozen for new customers from day one. Microsoft announced the retirement on November 12, 2026. From that day, according to the Unified Catalog documentation, new accounts can no longer be created and existing capabilities remain in maintenance mode. Support ends on November 12, 2027.
Maintenance mode means existing catalogs keep working, but customers should not expect new governance features in Purview. Microsoft also asks customers with contractual obligations and in highly regulated industries to engage their Microsoft account team early, because those cases are assessed individually. If your regulator expects an unbroken record of data ownership, definitions and approvals, start there.
What does Microsoft recommend instead?
Microsoft names two paths: its own, which is Microsoft Fabric with the OneLake catalog, and third-party data governance tools for needs that reach beyond Fabric. Both come from the announcement.
Microsoft's main path
Microsoft Fabric and the OneLake catalog
Governance inside the platform. Policies, lineage and stewardship stay close to the data in OneLake, and the catalog is embedded in Teams, Excel and Foundry.
Included in Fabric capacity. No separate meter, unlike the per-asset billing of Purview Data Governance.
Other sources through OneLake. Shortcuts, mirroring and supported connectors bring third-party data in without copying it.
For needs beyond Fabric
Third-party data governance tools
Microsoft says it plainly. Some organizations have needs that reach beyond what is in Fabric today, and Fabric integrates with third-party governance providers so customers can decide what works best for them.
Who it is for. Teams that run Fabric next to Databricks, Snowflake, SAP or on-premises systems, or that need a business glossary and data products with owners and approvals.
Where Dawiso fits. A data catalog across Fabric and the platforms next to it, bought through Microsoft Marketplace. See how the move works.
The announcement does not name which non-Microsoft platforms the "supported connectors" cover, and Microsoft has not announced a dedicated migration tool. A day later, Microsoft published transition guidance that maps Purview outcomes to Fabric, recommends moving in waves, and is candid about gaps: external metadata scanning, glossary and critical data element depth, data quality workflows and broad policy coverage are not one-to-one replacements today.
This is not the first such move. Customers of the earlier Azure Data Catalog were sent to Purview, and Microsoft's own migration guide warned there was "no in-place upgrade experience". The glossary a governance team builds tends to outlive the product it was built in, which is worth keeping in mind when choosing the next one.
Is the OneLake catalog enough to replace Purview Data Governance?
For organizations whose data lives almost entirely in Fabric and Power BI, the OneLake catalog may be enough. For a governance program built around a business glossary, data products and quality rules, or for data that lives outside Fabric, it is not a like-for-like replacement today. The OneLake catalog has three tabs, documented on Microsoft Learn:
Explore
Find Fabric items, such as lakehouses, warehouses, semantic models and reports, with owners, endorsement, labels, tags and lineage.
Govern
See governance health and recommended actions, such as label, description and endorsement coverage.
Secure
Manage workspace roles and OneLake security roles, including row-level and column-level security.
Mapped against what Purview Data Governance customers actually built, the picture looks like this as of November 2026, based on the OneLake catalog documentation and Microsoft's transition guidance:
| Purview Data Governance capability | OneLake catalog, as documented in November 2026 |
|---|---|
| Business glossary terms with owners and approval | Tags, descriptions and endorsement; Microsoft's guidance says to export and preserve terms and not to claim full glossary parity |
| Governance domains | Fabric domains and subdomains scope items and insights |
| Data products | Domains, endorsement and sharing; Microsoft's guidance says to define the product contract, owner, lifecycle and access process outside the catalog where needed |
| Critical data elements and OKRs | Not described; no full critical data element parity, per Microsoft's guidance |
| Data quality rules and scores | Not part of the OneLake catalog; Govern reports freshness and curation, and Microsoft notes it is not a rules, profiling and scoring engine. Fabric offers data quality constraints for materialized lake views |
| Approval workflows | Endorsement for items, item sharing and semantic model access requests; Microsoft advises keeping approval and evidence processes elsewhere where Fabric does not cover them end to end |
| Lineage | Fabric lineage and impact analysis for supported items; Microsoft advises another method for cross-system lineage |
| Sources outside Microsoft | Reached through OneLake shortcuts, mirroring and connectors; Microsoft notes that data connectivity is not enterprise metadata scanning |
Microsoft's Govern documentation also lists limitations worth reading before you plan: insights do not cover subitems such as tables, cross-tenant scenarios and guest users are not supported, and Govern is not available when Private Link is enabled. The Fabric roadmap moves quickly, so check it again before you decide, but plan on what is documented, not on what might ship.
The other question is scope. Governance in the OneLake catalog follows the data into OneLake. A Databricks lakehouse, a Snowflake account, an SAP system or an on-premises Oracle database is governed there only to the extent that it is shortcut or mirrored into Fabric. Comparable platform catalogs, such as Unity Catalog in Databricks or Snowflake Horizon, follow the same logic: they govern their own platform well and the rest of the estate partly. Our comparison of Unity Catalog and Microsoft Purview and of Databricks and Microsoft Fabric covers that boundary in more detail.
Two options for Purview Data Governance customers
Every Purview Data Governance customer now has two realistic paths, and the deciding question is whether your data lives only in Fabric.
Option 1. If you run only on Microsoft Fabric, move to the OneLake catalog
If your data estate is Fabric and Power BI and little else, the OneLake catalog is the natural target. Governance is built into the platform you already use, it is included in Fabric capacity instead of a separate per-asset bill, and Microsoft's transition guidance is written for exactly this case. For these teams, the move is mostly a matter of mapping domains and owners, and it will likely cost less than Purview Data Governance did.
In our experience, few enterprises run on Fabric alone. And there is one open question even for those that do: how Fabric will handle a business glossary and data products. Microsoft's own guidance maps both to tags, descriptions, endorsement and domains, and advises defining the data product contract, owner and lifecycle outside the catalog where needed. Our reading is that the OneLake catalog may develop into a strong technical catalog with lineage, much like Unity Catalog in Databricks, with less depth on the business side. That is a possibility, not a certainty. If your governance program is business-facing, with approved terms, owners and data products that business users work with, plan for the chance that you will need another tool next to Fabric even as a Fabric-native company.
Option 2. If your data is not only in Fabric, choose a third-party data catalog
If Fabric runs next to Databricks, Snowflake, SAP, Oracle or on-premises systems, you need a data catalog that covers all of them, and Microsoft itself points to third-party governance vendors for needs that reach beyond Fabric. Most teams will start with a shortlist of established data catalogs, and many will also look at what is available on Microsoft Marketplace.
Buying through Microsoft Marketplace works much like buying Purview did. The subscription is billed through your Microsoft account, so it appears on the Microsoft invoice you already pay, under the agreement you already have, rather than as a new vendor relationship. For procurement teams, that is often the difference between a quick purchase and a months-long vendor onboarding.
Option 2 does not mean leaving Microsoft. Purview stays the place for sensitivity labels and data loss prevention, Fabric stays the data platform, and the data catalog sits across Fabric and everything next to it. Your definitions, owners and lineage then no longer depend on one vendor's product strategy, which matters more now that the same definitions also feed AI agents.
Why start the Purview Data Governance migration now
A year sounds like plenty of time, but there are three reasons not to wait.
The migration takes work
Thousands of glossary terms, custom attributes, data products and owners need planning, mapping and validation. The more you built, the longer it takes.
Procurement takes time
With formal purchasing, security reviews and legal checks, buying a new tool can take months before anyone can use it.
Purview will not get better
In maintenance mode, expect no new governance features. Fixes your team was waiting for, such as better workflows, may never arrive, while the rest of the market moves on.
Purview Data Governance migration checklist
Treat the move as a migration project with a fixed end date, and separate what people built from what scanners found. Hand-built content, such as glossary terms, domains, data products, critical data elements, custom attributes and owners, carries the business value and has to be migrated. Scanned metadata and lineage are better rescanned by the new tool, so they start current. A realistic plan for the twelve months:
Q1 2027
Inventory and decide
List everything built by hand and every source Purview scanned, inside and outside Fabric. Leave labels and DLP in Purview. Choose the target and start procurement.
Q2 2027
Pilot one domain
Move one business domain end to end: its terms, owners and data products, with its sources rescanned. Validate it with the business owners.
Q3 2027
Migrate in waves
Move the remaining domains. Keep Purview running in parallel, reconcile counts of terms, owners and data products, and fix links that still point to Purview.
Q4 2027
Cut over and document
Switch off Purview Data Governance before November 12, 2027. For regulated teams, record what moved, who approved it and when.
If some domains live only in Fabric, they can be governed in the OneLake catalog while a platform-independent catalog covers the rest. Decide who owns which, so definitions are not maintained twice, and talk to your Microsoft account team early if your contract or regulator requires it.
Moving from Purview Data Governance to Dawiso
Dawiso is a Microsoft partner, available on Microsoft Marketplace, and a data catalog that covers Microsoft Fabric in depth together with the platforms next to it. Because you can buy it through Marketplace, it is billed through your Microsoft account like Purview was, without a new vendor agreement.
Why Purview customers choose Dawiso
A catalog the business uses
People search in their own words and see what an asset means, who owns it and whether it is approved. The business glossary has domains, terms, indicators and rules, with approval workflows.
Data products end to end
Data products have an owner and a lifecycle to production. In the Data Market, users add them to a cart and request access, and the approver decides.
Fabric and everything next to it
The Fabric connector reads workspaces, lakehouses, warehouses, semantic models and reports. Databricks, Snowflake, dbt, SAP HANA, Oracle and more add end-to-end lineage.
AI built in
Agent Studio runs AI agents on top of the catalog, and the MCP Server gives Claude, Cursor and other agents the governed definitions.
Priced per user
Per-user pricing with unlimited connectors, so cataloging more assets does not raise the bill the way a per-asset meter does.
Bought through Microsoft
Dawiso is a Microsoft partner on Microsoft Marketplace, billed through your Microsoft account like Purview was.
How the migration to Dawiso works
A member of the Dawiso customer success team runs the migration with you. Existing content is carried over from Purview: business terms, descriptions and data products, including custom attributes and other custom structures. Connected sources such as Fabric, Power BI and the platforms next to them are scanned fresh, so technical metadata and lineage start current. On top of what you had in Purview, you get the Data Market, Agent Studio and end-to-end lineage across platforms.
Pricing is hard to compare directly, because Purview Data Governance was billed per governed asset per day and Dawiso is billed per user. Tell us what Purview Data Governance cost you, and we will propose a Dawiso plan for a similar budget.
Bertel O. Steen runs Microsoft Fabric and Databricks side by side in Dawiso, with more than 18,000 Fabric objects cataloged and the rollout completed in about 60 days. Read the Bertel O. Steen story, see the Microsoft Purview alternative page for a side-by-side view, or book a demo built around your Purview setup.
FAQ
Is Microsoft Purview being discontinued?
When does support for Microsoft Purview Data Governance end?
What replaces Microsoft Purview Data Governance, and what should we replace it with?
What is the best alternative to Microsoft Purview Data Governance?
Do sensitivity labels and DLP policies need to be migrated?
Does the OneLake catalog have a business glossary?
Can glossary terms be moved from Purview to another data catalog?
Can we buy a Purview Data Governance replacement through Microsoft Marketplace?
Sources
- Microsoft Security Community Blog - A next step in the evolution of the Microsoft Data Governance strategy (November 12, 2026)
- Microsoft Partner Center - November 2026 announcements: Update on the Microsoft Data Governance strategy
- Microsoft Analytics on Azure Blog - From Purview Data Governance to the Fabric OneLake Catalog (November 13, 2026)
- Microsoft Learn - Learn about Microsoft Purview Unified Catalog (retirement notice)
- Microsoft Learn - OneLake catalog overview
- Microsoft Learn - Govern your data in the OneLake catalog
- Microsoft Learn - Discover and explore Fabric items in the OneLake catalog
- Microsoft Fabric Blog - OneLake catalog: The trusted catalog for organizations worldwide (February 9, 2026)
- Microsoft Learn - Migrate from Azure Data Catalog to Microsoft Purview
- Dawiso Help - Microsoft Fabric, Business Glossary, Workflows, Data product lifecycle and Object import from Excel
See it in action
Planning your move from Purview Data Governance?
Book a demo and see your Purview content in Dawiso, next to Microsoft Fabric and the rest of your stack.