Topic Last Modified: 2011-05-16
Supporting federation with a Microsoft Lync Online 2010 customer requires you to complete the following steps:
- Enabling support for the domain of the Lync Online 2010
customer with which you want to federate (for example,
contoso.onmicrosoft.com). As specified in the Prerequisites for
Federating with a Lync Online Customer section of this
documentation, you should have already enabled federation for your
organization. Enabling federation requires specifying the method to
be used to control access by federated domains. If you configured
your organization to use discovery, adding the domain to your
organization’s allowed list is optional. If you did not enable
domain discovery, then you must add the domain name of the Lync
Online customer to your allowed domains list. You can add a domain
name either by using Lync Server 2010 Control Panel or by running
the New-CSAllowedDomain cmdlet. For details about using Lync
Server 2010 Control Panel, including enabling discovery of domains,
Federated Partner Access in the Operations documentation. For
details about using the New-CSAllowedDomain cmdlet to add a
domain, see New-CsAllowedDomain
in the Operations documentation.
- Configure support for a hosting provider for the domain of the
Lync Online 2010 customer with which you want to federate. Use the
procedure in this section to configure support for the Lync Online
Note: This step is only required for federation with a domain of a Lync Online customer, not for federation with any domain that is deployed on premises at the federated partners location.
|A Lync Online customer can have multiple domains. If you want to federate with more than one of the domains, you must configure support for each of the domains with which you want to federate.|
To configure support for a hosting provider
From a Front End Server, Start the Lync Server Management Shell: Click Start, click All Programs, click Microsoft Lync Server 2010, and then click Lync Server Management Shell.
Run the New-CsHostingProvider cmdlet to create and configure the hosting provider. For example, run:
New-CsHostingProvider -Identity LyncOnline -ProxyFqdn "sipfed.online.lync.com" -VerificationLevel AlwaysVerifiable -Enabled $True -EnabledSharedAddressSpace $False -HostsOCSUsers $False -IsLocal $False
The preceding example sets the following parameters:
- Identity specifies a unique string value identifier for
the hosting provider you are creating. Note that the command will
fail if an existing provider has already been configured with that
- ProxyFQDN specifies the fully qualified domain name
(FQDN) for the proxy server used by the hosting provider. This
value cannot be modified. If the hosting provider changes its proxy
server you will need to delete and then recreate the entry for that
- VerificationLevel specifies how (or if) messages sent
from a hosting provider are verified to ensure that they were sent
from that provider.
- Enabled indicates whether the network connection between
your domain and the hosting provider is enabled. Messages cannot be
exchanged between the two organizations until this value is set to
- EnabledSharedAddressSpace indicates whether the hosting
provider is being used in a shared SIP address space (split domain)
- HostsOCSUsers indicates whether the hosting provider is
used to host Lync Server accounts. If False, the provider
hosts other account types, such as Microsoft Exchange accounts.
- IsLocal indicates whether the proxy server used by the
hosting provider is contained within your Lync Server topology.
For details about use of this cmdlet, see New-CsHostingProvider in the Operations documentation.
- Identity specifies a unique string value identifier for the hosting provider you are creating. Note that the command will fail if an existing provider has already been configured with that Identity.