Industry · 6 min read
Why bot-based notetakers keep getting banned
A guest joins the meeting. They see a participant called "Otter Notetaker" and ask: who let that in? You're now spending the first ninety seconds of your call defending your tooling.
The three failure modes
This isn't a story about any one tool failing. It's the structure of the bot model itself. When your product joins a meeting as a participant, you're betting on consent, attention, and IT goodwill.
The host kicks the bot: External meetings are the worst case. Your salesperson hops on a discovery call with a prospect. The bot lands in the lobby. The prospect doesn't recognize the name. The first impression is now "this vendor records me by default."
The lobby blocks the bot: Many tenants are configured so external participants need explicit admission. Bots show up as external. Half the time, nobody's watching the lobby.
The admin bans the bot: An IT admin notices the bot service principal across hundreds of meetings, decides it's an unmanaged data flow, and blocks it via Conditional Access. Users don't know why their notes stopped showing up.
The Graph API alternative
Microsoft publishes APIs that grant tenant-scoped access to meeting transcripts and chat without anything joining the call as a participant. Admin grants the scopes once, and the data flows server-to-server. Nothing to admit. Nothing to ban. For a technical deep dive, see our Graph API vs. bot frameworks comparison.
The tradeoff: it's Teams-only. You can't use the Graph API approach for a Zoom meeting. So a multi-platform tool genuinely can't escape the bot question on every platform, but a Teams-native tool can.
What this means if you're choosing
If you're a Teams-first organization, prefer tools that capture via the Graph API. You'll save your salespeople the awkward bot-introduction moment, your admin the audit trail headaches, and your guests the "what's that thing?" question.
If you're multi-platform, bots are still the answer. But know what you're signing up for: ongoing effort whitelisting service accounts and educating users about consent.
Either way, the choice is between visible-and-flexible (bots) or invisible-and-narrow (API-native). Pick the one that matches how your team actually works.
The AI notetaker built for Microsoft Teams. No bot in your meetings. 7 meetings per month free, no credit card.
Frequently Asked Questions
Why are meeting bots getting banned?
IT admins block bots because they represent unmanaged data flows. Hosts boot them because external participants don't trust unfamiliar meeting joiners. Microsoft is also flagging third-party bots as "Suspected threats" starting mid-2026.
What is the alternative to bot-based notetakers?
The Microsoft Graph API allows tools like CallScrib to read meeting transcripts after the call ends without any bot joining. Admin grants permissions once, and the tool is invisible to participants.
Do bot bans affect all AI notetakers?
Only bot-based ones. Graph API-native tools like CallScrib are not affected because they never join the meeting as a participant.
