Forum Discussion
Workaround Enabling Purview Data Quality & Profiling for Cross-Tenant Microsoft Fabric Assets
In my view, the root problem is that Purview cannot run Data Quality or Profiling on Fabric data held in another tenant; metadata scans may work, but the DQ engine requires the data to exist physically within the same tenant where Purview’s identity and RBAC operate.
From my experience, this creates a noticeable governance gap for multi-tenant setups, and it feels like the platform is not yet ready for true cross-tenant scenarios.
The workaround of exporting Fabric tables into an ADLS Gen2 account inside the Purview tenant does work reliably, enabling full profiling, rule execution and DQ scoring. This is effective because Purview can only process data it can access natively within its own tenant boundary.
The main drawbacks are that this produces a copy rather than a live view and requires scheduled refreshes, especially for large tables.
Overall, this staging approach is the only workable solution for now, though it feels like Microsoft needs to address cross-tenant DQ support sooner rather than later.
However, I might be wrong.
In my view, the root problem is that Purview cannot run Data Quality or Profiling on Fabric data held in another tenant; metadata scans may work, but the DQ engine requires the data to exist physically within the same tenant where Purview’s identity and RBAC operate.
From my experience, this creates a noticeable governance gap for multi-tenant setups, and it feels like the platform is not yet ready for true cross-tenant scenarios.
The workaround of exporting Fabric tables into an ADLS Gen2 account inside the Purview tenant does work reliably, enabling full profiling, rule execution and DQ scoring. This is effective because Purview can only process data it can access natively within its own tenant boundary.
The main drawbacks are that this produces a copy rather than a live view and requires scheduled refreshes, especially for large tables.
Overall, this staging approach is the only workable solution for now, though it feels like Microsoft needs to address cross-tenant DQ support sooner rather than later.
However, I might be wrong.