Sharing a Connection Reference

[sperry1625]

We are starting Coauthored Development for our Power Apps. We are running into some issues.  Here is a scenario:

Scenario

Developer 1

1. Creates New Solution for Shared Connection References (IT | Common | Connections)
   1. Common Solution contains Connection References for
      1. SharePoint Online
      2. Office 365 Outlook
      3. Office 365 Users

Developer 2

1. Creates new solution
2. Creates/imports Power App and related Flows

Problem

Developer 2, while creating flows, cannot see the common shared connection references created by Developer 1. Why?

If Developer 1 goes into the flow created by developer 2, they can see the connection References and use them. Save the Flow. Then Developer 2 can edit the flow and the shared connection references are still selected (although developer 2 cannot see the account used by the connection reference).

I can see a possible reason; the underlying Connection in the Shared Connection Reference is not accessible by Developer 2.

Even without using a Shared Connection, if developer 1 creates a Connection Reference local to the solution developer 2 will still have an issue as they will not have access to the underlying connection.

How is coauthoring supposed to work if solution components cannot be shared? How does one connection reference use different underlying connections based on what the developer has access to?

Connections can only be shared with Service Principals, not individuals. How is this supposed to work?

Any thoughts would be appreciated.

Thank you.

Regards,

-S

[AsaurdiffADTill]

It's possible that setting up a Co-owner for all the flows Dev 1 creates as Dev 2 will help with editing flows. 

As you have stated NEW flows would not have the same level of access. Dev 2 would be required to share their new flows with Dev 1. Dev 1 would then need to manually swap to the "primary" connectors. Then after that Dev 2 may see them again. 

FURTHER ISSUE: 

When promoting these flows to another environment the primary owner would need to promote the solution. Not only do you have one chance to create the connections in the next environment correctly (making sure they are still connected to the right account) but if different dev's are setting up their own "primary" connections then you would ruin the validity of the connections in the next environment. This presses more that all devs are sharing passwords... which is not a great idea at all.

MSoft has added a feature in Power Pipelines that allows you to "Update connection references" now. It brings back the option to change the connections being used in the next environment. But again, if Dev 1 and 2 are promoting they do not have the same level of access to the connections created. 

The answer to this for MSoft's sake is the "share" button under connection should use accounts. That way as dev's create flows they have the option to use connection references outside the flow, but within the solution, that they have shared and if a connection needs to be altered all the devs are sharing the SAME list of connections.