Microsoft Purview Data Governance is being retired

What does this mean for your organisation?

Microsoft has announced that Purview Data Governance will be retired in November 2027, with Microsoft Fabric OneLake Catalog becoming its strategic solution for data governance.

For organisations already using Purview, this raises some important questions. What happens to existing governance capabilities? Will everything move across to OneLake Catalog? And what if you’re not currently using Microsoft Fabric?

The direction Microsoft is taking makes sense. Bringing governance closer to the data platform should make it easier to manage data consistently, particularly as organisations introduce more AI capabilities.

However, OneLake Catalog isn’t necessarily a like-for-like replacement for everything organisations are using today. The implications will depend on your existing data architecture, the capabilities you rely on and how governance operates across your organisation.

Here are some of the key questions worth considering.

Is Microsoft Purview disappearing?

No. It’s important to distinguish between Purview Data Governance and Microsoft’s wider Purview portfolio.

The retirement specifically affects Purview Data Governance. Other capabilities, including Data Loss Prevention, Information Protection, Insider Risk Management and data security and compliance, will continue.

Microsoft is effectively separating where data is governed from how it’s protected. Fabric becomes the strategic platform for data governance, while Purview continues to focus on security and compliance.

When will Purview Data Governance be retired?

Microsoft has confirmed that support will end on 12 November 2027, giving organisations a year to prepare.

For some, the transition may be relatively straightforward. For others, particularly those with complex data estates, established governance processes or regulatory requirements, there could be more work involved.

The important thing is to understand the scale of the change early, rather than treating November 2027 as the point at which planning needs to begin.

Microsoft is also advising customers in highly regulated industries or with contractual obligations to engage with their Microsoft account teams early.

Can we simply migrate everything to OneLake Catalog?

Not necessarily, and this is probably one of the first things organisations should assess.

OneLake Catalog already provides a range of capabilities covering data discovery, governance, security and protection. However, it doesn’t necessarily provide a direct replacement for every capability currently available in Purview Data Governance.

For example, organisations should look carefully at connector coverage, data quality, governance workflows and stewardship processes.

Some capabilities are already available, others are on Microsoft’s roadmap, and some requirements may need a different approach or additional tools.

The impact will depend on how you’ve implemented Purview, the data sources you’re governing and the processes you’ve built around it.

For organisations operating across multiple platforms, or using federated governance models where different teams have responsibility for their own data, there may be additional architectural considerations.

The sensible starting point is to map what you’re currently using against what’s available in OneLake Catalog today, rather than designing a transition around functionality that may arrive later.

Will moving to OneLake Catalog cost more?

Potentially not. In fact, there may be opportunities to simplify costs.

Purview Data Governance has historically had its own consumption-based pricing model. Microsoft’s approach brings OneLake Catalog governance capabilities into the Fabric capacity model.

For organisations already using Fabric alongside Purview, this could simplify the overall architecture and licensing arrangements.

However, the financial impact will depend on existing capacity, usage patterns and governance requirements. Organisations should review their current costs and expected Fabric capacity needs before assuming the transition will deliver savings.

What if we’re not currently using Microsoft Fabric?

You don’t necessarily need to migrate your entire data platform to Fabric to use OneLake Catalog.

Microsoft supports governance across data held outside Fabric through capabilities such as shortcuts, mirroring and supported connectors. This means organisations can connect data from Azure and other platforms without necessarily moving or copying it into OneLake.

That’s an important distinction, particularly for organisations with established data platforms or hybrid environments.

However, it doesn’t mean every existing data source and governance requirement will automatically be supported.

Organisations will need to assess how OneLake Catalog fits into their current architecture, which connections are available and whether the governance capabilities meet their needs.

Moving to Fabric as a data platform is a significant decision. It shouldn’t become an automatic consequence of a change to Microsoft’s governance tooling.

Why is Microsoft making this change?

Microsoft’s wider direction has been towards a more unified data platform, with Fabric bringing together data engineering, analytics, reporting and increasingly AI capabilities.

Governance is becoming a more significant part of that platform.

Historically, managing governance through separate tools could introduce additional complexity, particularly where organisations needed to maintain policies, metadata and lineage across different systems.

Bringing those capabilities closer to where data is used should help reduce some of that complexity.

There’s also an important connection to AI. As organisations introduce Copilot and AI agents, they need to understand which data those systems can access, what that data means and whether it can be trusted.

But the technology alone won’t solve those challenges.

Organisations still need clearly defined data ownership, accountability, policies and processes. Those fundamentals remain important regardless of which platform provides the governance capabilities.

What should organisations be doing now?

The first step is to understand what the announcement means for your existing environment.

Oakland suggests focusing on three areas:

Microsoft Fabric is developing quickly, and the governance capabilities available today will continue to evolve. That makes it important to keep track of the roadmap while making decisions based on what your organisation actually needs.

Looking ahead

Bringing governance into Fabric is a logical step in Microsoft’s wider platform strategy, and it creates opportunities to simplify how organisations manage and use their data.

But the transition needs to be considered in the context of each organisation’s existing environment.

For some, it may provide an opportunity to consolidate tooling and improve how governance operates. For others, particularly those with complex or federated data estates, the changes may require more careful planning.

The priority should be understanding the implications now, identifying where changes are needed and making sure the future approach to governance supports the way the organisation actually works.

At Oakland, we’re reviewing Microsoft’s transition guidance and the implications for organisations using Purview Data Governance. If you’d like to discuss how these changes could affect your existing environment, get in touch with our Microsoft Data & AI team.

Source: Microsoft: A next step in the evolution of the Microsoft Data Governance strategy, 12 November 2026.