Unable to connect scope linked service from ADF

Question

Hi Team,

I am attempting to use the scope task in ADF to run my scope scripts, but the connection is failing despite having all the necessary permissions for ADLA. I am using a System Assigned Managed Identity (SAMI) to connect to my ADLA with the Datalake Analytics Reader role, which should ideally allow me to run the job. However, I am unable to submit my pipeline.

Below is the error I am encountering while connecting to the linked service.

Any pointers would be highly appreciated. 

Regards,

Answer 1

Hello , Welcome to MS Q&A

The error code 9512, "Unable to get access token, No MSI Authenticator available," indicates that the System Assigned Managed Identity (SAMI) is not able to authenticate and obtain an access token to connect to the Azure Data Lake Analytics (ADLA) service.

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

1. In the ADF portal, go to the "Manage" section, select "Linked services," and edit the linked service for ADLA. Ensure that the "Authentication method" is set to "Managed Identity."
2. Check if there are any network or firewall settings that might be blocking the connection from ADF to ADLA.
   • Ensure that the necessary endpoints and ports are open and accessible.
3. Check the Azure AD logs for any authentication errors related to the SAMI.

By following these steps, you should be able to identify and resolve the issue preventing the SAMI from obtaining an access token and connecting to the ADLA service

Please let us know if any questions

Kindly accept answer if it helps

Thanks

Deepanshu

Answer 2

Hello Bharati,

Welcome to the Microsoft Q&A and thank you for posting your questions here.

I understand that you are unable to connect scope linked service from ADF.

To resolve the issue, I will advise you to isolate whether the issue is with the SAMI or the ADF configuration by manually retrieve an access token using Azure CLI to verify that the SAMI can obtain a token via bash command: az account get-access-token --resource https://datalake.azure.net/

Then, start by verifying that the System Assigned Managed Identity (SAMI) is properly assigned to the Azure Data Factory (ADF) and has the necessary permissions in Azure Data Lake Analytics (ADLA). Next, confirm that the Data Lake Analytics Reader role is correctly assigned to the SAMI and ensure there are no delays in role assignment. Finally, review the configuration settings in both ADF and ADLA to ensure they adhere to best practices for managed identity authentication.

I hope this is helpful! Do not hesitate to let me know if you have any other questions.

---

Please don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful.