Forum Discussion
MicrosoftLineage scenario between Synapse pipeline and Purview failing
I'm currently testing a lineage scenario between a Synapse pipeline and Purview.
I used the Lab 22 to test this scenario 'Use Microsoft Purview with Azure Synapse Analytics':
https://microsoftlearning.github.io/dp-203-azure-data-engineer/Instructions/Labs/22-Synapse-purview.html#integrate-microsoft-purview-with-azure-synapse-analytics
Everything works fine, data are copied, except the lineage scenario which failed with the following error:
"The catalog provided for lineage reporting cannot be connected, please check the catalog uri and network connection."
Screenshot below:
Questions:
1. As Synpase seems to be correctly connected to Purview, in order to troubleshoot this error, is there a way to get further information like stack trace in the Synapse logs?
2. Should the Purview Account and Synapse Workspace be deployed in the same Azure Region?
3. Is Lineage scenario between Synapse and Purview still supported with the latest Purview version?
4. Could you share a sample where the Lineage Scenario between Synapse and Purview works?
Thanks for your help,
Fred
1 Reply
flecoquiFurther information below:
I'm facing the same issue between pipelines running on Data Factory, the lineage is not pushed to Purview because of the same error.
But the custom lineage running in a notebook on Data Factory or Synapse is still working.
Moreover, something changed in Purview configuration, for the new version the catalog and scan endpoints support the following format :"endpoints": {
"catalog": https://[TENANT-ID]-api.purview-service.microsoft.com/catalog,
"scan": https://[TENANT-ID]-api.purview-service.microsoft.com/scan
},
The previous version supported this format, which are still used and working for the Custom Lineage:
"endpoints": {
"catalog": https://[PURVIEW_ACCOUNT_NAME].purview.azure.com/catalog,
"scan": https://[PURVIEW_ACCOUNT_NAME].purview.azure.com/scan
},
Maybe the new endpoint is blocked?