MC1262588 – Microsoft Teams: Retirement of CAPTCHA for meeting join

Microsoft Teams logo

check before: 2026-05-01

Product:

Entra, Microsoft 365 admin center, Teams

Platform:

Android, iOS, Linux, Mac, Online, US Instances, Windows Desktop, World tenant

Status:

In development

Change type:

User impact, Retirement

Details:

Summary:
Microsoft Teams will retire CAPTCHA for meeting joins by August 2026, replacing it with a default-on bot detection feature that requires organizer approval for bots. This ensures continuous bot protection without join friction. Tenant admins and organizers should review new policies but no immediate action is needed.

Details:
[Introduction]
Microsoft Teams is retiring CAPTCHA for meeting join to improve accessibility, reduce join friction, and modernize protections against automated participants. This change follows the release of a new, default-on capability that detects external meeting assistant bots and provides organizers with increased visibility and control during the meeting join process, as previously announced in Message Center post MC1251206 (Microsoft 365 Roadmap ID 558107).
To ensure a smooth transition:
The new bot detection capability will be released and available to customers before CAPTCHA deprecation occurs.
There will be no gap where meetings are left without baseline bot protection.
CAPTCHA will be removed from meeting join flows and admin surfaces only after the new capability is fully in place.
[When this will happen]
Early May 2026: The Require verification by participants (CAPTCHA) policy will be locked and can no longer be enabled.
Late July 2026: CAPTCHA policy removed from PowerShell.
Late August 2026: CAPTCHA policy removed from the Teams Admin Center UI.
Note: Dates are subject to change based on the release of bot identification (MC1251206/Roadmap ID 558107).

Change Category:
XXXXXXX ... free basic plan only

Scope:
XXXXXXX ... free basic plan only

Release Phase:
General Availability, Targeted Release

Created:
2026-03-27

updated:
2026-04-17

Task Type

XXXXXXX ... free basic plan only

Docu to Check

XXXXXXX ... free basic plan only

MS How does it affect me

XXXXXXX ... free basic plan only

MS Preperations

XXXXXXX ... free basic plan only

MS Urgency

XXXXXXX ... free basic plan only

MS workload name

XXXXXXX ... free basic plan only

linked item details

XXXXXXX ... free basic plan only

summary for non-techies**

XXXXXXX ... free basic plan only

Direct effects for Operations**

Removal of CAPTCHA for meeting joins
Without proper preparation, users may experience confusion or frustration when attempting to join meetings, as they will no longer encounter CAPTCHA challenges, potentially leading to unauthorized bot access if not managed properly.
   - roles: Tenant Administrators, Meeting Organizers
   - references: https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=558107

Introduction of bot detection feature
If the new bot detection feature is not adequately communicated, users may not understand the new process for admitting bots, leading to delays in meeting starts and potential security risks.
   - roles: Tenant Administrators, Meeting Organizers
   - references: https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=558107

Changes in meeting policy management
Failure to prepare for the new meeting policy could result in mismanagement of bot approvals, leading to unauthorized access to sensitive meetings and data breaches.
   - roles: Tenant Administrators, Meeting Organizers
   - references: https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=558107

User experience during meeting joins
Users may face a learning curve with the new bot approval process, which could disrupt the flow of meetings and lead to dissatisfaction if not properly trained.
   - roles: Meeting Organizers, End Users
   - references: https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=558107

Compliance and security risks
Without preparation, organizations may inadvertently allow unauthorized bots into meetings, leading to compliance violations and potential data leaks.
   - roles: Tenant Administrators, Compliance Officers
   - references: https://www.microsoft.com/microsoft-365/roadmap?filters=&searchterms=558107

Configutation Options**

XXXXXXX ... paid membership only

Potentional Risks**

XXXXXXX ... paid membership only

IT Security**

XXXXXXX ... paid membership only

explanation for non-techies**

XXXXXXX ... free basic plan only

** AI generated content. This information must be reviewed before use.

a free basic plan is required to see more details. Sign up here


A cloudsocut.one plan is required to see all the changed details. If you are already a customer, choose login.
If you are new to cloudscout.one please choose a plan.



Last updated 2 days ago ago

Leave a Reply

Share to MS Teams

Login to your account

Welcome Back, We Missed You!