What causes SkipAllErrorFileNotSupportedForNonBinaryCopy?

Skip all error files not supported for non-binary copy. 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 SkipAllErrorFileNotSupportedForNonBinaryCopy?

Open the copy activity Settings tab and disable the 'Skip all error files' fault tolerance option.. If the copy involves format conversion (CSV to Parquet, JSON to Delimited Text, etc.), this setting is incompatible — disable it and let the copy fail visibly on error files.. To use this setting, switch both datasets to Binary format and remove all format conversion and schema mappings — this qualifies the copy as binary file copy.. If you need to handle error files with format conversion in place, use a Get Metadata + ForEach pattern to process files individually with per-file error handling.. Validate the pipeline after removing the incompatible setting.

Medium severityconfiguration

Power BI Refresh Error:
SkipAllErrorFileNotSupportedForNonBinaryCopy

What does this error mean?

The fault tolerance setting to skip all error files is only available when copying files in binary format. Disable this setting or switch to binary copy mode.

Common causes

1Skip all error files not supported for non-binary copy
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 Settings tab and disable the 'Skip all error files' fault tolerance option.
2If the copy involves format conversion (CSV to Parquet, JSON to Delimited Text, etc.), this setting is incompatible — disable it and let the copy fail visibly on error files.
3To use this setting, switch both datasets to Binary format and remove all format conversion and schema mappings — this qualifies the copy as binary file copy.
4If you need to handle error files with format conversion in place, use a Get Metadata + ForEach pattern to process files individually with per-file error handling.
5Validate the pipeline after removing the incompatible setting.

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