Forum Discussion

river200's avatar
river200
Copper Contributor
Dec 29, 2025

Lineage in Purview - Fabric

Dears,

 

I was checking the lineage which is collected in Microsoft Fabric by Purview and I saw this limitations on the Microsoft page :

 

I have some sources like :

 

  1. Dataverse (I am doing a Dataverse Direct Shortcut to bring the information from Dataverse into Fabric - Raw Layer)
  2. Sharepoint (I am doing a Fabric Shortcut into sharepoint. - Fabric Raw Layer) to bring the files into Fabric
  3. SQL Server MI ( I am doing a Fabric  mirroring - Fabric Raw Layer)

I did not undertand very well the lineage exceptions mentioned above. Let me ask this questions please:

 

1)

Suppose I have a table which came from SQL Server MI. This table was first ingested into Fabric Raw Layer, then into Bronze Layer, then into Fabric Silver Layer and After to Fabric Gold Layer. 

Each layer has its own fabric workspace.

When I bring the metadata via Purview , into the Purview Unified Catalog do I get automatic lineage between Silver layer and Gold layer for that table (suppose the table is named table 1).  Or this is not possible because :

 

1.1 ) They are different workspaces

1.2)  The table was originated outside Fabric , in the SQL Server MI?

 

2)

 

Suppose I have a table in Silver layer (in the silver layer workspace), then, in the gold layer, I create a shortcut to that table. And then I use a notebook to transform that table into another table in the same gold layer. Will I have lineage between the Silver table and the new transformed table in gold layer?

 

3)

 

To make the relationship of lineage between tables which is not create automatically I was thinking in using Purview Rest APIs. Which API shall I use specifically for this? 

 

Thanks,

 

Pedro

 

 

Thanks,

 

Pedro 

 

 

  

1 Reply

  • carolineharper's avatar
    carolineharper
    Occasional Reader
    Dec 29, 2025

    Thanks for the detailed explanation. From what I’ve seen, this looks like a current limitation rather than a configuration issue.

    Right now, Purview lineage in Fabric only works reliably within the same workspace and when using Fabric native tools. Once data moves from SQL Server into Fabric and then gets transformed into Silver and Gold layers, the lineage often breaks, especially if different workspaces or engines are involved. Purview treats those tables as separate assets, even if they are clearly related.

    Automatic lineage between Silver and Gold layers is not supported yet in this scenario. There is no API or setting to manually link or override lineage.

    The best workaround for now is keeping Silver and Gold in the same workspace and using Fabric pipelines or notebooks for transformations. Adding descriptions or documentation in Purview is currently the only way to show the relationship.

    Hopefully, Microsoft improves cross-workspace and cross-engine lineage soon.

Resources