We are announcing the deprecation of the Microsoft Graph Toolkit (MGT). The retirement period begins September 1st, 2025 with full retirement planned for August 28th, 2026.
Why we’re retiring this toolkit
We introduced the Microsoft Graph Toolkit (MGT) to simplify the developer experience when building web applications that connect to Microsoft Graph. It provided a set of reusable web components and helpers to accelerate development and reduce the complexity of authentication and data binding. However, the MGT’s narrower ecosystem, and overlap with more powerful alternatives have led to a decline in its usage over time. Our developer community has increasingly chosen to work with more modern frameworks and SDKs that offer greater flexibility, deeper integration, and broader community support.
Retirement timeline and support
The Microsoft Graph Toolkit will enter a deprecation phase starting September 1st, 2025, with full retirement planned for August 28th, 2026. During this period:
- No new features will be introduced.
- Only critical accessibility and security issues will be addressed.
- The toolkit will remain open source, but we will no longer actively maintain or support it.
Transition Guidance
We understand that some developers may still rely on MGT for specific scenarios. While there is no direct modern replacement for all components, we recommend the following:
- For UI components, consider building with Fluent UI Web Components or integrating directly with Microsoft Graph SDKs.
- For authentication and data access, use the Microsoft Graph SDKs for your preferred language, which offer full support and ongoing updates.
Looking Ahead
We are deeply grateful to everyone who used, contributed to, and advocated for the Microsoft Graph Toolkit. Your feedback helped shape the developer experience for Microsoft Graph. As we move forward, our focus remains on delivering high-quality, secure, and well-supported tools that empower developers to build with Microsoft Graph. We invite you to explore our latest SDKs and share your feedback as we continue to evolve the platform. Thank you for being part of the journey.
— The Microsoft Graph Developer Experience Team
Does this also mean the retirement of the @microsoft/mgt-element package? I use these to create authentication providers and to create Microsoft Graph Client to easily access the graph API. Is there a suitable alternative for the custom simpleprovider
Hi Tjerk, unfortunately all MGT components will be retired. To handle authentication, the current recommended approach is using the Microsoft Graph SDKs.
I initially thought this was a late April Fools joke, as the MGT is SUPER useful to me in several projects. That said, I only use a few bits like People and People picker. Is there some guidance on a migration path here, to what alternatives are suggested? Is usage so low as to justify discontinuing the project altogether? What about just decreasing the scope to most-used components?
Hi Hilton, thanks for the feedback. Are you using those components in spfx or standalone?
So I've certainly used MGT to good effect in SPFx over time, but my most value from it has definitely been standalone. As an example, I have several apps in the Teams store and have an admin portal where users can manage usage, assign licenses and so on, and showing existing assignees, picking new ones, etc. are great for MGT because I can offer a rich person card really easily. As another example, I've got a kind of standalone SaaS app also which is kind of like a vanilla "send to my manager" sort of thing and I pre-populate the...
Hi Hilton, thank you for sharing your feedback. One alternative you might consider is building a custom UI Web Component using Fluent UI, integrated directly with Microsoft Graph SDKs for data access. I am also interested in knowing if you are using the People and Picker components within SharePoint Framework?