Share via

Teams bidirectional translation toggle missing for external users

Mykhailo Sokol 0 Reputation points
2026-05-18T12:28:54.62+00:00

We are using Microsoft Teams virtual appointment meetings with language interpretation enabled.

We can assign the interpreter role to both internal and external users successfully. However, external interpreters do not see the bidirectional language switch buttons (to change translation direction), while internal interpreters do.

All users are joining via the Teams desktop client.

Is bidirectional interpretation fully supported for external/guest users in virtual appointment meetings, or are there known limitations for this meeting type or tenant/client combination?

Microsoft Teams | Microsoft Teams for business | Meetings and calls | Other
0 comments No comments

2 answers

Sort by: Most helpful
  1. Liora D 15,035 Reputation points Microsoft External Staff Moderator
    2026-05-18T15:37:14.65+00:00

    Dear @Mykhailo Sokol,

    I hope you’re having a good day.

    Thank you again for the detailed explanation, I spent some time testing a similar setup on my side to better understand your scenario.

    I was able to reproduce the same behavior: when assigning the interpreter role, internal users can see and use the bidirectional language switch, while external (guest/personal) users do not see this option, even though they are successfully assigned as interpreters and can participate.

    User's image

    Based on my research, there is no single document that explicitly describes this exact behavior. However, when comparing the official guidance, there are two important points:

    • The setup documentation confirms that external users can be assigned as interpreters during a meeting User's image
    • At the same time, the capability documentation indicates that language interpretation is not fully supported for external users User's image

    In practice, this seems to mean that external interpreters can join and perform the role, but do not receive the full set of interpreter controls, and this aligns with what both you and I are seeing, specifically, the missing bidirectional toggle.

    Due to the limitations of my test environment, I cannot validate every variation (for example across all meeting types like virtual appointments), but since this behavior is reproducible and consistent, it appears to be a difference in feature capability rather than a configuration issue.

    If this functionality is critical for your use case, the current reliable approach would be to use internal tenant users for interpreter roles to ensure full control availability.

    I hope this helps clarify things a bit and thank you again for raising such a well-documented case

    If my response has helped you better understand the situation and guided you toward a possible next step, please consider marking it as the “Accepted answer.” Doing so will pin the thread to the top, making it easier for others to discover your question and see the pioneering effort you have made in raising this issue. It also helps users searching with related keywords find the discussion more quickly and benefit from the insights shared. 

    Warm regards, 


    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.

    Was this answer helpful?

    0 comments No comments

  2. Q&A Assist
    2026-05-18T12:29:04.15+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    Bidirectional interpretation is not supported for external/guest users in Teams meetings, including virtual appointments.

    In the documented capabilities for Teams external users, Language interpretation is explicitly listed as not supported:

    • Under “Translation” features for Teams external users, the Language interpretation capability shows as not supported (❌).
    • In the meeting options, Enable language interpretation is also listed as not supported (❌) for Azure Communication Services/Teams interop scenarios.

    This indicates a platform limitation rather than a client issue: external/guest participants can join the meeting, but the full language interpretation experience (including controls such as changing translation direction / bidirectional toggles) is not available to them in these interop/guest scenarios.

    So, the behavior described—internal interpreters seeing bidirectional controls while external interpreters do not—is consistent with current limitations for external users in these meeting types, not a misconfiguration of the tenant or clients.


    References:

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.