What causes SkipForbiddenFileNotSupportedForThisConnector?

Skip forbidden file not supported for this connector. 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 SkipForbiddenFileNotSupportedForThisConnector?

Open the copy activity Settings tab and disable the 'Skip forbidden files' fault tolerance option — this setting is only supported for specific file-based connectors (Azure Blob Storage, ADLS Gen2, Amazon S3).. Check the ADF documentation for the specific source connector to confirm whether skip-forbidden is supported — tabular sources (SQL, REST APIs, etc.) do not support file-level fault tolerance.. The preferred fix is resolving the access denied issue — verify the linked service authentication and confirm the identity has the required read permissions.. If forbidden files are genuinely inaccessible and should be skipped, switch to a supported connector or use Get Metadata + ForEach with per-file error handling.. Validate the pipeline after removing the incompatible setting.

Medium severityconfiguration

Power BI Refresh Error:
SkipForbiddenFileNotSupportedForThisConnector

What does this error mean?

The fault tolerance setting to skip forbidden files is not supported by the connector configured as the source. Check the ADF documentation for supported connectors.

Common causes

1Skip forbidden file not supported for this connector
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 forbidden files' fault tolerance option — this setting is only supported for specific file-based connectors (Azure Blob Storage, ADLS Gen2, Amazon S3).
2Check the ADF documentation for the specific source connector to confirm whether skip-forbidden is supported — tabular sources (SQL, REST APIs, etc.) do not support file-level fault tolerance.
3The preferred fix is resolving the access denied issue — verify the linked service authentication and confirm the identity has the required read permissions.
4If forbidden files are genuinely inaccessible and should be skipped, switch to a supported connector or use Get Metadata + ForEach 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