Back in July 2018, Microsoft released new functionality to Microsoft Teams that would migrate existing contacts and contact groups that you have configured in your Skype For Business client into Teams. Specifically, the release details were:
Bring your Skype for Business contacts to Teams
When your organization moves from Skype for Business to Teams, your contacts will make the move with you. To see them, once you’re in Teams, click Chat on the left, then Contacts at the top.
During a recent migration from Skype for Business on-premises to Teams, though, I encountered a user who had multiple groups and contacts but none appeared in the Teams client. The fix was quick and painless.
When looking at the Skype client Configuration Information (press ctrl + right click the Skype for Business icon in the system tray), the Contact List Provider was listed as UCS. After speaking with support, we found that the CLP should have been Skype for Business Server instead. To resolve the issue, you must use PowerShell to connect to SFBO and perform UcsRollback.
$credential = Get-Credential Import-Module SkypeOnlineConnector $sfboSession = New-CsOnlineSession -Credential $credential Import-PSSession $sfboSession Invoke-CsUcsRollback –Identity email@example.com
Understand that this command will complete quickly but contact migration does take some time. A few hours after running the above commands, the contacts and groups were appearing in the Teams web interface. Simply signing out of the Teams client and back in forced the refresh needed for them to start appearing in the Teams client. Once the change is picked up, the user may see the following when they first check out their contacts.
Have you run into other gotchas when working with Microsoft Teams or Office 365? If so I’m interested in hearing about them! Comment below or connect with me on social media using @millh0use.
Have you found any other tricks to resolve this? I ran UCS roll back on a user after migrating to TeamsOnly over 24 hours ago but no change yet. Guessing i might just need to wait longer
This seems to have worked for me anytime I’ve used it. I will saw sometimes it takes longer than others but in at least one instance signing out of Teams and back in seemed to force the client to update. If you’ve run this and it still hasn’t updated that’s worth a shot.