Microsoft Teams Is Blocking Third-Party Recording Bots

What is happening

If your team uses Otter, Fireflies, or Gong to record Microsoft Teams calls, your setup breaks next month. Starting May 2026, Teams will detect and label third-party recording bots as "non-human participants" in the meeting lobby. Meeting organizers must individually admit them. Attendees will see a clear indicator that a bot is present.

This is not a complete ban. Bots are not blocked outright. But the friction changes the equation. A bot that silently joined meetings now requires explicit approval from the organizer every single time. One ops lead at a 200-person SaaS company told us they have three weeks to migrate recording for 80 reps. For teams recording hundreds of calls per week, that breaks the workflow.

Which tools are affected

Every tool that sends a bot participant into Teams meetings is affected. This includes:

• AI notetakers: Otter.ai, Fireflies.ai, tl;dv, Fathom, MeetGeek, Grain, Avoma, and others that join as a meeting participant
• Recording APIs: Recall.ai, MeetingBaaS, Nylas Notetaker, MeetStream, and any infrastructure that deploys bot participants
• Revenue intelligence: Gong, Chorus.ai, Salesloft, Outreach, and any tool that records Teams calls via a bot

Tools that record via browser extensions or desktop capture (Bluedot, Krisp, Jamie) are not affected because they never join as a meeting participant.

Why Microsoft is doing this

Three forces are converging. First, privacy regulators are pressuring platforms to make recording more transparent. The EU AI Act and multiple US state laws now require explicit consent for AI-powered recording. A silent bot in a meeting is a liability.

Second, Microsoft wants to own the recording layer. Teams Premium ($10/user/month add-on) includes native intelligent recap, live transcription, and meeting summaries. Every third-party bot that records a Teams meeting is a Teams Premium feature that goes unsold.

Third, IT administrators have been asking for this. Shadow AI in meetings (employees adding recording bots without company approval) is a data governance problem. Labeling bots gives admins visibility and control.

What your options are

Option 1: Accept the friction. Your recording bot still works. It just needs approval. If your company controls the meeting invites (sales calls, customer success meetings), the organizer can admit the bot as part of their workflow. This is annoying but functional.

Option 2: Switch to desktop-level recording. Recall.ai's Desktop Recording SDK captures meetings without a bot participant. The recording happens at the OS level, not the meeting platform level. No bot in the lobby, no approval needed. The trade-off: you need to install software on each user's machine.

Option 3: Use Teams-native recording. Teams' built-in recording and transcription are good enough for many use cases. If you only need transcripts and summaries (not conversation intelligence or CRM sync), this might be sufficient. The trade-off: no integration with your existing tools. Fathom's free tier, for instance, lacks CRM integrations that mid-market teams need, so Teams-native may actually cover the same ground for basic users.

Option 4: Switch platforms. If your organization controls the video platform choice, Zoom and Google Meet have not announced similar restrictions. As we covered in our post-bot era analysis, Zoom's RTMS API even offers a native, bot-free recording path.

The bigger picture

This is the beginning of platform control tightening, not the end. Zoom introduced RTMS (a native recording API that replaces bots) in June 2025. Google Meet has been limiting bot capabilities quietly. The direction is clear: meeting platforms want recording to happen through their APIs, not through bot participants.

For companies building on meeting recording infrastructure, the message is to diversify. Relying on a single recording method (bots only) is now a risk. The tools that survive this transition are the ones offering multiple capture methods: bots where they still work, native APIs where available, and desktop/mobile SDKs as the universal fallback.

Microsoft frames this as a privacy move. Maybe it is. But the timing, six months after Teams Premium added AI-powered meeting summaries, makes the revenue motive hard to ignore.