Microsoft Teams Interpreter agent has a name that can confuse working interpreters.
It sounds like a tool for interpreters. Microsoft built it for Teams participants who want to hear meeting speech translated into a chosen language.
That can be useful. It is not the same thing as an OPI interpreter workspace.
Meeting translation and OPI support solve different problems.
Short answer
Microsoft says Interpreter agent acts as a translator in Teams meetings. Participants with Microsoft 365 Copilot licensing can listen to meeting speech in their chosen language. Microsoft documentation lists supported languages such as Chinese Mandarin, English, French, German, Italian, Japanese, Korean, Portuguese, and Spanish in the admin page, while the user support page also references Taiwanese in its current supported-language list.
TIP
Use meeting-native translation for meetings it was built for. For phone interpreting, test whether it can hear both sides and stay out of the way.
Microsoft also says Interpreter uses cloud-based processing, can simulate or use automated voices, and requires eligible Microsoft 365, Teams, and Copilot licensing.
An OPI support tool is different. It supports the human interpreter on OPI and VRI calls with live transcription, two-way translation reference, speaker labels, Quick Lookup, notes, domains, and term mappings. It works beside the call source instead of asking the call to become a Teams meeting.
For Teams captions specifically, read Interpreter vs Microsoft Teams Captions.
Teams Interpreter agent serves meeting participants
Teams Interpreter agent helps people in a Teams meeting understand speech in another language.
A participant turns it on, selects a language to listen in, adjusts audio balance, and chooses a voice option. Microsoft says people without Interpreter turned on can see an indicator when someone’s speech is being translated, so participants know to wait before speaking.
That design makes sense for meetings. It helps participants collaborate across languages inside Teams.
It also depends on Teams. The meeting, admin policy, license, language support, and participant settings all matter.
If your assignment is a structured Teams meeting and the organization has enabled the feature, it may help that meeting. The host environment controls the lane.
OPI interpreters need control and portability
OPI is not a neat Teams meeting.
You may receive calls through:
- Agency portals.
- Browser softphones.
- Phone bridges.
- Telehealth systems.
- Insurance queues.
- Government intake systems.
- Zoom, Meet, Webex, or Teams.
The interpreter often does not control the platform. The caller may not have a Teams account. The provider or client may not allow a platform change. The workflow may require a specific portal for routing, quality monitoring, or compliance.
That is why portability matters.
Interpreter does not ask the caller to join a new meeting. It gives the interpreter live support around the audio source already in use, when policy and setup allow that capture.
AI speech translation is not professional interpreting
Teams Interpreter agent translates speech for meeting participants. A professional interpreter does more.
On a medical, legal, insurance, or government call, you handle:
- Clarification.
- Register.
- Cultural context.
- Speaker overlap.
- Ambiguous terms.
- Confidentiality.
- Role boundaries.
- Ethics.
The system may translate words. It does not take responsibility for those human decisions.
That is why the product category matters. If a tool speaks for participants, it may replace or bypass the interpreter. If a tool supports the interpreter, it keeps the qualified human in the workflow.
Interpreter belongs in the support category.
Licensing and access shape the fit
Microsoft ties Interpreter agent to Microsoft 365 Copilot licensing and eligible Teams requirements. Microsoft documentation says 20 hours of interpretation are included per user per month with a Microsoft 365 Copilot license, with access beyond included hours subject to capacity.
That may be fine for organizations already invested in Microsoft 365 Copilot.
For freelance OPI interpreters, access is the harder question. You may not own the tenant. You may join as a guest. You may not have the required license. You may not be working in Teams at all.
Interpreter pricing is built around active call support. If you work across many platforms, that model can fit the way OPI shifts happen.
See pricing for the current Interpreters pricing details.
A simple comparison
| Need | Microsoft Teams Interpreter agent | Interpreter |
|---|---|---|
| Main fit | Teams meeting speech translation | OPI and VRI interpreter support |
| Primary user | Teams participant | Working interpreter |
| Platform | Microsoft Teams | Works beside supported call audio sources |
| Human interpreter role | May be absent or separate | Central |
| Output | Translated speech/audio experience | Live transcript, translation reference, notes |
| Setup control | Admin, license, meeting settings | Interpreter-owned workflow, subject to policy |
| Language coverage | Microsoft-supported set | Built for interpreter call support across many language pairs |
| Best use | Multilingual Teams meetings | Live phone and video interpreting support |
Choose Teams Interpreter agent if
The meeting is already in Teams.
The organization has the right licensing and policies.
Participants need to listen to translated meeting audio.
The communication is appropriate for AI speech translation under the organization’s rules.
Choose Interpreter if
You are the interpreter.
Your calls come from different portals, softphones, or meeting tools.
You need both sides of the exchange visible while you interpret.
You want quick lookup, notes, speaker labels, domain settings, and term mappings.
You need support that follows your OPI workflow instead of a single meeting platform.
The honest take
Microsoft Teams Interpreter agent may help multilingual Teams meetings. The name does not make it an OPI interpreter tool.
Professional interpreters need support that respects the live call, the platform they must use, and the human decisions that make interpreting safe. Use Teams translation features when the meeting environment calls for them. Use an OPI tool when the work is interpreting.
Sources: Microsoft Teams Interpreter admin documentation, Microsoft Teams Interpreter user support.