---
title: "Microsoft Fabric vs Purview: What Each One Does | Dawiso"
description: "Microsoft Fabric vs Purview explained: an analytics platform and a security and compliance suite, and what changes as Purview Data Governance retires."
url: "https://www.dawiso.com/glossary/microsoft-fabric-vs-purview"
language: "en"
---

November 19, 2026

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](https://www.dawiso.com/glossary/onelake-catalog) compares with the Purview Unified Catalog. For the object-by-object move, see [Purview to Fabric](https://www.dawiso.com/glossary/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](https://www.dawiso.com/glossary/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](https://techcommunity.microsoft.com/blog/microsoft-security-blog/a-next-step-in-the-evolution-of-the-microsoft-data-governance-strategy/4572227) 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](https://learn.microsoft.com/en-us/purview/purview) 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](https://learn.microsoft.com/en-us/purview/data-governance-billing) and in our [Purview pricing guide](https://www.dawiso.com/glossary/microsoft-purview-pricing).

## What changes with the Purview Data Governance retirement?

On November 12, 2026, Microsoft [announced](https://techcommunity.microsoft.com/blog/microsoft-security-blog/a-next-step-in-the-evolution-of-the-microsoft-data-governance-strategy/4572227) 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](https://learn.microsoft.com/en-us/partner-center/announcements/2026-november) lists what retires: the Unified Catalog, Data Map, Workflows and the Microsoft Azure Purview solutions. The [Unified Catalog page on Microsoft Learn](https://learn.microsoft.com/en-us/purview/unified-catalog) 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](https://www.dawiso.com/blog-post/microsoft-purview-data-governance-retirement).

## How do Fabric and Purview work together?

Microsoft's [transition guidance](https://techcommunity.microsoft.com/blog/analyticsonazure/from-purview-data-governance-to-the-fabric-onelake-catalog/4573422) 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](https://learn.microsoft.com/en-us/fabric/governance/microsoft-purview-fabric) 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](https://www.dawiso.com/microsoft-purview-alternative)

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.

| Aspect | OneLake catalog | Unified Catalog |
| --- | --- | --- |
| Scope | Fabric items, including data brought into OneLake through shortcuts or mirroring | Sources registered and scanned in the Purview Data Map, inside and outside Azure |
| Business glossary | No glossary object described; terms map to tags, descriptions and endorsement, and Microsoft advises not to claim full glossary parity | Glossary terms and critical data elements, with policies attached |
| Data products | Domains, endorsement, sharing and discoverable semantic models; contract, lifecycle and access process defined elsewhere where needed | Data products with access policies and self-service access requests |
| Data quality | Freshness and curation insights in Govern; in Microsoft's words, not a rules, profiling and scoring engine | Data quality rules and scores at asset, data product and domain level |
| External sources | Not an inventory of every external source; "data connectivity is not enterprise metadata scanning" | Scanned through the Data Map |
| Pricing model | Included in Fabric capacity | Pay-as-you-go per governed asset per day, plus processing units for data quality |
| Status | Microsoft's data governance solution going forward | Maintenance 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](https://www.dawiso.com/glossary/purview-to-fabric), and how to export the glossary is in [Purview glossary migration](https://www.dawiso.com/glossary/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](https://www.dawiso.com/glossary/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](https://www.dawiso.com/glossary/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](https://www.dawiso.com/connectors/microsoft-fabric) and [Power BI](https://www.dawiso.com/connectors/power-bi) together with [Databricks](https://www.dawiso.com/connectors/databricks), [Snowflake](https://www.dawiso.com/connectors/snowflake) and other platforms, and adds a [business glossary](https://www.dawiso.com/product/business-glossary) with approval workflows and [data products](https://www.dawiso.com/product/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](https://www.dawiso.com/microsoft-purview-alternative) page for details.

## Sources

- Microsoft Learn - [What is Microsoft Fabric](https://learn.microsoft.com/en-us/fabric/fundamentals/microsoft-fabric-overview)
- Microsoft Learn - [Learn about Microsoft Purview](https://learn.microsoft.com/en-us/purview/purview)
- Microsoft Learn - [OneLake catalog overview](https://learn.microsoft.com/en-us/fabric/governance/onelake-catalog-overview)
- Microsoft Learn - [Use Microsoft Purview with Microsoft Fabric](https://learn.microsoft.com/en-us/fabric/governance/microsoft-purview-fabric)
- Microsoft Learn - [Learn about Microsoft Purview Unified Catalog](https://learn.microsoft.com/en-us/purview/unified-catalog)
- Microsoft Learn - [Billing in Microsoft Purview Data Governance](https://learn.microsoft.com/en-us/purview/data-governance-billing)
- Microsoft Security Community Blog - [A next step in the evolution of the Microsoft Data Governance strategy](https://techcommunity.microsoft.com/blog/microsoft-security-blog/a-next-step-in-the-evolution-of-the-microsoft-data-governance-strategy/4572227) (November 12, 2026)
- Microsoft Partner Center - [November 2026 announcements](https://learn.microsoft.com/en-us/partner-center/announcements/2026-november)
- Microsoft Analytics on Azure Blog - [From Purview Data Governance to the Fabric OneLake Catalog](https://techcommunity.microsoft.com/blog/analyticsonazure/from-purview-data-governance-to-the-fabric-onelake-catalog/4573422) (November 13, 2026, updated November 16, 2026)
- Dawiso Help - [Microsoft Fabric](https://help.dawiso.com/actual/microsoft-fabric/)

[See it in action](https://www.dawiso.com/microsoft-purview-alternative)

Moving off Purview Data Governance?

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

### Table of contents

What is Microsoft Fabric?What is Microsoft Purview?What changes with the Purview Data Governance retirement?How do Fabric and Purview work together?OneLake catalog vs Purview Unified CatalogWhen does a platform-independent catalog make sense?Sources

## Related Terms

### [What Is the Microsoft Purview Unified Catalog?](https://www.dawiso.com/glossary/microsoft-purview-unified-catalog)

The Microsoft Purview Unified Catalog explained: domains, data products, CDEs, how it differs from the Data Map, and what its retirement means for you.

Read more →

### [Is There a Microsoft Purview Migration Tool?](https://www.dawiso.com/glossary/microsoft-purview-migration-tool)

There is no Microsoft Purview migration tool for leaving Purview Data Governance. See what the three Purview migration tools do and how to export your content.

Read more →

### [Purview Glossary Migration: How to Move Your Terms](https://www.dawiso.com/glossary/purview-glossary-migration)

Purview glossary migration step by step: classic vs Unified Catalog terms, how to export them, what gets lost and how fields map to Fabric or a data catalog.

Read more →

### [Purview to Fabric: Mapping Data Governance to OneLake](https://www.dawiso.com/glossary/purview-to-fabric)

Purview to Fabric mapped object by object: what moves to the OneLake catalog, what is partial or missing, what stays in Purview and how to move in waves.

Read more →

### [Purview Role Migration After the Retirement](https://www.dawiso.com/glossary/purview-role-migration)

Purview role migration explained: what the Role Assignment Migrator does, and how Unified Catalog and Data Map roles map to Fabric or a data catalog.

Read more →

### [Microsoft Purview Pricing for Data Governance Explained](https://www.dawiso.com/glossary/microsoft-purview-pricing)

Microsoft Purview pricing: governance is billed per asset until it retires in 2027, security per user via Microsoft 365. Rates, examples and E5 answers.

Read more →
