Copilot in Teams meetings: recap and action items

Copilot in Teams meetings is the feature that sells Microsoft 365 Copilot to executives: join late and ask "what did I miss," leave early and get the action items, never take notes again. It delivers on most of that. What the demo hides is that everything depends on transcription, that there are two different features people call "recap," and that a handful of meeting-policy settings decide whether your users get any of it. This guide is the version you need before turning it on.

The transcript is the product

Copilot in a meeting has no ears of its own. It reads the live transcript. No transcription, no Copilot — the button is greyed out, or Copilot politely explains it has nothing to work with. That leads to the first consequence: the meeting-policy settings for transcription, and who is allowed to start it, are Copilot settings whether or not they're labelled that way.

The second consequence is the setting that generates the most confusion: Copilot without a retained transcript. In the Teams admin center meeting policy, the Copilot setting has three positions:

• On — Copilot works during the meeting only if transcription (or recording with transcription) is running, and the transcript is saved afterwards.
• On with saved transcript is the same thing under the naming Microsoft has used in some admin views; the point is that a transcript persists.
• On without a saved transcript (the "Copilot only during the meeting" option) — Copilot works in the meeting, transcribing in the background, but no transcript is retained when the meeting ends. Nothing is stored, and there is no post-meeting recap.
• Off — no Copilot in meetings.

The organiser also gets a per-meeting choice in Meeting options, within what policy allows. Legal and works-council conversations tend to land on "without saved transcript" for sensitive meetings and "on" for ordinary ones; the trade-off is explicit — privacy of the transcript versus having anything to recap later.

Two things called "recap"

In-meeting Copilot is the chat pane during the call: "summarise so far," "what are the open questions," "what did Priya say about the deadline," "draft a follow-up message." It works off the live transcript, it's available to anyone the policy allows, and it's the feature latecomers love.

Intelligent recap is the post-meeting page: AI-generated notes, suggested follow-up tasks, speaker timeline, topic chapters, and the ability to ask Copilot questions about the meeting afterwards. It appears in the meeting's Recap tab once the transcript is processed, which can take a little while after the meeting ends. Intelligent recap is a Teams Premium feature that a Microsoft 365 Copilot licence also unlocks — the two entitlements overlap here, which matters for organisations deciding whether they need Premium at all.

The requirement chain for recap: transcription or recording ran, the transcript was retained, the user viewing has Copilot or Premium. Miss any one and users see the plain recording page and ask why "Copilot didn't work."

Action items and follow-ups

The recap's follow-up tasks section lists things Copilot heard as commitments — "Sam to send the revised quote by Friday" — attributed by speaker. In practice:

• It's good at explicit commitments with a name and a verb. It's bad at implied ones and at anything decided in the last two minutes as everyone was leaving.
• Speaker attribution depends on identified speakers. On a laptop with one person per account it's accurate; in a meeting room with several people on one Teams Rooms device, attribution falls back to the room unless the room has voice recognition or people have enrolled voice profiles. Rooms-heavy organisations should expect "Conference Room 4B to send the quote."
• Tasks are suggestions, not assignments. Someone still has to create the Planner or To Do item — or use the Facilitator agent, below.

The Facilitator agent and collaborative notes

Alongside the Copilot pane, Teams has the Facilitator agent (a Copilot-licensed feature that came out of the older collaborative notes Loop component). When enabled for a meeting, it maintains live AI notes in a Loop component as the meeting happens — running summary, decisions, and action items — that everyone with access can edit, and that persist afterwards in the meeting chat and in the organiser's OneDrive as a Loop file. It can also create tasks in the notes that sync to Planner and To Do.

This is the closest thing to "the meeting writes its own minutes." It's also the newest piece, and Microsoft has been iterating on it quickly; check how it behaves in your channel before building a process around it. The persistence model (Loop file in OneDrive, governed by Loop policies and retention) is different from the recap, which lives with the meeting recording and transcript.

Governance and retention

• Transcripts and recordings are stored in OneDrive (organiser's or the person who started recording) for non-channel meetings and in SharePoint for channel meetings, and are governed by retention policies for OneDrive and SharePoint. Recap content is derived from them.
• Copilot interactions (the questions asked and answers given) are captured in the audit log and can be subject to retention through the Teams and Copilot interaction retention settings in Purview.
• Sensitivity labels on meetings (Teams Premium) can force transcription off, which — see above — forces Copilot off for that meeting. That is the cleanest way to keep AI out of specific categories of meeting.
• External participants can't use Copilot in your meeting unless they're licensed in their own tenant and the meeting policy allows it; they also can't see intelligent recap. Guests get nothing.

The settings to decide up front

1. Who may start transcription (meeting policy, and whether attendees or only organisers).
2. Copilot in meetings: on, on without retained transcript, or off — and whether organisers may change it per meeting.
3. Whether to enable the Facilitator agent broadly or for a pilot.
4. Retention for transcripts, recordings, and Copilot interactions.
5. Whether Teams Rooms devices get voice identification so attribution isn't "the room."

Decide those five with legal and the works council before the licence assignment, not after. Copilot in meetings is a genuinely good feature; unmanaged transcription of everything the organisation says is not a policy anyone signed off, and the two arrive together unless you separate them.