You can record a Microsoft Teams meeting on a Mac without a bot by capturing audio at the operating-system level — your microphone plus your Mac's system audio output — instead of asking Teams for it. Nothing joins the call, so there is nothing for Teams' bot detection to hold in the lobby, and it works even when you're a guest Teams won't let record.
Why can't you just use Teams' own recording?
Often you can't, because Teams recording is gated by tenant, licence, and role. Microsoft's support page lists who can start a recording: the organiser and people from the same organisation can; guests, anonymous attendees, and people from another organisation cannot. Both the organiser and the recorder need an eligible Microsoft 365 licence, and an admin must have recording turned on.
That rules out the most common reason to want a recording: you're the consultant, vendor, or candidate on someone else's Teams call. Even inside your own company, the recording isn't yours. It lands in the organiser's OneDrive or the channel's SharePoint, everyone gets a notification the moment it starts, and by default it is deleted on a timer — Microsoft documents a default expiration of 120 days, or 30 days on A1 licences (as of October 2026).
None of that is a flaw. Teams' recorder is built for the organisation's record of a meeting. Your own notes from a call you attend are a different problem.
Why are AI notetaker bots getting stuck in the Teams lobby?
Because Microsoft started detecting them. In 2026 Teams added bot detection for meetings, and the default policy setting — RequireApprovalWhenDetected — holds any detected external notetaker until an organiser lets it in. Microsoft's admin documentation says detected bots are:
"placed in the meeting lobby irrespective of the lobby configuration for the meeting."
— Microsoft Learn, "Manage external bots and their access to meetings"
The next step is already on the Microsoft 365 roadmap (ID 566201): an option for admins to automatically block all identified external bots, listed as rolling out from September 2026 on Mac, Windows, web, and mobile. With roughly 320 million monthly active users at Microsoft's last disclosure, Teams just became the largest platform where a bot-based notetaker may simply never get in.
Microsoft's stated reason is data leaving the tenant: bots "store meeting data in third-party systems outside of the organization's compliance boundaries." That's worth taking seriously even when you're not the admin — it is the same concern that makes a cloud notetaker's data policy worth reading.
How does botless Teams recording work on a Mac?
From your Mac's point of view, a Teams call is two audio streams: your microphone and the system audio output carrying everyone else. A botless recorder captures both locally. It never connects to the meeting, never appears in the participant list, and never passes through the join process Teams' bot detection inspects.
Since macOS 14.2, the clean way to get the second stream is Core Audio process taps — a first-class Apple API for capturing system or per-process audio with no virtual driver. That's why it works identically in the new Teams desktop app and in a browser tab. The full engineering picture is in how botless meeting recorders work on macOS.
Apple's own tools don't do this. QuickTime and Command-Shift-5 record only your microphone, so you get a recording of you talking to silence — the same trap we covered in the Zoom version of this guide.
Step by step: recording a Teams call with no bot
- Install a botless recorder that captures system audio on-device. Speechmark works this way; so do others, Granola among them (as of October 2026).
- Grant two macOS permissions, once: Microphone, and system-audio recording under System Settings → Privacy & Security → Screen & System Audio Recording. Teams is never asked.
- Join the Teams meeting normally — desktop app or browser, headphones are fine.
- Start recording from the menu bar. No lobby entry, no participant, nothing for an organiser to admit.
- Stop when the call ends. With an on-device tool, transcription and speaker separation run on the Mac and the transcript lands as a file on your disk.
The one hard prerequisite: process-tap apps need macOS 14.2 or later.
What this does not change: policy and consent
Teams' bot detection exists because organisations want to know what's capturing their meetings. A recorder Teams can't see doesn't make that interest go away — it makes it your responsibility.
Recording-consent law varies: some US states and many countries require every party to agree, and an invisible recorder changes none of it. If your employer or your client's contract prohibits recording, botless capture doesn't create an exception. The reasonable default is to say you're taking a recording for your notes and to stop if anyone objects. Botless is the right tool when bots are blocked, disruptive, or a data-leakage concern — not a way around a "no".
Where Teams' own recording is the better choice
- The organisation needs the record. Teams recordings sit in OneDrive and SharePoint under Microsoft Purview retention and eDiscovery. For regulated teams, that governance is the point.
- You need video or shared screens. Process taps capture audio only.
- You want consent built in. Teams notifies every participant when recording starts, and admins can require explicit consent. An OS-level recorder notifies nobody.
- You want Copilot recaps for the whole team. Microsoft 365 Copilot works on Teams' own transcripts; a local file isn't part of it.
- You're not on a Mac. Everything here is macOS-specific.
The bottom line
Teams' recorder belongs to the organiser's tenant, and Teams increasingly keeps third-party bots out. A botless recorder sidesteps both by reading the audio your Mac already plays — which is why it works as a guest and never sits in a lobby.
Whether it's also private depends on what happens after capture. Speechmark keeps the whole chain on the Mac — capture, transcription, speaker identification, summaries — and keeps the audio as your file. It's a one-time purchase ($79, currently $49 for founding users), not a subscription.