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.

Technology enables the operating model

Microsoft Purview Unified Catalog and Data Map can support a federated Data Governance operating model, but they do not replace accountability, decision rights, source-system security, IAM, self-serve data-platform capabilities, operating processes or domain capacity.

Governance Domains

Microsoft Purview supports five Governance Domain types: Functional Unit, Line of Business, Data Domain, Regulatory and Project. They provide flexible business- or governance-aligned boundaries for ownership, discovery and business concepts.

For an initial PoC / Proof of Value, Functional Unit is the suggested starting type where the ownership policy maps accountability to an organisational function; otherwise choose the type that best reflects the actual ownership model.

Data Products

Consumer-facing groupings of assets around a use case, with ownership and business context.

Glossary terms

Business vocabulary that improves understanding; active terms can carry policies that apply to linked products or assets.

Objectives and Key Results

Business concepts that describe measurable value and goals; health controls can measure product alignment to business OKRs.

Critical Data Elements (preview)

Logical groupings of important data concepts that require elevated governance.

Data Quality

Rules and profiling can produce scores that aggregate from columns to assets, Data Products and Governance Domains where supported.

Data health controls

Built-in measures track governance health, including self-serve access enablement, publication, ownership, Data Quality, critical data, classification and OKR alignment.

Access policies and requests

Support governed request and approval experiences. Approval does not itself guarantee that underlying technical permissions have already been provisioned; approvers or access providers must apply them.

Data Map

Captures metadata from supported data sources. Data Map and Unified Catalog roles do not by themselves grant access to underlying data.

Implementation boundary

Support varies by data source, connector and feature. The framework begins with business and governance outcomes and maps Purview capabilities into the operating model where they support those outcomes.

Microsoft references used by the framework

Learning with Data SkyLab Studio

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