-
Title
Working Elsewhere - FreeBusy request is not working with Working o00 Outlook calender entries -
Description
The FreeBusy lookup is not working for calendar entries that are classified as "Working Elsewhere" in Exchange. In the domino console the following error appears: 32,BTFreeBusy client: Server was unable to process request. ---> Call failed to the Exchange Web Services for - GetUserAvailability() ---> There is an error in XML document (1, 7655). ---> Instance validation error: 'WorkingElsewhere' is not a valid value -
Cause
The “WorkingElsewhere” value in the LegacyFreeBusyType enum was introduced in Exchange 2013 and is classified as an edge case, meaning the uptake of this feature was not widespread and although it is still part of Exchange / O365 it is not obvious how to set the status and is partly hidden.
Microsoft has issued a Tech Note on how to fix this issue for individual users while they deprecate the feature.
Free/Busy shows slashed lines in Scheduling Assistant (microsoft.com)
This issue was also reported by some customers in 2017. - Exchange 2010 - Outlook 2013 working elsewhere (microsoft.com)
-
Resolution
This "edge case" issue has been submitted to Development for inclusion in a future release, but due to the low priority and uptake, there is no date for an automated fix yet.
The resolution is to follow the Microsoft guidelines to remove "Working Elsewhere" for mailboxes where this would cause an issue.
Free/Busy shows slashed lines in Scheduling Assistant (microsoft.com)