Cross Tenant Sync and Teams calling

@Peter

This behavior is expected given the current capabilities and limitations of cross‑tenant synchronization for Teams calling.

When you synchronize users from another tenant, many attributes (like display name, presence, etc.) are brought over so that the user appears in your Teams environment. However, for voice and call routing scenarios the situation is more complex. The call routing logic in Teams is tied to tenant-specific configurations and policies, and, in a cross‑tenant scenario, the system isn’t set up to automatically forward or route calls to the target tenant’s Teams instance. That’s why you see the normalized name (first.last_Domain.com#Ext#) and why the call attempt ends up trying to reach a local tenant contact rather than establishing the connection with the user’s actual calling service.

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.

Hello Peter,

I'm facing the same issue, but hopefully there's a workaround.

If you setup call forwarding (or simultaneous calling) from the iOS Teams app (maybe the Android one too, I did not test) and when prompted to enter the name of the target Teams identity to forward calls to, be sure to type the complete UPN (usually the e-mail address) up to the last character.

At this moment you'll see a second identity proposed (the first one is the guest identity in your local tenant) and choose this one.

We've been doing this for many users and it seems the only to set this up. (Actually it used to be possible from the Windows version of Teams about one year ago but is not longer possible).