Plan for Office 365 Workload Deployment
Plan Office 365 Applications Deployment
The course is part of these learning paths
This Planning Office 365 Workloads and Applications course will teach you how to plan for Office 365 workload deployments and hybrid solutions. You will learn how to identify hybrid requirements for Exchange and SharePoint hybrid solutions, and how to plan connectivity and data flow for Office 365 services, including Exchange Online, SharePoint Online, and Teams. You’ll learn how to plan migration strategies for Exchange, SharePoint, and Teams, and how to determine the best strategies.
Later in the course, you will learn how to plan Office 365 application deployments and how to plan application updates. You’ll also learn about the different update channels and when to use each.
- How to plan for Office 365 workload deployments
- How to plan for migrations and hybrid solutions
- How to plan for Office 365 application deployments
- IT professionals who are interested in obtaining an Microsoft 365 certification
- Those tasked with planning Office 365 deployments and migrations
- A decent understanding of Office 365 workloads, including Exchange Online, SharePoint Online, and Teams
When you move a user from on-prem Skype for Business to Teams only the user's Skype for Business home is moved online. As a result the user is assigned the Teams upgrade policy with the mode set to Teams only.
Once a user has been moved from the on-prem environment to Teams only mode, incoming calls and chats from other users will land in the user's Teams client. The moved user will be able to communicate with Skype for Business users whether they are on-prem or online users. The moved user will also be able to communicate with users in federated organizations. And any new meetings that the moved user schedules will be Teams meetings.
Users who have been moved to Teams can still join Skype for Business meetings, and any pre-existing meetings that have been scheduled in the future are migrated from on-premises to Skype for Business online. Any contacts that existed on-prem will become available in Teams shortly after the moved user logs on to teams for the first time. It's important to note that users that have been moved will not be able to initiate calls or chats from Skype for Business, nor will they be able to schedule new meetings in Skype for Business.
If a moved user tries to launch the Skype for Business client, the user will be directed to Teams. In the event that the Teams client is not installed the user will be directed to the web version of Teams using his or her browser.
There are two ways to move users from on-prem to Teams. If the organization is using an earlier version than Skype for Business server 2015 with CU8 the move to Teams will require two steps. First the user will need to be moved from the on-prem Skype for Business server to Skype for Business online. Once the user has been homed in Skype for Business online you'll need to assign the user the Teams upgrade policy with mode set to Teams only. Granting Teams only mode requires you to run the grant CS Teams upgrade policy commandlet from a Skype for Business online PowerShell window. The full command is shown on your screen. Now, if you're using Skype for Business server 2015 CU8 or later, instead of performing these two steps we just covered, you can perform the move in just one step.
To move a user directly from an on-prem Skype for Business environment to Teams only you simply have to run the move CS user commandlet in PowerShell. Alternatively you can use the Skype for Business server control panel instead. The move CS user commandlet is available for an on-prem Skype for Business management shell PowerShell window. While the exact steps and migration process are outside the scope of this course, the overall process for moving users to Teams with the move CS user command will require you to use the identity parameter to specify the user being moved. You'll need to specify sipfed.online.lync.com as the target parameter, and then specify the move to Team switch. You'll also need to use the credential parameter to specify an account with permissions on Office 365, if the account you're using doesn't have permissions in both the on-prem environment and Office 365. To use the Skype for Business server control panel to move users to Teams, select the users that you'd like to move and choose, move selected users to Teams from the action drop down.
The on-prem admin tools in Skype for Business server 2015 with CU8 and later offer the ability to notify on-prem Skype for Business users of an impending migration to Teams. Once this notification option is enabled users see a notification in their Skype for Business client that looks something like what you see on your screen. When a user clicks the try it button the teams client is launched, if it's already installed. If the teams client isn't already installed the user is directed to the web version of Teams in his browser. Enabling notifications causes the Win32 Skype for Business client to silently download the teams client so that it's available prior to moving the user. That said, this behavior can also be disabled if necessary.
So with that said, you have two options for moving users to Teams. You can use PowerShell, or you can use the existing Skype for Business control panel.
Tom is a 25+ year veteran of the IT industry, having worked in environments as large as 40k seats and as small as 50 seats. Throughout the course of a long an interesting career, he has built an in-depth skillset that spans numerous IT disciplines. Tom has designed and architected small, large, and global IT solutions.
In addition to the Cloud Platform and Infrastructure MCSE certification, Tom also carries several other Microsoft certifications. His ability to see things from a strategic perspective allows Tom to architect solutions that closely align with business needs.
In his spare time, Tom enjoys camping, fishing, and playing poker.