Join us for an expert-led overview of the tools and concepts you'll need to pass exam PL-300. The first session starts on June 11th. See you there!
Get registeredJoin us at FabCon Vienna from September 15-18, 2025, for the ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM. Get registered
Hi all,
I have one semantic model connected to a fabric lakehouse by a cloud connection in a dev envoironment and one model in test environment.
When deploying the model from dev workspace to test workspace the Cloud Connection resets to Default. Is there some setting that prevents it from resetting after each deployment?
Br
Adrian
Solved! Go to Solution.
Hello @adnyk
Unfortunately, there is no direct method to prevent the cloud connection from resetting to default settings after deployment. While deployment rules can adjust parameters within the semantic model or its source, they do not support altering the connection type itself. Currently, Microsoft Fabric lacks a built-in feature to maintain cloud connection settings across deployments. The recommended approach is to update the cloud connection in the test environment after each deployment.
If you find this post helpful, please mark it as an "Accept as Solution" and give a KUDOS.
Thank you!
Hello @adnyk
Thank you for reaching out to Microsoft Fabric Community Forum.
Thank you @nilendraFabric for your response.
Could you please confirm if your query have been resolved the solution provided by @nilendraFabric ? If they have, kindly mark the helpful response and accept it as the solution. This will assist other community members in resolving similar issues more efficiently.
Thank you
Hello @adnyk
When deploying a semantic model across workspaces, Microsoft Fabric does default to resetting the cloud connection to "Default: Single Sign-On (SSO)" unless explicitly reconfigured. This behavior is linked to how deployment pipelines handle metadata updates but do not automatically retain environment-specific settings like cloud connections
Cloud connections are environment-specific and need to be reconfigured after deployment unless a mechanism such as deployment rules
If this is helpful please accept the solution and give kudos
https://learn.microsoft.com/en-us/fabric/cicd/deployment-pipelines/create-rules?tabs=new-ui
Hi @nilendraFabric and thank you for your reply.
As I understand it in deployment rules I can only change either parameters set inside the semantic model or the source of the model but not the connection used to access the source?
Deployment pipelines do not support changing the type of connection used to access the source. For example, if your semantic model uses a live connection or DirectQuery, you cannot switch it to another connectivity mode during deployment
So would you then say that the answer to my question is "No there is no way to prevent the Connection to change to default after deployment?"
If this is the case then we will have to look into other options for deploying.
Hello @adnyk
Unfortunately, there is no direct method to prevent the cloud connection from resetting to default settings after deployment. While deployment rules can adjust parameters within the semantic model or its source, they do not support altering the connection type itself. Currently, Microsoft Fabric lacks a built-in feature to maintain cloud connection settings across deployments. The recommended approach is to update the cloud connection in the test environment after each deployment.
If you find this post helpful, please mark it as an "Accept as Solution" and give a KUDOS.
Thank you!
User | Count |
---|---|
78 | |
44 | |
16 | |
11 | |
7 |
User | Count |
---|---|
93 | |
88 | |
27 | |
8 | |
8 |