Microsoft Teams Now Holds Third-Party Recording Bots in the Lobby

What is happening

Updated October 3, 2026. We first published this as a forecast in March 2026. The original headline said Teams was "blocking" bots, which overstated what Microsoft announced, and the original text included a quote from an unnamed ops lead that did not come from a real interview, which we removed. This version follows Microsoft's own message center posts. Details on the corrections page.

If your team uses Otter, Fireflies, or Gong to record Microsoft Teams calls, the default join flow has changed. Under message center post MC1251206 (roadmap 558107), Teams detects external meeting bots as they try to join meetings hosted by your organization, labels them in the lobby, and lets organizers approve, deny, or remove them. Microsoft says "Bot detection will be enabled by default for all tenants." Targeted release ran from mid-May to early June 2026. General availability started in early June and is due to finish by the end of October 2026, after slipping from mid-September.

This is not a ban. Detected bots are held in the lobby, not refused. Per Microsoft's Teams blog post, they wait under a "Suspected threats" group, there is "no one-click Admit option for identified bots", and they need approval "even in meetings where organizers allow participants to bypass the lobby." A bot that used to slip in now needs an organizer to click it through in each meeting. For teams recording hundreds of calls a week, that friction adds up.

Two details limit the reach. First, a tenant admin can turn detection off: the ExternalBotAccessMode setting takes RequireApprovalWhenDetected (the default) or AllowAllBots. Second, the policy covers meetings your organization hosts. Our reading: when a rep joins a call hosted by a customer, the customer's tenant settings apply.

Actual blocking is a separate, optional step. MC1459141 (roadmap 566201) adds an admin policy that stops identified external meeting bots from joining at all. Its "Default state: Off". Microsoft lists general availability from early October to late October 2026. Nothing is blocked unless an admin turns it on.

Which tools are affected

Every tool that sends a bot participant into Teams meetings can be caught by detection. Microsoft notes that some bots may still go undetected. 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. Several bot-first notetakers now ship the same fallback: Fireflies, Otter, tl;dv and Fathom all offer bot-free desktop recording as of October 2026.

Microsoft also runs a Teams Bot Identification Program, which lets registered bot providers mark their join requests so Teams can identify them as registered participants. Microsoft named Maestro Labs, Otter.ai, Read AI, and Recall.ai as partners. Registered bots still wait in the lobby, in the ordinary "Waiting" group instead of "Suspected threats". New vendors cannot join for now: Microsoft says the public preview "has reached its current bot provider capacity."

Why Microsoft is doing this

Microsoft's stated reason is consent and data control. MC1251206 says some bots "may access meetings without the knowledge or consent of the meeting organizer or the hosting tenant, which can create data security, privacy, and compliance risks." Recording consent rules come mainly from privacy and wiretap law (GDPR in the EU, all-party consent statutes in several US states), so an unnoticed bot is a liability for the meeting host.

Microsoft also sells its own recording layer. Teams Premium ($10/user/month add-on) includes intelligent recap, live transcription, and meeting summaries. Microsoft has not linked the bot rules to Teams Premium; our reading is that they do not hurt it.

IT administrators also want control. 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

Accept the friction. Your recording bot still works under the default policy. It just needs approval. If your company hosts the meetings (sales calls, customer success meetings), the organizer can admit the bot as part of their workflow, or your admin can set AllowAllBots. Check whether your admin plans to enable the MC1459141 block, which would end this option.

Switch to desktop-level recording. Your notetaker's own desktop app may already do this (see above). For teams building a product, 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.

Use Teams-native recording. Teams' built-in recording and transcription cover many use cases. If you only need transcripts and summaries (not conversation intelligence or CRM sync), this can be enough. The trade-off: no integration with your existing tools.

Switching platforms no longer escapes the issue. Google Meet added a second join queue in March 2026 for requests the host "is more likely to need a closer look" at, with deny as the default action. Zoom has required an On Behalf Of token for Meeting SDK apps joining externally hosted meetings since March 2, 2026, and points automated recording to its RTMS API. As we covered in our post-bot era analysis, RTMS offers a native, bot-free recording path on Zoom.

The bigger picture

All three major platforms tightened bot access in 2026. Zoom now requires OBF tokens and points bots to RTMS, a native media API it made generally available in June 2025. Google Meet added the second queue. Microsoft added detection and is adding optional blocking, and its blog lists "organization-wide policies to block external bots entirely" among planned controls. The direction is clear: meeting platforms want recording to happen through their APIs or registered participants, not through anonymous bots.

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 security and consent move, and the default it chose (hold for approval, block only if an admin opts in) fits that framing. Teams Premium has sold intelligent recap since 2023, so the bot rules did not arrive alongside it.