For years, every wave of Microsoft announcements raised the same question among SPFx developers: "Where do we fit in all this?" Power Automate arrived and it seemed automation could handle itself. Copilot Studio arrived and it seemed agents would replace webparts. Microsoft 365 Copilot arrived and the question became urgent: if AI already answers everything, why bother building interfaces?
On June 23, 2026, Vesa Juvonen answered from the Microsoft 365 Developer Blog. There is no replacement. There is an extension. And the framework you learned to build webparts is exactly what Microsoft chose to take enterprise AI to the next level.
The announcement SPFx developers were waiting for without knowing it
SharePoint Copilot Apps is Microsoft's most concrete bet to connect SPFx development with Microsoft 365 Copilot as a first-class surface. Not as a complement, not as a lateral integration: as the canvas where apps live and operate.
The pitch is straightforward: instead of Copilot only responding in text, developers can build complete visual experiences that run within the Copilot context. The "My Day" demo Microsoft published shows how an app built with SPFx can appear directly in the conversation, display personalized information, and allow actions without leaving the chat.
The Public Preview kicks off in July 2026. GA is planned for September alongside SPFx 1.24.
Copilot as a surface, not a destination
The difference that matters is not technical: it is conceptual. Until now, the mental model for SPFx was "I build for SharePoint and it optionally shows up in Teams." The new model is "I build for Copilot and it optionally shows up in SharePoint or Teams."
Copilot stops being the place where users search for things and becomes the place where apps live. The distribution of experience reverses: before, the user went to the page where the webpart was; now the app goes to where the user is.
That changes quite a bit about how you think about architecture. It does not change the tools.
What Microsoft does not force you to throw away
Here is the part worth underlining: Microsoft chose SPFx as the foundation of SharePoint Copilot Apps not out of nostalgia, but because it is the technology that already has proven enterprise scale. React, TypeScript, Fluent UI, Graph API, PnPjs: everything you already use remains valid.
The strategy is explicit: you reuse existing SPFx skills, tooling, and investments to reach AI-powered scenarios faster. There is no new platform to learn. There is a new surface to reach with what you already know.
SPFx 1.23.2 shipped as a quality release and foundation for what comes next. SPFx 1.24 Preview arrives in July with SharePoint Copilot Apps. And in September, with GA, come Navigation customizers (to customize SharePoint navigation with SPFx components) and, finally, React 18.
A date also worth noting: July 2027
While one door opens toward Copilot, Microsoft closed another. On June 29 it was published that Remote Event Receivers (RER) retire on July 1, 2027. If you have solutions that rely on RER to respond to events in lists and libraries, the migration to SharePoint Webhooks now has a deadline.
It is not urgent, but it is also not something to leave for December.
Those who know how to build now build for Copilot
Microsoft's pattern over the last two years is consistent: instead of creating parallel AI platforms that compete with the existing ecosystem, it extends what already exists toward AI. Copilot Studio extended Power Virtual Agents. Microsoft 365 Copilot extended productivity products. And now SharePoint Copilot Apps extends SPFx.
For developers who have been in the ecosystem for years, this is good news with a catch: the core skills still hold, but the design mindset needs updating. Building for the Copilot canvas is not the same as building a webpart. Users no longer look for the app; the app finds them.
That is what changes. The rest you already have.
If you want to follow how SPFx evolves in the Copilot era, subscribe to the macareno.net newsletter.
Sources
- SharePoint Framework (SPFx) roadmap update – July 2026 — Microsoft 365 Developer Blog
- Going beyond text in Microsoft 365 Copilot – Introducing SharePoint Copilot Apps — Microsoft 365 Developer Blog
- Remote Event Receivers are retiring: move to SharePoint webhooks before July 1, 2027 — Microsoft 365 Developer Blog