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.
Community SupportHi aFabricUser,
Thankyou BhavinVyas3003, You are correct to highlight the behavior seen when combining multiple sources. This usually occurs because Power BI treats these datasets as hybrid models, causing it to mistakenly route cloud sources (like SharePoint/Dataflows) through the gateway.
To address this, you can adjust the dataset slightly:
Move all SharePoint and Dataflow logic into Dataflows.
Use only the Azure File Share in your main dataset.
Then, pull data from the Dataflows back into your model, ensuring cloud sources remain cloud-based and are not routed via the gateway.
This setup provides a clear separation and avoids Power BI's auto-routing issues.
I hope my suggestions provided valuable insights. If you have any further questions, don’t hesitate to ask in a follow-up message.
If this post helped, please mark it as "Accept as Solution" so others can benefit as well.
Best regards,
Sahasra.
At what stage would I add the dataflow back into the model, before publishing, or after publishing to the service?
The issue resolves if I'm just using file share content or just Dataflows. My main content is from the File Share, but if I add the cloud connection to the Dataflow within BI Desktop, then publish. Same issue happens.
Here's an example of another report I'm having issues with. Same thing. Lineage shows separate sources but still bundles the Dataflow within the gateway.
- v-sgandrathi
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.
Thank you for the clarification. This is really helpful!