Gateway connection/Cloud connection settings reset after source control updates

Thankyou, Olufemi7 for your response.

Hi notsobad__,

Based on our understanding, when we perform updates from Git, Fabric may not always carry out an in-place update. In certain scenarios, it may overwrite workspace metadata or recreate the semantic model with a new internal identity.

As a result, connection related settings such as the gateway toggle, cloud connection mapping, and credentials may not be fully preserved as part of the Git tracked model definition. Therefore, these bindings may reset when an overwrite or recreation occurs. This could explain why the issue affects only certain semantic models, while others remain unaffected. It may appear random because it typically occurs in cases where metadata overwrite, logical ID mismatches, for example, due to branch changes, renames, or sync differences , or datasource/query changes occur. These changes may include modifications to M queries, parameters, or connection strings. Models that do not experience such differences may remain unchanged, which makes the behaviour seem inconsistent.

As a validation step, please also check whether any of the affected models combine multiple sources or include a source that requires a gateway. In such cases, Power BI may enforce gateway usage even for cloud sources.

If the issue occurs consistently without any model or datasource changes, we kindly request you to raise a Microsoft Support ticket for further investigation using the following link:Microsoft Fabric Support and Status | Microsoft Fabric

Additionally, please refer to the links provided below:
Get started with Git integration - Microsoft Fabric | Microsoft Learn
Git integration process - Microsoft Fabric | Microsoft Learn
On-premises data gateway - Power BI | Microsoft Learn

We hope the information provided helps resolve the issue. Should you have any further queries, please feel free to contact the Microsoft Fabric community.

Thank you.