- Subject
- Microsoft 365 & SharePoint
- Filed
- Source
- Vesa Juvonen
- Loans
- 909
SPFx 1.25 Plans and Developer Survey: What Microsoft 365 Teams Should Know
SPFx’s survey is open until December 2, 2026. Microsoft is also planning SPFx 1.25 for December 2026 to January 2027.


SPFx developers have a direct opportunity to influence what Microsoft works on next: the developer survey is open until Wednesday, December 2, 2026. That timing matters for teams planning Microsoft 365 extensions, because the framework has recently added Copilot UX components and updated its supported development stack. The survey asks how SPFx is working today and what developers need from future releases.
Take the SPFx developer survey if you build web parts, extensions, Teams apps, Viva Connections cards, or Copilot UX components. Microsoft says responses go to the team planning SPFx investments. The survey is intended to inform priorities; it doesn’t replace the issue tracker for reporting a reproducible bug or requesting a specific feature.

Recent changes affect both extension scenarios and tooling
SPFx 1.24 became available on October 28, 2026, with Copilot UX components reaching general availability. These components let developers build interactive experiences, including dashboards, forms, and business actions, for use inside Microsoft Copilot conversations. They use familiar web technologies, and Microsoft 365 hosts the experiences automatically. For developers, the release adds a way to bring custom application interactions into Copilot alongside existing SharePoint and Microsoft 365 extensions.
SPFx 1.24 also updated the framework’s React-based solutions to React 18.3.1 and added support for Node.js 24 and Node.js 26, alongside Node.js 22. Teams maintaining SPFx projects should account for those versions when reviewing local development environments and build pipelines. The available details identify supported Node.js versions but don’t specify changes to individual project upgrade steps, so check the framework documentation before changing a production build process.

The previous major update, SPFx 1.23, arrived in May 2026. It included improvements to list view command sets and a preview of a new open-source SPFx CLI. Microsoft has also issued maintenance updates addressing reported npm dependency vulnerabilities: the cited releases run from SPFx 1.22.2 in January 2026 through SPFx 1.24.1 on November 2, 2026. Administrators supporting several SPFx projects can use the release history to identify which framework versions are in their environments and review the relevant maintenance updates.
More detail on the Copilot components is available in the SPFx Copilot UX components documentation and the general availability announcement. The broader release history and plans are listed on the SPFx roadmap on Microsoft Learn.

Send roadmap feedback through the right channel
The survey is aimed at understanding developer satisfaction and helping Microsoft choose where to invest. That makes it useful for describing broader needs, such as which extension scenarios need attention or where the framework’s development experience could improve. For a specific defect or feature request, Microsoft directs developers to the SPFx issue list in the sp-dev-docs repository on GitHub. Keeping concrete reports there gives teams a place to describe and track individual requirements.
The survey deadline is Wednesday, December 2, 2026. Developers who want their feedback considered in future planning should submit it by then. Microsoft says it will share what it heard in an upcoming monthly update, though no date for that update is specified.

SPFx 1.25 is planned for late 2026 or early 2027
The roadmap currently targets SPFx 1.25 for December 2026 to January 2027. Planned work includes continued development of Copilot UX components and general availability for the open-source SPFx CLI, as well as other work across Microsoft 365. Those are current plans, and Microsoft notes that dates and plans can change. Teams should treat the target window as a planning reference rather than a confirmed release date.
For administrators and development leads, the practical next step is to compare the roadmap with the extensions and build processes they support. Copilot UX components may be relevant to teams considering interactive experiences in Copilot, while React and Node.js updates may affect developer workstations and build environments. The release information doesn’t prescribe a migration schedule, so teams should base upgrade decisions on their own compatibility checks and deployment needs.
Use community calls to see SPFx work in practice
Microsoft’s community calls run weekly and include live demos, product updates, and time for questions with presenters from Microsoft and the community. Developers can find details about the community calls and request a demo slot to show work built with SPFx or Copilot UX components. The Microsoft 365 & Power Platform Community also provides a place to share samples and learn from others building for Microsoft Copilot, Microsoft 365, and Power Platform.
The survey, issue tracker, roadmap, and community calls each serve a different purpose: broad feedback, specific reports, release planning, and practical discussion. With SPFx 1.25 on the roadmap and Copilot UX components now generally available, developers can use those channels to flag what they need and track how the framework’s next steps take shape.
