What causes QueryMissingFormatSettingsInDataset?

Query missing format settings in dataset. 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 QueryMissingFormatSettingsInDataset?

Open the dataset in ADF Studio and check that a file format is selected — the dataset must have a format type (Delimited text, JSON, Parquet, ORC, Avro, etc.) configured before a query can be run against it.. If the dataset was created as a 'Binary' dataset for file copy without transformation, switch to the appropriate format type that matches the source file — Binary datasets do not support schema-based queries.. Go to dataset's 'Schema' tab and import or manually define the column schema — a dataset with no schema definition cannot be queried with column references.. Check whether the copy activity source settings reference a query or column filter — if so, the dataset must have an explicit format and schema defined, not a linked service and container path.. Validate the dataset configuration using the 'Validate' button in ADF Studio before re-running the pipeline.

Medium severityconfiguration

Power BI Refresh Error:
QueryMissingFormatSettingsInDataset

What does this error mean?

The dataset used in the copy activity is missing required format settings. The dataset schema or format configuration must be specified before a query can be executed.

Common causes

1Query missing format settings in dataset
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 dataset in ADF Studio and check that a file format is selected — the dataset must have a format type (Delimited text, JSON, Parquet, ORC, Avro, etc.) configured before a query can be run against it.
2If the dataset was created as a 'Binary' dataset for file copy without transformation, switch to the appropriate format type that matches the source file — Binary datasets do not support schema-based queries.
3Go to dataset's 'Schema' tab and import or manually define the column schema — a dataset with no schema definition cannot be queried with column references.
4Check whether the copy activity source settings reference a query or column filter — if so, the dataset must have an explicit format and schema defined, not a linked service and container path.
5Validate the dataset configuration using the 'Validate' button in ADF Studio 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