Notifications
Announcements
Hi everyone. I'm having an issue with my connection references not cooperating after publishing from Dev to Prod. In my sandbox environment I have a connection reference set up and owned by a service account. It works just as expected in the dev environment, great! However, when I import the solution to my Prod environment, the connection owner is changed to my personal account. So now whenever a prod cloud flow runs using this connection, it is using my account rather than the service account. I can't figure out how or why this is happening. Any suggestions on what I'm doing wrong here? I just want the connection to remain the same between my dev and prod environments.
Hi @IanJB
Connection references may change when I import a solution if when users are different
You can use this method according to the official documentation so when you import you put the connection string you need
https://learn.microsoft.com/en-us/power-platform/alm/conn-ref-env-variables-build-tools
Thanks @Jmanriquerios .This seems a bit complex for my needs, and I'm not running an automated deployment solution. From that documentation it mentions:
Which sounds to me like at some point in the past (maybe the first time the solution was imported to Prod?) it used one set of credentials for the connection reference, and it's just stuck with that ever since. On subsequent solution imports there is no prompt to update this information, even if I import the solution from the desired account. Any idea on how this can be updated on the Prod environment? On the dev environment the connection reference is set to allow customizations:
But it is going into a managed solution in the Prod environment so the connection reference is locked for edits.
Found the answer in an old power automate thread:Solved: Changing a Connection Reference in a Managed Solut... - Power Platform Community (microsoft.com)In the prod environment simply go to the Default Solution, find the connection reference in question, and it is editable from there. Once updated all of the flows in the managed solution using the reference now are linked to the correct credentials. Very easy!
Hi, I believe the account used for the deployment takes ownership of all the resources in the solution. So if you connect with the service account for the deployment it should be ok. Doing changes in the default solution creates solution layers which can be problematic as they are applied on top of the deployed solution. It is helpful when used as a hot fix in production. Ultimately you should always delete the solution layer before deploying a new version solution in prod.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
In our never-ending quest to improve we are simplifying the forum hierarchy…
We are honored to recognize Ajay Kumar Gannamaneni as our Community Spotlight for December…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
WarrenBelz 721 Most Valuable Professional
Michael E. Gernaey 320 Super User 2025 Season 2
Power Platform 1919 268