Checklist: Connect Lync Server 2010 to Exchange Online UM

 

Applies to: Office 365 for enterprises

Topic Last Modified: 2011-12-19

Lync Server 2010 on-premises supports interoperability with Exchange Online in the following ways:

  • Calendar data and Out of Office messages
  • Instant Messaging (IM) and presence interoperability in Outlook Web App
  • Voice mail interoperability

Outlook Web App interoperates with Lync Server 2010 on-premises to provide users with instant messaging (IM) and presence information in Outlook Web App.

Exchange Online Unified Messaging (UM) relies on supported telephony solutions, such as Lync Server 2010 Enterprise Voice, to provide dial tone, voice call switching, and telephone number translation services. For a list of the features available with Exchange Online UM, refer to the Office 365 Service for Enterprise Service Descriptions. Hosted voice mail is only available for users in certain countries based on the “Usage Country” assigned to the user in Office 365. For a list of countries where voice mail is available, see About License Restrictions.

To enable the Lync-to-UM online integration, you must configure the Lync Edge server in your on-premises Lync Server 2010 deployment. The diagram below shows the basic architecture.

Connecting Lync Server to Exchange Online UM
Checklist

  1. Deploy and configure Lync Server 2010.
    1. Deploy Lync Server 2010. For more information, see Deploying Lync Server 2010.
    2. Deploy Edge servers. For more information, see Deploying Edge Servers 2010.
    3. Deploy Enterprise Voice. For more information, see Deploying Enterprise Voice.
  2. Provide Lync Server 2010 users with voice mail on hosted Exchange UM.
    1. Create a DNS SRV record for integration with hosted Exchange UM. For more information, see Create a DNS SRV Record for Integration with Hosted Exchange UM.
      warningWarning:
      The domain used in the SRV record that you create must match the domain used in the DNS host (A) record. This will be used as the FQDN for the Edge pool.
    2. Set up Edge certificates. For more information, see Set Up Certificates for the External Edge Interface.
      warningWarning:
      The domain on the SRV record and domain name used on the Edge server must match for TLS negotiation to be successful. You will also need to use a certificate from a public certification authority (CA) on the external interfaces on the Edge servers.
    3. Configure the Edge server for integration with hosted Exchange UM. For more information, see Configure the Edge Server for Integration with Hosted Exchange UM.
      1. Configure a shared SIP address space.
      2. Configure a hosting provider on the Edge server.
      3. Verify replication of the updated Central Management store.
    4. Enable Lync users for hosted voice mail with Exchange UM. For more information, see Enable Lync Users for Hosted Voice Mail with Exchange UM.
    5. Create contact objects for hosted Exchange UM. For more information, see Create Contact Objects for Hosted Exchange UM.
  3. Configure Exchange Online UM to work with Lync Server 2010. Here's how: Create a New UM Dial Plan and Configure a UM Dial Plan.
    • When you create the dial plan, select SIP URI as the URI type.
    • Ensure that the domain that’s configured on your Lync Hosted voice mail policy is added to your Office 365 domains (see Add your domain to Office 365). In the Exchange Online configuration, it must be an authoritative domain. The best choice is usually the third-level domain assigned when you signed up for Office 365 (for example, customer.onmicrosoft.com). This domain already exists and is authoritative, plus you can avoid additional steps by configuring this domain name as the Organization property on the Lync hosted voice mail policy. Note that this won’t be the same domain that you use for your Lync users’ SIP addresses.

  4. Direct a Lync Server to Exchange Online UM
  5. Verify the Connection Between the Lync Server 2010 Server and Exchange Online UM
 
Related help topics
Loading...
No resources were found.