You are currently offline, waiting for your internet to reconnect

OAuth authentication fails in a proxy scenario between Exchange Server 2013 hybrid on-premises and Office 365

When you set up OAuth authentication between an Exchange Server 2013 hybrid on-premises installation and Office 365, OAuth authentication may fail in a proxy scenario.

If the on-premises Exchange organization can successfully connect to Exchange Online, you may receive the following error:
System.Net.WebException: Unable to connect to the remote
server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond IP_Address:443
at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)

If the direction from Exchange Online organization to the on-premises Exchange organization is successful, the Free/Busy information works only from a cloud user to an Exchange on-premises user.
This issue occurs because OAuth authentication does not honor InternetWebProxy. This causes an OAuth token retrieval failure.
To fix this issue, install Cumulative Update 12 for Exchange Server 2013 or a later cumulative update for Exchange Server 2013.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Learn about the terminology that Microsoft uses to describe software updates.

Article ID: 3137585 - Last Review: 03/15/2016 15:30:00 - Revision: 1.0

Microsoft Exchange Server 2013 Enterprise, Microsoft Exchange Server 2013 Standard

  • kbqfe kbsurveynew kbfix kbexpertiseinter KB3137585