Connect Azure Synapse directly to Model Registry

Michael Wittman 76

I'm attempting to connect my Azure Synapse Workspace to an Azure Machine Learning Registry resource directly, without the addition of a Machine Learning Workspace. I had previously had networking issues utilizing the workspace and, seeing as Synapse is going to be the main development platform, setting up a workspace felt redundant. I was able to create just a registry within the AZ ML portal, and am hoping we can use just the registry as our MLFlow server and model repository.

We are utilizing fully secured resources behind a VNET and connect everything via private endpoints. I have created PEs in the portal for synapse to connect to the model registry and the container registry resources, and created an MPE in the Synapse workspace to connect to the storage account under the model registry.

Within a Synapse notebook, I attempt to set the MLFlow tracking URI to the same URI present on the Model Registry's page. However, when running the notebook and attempting to set the experiment, I receive an "MlflowException: API request to endpoint /api/2.0/mlflow/experiments/create failed with error code 404 != 200. Response body: ''" error. I'm not seeing any way to create MPEs to either the container or model registries within the Synapse portal.

I'm not sure where I might be going wrong, but is it even possible to connect to the registry directly like this within a synapse environment?

romungi-MSFT 43,696 Reputation points Microsoft Employee

2024-06-11T05:24:42.35+00:00

@Michael Wittman I do not see any documented method in ML documentation to connect to registry from synapse workspace but there are some scenarios mentioned to isolate the registry with an existing private endpoint or create one with disabled public access. Does this help?

https://learn.microsoft.com/en-us/azure/machine-learning/how-to-registry-network-isolation?view=azureml-api-2&tabs=existing#how-to-create-a-private-endpoint

There are also steps to locate the registry component in storage account and to create PE for the same. Thanks!!
Michael Wittman 76 Reputation points

2024-06-18T18:57:00.3866667+00:00

@romungi-MSFT Thank you for your response. I had followed the links you had given and had tried the implementation, but to no avail. I eventually found out that the VNet the PEs we had created to the registry's sub-components was not the same as the VNet the Synapse instance was a part of - and I don't have permission to create resources within it either. The only way I have to get those created would be Managed PEs created from within Synapse, which as you stated, isn't present.

Share via

Connect Azure Synapse directly to Model Registry