Microsoft will retire Purview Data Governance, with support ending November 12, 2027, and has made Fabric its data governance solution. Purview Data Governance is the part of Microsoft Purview that catalogs data, through Unified Catalog and Data Map, per Microsoft Learn. Purview stays focused on security and compliance. That splits the old question, coexist with Purview, extend it or replace it, into two. Security and compliance stay in Purview, so there is nothing to decide there. Data governance leads who wait lose the maintenance window to pilot and migrate. Governance moves to Fabric and the OneLake catalog, and what is left to decide is whether that catalog covers your estate or whether you add a third-party catalog for needs beyond Fabric. The retirement guide has the full timeline, and the migration plan covers the how.
| Field | Value |
|---|---|
| Category | Microsoft Purview role decision: coexist, extend or replace |
| Guide type | Decision framework, not a vendor shortlist |
| Decision window | Purview Data Governance support ends Nov 12, 2027, so roughly the next twelve months |
| Key stakeholders | Data and analytics leadership, data governance leads, enterprise architects |
| Budget consideration | Microsoft says governance in Fabric is included in Fabric capacity rather than billed through separate meters; a third-party catalog is a separate purchase |
| Core decision criteria | Estate heterogeneity, lineage depth needed, business-user adoption, AI and Copilot grounding needs, volume of Purview governance content to move |
Is Microsoft Purview a catalog, a DLP tool or a governance platform after Nov 12, 2026?
Microsoft’s November 12, 2026 announcement says the OneLake catalog is “the single foundation for governing data across your entire estate,” and that it can govern data across Fabric, Azure and third-party sources through shortcuts, mirroring and supported connectors, without copying or moving it. Microsoft Learn adds that Unified Catalog and classic Purview data governance capabilities (formerly Azure Purview) are being retired, that new accounts can no longer be created, and that existing capabilities stay in maintenance mode through November 12, 2027.
What stays is the security side. Microsoft says Purview stays focused on “classifying, labeling and protecting sensitive data, preventing data loss across your estate and AI.” Sensitivity labels and Data Loss Prevention (DLP, policies that stop sensitive data from leaving approved places) stay in Purview.
| Job | Where it lives going forward |
|---|---|
| Classify, label and protect sensitive data | Purview (sensitivity labels) |
| Prevent data loss | Purview (DLP) |
| Catalog, glossary, data products, discovery | Fabric and the OneLake catalog |
| Needs beyond Fabric | Third-party catalogs; Microsoft names Atlan, Alation, Collibra and Informatica |
Microsoft advises regulated or contract-bound customers to contact their account team early.
Is Purview enough?
The answer depends on the job. For security and compliance, yes.
For governance, the question changes, because Microsoft Purview Data Governance has an end date. The better question is whether the OneLake catalog is enough. Where Purview’s governance coverage stops shows what you are moving.
Microsoft says some organizations have needs that reach beyond what is in Fabric today. Two tests tell you which side you are on. Does every source you govern sit in Fabric or reach it through shortcuts, mirroring or a supported connector? Do your AI agents need business context from outside Fabric? A yes to the first and a no to the second points to the OneLake catalog alone. Anything else points to a third-party catalog. The OneLake catalog guide covers what it includes.
What are the three types of path now: coexist, extend or replace?
| Path | What it means after Nov 12, 2026 | Best fit when |
|---|---|---|
| Coexist | Purview handles labels and DLP; the OneLake catalog handles governance | Microsoft-dominant estate, business users already work in Fabric, no AI context need beyond it |
| Extend | Same split, plus a third-party catalog for cross-platform catalog, lineage and business context | Mixed estate (Snowflake, Databricks, AWS, GCP), AI or Copilot grounding beyond Fabric |
| Replace | Purview Data Governance content (domains, glossary, data products, Data Map scans) moves to a new home before support ends | Every estate that uses Purview Data Governance today, whichever home you pick |
Replace used to be the narrow, contrarian option. It is now the default for governance content, because the product is retiring.
What you still choose is the destination: the OneLake catalog, a third-party catalog, or both. Replace never touches sensitivity labels or DLP, which stay in Purview under every path.
How does Purview differ from a catalog? Enforcement versus discovery
Enforcement means policies that act on data: a sensitivity label that protects a file, a DLP rule that blocks a risky share. Discovery means people finding data, understanding where it came from and trusting it.
After the announcement, the first stays in Purview and the second sits in a catalog.
Security teams keep working in Purview. Data teams work in the OneLake catalog, which Microsoft says is embedded in Teams, Excel and Foundry, or in a third-party catalog connected to Fabric. Purview’s controls for AI agents cover the security half for AI; what an agent needs to know about the data it reads is a governance question, and that moves with the catalog.
When to coexist, with the OneLake catalog as your catalog
Coexist fits more estates than vendor content admits. Five signals point to it:
- The estate is Microsoft-only or Microsoft-dominant, with no material Snowflake, Databricks, AWS or GCP footprint outside what Fabric reaches.
- Business users already find and trust data in Fabric, Teams or Excel.
- There is no near-term AI or Copilot grounding need that depends on context from outside the Microsoft estate.
- The gaps you can name are bounded, not blocking an active initiative.
- Your Purview Data Governance footprint is small enough to move without a dedicated program.
Evaluating a governance platform for Fabric: 20 questions to ask gives a checklist for testing whether the OneLake catalog meets your bar.
When should you extend with a third-party catalog?
Microsoft’s own wording is that Fabric “integrates with other 3rd party providers such as Atlan, Alation, Collibra and Informatica so customers can decide what works best for their data governance requirements.” Extend is that choice. Four signals point to it:
- Real, ongoing workloads sit on Snowflake, Databricks, BigQuery, Redshift or Azure SQL alongside Fabric, beyond a pilot.
- Lineage has to cross platform boundaries. Per Microsoft Learn, a Purview scan of a Fabric tenant captures item-level metadata and lineage for items other than Power BI, so check the OneLake catalog’s lineage depth against your own pipelines.
- AI or Copilot agents need business context spanning more than Fabric. That includes Copilot Studio agents Fabric data agents, and Azure AI Foundry agents.
- Business users need one front door across Microsoft and non-Microsoft assets.
Atlan fits this path in specific ways. Atlan connects to more than 100 sources. Its Fabric connector is generally available and catalogs workspaces, lakehouses, warehouses, semantic models, reports, dashboards, dataflows and data pipelines down to column level, with end-to-end lineage. Atlan’s Context Lakehouse stores context as open Apache Iceberg tables in OneLake that Fabric can query directly, and that context reaches people in Microsoft Teams and agents in Copilot Studio. Atlan is available in Microsoft Marketplace. For a head-to-head read, see Microsoft Purview and Atlan, Purview alternatives and the best data catalogs for Microsoft Fabric.
How do you pilot a catalog alongside Purview?
Purview Data Governance runs in maintenance mode until November 12, 2027, which gives you a window to pilot without a cutover. Plan the move in phases:
- Pick one governance domain with a real owner.
- Stand the candidate catalog up alongside Purview and connect the same sources.
- Compare answers to the same questions in both: where does this column come from (column-level lineage), who owns it, is it certified.
- Move that domain’s glossary terms and classifications once the answers match.
- Repeat by domain, retiring Purview content as each proves out.
Atlan’s Migration Studio, in private preview, reads Purview Data Governance with read-only access, checks the plan against Atlan before writing, lets the governance lead approve where objects land, and produces a reconciliation report comparing what landed against the plan. The migration plan walks through the phases.
How do you decide which path fits your estate?
Five questions, in order.
Step 1: Map your estate. Microsoft-only, or does it include Snowflake, Databricks, BigQuery or other platforms alongside Fabric?
Step 2: Size your Purview Data Governance footprint: domains, glossary terms, data products, Data Map scans. That sets the migration effort whatever you pick.
Step 3: Name your lineage depth requirement, and test the OneLake catalog against it on a real pipeline.
Step 4: Check for an AI or Copilot grounding need that reaches beyond Fabric. Why AI agents need an enterprise context layer explains why this often decides the outcome alone.
Step 5: Check contractual and regulatory constraints, and contact your Microsoft account team early if they apply.
Decision scorecard: which path fits your estate
| Criterion | Coexist signal | Extend signal |
|---|---|---|
| Estate heterogeneity | Microsoft-only or Microsoft-dominant | Mixed or multi-cloud |
| Lineage depth needed | Inside Fabric | Cross-platform, column level |
| Business-user adoption | Users already work in Fabric, Teams and Excel | Users need one front door across platforms |
| AI or Copilot grounding need | None near-term | Yes, beyond Fabric |
| Purview Data Governance footprint | Small, movable in a quarter | Large, needs a phased program |
Score each row for your own estate. Two red flags: changing anything about labels or DLP, which stay in Purview, and planning the move as a single step.
Context layer evaluation criteria is the fuller framework.
What should you ask before committing to a path?
Questions for your own team
Which systems hold business context that sits outside Fabric today, and how many matter day to day?
Questions for Microsoft
Which Purview Data Governance capabilities map to the OneLake catalog today, and where does each land? What are the dates in your contract? Where is the detailed transition guidance Microsoft says is available? Microsoft data governance tools maps the wider portfolio.
Questions for a catalog vendor
What exactly connects to Fabric, and how deep is the lineage? What does migration from Purview Data Governance look like, and how is it checked afterward? Context layer TCO: build versus buy versus bundle helps frame that conversation.
How does Atlan approach the decision?
Atlan is the AI Context Platform, built on a context layer that is model-agnostic and spans Microsoft and non-Microsoft estates. See what a context layer for AI agents is and Purview vs Unity Catalog.
Microsoft names Atlan among the third-party providers Fabric integrates with. The guidance above holds whether or not Atlan is your pick. For estates that reach beyond Fabric, what is context engineering and how to implement an enterprise context layer for AI cover what comes next.
The decision in one paragraph
Microsoft settled half the old question: security stays in Purview, and governance moves to Fabric on a known date.
The half left is yours. Does the OneLake catalog cover the sources and AI context you need, or does something sit beyond it?
FAQs about deciding Purview’s role
Short answers to common questions.
1. Is Microsoft Purview being replaced by Microsoft Fabric’s OneLake catalog?
For governance, yes. Microsoft’s November 12, 2026 announcement says Fabric is now its data governance solution and that Purview Data Governance will be retired a year from now, with support ending November 12, 2027. Purview stays focused on security and compliance: classifying, labeling and protecting sensitive data, and preventing data loss across your estate and AI. Sensitivity labels and Data Loss Prevention stay in Purview.
2. Can you run a third-party catalog on top of Microsoft Purview?
Microsoft says Fabric integrates with third-party providers such as Atlan, Alation, Collibra and Informatica, so customers can decide what works best for their governance requirements. Because Purview Data Governance is retiring, the practical setup is a third-party catalog alongside Fabric and the OneLake catalog, with Purview handling security and compliance.
3. If we keep Purview for DLP and sensitivity labels, what exactly still needs a separate catalog?
Possibly nothing. If the OneLake catalog covers the sources you govern, it can be your catalog. A separate catalog is for needs beyond Fabric, which Microsoft says some organizations have: governance across non-Microsoft platforms, deeper cross-platform lineage, and business context for AI agents that spans more than the Fabric estate.
4. Why pay for a separate catalog if Purview is already bundled into our Microsoft 365 license?
The comparison has changed. Purview Data Governance is retiring, with support ending November 12, 2027, and Microsoft says governance in Fabric is included in Fabric capacity rather than billed through separate meters. The question is no longer Purview’s bundle against a catalog. It is whether Fabric’s included governance covers your needs or whether needs beyond Fabric justify a third-party catalog.
5. How do we migrate metadata, glossary terms and classifications off Purview without starting over?
In phases. Stand the new catalog up alongside Purview during the maintenance window, prove it against real workflows, then move domains, glossary terms and classifications in batches. Atlan’s Migration Studio, in private preview, reads Purview Data Governance with read-only access, checks the plan before writing, and produces a reconciliation report of what landed. Microsoft says detailed transition guidance is available through your account team.
6. What are the main limitations of Microsoft Purview for data lineage?
Per Microsoft Learn, a Purview scan of a Fabric tenant captures item-level metadata and lineage for items other than Power BI, and sub-item metadata for lakehouse tables and files. Purview Data Governance is retiring, so the lineage question now belongs to the OneLake catalog or a third-party catalog. Test lineage depth on your own workloads before you commit.
7. Can Microsoft Purview catalog non-Microsoft data sources like Snowflake or Databricks, and should we use it for multi-cloud governance?
For governance, plan on the OneLake catalog instead. Microsoft says it can govern data across Fabric, Azure and third-party sources through shortcuts, mirroring and supported connectors, without copying data. Whether that depth is enough for your multi-cloud estate is the open question, and it is the one a third-party catalog is meant to answer.
8. How does Unity Catalog relate to Microsoft Purview? Do we need both?
They sit at different layers. Unity Catalog governs Databricks-native technical metadata. Purview now centers on security and compliance, while governance moves to Fabric.
Sources
- A next step in the evolution of the Microsoft data governance strategy, Microsoft Security Blog, November 12, 2026
- Learn about data governance with Microsoft Purview, Microsoft Learn (retirement notice)
- Learn about Microsoft Purview, Microsoft Learn
- Connect to your Microsoft Fabric tenant, Microsoft Learn
- Use Microsoft Purview with Microsoft Fabric, Microsoft Learn
- What lineage does Atlan extract from Microsoft Fabric, Atlan documentation