SPFx Roadmap Update August 2026: Copilot Components, React 18, and SPFx 1.24

Microsoft published the SharePoint Framework roadmap update for August 2026 on August 27, 2026. The update is important for SharePoint developers because it connects three workstreams that have been moving quickly: SPFx 1.24, Copilot Components, and React 18 support.

The short version: SPFx 1.24 Beta 3 is available, Copilot Components are in public preview, React 18 support is confirmed for SPFx 1.24, and Microsoft is targeting October 2026 for SPFx 1.24 general availability.

What changed in the August 2026 roadmap update?

The announcement gives SharePoint developers a clearer planning path after the earlier SharePoint Copilot Apps preview. Microsoft says the preview capability is now being referred to as Copilot Components, while noting that the final name still needs to be locked before general availability.

For practical planning, there are five main takeaways:

• SPFx 1.24 Beta 3 is available with updates focused on Copilot Components.
• Copilot Components public preview is open broadly, so teams can test with samples instead of waiting for a private ring.
• React 18 support is confirmed for SPFx 1.24, which matters for existing React-based SPFx solutions and future component libraries.
• General availability is targeted for October 2026 for SPFx 1.24 and Copilot Components.
• SPFx 1.25 is planned for December 2026 or January 2027, with SPFx CLI GA and navigation customizer investments on the roadmap.

What are Copilot Components?

Copilot Components let developers build interactive user experiences that can render on the Microsoft 365 Copilot canvas. Instead of returning only a text answer, an agent can show cards, forms, actions, business records, or other React-based UI where the user is already working.

The model is especially relevant for SharePoint Framework teams because it builds on skills they already use: React, JavaScript or TypeScript, SPFx packaging, tenant deployment, and Microsoft 365 governance. Microsoft's post also highlights that components run in the customer tenant and use the SPFx hosting model rather than requiring a separate app-hosting stack.

Why the name change matters

If you followed the June preview announcement, you may know the capability as SharePoint Copilot Apps. Microsoft now says the likely name going forward is Copilot Components. The name is not just cosmetic for content teams, documentation, and internal enablement.

• Update internal slide decks and wiki pages to mention both names during the transition.
• Use Copilot Components for new planning documents, but keep SharePoint Copilot Apps as a search synonym.
• Avoid hard-coding the preview name into productized user-facing labels until Microsoft confirms final naming.
• Make sure developers understand that the capability itself is not being removed because of the naming shift.

React 18 support is the developer headline

React 18 support has been one of the most requested SPFx updates. Microsoft has now confirmed it for SharePoint Framework 1.24. That matters because many enterprise SPFx projects depend on React component libraries, design systems, and modern React patterns that are difficult to standardize while the platform lags behind.

Do not treat this as a blind upgrade. React 18 can expose behavior differences in rendering, effects, strict mode checks, type definitions, and third-party component compatibility. The right move is to create a controlled upgrade branch and test real web parts, extensions, and component packages against SPFx 1.24 preview bits before planning a wider migration.

What teams should test now

Preview testing should be concrete. A useful pilot is not just running a generator and checking whether the project builds. Test the pieces that affect your production delivery path.

• Existing SPFx web parts: build, bundle, package, and smoke-test components that use React-heavy UI libraries.
• Copilot Component samples: deploy Microsoft's samples in a test tenant and validate inline and full-screen experiences.
• Permissions: confirm that users only see data they are allowed to access.
• ALM: validate source control, package versioning, tenant app catalog deployment, and rollback notes.
• Accessibility: test keyboard flow, labels, focus states, responsive layout, and screen reader behavior.
• Support model: document what is preview-only and what should wait for GA before production adoption.

Roadmap timeline

Version	Timing	Main items
SPFx 1.23.2	June 2026	Quality improvements, list and library panel readiness, npm audit work.
SPFx 1.24 Beta 3	August 2026	Copilot Components preview updates, React 18 support, and preview fixes.
SPFx 1.24 GA	October 2026	Copilot Components general availability and React 18 support for SPFx solutions.
SPFx 1.25	December 2026 / January 2027	Further Copilot Components work, SPFx CLI GA, open-source templates, and navigation customizer investments.

Licensing and cost details are still a planning gap

Microsoft says the Copilot Components preview is available without a Copilot license and without consumption-based costs during preview. For production planning, the key phrase is during preview. The licensing and cost model for general availability is still expected to be confirmed.

That means solution owners should separate technical validation from rollout commitment. It is reasonable to test architecture, UX, deployment, permissions, and upgrade readiness now. It is risky to promise broad business availability until Microsoft publishes GA licensing, cost, support, and admin-control details.

How this affects SharePoint developers

The SPFx roadmap is moving toward a more modern and Copilot-aware development model. SharePoint developers should prepare in four practical areas:

• Modernize React skills: review React 18 rendering behavior, hooks, strict mode implications, and component library support.
• Strengthen SPFx ALM: preview features make versioning, release notes, testing, and rollback discipline more important.
• Learn agent-connected UX patterns: Copilot Components are not traditional page-only web parts; they need task-focused UI that works with conversational context.
• Keep governance close: tenant deployment, permissions, data boundaries, and security review still matter even when the UI appears inside Copilot.

Recommended next steps

1. Read Microsoft's official August 2026 SPFx roadmap update.
2. Review the SPFx 1.24 preview release notes before upgrading any project.
3. Deploy the public Copilot Component samples in a non-production tenant.
4. Inventory existing SPFx projects that depend on React libraries and custom build tooling.
5. Create a short React 18 compatibility checklist for your SPFx team.
6. Wait for GA licensing and support guidance before making broad production commitments.

Summary

The August 2026 SPFx roadmap update is a strong signal that SharePoint Framework remains central to Microsoft 365 extensibility. SPFx 1.24 brings Copilot Components closer to general availability and finally confirms React 18 support. For development teams, the best next step is disciplined preview testing: validate samples, check React compatibility, document risks, and prepare governance before the October 2026 GA target.

For related context, review SharePoint Copilot Apps: SPFx Meets Microsoft 365 Copilot and SharePoint HTML Pages: What Roadmap 569208 Means for Microsoft 365.