Grant-CsTeamsUpgradePolicy

Syntax

Grant-CsTeamsUpgradePolicy
     [[-Identity] <String>]
     [-MigrateMeetingsToTeams <Boolean>]
     [-PassThru]
     [[-PolicyName] <String>]
     [-MsftInternalProcessingMode <String>]
     [<CommonParameters>]

Grant-CsTeamsUpgradePolicy
     [-MigrateMeetingsToTeams <Boolean>]
     [-PassThru]
     [[-PolicyName] <String>]
     [-MsftInternalProcessingMode <String>]
     [-Force]
     [-Global]
     [<CommonParameters>]

Grant-CsTeamsUpgradePolicy
     [-MigrateMeetingsToTeams <Boolean>]
     [-PassThru]
     [[-PolicyName] <String>]
     [-MsftInternalProcessingMode <String>]
     -Group <String>
     [-Rank <Int32>]
     [<CommonParameters>]

Description

TeamsUpgradePolicy allows administrators to manage the transition from Skype for Business to Teams. As an organization with Skype for Business starts to adopt Teams, administrators can manage the user experience in their organization using the concept of coexistence "mode". Mode defines in which client incoming chats and calls land as well as in what service (Teams or Skype for Business) new meetings are scheduled in. Mode also governs what functionality is available in the Teams client. Finally, prior to upgrading to TeamsOnly mode administrators can use TeamsUpgradePolicy to trigger notifications in the Skype for Business client to inform users of the pending upgrade.

This cmdlet enables admins to apply TeamsUpgradePolicy to either individual users or to set the default for the entire organization.

NOTE: Earlier versions of this cmdlet used to support -MigrateMeetingsToTeams option. This option is removed in later versions of the module. Tenants must run Start-CsExMeetingMigration. See Start-CsExMeetingMigrationService.

Microsoft Teams provides all relevant instances of TeamsUpgradePolicy via built-in, read-only policies. The built-in instances are as follows:

Identity	Mode	NotifySfbUsers	Comments
Islands	Islands	False	Default configuration. Allows a single user to evaluate both clients side by side. Chats and calls can land in either client, so users must always run both clients.
IslandsWithNotify	Islands	True	Same as Islands and it adds a banner in the Skype for Business client informing the user that Teams will soon replace Skype for Business.
SfBOnly	SfBOnly	False	Calling, chat functionality and meeting scheduling in the Teams app are disabled.
SfBOnlyWithNotify	SfBOnly	True	Same as SfBOnly and it adds a banner in the Skype for Business client informing the user that Teams will soon replace Skype for Business.
SfBWithTeamsCollab	SfBWithTeamsCollab	False	Calling, chat functionality and meeting scheduling in the Teams app are disabled.
SfBWithTeamsCollabWithNotify	SfBWithTeamsCollab	True	Same as SfBWithTeamsCollab and it adds a banner in the Skype for Business client informing the user that Teams will soon replace Skype for Business.
SfBWithTeamsCollabAndMeetings	SfBWithTeamsCollabAndMeetings	False	Calling and chat functionality in the Teams app are disabled.
SfBWithTeamsCollabAndMeetingsWithNotify	SfBWithTeamsCollabAndMeetings	True	Same as SfBWithTeamsCollabAndMeetings and it adds a banner in the Skype for Business client informing the user that Teams will soon replace Skype for Business.
UpgradeToTeams	TeamsOnly	False	Use this mode to upgrade users to Teams and to prevent chat, calling, and meeting scheduling in Skype for Business.
Global	Islands	False

When users are in any of the Skype for Business modes (SfBOnly, SfBWithTeamsCollab, SfBWithTeamsCollabAndMeetings), calling and chat functionality in the Teams app are disabled (but chat in the context of a Teams meeting is still allowed). Similarly, when users are in the SfBOnly or SfBWithTeamsCollab modes, meeting scheduling is disabled. For more details, see Migration and interoperability guidance for organizations using Teams together with Skype for Business.

The Grant-CsTeamsUpgradePolicy cmdlet checks the configuration of the corresponding settings in TeamsMessagingPolicy, TeamsCallingPolicy, and TeamsMeetingPolicy to determine if those settings would be superceded by TeamsUpgradePolicy and if so, an informational message is provided in PowerShell. It is not necessary to set these other policy settings. This is for informational purposes only. Below is an example of what the PowerShell warning looks like:

Grant-CsTeamsUpgradePolicy -Identity [email protected] -PolicyName SfBWithTeamsCollab

WARNING: The user [email protected] currently has enabled values for: AllowUserChat, AllowPrivateCalling, AllowPrivateMeetingScheduling, AllowChannelMeetingScheduling, however these values will be ignored. This is because you are granting this user TeamsUpgradePolicy with mode=SfBWithTeamsCollab, which causes the Teams client to behave as if they are disabled.

Examples

Example 1: Grant Policy to an individual user

PS C:\> Grant-CsTeamsUpgradePolicy -PolicyName UpgradeToTeams -Identity [email protected]

The above cmdlet assigns the "UpgradeToTeams" policy to user [email protected]. This effectively upgrades the user to Teams only mode. This command will only succeed if the user does not have an on-premises Skype for Business account.

Example 2: Remove Policy for an individual user

PS C:\> Grant-CsTeamsUpgradePolicy -PolicyName $null -Identity [email protected]

The above cmdlet removes any policy changes made to user [email protected] and effectively Inherits the global tenant setting for teams Upgrade.

Example 3: Grant Policy to the entire tenant

PS C:\> Grant-CsTeamsUpgradePolicy -PolicyName SfBOnly -Global

To grant a policy to all users in the org (except any that have an explicit policy assigned), omit the identity parameter. If you do not specify the -Global parameter, you will be prompted to confirm the operation.

Example 4 Get a report on existing TeamsUpgradePolicy users (Screen Report)

Get-CSOnlineUser | select UserPrincipalName, teamsupgrade*

You can get the output on the screen, on CSV or Html format. For Screen Report.

Example 5 Get a report on existing TeamsUpgradePolicy users (CSV Report)

$objUsers = Get-CSOnlineUser | select UserPrincipalName, teamsupgrade*
$objusers | ConvertTo-Csv -NoTypeInformation | Out-File "$env:USERPROFILE\desktop\TeamsUpgrade.csv"

This will create a CSV file on the Desktop of the current user with the name "TeamsUpgrade.csv"

Example 6 Get a report on existing TeamsUpgradePolicy users (HTML Report)

$objUsers = Get-CSOnlineUser | select UserPrincipalName, teamsupgrade*
$objusers | ConvertTo-Html | Out-File "$env:USERPROFILE\desktop\TeamsUpgrade.html"

After running these lines will create an HTML file on the Desktop of the current user with the name "TeamUpgrade.html"

Example 7 Get a report on existing TeamsUpgradePolicy users (CSV Report - Oneliner version)

Get-CSOnlineUser | select UserPrincipalName, teamsupgrade* | ConvertTo-Csv -NoTypeInformation | Out-File "$env:USERPROFILE\desktop\TeamsUpgrade.csv"

This will create a CSV file on the Desktop of the current user with the name "TeamsUpgrade.csv"

Example 8 Get a report on existing TeamsUpgradePolicy users (HTML Report - Oneliner Version)

Get-CSOnlineUser | select UserPrincipalName, teamsupgrade* | ConvertTo-Html | Out-File "$env:USERPROFILE\desktop\TeamsUpgrade.html"

After running these lines will create an HTML file on the Desktop of the current user with the name "TeamUpgrade.html"

Parameters

-Force

-Global

-Group

-Identity

-MigrateMeetingsToTeams

-PassThru

-PolicyName

-Rank

-Tenant

Inputs

Microsoft.Rtc.Management.AD.UserIdParameter

Outputs

System.Object

Related Links

• Migration and interoperability guidance for organizations using Teams together with Skype for Business
• Using the Meeting Migration Service (MMS)
• Coexistence with Skype for Business
• Get-CsTeamsUpgradeConfiguration
• Set-CsTeamsUpgradeConfiguration
• Get-CsTeamsUpgradePolicy