Forum Discussion
Issue with Cloud Connections appearing under Gateway Connection
Hi aFabricUser,
Thank you for the clarification, and I completely understand your concern.
Based on the scenario you've described, the issue arises due to how Power BI handles hybrid data models, which combine gateway-bound sources like Azure File Share with cloud-based sources such as Dataflows or SharePoint. When these sources are combined within Power BI Desktop, the platform may incorrectly associate cloud sources with the on-premises data gateway during the publish process, resulting in unexpected refresh behavior and source bundling, as seen in the Lineage view.
We recommend adding the Dataflow connection after publishing your dataset to the Power BI Service.
Here’s the ideal approach to avoid the bundling issue:
In Power BI Desktop, build your dataset using only the Azure File Share connection (which routes via the gateway).
Publish the dataset to the Power BI Service.
In the Service, add the Dataflow using DirectQuery or composite model options. This ensures the Dataflow is treated correctly as a cloud-based source and is not routed through the gateway.
By separating the addition of cloud sources from the desktop model, Power BI can more accurately manage source classification and refresh routing, preventing Dataflows or SharePoint connections from being misassigned to the gateway.
If my response was helpful, consider clicking "Accept as Solution" and give us "Kudos" so that other community members can find it easily. Let me know if you need any more assistance!Thank you for being a part of the Microsoft Fabric Community.
Advocate IVFix (3 Steps):
Check Dataset Settings in Power BI Service
Go to Settings > Datasets > Your Dataset.
Under Gateway Connection, ensure only the Azure File Share is mapped to the gateway.
Remove any cloud sources (Dataflows/SharePoint) from the gateway list.
Re-enter Cloud Credentials
For Dataflows/SharePoint, go to Data Source Credentials and re-authenticate using OAuth2 (not gateway).
Restart Gateway & Test
Restart the On-Premises Data Gateway service.
Trigger a manual refresh to verify cloud sources now work directly.
If still failing, recreate the dataset with separated connections.
I've checked all the connectors and only the azure file share is listed on the gateway. Both Sharepoint and Dataflow is using OAuth2. I've also published various versions, dataflow only and sharepoint only (works fine and doesn't attempt to connect thru gateway). Have also tried a report just using the file share and there's no issues. It's only when attempting to publish a bi report that uses various connectors, it'll add them to the gateway section as shown above.
- BhavinVyas3003
Super User
This issue is likely due to Power BI treating the combined model as hybrid, forcing cloud sources into the gateway list again.
Rebuild the dataset using Dataflows or DirectQuery layering:
Move SharePoint and other cloud logic into Dataflows.
Use only the Azure File Share in the dataset.
Pull Dataflows into the model as cloud sources (they won’t route through the gateway)
This separates gateway-bound and cloud-bound processing cleanly and avoids Power BI auto-routing issues.
So the dataflow actually pulls from sharepoint. Are you saying to only add the dataflow into the model after publishing online?
