Forum Discussion

sarav_s's avatar
sarav_s
Copper Contributor
Jan 29, 2026

Cross workspace lineage for Fabric Lakehouse tables in Purview

I’m currently exploring lineage capture in Microsoft Purview for Fabric Lakehouse tables that are spread across multiple workspaces, following medallion architecture (Bronze, Silver, Gold in separate Fabric workspaces).

While reviewing the documentation, I noticed the stated limitation around cross-workspace lineage for non-power BI assets, as mentioned here:

snippet from

https://learn.microsoft.com/en-us/purview/data-map-lineage-fabric

  • Is there any update or workaround planned to support cross-workspace Fabric lineage in Purview?
  • Is this limitation on the product roadmap or actively being worked on?
  • Until native support is available, are there any recommended design patterns to handle lineage in this scenario?
developer
fabric
lineage
lineage limitation

1 Reply

  • Ajeeth_Muthu's avatar
    Ajeeth_Muthu
    Copper Contributor
    Feb 02, 2026

    Hi Sarav_s,

    1. Is there any update or workaround planned to support cross‑workspace Fabric lineage in Purview?
      Right now, no update has been published. The official documentation still states that cross‑workspace lineage for non‑Power BI Fabric items is not supported.There is also no published workaround that enables automatic cross‑workspace lineage today.
    2. Is this limitation on the product roadmap or actively being worked on?
      There is no public roadmap entry or ETA for cross‑workspace lineage support.
      Nothing in the Fabric or Purview documentation indicates that this feature is in active preview or upcoming.
    3. Until native support is available, are there any recommended design patterns?
    • Keep your Bronze/Silver/Gold chain inside one workspace, because Fabric lineage is workspace‑scoped and downstream items in other workspaces are not shown. 
    • Use Purview’s custom lineage APIs (Atlas/REST) to manually stitch lineage across workspaces if you need an end‑to‑end view. This is officially supported for custom lineage scenarios. 
    • Use shortcuts, but keep the transformation step in one workspace so the lineage can be captured inside that workspace.


    If you found this information useful, please consider giving it a like and marking the response as the accepted solution. 😁

Resources