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.