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

StephanG 846 Reputation points
2026-03-10T12:56:06.6566667+00:00

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

Microsoft Copilot | Other

Answer recommended by moderator
StephanG 846 Reputation points
2026-08-29T18:00:14.9633333+00:00

The bot is/was preview and i needed to put my Teams into "Preview" Mode.

After that i could add the agent and it could also be used by "normal" users.

https://learn.microsoft.com/en-us/microsoftteams/public-preview-doc-updates

Was this answer helpful?

0 comments No comments

1 additional answer

Sort by: Newest
  1. Karan Shewale 2,585 Reputation points Microsoft External Staff
    2026-03-11T06:18:50+00:00

    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:

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

    Thanks

    Karan Shewale.

    Was this answer helpful?


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.