← Back to Blog

SPFx 1.24: What's Confirmed in the Public Preview (2026)

SPFx 1.24 shipped as a public preview on July 8, 2026 — not GA. Here's exactly what's confirmed so far: SharePoint Copilot Apps and the Copilot Workbench.

SPFx 1.24: What's Confirmed in the Public Preview (2026)


Key Takeaways

  • SPFx 1.24 landed as Beta.1 public preview on July 8, 2026 — it is not GA, and you install it with the @next npm tag, not the default one

  • The headline feature is SharePoint Copilot Apps: SPFx components that render inside the Microsoft 365 Copilot canvas instead of a SharePoint page

  • You build and debug Copilot Apps locally with the Copilot Workbench, using the same packaging and project structure as a normal SPFx web part

  • No Copilot license is required to build and test during preview — Microsoft flags that as subject to change before GA

  • Claims floating around that 1.24 ships React 18 support or SPFx CLI GA aren't in the official release notes as of this writing — treat them as unconfirmed until Microsoft says otherwise

SPFx 1.24 is not out yet. Not really. What shipped on July 8, 2026 is a Beta.1 public preview, and the APIs, feature names, and even some of what's in this post are explicitly subject to change before general availability. If you searched "spfx 1.24" hoping for a changelog, this is the honest version: here's what's actually confirmed, and here's what's still just a roadmap line item.

Install the preview with the @next npm tag, not the default one:

npm install @microsoft/generator-sharepoint@next --global
yo @microsoft/sharepoint

Why This Post Exists

Two things are true at once right now. First, "spfx 1.24" keeps showing up in this site's own Search Console data with zero clicks despite climbing impressions — no post here matched what people were actually searching for. Second, some search results for that query already describe React 18 support and SPFx CLI general availability as settled features of 1.24. I checked the source Microsoft actually publishes release notes to — SharePoint/sp-dev-docs on GitHub — and neither claim is in there. So this post sticks to what's verified, and calls out what isn't.

If you migrated to Heft and the new SPFx CLI already, you've read the 1.22/1.23 toolchain guide — that post projected SPFx CLI GA for "June 2026" based on the roadmap at the time. That didn't happen on schedule. 1.24 arrived in July instead, and its release notes are about something else entirely: Copilot.

What's Actually Confirmed in SPFx 1.24 Beta.1

SharePoint Copilot Apps (Public Preview)

The centerpiece of 1.24 is SharePoint Copilot Apps — SPFx components that render inside the Microsoft 365 Copilot canvas rather than a SharePoint page, web part zone, or Viva Connections dashboard. If you've built a Viva Connections Adaptive Card Extension, the mental model is similar: your component lives inside someone else's host surface, not your own page. Copilot Apps just moves that host surface into the Copilot chat/canvas experience.

Three things Microsoft confirms about how it works in preview:

  • Same tooling, new surface. Copilot Apps reuse SPFx's existing packaging, build tooling, and project structure. You're not learning a second framework — you're targeting a new render target with tools you already know.

  • No Copilot license needed to build or test. During preview, you can develop and test Copilot Apps in any Microsoft 365 tenant without a Copilot license. Microsoft explicitly flags this as preview behavior that could change before GA — don't build a business case around it staying free.

  • Three starter templates. Scaffolding gives you a choice of Minimal, No framework, or React-based starting points, matching the pattern SPFx has used for web part generators for years.

The Copilot Workbench

Local development and debugging happens through the Copilot Workbench — the 1.24-era equivalent of the SPFx hosted/local workbench you already use for web part development. Microsoft's stated goal is fast iteration that matches your existing SPFx workflow: build, run, and debug locally before you ever deploy to a tenant.

That's genuinely useful if it holds up in practice, but it's also the part of the release most likely to shift. Preview tooling documentation tends to move fast, and the release notes themselves warn that APIs and feature names are subject to change before GA.

npm Audit Cleanup — Partial

Microsoft used this release cycle to chip away at long-standing npm audit warnings in the SPFx toolchain — the same class of dependency-chain noise the Heft migration started addressing back in 1.22. Some issues are resolved in Beta.1. Some aren't. If you're auditing a fresh 1.24 project and still see warnings, that's expected for now, not a regression on your end.

What's Explicitly Not There Yet

This is the section most "what's new" posts skip, and it's the one that actually matters if you're deciding whether to touch 1.24 today:

LimitationWhat it means for you
Not GADon't ship production solutions on @next — APIs can still change
Copilot canvas onlyCopilot Apps render in the Copilot canvas; no other host surfaces yet
Worldwide rollout incompleteFull availability was targeted for July 20, 2026 — if you can't see preview features yet, check back
Duplicate tool-name bugA known issue with duplicate tool name handling exists in Beta.1; Microsoft's fix is targeted for August
No App Store distributionYou can't publish a Copilot App to the Microsoft AppSource-equivalent store during preview

None of that is a knock on the release — preview software is supposed to have rough edges. It's a reason to build a side project against @next this week, not to migrate anything a client depends on.

What About React 18 and SPFx CLI GA?

You'll find both claims in circulation: that 1.24 brings React 18 support to SPFx solutions, and that it finally takes the SPFx CLI — previewed since 1.23 — to general availability. Neither appears in Microsoft's own release-1.24.0.md release notes as of this writing (checked July 15, 2026).

That doesn't mean they're false. Roadmap posts earlier in 2026 did describe both as directional goals for the SPFx team. But "on the roadmap" and "shipped in Beta.1" are different claims, and conflating them is exactly how outdated info ends up ranking for "spfx 1.24" instead of the truth. If you need React 18 or CLI GA today, they're not confirmed in this release — check the SharePoint Framework roadmap directly before you plan around either one.

Should You Try It?

If you're curious and have a sandbox tenant, yes — install with @next, scaffold a Copilot App with the React-based template, and see what the Copilot Workbench actually feels like to develop against. That's a low-risk way to be ready when GA lands.

If you're shipping production SPFx solutions for clients, stay on the current GA release. Beta.1 preview software with an August bugfix already queued and "subject to change before GA" stamped across the feature set is not where production code belongs.

FAQ

Q: Is SPFx 1.24 generally available (GA)?

No. As of July 15, 2026, SPFx 1.24 is in Beta.1 public preview, released July 8, 2026. It's installed via the @next npm tag, not the default GA channel.

Q: What's the main new feature in SPFx 1.24?

SharePoint Copilot Apps — SPFx components that render inside the Microsoft 365 Copilot canvas, built and debugged locally via the Copilot Workbench using standard SPFx tooling and project structure.

Q: Do I need a Microsoft 365 Copilot license to build Copilot Apps?

Not during preview — Microsoft's release notes confirm development and testing work without a Copilot license in any M365 tenant. That's explicitly flagged as preview behavior and may not carry through to GA.

Q: Does SPFx 1.24 include React 18 support or SPFx CLI general availability?

Neither is confirmed in Microsoft's official 1.24 release notes as of this writing. Some secondary sources list them as included — treat that as unverified until Microsoft's release documentation or roadmap page confirms it directly.

Q: When will SPFx 1.24 reach GA?

Microsoft hasn't published a GA date. The release notes describe Beta.1 rollout completing worldwide around July 20, 2026, with a known duplicate-tool-name bug fix targeted for August — neither of those is a GA date, just the next preview milestones.

What's Next



SPFx 1.24 is still moving. This post reflects what Microsoft has confirmed as of July 15, 2026 — check the official release notes before you build anything that depends on a feature staying exactly as described here.

---

Test Your Expertise


Think you've mastered SPFx and the broader Microsoft 365 ecosystem? Take the M365 Challenge Mode | Developer Quiz to test your knowledge against increasingly difficult enterprise scenarios.

Free Developer Tool

GUID Generator

Every SPFx web part needs a unique GUID in its manifest. Generate cryptographically secure v4 UUIDs instantly — bulk generation supported.

Try It Free →

We use cookies for analytics and personalised advertising. By accepting, you allow these uses. See our Privacy Policy and Cookie Policy.