Microsoft Purview Unified Catalog & Data Map Explained

How Unified Catalog and Data Map Work Together

Microsoft Purview Unified Catalog and Data Map support different parts of the same Data Governance journey.

Unified Catalog provides the business-facing governance and discovery experience. Data Map provides the technical metadata foundation underneath it.

They work together, but they are not the same thing.

Start with the Enterprise Data Catalogue

An Enterprise Data Catalogue (EDC) is a conceptual enterprise capability rather than the name of one specific product.

Depending on an organisation’s Enterprise Architecture, Microsoft Purview Unified Catalog and Data Map may provide much of that capability, or form part of a broader catalogue model alongside other platforms such as Azure Databricks Unity Catalog and AWS DataZone.

The important point is the capability: bringing technical metadata, business meaning, ownership, governance and discovery together so people can find and understand organisational data.

The Pyramid of Gascoigne Reference Metamodel

The Pyramid of Gascoigne is used in the video as a reference metamodel for explaining how the different Microsoft Purview capabilities fit together.

It is not a literal Microsoft Purview screen or product interface. It is a way of showing how the technical foundation at the bottom supports the business and consumer experience at the top.

Working from the top down, the model connects:

1. Unified Catalog
   The business-facing governance experience.
2. Discovery
   Data Products, Data Assets and the Enterprise Glossary help consumers find and explore governed information.
3. Governance Domains
   Business ownership, accountability and organisational governance boundaries.
4. Business Concepts
   Data Products, Glossary Terms, Objectives and Key Results (OKRs), and Critical Data Elements (CDEs) add business meaning and governance context.
5. Data Map
   The technical metadata foundation beneath Unified Catalog.
6. Collections
   Technical and administrative groupings used to organise the Data Map.
7. Registration of Data Sources
   Connecting and registering source systems so Purview knows where governed metadata can come from.
8. Scanning
   The foundation for ingesting supported metadata and making technical assets discoverable.

SCAN → REGISTER → ORGANISE → GOVERN → DISCOVER → UNDERSTAND → USE

Unified Catalog vs Data Map

Data Map supplies the technical metadata foundation. Unified Catalog turns governed metadata into a business-facing discovery and governance experience.

Governance Domains and Collections Are Different

One distinction in the model is between Governance Domains and Collections.

Governance Domains support business ownership, accountability and governance organisation within Unified Catalog.

Collections provide technical and administrative structure within Data Map.

They may be related within an organisation’s design, but they solve different problems and should not automatically be treated as the same hierarchy.

Finding the Right Data Product

The video then moves from architecture into a practical Data Consumer journey.

A consumer may not know the exact Data Product or technical asset name. They may simply know the business information they need.

Microsoft Purview Unified Catalog can support both keyword search and natural-language search, but the quality of the result depends heavily on the quality of the metadata and business context available.

Good search depends on good metadata.

Descriptions, Glossary Terms, ownership, business purpose and other contextual metadata make it easier for consumers to understand why a result is relevant rather than relying only on technical names.

Search Is Only the Beginning

Finding a result is not the end of the Data Consumer journey.

A useful catalogue experience should help the consumer:

1. Search for the information they need.
2. Find a relevant Data Product or Data Asset.
3. Review its purpose, metadata and business context.
4. Understand ownership, meaning and supporting governance information.
5. Assess whether the data is suitable for the intended purpose.
6. Access it through the appropriate governed process.
7. Use the underlying data with greater confidence.

SEARCH → FIND → REVIEW → UNDERSTAND → ASSESS → ACCESS → USE

Another Face of the Pyramid: Health Management

The video also uses another face of the Pyramid of Gascoigne to show that a catalogue must be actively managed after implementation.

Health Management provides oversight of the ongoing quality and operational health of the Unified Catalog experience.

The model groups this into areas such as:

• Controls — Actions, Reports, Data Observability, Process Automation and Workflows
• Data Quality — Scheduled Scans, Alerts, Connections, Monitoring and Settings

The message is that a trusted Enterprise Data Catalogue is not a one-off implementation. Metadata, ownership, quality and governance need continual management if the catalogue is to remain accurate and useful.

The Key Message

From scanning and technical metadata through to business meaning, governance and consumer discovery, Microsoft Purview Unified Catalog and Data Map work together to support an Enterprise Data Catalogue capability.

Data Map provides the technical metadata foundation. Unified Catalog provides the governed business-facing experience built on top of that foundation.

The Pyramid of Gascoigne is a reference metamodel for explaining that relationship. Actual implementation, terminology and the scope of an organisation’s Enterprise Data Catalogue will vary according to its Enterprise Architecture.

Pyramid of Gascoigne reference metamodel — Sasha Korniak.