Teams Meetings to Block Third-Party Recording Bots

Stop Third-Party Recording Bots Generating Transcription and AI Summaries

Message center notification MC1251206 (13 March 2026, Microsoft 365 roadmap item 558107) is very interesting. It announces the introduction of third-party recording bot detection and blocking in Teams meetings. According to Microsoft, a profusion of third-party “meeting assistant bots” that join meetings and use the audio stream to transcribe and summarize meetings are in increasing use.

Microsoft plans to deploy the feature to targeted release tenants starting in mid-May 2026. General availability should follow in early June 2026 to complete by mid-June. GCC will also get the feature in the same timeframe. Bot detection becomes part of the core Teams infrastructure and will be enabled for all tenants.

The Preference for Native Transcription

Naturally, Microsoft would like you to use the transcription feature built into Teams to create transcripts of Teams meetings. Their point is that use of native transcription is clearly flagged through warning notices shown to meeting participants. Meeting transcripts are stored in OneDrive for Business in the MP4 files generated for Teams recordings (with or without video) and available for eDiscovery. If you want summarization (meeting notes and action items), Copilot for Teams can do that, and its meeting notes are available for compliance purposes too. Such are the benefits of using integrated features within an ecosystem like Microsoft 365.

By comparison, Microsoft says that some third-party “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.” They have a point. I have joined many Teams meetings, including some in the Microsoft tenant, where an odd participant shows up that’s been added by a human participant.

Detecting the Presence of Third-Party Recording Bots

The new capability allows Teams to check participants as they attempt to join meetings to detect the presence of bots. If meeting organizers are happy for people to use personal bots to capture details of what goes on and store that information outside of your tenant, they can admit the bot from the meeting lobby to join the meeting (Figure 1) and do its stuff. I don’t think this is a sensible idea.

Teams detects the presence of a third-party recording bot in a meeting (image credit: Microsoft)
Figure 1: Teams detects the presence of a third-party recording bot in a meeting (image credit: Microsoft)

Microsoft admits that bot detection is not perfect and might not pick up every third-party recording bot that’s currently available. However, over time they reckon that customer reports and their own research will allow the detection algorithm to become more accurate and dependable. And besides, if meeting organizers notice strange participants, they can always eject those participants to protect the information discussed in the meeting.

Administrative Control

Microsoft says that a new meeting policy will be available in the Teams admin center to allow administrators to control how bot detection works. I believe this to mean that Microsoft plans to add a new control to the Teams meeting policy that will have values such as disable bot detection and require approval to admit bots. The policy is not yet available and V7.6 of the Teams PowerShell module doesn’t show a setting for the Set-CsTeamsMeetingPolicy cmdlet either. Microsoft says that they plan to provide more granular controls in the future.

A Question of Balance

Cynics will say that blocking third-party recording bots is a blatant attempt by Microsoft to protect their ability to sell Microsoft 365 Copilot licenses to the 96% of the 450 million-plus installed base that haven’t yet bought Microsoft 365 Copilot. Microsoft disagrees and points to the obvious compliance issues that arise when potentially confidential data is taken outside the tenant to be processed to generate meeting notes and summaries.

On balance, I think Microsoft is right to introduce third-party recording bot detection and to make the feature part of the base Teams software. If tenants want to allow the use of third-party recording bots, they can update their Teams meeting policies to disable the block.


Learn about managing Teams and the rest of the Microsoft 365 ecosystem by subscribing to the Office 365 for IT Pros eBook. Use our experience to understand what’s important and how best to protect your tenant.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.