What causes DF-SQLDW-InvalidBlobStagingConfiguration?

The staging Blob storage account name or endpoint in the linked service is incorrect. The storage account was deleted or moved after the staging configuration was set up. The endpoint suffix is wrong for the Azure environment (global vs sovereign cloud). The pipeline was migrated from a different environment and the staging linked service was not updated

How do I fix DF-SQLDW-InvalidBlobStagingConfiguration?

In ADF Studio, open the Synapse dataset or linked service and go to staging configuration section.. Open the Blob staging linked service and verify the storage account name and endpoint suffix.. For global Azure Blob: endpoint should be https:// .blob.core.windows.net.. Click Test connection to verify the staging linked service is reachable.. If the storage account was deleted, create a new one and update the linked service, or switch to ADLS Gen2 staging (which Synapse also supports).. Retry the pipeline after confirming the staging linked service works.

Medium severitydata source

Power BI Refresh Error:
DF-SQLDW-InvalidBlobStagingConfiguration

What does this error mean?

The Azure Blob Storage staging configuration for the Synapse Analytics connector is invalid. A property of the Blob staging linked service — account name, endpoint, or credential — is wrong. Synapse requires a valid staging area for PolyBase or COPY INTO.

Common causes

1The staging Blob storage account name or endpoint in the linked service is incorrect
2The storage account was deleted or moved after the staging configuration was set up
3The endpoint suffix is wrong for the Azure environment (global vs sovereign cloud)
4The pipeline was migrated from a different environment and the staging linked service was not updated

How to fix it

1In ADF Studio, open the Synapse dataset or linked service and go to staging configuration section.
2Open the Blob staging linked service and verify the storage account name and endpoint suffix.
3For global Azure Blob: endpoint should be https://<accountname>.blob.core.windows.net.
4Click Test connection to verify the staging linked service is reachable.
5If the storage account was deleted, create a new one and update the linked service, or switch to ADLS Gen2 staging (which Synapse also supports).
6Retry the pipeline after confirming the staging linked service works.

Frequently asked questions

Why does Synapse Analytics need a staging storage account?

Synapse uses PolyBase or COPY INTO, both of which require data staged in cloud storage. Row-by-row INSERT is not used by data flows. The staging area is the Blob or ADLS Gen2 account in the connector.

Can I switch from Blob staging to ADLS Gen2 staging for Synapse?

Yes — both are supported. ADLS Gen2 (with HNS) is preferred as Synapse's native storage. Switch by creating an ADLS Gen2 linked service and updating the staging configuration.

How is InvalidBlobStagingConfiguration different from InvalidGen2StagingConfiguration?

InvalidBlobStagingConfiguration means the Blob staging linked service has an invalid property. InvalidGen2StagingConfiguration is the same error for ADLS Gen2 staging. The fix approach is identical — check the linked service settings and Test connection.

Will downstream Power BI datasets be affected?

Yes — without valid 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