Microsoft has rolled out a new bot protection capability in Microsoft Teams that gives IT administrators and meeting organizers greater control over external bots attempting to join meetings, a move designed to address growing privacy and security concerns around AI-powered meeting tools.<\/p>\n
As AI note-taking bots have become increasingly embedded in the workplace, a parallel problem has emerged: bots joining meetings without participants\u2019 knowledge or intent.<\/p>\n
Users integrating third-party services have reported that the associated bots continue to auto-join future meetings, creating unintended surveillance risks, particularly during discussions involving sensitive or confidential information.<\/p>\n
Recently, Microsoft has rolled out a new workplace presence feature<\/a> in\u00a0Microsoft Teams\u00a0that automatically updates a user\u2019s work location when they connect to their organization\u2019s Wi-Fi network.<\/p>\n Microsoft has introduced a dedicated admin policy,\u00a0\u201cManage external bots and their access to meetings,\u201d\u00a0now available in the Teams Admin Center. The policy can be assigned granularly to individual users or specific groups. Admins have two configuration options:<\/p>\n Bot detection is enabled by default for all tenants, meaning organizations receive baseline protection without requiring any manual configuration.<\/p>\n Microsoft has enhanced Teams\u2019 ability<\/a> to differentiate bots from human participants by leveraging a combination of behavioral and infrastructure signals to improve detection accuracy.<\/p>\n In parallel, Microsoft is rolling out a Teams Bot Identification Program, a registration pathway for Independent Software Vendors (ISVs) that build meeting experiences on Teams.<\/p>\n Registered bot providers can embed a self-identification marker in their join requests, which Teams can recognize and classify the bot as a known, verified participant rather than a suspected threat.<\/p>\n When the policy is active, detected bots are placed in the meeting lobby and visually distinguished from human attendees. Participants waiting in the lobby are now organized into two distinct categories visible to organizers:<\/p>\n This lobby segmentation enables organizers to quickly triage who is waiting to join and identify potential risks at a glance, eliminating the need to manually scan a full participant list.<\/p>\n Microsoft has also implemented deliberate friction points to prevent accidental bot admissions. There is no one-click Admit option available for identified bots. Organizers receive confirmation prompts when admitting participants that include bots, and warning dialogs appear when selecting Admit All if bots are included in the queue.<\/p>\n This new bot protection framework also marks the retirement of Teams\u2019 existing CAPTCHA verification system, with the CAPTCHA policy set to be fully removed from the Teams Admin Center by late August 2026.<\/p>\n Microsoft has indicated it will continue expanding the bot management ecosystem, with upcoming capabilities including:<\/p>\n The feature reached general availability globally in early-to-mid June 2026, with GCC environments receiving the rollout on the same timeline.<\/p>\n Microsoft recommends setting the meeting option \u201cWho can admit from lobby\u201d to organizers and co-organizers only, ensuring that no unintended participant can inadvertently admit a bot on behalf of the meeting host.<\/p>\n \u00a0Strengthen Your SOC by Accelerating Threat Detection & Rapid Investigations.\u00a0-> Integrate ANY.RUN With Your SOC <\/a>Now<\/a><\/strong>.<\/strong><\/p>\n The post Microsoft Teams\u2019 New Feature Blocks Bots from Joining Meetings<\/a> appeared first on Cyber Security News<\/a>.<\/p>\n<\/div>\nNew Admin Policy in Teams Admin Center<\/strong><\/h2>\n
![\"\"](\"https:\/\/i0.wp.com\/blogger.googleusercontent.com\/img\/b\/R29vZ2xl\/AVvXsEjuNH9h5h3MJUie5GyK1EMo78RaDp1iRoxodGM9swkE7J8Vq-1YKFGeAhaai258CJVE4c1bnXqfgGKtAiw1j1RyfFOIIvGMxCPk5s4loScAFfRRgISjs_VehF7bbGpSgQ28gvcec_UjWl8oNKhHL_3fETZJMRPAx1dJy4MmOzPI6J53JT1g0epFxbM54qoj\/s16000\/Microsoft%2520Teams%2520Bot%2520Protection2.webp?ssl=1\")
\n
\n
![\"\"](\"https:\/\/i0.wp.com\/blogger.googleusercontent.com\/img\/b\/R29vZ2xl\/AVvXsEgIIRzIpgfcIPCI_2u9__JrWbh3NDmNpcFS_m8QsIYL6DQi6EVeCQZTT3aavBEUfwIlxikxw_9id4QiakU0qJEWWBP4BWu7vwBg6WBo353xjbYUZ3LtimgCpkVUjTv80khbtEo5gMvOCwp3d7C9bI6eQiuMorMkLxVhQv7kVj141Cxk37u7ymiSAV8RcZf8\/w640-h360\/Microsoft%2520Teams%2520Bot%2520Protection1.webp?ssl=1\")
\n