Power Platform Community Forum Thread Details

Hi,

I have a Copilot Studio agent with a topic using an HTTP request node.

The agent:

publishes successfully
works in Teams Microsoft 365 Copilot
but fails when I try to Add it to Teams personal chat

The error happens at the Add step itself, before the agent is installed, and the message is just:

Something went wrong

So I’m trying to understand:

Is this a known issue/limitation for agents with HTTP request nodes in Teams personal chat?
Or is it more likely related to Teams channel / app install / admin policy / authentication settings?

Since the agent works in M365 Copilot, I suspect this may be Teams-specific rather than an HTTP node limitation.

Has anyone seen this before, and what should I ask my admin to check first?

Thanks!

Categories:

Building Copilot Studio chatbots in Microsoft Teams

Hi @AZ-01040635-0,
This is not a known limitation of HTTP request nodes in Microsoft Copilot Studio.

HTTP actions are supported across channels, including Microsoft Teams. Since your agent works correctly in Microsoft 365 Copilot, this indicates the issue is not related to the topic or HTTP node, but rather to Teams app installation or policy configuration.

Because your error occurs during the “Add to Teams” step (before installation completes), this typically points to a Teams-side provisioning or policy issue.