Topic Last Modified: 2013-01-24
Hybrid Deployments are configurations that use both the Microsoft Lync Online cloud service and the on premises deployment. In this type of configuration, the Autodiscover service must be able to locate where the user is actually located. That is to say, Autodiscover aids in finding the user account and where the server that hosts the user’s account is, regardless if it is in the on premises deployment or in the Lync Online deployment.
For example, if a user’s account is hosted on a server in Lync Online, the attempt to locate the user will happen as follows, in a process known as discoverability:
User initiates a connection attempt to the on premises deployment, contoso.com.
The attempt is sent to lyncdiscover.contoso.com, the DNS name associated with the Autodiscover service.
Autodiscover refers to the assumed registrar pool at the contoso.com on premises deployment and is given information on the user’s actual home server hosted in Lync Online. Autodiscover then sends the user a referral to the lync.com online Autodiscover service.
The user initiates a connection attempt to the lync.com online Autodiscover service and is able to locate the user’s account and the user’s home server.
To enable mobile clients to discover the deployment where the user home server is located, you must configure the Autodiscover service with a new uniform resource locator (URL). Do the following to configure the Autodiscover service.
Configuring Autodiscover for Hybrid Deployments
You use Get-CsHostingProvider to retrieve the value of the attribute ProxyFQDN.
From the Lync Server Management Shell, type
Set-CsHostingProvider -Identity [identity] -AutodiscoverUrl https://webdir.online.lync.com/autodiscover/autodisccoverservice.svc/root
Where [identity] is replaced with the domain name of the shared SIP address space.