Unable to use linked service to blob storage account with Test Connection as "To File Path"

Question

I am trying to create a linked service to Azure blob storage account. I need to use System Assigned Managed Identity for Authentication. No restriction on account selection method. I tried using "From Azure Subscription" (which gets modified to "Enter Manually" when you save and reopen the linked service). Need to use Test Connection as "To File Path" (Able to use it and test connection successfully. But this also gets updated to "To Linked Service" when I save and reopen the lined service).

Basically my Account Selection & Test Connection are getting changed once I save and reopen my Linked service.

Due to same, when I am creating the dataset using same linked service it's giving me error code 403.

Can you please help me with this?

Answer 1

It sounds like you're facing an issue where the configuration settings in your linked service to Azure Blob Storage are changing unexpectedly after saving and reopening the linked service. Specifically, the Account Selection method and Test Connection setting are not persisting as expected, leading to issues when you try to create a dataset, including the error code 403 (which typically indicates a permission issue).

1. Assign Permissions: Ensure the System Assigned Managed Identity has Storage Blob Data Contributor role on the Azure Blob Storage account.
2. Enable Managed Identity: Ensure the System Assigned Managed Identity is enabled in Azure Data Factory.
3. Reconfigure Linked Service:
   • Select the correct Account Selection method (manually or from Azure Subscription).
   • Ensure System Assigned Managed Identity is used for authentication.
4. Test Connection: Verify the connection works after saving and reopening the linked service.
5. Recreate Linked Service: If the settings change after saving, try deleting and recreating the linked service.
6. Check Dataset: Ensure the dataset is correctly linked to the reconfigured service and that the file path is valid.

Think this should resolve the 403 error.