Microsoft Teams call recording

What Teams call recording covers

Microsoft Teams call recording is the capture of what happens on a Teams call so you can listen to it, read it, or reference it later. In practice, teams want to record calls for plenty of everyday reasons: keeping an accurate record of what was agreed, letting people who missed a meeting catch up, training new staff on real customer conversations, resolving "who said what" questions, and building a searchable history of decisions. None of those require a regulator to be involved — they are just good operational hygiene.

Our service records the full range of Teams conversations, not just formal meetings. That includes scheduled meetings, ad-hoc group calls, and direct 1:1 calls to and from the people you choose to cover. Each recorded call produces two things: audio and a written transcript. The audio is exactly what you would expect; the transcript turns the conversation into searchable text so you rarely need to scrub through a recording to find the moment you care about.

Where the built-in Teams Record button relies on a person deciding to press it on every call, our approach is built around reliable, automatic recording. You decide who and what gets recorded once, and it happens consistently from then on, with the recordings landing in your own environment rather than scattered across individual mailboxes and drives.

Four ways to record a Teams call

The recording bot can join a Teams call in four different ways. Together they cover almost any scenario, from "record everything for this group of people" to "record this one meeting I'm about to start":

• Policy-based (automatic). Assign a recording policy to a user and the bot joins every call that user makes or receives automatically. This is the most reliable method because there is nothing to remember — and participants see the standard Teams recording banner.
• Manual join. Add the bot to a specific call or meeting on demand when you only want a one-off recorded session, rather than recording someone all the time.
• Calendar auto-join. The bot monitors Exchange Online calendars for a defined group and automatically joins their scheduled meetings, so recurring and planned meetings are captured without touching each one.
• Direct 1:1 calls. Direct person-to-person Teams calls to and from in-scope users are captured as well, so the quick calls between meetings are recorded the same way the meetings are.

Most organizations mix these methods — for example, calendar auto-join for a project team plus manual join for the occasional client call. The mechanics of each method are covered in more depth on the recording bot page.

Combined and per-participant audio

Every recorded call gives you two forms of audio: a single combined recording with everyone mixed together, and per-participant (unmixed) audio, where each speaker is captured on their own separate track. The combined file is the natural way to play a call back from start to finish. The per-participant tracks are what make the recording genuinely useful when more than two people are talking.

The Teams native Record button produces a single mixed track, which is fine for a quiet two-person chat but gets messy on a busy group call — when several people speak at once, it is hard to tell exactly who said what. Unmixed audio removes that ambiguity. Because each voice is isolated, you get clean attribution: you can follow one participant's contributions in isolation, and the transcription that follows is far more accurate because the system is never trying to untangle overlapping voices from a single track.

Automatic transcripts of every call

Audio on its own is slow to search. That is why every call we record is also transcribed automatically, using Azure AI Speech-to-Text with speaker diarization. Diarization is simply the step that labels who is speaking, so the transcript reads as a proper back-and-forth with each line attributed to a person rather than one undifferentiated wall of text.

The practical payoff is speed. Instead of remembering "that was somewhere in Tuesday's call," you search the text for a name, a price, or a phrase and jump straight to it. Every conversation becomes both listenable audio and readable, searchable text — useful for catching up on a missed meeting, checking a detail, or pulling an exact quote. There is more detail on how transcription works, and its accuracy, on the transcription page.

Where your recordings live

When Teams records a call natively, the file can end up in a few different places depending on the meeting type — a channel meeting goes to that channel's SharePoint site, while a regular meeting recording lands in the organizer's OneDrive. That is convenient, but it scatters recordings across individual users' storage, which makes them hard to find, govern, and keep consistently. Microsoft documents this native behavior here.

Our service takes a tidier approach. Recordings and their transcripts upload automatically to a SharePoint document library inside your own Microsoft 365 tenant— one known, central location that you control. Everything stays under your organization's access controls and retention rules, rather than living on a third-party platform. If you want the full picture of where Teams recordings can end up and why a central archive matters, see where are Teams recordings stored.

When you need compliance-grade recording

For most teams, reliable recording plus searchable transcripts in your own SharePoint is exactly enough. But if you work in a regulated industry — financial services, healthcare, insurance, or anywhere subject to recorded-communication rules — "most calls, most of the time" is not sufficient. Regulators expect that every in-scope conversation is captured, enforced by policy rather than left to individual choice, and retained for a defined period.

That is a stricter standard than general call recording, and it is what our Microsoft Teams compliance recording service is built for. It uses the same recording engine, but centered on the policy-based method so coverage is automatic and cannot be quietly switched off, with configurable retention aligned to obligations such as SEC Rule 17a-4, FINRA books-and-records rules, and HIPAA. Microsoft provides the underlying compliance recording policy framework, and a certified recording application — the one we host and manage — performs the capture. If you are unsure which side of the line you fall on, that page is the place to start.

Recording without managing infrastructure

A recording bot that has to join calls, process per-participant audio, run transcription, and upload to SharePoint is a real piece of software that needs a server to run on — one that stays patched, monitored, and available. The point of our service is that you never have to build or babysit any of that.

Every client runs on a single-tenant dedicated serverthat we provision, host in the US, and fully manage — provisioning, hosting, monitoring, patching, and support all included. Your recordings, transcripts, and configuration are never co-mingled with another organization's data. You handle the Microsoft 365 side (deciding who and what to record), and we run everything else. There is a full breakdown of what the dedicated-server model includes on the managed service overview.

Frequently asked questions