We are humbled to see the incredible momentum of SharePoint Framework (SPFx) and the growth it is driving with our customers and partners. There are tens of millions of users using custom SPFx solutions each day worldwide in Microsoft 365. Your innovation and feedback continue to shape its success, and we are excited and committed to keep partnering with you on this journey. We are starting a new blog post series which will be a first step on the future evolution of SharePoint Framework.
We see customers building powerful solutions like personalized AI powered employee portals and dashboards that seamlessly bring together SharePoint, Microsoft Teams, and Viva Connections – all powered by SPFx. These scenarios highlight how extensibility through SPFx accelerates innovation, helps organizations meet unique business needs, and creates richer employee experiences on a scale.
SPFx is a core part of the Microsoft 365 platform extensibility strategy, and we are committed to making sure our updates reflect that. We are adjusting our communication patterns and launching a monthly roadmap update to ensure that you have more transparency and predictability on upcoming releases.
This is not just about planning; it is about showing how SPFx is evolving to meet the demands of the Era of AI. SPFx has a huge role to play in enabling intelligent, adaptive experiences across Microsoft 365, and we want to make sure you can confidently plan, innovate, and grow with it. To that end, we are:
- Focusing on our customer and partner feedback and input – We have already introduced a new in-product feedback feature, which is visible on the online workbench for your input. Soon you will also see the feedback option available when you perform live debugging on the pages.
- Being more transparent on our SPFx roadmap with monthly updates on the latest features and capabilities
- Forming a community advisory committee that includes respected customer and partner representatives to provide input and help us ensure transparency in decision-making.
Roadmap
We are evolving towards a quarterly release cycle, providing more predictability on new features introduction and updates. Here is the set of investments which we are planning to ship within the upcoming SPFx releases:
Version 1.22 – October 2025
- Addressing npm audit reported security issues on the dependency tree.
- Transitioning from Gulp to an open webpack based toolchain orchestrated by Heft.
Version 1.23 – February 2026
- Open-sourcing Yeoman generator solution templates via GitHub and opening them for community contributions.
- A new open-sourced SPFx CLI for replacing the existing Yeoman generator – You will be able to introduce your company specific templates or adjustments on the scaffolded baseline for the SPFx solutions. We are decoupling the CLI itself from the SPFx release versions.
- Command set improvements for lists and libraries – grouping and potentially other improvements.
- New and edit panel override in lists – support panel level override on the Microsoft Lists and SharePoint lists with SPFx.
- New debugging toolbar improving the in-page development experience when workbench is not used.
Version 1.24 – May 2026
- Navigation customizers – Options to override navigation nodes and/or experiences with SPFx components.
- Other features which will be shared in following blog posts.
We also continue further innovation in the AI space with focus on both customer features and developer tooling. More on this in future blog posts on this monthly series.
Please continue providing feedback to support our product planning for the upcoming semesters. We already have an extensive list of ideas and enhancements in our mind, across AI and traditional areas, but are always interested in your input.
Community Advisory Committee and Feedback Loop
To further strengthen our partnership with the community, we are introducing a new SPFx Community Advisory Committee, which is a group of non-Microsoft people who are actively involved in our product and release planning. We are excited about this new engagement model and will collaborate closely with the Community Committee members to have an active engagement with our product group to plan together next steps within our journey.
We will be using this new community advisory committee as our initial strategic review board for our future investments and community representatives for the future platform changes. Your feedback continues to matter here as well.
The initial set of SPFx Community Committee members are following Microsoft MVPs:
- Adam Wojcik
- Andrew Connell – Voitanos
- Anoop Tatti – Advania
- Beau Cameron
- Chris Kent – Takeda
- David Warner – Quisitive
- Derek Cash-Peterson – Sympraxis Consulting
- Don Kirkham – Encora
- Hugo Bernier – Takeda
- Julie Turner – Sympraxis Consulting
- Stefan Bauer – N8D
We are open to including additional SPFx Community Committee members and continue evolving this new engagement model in future.
Frequently Asked Questions
We will include this section in all upcoming SPFx roadmap blog posts to provide more clarity and transparency by addressing any frequently asked questions within the past month(s).
What is the status and future of SPFx powered field customizers in lists and libraries? We did update our plans to potentially deprecate field customizers in June 2025. Based on careful evaluation after feedback from the ecosystem, we have decided to not deprecate field customizers in lists and libraries.
Single part SPFx solutions were momentarily not available in the new page creation, are they going away? No. This was a regression, and it has been fixed. Single part SPFx solutions are widely used by customers and partners. We will continue supporting them normally also in future.
We have seen issues on using SharePoint Framework within the Microsoft Teams context – any work done to improve this experience? We are committed to providing an easy option to build Microsoft Teams experiences also with SharePoint Framework. We are aware of challenges in these areas and are actively working with our Microsoft Teams’ counterparts to address the known issues. Please continue informing us on any issues using the GitHub issue list – https://aka.ms/spfx/issues.
What’s next?
We continue expanding the SharePoint platform to unlock more innovation across Microsoft 365:
- SharePoint Framework (SPFx) for building rich, AI powered and business integrated solutions with custom user interfaces directly in Microsoft 365.
- SharePoint Embedded to bring SharePoint content into your own apps hosted outside of Microsoft 365 with your own user interface.
- Agents and AI to create intelligent, adaptive experiences to access your content and business information efficiently and expose those easily for your end users.
- Microsoft Graph to access data and insights everywhere using our standard API surface.
We encourage you to explore these capabilities and see how they can help you build the next generation of solutions for your organization and customers.
If you are looking to build experiences for Microsoft 365, we strongly recommend joining our community calls and other Microsoft 365 & Power Platform Community activities covering Copilot, Power Platform, SharePoint, Microsoft Teams, Microsoft Graph, Microsoft Viva, and more. See community call details and other assets from https://aka.ms/community/home.
We are also excited to share that we will be organizing the SharePoint Hackathon event also during 2026 where we previously saw an impressive set of examples of ecosystem innovation across intelligent portals powered by AI and SPFx.
Follow us also on LinkedIn or in X to stay up to date on Microsoft 365 Platform announcements.
Got feedback or input on this blog post? – Leave a comment and we will get back to you.
Happy coding! Sharing is Caring! 🧡
When do you plan to fix this? https://github.com/sharepoint/sp-dev-docs/issues/10343
Hi,
we do not have unfortunately direct ETA for this fix. I’ve updated the GitHub issue on the situation and guidance where suitable. Really unfortunate situation impacting SharePoint 2019.
This is very exciting – and great news. Any updates on the REACT version for the new SPFX 1.22+ onwards ?
Has been stuck on 17.0.1 for a few years – since 1.16 (Nov, 2022) – and REACT is now up to v19.
Last question – when is there a BETA available for 1.22 ?? And some preparation work for the new HEFT tooling ?
We are hoping to have news on this soon, but no React updates at least in 1.22 unfortunately. We absolutely need to address this for the ecosystem. There are technical challenges for us to do this, but those are more excuses and we need to address.
Currently SPFx cannot move to React 18 or newer - as the used React version is dependent on the React version used by the out of the box features in SharePoint Online. This dependency exists so that not each web part needs to bundle React packages on their bundle - we rather share a...
Vesa—I realise the release is still some months away, but can you provide any more details on the Navigation Customizers proposed for SPFx v1.24? For example, will it provide a way to add commands to the SharePoint App Bar (Global Navigation) like Command Bar extensions, or will it let us fully replace the Top Navigation without relying on fragile CSS and DOM manipulation?
Hi James,
there are two specific objectives of this work 1) override navigation nodes which are rendered in the navigation control – so that you could use custom logic to resolve them etc. 2) Override the whole navigation control with clean and reliable way without relying on CSS and DOM manipulation.
We will definitely share more details on this as we get the plans locked in more detailed.
Thanks, Vesa – We’ll be watching this one with great interest!
Hi,
Thanks !
I’m so excited to be able to CRUD Dataverse data from SPFx without having to deal with Graph. Will that be in SPFx set or in PnP set ?
Gilbert
Hi Gilbert,
Dataverse Web API is like any Azure Web API which can technically used with SPFx already today. There has not bee any limitations on this in the SPFx side, so you should be all good to use it with any recent version. You are not limited to Microsoft Graph API surface when SPFx is used.
There is no specific plans to enable or invest on this integration option with SPFx context. We are though definitely always interested on the feedback on how we could improve the integration options across all systems.
Thanks you Vesa.
In 2013, we developed a tool to use SSOM and CSOM to manipulate data and structure “agnosticaly”. So, our onPremise webparts did run the same online.
I was hoping to have the same kind of proxy to SP and Dataverse so a code developed for SP could run with no change with Dataverse.
So, as Microsoft does not plan to go in this direction, perhaps we will have to think about doing the same kind of dev as we did in 2013.
Anyhow, thanks for your clear answer.
Extraordinary timing, as I was reviewing for
Upgrade few solutions after years of not being deep into #SPFX. Congratulations to everyone behind this and for keeping the standards high!
C:\>Marius
thx Marius, appreciated. For the any immediate upgrades, you should be looking 1.21.1 version and the easiest way to do that would be to use CLI for Microsoft 365 with spfx project upgrade command – https://pnp.github.io/cli-microsoft365/cmd/spfx/project/project-upgrade.
Keep the feedback coming as we rollout the following versions. We are building these for our customers and partners – so your input is invaluable for us.