Fabric - Data Gateway connection

Hi Anonymous 

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.

Hi Anonymous ,

I hope the response provided helped in resolving the issue. If you still have any questions, please let us know we are happy to address.

Regards,
Akhil.