What causes DataSource.NotFound?

The file path or URL of the data source has changed since the query was created. The user running the refresh does not have permission to access the data source. The data source server or service is offline or temporarily unavailable. Network path to a local file or UNC share is not accessible from the gateway machine. The database name or table name referenced in the query no longer exists

How do I fix DataSource.NotFound?

Check whether the source file or database connection string still points to a valid location.. If the source was moved or renamed, update the connection in Power BI Desktop and republish.

High severitydata source

Power BI Refresh Error:
DataSource.NotFound

What does this error mean?

Power Query cannot find or access the data source. The source is unreachable, moved, or the user lacks permissions to access it.

Common causes

1The file path or URL of the data source has changed since the query was created
2The user running the refresh does not have permission to access the data source
3The data source server or service is offline or temporarily unavailable
4Network path to a local file or UNC share is not accessible from the gateway machine
5The database name or table name referenced in the query no longer exists

How to fix it

1Check whether the source file or database connection string still points to a valid location.
2If the source was moved or renamed, update the connection in Power BI Desktop and republish.

Beyond the docs

Common practitioner solutions not covered in the official documentation.

1Open Power BI Desktop and click Refresh — the Query Editor will identify the exact failing step
2In Power BI Service, go to dataset Settings → Data source credentials and verify the credentials are current
3If accessing a file share, confirm the gateway service account has read access to the UNC path

Frequently asked questions

Does this error affect multiple datasets at once?

If multiple datasets connect to the same data source, yes — all of them will fail until the source connectivity is restored.

Can this error be caused by a server migration or rename?

Yes — if the server name, database name, or connection string changed (e.g., during a cloud migration), Power BI still holds the old connection details. Update the connection in Power BI Desktop and republish.

Does this error appear in Power BI Desktop?

Sometimes — if you open the .pbix file and attempt a refresh, Desktop will surface the same connection error. This is useful for debugging without affecting the Service dataset.

Will the error resolve automatically once the source is back online?

Only if it was a temporary outage. The next scheduled refresh will succeed automatically. If the connection string changed or credentials expired, manual intervention is needed.

Source · learn.microsoft.com/en-us/power-query/dealing-with-errors