What causes QueryUnsupportedCommandBehavior?

Unsupported command behavior in query. Integration runtime configuration is incorrect or outdated. Authentication credentials or permissions are insufficient. The feature or setting is not supported for the selected connector or copy mode

How do I fix QueryUnsupportedCommandBehavior?

Open the copy activity source settings in ADF Studio and check the 'Query' or 'Stored procedure' configuration — ADF only supports sequential SELECT reads for this connector type and does not support non-query behaviors.. If the source uses a stored procedure that performs writes, deletes, or multi-result set operations, refactor it into a SELECT-only stored procedure — ADF reads the first result set returned.. Remove any SET statements, transaction controls, or DDL commands from the source query — ADF passes the query to the driver with sequential read behavior only.. For pre-copy scripts (e.g., truncating a staging table), use the 'Pre-copy script' field in the sink settings or add a Script activity before the copy — do not include it in the source query.. Validate the configuration change using the 'Validate' button before re-running the pipeline.

Medium severityconfiguration

Power BI Refresh Error:
QueryUnsupportedCommandBehavior

What does this error mean?

The SQL command behavior specified in the copy activity source is not supported by ADF. Only sequential reads are supported for the configured source type.

Common causes

1Unsupported command behavior in query
2Integration runtime configuration is incorrect or outdated
3Authentication credentials or permissions are insufficient
4The feature or setting is not supported for the selected connector or copy mode

How to fix it

1Open the copy activity source settings in ADF Studio and check the 'Query' or 'Stored procedure' configuration — ADF only supports sequential SELECT reads for this connector type and does not support non-query behaviors.
2If the source uses a stored procedure that performs writes, deletes, or multi-result set operations, refactor it into a SELECT-only stored procedure — ADF reads the first result set returned.
3Remove any SET statements, transaction controls, or DDL commands from the source query — ADF passes the query to the driver with sequential read behavior only.
4For pre-copy scripts (e.g., truncating a staging table), use the 'Pre-copy script' field in the sink settings or add a Script activity before the copy — do not include it in the source query.
5Validate the configuration change using the 'Validate' button before re-running the pipeline.

Frequently asked questions

Does this configuration error affect every pipeline run?

Yes — configuration errors are deterministic. Every run fails until fixed; retrying does not help.

How do I validate an ADF pipeline configuration before running it?

Click 'Validate' in the ADF authoring UI for configuration checks. For data flows, use Debug mode with a small sample to validate expressions and mappings.

Can dynamic content expressions in ADF cause configuration errors at runtime?

Yes — @activity(), @pipeline(), or @dataset() parameters that resolve to null or an unexpected type cause runtime failures even when design-time validation passes.

Do configuration errors appear in the ADF activity output?

Yes — the ADF Monitor activity detail shows the error code and the specific property that is invalid or missing.

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