Microsoft Graph SDK versions.
The Microsoft Graph packages Versyka recognizes on npm and PyPI, their latest releases, and where the breaking changes are documented. Monitoring checks connected repositories against these every day.
Packages we track
| Package | Registry | Latest | Status | Release notes |
|---|---|---|---|---|
@microsoft/microsoft-graph-client | npm | 3.0.7 | Maintained | View → |
msgraph-sdk | PyPI | 1.65.0 | Maintained | View → |
Latest versions from the public npm and PyPI registries, checked and refreshed daily.
Microsoft Graph SDK questions
What is the latest version of the Microsoft Graph SDK?
As of 2026-10-26: @microsoft/microsoft-graph-client 3.0.7 on npm; msgraph-sdk 1.65.0 on PyPI.
Versions come from the public registries and are refreshed every day.
How do I upgrade the Microsoft Graph SDK without breaking my code?
Read the release notes for every major version between yours and the latest, update each call that changed, then run your typecheck, build and tests.
- Versyka's free upgrade check shows which Microsoft Graph packages in your package.json or requirements.txt are major versions behind, with the release notes.
- Versyka can do the upgrade for you: it finds every affected Microsoft Graph call, rewrites it, runs your own tests and opens a pull request only if they pass.
Does Versyka monitor Microsoft Graph SDKs?
Yes. Versyka recognizes @microsoft/microsoft-graph-client (npm), msgraph-sdk (PyPI) in connected repositories and flags them every day when they fall a major version behind or are deprecated.
Behind on Microsoft Graph?
Versyka finds every affected Microsoft Graph call in your code, rewrites it, runs your tests and opens a pull request.