Feb 01 2022 05:44 AM - edited Feb 01 2022 06:27 AM
Hey All,
As of today i have users reporting issues with external chat functionality. For some reason all external users (even if they are Teams users) are shown as Skype for Business users. When opening an existing external Teams chat, it display the message "due to an organization change this chat is no longer availlable Please continue your chat here".
When the user clicks on the link they are directed to a Skype chat. The external user can recieve the chat in Teams. When the external user replies back, the chat i sent to a Teams chat for the internal user, but they cannot respond unless they use the Skype chat.
I wonder how this can suddenly happen without us changing any tenant-settings in the last six months. Maybe you guys have a sugestion on how this can happen. Just to clarify, we have been in Island mode since the beginning (6 years ago) and never had any issues untill today.
Thanks!
Feb 01 2022 06:40 AM
Feb 01 2022 08:24 AM
I can confirm that I have this issue with an external organisation that have never used SfB to my knowledge, along side my organisation who has never used SfB. If nothing has changed either side, why are we seeing this?
Feb 01 2022 01:38 PM
Feb 02 2022 12:18 AM
Both sides are Teams only, yes. I have checked this morning and I get prevented from sending a Teams message on the web (https://teams.microsoft.com) and via the Windows client. The Android client allows sending messages but warns that the contact "might be using Skype for Business. They will see your message if they sign back in to Teams"
Feb 02 2022 12:45 AM - edited Feb 02 2022 01:07 AM
After closer inspection of the users in my tenant, i found that the following user settings was set incorrectly.
InterpretedUserType : PureOnlineSfBUserWithTeamsLicense
I then forced the UpgradeToTeams policy to get the users InterpretedUserType changed to
InterpretedUserType : PureOnlineTeamsOnlyUser
Once this has been set wait 24 hours for it to properly set the user type. Let the user logout and login again and you should be good to go.
Steps to take:
After i followed this list the user that i have migrated could use Teams as intended. Hope that this is usefull for you guys.
Feb 02 2022 12:57 AM
Feb 02 2022 05:30 AM
Feb 02 2022 07:06 AM - edited Feb 02 2022 07:14 AM
That is the correct usertype if you are using Azure AD connect with Teams only.
Also you could turn off the external access wait for 4 to 24 hours and turn it on again. Please keep in mind that turning it on might take another 24 hours to be populated again in the Teams back-end.
Feb 02 2022 08:51 AM
Feb 07 2022 03:33 AM
Can you check if you run the commands in the pictures shown below you get the same output?
Feb 07 2022 03:41 AM - edited Feb 07 2022 03:53 AM
@JeroenKIT1605 @kevin91 and all. This is a heads-up that the following has rolled out ON as default.
Tenant level: CsTenantFederationConfiguration
User level: CsExternalAccessPolicy
Feb 07 2022 03:42 AM - edited Feb 07 2022 03:43 AM
Feb 07 2022 05:00 AM
I understand the contents of the post you shared. However, i wonder why this causes the external chat to stop functioning all of a sudden. Besides our company did not change any settings latelly. And the settings you sugested where already in place before the issue arose. The issue was between Teams to Teams bussiness users.
Does it allow external domains as shown in the below command.
Feb 07 2022 06:17 AM - edited Feb 07 2022 06:30 AM
Simply a heads-up. If nothing has changed in your org. for federation though most likely something has changed at the federated companys org. settings. And if no change there either, a support ticket is the obvious choice and not posting here really.
But there’s three topics to consider.
1. Federation
2. Teams consumer
3. Skype consumer
And the settings associated using PS.