Microsoft opened the SharePoint Framework (SPFx) developer survey on 4 November 2026, asking developers to feed into future planning after SPFx 1.24 brought Copilot UX components to general availability. The survey is open until 2 December 2026 and covers developers building Copilot UX components, web parts, extensions, Teams apps and Viva Connections cards.
Microsoft says it uses the survey to understand developer satisfaction and to decide what to prioritise next for SPFx. The survey is separate from the SPFx issue list in the sp-dev-docs repository, which remains the place for bugs and specific feature requests.
What changed in SPFx 1.24
Copilot UX components became generally available with SPFx 1.24 on 28 October 2026. They let developers render interactive dashboards, forms and business actions inside Microsoft 365 Copilot conversations, instead of returning only text or sending the user to a separate application.
The components are built with web technologies and packaged as SPFx solutions. A solution can include a declarative agent definition and one or more client-side UI components that Microsoft 365 Copilot can call from a conversation.
SPFx 1.24 also moved React-based solutions to React 18.3.1. It added support for Node.js 24 and Node.js 26, alongside Node.js 22. Microsoft also lists fixes from preview feedback and updates addressing npm audit findings.
Deployment and client support
Copilot UX components use the established SPFx deployment model. Developers package the solution as an .sppkg file and deploy it through the SharePoint App Catalog. When configured to include client-side assets, the package places JavaScript and other static assets in the App Catalog site collection, where SharePoint hosts them.
The same model allows a solution to carry the agent and its components together. After deployment, an administrator synchronises the baseline declarative agent to the tenant agent catalog from the App Catalog. Later component and tool changes can be discovered at runtime, while changes to the baseline agent configuration require another sync.
At general availability, Copilot UX components are supported in Microsoft 365 Copilot in browser and desktop clients. They are also supported through Copilot in Microsoft Teams in browser and desktop clients. iOS and Android clients, including Teams mobile, are not supported at general availability.
The documentation also lists limits for combined Copilot and Teams solutions. A solution that combines Copilot UX components and SPFx Teams functionality has a mismatch in automatic Sync to Teams at general availability. Microsoft describes a manually created Teams package as the workaround.
Licensing and costs
Use of Copilot UX components in Copilot requires the Microsoft 365 Copilot add-on licence on top of a user's normal E3, E5 or E7 licence. The same requirement applies to development and testing, including the Copilot Workbench.
The component capability itself does not use a consumption-based plan and has no consumption-based charges. APIs or services called from inside the component can have their own charges, and those charges remain separate from the Copilot UX component capability.
Users without the required add-on licence cannot use the component experience. Microsoft says components do not render for those users and the user sees a message explaining the licence requirement.
Roadmap items still in motion
SPFx 1.23, released in May 2026, brought list view command set improvements and a preview of the new open-source SPFx CLI. Maintenance releases have continued to address reported npm dependency vulnerabilities, including SPFx 1.22.2 in January 2026 and SPFx 1.24.1 on 2 November 2026.
The current SPFx roadmap lists SPFx 1.25 as targeted for December 2026 to January 2027. Planned work includes further development of Copilot UX components and general availability of the open-source SPFx CLI. Microsoft says plans and dates can change.
For developers maintaining SPFx solutions, the survey comes at a point where the framework is carrying more of Microsoft's Copilot extensibility work. The practical questions are now less about whether SPFx can host Copilot UI, and more about upgrade paths, tenant deployment, licensing checks and where Copilot components fit beside existing SharePoint and Teams code.
When SPFx becomes the route for Copilot UX components, the design questions move into packaging, agent manifests, Microsoft Graph access and Teams surfaces, which ECS's Development topic covers alongside Microsoft Graph, SPFx, Teams Toolkit and Copilot extensibility. Sessions in the Development topic give developers practitioner experience on building and maintaining Microsoft 365 extensions, including the constraints that appear after a feature reaches general availability. Bring tenant deployment questions, upgrade plans and Copilot extensibility assumptions to test them with people working on comparable projects.
This article was written by the ECS editorial team with the assistance of Amal Agent, run.events' AI assistant, which supported the research, drafting and proofreading.