Power Platform Community Forum Thread Details

We have a Copilot Agent making a call to a Power Automate Flow. The flow uses 2 connections, one a custom connector and another oracle premium connector.

The Agent is published to MS Teams. When a end user interacts with the agent which invokes the flow, they are asked to make their own connection to the Oracle DB and the Custom Connector.

How can we avoid this? One way we tried is to make end users as the Run-Only users and choose to the the flow owner's connection. Is there a way to avoid this so we dont have to give the end users access to the flow?

Categories:

Calling actions from Copilot Studio

Hi @SH-07112002-0

To a small degree, there is technical and then there is Eula/legal.

As long as you have licenses for everyone then the second point is moot.

As for technical, are you concerned about them "seeing" the flow or it running as them?

If you purely do not want them too, then create a service account, with a license to everything it needs. Then set the connections to run as that connection (owner) only instead of run-only for the users.

Make sure in the agent its set to run as the flow owner / agent owner.

Are you saying if you do this is still does not do what you want (it still prompts them?)

Or can you set it this way, making sure under additional details (if you see it for your tool etc) that its set to not prompt the user and set to run as the owner.

If these suggestions help resolve your issue, Please consider Marking the answer as such and also maybe a like.

Thank you!
Sincerely, Michael Gernaey