Merge pull request MicrosoftDocs#2061 from bjwhalen/patch-38

Update Enable-CsOnlineSipDomain.md

Author: kenwith

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

@@ -15,21 +15,20 @@ This cmdlet enables provisioning of users in Skype for Business Online for the s
 ## SYNTAX
 
 ```
-Enable-CsOnlineSipDomain -Domain <String> [-Tenant <System.Guid>] [-DomainController <String>] [-Force]
- [-WhatIf] [-Confirm] [<CommonParameters>]
+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-premise 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.)   
+ - 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-premise 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-premise 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 below.
 
 **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 SID domain that is being enabled. 
+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. 
 
 **HOW TO DETACH A HYBRID DEPLOYMENT FROM OFFICE 365**
 
@@ -41,22 +40,21 @@ Once you have moved all users from on-premises into the cloud, you can decommiss
 These steps should be done together as a unit. 
 
 > [!NOTE]
-> Any federated organizations that are using the older Direct Federation model (also known as Allowed Partner Server) will need to update their allowed domain entries for you organization to remove the proxy FQDN. This legacy federation model is not based on DNS SRV records, so such a config will become out of date, once your organization moves to the cloud. If you suspect any of your federated partners may be using Direct Federation, we suggest you send them a communication about this as you prepare to complete your migration to the cloud.
+> Any federated organizations that are using the older Direct Federation model (also known as Allowed Partner Server) will need to update their allowed domain entries for your organization to remove the proxy FQDN. This legacy federation model is not based on DNS SRV records, so such a config will become out of date, once your organization moves to the cloud. If you suspect any of your federated partners may be using Direct Federation, we suggest you send them a communication about this as you prepare to complete your migration to the cloud.
 
 The steps are:
 </br>
-1. Disable shared sip address space in the Office 365 tenant
-\_sipfederationtls.\_tcpThe command below needs to be done from a Skype for Business Online PowerShell window. 
+1. **Disable shared sip address space in the Office 365 tenant**
+The command below needs to be done from a Skype for Business Online PowerShell window. 
 
 `PS C:\> Set-CsTenantFederationConfiguration -SharedSipAddressSpace $false`</br>
 
-2. Disable ability in on-premise to communicate with Office 365 
+2. **Disable ability in on-premise to communicate with Office 365** 
 The command below needs to be done from an on-premises PowerShell window.  If you have previously imported an Office 365 session, start a new Skype for Business PowerShell session.
 
 `Get-CsHostingProvider|Set-CsHostingProvider -Enabled $false`</br>
 
-3. Update DNS to point to O365
-
+3. **Update DNS to point to O365**
 The organization’s external DNS for the former on-premises deployment needs to be updated so that Skype for Business records point to Office 365 instead of Onprem. Specifically:
 
 
@@ -82,23 +80,8 @@ Enables the domain contoso.com for online provisioning in Skype for Business Onl
 
 ## PARAMETERS
 
-### -Confirm
-Prompts you for confirmation before running the cmdlet.
-
-```yaml
-Type: SwitchParameter
-Parameter Sets: (All)
-Aliases: cf
-applicable: Skype for Business Online
-Required: False
-Position: Named
-Default value: None
-Accept pipeline input: False
-Accept wildcard characters: False
-```
-
 ### -Domain
-The sip domain to be enabled for online provisioning in Skype for Business Online.
+The SIP domain to be enabled for online provisioning in Skype for Business Online.
 
 ```yaml
 Type: String
@@ -112,13 +95,13 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
-### -DomainController
-{{Fill DomainController Description}}
+### -Confirm
+Prompts you for confirmation before running the cmdlet.
 
 ```yaml
-Type: String
+Type: SwitchParameter
 Parameter Sets: (All)
-Aliases: DC
+Aliases: cf
 applicable: Skype for Business Online
 Required: False
 Position: Named
@@ -127,8 +110,9 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
+
 ### -Force
-{{Fill Force Description}}
+Suppresses all confirmation prompts that might occur when running the command.
 
 ```yaml
 Type: SwitchParameter
@@ -142,36 +126,6 @@ Accept pipeline input: False
 Accept wildcard characters: False
 ```
 
-### -Tenant
-{{Fill Tenant Description}}
-
-```yaml
-Type: System.Guid
-Parameter Sets: (All)
-Aliases:
-applicable: Skype for Business Online
-Required: False
-Position: Named
-Default value: None
-Accept pipeline input: False
-Accept wildcard characters: False
-```
-
-### -WhatIf
-Shows what would happen if the cmdlet runs.
-The cmdlet is not run.
-
-```yaml
-Type: SwitchParameter
-Parameter Sets: (All)
-Aliases: wi
-applicable: Skype for Business Online
-Required: False
-Position: Named
-Default value: None
-Accept pipeline input: False
-Accept wildcard characters: False
-```
 
 ### CommonParameters
 This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable.
@@ -183,7 +137,8 @@ For more information, see about_CommonParameters (http://go.microsoft.com/fwlink
 
 ## OUTPUTS
 
-### System.Object
+### None
+
 ## NOTES
 
 ## RELATED LINKS