What causes Fabric Pipeline Error 2502?

Incorrect storage account name specified in the Batch-linked storage connection. Expired or rotated storage account access key not updated in the linked service. Storage account was deleted or renamed after the linked service was created. Linked service was not re-published after credential changes were made

How do I fix Fabric Pipeline Error 2502?

Step 1: In the Azure Portal, navigate to the storage account used by your Azure Batch activity and go to Access Keys to retrieve the current key1 or key2 value.. Step 2: In Microsoft Fabric Data Factory, open the linked service for this storage account and update the access key with the value from Step 1.. Step 3: Confirm the storage account name in the linked service exactly matches the name shown in the Azure Portal (names are case-sensitive and must not include the full URL).. Step 4: Click 'Test connection' in the linked service editor to confirm the updated credentials are valid.. Step 5: Re-publish the pipeline and re-run it to confirm error 2502 no longer appears.

High severityauthenticationMicrosoft Fabric →

Power BI Refresh Error:
Fabric Pipeline Error 2502

What does this error mean?

The pipeline cannot access the storage account associated with the Azure Batch activity due to an incorrect account name or access key. Verify your storage account credentials in the linked service.

Common causes

1Incorrect storage account name specified in the Batch-linked storage connection
2Expired or rotated storage account access key not updated in the linked service
3Storage account was deleted or renamed after the linked service was created
4Linked service was not re-published after credential changes were made

How to fix it

1Step 1: In the Azure Portal, navigate to the storage account used by your Azure Batch activity and go to Access Keys to retrieve the current key1 or key2 value.
2Step 2: In Microsoft Fabric Data Factory, open the linked service for this storage account and update the access key with the value from Step 1.
3Step 3: Confirm the storage account name in the linked service exactly matches the name shown in the Azure Portal (names are case-sensitive and must not include the full URL).
4Step 4: Click 'Test connection' in the linked service editor to confirm the updated credentials are valid.
5Step 5: Re-publish the pipeline and re-run it to confirm error 2502 no longer appears.

Frequently asked questions

Does Azure Batch require a specific type of storage account?

Azure Batch works with general-purpose Azure Storage accounts using access key authentication. Ensure the storage account is not using only SAS tokens or managed identity configurations, as those are not supported for this linked service type.

How can I avoid this error when storage keys are rotated?

Store the storage account access key as a secret in Azure Key Vault and configure the Fabric linked service to reference it dynamically. This ensures the pipeline always uses the latest key without manual intervention.