MC1251206: Microsoft Teams Adds Detection and Controls for External Meeting Bots

MWPRO IMPACT SCORE
OPERATIONAL IMPACT
52
0 25 50 75 100
HIGH IMPACT • REVIEW RECOMMENDED
Recommended Action:
Review the update and plan any required actions before rollout.
What is MWPro Impact Score? Watch our 60‑second explainer

Primary Audience

Microsoft 365 AdminsTeams AdminsSecurity TeamsIT ManagersService Owners
Why this score?
AI Confidence
HIGH
Enough detail is available to trust this assessment.
Assessment Reasoning
The rollout is still in progress and the timeline has been extended to mid-September. Admin impact is significant as a new policy control is being added in the Teams admin center and defaults will apply automatically, requiring governance review. Organizers will see new approval prompts and indicators, creating moderate user impact. Urgency remains moderate because the feature is enabled by default and controls may need review to align with compliance requirements.
60
🛡️ Admin Impact
35
👥 User Impact
55
Urgency
45
🔧 Effort
ℹ️ WHAT YOU NEED TO KNOW
📌

AT A GLANCE

Teams will now detect external meeting bots, showing them in the lobby and giving organizers approval controls. A new admin policy is available.
👥

END USERS

Organizers may see bots flagged in the lobby and need to approve or deny them before joining.
🛡️

IT ADMINS

Review the new Teams meeting policy and inform organizers about bot detection and approval prompts.
📅

ROLLOUT TIMELINE

Rolling out:
Completing mid-Sept 2026

📢 Official Microsoft Message Center Announcement


(Updated) Microsoft Teams: Identify external bots joining your Teams meetings
Message ID: MC1251206 (Updated)

Updated September 2, 2026: We have updated the timeline. Thank you for your patience.

[Introduction]

AI‑powered meeting assistant bots—such as transcription and summarization services—are increasingly used to enhance productivity in online meetings. While these tools can be valuable, some bots may access meetings without the knowledge or consent of the meeting organizer or the hosting tenant, which can create data security, privacy, and compliance risks.

To help organizations protect meeting content and increase visibility into automated participants, Microsoft Teams is introducing a new capability that detects external meeting assistant bots as they attempt to join meetings. This update gives organizers greater awareness and control and provides administrators with clear controls to manage how detected bots are handled in meetings hosted across the organization.

This message is associated with Microsoft 365 Roadmap ID 558107.

[When this will happen]

  1. Targeted Release: We will begin rolling out in mid-May 2026 and expect to complete by early June 2026.
  2. General Availability (Worldwide): We will begin rolling out in early June 2026 and expect to complete by mid-September 2026 (previously end of August).
  3. General Availability (GCC): We will begin rolling out in early June 2026 and expect to complete by mid-September 2026 (previously end of August).

[How this will affect your organization]

Who is affected

  1. All organizations using Microsoft Teams meetings, including GCC tenants
  2. Meeting organizers and Teams administrators

What will happen

  1. Teams will detect external meeting bots as they attempt to join meetings hosted by your organization.
  2. When detected, bots will be clearly labeled in the meeting lobby experience.

  3. Note: There might still be bots that are undetected by the system due to their intrinsic behavior. Please inform your users to report them out directly from the app/meeting. This will help us improve our detection system.
  4. Organizers will be able to:
  5. approve or deny detected bots from the meeting lobby.
  6. see clearly which participants have been identified as bots.
  7. remove detected bots during the meeting if necessary.
  8. These organizer controls are designed to help ensure that bot participation in meetings is an intentional and informed decision.
  9. A new meeting policy will be available in the Teams admin center that allows admins to configure how detected bots are handled (do not detect bots, require approval). In the future, we intend to provide more granular controls to admins, as appropriate.
  10. Bot detection will be enabled by default for all tenants.
  11. Teams will continue improving detection accuracy; however, some bots may not be detected in all scenarios.

user settings

user settings

[What you can do to prepare]

No action is required at this time.

However, we recommend that Teams admins:

  1. Review the new meeting policy in the Teams admin center once it becomes available.
  2. Keep the default setting, which requires organizers to approve detected bots before they join meetings (recommended).
  3. Choose a stricter or more permissive option based on your organization’s collaboration and compliance requirements.
  4. Inform meeting organizers that they may see new indicators and approval prompts when detected bots attempt to join meetings.
  5. Update internal helpdesk or governance documentation if your organization documents meeting join or lobby controls behavior.
  6. Monitor future Message center updates for expanded administrative controls.

[Compliance considerations]

QuestionAnswer
Does the change introduce or significantly modify AI/ML or agent capabilities that interact with or provide access to your data?Yes. This change introduces detection logic that analyzes meeting join metadata to identify external automated bots attempting to join meetings.
Does the change provide a new way of communicating between users, tenants, or subscriptions?No. The feature only changes how external meeting assistant bots are surfaced to organizers during the meeting join process, increasing visibility of automated external participants. There is no change in the way participants can communicate with these bots or vice versa.
Does the change include an admin control, and can it be controlled through Entra ID group membership?Yes. The change introduces a new meeting policy in the Teams admin center that allows admins to define how detected bots are handled. It cannot be controlled through Entra ID group membership at this time.


Source: Microsoft Message Center • Analysed by MWPro

<<< [MC1251206] Archive
Tooltip: View earlier revisions of this post

Share This Update