Forum Discussion
Teams to external Teams chat
- Aug 08, 2019
Hi,
That Island mode makes it messy, you should only use that for a short period for some test users, don't use it in production. Is both domain A and domain B users in Islands mode?
Since the current version of federation is using Skype for Business Online be messy. When a user in domain A initiates a chat to any person in domain B do they get the message in Skype or does it only disappear?
The solution would be to use Teams mode, or maybe some of the Skype Only mode but that can cause other problems when moving from Islands to SfBOnly.
Islands does not allow external chat (federation) into the recipients endpoint setting, it always routes to Skype for Business client unless you are on Teams Only. Please see this video for a good explanation of such. https://youtu.be/wEc9u4S3GIA?t=3049
Also note, if they have Skype for Business on-prem, not setup hybrid, then you cannot federate/chat to them via Teams.
- Erjen RijndersAug 09, 2019Brass Contributor
ChrisWebbTech, I think you are right after all. The reason that people in Domain B can chat in island mode, is because they initiate the chat to someone with Teams Only mode. Then it works.
If the team only mode person initiates a chat to the island mode person, it's failing all the time. Changing it to Teams Only mode (and waiting for some time), it starts working.
I am happy it starts working normally, but it's pretty complex and illogical. Thanks again.
- LinusCansbyAug 09, 2019MVP
If a person in Domain A (teams only) sends a message to a person in Domain B (islands) they should receive the message in their Skype client at least.
- Erjen RijndersAug 09, 2019Brass ContributorYes indeed, except when the person in Domain B initiates the chat with Teams. That works fine.
- Erjen RijndersAug 09, 2019Brass Contributor
ChrisWebbTech, that video helps a lot and gives a great overview, but I have users in domain A (Teams only mode whole organization), sending chats to Domain B (Island mode) and they receive the message in Teams. I am very sure, I checked that with multiple users.
So I think it makes it messy, like LinusCansby says. It's not 100% reproducible so messy is the right word.
But the good news is, I got it all working. Only with the help of you guys. Thanks a lot, I appreciate it.