Forum Discussion
Teams Native Chat Problem
ThomasOeser 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.
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.
- If your org isn’t set teams only it might still be utilizing the dns records. I would just add them anyway. You def don’t need the org changed for federation(external chat)to work properly.
It could be a timing thing. Those changes to upgrade mode used to take up to a week. I figure they would have fixed that by now but with everything going on with system load lately they could have scaled back and it might be taking a bit longer.
Anyway try the dns and let us know!thank you, it was indeed a delay after applying the teams only mode to the users. After about 48 hours everything works as expected now even without the DNS entries. But we will for sure ad them as well.
