What causes Unsupported data source for refresh?

Using a data source connector that does not support cloud-based refresh (e.g., local files, certain OData feeds, or Web.Page-based connectors without a gateway). Web connector scripts using the Web.Page function created or updated after November 18, 2016 that are not routed through an on-premises data gateway. Connecting to a local or network file path that is inaccessible from the Power BI cloud service. Using a custom or third-party connector that is not certified for Power BI service refresh

How do I fix Unsupported data source for refresh?

Step 1: In the Power BI service, open the semantic model settings and review the Data Source Credentials section to identify which data source is flagged as unsupported.. Step 2: If you are using a Web connector with the Web.Page function, install and configure an on-premises data gateway, then associate it with your dataset in the service settings.. Step 3: For local file sources (Excel, CSV, etc.), move the files to a cloud-accessible location such as SharePoint Online, OneDrive for Business, or Azure Blob Storage, then update the data source path in Power Query.. Step 4: Replace any unsupported connectors with supported alternatives — consult the official Power BI data sources list at learn.microsoft.com to confirm refresh support status.. Step 5: After reconfiguring the data source, re-enter credentials in the dataset settings and run a manual refresh to confirm the issue is resolved.

High severityconfiguration

Power BI Refresh Error:
Unsupported data source for refresh

What does this error mean?

The semantic model references a data source type that Power BI Service does not support for scheduled or on-demand refresh. Refresh cannot proceed until the data source configuration is updated.

Common causes

1Using a data source connector that does not support cloud-based refresh (e.g., local files, certain OData feeds, or Web.Page-based connectors without a gateway)
2Web connector scripts using the Web.Page function created or updated after November 18, 2016 that are not routed through an on-premises data gateway
3Connecting to a local or network file path that is inaccessible from the Power BI cloud service
4Using a custom or third-party connector that is not certified for Power BI service refresh

How to fix it

1Step 1: In the Power BI service, open the semantic model settings and review the Data Source Credentials section to identify which data source is flagged as unsupported.
2Step 2: If you are using a Web connector with the Web.Page function, install and configure an on-premises data gateway, then associate it with your dataset in the service settings.
3Step 3: For local file sources (Excel, CSV, etc.), move the files to a cloud-accessible location such as SharePoint Online, OneDrive for Business, or Azure Blob Storage, then update the data source path in Power Query.
4Step 4: Replace any unsupported connectors with supported alternatives — consult the official Power BI data sources list at learn.microsoft.com to confirm refresh support status.
5Step 5: After reconfiguring the data source, re-enter credentials in the dataset settings and run a manual refresh to confirm the issue is resolved.

Frequently asked questions

Which data sources support refresh in the Power BI service without a gateway?

Cloud-based sources such as Azure SQL Database, SharePoint Online, Dynamics 365, Salesforce, and most SaaS connectors support direct refresh. Local or on-premises sources require an on-premises data gateway.

Why did refresh work before November 18, 2016 with Web.Page but not after?

Microsoft changed the handling of Web.Page-based connectors on that date, requiring all such connections to be routed through an on-premises data gateway to continue functioning in scheduled refresh.