CUA in Copilot Studio — Not triggering in Microsoft Teams channel but works in Test Window

(1) Share

Report

Posted on by GH-21080624-0

I have set up a Computer Use Agent (CUA) tool in my Copilot Studio conversational agent and it works perfectly in the Copilot Studio Test Window when I test it, but when I publish the agent to Microsoft Teams and test it there, the CUA tool does not trigger / execute. Instead I get following AI generated response

My setup:
- Copilot Studio agent with Generative Orchestration enabled
- CUA tool added with a configured machine connection
- Agent published to the Microsoft Teams channel
- CUA works fine in the Copilot Studio built-in test chat

What I've checked so far:
- Generative Orchestration is ON
- CUA is not inside a Topic (triggered via the agent's generative orchestration)
- Authentication method for the tool is Maker provided credentials

Categories:

Building Copilot Studio chatbots in Microsoft Teams

General topics

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Suggested answer

Valantis 5,364 on at

Like (1)

Report
Copy link

Link copied!

Hi @GH-21080624-0,

The reason CUA works in the test window but not in Teams comes down to how CUA actually executes.
CUA automates tasks on a Windows desktop by connecting to a physical or virtual machine via a machine connection. In the Copilot Studio test window, you're running in the same context as the machine connection you configured, so the CUA tool can reach the machine and execute.

When the agent is published to Teams, the execution context changes. Teams users are invoking the agent from the cloud via the Teams channel, and the CUA tool still needs to connect to a Windows machine to run. The machine connection configured with "maker provided credentials" means the machine session was set up under your account. When a Teams user triggers the agent, that machine connection either doesn't have permission to connect from the Teams invocation context, or the machine session is not available to that user's request.

To make CUA work in Teams:

1. The machine connection must be accessible from the channel context, not just the maker's test context. Check whether the machine connection is shared or if it needs to be set up per user.

2. For attended scenarios (user-specific): the connection needs to use end-user credentials rather than maker credentials. Change the authentication from maker provided to end-user, which means each Teams user would authenticate to their own machine session.

3. For unattended scenarios: the machine must be running and available at all times with a service account, and the connection needs to support the Teams execution context.

CUA also went GA on May 13, 2026 with Cloud PC pool support added. If your use case is unattended automation, Cloud PC pools are the recommended production path.

Ref: https://learn.microsoft.com/en-us/microsoft-copilot-studio/computer-use

Best regards,

Valantis

✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

🏷️ For follow-ups @Valantis.

📝 https://valantisond365.com/

💼 LinkedIn

▶️ YouTube

Was this reply helpful? Yes No
Suggested answer

11manish 2,385 on at

Like (0)

Report
Copy link

Link copied!
What you are seeing is most likely a current channel limitation / orchestration limitation in Microsoft Teams rather than an issue with your CUA configuration itself.

The key indicator is:

CUA works in Copilot Studio Test Window

CUA does not execute in Microsoft Teams

Teams returns only an AI-generated text response

This usually means the Teams channel is not invoking the Computer Use Agent tool execution pipeline correctly.

My Recommendation
Immediate Actions

Check analytics/diagnostics

Republish Teams channel

Test user-authentication instead of maker credentials

Add explicit tool invocation instructions

Validate whether:

CUA execution is officially supported in Teams for your configuration

because your symptoms strongly suggest a current channel/runtime limitation rather than a configuration issue.

Was this reply helpful? Yes No