A video meeting interface illustrates AI bots awaiting approval or being blocked at a secure meeting access gate.
Microsoft is getting ready to add an approved list for AI notetakers in Teams meetings. Today, admins have three broad choices for external meeting bots: ignore them, send them to the lobby for approval, or block them. A new item on the Microsoft 365 roadmap, ID 580451, will let admins name the specific external meeting bots that may join meetings hosted in their organization. Admins will then decide what happens to every other bot: block it, or keep sending it to the existing lobby approval step.

The feature is still in development. Microsoft estimates general availability in January 2027. You can't configure it today.

A video meeting interface illustrates AI bots awaiting approval or being blocked at a secure meeting access gate. What the roadmap item says​

Here is what Microsoft's roadmap entry says:

  • Allowed-bot list: Admins will be able to list the external meeting bots that may join meetings hosted in their organization.
  • What happens to other bots: Admins can either block all other bots or send them to the current lobby approval experience, which the roadmap calls "high friction."
  • How approved bots are treated: An allowed bot is handled like a regular external participant. Meeting policies still apply to it where relevant.
  • Platforms: Android, desktop, iOS and Mac.
  • Clouds: Worldwide (Standard Multi-Tenant) and GCC.
  • Release ring: General Availability. Estimated GA is January 2027.

The roadmap is a forecast, not a promise. Microsoft says the roadmap gives estimated release dates and descriptions, and that all of it is subject to change.

The entry also leaves several things unanswered:

  • What the admin interface will look like.
  • Whether bots are identified by vendor, app ID or something else.
  • How list entries are created and maintained.
  • How the list interacts with separate meeting policies.
  • Whether GCC High, DoD or other clouds will get it.

Treat any confident answers to those questions with caution until Microsoft publishes documentation.

Summary: Microsoft plans to add a per-bot exception list on top of the bot detection Teams already has, with a target of January 2027.

Where this fits: the controls that already exist​

The new list builds on bot detection that has been arriving throughout 2026. Topedia reported that Microsoft was rolling out bot detection for Teams meetings, with an additional approval step before external meeting assistant bots can be admitted from the lobby. The blog added that previously, Teams labeled such a bot as a normal meeting participant.

Admins control this with the ExternalBotAccessMode setting in Teams meeting policies. Microsoft's PowerShell reference for Set-CsTeamsMeetingPolicy lists three values:

ValueBehavior
AllowAllBotsNo detection. Bots look like any other participant, normal lobby rules apply, and a bot can be admitted by mistake.
RequireApprovalWhenDetectedDefault. A detected bot always goes to the lobby, whatever the meeting's lobby setting, and someone must approve it.
BlockDetectedBotsA detected external bot or meeting assistant can't join meetings hosted in your organization.

The block option came out earlier in 2026. VoIP Review reported in July that from August 2026, administrators can automatically block detected external AI notetakers. Basil AI tracked that change as roadmap item 566201. CyberPress said admins can apply the block policy across an entire Microsoft 365 tenant or apply it selectively to particular users and groups.

That leaves an obvious gap. Blocking every detected bot is crude when your sales team relies on one approved transcription service. Requiring approval for every bot puts the decision on each meeting organizer, every time. As VoIP Review noted, the approval step still relied on fast human judgment. The roadmap's allowed-bot list is meant to sit between those two extremes.

Summary: You can already ignore, review or block detected external bots. The new list will let you exempt the specific bots your organization approves.

How to configure today's bot controls​

While you wait for January, review your current bot setting.

In the Teams admin center​

  1. Open the Teams admin center and go to Meetings > Meeting policies.
  2. Edit the org-wide default (Global) policy, or a custom policy assigned to specific users or groups.
  3. In the Meeting join & lobby section, find Manage external bots and their access to meetings.
  4. Choose your option and save.

Microsoft Learn's page on managing external bots lists only two options in its table: Do not detect bots and When detected, require approval before joining. Third-party coverage describes a third option in the admin center. AdminDroid listed Block detected bots – New (ExternalBotAccessMode: BlockDetectedBots). If your tenant doesn't show the block option yet, use PowerShell instead.

In PowerShell​

Run these commands from the MicrosoftTeams module:

Code:
# Check the current setting on every meeting policy
Get-CsTeamsMeetingPolicy | Select-Object Identity, ExternalBotAccessMode

# Default: send detected bots to the lobby for approval
Set-CsTeamsMeetingPolicy -Identity Global -ExternalBotAccessMode RequireApprovalWhenDetected

# Stricter: block detected external bots
Set-CsTeamsMeetingPolicy -Identity Global -ExternalBotAccessMode BlockDetectedBots

Watch for documentation errors. Microsoft's own pages don't agree with each other:

  • The Learn page's table calls the "do not detect" value AllowBots. The cmdlet reference calls it AllowAllBots.
  • The Learn page's example commands use Set-CsTeamsEventsPolicy, even though the surrounding text says to use Set-CsTeamsMeetingPolicy.

The cmdlet reference documents ExternalBotAccessMode on Set-CsTeamsMeetingPolicy. Use that cmdlet with the values shown in the table above.

Signs the change worked​

  • Approval mode: Detected bots show up flagged in the lobby. They don't pass straight through, even in meetings whose lobby settings would normally let people skip the lobby.
  • Block mode: CyberPress reported that the bot will not remain in the lobby, and organizers will not need to approve or reject it manually.

Summary: Check your current setting, pick approval or blocking per policy, and follow the cmdlet reference where the Learn page disagrees with it.

Limits to understand before and after January​

This is a governance control, not a guarantee. Microsoft's documentation states several limits:

  • Some bots won't be detected. Microsoft says detection uses a mix of infrastructure and behavioral signals collected while a participant joins, and that some external bots may still get through. Users can report missed bots through the Feedback option in Teams.
  • Real people can be flagged as bots. An organizer can admit the person from the lobby and choose This is not a bot. That changes how the person appears for that meeting only.
  • Only external bots are covered. Topedia reported the detection does not affect internally managed bots or Entra ID applications registered within your own organization's tenant.
  • Notetakers running on someone's own computer aren't covered. Scribbl put it bluntly: A note taker on your computer isn't in scope. The PowerShell reference does list a separate client-side setting, EnableExternalRecordingDetection. It controls whether Teams detects third-party apps capturing audio on the user's device and notifies participants, and it is off by default.

An allowed-bot list will make detection more useful, but it won't make detection complete. A bot that Teams never recognizes as a bot can't be held to your list. It just looks like another participant.

What admins should do now​

Microsoft's guidance and the coverage above point to a few practical steps:

  1. Keep the default approval mode unless you have a reason to change it. Microsoft recommends it as the balanced choice and advises against turning detection off unless a specific business need requires it.
  2. Limit who can admit people from the lobby. Microsoft suggests allowing only organizers and co-organizers to admit participants, so other presenters can't let a bot in without proper checks.
  3. Use stricter policies for sensitive groups. Legal, HR and executive teams are good candidates for BlockDetectedBots through a targeted policy.
  4. Make a list of notetakers people actually use. Basil AI recommends pulling the last 30 days of Teams admin center reporting and Microsoft 365 audit logs to see which external bots have been joining your meetings. That list will be the starting point for your allowed bots in January.
  5. Tell meeting organizers what's happening. Microsoft's guidance includes educating organizers about bot risks and watching audit logs for unusual participant activity.

The bigger picture​

AI notetakers multiplied faster than most compliance teams could vet them. Microsoft says external meeting assistants can record or transcribe meetings without participants knowing, and can store meeting data in third-party systems outside an organization's compliance boundaries.

Microsoft has responded in stages. First came detection, then lobby approval, then blocking. An allowed-bot list is the next step, and it lets admins approve the tools their organization has actually vetted instead of blocking or reviewing everything.

Vendors of browser-based or device-based notetakers that don't join as participants will likely market themselves as unaffected by these controls. Basil AI already says this policy doesn't affect its product. That's a reminder that you also need endpoint and app policies, not just meeting-join rules.

Whether January 2027 arrives on schedule is up to Microsoft's roadmap. If you've already settled your current bot policy and vetted the notetakers you use, turning on the allowed list should be a quick change.

 

References

  1. Microsoft Teams: Configure a list of allowed external meeting notetaker bots for your Teams meetings Microsoft 365 Roadmap 2026-11-19T23:37:54.702214Z
  2. Microsoft Teams Lets Admins Automatically Block AI Notetakers From Meetings cyberpress.org
  3. Microsoft Teams Is Blocking Meeting Bots in 2026: The Lobby Rule, the New Block Policy, and What It Means for Each AI Note Taker · Scribbl scribbl.co