Set-CsTeamInteropPolicy (do not exists)
Upgrade Journey to TEAMS
The cmdlet Set-CsTeamsInteropPolicy has never existed. Previously, if you wanted to create a new custom Teams Interop policy you would have to use the New-CsTeamsInteropPolicy. But now also the New-CsTeamsInteropPolicy cmdlet has been deprecated and it is not possible to create custom Teams Interop Policies anymore. Additionally, Microsoft is in the process of retiring TeamsInteropPolicy and you need to use the pre-canned instances moving forward:
Here the answer from Microsoft with a similar question about custom Teams Interop policies:
"There is no need to create a new instance of TeamsInteropPolicy. All the necessary instances are already created. Also, we are retiring TeamsInteropPolicy and at this point only 3 instances of TeamsInteropPolicy are supported to be granted.
Going forward TeamsUpgradePolicy replaces TeamsInteropPolicy.
During the transition, customers should set both InteropPolicy and UpgradePolicy."
You can see these answers I got, at the comments and questions section at the very end of this article: https://docs.microsoft.com/en-us/microsoftteams/configuring-teams-calling-quickstartguide
NOTE:Therefore, remember you will NOT be able to use Set-TeamsUpgradePolicy, after your tenant was "migrated". So Teams has become your only collab tool
Example 1: Grant Policy to an individual user
PS C:\> Grant-CsTeamsUpgradePolicy -PolicyName UpgradeToTeams -Identity firstname.lastname@example.org
The above cmdlet assigns the "UpgradeToTeams" policy to user Mike@domain.com. This effectively upgrades the user to Teams only mode.
Example 2: Grant Policy to the entire tenant
PS C:\> Grant-CsTeamsUpgradePolicy -PolicyName SfBOnly
To grant a policy to all users in the org (except any that have an explicit policy assigned), omit the identity parameter.
Post a Comment