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 Lync Server 2013

  • Microsoft Exchange Server 2013

  • Microsoft Office Web Apps Server

  • Microsoft SharePoint Server 2013

  • Microsoft SharePoint Foundation 2013

  • Office Online Server

  • Microsoft Skype for Business Server 2015

  • Microsoft SharePoint Server 2016

  • Microsoft Skype for Business Server 2019

  • Microsoft SharePoint Server 2019

  • Microsoft SharePoint Server Subscription Edition

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 3.3.5.1.1:  SharePoint Server 2019, SharePoint Server 2016, SharePoint Server 2013 and Office Web Apps Server do not support the AddActivities operation.

<2> Section 3.3.5.1.2.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the AADUserObjectId field.

<3> Section 3.3.5.1.2.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the AccessTokenExpiry field. SharePoint Server 2019 does not set this field and returns the default value.

<4> Section 3.3.5.1.2.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the AllowAddActivitiesUserBatching field. SharePoint Server 2019 does not set this field and returns the default value.

<5> Section 3.3.5.1.2.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the AllowAdditionalMicrosoftServices field. SharePoint Server 2019 does not set this field and returns the default value.

<6> Section 3.3.5.1.2.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the AllowEarlyFeatures field.

<7> Section 3.3.5.1.2.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the AllowErrorReportPrompt field. SharePoint Server 2019 does not set this field and returns the default value.

<8> Section 3.3.5.1.2.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the AppCatalogUrl field. SharePoint Server 2019 does not set this field and returns the default value.

<9> Section 3.3.5.1.2.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the AppliedPolicyId field. SharePoint Server 2019 does not set this field and returns the default value.

<10> Section 3.3.5.1.2.2:  SharePoint Server 2013 supports the BreadcrumbDocUrl field.

<11> Section 3.3.5.1.2.2:  SharePoint Server 2013 and Office Web Apps Server do not support the ClosePostMessage field.

<12> Section 3.3.5.1.2.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the DirectInvokeDAVUrl field. SharePoint Server 2019 does not set this field and returns the default value.

<13> Section 3.3.5.1.2.2:  Microsoft Excel Online web application does not support DownloadUrl. Instead workbook is retrieved by using a cached copy from Office Online Server.

<14> Section 3.3.5.1.2.2:  SharePoint Server 2013 do not support the EditingCannotSave field. SharePoint Server 2019 and SharePoint Server 2016 do not set this field and return the default value.

<15> Section 3.3.5.1.2.2:  SharePoint Server 2013 and Office Web Apps Server do not support the EditNotificationPostMessage field.

<16> Section 3.3.5.1.2.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the EmbeddingPageOrigin field.

<17> Section 3.3.5.1.2.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the EmbeddingPageSessionInfo field.

<18> Section 3.3.5.1.2.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the EnabledApplicationFeatures field. SharePoint Server 2019 does not set this field and returns the default value.

<19> Section 3.3.5.1.2.2:  SharePoint Server 2013, SharePoint Server 2016 and Office Web Apps Server do not support the FileEmbedCommandPostMessage field. SharePoint Server 2019 does not set this field and returns the default value.

<20> Section 3.3.5.1.2.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the FileEmbedCommandUrl field. SharePoint Server 2019 does not set this field and returns the default value.

<21> Section 3.3.5.1.2.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the FileExtension field. SharePoint Server 2019 does not set this field and returns the default value.

<22> Section 3.3.5.1.2.2:  SharePoint Server 2013 and Office Web Apps Server do not support the FileSharingPostMessage field.

<23> Section 3.3.5.1.2.2:  SharePoint Server 2013, SharePoint Server 2016 and Office Web Apps Server do not support the FileVersionPostMessage field. SharePoint Server 2019 does not set this field and returns the default value.

<24> Section 3.3.5.1.2.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the FileVersionUrl field. SharePoint Server 2019 does not set this field and returns the default value.

<25> Section 3.3.5.1.2.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the HostAuthenticationIdType field. SharePoint Server 2019 does not set this field and returns the default value.

<26> Section 3.3.5.1.2.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the HostDivSyndicationViewUrl field. SharePoint Server 2019 does not set this field and returns the default value.

<27> Section 3.3.5.1.2.2:  SharePoint Server 2013, SharePoint Server 2016 and Office Web Apps Server do not support the InsertImagePostMessage field. SharePoint Server 2019 does not set this field and returns the default value.

<28> Section 3.3.5.1.2.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the IsAnonymousUser field.

<29> Section 3.3.5.1.2.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the IsEduUser field.

<30> Section 3.3.5.1.2.2:  SharePoint Server 2013 does not support the IsYammerEnabled field. SharePoint Server 2019 and SharePoint Server 2016 do not set this field and return the default value.

<31> Section 3.3.5.1.2.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the LastModifiedTime field.

<32> Section 3.3.5.1.2.2:  SharePoint Server 2013 does not support the LicensedOrganization field. SharePoint Server 2019 and SharePoint Server 2016 do not set this field and return the default value.

<33> Section 3.3.5.1.2.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the OfficeCollaborationServiceEndpointUrl field.

<34> Section 3.3.5.1.2.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the OpenInClientCommandUrl field. SharePoint Server 2019 does not set this field and returns the default value.

<35> Section 3.3.5.1.2.2:  SharePoint Server 2013, SharePoint Server 2016 and Office Web Apps Server do not support the OpenInClientPostMessage field. SharePoint Server 2019 does not set this field and returns the default value.

<36> Section 3.3.5.1.2.2:  SharePoint Server 2013, SharePoint Server 2016 and Office Web Apps Server do not support the PermissionsPostMessage field.

<37> Section 3.3.5.1.2.2:  SharePoint Server 2013, SharePoint Server 2016 and Office Web Apps Server do not support the PolicyCheckPostMessage field. SharePoint Server 2019 does not set this field and returns the default value.

<38> Section 3.3.5.1.2.2:  SharePoint Server 2013 does not support the PostMessageOrigin field.

<39> Section 3.3.5.1.2.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the ProtectedFile field. SharePoint Server 2019 does not set this field and returns the default value.

<40> Section 3.3.5.1.2.2:  SharePoint Server 2013, SharePoint Server 2016 and Office Web Apps Server do not support the ReportAbusePostMessage field. SharePoint Server 2019 does not set this field and returns the default value.

<41> Section 3.3.5.1.2.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the ReportAbuseUrl field. SharePoint Server 2019 does not set this field and returns the default value.

<42> Section 3.3.5.1.2.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the SafeLinksStatus field. SharePoint Server 2019 does not set this field and returns the default value.

<43> Section 3.3.5.1.2.2:  SharePoint Server 2019, SharePoint Server 2016 and SharePoint Server 2013 do not set the SHA256 field and return the default value.

<44> Section 3.3.5.1.2.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the SupportedShareUrlTypes field. SharePoint Server 2019 does not set this field and returns the default value.

<45> Section 3.3.5.1.2.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the SupportsAddActivities field.

<46> Section 3.3.5.1.2.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the SupportsCheckPolicy field. SharePoint Server 2019 does not set this field and returns the default value.

<47> Section 3.3.5.1.2.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the SupportsCheckUserAccess field.

<48> Section 3.3.5.1.2.2:  SharePoint Server 2019, SharePoint Server 2016 and SharePoint Server 2013 do not set the SupportsCoauth field and return the default value.

<49> Section 3.3.5.1.2.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the SupportsContactsResolution field. SharePoint Server 2019 does not set this field and returns the default value.

<50> Section 3.3.5.1.2.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the SupportsContainers field. SharePoint Server 2019 does not set this field and returns the default value.

<51> Section 3.3.5.1.2.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the SupportsDeleteFile field. SharePoint Server 2019 does not set this field and returns the default value.

<52> Section 3.3.5.1.2.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the SupportsEcosystem field. SharePoint Server 2019 does not set this field and returns the default value.

<53> Section 3.3.5.1.2.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the SupportsExtendedLockLength field. SharePoint Server 2019 does not set this field and returns the default value.

<54> Section 3.3.5.1.2.2:  SharePoint Server 2013 does not support the SupportsFileCreation field.

<55> Section 3.3.5.1.2.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the SupportsFileUserValue field. SharePoint Server 2019 does not set this field and returns the default value.

<56> Section 3.3.5.1.2.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the SupportsGetActivities field.

<57> Section 3.3.5.1.2.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the SupportsGetLock field. SharePoint Server 2019 does not set this field and returns the default value.

<58> Section 3.3.5.1.2.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the SupportsGrantUserAccess field. SharePoint Server 2019 returns false for this field.

<59> Section 3.3.5.1.2.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the SupportsPolicies field. SharePoint Server 2019 does not set this field and returns the default value. 

<60> Section 3.3.5.1.2.2:  SharePoint Server 2013 does not support the SupportsRename field.

<61> Section 3.3.5.1.2.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the SupportsReviewing field.

<62> Section 3.3.5.1.2.2:  SharePoint Server 2013 do not support the SupportsUserInfo field. SharePoint Server 2019 and SharePoint Server 2016 do not set this field and return the default value.

<63> Section 3.3.5.1.2.2:  SharePoint Server 2019, SharePoint Server 2016 and SharePoint Server 2013 do not set the UniqueContentId field and return the default value.

<64> Section 3.3.5.1.2.2:  SharePoint Server 2013 does not support the UserCanRename field.

<65> Section 3.3.5.1.2.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the UserCanReview field.

<66> Section 3.3.5.1.2.2:  SharePoint Server 2013 does not support the UserPrincipalName field.

<67> Section 3.3.5.1.2.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the WorkflowPostMessage field.

<68> Section 3.3.5.1.2.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the WorkflowType field.

<69> Section 3.3.5.1.2.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the WorkflowUrl field.

<70> Section 3.3.5.1.3:  SharePoint Server 2019, SharePoint Server 2016, SharePoint Server 2013 and Office Web Apps Server do not support the CheckPolicy operation.

<71> Section 3.3.5.1.4:  SharePoint Server 2019, SharePoint Server 2016, SharePoint Server 2013 and Office Web Apps Server do not support the CheckUserAccess operation.

<72> Section 3.3.5.1.8:  SharePoint Server 2019, SharePoint Server 2016, SharePoint Server 2013 and Office Web Apps Server do not support the GetActivities operation.

<73> Section 3.3.5.1.9:  SharePoint Server 2019, SharePoint Server 2016, SharePoint Server 2013 and Office Web Apps Server do not support the GetFileUserValue operation.

<74> Section 3.3.5.1.10:  SharePoint Server 2019, SharePoint Server 2016, SharePoint Server 2013 and Office Web Apps Server do not support the GetLock operation.

<75> Section 3.3.5.1.12:  SharePoint Server 2019, SharePoint Server 2016, SharePoint Server 2013 and Office Web Apps Server do not support the GetShareUrl operation.

<76> Section 3.3.5.1.13:  SharePoint Server 2019, SharePoint Server 2016, SharePoint Server 2013 and Office Web Apps Server do not support the GrantUserAccess operation.

<77> Section 3.3.5.1.15.2:  SharePoint Server 2016, SharePoint Server 2013 and Office Web Apps Server do not support the HostEditNewUrl field. SharePoint Server 2019 does not set this field and returns the default value.

<78> Section 3.3.5.1.16:  SharePoint Server 2019, SharePoint Server 2016 and SharePoint Server 2013 do not support the PutUserInfo operation.

<79> Section 3.3.5.1.17:  SharePoint Foundation 2013 does not support the ReadSecureStore operation.

<80> Section 3.3.5.1.19:  SharePoint Server 2013 does not support the RenameFile operation.

<81> Section 3.3.5.1.21:  SharePoint Server 2019, SharePoint Server 2016, SharePoint Server 2013 and Office Web Apps Server do not support the SetFileUserValue operation.

<82> Section 3.3.5.2.1.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the AADUserObjectId field.

<83> Section 3.3.5.2.1.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the AccessTokenExpiry field. SharePoint Server 2019 does not set this field and returns the default value.

<84> Section 3.3.5.2.1.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the AllowEarlyFeatures field.

<85> Section 3.3.5.2.1.2:  SharePoint Server 2013 does not support the AllowExternalMarketplace field.

<86> Section 3.3.5.2.1.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the AppCatalogUrl field. SharePoint Server 2019 does not set this field and returns the default value.

<87> Section 3.3.5.2.1.2:  SharePoint Server 2013 supports the BreadcrumbDocUrl field.

<88> Section 3.3.5.2.1.2:  SharePoint Server 2013 and Office Web Apps Server do not support the ClosePostMessage field.

<89> Section 3.3.5.2.1.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the DirectInvokeDAVUrl field. SharePoint Server 2019 does not set this field and returns the default value.

<90> Section 3.3.5.2.1.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the DisablePrint field.

<91> Section 3.3.5.2.1.2:  SharePoint Server 2013 and Office Web Apps Server do not support the EditNotificationPostMessage field.

<92> Section 3.3.5.2.1.2:  SharePoint Server 2013 and Office Web Apps Server do not support the FileSharingPostMessage field.

<93> Section 3.3.5.2.1.2:  SharePoint Server 2013, SharePoint Server 2016 and Office Web Apps Server do not support the FileVersionPostMessage field. SharePoint Server 2019 does not set this field and returns the default value.

<94> Section 3.3.5.2.1.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the FileVersionUrl field. SharePoint Server 2019 does not set this field and returns the default value.

<95> Section 3.3.5.2.1.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the HostAuthenticationIdType field. SharePoint Server 2019 does not set this field and returns the default value.

<96> Section 3.3.5.2.1.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the IrmPolicyDescription field.

<97> Section 3.3.5.2.1.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the IrmPolicyTitle field.

<98> Section 3.3.5.2.1.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the IsAnonymousUser field.

<99> Section 3.3.5.2.1.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the OpenInClientCommandUrl field. SharePoint Server 2019 does not set this field and returns the default value.

<100> Section 3.3.5.2.1.2:  SharePoint Server 2013, SharePoint Server 2016 and Office Web Apps Server do not support the OpenInClientPostMessage field. SharePoint Server 2019 does not set this field and returns the default value.

<101> Section 3.3.5.2.1.2:  SharePoint Server 2013 does not support the PostMessageOrigin field.

<102> Section 3.3.5.2.1.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the ProtectInClient field.

<103> Section 3.3.5.2.1.2:  SharePoint Server 2013, SharePoint Server 2016 and Office Web Apps Server do not support the ReportAbusePostMessage field. SharePoint Server 2019 does not set this field and returns the default value.

<104> Section 3.3.5.2.1.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the ReportAbuseUrl field. SharePoint Server 2019 does not set this field and returns the default value.

<105> Section 3.3.5.2.1.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the SafeLinksStatus field. SharePoint Server 2019 does not set this field and returns the default value.

<106> Section 3.3.5.2.1.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the SupportsFileUserValue field. SharePoint Server 2019 does not set this field and returns the default value.

<107> Section 3.3.5.2.1.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the UserCanReview field.

<108> Section 3.3.5.2.1.2:  SharePoint Server 2013 does not support the UserPrincipalName field.

<109> Section 3.3.5.2.1.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the WorkflowPostMessage field.

<110> Section 3.3.5.2.1.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the WorkflowType field.

<111> Section 3.3.5.2.1.2:  SharePoint Server 2013 and SharePoint Server 2016 do not support the WorkflowUrl field.