TEAMS NOTETAKER BOT BLOCKED
Teams Notetaker Bot Blocked? The Bot-Free Way to Keep Meeting Notes
Microsoft Teams now lets admins auto-block external notetaker bots — Otter, Fireflies, and unregistered AI assistants can be shut out of meetings entirely (rollout started September 2026). If your bot stopped joining, this page explains the policy and your three realistic options, including the one that never depends on a bot: capturing notes locally from your own desktop with no meeting attendee at all. VocalFuse works this way — from $5/mo.
What changed: Teams' external bot policy
In June 2026, Microsoft upgraded Teams' bot detection and started placing identified external
AI bots in the meeting lobby, where an organizer had to admit them explicitly. On August 21,
2026, Microsoft 365 Message Center post MC1459141 announced the next step: a meeting policy —
ExternalBotAccessMode — that can automatically block detected
external bots instead of waiting on an organizer's click.
The rollout timeline matters for your calendar: targeted release began mid-September 2026, and worldwide general availability is expected to complete through late October 2026. The auto-block setting is off by default — but security-conscious tenants (legal, finance, healthcare, any company handling client confidentiality) are exactly the ones flipping it on. Coverage from TechRepublic and Microsoft's own Teams blog confirms the direction: unregistered bots are treated as a risk, and even registered ones can be blocked wholesale by policy.
Practical consequence: a notetaker bot that worked last week can silently stop joining this week. Nobody admits it from the lobby; the meeting simply proceeds without it. Your transcript pipeline breaks without any error on your side.
Your three options, honestly compared
When a bot is blocked, you have three real paths. Two of them still depend on someone else's permission or license. The third depends on nothing but your own PC.
1. Get the bot approved
Ask IT to allowlist your notetaker. Microsoft's Bot Identification Program already covers Otter.ai, Read AI, Recall.ai, and Maestro Labs — recognized bots still need policy approval, and an org that auto-blocks can decline entirely. Slow, and one policy change away from breaking again.
2. Use built-in Teams recap
Microsoft's own transcription and recap features are not "external bots," so policy never blocks them. The catch: full recap and Copilot meeting features require Microsoft 365 Copilot licensing. Without it, you get limited built-in recording — and it still lives in the tenant cloud.
3. Capture locally — no bot
Run a desktop transcriber beside Teams on your own machine. Nothing joins the call, so there is nothing for bot policy to detect or block. This is how VocalFuse works: local Whisper transcription on your Windows PC, audio never uploaded, from $5/mo flat.
| Capability | Notetaker bot (Otter, Fireflies) | Built-in Teams recap | Local desktop capture (VocalFuse) |
|---|---|---|---|
| Joins the meeting | Yes — visible attendee | Native, tenant-managed | Never — nothing to admit or block |
| Subject to bot policy | Yes — lobby or auto-block | No | No |
| Works if org blocks bots | No | Yes (Copilot license) | Yes |
| Where audio is processed | Vendor cloud | Microsoft cloud | Your Windows PC |
| Voiceprints of participants | Often (speaker ID) | Tenant-controlled | None — text only |
| Cost model | Per-user subscription + minute caps | Copilot add-on licensing | Flat $5/mo Basic, $10/mo Pro |
Local capture is the only path that works on every Teams call regardless of tenant policy — because it never touches the tenant.
How bot-free local capture actually works
The blocked-bot problem only exists for tools that join your call as a participant. A local desktop transcriber removes that entire category of failure: VocalFuse runs on your Windows PC, listens through your microphone (or system audio) while Teams runs normally beside it, and transcribes with an on-device Whisper model. From the meeting's point of view — and from the admin's dashboard — nothing extra ever joined.
- No bot attendee in Teams, Zoom, or Meet — nothing for ExternalBotAccessMode to catch
- No lobby approval, no admin allowlist request, no registration program
- Local Whisper transcription; raw audio is not uploaded for cloud recognition
- No voiceprints or speaker biometric store — text output only
- Pro adds AI summaries, Note Taking, and Account → Notes sync
- Unlimited dictation at every tier; flat pricing, no per-minute meter
This also sidesteps the adjacent enforcement coming across platforms: Zoom admins can blocklist notetaker bots, and any conferencing vendor can keep tightening detection. A tool that never connects to the platform cannot be listed, detected, or blocked. For the privacy rationale behind avoiding cloud transcription entirely, see AI notetaker privacy.
If your bot is already blocked: the 5-minute switch
- Confirm it's policy, not a bug. The bot never appears in the lobby or participant list. Ask your admin whether ExternalBotAccessMode is set to block or require approval — Message Center post MC1459141 documents both.
- Decide what you actually need. If you only need your own notes and a summary, local capture covers it. If you need team-wide shared transcripts with CRM sync, you need an approved bot or Copilot recap — that's an IT conversation, not a workaround.
- Install a local transcriber. VocalFuse installs on Windows 10/11. Hold the record pill when the meeting starts, release to paste the transcript anywhere — email, docs, your notes app.
- Disclose like you would with any recorder. Bot policy compliance is not recording consent. Tell participants the meeting is being transcribed on your side; consent rules still apply to your recording. See our consent guide.
Deeper comparisons: Otter AI alternative, AI note taker, AI meeting notes, and free voice transcription.
- ✓ No meeting bot
- ✓ Nothing to detect or block
- ✓ Local Whisper STT
- ✓ From $5/mo flat
Teams notetaker bot FAQ
Why did my notetaker bot stop joining Teams meetings?
Most likely your tenant enabled Microsoft's external bot policy (ExternalBotAccessMode, announced in Message Center post MC1459141). The rollout runs from September through late October 2026 and lets admins lobby-block or fully auto-block third-party notetaker bots like Otter and Fireflies. The bot never appears in the lobby or participant list — the meeting just proceeds without it.
Can Microsoft Teams block AI notetakers?
Yes. Since June 2026 Teams detects identified external AI bots and places them in the meeting lobby, and the ExternalBotAccessMode policy (MC1459141) adds automatic blocking. Microsoft's Bot Identification Program covers Otter.ai, Read AI, Recall.ai, and Maestro Labs — but even registered bots can be declined by tenant policy.
What is the bot-free way to keep meeting notes in Teams?
Run a desktop transcriber beside Teams on your own PC. VocalFuse listens through your microphone while Teams runs normally, transcribes with a local Whisper model, and never joins the call — so there is nothing for ExternalBotAccessMode to detect or block. Pro adds AI summaries and note sync for $10/mo; Basic dictation is $5/mo.
Does the Teams bot block affect Zoom or Google Meet?
Teams is furthest along, but the direction is industry-wide: Zoom admins can restrict or blocklist meeting bots, and Google Meet has its own consent prompts. A bot-based workflow can break on any of them. Local capture is platform-independent because it never connects to the conferencing platform at all.
Is local transcription compliant with the Teams bot policy?
Bot policy governs participants that join the tenant — a local recorder is not a participant, so the policy does not apply to it. That is not the same as recording consent: tell participants the meeting is being transcribed on your side and follow your state's consent rules. See our AI notetaker privacy guide.