Microsoft Purview for Data Architects

Start Here

Begin with the core concepts, roles and responsibilities that shape this Microsoft Purview learning journey.

Discover

Explore the Microsoft Purview structures, information and capabilities most relevant to this role.

Business and Technical Metamodels in Microsoft Purview

Learn how Microsoft Purview separates business governance concepts from the technical asset model and how architecture connects the two.

Data Map Sources, Collections and Technical Assets

Learn how registered sources, collections and scanned technical assets fit together in Microsoft Purview Data Map.

Governance Domains, Data Map Domains and Collections — Different Boundaries

Understand why Unified Catalog Governance Domains and Data Map domains or collections serve different architectural purposes and should not automatically mirror each other.

Governance Domain Types

Understand the five Microsoft Purview Governance Domain types and how to choose the right descriptor for a business-aligned governance boundary.

Data Products and Data Assets — Logical to Physical Architecture

Learn how data products provide a logical consumer-facing use case while Data Map assets represent the underlying physical or platform-specific data.

Federated Governance Operating Model

Understand central, domain and shared decision rights in a federated governance operating model, including how Governance Domain design should follow ownership policy.

Data Mesh and Governed Data Democratisation

Understand how federated Data Governance supports data mesh principles and governed data democratisation without treating either as unrestricted decentralisation or open access.

Understand

Build practical understanding of the tasks, decisions and governance responsibilities this role performs in Microsoft Purview.

Microsoft Purview Unified Catalog: Enterprise and Local Glossary Terms Governance Model

Read a practical Microsoft Purview Unified Catalog model for adding semantic business meaning to technical metadata, governing enterprise and local terminology, and reusing authoritative Glossary Terms at scale.

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.

Lineage as Architectural Evidence

Understand how architects use Microsoft Purview lineage for dependency analysis, impact assessment and provenance while accounting for connector coverage and gaps.

Purview and Platform Catalogues — Azure Databricks Unity Catalog

Understand how Microsoft Purview can sit above or alongside platform catalogues such as Azure Databricks Unity Catalog in a wider enterprise governance architecture.

Technical Lineage and Lineage Completeness

Understand how technical lineage reaches Microsoft Purview and why complete source coverage matters when consumers rely on lineage evidence.

Azure Databricks Unity Catalog Scanning

Learn the key Microsoft Purview considerations for scanning Azure Databricks Unity Catalog metadata, scope and lineage.

Microsoft Purview Alignment for Federated Governance

Map the federated governance operating model to Microsoft Purview Governance Domains, Data Products, glossary terms, OKRs, CDEs, Data Quality, health controls, access and Data Map.

Data Architecture Professionals

Your Learning Journey

What federated governance gives you