Out of the box, Microsoft Teams does not ask participants for recording consent. Explicit consent is a policy an admin has to turn on, and it is off by default. For EU teams that means the default Teams experience records everyone without an opt-in, so you have to change the setting and add your own notice and lawful basis on top.
What Teams does by default
Microsoft's own documentation is blunt about the default. For the recording consent policy, the "Off" state is "the default value," and with it "participants aren't asked for consent to be recorded and transcribed. All participants are included in recordings and transcripts from these organizers' meetings." (Microsoft Learn, retrieved 2026-07-26.) So the default behaviour is capture-first, ask-never.
What the explicit-consent policy changes
When an admin turns the policy on, the flow changes sharply. Microsoft states that once recording or transcription starts, "all other participants are muted, with their cameras and content-share off," and that when someone tries to unmute or share, "they're asked to respond 'Yes' or 'No' to consent to be included in the meeting recording and transcription. If a participant responds 'No' to the question, they have a view-only meeting experience." The choice "is included in the attendance report." (Microsoft Learn, retrieved 2026-07-26.)
Microsoft Teams recording consent is an admin policy that is disabled by default. With it off, everyone is recorded without being asked. With it on, participants must actively answer Yes or No before joining audio, video, or sharing, and declining leaves them with a view-only experience. The setting is per-organiser and logged in the attendance report.
Why default-off is a GDPR problem
Capture-first is exactly the posture GDPR reviewers push back on. Where consent is your lawful basis it must be a clear affirmative act, and a meeting that records everyone unless an admin changed a tenant setting does not evidence that. Even where you rely on a different lawful basis, the transparency and data-minimisation duties still bite. The safe reading is: treat the default-off policy as a setting you must deliberately enable, then layer your own advance notice and lawful basis on top.
Copilot couples recording and transcription
The AI features raise the stakes. Microsoft notes that in Teams, "When organizers turn off Copilot for their meeting or event, recording and transcription are also turned off," and that the default Copilot mode requires a saved transcript that organisers cannot switch off. (Microsoft Learn, retrieved 2026-07-26.) So enabling the assistant can force a transcript to exist, which is more personal data to account for, not less.
Where Germany and the EU go further
National law can demand more than Teams provides. In Germany, recording a confidential conversation without agreement can engage §201 StGB, and monitoring tools usually involve the works council. We cover that in AI notetaker consent, §201 StGB, and the Betriebsrat, and the broader legal picture in recording sales calls under GDPR in Europe.
How Numi handles consent on Teams
Numi's meeting bot joins Teams as a named, visible participant, so recording is never covert and attendees can be told before it starts. The audio then runs through an EU-only pipeline, transcribed on self-hosted models in Frankfurt, stored and analysed in the EU under an Article 28 AVV, with no training on your data. It does not replace your consent process, but it makes the visible-participant part, which the covert browser-extension tools get wrong, easy. See the full setup in a GDPR-compliant AI notetaker for Microsoft Teams.