Complete End-to-End Lineage from AWS S3 to Azure Blob to Snowflake in Microsoft Purview - ADF SnowflakeV2 Connector Not Reporting Lineage

Dinesh Murugappan 0 Reputation points
2026-06-29T06:10:23.2166667+00:00

Hello Microsoft Purview Community,

I am building a POC to demonstrate complete end-to-end data lineage using Microsoft Purview. My data pipeline is:

AWS S3 --> Azure Blob Storage --> Snowflake (via ADF) --> Snowflake Transformation

ENVIRONMENT:

  • Microsoft Purview (Standard Edition, Default Directory tenant)
  • Azure Data Factory (ADF)
  • Snowflake Standard Edition
  • AWS S3

WHAT I HAVE ACHIEVED:

  1. ADF Lineage (Chain 1) -- Working partially:

S3 --> Copy_S3_To_Blob --> Azure Blob
Screenshot 2026-06-30 at 2.54.53 PM

Azure Blob --> Copy_Blob_To_Snowflake --> EMPLOYEES table
Screenshot 2026-06-30 at 2.52.10 PM Note: Copy_S3_To_Blob shows lineage correctly in Purview.

However, Copy_Blob_To_Snowflake shows this message:
"The lineage of this copy activity is not reported because it used the following unsupported connector: SnowflakeV2."

  1. Snowflake Stored Procedure Lineage (Chain 2) -- Working:

EMPLOYEES --> SP_EMPLOYEES_SUMMARY --> EMPLOYEES_SUMMARYScreenshot 2026-06-30 at 2.53.30 PM This works correctly through Purview scan with "Lineage, code, signature" option selected.

WHAT I CANNOT ACHIEVE:

Connecting Chain 1 and Chain 2 into ONE complete lineage map:

S3 --> Blob --> EMPLOYEES --> SP_EMPLOYEES_SUMMARY --> EMPLOYEES_SUMMARY

QUESTIONS:

  1. Is ADF SnowflakeV2 connector lineage reporting to Purview supported? If not, is it on the roadmap?
  2. Is there any supported way to connect ADF lineage and Snowflake stored procedure lineage into ONE lineage map in Purview?
  3. We tried Purview REST API to create custom lineage links but got this error: "AADSTS500011: The resource principal named https://purview.azure.com was not found in the tenant named Default Directory" How can we resolve this?
  4. Is Microsoft Fabric Data Factory the recommended solution for complete Snowflake lineage in Purview?

WHAT WE TRIED:

  • ADF Copy Data activity with SnowflakeV2 connector (lineage not reported)
  • Script activity to call stored procedures (not tracked by Purview)
  • Pre-copy script in Copy Data activity (does not connect lineage chains)
  • Purview REST API with service principal (blocked by tenant configuration)
  • Snowflake stored procedure lineage via scan (works but separate from ADF lineage)

Any guidance or workaround would be greatly appreciated.

Thank you!

Microsoft Security | Microsoft Purview
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Pilladi Padma Sai Manisha 10,770 Reputation points Microsoft External Staff Moderator
    2026-07-01T08:49:11.8133333+00:00

    Hi @Dinesh Murugappan
    Thank you for sharing the detailed workflow and screenshots. Based on the information you've provided, the behavior you're seeing is consistent with the current Microsoft Purview lineage capabilities.

    The message displayed in Purview:

    "The lineage of this copy activity is not reported because it used the following unsupported connector: SnowflakeV2."

    indicates that lineage metadata is not currently being emitted for that Azure Data Factory copy activity when using the SnowflakeV2 connector. Because of this, Purview doesn't receive the metadata required to automatically connect the Azure Blob asset to the Snowflake table, which is why your lineage appears as two separate graphs.

    The Snowflake stored procedure lineage you're seeing is discovered independently through the Snowflake scan using the Lineage, code, and signature option. Although this correctly captures the relationship between the EMPLOYEES and EMPLOYEES_SUMMARY tables, it isn't automatically stitched together with the ADF operational lineage because the preceding copy activity doesn't report lineage.

    Regarding your questions, based on the behavior shown in your environment, lineage reporting for the SnowflakeV2 connector is currently unavailable for this copy activity. At this time, there is no public Microsoft documentation confirming roadmap information for support of this connector.

    There is also no documented mechanism to automatically merge these two lineage paths into a single end-to-end graph. Purview can build a continuous lineage graph only when each stage publishes compatible lineage metadata. Since the ADF copy activity isn't reporting lineage for the SnowflakeV2 connector, Purview has no metadata available to connect the Azure Blob asset with the scanned Snowflake table.

    For the Purview REST API error:

    AADSTS500011: The resource principal named https://purview.azure.com was not found...

    this typically indicates an authentication configuration issue, such as using an incorrect resource or audience, or requesting a token from the wrong Microsoft Entra tenant. Verify that the service principal exists in the same tenant as the Purview account, that the application requests an access token for the appropriate Purview endpoint, and that the service principal has the required Microsoft Purview Data Map permissions.

    Regarding Microsoft Fabric Data Factory, while Fabric provides enhanced lineage across Fabric-native workloads, there is currently no documented guidance stating that it provides complete end-to-end lineage for a workflow spanning AWS S3 → Azure Blob → Azure Data Factory → Snowflake. Migrating only the orchestration layer to Fabric is therefore unlikely to resolve this specific connector limitation.

    As a final verification, ensure that the Azure Data Factory has been connected to Purview, the pipeline was re-executed after enabling lineage integration, and both the Azure Blob and Snowflake assets have been successfully scanned and registered in Purview. If all of these prerequisites are satisfied and the copy activity continues to display the unsupported connector message, the behavior is most likely due to the current product limitation rather than a configuration issue.

    For more information, please refer to the following documentation:

    Azure Data Factory lineage in Microsoft Purview: https://learn.microsoft.com/purview/data-map-lineage-azure-data-factory

    Azure Synapse and ADF lineage capabilities: https://learn.microsoft.com/purview/data-map-lineage-azure-synapse-analytics

    Microsoft Purview lineage concepts: https://learn.microsoft.com/purview/data-map-lineage

    Was this answer helpful?

    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.