Forum Discussion

JeroenKIT1605's avatar
JeroenKIT1605
Copper Contributor
Feb 01, 2022

Teams external chat

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 ...
Conversations
Messaging
SkeedCompton's avatar
SkeedCompton
Copper Contributor
Feb 01, 2022

AndresGorzelany 

 

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?

  • AndresGorzelany's avatar
    AndresGorzelany
    MVP
    Feb 01, 2022
    So the other org is TeamsOnly?
    • SkeedCompton's avatar
      SkeedCompton
      Copper Contributor
      Feb 02, 2022

      AndresGorzelany 

      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"

      • JeroenKIT1605's avatar
        JeroenKIT1605
        Copper Contributor
        Feb 02, 2022

        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:

        1. Connect to MicrosoftTeams powershell
        2. Use the command Get-CSOnlineUser Email address removed
        3. Check the output for the InterpretedUserType. If it set to PureOnlineSfbUserWithTeamsLicense and the TeamsUpgradeEffectiveMode is set to Island the user needs to be migrated manually.
        4. Run the Grant-CsTeamsUpgradePolicy Email address removed -PolicyName UpgradeToTeams
        5. Check the migration status with the command Get-CsMeetingMigrationStatus
        6. The status "Pending" and "Succeeded" are correct statusses. If any other status is displayed please consult Microsoft Support.
        7. Use the command Get-CSOnlineUser Email address removed
        8. Check the output for the InterpretedUserType. If it set to PureOnlineTeamsOnlyUser and the TeamsUpgradeEffectiveMode is set to TeamsOnly.
        9. Up to 24 hours after the migration the Teams back-end needs to catch up with the changes so funky chat behaviour might occur for the user(s)
        10. Logoff and logon into the Teams client. If the behaviour persist uninstall Teams entirely, remove all Teams folders from "Program files" and "Appdata\Local" and "Appdata\Roaming". Restart the user-machine and reinstall Teams.

        After i followed this list the user that i have migrated could use Teams as intended. Hope that this is usefull for you guys.

    • JeroenKIT1605's avatar
      JeroenKIT1605
      Copper Contributor
      Feb 02, 2022
      Yes, i have tested this with a test-tentant we have on the side.
      • SkeedCompton's avatar
        SkeedCompton
        Copper Contributor
        Feb 02, 2022
        I have checked this for myself and a colleague and I've got;
        InterpretedUserType == AADConnectEnabledOnlineTeamsOnlyUser
        TeamsUpgradeEffectiveMode == TeamsOnly

Resources