Microsoft Teams transcribes calls and meetings with no extra software: during a call you go to More actions, then Record and transcribe, then Start transcription. Whether that menu item shows up is decided by the administrator's policy; starting it, stopping it and setting the language is then done by an authorised person in the call. Teams keeps two worlds apart: the meeting policy for meetings and group calls, the calling policy for 1:1 calls and calls to the phone network. Afterwards it sits in the chat under Recap > Transcript. And before anything else: every participant sees a notification that transcription is running, but a notification is not consent. Recording the non-publicly spoken word without authorisation is a criminal offence under § 201 of the German Criminal Code; the safe house rule is prior consent from everyone involved.
To me a transcript is never the result, it's the raw material. What actually saves time starts afterwards: when thirty conversations reveal that one question came up nineteen times. How I take workflows apart is on Process optimisation; which ones suit the handover is in Which tasks you can hand to AI.
Why the feature may not show up for you at all
This is where most searches for "transcribe Teams calls" stop without being answered. Availability is set by a policy an administrator assigns; the decision inside the call stays with the person, who starts, stops and picks the language. For meetings and events Microsoft names two conditions at once: organizer and the person starting must have the setting turned on. If one is missing, the button is gone, with no error message. On top of that, meeting policy and calling policy drift apart in practice.
That bottom row explains the most common case: transcription works in meetings but not on a call. Not a defect, just the default. Microsoft lists further reasons for a missing button, worth checking before any software purchase:
- You're a guest, anonymous, or from a different organization than the organizer.
- The admin hasn't allowed transcription for meetings or for calls: two switches.
- The organizer isn't allowed to transcribe. Then nobody has the button.
- You're an attendee rather than a presenter.
- The organizer set Who can record and transcribe to Organizer and co-organizers or No one.
- The organizer turned Copilot off. Recording and transcription go off with it.
- The admin set
PreventTollBypass, which forces calls through the phone network.
Knowing the list gets you a precise question to IT instead of a "transcription doesn't work" ticket.
What the administrator has to enable
For calls the switches live under Voice > Calling policies, and each controls its own feature. They don't require one another: you only need the matching one.
- Transcription permits the text after the call: the switch this article is about. The cmdlet reference says of
-AllowTranscriptionForCalling only "determines whether post-call transcriptions are allowed", without making a recording a condition. Off by default: Set-CsTeamsCallingPolicy -Identity Global -AllowTranscriptionForCalling $true.
- Cloud recording for calling permits audio and video on 1:1 and PSTN calls:
-AllowCloudRecordingForCalls $true. Only needed if you want the recording.
- Real-time captions in Teams calls:
-LiveCaptionsEnabledTypeForCalling. On by default, never saved, no replacement for a transcript.
For meetings the switch lives under Meetings > Meeting policies, is also called Transcription, and is on for new policies. Changes to the global policy apply to everyone except people with their own assigned policy: that's where the effect comes from that one department can transcribe and the one next door can't. The Microsoft 365 admin center also has a diagnostic tool: enter the user's address and the meeting URL, and it names the missing condition.
Step by step: transcribing a call
- Get consent first. One sentence at the start: that transcription is running, what for, how long the result is kept, and that saying no carries no consequences.
- More actions > Record and transcribe > Start transcription.
- Check the language via Show transcript > Language settings, confirm with Update.
- Let it run, don't read along. Correcting later is cheaper than not listening now.
- Collect it. Chat > Recap > Transcript, and for meetings on the calendar event as well.
- Set a retention period and delete. The defaults are not a deletion policy, more on that below.
Whoever may start may also stop: organizers, co-organizers, presenters.
Set the language before anyone speaks
Speech recognition runs on the language you set, and it has to be the right one or Teams produces formatted nonsense. Microsoft's language list (article dated 06.07.2026, retrieved 19.09.2026) includes German (Germany) and German (Switzerland) among roughly sixty variants from Arabic to Welsh.
- The setting lives in the transcript, not in your account. You change it during the call via Language settings.
- One transcript, one language. A conversation that jumps between German and English is the standard case in many companies and the exception in the product logic. That's a product limit, not a law of nature: it says so in the version of the page cited above, and before a multilingual meeting it's worth checking whether it still holds.
- Translation is a separate feature. Live translated transcription requires a Teams Premium licence for the organizer and only runs with ordinary transcription switched on.
Transcript, captions, recording: three different things
These three get mixed up constantly, and that costs you exactly the material you were after.
The key sentence comes from Microsoft's admin documentation: if recording is on but transcription is off, there is no transcript file next to it, and captions can't be turned on during playback. That a starting recording also starts transcription, as the help page says, doesn't contradict this: only if transcription is allowed anyway. If you only want the text, transcribe without recording.
Where the transcript lands and how long it stays
For meetings and calls with a recording, Microsoft documents storage in OneDrive or SharePoint. The following storage and permissions table covers those cases, and its guiding question is who selected Record. For a telephone transcript without a recording, the Microsoft pages checked here name neither the same owner nor the same retention period.
Two clocks run on retention. For meetings and events, Recordings and transcriptions automatically expire (under Meeting policies > Recording & transcription) defaults to 120 days; the range is 1 to 99999 days, -1 means "never expires", A1 licences cap at 30. For recorded 1:1 calls, CallRecordingExpirationDays applies, and the cmdlet reference is narrow about it: "sets the expiration of the recorded 1:1 calls. Default is 60 days."
For a call transcript where nobody selected Record, these pages name neither an owner nor a retention period. So don't carry the numbers over from the recording world: collect the transcript from the chat, put the copy where your filing is already governed, and set the period yourself.
Two traps are spelled out in the documentation. Changes to the period only affect new files. And "expired" doesn't mean "deleted": the file moves to the recycle bin and stays there for a further 93 days by default on work and school accounts. Anyone promising a deletion deadline counts those in or uses retention labels in Microsoft Purview, whose shortest period is one day.
One paragraph on consent
Teams shows every participant a notification that transcription is running, and admins can replace the default notice with their own privacy URL. But a notification is not consent, and conversely no evidence that anyone consented. § 201 of the German Criminal Code makes recording the non-publicly spoken word without authorisation an offence: secret recording is forbidden, and "without authorisation" is the hinge. Prior, explicit consent from everyone involved makes the recording authorised, and that is the safe house rule; narrowly limited exceptions are a case-by-case question for a lawyer. Separate from that comes the second step: storing, analysing and retaining are processing of personal data and need their own legal basis, even when the recording itself was clean. Teams has an explicit recording consent feature for this: the other party is muted and has to answer yes or no before they can take part again, and the answer lands in the audit log. It's controlled through the meeting or calling policy, though Microsoft's cmdlet reference still marks the parameter for calls as not released. What the law requires and what the GDPR demands for the later analysis is in Transcribing Calls: What German Law Says. I'm a developer, not a lawyer, and this isn't legal advice.
When Teams isn't enough
Three limits show up reliably. First: you also work in Zoom or Meet and don't want to maintain three built-in tools. For that, the comparison in Automatic Meeting Minutes with AI also covers what Teams adds with a Premium or Copilot licence. Second: you have audio files that never went through Teams, old recordings, voice notes from your phone, interviews. For those the route runs through dedicated transcription software, including the question of whether it works locally or in the cloud. Third, quieter: recognition quality on technical vocabulary, a usable export format, your own retention period or processing on your own machine aren't negotiable inside Teams.
From transcript to register
Now you have text. A language model will write a single set of minutes from it if you give it the structure, as shown in Have Minutes Written. After thirty conversations you have thirty texts, and that's where most people stop, because nobody reads thirty transcripts. The value is in the pattern: which question keeps coming back, which objection in which order, and which of your own answers worked best.
That's exactly what Gustav, my AI employee for call analysis is for. His first working step isn't analysis but pseudonymisation, hard-wired: names become roles, companies become industries, amounts become orders of magnitude, places become regions. Replacing names is not yet anonymisation: Art. 4(5) GDPR calls precisely that pseudonymisation, and under Recital 26 such data remains personal data. The counter-check using role, industry and one rare detail is therefore a minimum test. True anonymity depends on the full context and all means reasonably likely to lead back to a person. If doubt remains, the register gets a purpose, a retention period and protection like any personal filing. For speech recognition Gustav uses Whisper locally on the machine in my setup. His product deliberately isn't the transcript but a pattern register: the recurring questions together with your own best answer, which turns into a playbook, FAQ, content raw material and an objection library. He distils what you said and invents nothing on top. What that looks like in day-to-day coaching is in AI for Coaches, and what data goes anywhere near AI in my business is in AI and Privacy.
Frequently asked questions
Can Teams transcribe phone calls?
Yes, for 1:1 calls and calls to the phone network. The Transcription toggle in the calling policy is off by default according to Microsoft, so an admin has to enable it. Cloud recording isn't required for it.
Why is "Start transcription" missing for me?
Usually the policy: transcription isn't allowed for calls or meetings, the organizer isn't allowed to transcribe, you're a guest, anonymous, external or an attendee rather than a presenter, or Copilot is off. Full list above.
How do I set the Teams transcript to German?
During the call via Record and transcribe > Show transcript > Language settings, pick German (Germany) or German (Switzerland) and confirm with Update. One spoken language applies per transcript; for translation the organizer needs Teams Premium.
Where do I find the transcript, and how long does it stay?
In the chat under Recap > Transcript, and for meetings on the calendar event; if it was recorded, the file sits next to the recording. The 120 days for meetings and 60 days for 1:1 calls apply, in Microsoft's own wording, to those recording cases; for a transcript without a recording Microsoft names no period, so you set it yourself.
What's the difference between a transcript and a recording?
The recording is the video, the transcript the searchable text with timestamps and speaker attribution; captions are never saved. Both are controlled separately, details in the table above.
Is Teams enough, or do I need dedicated transcription software?
For conversations that happen in Teams anyway, Teams gets you a long way. The reasons that still speak for dedicated software are above under "When Teams isn't enough".
How to continue
Run the test before you buy anything: call a colleague and check under More actions whether Record and transcribe is there. If it's missing, you ask IT for the Transcription toggle in the calling policy, not for a new tool. If it's there, hold a conversation with consent and look at what comes out. And put the question next to it that starts to matter around the tenth transcript: what do you actually want to know from all this?
How a pile of conversations turns into a register is what Gustav does as a ready-made package in my community, with the pseudonymisation pass and consent templates to build on. You don't have to draft the request to your IT alone either: others have already sent one, and in the calls we go through yours together. The templates are samples without warranty. Everything about it under Community.
