Answer in brief
Microsoft’s September 30 SPFx update sets an October availability target for interactive Copilot components. The public preview is open worldwide; final licensing and several platform changes are still pending.
An October target is still a roadmap commitment
Microsoft’s September 30 SharePoint Framework update sets an October target for general availability of Copilot UX components alongside SPFx 1.24. The components provide interactive interfaces inside Microsoft 365 Copilot. The publication describes a public preview already enabled worldwide, while production licensing is still to be confirmed. Readers planning an implementation should preserve that distinction between current access and the intended release milestone.
The article also says a separate hands-on preview program has closed to new registrations because of demand. That does not close the public preview. Samples remain available, and Microsoft says developers can build and test during preview without a Microsoft 365 Copilot license or consumption-based charges. Those are stated preview conditions, not a pricing commitment for the eventual production release.
The interface exposes the decision a person must make
Microsoft describes components that display business data, charts, forms and approval choices in the conversation. The agent interprets a request, the component renders information through application code, and a person reviews or confirms the action. Existing business APIs perform the resulting operation. This describes an interaction pattern; it does not independently establish the accuracy of every connected business system or every generated suggestion.
A useful example is an employee reviewing a proposed leave request. Dates, remaining allowance and the intended approver can be shown together before submission. Our interpretation is that a visible form can make ambiguity easier to resolve than a conversational confirmation alone. Its value depends on showing the actual pending action and giving the employee a clear way to correct or cancel it.
The dates describe different levels of readiness
The roadmap reports SPFx 1.24 beta 4 on September 17 and beta 5 on September 23. It places the release candidate next and general availability in October. React 18 is present in the preview, while support for Node.js 24 and 26 is planned for the release candidate and final release. The table separates those states so teams do not treat every roadmap item as already shipped.
Microsoft also places general availability of the newer SPFx command-line tool in version 1.25, targeted for December 2026 or January 2027. A team building for the current preview should therefore follow the current documented tooling rather than assume the future scaffolding route is ready. The vendor explicitly says plans may change as development and customer feedback progress.
| Capability | State in the source | Timing or condition |
|---|---|---|
| Interactive components | Worldwide public preview | General availability targeted for October |
| SPFx 1.24 beta 5 | Shipped | 23 September 2026 |
| React 18 in SPFx | Available in 1.24 preview | Included in planned 1.24 final release |
| Node.js 24 and 26 support | Planned | Release candidate and general availability |
| Production licensing | Not confirmed | Preview terms do not establish final terms |
React changes deserve application-level testing
The move to React 18 is a platform dependency update within SPFx, not a new React release. React’s own March 2022 release article is historical context: it describes development-only Strict Mode checks that help expose effects and other behavior that is not resilient to repeated execution. Microsoft now asks developers to examine rendering, build and third-party library compatibility in their SPFx solutions.
For a business component, the meaningful test is whether a user can still complete the intended task reliably. Check how a form preserves an unfinished change, how loading and failure states appear and whether confirmation triggers the intended operation only once. These are editorial testing examples, not a claim that the preview is known to have those defects or that VJOURNAL has run a compatibility suite.
A common app model does not remove host differences
Microsoft says the components implement the MCP Apps model and use familiar web technologies, including React and standard JavaScript libraries. The protocol project’s own documentation describes interactive interfaces rendered inside a host, with host-controlled isolation and communication. It also notes that support varies by client. That gives independent technical context for the interface concept without proving identical behavior in every application host.
Organizations reusing an existing portal view should therefore inspect more than its appearance. The component needs the right user permissions, a useful state when data is unavailable and a clear handoff to the business API. The September roadmap discusses broader placement across Microsoft applications as an investment area; that wording should not be converted into a claim that every named surface already supports the same experience.
Plan the pilot around what is available today
The final product name is now Copilot UX components; earlier Microsoft material used SharePoint Copilot Apps and then Copilot Components. The September post says these names refer to the same capability. That clarification helps teams find the right preview documentation and prevents a renamed feature from being mistaken for several separate products with different availability rules.
A practical pilot can use the current samples and one well-understood business action while keeping a separate decision for production licensing and rollout. Record what the user sees, what they approve and which operation the backend completes. The September update supports experimentation now and planning for an October milestone. It does not yet settle final commercial terms or prove that a particular organization is ready for production adoption.
Questions and answers
Are the components generally available now?
The September 30 source describes public preview and an October target for general availability. It is a roadmap statement, not confirmation that the production release happened on October 1.
Do developers need a Copilot license to test?
Microsoft says the public preview does not require a Microsoft 365 Copilot license for development or testing and has no consumption-based costs. These preview conditions do not settle licensing after general availability.
Did closing the preview program close access?
No. Microsoft closed sign-ups for a separate hands-on program with its engineering team. The source explicitly says the public preview and sample packages remain available in tenants worldwide.