How to prevent semantic model switching from Cloud to Gateway (published but disconnected)

[Sysitwp]

Hi,

We have a semantic models that has no references to local storage (Data source settings-> Data sources in current file), only two cloud storage (SalesForce & SharePoint).

In PowerBI online, we have setup cloud connections for both of these sources, and it refreshes without issue.

However, if any one of the users makes a change to the PowerBI pbix file (desktop) and publishes it, they get "Your file was published, but disconnected" and it changes the model to "Use An On-premises or VNet data gateway" = TRUE. This obviously doesn't work as we don't use/want a gateway to their laptops. In the sementic model settings it even says it is not required:

"You don't need a gateway for this semantic model, because all of its data sources are in the cloud, but you can use a gateway for enhanced control over how you connect."

If there are only data sources in the cloud, why is it changing to use a gateway and giving "Your file was published, but disconnected"?

Thanks

[v-echaithra]

Hi @Sysitwp ,

We would like to confirm if you've successfully resolved this issue or if you need further help. If you still have any questions or need more support, please feel free to let us know. We are more than happy to continue to help you.

Thank you for your patience and look forward to hearing from you.
Best Regards,
Chaithra E.

[Poojara_D12]

Hi @Sysitwp 

The issue you're encountering stems from how Power BI Desktop handles data source definitions and metadata during development and publishing. Even though your semantic model only connects to cloud-based sources like Salesforce and SharePoint—which do not require a data gateway—Power BI Desktop sometimes embeds residual metadata from the local environment, especially if the file was initially authored or edited using a local credential context. When a user opens the PBIX file on their machine and republishes it, Power BI Service may interpret some embedded metadata (such as authentication method defaults or local data source previews) as implying a potential need for a gateway, which causes the "Your file was published, but disconnected" message and toggles the semantic model to require an on-premises or VNet data gateway. This behavior occurs despite the portal stating that a gateway isn't technically required, and it's usually resolved by re-binding the cloud connections manually after publishing. To avoid this, ensure that all authors use organizational cloud credentials in Power BI Desktop, clear any preview cache before publishing, and consistently bind their PBIX files to the cloud data source definitions (via Data Source Settings → Global Permissions). This helps prevent the service from interpreting the data sources as local or hybrid when the report is published.

[v-echaithra]

Hi @Sysitwp ,

As we haven’t heard back from you, so just following up to our previous message. I'd like to confirm if you've successfully resolved this issue or if you need further help.

If yes, you are welcome to share your workaround and mark it as a solution so that other users can benefit as well. If you find a reply particularly helpful to you, you can also mark it as a solution.
If you still have any questions or need more support, please feel free to let us know. We are more than happy to continue to help you.

Thank you for your patience and look forward to hearing from you.
Best Regards,
Chaithra E.

[Sysitwp]

Hi,

Unfortunately it's not solved yet.

I'm not sure what to try next, there is no gateway connection as both sources connected are cloud connections. However, each time we upload, the connections gets disconnected.

[v-echaithra]

Hi @Sysitwp ,

Standardize the credentials across all Developers.

Go to File > Options and Settings > Data Source Settings > Global Permissions.

Remove all existing credentials for SharePoint, Salesforce, and any other source related to the PBIX. Re-add them using Organizational Account (OAuth) only.

SharePoint > Choose OAuth with Microsoft Account.

Salesforce > Choose OAuth via cloud connector, not Basic.

Do not use anonymous for SharePoint Folder or Web.Contents, even if it works in Desktop.

If you're accessing structured data, prefer the SharePoint Online List connector.

The SharePoint Folder connector internally uses Web.Contents, which is not fully gateway-agnostic in Desktop, even if the final source is cloud. Explicitly use SharePoint.Contents instead of Web.Contents, and also ensure all path logic is driven by parameterized strings without dynamic functions that depend on user context.
Check privacy levels on each dev machine because mismatched or private privacy settings cause Power BI to create isolated containers, which can lead to hybrid behavior and false gateway triggers.

Options > Privacy → Set to “Always ignore Privacy Level settings”.

In Data Source Settings, ensure both sources (Salesforce, SharePoint) are set to Organizational or Public.

Clear preview cache & Re-publish from a clean environment with standardized credentials.

Validate Cloud Binding in Power BI Service After Publish.

Go to the semantic model in Power BI Service > Settings > Data source credentials.

Confirm both sources say "Cloud data source" and do not list a gateway.

If any credential is missing, re-enter it as OAuth.

If this helped, please mark it as the solution so others can benefit too. And if you found it useful, kudos are always appreciated.

Thanks,
Chaithra E.

[v-echaithra]

Hi @Sysitwp ,

May I ask if you have gotten this issue resolved?

If it is solved, please mark the helpful reply or share your solution and accept it as solution, it will be helpful for other members of the community who have similar problems as yours to solve it faster.

Regards,
Chaithra.

[v-echaithra]

Hi @Sysitwp ,

At some point you might have created a gateway connection for a cloud data source. Delete that connection from the gateway, re-publish the semantic model, and then do not select a gateway.

The sources in the Power BI semantic model, does not require a gateway connection.

1) Verify all data sources for any misconfigurations. Ensure the source paths and connection strings are accurate, and confirm they are correctly mapped between cloud and local data sources.

2) If feasible, please try to publish one semantic model at a time to determine if a particular model is causing the issue. Exporting the model to a local file and then re-importing it may sometimes resolve connection problems.

3) Kindly review the error logs to identify any information that may indicate the root cause of the failures. Pay special attention to messages concerning missing gateways or sources.

4) Verify that all users involved have the appropriate access permissions to the required data sources.

If this post helps, then please give us ‘Kudos’ and consider Accept it as a solution to help the other members find it more quickly.

Thank you.

Chaithra E.

[freginier]

Hey there!

Here are some possible solutions: 

1. Desktop Connection Type Changes: When a user works on the .pbix file in Power BI Desktop, Power BI might interpret the connection as local instead of a cloud-based source.
Solution: Ensure that the data sources in Power BI Desktop are explicitly set to use cloud connectors (like SharePoint Online & Salesforce Online) instead of local file paths.

2. Publishing from a Different Environment: If a user publishes from a different Power BI tenant or workspace, the model might lose its original cloud connection settings.
Solution: Ensure that users are publishing to the correct workspace where cloud credentials are already configured.

Hope this helps! 

😁😁

[Sysitwp]

Thanks for your reply.

1. The data is set to use "SharePoint Folder" which then requires a Site URL. We are using https://***.sharepoint.com/sites/*** , so i'm quite sure this is SharePoint Online.

For Salesforce, we use "Salesforce Objects". There are two options but both are cloud, since Salesforce is cloud-only.

There are no other sources in Options -> Data Source Settings -> Data sources in current file.

According to the message in the semantic model settings (quoted in first post), it's already using cloud-only sources.

I don't know how else people would be working on PowerBI without using the desktop client as it has a lot more features?

2. The users are all in the same tenant and upload to the same workspace.

Thanks