Microsoft Teams – Pilot tips #2

Hi there

This article will cover a crucial tip to succeed on a Microsoft Teams Alpha or Pilot phase on a project regarding to interoperability between Skype for Business Online and Microsoft Teams.

During an Alpha/Pilot phase we kept the client environment as follows:

  • Teams Upgrade mode: islands (all users that are not part of the Pilot are on islands mode “org-wide”)
  • Teams Pilot Targeted users mode: teams only


  • for users that uses only Skype they haven’t reported issues regarding to booking and joining meetings neither initiating chat, audio and video calls with Teams Pilot targeted users (teams only mode)


  • Teams pilot targeted users (on teams only mode) reported issues initiating chat, audio and video as well sharing content / desktop / app with Skype for Business users within the same organization.

We noticed that some clients on islands mode piloted Teams differently having both Skype and Teams client installed on their PCs (confusing and a lot of extra work educating users on how to use both tools).

  • all users on Skype interacting with Skype users
  • all users on Teams interacting with Teams users

Quick fix

In order to isolate the users experience pick a few users that are on islands mode and change them to Skype only mode

Get-CsOnlineUser -Identity | fl *teamsupgrade*

you should get the following

TeamsUpgradeEffectiveMode : Islands
TeamsUpgradeNotificationsEnabled : False
TeamsUpgradePolicyIsReadOnly : None
TeamsUpgradePolicy :
TeamsUpgradeOverridePolicy :

Now you can change the user to Skype for business only mode

Grant-CsTeamsUpgradePolicy -PolicyName SfBOnly -Identity

Wait up to 10 minutes and check the user TeamsUpgradeEffectiveMode

Get-CsOnlineUser -Identity | fl *teamsupgrade*

TeamsUpgradeEffectiveMode : SfBOnly
TeamsUpgradeNotificationsEnabled : False
TeamsUpgradePolicyIsReadOnly : None
TeamsUpgradePolicy : SfBOnly
TeamsUpgradeOverridePolicy :

ALERT! – This change can take up to 24 hours to replicate as per Microsoft recommendation. On our tests it took up to 12 hours to take effect.

Long Term Fix

Change org-wide upgrade to Skype Only (forcing all current / remaining users if Pilot phase it’s ongoing) to be in one side of this fence. Then you plan the waves to switch users over to Teams only mode.

  • change can be done at Teams Admin Portal or using powershel (Grant-CsTeamsUpgradePolicy -PolicyName SfBOnly)

Validating users experience

On Microsoft Teams search for the user on Skype for Business only mode and click on it

You should the see the following screen if you’ve talked to Skype user before (when it was on islands mode and all the communication was reaching its Teams and not his Skype client). In order to get the correct experience click on the link provided with the “Due to org policy changes, some chat and calling features are no longer available. Continue your conversation here” warning.

Now you got redirected to the Skype user (where all conversation will land user’s Skype client)

Check the Skype user and see the message landing on its skype client

  • Skype user can see Teams users (teams only mode) status.
  • Skype user can chat and make audio and video calls with Teams users
  • Skype user can share desktop and apps with Teams user (each user will receive a meeting invitation weather it’s from initiate from Teams or Skype to join the shared session as a meeting)

Possible issues on this scenario

  • Teams’ users may report they can’t see Skype user’s status or neither chat to them
    • Teams flat client has known issues with cache information. Please clear Teams cache to fix it
    • The quick way to test this out it’s by logging on and launch Teams on web and search for Skype user from there.

Systems Tested

  1. VDI
  2. Windows PC
  3. Web client (Opera, Google Chrome and Microsoft Edge)
  4. iOS client
  5. Fresh Windows 10 Virtual Machine on Windows 10 Hyper-v with Skype user logged on there

I hope that helps.


Check my Github repository


Thiago Beier