What causes UserErrorFileNotFound?

The source file path in the dataset is hardcoded and the file was deleted or moved after the previous run. A dynamic path expression resolves to a path that does not exist (e.g., date-partitioned folder with no data for today). The blob container or ADLS filesystem was renamed or deleted. The SAS token or managed identity lacks List permission on the container, causing a false 'not found' error. File name is case-sensitive and the case does not match

How do I fix UserErrorFileNotFound?

Verify the exact path in Azure Storage Explorer or the Azure portal — confirm the container, folder, and file name.. If using a dynamic path, debug the expression to see what path it resolves to at runtime.. Check if the upstream process that creates the file is running and completing on time.. Review the storage account access control — ensure the ADF managed identity or service principal has Storage Blob Data Reader role.. Add a 'Get Metadata' activity before the copy to validate file existence and branch to a notification activity if missing.. If files are intentionally absent on some days, add a condition to skip the copy rather than failing.

High severitydata source

Power BI Refresh Error:
UserErrorFileNotFound

What does this error mean?

ADF could not find the file or folder specified as the source. The path may be wrong, the file was deleted or moved, or the container does not exist.

Common causes

1The source file path in the dataset is hardcoded and the file was deleted or moved after the previous run
2A dynamic path expression resolves to a path that does not exist (e.g., date-partitioned folder with no data for today)
3The blob container or ADLS filesystem was renamed or deleted
4The SAS token or managed identity lacks List permission on the container, causing a false 'not found' error
5File name is case-sensitive and the case does not match

How to fix it

1Verify the exact path in Azure Storage Explorer or the Azure portal — confirm the container, folder, and file name.
2If using a dynamic path, debug the expression to see what path it resolves to at runtime.
3Check if the upstream process that creates the file is running and completing on time.
4Review the storage account access control — ensure the ADF managed identity or service principal has Storage Blob Data Reader role.
5Add a 'Get Metadata' activity before the copy to validate file existence and branch to a notification activity if missing.
6If files are intentionally absent on some days, add a condition to skip the copy rather than failing.

Frequently asked questions

How do I make the pipeline handle a missing file gracefully?

Add a 'Get Metadata' activity with an 'exists' field check before the copy. Use an If Condition activity to skip the copy and send a notification when the file is absent.

Official documentation: azure-data-factory