Microsoft Purview Data Governance is retiring. What happens next?

Microsoft has announced the retirement of Microsoft Purview Data Governance, with support ending on November 12, 2027. The announcement, made on November 12, 2026, marks a significant shift in Microsoft’s data governance strategy: governance capabilities are moving into Microsoft Fabric, with the OneLake catalog becoming the foundation of its approach.

For organizations using Purview to manage metadata, business glossaries, data lineage, and governance responsibilities, the announcement raises an important question: What happens to the data governance work you’ve already built?

The answer depends on your current architecture, governance requirements, and how much of your data ecosystem extends beyond Microsoft.

This article explains what is changing, what isn’t, and how to prepare for the transition without losing the business knowledge your organization depends on.

What is happening to Microsoft Purview Data Governance?

Microsoft is retiring its standalone Purview Data Governance offering and shifting its data governance strategy toward Microsoft Fabric.

According to Microsoft’s official announcement, the company wants governance to operate closer to where data is stored, analyzed, and consumed.

Rather than maintaining a separate governance experience, Microsoft is positioning the OneLake catalog within Fabric as the central experience for data discovery, governance, and trust.

The retirement affects several established components of the Purview governance ecosystem, including:

• Microsoft Purview Unified Catalog, used to organize and discover governed data assets, business concepts, and data products.
• Microsoft Purview Data Map, the metadata foundation for discovering and describing data assets and their relationships.
• Microsoft Purview Workflows, used to coordinate governance processes and approvals.
• Classic Azure Purview governance solutions, including earlier catalog experiences.

Microsoft confirmed the affected components in its November 2026 Partner Center announcement.

When is Microsoft Purview Data Governance retiring?

The key dates are:

Date	Milestone
November 12, 2026	Microsoft announces the retirement and transition strategy
November 12, 2026 onward	Microsoft supports existing customers transitioning to Fabric
November 12, 2027	Support for Purview Data Governance ends

Organizations therefore have a one-year transition window to assess their current governance environment, evaluate alternatives, and plan their next steps.

For enterprises with extensive metadata inventories, established stewardship processes, and multiple data platforms, that timeline makes early planning particularly important.

Is Microsoft Purview being discontinued entirely?

No. Microsoft Purview is not disappearing. The retirement specifically concerns Microsoft Purview Data Governance.

Microsoft Purview Data Security and Compliance will continue operating, including capabilities for protecting sensitive information and supporting regulatory compliance.

The distinction is important because governance and security, although closely connected, serve different purposes.

Capability	What happens next?
Purview Data Governance	Retiring, with support ending November 12, 2027
Purview Unified Catalog	Included in the retirement
Purview Data Map	Included in the retirement
Purview Workflows	Included in the retirement
Microsoft Purview Data Security	Continues
Microsoft Purview Compliance	Continues
Sensitivity labels and Data Loss Prevention	Continue within Microsoft’s security and compliance offerings
Microsoft Fabric OneLake catalog	Becomes Microsoft’s primary data governance experience

Put simply, Microsoft is separating two responsibilities more clearly.

Data security and compliance remain associated with Microsoft Purview, while data governance becomes part of the Microsoft Fabric experience.

For organizations using both, the transition does not necessarily require replacing their security and compliance solutions. It does require reassessing how they manage data discovery, business definitions, stewardship, and metadata governance.

What is replacing Microsoft Purview Data Governance?

Microsoft is positioning the OneLake catalog in Microsoft Fabric as its successor governance experience.

Microsoft Fabric brings together data integration, engineering, warehousing, analytics, and business intelligence within a unified platform. OneLake provides the underlying data foundation, while the OneLake catalog helps users discover and govern data assets.

Its governance capabilities include data discovery, ownership information, lineage, endorsements, and security-related context.

This approach reflects a wider industry trend toward embedding governance directly into data platforms and analytical workflows.

How does the OneLake catalog work?

The OneLake catalog provides a central experience for finding, understanding, and managing data within the Fabric ecosystem.

It also supports governance of external data through mechanisms such as OneLake shortcuts, mirroring, and supported connectors. This means it is not restricted to data physically stored in OneLake.

For organizations already using Microsoft Fabric extensively, the integration between the analytical platform and governance experience can simplify certain operations.

For example, teams working with Fabric lakehouses, warehouses, and Power BI can benefit from governance information connected to their existing analytical environment.

However, moving from Purview to OneLake should not be treated as a guaranteed one-to-one replacement of every existing governance capability.

Organizations need to assess how their current glossaries, custom metadata, stewardship workflows, data products, and integrations map to the capabilities available in Fabric.

That assessment becomes particularly important when data governance extends across multiple cloud platforms, business applications, and analytics tools.

Is Microsoft Fabric OneLake catalog enough for enterprise data governance?

For some organizations, it may be.

For others, the answer depends on the complexity of their data ecosystem and the role governance plays across the business.

Microsoft explicitly acknowledges that certain organizations have governance requirements beyond the capabilities currently available in Fabric and that third-party governance platforms can complement its ecosystem.

The central question is therefore not simply whether OneLake can catalog your data.

It is whether your governance strategy needs to connect data knowledge across different platforms, teams, and business initiatives.

Consider an organization where:

• Customer data is managed in Salesforce.
• Financial information is stored in Snowflake.
• Data transformation happens through dbt.
• Analytics teams build dashboards in Power BI.
• AI teams develop applications using data from several environments.

Even with Microsoft Fabric at the center of its analytics architecture, that organization still needs consistent business definitions, ownership, and visibility across the systems involved.

A metric such as net revenue should mean the same thing whether it appears in a Snowflake table, a Power BI report, or an AI-generated business analysis.

Similarly, a data owner should be able to understand where a critical data asset is used, which processes depend on it, and what might be affected by a change.

This is where an enterprise data catalog can provide additional value.

Rather than replacing Fabric’s native governance, a cross-platform catalog can help organizations build a shared business understanding across their broader data estate.

What happens to your existing Purview metadata, glossaries, and lineage?

One of the most important considerations in the Purview retirement is preserving the governance knowledge organizations have already created.

A data catalog is more than an inventory of technical assets.

Over time, it accumulates business knowledge that can be difficult to reconstruct, including agreed definitions, ownership assignments, documentation, and relationships between data assets.

For organizations with mature governance programs, this knowledge may represent years of collaboration between technical teams and business stakeholders.

Before planning a migration, identify which elements of your existing Purview environment must be preserved.

1. Business glossaries and definitions

Business glossaries provide shared definitions for important concepts such as customer, revenue, churn, and profitability.

When moving to a new governance environment, organizations should preserve not only the terms themselves but also their relationships, descriptions, ownership, and connections to technical assets.

2. Technical metadata

Technical metadata describes datasets, tables, columns, schemas, and other data assets.

Some information can be rediscovered by connecting a new catalog to source systems. Other information, including manually added descriptions and classifications, may require dedicated migration work.

3. Data lineage

Data lineage explains how information moves between sources, transformations, and analytical outputs.

Preserving lineage is important for impact analysis, troubleshooting, regulatory requirements, and understanding dependencies.

The migration process should distinguish between lineage automatically generated from connected platforms and relationships manually documented by governance teams.

4. Ownership and stewardship

Data owners and stewards are essential to maintaining accountability.

A successful transition should preserve clear responsibilities and ensure that governance processes remain operational after the original platform is retired.

5. Custom metadata and governance workflows

Custom attributes, classifications, approval processes, and other organization-specific configurations may not have exact equivalents in a new platform.

These elements require particular attention because transferring metadata does not automatically reproduce how a governance program operates.

The objective should be to preserve the knowledge, relationships, and responsibilities behind your governance program, rather than simply transfer as many catalog objects as possible.

How to prepare for Microsoft Purview Data Governance retirement

Organizations do not need to replace their entire data architecture because Purview Data Governance is retiring.

They do, however, need a structured transition plan.

The following five steps provide a practical starting point.

Step 1: Audit your existing Purview environment

Start by identifying what is currently managed in Purview.

Document your metadata sources, cataloged assets, business glossaries, governance domains, data products, and lineage relationships.

Pay particular attention to information created manually by business experts and data stewards.

This is often the knowledge that requires the most effort to recreate.

Your objective: Establish a clear inventory of the governance assets and processes that must be retained.

Step 2: Map your current and future data architecture

Identify where your organization’s data actually lives and how it is used.

This includes Microsoft technologies such as Fabric, Azure, and Power BI, but also other environments such as Snowflake, Databricks, SAP, and cloud applications.

Determine which systems are already connected to Fabric and which require independent governance capabilities.

Your objective: Understand whether your future governance architecture can rely primarily on OneLake or requires a broader enterprise catalog.

Step 3: Define your governance requirements

Evaluate your requirements before selecting a replacement or complementary solution.

Important questions include:

• Do business users need a shared glossary across multiple platforms?
• How are ownership and stewardship managed?
• Do teams need lineage across different technologies?
• Which classifications and custom metadata must be preserved?
• How will employees discover trusted data?
• How will AI applications and agents access governed business context?
• How will governance activities connect to business priorities?

Your objective: Select an architecture based on the capabilities your organization needs, not simply the technology being retired.

Step 4: Evaluate Microsoft Fabric and alternative data catalogs

Microsoft Fabric and the OneLake catalog should be part of the evaluation, especially for organizations with significant Microsoft investments.

But the transition is also an opportunity to evaluate enterprise governance platforms that operate across different technologies.

Compare solutions on their metadata coverage, business glossary capabilities, lineage depth, stewardship workflows, integration ecosystem, and support for AI-related use cases.

For existing Purview customers, migration feasibility is another essential criterion.

Ask potential providers what can be imported, which relationships can be reconstructed, and what must be recreated manually.

Your objective: Find the right balance between native platform governance and enterprise-wide business context.

Step 5: Validate the transition before switching

Avoid treating a successful metadata import as proof that a governance migration is complete.

Test the new environment with real use cases.

Can a business analyst find a trusted revenue metric? Can a data owner identify downstream reports affected by a source change? Can a steward update and validate a definition? Can governance teams still follow their approval processes?

Where possible, operate the existing and target environments in parallel while validating critical governance assets.

Your objective: Complete the transition before November 12, 2027, without disrupting the teams that depend on governed data.

Microsoft Purview alternatives: What should organizations look for?

The retirement creates an opportunity to reassess what organizations expect from their data governance platforms.

A modern enterprise data catalog should help teams move beyond documenting metadata toward making data understandable, trustworthy, and usable.

When evaluating Microsoft Purview alternatives, prioritize five capabilities.

Cross-platform metadata discovery. Connect data assets across cloud platforms, databases, transformation tools, and business intelligence environments.

A shared business glossary. Give technical and business teams a common understanding of the data they use.

Data lineage and impact analysis. Understand relationships and dependencies so teams can assess changes and investigate issues.

Collaboration and accountability. Make ownership, stewardship, and knowledge sharing part of everyday work.

Context for AI and measurable business outcomes. Ensure governed data knowledge can support AI applications while connecting data and AI initiatives to organizational priorities.

The most suitable solution will depend on your existing technology stack, the maturity of your governance program, and how widely governed data needs to be used.

For some organizations, the native governance experience in Fabric may be sufficient.

For others, an enterprise-wide catalog will be an important complement.

How DataGalaxy helps organizations move beyond platform-specific governance

Microsoft’s announcement highlights a broader challenge facing data-driven organizations.

Data governance cannot create its full value if the knowledge it produces remains disconnected from the people, applications, and business decisions that depend on it.

DataGalaxy helps organizations connect technical metadata with business context, ownership, and governance information across their data ecosystem.

With DataGalaxy’s integration ecosystem, organizations can bring together knowledge from multiple platforms rather than maintaining disconnected documentation for each system.

Connect Power BI to trusted business context

Power BI reports often play a central role in business decision-making.

But a dashboard alone cannot always explain how a metric is defined, which data sources contribute to it, or who is responsible for its accuracy.

With the DataGalaxy Power BI connector, organizations can connect Power BI metadata to business definitions, ownership information, and data lineage.

This helps business users understand what they are looking at and gives data teams greater visibility into the relationships behind analytical outputs.

Build a shared understanding beyond Microsoft

Many organizations operate across multiple analytical and operational platforms.

DataGalaxy helps connect metadata and business knowledge across supported technologies, including Power BI, Snowflake, Databricks, and dbt.

The goal is not to replace the tools teams already use.

It is to give them a shared understanding of what their data means, where it comes from, and how it supports the business.

DataGalaxy is also expanding its integration with Microsoft Fabric. The first capabilities of its dedicated Fabric connector were announced for Early Access in September 2026, with availability and supported coverage evolving as development progresses.

Connect trusted data to AI and business value

Data governance is increasingly important for AI.

AI applications need more than access to datasets. They need reliable context about the meaning, origin, ownership, and permitted use of information.

DataGalaxy’s Catalog helps structure that governed context for people and AI agents, including access through the Model Context Protocol (MCP).

DataGalaxy Portfolio complements this by helping organizations connect data and AI initiatives to business objectives, priorities, and measurable outcomes.

Together, they help organizations move from documenting data to understanding how it supports decisions and creates value.

The opportunity is not simply to replace an existing catalog. It is to make the knowledge behind your data more useful across the enterprise.

Purview retirement: A chance to rethink your data governance strategy

The retirement of Microsoft Purview Data Governance marks an important change for organizations invested in Microsoft’s governance ecosystem.

But it does not mean abandoning Microsoft Fabric, Power BI, or existing data platforms.

Instead, it creates an opportunity to reconsider how governance should work as data environments become more distributed and AI applications depend on trusted enterprise knowledge.

For some organizations, Microsoft’s OneLake catalog will provide the governance capabilities they need.

For others, the best approach may combine native platform governance with an enterprise catalog that connects business knowledge across systems.

Whatever approach you choose, the priority should remain the same: preserve the knowledge your teams have built, maintain trust in your data, and make that knowledge useful for the decisions and AI initiatives ahead.

Explore what comes next with DataGalaxy

Preparing for the end of Purview Data Governance? Discover how DataGalaxy can help connect your data assets, business definitions, and governance knowledge across your existing technology ecosystem.

Explore DataGalaxy’s integrations or request a demo.

---

Frequently asked questions about Microsoft Purview retirement

Is Microsoft Purview Data Governance being retired?

Yes. Microsoft announced on November 12, 2026, that Purview Data Governance is retiring. Support ends on November 12, 2027. The retirement includes the Unified Catalog, Data Map, Workflows, and classic Azure Purview governance solutions.

When is Microsoft Purview’s end-of-life date?

The end-of-support date for Microsoft Purview Data Governance is November 12, 2027. This does not apply to the entire Microsoft Purview product family.

What is replacing Microsoft Purview Data Governance?

Microsoft Fabric, with the OneLake catalog, is becoming Microsoft’s primary data governance solution. Organizations should evaluate its capabilities against their existing Purview requirements before transitioning.

Is Microsoft Purview Data Security also retiring?

No. Microsoft Purview Data Security and Compliance offerings are continuing. Microsoft has confirmed that its data security and compliance strategy remains separate from the retirement of Purview Data Governance.

What happens to the Microsoft Purview Unified Catalog?

Microsoft has included the Purview Unified Catalog in the retirement scope. Organizations using it should plan how to preserve and transition governance domains, business glossaries, data products, and other business metadata.

Can I migrate from Microsoft Purview to another data catalog?

Yes, organizations can evaluate alternative catalogs, but the migration process depends on the source and destination platforms. Technical metadata may be rediscovered from source systems, while business glossaries, custom metadata, ownership, and manually curated relationships may require dedicated export, mapping, and validation.

Is Microsoft Fabric OneLake catalog a replacement for Purview?

OneLake catalog is Microsoft’s intended successor governance experience. Whether it fully meets an organization’s requirements depends on its existing Purview capabilities, connected technologies, workflows, and enterprise governance needs.

What are the alternatives to Microsoft Purview Data Governance?

Organizations can consider Microsoft Fabric’s OneLake catalog and enterprise governance platforms such as DataGalaxy, Atlan, Collibra, Alation, and Informatica. The right choice depends on metadata connectivity, governance requirements, business context, migration support, and integration with existing systems.

Does DataGalaxy integrate with Microsoft Power BI and Fabric?

DataGalaxy offers a documented Power BI integration for connecting BI metadata, business context, and lineage. A dedicated Microsoft Fabric connector was also announced for Early Access in September 2026. Its current availability and technical coverage should be confirmed with DataGalaxy.

Do I need to stop using Microsoft Fabric if I choose another data catalog?

No. Enterprise data catalogs can complement Fabric’s native governance capabilities. Organizations can continue using Fabric and Power BI while connecting their metadata and business context with other systems through a broader governance platform.

About the author: Max Faivre

Product Marketing Manager

Share on social

X (Twitter)LinkedInFacebook