Lineage scenario between Synapse pipeline and Purview failing

Further 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?