Microsoft Teams meetings

How to block AI bots from joining Teams meetings

AI notetaker bots arrive through calendar connections, outside attendees and forwarded links. They record what people say and keep it on servers your organisation does not control.

This guide shows the Teams admin center settings that keep them out, and how to block the notetaker services behind them on your network and devices.

Waiting in the lobby 3 people
Guest from a partner companyExternal, signed inInvited
Meeting notetakerJoined from a calendar connectionDetected bot
Anonymous participantJoined by link, not signed inNot verified
With bot detection on, a detected bot waits here even when your lobby rules would let it straight in.

Next step

AI Agent Blocklist: block AI notetaker and meeting agent services on every managed device

Teams settings decide who gets into a meeting. Our list stops staff from signing up to, installing and using notetaker services you never approved.

AI meeting and voice agentsExtension IDsDesktop app IDsUpdated every day
From $99 a month for one organisation Files for firewalls, DNS filters, Intune and browser policies

How AI bots get into Teams meetings

Most admins first notice a meeting bot when it shows up in a sensitive call. By then it has usually been joining meetings for weeks. There are four common ways in, and each one needs a different control.

1

A calendar connection

A user signs up to a notetaker with their work account and lets it read their calendar. From then on the bot tries to join every meeting on that calendar, including meetings other people organise.

Control: Entra consent, bot detection
2

An outside attendee

A customer, supplier or candidate uses their own notetaker. Their bot follows their invite into your meeting as an external or anonymous participant.

Control: bot detection, lobby rules
3

A forwarded link

Meeting links get forwarded, pasted into chats and posted in tickets. Anyone with the link can try to join as an anonymous participant, and bots are no exception.

Control: anonymous join, lobby
4

No bot at all

Desktop notetaker apps and browser extensions record audio on the laptop itself. Nothing appears in the participant list, so no meeting setting can see them.

Control: device and network blocking

Who is exposed

Meeting typeWhat a bot capturesWhy it hurts
HR and disciplinary meetingsNames, health details, complaintsPersonal data held by a service with no contract with you
Legal and privileged callsAdvice, strategy, settlement figuresA transcript at a third party can weaken privilege
Board and financeResults before release, deal termsInside information leaves your control
Customer and sales callsPrices, contract terms, customer dataYour customer's data ends up in a tool they never agreed to
School, patient or client meetingsStudent, patient or case detailsSector privacy rules usually forbid this
Security incident callsWeak points, response stepsA record of what you know and what you do not

Signs to look for

  • Participants named like a tool, such as "Notetaker" or "someone's assistant"
  • Staff receive meeting summaries from a service IT never approved
  • Consent grants for meeting assistant apps in Microsoft Entra
  • Unknown meeting apps in the Teams app usage report
  • Anonymous participants that never speak and never turn on video
  • DNS or firewall logs show traffic to notetaker domains
  • Questions to the help desk about recaps nobody asked for

What a meeting bot can take with it

A notetaker bot is a participant that never forgets. Microsoft's own admin guidance lists the same risks we see: recording without people knowing, data stored outside the organisation's compliance boundary, and leaks.

Every word spoken

A full transcript with speaker names, often with timestamps and action items added.

Shared screens

Spreadsheets, dashboards and documents shown during the call can be captured as video or images.

Meeting chat

Links, file names and side remarks typed into the chat during the meeting.

Who attended

Names and email addresses of every participant, which can feed sign-up invitations later.

Storage you do not run

Recordings and transcripts sit in the vendor's cloud under the vendor's retention rules.

Summaries sent onward

Many services email a summary to attendees, so the content travels further than the invite list.

The problem is not one product. It is meeting data leaving the company through tools nobody approved. Our guide to shadow AI agents covers the wider pattern.

Microsoft Teams: turn on bot detection in meeting policies

Teams meeting policies have a setting called Manage external bots and their access to meetings. It sits in the Meeting join & lobby section and works per policy, so you can treat HR, legal or the board differently from everyone else.

Do not detect botsOff
AllowAllBots

Bots look like any other external participant. Normal lobby rules apply, so a bot can be admitted by mistake.

When detected, require approval before joiningDefault
RequireApprovalWhenDetected

Detected bots always wait in the lobby, even if the meeting lets everyone bypass it. Organizers must admit them on purpose.

Block detected botsStrict
BlockDetectedBots

Detected external meeting bots and meeting assistants cannot join meetings your organisation hosts. Newer option: check the current admin console for its label.

  1. Open meeting policies

    In the Teams admin center, expand Meetings and select Meeting policies.
  2. Pick the policy

    Open the org-wide default policy (Global) to change everyone, or a custom policy assigned to a sensitive group.
  3. Find the bot setting

    In Meeting join & lobby, open Manage external bots and their access to meetings and choose approval or block.
  4. Save and wait

    Select Save. Microsoft says meeting policy changes can take up to 24 hours to reach users.
  5. Tell your organizers

    Explain the new lobby label for bots and ask people not to admit a bot unless the meeting owner has agreed to it.
Set-CsTeamsMeetingPolicy -Identity Global -ExternalBotAccessMode RequireApprovalWhenDetected Set-CsTeamsMeetingPolicy -Identity "Board and Legal" -ExternalBotAccessMode BlockDetectedBots

Detection is one layer, not the whole fix. Microsoft states that some external bots may not be detected and that a person can occasionally be flagged as a bot. An organizer can admit a wrongly flagged person and mark them as not a bot.

Microsoft retired the older CAPTCHA verification check for meeting join during 2026 and now relies on bot detection. If you still see a verification check setting, check the current admin console.

Lobby and anonymous join settings that stop bots at the door

Bots that are not detected still have to get past the lobby. These meeting policy settings, all in Meeting join & lobby, decide who waits and who walks straight in.

SettingValue for bot controlEffect on botsTrade-off
Anonymous users can join a meetingOff for sensitive groupsBots that join without a signed-in account cannot get inGuests without a work account cannot join either
Anonymous users and dial-in callers can start a meetingOff (the default)A bot cannot sit in an empty meeting before a verified person arrivesNone for most organisations
Who can bypass the lobbyPeople who were invited, or People in my orgAnonymous joiners and link holders wait for an organizerOrganizers admit external guests by hand
People dialing in can bypass the lobbyOff (the default)Phone callers wait until admittedDial-in users wait a little longer
Who can admit from lobbyOrganizers and co-organizersA presenter cannot wave a bot inFewer people can admit latecomers

To switch anonymous join off for the whole tenant, go to Meetings, Meeting settings, then the Participants section, and set Anonymous users can join a meeting to Off. The meeting policy setting with the same name lets you do it per organizer instead.

Set-CsTeamsMeetingPolicy -Identity "Board and Legal" -AllowAnonymousUsersToJoinMeeting $false Set-CsTeamsMeetingPolicy -Identity "Board and Legal" -AutoAdmittedUsers InvitedUsers Set-CsTeamsMeetingPolicy -Identity Global -AllowAnonymousUsersToStartMeeting $false

Organizers can change lobby defaults. Who can bypass the lobby, People dialing in can bypass the lobby and Who can admit from lobby are defaults that organizers can change in Meeting options.

To enforce lobby values for sensitive meetings, Microsoft points to meeting templates or sensitivity labels, which need Teams Premium. Who can admit from lobby is not supported there.

Block notetaker apps in Teams and stop calendar connections in Entra

Some notetakers also offer a Teams app, and almost all of them connect to Microsoft 365 calendars through a consent prompt. Close both doors so a bot is not invited from inside your tenant.

Teams apps: Manage apps

  1. Go to Teams apps then Manage apps and search for the notetaker by name.
  2. Select it and choose Block, or open its details page and switch the status to Blocked.
  3. To stop all third-party apps, open Actions, then Org-wide app settings, and turn off Third-party apps.
  4. Use app centric management to allow an approved meeting app only for the users or groups who need it.
  5. Export the app catalog as CSV and review what is allowed today.

Built-in Teams agents are managed on their own page, Teams apps then Built-in Teams agents, not on Manage apps.

Microsoft Entra: user consent

  1. In the Microsoft Entra admin center, browse to Identity, Applications, Enterprise apps, Consent and permissions, User consent settings.
  2. Choose Do not allow user consent, or allow consent only for apps from verified publishers for permissions you classed as low impact.
  3. Turn on the admin consent workflow so people can ask for an app instead of finding a way around you.
  4. Review existing grants under Enterprise apps. Changing the setting does not remove consent people already gave.
  5. For an unwanted notetaker app, revoke its permissions or set Enabled for users to sign-in? to No.

Agents use the same door. General AI agents, ChatGPT agent among them, reach Microsoft 365 mail, files and calendars through connections a user approves. Your consent settings decide whether one person can approve that alone.

Our page on AI agent identity and permissions goes deeper.

Block the notetaker services with the AI Agent Blocklist

Teams settings protect meetings you host. They do not stop staff from signing up to a notetaker, installing its desktop app or adding its extension, and they cannot see a recorder that never joins. That is the gap our list closes.

What the list holds for meetings

  • Domains of AI meeting and voice agents: notetakers, call recorders and meeting summarisers
  • Chrome and Edge extension IDs of meeting recorder extensions
  • macOS bundle IDs and Windows package IDs of desktop notetaker apps
  • A category and a risk grade on every entry, so you can block all of them or only the higher-risk ones
  • Daily updates as new meeting assistants appear

Example entries

ToolTypeIdentifier
Read AIDomainread.ai
Read AIChrome extensionaiamjjeggglngiggkmmbnpnpeejjejaf
Read AIWindows packageReadAI.ReadAI
Otter.aiDomainotter.ai
Fireflies.aiDomainfireflies.ai

A few examples only. The full files cover far more tools and identifiers.

Firewall

Load the domain list as an external list. See FortiGate and other firewalls.

DNS filter

Import the DNS file so lookups for notetaker domains fail. Guide: block AI with DNS.

Intune

Use the Windows and macOS identifiers to find and remove desktop notetakers. See Intune.

Browser policy

Add the extension IDs to your blocklist. Steps: block AI extensions.

Block Read AI with FortiGate

A common search is how to block one notetaker at the firewall. The same steps load our whole meeting agent category at once, so the next new service is covered too.

This stops use from your networks. A bot running in the vendor's cloud still needs the Teams settings above.

  1. Go to Security Fabric, External Connectors, Create New, and pick Domain Name under Threat Feeds.
  2. Name it, set the update method to External Feed and enter the URL of your list file as the external resource.
  3. In Security Profiles, DNS Filter, enable the FortiGuard category based filter and set the action for the feed under Remote Categories.
  4. Apply the DNS filter profile to the firewall policies your users go through, then check the logs.

Block

  • Notetaker services nobody approved
  • Their browser extensions
  • Their desktop apps on Windows and macOS
  • Higher-risk meeting agents by grade

Monitor

  • New entries in the meeting agent category
  • Who still tries to reach blocked services
  • Consent grants and app requests in Entra

Allow

  • The meeting assistant your organisation licensed
  • Its domains, placed above the block rule
  • Only for the groups that need it

A rollout that keeps meetings working

Changing meeting policies for a whole company at once causes support calls. This order lets you see what is in use before you block it.

  1. See what is in use

    Export Entra consent grants, the Teams app catalog and a week of DNS logs matched against our meeting agent category in monitor mode.

  2. Pick one approved notetaker, or none

    Write the decision into your rules. Our AI agent acceptable use policy has wording you can adapt.

  3. Turn on bot detection

    Keep approval when detected for everyone, and use the block option for HR, legal, finance and board policies.

  4. Tighten lobby and consent

    Set lobby bypass to invited people, limit who can admit, and restrict user consent with an admin request path.

  5. Block the services

    Load the list into your firewall or DNS filter and your browser policies, with the approved tool on the allow list.

  6. Review every week

    New meeting assistants appear all the time. The daily list picks them up; your job is to read the blocked-traffic report.

A bot is already in the meeting? The organizer can remove it from the participant list and lock the meeting so it cannot rejoin. Afterwards, find whose calendar brought it, remove that consent grant and move the user to a stricter policy.

Keep meeting data inside your tenant

The AI Agent Blocklist covers AI meeting and voice agents along with AI browsers, agents, extensions, coding agents and MCP servers. One subscription, every format, updated every day.

After an order we set up your download access within one business day. See what the blocklist contains or compare plans.

  • Plain domain list, hosts file and PAC file
  • CSV and JSON with tool name, category, identifier type and risk grade
  • Firewall external list format for FortiGate, Palo Alto and others
  • DNS filter import files
  • Chrome and Edge extension block lists for Group Policy, Intune and the Google Admin console
  • macOS and Windows identifiers for Jamf and Intune

Running Zoom as well? The same layers apply there, with different setting names. Read how to stop AI notetakers in Zoom, or start wider with blocking AI agents across the company.

Ask us or order a plan

Tell us what you need to block and where your rules live. We reply within one business day.

  • Files for firewalls, DNS filters, secure web gateways, MDM and browser policies
  • Updated every day as new AI browsers, agents and extensions appear
  • Plans for one organisation, for MSPs and for product makers, or a hosted filter we run for you

We use your details only to answer you. No newsletters.

Teams AI bot questions

How do I block AI bots from joining Teams meetings?

In the Teams admin center go to Meetings, Meeting policies, open the policy and find Manage external bots and their access to meetings in the Meeting join and lobby section. Choose to require approval when a bot is detected, or to block detected bots where your tenant offers it.

Then tighten anonymous join and lobby settings, block notetaker apps under Teams apps, limit user consent in Microsoft Entra and block the notetaker services on your network.

Can I block Read AI and other bots brought by external participants?

Yes, for meetings your organisation hosts. Bot detection applies to external third-party meeting bots whoever invited them, and detected bots wait in the lobby or are blocked depending on the policy. Turning off anonymous join for sensitive groups stops bots that join without a signed-in account.

How do I disable an AI bot that is already in a Teams meeting?

The organizer can remove the bot from the participant list and lock the meeting so it cannot rejoin. To stop it next time, find the user whose calendar brought it, remove the consent grant in Microsoft Entra and change the meeting policy for that group.

Does Teams detect AI notetaker bots on its own?

Teams meeting policies include bot detection. The default setting sends detected bots to the lobby until someone admits them. Microsoft says some bots may not be detected and some people may be flagged by mistake, so treat it as one layer, not the whole fix.

Can I block Read AI with FortiGate?

Yes, on your own network. Add our domain list as a Domain Name threat feed under Security Fabric, External Connectors, then set the action for that remote category in your DNS filter profile. This stops staff from using notetaker services from managed networks.

It does not stop a bot that runs in the vendor's cloud and joins by meeting link, which is why the Teams settings matter too.

Does turning off anonymous join stop every bot?

No. It stops bots that join without a signed-in account.

A bot can still arrive as a signed-in external participant, and a desktop notetaker can record from a laptop without joining at all. Combine anonymous join settings with bot detection, consent controls and device blocking.

What about ChatGPT agent and other AI agents in Teams?

General AI agents reach Microsoft 365 data through app connections that a user approves. Your Entra user consent settings decide whether people can approve those connections on their own, and our list covers the agent services and their extensions so you can block or allow them on purpose.

Microsoft, Microsoft Teams, Microsoft 365, Microsoft Entra and Intune are trademarks of the Microsoft group of companies. Fortinet and FortiGate are trademarks of Fortinet, Inc. ChatGPT is a trademark of OpenAI.

Read AI, Otter.ai, Fireflies.ai and Zoom are trademarks of their respective owners. Names are used only to identify the products discussed. AI Agent Blocklist is not affiliated with, sponsored or endorsed by these companies.