Forum Discussion
"We can't setup the conversation because your organizations are not setup to talk to each other"
Looks like I found the issue. When I did a Get-CsTenantFederationConfiguration, the AllowedDomains setting was blank. I added "AllowAllKnownDomains" and chat is working now.
https://www.thirdtier.net/2020/04/10/microsoft-teams-does-not-allow-remote-users-to-connect/
I think this setting was inherited from our Skype for Business configuration which had federation disabled, but that is a guess. Our tenant is still in Islands mode, target is Teams only, and I'm able to chat with them now.
Joe McGowan Hi, I get the feeling that an Allow list is in use here. Have you verified that?
https://docs.microsoft.com/en-us/microsoftteams/manage-external-access#plan-for-external-access
Btw, this is the text next to the toggle:
Users can communicate with other Skype for Business and Teams users
See this as well
https://docs.microsoft.com/en-us/microsoftteams/coexistence-chat-calls-presence#federated-routing-for-new-chats-or-calls
Nothing in the allow/disallow list. I get the feeling both tenants need to be in Teams only mode.
I had this working previously in Islands mode, but I had to go into the Skype for Business Admin Center and allow external communication. That no longer exists, so I may need Powershell to check status. We're going to Teams Only mode in less than 30 days, so I'll see what happens then.
Joe McGowan And how does the other tenant settings look like? You don't necessarily have to be Teams-only as the table I sent shows.
I read your initial post again, you are correct in your scenario in that way that it can ONLY be a Teams RECIPIENT.
Federated routing for new chats or calls
https://docs.microsoft.com/en-us/microsoftteams/coexistence-chat-calls-presence#federated-routing-for-new-chats-or-calls
Joe McGowan See above 🙂
Its just not working. I opened a Microsoft support case.