7 Appendix B: Product Behavior

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

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.2.2.3:  The X-ClientCanHandle header is used to indicate the capabilities that the client supports when the client is not Outlook. Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019 do not use this header. Exchange 2007, Exchange 2010, and the initial release of Exchange 2013 do not support processing of the X-ClientCanHandle header. Exchange 2013 cumulative update 6, Exchange 2016, and Exchange 2019 support processing of the X-ClientCanHandle header.

<2> Section 2.2.4.1.1.1.1: Exchange 2007 and the initial release version of Exchange 2010 do not include the AutoDiscoverSMTPAddress element. The AutoDiscoverSMTPAddress element was introduced in Microsoft Exchange Server 2010 Service Pack 1 (SP1).

<3> Section 2.2.4.1.1.1.2: Exchange 2007, and the initial release version of Exchange 2010 do not include the DefaultABView element. The DefaultABView element was introduced in Exchange 2010 SP1.

<4> Section 2.2.4.1.1.2.3: The AlternativeMailbox element is not supported by Exchange 2007.

<5> Section 2.2.4.1.1.2.3.1: The DisplayName element is not supported by Exchange 2007.

<6> Section 2.2.4.1.1.2.3.2: The LegacyDN element is not supported by Exchange 2007.

<7> Section 2.2.4.1.1.2.3.3: The Server element is not supported by Exchange 2007.

<8> Section 2.2.4.1.1.2.3.4:  Exchange 2007 and Exchange 2010 do not support the SmtpAddress element. Office Outlook 2007 and Outlook 2010 ignore the SmtpAddress element.

<9> Section 2.2.4.1.1.2.3.5: The Type element is not supported by Exchange 2007.

<10> Section 2.2.4.1.1.2.3.5:  Exchange 2007 and Exchange 2010 do not support the "TeamMailbox" value for the Type element. Office Outlook 2007 and Outlook 2010 ignore AlternativeMailbox elements with a value of "TeamMailbox" in the child Type element.

<11> Section 2.2.4.1.1.2.4.4:  The Negotiate authentication method is not implemented in Exchange 2007, Exchange 2010, Office Outlook 2007, or Outlook 2010.

<12> Section 2.2.4.1.1.2.4.4:  The "anonymous" value for the AuthPackage element is not implemented in Exchange 2007, Exchange 2010, Office Outlook 2007, or Outlook 2010.

<13> Section 2.2.4.1.1.2.4.9: Exchange 2007 does not support the EcpUrl element.

<14> Section 2.2.4.1.1.2.4.10: Exchange 2007 does not support the EcpUrl-aggr element.

<15> Section 2.2.4.1.1.2.4.11:  Exchange 2007 and Exchange 2010 do not support the EcpUrl-extinstall element. Office Outlook 2007 and Outlook 2010 ignore this element.

<16> Section 2.2.4.1.1.2.4.12: Exchange 2007 does not support the EcpUrl-mt element.

<17> Section 2.2.4.1.1.2.4.13:  Exchange 2007 and Exchange 2010 do not support the EcpUrl-photo element. Office Outlook 2007 and Outlook 2010 ignore this element.

<18> Section 2.2.4.1.1.2.4.14: Exchange 2007 and Exchange 2010 do not support the EcpUrl-publish element.

<19> Section 2.2.4.1.1.2.4.15: Exchange 2007 does not support the EcpUrl-ret element.

<20> Section 2.2.4.1.1.2.4.16: Exchange 2007 does not support the EcpUrl-sms element.

<21> Section 2.2.4.1.1.2.4.17:  Exchange 2007 and Exchange 2010 do not support the EcpUrl-tm element. Office Outlook 2007 and Outlook 2010 ignore this element.

<22> Section 2.2.4.1.1.2.4.18:  Exchange 2007 and Exchange 2010 do not support the EcpUrl-tmCreating element. Office Outlook 2007 and Outlook 2010 ignore this element.

<23> Section 2.2.4.1.1.2.4.19:  Exchange 2007 and Exchange 2010 do not support the EcpUrl-tmEditing element. Office Outlook 2007 and Outlook 2010 ignore this element.

<24> Section 2.2.4.1.1.2.4.20:  Exchange 2007 and Exchange 2010 do not support the EcpUrl-tmHiding element. Office Outlook 2007 and Outlook 2010 ignore this element.

<25> Section 2.2.4.1.1.2.4.21: Exchange 2007 does not support the EcpUrl-um element.

<26> Section 2.2.4.1.1.2.4.26:  Exchange 2007, Exchange 2010, and the initial release of Exchange 2013 don't support the GroupingInformation element. The GroupingInformation element was introduced in Microsoft Exchange Server 2013 Service Pack 1 (SP1).

<27> Section 2.2.4.1.1.2.4.27.1:  The "LiveIdFba" value of the AuthenticationMethod attribute is not implemented in Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, Exchange 2019, Office Outlook 2007, Outlook 2010, Outlook 2013, Outlook 2016, and Outlook 2019.

<28> Section 2.2.4.1.1.2.4.38:  Exchange 2007, Exchange 2010, Office Outlook 2007, and Outlook 2010 do not support the ServerExclusiveConnect element.

<29> Section 2.2.4.1.1.2.4.41:  Exchange 2007 and Exchange 2010 do not support the EcpUrl-extinstall element. Office Outlook 2007 and Outlook 2010 ignore this element.

<30> Section 2.2.4.1.1.2.4.46:  Exchange 2007 and Exchange 2010 do not support the "EXHTTP" value for the Type element. Office Outlook 2007 and Outlook 2010 ignore Protocol elements with a Type child element that has a value of "EXHTTP".

<31> Section 2.2.4.1.1.2.4.46:  Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not support the "POP3" value for the Type element.

<32> Section 2.2.4.1.1.2.4.46:  Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not support the "SMTP" value for the Type element.

<33> Section 2.2.4.1.1.2.4.46:  Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not support the "IMAP" value for the Type element.

<34> Section 2.2.4.1.1.2.4.46:  Exchange 2007, Exchange 2010, Exchange 2013, Exchange 2016, and Exchange 2019 do not support the "DAV" value for the Type element.

<35> Section 2.2.4.1.1.2.5: Exchange 2007 and Exchange 2010 do not support the PublicFolderInformation element. Office Outlook 2007 and Outlook 2010 ignore the PublicFolderInformation element.

<36> Section 3.1.5.4:  Office Outlook 2007 and Outlook 2010 ignore the ServerExclusiveConnect element.

<37> Section 3.1.5.4:  Office Outlook 2007 and Outlook 2010 ignore Protocol elements that contain a Type element with the "EXHTTP" value, and do not ignore Protocol elements that contain a Type element with the "EXPR" value in this case.

<38> Section 3.1.5.4:  Office Outlook 2007 and Outlook 2010 ignore Protocol elements that contain a Type element with the "EXHTTP" value.

<39> Section 3.2.5:  Exchange 2007, Exchange 2010, and the initial release of Exchange 2013 do not support processing of the X-MapiHttpCapability header. Exchange 2013 SP1, Exchange 2016, and Exchange 2019 support processing of the X-MapiHttpCapability header only when it is specifically enabled.