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

Message ID

MC1251206

Service

Microsoft Teams

Summary

Microsoft Teams will detect and label external meeting assistant bots attempting to join meetings, giving organizers control to approve, deny, or remove them. This feature, rolling out mid-2026, includes new admin policies for managing bots and aims to enhance meeting security and compliance.

Details

Updated July 20, 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]

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

[How this will affect your organization]

Who is affected

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

What will happen

Teams will detect external meeting bots as they attempt to join meetings hosted by your organization.
When detected, bots will be clearly labeled in the meeting lobby experience.
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.
Organizers will be able to:
approve or deny detected bots from the meeting lobby.
see clearly which participants have been identified as bots.
remove detected bots during the meeting if necessary.
These organizer controls are designed to help ensure that bot participation in meetings is an intentional and informed decision.
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.
Bot detection will be enabled by default for all tenants.
Teams will continue improving detection accuracy; however, some bots may not be detected in all scenarios.

user settings

[What you can do to prepare]

No action is required at this time.

However, we recommend that Teams admins:

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

[Compliance considerations]

Question	Answer
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.

Community Resources

Commentary - 365 Message Center Show

Video

Change History

Show

Published: March 13, 2026

Last Updated: July 21, 2026

July 21, 2026 at 10:30 PM Updated

Summary

Microsoft Teams will detect and label external meeting assistant bots attempting to join meetings, giving organizers approval and removal controls. A new admin policy will manage bot handling. Rollout starts mid-May 2026, completing mid-July 2026, with detection enabled by default to enhance meeting security and compliance.

New

Last Updated Date

2026-06-29T16:09:07.857Z

New

2026-07-21T18:33:15.970Z

Body Content

Updated June 29, 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 <a href="https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=558107" target="_blank">558107</a>.[When this will happen]<ul><li>Targeted Release: We will begin rolling out in mid-May 2026 and expect to complete by early June 2026.</li><li>General Availability (Worldwide): We will begin rolling out in early June 2026 and expect to complete by mid-July 2026 (previously mid-June).</li><li>General Availability (GCC): We will begin rolling out in early June 2026 and expect to complete by mid-July 2026 (previously mid-June).</li></ul>[How this will affect your organization]Who is affected<ul><li>All organizations using Microsoft Teams meetings, including GCC tenants</li><li>Meeting organizers and Teams administrators</li></ul>What will happen<ul><li>Teams will detect external meeting bots as they attempt to join meetings hosted by your organization.</li><li>When detected, bots will be clearly labeled in the meeting lobby experience.<ul><li>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.</li></ul></li><li>Organizers will be able to:<ul><li>approve or deny detected bots from the meeting lobby.</li><li>see clearly which participants have been identified as bots.</li><li>remove detected bots during the meeting if necessary.</li></ul></li><li>These organizer controls are designed to help ensure that bot participation in meetings is an intentional and informed decision.</li><li>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.</li><li>Bot detection will be enabled by default for all tenants.</li><li>Teams will continue improving detection accuracy; however, some bots may not be detected in all scenarios.</li></ul><img src="https://cxcs.microsoft.net/static/public/messagecenter/neutral/d26db94f-4c29-47b4-be0b-b0ba6dd55c11/be8d0b8cc99c17858107b52e66401f803ffbfbd2.png" style="width: 400px;" alt="user settings"><img src="https://cxcs.microsoft.net/static/public/messagecenter/neutral/f0d137a6-2ac7-4f55-b61e-2290f762d10d/3f0e1e0c229c7d44a5fd74cd9d13157ab3d38378.png" style="width: 400px;" alt="user settings">[What you can do to prepare]No action is required at this time.However, we recommend that Teams admins:<ul><li>Review the new meeting policy in the Teams admin center once it becomes available.</li><li>Keep the default setting, which requires organizers to approve detected bots before they join meetings (recommended).</li><li>Choose a stricter or more permissive option based on your organization’s collaboration and compliance requirements.</li><li>Inform meeting organizers that they may see new indicators and approval prompts when detected bots attempt to join meetings.</li><li>Update internal helpdesk or governance documentation if your organization documents meeting join or lobby controls behavior.</li><li>Monitor future Message center updates for expanded administrative controls.</li></ul>[Compliance considerations]<table class="table table-bordered"><tbody><tr><td>Question</td><td>Answer</td></tr><tr><td>Does the change introduce or significantly modify AI/ML or agent capabilities that interact with or provide access to your data?</td><td>Yes. This change introduces detection logic that analyzes meeting join metadata to identify external automated bots attempting to join meetings.</td></tr><tr><td>Does the change provide a new way of communicating between users, tenants, or subscriptions?</td><td>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.</td></tr><tr><td>Does the change include an admin control, and can it be controlled through Entra ID group membership?</td><td>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.</td></tr></tbody></table>

New

Updated July 20, 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 <a href="https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=558107" rel="noopener noreferrer" target="_blank">558107</a>.[When this will happen]<ol><li data-list="bullet">Targeted Release: We will begin rolling out in mid-May 2026 and expect to complete by early June 2026.</li><li data-list="bullet">General Availability (Worldwide): We will begin rolling out in early June 2026 and expect to complete by early August 2026 (previously mid-July).</li><li data-list="bullet">General Availability (GCC): We will begin rolling out in early June 2026 and expect to complete by early August 2026 (previously mid-July).</li></ol>[How this will affect your organization]Who is affected<ol><li data-list="bullet">All organizations using Microsoft Teams meetings, including GCC tenants</li><li data-list="bullet">Meeting organizers and Teams administrators</li></ol>What will happen<ol><li data-list="bullet">Teams will detect external meeting bots as they attempt to join meetings hosted by your organization.</li><li data-list="bullet">When detected, bots will be clearly labeled in the meeting lobby experience.</li><li data-list="bullet"> </li><li data-list="bullet" class="ql-indent-1">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.</li><li data-list="bullet">Organizers will be able to:</li><li data-list="bullet" class="ql-indent-1">approve or deny detected bots from the meeting lobby.</li><li data-list="bullet" class="ql-indent-1">see clearly which participants have been identified as bots.</li><li data-list="bullet" class="ql-indent-1">remove detected bots during the meeting if necessary.</li><li data-list="bullet">These organizer controls are designed to help ensure that bot participation in meetings is an intentional and informed decision.</li><li data-list="bullet">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.</li><li data-list="bullet">Bot detection will be enabled by default for all tenants.</li><li data-list="bullet">Teams will continue improving detection accuracy; however, some bots may not be detected in all scenarios.</li></ol><img src="https://cxcs.microsoft.net/static/public/messagecenter/neutral/d26db94f-4c29-47b4-be0b-b0ba6dd55c11/be8d0b8cc99c17858107b52e66401f803ffbfbd2.png" alt="user settings"><img src="https://cxcs.microsoft.net/static/public/messagecenter/neutral/f0d137a6-2ac7-4f55-b61e-2290f762d10d/3f0e1e0c229c7d44a5fd74cd9d13157ab3d38378.png" alt="user settings">[What you can do to prepare]No action is required at this time.However, we recommend that Teams admins:<ol><li data-list="bullet">Review the new meeting policy in the Teams admin center once it becomes available.</li><li data-list="bullet">Keep the default setting, which requires organizers to approve detected bots before they join meetings (recommended).</li><li data-list="bullet">Choose a stricter or more permissive option based on your organization’s collaboration and compliance requirements.</li><li data-list="bullet">Inform meeting organizers that they may see new indicators and approval prompts when detected bots attempt to join meetings.</li><li data-list="bullet">Update internal helpdesk or governance documentation if your organization documents meeting join or lobby controls behavior.</li><li data-list="bullet">Monitor future Message center updates for expanded administrative controls.</li></ol>[Compliance considerations]<table><tbody><tr><td data-row="row-mruzo7ix-90">Question</td><td data-row="row-mruzo7ix-90">Answer</td></tr><tr><td data-row="row-mruzo7ix-91">Does the change introduce or significantly modify AI/ML or agent capabilities that interact with or provide access to your data?</td><td data-row="row-mruzo7ix-91">Yes. This change introduces detection logic that analyzes meeting join metadata to identify external automated bots attempting to join meetings.</td></tr><tr><td data-row="row-mruzo7ix-92">Does the change provide a new way of communicating between users, tenants, or subscriptions?</td><td data-row="row-mruzo7ix-92">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.</td></tr><tr><td data-row="row-mruzo7ix-93">Does the change include an admin control, and can it be controlled through Entra ID group membership?</td><td data-row="row-mruzo7ix-93">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.</td></tr></tbody></table>

June 29, 2026 at 6:30 PM Updated

Title

Microsoft Teams: Identify external bots joining your Teams meetings

New

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

Summary

Microsoft Teams will detect and label external meeting assistant bots joining meetings, giving organizers control to approve, deny, or remove them. A new admin policy will manage bot handling, with detection enabled by default starting mid-May to mid-June 2026. This enhances security and compliance visibility.

New

Last Updated Date

2026-03-13T22:52:43.807Z

New

2026-06-29T16:09:07.857Z

Tags

New feature,User impact,Admin impact

New

Updated message,New feature,User impact,Admin impact

Body Content

[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 <a href="https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=558107" target="_blank">558107</a>.[When this will happen]<ul><li>Targeted Release: We will begin rolling out in mid-May 2026 and expect to complete by early June 2026.</li><li>General Availability (Worldwide): We will begin rolling out in early June 2026 and expect to complete by mid-June 2026.</li><li>General Availability (GCC): We will begin rolling out in early June 2026 and expect to complete by mid-June 2026.</li></ul>[How this will affect your organization]Who is affected<ul><li>All organizations using Microsoft Teams meetings, including GCC tenants</li><li>Meeting organizers and Teams administrators</li></ul>What will happen<ul><li>Teams will detect external meeting bots as they attempt to join meetings hosted by your organization.</li><li>When detected, bots will be clearly labeled in the meeting lobby experience.<ul><li>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.</li></ul></li><li>Organizers will be able to:<ul><li>approve or deny detected bots from the meeting lobby.</li><li>see clearly which participants have been identified as bots.</li><li>remove detected bots during the meeting if necessary.</li></ul></li><li>These organizer controls are designed to help ensure that bot participation in meetings is an intentional and informed decision.</li><li>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.</li><li>Bot detection will be enabled by default for all tenants.</li><li>Teams will continue improving detection accuracy; however, some bots may not be detected in all scenarios.</li></ul><img src="https://cxcs.microsoft.net/static/public/messagecenter/neutral/d26db94f-4c29-47b4-be0b-b0ba6dd55c11/be8d0b8cc99c17858107b52e66401f803ffbfbd2.png" style="width: 400px;" alt="user settings"><img src="https://cxcs.microsoft.net/static/public/messagecenter/neutral/f0d137a6-2ac7-4f55-b61e-2290f762d10d/3f0e1e0c229c7d44a5fd74cd9d13157ab3d38378.png" style="width: 400px;" alt="user settings">[What you can do to prepare]No action is required at this time.However, we recommend that Teams admins:<ul><li>Review the new meeting policy in the Teams admin center once it becomes available.</li><li>Keep the default setting, which requires organizers to approve detected bots before they join meetings (recommended).</li><li>Choose a stricter or more permissive option based on your organization’s collaboration and compliance requirements.</li><li>Inform meeting organizers that they may see new indicators and approval prompts when detected bots attempt to join meetings.</li><li>Update internal helpdesk or governance documentation if your organization documents meeting join or lobby controls behavior.</li><li>Monitor future Message center updates for expanded administrative controls.</li></ul>[Compliance considerations]<table class="table table-bordered"><tbody><tr><td>Question</td><td>Answer</td></tr><tr><td>Does the change introduce or significantly modify AI/ML or agent capabilities that interact with or provide access to your data?</td><td>Yes. This change introduces detection logic that analyzes meeting join metadata to identify external automated bots attempting to join meetings.</td></tr><tr><td>Does the change provide a new way of communicating between users, tenants, or subscriptions?</td><td>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.</td></tr><tr><td>Does the change include an admin control, and can it be controlled through Entra ID group membership?</td><td>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.</td></tr></tbody></table>

New

Never Miss a Microsoft 365 Update

Join thousands of IT professionals who rely on DeltaPulse for real-time Microsoft 365 change intelligence, automated notifications, and community insights.

Explore Dashboard Sign Up Free