Microsoft Graph API follows the guidance described in the Model Versioning section in the Microsoft REST API guidelines. If you generate your own client proxies (like WCF clients), our guidance is that your client applications should be prepared to receive properties and derived types not previously defined by the Microsoft Graph API service.
API 671 LATEST EDITION OF MICROSOFT UPDATE
Note: Over time, we will update the list of backward compatible changes. Changes to the length or format of opaque strings, such as resource IDs.Introduction of paging to existing collections.Removal, rename, or change to the type of an annotation.Removal, rename, or change to the type of an open extension.Addition of properties that are nullable or have a default value.The following are examples of backward compatible changes: Removal or rename of APIs or API parameters.Removal, rename, or change to the type of a declared property.Changes to the URL or fundamental request/response associated with a resource.The following are examples of non-backward compatible changes: As new functionality and data is added to Microsoft Graph, we will increment the API version number for any non-backward compatible changes to the API. These changes are listed in the Microsoft Graph Changelog. Microsoft Graph has a log of changes across versions. API contract and non-backward compatible changes In those cases, only active applications that currently use the deprecated APIs can continue to use them. In some cases, we will announce that new applications will have to start using the new APIs a short time after the original APIs are deprecated. When an API is marked as deprecated, we strongly recommend that you migrate to the latest version as soon as possible. We might make exceptions to this policy for service security or health reliability issues. When we increment the major version of the API (for example, from v1.0 to v2.0), we are announcing that the current version (in this example, v1.0) is immediately deprecated and we will no longer support it 24 months after the announcement. Similarly, for individual APIs that are generally available (GA), Microsoft declares an API as deprecated at least 24 months in advance of removing it from the GA version.
Microsoft declares a version as deprecated at least 24 months in advance of retiring it. Microsoft Graph follows the Microsoft Lifecycle Policy.Īs new versions of the Microsoft Graph REST APIs and Microsoft Graph SDKs are released, earlier versions will be retired. Support policy and deprecation information This article describes the support and breaking change policies for Microsoft Graph and the versions of the Microsoft Graph API that are currently available.
0 kommentar(er)
