What causes DF-GEN2-InvalidStorageAccountConfiguration?

The container or file system name in the linked service or dataset is missing, misspelled, or does not exist on the storage account. A combination of settings is invalid — for example, using account key authentication with a user delegation SAS token option. The storage account was deleted or renamed after the linked service was created

How do I fix DF-GEN2-InvalidStorageAccountConfiguration?

Open the ADLS Gen2 linked service in ADF Studio and check for any empty or invalid fields in the 'Connection' settings.. Verify the container (file system) name exists by browsing the storage account in the Azure portal or Storage Explorer.. Open the dataset configuration and confirm the folder path exists and is not pointing to a deleted location.. Test connection the linked service to get a specific error message about what is misconfigured.. If the storage account was deleted or renamed, update the linked service with the new account details or restore the account.

Medium severitydata source

Power BI Refresh Error:
DF-GEN2-InvalidStorageAccountConfiguration

What does this error mean?

The ADLS Gen2 storage account configuration in the ADF linked service has a structural error — such as a missing or invalid container name, a folder path that doesn't exist, or a combination of settings that is not supported for the chosen authentication type.

Common causes

1The container or file system name in the linked service or dataset is missing, misspelled, or does not exist on the storage account
2A combination of settings is invalid — for example, using account key authentication with a user delegation SAS token option
3The storage account was deleted or renamed after the linked service was created

How to fix it

1Open the ADLS Gen2 linked service in ADF Studio and check for any empty or invalid fields in the 'Connection' settings.
2Verify the container (file system) name exists by browsing the storage account in the Azure portal or Storage Explorer.
3Open the dataset configuration and confirm the folder path exists and is not pointing to a deleted location.
4Test connection the linked service to get a specific error message about what is misconfigured.
5If the storage account was deleted or renamed, update the linked service with the new account details or restore the account.

Frequently asked questions

What is the difference between InvalidAccountConfiguration and InvalidStorageAccountConfiguration?

InvalidAccountConfiguration signals an issue with account-level settings (account name, hierarchical namespace, endpoint type). InvalidStorageAccountConfiguration is about a structural setting error in the linked service or dataset.

How do I verify my container name is correct?

In the Azure portal, go to the storage account > Containers (or File systems for Gen2) to see the exact container names ADF needs to reference.

Will this error appear if the storage account was moved to a different resource group?

No — resource group moves don't change the storage account name or endpoint. However, if the account was migrated to a different subscription or region with a new name, the linked service must be updated.

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