Microsoft Teams

Skype for Business Online is retiring – What does it mean?


Soon July 31st, 2021, will be upon us, as the official Skype for Business Online (SfBO) retirement day looms closer. So, what does that really mean? It means just that, SfBO will not be available in Microsoft 365 anymore. Teams Only mode will be the only option for users homed in Microsoft 365.

Assisted Transitions from Microsoft

Microsoft will offer assisted transitions for your tenant during specified periods. To find the date specified for you, navigate over to the Teams admin center. During that time, Microsoft will help flip your tenant to Teams Only mode for all users homed in Microsoft 365.

After that period, all other modes like IslandsMeeting First, or Meeting and collaboration will not be available options for your users, as these modes were just steps along the way to Teams Only mode.

Figure 1: Microsoft Teams Upgrade Message.


If necessary, you do not have to wait for Microsoft to help you with the transition. There are ways to flip your tenant over to Teams Only mode yourself, and those steps are outlined below:

  1. Validate DNS records for all enabled SIP domains.
  2. Make sure SharedSipAddressSpace is set to $False.
  3. Set the global TeamsUpgradePolicy to Teams Only mode.
  4. Make sure users with other TeamsUpgradeEffectiveModes are also updated.
  5. Plan to uninstall the Skype for Business (SfB) client.
  6. If you are in Exchange hybrid mode, consider completing the migration to Exchange Online before going to Teams Only mode.

Before you can set the TeamsUpgradePolicy to Teams Only mode, you need to comb through all active SIP domains and make sure the DNS exists and points to SfBO. If you’ve verified domains in your tenant, but are not using them for SfBO and Teams, you can disable them for this functionality by running the Disable-CsOnlineSipDomain cmdlet. This is a straightforward way to determine if you have any verified domains in your tenant that are SIP-enabled, but not in use. Just make sure you have the latest Teams PowerShell module to perform the below PowerShell operations first, since the SfBO PowerShell module is decommissioned.

For the remaining domains that are SIP enabled, you need to make sure the following DNS records exist:

  • _sip._tls SRV record handles sign in for the SfB client
  •  _sipfederationtls handles federation in Microsoft Teams
  • CNAME handles sign for the SfB client and specifically the SfB mobile client
  • CNAME handles sign in for the SfB client

When these records are implemented, and all are pointing to Microsoft 365, there is one more setting you can triple check which is the SIP shared namespace setting for your tenant. If this setting is set to True, it means that at some point you had a Hybrid SfB setup and never turned it off. Here’s how you check it and set it to False using the Teams PowerShell module:

You are now ready to flip the tenant with the below cmdlet:

If your users explicitly have assigned modes different from the tenant standard, then you need to set these users to Teams Only mode. The Grant-CsTeamsUpgradePolicy article has some good examples of how you can identify all users and their TeamsUpgradeEffectiveMode. From there you can create a list of users where you can use the New-CsBatchPolicyAssignmentOperation to bulk assign the Teams Only mode policy.

Do you need the Skype client after you have moved to Teams Only mode?

It depends. After you’ve moved all users to Teams, the client changes to a meeting mode client where you will find your SfB meetings and Teams meetings. Chat and calling are moved to and handled by Teams. A reason for many organizations to hold on to the SfB client in the past has been:

  • Federation, chat, audio call, and video call with non-guest users
  • Group chat with internal and federated participants
  • Escalate a federated audio call to a screen sharing call

All the above works fine in Teams now, with the latest addition being group chats where you can combine internal and federated users. The requirement is that both sides are in Teams Only mode. If you are collaborating with someone still on SfBS, then you must invite them to a meeting where you join via the SfB web client, or they can join a Teams meeting you invite them to.

Figure 2: Teams Only mode in the SfB Client.

Unless you are participating in a lot of externally invited SfB Server calls, my recommendation is to uninstall the SfB client. Reason being, we’ve seen that the SfB client can sign in and interfere with the Teams audio device and sometimes reinitialize the device driver and hang up your Teams call. It turns out that it’s not so easy to just uninstall the SfB client, since it is part of the Office installation. This means that Office needs to be re-deployed in your organization without the Skype client as part of the deployment package. Until you can initiate the redeployment, consider setting the SfB client to not start at logon.

Where your Exchange mailbox is, matters for success

To achieve the best results when moving over to Teams, ensure you open your Exchange mailbox in Exchange Online. In that instance, the Meeting Migration Service will initiate and convert all SfB meetings to Teams meetings. However, you should be aware that re-invitations will generate for external participants, but internally these updated invitations are suppressed.

If your mailbox is still in Exchange Server on-premises, then you’ll require a hybrid setup so you can assign an Exchange license to the user. By doing it this way the Teams client can still access the calendar and schedule meetings, but they will not automatically be updated from Skype to Teams meetings.

You’ll need to plan the move accordingly and communicate to users that they will need to send updated meeting invitations manually. The good news with moving to Teams though is that all Teams clients do not connect directly to your on-premises mailbox. They connect via Microsoft 365, which means you can harden your on-premises environment and limit the number of IP ranges able to connect to the servers, and no calendar data is cashed in Microsoft 365 when using Teams.

Skype for Business Server (SfBS) Hybrid will still work with all modes

As explained earlier in this article, DNS needs to point online to move your tenant to Teams Only mode. If DNS is pointing on-premises in a hybrid SfBS setup, you can still have users in Island ModeMeeting First, or Meeting First with Collaboration, which I’ve verified with Microsoft. This emphasizes that only SfBO is being retired and not the Skype ecosystem itself. The moment you migrate a user online, then Teams Only mode will be the only option for that user. If you do not migrate the user, then you can choose modes.

Speaking of migration, if you haven’t done so already, you’ll need to install the Teams PowerShell Module on your SfBS Front End servers. Microsoft retired the SfBO PowerShell module and connection point in April 2021, which means if you had a migration routine going or you at some point tested a migration before that date, it will now fail.

The SfBO PowerShell cmdlets are now part of the Teams PowerShell module, and that is why you need to install the module and use it when migrating. A caveat of this scenario is that the SfB Control Panel will also fail to connect to SfBO since it used the SfBO PowerShell module in the backend. This means that you can only migrate users using the Teams PowerShell module now.

Closing note

It’s important to understand that with SfBO being retired, if your users are homed in Microsoft 365 and you’ve already migrated all your users, Teams will be their only option after July 31st, 2021.

At the time of writing, it’s required to assign both the SfBO and Teams license to all users, however, that may change over time. And finally, make sure you go through all verified SIP-enabled domains and add the SfB DNS records to ensure a smooth transition. I hope this article provided some clarity around what the SfB retirement means for you and your users.

Source Practical 365

Chioma Ugochukwu

The author Chioma Ugochukwu

Leave a Response