---
title: "What Is the Microsoft Purview Unified Catalog? | Dawiso"
description: "The Microsoft Purview Unified Catalog explained: domains, data products, CDEs, how it differs from the Data Map, and what its retirement means for you."
url: "https://www.dawiso.com/glossary/microsoft-purview-unified-catalog"
language: "en"
---

November 19, 2026

purview unified catalogmicrosoft purview unified catalogpurview unified catalog vs data mappurview data catalog vs unified catalogpurview unified catalog permissionspurview unified catalog lineagepurview data governance retirement

# What Is the Microsoft Purview Unified Catalog?

**The Microsoft Purview Unified Catalog is the business layer of Purview Data Governance, with governance domains, data products and glossary terms on top of the Data Map, retiring with end of support on November 12, 2027.** No new accounts can be created, and existing ones stay in maintenance mode until then.

Many Purview customers know the Unified Catalog well but have never had to separate it from the Data Map underneath it or from the classic Data Catalog it replaced. That separation matters now, because each part has its own content, roles and migration path. This page explains what the Unified Catalog contains, how it relates to the Data Map, how permissions, lineage and billing work across the two, and what happens to your content as the product retires.

TL;DR

The **Unified Catalog** is where Purview customers organize data by **governance domains** and build **data products, glossary terms, critical data elements, OKRs, data quality rules and health controls**, with **self-service access requests**. It runs on the **Data Map**, which scans sources and holds technical assets, **collections**, classifications and **lineage**. Both are part of **Purview Data Governance**, which Microsoft is retiring: **no new accounts**, **maintenance mode until November 12, 2027**. Microsoft points customers to the **OneLake catalog in Microsoft Fabric**, which in its own transition guidance covers glossary terms, data products and lineage only in part, and data quality rules not at all. Sensitivity labels and DLP stay in Purview. Plan the move of your terms, data products and roles now.

## What is the Microsoft Purview Unified Catalog?

Microsoft's [Unified Catalog overview](https://learn.microsoft.com/en-us/purview/unified-catalog) describes it as a data governance platform in a single, integrated SaaS framework, and says Microsoft is working toward experiences for data consumers, data stewards and data owners in it. It is the part of Purview Data Governance that business users actually see. Its main building blocks:

- **Governance domains.** Boundaries that align the data estate to the organization, such as Marketing or Finance. Microsoft calls a domain "a mini catalog inside Unified Catalog". Terms, OKRs, data products and critical data elements are created inside a domain.
- **Data products.** Groups of related data assets, such as tables, files and Power BI reports, packaged for one use case so users find and request them together. See [what a data product is](https://www.dawiso.com/glossary/data-product).
- **Glossary terms.** Business vocabulary attached to data assets. In the Unified Catalog, terms can carry policies that flow down to the assets of a data product.
- **Critical data elements.** Logical groupings of important fields across the estate. Microsoft's example is a "Customer ID" element that maps CustID in one table and CID in another. See [critical data elements](https://www.dawiso.com/glossary/critical-data-elements).
- **OKRs.** Objectives and key results that link data products to business goals.
- **Health management.** Health controls that score the estate against governance standards, health actions that list concrete fixes, and ready-made reports.
- **Data quality.** No-code and low-code rules applied to columns, with scores rolled up to the asset, the data product and the governance domain, as described in the [data quality overview](https://learn.microsoft.com/en-us/purview/unified-catalog-data-quality).
- **Access policies and access requests.** Self-service requests for the data in a data product, approved against the policy attached to it.

## Unified Catalog vs Data Map

Purview Data Governance has two solutions in the Purview portal, the Data Map and the Unified Catalog. The [Data Map](https://learn.microsoft.com/en-us/purview/data-map) is, in Microsoft's words, "the foundation for data discovery and data governance in Microsoft Purview". It registers and scans sources across analytics, SaaS and operational systems, on-premises and in multiple clouds, and stores what it finds: schemas, columns, classifications, lineage and the descriptions added to them. Sources and assets are organized in Data Map [domains and collections](https://learn.microsoft.com/en-us/purview/data-map-domains-collections-manage), which also carry access control.

The Unified Catalog sits on top. It does not scan anything itself. Its data products, terms and critical data elements point to assets the Data Map already holds, which is why Microsoft's data quality workflow starts by registering and scanning a source in the Data Map before the asset can be added to a data product.

| Aspect | Unified Catalog | Data Map |
| --- | --- | --- |
| Role | Business layer: curate, describe and govern data for consumers | Technical layer: scan sources and store metadata |
| Main objects | Governance domains, data products, glossary terms, critical data elements, OKRs, data quality rules, health controls, access policies | Registered sources, scans, technical assets, classifications, lineage |
| Organized by | Governance domains | Data Map domains (a default domain plus up to four custom domains) and collections |
| Typical users | Domain owners, data stewards, data product owners, data consumers | Data source administrators, data curators, data readers |
| Permissions | Catalog-level and governance domain roles | Domain and collection roles, inherited by default |
| Billing | Governed assets per day, plus processing units for data quality and health | Capacity units on classic accounts; no Data Map or scan charges for Unified Catalog customers who consented or upgraded |
| Status | Retiring, maintenance mode until November 12, 2027 | Retiring, maintenance mode until November 12, 2027 |

### Unified Catalog vs the classic Data Catalog

Before the Unified Catalog, Purview customers worked in the classic Data Catalog in the classic Microsoft Purview governance portal, the experience that started as Azure Purview. It had its own glossary, organized by collections, with roles such as data curator and data reader. Microsoft's [billing documentation](https://learn.microsoft.com/en-us/purview/data-governance-billing) states that customers who did not consent to pay-as-you-go billing can still use the classic Data Catalog, and that Data Map assets remain intact either way. Classic glossary terms could be moved into the Unified Catalog through a preview migration flow, covered in [Purview glossary migration](https://www.dawiso.com/glossary/purview-glossary-migration). The retirement covers both: the Unified Catalog and the classic data governance capabilities formerly known as Azure Purview.

## How do Unified Catalog permissions, lineage and billing work?

**Permissions** span both layers. Microsoft's [roles documentation](https://learn.microsoft.com/en-us/purview/data-governance-roles-permissions) describes tenant role groups (Purview Administrators, Data Source Administrators, Data Governance), catalog-level roles such as Governance Domain Creator, Global Catalog Reader and Data Health Owner, and governance domain roles such as Governance Domain Owner, Data Steward, Data Product Owner and Data Quality Steward. Two details trip people up. A search in the Unified Catalog returns only assets the user can already see through Data Map permissions or Read access on the Azure or Fabric resource. And Data Product Owners and Data Stewards also need Data Map read permissions before they can add assets to a data product. How each role maps to Fabric or another catalog is covered in [Purview role migration](https://www.dawiso.com/glossary/purview-role-migration).

**Lineage** lives in the Data Map. Microsoft's [lineage documentation](https://learn.microsoft.com/en-us/purview/data-gov-classic-lineage) describes how the catalog connects to data processing, storage and analytics systems to extract lineage, at entity level and, where the source system supports it, at column level. In the Unified Catalog, lineage appears in the details of a data asset. See [data lineage](https://www.dawiso.com/glossary/data-lineage) for the general concept.

**Billing** follows the same split. The Unified Catalog charges per unique governed asset per day, meaning an asset linked to a governance concept such as a data product, a critical data element or a glossary term, counted once a day however many concepts it is linked to. Data quality and health management run on data governance processing units. On classic accounts the Data Map was billed in capacity units, each covering 25 operations per second and 10 GB of metadata. More detail and examples are in [Microsoft Purview pricing](https://www.dawiso.com/glossary/microsoft-purview-pricing).

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

Dawiso as a Microsoft Purview alternative

One data catalog across Microsoft Fabric and the platforms next to it, with a business glossary and data products your teams use.

## Is the Purview Unified Catalog retiring?

Yes. 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 support for Purview Data Governance ends on November 12, 2027. The [November 2026 partner notice](https://learn.microsoft.com/en-us/partner-center/announcements/2026-november) lists what is included: the Unified Catalog, Data Map, Workflows and the Azure Purview solutions. The banner now shown on the Unified Catalog pages of Microsoft Learn says new accounts can no longer be created and existing capabilities stay in maintenance mode through November 12, 2027.

Purview itself stays. Data security and compliance, including sensitivity labels, data loss prevention, audit and Insider Risk Management, are unchanged. Microsoft names Microsoft Fabric as its data governance solution, with the [OneLake catalog](https://www.dawiso.com/glossary/onelake-catalog) as the foundation, included in Fabric capacity. The wider picture is in [Microsoft Purview Data Governance is retiring](https://www.dawiso.com/blog-post/microsoft-purview-data-governance-retirement).

## What happens to Unified Catalog content?

Nothing moves on its own, and Microsoft names no migration tool for leaving Purview Data Governance. What each object becomes depends on where it goes. In Microsoft's [transition guidance](https://techcommunity.microsoft.com/blog/analyticsonazure/from-purview-data-governance-to-the-fabric-onelake-catalog/4573422) for the move to Fabric, as documented in November 2026:

- **Glossary terms and critical data elements** map to tags, descriptions and endorsement on Fabric items, a partial match. Microsoft's advice is to export and preserve terms and ownership. Details: [Purview glossary migration](https://www.dawiso.com/glossary/purview-glossary-migration).
- **Data products** map to domains, endorsement, sharing and discoverable semantic models, again partial. The contract, owner, lifecycle and access process need to be defined somewhere.
- **Governance domains** map to Fabric domains and subdomains, partial, with a responsibility matrix for stewardship duties that have no dedicated Fabric role. Details: [Purview role migration](https://www.dawiso.com/glossary/purview-role-migration).
- **Data quality rules and scores** have no rules engine in the OneLake catalog. Microsoft says governance health is not a rules, profiling and scoring engine.
- **Lineage** is partial: Fabric lineage covers supported Fabric items, and cross-system or granular lineage needs another method.
- **Data Map scanning of sources outside Fabric** has no equivalent. In Microsoft's words, "data connectivity is not enterprise metadata scanning".

To get the content out, the [Unified Catalog API](https://learn.microsoft.com/en-us/rest/api/purview/unified-catalog-api-overview), in public preview, lists and reads terms, data products, critical data elements and OKRs, and classic glossary terms can be exported to CSV. Which exports exist and what they miss is covered in [Is there a Microsoft Purview migration tool?](https://www.dawiso.com/glossary/microsoft-purview-migration-tool), and the full object-by-object mapping in [Purview to Fabric](https://www.dawiso.com/glossary/purview-to-fabric).

## Choosing a catalog after the Unified Catalog

The Unified Catalog was built around business use: domains owned by the business, data products people can request, a glossary with policies. Whatever replaces it should keep that, or the governance program loses the users it worked to win. For an estate that lives mostly in Fabric and Power BI, the OneLake catalog may be enough. When data also lives in Databricks, Snowflake, SAP or on-premises systems, or when the program runs on a business glossary and data products with owners, a catalog that is independent of any one data platform is the safer home. Definitions kept there do not have to move again the next time a vendor changes its strategy.

Dawiso is one such catalog. 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, with a [business glossary](https://www.dawiso.com/product/business-glossary) that has approval workflows and [data products](https://www.dawiso.com/product/data-products) with owners and access requests. There is no one-click Purview importer. The Dawiso customer success team migrates your terms, descriptions, data products and custom attributes, and critical data elements can be modeled as a custom object type. Data quality rules need a separate tool. Dawiso is available on Microsoft Marketplace and priced per user, and sensitivity labels and DLP stay in Purview. See the [Microsoft Purview alternative](https://www.dawiso.com/microsoft-purview-alternative) page.

## Sources

- Microsoft Learn - [Learn about Microsoft Purview Unified Catalog](https://learn.microsoft.com/en-us/purview/unified-catalog) (updated November 12, 2026)
- Microsoft Learn - [Microsoft Purview Data Map overview](https://learn.microsoft.com/en-us/purview/data-map)
- Microsoft Learn - [Manage domains and collections in Data Map](https://learn.microsoft.com/en-us/purview/data-map-domains-collections-manage)
- Microsoft Learn - [Data governance roles and permissions in Microsoft Purview](https://learn.microsoft.com/en-us/purview/data-governance-roles-permissions)
- Microsoft Learn - [Data lineage in classic Microsoft Purview Data Catalog](https://learn.microsoft.com/en-us/purview/data-gov-classic-lineage)
- Microsoft Learn - [Data quality in Microsoft Purview Unified Catalog](https://learn.microsoft.com/en-us/purview/unified-catalog-data-quality)
- Microsoft Learn - [Billing in Microsoft Purview Data Governance](https://learn.microsoft.com/en-us/purview/data-governance-billing)
- Microsoft Learn - [Unified Catalog API overview](https://learn.microsoft.com/en-us/rest/api/purview/unified-catalog-api-overview)
- 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)
- Dawiso Help - [Microsoft Fabric](https://help.dawiso.com/actual/microsoft-fabric/)

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

Planning life after the Unified Catalog?

Dawiso catalogs Microsoft Fabric together with Databricks, Snowflake and more, with a business glossary and data products on top.

### Table of contents

What is the Microsoft Purview Unified Catalog?Unified Catalog vs Data MapHow do Unified Catalog permissions, lineage and billing work?Is the Purview Unified Catalog retiring?What happens to Unified Catalog content?Choosing a catalog after the Unified CatalogSources

## Related Terms

### [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 →

### [Unity Catalog vs Microsoft Purview](https://www.dawiso.com/glossary/unity-catalog-vs-microsoft-purview)

Unity Catalog vs Microsoft Purview compared: scope, access control, lineage and pricing, and what the 2027 Purview Data Governance retirement changes.

Read more →

### [Microsoft Fabric vs Purview: What Each One Does](https://www.dawiso.com/glossary/microsoft-fabric-vs-purview)

Microsoft Fabric vs Purview explained: an analytics platform and a security and compliance suite, and what changes as Purview Data Governance retires.

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 →

### [What Is the OneLake Catalog?](https://www.dawiso.com/glossary/onelake-catalog)

The OneLake catalog is Microsoft Fabric's built-in catalog. Learn its Explore, Govern and Secure tabs, what it covers, its limits and its link to Purview.

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 →
