[ALM Accelerator - Feature]: Ability to share Flows and Connectors with multiple groups

[BJHF-power]

Is your feature request related to a problem? Please describe.

Currently, we automatically share every Flow and Custom Connector in a solution with the same groups that any Canvas App(s) in the solution are shared with. We do this to ensure that there are no Connection permissions issues for users when opening the app, and to ensure that any App-connected Flows are able to execute when the user interacts with the app.

However, even when we include multiple flow.sharing.xxxx.xxxx or connector.teamname.xxxx.xxxx values for different groups in the Deployment Settings, the Flow and Connection only get shared with 1 group.

example for Flows, trying to share with 3 different groups (same behavior for connectors, screenshots below are interchangeable):

results in the following customDeploymentSettings.json:

but only 1 pipeline variable:

and the FLow being shared with that 1 group 3 times:

Describe the solution you'd like

Would like to be able to share each Flow and Connector with >1 group

Describe alternatives you've considered

No response

Additional context?

No response

[BJHF-power]

I will add here as well - it would be preferable to share with Groups based on their Azure Object IDs, rather than display names, as is done for sharing Canvas Apps in the Deployment Settings

[RajeevPentyala]

@BJHF-power The capability to share Flows and Connectors with multiple Dataverse teams has been implemented. Users can add multiple entries in the 'User Setting' record within the 'ALM Accelerator for Power Platform Administration' model-driven app, as demonstrated below. This feature will be available in the September 2023 release.

[BJHF-power]

@RajeevPentyala great news - and the format will continue to follow the existing pre-September pattern it looks like, correct? (i.e., not switching to provide the AAD group ID instead of name)

[CoEStarterKitBot]

@BJHF-power This has been fixed in the latest release. Please install the latest version of the toolkit following the instructions for installing updates. Note that if you do not remove the unmanaged layers as described there you will not receive updates from us.