Monday, August 6, 2018

Cannot set users or Tenant to Teams Only upgrade mode in Teams Admin Center

Edit: 1/11/2019 - Seems that Teams Only mode is starting to appear in the admin center again. 


I've been seeing a few posts around the community that they cannot upgrade their Tenant to Teams Only mode through the admin center and at first I believed that it might be just an update that needed to take place on the back end for this ability to show up, but now I believe it's an admin center issue and the best way to set these items is through PowerShell.

At some point about a month ago I was able to set my own upgrade policy to Teams Only in the new Teams admin center UI and even had the option to set it for the tenant, but recently discovered both these options have magically vanished from the UI in the new admin center.



Wanting to set my tenant now to Teams Only mode I figured I would check PowerShell and sure enough you're able to easily do this using the Grant-CsTeamsUpgradePolicy commandlet. 


There is a great article touching over all the interoperability operations and settings at https://docs.microsoft.com/en-us/MicrosoftTeams/migration-interop-guidance-for-teams-with-skype 





If you want to set a single user set to Teams Only or one of the other upgrade policies you can by using the following. The example upgrades user@user.com to Teams Only mode. 


Grant-CsTeamsUpgradePolicy -PolicyName UpgradeToTeams -Identity user@user.com


Once ran you can look at your user and you will notice the user has the policy now assigned. (This no longer is the case, it will just show blank now, until they update the GUI to support TeamsOnly again)





To set your entire tenant to Teams Only you can use the following command

Grant-CsTeamsUpgradePolicy -PolicyName UpgradeToTeams


How to access and use these commands If you don't know how to access these Powershell commands you need to do the following. 

1. First Install the Skype for Business Online powershell module from here
2. Says a reboot is required after installation but I don't think it is, try if it doesn't work, then reboot ;). 
3. Now open powershell and run the following to connect: 
Import-Module SkypeOnlineConnector
$sfbSession = New-CsOnlineSession
Import-PSSession $sfbSession

After you enter your password to connect, you will now have access to all the commands to manage this and many other items with Skype/Teams. 





11 comments:

  1. Thanks - this worked perfectly for me.
    NOTE: Even though you set the tenant to Teams via Power-Shell it will show blank in the GUI dropdown.

    ReplyDelete
  2. I'm not having such success. I have spent the last few hours trying to wrap my head around it and I can't seem to figure it out! I've downloaded the module, imported the module into my session, enter the credentials, ran the command, and everytime I get that the cmdlet is not recognized.

    1. Running PS as Admin
    2. All prereq software is downloaded
    3. Ran Get-Module, to ensure it was in the session

    I just don't get it. Please any assitance in the matter would GREATLY be appreciated.

    ReplyDelete
    Replies
    1. we're you ever able to figure this out? Sorry don't have notifications setup on replies apparently ;(. I'd recommend taking the issue to the Tech Community, I or someone else will be able to try to figure this out for you! https://techcommunity.microsoft.com/t5/custom/page/page-id/Community-My-Dashboard

      Delete
  3. Worked perfectly and my quick test of messaging looks good. This mode is the last piece I need to convince more people to make the switch, so this is very helpful.

    ReplyDelete
  4. Hi,

    Is this going to fix the skype account entries in Teams?

    ReplyDelete
    Replies
    1. What do you mean? I would suggest starting a Teams tech community post. I and many others can help straighten it out, we monitor it closely! https://techcommunity.microsoft.com

      Delete
  5. I came across this post today as I just received my Teams desk phone and wanted to ensure inbound calls actually went to my desk phone (my tenant = my lab, so I'm my IT department).

    Couple of things I had to do to ensure all of this worked. Since I've never run the Skype PowerShell, I definitely had to install the module, but I also had to do the following:
    set-executionpolicy unrestricted
    Import-Module "C:\\Program Files\\Common Files\\Skype for Business Online\\Modules\\SkypeOnlineConnector\\SkypeOnlineConnector.psd1"

    Then I was able to to create my session and do the "Grant". Thanks for this great article!
    (yeah, I probably ought to consider setting the execution policy back to the default "commandlet")

    ReplyDelete