Skype for Business Online users in an Office 365 domain can’t IM or detect users in an on-premises domain
Consider the following scenario:
- You have a hybrid deployment of on-premises Skype for Business Server or Lync Server 2013.
- The contoso.com domain is confirmed in the on-premises topology and verified by the Office 365 organization.
- The my.contoso.com domain is verified by the Office 365 organization.
- Federation DNS records for contoso.com point to the on-premises edge server.
- Federation DNS records for my.contoso.com point to Office 365.
You may also see the following detail recorded in the client logs:
ms-diagnostics: 1017; reason="Cannot route From and To domains in this combination"; summary="Domain type analysis indicates that the ms-split-domain-info header in the message is the wrong type”
To resolve this problem, add the Office 365 domain to the on-premises topology. For more information about how to configure the domains for hybrid deployment, go to the following Microsoft resource:
The hybrid configuration is correct for the contoso.com domain. However, the configuration isn't correct for the my.contoso.com domain.
To configure your on-premises deployment for a hybrid deployment, federation DNS records must be pointed to the on-premises edge server for all domains that are verified by the Office 365 organization. Domain matching must be configured in the same manner for both the on-premises deployment and the Office 365 organization.
Note The shared Session Initiation Protocol (SIP) address space configuration option is configured for all domains in the organization. It can't be configured for only a specific domain.
Still need help? Go to the Office 365 Community website.
Article ID: 3124484 - Last Review: 02/29/2016 19:11:00 - Revision: 3.0
Skype for Business Online, Skype for Business 2015, Skype for Business Server 2015, Skype for Business 2016, Microsoft Lync 2013, Microsoft Lync Server 2013
- o365 o365e o365p o365a o365m o365022013 KB3124484