Skip to content

Update Enable-CsOnlineSipDomain.md #2042

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 5, 2018
Merged

Update Enable-CsOnlineSipDomain.md #2042

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 3 additions & 8 deletions skype/skype-ps/skype/Enable-CsOnlineSipDomain.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,8 +36,7 @@ If you have more than one on-premises deployment of Skype for Business Server, y
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:
- Disable shared sip address space in the O365 tenant.
- Disable the ability in the on-premises environment to communicate with O365
- Update DNS records to point to Office 365.
</br>
- Update DNS records to point to Office 365. </br>
These steps should be done together as a unit.

> [!NOTE]
Expand All @@ -48,16 +47,12 @@ The steps are:
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.

`
PS C:\> Set-CsTenantFederationConfiguration -SharedSipAddressSpace $false
`
`PS C:\> Set-CsTenantFederationConfiguration -SharedSipAddressSpace $false`

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
`
`Get-CsHostingProvider|Set-CsHostingProvider -Enabled $false`

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:
Expand Down