Skip to main content
microsoft fabric vs purviewfabric vs purviewonelake catalog vs purviewfabric catalog vs purviewpurview unified catalogpurview data governance retirement

Microsoft Fabric vs Purview: What Is the Difference?

Microsoft Fabric is a data and analytics platform, and Microsoft Purview is a family of data security, compliance and, until November 12, 2027, data governance solutions. They solve different problems, which is why most Microsoft customers use both.

The question "Fabric vs Purview" became pressing on November 12, 2026, when Microsoft announced that Purview Data Governance is retiring and that Fabric is now its data governance solution. This page explains what each product does, what the retirement changes, how the two work together on Fabric data, and how the OneLake catalog compares with the Purview Unified Catalog. For the object-by-object move, see Purview to Fabric.

TL;DR

Microsoft Fabric is where data is stored, processed and reported on: OneLake, workloads such as Data Factory, Data Warehouse and Power BI, and the OneLake catalog for discovering and governing Fabric items. Microsoft Purview protects and monitors data: sensitivity labels, DLP, audit and Insider Risk Management. Its data governance part, the Unified Catalog and Data Map, is in maintenance mode and reaches end of support on November 12, 2027. After that, Microsoft's split is simple: the OneLake catalog governs Fabric data, Purview secures it. Data outside Fabric, a business glossary and data quality rules have no full Fabric equivalent, which is where a platform-independent data catalog comes in.

What is Microsoft Fabric?

Microsoft Learn describes Microsoft Fabric as "an analytics platform that supports end-to-end data workflows", from ingestion and transformation to real-time processing, analytics and reporting. It is delivered as software as a service, so there is no infrastructure to provision.

  • OneLake is the storage layer: one logical data lake per tenant, built on Azure Data Lake Storage Gen2, which every workload reads and writes. Shortcuts reach data in Azure Data Lake Storage, Amazon S3 and Google Cloud Storage without copying it, and mirroring replicates sources such as Azure SQL Database, Azure Databricks and Snowflake into OneLake.
  • Workloads cover the roles that work with data: Data Factory, Data Engineering, Data Science, Data Warehouse, Databases, Real-Time Intelligence, Power BI and Fabric IQ (its ontology item in preview).
  • The OneLake catalog is the governance and discovery layer. It has three experiences: Explore to find and understand Fabric items, Govern for governance insights, recommended actions, domains, endorsement and policies, and Secure for workspace roles and OneLake security roles. It is also embedded in Teams, Excel and Copilot Studio, and exposed through the Catalog Search REST API.

Fabric is billed through capacity, and the retirement announcement states that OneLake catalog governance is included in Fabric capacity rather than billed through separate meters.

What is Microsoft Purview?

Microsoft Purview is a product family. In Microsoft's words, it is "a comprehensive set of solutions that helps your organization govern, protect, and manage data". The Purview overview on Microsoft Learn groups them into three areas:

  • Data security: Information Protection (sensitivity labels), Data Loss Prevention, Insider Risk Management, Information Barriers, Data Security Investigations and Privileged Access Management.
  • Data compliance: Audit, eDiscovery, Communication Compliance, Compliance Manager, Data Lifecycle Management and Records Management.
  • Data governance: the Data Map, which scans and inventories data sources, and the Unified Catalog, with governance domains, glossary terms, critical data elements, data products, OKRs, health management and data quality rules. This area grew out of Azure Purview.

The security and compliance solutions are mostly licensed per user through Microsoft 365, while data governance is billed pay-as-you-go through an Azure subscription, per governed asset per day plus processing units for data quality and health checks, as described in Microsoft's billing documentation and in our Purview pricing guide.

Microsoft Fabric vs Purview MICROSOFT FABRIC VS PURVIEW MICROSOFT FABRIC Data and analytics platform Workloads and Fabric items Data Factory, Warehouse, lakehouses, Power BI OneLake One logical data lake per tenant OneLake catalog Explore, Govern, Secure for Fabric items MICROSOFT PURVIEW Security, compliance and governance solutions Data security Sensitivity labels, DLP, Insider Risk Data compliance Audit, eDiscovery, Compliance Manager Data governance (retiring) Unified Catalog, Data Map, end of support Nov 12, 2027 Labels, DLP and audit Microsoft's path Based on Microsoft Learn and Microsoft's retirement announcement, November 2026
Click to enlarge

What changes with the Purview Data Governance retirement?

On November 12, 2026, Microsoft announced that "Microsoft Fabric is now our data governance solution" and that support for Purview Data Governance will end on November 12, 2027. The November 2026 partner notice lists what retires: the Unified Catalog, Data Map, Workflows and the Microsoft Azure Purview solutions. The Unified Catalog page on Microsoft Learn adds that no new accounts can be created and that existing capabilities stay in maintenance mode until that date.

What does not change is the rest of Purview. In the announcement's words, "Microsoft Purview stays focused on data security and compliance". Sensitivity labels, DLP, audit, Insider Risk Management and eDiscovery continue as before, and the partner notice confirms that the security and compliance offerings are unchanged.

So the Fabric vs Purview question used to have three answers and now has two. Before the retirement, a Microsoft customer could run governance in the Purview Unified Catalog, in the OneLake catalog, or in both. From November 2027, Microsoft's own governance answer is the OneLake catalog, and Purview is the security and compliance layer around it. The wider decision is covered in Microsoft Purview Data Governance is retiring.

How do Fabric and Purview work together?

Microsoft's transition guidance gives a rule of thumb: use the OneLake catalog to discover, understand and govern Fabric data, OneLake security and Fabric controls to enforce access, and Microsoft Purview to classify, protect, monitor, investigate and demonstrate compliance. The Fabric documentation on Purview lists the integrations available today:

  • Information Protection. Sensitivity labels can be set on all Fabric items, and data stays protected when it is exported through supported export paths.
  • Data loss prevention. DLP policies cover structured data in Fabric, such as lakehouses, warehouses, databases and semantic models, and can show policy tips and raise alerts when sensitive data is detected.
  • Audit. All Fabric user activities are logged in the Purview audit log.
  • Insider Risk Management. Ready-to-use risk indicators cover Fabric activity, such as Power BI and lakehouse activities.
  • AI governance. Purview controls cover supported Fabric Copilots and agents, including audit of AI interactions.

Two practical points follow. First, labels and DLP on Fabric items require Purview licensing, according to the transition guidance, so Fabric capacity alone does not cover them. Second, as Microsoft's documentation puts it, using Purview "doesn't change where Fabric governance lives". Discovery, domains, endorsement and lineage for Fabric items sit in the OneLake catalog, not in Purview.

See it in action

Dawiso as a Microsoft Purview alternative

A data catalog across Microsoft Fabric and the platforms next to it, with a business glossary the business actually uses.

OneLake catalog vs Purview Unified Catalog

When people compare Fabric and Purview for governance, they usually mean two catalogs: the OneLake catalog in Fabric and the Unified Catalog in Purview. The table compares them as documented in November 2026. The OneLake catalog column follows Microsoft's transition guidance, which maps several Unified Catalog objects to Fabric only in part.

AspectOneLake catalogUnified Catalog
ScopeFabric items, including data brought into OneLake through shortcuts or mirroringSources registered and scanned in the Purview Data Map, inside and outside Azure
Business glossaryNo glossary object described; terms map to tags, descriptions and endorsement, and Microsoft advises not to claim full glossary parityGlossary terms and critical data elements, with policies attached
Data productsDomains, endorsement, sharing and discoverable semantic models; contract, lifecycle and access process defined elsewhere where neededData products with access policies and self-service access requests
Data qualityFreshness and curation insights in Govern; in Microsoft's words, not a rules, profiling and scoring engineData quality rules and scores at asset, data product and domain level
External sourcesNot an inventory of every external source; "data connectivity is not enterprise metadata scanning"Scanned through the Data Map
Pricing modelIncluded in Fabric capacityPay-as-you-go per governed asset per day, plus processing units for data quality
StatusMicrosoft's data governance solution going forwardMaintenance mode, end of support November 12, 2027

The short version: the OneLake catalog is the stronger fit for data that lives in Fabric and costs nothing extra, while the Unified Catalog carried the business-facing objects, glossary, data products and quality rules, across a wider estate. Those objects are the ones Purview customers have to find a new home for. How each one maps is in Purview to Fabric, and how to export the glossary is in Purview glossary migration.

When does a platform-independent catalog make sense?

For a small estate that lives in Fabric and Power BI, run by a few data engineers, Fabric plus Purview security covers a lot: the OneLake catalog for discovery and governance, Purview for labels, DLP and audit. A platform-independent data catalog next to Fabric makes sense in three situations:

  • Data beyond Fabric. When Databricks, Snowflake, SAP or on-premises systems stay where they are, the OneLake catalog does not inventory them, and Microsoft's own guidance calls for a bridge or partner approach for sources it does not cover.
  • A business glossary used by the business. If definitions, owners and approvals are how the business finds and trusts data, tags and descriptions on Fabric items are a step down from a business glossary with owners and workflows.
  • Governance at scale. Many domains, stewards and data products need roles, approvals and a data product lifecycle in one place. Microsoft's announcement itself says Fabric integrates with third-party governance providers, so customers can choose what works best for them. A catalog that is independent of any one platform also does not have to move the next time a vendor changes its strategy, and long-standing Purview customers have already moved once, from Azure Data Catalog.

Dawiso works as that layer next to Fabric and Purview. It catalogs Microsoft Fabric and Power BI together with Databricks, Snowflake and other platforms, and adds a business glossary with approval workflows and data products on top. Labels, DLP and audit stay in Purview. Dawiso is available on Microsoft Marketplace and priced per user, and its customer success team helps move glossary terms, descriptions, data products and custom attributes out of Purview. See the Microsoft Purview alternative page for details.

Sources

See it in action

Moving off Purview Data Governance?

Dawiso catalogs Microsoft Fabric together with Databricks, Snowflake and other platforms, with a business glossary on top.

A cookie a day keeps bad UX away.

We use cookies to personalize content, ads and to analyze our traffic. We also share information about your use of our site with our advertising and analytics partners who may combine it with other information that you've provided to them or that they've collected from your use of their services. By clicking "Accept All", you allow us to use cookies for analytics and ads via Google Tag Manager. You can also customize cookies.

Customize Consent Preferences

We use cookies to personalize content, ads and to analyze our traffic. We also share information about your use of our site with our advertising and analytics partners. Privacy Policy

Necessary cookies allow core website functionality such as user login and account management. The website cannot be used properly without strictly necessary cookies.

Functionality cookies are used to remember visitor information on the website, eg. language, timezone, enhanced content.

Analytics cookies are used to see how visitors use the website, eg. analytics cookies. Those cookies cannot be used to directly identify a certain visitor.

We use Microsoft Clarity to see how you use our website (including heatmaps and session replays) so we can improve it. By using our site, you agree that we and Microsoft can collect and use this data. See our Privacy Policy for details.

Advertisement cookies are used to identify visitors between different websites, eg. content partners, banner networks. Those cookies may be used by companies to build a profile of visitor interests or show relevant ads on other websites.