Users can’t add Copilot agents or bots to Teams chats – where should I look?

Question

Users can’t add Copilot agents or bots to Teams chats – where should I look?

StephanG 846

Hi everyone,

we are currently rolling out Copilot for everyone and came across this feature: https://support.microsoft.com/en-us/office/copilot-in-teams-chats-2c613de4-cd26-4ae3-9e4b-6905d745d991

But we ran into a situation where users could neither add agents/bots to Teams chats nor add them from the Copilot app, even though Copilot itself was available.

3rd party and custom is not allowed - everything von Microsoft is allowed. The Copilot App in Teams is allowed for everyone.
I could add a bot or agent from a group chat - but not Copilot or any other MS bot.

Where is a setting gone wrong?

BR

Stephan

0 comments

1 answer

Your answer

Answer 1

Karan Shewale 2,505 Microsoft External Staff

Hi Stephan, this is usually a Teams app policy scope issue (not a Copilot license issue).

Please check in this order: Teams admin center → Teams apps → Manage apps

Confirm Microsoft 365 Copilot and the specific Microsoft bot/agent apps are Allowed.

Teams admin center → Teams apps → Permission policies

Make sure affected users are assigned a policy that allows Microsoft apps.
Verify no stricter policy is overriding via group/user assignment.

Teams admin center → Teams apps → Setup policies

Confirm users are assigned the expected setup policy and Copilot app is available/pinned as intended.

Per-user policy check

Open an affected user and verify effective policies (permission/setup) are the same as a working user. Scope behavior
Test both 1:1 chat and group chat. Some apps support only certain scopes. Propagation + client test
Wait for policy propagation, then test in Teams Web (InPrivate) to rule out client cache. IF
tenant ID,
affected UPN(s),
chat type (1:1/group),
timestamp,
screenshots/error text.

That is typically needed to confirm backend rollout or policy-gating for your tenant.

Reference docs:

- Copilot in Teams chats (feature behavior): https://support.microsoft.com/en-us/office/copilot-in-teams-chats-2c613de4-cd26-4ae3-9e4b-6905d745d991
Manage apps in Teams admin center: https://learn.microsoft.com/microsoftteams/manage-apps
App permission policies: https://learn.microsoft.com/microsoftteams/app-permission-policies
App setup policies: https://learn.microsoft.com/microsoftteams/teams-app-setup-policies
- Assign Teams policies to users/groups: https://learn.microsoft.com/microsoftteams/assign-policies-users-and-groups

Please consider accepting the answer if it resolved your issue. This helps improve the community by highlighting helpful solutions.

Thanks

Karan Shewale.

StephanG 846 Reputation points

2026-03-12T14:25:26.8733333+00:00

Thanks. Sorry for the late message. I will check tomorrow and get back to you.
StephanG 846 Reputation points

2026-03-13T07:19:27.6833333+00:00
I checked

lease check in this order: Teams admin center → Teams apps → Manage apps

We have all Microsoft Apps allowed by default - Copilot is allowed for everyone

Teams admin center → Teams apps → Permission policies

Does not exist anymore

Teams admin center → Teams apps → Setup policies

Not pinned but they (also myself) can install

Per-user policy check

All users are affected
Scope behavior

Test both 1:1 chat and group chat. Some apps support only certain scopes. Propagation + client test

Does not matter - but in the M365 app it is also not possible

Wait for policy propagation, then test in Teams Web (InPrivate) to rule out client cache. IF

We do not need a change in policy - I signed out of my Teams and signed in again, tried on web etc

Rest of data is not for public
StephanG 846 Reputation points

2026-03-13T07:54:51.2466667+00:00

Ticket opened:
‎Users are unable to use #M365Copilot agent in Teams group chats‎ (#‎Removed PII)
Karan Shewale 2,505 Reputation points Microsoft External Staff

2026-03-13T10:15:01.5333333+00:00
Hi Stephan,

Thanks for the update — since you've verified policies and tested across clients with the same result, this is likely backend rollout/feature-gating for your tenant.

Opening the support ticket was the right move.

Share with Microsoft Support:

Tenant ID

Affected UPNs

Chat type (1:1 vs group)

Timestamps + screenshots

One more check: Teams admin center → Settings → Copilot — confirm Copilot features are enabled tenant-wide.

Please update here once support responds — it will help others with the same issue.
StephanG 846 Reputation points

2026-03-25T07:46:12.1666667+00:00

I opened the support ticket - but it reaaallly slow.
It's more than 12 days now - and the only thing they proposed was allowing custom apps?!
Karan Shewale 2,505 Reputation points Microsoft External Staff

2026-03-27T05:30:13.93+00:00

Sorry you’re facing this — that does sound frustrating. Suggesting custom apps doesn’t really fit your case, so this likely points to a backend/feature rollout issue. I’d recommend asking support to escalate and confirm tenant-level enablement.
StephanG 846 Reputation points

2026-03-27T06:05:08.6533333+00:00

Support now says that the Agent is a 3rd Party and "custom agent"?
I think i would find more forums posts about that if this is true.

Share via

Users can’t add Copilot agents or bots to Teams chats – where should I look?

1 answer

Your answer