 | This article is intended for readers who are looking for guidance on how to deploy Lync 2013 Hybrid Split Domain with shared SIP address space. It documents the steps necessary to move from a fully on-premise Lync2013 deployment to a hybrid Office365 Lync split-domain deployment where some users are homed on-premise while some are homed on-line. Hopefully this serves as a useful reference to compliment the documentation already provided by TechNet. Do note that this is a very long article! |
The starting point for this article is an already fully functional Lync2013 on-premise deployment complete with Edge server deployed with
federation enabled and all modalities working properly. All the necessary external and internal DNS records are already in-place and public SSL certificates are already assigned to the Lync Edge services and Reverse Proxy services. At the same time, an enterprise Office365 tenant to build the split domain topology on must also be available. In this setup an O365 E3 tenant is used for the hybrid deployment. Readers who do not have a tenant can sign up for a 30-day E3 trial here. Note also that the desired shared SIP address space must be a publicly verifiable domain therefore domain suffixes such as ".local" will not work. Ownership of the SIP domain is also required along with the ability to create public DNS records and purchasing of public SSL certificates. With all these in place, a quick overview of the steps involved is summarized below:
federation enabled and all modalities working properly. All the necessary external and internal DNS records are already in-place and public SSL certificates are already assigned to the Lync Edge services and Reverse Proxy services. At the same time, an enterprise Office365 tenant to build the split domain topology on must also be available. In this setup an O365 E3 tenant is used for the hybrid deployment. Readers who do not have a tenant can sign up for a 30-day E3 trial here. Note also that the desired shared SIP address space must be a publicly verifiable domain therefore domain suffixes such as ".local" will not work. Ownership of the SIP domain is also required along with the ability to create public DNS records and purchasing of public SSL certificates. With all these in place, a quick overview of the steps involved is summarized below:
- Add your domain and verify ownership
- Install and Configure Active Directory synchronization
- Install and Configure Active Directory Federation Services (AD FS)
- Install and Configure Active Directory Federation Services Proxy (AD FS Proxy)
- Configure Single Sign-on (SSO) with ADFS
- Configure federation of Lync Server 2013 with Lync Online
- Move user to Lync Online and test calls between Lync Online and Lync Onprem
RSS Feed