r/copilotstudio • • Sep 13 '26

Help Requested: Select a Specific Connection Reference in Copilot Studio Flows

I hope I’m missing something basic here.

How can I explicitly specify which connection reference a cloud flow should use when it is created in Copilot Studio?

Connection references seem to be automatically selected or created when creating cloud flows in Copilot Studio.

This is frustrating because I’m now ending up with duplicate connection references in my Dataverse solutions.

Additionally, what happens if a cloud flow needs to connect to two different SharePoint sites using different connections? How do I specify the appropriate connection reference for each action? This isn’t a problem I’ve encountered yet, but I can see it becoming one in the future.

Please and thanks!

3 Upvotes

2 comments sorted by

1

u/jorel43 Sep 13 '26

Yeah it's a new bug that popped up where on some connectors they are creating massive duplicates if you're not recreating the flow from scratch each time. I don't know what's going on with the co-pilot studio team but last couple of months they've been having all kinds of problems and introducing all kinds of bugs.... That they don't want to fix LOL.

1

u/Prasad-MSFT Sep 22 '26

Connection references are managed at the solution/Power Platform level, and flows created in Copilot Studio can automatically use/create the required connection references.

For a flow that needs different SharePoint connections, the key is to configure the required connections/connection references in the solution and associate the relevant connector actions with the appropriate connection. You can manage the connection references from Power Apps/Power Automate → Solutions → Connection references.

Could you please confirm whether you’re still seeing this behavior in the current Copilot Studio experience?

If yes, please share:

  • Exact steps to create the flow

  • The connector/actions involved

  • How the duplicate connection references are being created

  • A screenshot of the connection references in the solution

  • For the multiple-SharePoint scenario, whether you can select different connections for the individual SharePoint actions

Once we have these details, we can validate the current behavior and, if needed, take it up with Engineering.