03-27-2020 05:46 AM
03-27-2020 05:46 AM
I would expect that the new Teams native chat should work here but following problem occurs:
Tenant B user sends chat message to tenant A user. Tenant A user receives the message but a Skype Symbol is displayed next to tenant B user. The Message "Due to an org policy change, you can enjoy a richer chat and calling experience" is displayed. When clicking the link a new chat opens with rich features but the reply there is again received in a new chat on Tenant B users Teams. So replies to messages initiated in either tenant always end up in a seperate chat.
Do we need to add the SIP DNS records despite native federation capability here to solve the problem or is this completely unrelated? What could be the problem here?
03-27-2020 05:55 AM - edited 03-27-2020 06:01 AM
@Thomas Oeser So on Tenant B its a new Domain and no External DNS records has been setup yet?
If no record has been created, please do so using the below overview:
And make sure the following is configured:
Also Teams upgrade, check this as well.
The Coexistence mode that is used determines both routing of incoming calls and chats and the app that is used by the user to initiate chats and calls or to schedule meetings.
Put it on "Teams Only" when Skype is not being used anymore.
03-27-2020 06:09 AM
Thank you for your answer. Based on my understanding the global setting for Coexistence mode does not need to be touched. Should work on an individual bases. My assumption was that Teams native federated chat does no longer need the external DNS records and instead the chats are routed directly in the Office 365 Teams infrastructure. But i could be wrong on that.
So if the missing DNS records could be the problem here, i think i will give it a try.
03-27-2020 06:27 AM
by Meng_Kuijun on June 01, 2020
by grigsy on June 01, 2020
by MicrosoftTeamsTeam on May 29, 2020
by Jace Moreno on May 28, 2020
Posted in Microsoft Ignite The Tour 2019 on February 14, 2020