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/Enable-CsOnlineSipDomain.md
+1-40Lines changed: 1 addition & 40 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,8 +8,6 @@ schema: 2.0.0
8
8
# Enable-CsOnlineSipDomain
9
9
10
10
## SYNOPSIS
11
-
THIS IS PRELIMINARY DOCUMENTATION OF UPCOMING FUNCTIONALITY</br>
12
-
13
11
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.
14
12
15
13
## SYNTAX
@@ -25,48 +23,11 @@ This cmdlet enables online provisioning of users in the specified SIP domain. I
25
23
- 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.
26
24
- 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.
27
25
28
-
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.
26
+
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 clou](https://docs.microsoft.com/en-us/skypeforbusiness/hybrid/cloud-consolidation-disabling-hybrid).
29
27
30
28
**IMPORTANT**
31
29
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.
32
30
33
-
**HOW TO DETACH A HYBRID DEPLOYMENT FROM OFFICE 365**
34
-
35
-
Once you have moved all users from on-premises into the cloud, you can decommission the on-premises Skype for Business deployment. Aside from removing any hardware, a critical step is to logically detach that on-premises deployment from Office 365. Detaching hybrid consists of 3 steps, which are detailed below:
36
-
- Disable shared sip address space in the O365 tenant.
37
-
- Disable the ability in the on-premises environment to communicate with O365
38
-
- Update DNS records to point to Office 365. </br>
39
-
40
-
These steps should be done together as a unit.
41
-
42
-
> [!NOTE]
43
-
> 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.
44
-
45
-
The steps are:
46
-
</br>
47
-
1.**Disable shared sip address space in the Office 365 tenant**
48
-
The command below needs to be done from a Skype for Business Online PowerShell window.
1.**Disable ability in on-premise to communicate with Office 365**
53
-
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.
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:
0 commit comments