8 Appendix C: Product Behavior

  • Article

The information in this specification is applicable to the following Microsoft products or supplemental software. References to product versions include updates to those products.

  • Microsoft Exchange Server 2007

  • Microsoft Exchange Server 2010

  • Microsoft Exchange Server 2013

  • Microsoft Exchange Server 2016

  • Microsoft Exchange Server 2019

  • Microsoft Office Outlook 2007

  • Microsoft Outlook 2010

  • Microsoft Outlook 2013

  • Microsoft Outlook 2016

  • Microsoft Outlook 2019

  • Microsoft Outlook 2021

  • Microsoft Outlook 2024 Preview

Exceptions, if any, are noted in this section. If an update version, service pack or Knowledge Base (KB) number appears with a product name, the behavior changed in that update. The new behavior also applies to subsequent updates unless otherwise specified. If a product edition appears with the product version, behavior is different in that product edition.

Unless otherwise specified, any statement of optional behavior in this specification that is prescribed using the terms "SHOULD" or "SHOULD NOT" implies product behavior in accordance with the SHOULD or SHOULD NOT prescription. Unless otherwise specified, the term "MAY" implies that the product does not follow the prescription.

<1> Section 2.1.1:  Office Outlook 2007 does not send the X-ClientStatistics header. Exchange 2007 ignores the X-ClientStatistics header.

<2> Section 2.2: Office Outlook 2007 does not include the MessageID header in requests. Exchange 2007 ignores the MessageID header.

<3> Section 3.1.4.1: When a user creates a meeting request, adds attendees, and switches to the scheduling assistant to view the attendees' free/busy status, Office Outlook 2007, Microsoft Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 issue a request to the Availability Web service.

<4> Section 3.1.4.1:  Exchange 2007, Exchange 2010, and Microsoft Exchange Server 2010 Service Pack 1 (SP1) do not use the Impersonation, TimeZoneContext, and RequestVersion headers. These headers were introduced in Microsoft Exchange Server 2010 Service Pack 2 (SP2).

<5> Section 3.1.4.1.1.1:  Exchange 2007, Exchange 2010, and Exchange 2010 SP1 do not use the Impersonation header. The Impersonation header was introduced in Exchange 2010 SP2.

<6> Section 3.1.4.1.1.1:  Exchange 2007, Exchange 2010, and Exchange 2010 SP1 do not use the TimeZoneContext header. The TimeZoneContext header was introduced in Exchange 2010 SP2.

<7> Section 3.1.4.1.1.1:  Exchange 2007, Exchange 2010, and Exchange 2010 SP1 do not use the RequestVersion header. The RequestVersion header was introduced in Exchange 2010 SP2.

<8> Section 3.1.4.1.3.1:  The default value for Exchange 2007 is 100. The default value for Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 is 20.

<9> Section 3.1.4.1.3.13: The maximum time period for Exchange 2007 and Exchange 2010 is 42 days. The maximum time period for Exchange 2010 SP1, Exchange 2013, Exchange 2016, and Exchange 2019 is 62 days.

<10> Section 3.1.4.1.3.21: Exchange 2007 does not return the SuggestionQuality element in a Suggestion element when the value of the SuggestionQuality element is "Poor".

<11> Section 3.1.4.1.3.22: Exchange 2007 does not return the SuggestionArray element in a SuggestionDayResult element when the value of the DayQuality element is "Poor".

<12> Section 3.1.4.1.4.1: The Availability Web service in Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 supports this by doing an access check with the requester's credentials against the permissions that have been set on the mailbox owner's Calendar folder, as described in [MS-OXCPERM]. The permissions are used to specify an access level that determines the type of information that the requester can view. The following table shows how the access level that is returned from this check is treated.

RequestedView element value (from the GetUserAvailability operation request)

Allowed view based on Access level

Detailed

FreeBusy

No Access

None

-

-

-

MergedOnly

Merged

Merged

Error (InvalidAccessLevelException)

FreeBusy

FreeBusy

FreeBusy

Error (InvalidAccessLevelException)

FreeBusyMerged

FreeBusyMerged

FreeBusyMerged

Error (InvalidAccessLevelException)

Detailed

Detailed

FreeBusy

Error (InvalidAccessLevelException)

DetailedMerged

DetailedMerged

FreeBusyMerged

Error (InvalidAccessLevelException)