- Hello and welcome to Microsoft Mechanics.
Coming up in the next few minutes,
I'm gonna show you the hands-on admin steps
to upgrade from Skype for Business to Microsoft Teams,
whether you're online or on-premises.
So Skype for Business Online will be retired
on July 31st, 2021.
So now is really the time to start planning
and taking next steps to implement Microsoft Teams.
I'm gonna start with a few basic concepts
to consider during your migration.
Presence displays user availability status
in things like Teams, Skype, Outlook
and even other Office apps.
You need to make sure that's working.
Also, interop or interoperability is the 1:1
communication layer between Skype for Business
and also a Teams user.
Now we've designed the Presence and interop capabilities
in Skype for Business and Teams
to work seamlessly during your migration.
And there are also several different
coexistence modes that enable interop
and tailor the recipient's user experience to your needs,
as we've covered in our previous Essentials episode
at aka.ms/MicrosoftTeamsforIT.
Now, here there are two different altitudes available
for setting these coexistence modes.
First, as you can see here, org-wide policies.
Now these make it the default for all your users
and your tenant and this a global switch.
Now, the second way to do this,
is actually using per user policies.
This lets you actually override that org-wide policy
that we just saw, at the user level
and basically, if this is set to a user,
by changing your org-wide policy,
it doesn't actually change the user's settings.
So you have to go ahead and go back to the user
and change those settings if you've made any changes here.
And here you can see all the same options
that are available at a per user level.
Now, another tool in your tool belt
is the built-in Meeting Migration Service.
Now, this service is invoked behind the scenes
as you modify per user coexistence modes
or you can do that via PowerShell,
and it is a point-and-time configuration.
Now what it's gonna do is actually migrate
Skype for Business meetings into Teams meetings
by replacing what you see at the bottom here,
the meeting cards with Teams details.
Now these are just a few of the fundamentals,
but for more technical reference,
check out aka.ms/skypetoteams.
So now with the fundamentals and key concepts,
and tools understood,
let's move on to the Teams upgrade processes themselves,
starting first with Skype for Business Online
moving to Microsoft Teams,
whether you have a calling plan or not for Microsoft.
Now the good news here in this case,
is that you only need to perform two different steps.
Now the first step here, as you can see on the screen,
like we saw before, is enabling teams-only mode.
You can do that an an org-wide setting.
Once you click save
you'll check that you understand the effect of the change
and now you've set your org-wide setting,
to be Teams only.
Now the next thing we're gonna have to do
is actually run the Meeting Migration Service in PowerShell.
To do that, we're gonna login to Skype for Business Online,
in that module
and now, we have to go in, we can either set per user,
we can use these Start CsEx Meeting Migration Service
against our user principle name for the identity parameter
and then target meeting type is team.
We'll go ahead and click yes for that one.
That's gonna just migrate Adele Vance in our case
and that one email address.
Or we can start identifying variables
within PowerShell to do a bulk operation against all users.
One handy tip here after I use my $TOUsers,
is to use the Teams Upgrade Effective Mode property,
or where those objects are equal to that.
That actually says if they're default on Teams only
or if you've set them to that in the past.
Now I'm gonna run it against all users.
Here you can see we've got 29 Meeting Migrations pending
and we've also got one that succeeded our Adele operation
that we just performed by the single user.
So those were the only two administrative steps
that you have to perform.
And that's it, you're done.
Now the next implementation type I'll describe
is Skype for Business Online with Enterprise Voice,
either using a Cloud Connector Edition or Direct Routing.
So the first thing you'll wanna do,
is determine whether you want to be using Direct Routing
or porting telephone numbers to a Microsoft Calling Plan.
First, if you're using a Microsoft Calling Plan,
you're gonna need to acquire PSTN telephone numbers
and assign them to users in your tenant.
But if you're using Direct Routing,
what you're gonna have to do is actually establish
a new trunk line from your Session Border Controller
and set it to communicate with Microsoft 365.
Now your SBC config's gonna vary based
on the type or vendor that you got
and once you've set it up,
it's actually gonna appear in your Teams Admin Center.
At that point, you will then route PSTN numbers
to the newly established trunk to Teams
as you move users to Teams Only mode.
Now once you've moved users to Teams Only mode,
you're still gonna have to run the Meeting Migration Service
that we saw earlier
and you'll probably wanna to do that in bulk
like you can see here on the screen.
Now for all on-premises implementation
of Skype for Business Server,
you're gonna need to first establish a hybrid configuration
with Skype for Business Online.
Check out aka.ms/teamssfbhybrid for more information.
Each Skype for Business on-premises user
will need to be moved to Skype for Business Online
before they can be assigned a Teams Only policy.
Now this move can actually be done in PowerShell in one step
if you've got Skype for Business Server 2019
or 2015 with CU8 and newer,
using the following single cmdlet:
the Move-CsUser, identity = user principle name.
In our case we've got Adele here.
Target, the sipfed.online.lync.com will be for everyone
and you can use the optional switch in this case
for the one step of MoveToTeams.
Now if you've got an older Skype for Business Server,
or if you just wanna use two lines of PowerShell,
you can do that as well.
And for that, you're gonna use the same cmdlet
minus that MoveToTeams property.
And then you also have to run Grant-csTeamsUpgradePolicy
with Policy Name of UpgradeToTeams.
Your identity again of the user principle name
that you want to upgrade from
Skype for Business Online to Teams only.
Now once you've done that,
you still have to run the Meeting Migration Service
as we saw in the last two steps and scenarios,
to get everyone's meetings migrated
from Skype for Business Online into Microsoft Teams.
So that was an overview of the IT admin steps
needed to upgrade from Skype for Business
to Microsoft Teams, depending on your current configuration.
Additional considerations will include
distributing the Microsoft Teams apps for Windows, Mac,
mobile and VDI environments, along with
which meeting add-in you're gonna want
to display in Outlook,
especially if your users are primarily scheduling
their meetings in Outlook.
Now you can also learn more at aka.ms/skypetoteams.
And of course upgrading to Teams is more
than just a technical upgrade.
You're going to want to consider user adoption and training
and we'll be covering that in our next episode
at aka.ms/MicrosoftTeamsforIT.
Thanks for watching!
(upbeat music)