Almanac
Microsoft/teamsMicrosoft 365

Consultant-focused KB for Microsoft Teams: implementation notes, gotchas and configuration decisions beyond the official docs — across chat and collaboration, meetings, webinars and town halls, Teams Phone, PSTN connectivity (Direct Routing, Operator Connect, Calling Plans, Teams Phone Mobile), auto attendants, call queues and contact centre integration, Teams Rooms and devices, apps and extensibility, Copilot in Teams, administration and governance, security and compliance, network and call quality, and licensing — plus cross-cutting decision guides.

teams/08-copilot-and-ai-in-teams/feature-teams-copilot-chats-and-channel-agent.md
feature-teams-copilot-chats-and-channel-agent.mdv1 · history
CurrentApplies to Microsoft 365 CopilotUpdated 3 weeks agoSource Microsoft Learn ↗

What it does

Two layers. Copilot in chats and channels is the personal one: each licensed user privately summarises a thread, asks questions of it and gets help drafting replies. The Channel Agent is shared: one agent per channel, named after the channel, that builds knowledge from the channel's messages, files and meetings and answers anyone licensed in the channel.

Key facts

  • Copilot in chats and channels comes with the Copilot licence (Learn labels it the Microsoft Copilot licence). Learn's AI overview lists no admin article for it — there's no Teams policy to tune; licensing is the control.
  • Without a Copilot licence users still get the Copilot Chat app in Teams (web-grounded only) and suggested replies in 1:1 and group chats.
  • Channel Agent is in public preview per Learn. Users need a Microsoft 365 base licence, a Teams licence, a Copilot licence, Teams Public preview enrolment, and Loop experiences in Teams turned on (for meetings).
  • Admin control is the app: Teams apps > Manage apps, search "Channel Agent", Allow or Block. Allowed by default unless all apps are blocked. Scope it with an app permission policy or app-centric management.
  • Teams apps > Agent settings has an auto-creation toggle. By default a Channel Agent is added automatically to every new channel an eligible user creates; education tenants default to Off.
  • Knowledge: channel messages and the channel's SharePoint files, channel meetings, standard meetings it's added to, their transcripts, and web search (which can be turned off — but that switch also turns off web search for all Copilot features).
  • Meeting summaries go into its knowledge after a 24-hour approve/reject window; if nobody acts, they're added automatically. Added to a recurring series, it can see one prior transcript and up to 28 days of chat history.
  • In group chats it answers questions but doesn't absorb the chat into its knowledge, and it can't read files shared in meetings or chats.
  • Limits: one agent per channel, no private channels, not functional with external users, not supported in Customer Key tenants, and preview processing can happen outside the EU Data Boundary.
  • Status reports are .loop files in the channel's folder on its SharePoint site, authored by whoever created the agent.

When to use / skip

Personal Copilot in chats is a no-brainer for anyone already licensed — "summarise what I missed in this channel since Monday" is the prompt most users reach for first. There's nothing to design beyond licensing and adoption.

The Channel Agent is a different animal. For a project channel with a long-running workstream it's useful: deadlines pulled out of conversation, a status report on demand, and people who missed a meeting can still ask what was decided. But it's preview, it defaults to auto-creating itself in every new channel, and it can gather context across Information Barriers. For a regulated client, that last point alone means it stays off until compliance has looked at it.

Skip it outright in Customer Key tenants (unsupported), in tenants that rely heavily on private channels (unsupported), and anywhere EU data residency is a hard requirement while it's still in preview.

Configuration decisions

  • Allow Channel Agent for everyone, block it, or allow it for a pilot group via app permission policy.
  • Auto-creation on or off. For most enterprise tenants, off — let channel owners add it on purpose.
  • Web search for Copilot: remember the switch is tenant-wide across Copilot features, not Channel Agent only.
  • Information Barriers: whether the agent's ability to cross them is acceptable, or whether that rules it out.
  • Sensitivity labels: the agent shows the label on responses but the output doesn't inherit label controls — decide whether that's acceptable for labelled teams.
  • Who should create agents, given status reports are authored by the creator and stored in the channel's SharePoint.

Gotchas

  • Auto-creation is on by default outside education. Enable the preview without checking Agent settings and every new channel gets an agent.
  • Removing the agent from a channel wipes its knowledge. Recreating it starts from zero.
  • Sensitivity labels are displayed on responses but not enforced on them — the answer can be shared onward freely.
  • Turning off web search for the Channel Agent turns it off for every Copilot feature that searches the web.
  • If a team owner has turned off "Allow members to add and remove apps", only owners can create or delete the agent — but auto-creation still adds one when a member creates a channel.
  • If the Allow button doesn't show in Manage apps, the app's availability is probably set to "No one".
  • Learn's admin page for Channel Agent was last updated in November 2025 — check the preview status again before telling a client it's still preview.

Consultant notes

  • Check Teams apps > Agent settings the day the tenant joins public preview. That's the setting that surprises people.
  • Bring the compliance team in early: Purview has a dedicated Channel Agent page, and Information Barriers is the question they'll ask first.
  • For personal Copilot in chats, adoption beats configuration — give users five prompts that work in their own channels.
  • Pilot the Channel Agent on one or two real project teams with tidy channel files. It's only as good as the channel's SharePoint content.
  • Keep the Copilot Chat app (free) and Copilot in chats (licensed) clearly separated in comms — users mix them up constantly.

Recheck when the Channel Agent leaves public preview, or when Learn publishes an admin page for Copilot in chats and channels

Was this accurate?
Related
Facilitator agent in Teams meetings08-copilot-and-ai-in-teamsTeams Premium vs Microsoft 365 Copilot for meeting intelligence13-decision-guidesCopilot in Teams Phone calls — 1:1 VoIP and PSTN08-copilot-and-ai-in-teamsInformation barriers in Teams10-security-and-complianceMicrosoft Graph APIs and Change Notifications for Teams07-apps-and-extensibilityMicrosoft Teams KB — Features & Changelog_root