Fabric - Data Gateway connection

[mariaroche]

My semantic model on fabric was configured with an On-Prem gateway to Azure SQL. I then configured it with a cloud connection to the same source. I have scheduled a refresh but the scheduled refresh failed. On inspection I noticed the gateway was not chosen. I re-selected the gateway and refreshed manually. It worked. But every scheduled refresh fails and when I check the gatway is not chosen. Is this a transient error? I have another semantic model with the same cloud gateway but it works fine!

[v-agajavelly]

Hi @mariaroche ,

Were you able to try out the suggested steps by  super user, following them should help resolve the issue. Let us know how it goes so we can look into any remaining challenges if needed.

Regards,
Akhil.

[v-agajavelly]

Hi @mariaroche ,

Thanks @shashiPaul1570_  lot for your detailed explanation really appreciate you calling out the root cause around mixed connections (cloud + on-prem).

@mariaroche did you get a chance to work on the solution provided by the super user? It should resolve the issue if followed step by step. Let us know how it goes. Happy to help you.

Regards,
Akhil.

[shashiPaul1570_]

Hi @mariaroche 

Thanks for bringing this up — this seems to be a known behavior when multiple connections (cloud + on-prem gateway) are configured for the same semantic model in Microsoft Fabric.

 Why This Happens

When a semantic model is initially configured with an on-premises gateway and later updated to use a cloud connection, Power BI may fail to persist the correct gateway selection, especially during scheduled refresh. Manual refreshes often work because the gateway gets selected in-session, but scheduled refresh resets it.

---

Recommended Solution

1. Remove the cloud connection (if not needed) from
   Power BI Service → Manage Gateways → Data Source Settings
   This avoids connection conflicts.

2. Manually re-bind the correct gateway

   • Go to your semantic model in the Power BI service

   • Click on Settings > Gateway Connection

   • Select your on-premises gateway

   • Save the settings

3. Re-configure the scheduled refresh after saving the above change.

4. If the issue persists

   • Reopen your PBIX in Power BI Desktop

   • Repoint it to the correct gateway data source

   • Republish the model — this can help persist the correct settings

 

This issue is more likely to happen if there are duplicate data source credentials or if a model is trying to fallback between gateway types.

Let me know if this helps resolve the issue — and feel free to mark this as a solution if it works.