Troubleshooting SAS URI Authentication for ADF Linked Service to ADLS

Question

What steps can I follow to troubleshoot and resolve SAS URI authentication issues when setting up an ADF Linked Service to ADLS?

PS - Based on common issues that we have seen from customers and other sources, we are posting these questions to help the Azure community.

Answer 1

Greetings!

To troubleshoot and resolve SAS URI authentication issues when setting up an ADF Linked Service to ADLS, follow these steps:

1. Generate the SAS Token Correctly: Make sure the SAS token is generated with the necessary permissions (Add, Create, Write, Delete, List).
2. Configure the SAS URI: Use the SAS token to set up the SAS URI for the container in the format: https://<storageaccount>.dfs.core.windows.net/<container>?<SAS token>.
3. Check Permissions: Verify that container-level permissions are correctly set. Note that with container-level permissions only, certain features like the [Browse] feature in the file path may not be available. You will need to manually enter the complete path.
4. Validate the Setup: Test the connection in the ADF linked service. If the connection fails, recheck the SAS token for validity and proper permissions.
5. Address Common Errors: For errors like "Signature did not match," ensure that the SAS token is correctly configured and formatted. Verify that it includes all required permissions.

Following these steps should help you resolve the SAS URI authentication issues and successfully configure the ADF Linked Service to ADLS.

Resources:

• Create a Shared Access Signature (SAS)
• Azure Data Factory Linked Service to Azure Data Lake Storage

Hope this helps. If you have any follow-up questions, please let me know. I would be happy to help.

Please do not forget to "up-vote" wherever the information provided helps you, as this can be beneficial to other community members.