In many of the tenants I work with, Copilot in Teams meetings is the first AI feature business users ask for. Live summaries, extracted action items and follow-up suggestions, with nobody frantically taking notes, sound great on paper. The enthusiasm usually fades once people realize that Copilot depends on meeting transcripts, and that raises a whole set of technical and privacy questions. In Germany in particular, you can't simply wave through the recording and storage of what's said in a Teams call. Works councils and external attendees regularly push back.

Copilot in Teams meetings needs a transcript to work

As of early June 2024, Copilot in Teams meetings generally needs a transcript. The AI analyzes what people say in real time and produces summaries or answers, but only while a transcript is being created. With transcription on, everything said is saved, usually to the meeting organizer's OneDrive or SharePoint. If you turn transcription off or don't record, Copilot is mostly unavailable. The diagram below shows the basic logic:

flowchart TD
    Meeting["Teams meeting"] --> Transcript["Create transcript?"]
    Transcript -->|"Yes"| Copilot["Copilot active"]
    Copilot --> Recap["Summaries & answers"]
    Transcript -->|"No"| CopilotLimited["Copilot limited"]
    CopilotLimited -->|"No transcript"| NoRecap["No AI summary"]

Figure: Without a transcript, Copilot has no context to work with, unless the new policy is in place.

The "Only during the meeting" option gives privacy a practical boost

A recent change to the Teams meeting policy adds some welcome flexibility. With the "Only during the meeting" option, admins can allow Copilot during the meeting while preventing the transcript from being kept afterwards. Participants still get live AI help with actions, quick answers and summaries, but nothing stays behind permanently. For many German organizations this is a real privacy improvement, and it can make works council negotiations a lot easier. You do give something up, though. Copilot's meeting insights exist only during the call and are gone once it ends.

Microsoft's official docs go into the details. One point matters a lot here: you have to configure this setting deliberately in the meeting policy. By default, transcripts are still saved whenever Copilot is used.

Practical tip: Talk to the works council early and agree on how recordings and transcripts are handled. Tell every attendee when Copilot or any kind of recording will be active, preferably in the invite itself.

Organizer settings have real consequences in day-to-day use

Many IT teams miss the fact that each meeting organizer can decide whether Copilot and transcript features are enabled for a given meeting. That's convenient. Without a solid policy baseline, however, it produces inconsistency and confusion, especially when the defaults mean transcripts are saved quietly and not everyone gets told. What I often find is a patchwork across teams, with hardly anyone keeping track of where transcripts land or how long they stick around.

Questions you'll need to answer in practice:

  • How do you make sure participants clearly know about Copilot and transcription?
  • Where are transcripts stored, and for how long (usually in the organizer's OneDrive/SharePoint)?
  • How do you handle external participants, and do they get notified in advance?
  • Is there a process for deleting old transcripts once a retention period ends?

If you have meetings with externals, take another look at the Teams recording and transcription policy and decide whether certain meeting types or groups need restrictions.

Recap, Intelligent Recap and Copilot are not the same thing

Teams Premium brought in "Intelligent Recap", and the name confuses people. Basic Recap lets users browse meeting recordings and transcripts. Intelligent Recap adds AI-generated chapters, key points and markers, but only for Premium licensees. Copilot in Teams meetings is a separate add-on and goes further, with real-time Q&A, topic summaries and action suggestions, as long as a transcript exists and is saved for use after the meeting. People regularly assume Copilot and Intelligent Recap are interchangeable. They aren't, and they differ considerably in licensing, feature scope and data storage. I've written up more lessons from rollouts in an earlier post: Copilot for Microsoft 365 pilot: Lessons from the first weeks.

German data protection shapes how privacy works in practice

In Germany, no AI feature goes live without close cooperation with the works council. Copilot in Teams meetings is a particularly sensitive case, because recording and storing conversations often feels like surveillance to employees. The new "Only during the meeting" option helps here, since organizations can use Copilot without keeping audio or transcripts after the call. The privacy questions don't disappear because of it. You still need to inform all participants openly, define clear processes for storing and deleting transcripts, and document everything for compliance. Microsoft's Copilot privacy FAQ describes in detail what happens to meeting data and how Copilot differs from Teams recordings.

On the technical side, I recommend auditing transcript retention on a regular basis. This PowerShell snippet can help you find old Teams transcripts:

Get-Team | ForEach-Object {
  Get-TeamChannel -GroupId $_.GroupId |
    ForEach-Object {
      Get-TeamChannelMessage -GroupId $_.GroupId -ChannelId $_.Id | Where-Object { $_.Type -eq 'meetingTranscript' }
    }
}

If you want to use Copilot in Teams meetings safely, your meeting policies, retention rules and communication have to fit together. Talk to your works council and security team early, not after the fact.

I don't see Copilot in meetings as a default setting

Copilot in Teams meetings does make people more productive, but you can't just switch it on and walk away, least of all where privacy and compliance matter. It only pays off, rather than becoming a risk, once clear policies, upfront communication and careful configuration are in place. The new live-only transcript option is a big improvement. It doesn't give you a free pass, though. Turning on the technology is the easy part. The real work is earning the trust of everyone involved, being transparent with them and making clear who is responsible for what.