Article ID: 2879736 - View products that this article applies to.
Consider the following scenario:
Note This issue does not occur if an Office 365 user uses Microsoft Outlook 2010 to look up an on-premises user’s free/busy data.
This issue occurs because Outlook 2013 defines a new Working Elsewhere free/busy value for calendar items. When Office 365 users request free/busy data, the on-premises Exchange 2010 server incorrectly maps the new free/busy value.
To resolve this issue, install the following update rollup:
(http://support.microsoft.com/kb/2891587/ )Description of Update Rollup 3 for Exchange Server 2010 Service Pack 3
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about how to set Working Elsewhere in Outlook 2013, go to the following Microsoft website:
More information about "Working Elsewhere"
Article ID: 2879736 - Last Review: November 25, 2013 - Revision: 2.0