Power Platform Community Forum Thread Details

Hi everyone,

We're implementing ALM for Power Platform and have set up dedicated Dev, Test, and Prod environments to keep production data separate from dev and test data.
We're running into two issues with connection management that we're hoping the community can help with:

Issue 1: Connection References Not Usable in Flows
We followed guidance about using a service account (SA) with a Core Connection Reference Solution:

Created connections using our SA
Added connection references to a core solution
Developers can import these references into their solutions

However, developers cannot use these connections within flows. Everything we've read says this should be possible, but we can't get it functioning.

Issue 2: Deployment Creates Developer-Owned Connections
When we deploy solutions to new environments, we're forced to recreate connections, which then become owned by whichever developer is doing the deployment. We want all connections centrally managed under the service account, not tied to individual developer accounts.

Questions:

Has anyone successfully implemented service account-owned connections that multiple developers can use? If so, what are we missing?
How do you prevent connections from becoming owned by the deploying developer during environment deployments?
What's the community's recommended best practice for connection management in a multi-developer ALM setup?

Our research shows many different approaches to Power Platform ALM, but we haven't found clear best practices around connection management.

I have attached two images showing that the connection reference is in the same solution, but it cannot be accessed from within the flow.

Any guidance would be greatly appreciated!