Skip to content

Commit 49008e7

Browse files
authored
Update Grant-CsTeamsInteropPolicy.md
Fixed formatting issue (code block in Description section) that was causing build errors.
1 parent 68b1e74 commit 49008e7

File tree

1 file changed

+3
-10
lines changed

1 file changed

+3
-10
lines changed

skype/skype-ps/skype/Grant-CsTeamsInteropPolicy.md

Lines changed: 3 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -26,14 +26,10 @@ Grant-CsTeamsInteropPolicy [-PassThru] [-Confirm] [[-PolicyName] <Object>] [[-Id
2626
IMPORTANT: TeamsInteropPolicy has been replaced by TeamsUpgradePolicy. It is no longer honored by the system, except if TeamsUpgradePolicy has mode=Legacy. Legacy mode is being deprecated. Customers that are still using Legacy mode should update their configurations to use a mode other than Legacy. Granting mode=Legacy is now blocked by default, although admins can override this using -Force for the time being. Eventually, the -Force switch will be removed and granting mode=Legacy will not be possible.
2727

2828
Any customers still using Legacy mode must ensure the following:
29-
- The global policy must have CallingDefaultClient=ChatDefaultClient, and AllowEndUserClientOverride must be false. If you customized the built-in global policy, undo this by running `Remove-CsTeamsInteropPolicy`. This will remove the tenant-specific global policy and revert back to the system-wide built-in policy (which cannot be removed). Use the following syntax:
30-
31-
```
32-
Remove-CsTeamsInteropPolicy -Identity Global
33-
```
3429

35-
- If TeamsInteropPolicy is explicitly assigned to any users, one of these three built-in instances for which CallingDefaultClient = ChatDefaultClient, and for which AllowEndUserClientOverride = false. The other instances are no longer valid configurations, are not supported, and will soon be removed from the system. The valid instances are:
30+
- The global policy must have CallingDefaultClient=ChatDefaultClient, and AllowEndUserClientOverride must be false. If you customized the built-in global policy, undo this by running `Remove-CsTeamsInteropPolicy`. This will remove the tenant-specific global policy and revert back to the system-wide built-in policy (which cannot be removed). Use the following syntax: `Remove-CsTeamsInteropPolicy -Identity Global`.
3631

32+
- If TeamsInteropPolicy is explicitly assigned to any users, one of these three built-in instances for which CallingDefaultClient = ChatDefaultClient, and for which AllowEndUserClientOverride = false. The other instances are no longer valid configurations, are not supported, and will soon be removed from the system. The valid instances are:
3733

3834
**Identity: DisallowOverrideCallingDefaultChatDefault**
3935
**AllowEndUserClientOverride: False**
@@ -50,10 +46,7 @@ Remove-CsTeamsInteropPolicy -Identity Global
5046
**CallingDefaultClient: Teams**
5147
**ChatDefaultClient: Teams**
5248

53-
54-
Use the following cmdlet syntax, where $policy is one of the above values of identity:
55-
`Grant-CsTeamsInteropPolicy -PolicyName $policy -Identity $SipAddress`
56-
49+
Use the following cmdlet syntax, where $policy is one of the above values of identity: `Grant-CsTeamsInteropPolicy -PolicyName $policy -Identity $SipAddress`.
5750

5851
For comprehensive documentation on this policy and its settings, see [Microsoft Teams and Skype for Business Interoperability](https://docs.microsoft.com/MicrosoftTeams/teams-and-skypeforbusiness-interoperability).
5952

0 commit comments

Comments
 (0)