Created Agent Not working inside the MS teams

(1) Share

Report

Posted on by KW-08040128-0

I created a few agents using Copilot Studio, and the tools use REST APIs to retrieve Azure DevOps data.

Initially, everything was working fine. However, after some time, the agent installed in Microsoft Teams started showing errors. The same bot is still working correctly in Microsoft 365 Copilot.

I have already tried several troubleshooting steps, including:

Uninstalling and reinstalling the agent from Microsoft Teams

Clearing the cache

Rewriting the agent instructions

Rechecking and granting API permissions

Sharing the agent with everyone

However, the error still occurs only when using the agent through Microsoft Teams.

Could you please help me understand why this issue is happening in Teams and how to resolve it?

CopilotMS.png

Your file is currently under scan for potential threats. Please wait while we review it for any viruses or malicious content.

Categories:

Building Copilot Studio chatbots in Microsoft Teams

I have the same question (0)

All responses (4)

Answers (0)

Sort by

Suggested answer

11manish 2,385 on at

Like (1)

Report
Copy link

Link copied!
This issue is fairly common right now with Microsoft Copilot Studio agents deployed to Microsoft Teams. The important clue is:

Agent works in Microsoft 365 Copilot

Same agent fails only in Teams

That usually means the problem is not your REST API or Azure DevOps integration itself, but rather a difference in how Teams hosts and authenticates Copilot Studio agents.

Was this reply helpful? Yes No
Suggested answer

Valantis 5,364 on at

Like (1)

Report
Copy link

Link copied!

Hi @KW-08040128-0,

The connectorRequestFailure error only in Teams (not M365 Copilot) when calling REST API tools is a known pattern.

check please this:

1. Connection authentication context in Teams vs M365 Copilot. When the agent calls REST APIs through a connector, the connection is authenticated under a specific account. M365 Copilot and Teams can invoke the connector under different identity contexts. If the connection was created or last authenticated in the M365 Copilot context, it may fail when Teams tries to invoke the same connector because the auth token issued for Teams has different scope or audience. Open the connection in Power Platform (make.powerapps.com > Connections) and check when it was last authenticated. Delete and recreate it.

2. Check Analytics sessions. In Copilot Studio go to Analytics and look at Teams-specific sessions. If sessions appear, the agent is being invoked but the connector call fails. If zero sessions, the issue is before the agent runtime. This tells you where in the chain the failure is.

3. Check if any DLP policy blocks the HTTP connector or custom connector in the environment for Teams channel specifically. PPAC > Data policies > check if the connector used for Azure DevOps REST API is in the blocked group.

4. The "worked before, fails now" pattern often means the OAuth token for the connection expired and the automatic refresh failed. Delete the connection and create a fresh one.

Can you confirm what type of connector you're using for the Azure DevOps REST API — a custom connector, the built-in Azure DevOps connector, or a plain HTTP action?

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
KW-08040128-0 8 on at

Like (1)

Report
Copy link

Link copied!

I'm using Azure DevOps REST API — a custom connector,

Was this reply helpful? Yes No
Suggested answer

Valantis 5,364 on at

Like (1)

Report
Copy link

Link copied!

Hi @KW-08040128-0,

Since it's a custom connector, the most likely cause is the OAuth connection going stale. Custom connectors using OAuth for Azure DevOps require the connection to stay authenticated, and the Teams channel invoking the connector under a different context can trigger a token refresh failure that M365 Copilot handles more gracefully.

Try this first: go to make.powerapps.com > Connections, find the connection your custom connector uses, delete it, and create a fresh one. Then go back to Copilot Studio, open the agent, re-select the connection on the affected tool, save and republish.

If the error comes back after a period of time, check the custom connector authentication settings:
- Verify the Refresh URL is correctly set to the Azure DevOps OAuth token endpoint
- Make sure the Token URL and Refresh URL are not the same (a common mistake that breaks silent refresh)
- Check that the scope includes offline_access or the equivalent for Azure DevOps if using Entra OAuth

Also check whether the connection is set to use maker credentials or end-user credentials. In Teams, if the connection uses maker credentials and the token session expires, Teams has no way to prompt for reauthentication the way M365 Copilot might handle it more gracefully in its shell.

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