Teams Puts AI Bots in the Lobby: Your Meetings Take Back Control

Microsoft Teams now detects external note-taking bots, holds them in the lobby and requires the organizer to approve them before they join. The behaviour is on by default, it is managed from the admin centre, and starting in August 2026 an administrator will be able to block detected bots automatically.

For a year or two now, a small note-taking robot has been letting itself into more and more Teams meetings. It carries the name of a familiar app, it records, it transcribes, and often nobody around the table really knows who let it in or where the data goes. Those automatic assistants (Otter.ai, Fireflies, Gong and a crowd of others) have become regulars on business calls, sometimes without half the participants knowing.

Microsoft has tightened the screws. The company rolled out a new protection in Teams that detects those external bots, holds them in the lobby and requires the organizer to confirm before they join the meeting. The full switch is planned for the end of July 2026, and an option to block those robots outright arrives in August. For a business in Trois-Rivières or the Mauricie that holds confidential meetings, this is good news worth a closer look.

1. What did Microsoft change in Teams?

The feature carries a clear name in the Teams admin centre: a policy called "Manage external bots and their access to meetings". When it is active, Teams analyzes participants using behavioural and infrastructure signals to spot robots. As soon as it detects one from outside your organization, it holds it in the lobby, flags it visually and asks the organizer to confirm before it joins.

The important detail: even in a meeting where you have allowed participants to bypass the lobby, a bot caught by this policy stays blocked until the organizer approves it. The rule for humans and the rule for robots are no longer the same.

• Automatic detection of external robots at the meeting door.
• Held in the lobby with a visual marker distinguishing them from real participants.
• Manual confirmation from the organizer required before admission.
• Adjustable scope: the policy can target the whole organization, certain groups or certain users.

2. Why do note-taking robots create a real problem?

An assistant that transcribes a meeting is convenient. The catch is what happens afterward. These tools capture everything said, send it to servers that are often located abroad, and sometimes feed the content of your discussions into artificial intelligence models. In a meeting where you are discussing a contract, an employee file, financial numbers or a client, that becomes a potential data leak.

In Quebec, the question is not only about good practice. Law 25 governs how personal information is collected and circulated. If a third-party robot records a meeting where clients or employees are named, with no clear consent and no idea where the data goes, your business is exposed. The problem is not the robot itself, but the fact that until now it walked in without anybody actually giving the green light.

• Recording and transcription of confidential discussions without explicit consent.
• Data hosted outside Quebec, sometimes outside Canada.
• Meeting content potentially reused to train AI models.
• No clear trace of who invited the robot or what it kept.

3. How does the protection work in practice?

Everything is driven from the Teams admin centre. An administrator assigns the policy to the whole organization, to one department or to a handful of people. By default, the behaviour Microsoft recommends is simple: detect the robots, send them to the lobby and require the organizer’s confirmation.

Microsoft also advises reserving the right to admit somebody from the lobby to organizers and co-organizers, so a participant does not let a robot in by accident. A "Do not detect bots" option exists for organizations that would rather let assistants in freely, but that is not the setting to favour if confidentiality matters to you.

The roadmap goes further. Starting in August 2026, an administrator will be able to choose among three behaviours: allow everything, require approval when a robot is detected (the default), or automatically block the robots that are caught. Microsoft then plans allow lists for approved tools, organization-wide blocking, and reports and audit logs on robot presence. If you want those settings configured correctly the first time, our managed IT services cover exactly this kind of hardening.

4. What does this change for your Quebec business?

If your teams use Teams for internal meetings or client calls, you want this setting active and scoped properly. It keeps a supplier, a partner or even a well-meaning employee from bringing a recording robot into a sensitive call. It also gives you a clear answer the day a client asks who is listening and who keeps the record.

Here is what we recommend doing now:

• Confirm the bot detection policy is active in your Teams admin centre.
• Limit the right to admit participants to organizers and co-organizers.
• Decide which note-taking tools are accepted, and which are not.
• Plan for the August 2026 change so you can choose between required approval and automatic blocking.
• Document all of it, to stay aligned with Law 25.

For a business in Trois-Rivières, the Mauricie or the Quebec City area with no full-time IT team, this kind of configuration is settled quickly with the right help. It is a good moment to tidy up your Teams settings while Microsoft rolls the feature out.

Frequently asked questions

Does this also block Microsoft 365 Copilot meeting notes?

No. Detection targets robots external to your organization, such as third-party note-taking assistants. Microsoft 365 internal tools, including Copilot, are not treated as external bots. Microsoft does plan to extend unified management of AI participants later on.

Do I have to do something, or is it automatic?

The protection arrives by default, but it deserves a check. You need to confirm it is active, decide who it applies to and restrict who can admit a participant from the lobby. Those choices are made in the Teams admin centre, not in the user application.

Are note-taking robots illegal in Quebec?

No, they are not illegal in themselves. The risk comes from recording personal information without clear consent and without knowing where the data goes. Law 25 asks you to govern that collection, and this new control is exactly what helps you do it.

Take back control of your meetings

This Teams update is a good example of a simple setting that protects your data with no ongoing effort once it is configured. If you are unsure where your Microsoft 365 environment stands, our team can review your policies, turn on the right protection and document it for compliance. Take a look at our managed IT services or write to us through the contact page to talk it over.