Forum Discussion
Gateway connection/Cloud connection settings reset after source control updates
Hi, maybe someone else encountered this problem.
We have our reports synced with remote repository Azure Devops, in few semantic models we have a problem that occurs after workspace items are updated within source control.
The gateway connections button turns on from off position(we use only cloud connections that are not included in any gateways).
So the whole refresh process failes in next attempt. We need to go to the settings, turn off "Use an On-premises or VNet data gateway" and map once again each datasource to personal cloud connect. This is a bug? Or we missed something.
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 LearnWe 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.
5 Replies
Hello notsobad__,
When Power BI workspace items are updated from source control (Azure DevOps/Git), cloud vs gateway connection settings can reset because Git sync only stores metadata, not data source credentials or connection toggles. This is expected behavior, not a bug.
Fix / Mitigation:
Remap datasources to cloud connections manually after update or
Automate remapping using Power BI REST API (UpdateDatasources) after deployment.
References:
Ok, but why they "can" reset. The situation occurs randomly, only for few specific semantic models.
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 LearnWe 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.
Hi notsobad__,
We would like to follow up and see whether the details we shared have resolved your problem. If you need any more assistance, please feel free to connect with the Microsoft Fabric community.
Thank you.Hi notsobad__,
We are following up to see if what we shared solved your issue. If you need more support, please reach out to the Microsoft Fabric community.
Thank you.
