What causes DF-SQLDW-InvalidGen2StagingConfiguration?

The staging ADLS Gen2 linked service references an account that does not have Hierarchical Namespace (HNS) enabled — it is a regular Blob account being used as Gen2. The account name or endpoint in the Gen2 staging linked service is incorrect. The staging storage account was deleted or moved after the configuration was set up. The pipeline was migrated from a different environment and the Gen2 staging linked service was not updated

How do I fix DF-SQLDW-InvalidGen2StagingConfiguration?

In ADF Studio, open the ADLS Gen2 staging linked service used by the Synapse connector.. Verify the storage account name and confirm the endpoint is https:// .dfs.core.windows.net (note: DFS endpoint, not blob).. In the Azure portal, open the storage account and check Settings > Properties > Hierarchical namespace — it must show 'Enabled' for ADLS Gen2.. If HNS is disabled, switch the staging to an Azure Blob Storage linked service instead (using the .blob.core.windows.net endpoint).. Click Test connection on the staging linked service to verify it works, then save and retry the pipeline.

Medium severitydata source

Power BI Refresh Error:
DF-SQLDW-InvalidGen2StagingConfiguration

What does this error mean?

The ADLS Gen2 staging configuration for the Synapse Analytics connector is invalid. A property of the Gen2 staging linked service — account name, endpoint, or Hierarchical Namespace setting — is wrong or inaccessible.

Common causes

1The staging ADLS Gen2 linked service references an account that does not have Hierarchical Namespace (HNS) enabled — it is a regular Blob account being used as Gen2
2The account name or endpoint in the Gen2 staging linked service is incorrect
3The staging storage account was deleted or moved after the configuration was set up
4The pipeline was migrated from a different environment and the Gen2 staging linked service was not updated

How to fix it

1In ADF Studio, open the ADLS Gen2 staging linked service used by the Synapse connector.
2Verify the storage account name and confirm the endpoint is https://<accountname>.dfs.core.windows.net (note: DFS endpoint, not blob).
3In the Azure portal, open the storage account and check Settings > Properties > Hierarchical namespace — it must show 'Enabled' for ADLS Gen2.
4If HNS is disabled, switch the staging to an Azure Blob Storage linked service instead (using the .blob.core.windows.net endpoint).
5Click Test connection on the staging linked service to verify it works, then save and retry the pipeline.

Frequently asked questions

What is the difference between .blob.core.windows.net and .dfs.core.windows.net?

.blob.core.windows.net is the Blob endpoint. .dfs.core.windows.net is the ADLS Gen2 endpoint — only available when HNS is enabled. If HNS is disabled, use .blob with a Blob Storage linked service.

Does Synapse Analytics require ADLS Gen2 specifically for staging?

No — Synapse supports both Azure Blob Storage and ADLS Gen2 for staging. ADLS Gen2 is preferred for Synapse workspaces (native storage tier, better performance), but regular Blob is also supported.

How do I check if an existing storage account has HNS enabled?

In the Azure portal, open the storage account > Settings > Properties and look for 'Hierarchical namespace'. HNS cannot be enabled after creation — create a new ADLS Gen2 account if it was not set at creation.

Will downstream Power BI datasets be affected?

Yes — without valid Gen2 staging, the Synapse write fails and the table receives no new data. Dependent datasets will show stale data.

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