in #productivity, Semi-Professional

Demystifying Teams Federation

Prepare to have your mind bent. Everything circles around your Teams Upgrade Coexistence Settings. The default setting is Island Mode, which is unlikely to behave how you expect.

There’s an upcoming option (that you can activate via PowerShell) called TeamsOnly that is what you need once you no longer intend to use Skype. This insures all of your federated messages are sent to Teams, and prevents your users from using Skype at all.

So, how do you reach this Nirvana that is TeamsOnly? Well, it’s not quite ready for prime-time and your mileage may vary but if you definitely don’t need Skype there’s not a lot to loose. You’ll have to use Powershell, with the Skype for Business Connector Module installed.

Import-Module SkypeOnlineConnector
$userCredential = Get-Credential
$sfbSession = New-CsOnlineSession -Credential $userCredential
Import-PSSession $sfbSession
Grant-CsTeamsInteropPolicy -PolicyName $null -Global
Grant-CsTeamsUpgradePolicy -PolicyName UpgradeToTeams -Global

If you need to facilitate a transition to Teams, you can use the policy named IslandsWithNotify to tell your users you’ll be transitioning to Teams and help them download it. You can also use -Identity user@upn.tld instead of -Global to apply the policy to a single user.

Known Limitations

This isn’t ready for prime-time, so your mileage may vary.

  1. Users who have the coexistance mode of TeamsOnly cannot use Skype for Business at all (I though this was obvious, but you may not)
  2. Teams doesn’t support file transfers to external users. External Skype users who send you a file via Skype will get a transfer failed notice.
    1. This includes images, emojis, gifs, etc.
  3. Teams doesn’t seem to be able to speak to consumer Skype accounts. If you want to chat with external users who don’t use Office365 internally, they either need to create a Free Teams tenant or you’d need to use guest access or another chat platform.

Write a Comment

Comment