Microsoft Teams will eventually become the standard collaboration tool for Office 365, replacing Skype for Business Online. In the meantime, you may need to manage how your end users will use both products, as well as how to transition fully to Teams. This article will discuss what options are available to you, how to manage this on a per-user and tenant basis, and what is on the roadmap.

Since Microsoft Teams and Skype for Business Online have some overlapping functionality (chat, calling, meetings), Microsoft provides a couple of ways to manage the migration to Microsoft Teams, as well as the interoperability with legacy Lync/Skype for Business. This is managed through coexistence modes determined by a TeamsUpgradePolicy. Assigning a coexistence mode to a user or the tenant will determine how incoming calls and chats are routed, as well as where users can schedule their meetings.

The first coexistence mode is Islands. This mode treats Skype for Business and Microsoft Teams like they are two separate products. The end user can use all functionality in both products, such as calling, chatting, and scheduling meetings. An incoming call from other Teams or Skype for Business users will land in the end user’s same client. Inside of Teams, the user will have access to teams and channel functionality. This is usually a good coexistence mode to start with if the end user can understand the difference between the products and can handle having the same functionality in both. Starting in this mode can drive Team adoption more quickly.

The next mode is Skype for Business Only. All incoming calls and chat messages are routed to Skype for Business, where the user can schedule meetings. However, this mode is not currently enforced, as it will not remove any access to Teams for Teams and channels access.

Next is Teams Only mode. As its name suggests, the end user will use only Teams for calling, chatting, and scheduling meetings. When this mode is applied, the user is considered upgraded to Teams, as they will no longer use Skype for Business. However, this mode does not prevent the end user from joining Skype for Business meetings, as they may still receive invitations from coworkers or external partners. There is also an option in the admin portal that will determine if the user can join these meetings via the Skype desktop client or the Skype meetings app.

The last two modes are currently not available in the admin portal, as they do not yet have the components in the service to be enforced. The first is Skype for Business with Teams collaboration. As the name suggests, Skype for Business with Teams collaboration will give Skype for Business chatting, calling, and meeting scheduling abilities while Teams is only available with teams and channels.

Users will not have the ability to use Teams for calling, chatting, or scheduling meetings, and these options will be removed in the Teams client. If the overlapping functionality of calling and chatting with the two clients might confuse your users, this would be a good mode to start with, as it will distinguish each client with only certain capabilities, without overlap. The concepts of teams and channels can be explored in Teams without worrying about chatting, calling, and meetings.

The second currently unavailable mode is Skype for Business with Teams Collaboration and Meetings, and it takes the previous mode a step further by moving the ability to schedule meetings to Teams. This gives the user a first-class meeting experience in the Teams client, while still using Skype for Business for chatting and calling. Each client is still only responsible for specific tasks without any overlap between the two. Chat is available in the Teams client, but only during meetings, and is not available for 1-to-1 chats.

To clear up what how each mode works, here is a visual diagram that shows each mod