Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Exchange Server 2013 Cumulative Update 5 breaks free|busy lookup from Exchange Online to Exchange Server 2007

Exchange Server 2013 Cumulative Update 5 breaks free|busy lookup from Exchange Online to Exchange Server 2007

View products that this article applies to.

Symptoms

Consider the following scenario:
  • You have a hybrid deployment of Microsoft Exchange Online in Microsoft Office 365 and of on-premises Microsoft Exchange Server that contains Microsoft Exchange Server 2013 and Microsoft Exchange Server 2007. Or, two organizations are federated, and at least one of them has Exchange Server 2007. 
  • Exchange Server 2013 has Cumulative Update 5 installed.
  • Exchange Server 2013 and Exchange Server 2007 have different external Exchange Web Services (EWS) URL namespaces.
In this scenario, free/busy lookup from Office 365 mailboxes to on-premises Exchange Server 2007 mailboxes does not work.

↑ Back to the top

Cause

This issue occurs because the Exchange Server 2013 Autodiscover service returns the legacy namespace that is configured on Exchange Server 2007 EWS virtual directory after you apply Cumulative Update 5. However, Exchange Server 2007 does not understand the availability call that is coming in from the Exchange Online mailboxes and the Wssecurity authentication method.

Note Prior to Cumulative Update 5, when an Exchange Online mailbox queries the free/busy information about an Exchange Server 2007 mailbox, Exchange Server 2013 returns the Exchange Server 2013 EWS endpoint and performs the Wssecurity authentication successfully, and then proxies the EWS traffic to the Exchange Server 2007 Client Access servers.

↑ Back to the top

Resolution

To resolve this issue, install Cumulative Update 7 for Exchange Server 2013.

↑ Back to the top

Workaround

To work around this issue, configure the TargetSharingEpr value in the cloud-based Organization Relationship to point to the external Exchange Server 2013 EWS endpoint.

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

Keywords: kbqfe, kbfix, kbsurveynew, kbexpertiseinter, kb

↑ Back to the top

Article Info
Article ID : 3005391
Revision : 1
Created on : 1/7/2017
Published on : 12/9/2014
Exists online : False
Views : 217