You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: skype/skype-ps/skype/Get-CsTeamsInteropPolicy.md
+5-44Lines changed: 5 additions & 44 deletions
Original file line number
Diff line number
Diff line change
@@ -11,13 +11,13 @@ schema: 2.0.0
11
11
12
12
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).
13
13
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.
@@ -26,31 +26,7 @@ IMPORTANT: TeamsInteropPolicy has been replaced by TeamsUpgradePolicy. TeamsInte
26
26
27
27
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.
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
54
30
55
31
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).
56
32
@@ -59,10 +35,10 @@ For comprehensive documentation on this policy and its settings, see [Migration
59
35
60
36
### -------------------------- Example 1 --------------------------
61
37
```
62
-
PS C:\> {{ Add example code here }}
38
+
PS C:\> Get-CsTeamsInteropPolicy
63
39
```
64
40
65
-
{{ Add example description here }}
41
+
List all available instances of TeamsInteropPolicy.
Copy file name to clipboardExpand all lines: skype/skype-ps/skype/Get-CsTeamsUpgradePolicy.md
+11-28Lines changed: 11 additions & 28 deletions
Original file line number
Diff line number
Diff line change
@@ -29,10 +29,9 @@ TeamsUpgradePolicy allows administrators to manage the transition from Skype for
29
29
NOTES:
30
30
- 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.
31
31
- 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.
34
33
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.
36
35
37
36
38
37
## EXAMPLES
@@ -45,25 +44,21 @@ Identity : Global
45
44
Description : Users can use either Skype for Business client or Teams client
46
45
Mode : Islands
47
46
NotifySfbUsers : False
48
-
Action : None
49
47
50
48
Identity : Tag:NoUpgrade
51
49
Description : Users can use either Skype for Business client or Teams client
52
50
Mode : Legacy
53
51
NotifySfbUsers : False
54
-
Action : None
55
52
56
53
Identity : Tag:NotifyForTeams
57
54
Description : Show notification of pending upgrade in Skype for Business client
58
55
Mode : Legacy
59
56
NotifySfbUsers : True
60
-
Action : Notify
61
57
62
58
Identity : Tag:UpgradeToTeams
63
59
Description : Use Teams Only
64
60
Mode : TeamsOnly
65
61
NotifySfbUsers : False
66
-
Action : Upgrade
67
62
68
63
Identity : Tag:Islands
69
64
Description : Use either Skype for Business client or Teams client
Copy file name to clipboardExpand all lines: skype/skype-ps/skype/Grant-CsTeamsInteropPolicy.md
+12-61Lines changed: 12 additions & 61 deletions
Original file line number
Diff line number
Diff line change
@@ -9,9 +9,9 @@ schema: 2.0.0
9
9
10
10
## SYNOPSIS
11
11
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).
13
13
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.
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.
27
27
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:
Use the following cmdlet syntax, where $policy is one of the above values of identity: `Grant-CsTeamsInteropPolicy -PolicyName $policy -Identity $SipAddress`.
50
28
51
29
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).
52
30
@@ -57,19 +35,6 @@ For comprehensive documentation on this policy and its settings, see [Microsoft
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 --------------------------
**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.
73
38
74
39
75
40
## PARAMETERS
@@ -90,21 +55,7 @@ Accept pipeline input: False
90
55
Accept wildcard characters: False
91
56
```
92
57
93
-
### -DomainController
94
-
{{Fill DomainController Description}}
95
-
96
-
```yaml
97
-
Type: Object
98
-
Parameter Sets: (All)
99
-
Aliases:
100
-
Applicable: Skype for Business Online
101
58
102
-
Required: False
103
-
Position: Named
104
-
Default value: None
105
-
Accept pipeline input: False
106
-
Accept wildcard characters: False
107
-
```
108
59
109
60
### -Identity
110
61
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.
0 commit comments