A unified data governance solution that helps manage, protect, and discover data across your organization
Transition from Microsoft Purview Data Governance to Microsoft Fabric: Impact on Existing Metadata Management, Discovery, Access Controls, and Planned Data Quality
BHOWMICK, Sourav
0
Reputation points
Issue:
Our enterprise has already operationalized metadata management and data discovery within Microsoft Purview, and we are currently preparing to initiate Data Quality and Data Health assessments. Following Microsoft’s announcement regarding the retirement of Microsoft Purview Data Governance and the transition to Microsoft Fabric (OneLake Catalog), we require official guidance on the architectural and operational impact—specifically concerning Access Management, Functionality Parity, and Implementation/Migration—as we conduct our enterprise impact analysis.
Current Implementation & Scope:
- Metadata Management & Discovery (Already Implemented):
- Assets, schemas, classifications, and lineage are registered in Microsoft Purview.
- Business Glossaries and Unified Catalog search/discovery are active and used across project teams
- Planned Data Health & Quality (Planned):
- Define and automate Data Quality rules (Completeness, Accuracy, Consistency, Timeliness).
- Data profiling and health scoring at Data Asset and Data Product levels. - **Access Control Model:** - Configured around Purview role definitions (Governance Domain Owner, Data Product Owner, Data Curator, Data Reader) across Collections and Governance Domains. - **Underlying Billing/Infrastructure:** - Operating under a centralized Azure subscription/tenant model. ```---
- Define and automate Data Quality rules (Completeness, Accuracy, Consistency, Timeliness).
- Assets, schemas, classifications, and lineage are registered in Microsoft Purview.
Observed Challenge / Transition Concern:
- With Microsoft setting the end-of-support deadline for Purview Data Governance to November 12, 2027, and shifting focus to the OneLake Catalog in Microsoft Fabric, we need to assess the risk of continued investment in Purview versus migrating to Fabric.
- We need clarity on how our existing metadata assets and planned Data Quality pipelines will map to Fabric, and how multi-team cost allocation and access control will change.
Expected Behavior / Objective:
- A clear understanding of the migration path from Purview Unified Catalog / Data Map to the Fabric OneLake Catalog.
- Clear guidance on how access management transforms from Purview role-based collection/domain permissions to Fabric workspace and capacity RBAC.
- An established approach for running Data Health/Quality assessments natively in Fabric while attributing compute consumption to respective department budgets via Fabric Capacity (F-SKUs).
Questions for Microsoft Support / Product Team:
Access Management & RBAC Impact:
- How do Purview’s granular governance roles (Governance Domain Owner, Data Curator, Data Reader, Collection Admin) map to Microsoft Fabric’s permission model (Workspace Admin/Member/Contributor/Viewer, OneLake Data Access Security, and Item permissions)?
- Can domain-level governance and curation permissions be maintained without granting full workspace access to underlying raw data?
- **Catalog & Metamodel:** How will custom metamodels, business glossaries, hierarchies, and lineage established in Purview be migrated into the Fabric OneLake Catalog? - **Data Quality & Health:** For teams currently implementing Data Quality rules and profiling in Purview, does Fabric offer direct parity for automated data profiling and rule engines, or will these transition to Fabric native items (e.g., Fabric Notebooks, Dataflows, or OneLake DQ integration)? **Implementation & Ingestion of External Sources:** - Purview currently scans external, hybrid, and multi-cloud systems directly. In Fabric OneLake Catalog, will metadata discovery continue via remote scanners/connectors, or does it require data to be Shortcuted / Mirrored into OneLake? **Capacity & Cost Allocation (Chargeback):** - In a shared enterprise tenant where multiple independent teams (e.g., Data Governance Office vs. specific platform teams) share a central Fabric Capacity (F-SKU), how can Data Quality profiling and catalog scanning compute be tracked and charged back to the respective departmental cost centers? Does Microsoft recommend the **Fabric Chargeback App** for this purpose? ```**Migration Tooling & Official Timelines:** - Is Microsoft releasing automated migration/export utilities to transition existing Purview Data Map metadata, glossaries, and lineage into Fabric, or is a re-cataloging effort required?
Microsoft Security | Microsoft Purview
Microsoft Security | Microsoft Purview
Sign in to answer