One channel. One domain expert.
Every other Copilot agent is a generalist you point at things. Channel Agent is the opposite: it belongs to a single Teams channel, learns that channel's conversations and meetings, and becomes the person on the project who actually remembers what was decided in March. It is still in public preview — which changes how you should pilot it, not whether you should.
01 What it actually does
Microsoft frames Channel Agent as a domain expert for a project, drawing on the channel's own conversations and meetings. Five capabilities carry the value:
- Status reports. It drafts and shares them, and the team reviews, edits and customises before anything goes out.
- Meeting integration. Meeting transcripts become knowledge sources, and it can schedule meetings with suggested titles, agendas, invite lists and times based on what the project needs.
- Task management. It creates tasks and reminds the team about them.
- Questions and answers. It answers in the channel, and in group chats and meetings it's invited to, using channel messages, meeting transcripts, and web search if your IT admin allows it.
- Email. It drafts and sends email from inside Teams, which removes the Teams-to-Outlook context switch that eats status-update Fridays.
It also connects out: Microsoft documents using Channel Agent to manage tasks in Jira, Asana and GitHub, which is where it stops being a note-taker and starts being a project participant.
02 Who can use it — and who only watches
Three requirements to create, interact with and manage a Channel Agent: a Microsoft Copilot subscription assigned to you, membership of the channel where the agent was created, and permission from your IT admin to use apps in Teams.
The interesting part is what happens to everyone else, because it shapes how a channel feels once the agent is in it:
| Who | Can ask the agent? | Can see its output? |
|---|---|---|
| Channel member with a Copilot subscription | Yes | Yes |
| Channel member without a Copilot subscription | No | Yes — responses, generated content, and other people's interactions |
| Non-member, in a group chat or meeting the agent was added to | No | Yes — they see others' interactions |
Unlicensed teammates aren't locked out of the conversation — they see everything the agent produces, they just can't drive it. That makes a single channel a genuinely good place to demonstrate Copilot's value to people who don't have a licence yet. It also means anything the agent says is visible to the whole channel, so treat its output as public within that group.
03 Running it well
04 Where it beats the alternatives
You could ask Researcher to summarise a project, or build something in Copilot Studio. Channel Agent wins on a narrow but common case: the knowledge is the conversation itself. Nobody wrote the project down. It exists as six months of Teams messages and forty meeting transcripts, and every status update currently costs a human three hours of scrolling. That is the job this agent was built for.
It loses when the knowledge lives in documents rather than chat — that is SharePoint agents — or when the work is task execution rather than recall, which is Planner Agent.
Pick your messiest active project channel. Create the agent, then ask it the question you'd normally ask a person: “What did we decide about scope, and when?” Compare its answer to what you'd have found by scrolling. That gap is the business case.