Are Microsoft Teams and Google Meet really blocking notetaker bots?

Yes. Microsoft is rolling out controls that let Teams block third-party recording bots from generating transcripts and summaries, reaching targeted tenants from mid-May 2026 and general availability by mid-June 2026, with automatic admin blocking of identified external AI bots rolling out from August 2026. Google Meet's March 2026 update flags third-party notetaker bots as a potential risk and defaults to denying them entry, so a bot-based tool now needs manual host approval to join. The direction of travel across the major platforms is to treat guest bots as untrusted by default.

What is the difference between bot-based and bot-free meeting capture?

Bot-based capture sends a separate software participant, a bot, to join the meeting as a guest, record the audio, and ship it to the vendor's cloud. Otter, Fireflies, Read AI and Fathom work this way. Bot-free capture records the meeting from a participant's own client, for example the audio playing in their browser tab, so no extra attendee joins and nothing has to be admitted through the lobby. The platform crackdown targets the guest-bot pattern specifically, which is why bot-free capture is unaffected by it.

Why are the platforms blocking notetaker bots?

Because a guest bot is an unmanaged third party that joins the meeting, captures everything said, and exfiltrates the audio and transcript to an external cloud outside the organiser's control. That raises security, confidentiality and consent concerns: the bot is often admitted without participants understanding who ultimately receives the recording. Detecting and gating these bots gives administrators back control over what leaves the meeting, which is why Teams now labels detected bots in the lobby and applies an admin policy, and Meet routes them into a screening flow.

Will blocking bots break my AI notetaker?

If your tool relies on sending a bot into the meeting, then in organisations that enable the new controls it can be blocked outright or forced to wait for manual host approval every time, and it may be barred from generating transcripts at all. Tools that capture bot-free, from the user's own client, are not affected because there is no guest bot to detect or block. When evaluating a meeting-AI tool in 2026, the capture architecture is now a durability question, not just a preference.

How does Numi capture meetings without a bot?

Numi captures from the participant's own client, recording the meeting audio present in the browser tab, rather than sending a separate bot to join as a guest. No extra attendee appears in the meeting and nothing has to be admitted through the lobby, so the Teams and Meet bot controls do not block it. This is a deliberate architectural choice: capture belongs to the participant who is already lawfully in the meeting, not to an external bot admitted on their behalf.

Why Google Meet and Teams Now Block Notetaker Bots, and What Bot-Free Capture Means

For years the standard way an AI notetaker worked was to send a bot into your meeting. It joined as a guest, sat in the participant list with a name like "Otter.ai" or "Fireflies Notetaker," recorded everything, and shipped the audio to the vendor's cloud. In 2026 the meeting platforms decided they had seen enough. Microsoft Teams and Google Meet are now actively detecting and blocking third-party notetaker bots. If your meeting-AI tool depends on that bot getting in, this is the year the model breaks. The alternative, bot-free capture, is not a marketing phrase; it is a different architecture, and it is the one the crackdown does not touch.

The short version

A bot-based notetaker sends a separate software attendee into your meeting to record it. A bot-free notetaker records from a real participant's own client, for example the audio in their browser tab, so nothing extra joins. Teams and Meet are blocking the first kind. They cannot block the second, because there is no guest to detect.

What actually changed in 2026

Microsoft Teams. Microsoft is rolling out controls that stop third-party recording bots from generating transcripts and summaries in Teams meetings. The capability reaches targeted release tenants from mid-May 2026 and general availability by mid-June 2026. On top of that, an administrator setting to automatically block every identified external AI bot begins rolling out from August 2026 across desktop, web, Mac, iOS and Android. When Teams detects an external meeting-assistant bot trying to join, it labels the bot in the lobby and applies whatever policy the administrator has set, up to and including an automatic block.

Google Meet. Google Meet's March 2026 update flags third-party notetaker bots as a potential risk and defaults to denying them entry, so a bot-based tool now requires manual host approval to get in. Google also began routing higher-risk join requests, which is where third-party bots tend to land, into a separate safeguarded admit flow. The friendly automatic bot that used to slip into the meeting is now a join request a human has to consciously approve every single time.

This is not one vendor's quirk. It is the major platforms converging on the same posture: an unmanaged bot that joins a meeting and sends the recording somewhere else is a risk to be gated by default, not a convenience to be waved through.

Why the platforms are doing this

The reasoning is straightforward once you look at what a guest bot actually is. It is an external, unmanaged participant that enters a private conversation, captures every word, and exfiltrates the audio and transcript to a cloud the meeting organiser does not control. Several things about that make security and compliance teams uneasy:

Data leaves your control. The recording lands in the bot vendor's environment, under the bot vendor's jurisdiction and retention rules, not yours.
Consent is murky. A bot admitted quickly at the top of a call rarely comes with a clear moment where every participant understands who ultimately receives the recording.
Identity is weak. A named guest in the participant list is not an authenticated, managed identity; it is a label. Administrators had little ability to say "no automated recorders from outside our tenant" until now.

Detecting and gating bots hands that control back to the organisation. Teams labelling a bot in the lobby and Meet forcing manual approval are both about the same thing: making the decision to let an external recorder into the room a deliberate, visible one.

Bot-based versus bot-free, concretely

	Bot-based capture	Bot-free capture
How it records	A separate bot joins the meeting as a guest	A real participant's own client records the audio it already receives
Appears in the meeting	Yes, as an extra attendee	No extra attendee
Goes through the lobby	Yes, and can be labelled and blocked	No lobby step to gate
Affected by the 2026 Teams/Meet controls	Yes, can be blocked or forced to wait for approval	No
Typical tools	Otter, Fireflies, Read AI, Fathom	Client-side and tab-based recorders

The honest nuance: bot-free is not automatically "more compliant" in every respect, and it does not remove your obligation to tell participants a meeting is being captured. Consent, lawful basis and, in Germany, works-council duties apply to any recording regardless of how it is captured. What bot-free capture changes is narrower and specific: there is no external guest joining the meeting, so the platform bot controls have nothing to act on, and no data is handed to a third-party bot vendor in the process.

What this means for your stack

If your organisation runs Teams or Meet and enables the new controls, a bot-based notetaker faces one of three outcomes: it is blocked outright, it is forced to wait for a host to manually approve it on every call, or it is allowed in but barred from generating the transcript. None of those is a reliable foundation for a workflow people depend on. Reliability is now an architectural property, not a feature you can patch.

So the buying question has changed. It used to be enough to ask what a notetaker does with your data after the meeting. In 2026 you also have to ask how it gets into the meeting in the first place, because that determines whether it will keep working as administrators tighten these controls. A single question separates the two models: does your tool join my meeting as a bot, or does it capture from my own client?

Where Numi sits, honestly

Numi captures bot-free. It records from the participant's own client, the audio present in the browser tab, rather than sending a separate bot to join as a guest. No extra attendee shows up in the meeting, nothing has to be admitted through the lobby, and there is no external bot for Teams or Meet to detect or block. That is why the 2026 platform controls do not break Numi: there is simply nothing there for them to gate.

We did not choose this design to dodge a crackdown that had not happened yet; we chose it because capture should belong to a participant who is already lawfully in the meeting, not to an external recorder admitted on their behalf. The platform shift just made the architectural difference visible. The honest claim stops there: bot-free capture keeps the tool working and keeps the recording out of a third-party bot vendor's cloud. Your consent and documentation duties still apply, and we build the disclosure and EU-sovereign processing to make those easy to meet.

This article describes platform behaviour and rollout timelines as of 31 July 2026, based on Microsoft and Google announcements and reporting; exact dates and availability can shift per tenant and region. It is general information, not legal advice. Sources: Microsoft Teams third-party recording bot controls (targeted release from mid-May 2026, general availability by mid-June 2026, admin auto-block from August 2026); Google Meet March 2026 notetaker-bot risk gating.