Data Estate Mappings — Align Business and Technical Architecture

Understand how Data Estate mappings connect Governance Domains to Data Map collections as architectural guidance without replacing technical permissions.

Data Estate mappings connect a Unified Catalog Governance Domain to a Data Map collection.

What the mapping does

The mapping guides Data Product Owners and Data Stewards toward the technical assets associated with their governance area.

What the mapping does not do

It does not grant Data Map access and it does not require the Governance Domain hierarchy to mirror the collection hierarchy.

Architecture use

Architects can use mappings to establish a controlled relationship between business governance boundaries and the technical estate. This is particularly useful when technical collections are structured around platforms, source systems or operational ownership while Governance Domains follow business functions or subject areas.

The mapping should therefore communicate architectural intent, while permissions remain managed through the Data Map access model.

Learning with Data SkyLab Studio

Follow practical Microsoft Purview and Data Governance learning from Data SkyLab Studio on YouTube.