Graph versioning and breaking-change policy
Microsoft's edit ·
Microsoft's commit message in microsoftgraph/microsoft-graph-docs-contrib · commit 5a2fb75 · +6 −4 lines · also on GitHub
⋯ 11 unchanged lines
1212
1313
Microsoft Graph follows the [Microsoft Lifecycle Policy](https://support.microsoft.com/lifecycle).
1414
15
−As new versions of the Microsoft Graph REST APIs are released, earlier versions will be retired. Microsoft declares a version as deprecated at least 24 months in advance of retiring it. 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. For Microsoft Graph SDKs, only the latest major version of any given library is supported and updated with new features, bug fixes, and workarounds. The major version prior to the latest version is supported for 12 months from the release date of the latest major version, for security fixes only. We recommend that you upgrade to the latest version of the SDKs whenever possible.
15
+As new versions of the Microsoft Graph REST APIs are released, earlier versions will be retired. Microsoft declares a version as deprecated at least 24 months in advance of retiring it. Similarly, for individual APIs that have reached general availability (GA), Microsoft declares an API as deprecated at least 24 months in advance of removing it from the GA version.
1616
17
+For Microsoft Graph SDKs, only the latest major version of any given library is supported and updated with new features, bug fixes, and workarounds. The major version prior to the latest version is supported for 12 months from the release date of the latest major version, for security fixes only. We recommend that you upgrade to the latest version of the SDKs whenever possible.
18
+
1719
When we increment the major version of the API (for example, from v1.0 to v2.0), we're announcing that the current version (in this example, v1.0) is immediately deprecated and we'll no longer support it 24 months after the announcement. We might make exceptions to this policy for service security or health reliability issues.
1820
1921
When an API is marked as deprecated, we strongly recommend that you migrate to the latest version as soon as possible. In some cases, we'll announce that new applications will have to start using the new APIs a short time after the original APIs are deprecated. In those cases, only active applications that currently use the deprecated APIs can continue to use them.
2022
2123
### API contract and nonbackward compatible changes
2224
23
−Microsoft Graph has a log of changes across versions. These changes are listed in the [Microsoft Graph Changelog](changelog.md). As new functionality and data are added to Microsoft Graph, we increment the API version number for any nonbackward compatible changes to the API.
25
+Microsoft Graph has a log of changes across versions. These changes are listed in the [Microsoft Graph changelog](https://developer.microsoft.com/graph/changelog). As new functionality and data are added to Microsoft Graph, we increment the API version number for any nonbackward compatible changes to the API.
2426
2527
The following are examples of nonbackward compatible changes:
2628
⋯ 26 unchanged lines
5355
5456
### Current version
5557
56
−The current version of Microsoft Graph is v1.0. Exposed under `https://graph.microsoft.com/v1.0`, the Microsoft Graph API v1.0 version contains features that are generally available and ready for production use. Browse the [documentation for the v1.0 APIs](/graph/api/overview?view=graph-rest-1.0&preserve-view=true).
58
+The current version of Microsoft Graph is v1.0. Exposed under `https://graph.microsoft.com/v1.0`, the Microsoft Graph API v1.0 version contains features that are generally available and ready for production use. For v1.0 API documentation, see [Microsoft Graph v1.0 endpoint reference](/graph/api/overview?view=graph-rest-1.0&preserve-view=true).
5759
5860
## Preview status
59
−An API or feature in Microsoft Graph is labeled as "(preview)" to indicate its behavior is _unique_ in the beta endpoint.
61
+An API or feature in Microsoft Graph is labeled as "(preview)" to indicate that its behavior is _unique_ in the beta endpoint.
6062
6163
The behavior of most APIs and features in the v1.0 version is in parity with the beta version. A minority of APIs are marked as "preview" for one of the following reasons:
6264
- The APIs are available in beta only
⋯ 15 unchanged lines
Microsoft's Markdown source from microsoftgraph/microsoft-graph-docs-contrib, © Microsoft Corporation, under CC BY 4.0. Changed lines with up to 3 unchanged lines around each; ChangeIntel kept this copy 10 Oct 09:39 UTC. The commit date is when the source changed, which can be hours or days before Learn published it.