MetricSign
EN|NLRequest Access
Medium severityconfiguration

Power BI Refresh Error:
SkipInconsistencyDataNotSupportedForNonDirectBinaryCopy

What does this error mean?

The fault tolerance setting to skip inconsistent data is only available for direct binary copy operations. Disable this setting or switch to direct binary copy mode.

Common causes

  • 1Skip inconsistency 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. 1In the copy activity, go to the Settings tab, and disable the fault tolerance option for skipping inconsistent data — this option is only valid for direct binary copy (Binary format, no format conversion).
  2. 2For format-converting copies, handle data quality in a downstream Data Flow with a Conditional Split to route inconsistent rows to a separate output.
  3. 3To use direct binary copy (where this setting is supported), both source and sink must be file-based stores using Binary format with no schema mapping applied.
  4. 4If the inconsistent data skipping is not critical, disable the setting and let the copy fail on bad data — this makes the pipeline fail visibly rather than silently dropping rows.
  5. 5Validate the configuration after removing the incompatible setting and test 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

Other configuration errors