I was recently setting up hybrid
Lync Skype for Business for a customer. This is more properly known as “split-domain” configuration because you share a single SIP namespace across both the on-premises and cloud portions of the infrastructure.
If you’re not familiar with the process, it goes like this (although I think Set up AD FS or whatever other identity federation solution you like.
- Configure the service to allow federation.
- Configure the on-premises Lync/SfB servers to allow federation.
- Turn on federation.
- Enable your tenant for split-domain operations with Set-CsTenantFederationConfiguration.
- Start moving users.
Adam Jacobs’ summary is worth reading if you haven’t seen this before, but even without reading it, it seems straightforward enough, right? I found that when I got to step 6 I got a vexing error: “Cannot find Registrar pool. Verify that ‘sipfed.online.lync.com’ is a valid registrar pool.”
I was 100% sure that the registrar pool name…
View original post 178 more words