Microsoft Teams is blocking AI notetaker bots: how to still get meeting notes in 2026
Published 11 Aug 2026 · 7 min read
If your AI notetaker has stopped showing up in Microsoft Teams meetings, it is probably not broken — it is being detected and held in the lobby. Since a change Microsoft announced in March 2026 (Message Center notice MC1251206), Teams identifies external third-party meeting bots, flags them as unverified, and requires the organiser to admit them explicitly. From August 2026, administrators can switch a tenant-wide policy to block detected bots outright. The durable fix is not a different bot: it is a tool that captures the audio on your own machine and never joins the call as a participant.
Why is my AI notetaker stuck in the Microsoft Teams lobby?
An AI notetaker gets stuck in the Microsoft Teams lobby because Teams now classifies external third-party meeting bots as a distinct participant type and screens them on join. Microsoft's stated reasoning is blunt: bots may access meetings "without the knowledge or consent of the meeting organizer or the hosting tenant." Detected bots land in a lobby group labelled as suspected threats, and there is deliberately no one-click admit for them.
Practically, that means your Otter Assistant, Fireflies "Fred" or tl;dv recorder now depends on a human noticing a prompt and approving it, every single meeting. If the organiser is not you, you have no control over that at all.
What exactly did Microsoft change in Teams in 2026?
Microsoft added a Teams meeting policy called "Manage external bots and their access to meetings", exposed in the Teams Admin Center and via the ExternalBotAccessMode attribute of Set-CsTeamsMeetingPolicy. It has three values: AllowAllBots (no detection), RequireApprovalWhenDetected (lobby approval — the current default), and BlockDetectedBots (refused at the door). The dates, per Microsoft's own communications and roadmap entry 566201:
- 13 March 2026 — announced in Message Center notice MC1251206.
- Mid-May 2026 — Targeted Release: bots labelled and routed to the lobby.
- Early-to-mid June 2026 — general availability of lobby approval as the default.
- August 2026 —
BlockDetectedBotsbegins rolling out across desktop, web, Mac, iOS and Android, for worldwide and GCC tenants.
Two exclusions matter: the policy targets external third-party bots, so it does not block Microsoft 365 Copilot, and it excludes bots registered as Entra ID applications inside your own tenant. The older CAPTCHA verification policy is being retired in favour of this framework. So this is not a temporary glitch to wait out — it is the new default posture, and it only gets stricter.
Are Zoom and Google Meet blocking notetaker bots too?
Zoom and Google Meet have moved in the same direction, though less aggressively than Teams. Zoom updated its settings back in October 2024 to let organisations block third-party AI bot domains from joining meetings, and Zoom's own AI Companion requires host initiation with a visible indicator. Google Meet in 2026 flags third-party notetaker bots as a potential risk and routes higher-risk join requests into a separate screening queue, while Workspace admins can restrict OAuth-connected notetakers outright.
The direction of travel is consistent across all three platforms: a recorder that joins as a guest is now treated as an unknown third party by default. Part of the pressure is legal — the consolidated class action In re Otter.AI Privacy Litigation (case 5:25-cv-06911, Northern District of California) had a motion-to-dismiss hearing on 20 May 2026, with plaintiffs arguing that a bot's consent model fails in all-party consent states.
Does "bot-free" also mean my meeting audio stays private?
No — and this is the distinction most "best bot-free notetaker" listicles quietly skip. "Bot-free" describes only how the audio is captured: from your device instead of a guest participant. It says nothing about where the audio is transcribed. Several popular bot-free tools capture locally and then stream that audio straight to a cloud transcription provider.
Granola is the clearest example: it runs on your computer and listens to microphone and system audio, then passes that audio to cloud transcription subprocessors (AssemblyAI and Deepgram are listed) while the meeting is happening. The audio is deleted after transcription and the notes sit in a US-hosted AWS VPC — reasonable engineering, and Granola is SOC 2 Type 2 certified. But if the reason your IT team blocked bots was "meeting content must not reach a third party", a bot-free cloud tool does not actually solve their problem. It just makes the violation invisible.
If that distinction matters to you, the question to ask a vendor is not "do you send a bot?" but "does the audio leave my machine, and does the transcript leave my tenant?"
Which meeting note tools do not send a bot into the call?
Tools that do not send a bot into the call fall into three groups: local-first desktop capture, cloud-backed desktop capture, and browser extensions that read native captions. The table below separates the two things that get conflated — bot presence and audio destination. Prices are approximate, as of August 2026.
| Tool | Joins as a bot? | Where audio is transcribed | Survives BlockDetectedBots |
Price model |
|---|---|---|---|---|
| Meeting AI Analyser | No | On your PC (Whisper, local) | Yes | €29 one-time |
| Otter.ai | Yes (Otter Assistant) | Otter cloud | No | ~$17/user/mo |
| Fireflies.ai | Yes ("Fred") | Fireflies cloud | No | ~$18/user/mo |
| tl;dv | Yes | tl;dv cloud | No | ~$25/user/mo |
| Fathom | Yes by default; bot-free desktop capture in beta (Mac) | Fathom cloud | Only in the bot-free mode | Free tier / ~$20/user/mo |
| Granola | No | Cloud subprocessors (AssemblyAI, Deepgram) | Yes | Subscription |
| Tactiq | No (Chrome extension) | Tactiq cloud | Yes | ~$12/user/mo |
Only the first row keeps the audio on the machine. Meeting AI Analyser captures system audio and microphone through the Windows WASAPI stack, transcribes locally with Whisper in 90+ languages, and sends only the resulting text to Claude for summaries, translation and action items — through your own Claude plan or Anthropic API key. Nothing joins the meeting, so there is no bot for Teams to detect, label or block. For the full feature-by-feature view, see the comparison on the homepage.
Will IT block a desktop capture app as well?
A desktop capture app is governed by a different control than a meeting bot, so the Teams policy does not apply to it — but that is not the same as blanket approval. ExternalBotAccessMode operates on participants joining a meeting; an application recording your own machine's audio output never joins, so there is nothing for Teams to screen. Endpoint policy, software allowlisting and your organisation's recording rules still apply, and they should.
The honest framing for a conversation with IT is this: the tool removes the third-party data flow they were worried about, and it removes the undisclosed participant. It does not remove your obligation to follow the recording policy. Being able to point at open source code on GitHub and say "here is exactly what leaves the machine — the text transcript, to an Anthropic endpoint we already have a contract with, or nothing at all if AI analysis is off" is a much shorter security review than defending a SaaS recorder.
Do I still have to tell participants that I am transcribing?
Yes. Removing the bot removes a technical disclosure, not a legal one. Consent rules follow the participants' location, not the architecture of your tool: over a dozen US states, including California, Florida and Pennsylvania, require all-party consent, and the safest practice in a mixed-location call is to apply the strictest rule. In the EU, a meeting transcript is personal data of every participant under GDPR, and from 2 August 2026 Article 50 of the AI Act adds transparency obligations on deployers of AI systems, with worker monitoring treated as high-risk under Annex III.
What local transcription genuinely changes is the compliance surface: no international transfer to assess, no additional sub-processor to document, no third-party retention period to audit. We wrote about that in more detail in why local meeting transcription matters for privacy in 2026. Say out loud that you are taking AI-assisted notes. It costs you one sentence.
What does this cost compared to a per-seat subscription?
Switching away from bot-based notetakers is usually cheaper, not more expensive. Cloud meeting assistants bill roughly $12 to $25 per user per month, indefinitely, and the AI analysis is metered on their side. Meeting AI Analyser is a one-time €29 Pro license valid on up to 3 machines with free updates for life, after a 7-day free trial. The AI side runs on the Claude subscription or Anthropic API key you already control, so there is no per-minute analysis fee — the mechanics of that are covered in how to use your Claude subscription as a live meeting assistant.
The trade-off, honestly
Local transcription is not free of downsides. Whisper needs roughly 4 GB of free RAM and a modern multi-core CPU, and a GPU helps if you want the larger models; a cloud service offloads all of that. Meeting AI Analyser is Windows 10 and 11 only, so Mac and Linux users are out. There is no shared web inbox of past meetings for your whole team to browse, no CRM auto-sync, and setup asks a little more of you than clicking "connect calendar" — you pick a mode and, for the AI features, install the Claude Code CLI or paste an API key.
What you get in exchange is a tool that cannot be blocked in the lobby, cannot be labelled a suspected threat, does not appear in anyone's participant list, does not put your meeting audio on someone else's infrastructure, and does not add a monthly line item. If the reason you are reading this is that Teams stopped admitting your notetaker, that set of properties is the actual fix.