While it might be tempting to wait for a deadline, there’s less and less reason to postpone your Skype upgrade to Teams. Microsoft Teams brings capabilities that your users already enjoy with Skype, like messaging, calling, managing contacts, or hosting online meetings. But it goes beyond to deliver all of this in a single hub for teamwork that can connect to your favourite apps and enhance productivity. Of course, some of the biggest differences between Skype and Teams are under the covers. Teams is built on a modern platform for audio and video and uses the latest cloud infrastructure on Azure for optimised global coverage, which brings several performance and networking benefits. For example, meetings get started faster and user ratings show that call quality in Teams is superior. For an IT Admin this means you can expect fewer helpdesk calls related to meeting experiences and calling.
Also, because Teams is cloud-native, it benefits from ongoing innovation such as whiteboard sharing, background blur and in-line translation, which allow for a more inclusive collaboration experience. Best of all for IT, Microsoft gives you a comprehensive admin experience for day to day management, security and compliance.
Another good reason to start your Skype upgrade to Teams now is that whether you are coming from Skype for Business Online or Skype for Business Server on-premises, with or without Enterprise voice, we have a number of robust options to help in your journey to Teams. If you follow our guidance as you make the transition, you trust that no user will miss a chat message and meetings will always be accessible either from Skype or Teams. Here are some pointers on the top things to get started:
1. You may not need to do anything at all:
For smaller organisations that do not have hybrid or on-premises dependencies and are using Skype for Business Online only, Microsoft offers an automated upgrade for your Office 365 tenant. Microsoft will notify you in advance in the message center and via email if your tenant has been selected for this automated upgrade. This is a great benefit if you don’t have dedicated IT staff.
2. Upgrading from Skype to Teams is more than just a technical upgrade:
Aside from specific architectural considerations, the rate at which users adopt Teams will impact your timeline and influence the success of your upgrade the most. Managing change across your users is imperative to any successful adoption strategy. Your roll out team needs to extend beyond IT to incorporate the right sponsors and stakeholders such as executive sponsors; a project lead to help instigate and keep track of training and roll-out milestones; and various champions that can share user feedback.
3. Microsoft Teams comes with built-in upgrade options and interoperability:
This applies whether you are coming from Skype for Business Online, Skype for Business Server on-premises, have a hybrid configuration, or have an enterprise voice plan.
4. Microsoft allow you to incrementally get your organisation on board:
Skype and Teams can coexist during your upgrade. This way, while you gradually onboard users to Teams, you have flexibility to ensure the pre-requisites are in place with SharePoint, OneDrive, Exchange, Azure AD synchronisation, and network optimisation requirements.
5. There are two main upgrade paths to choose from:
1. The first path has overlapping capabilities across Skype and Teams and is enabled with “Islands mode”. This is our recommended path to start with. Note that by default, this will be the coexistence mode for your tenant. Because chat, meetings, and VoIP calling are available in both clients, your users can get familiar with Teams while still being able to access all the features from Skype at the same time.
2. The second path is where you can pick select capabilities selecting from two interoperability modes. “Skype for Business with Teams Collab and Meetings” mode, also known as our “meetings-first approach”, allows to have chat and calls initiated and received in Skype while scheduling and collaboration capabilities are handled by Teams. Otherwise, you can keep chats, calls and meetings in Skype while collaboration capabilities remain unique to Teams with team conversations, file sharing, and co-authoring enabled with “Skype for Business with Teams Collab” mode.
3. Once your organization is ready, you can turn on Teams only mode, which means all incoming calls and chats land in the Teams client. In fact, if you have PSTN calling configured, users will receive all incoming voice calls in Teams, and PSTN connectivity is enabled with a calling pad that lights up in Teams.
6. You can mix and match your coexistence modes:
Modes can be set organisation-wide or for specific users in the Teams Admin center or using PowerShell. You’ll want to use PowerShell if you have a large number of users that you want to assign specific modes to, and we have a range of cmdlets that enable you to perform bulk actions, such as setting modes with or without user notifications. This allows you for example to have subsets of users still on Skype for Business with select capabilities, or on overlapping capabilities, or just Teams only based on the upgrade strategy for your organisation.
7. A hybrid configuration is required if you are coming from Skype for Business Server:
User accounts in Skype for Business Server need to also be present in Skype for Business Online for interoperability with Teams to work. If you are already using Office 365, you probably have this in place already. Also, a hybrid configuration with Skype for Business Online needs to be in place to ensure that chat and calling traffic between Skype and Teams is automatically transferred via our gateway service. You’ll need to use PowerShell for that.
8. There are two voice options to enable integration between your PSTN or Voice over IP services:
- A Microsoft calling plan: If you are using a phone system and a Microsoft calling plan (such as Business Voice) where Microsoft provides your phone numbers directly, once you enable Teams only mode traffic is routed to Teams automatically, or
- Direct Routing, which can be configured in a few ways.. If you have an on-premises Session Border Controller device that connects directly with your PSTN trunk line from your telecommunications provider or ISP, you’ll need to route the connection to your Microsoft 365 tenant. Or, if your direct Routing is done off-site by your telecommunications provider via their Session Border Controller, you will need to work with them to direct PSTN traffic to your Microsoft 365 tenant.
9. There are tools to help you track organisational readiness:
Your can track Microsoft Teams usage in your environment with built-in usage reports and dashboards available in both the Microsoft 365 admin center and the Teams Admin Center. We also recommend circling back with your onboarding team and conducting regular end-user surveys using Advisor for Teams. this will help you to capture user feedback and sentiment and ensure you have a comprehensive perspective on the readiness of your organisation to upgrade to Teams.
10. Your users' contacts and upcoming meetings can also be upgraded to Teams:
The migration of your data and meetings, like interop, for the most part happens behind the scenes. There are options to automatically upgrade upcoming Skype for Business meetings across all your users’ calendars to Teams