Events
Mar 17, 11 PM - Mar 21, 11 PM
Join the meetup series to build scalable AI solutions based on real-world use cases with fellow developers and experts.
Register nowThis browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
This article describes the support and breaking change policies for Microsoft Graph and the versions of the Microsoft Graph API that are currently available.
Microsoft Graph follows the Microsoft Lifecycle Policy.
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 reached general availability (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 that precedes 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.
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.
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.
Microsoft Graph has a log of changes across versions. These changes are listed in the Microsoft 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.
The following are examples of nonbackward compatible changes:
The following are examples of backward compatible changes:
Note: Over time, we update the list of backward compatible changes. 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. Microsoft Graph API follows the guidance described in the Model Versioning section in the Microsoft REST API guidelines.
The following versions of the Microsoft Graph API are currently available.
In general, APIs debut in the beta version and are accessible in the https://graph.microsoft.com/beta
endpoint. For beta API documentation, see Microsoft Graph beta endpoint reference. Expect breaking changes and deprecation of APIs in the beta version from time to time. Use of beta APIs in production applications is not supported.
We make no guarantees that a beta feature will be promoted to the current version. When the Microsoft Graph API team believes that a beta feature is ready for general availability, we add that feature to the latest current version. If the promotion of the feature would result in a breaking change to the current version, the version number is incremented, with the new version becoming the current version.
The current version of Microsoft Graph is v1.0. These APIs are accessible in the https://graph.microsoft.com/v1.0
endpoint. 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.
An API or feature in Microsoft Graph is labeled as "(preview)" to indicate that its behavior is unique in the beta endpoint.
The behavior of most APIs and features in the v1.0 version is in parity with the beta version. Some APIs are marked as "preview" for one of the following reasons:
Like any other API in the beta endpoint, we can introduce breaking changes to APIs that are marked as preview without notice. Don't access APIs from the beta endpoint in production apps.
Note: APIs can be in preview even when the feature or product itself is generally available.
Currently, no versions of Microsoft Graph are deprecated or unsupported.
By using the Microsoft Graph APIs, you agree to the Microsoft APIs Terms of Use.
Your feedback is important to us. Connect with us on Microsoft Q&A. Tag your questions with [microsoft-graph-*].
Events
Mar 17, 11 PM - Mar 21, 11 PM
Join the meetup series to build scalable AI solutions based on real-world use cases with fellow developers and experts.
Register nowTraining
Learning path
Microsoft Graph Fundamentals - Training
New to Microsoft Graph? Microsoft Graph Fundamentals is a multi-part series that teaches you basic concepts of Microsoft Graph. It will guide you with hands-on exercises on how to use Microsoft Graph API requests to start developing or enhancing your applications with Microsoft 365 data.
Certification
Microsoft 365 Certified: Fundamentals - Certifications
Demonstrate understanding of Microsoft 365, to deliver industry-leading productivity apps along with intelligent cloud services, and world-class security.
Documentation
What's new in Microsoft Graph - Microsoft Graph
Find out what's new in Microsoft Graph APIs, SDKs, documentation, and other resources.
Use Graph Explorer to try Microsoft Graph APIs - Microsoft Graph
Try Microsoft Graph APIs on the default sample tenant to explore capabilities, or sign in to your tenant and use it as a prototyping tool to fulfill your app scenarios.
Users you can reach with Microsoft Graph - Microsoft Graph
Use the Microsoft Graph API to build Microsoft 365 applications that connect users to personal services, work services, and school services.