Power Platform Community Forum Thread Details

Hello!

I'm trying to run a cloud flow that executes a Power Automate desktop flow with my Copilot agent.

The error occurs when it connects to the cloud flow, since it seems to create a new connection (which doesn’t work) instead of using the existing one (the one that appears to be connected).

I’m attaching screenshots in order.

If you need more info or more screenshots, just let me know (I can only add 3).

Categories:

Using connectors

Power Automate Desktop

Using flows

Hi,

Based on the screenshots, it looks like Copilot Studio is prompting for a Desktop Flows connection during testing, but the connection cannot be established even though the machine appears registered and connected in Power Automate Desktop.
A few things I'd check:

Verify that the cloud flow and the Copilot agent are in the same environment as the desktop flow, machine, and Desktop Flows connection. Environment mismatches are a common cause of connection issues.
Open the cloud flow and confirm that the Run a flow built with Power Automate for desktop action is using a valid connection reference and that it doesn't show any warnings or broken connections.
In the Connections page, try removing the failing Desktop Flows connection and recreating it. Even when a connection appears valid, the underlying authentication token can become stale.
Confirm that the account testing the Copilot has permission to use the desktop flow, machine/machine group, and all related connections. Copilot executes actions using the caller's permissions, so missing access can trigger a connection prompt.
If the cloud flow is inside a solution, ensure all connection references are properly mapped and published. Unmapped connection references can cause Copilot to attempt creating a new connection instead of reusing the existing one.
Check whether the machine is assigned to a machine group and that unattended/attended settings match the way the desktop flow is being invoked.

From your screenshots, the machine itself appears connected, so I'd focus first on the Desktop Flows connection reference, environment alignment, and user permissions, as those are the most common reasons Copilot creates a new connection instead of using the existing one.
If you can share the exact error message shown after clicking Permitir/Reintentar and a screenshot of the cloud flow action configuration, that would help narrow down whether this is a connection reference issue, permissions issue, or an environment mismatch.

Thanks,

Manoj Annavajjala