8 Appendix C: 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 2007

  • Microsoft Exchange Server 2010

  • Microsoft Exchange Server 2013

  • Microsoft Exchange Server 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.2.4.1:  Exchange 2007 and Exchange 2010 do not support the AddressListIdType complex type.

<2> Section 2.2.4.5:  Exchange 2007 and Exchange 2010 do not support the DistinguishedFolderId element in the BaseFolderType complex type.

<3> Section 2.2.4.5:  Exchange 2007 and Exchange 2010 do not support the PolicyTag element.

<4> Section 2.2.4.5:  Exchange 2007 and Exchange 2010 do not support the ArchiveTag element.

<5> Section 2.2.4.5:  Exchange 2007, Exchange 2010, and Exchange 2013 do not support the ReplicaList element.

<6> Section 2.2.4.8:  Exchange 2007, Exchange 2010, and Exchange 2013 do not support the ConsumerCalendarIdType complex type.

<7> Section 2.2.4.13:  Exchange 2007, Exchange 2010, Exchange 2013, and Exchange 2016 do not use this value to indicate the managed folder can be deleted.

<8> Section 2.2.4.13:  Exchange 2007, Exchange 2010, Exchange 2013, and Exchange 2016 do not use this value to indicate the managed folder can be renamed or moved.

<9> Section 2.2.4.15:  Exchange 2007 and Exchange 2010 will return an ErrorInvalidPermissionSettings ([MS-OXWSCDATA] section 2.2.5.24) response code if any field of BasePermissionType other than UserId field is set, and the PermissionLevel field is not set to "Custom".

<10> Section 2.2.4.16:  Exchange 2007, Exchange 2010, and Exchange 2013 do not support the ConsumerCalendarId element.

<11> Section 2.2.5.3:  In Microsoft Exchange Server 2013 Service Pack 1 (SP1) and Exchange 2016 the user can create items in the folder and read those items.

<12> Section 3.1.4.1:  Exchange 2013 and Exchange 2016 do not support the CopyFolder operation if either the source folder or the destination folder is a public folder.

<13> Section 3.1.4.5:  Exchange 2013 and Exchange 2016 do not support the EmptyFolder operation for use with public folders.

<14> Section 3.1.4.5: Exchange 2007 and the initial release version of Exchange 2010 do not include the EmptyFolder operation.

Show: