Learn › Microsoft 365 Copilot › 4 · Apps & surfaces

Copilot in Teams

The richest Copilot surface — and the one with the longest dependency chain: policy, transcription, retention and licence all have to agree before 'what did I miss?' works. The chain is mapped in detail in our Teams curriculum; this is the Copilot-side view.

The three Teams surfaces

  1. Copilot in meetings — the flagship: live 'what did I miss', decisions, action items, post-meeting recap. Runs entirely on the TRANSCRIPT — the dependency pyramid covered in depth in the Teams curriculum (learn/teams/meetings/copilot-in-meetings): AllowTranscription per policy instance, transcription actually started, licence on the asker, and no e2ee (which removes service-side media by design).
  2. Copilot in chat/channels — summarise threads, draft replies, catch up on a channel. Grounds on message history the user can read (permissions model applies to chat like everything else); long-thread synthesis is where it shines.
  3. Intelligent recap — the post-meeting page (chapters, speakers, mentions) — Premium OR Copilot licensed, again transcript-fed.

Copilot-side facts worth adding to the Teams-side chain

  • Retention shortens memory: chat summarisation reaches only what retention kept — a 30-day chat deletion policy quietly caps 'summarise this quarter's discussion'. Records decisions are now UX decisions.
  • Meeting Copilot honours meeting sensitivity: no-transcript hardened meetings (Teams curriculum's meeting-hardening) produce no Copilot, on purpose — brief executives so it reads as control, not breakage.
  • The interaction records from Teams surfaces land like all Copilot interactions (mailbox records) — the meeting's transcript AND the questions asked about it are both discoverable artifacts (security module).

What to watch (proofs)

  • The dependency chain per organiser population: transcription-allowed census (Get-CsTeamsMeetingPolicy | ft Identity, AllowTranscription) — the serv365 verdict engine already alerts on exactly this column.
  • The recap presence test: meeting with transcript → Recap tab populated; without → absent. Two meetings, chain proven.
  • Retention interplay: summarise-history prompts in a short-retention test team vs a normal one — the memory-cap demo for records stakeholders.
  • Licence reality on askers: service-plan check for the complaining user (the Teams curriculum's thirty-second ticket-ender).

PowerShell for this concept

Discussion

No messages yet — start the thread.

Sign in with your email to join the discussion — we send a one-time link, no password.