How to record a Microsoft Teams meeting on a Mac
If the Record button is missing, it is almost never a bug and almost never your Mac. Teams recording is a licence and an admin policy, and Microsoft’s own documentation says who is excluded.
- Microsoft’s own table settles who may press Record — “Person from another org or company: No”, “Guest: No”, “Anonymous: No”. If you were invited from outside, the button was never yours to find.
- Inside the organisation it still takes a licence plus an admin policy. Microsoft names “Office 365 Enterprise E1, E3, E5, F3, A1, A3, A5, M365 Business, Business Premium, or Business Essentials”, and one PowerShell parameter —
-AllowCloudRecording— turns it off for everybody. - A Teams recording is stored in the organiser’s OneDrive for private meetings and SharePoint for channel meetings, and “guests and external attendees can view the recording only if the recording is explicitly shared with them”.
- Recording your Mac’s own audio ignores every one of those gates, because Teams is not part of it. macOS will not do it with built-in apps: Apple’s screen-recording controls offer a microphone or “None”, and nothing else.
- Non-obvious gate worth knowing before you blame IT: “When organizers turn off Microsoft 365 Copilot in Teams meetings and events, recording and transcription are also turned off.”
Teams recording is not a feature you have. It is a feature your employer’s Microsoft 365 tenant either grants you or doesn’t, and Microsoft is unusually direct about the exclusions.
So the first useful thing to know is whether the button is missing or withheld. Microsoft’s troubleshooting page tells you how to find out: hover the lock icon on the Start recording button and Teams shows the reason. Then either you can fix it in ninety seconds, or you cannot fix it at all and should record your own Mac instead.
Four reasons the Record button isn’t there
You are not in the organisation. Microsoft publishes a table of who may start and stop a recording, and three rows of it are the reason most people are reading this page:
| Type of user | Can start recording? | Can stop recording? |
|---|---|---|
| Meeting organizer | Yes | Yes |
| Person from same org | Yes | Yes |
| Person from another org or company | No | No |
| Guest | No | No |
| Anonymous | No | No |
There is no setting behind this. If you joined a client’s Teams meeting from your own tenant, or by link, no amount of being promoted to presenter will produce a Record button, because the constraint is which directory you belong to.
Your admin's policy has it off. Recording lives in a Teams meeting policy that an admin flips in the admin centre, or in one line of PowerShell: Set-CsTeamsMeetingPolicy -Identity Global -AllowCloudRecording $false. Microsoft’s own phrasing is that “Both the organizer and recording initiator need to have recording permissions” — so an organiser without the permission means nobody in that meeting has a Record button, whatever their own policy says.
Licence. Microsoft lists it as: “Both the meeting organizer and recorder must have one of the following licenses: Office 365 Enterprise E1, E3, E5, F3, A1, A3, A5, M365 Business, Business Premium, or Business Essentials.” In practice your admin knows which of those you have, and you are not going to change it before this afternoon’s call.
Copilot is off. This one catches people who assume the two are unrelated: “When organizers turn off Microsoft 365 Copilot in Teams meetings and events, recording and transcription are also turned off.” An organiser tightening a meeting’s AI settings can remove recording as a side effect and have no idea they did.
Worth knowing regardless of which reason applies: even a successful Teams recording is not yours. It “gets uploaded to the meeting organizer’s OneDrive (private meetings) or SharePoint (channel meetings)", and Microsoft is explicit that “guests and external attendees can view the recording only if the recording is explicitly shared with them”. An admin can also route channel recordings into a Recordings\View only folder where members can watch but not download.
Your Mac won’t do it out of the box either
The reflex at this point is a screen recording. It will not capture the meeting.
macOS treats your microphone and your Mac’s audio output as two different things with different privacy rules, and Apple’s own apps only ever ask for the first. Apple’s documentation for the screen-recording controls describes exactly one audio choice: “Below Microphone, select the microphone you want to use so that a checkmark appears next to it. To turn off the microphone, select None.” No system-audio option is listed anywhere on that page. QuickTime’s audio recorder is the same, and Voice Memos is the same.
So ⌘⇧5 through a Teams call gives you your own voice and silence where your colleagues were. People usually discover this after the meeting they needed.
The capability exists in macOS — Apple’s privacy documentation describes granting an app “both your screen and audio, or just your audio” — it is just reserved for apps that ask for it.
Route 1 — get it turned on properly
Worth one attempt, because it is the cleanest outcome when it works. Ask the organiser to record, or to give you recording rights in the meeting options; if the block is the policy rather than the meeting, ask your admin whether recording is off deliberately or off by inheritance from the Global policy. Plenty of tenants have it off because nobody ever turned it on.
This route dies immediately if you are external to the organiser’s tenant. Nothing on your side is negotiable there.
Route 2 — a virtual audio device
Install BlackHole (free) or Loopback, build a Multi-Output Device in Audio MIDI Setup so sound reaches your headphones and the virtual device, set that as your Mac’s output, then record the virtual device as an input. Full walkthrough here.
It works, and it costs you something: your Mac’s audio output is now a contraption you have to remember to undo, keyboard volume control stops working while a Multi-Output Device is selected, and you and the call land in a single mixed track that nothing afterwards can reliably attribute to a person. Getting your microphone in as well means stacking an Aggregate Device on top of the arrangement.
Route 3 — an app that holds the system-audio permission
Narada asks macOS for Microphone and System Audio Recording and reads both streams where they already are. Your output device never changes, there is no driver, and no Screen Recording permission is involved — it does not record your screen.
Because the two streams are opened separately they stay separate. Your lines are attributed to you because they came from your own microphone; the call’s audio is split into distinct voices labelled Speaker 1, Speaker 2 and so on. The app does not know your colleagues' names and does not invent them.
Transcription runs on the Mac through Parakeet TDT v3, in 25 European languages. Accuracy is not one number and anyone quoting you one is guessing — the model’s published word error rates on FLEURS run from about 4% on Italian to about 37% on Greek, so a Dutch or Polish or Ukrainian call comes back clean and a Greek or Latvian one will need editing.
If the meeting is in your calendar, Narada can start on its own when it begins — Outlook, Google Calendar and the macOS Calendar all work as sources. That is opt-in rather than the out-of-the-box default: the shipping default is to ask, and when auto-record is enabled it arms up to a minute before the scheduled start and runs a three-second countdown you can cancel. Requires macOS 15.6 or later. The recorder itself, including transcription and speaker separation, is free; Pro AI summaries are $6.99/month or $69.99/year with a 3-day trial, and there is an on-device AI mode that costs nothing and needs no account, on Apple Silicon with a one-time 3 GB or 7 GB model download and lighter notes than the cloud.
Route 4 — a bot notetaker
Otter’s assistant, Fireflies, Fathom and the rest join your Teams meeting as a participant and record on their servers. You get transcription and CRM integrations without touching your audio settings; in exchange there is a visible extra attendee and the audio is uploaded to a vendor.
Note also that Microsoft treats third-party recording as a policy matter in its own right: “External participants can’t record meetings except when it’s a Teams third-party compliance recording”, and organisers are notified and can eject the participant when that happens.
Which route
| Situation | Best route |
|---|---|
| You organise the meeting and your tenant allows recording | Teams' own recording |
| You are a guest or from another org — no Record button will ever appear | Record your Mac’s audio |
| Admin has recording off and won’t change it | Record your Mac’s audio, after checking the policy question below |
| You want notes on every call without asking a rotating cast of organisers | An app with the system-audio permission |
| Notes pushed into a CRM for a whole team | A bot notetaker |
| Raw audio to edit | Virtual audio device |
The conversation to have with IT, not around it
If your admin has switched Teams recording off, they did it for a reason, and a local recorder does not make that reason disappear. Recording a call your employer’s policy forbids you to record is a problem whichever tool you use.
What a local recorder does change is the objection that usually sits underneath the policy: that a copy of the meeting ends up on somebody else’s servers. With Narada the audio file is on your Mac, in a folder you pick, and the transcription happens on the Mac too — no vendor gets the recording. Two honest qualifications, because an IT reviewer will find both. The files are deliberately unencrypted, so they inherit whatever disk encryption and backup policy your Mac already has and nothing more. And in the cloud AI modes the transcript text is sent to OpenAI after you explicitly consent to it. The audio never leaves in any mode, and in Recorder-only or on-device mode no part of the meeting leaves the Mac — the network traffic that remains is calendar sync, subscription checks, and a one-time model download if you switch on on-device AI.
That is a checkable answer to “where does this data go”. Bring it to IT before you need it.
Teams announces its recordings. Nothing announces yours.
When Teams records, “All meeting participants will receive a notification in their Teams desktop, web, or mobile app as soon as a meeting recording starts.” Some tenants go further — an admin can require participants to actively consent before a meeting can be recorded at all.
None of that machinery knows about a recorder running on your Mac. So the disclosure is yours to make, out loud, in the first thirty seconds. Recording law varies by country and by state and in some places turns on whether everyone consented rather than just you. Narada keeps a reminder on screen for the whole recording; it cannot make a recording lawful for you and it does not notify anyone on your behalf.
What you get afterwards
One folder per meeting, holding an .m4a file, the transcript as plain text with timestamps and speaker labels, and the summary as Markdown. Nothing proprietary, nothing to export.
One thing worth saying plainly, since it is the opposite of what recorder marketing usually claims: macOS audio capture can fail mid-recording. A device can be reshaped underneath a live capture, an overloaded audio subsystem can drop what it was handed. Narada compares each finished recording against what the capture actually submitted and marks it Incomplete, with a reason, when the numbers do not match — the microphone stopped early, the exported file is shorter than what was recorded, and so on. It cannot get the missing audio back. It can stop a recording that lost eight minutes from being handed to you as a complete meeting, which is the failure mode that actually costs people something.
Sources
- Microsoft Support, Record a meeting in Microsoft Teams — the who-can-record table, the licence list, and the participant-notification sentence. https://support.microsoft.com/en-us/office/record-a-meeting-in-microsoft-teams-34dfbe7f-b07d-4a27-b4c6-de62f1348c24
- Microsoft Support, I can't record a meeting in Microsoft Teams — anonymous/external users, attendee vs presenter, admin policy, organiser restrictions, and the Copilot dependency. https://support.microsoft.com/en-us/office/i-can-t-record-a-meeting-in-microsoft-teams-f35329c2-57b1-487f-b5e3-70a7efb0945b
- Microsoft Learn, Manage Teams recording policies for meetings and events —
-AllowCloudRecording, OneDrive vs SharePoint storage, external participants,ChannelRecordingDownload, and explicit recording consent. https://learn.microsoft.com/en-us/microsoftteams/meeting-recording - Apple Support, Take a screenshot or screen recording on Mac — the microphone-only audio control. https://support.apple.com/guide/mac-help/take-a-screenshot-or-screen-recording-mh26782/mac
- Apple Support, Control access to screen and system audio recording on Mac — the audio-only permission — https://support.apple.com/guide/mac-help/control-access-to-screen-and-system-audio-recording-mchld6aa7d23/mac
- FluidAudio documentation, Parakeet TDT v3 language coverage and FLEURS word error rates. https://raw.githubusercontent.com/FluidInference/FluidAudio/main/Documentation/Benchmarks.md
Microsoft and Apple pages fetched 4 August 2026.
Questions people ask about this
Why is there no Record button in my Teams meeting?
Most likely one of four reasons Microsoft lists — you are a guest, external or anonymous participant; your admin’s meeting policy has recording off; the organiser restricted recording to organisers and co-organisers only; or Copilot is turned off for that meeting, which switches recording off with it. Hovering the lock icon on the Start recording button shows which one applies.
Can a guest record a Teams meeting?
No. Microsoft’s table lists “Guest”, “Anonymous” and “Person from another org or company” as unable to start or stop a recording. Being promoted to presenter does not change your organisation.
Does Teams tell people if I record with a separate Mac app?
No. Teams notifies participants when Teams is doing the recording — “All meeting participants will receive a notification in their Teams desktop, web, or mobile app as soon as a meeting recording starts.” A local recorder on your Mac is not something Teams can see, which is exactly why the announcement has to come from you.
Where does a Teams recording end up, and can I keep a copy?
In the meeting organiser’s OneDrive for a private meeting, or the channel’s SharePoint site for a channel meeting. An admin can also set channel recordings to a view-only folder where members cannot download them at all.
Do I need BlackHole or Loopback to record a Teams call on a Mac?
Only if your recorder cannot capture system audio itself. An app that holds macOS’s System Audio Recording permission reads the output stream where it already is, so your output device and volume keys keep working normally.
Try it on your next call
Narada records your Mac's audio and your microphone, transcribes on-device, and hands you the decisions and follow-ups. Free to use, no account, no bot in the meeting.