Skip to content

Commit 9ed2f67

Browse files
authored
Merge branch 'master' into patch-15
2 parents fd5528e + d336e1c commit 9ed2f67

File tree

5 files changed

+70
-199
lines changed

5 files changed

+70
-199
lines changed

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

Lines changed: 5 additions & 44 deletions
Original file line numberDiff line numberDiff line change
@@ -11,13 +11,13 @@ schema: 2.0.0
1111

1212
IMPORTANT: TeamsInteropPolicy has been replaced by TeamsUpgradePolicy. Please read description for more details. You can also find more guidance here: [Migration and interoperability guidance for organizations using Teams together with Skype for Business](https://docs.microsoft.com/en-us/microsoftteams/migration-interop-guidance-for-teams-with-skype).
1313

14-
If TeamsUpgradePolicy has mode=Legacy, TeamsInteropPolicy determines how calls are routed between Skype for Business and Microsoft Teams. Otherwise it is ignored.
14+
If TeamsUpgradePolicy has mode=Legacy, TeamsInteropPolicy determines how calls are routed between Skype for Business and Microsoft Teams. *Otherwise TeamsInteropPolicy is ignored.* Granting TeamsUpgradePolicy with mode=Legacy is now blocked. Customers with exisitng configurations using Legacy mode must update their configuration to use a mode other than Legacy.
1515

1616

1717
## SYNTAX
1818

1919
```
20-
Get-CsTeamsInteropPolicy [-LocalStore] [[-Identity] <Object>] [-Tenant <Object>] [-Filter <Object>] [-AsJob]
20+
Get-CsTeamsInteropPolicy [-Identity] <Object>] [-Tenant <Object>] [-Filter <Object>] [-AsJob]
2121
```
2222

2323
## DESCRIPTION
@@ -26,31 +26,7 @@ IMPORTANT: TeamsInteropPolicy has been replaced by TeamsUpgradePolicy. TeamsInte
2626

2727
For any user that is still assigned TeamsInteropPolicy and in Legacy mode, these users must be assigned only one of these three built-in instances for which CallingDefaultClient = ChatDefaultClient, and for which AllowEndUserClientOverride = false. The other instances are not longer valid configurations, are not supported and will be removed.
2828

29-
The valid instances are:
3029

31-
32-
**Identity: DisallowOverrideCallingDefaultChatDefault**
33-
**AllowEndUserClientOverride: False**
34-
**CallingDefaultClient: Default**
35-
**ChatDefaultClient: Default**
36-
37-
**Identity: DisallowOverrideCallingSfbChatSfb**
38-
**AllowEndUserClientOverride: False**
39-
**CallingDefaultClient: Sfb**
40-
**ChatDefaultClient: Sfb**
41-
42-
**Identity: DisallowOverrideCallingTeamsChatTeams**
43-
**AllowEndUserClientOverride: False**
44-
**CallingDefaultClient: Teams**
45-
**ChatDefaultClient: Teams**
46-
47-
48-
Use the following cmdlet syntax, where $policy is one of the above values of identity:
49-
`Grant-CsTeamsInteropPolicy -PolicyName $policy -Identity $SipAddress`
50-
51-
52-
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:
53-
Remove-CsTeamsInteropPolicy -Identity Global
5430

5531
For comprehensive documentation on this policy and its settings, see [Migration and interoperability guidance for organizations using Teams together with Skype for Business](https://docs.microsoft.com/en-us/microsoftteams/migration-interop-guidance-for-teams-with-skype).
5632

@@ -59,10 +35,10 @@ For comprehensive documentation on this policy and its settings, see [Migration
5935

6036
### -------------------------- Example 1 --------------------------
6137
```
62-
PS C:\> {{ Add example code here }}
38+
PS C:\> Get-CsTeamsInteropPolicy
6339
```
6440

65-
{{ Add example description here }}
41+
List all available instances of TeamsInteropPolicy.
6642

6743
## PARAMETERS
6844

@@ -83,7 +59,7 @@ Accept wildcard characters: False
8359
```
8460
8561
### -Identity
86-
{{Fill Identity Description}}
62+
The name of the policy instance
8763
8864
```yaml
8965
Type: Object
@@ -98,21 +74,6 @@ Accept pipeline input: False
9874
Accept wildcard characters: False
9975
```
10076
101-
### -LocalStore
102-
{{Fill LocalStore Description}}
103-
104-
```yaml
105-
Type: SwitchParameter
106-
Parameter Sets: (All)
107-
Aliases:
108-
Applicable: Skype for Business Online
109-
110-
Required: False
111-
Position: Named
112-
Default value: None
113-
Accept pipeline input: False
114-
Accept wildcard characters: False
115-
```
11677
11778
### -Tenant
11879
{{Fill Tenant Description}}

skype/skype-ps/skype/Get-CsTeamsUpgradePolicy.md

Lines changed: 11 additions & 28 deletions
Original file line numberDiff line numberDiff line change
@@ -29,10 +29,9 @@ TeamsUpgradePolicy allows administrators to manage the transition from Skype for
2929
NOTES:
3030
- Except for on-premise versions of Skype for Business Server, all relevant instances of TeamsUpgradePolicy are built into the system, so there is no corresponding New cmdlet.
3131
- If you are using Skype for Business Server, there are no built-in instances and you'll need to create one. Also, only the NotifySfBUsers property is available. Mode is not present
32-
- Instances with mode set to SfBWithTeamsCollab are not yet functional. From a routing perspective, this will behave like SfBOnly mode.
33-
- Action property is redundnant with the combination of NotifySfBUsers and Mode. It will eventually be removed.
32+
- Instances with mode set to SfBWithTeamsCollab and SfBWithTeamsCollabAndMeetings are not yet fully functional. From a routing perspective, they will behave like SfBOnly mode.
3433

35-
IMPORTANT: TeamsUpgradePolicy has replaced TeamsInteropPolicy. Components that previously honored TeamsInteropPolicy have been updated to honor TeamsUpgradePolicy instead.
34+
IMPORTANT: TeamsUpgradePolicy has replaced TeamsInteropPolicy. Components that previously honored TeamsInteropPolicy have been updated to honor TeamsUpgradePolicy instead. Do not use TeamsInteropPolicy.
3635

3736

3837
## EXAMPLES
@@ -45,25 +44,21 @@ Identity : Global
4544
Description : Users can use either Skype for Business client or Teams client
4645
Mode : Islands
4746
NotifySfbUsers : False
48-
Action : None
4947
5048
Identity : Tag:NoUpgrade
5149
Description : Users can use either Skype for Business client or Teams client
5250
Mode : Legacy
5351
NotifySfbUsers : False
54-
Action : None
5552
5653
Identity : Tag:NotifyForTeams
5754
Description : Show notification of pending upgrade in Skype for Business client
5855
Mode : Legacy
5956
NotifySfbUsers : True
60-
Action : Notify
6157
6258
Identity : Tag:UpgradeToTeams
6359
Description : Use Teams Only
6460
Mode : TeamsOnly
6561
NotifySfbUsers : False
66-
Action : Upgrade
6762
6863
Identity : Tag:Islands
6964
Description : Use either Skype for Business client or Teams client
@@ -75,32 +70,36 @@ Identity : Tag:IslandsWithNotify
7570
Description : Use either Skype for Business client or Teams client
7671
Mode : Islands
7772
NotifySfbUsers : True
78-
Action : Notify
7973
8074
Identity : Tag:SfBOnly
8175
Description : Use only Skype for Business
8276
Mode : SfBOnly
8377
NotifySfbUsers : False
84-
Action : None
8578
8679
Identity : Tag:SfBOnlyWithNotify
8780
Description : Use only Skype for Business
8881
Mode : SfBOnly
8982
NotifySfbUsers : True
90-
Action : Notify
9183
9284
Identity : Tag:SfBWithTeamsCollab
9385
Description : Use Skype for Business and use Teams only for group collaboration
9486
Mode : SfBWithTeamsCollab
9587
NotifySfbUsers : False
96-
Action : None
9788
9889
Identity : Tag:SfBWithTeamsCollabWithNotify
9990
Description : Use Skype for Business and use Teams only for group collaboration
10091
Mode : SfBWithTeamsCollab
10192
NotifySfbUsers : True
102-
Action : Notify
10393
94+
Identity : Tag:SfBWithTeamsCollabAndMeetings
95+
Description : Use Skype for Business and use Teams only for group collaboration
96+
Mode : SfBWithTeamsCollabAndMeetings
97+
NotifySfbUsers : False
98+
99+
Identity : Tag:SfBWithTeamsCollabAndMeetingsWithNotify
100+
Description : Use Skype for Business and use Teams only for group collaboration
101+
Mode : SfBWithTeamsCollabAndMeetings
102+
NotifySfbUsers : True
104103
```
105104

106105
List all instances of TeamsUpgradePolicy
@@ -114,7 +113,6 @@ Identity : Global
114113
Description : Users can use either Skype for Business client or Teams client
115114
Mode : Islands
116115
NotifySfbUsers : False
117-
Action : None
118116
119117
```
120118

@@ -165,21 +163,6 @@ Accept pipeline input: False
165163
Accept wildcard characters: False
166164
```
167165
168-
### -LocalStore
169-
Do Not Use
170-
171-
```yaml
172-
Type: SwitchParameter
173-
Parameter Sets: (All)
174-
Aliases:
175-
Applicable: Skype for Business Online, Skype for Business Server 2019
176-
177-
Required: False
178-
Position: Named
179-
Default value: None
180-
Accept pipeline input: False
181-
Accept wildcard characters: False
182-
```
183166
184167
### -Tenant
185168
{{Fill Tenant Description}}

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

Lines changed: 12 additions & 61 deletions
Original file line numberDiff line numberDiff line change
@@ -9,9 +9,9 @@ schema: 2.0.0
99

1010
## SYNOPSIS
1111

12-
IMPORTANT: TeamsInteropPolicy has been replaced by TeamsUpgradePolicy. See description for more information. You can also find more guidance here: https://docs.microsoft.com/en-us/MicrosoftTeams/migration-interop-guidance-for-teams-with-skype
12+
IMPORTANT: TeamsInteropPolicy has been replaced by TeamsUpgradePolicy. See description for more information. You can also find more guidance here: [Migration and interoperability guidance for organizations using Teams together with Skype for Business](https://docs.microsoft.com/en-us/MicrosoftTeams/migration-interop-guidance-for-teams-with-skype).
1313

14-
This cmdlet previously determined how calls are routed between Skype for Business and Microsoft Teams. It is no longer honored, except if TeamsUpgradePolicy mode=Legacy. However, Legacy mode has been deprecated and customers should update their configurations to use a mode other than Legacy.
14+
This cmdlet previously determined how calls are routed between Skype for Business and Microsoft Teams. It is no longer honored, except if TeamsUpgradePolicy mode=Legacy. However, Legacy mode has been deprecated and can no longer be granted. Any customers with user or tenant policy using Legacy mode must update their configurations to use a mode other than Legacy.
1515

1616

1717
## SYNTAX
@@ -23,30 +23,8 @@ Grant-CsTeamsInteropPolicy [-PassThru] [-Confirm] [[-PolicyName] <Object>] [[-Id
2323

2424
## DESCRIPTION
2525

26-
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.
26+
IMPORTANT: TeamsInteropPolicy has been replaced by TeamsUpgradePolicy. It is no longer honored by the system, except if TeamsUpgradePolicy has mode=Legacy. However, Legacy mode has been deprecated. Granting mode=Legacy is now blocked. Customers that are still using Legacy mode must update their configurations to use a mode other than Legacy.
2727

28-
Any customers still using Legacy mode must ensure the following:
29-
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`.
31-
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:
33-
34-
**Identity: DisallowOverrideCallingDefaultChatDefault**
35-
**AllowEndUserClientOverride: False**
36-
**CallingDefaultClient: Default**
37-
**ChatDefaultClient: Default**
38-
39-
**Identity: DisallowOverrideCallingSfbChatSfb**
40-
**AllowEndUserClientOverride: False**
41-
**CallingDefaultClient: Sfb**
42-
**ChatDefaultClient: Sfb**
43-
44-
**Identity: DisallowOverrideCallingTeamsChatTeams**
45-
**AllowEndUserClientOverride: False**
46-
**CallingDefaultClient: Teams**
47-
**ChatDefaultClient: Teams**
48-
49-
Use the following cmdlet syntax, where $policy is one of the above values of identity: `Grant-CsTeamsInteropPolicy -PolicyName $policy -Identity $SipAddress`.
5028

5129
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).
5230

@@ -57,19 +35,6 @@ For comprehensive documentation on this policy and its settings, see [Microsoft
5735
Grant-CsTeamsInteropPolicy -PolicyName DisallowOverrideCallingDefaultChatDefault -Identity [email protected]
5836
```
5937

60-
**Default Policy**
61-
62-
By default, Microsoft Teams is configured to ensure that existing Skype for Business and Microsoft Teams calling workloads remain distinct and separate.
63-
This is a safe configuration for organizations just beginning to experiment with Teams Calling.
64-
65-
### -------------------------- Example 2 --------------------------
66-
```
67-
Grant-CsTeamsInteropPolicy -PolicyName DisallowOverrideCallingTeamsChatTeams -Identity [email protected]
68-
```
69-
70-
**Policy to enable all inbound calls and chats to be routed to Microsoft Teams (assumed Mode=Legacy)**
71-
72-
Users who have calling plans and would like to receive their calls in Microsoft Teams can have their calls routed to Teams.
7338

7439

7540
## PARAMETERS
@@ -90,21 +55,7 @@ Accept pipeline input: False
9055
Accept wildcard characters: False
9156
```
9257
93-
### -DomainController
94-
{{Fill DomainController Description}}
95-
96-
```yaml
97-
Type: Object
98-
Parameter Sets: (All)
99-
Aliases:
100-
Applicable: Skype for Business Online
10158
102-
Required: False
103-
Position: Named
104-
Default value: None
105-
Accept pipeline input: False
106-
Accept wildcard characters: False
107-
```
10859
10960
### -Identity
11061
For this cmdlet, the full UserPrincipalName/SIP address is required. If you don't provide the full UPN/SIP and instead provide an Alias, the cmdlet can throw an "Object reference not set to an instance of an object" error.
@@ -122,33 +73,33 @@ Accept pipeline input: False
12273
Accept wildcard characters: False
12374
```
12475
125-
### -PassThru
126-
{{Fill PassThru Description}}
76+
### -PolicyName
77+
{{Fill PolicyName Description}}
12778
12879
```yaml
129-
Type: SwitchParameter
80+
Type: Object
13081
Parameter Sets: (All)
13182
Aliases:
13283
Applicable: Skype for Business Online
13384

13485
Required: False
135-
Position: Named
86+
Position: 1
13687
Default value: None
13788
Accept pipeline input: False
13889
Accept wildcard characters: False
13990
```
14091
141-
### -PolicyName
142-
{{Fill PolicyName Description}}
92+
### -PassThru
93+
{{Fill PassThru Description}}
14394
14495
```yaml
145-
Type: Object
96+
Type: SwitchParameter
14697
Parameter Sets: (All)
14798
Aliases:
14899
Applicable: Skype for Business Online
149100

150101
Required: False
151-
Position: 1
102+
Position: Named
152103
Default value: None
153104
Accept pipeline input: False
154105
Accept wildcard characters: False
@@ -212,7 +163,7 @@ Accept wildcard characters: False
212163
### System.Object
213164
214165
## NOTES
215-
This policy has been deprecated. Customers should use TeamsUpgradePolicy to control interop and routing.
166+
This policy has been deprecated and should not be used. Instead, customers should use TeamsUpgradePolicy to control interop and routing.
216167
217168
## RELATED LINKS
218169

0 commit comments

Comments
 (0)