Forum Discussion
Lineage in Purview - Fabric
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.