If your organization has decided to move off its Skype for Business Server deployment to Teams, you’ll hit an in-between period. A time when some users are on Skype4B, and some have moved to Teams.
Can they still communicate with one another during this period?
It’s possible…but it’ll take some extra configuration. Let’s talk about what you’ll need to do.
How to Make Skype for Business and Teams Talk to One Another
Before any Skype4B user can talk to a Teams user, the disparate systems have to talk to one another. Therefore, you’ll need to setup communications between your Skype for Business Server and your Teams tenant.
Most of the work’s done on the Skype side for this. You must change Skype for Business to work in “Native Interop” mode. Here’s some migration and interoperability guidance on the basics.
Essentially, any on-prem deployment must move to a Hybrid deployment. If you already run Skype4B in Hybrid mode, half the work’s already done. You can skip the Part 1 section below & move to Part 2.
But before you do that, let me call out a major communication limitation.
Limitations on Native Interop
Before we dive into the config work required, let me make this point. Users talking between Skype for Business and Teams will have ONLY TWO TOOLS to communicate:
- One-to-one IM/Chats
- Voice calls
That’s it. No video conference, no group chats, no emojis or file transfers. Not available.
If you have a long transition period, doing the config for this limited communication toolset may make sense. However, if you’re doing a fast cut-over (e.g., less than 4 months), then it doesn’t seem worth the time investment. I would recommend skipping it in that case.
Still here? Great! Let’s talk about making Teams and Skype4B talk.
Part 1: Setting Hybrid Mode with Azure AD Connect
If you’re not already familiar with Azure AD Connect, it’s basically a connection between your Skype for Business Server’s Active Directory and an Office 365 tenant. AD Connect synchronizes your users’ accounts in Active Directory with Azure Active Directory on O365, and vice versa.
This sets up the question of homing. If you created all of your users in your own on-prem Active Directory, then the users are ‘homed’ locally. If you have Teams users you created within your Office 365 tenant, those users are ‘homed’ in Azure Active Directory.
This is important for one reason: Interop between Teams and Skype for Business users only works if you home the user online.
Effectively, you’ll have to transfer all of your Skype for Business users up into the Teams O365 tenant. They’ll still use the on-prem server (in fact they won’t even notice the difference), but they have to live up there to talk to Teams users.
This post would run on forever if I detailed the whole AD Connect setup process. If you do need to set this up, please refer to these MS documentation pages:
- Configure Azure AD Connect for Teams and Skype for Business – MS Docs
- What is Hybrid Identity with Azure Active Directory? – MS Azure
Once you’ve verified AD Connect runs properly, you’ll be able to move Skype4B users up into Azure AD. Fortunately, this part’s not too time-consuming. You have two possible methods:
- Use the Move-CsUser cmdlet.
- Example: “Move-CsUser -Identity email@example.com -Target sipfed.online.lync.com -Credential $cred -HostedMigrationOverrideUrl $url”
- Use the Skype for Business Control Panel.
- Select Users in the Panel window.
- Use Find to locate the users you need to re-home.
- Select the users, and click the Action dropdown menu. Choose Move selected users to Skype for Business Online.
- In the wizard, click Next.
- You may see an Office 365 prompt. Sign in using an administrative account. (Must end in “.onmicrosoft.com”!)
- Click Next two more times to complete the move.
Now it’s time for Part 2.
Part 2: Change Users’ TeamsUpgrade Modes
Every Teams user has a mode assigned to it. Same with Skype4B users. The default mode is “Islands” – meant to signify the user as either on the Skype for Business ‘island’ or the Teams ‘island.’
Now, that won’t work if we want people talking between islands. Each & every user, on both sides, needs to have this mode changed for interop.
Other possible modes are:
- TeamsOnly – For Teams users only
- SfBOnly – For Skype4B users only
- SfBWithTeamsCollabAndMeetings – This is called “Meetings First,” meant for using Teams’ meetings as an introduction to the platform.
- SfBWithTeamsCollab** – This is the mode we want. It facilitates native interop.
In SfBWithTeamsCollab mode, users still use Skype for Business for IM, calls, and meetings. (If you used SfBWithTeamsCollabAndMeetings mode, your users would use Teams for meetings instead. Everything else is the same.)
To change users’ modes, we’ll use the Grant-TeamsUpgradePolicy cmdlet.
If you want to do this user-by-user, use this format:
“Grant-CsTeamsUpgradePolicy -Identity firstname.lastname@example.org -PolicyName SfBWithTeamsCollab”
If you want to do it for all users, use this format:
“Grant-CsTeamsUpgradePolicy -PolicyName SfBWithTeamsCollab -Global”
As I understand, that’s pretty much it. Changing this mode allows Skype for Business users to chat with Teams users, after all the prerequisites are in place.
(By the way, this process also sets up the users to move completely to Teams. It doesn’t mean you have to move them, but you save yourself time this way.)
Teams, Can You Hear Us Now? Good!
I remember our team having some serious issues with Azure AD Connect, the first time we hybridized a Skype for Business Server. (In fairness, that was over 3 years ago. The tech and documentation have improved since then.)
Still, I urge caution if you need to deploy it in your existing on-prem environment. If possible, use a staging environment to test AD Connect setup first, so you’re comfortable. I believe that’s what we did.
What’s your status with Teams and/or Skype for Business? Using one or both? Comment below on your communication situation.