Skip to content

Commit 6d8ab95

Browse files
kenwithkenwith
authored
Merge pull request MicrosoftDocs#680 from nsshommo/nasim
Adding Notes
2 parents 2649d36 + d1f68fd commit 6d8ab95

File tree

3 files changed

+160
-11
lines changed

3 files changed

+160
-11
lines changed

‎skype/skype-ps/skype/Get-CsTeamsInteropPolicy.md

Lines changed: 55 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -9,15 +9,15 @@ schema: 2.0.0
99

1010
## SYNOPSIS
1111

12-
Determines how calls are routed between Skype for Business and Microsoft Teams. This cmdlet s typically used by organizations that have users on both Skype for Business and Microsoft Teams and want to configure how calls are handled in their organization.
12+
This cmdlet Determines how calls are routed between Skype for Business and Microsoft Teams. This cmdlet s typically used by organizations that have users on both Skype for Business and Microsoft Teams and want to configure how calls are handled in their organization.
1313

1414

1515
Note: This document is provided for early evaluation of Calling Plans support for Microsoft Teams. TeamsInteropPolicy does not currently respect the policy’s chat settings and the current implementation may change in the future.
1616

17+
`Get-CsTeamsInteropPolicy \[\[-Identity\] \<XdsIdentity\>\] \[-Tenant \<guid\>\] \[-LocalStore\] \[\<CommonParameters\>\]`
1718

18-
Get-CsTeamsInteropPolicy \[\[-Identity\] \<XdsIdentity\>\] \[-Tenant \<guid\>\] \[-LocalStore\] \[\<CommonParameters\>\]
19+
`Get-CsTeamsInteropPolicy \[-Tenant \<guid\>\] \[-Filter \<string\>\] \[-LocalStore\] \[\<CommonParameters\>\]`
1920

20-
Get-CsTeamsInteropPolicy \[-Tenant \<guid\>\] \[-Filter \<string\>\] \[-LocalStore\] \[\<CommonParameters\>\]
2121

2222
## SYNTAX
2323

@@ -26,6 +26,57 @@ Get-CsTeamsInteropPolicy [-LocalStore] [[-Identity] <Object>] [-Tenant <Object>]
2626
```
2727

2828
## DESCRIPTION
29+
30+
Important:
31+
32+
TeamsInteropPolicy is being replaced by TeamsUpgradePolicy. During the transition, some components will honor TeamsInteropPolicy while others honor TeamsUpgradePolicy. Therefore, use of these 2 policies must be coordinated during the transition. After transition is complete, TeamsInteorpPolicy will be removed. To prepare for these upcoming changes, customers should do the following:
33+
34+
Ensure users with TeamsInteropPolicy are assigned only one of these 3 built-in instances for which CallingDefaultClient = ChatDefaultClient, and for which AllowEndUserClientOverride = false. The other instances are no longer valid configurations and will not be supported.
35+
36+
The valid instances are:
37+
38+
39+
**Identity: DisallowOverrideCallingDefaultChatDefault**
40+
**AllowEndUserClientOverride: False**
41+
**CallingDefaultClient: Default**
42+
**ChatDefaultClient: Default**
43+
44+
**Identity: DisallowOverrideCallingSfbChatSfb**
45+
**AllowEndUserClientOverride: False**
46+
**CallingDefaultClient: Sfb**
47+
**ChatDefaultClient: Sfb**
48+
49+
**Identity: DisallowOverrideCallingTeamsChatTeams**
50+
**AllowEndUserClientOverride: False**
51+
**CallingDefaultClient: Teams**
52+
**ChatDefaultClient: Teams**
53+
54+
55+
Use the following cmdlet syntax, where $policy is one of the above values of identity:
56+
`Grant-CsTeamsInteropPolicy -PolicyName $policy -Identity $SipAddress`
57+
58+
59+
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:
60+
Remove-CsTeamsInteropPolicy -Identity Global
61+
62+
Grant TeamsInteropPolicy and TeamsUpgradePolicy together as noted below to manage users:
63+
64+
- Coordinate granting of TeamsUpgradePolicy and TeamsInteropPolicy:
65+
66+
67+
**Grant instance of TeamsUpgradePolicy using mode: Islands**
68+
**Grant instance of TeamsInteropPolicy: DisallowOverrideCallingDefaultChatDefault**
69+
70+
**Grant instance of TeamsUpgradePolicy using mode: SfBonly, SfBWithTeamsCollab**
71+
**Grant instance of TeamsInteropPolicy: DisallowOverrideCallingSfbChatSfb**
72+
73+
**Grant instance of TeamsUpgradePolicy using mode: TeamsOnly**
74+
**Grant instance of TeamsInteropPolicy: DisallowOverrideCallingTeamsChatTeams**
75+
76+
77+
In particular, if you grant the TeamsUpgradePolicy instance “UpgradeToTeams” (Mode =TeamsOnly) to any user, you must also grant the DisallowOverrideCallingTeamsChatTeams instance of TeamsInteropPolicy to ensure the user can receive chats and calls.
78+
79+
2980
Interoperability (interop for short) enables Skype for Business and Teams users to chat and call with one another, ensuring that communications remain fluid across your organization.
3081
This policy helps IT pros manage the adoption of Teams by determining how to route calls across apps and whether to enable users to choose which app to use for calling.
3182
Teams interop policy can be defined at the tenant or per-user level.
@@ -37,7 +88,7 @@ For comprehensive documentation on this policy and it’s settings, see [Microso
3788

3889
## EXAMPLES
3990

40-
### Example 1
91+
### -------------------------- Example 1 --------------------------
4192
```
4293
PS C:\> {{ Add example code here }}
4394
```
@@ -130,7 +181,6 @@ Accept wildcard characters: False
130181
131182
### None
132183
133-
134184
## OUTPUTS
135185
136186
### System.Object

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

Lines changed: 52 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,8 @@ schema: 2.0.0
88
# Grant-CsTeamsInteropPolicy
99

1010
## SYNOPSIS
11-
Determines how calls are routed between Skype for Business and Microsoft Teams. This cmdlet s typically used by organizations that have users on both Skype for Business and Microsoft Teams and want to configure how calls are handled in their organization.
11+
12+
This cmdlet determines how calls are routed between Skype for Business and Microsoft Teams. This cmdlet s typically used by organizations that have users on both Skype for Business and Microsoft Teams and want to configure how calls are handled in their organization.
1213

1314
Note: This document is provided for early evaluation of Calling Plans support for Microsoft Teams. TeamsInteropPolicy does not currently respect the policy’s chat settings and the current implementation may change in the future.
1415

@@ -22,6 +23,56 @@ Grant-CsTeamsInteropPolicy [-PassThru] [-Confirm] [[-PolicyName] <Object>] [[-Id
2223
```
2324

2425
## DESCRIPTION
26+
27+
Important:
28+
29+
TeamsInteropPolicy is being replaced by TeamsUpgradePolicy. During the transition, some components will honor TeamsInteropPolicy while others honor TeamsUpgradePolicy. Therefore, use of these 2 policies must be coordinated during the transition. After transition is complete, TeamsInteorpPolicy will be removed. To prepare for these upcoming changes, customers should do the following:
30+
31+
Ensure users with TeamsInteropPolicy are assigned only one of these 3 built-in instances for which CallingDefaultClient = ChatDefaultClient, and for which AllowEndUserClientOverride = false. The other instances are no longer valid configurations and will not be supported.
32+
33+
The valid instances are:
34+
35+
36+
**Identity: DisallowOverrideCallingDefaultChatDefault**
37+
**AllowEndUserClientOverride: False**
38+
**CallingDefaultClient: Default**
39+
**ChatDefaultClient: Default**
40+
41+
**Identity: DisallowOverrideCallingSfbChatSfb**
42+
**AllowEndUserClientOverride: False**
43+
**CallingDefaultClient: Sfb**
44+
**ChatDefaultClient: Sfb**
45+
46+
**Identity: DisallowOverrideCallingTeamsChatTeams**
47+
**AllowEndUserClientOverride: False**
48+
**CallingDefaultClient: Teams**
49+
**ChatDefaultClient: Teams**
50+
51+
52+
Use the following cmdlet syntax, where $policy is one of the above values of identity:
53+
`Grant-CsTeamsInteropPolicy -PolicyName $policy -Identity $SipAddress`
54+
55+
56+
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:
57+
Remove-CsTeamsInteropPolicy -Identity Global
58+
59+
Grant TeamsInteropPolicy and TeamsUpgradePolicy together as noted below to manage users:
60+
61+
- Coordinate granting of TeamsUpgradePolicy and TeamsInteropPolicy:
62+
63+
64+
**Grant instance of TeamsUpgradePolicy using mode: Islands**
65+
**Grant instance of TeamsInteropPolicy: DisallowOverrideCallingDefaultChatDefault**
66+
67+
**Grant instance of TeamsUpgradePolicy using mode: SfBonly, SfBWithTeamsCollab**
68+
**Grant instance of TeamsInteropPolicy: DisallowOverrideCallingSfbChatSfb**
69+
70+
**Grant instance of TeamsUpgradePolicy using mode: TeamsOnly**
71+
**Grant instance of TeamsInteropPolicy: DisallowOverrideCallingTeamsChatTeams**
72+
73+
In particular, if you grant the TeamsUpgradePolicy instance “UpgradeToTeams” (Mode =TeamsOnly) to any user, you must also grant the DisallowOverrideCallingTeamsChatTeams instance of TeamsInteropPolicy to ensure the user can receive chats and calls.
74+
75+
2576
Interoperability (interop for short) enables Skype for Business and Teams users to chat and call with one another, ensuring that communications remain fluid across your organization.
2677
This policy helps IT pros manage the adoption of Teams by determining how to route calls across apps and whether to enable users to choose which app to use for calling.
2778
Teams interop policy can be defined at the tenant or per-user level.
@@ -210,7 +261,6 @@ Accept wildcard characters: False
210261
211262
### Microsoft.Rtc.Management.AD.UserIdParameter
212263
213-
214264
## OUTPUTS
215265
216266
### System.Object

‎skype/skype-ps/skype/Remove-CsTeamsInteropPolicy.md

Lines changed: 53 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,57 @@ Remove-CsTeamsInteropPolicy [-WhatIf] [-Confirm] [[-Identity] <Object>] [-Tenant
2222
```
2323

2424
## DESCRIPTION
25+
26+
Important:
27+
28+
TeamsInteropPolicy is being replaced by TeamsUpgradePolicy. During the transition, some components will honor TeamsInteropPolicy while others honor TeamsUpgradePolicy. Therefore, use of these 2 policies must be coordinated during the transition. After transition is complete, TeamsInteorpPolicy will be removed. To prepare for these upcoming changes, customers should do the following:
29+
30+
Ensure users with TeamsInteropPolicy are assigned only one of these 3 built-in instances for which CallingDefaultClient = ChatDefaultClient, and for which AllowEndUserClientOverride = false. The other instances are no longer valid configurations and will not be supported.
31+
32+
The valid instances are:
33+
34+
35+
**Identity: DisallowOverrideCallingDefaultChatDefault**
36+
**AllowEndUserClientOverride: False**
37+
**CallingDefaultClient: Default**
38+
**ChatDefaultClient: Default**
39+
40+
**Identity: DisallowOverrideCallingSfbChatSfb**
41+
**AllowEndUserClientOverride: False**
42+
**CallingDefaultClient: Sfb**
43+
**ChatDefaultClient: Sfb**
44+
45+
**Identity: DisallowOverrideCallingTeamsChatTeams**
46+
**AllowEndUserClientOverride: False**
47+
**CallingDefaultClient: Teams**
48+
**ChatDefaultClient: Teams**
49+
50+
51+
Use the following cmdlet syntax, where $policy is one of the above values of identity:
52+
`Grant-CsTeamsInteropPolicy -PolicyName $policy -Identity $SipAddress`
53+
54+
55+
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:
56+
Remove-CsTeamsInteropPolicy -Identity Global
57+
58+
Grant TeamsInteropPolicy and TeamsUpgradePolicy together as noted below to manage users:
59+
60+
- Coordinate granting of TeamsUpgradePolicy and TeamsInteropPolicy:
61+
62+
63+
**Grant instance of TeamsUpgradePolicy using mode: Islands**
64+
**Grant instance of TeamsInteropPolicy: DisallowOverrideCallingDefaultChatDefault**
65+
66+
**Grant instance of TeamsUpgradePolicy using mode: SfBonly, SfBWithTeamsCollab**
67+
**Grant instance of TeamsInteropPolicy: DisallowOverrideCallingSfbChatSfb**
68+
69+
**Grant instance of TeamsUpgradePolicy using mode: TeamsOnly**
70+
**Grant instance of TeamsInteropPolicy: DisallowOverrideCallingTeamsChatTeams**
71+
72+
73+
In particular, if you grant the TeamsUpgradePolicy instance “UpgradeToTeams” (Mode =TeamsOnly) to any user, you must also grant the DisallowOverrideCallingTeamsChatTeams instance of TeamsInteropPolicy to ensure the user can receive chats and calls.
74+
75+
2576
Interoperability (interop for short) enables Skype for Business and Teams users to chat and call with one another, ensuring that communications remain fluid across your organization.
2677
This policy helps IT pros manage the adoption of Teams by determining how to route calls across apps and whether to enable users to choose which app to use for calling.
2778
Teams interop policy can be defined at the tenant or per-user level.
@@ -30,9 +81,10 @@ Teams interop policy can be configured to keep voice communications in Teams and
3081

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

84+
3385
## EXAMPLES
3486

35-
### Example 1
87+
### -------------------------- Example 1 --------------------------
3688
```
3789
PS C:\> {{ Add example code here }}
3890
```
@@ -142,7 +194,6 @@ Accept wildcard characters: False
142194
143195
### Microsoft.Rtc.Management.Xds.XdsIdentity
144196
145-
146197
## OUTPUTS
147198
148199
### System.Object
@@ -159,13 +210,11 @@ Interoperability between Teams and Skype for Business is supported between users
159210
Interop support for Skype for Business Hybrid does not include Hybrid Voice capabilities delivered through CCE (Cloud Connector Edition) or on-premises PSTN connectivity using existing deployment--or commonly called as OPCH (On Prem Config Hybrid).
160211
Teams users cannot be enabled for PSTN calling capabilities using CCE or OPCH.
161212
162-
**IP Phone Support**
163213
**IP Phone Support**
164214
Currently, changing CallingDefaultClient to Teams will also affect calls to Skype for Business IP phones.
165215
Incoming calls will not be received on the phones and will only ring Teams clients.
166216
Please consult the [Skype for Business to Microsoft Teams Capabilities Roadmap](https://aka.ms/skype2teamsroadmap) for information about support for existing certified SIP phones.
167217
168-
169218
## RELATED LINKS
170219
171220
[Skype for Business to Microsoft Teams Capabilities Roadmap](https://aka.ms/skype2teamsroadmap)

0 commit comments

Comments
 (0)