Article ID: 2614614 - View products that this article applies to.
Expand all | Collapse all

SUMMARY

This article discusses the configuration steps and requirements to integrate Microsoft Exchange Online in Microsoft Office 365 (with or without an on-premises Microsoft Exchange Server 2013 deployment in hybrid mode) with Microsoft Lync Server 2013, Microsoft Lync Online in Office 365, or a hybrid combination of both. The following user configurations are considered in this article:
  • A user mailbox on Exchange Online integrated with Lync Online
  • A user mailbox on Exchange Online integrated with Lync Server 2013 on-premises
    • In this configuration, directory synchronization isn't required. However, we recommend it.
    • This configuration is partly supported. See the "More Information" section.
  • A user mailbox on Exchange Online integrated with Lync Online through a Lync Server 2013 hybrid deployment
    • Directory synchronization and single sign-on (SSO) are required as part of setting up a Lync hybrid deployment.

DEPLOYMENT

  1. Configure the Domain Name System (DNS) records for Lync federation and Lync client discovery so that Microsoft Outlook Web App can determine where the user’s Lync server is located.
    With Lync Online only
    Collapse this imageExpand this image
    assets folding start collapsed
    DNS Records should all point to Lync Online. For more information, go to the following Microsoft Knowledge Base article:
    • 2566790 Troubleshooting Lync Online
    Collapse this imageExpand this image
    assets folding end collapsed
    With Lync Server 2013 or a Lync Server 2013 hybrid deployment
    Collapse this imageExpand this image
    assets folding start collapsed
    DNS records should all point to on-premises. For more information, go to the following Microsoft websites:
    Collapse this imageExpand this image
    assets folding end collapsed

    Important Stop here if you're using only Exchange Online integrated with Lync Online. The following steps apply only if you’re using on-premises Lync or Exchange resources.
  2. Make sure that  Exchange Online has access to the user’s Lync SIP address. Exchange uses the Active Directory ProxyAddresses attribute to determine the user’s Session Initiation Protocol (SIP) address. If the attribute doesn’t contain the user’s SIP address, Outlook Web App won't be able to connect.
    With Lync Server 2013 only (with directory synchronization)
    Collapse this imageExpand this image
    assets folding start collapsed
    No additional action is required.
    Collapse this imageExpand this image
    assets folding end collapsed
    With Lync Server 2013 only (without directory synchronization)
    Collapse this imageExpand this image
    assets folding start collapsed
    • Directory synchronization is recommended for this scenario.
    • Connect to the Exchange Admin Center (EAC), and then add the user’s SIP address. Use the following Microsoft TechNet website for guidance:
      Add or Remove Email Addresses for a Mailbox
      Note Make sure that you add the SIP address by using the correct format (for example, sip:user@contoso.com, where user@contoso.com represents the email address of the user).
    Collapse this imageExpand this image
    assets folding end collapsed
    With Lync Online in a hybrid deployment with Lync Server 2013
    Collapse this imageExpand this image
    assets folding start collapsed
    • Directory synchronization is required for this scenario as part of setting up a Lync hybrid deployment.
    • No action is necessary beyond implementing DirSync. The msRTCSIP-PrimaryUserAddress attribute is set on-premises and synchronized to Microsoft Office 365.
    Collapse this imageExpand this image
    assets folding end collapsed
  3. Make sure that Lync has access to the user’s Exchange email address.
    With Lync Server 2013 only (with directory synchronization)
    Collapse this imageExpand this image
    assets folding start collapsed
    No additional action is required.
    Collapse this imageExpand this image
    assets folding end collapsed
    With Lync Server 2013 only (without directory synchronization)
    Collapse this imageExpand this image
    assets folding start collapsed
    • Directory synchronization is recommended for this scenario.
    • Because Lync Server 2013 users don’t have a mailbox on-premises, you must manually populate the MAIL attribute in the on-premises Active Directory schema.
    Collapse this imageExpand this image
    assets folding end collapsed
    With Lync Online in a hybrid deployment with Lync Server 2013
    Collapse this imageExpand this image
    assets folding start collapsed
    • Directory synchronization is required for this scenario. Because Lync Online users don’t have a mailbox in the cloud, there's no other way to manually specify the MAIL attribute.
    • Directory synchronization is a prerequisite for a Lync Server 2013 hybrid deployment.
    Collapse this imageExpand this image
    assets folding end collapsed
  4. Configure a shared SIP address space. This integrates on-premises Lync Server 2013 with Exchange Online. The same SIP domain address space is supported by both Lync Server and the Exchange Online service.
    With Lync Server 2013 or a Lync Server 2013 Hybrid Deployment
    Collapse this imageExpand this image
    assets folding start collapsed
    Using the Lync Server Management Shell, configure the Edge Server for federation by running the Set-CSAccessEdgeConfiguration cmdlet, and use the parameters in the following example:
    Set-CsAccessEdgeConfiguration -AllowFederatedUsers $True
    The AllowFederatedUsers parameter specifies whether internal users can communicate with users from federated domains. This property also determines whether internal users can communicate with users in a shared SIP address space scenario with Lync Server and Exchange Online.

    For more information, go to the following Microsoft TechNet website:
    Configuring On-premises Lync Server 2013 Integration with Exchange Online
    Collapse this imageExpand this image
    assets folding end collapsed
  5. Add a hosting provider. Lync Server has to trust the connection attempt from the Exchange Online Access Edge.
    With Lync Server 2013 only
    Collapse this imageExpand this image
    assets folding start collapsed
    Run the following cmdlet from Lync Management Shell. (Notice that the EnableSharedAddressSpace flag is set to False.)
    New-CsHostingProvider -Identity "Exchange Online" -Enabled $True -EnabledSharedAddressSpace $False -HostsOCSUsers $False -ProxyFqdn "exap.um.outlook.com" -IsLocal $False -VerificationLevel UseSourceVerification
    Collapse this imageExpand this image
    assets folding end collapsed
    With a Lync Server 2013 hybrid deployment
    Collapse this imageExpand this image
    assets folding start collapsed
    Run the same cmdlet that is given for Lync Server 2013 only, but set the EnableSharedAddressSpace flag to True. The EnableSharedAddressSpace flag indicates to Lync that the hosting provider can service users in a shared SIP address space.

    For more information, go to the following Microsoft TechNet website:
    Configuring On-premises Lync Server 2013 Integration with Exchange Online
    Collapse this imageExpand this image
    assets folding end collapsed
  6. Add trusted applications.

    Note This step applies to Exchange Online only or to Exchange hybrid customers who are trying to integrate with Lync Server 2013 or Lync hybrid deployments.
    With Lync Server 2013 or a Lync Server 2013 Hybrid deployment integrating with Exchange Online only
    Collapse this imageExpand this image
    assets folding start collapsed
    No additional action is required. This step isn't needed with Exchange Online.
    Collapse this imageExpand this image
    assets folding end collapsed
    With Lync Server 2013 or a Lync Server 2013 hybrid deployment integrating with an Exchange Server 2013 hybrid deployment
    Collapse this imageExpand this image
    assets folding start collapsed
    Lync Server 2013 and Exchange Server 2013 must be configured to use OAuth for server to server authentication. For more information, go to the following Microsoft TechNet website:Both Lync and Exchange must be added as Partner Applications. For more information about how to configure Partner Applications between Exchange Server 2013 and Lync Server 2013, go to the following TechNet website:
    Collapse this imageExpand this image
    assets folding end collapsed
  7. In a Lync Server 2013 or Lync hybrid deployment, make sure that the on-premises Lync Server trusts the Office 365 authentication service.
    With Lync Server 2013 or a Lync Server 2013 hybrid deployment
    Collapse this imageExpand this image
    assets folding start collapsed
    Trusting the Office 365 authentication service enables Lync Server to trust connection attempts from Exchange Online. For more information about this step, go to the following TechNet website:
    Collapse this imageExpand this image
    assets folding end collapsed

MORE INFORMATION

The following table lists the supported features and configurations for Lync and Exchange integration. For more information about supported Lync hybrid scenarios, go to the following Microsoft TechNet website:
Supported Lync Server 2013 Hybrid Configurations
Collapse this tableExpand this table
Lync and Exchange integration featuresOutlook integration (EWS, MAPI)Outlook Web App integration (IM/P)Outlook Web App online meetings (scheduling)Unified Contact StoreHigh-resolution contact photos
Lync Online onlySupportedSupportedSupportedSupportedSupported
Lync Server 2013 onlySupportedSupportedNot supportedNot supportedSupported
Lync Server 2013 hybrid deployment with Lync OnlineSupportedSupportedSupported*Supported*Supported
*Supported only for Lync Online users in the hybrid deployment.

The following Microsoft Knowledge Base articles will help you troubleshoot specific features of Exchange and Lync integration. If you’re still having problems with any specific feature after you follow the steps in this article, see the appropriate articles in this section for more information.

Integration with Outlook and Exchange Web Services

  • 2436962 "There was a problem connecting to Microsoft Office Outlook. The email address used in your default Outlook profile is different" error message when you sign in to Lync Online
  • 2787614 Conversation history, contact cards, Free/Busy, and Out of Office information are unavailable when Lync fails to connect to Exchange
  • 2298541 You’re repeatedly prompted for Exchange credentials after you sign in to Lync

Exchange Unified Contact Store and the Lync contact list

  • 2859882 The Lync Online contact list is empty or isn't available for users who have Exchange Online mailboxes
  • 2435699 Contacts in Lync appear offline or aren't searchable in the address book
  • 2811654 Lync contact list is empty or read-only after a user's Exchange mailbox is disconnected, unlicensed, or moved
  • 2757458 Users are unable to modify their contact lists in Lync 2010 and Lync for Mac 2011

Exchange high-resolution contact photos in Lync

  • 2497721 User contact photos in Lync aren't displayed correctly
  • 2860366 You can't upload a photo from Lync 2013 to Lync Online

Instant messaging and online meeting scheduling in Outlook Web App

  • 2565604 Can't schedule Lync online meetings, see presence info, or send IMs from Outlook Web App in Office 365

Still need help? Go to the Office 365 Community website.

Properties

Article ID: 2614614 - Last Review: July 2, 2014 - Revision: 7.0
Applies to
  • Microsoft Exchange Online
  • Microsoft Lync Online
Keywords: 
o365 vkbportal231 o365e o365a o365m o365022013 hybrid KB2614614

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com