dinsdag 22 november 2011

Configuring IM integration with Lync on-prem and Office 365 OWA

When using Office 365 in a Hybrid configuration and use Lync on-prem , you will probably notice that IM is not available in Outlook Web App.

To integrate on-premises Lync Server 2010 with Exchange Online, you must configure a shared SIP address space (also called a split domain). We need to follow below steps in the on-premise Lync environment. Actually, these steps are also mandatory for configuring Hosted Voicemail

  • Check SRV records
  • Check setting "Enable partner domain discovery" in Access Edge configuration
  • Configure Lync Edge server for Integration with Hosted UM

First, you have to check the presence of the Lync DNS SRV records.
These records are required for a Lync Edge server to route to a hosted Exchange such as Office 365.
To verify the presence of the SRV record, follow these steps :

  • Log on to a client computer in the domain.
  • Click Start, and then click Run.
  • At the command prompt, run the following command:
  • Nslookup _sipfederationtls._tcp.domain.com

This should return the name of the DC, its IP address and the record name.
If it returns a non-existent domain, follow this Technet Article.
Please note that the SRV records need to be in your external domain name DNS zone when using split DNS.

The next step is to check if the setting "Enable partner domain discovery' is enabled in the access edge configuration.
Steps to check this can be found in the following article :

The next step is configuring the Lync Edge server for Integration with Office 365 OWA
If you already configured Federation on you edge server, you can skip the "Set-CsAccessEdgeConfiguation" cmdlet. ( verify below settings using the Get-CsAccessEdgeConfig | fl)
If you haven't set up federation yet, log on to your Lync server and open up an elevated Lync Server Management Shell.

Use the "Set-CsAccessEdgeConfiguration -AllowFederatedUsers $True" to allow Federation.
Use the "Get-CsAccessEdgeConfiguration | fl" to verify this changed the "AllowFederatedUsers" to true.

The last thing we have to set up is a HostingProvider for Office 365.
Use the same Lync Server Management Shell to do this.
Use the below cmdlet to add the Office 365 Hosting Provider.

"New-CsHostingProvider -Identity “Hosted UM” -Enabled $True -EnabledSharedAddressSpace $True –HostsOCSUsers $False -ProxyFqdn "exap.um.outlook.com" –IsLocal $False -VerificationLevel UseSourceVerification"

Use the "Get-CsHostingProvider" to verify that the hosting provider has been made.

Source :  Technet Article

Now, the only thing we have to do is wait for replication between the Lync server and the Lync Edge.
After some time, you should see that IM is working within Office 365 OWA.

 Good luck!

7 opmerkingen:

  1. Does this still work if you have actual Exchnage UM on premise in the hybrid environment?

  2. Harm-Jan van Tiel23 november 2011 om 13:26

    The only thing changed by this is that you allow Office 365 to use Lync on-premise presence information to use within OWA. On-premise users with UM enabled will still be able to use voicemail/UM

  3. Hello How many time we must wait to see the results

    1. This should work as soon as changes are replicated between Lync servers.

  4. Cristiano Santos28 juni 2012 om 03:04

    The communication (we only tested IM) from internal Lync users to federated users stopped working after created the CsHostingProvider. _sipfederationtls._tcp.domain SRV record was already in place externally.
    The problem was caused by the "Enable partner domain discovery" setting disabled on Access Edge Configuration. After enabling, the communication with partners was restored.

    1. Thanks for sharing that with me. I will add this to the post.

  5. Any tips for troubleshooting why this would not work? I have verified all the steps here and settings. I just recently migrated from Lync Online (office365) to Lync 2013 on-prem.