AI Note Taker for Microsoft Teams: What Your Tenant Policy Allows
11 vendors, all facts read off the vendor’s own documentation and verified 2026-09-07.
On Microsoft Teams the buying question is not which notetaker is best. It is whether your Microsoft 365 tenant will let it into the room at all. Most bot-based tools here depend on the same family of tenant settings, and those settings are off by default in most organisations for good reasons. Five of the seven bot-based tools here publish such a requirement; the other two publish no Teams admin documentation at all.
So the spine of this page is a single split. Bot-based tools all need the same tenant policy changed. If you cannot get that change approved, stop evaluating them entirely and look only at the bot-free column, where nothing joins the meeting and no admin has to sign anything off.
The Zoom equivalent of this page gates on something else - Marketplace approval and encryption - and is at AI note taker for Zoom. Where a vendor’s pages disagree with each other, that is catalogued on the vendor claim tracker.
Bot-based on Teams: all gated on the same tenant setting
Each of these tools joins the meeting as an anonymous or guest participant, which means the tenant has to permit anonymous or guest join. The differences between them are in how many additional settings they need, and in what they publish about the failure modes.
Bot joins the meeting
“Fathom records Microsoft Teams meetings by joining them as the Fathom Notetaker.”
“The organization-wide Anonymous users can join a meeting setting must be on, and the organizer's assigned meeting policy must allow Anonymous users can join a meeting unverified.”
“Even when ordinary anonymous participants are allowed to bypass the lobby, Microsoft may identify an external meeting assistant as a bot and require explicit approval before it can join.”
- Tenant setting: Anonymous users can join a meeting - On
- Organizer's meeting policy: Anonymous users can join a meeting unverified
- Standard meeting-join links only
Even with anonymous join allowed, Microsoft may identify the Fathom Notetaker as a bot and require explicit approval before it can join, so an approved tenant policy is still not a guarantee.
Bot joins the meeting
“Set Who can bypass the lobby to People in my org and guests”
“Set Require a verification check from to Not required”
“Set Manage external bots and their access to meetings to Do not detect bots”
“up to 24 hours”
- Who can bypass the lobby: People in my org and guests
- Require a verification check from: Not required
- Anonymous users can join a meeting unverified: On
- Manage external bots and their access to meetings: Do not detect bots
Fireflies publishes four distinct Teams settings and states the changes may take up to 24 hours to propagate.
Bot joins the meeting
“Notetaker joins Zoom, Google Meet, and Microsoft Teams meetings as a guest participant”
“Your meeting and organization settings must allow guest participants for Notetaker to join”
“Notetaker cannot join a meeting anonymously or without appearing to other participants.”
“On February 14th, 2024, Microsoft published a change that will now label guest users as `unverified`.”
“Refer to Microsoft's documentation for the most up-to-date information on unverified guests.”
- Meeting and organization settings must allow guest participants
Otter publishes that Microsoft now labels guest users as unverified, and its article points the reader to Microsoft's own documentation for the most up-to-date information on unverified guests.
Bot joins the meeting
“The Notetaker joins Teams meetings as a participant at the scheduled start time. It joins independently, even if you don't join yourself.”
“The Notetaker joins Teams meetings unauthenticated.”
“the Notetaker is placed in the lobby and waits up to 10 minutes to be admitted by the host.”
“The keyword 'MeetGeek Bot' must remain in the Notetaker's name so it can tell real participants apart from bots and correctly detect the end of the meeting.”
- Unauthenticated join must be permitted (anonymous join)
- A host must admit the bot from the lobby within 10 minutes
- Only teams.microsoft.com and teams.live.com links are supported
Instant meetings need the link pasted in manually, the bot's name cannot be freely renamed, and an unadmitted bot gives up after 10 minutes.
Bot joins the meeting
“Notta Bot joins Teams meetings as a guest. If your Teams meetings require user authentication, the bot won't be able to enter.”
- Anonymous users can join a meeting unverified: enabled
- Verification check: Not Required
Any tenant that requires user authentication blocks the bot outright: Notta states the bot joins as a guest and cannot enter where authentication is required.
Bot joins the meeting
“tl;dv streamlines and saves time by enabling any user to record a Microsoft Teams meeting, no host permission required!”
“All participants can see the live tl;dv recorder in the call, ensuring full transparency.”
- Not published by the vendor
tl;dv publishes no help-centre article on Teams lobby or anonymous-join policy. Its Teams admin requirements are not published by the vendor, so an admin cannot pre-check them before the first meeting.
Bot or browser extension
“Connect your Teams calendar and let a bot join and record the conversation.”
“participants will be notified of the bot's presence and the reason for your recording.”
“Download the Noota extension to record your Teams meetings on your browser.”
- Not published by the vendor
Noota publishes no admin-configuration article for Teams at all. noota.io and support.noota.io document calendar connection and an in-meeting permission prompt, and nothing about Teams tenant policy. An IT admin has no vendor page to work from.
Bot-free on Teams: no tenant policy change at all
These tools capture audio on the device you are sitting at. Nothing joins the call, so there is nothing for a tenant policy to block - and equally, nothing that announces itself to the other participants. The constraints move from the tenant to the machine: operating-system version, audio-device selection, and which app the meeting runs in.
Bot-free, local device capture
“Granola runs on your laptop and uses your device's audio to generate notes”
“There is no meeting bot - Granola runs only on your computer and uses your system audio and microphone.”
“Granola cannot isolate audio from individual applications.”
- Microsoft Teams desktop app
- macOS 13+ or Windows
An audio-device mismatch captures only one side of the conversation, and Granola cannot isolate meeting audio from anything else playing on the machine.
Bot-free, local device capture
“Jamie transcribes your computer's audio directly, with no meeting bots joining your call.”
- macOS 13.1+, Windows, or iOS
Capture is tied to the device Jamie is installed on: a meeting taken on an unequipped machine is not captured at all, and the macOS floor of 13.1 rules out older hardware.
Bot-free, local device capture
“Krisp runs entirely on your device as a desktop app and never joins the call as a participant.”
“Krisp AI Meeting Assistant connects to MS Teams automatically with no plugins or extra setup.”
“only your speech is included, resulting in incomplete Transcripts”
“You should have at least a 30 seconds call to get a transcript”
“AI Meeting Assistant is not tailored for Enterprise teams.”
- Both the Krisp Microphone and the Krisp Speaker must be selected as devices
- macOS 14 Sonoma or higher, or Windows 10 1903+ / Windows 11
The transcript is private to the local user, an incorrect device selection silently captures only your own voice, calls under 30 seconds produce nothing, and Krisp itself states the assistant is not tailored for enterprise teams.
Bot-free, local device capture
“Bot-Free Recording is Notta Desktop's core feature. It records your meetings without sending a bot into the meeting room”
“Works with any meeting software: Zoom, Google Meet, Microsoft Teams, Webex, and browser-based meetings.”
“Microphone only - System audio recording is not supported”
“System audio captures all sounds played on your computer-not just meeting audio, but also music, notifications, and other sounds.”
- macOS 13 or later for system-audio capture; Windows supported
On macOS 11 and 12 recording is microphone only: Notta captures your own voice and not the other participants. On supported versions it captures every sound on the machine, not only the meeting.
Bot-free, local device capture
“records directly from your system audio, with no meeting bot required.”
- macOS or Windows
tl;dv publishes no minimum OS version and no Teams-specific caveats for the desktop app: those requirements are not published by the vendor.
Cannot use the Teams desktop app at all
Browser extension, reads platform captions
“Tactiq supports Microsoft Teams meetings in Google Chrome, Microsoft Edge, and the Microsoft Teams Progressive Web App (PWA). The Microsoft Teams desktop application is not currently supported.”
“Turn on Teams live captions from More actions > Language and speech > Show live captions.”
- Teams in Chrome, Edge, or the Teams PWA
- Teams live captions turned on in the meeting
In an organisation standardised on the Teams desktop client, Tactiq does not work. That is the vendor's own statement, not our inference.
What you are actually asking your IT admin to change
Microsoft ships these settings off, or restricted, because each one widens who can get into meetings. That is the honest trade-off: none of them can be scoped to a recording bot. They apply to every meeting under the policy.
| Setting | Asked for by | What it widens | Source |
|---|---|---|---|
| Anonymous users can join a meeting (org-wide) | Fathom | Permits participants with no Microsoft 365 identity into meetings across the tenant, not only recording bots. | |
| Anonymous users can join a meeting unverified (meeting policy) | Fathom, Fireflies.ai, Notta | Removes the verification check for anonymous participants under that policy, for every meeting the policy covers. | |
| Who can bypass the lobby: People in my org and guests | Fireflies.ai | Guests skip the lobby entirely, so a host no longer sees and admits each external participant. | |
| Require a verification check from: Not required | Fireflies.ai | Turns off the check that distinguishes an unverified joiner from a verified one. | |
| Manage external bots and their access to meetings: Do not detect bots | Fireflies.ai | Disables Microsoft's own bot detection for the tenant, which is the control that flags external meeting assistants. | |
| Guest participants allowed in meeting and organization settings | Otter.ai | Guest identities are permitted; Microsoft labels those guests unverified since 2024. |
If those changes will not be approved in your organisation, that is a complete answer, not a setback. Evaluate the bot-free column only, and drop every bot-based tool from the shortlist before you run a trial that cannot succeed.
Operating-system floors, which quietly eliminate tools
Bot-free capture depends on the machine. A fleet on older macOS silently rules some of these out, or degrades them to recording only your own voice.
| Tool | Published OS floor | Source |
|---|---|---|
| Krisp | macOS 14 Sonoma or higher; Windows 10 1903+ or Windows 11 | help.krisp.ai/hc/en-us/articles/360011979299-System-requirements-for-using-Krisp |
| Jamie | macOS 13.1 or higher; Windows; iOS | www.meetjamie.ai/blog/llm-info |
| Granola | macOS 13 or higher; Windows | docs.granola.ai/help-center/taking-notes/transcription |
| Notta Desktop | macOS 11-12: microphone only, no system audio. macOS 13+ for full capture | support.notta.ai/hc/en-us/articles/48345161234203-What-is-Bot-Free-Recording |
Questions buyers ask first
Why will a Teams AI notetaker not join my meeting?
Bot-based notetakers join Microsoft Teams as anonymous or guest participants. Microsoft 365 tenants block that by default. Five tools publish a tenant requirement: Fathom, Fireflies.ai, Otter.ai, MeetGeek and Notta all depend on the tenant permitting anonymous or guest join, and Microsoft may additionally identify the assistant as a bot and require explicit approval. tl;dv and Noota publish no Teams admin documentation at all, so with those two a buyer cannot tell in advance whether their tenant will admit them.
Which AI notetakers work on Microsoft Teams without an admin changing anything?
The bot-free tools capture audio on your own device rather than joining the call: Granola, Jamie, Krisp, Notta Desktop and the tl;dv desktop app. No tenant policy change is required for any of them, because nothing joins the meeting.
Does Tactiq work with the Microsoft Teams desktop app?
No. Tactiq states that it supports Teams in Google Chrome, Microsoft Edge and the Teams Progressive Web App, and that the Microsoft Teams desktop application is not currently supported. Teams live captions must also be switched on in the meeting.
What is the risk of enabling anonymous join for a notetaker?
Every one of these settings widens who can enter meetings across the whole tenant, not just for the notetaker. Allowing unverified anonymous join, lobby bypass for guests, or disabling bot detection applies to all meetings under that policy, not only the ones you want recorded.
Every fact on this page was verified on 2026-09-07 against the vendor documentation linked beside it. Where a vendor publishes nothing on a point, this page says so rather than filling the gap. The Zoom guide and the Google Meet guide cover the same tools on the other platforms, and AI note takers that don’t join the meeting compares the bot-free options directly.