Industry · 10 min read
Microsoft Teams 2026 Bot Ban: A Complete Admin Guide
Starting in mid-2026, Microsoft Teams begins flagging third-party meeting bots as "Suspected threats" in the meeting lobby. This isn't a rumor — it's an enforcement of policies Microsoft has been signaling since 2024. By the end of 2026, IT admins will be able to block third-party bots entirely at the tenant level. If your organization uses an AI notetaker that joins meetings as a bot — Otter, Fireflies, Fathom, TeamsMaestro, and most other tools fall into this category — your users may experience disruption starting Q3 2026. This guide covers what's actually changing, what tools are affected, and what IT teams should do now to avoid scrambling later.
What Microsoft is actually changing
Microsoft is rolling out three policy changes through 2026:
1. Bot detection in meeting lobbies (mid-2026). Teams will identify accounts that exhibit bot-like behavior — joining many meetings, having no recent human activity, accounts created by SaaS vendors — and flag them with a "Suspected threat" label. Hosts will see warnings before admitting these participants.
2. Tenant-level bot blocking (Q3 2026). A new Teams Admin Center policy will let admins block flagged bot accounts automatically. Once enabled, bots can't even reach the lobby.
3. Mandatory bot identification (late 2026). All legitimate Bot Framework applications will need to clearly identify as bots. Attempts to disguise bots as human participants will result in tenant-level blocks.
Which tools are affected?
Any tool that joins Microsoft Teams meetings as a participant is affected. This includes:
Fireflies.ai — joins as "Fireflies.ai Notetaker" or similar. Bot-based. Otter.ai — joins as "Otter.ai" participant. Bot-based. Fathom — joins as a meeting participant. Bot-based. TeamsMaestro — joins meetings via bot. Bot-based. Gong — joins as a recording bot. Bot-based. Chorus.ai (ZoomInfo) — joins as a participant. Bot-based.
All of these tools rely on joining the meeting to capture audio. When Microsoft blocks their accounts from the lobby, they stop working entirely.
For a deeper technical analysis, see our Graph API vs. bot frameworks comparison.
Which tools are NOT affected?
Tools that use the Microsoft Graph API to read transcripts after the meeting ends are not affected. These tools never join the meeting as a participant.
CallScrib — reads transcripts via Microsoft Graph API. No bot. Not affected. Microsoft Copilot — built into Teams. Not affected.
Desktop-based tools that capture audio locally (like Granola) are also unaffected, since they don't join the meeting as a participant.
What IT admins should do now
1. Audit your current tools. List every third-party tool that connects to Microsoft Teams meetings. Check whether each tool joins as a participant (bot-based) or reads data via the Graph API (API-native).
2. Plan migration for bot-based tools. If you're using Fireflies, Otter, Fathom, or similar, start evaluating Graph API-based alternatives now. Don't wait for the ban to take effect.
3. Enable transcription. Graph API-based tools like CallScrib require meeting transcription to be enabled in the Teams Admin Center. Turn it on now so there's no gap when you switch.
4. Review tenant bot policies. Check your current meeting policies in the Teams Admin Center. Understand which external participants are currently allowed and what changes when the new bot detection rolls out.
5. Communicate to users. Let your users know that bot-based notetakers will be disrupted. Provide them with an approved alternative before the ban takes effect.
Timeline
Q2 2026 (now): Microsoft begins rolling out bot detection in preview. Some tenants may see "Suspected threat" warnings.
Q3 2026: Bot detection GA. Tenant-level blocking policy available in Teams Admin Center. Bot-based notetakers start experiencing disruption.
Q4 2026: Mandatory bot identification enforced. Disguised bots blocked at scale. IT admins can auto-reject all flagged participants.
2027: Expected expansion to other M365 meeting surfaces.
The case for switching early
Waiting until the ban takes effect means your users lose meeting notes with no replacement. Switching now means:
No disruption. Users keep getting meeting summaries through the transition. Admin peace of mind. No unknown service principals in your tenant. Cost savings. Most bot-based tools are 3-5x more expensive than Graph API alternatives. CallScrib is $5/user/month vs $19-30/month for bot-based tools.
See our best AI notetaker comparison for Teams for a full feature breakdown.
The AI notetaker built for Microsoft Teams. No bot in your meetings. 7 meetings per month free, no credit card.
Frequently Asked Questions
When does the Microsoft Teams bot ban take effect?
Bot detection begins mid-2026, with tenant-level blocking available in Q3 2026 and mandatory bot identification by late 2026. IT admins should start planning now.
Will Microsoft Copilot be affected by the bot ban?
No. Copilot is built into Microsoft Teams and is not a third-party bot. It is not affected by the bot detection policies.
Is CallScrib affected by the bot ban?
No. CallScrib uses the Microsoft Graph API to read meeting transcripts after the call ends. It never joins meetings as a participant and is not affected by bot detection.
What should I use instead of a bot-based notetaker?
Use a Graph API-based tool like CallScrib that reads transcripts without joining meetings. Enable meeting transcription in your Teams Admin Center first.
Do I need to enable transcription for Graph API tools to work?
Yes. Graph API-based tools read the transcripts that Teams generates. Your M365 admin needs to enable transcription in the Teams Admin Center under Meeting policies.
