Error using the Azure ML activity in Fabric Pipeline

[yangruanEXCG]

Hello, I am using the Azure ML activity to call a batch endpoint in Azure ML. I followed these instruction. https://learn.microsoft.com/en-us/azure/machine-learning/how-to-use-batch-fabric?view=azureml-api-2

It actually does run and finish correctly in Azure, but in Fabric the step fails with error code 2011, and with this message.

"Value cannot be null.
Parameter name: partnerResourceProviderUrl"

I can't seem to find more information about this parameter. That error code also doesn't seem to exist. Does anyone know how to deal with this or how to find more information? Thanks!

[yangruanEXCG · Accepted solution]

In fact, this turned out to be a Fabric bug. Fabric support has let me know that they will be deploying a fix in the first week of March.

[v-ssriganesh]

Hi @yangruanEXCG,

Thank you for reaching out to the Microsoft Fabric community.

The error code 2011 and the message "Value cannot be null. Parameter name: partnerResourceProviderUrl" indicate that there might be a missing or incorrectly configured parameter in your Azure ML activity setup within the Fabric Pipeline.

Here are a few steps you can take to troubleshoot and resolve this issue:

• Please Ensure that all required parameters, especially partnerResourceProviderUrl, are correctly configured in your Azure ML activity. This parameter might be related to the endpoint or resource provider URL that your activity is trying to access.
• Double-check the instructions you followed on the Azure ML Batch Documentation to ensure that no steps were missed.
• Make sure that all dependencies and linked services in your Fabric Pipeline are up to date and correctly configured.
• Look at the detailed logs in both Azure ML and Fabric to identify any additional clues or related errors that might help pinpoint the issue.
• Make sure that the Microsoft Fabric service principal has the necessary permissions to interact with Azure Machine Learning. In Azure ML, verify that the Fabric identity has Contributor or higher access.
• Since your batch endpoint runs fine in Azure ML, but Fabric fails, the issue may be how Fabric is handling authentication or passing parameters. Try using a Web activity in Fabric to manually call the batch endpoint using its REST API and compare the request details.

If this helps, then please Accept it as a solution and dropping a "Kudos" so other members can find it more easily.
Hope this works for you!
Thank you.