Data Platform, Mesh & Governance Financial Services

13Federated Data Governance (Purview + Fabric + Databricks)

Role: Governance Solution Engineer

Executive summary

Integrated Microsoft Purview with Azure Databricks and Microsoft Fabric to deliver a unified catalog, cross-platform masking and an Entra ID-based access model—giving a financial-services client a single governance pane.

  • Microsoft Purview
  • Azure Databricks
  • Unity Catalog
  • Microsoft Fabric
  • Entra ID
  • RLS / CLS
  • Conditional Access
SSituation

A key Financial Services concern is governance consistency across multiple data platforms. I worked on federated data governance in Azure, integrating Microsoft Purview with Azure Databricks and Microsoft Fabric for a single pane of cataloging, lineage and policy across the data estate.

TTasks
  • Configure Purview to scan and catalog Databricks Delta tables (Unity Catalog) and Fabric assets for a unified catalog.
  • Implement security/privacy policies spanning platforms (sensitive labels and masking enforceable on both engines).
  • Demonstrate RLS and CLS across consumption layers (one policy masking a column in both Databricks and Power BI).
  • Use Entra ID so identities and conditional access (MFA) apply uniformly across Spark and Fabric SQL.
  • Document a governance operating model (central oversight + domain-managed local permissions).
AActions

I connected Purview to the client's Databricks Unity Catalog and registered the Fabric tenant, then created sample classification and masking policies—verifying that a Databricks query returned masked data per Purview policy. For RLS, I aligned Fabric's internal RLS for Power BI with Purview classifications and documented the policy-translation gap. I integrated Entra ID Conditional Access requiring MFA for external access to both Fabric and Databricks, and delivered a technical guide.

RResults

The client gained a unified view of assets across Databricks and Fabric in Purview, streamlining discovery and compliance tracking. Consistent masking proved that privacy rules defined centrally can be enforced per platform. Regulators could obtain lineage regardless of platform from one portal, and the federated model allowed domain autonomy under central oversight—reinforcing Fabric as an open, governable platform.

LLessons Learned

Cross-platform governance hinges on integration points like Purview connectors, and on cleverly filling gaps (Purview does not yet auto-propagate RLS—communicated with interim solutions). Security must be by design, and I gained deep familiarity with Purview's scanning and policy engine, applied to later scenarios.

Solution overview: Federated Data Governance (Purview + Fabric + Databricks) Federated Data Governance (Purview + Fabric + Databricks) — flow: Platforms then Catalog then Policy then Identity. PLATFORMS Databricks (Unity Catalog) Microsoft Fabric CATALOG Purview scan → unified catalog Lineage POLICY Classification + masking RLS / CLS alignment IDENTITY Entra ID Conditional Access (MFA) One governance pane · consistent masking enforced across engines
Solution overview — Federated Data Governance (Purview + Fabric + Databricks) (illustrative; replace with your own diagram anytime)