Merge pull request MicrosoftDocs#2151 from MicrosoftDocs/kenwith-patch-7

Restores overwritten description.

Author: kenwith

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

@@ -1,5 +1,5 @@
 ---
-external help file: 
+external help file: Microsoft.Rtc.Management.Hosted.dll-help.xml
 applicable: Skype for Business Online
 title: Get-CsStorageServiceConfiguration
 schema: 2.0.0
@@ -9,76 +9,48 @@ schema: 2.0.0
 
 ## SYNOPSIS
 
-IMPORTANT: TeamsInteropPolicy is being replaced by TeamsUpgradePolicy. See description for details. You can also find more guidance here: https://docs.microsoft.com/en-us/MicrosoftTeams/migration-interop-guidance-for-teams-with-skype
+IMPORTANT: TeamsInteropPolicy has been  replaced by TeamsUpgradePolicy. See description for details. You can also find more guidance here: https://docs.microsoft.com/en-us/MicrosoftTeams/migration-interop-guidance-for-teams-with-skype
 
-Determines how calls are routed between Skype for Business and Microsoft Teams. This cmdlet is 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.
-
-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.
+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.
 
 ## SYNTAX
 
 ```
-Remove-CsTeamsInteropPolicy [-Tenant <Guid>] [-Identity] <XdsIdentity> [-Force] [-WhatIf] [-Confirm]
- [<CommonParameters>]
+Remove-CsTeamsInteropPolicy [-WhatIf] [-Confirm] [[-Identity] <Object>] [-Tenant <Object>] [-Force] [-AsJob]
 ```
 
 ## DESCRIPTION
 
-IMPORTANT: TeamsInteropPolicy is being replaced by TeamsUpgradePolicy. During the transition, some components will honor TeamsInteropPolicy while others honor TeamsUpgradePolicy. Therefore, use of these two policies must be coordinated during the transition. After the transition is complete, TeamsInteropPolicy will be removed. To prepare for these upcoming changes, customers should do the following:
+IMPORTANT: TeamsInteropPolicy has been replaced by TeamsUpgradePolicy. It is no longer honored by the system, except if TeamsUpgradePolicy has mode=Lgeacy. 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.
+ 
+ 
+Any customers still using Legacy mode must ensure the following:
+ - 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`
+ - 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:
 
-Ensure that users with TeamsInteropPolicy are assigned only one of these three 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. 
-
-The valid instances are:
-
 
 **Identity: DisallowOverrideCallingDefaultChatDefault**   
-**AllowEndUserClientOverride: False**   
-**CallingDefaultClient: Default**   
-**ChatDefaultClient: Default**
+ - AllowEndUserClientOverride: False   
+ - CallingDefaultClient: Default   
+ - ChatDefaultClient: Default
 
 **Identity: DisallowOverrideCallingSfbChatSfb**   
-**AllowEndUserClientOverride: False**   
-**CallingDefaultClient: Sfb**   
-**ChatDefaultClient: Sfb**
+ - AllowEndUserClientOverride: False   
+ - CallingDefaultClient: Sfb   
+ - ChatDefaultClient: Sfb
 
 **Identity: DisallowOverrideCallingTeamsChatTeams**   
-**AllowEndUserClientOverride: False**   
-**CallingDefaultClient: Teams**     
-**ChatDefaultClient: Teams**
+ - AllowEndUserClientOverride: False   
+ - CallingDefaultClient: Teams  
+ - ChatDefaultClient: Teams
 
 
 Use the following cmdlet syntax, where $policy is one of the above values of identity:
 `Grant-CsTeamsInteropPolicy -PolicyName $policy -Identity $SipAddress`
 
 
-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
- 
-Grant TeamsInteropPolicy and TeamsUpgradePolicy together as noted below to manage users:
- 
-- Coordinate granting of TeamsUpgradePolicy and TeamsInteropPolicy:
-
-
-    **Grant instance of TeamsUpgradePolicy using mode: Islands**  
-    **Grant instance of TeamsInteropPolicy: DisallowOverrideCallingDefaultChatDefault**
-
-    **Grant instance of TeamsUpgradePolicy using mode: SfBonly, SfBWithTeamsCollab**  
-    **Grant instance of TeamsInteropPolicy: DisallowOverrideCallingSfbChatSfb**
-
-    **Grant instance of TeamsUpgradePolicy using mode: TeamsOnly**    
-    **Grant instance of TeamsInteropPolicy: DisallowOverrideCallingTeamsChatTeams**
-
-
-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 that the user can receive chats and calls.
-
-
-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. 
-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. 
-Teams interop policy can be defined at the tenant or per-user level.
-
-Teams interop policy can be configured to keep voice communications in Teams and Skype for Business siloed, or it can be configured to enable users to communicate across application boundaries.
-
-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).
+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).
 
 
 ## EXAMPLES
@@ -128,7 +100,7 @@ Accept wildcard characters: False
 {{Fill Identity Description}}
 
 ```yaml
-Type: XdsIdentity
+Type: Object
 Parameter Sets: (All)
 Aliases: 
 Applicable: Skype for Business Online 
@@ -144,7 +116,7 @@ Accept wildcard characters: False
 {{Fill Tenant Description}}
 
 ```yaml
-Type: Guid
+Type: Object
 Parameter Sets: (All)
 Aliases: 
 Applicable: Skype for Business Online 
@@ -173,6 +145,22 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+### -AsJob
+{{Fill AsJob Description}}
+
+```yaml
+Type: SwitchParameter
+Parameter Sets: (All)
+Aliases: 
+Applicable: Skype for Business Online 
+
+Required: False
+Position: Named
+Default value: None
+Accept pipeline input: False
+Accept wildcard characters: False
+```
+
 ## INPUTS
 
 ### Microsoft.Rtc.Management.Xds.XdsIdentity
@@ -183,24 +171,8 @@ Accept wildcard characters: False
 
 ## NOTES
 
-**External Calling Support**
-Calls from external callers on PSTN is only available for users who have been provisioned with a Calling Plan.
-
-**Supported Topologies**
-Interoperability between Teams and Skype for Business is supported between users who are purely online (Skype for Business Online and Teams), and users homed in a Skype for Business on-premises deployment in a mixed (Hybrid) deployment topology.
-
-**Hybrid Voice is not supported at this time**
-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--commonly called OPCH (On Prem Config Hybrid). 
-Teams users cannot be enabled for PSTN calling capabilities using CCE or OPCH.
-
-**IP Phone Support**
-Currently, changing CallingDefaultClient to Teams will also affect calls to Skype for Business IP phones. 
-Incoming calls will not be received on the phones and will only ring Teams clients. 
-Please consult the [Skype for Business to Microsoft Teams Capabilities Roadmap](https://aka.ms/skype2teamsroadmap) for information about support for existing certified SIP phones.
+This policy has been deprecated. Customters should use TeamsUpgradePolicy to control interop and routing.
 
 ## RELATED LINKS
 
-[Skype for Business to Microsoft Teams Capabilities Roadmap](https://aka.ms/skype2teamsroadmap)
-
-[Microsoft Teams and Skype for Business Interoperability](https://docs.microsoft.com/MicrosoftTeams/teams-and-skypeforbusiness-interoperability)
-
+[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)