MetricSign
EN|NLRequest Access
Medium severityconfiguration

Power BI Refresh Error:
SkipInvalidFileNameNotSupportedForNonDirectBinaryCopy

What does this error mean?

The fault tolerance option to skip files with invalid names is only available for direct binary copy between file-based stores.

Common causes

  • 1Skip invalid filename not supported for non-direct 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

  1. 1Open the copy activity Settings tab and disable the 'Skip invalid file names' fault tolerance option.
  2. 2To use this setting, switch both datasets to Binary format and remove schema mappings — that qualifies the copy as direct binary mode.
  3. 3If format conversion is required, rename the problematic source files to use valid characters before the copy, or filter them using Get Metadata + Filter activities.
  4. 4Files with invalid names (characters not allowed by the destination file system) cause deterministic failures — renaming them upstream is the correct long-term fix.
  5. 5Validate the configuration 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

Other configuration errors