Microsoft made Copilot UX components generally available on 28 October 2026 with SharePoint Framework 1.24, allowing developers to place interactive web interfaces inside the Microsoft Copilot canvas. The change affects teams building Copilot agents that need forms, dashboards, approvals or other task interfaces rather than text-only responses.
Copilot UX components render inside a Copilot conversation when an agent invokes them. They can appear inline for compact interactions or in full screen for scenarios that need more space, such as dashboards, multi-step forms, maps or detailed views.
What developers can build
Microsoft describes the components as client-side web experiences built with existing web skills. React is used in many examples, but standard JavaScript libraries and other web frameworks can also be used.
The model is aimed at business processes that already exist in portals, forms, dashboards and line-of-business applications. Examples in Microsoft's material include sales dashboards, time-off requests, help desk tasks, travel booking, onboarding tasks, site provisioning and policy checks.
The agent handles intent. The component presents the data, choices, validation and operations defined by the developer's code and connected systems. For consequential actions, Microsoft says the component should include review and confirmation steps before changes are sent to a business system through its APIs.
Packaging and hosting
Copilot UX components use the Model Context Protocol Apps model for interactive user interfaces in AI experiences. In this implementation, SharePoint Framework handles the packaging, hosting and registration work inside the Microsoft 365 tenant.
A single SPFx solution can package a declarative agent and one or more Copilot UX components. The package is deployed through the SharePoint App Catalog. Component JavaScript and CSS are hosted in the tenant, so teams do not need to operate a separate web server for the component itself.
Components run with the signed-in user's identity and permissions through built-in single sign-on. Permissions and consent for connected business APIs remain part of the solution configuration. If a component calls an API with consumption-based charging, such as Work IQ, those charges may apply.
The same web code can also support other Microsoft 365 surfaces where the host fits the workflow. Microsoft lists SharePoint web parts, Teams tabs and Outlook apps opened from the left navigation as reuse options. At general availability, a solution that combines Copilot UX components with SPFx Teams functionality requires a manually created Teams package because automatic Sync to Teams has a mismatch for that combination.
Licensing and client support
Users need a Microsoft Copilot add-on licence to use Copilot UX components in Copilot. Components do not render for users without that licence, and Copilot shows a message explaining the requirement.
Using Copilot UX components does not itself add consumption-based charges. The cost position changes only where the component calls another service or API that is billed by consumption.
At general availability, supported clients are Microsoft Copilot in the browser and on desktop. Components also work when users access Copilot through Microsoft Teams in both browser and desktop clients.
Mobile support for Android and iOS is planned. Microsoft also plans support for packaging agents and components with the new Copilot plug-in model, so components can appear in standard Copilot chat without switching to a specific agent, subject to tenant configuration. Support for Cowork and additional Copilot surfaces is also listed as planned.
SPFx 1.24 platform changes
SharePoint Framework 1.24 is the release that brings Copilot UX components into production use. It also changes the development platform around them.
New SPFx solutions use React 18.x by default. Node.js 24 and Node.js 26 are supported for SPFx development. The release also adds build-time validation for declarative agent manifests, automatic Teams manifest version updates when a component changes, and new components scaffolded with declarative agent manifest v1.8.
Microsoft says the release includes fixes based on preview feedback and updates addressing npm audit findings. Teams that built against the 1.24 preview releases need to update to the general availability version. Teams moving existing solutions to React 18 need to test the upgrade path and third-party library behaviour.
Earlier material may use the names SharePoint Copilot Apps or Copilot Components. Microsoft says the current name is Copilot UX components.
Turning Copilot answers into tenant-hosted SPFx components is a Copilot extensibility problem, and ECS's Development topic covers it alongside Microsoft Graph, SPFx and Teams Toolkit. The programme gives developers and architects room to compare implementation patterns, packaging choices and tenant controls with people building on the same Microsoft 365 surface. Bring the agent scenarios that still depend on a portal or form today, and use the conference to test whether they belong inside Copilot or elsewhere in the workflow.
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.