What causes DF-SQLDW-StagingStorageNotSupport?

The Synapse Analytics sink does not have a staging linked service configured in the sink Settings tab. The staging linked service field was left blank when the data flow was created or last edited. The pipeline was upgraded or migrated and the staging configuration was lost. A copy activity was converted to a data flow and the staging configuration was not carried over

How do I fix DF-SQLDW-StagingStorageNotSupport?

Open the failing data flow in ADF Studio and click the Synapse Analytics sink transformation.. In the sink Settings tab, find the Staging linked service field — it must reference an Azure Blob Storage or ADLS Gen2 linked service.. If the field is empty, click the field and select or create a linked service pointing to a staging storage account in the same Azure region as the Synapse workspace.. In the staging settings, also specify the staging container (and optionally a folder path) where ADF will write intermediate files during the load.. Test connection the staging linked service to verify ADF can write to it.. Save and re-run the data flow.

Medium severityconfiguration

Power BI Refresh Error:
DF-SQLDW-StagingStorageNotSupport

What does this error mean?

No staging storage is configured for the Synapse Analytics sink, but staging is required. Writing to Synapse from a Mapping Data Flow requires Azure Blob Storage or ADLS Gen2 staging for PolyBase or COPY INTO.

Common causes

1The Synapse Analytics sink does not have a staging linked service configured in the sink Settings tab
2The staging linked service field was left blank when the data flow was created or last edited
3The pipeline was upgraded or migrated and the staging configuration was lost
4A copy activity was converted to a data flow and the staging configuration was not carried over

How to fix it

1Open the failing data flow in ADF Studio and click the Synapse Analytics sink transformation.
2In the sink Settings tab, find the Staging linked service field — it must reference an Azure Blob Storage or ADLS Gen2 linked service.
3If the field is empty, click the field and select or create a linked service pointing to a staging storage account in the same Azure region as the Synapse workspace.
4In the staging settings, also specify the staging container (and optionally a folder path) where ADF will write intermediate files during the load.
5Test connection the staging linked service to verify ADF can write to it.
6Save and re-run the data flow.

Frequently asked questions

Why can't ADF write directly to Synapse without staging?

Dedicated SQL pools use PolyBase or COPY INTO — both require staged data. Direct T-SQL row inserts are orders of magnitude slower and not used by data flows. Staging is mandatory for any meaningful volume.

Is staging also required when reading from Synapse, not writing?

Staging for reads is optional in copy activities but configured for performance. In Mapping Data Flows, writing (sink) is the side that requires staging; source reads from Synapse do not require a staging area.

Does the staging container need to exist before the pipeline runs?

Yes — ADF does not auto-create the staging container. Create the container in the Azure portal before running the pipeline. The folder path within the container is created automatically by ADF on first run.

Will downstream Power BI datasets be affected?

Yes — without staging, the Synapse write fails entirely and the target table receives no data. Dependent datasets will show stale or empty results.

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