How to Automatically Block External Meeting Bots in Microsoft Teams

IT administrator configuring Teams meeting protection

External AI note-takers and meeting bots are turning up in more and more Teams meetings, often invited by someone outside your organisation and often without anyone really thinking about where that recording or transcript ends up. Microsoft has been steadily adding controls for this, and the latest one is a Teams meeting policy option that automatically blocks identified external meeting bots from joining. Here’s what it does and exactly how I’d roll it out.

What’s changing

This is covered in Message Center post MC1459141 (Roadmap ID 566201). Today, Teams can already detect external bots, mark them in the lobby and require the organiser to admit them. The new option goes one step further: when it is enabled, identified external meeting bots are simply prevented from joining meetings governed by that policy.

The key points from Microsoft are:

  • It’s a new option in the existing Manage bots meeting protection settings in Teams meeting policies.
  • It is off by default. Nothing changes unless an administrator turns it on.
  • It can be assigned to specific users or groups through normal meeting policy assignment.
  • Existing bot detection and visibility for organisers and administrators stays the same.
  • Targeted Release started mid-September 2026 and was due to complete by late September. General Availability began in early October 2026 and is now expected to complete by the end of November 2026 (timeline updated 3 November).

For background, Microsoft Learn’s Manage external bots and their access to meetings page explains how detection works, using infrastructural and behavioural signals during the join process. Detection isn’t perfect, so a bot that isn’t identified can still get in, and occasionally a human may be misclassified.

Before you start

  • You need the Teams Administrator or Global Administrator role.
  • The option may not appear yet if the rollout hasn’t reached your tenant. If you don’t see it, check back later rather than hunting for a workaround.
  • I haven’t confirmed the exact wording of the new toggle across tenants, so look for the option to automatically block identified external meeting bots inside the Manage bots section rather than expecting a specific label.
  • Remember this may block note-taker and recording bots that some of your people rely on. That’s why piloting matters.

Step-by-step: enable auto-block

  1. Sign in to the Teams admin center at https://admin.teams.microsoft.com.
  2. Go to Settings & policies, then Meeting policies.
  3. Choose where to apply it. For a pilot (recommended), select Add to create a new policy, such as Pilot – Block meeting bots. To apply it to everyone, open Global (Org-wide default).
  4. Scroll to the Manage bots section.
  5. Turn on the option to automatically block identified external meeting bots.
  6. Select Save.
  7. If you created a pilot policy, assign it to the pilot users or a group. You don’t need to assign the Global policy, as it already applies to everyone without another policy.
  8. Wait a few hours for the policy to apply. Changes to meeting policies aren’t instant.
  9. Test it. Schedule a meeting as a pilot user and have an external bot try to join. It should be blocked rather than sitting in the lobby waiting for approval.

Doing it with PowerShell

If you prefer scripting, the Set-CsTeamsMeetingPolicy documentation lists an ExternalBotAccessMode parameter with three values: AllowAllBots, RequireApprovalWhenDetected (the default) and BlockDetectedBots. Using the Microsoft Teams PowerShell module:

Connect-MicrosoftTeams
New-CsTeamsMeetingPolicy -Identity "Pilot-BlockBots"
Set-CsTeamsMeetingPolicy -Identity "Pilot-BlockBots" -ExternalBotAccessMode BlockDetectedBots
Grant-CsTeamsMeetingPolicy -Identity "user@yourdomain.com" -PolicyName "Pilot-BlockBots"
Get-CsTeamsMeetingPolicy -Identity "Pilot-BlockBots" | Select-Object Identity, ExternalBotAccessMode

As always, test the cmdlets in your own tenant first, as parameter availability can lag the rollout.

Microsoft’s recommendations

Microsoft suggests the following if you plan to enable automatic blocking:

  • Review your organisation’s use of meeting bots and automated meeting applications.
  • Evaluate the feature with a pilot group before broader deployment.
  • Review existing Teams meeting policies and decide which users or groups should receive the policy.
  • Update internal documentation and help desk guidance.
  • Communicate the change to meeting organisers and users who rely on automated meeting bots.

My take

For most businesses I work with, this is a sensible control to have, but it’s not one to flip on for the whole tenant on day one. Find out who is actually using external note-takers, pilot it with a group that isn’t, then widen it once you know what breaks. Pair it with a clear position on which AI meeting tools are approved, because blocking the unapproved ones works best when people know what they should be using instead.

Leave a Reply