Share via

Unable to Create Full End-to-End Lineage Between SQL Server → Fabric Pipeline → Fabric Lakehouse in Microsoft Purview

Prashant Prakash Vidhate 0 Reputation points
2025-12-11T07:21:22.7466667+00:00

I am attempting to build a complete end-to-end data lineage in Microsoft Purview for a SQL Server → Microsoft Fabric → Power BI architecture. Our actual data flow includes ingestion pipelines, staging tables, silver tables, gold/fact tables, and Power BI semantic models. The expected lineage looks like:

SQL Server Source 

 ↓  
```Fabric Data Factory Ingestion Pipeline

↓

↓

↓

↓ 


However, Purview is not allowing us to model this lineage correctly. We are encountering several limitations that prevent us from adding the ingestion pipeline and upstream SQL Server source to the Fabric Lakehouse tables.  
  
Problems We Are Facing

1. Cannot insert a Fabric pipeline between two dataset assets

When editing lineage in Purview, the Lakehouse table always appears as a locked asset on one side of the lineage row.

Purview does not allow us to add the Fabric Data Factory pipeline as an upstream asset.

Any attempt to create a relationship like:

SQL Table → Fabric Pipeline → Lakehouse Table

results in validation errors, and the relationship cannot be saved.  
  
2.Purview allows manual lineage only between dataset → dataset, not dataset → process → dataset

Fabric pipelines appear as process-type assets.

Purview does not allow a process to be manually inserted between two datasets, even though this is needed to represent the ingestion flow.

Only dataset-to-dataset manual lineage is allowed.

---
*moved from "Microsoft Teams | Development"*
Microsoft Security | Microsoft Purview
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Q&A Assist
    2025-12-11T07:21:38.1366667+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    It seems you are encountering limitations with Microsoft Purview when trying to create a full end-to-end lineage for your SQL Server to Power BI architecture through Microsoft Fabric. Here are some insights based on the context provided:

    1. Lineage Limitations: Currently, for non-Power BI Fabric items, external data sources as upstream sources in lineage are not supported. This means that you may not be able to directly link your SQL Server source to the Fabric Lakehouse tables through the ingestion pipeline as you intended.
    2. Locked Assets: The Fabric Lakehouse tables appear as locked assets in Purview, which prevents you from adding the Fabric Data Factory pipeline as an upstream asset. This behavior is expected as Purview does not allow for the insertion of a Fabric pipeline between dataset assets, which is causing the validation errors you mentioned.
    3. Manual Lineage Restrictions: Purview currently allows manual lineage only between dataset-to-dataset, not dataset-process-dataset. Since Fabric pipelines are treated as process-type assets, this restriction further complicates your ability to represent the ingestion flow accurately.

    Given these limitations, you might need to explore alternative methods for documenting your data lineage or consider providing feedback to Microsoft regarding these constraints in Purview.

    References:

    0 comments
  2. VRISHABHANATH PATIL 2,305 Reputation points Microsoft External Staff Moderator
    2025-12-12T03:21:22.66+00:00

    Hi @Prashant Prakash Vidhate

    It sounds like you're facing some challenges with modeling data lineage in Microsoft Purview for your SQL Server to Fabric Lakehouse architecture. Here’s a breakdown of what you may be experiencing and some suggestions to consider:

    Issues You're Facing:

    Inserting Fabric Pipeline Limits: You're unable to insert a Fabric Data Factory (ADF) pipeline between dataset assets, as the Lakehouse table appears locked when you try to add it. This is a known limitation in Purview.

    Drawbacks of Manual Lineage: Manual lineage relationships are currently only supported between dataset-to-dataset, which means you cannot create a lineage representation of dataset → process → dataset.

    Suggested Steps to Address the Issues:

    Check Known Limitations:

    • According to Microsoft Purview documentation, lineage from non-Power BI Fabric items does not support external data sources as upstream sources and does not support adding processes directly between datasets.

    Verify the Scans: Make sure your Fabric tenant is properly scanned. If the Fabric workspace scan hasn’t been conducted or is incomplete, it may limit the assets visible in Purview.

    Manually Capture Lineage via Custom API: Due to limitations in the manual editing of lineage paths in Purview, consider using the custom lineage API to represent your ingestion flows if having an accurate lineage model is critical for your use case. You can find more about this here.

    Consult Documentation for Updates: There may have been updates or enhancements to Purview since your last check. Keep an eye on Microsoft Docs for the latest capabilities around data lineage.

    Follow-Up Questions:

    To better assist you, here are a few follow-up questions you might consider:

    1. Have you confirmed that the necessary scans of your Fabric tenant are complete and successfully running?
    2. Are there specific error messages when you attempt to save the lineage relationships, or is it just that certain assets appear locked?
    3. Are you currently using custom API implementations for lineage, or are you strictly relying on the graphical interface in Purview?
    4. Is the source SQL Server properly registered in Purview, and does it have the required configurations for lineage extraction?

    I hope this helps you get closer to resolving the issues! If you have any further questions or details, feel free to share. 

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.