How to Transcribe a Microsoft Teams Meeting on a Mac
The three real options, what each one requires from IT, and where your meeting audio ends up.
There are three honest ways to turn a Teams meeting into a transcript on a Mac: Teams' own transcription, a bot note-taker, or recording locally on your machine. They differ in what your IT admin has to allow, what they cost, and where your meeting ends up. Here's each one, straight.
Option 1: Teams' built-in transcription
Teams can transcribe meetings, but it comes with conditions. You need a work or school Microsoft 365 license, your organization's admin has to have transcription enabled in policy, and someone with permission starts it during the meeting. The transcript is saved to the organizer's OneDrive or SharePoint. On Copilot-licensed tenants, Copilot can also write AI notes on top.
When it's enabled, it's the zero-extra-tools route. In practice, the admin policy is the catch: in plenty of organizations the button simply isn't there, and personal or free Teams accounts don't get saved transcripts at all. Either way, the transcript lives in Microsoft's cloud under your org's control.
Option 2: A bot note-taker
Services like Otter join the meeting as an extra participant, transcribe in real time, and offer shared notes your team can read together. That collaboration is genuinely useful for some teams.
The trade-offs: everyone sees the bot in the participant list, many corporate tenants block unknown participants outright, your meeting audio is processed on the service's servers, and the plans meter you by minutes per month. We wrote an honest side-by-side in Chirp vs Otter for Mac.
Option 3: Record locally on your Mac
This is the route I built Chirp for. Your Mac is already playing the meeting audio, so there's no reason a transcript has to involve anyone's servers, or a ticket to IT. Chirp captures the call audio plus your microphone, transcribes it on-device, and labels each speaker automatically.
- Install Chirp. It walks you through the audio permissions on first launch.
- When the meeting starts, begin a Meeting recording from Chirp's indicator in your Mac's notch. There's also an auto-record option that notices a meeting starting and handles this for you.
- Have the meeting. No bot appears in the call, and nothing is uploaded.
- When it ends, stop the recording. The transcript lands in your history with each speaker labeled, searchable, with the audio attached. Export to Markdown or SRT if you need to share it.
Kicking off the reporting project. Goal is a first cut by the end of the month.
I can own the data layer. The export piece needs a decision on formats first, though.
Let's do CSV first and revisit the rest. Elena, can you mock the summary page this week?
Yes, by Thursday. I'll keep it to one screen for the first version.
It works whether you're the organizer or a guest, whether or not your tenant has transcription enabled, and the same setup covers Zoom, Google Meet, webinars, and anything else your Mac can play. The details are on the Meeting Transcription page, including how the speaker labeling works.
A note on consent
Whichever route you pick, tell people you're recording. Recording rules vary by region, many workplaces have their own policies, and it's the decent thing to do regardless. A local recording doesn't announce itself the way a bot does, so the announcing is on you.
Which one should you use?
- Your org has transcription enabled and OneDrive storage is fine: use Teams' built-in transcription.
- Your team works inside shared live notes during the call: a bot service earns its subscription, if your tenant lets it in.
- You want a transcript of any Teams meeting, no admin policy, no bot, nothing uploaded: record locally. That's Chirp's whole job, and it also keeps every transcript on-device.
