Link to home
Create AccountLog in
Avatar of TechBoston
TechBostonFlag for United States of America

asked on

Lync Profile Migration to Office 365

We have a hybrid config setup between our on-prem Exchange 2010 servers and our Office 365 tenant. Communication for emails are working properly, we can (and have) migrated mailboxes to O365 with no problems. We also have Lync 2013 on-prem with 1 edge and 1 front end server.

We follow the instructions here: https://technet.microsoft.com/en-us/library/jj204969.aspx. However, it fails saying that it can't find the sipfed.online.lync.com pool. It's my understanding that this happens because we don't have Lync/Skype for Business set up as a hosting provider in our Lync environment.

This is where the problem comes up. Lync will not let us have federated domains AND a hosting provider with the same FQDN. We already have a couple of external O365 domains that we've individually federated with which use sipfed.online.lync.com. So we can't add the sipfed.online.lync.com pool as a hosting provider for this reason. If we removed the federation with those 2 external domains, then we can add the hosting provider but that breaks the federation between us and those 2 external domains. All of their Lync contacts begin showing as either "Updating..." or "Presence Unknown" in Lync.

Everything I've found online says that the hosting provider with FQDN should be all that's required to federate with all O365 domains. But that's not the case in our environment and it's something that is driving us nuts. We've opened a case with Microsoft and they've seen the issue and have escalated the case a couple of times but we feel like we're getting nowhere with them.

Any help is greatly appreciated. Let me know if there's any other information I didn't include that might be helpful.
ASKER CERTIFIED SOLUTION
Avatar of Jian An Lim
Jian An Lim
Flag of Australia image

Link to home
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
See answer
Avatar of TechBoston

ASKER

That was exactly it! I could've swore Microsoft had previously checked this but I guess not. Thank you very much Jian!