External interprators doesn't have the switch button

Question

External interprators doesn't have the switch button

Bourguignon A 0

Hi,

My ask is about a feature mentionned in this article in "interpreter experience" : https://support.microsoft.com/en-gb/office/use-language-interpretation-in-microsoft-teams-meetings-b9fdde0f-1896-48ba-8540-efc99f5f4b2e

The switch language button is displayed when we test internally but when our interpreter (who is extern) is added as an interpreter, he doesn't see the switch button.

It's very important because without this feature, we need at least two interpreters and it doubled the cost. So we will use Zoom in place of Teams if Teams doesn't fix this problem.

I don't see anywhere a technical documentation that explain when and why the switch button is diplay or not.

Kr,

0 commentaires

1 réponse

Votre réponse

Answer 1

Since your question is in English, I'd reply in English for clarity.

Dear @Bourguignon A,

Good day! Welcome to Microsoft Q&A forum!

Based on your description, I understand that the language switch button for interpreters appears correctly during internal testing, but when an external interpreter is added to a Microsoft Teams meeting, the switch button does not appear. Because of this limitation, the interpreter cannot switch languages during the meeting. Therefore, you’re looking for clarification on when and why this switch button is displayed, as well as guidance on whether this behavior is expected or can be fixed.

To understand the situation better and provide you with the most suitable support, could you confirm the following information:

Was the interpreter explicitly assigned the Interpreter role by the meeting organizer (not just added as an attendee)?
Is the interpreter joining via:
- Teams desktop app
- Teams web (browser)
- Mobile app
Does the switch button appear briefly and then disappear, or never appear at all?
Does the behavior change if the interpreter:
- Signs out and back in?
- Clears Teams cache?

Your confirmation would be very helpful in ensuring you receive the most suitable support!

In the meantime, kindly try the following suggestions to check what might have caused the issue:

Verify interpreter role assignment: Ensure the meeting organizer assigns the external user specifically as an interpreter for the required language pair.
Test with Teams desktop app: Have the interpreter join using the full Teams desktop client, as some advanced controls may not appear in the web or mobile versions.
Check external access and guest policies: Review Teams admin settings to confirm external/guest users are allowed full participation features for meetings.
Run a controlled test: Create a test meeting with one internal and one external interpreter under identical conditions (same app, same role assignment) and compare behavior.

I hope this information is helpful. Please follow these steps and let me know if it works for you. If not, we can work together to resolve this.

Please understand that our initial response does not always resolve the issue immediately. However, with your help and more detailed information, we can work together to find a solution.

Kindly let me know when there are updates or if you need further assistance. Any updates you’re able to share would be really helpful. I appreciate your time and look forward to hearing how things are going!

Thank you for your time and patience.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in [our documentation] to enable e-mail notifications if you want to receive the related email notification for this thread.

Bourguignon A 0 Points de réputation

2026-05-01T11:18:40.5566667+00:00

Hi,I've learned that the external translator was using a family licence and not a pro licence so I'm guessing it's the problem. It's not written anywhere but I'm kinda sure it's the problem.

We will create internal accounts, even if I don't like that for security reasons.

Thanks to have try to help me.
Julie Huynh 3,770 Points de réputation Conseiller(ère) indépendant(e)

2026-05-04T13:02:29.88+00:00

Dear @Bourguignon A,

Thank you for the additional details and for sharing your findings.

Based on what you’ve described and the follow‑up information, your conclusion is reasonable. In Microsoft Teams, advanced meeting features such as Language Interpretation are tied to the meeting policies and licenses associated with the interpreter’s account. In practice, this means that:

The Switch language button is displayed only when the interpreter account meets the required licensing and policy conditions.

Consumer or family-type licenses are not designed to support these enterprise meeting capabilities, which would explain why the button was visible during internal testing but not for the external interpreter.

Given the importance of this feature for your use case and to avoid the need for multiple interpreters, creating internal (or dedicated business) accounts for interpreters is the most reliable and supported approach.

For more information, please refer to: Use guest access and external access to collaborate with people outside your organization

Thank you for your patience and understanding.