6 Appendix A: Product Behavior

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

  • Microsoft Exchange Server 2003

  • Microsoft Exchange Server 2007

  • Microsoft Exchange Server 2010

  • Microsoft Exchange Server 2013

  • Microsoft Exchange Server 2016

  • Microsoft Office Outlook 2003

  • Microsoft Office Outlook 2007

  • Microsoft Outlook 2010

  • Microsoft Outlook 2013

  • Microsoft Outlook 2016

Exceptions, if any, are noted below. If a service pack or Quick Fix Engineering (QFE) number appears with the product version, behavior changed in that service pack or QFE. The new behavior also applies to subsequent service packs of the product 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: Exchange 2003 and Exchange 2007 point the client to Active Directory Domain Services (AD DS), which implements the NSPI methods as described in [MS-NSPI]. Exchange 2010, Exchange 2013, and Exchange 2016 point the client to the Exchange NSPI server, which implements the NSPI methods as described in [MS-OXNSPI]. The only exception is when Exchange 2010, Exchange 2013, or Exchange 2016 is installed on an Active Directory® global catalog server, in which case the server points the client to AD DS.

<2> Section 2.1:  Exchange 2003, Exchange 2007, Exchange 2010, the initial release of Exchange 2013, Office Outlook 2003, Office Outlook 2007, Outlook 2010, and the initial release of Outlook 2013 do not support the Messaging Application Programming Interface (MAPI) Extensions for HTTP. The MAPI Extensions for HTTP were introduced in Microsoft Exchange Server 2013 Service Pack 1 (SP1) and Microsoft Outlook 2013 Service Pack 1 (SP1).

<3> Section 2.2:  Exchange 2003, Exchange 2007, Exchange 2010, the initial release of Exchange 2013, Office Outlook 2003, Office Outlook 2007, Outlook 2010, and the initial release of Outlook 2013 do not support the Messaging Application Programming Interface (MAPI) Extensions for HTTP. The MAPI Extensions for HTTP were introduced in Exchange 2013 SP1 and Outlook 2013 SP1.

<4> Section 2.2.1.1: Exchange 2003 and Exchange 2007 point the client to AD DS, which implements the PermanentEntryId structure as described in [MS-NSPI]. Exchange 2010, Exchange 2013, and Exchange 2016 point the client to the Exchange NSPI server, which implements the PermanentEntryId structure as described in [MS-OXNSPI] section 2.2.9.3. The only exception is when Exchange 2010, Exchange 2013, or Exchange 2016 is installed on an Active Directory global catalog server, in which case the server points the client to AD DS and implements the PermanentEntryId structure as described in [MS-NSPI].

<5> Section 2.2.1.1: The OAB version 4 implementation in Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, and Exchange 2016 includes the following properties, which are not included in objects on an NSPI server: PidTagAddressBookDistributionListExternalMemberCount (section 2.2.3.30), PidTagAddressBookDistributionListMemberCount (section 2.2.3.29), and PidTagOfflineAddressBookTruncatedProperties property ([MS-OXOAB] section 2.9.2.2).

<6> Section 2.2.2: Retrieval of information about the address book hierarchy by using the OAB Public Folder Retrieval Protocol, as described in [MS-OXPFOAB], is supported by Exchange 2003, Exchange 2007, and Exchange 2010.

<7> Section 2.2.2.3: Exchange 2003 and Exchange 2007 point the client to AD DS, which implements the NspiBind method as described in [MS-NSPI]. Exchange 2010, Exchange 2013, and Exchange 2016 point the client to the Exchange NSPI server, which implements the NspiBind method as described in [MS-OXNSPI] section 3.1.4.1.1. The only exception is when Exchange 2010, Exchange 2013, or Exchange 2016 is installed on an Active Directory global catalog server, in which case the server points the client to AD DS and implements the NSPIBind method as described in [MS-NSPI].

<8> Section 2.2.2.3:  Exchange 2003, Exchange 2007, Exchange 2010, the initial release of Exchange 2013, Office Outlook 2003, Office Outlook 2007, Outlook 2010, and the initial release of Outlook 2013 do not support the Bind request type response. The Bind request type response was introduced in Exchange 2013 SP1 and Outlook 2013 SP1.

<9> Section 2.2.3: Exchange 2003 and Exchange 2007 point the client to AD DS, which implements the NSPI methods as described in [MS-NSPI]. Exchange 2010, Exchange 2013, and Exchange 2016 point the client to the Exchange NSPI server, which implements the NSPI methods as described in [MS-OXNSPI]. The only exception is when Exchange 2010, Exchange 2013, or Exchange 2016 is installed on an Active Directory global catalog server, in which case the server points the client to AD DS and implements the NSPI methods as described in [MS-NSPI].

<10> Section 2.2.3:  Exchange 2003, Exchange 2007, Exchange 2010, the initial release of Exchange 2013, Office Outlook 2003, Office Outlook 2007, Outlook 2010, and the initial release of Outlook 2013 do not support the HTTP request types for an address book server endpoint. The HTTP request types for an address book server endpoint were introduced in Exchange 2013 SP1 and Outlook 2013 SP1.

<11> Section 2.2.3.2: Exchange 2003 and Exchange 2007 point the client to AD DS, which implements the PermanentEntryID and EphemeralEntryID structures as described in [MS-NSPI]. Exchange 2010, Exchange 2013, and Exchange 2016 point the client to the Exchange NSPI server, which implements the PermanentEntryID and EphemeralEntryID structures as described in [MS-OXNSPI]. The only exception is when Exchange 2010, Exchange 2013, or Exchange 2016 is installed on an Active Directory global catalog server, in which case the server points the client to AD DS and implements the PermanentEntryID and EphemeralEntryID structures as described in [MS-NSPI].

<12> Section 2.2.3.9: The PidTagAddressBookPhoneticDisplayName property (section 2.2.3.9) is not used in Exchange 2003 servers or Office Outlook 2003 clients.

<13> Section 2.2.3.11: Exchange 2003 and Exchange 2007 point the client to AD DS, which implements the display type values as described in [MS-NSPI]. Exchange 2010, Exchange 2013, and Exchange 2016 point the client to the Exchange NSPI server, which implements the display type values as described in [MS-OXNSPI] section 2.2.1.3. The only exception is when Exchange 2010, Exchange 2013, or Exchange 2016 is installed on an Active Directory global catalog server, in which case the server points the client to AD DS and implements the display type values as described in [MS-NSPI].

<14> Section 2.2.3.12: Exchange 2003 and Exchange 2007 point the client to AD DS, which implements the display type values as described in [MS-NSPI]. Exchange 2010, Exchange 2013, and Exchange 2016 point the client to the Exchange NSPI server, which implements the display type values as described in [MS-OXNSPI] section 2.2.1.3. The only exception is when Exchange 2010, Exchange 2013, or Exchange 2016 is installed on an Active Directory global catalog server, in which case the server points the client to AD DS and implements the display type values as described in [MS-NSPI].

<15> Section 2.2.3.24:  The PidTagAddressBookSeniorityIndex property (section 2.2.3.24) is not used by Exchange 2003, Exchange 2007, Office Outlook 2003, or Office Outlook 2007.

<16> Section 2.2.3.25:  The PidTagAddressBookObjectGuid property (section 2.2.3.25) is not used by Exchange 2003, Exchange 2007, Office Outlook 2003, or Office Outlook 2007.

<17> Section 2.2.3.26: The PidTagAddressBookSenderHintTranslations property (section 2.2.3.26) is not used by Exchange 2003, Exchange 2007, Office Outlook 2003, or Office Outlook 2007.

<18> Section 2.2.3.27: The PidTagAddressBookDeliveryContentLength property (section 2.2.3.27) is not used by Exchange 2003, Exchange 2007, Office Outlook 2003, or Office Outlook 2007.

<19> Section 2.2.3.28: The PidTagAddressBookModerationEnabled property (section 2.2.3.28) is not used by Exchange 2003, Exchange 2007, Office Outlook 2003, or Office Outlook 2007.

<20> Section 2.2.3.29: The PidTagAddressBookDistributionListMemberCount property (section 2.2.3.29) is not used by Exchange 2003, Exchange 2007, Office Outlook 2003, or Office Outlook 2007.

<21> Section 2.2.3.30: The PidTagAddressBookDistributionListExternalMemberCount property (section 2.2.3.30) is not used by Exchange 2003, Exchange 2007, Office Outlook 2003, or Office Outlook 2007.

<22> Section 2.2.3.35: The PidTagAddressBookDisplayTypeExtended property (section 2.2.3.35) is not used in Exchange 2003 servers or Office Outlook 2003 clients.

<23> Section 2.2.4.10: The PidTagAddressBookPhoneticGivenName property (section 2.2.4.10) is not used in Exchange 2003 servers or Office Outlook 2003 clients.

<24> Section 2.2.4.11: The PidTagAddressBookPhoneticSurname property (section 2.2.4.11) is not used in Exchange 2003 servers or Office Outlook 2003 clients.

<25> Section 2.2.4.12: The PidTagAddressBookPhoneticCompanyName property (section 2.2.4.12) is not used by Exchange 2003 servers or Office Outlook 2003 clients.

<26> Section 2.2.4.13: The PidTagAddressBookPhoneticDepartmentName property (section 2.2.4.13) is not used by Exchange 2003 servers or Office Outlook 2003 clients.

<27> Section 2.2.4.36.4: The PidTagAddressBookPhoneticDisplayName property (section 2.2.3.9) is not used in Exchange 2003 or Office Outlook 2003 servers.

<28> Section 2.2.4.36.5: The PidTagAddressBookPhoneticDisplayName property (section 2.2.3.9) is not used in Exchange 2003 or Office Outlook 2003 servers.

<29> Section 2.2.4.36.7: The PidTagAddressBookPhoneticDisplayName property (section 2.2.3.9) is not used in Exchange 2003 or Office Outlook 2003 servers.

<30> Section 2.2.4.36.9: The PidTagAddressBookPhoneticDisplayName property (section 2.2.3.9) is not used in Exchange 2003 or Office Outlook 2003 servers.

<31> Section 2.2.4.39: The PidTagAddressBookOrganizationalUnitRootDistinguishedName property (section 2.2.4.39) is not used by Office Outlook 2003 clients.

<32> Section 2.2.4.40: The PidTagThumbnailPhoto property (section 2.2.4.40) is not used by Exchange 2003, Exchange 2007, Office Outlook 2003, or Office Outlook 2007.

<33> Section 2.2.4.41: The PidTagSpokenName property (section 2.2.4.41) is not used by Exchange 2003, Exchange 2007, Office Outlook 2003, or Office Outlook 2007.

<34> Section 2.2.4.42: The PidTagAddressBookAuthorizedSenders property (section 2.2.4.42) is not used by Exchange 2003, Exchange 2007, Office Outlook 2003, or Office Outlook 2007.

<35> Section 2.2.4.43: The PidTagAddressBookUnauthorizedSenders property (section 2.2.4.43) is not used by Exchange 2003, Exchange 2007, Office Outlook 2003, or Office Outlook 2007.

<36> Section 2.2.4.44: The PidTagAddressBookDistributionListMemberSubmitAccepted property (section 2.2.4.44) is not used by Exchange 2003, Exchange 2007, Office Outlook 2003, or Office Outlook 2007.

<37> Section 2.2.4.45: The PidTagAddressBookDistributionListMemberSubmitRejected property (section 2.2.4.45) is not used by Exchange 2003, Exchange 2007, Office Outlook 2003, or Office Outlook 2007.

<38> Section 2.2.5: Exchange 2003 and Exchange 2007 point the client to AD DS, which implements the tables as described in [MS-NSPI]. Exchange 2010, Exchange 2013, and Exchange 2016 point the client to the Exchange NSPI server, which implements the tables as described in [MS-OXNSPI] section 3.1.4.4.2.2. The only exception is when Exchange 2010, Exchange 2013, or Exchange 2016 is installed on an Active Directory global catalog server, in which case the server points the client to AD DS and implements the tables as described in [MS-NSPI].

<39> Section 2.2.5: Exchange 2003 and Exchange 2007 point the client to AD DS, which implements the NspiGetMatches and NspiModLinkAtt methods as described in [MS-NSPI]. Exchange 2010, Exchange 2013, and Exchange 2016 point the client to the Exchange NSPI server, which implements the NspiGetMatches and NspiModLinkAtt methods, as described in [MS-OXNSPI]. The only exception is when Exchange 2010, Exchange 2013, or Exchange 2016 is installed on an Active Directory® global catalog server, in which case the server points the client to AD DS and implements the NspiGetMatches and NspiModLinkAtt methods as described in [MS-NSPI].

<40> Section 2.2.5:  Exchange 2003, Exchange 2007, Exchange 2010, the initial release of Exchange 2013, Office Outlook 2003, Office Outlook 2007, Outlook 2010, and the initial release of Outlook 2013 do not support the GetMatches request type and the ModLinkAtt request type. The GetMatches request type and the ModLinkAtt request type were introduced in Exchange 2013 SP1 and Outlook 2013 SP1.

<41> Section 2.2.5.3:  The PidTagAddressBookIsMemberOfDistributionList property (section 2.2.5.3) is not used by Exchange 2003, Exchange 2007, Office Outlook 2003, or Office Outlook 2007.

<42> Section 2.2.6.1:  The PidTagAddressBookMember property (section 2.2.6.1) is not used by Exchange 2003, Exchange 2007, Office Outlook 2003, or Office Outlook 2007.

<43> Section 2.2.6.5:  The PidTagAddressBookHierarchicalIsHierarchicalGroup property (section 2.2.6.5) is not used by Exchange 2003, Exchange 2007, Office Outlook 2003, or Office Outlook 2007.

<44> Section 2.2.7: The PidTagAddressBookOrganizationalUnitRootDistinguishedName property (section 2.2.4.39) is not used by Office Outlook 2003 clients.

<45> Section 2.2.7.2: Office Outlook 2003 clients do not recognize departmental groups. If the department hierarchy is represented by using departmental groups, these clients run as if the PidTagAddressBookHierarchicalRootDepartment property (section 2.2.7.2) is not present, and there is no hierarchical representation of the departments.

<46> Section 2.2.8: If a server represents a department hierarchy by using both Department objects and departmental groups, Office Outlook 2003 only makes use of the hierarchy that is represented by the Department objects, and Office Outlook 2007, Outlook 2010, Outlook 2013, and Outlook 2016 only make use of the hierarchy that is represented by the departmental groups. Note that a single hierarchy cannot be represented by a combination of the two schemas.

<47> Section 2.2.10.1: Exchange 2003 and Exchange 2007 point the client to AD DS, which implements the NspiGetMatches methods as described in [MS-NSPI]. Exchange 2010, Exchange 2013, and Exchange 2016 point the client to the Exchange NSPI server, which implements the NspiGetMatches methods as described in [MS-OXNSPI] section 3.1.4.1.10. The only exception is when Exchange 2010, Exchange 2013, or Exchange 2016 is installed on an Active Directory global catalog server, in which case the server points the client to AD DS and implements the NspiGetMatches method as described in [MS-NSPI].

<48> Section 2.2.10.1:  Exchange 2003, Exchange 2007, Exchange 2010, the initial release of Exchange 2013, Office Outlook 2003, Office Outlook 2007, Outlook 2010, and the initial release of Outlook 2013 do not support the GetMatches request body. The GetMatches request body was introduced in Exchange 2013 SP1 and Outlook 2013 SP1.

<49> Section 2.2.10.1: Exchange 2003 and Exchange 2007 point the client to AD DS, which implements ANR as described in [MS-NSPI]. Exchange 2010, Exchange 2013, and Exchange 2016 point the client to the Exchange NSPI server, which implements ANR as described in [MS-OXNSPI] section 3.1.4.7. The only exception is when Exchange 2010, Exchange 2013, or Exchange 2016 is installed on an Active Directory global catalog server, in which case the server points the client to AD DS and implements the ANR as described in [MS-NSPI].

<50> Section 2.2.10.1: Office Outlook 2003, Office Outlook 2007, Outlook 2010, Outlook 2013, and Outlook 2016 perform a lookup of SMTP addresses by constructing a specific target string for ambiguous name resolution (ANR) that is understood by Exchange 2003, Exchange 2007, Exchange 2010, Exchange 2013, and Exchange 2016 servers. When the target string starts with "=SMTP: " and is followed by a valid SMTP address, the NSPI server returns exactly one match, if any are found. The match will be an address book entry that has the target string as a valid SMTP address. Such a target string can be specified as a PidTagAnr property restriction to the NspiGetMatches method, as described in [MS-OXNSPI] section 3.1.4.1.10. Such a target string is also understood by the paStr parameter to the NspiResolveNames method, as specified in [MS-OXNSPI] section 3.1.4.1.16, or the paWStr parameter to the NspiResolveNamesW method, as specified in [MS-OXNSPI] section 3.1.4.1.17.

<51> Section 3.1.3:  Exchange 2003, Exchange 2007, Exchange 2010, the initial release of Exchange 2013, Office Outlook 2003, Office Outlook 2007, Outlook 2010, and the initial release of Outlook 2013 do not support the Messaging Application Programming Interface (MAPI) Extensions for HTTP. The Messaging Application Programming Interface (MAPI) Extensions for HTTP were introduced in Outlook 2013 SP1 and Exchange 2013 SP1.

<52> Section 3.1.3.1: Exchange 2003 and Exchange 2007 point the client to AD DS, which implements the NspiBind method as described in [MS-NSPI]. Exchange 2010, Exchange 2013, and Exchange 2016 point the client to the Exchange NSPI server, which implements the NspiBind method as described in [MS-OXNSPI] section 3.1.4.1.1. The only exception is when Exchange 2010, Exchange 2013, or Exchange 2016 is installed on an Active Directory global catalog server, in which case the server points the client to AD DS and implements the NspiBind method as described in [MS-NSPI].

<53> Section 3.1.3.2:  Exchange 2003, Exchange 2007, Exchange 2010, the initial release of Exchange 2013, Office Outlook 2003, Office Outlook 2007, Outlook 2010, and the initial release of Outlook 2013 do not support the Messaging Application Programming Interface (MAPI) Extensions for HTTP. The Messaging Application Programming Interface (MAPI) Extensions for HTTP were introduced in Outlook 2013 SP1 and Exchange 2013 SP1.

<54> Section 3.1.3.3:  Retrieval of address lists by using the OAB Public Folder Retrieval Protocol, as described in [MS-OXPFOAB], is supported by Exchange 2003, Exchange 2007, and Exchange 2010.

<55> Section 3.1.4.1: Exchange 2003 and Exchange 2007 point the client to AD DS, which implements the NspiGetSpecialTable method as described in [MS-NSPI]. Exchange 2010, Exchange 2013, and Exchange 2016 point the client to the Exchange NSPI server, which implements the NspiGetSpecialTable method as described in [MS-OXNSPI] section 3.1.4.1.3. The only exception is when Exchange 2010, Exchange 2013, or Exchange 2016 is installed on an Active Directory global catalog server, in which case the server points the client to AD DS and implements the NspiGetSpecialTable method as described in [MS-NSPI].

<56> Section 3.1.4.1:  Exchange 2003, Exchange 2007, Exchange 2010, the initial release of Exchange 2013, Office Outlook 2003, Office Outlook 2007, Outlook 2010, and the initial release of Outlook 2013 do not support the Messaging Application Programming Interface (MAPI) Extensions for HTTP. The Messaging Application Programming Interface (MAPI) Extensions for HTTP were introduced in Outlook 2013 SP1 and Exchange 2013 SP1.

<57> Section 3.1.4.1:  Retrieval of hierarchy tables by using the OAB Public Folder Retrieval Protocol, as described in [MS-OXPFOAB], is supported by Exchange 2003, Exchange 2007, and Exchange 2010.

<58> Section 3.1.4.2:  Exchange 2003, Exchange 2007, Exchange 2010, the initial release of Exchange 2013, Office Outlook 2003, Office Outlook 2007, Outlook 2010, and the initial release of Outlook 2013 do not support the Messaging Application Programming Interface (MAPI) Extensions for HTTP. The Messaging Application Programming Interface (MAPI) Extensions for HTTP were introduced in Outlook 2013 SP1 and Exchange 2013 SP1.

<59> Section 3.1.4.2: Exchange 2003 and Exchange 2007 point the client to AD DS, which implements the STAT structure as described in [MS-NSPI]. Exchange 2010, Exchange 2013, and Exchange 2016 point the client to the Exchange NSPI server, which implements the STAT structure as described in [MS-OXNSPI] section 2.2.8. The only exception is when Exchange 2010, Exchange 2013, or Exchange 2016 is installed on an Active Directory global catalog server, in which case the server points the client to AD DS and implements the STAT structure as described in [MS-NSPI].

<60> Section 3.1.4.2: Exchange 2003 and Exchange 2007 point the client to AD DS, which implements the NspiUpdateStat method as described in [MS-NSPI]. Exchange 2010, Exchange 2013, and Exchange 2016 point the client to the Exchange NSPI server, which implements the NspiUpdateStat method, as described in [MS-OXNSPI] section 3.1.4.1.4. The only exception is when Exchange 2010, Exchange 2013, or Exchange 2016 is installed on an Active Directory global catalog server, in which case the server points the client to AD DS and implements the NspiUpdateStat method as described in [MS-NSPI].

<61> Section 3.1.4.2:  Exchange 2003, Exchange 2007, Exchange 2010, the initial release of Exchange 2013, Office Outlook 2003, Office Outlook 2007, Outlook 2010, and the initial release of Outlook 2013 do not support the Messaging Application Programming Interface (MAPI) Extensions for HTTP. The Messaging Application Programming Interface (MAPI) Extensions for HTTP were introduced in Outlook 2013 SP1 and Exchange 2013 SP1.

<62> Section 3.1.4.2:  Exchange 2003, Exchange 2007, Exchange 2010, the initial release of Exchange 2013, Office Outlook 2003, Office Outlook 2007, Outlook 2010, and the initial release of Outlook 2013 do not support the Messaging Application Programming Interface (MAPI) Extensions for HTTP. The Messaging Application Programming Interface (MAPI) Extensions for HTTP were introduced in Outlook 2013 SP1 and Exchange 2013 SP1.

<63> Section 3.1.4.2:  Exchange 2003, Exchange 2007, Exchange 2010, the initial release of Exchange 2013, Office Outlook 2003, Office Outlook 2007, Outlook 2010, and the initial release of Outlook 2013 do not support the Messaging Application Programming Interface (MAPI) Extensions for HTTP. The Messaging Application Programming Interface (MAPI) Extensions for HTTP were introduced in Outlook 2013 SP1 and Exchange 2013 SP1.

<64> Section 3.1.4.3: Exchange 2003 and Exchange 2007 point the client to AD DS, which implements the NspiQueryRows method as described in [MS-NSPI]. Exchange 2010, Exchange 2013, and Exchange 2016 point the client to the Exchange NSPI server, which implements the NspiQueryRows method as described in [MS-OXNSPI] section 3.1.4.1.8. The only exception is when Exchange 2010, Exchange 2013, or Exchange 2016 is installed on an Active Directory global catalog server, in which case the server points the client to AD DS and implements the NspiQueryRows method as described in [MS-NSPI].

<65> Section 3.1.4.3:  Exchange 2003, Exchange 2007, Exchange 2010, the initial release of Exchange 2013, Office Outlook 2003, Office Outlook 2007, Outlook 2010, and the initial release of Outlook 2013 do not support the Messaging Application Programming Interface (MAPI) Extensions for HTTP. The Messaging Application Programming Interface (MAPI) Extensions for HTTP were introduced in Outlook 2013 SP1 and Exchange 2013 SP1.

<66> Section 3.1.4.3:  Exchange 2003, Exchange 2007, Exchange 2010, the initial release of Exchange 2013, Office Outlook 2003, Office Outlook 2007, Outlook 2010, and the initial release of Outlook 2013 do not support the Messaging Application Programming Interface (MAPI) Extensions for HTTP. The Messaging Application Programming Interface (MAPI) Extensions for HTTP were introduced in Outlook 2013 SP1 and Exchange 2013 SP1.

<67> Section 3.1.4.3:  Exchange 2003, Exchange 2007, Exchange 2010, the initial release of Exchange 2013, Office Outlook 2003, Office Outlook 2007, Outlook 2010, and the initial release of Outlook 2013 do not support the Messaging Application Programming Interface (MAPI) Extensions for HTTP. The Messaging Application Programming Interface (MAPI) Extensions for HTTP were introduced in Outlook 2013 SP1 and Exchange 2013 SP1.

<68> Section 3.1.4.3:  Exchange 2003, Exchange 2007, Exchange 2010, the initial release of Exchange 2013, Office Outlook 2003, Office Outlook 2007, Outlook 2010, and the initial release of Outlook 2013 do not support the Messaging Application Programming Interface (MAPI) Extensions for HTTP. The Messaging Application Programming Interface (MAPI) Extensions for HTTP were introduced in Outlook 2013 SP1 and Exchange 2013 SP1.

<69> Section 3.1.4.3: Exchange 2003 and Exchange 2007 point the client to AD DS, which implements the PermanentEntryID structure as described in [MS-NSPI]. Exchange 2010, Exchange 2013, and Exchange 2016 point the client to the Exchange NSPI server, which implements the PermanentEntryID structure as described in [MS-OXNSPI] section 2.2.9.3. The only exception is when Exchange 2010, Exchange 2013, or Exchange 2016 is installed on an Active Directory global catalog server, in which case the server points the client to AD DS and implements the PermanentEntryID structure as described in [MS-NSPI].

<70> Section 3.1.4.3:  Exchange 2003, Exchange 2007, Exchange 2010, the initial release of Exchange 2013, Office Outlook 2003, Office Outlook 2007, Outlook 2010, and the initial release of Outlook 2013 do not support the Messaging Application Programming Interface (MAPI) Extensions for HTTP. The Messaging Application Programming Interface (MAPI) Extensions for HTTP were introduced in Outlook 2013 SP1 and Exchange 2013 SP1.

<71> Section 3.1.4.3:  Exchange 2003, Exchange 2007, Exchange 2010, the initial release of Exchange 2013, Office Outlook 2003, Office Outlook 2007, Outlook 2010, and the initial release of Outlook 2013 do not support the Messaging Application Programming Interface (MAPI) Extensions for HTTP. The Messaging Application Programming Interface (MAPI) Extensions for HTTP were introduced in Outlook 2013 SP1 and Exchange 2013 SP1.

<72> Section 3.1.4.3:  Exchange 2003, Exchange 2007, Exchange 2010, the initial release of Exchange 2013, Office Outlook 2003, Office Outlook 2007, Outlook 2010, and the initial release of Outlook 2013 do not support the Messaging Application Programming Interface (MAPI) Extensions for HTTP. The Messaging Application Programming Interface (MAPI) Extensions for HTTP were introduced in Outlook 2013 SP1 and Exchange 2013 SP1.

<73> Section 3.1.4.4: Exchange 2003 and Exchange 2007 point the client to AD DS, which implements the NspiResolveNames

method, as described in [MS-NSPI]. Exchange 2010, Exchange 2013, and Exchange 2016 point the client to the Exchange NSPI server, which implements the NspiResolveNames method, as described in [MS-OXNSPI] section 3.1.4.1.16. The only exception is when Exchange 2010, Exchange 2013, or Exchange 2016 is installed on an Active Directory global catalog server, in which case the server points the client to AD DS and implements the NspiResolveName methods, as described in [MS-NSPI].

<74> Section 3.1.4.4:  Exchange 2003, Exchange 2007, Exchange 2010, the initial release of Exchange 2013, Office Outlook 2003, Office Outlook 2007, Outlook 2010, and the initial release of Outlook 2013 do not support the Messaging Application Programming Interface (MAPI) Extensions for HTTP. The Messaging Application Programming Interface (MAPI) Extensions for HTTP were introduced in Outlook 2013 SP1 and Exchange 2013 SP1.

<75> Section 3.1.4.4:  Exchange 2003, Exchange 2007, Exchange 2010, the initial release of Exchange 2013, Office Outlook 2003, Office Outlook 2007, Outlook 2010, and the initial release of Outlook 2013 do not support the Messaging Application Programming Interface (MAPI) Extensions for HTTP. The Messaging Application Programming Interface (MAPI) Extensions for HTTP were introduced in Outlook 2013 SP1 and Exchange 2013 SP1.

<76> Section 4:  Exchange 2003, Exchange 2007, Exchange 2010, the initial release of Exchange 2013, Office Outlook 2003, Office Outlook 2007, Outlook 2010, and the initial release of Outlook 2013 do not support the Messaging Application Programming Interface (MAPI) Extensions for HTTP protocol. The Messaging Application Programming Interface (MAPI) Extensions for HTTP protocol was introduced in Outlook 2013 SP1 and Exchange 2013 SP1.

<77> Section 5.1:  Exchange 2003, Exchange 2007, Exchange 2010, the initial release of Exchange 2013, Office Outlook 2003, Office Outlook 2007, Outlook 2010, and the initial release of Outlook 2013 do not support the Messaging Application Programming Interface (MAPI) Extensions for HTTP protocol. The Messaging Application Programming Interface (MAPI) Extensions for HTTP protocol was introduced in Outlook 2013 SP1 and Exchange 2013 SP1.

Show: