Hello Microsoft Q&A,
we are using a Azure Synapse Workspace and a Azure Machine Learning Workspace for quite some time now. The Synapse Workspace has a activated Data Exfiltration Protection. The connection between these two resources is not working any longer. When running a pipeline reading data from the ADLS Gen2 storage of the Synapse Workspace in the MLW I get the following error:
Error Code: ScriptExecution.StreamAccess.NotFound
Native Error: error in streaming from input data sources
StreamError(ConnectionFailure { source: Some(hyper::Error(Connect, ConnectError("dns error", Custom { kind: Uncategorized, error: "failed to lookup address information: Name or service not known" }))) })
=> connection failure when access stream
ConnectionFailure { source: Some(hyper::Error(Connect, ConnectError("dns error", Custom { kind: Uncategorized, error: "failed to lookup address information: Name or service not known" }))) }
=> error trying to connect: dns error: failed to lookup address information: Name or service not known
hyper::Error(Connect, ConnectError("dns error", Custom { kind: Uncategorized, error: "failed to lookup address information: Name or service not known" }))
=> dns error: failed to lookup address information: Name or service not known
ConnectError("dns error", Custom { kind: Uncategorized, error: "failed to lookup address information: Name or service not known" })
=> failed to lookup address information: Name or service not known
Custom { kind: Uncategorized, error: "failed to lookup address information: Name or service not known" }
Error Message: Connection failed when trying to access the stream. Make sure uri is correct. error trying to connect: dns error: failed to lookup address information: Name or service not know
I struggeled to find a reason. But now I read that:
The Azure Machine Learning integration is not currently supported in Synapse Workspaces with Data Exfiltration Protection
https://learn.microsoft.com/en-us/azure/synapse-analytics/machine-learning/quickstart-integrate-azure-machine-learning?view=azureml-api-2
Is there a workaround for this problem?
Best regards
Lukas