Workaround Enabling Purview Data Quality & Profiling for Cross-Tenant Microsoft Fabric Assets

[pranavsabnis]

The Challenge: Cross-Tenant Data Quality Blockers Like many of you, I have been managing a complex architecture where Microsoft Purview sits in Tenant A and Microsoft Fabric resides in Tenant B.

While we can achieve basic metadata scanning (with some configuration), I hit a hard wall when trying to enable Data Quality (DQ) scanning. Purview's native Data Quality scan for Fabric currently faces limitations in cross-tenant scenarios, preventing us from running Profiling or applying DQ Rules directly on the remote Delta tables.

The Experiment: "Governance Staging" Architecture rather than waiting for a native API fix, I conducted an experiment to bridge this gap using a "Data Staging" approach. The goal was to bring the data's "physicality" into the same tenant as Purview to unlock the full DQ engine.

The Solution Steps:

Data Movement (Tenant B to Tenant A): Inside the Fabric Workspace (Tenant B), I created a Fabric Data Pipeline. I used this to export the critical Delta Tables as Parquet files to an ADLS Gen2 account located in Tenant A (the same tenant as Purview).

Note: You can schedule this to run daily to keep the "Governance Copy" fresh.

Native Scanning (Tenant A): I registered this ADLS Gen2 account as a source in Purview. Because both Purview and the ADLS account are in the same tenant, the scan was seamless, instantaneous, and required no complex authentication hurdles.

Activating Data Quality: Once the Parquet files were scanned, I attached these assets to a Data Product in the Purview Data Governance portal.

The Results: The results were immediate and successful. Because the data now resides on a fully supported, same-tenant ADLS Gen2 surface:

✅ Data Profiling: I could instantly see column statistics, null distributions, and value patterns.

✅ DQ Rules: I was able to apply custom logic and business rules to the data.

✅ Scans: The DQ scan ran successfully, generating a Data Quality Score for our Fabric data.

Conclusion: While we await native cross-tenant "Live View" support for DQ in Fabric, this workaround works today. It allows you to leverage the full power of Microsoft Purview's Data Quality engine immediately. If you are blocked by tenant boundaries, I highly recommend setting up a lightweight "Governance Staging" container in your primary tenant.

Has anyone else experimented with similar staging patterns for Governance? Let's discuss below.

[pranavsabnis]

Thanks @v-echaithra. If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution. 

[v-echaithra]

Hi @pranavsabnis ,

Thanks for sharing this detailed workaround, it’s a solid and practical approach for customers working across multi-tenant environments. This is currently the recommended pattern for enabling Data Quality insights on Fabric datasets that reside in a different tenant. We appreciate you validating this solution and sharing your findings with the community. I would also encourage you to publish this as a blog post on the Microsoft Tech Community, as it would benefit many customers facing similar challenges. Power BI Community Blog - Microsoft Fabric Community

Best Regards,
Chaithra E.