How to translate a Microsoft Teams meeting live
Teams Interpreter does voice-to-voice in 10 languages, but it requires Microsoft 365 Copilot rather than Teams Premium, excludes external guests, and does not work in ad hoc meetings, webinars or town halls. Check those four limits before planning around it.
Teams has the most capable native translation of the three major platforms and the most conditions attached. The conditions are where plans fail.
What Teams Interpreter does
Voice-to-voice translation with voice simulation, so the translated audio approximates the speaker’s voice rather than a generic one. In 10 languages.
For a scheduled internal meeting between two of those languages, with everyone appropriately licensed, it works well.
The four limits to check first
1. It requires Microsoft 365 Copilot, not Teams Premium. This is the most expensive surprise. Teams Premium — around $10 per user per month on annual billing — is not sufficient. The prerequisite is Microsoft 365 Copilot, roughly $30 per user per month. Organisations that budgeted for Teams Premium discover the real entry cost is about three times what they planned.
2. It excludes external guests and anonymous users. Anyone joining without a licensed account in your tenant cannot use it. That rules out most client calls, supplier calls, candidate interviews and partner meetings — which for many teams is the majority of the calls where translation would matter.
3. It does not work in ad hoc meetings, webinars or town halls. Scheduled meetings only. If your use case is the unscheduled call that comes up on Tuesday, or an all-hands, Interpreter is not available.
4. Recordings do not keep it. Microsoft’s own documentation states that meeting recordings only capture the original meeting audio and don’t include interpretation audio, and translated transcripts disappear when the meeting ends.
For a distributed team where most people watch afterwards, this is the limit that matters most, and it is the one least often checked in advance.
Ten languages is the other constraint
If your languages are inside the ten, good. If your team spans Polish, Turkish or Vietnamese, check the current list against your actual needs rather than assuming coverage.
When Teams Interpreter is the right choice
- Internal meetings only
- Two languages, both in the supported set
- Everyone already has or will get Microsoft 365 Copilot
- Scheduled, not ad hoc
- The live session is what matters; the recording is not
That is a real scenario, particularly in large enterprises that have already bought Copilot for other reasons. If it describes you, the marginal cost is zero and you should use it.
When you need something else
- External participants of any kind
- More than the supported languages
- Ad hoc meetings, webinars or town halls
- Recordings that must keep the translation
- You are not buying Copilot
Practical notes if you do use it
- Brief speakers to pause at clause boundaries rather than trailing off
- Put numbers, names and acronyms in the chat as well as saying them
- Test with real speakers before a meeting that matters — spontaneous speech behaves differently from a scripted demo
- Decide the fallback if it fails mid-meeting: continue in the source language and circulate a translated summary is usually the least disruptive answer
Following a Teams call you were invited to
Teams Interpreter is something the organisation enables, which is exactly the problem for an external guest — the group Interpreter explicitly excludes.
If you join Teams in the browser rather than the desktop app, VoxTranslate for Chrome translates that tab’s audio into subtitles over the call, and can speak the translation while the original stays audible underneath. It needs no Microsoft licence and nothing from the organiser.
Same boundary as everywhere else: it translates what you hear, not what you say. It is the answer to “I cannot follow this meeting”, not to “we need a meeting nobody has to hold in a second language”.