Insight · Microsoft Fabric

    Microsoft Purview Data Governance Is Retiring: What Moves to the OneLake Catalog

    Microsoft is retiring Purview Data Governance, including the Unified Catalog and Data Map, with end of support on 12 November 2027. What is affected and how to move to the OneLake catalog.

    Nick de Vrye, CTOPublished 18 November 20265 min readMore on Data governance and security
    Navy Solv Systems title card reading 'Purview Data Governance retiring', with the Microsoft Purview icon at the centre of a hub of Microsoft product icons: Microsoft Fabric, Power BI, Azure SQL Database, Entra ID, Azure Data Factory and Key Vault.

    In Short: What Is Retiring?

    On 12 November 2026, Microsoft announced that Microsoft Purview Data Governance is being retired, with end of support by 12 November 2027. The retirement covers four solutions:

    • Unified Catalog
    • Data Map
    • Workflows
    • Microsoft Azure Purview (the classic solutions)

    Microsoft is directing data governance to the OneLake catalog in Microsoft Fabric. Purview's data security and compliance products are not affected. In Microsoft's words: "Purview Data Security and Compliance offerings are unchanged."

    If you use Unified Catalog or Data Map today, you have roughly 12 months to decide where your catalog, glossary and lineage will live.

    What Is Not Changing

    Purview covers two very different things, and only one is retiring. The data security and compliance side carries on as before:

    • Sensitivity labels and their inheritance into Fabric and Power BI
    • Data loss prevention (DLP), including DLP for Fabric
    • Insider risk management and communication compliance
    • Data Security Posture Management, including DSPM for AI
    • Audit, eDiscovery and retention

    If your Purview use is mostly labels and DLP, as it is for many Power BI estates, this retirement barely touches you. Microsoft also announced new Purview data security capabilities in preview at Ignite 2026, which is a clear signal that side of the product is still growing.

    Why Microsoft Is Doing This

    Microsoft has spent two years building governance into Fabric itself: the OneLake catalog and its Govern experience, domains, endorsement, lineage, sensitivity label inheritance and, more recently, Fabric Policies. Running a second catalog in Purview alongside that created overlap and confusion for customers. Consolidating governance into OneLake gives one catalog for data that Fabric, Power BI, Copilot and Fabric IQ all read.

    The trade-off is scope. Data Map was built to scan sources across Azure, on-premises and other clouds. The OneLake catalog governs what is in Fabric and OneLake. Data that stays outside Fabric is the main thing to plan for.

    What Moves Where

    Microsoft's guidance, From Purview Data Governance to the Fabric OneLake catalog, sets out the migration approach. In outline:

    • Data assets and lineage: for Fabric items, the OneLake catalog already holds them. For external sources, bring the data into OneLake with mirroring or shortcuts so it can be governed there.
    • Business domains and data products: map Unified Catalog governance domains to Fabric domains and data products to endorsed, documented Fabric items.
    • Ownership and stewardship: record owners and contacts on Fabric items and domains.
    • Access policies: move towards Fabric workspace roles, OneLake security and Fabric Policies. Some of these, including Fabric Policies, are still in preview, so check the status of each before you depend on it.
    • Workflows: there is no like-for-like replacement named in the announcement. Approval steps may need to move to Power Automate or your service desk.

    The OneLake catalog's Govern experience and DLP restrict-access for Fabric are generally available, so the core of the destination is production-ready.

    A 12-Month Plan

    Months 1 to 2: inventory. List every registered source and scan in Data Map, every glossary term, data product, owner and workflow in Unified Catalog, and who actually uses them. Many organisations find the catalog is used by a handful of people.

    Months 2 to 3: map and find gaps. Mark each item as already in Fabric, movable into OneLake, or outside Fabric with no obvious home. The third list is the one that needs decisions.

    Months 3 to 9: build the target. Set up domains, endorsement, ownership and sensitivity labels in Fabric. Bring priority external sources into OneLake. Rebuild the glossary where people will see it, in the OneLake catalog and in semantic model descriptions that Copilot reads.

    Months 9 to 12: switch over and retire. Point users to the OneLake catalog, stop scans, and export anything you need to keep before end of support on 12 November 2027.

    Do not leave this to the last quarter. Governance migrations are mostly about people and agreed definitions, not tooling, and those take time.

    What This Means for Your Governance Framework

    The principles in our data governance framework do not change: clear ownership, agreed definitions, access by role, and quality checks where data enters. What changes is where they are recorded. For Fabric customers the OneLake catalog becomes the single place, which is simpler than keeping Purview and Fabric in step.

    For organisations with large estates outside Fabric, such as many on-premises databases or other clouds, the question is harder: how much of that estate should move into OneLake, and what governs the rest. That decision is worth making deliberately in the first quarter of the plan.

    Sources and Further Reading

    Frequently asked

    Only part of it. Microsoft is retiring Purview Data Governance, which covers the Unified Catalog, Data Map, Workflows and the classic Microsoft Azure Purview solutions. Purview's data security and compliance products, such as sensitivity labels, data loss prevention and insider risk management, are unchanged.

    Microsoft announced the retirement on 12 November 2026, with end of support by 12 November 2027. That gives existing customers about 12 months to plan and complete a move.

    Microsoft is directing data governance to the OneLake catalog in Microsoft Fabric. The OneLake catalog's Govern experience is generally available, and Microsoft has published migration guidance, though some related Fabric governance features, such as Fabric Policies, are still in preview.

    Yes. Sensitivity labels, data loss prevention and other Purview data security and compliance features are not part of the retirement. Microsoft advises keeping them central to data security across Microsoft 365, Azure and Fabric.

    Take an inventory of what you actually use: registered sources and scans in Data Map, glossary terms, data products and owners in Unified Catalog, and any workflows. Then map each to its OneLake catalog equivalent and note gaps, especially sources outside Fabric.

    Potentially, yes. Data Map scans sources across Azure, on-premises and other clouds. The OneLake catalog governs data in Fabric and OneLake, so sources outside Fabric may need mirroring, shortcuts or another catalog. Check each source in your inventory against Microsoft's migration guidance.