What causes DF-Blob-InvalidAccountConfiguration?

The storage account name in the linked service is misspelled or refers to an account that has been deleted or renamed. The linked service uses a custom endpoint URL that points to the wrong storage tier (e.g., table or queue endpoint instead of blob endpoint). The connection string in the linked service was built with an incorrect account name or key and has never been validated

How do I fix DF-Blob-InvalidAccountConfiguration?

Open the Azure Blob Storage linked service in ADF Studio and click 'Test connection' to confirm the account is reachable.. Verify the storage account name matches exactly what appears in the Azure portal — account names are lowercase and globally unique.. If using a connection string, regenerate it from the Azure portal under the storage account's 'Access keys' section and update the linked service.. Check the Azure portal to confirm the storage account still exists and is in the same subscription and region as your ADF instance.. If using a custom endpoint, confirm the endpoint URL is the blob service endpoint (ending in .blob.core.windows.net) not the table or queue endpoint.

Medium severitydata source

Power BI Refresh Error:
DF-Blob-InvalidAccountConfiguration

What does this error mean?

The ADF Mapping Data Flow Azure Blob Storage linked service has an invalid account configuration. The storage account name, endpoint, or connection string in the linked service does not point to a valid, accessible Blob Storage account.

Common causes

1The storage account name in the linked service is misspelled or refers to an account that has been deleted or renamed
2The linked service uses a custom endpoint URL that points to the wrong storage tier (e.g., table or queue endpoint instead of blob endpoint)
3The connection string in the linked service was built with an incorrect account name or key and has never been validated

How to fix it

1Open the Azure Blob Storage linked service in ADF Studio and click 'Test connection' to confirm the account is reachable.
2Verify the storage account name matches exactly what appears in the Azure portal — account names are lowercase and globally unique.
3If using a connection string, regenerate it from the Azure portal under the storage account's 'Access keys' section and update the linked service.
4Check the Azure portal to confirm the storage account still exists and is in the same subscription and region as your ADF instance.
5If using a custom endpoint, confirm the endpoint URL is the blob service endpoint (ending in .blob.core.windows.net) not the table or queue endpoint.

Frequently asked questions

Does this error mean my storage account was deleted?

Possibly, but more often the account name is misspelled in the linked service. Confirm the account exists in the Azure portal before regenerating credentials.

How do I regenerate a Blob Storage connection string?

In the Azure portal, go to the storage account → Access keys → Show keys, copy the full connection string, paste it into the ADF linked service, and click 'Test connection'.

Can this error occur with managed identity authentication?

Yes. With managed identity, the account name must still be correct, and the ADF managed identity must have at least 'Storage Blob Data Reader' or 'Contributor' role on the storage account.

Official documentation: https://learn.microsoft.com/en-us/azure/data-factory/data-flow-troubleshoot-guide