When businesses think about Microsoft Purview, the chances are they think about sensitivity labels, data loss prevention and keeping Microsoft 365 data compliant. But Purview has also had a second job: helping data teams find, describe and govern data across the business.

On 12 November 2026, Microsoft announced that this second job is moving home, into Microsoft Fabric, with the OneLake catalog becoming the single place to govern data across your organisation. 

If you use Microsoft Purview to protect your Microsoft 365 data, the good news is that your day-to-day tools aren’t going anywhere. If your data team uses Purview’s data catalogue, there’s a year to plan the move, and some real benefits waiting on the other side. 

In this blog, Paul Westlake, Senior Purview Consultant at Arc, explains what’s changing, why it’s good news for most organisations, and what to do if your data team relies on Purview today. 

What has Microsoft announced? 

In its announcement, Microsoft confirmed that Microsoft Fabric is now its data governance solution. The headline points are: 

  • The OneLake catalog in Fabric is the new home for data governance. It becomes the single foundation for governing data across your estate. 
  • Purview Data Governance will retire. This is the catalogue side of Purview, used by data teams to find, describe and curate data. Support ends on 12 November 2027. 
  • Transition support starts now. Microsoft says detailed transition guidance is already available, and it’s helping existing customers move to Fabric. 
  • Purview’s security and compliance tools are unaffected. Microsoft says Purview stays focused on protecting data and keeping you compliant. 

Microsoft also asks customers with contractual obligations, and those in highly regulated industries, to speak to their Microsoft account team early, as these situations will be assessed individually. 

Why this is good news for data teams 

Until now, many organisations have built their data in one product and governed it in another. Microsoft says customers have been clear that this slows them down, because every policy, label and lineage update has to bridge two systems. Bringing governance into Fabric keeps it alongside the data and the people who use it. 

The benefits Microsoft describes include: 

  • Governance where the work happens. Policies, lineage and data ownership sit next to the data itself, instead of in a separate tool. 
  • Ready for AI. The same permissions, sensitivity labels and lineage that govern your data also govern how AI agents use it, which matters as more organisations adopt Copilot and agents. 
  • Reach beyond Fabric. Through shortcuts, mirroring and supported connectors, the OneLake catalog can govern data in Azure and third-party sources without copying or moving it. 
  • Simpler billing. Governance is included in Fabric capacity, rather than billed through separate meters. 
  • Easier access for everyone. The OneLake catalog is built into apps people already use, including Teams and Excel. 

The OneLake catalog itself is organised into three tabs: Explore for finding data, Govern for checking its health and quality, and Secure for managing who has access (OneLake catalog overview). Helpfully, the Govern tab already shows Purview sensitivity label and data loss prevention (DLP) coverage, so security and governance teams can see the same picture. 

And if your needs go beyond what Fabric offers today, Microsoft says Fabric also integrates with third-party catalogues including Atlan, Alation, Collibra and Informatica. 

Your Purview protection stays put 

For most of the organisations we work with, Purview means protecting Microsoft 365 data: sensitivity labels, DLP policies and the compliance tools that keep you audit-ready. That doesn’t change. 

Microsoft is drawing a clearer line between protecting data and governing it. Purview stays focused on data security and compliance: classifying, labelling and protecting sensitive data, and preventing data loss across your estate and AI. Microsoft says it will keep investing in these capabilities, and that they’ll continue to work with Microsoft 365, Azure and Fabric just as they do today. 

So if you’ve implemented Microsoft Purview to protect your emails, Teams chats and SharePoint files, there’s nothing you need to do as a result of this announcement. 

A quick bit of history 

There’s a nice twist here. The name Purview actually came from the data governance side. Azure Purview was Microsoft’s data governance service, and in April 2022 Microsoft brought it together with its Microsoft 365 compliance tools under one brand: Microsoft Purview (Microsoft Azure blog). 

So the part of Purview that’s moving to Fabric is the original Purview, and it leaves its name behind with the security and compliance tools that now carry it forward. 

Where this needs a reality check 

We’d rather be upfront about what isn’t clear yet. 

Microsoft’s announcement doesn’t say exactly what happens to existing catalogue content, such as glossary terms, data products and scan history, so don’t assume it will all move across on its own. 

The OneLake catalog is organised differently from Purview’s catalogue, so check that the features your data team relies on today are available in Fabric before you commit to a timeline. If something isn’t there yet, Microsoft points to third-party catalogues as an option. 

None of that is a reason to wait. It’s a reason to take stock now, while there’s a full year to work with. 

Who needs to act, and when? 

If your organisation uses Purview’s data governance features, such as Unified Catalog, the Data Map or a classic Azure Purview account, you have until 12 November 2027 to move. A year sounds like plenty of time, but catalogues tend to hold years of work, so it pays to start early. 

Here’s where we’d suggest you begin: 

  • Take stock of what you have. List your scanned data sources, glossary terms, data products, ownership records, and any scripts or integrations that rely on the catalogue. This tells you what to carry across, and what can be left behind. 
  • Agree who owns what. Decide which team looks after security and compliance in Purview and which looks after data governance in Fabric, and who owns the overlap between them. 
  • Check for hidden dependencies. Some organisations use the Data Map to extend sensitivity labels and protection policies to Azure data sources. Microsoft’s announcement doesn’t cover these scenarios yet, so check them against the transition guidance before you plan the move. 
  • Think about evidence. Catalogue information like ownership, classifications and lineage can form part of your audit trail. If you’re in a regulated sector, decide what needs to be kept, and for how long, before anything is retired. 
  • Talk to Microsoft early if you’re regulated. If you have contractual obligations or work in a highly regulated industry, Microsoft recommends engaging your account team now. 

Final thoughts

Microsoft’s commitment to data governance hasn’t changed, only where it lives. For most organisations that use Purview to protect Microsoft 365, nothing changes at all. For those with a data catalogue in Purview, there’s a year to plan a move that should leave governance closer to the data, easier to use and simpler to pay for. 

Whether you want to confirm this change doesn’t affect your Purview set-up, or you need help planning a move from Purview Data Governance to Fabric, our team can help. We’ll look at how you use Purview today, what depends on it, and what a smooth transition looks like for your organisation. 

New to Purview? Our free guide to our Microsoft Purview baseline packages is a good place to start. 

Talk to our team to get started today.