How to transcribe a Microsoft Teams meeting without a bot

Microsoft Teams can already turn a meeting into text — but the built-in transcript is tied up in admin settings, licences and where your organisation lets recordings live, and it is not always available on the call you are actually in. This guide covers the three realistic ways to transcribe a Teams meeting — the native feature, a notetaker bot, and local capture on your own Mac — what each one needs, and how to do it with consent and without a bot in the participant list.

Three ways to transcribe a Teams meeting

There are three practical routes, and which one you can use often comes down to who controls the Teams tenant.

Teams’ built-in transcription. Teams can generate a live transcript and a recording itself. It is the most integrated option, but it depends on your organisation’s settings and your licence — and on a call hosted by someone else’s company, you may not be allowed to start it.
A notetaker bot. A third-party tool joins the meeting as a participant and captures the audio in the cloud. It works regardless of tenant settings, but it is visible to everyone and sends your meeting to an outside vendor.
Local capture on your Mac. An app on your own machine records the audio Teams plays and your microphone, and transcribes it there. No bot joins, and nothing has to leave your Mac.

What Teams’ own transcription can and can’t do

Teams’ native transcription is genuinely good when it is available. It produces a speaker-labelled transcript, can run live during the call, and files everything neatly into Microsoft 365 — recordings to OneDrive or SharePoint, transcripts attached to the meeting.

The catches are administrative. Transcription has to be enabled for your organisation, and an administrator can switch it off; some capabilities depend on the licence attached to your account; and the person who can start it is usually the host or someone in the host’s organisation. If you are the external guest on a client’s Teams call, the transcript is their decision, stored in their tenant, under their retention rules — not yours. When you need your own copy, on your own terms, the native feature often is not the answer.

The bot route — and why people avoid it

Connect a tool like Otter, Fireflies or tl;dv to your calendar and it will dial into your Teams meetings as a participant and transcribe them in the cloud. It needs no tenant permissions and no app kept open, which is the appeal. The downsides are the familiar ones: the bot shows up in the attendee list with a name, so a sensitive client call now visibly has a stranger in it, and the audio is uploaded to the vendor to be transcribed and stored. Several of these tools added a “bot-free” desktop mode in 2026, but bot-free is not the same as local — most still send your meeting to their servers.

Transcribing Teams locally on a Mac

Local capture sidesteps both the tenant settings and the upload. macOS can record the audio your computer is playing — the other participants you hear in Teams — alongside your microphone; an app combines the two streams and transcribes them on the machine. Because it listens to the audio rather than plugging into Teams, it does not need anyone to enable a feature or grant an admin permission, and it works the same way on Zoom, Meet or an in-person conversation. The trade-off is that your Mac has to be running the app during the call, and it is Mac-only by nature — for a recording made while you are away from your desk, the native feature or a cloud bot is the better fit.

Consent still comes first

However you transcribe a Teams call, telling the other people is not optional. Around a dozen US states require every participant to consent, and GDPR generally treats a recording as personal data that needs a lawful basis — usually consent — with the strictest applicable rule governing a call that crosses borders. Teams’ own transcription shows participants a notice when it starts, which is a good model to copy: say you are recording, say why, and note it in the invite. Recording locally keeps your audio away from third parties; it does not remove the duty to disclose. This is not legal advice — see GDPR-compliant meeting recording for the detail.

Doing it in folo

folo takes the local route on a Mac: it records your Teams calls and transcribes them on-device, with no bot joining and — by default — nothing uploaded. It captures system audio and your microphone across any meeting app, separates and recognises each speaker locally, and writes the summary on the machine too. There is a cloud transcription option, but you have to switch it on. If what you need instead is a transcript that lives in your company’s Microsoft 365 for everyone to share, Teams’ own feature is the more natural home; folo is for keeping your copy of the conversation on your own Mac.

Questions, answered

Can I transcribe a Teams meeting without a bot?

Yes. Teams’ own built-in transcription adds no bot, and a local capture app on your Mac records the audio directly without joining the call. Only cloud notetakers that transcribe on their own servers need a visible bot in the participant list.

Why can’t I turn on transcription in a Teams meeting?

Native transcription has to be enabled for the organisation and can be restricted by licence or by the host. On a call hosted by another company you often cannot start it — capturing locally on your own Mac is a way to get your own transcript.

Does Teams tell everyone when a meeting is transcribed?

Yes. Teams shows participants a notice when recording or transcription starts. Whatever method you use, announcing the recording and noting it in the invite is the safe, consent-first habit.

Can I transcribe a Teams call on a Mac?

Yes. macOS can capture the system audio Teams plays plus your microphone, and an on-device app transcribes both locally — no Windows, no admin settings and no upload required.