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.

Jeff Brown

Jeff is a Premier Field Engineer at Microsoft specializing in their Intelligent Communications platform and a PowerShell enthusiast. He holds multiple Microsoft certifications in Exchange, Skype for Business, and Office 365. You can follow Jeff on his blog at jeffbrown.tech, or feel free to contact him on Twitter at @jeffwbrown.

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 mode and the capabilities provided by each client.

Coexistence modes and available capabilities

Coexistence modes and available capabilities

Coexistence modes are applicable for both users homed in Skype for Business Online and on-premises or hybrid scenarios. However, in order to move to Teams Only mode, the user’s corresponding Skype for Business account must be homed into Skype for Business Online. When using one of the other coexistence modes, there are also other advantages to having the Skype for Business account already in Office 365 in relation to interop and federation, but that is a topic for a different article.

So how are these modes managed? In the modern Microsoft Teams & Skype for Business Admin Center (https://admin.teams.microsoft.com), navigate to Org-wide settings > Teams upgrade. Here you can control settings for the entire tenant, and options may vary from tenant to tenant depending on where they are in the feature release cycle. First, there is the coexistence modes drop-down menu, and whether you want to notify users that an upgrade to Teams is coming. This upgrade notification feature is displayed in the Skype for Business client when they log in. Notice the only options in the admin center for modes are Islands, Skype for Business Only, and Teams Only. As previously mentioned, the other two are not available yet.

Currently available coexistence modes

Currently available coexistence modes

Other options include app preferences, such as you want users to join Skype for Business meetings once they move to Teams Only mode. They can use either their existing Skype for Business client to join meetings, or use the Skype Meetings App if the desktop client has been removed.

Skype for Business meeting join options

Skype for Business meeting join options

Finally, if you are preparing end users for Teams Only mode, you can prepare Windows-based systems to download the Teams client in the background in preparation for migration.

Download Teams app option

Download Teams app option

While the above sets the coexistence mode for everyone in the tenant, you can set the mode on a per user basis. This allows migrating cohorts of users from one mode to another. In the admin center, navigate to Users and search or select the user to modify. In the user account options, there is a section for the Teams upgrade mode and whether you want to notify the user that a change is upcoming.

Individual user Teams upgrade modes

Individual user Teams upgrade modes

As mentioned previously, there are advantages to having the Skype for Business account already homed in Office 365 when using coexistence modes. However, sometimes there are situations when you need to keep the account in your on-premises environment. Fortunately, this is not going to prevent you from using the modern Teams meeting experience. Announced at Microsoft Ignite 2018, there will be a future capability where on-premises users can take advantage of Microsoft Teams meetings. For more information, check out BRK3124 – How Skype for Business on-premises customers can take advantage of Microsoft Teams meetings.

Are you an IT pro? Apply for membership!

Your question was not answered? Ask in the forum!

1+
Share
2 Comments
  1. michael 9 months ago

    Thanks Jeff, for that great article.

    Do you see any way to use Teams saving e.g. chats conversiantions on-prem?

    To me it looks like SfB on-prem will disapear in the future, while a lot companies try to hold there data on premise.

    1+

    • Author
      Jeff Brown 5 months ago

      Hi Michael, apologies for not seeing this comment sooner. Right now this is not a native way to store chats/conversations on-premises. That data is initially stored in the chat service, then copied to the Exchange mailbox for search/eDiscovery purposes. Even if the mailbox is on-premises, it is stored in a "shadow mailbox" in O365.

      If you have developer capabilities, maybe a bot or other add-in to Teams could read data and funnel it to an on-premises database. Don't know if this is possible off the top of my head but something worth investigating. There could also be other third-party solution like Smarsh that may have this capability.

      1+

      Users who have LIKED this comment:

      • avatar

Leave a reply

Your email address will not be published. Required fields are marked *

*

© 4sysops 2006 - 2019

CONTACT US

Please ask IT administration questions in the forums. Any other messages are welcome.

Sending

Log in with your credentials

or    

Forgot your details?

Create Account