microsoft teams is blocking ai notetaker bots — what still works

what's changing in August 2026

Per UC Today's reporting, Microsoft Teams will begin automatically blocking external AI notetaker bots in August 2026, hardening a crackdown that had previously left enforcement to individual admins and meeting hosts. A "bot" here means a virtual participant: a piece of software that joins the call like a person would, shows up in the participant list, and receives the meeting's audio stream so a cloud service can transcribe it. That is how most popular AI notetakers work — Otter sends OtterPilot into your meetings, Fireflies sends its assistant "Fred," and Fathom joins as a visible bot.

The exact scope, admin controls, and rollout details are Microsoft's to confirm — this page describes the change as reported, not as documented policy. But the direction is unambiguous: the era of third-party software walking into Teams meetings as a pseudo-participant is ending, and it's ending by default rather than by opt-in.

The timing isn't accidental. Bot recorders were already under pressure before the platforms moved: Otter faces a consolidated federal class action over non-consent recording and voiceprints, Fireflies faces two BIPA voiceprint suits, and Fireflies users have reported bots that kept joining meetings even after they deleted their accounts. Auto-blocking is the platform-level response to a trust problem the bots created themselves.

who actually feels the block

If your notetaker joins meetings as a participant, this lands on you directly. The people hit hardest are the ones who never controlled the meeting in the first place: consultants, contractors, salespeople, recruiters, and anyone who spends their day as a guest in other organizations' Teams calls. Their bot didn't need the host's software — but it did need to get through the door as a participant, and per the reporting, that door closes automatically in August 2026.

For IT admins, the change is mostly relief: instead of playing whack-a-mole with bot domains and lobby policies, enforcement becomes central and automatic. But blocking bots is a floor, not a policy — it says nothing about the other ways meeting audio leaves the organization, which is where the remaining options differ sharply.

what still works — three honest categories

Option one: Microsoft's own Copilot meeting recap. It's the sanctioned path — native to Teams, no bot, transcripts and recaps inside the tools your org already runs. The catch is access: it requires Copilot licensing, it works from the organizer's side, and admins control whether it's available at all. If you're a licensed employee in a Copilot-enabled tenant organizing your own meetings, it's the path of least resistance. If you're a guest, a consultant, or in an org that hasn't bought Copilot, it does nothing for you.

Option two: desktop-capture apps with cloud processing, Granola being the best-known. No bot joins the call — the app captures your computer's audio locally — so the Teams block doesn't touch it, and the note-taking experience is genuinely polished. But the audio still leaves your machine: Granola routes audio to Deepgram or AssemblyAI for transcription, sends transcripts to OpenAI and Anthropic for summarization, and trains on user data by default; its free plan caps history at roughly 25 notes. The bot is gone, the upload is not. To be fair, that cloud pipeline buys real accuracy: dedicated cloud ASR still leads on-device transcription on difficult audio, and if maximum accuracy on messy multi-speaker recordings is your hard requirement, cloud processing has the edge.

Option three: browser-side on-device capture, which is how now recording works. Nothing joins the call — the recorder runs in a browser tab (or the iOS app for in-person meetings) and transcribes locally: Whisper runs in the browser via WebAssembly, ready in about two seconds on any current Chrome or Edge, including locked-down managed work profiles, with no GPU needed. There is nothing for Teams to block because nothing ever enters the meeting, and there is no upload to worry about because the audio never leaves your device — a claim you can verify yourself in the browser's network tab, and one we document against competitors at nowrecording.com/trust. It works for guests, works identically on Zoom, Meet, and in-person meetings, and is currently free for everyone in early access. Afterward you get speaker labels and talk-time stats, an AI summary whose action items cite the exact transcript turns, and one-click exports — Markdown, plain text, .srt/.vtt subtitles, JSON, or the original audio.

• Copilot recap: best if you're the organizer in a Copilot-licensed, admin-enabled tenant — native, sanctioned, zero extra tools
• Desktop + cloud (Granola-style): best if you want polished notes and accept audio going to cloud providers
• Browser on-device (now recording): best if you're a guest, on a locked-down machine, or need the audio to provably stay local — free in early access

practical guidance: individuals vs. IT admins

If you're an individual — especially a guest in other people's Teams calls: first, check how your current notetaker actually captures audio, because "AI notetaker" spans both bots (blocked, per reporting) and local capture (unaffected). Second, don't look for ways to sneak a bot back in; hosts and platforms are aligned on this, and a workaround that annoys your client is worse than no notes. Third, whatever tool you use, keep disclosure clean: recording laws apply regardless of architecture. now recording shows a visible indicator while recording and copies an "I'm recording this meeting" notice to paste into the meeting chat in one click.

If you're an IT admin: the auto-block handles the uninvited-participant problem for you, but it doesn't decide your recording policy. The useful question after August 2026 is not "is there a bot?" but "where does the audio go?" Copilot keeps it inside your Microsoft tenant with licensing costs attached; desktop cloud apps move it to third-party AI providers under their terms; on-device browser capture keeps it on the employee's machine entirely, with only text leaving (and only when the user asks for a summary or signs in to sync). The comparison matrix at nowrecording.com/trust lays out what each tool sends off-device, with sources.

frequently asked questions

Will Microsoft Teams block now recording?

No. The reported block targets bots — virtual participants that join the call. now recording never joins the meeting: it records locally in your browser on your own machine, nothing appears in the participant list, and there is nothing on the call for Teams to block.

Which notetaker tools does the Teams block affect?

Per the reporting, tools whose capture depends on a bot joining the call as a participant — the model used by Otter's OtterPilot, Fireflies' Fred, and Fathom's visible bot. Tools that capture audio on your own device without joining the meeting, like Granola (desktop, cloud processing) or now recording (browser, on-device processing), aren't affected because nothing joins the call.

Can I keep using Otter or Fireflies in Teams meetings after August 2026?

Their bot-based capture is exactly what the auto-block targets, per the reporting. Whether those vendors offer alternative capture modes for Teams is up to them — check their documentation. What's clear is that the join-as-a-participant approach stops being viable in Teams once automatic blocking is on.

Isn't Microsoft Copilot the obvious replacement?

It is — if you fit its constraints. Copilot recap requires Copilot licensing, works from the organizer's side, and is admin-gated, so it covers licensed employees in enabled tenants organizing their own meetings. It doesn't cover guests, consultants joining someone else's call, organizations that haven't bought Copilot, or any meeting outside Teams.

If no bot joins, do I still need consent to record?

Yes. Recording laws apply regardless of the tool — many places require everyone on the call to consent. The bot block changes what software can enter a meeting, not your legal responsibility to inform people where required. now recording shows a visible indicator while recording, and one click copies an "I'm recording this meeting" disclosure you can paste into the Teams chat.

Does this affect Zoom or Google Meet too?

The reported change is specific to Microsoft Teams. But hosts and admins on every platform were already ejecting and blocking bots manually, and Teams making it automatic signals where the market is heading — which is why capture that doesn't depend on joining the call is the durable architecture.

Is now recording really free?

Right now, everything is free — the product is in early access. Unlimited recording, live on-device transcription, speaker labels, file imports, and AI summaries need no account; signing in (also free) adds cloud text sync, search, and share links. A paid Pro plan is planned at $8/month ($5/month billed annually) but isn't purchasable today.