Merge branch 'patch-3' of https://github.com/mibrest-MSFT/office-docs-powershell into pr/7516

Author: garycentric

skype/skype-ps/skype/Disable-CsOnlineSipDomain.md

@@ -13,11 +13,12 @@ ms.reviewer: rogupta
 # Disable-CsOnlineSipDomain
 
 ## SYNOPSIS
+
 This cmdlet prevents provisioning of users in Skype for Business Online for the specified domain. This cmdlet allows organizations with multiple on-premises deployments of Skype For Business Server or Lync Server to safely synchronize users from multiple forests into a single Office 365 tenant.
 
 ## SYNTAX
 
-```
+```powershell
 Disable-CsOnlineSipDomain -Domain <String> [-Force] [-Confirm] [<CommonParameters>]
 ```
 
@@ -31,24 +32,31 @@ This cmdlet enables organizations with *multiple on-premises deployments of Skyp
 This cmdlet facilitates consolidation of multiple Skype for Business Server deployments into a single Office 365 tenant. Consolidation can be achieved by moving one deployment at a time into Office 365, **provided the following key requirements are met**:
 
 - There must be at most 1 O365 tenant involved. Consolidation in scenarios with >1 O365 tenant is not supported.
+
 - At any given time, only 1 on-premises SfB forest can be in hybrid mode (Shared Sip Address Space) with Office 365. All other on-premises SfB forests must remain on-premises. (They presumably are federated with each other.) 
+
 - If 1 deployment is in hybrid mode, all sip domains from any other SfB forests must be disabled using this cmdlet before they can be synchronized into the tenant with Azure AD Connect. Users in all SfB forests other than the hybrid forest must remain on-premises.
+
 - Organizations must fully migrate each SfB forest individually into the O365 tenant using hybrid mode (Shared Sip Address Space), and then detach the "hybrid" deployment, *before* moving on to migrate the next on-premises SfB deployment. 
 
 
 This cmdlet may also be useful for organizations with on-premises deployments of Skype for Business Server that have not properly configured Azure AD Connect. If the organization does not sync msRTCSIP-DeploymentLocator for its users, then Skype for Business Online will attempt to provision online any users with an assigned Skype for Business license, despite there being users on-premises. While the correct fix is to update the configuration for Azure AD Connect to sync those attributes, using Disable-CsOnlineSipDomain can also mitigate the problem until that configuration change can be made. If this cmdlet is run, any users that were previously provisioned online in that domain will be de-provisioned in Skype for Business Online.
 
-**IMPORTANT**
-This cmdlet should not be run for domains that contain users hosted in Skype for Business Online. Any users in a sip domain that are already provisioned *online* will cease to function if you disable the online sip domain:
+> [!IMPORTANT]
+> This cmdlet should not be run for domains that contain users hosted in Skype for Business Online. Any users in a sip domain that are already provisioned *online* will cease to function if you disable the online sip domain:
+> 
+> - Their SIP addresses will be removed.
+> - All contacts and meetings for these users hosted in Skype for Business Online will be deleted.
+> - These users will no longer be able to login to the Skype for Business Online environment.
+> - If these users use Teams, they will no longer be able to inter-operate with Skype for Business users, nor will they be able to federate with any users in other organizations.
 
-- Their SIP addresses will be removed.
-- All contacts and meetings for these users hosted in Skype for Business Online will be deleted.
-- These users will no longer be able to login to the Skype for Business Online environment.
-- If these users use Teams, they will no longer be able to inter-operate with Skype for Business users, nor will they be able to federate with any users in other organizations.
+> [!NOTE]
+> If the Tenant is disabled for Regionally Hosted Meetings in Skype for Business Online, Online SIP Domains must be disabled in all regions. You must execute this cmdlet in each region that is added in Allowed Data Location.  
 
 ## EXAMPLES
 
 ### Example 1
+
 ```powershell
 Disable-CsOnlineSipDomain -Domain Fabrikam.com
 ```
@@ -58,6 +66,7 @@ The cmdlet above disables the online sip domain Fabrikam.com. This would be usef
 ## PARAMETERS
 
 ### -Domain
+
 The SIP domain to be disabled for online provisioning in Skype for Business Online.
 
 ```yaml
@@ -73,6 +82,7 @@ Accept wildcard characters: False
 ```
 
 ### -Confirm
+
 Prompts you for confirmation before running the cmdlet.
 
 ```yaml
@@ -88,6 +98,7 @@ Accept wildcard characters: False
 ```
 
 ### -Force
+
 Suppresses all confirmation prompts that might occur when running the command.
 
 ```yaml
@@ -104,6 +115,7 @@ Accept wildcard characters: False
 
 
 ### CommonParameters
+
 This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable.
 For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).
 
@@ -116,6 +128,7 @@ For more information, see [about_CommonParameters](https://go.microsoft.com/fwli
 ### None
 
 ## NOTES
+
 This cmdlet is for advanced scenarios only. Organizations that are pure online or have only 1 on-premises deployment need not run this cmdlet.
 
 ## RELATED LINKS

skype/skype-ps/skype/Enable-CsOnlineSipDomain.md

@@ -13,30 +13,39 @@ ms.reviewer: rogupta
 # Enable-CsOnlineSipDomain
 
 ## SYNOPSIS
+
 This cmdlet enables provisioning of users in Skype for Business Online for the specified domain. This cmdlet is only necessary to run if you previously disabled a domain using Disable-CsOnlineSipDomain. Enable-CsOnlineSipDomain is used to facilitate consolidation of separate Skype for Business deployments into a single Office 365 tenant.
 
 ## SYNTAX
 
-```
+```powershell
 Enable-CsOnlineSipDomain -Domain <String> [-Force] [-Confirm] [<CommonParameters>]
 ```
 
 ## DESCRIPTION
+
 This cmdlet enables online provisioning of users in the specified SIP domain. In conjunction with Disable-CsOnlineSipDomain, this cmdlet allows organizations to consolidate *multiple on-premises deployments of Skype for Business Server (or Lync Server)* into a single Office 365 tenant. Consolidation can be achieved by moving one deployment at a time into Office 365, provided the following key requirements are met:
 
 - There must be at most 1 O365 tenant involved. Consolidation for scenarios with > 1 O365 tenant is not supported. 
+
 - At any given time, only 1 on-premises SfB forest can be in hybrid mode (Shared Sip Address Space) with Office 365. All other on-premises SfB forests must remain on-premises. (They presumably are federated with each other.) 
+
 - If 1 deployment is in hybrid mode, all online SIP domains from any other SfB forests must be disabled before they can be synchronized into the tenant with Azure AD Connect. Users in all SfB forests other than the hybrid forest must remain on-premises. 
+
 - Organizations must fully migrate (e.g move all users to the cloud) each SfB forest individually into the O365 tenant using hybrid mode (Shared Sip Address Space), and then detach the "hybrid" deployment, *before* moving on to migrate the next on-premises SfB deployment. 
 
 Before running this cmdlet for any SIP domain in a Skype for Business Server deployment, you must complete migration of any other existing hybrid SfB deployment that is in progress. All users in an existing hybrid deployment must be moved to the cloud, and that existing hybrid deployment must be detached from Office 365, as described in this article: [Disable hybrid to complete migration to the cloud](https://docs.microsoft.com/skypeforbusiness/hybrid/cloud-consolidation-disabling-hybrid).
 
-**IMPORTANT**
-If you have more than one on-premises deployment of Skype for Business Server, you *must* ensure SharedSipAddressSpace is disabled in all other Skype for Business Server deployments except the deployment containing the SIP domain that is being enabled. 
+> [!IMPORTANT]
+> If you have more than one on-premises deployment of Skype for Business Server, you *must* ensure SharedSipAddressSpace is disabled in all other Skype for Business Server deployments except the deployment containing the SIP domain that is being enabled. 
+
+> [!NOTE]
+> If the Tenant is enabled for Regionally Hosted Meetings in Skype for Business Online, Online SIP Domains must be Enabled in all regions. You must execute this cmdlet in each region that is added in Allowed Data Location for Skype for Business.  
 
 ## EXAMPLES
 
 ### Example 1
+
 ```powershell
 Enable-CsOnlineSipDomain -Domain contoso.com
 ```
@@ -46,6 +55,7 @@ Enables the domain contoso.com for online provisioning in Skype for Business Onl
 ## PARAMETERS
 
 ### -Domain
+
 The SIP domain to be enabled for online provisioning in Skype for Business Online.
 
 ```yaml
@@ -61,6 +71,7 @@ Accept wildcard characters: False
 ```
 
 ### -Confirm
+
 Prompts you for confirmation before running the cmdlet.
 
 ```yaml
@@ -76,6 +87,7 @@ Accept wildcard characters: False
 ```
 
 ### -Force
+
 Suppresses all confirmation prompts that might occur when running the command.
 
 ```yaml
@@ -91,7 +103,9 @@ Accept wildcard characters: False
 ```
 
 ### CommonParameters
-This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable.
+
+This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, 
+-OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable.
 For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).
 
 ## INPUTS