[MS] Copilot UX components are generally available: bring interactive experiences into Copilot - devamazonaws.blogspot.com
Copilot UX components are generally available with SharePoint Framework (SPFx) 1.24. Bring interactive dashboards, forms, and business actions directly into the Copilot conversation. Build with familiar web technologies, with component hosting handled by Microsoft 365.
People do not just need an answer. They need a clear way to act on it.
Copilot UX components let organizations bring interactive web experiences, such as dashboards, forms, approvals, and live business data, directly into the Microsoft Copilot canvas. Instead of sending someone to another portal or app, an agent can present the information and controls needed to complete a task in the conversation.
A sales dashboard can open in the conversation when someone asks how the quarter is tracking, with filters to explore the numbers. A time-off request can show the employee’s leave balance, proposed dates, and a Submit button together. The person can review the details and take the next step without losing the context of the request.
For customers, the opportunity is to make existing business processes easier to reach and complete. Teams can use their web skills, business rules, and APIs to bring those processes into Copilot while keeping people in control of consequential actions.
[embed]https://www.youtube.com/watch?v=BoPNG32cdoc[/embed]
Post Updated on October 28, 2026 at 10:55AM
Thanks for reading
from devamazonaws.blogspot.com
People do not just need an answer. They need a clear way to act on it.
Copilot UX components let organizations bring interactive web experiences, such as dashboards, forms, approvals, and live business data, directly into the Microsoft Copilot canvas. Instead of sending someone to another portal or app, an agent can present the information and controls needed to complete a task in the conversation.
A sales dashboard can open in the conversation when someone asks how the quarter is tracking, with filters to explore the numbers. A time-off request can show the employee’s leave balance, proposed dates, and a Submit button together. The person can review the details and take the next step without losing the context of the request.
For customers, the opportunity is to make existing business processes easier to reach and complete. Teams can use their web skills, business rules, and APIs to bring those processes into Copilot while keeping people in control of consequential actions.
[embed]https://www.youtube.com/watch?v=BoPNG32cdoc[/embed]
From walls of text to work done
Microsoft Copilot helps people express what they need in natural language. But completing a business task often requires more than a written answer. People need accurate data, clear choices, validation, and a chance to confirm before anything changes. A text response that points to several portals and forms leaves the person to find the right destination, carry over the context, and finish the task elsewhere. Each handoff adds friction, especially for routine processes used across an organization. Copilot UX components put the next step in the same place as the request. The agent identifies the need; the component presents a purpose-built experience that the person can use immediately.
An interactive experience where the work happens
A Copilot UX component is an interactive web experience that appears in the Microsoft Copilot canvas when an agent needs it - based on user's intent. It can provide a quick in-conversation action or a larger workspace for a task that needs more detail. Customers can shape the interface around the process rather than fit the process into a fixed card.- Inline for quick, in-context interactions right in the conversation.
- Full screen when the scenario needs more room, such as dashboards, multi-step forms, maps, and detailed views.
- You're in control of the experience. Decide which modes each component supports and what it renders in each one. Components can also adapt to light and dark themes in Copilot.
AI for intent. UX for action. Humans in control.
The model separates the strengths of AI, application code, and human judgment:- Copilot interprets the request and brings up the appropriate component.
- The component presents business data, choices, validation, and operations defined by your code and connected systems.
-
Your code defines the review and confirmation steps. For consequential actions, design the component so the person can review and confirm before the solution sends changes to the business system through its APIs.
Copilot helps people find the right path. The component makes the path usable. The person remains in control.
[embed]https://www.youtube.com/watch?v=3wacPcqFuKw[/embed]Modernize the business processes you already run
Many customer processes already live in portals, forms, dashboards, and line-of-business apps. Copilot UX components offer a way to bring the relevant part of those processes into Microsoft Copilot. A person can start in natural language, work with an interface grounded in the organization’s systems, and complete the task in the canvas. That creates opportunities across everyday work:- Line-of-business data: sales dashboards, customer 360 views, stock levels, expenses, and pay slips.
- Employee services: time off, help desk, travel booking, onboarding tasks, and recognition.
- Personal dashboards: relevant news, latest tasks, and your day at a glance.
- Governance and operations: site provisioning, policy checks, and site dashboards, with an admin confirming each step.
Build with familiar web skills
The opportunity is accessible to teams that already build for the web. Copilot UX components use the Model Context Protocol (MCP) Apps model and familiar JavaScript tooling:- Industry standards. Components implement the MCP Apps model for interactive UI in AI experiences. It provides an open, interoperable foundation without the hosting and routing work that usually comes with it.
- The web stack you already know. React, TypeScript, and standard JavaScript libraries all work, as does whichever framework your team prefers. React appears in most of our examples, but it’s never a requirement.
- Familiar tools. Starter templates (Minimal, No framework, or React), npm, your editor of choice, and the Copilot Workbench for local debugging and testing across inline and full-screen modes, light and dark themes, and different input properties.
- One solution, many components. A single SPFx solution ships the agent and its components together.
Made for agentic coding
Because components use a familiar React or JavaScript project structure, teams can also use coding assistants to scaffold, build, refactor, and troubleshoot them. The samples and documentation provide a starting point, while developers remain responsible for the experience and the business behavior it implements. [embed]https://www.youtube.com/watch?v=nuXGCUpGscU[/embed]Deploy within the customer tenant
The deployment model matters as much as the interface. It reduces the extra hosting and identity work that can slow down a customer project. SPFx packages the agent and components for deployment inside the customer’s Microsoft 365 tenant:- Automatic component hosting. After the solution package is deployed, the platform hosts the component’s JavaScript and CSS in the tenant. Teams do not need to build a separate web server for the component.
- Automatic routing. Your components are registered for Copilot, and the agent that uses them becomes available in the tenant. When the conversation calls for a component, Copilot renders it in the canvas without endpoints to expose or wire together.
- Native security and single sign-on. Components run with the signed-in user's identity and permissions through built-in SSO. No extra sign-in prompts, and access follows the permissions people already have.
-
Familiar governance model. Components use the SPFx deployment and governance model, without a separate external component-hosting service. Permissions and consent for connected business APIs remain part of your solution’s configuration.
- Fewer infrastructure pieces to review. Without a separate component-hosting service or externally exposed component endpoint, teams can focus their review on the solution and the business APIs it uses.
The MCP Apps model, without the operational overhead
Both approaches use the MCP Apps model for interactive UI. An externally hosted MCP App requires a team to host, secure, and operate the web app and endpoint. With Copilot UX components, SPFx handles component hosting and registration in the customer tenant. The comparison below shows the operational differences.| Externally hosted MCP App | Copilot UX components | |
| Hosting | You build, deploy, and scale a web app and endpoint in Azure or another cloud | Automatic, inside the customer's Microsoft 365 tenant |
| Tool routing | You expose, secure, and maintain the endpoint | Automatic: components are registered and routed for you |
| Identity and SSO | You implement and maintain authentication | Built-in SSO with the signed-in user's permissions |
| Tenant approval | A new external app or service to review and consent to |
Uses existing SPFx governance; connected APIs may require additional permissions or consent. |
| Operations | Patching, monitoring, scaling, and uptime are yours | No separate component-hosting infrastructure to operate |
| Your data | Requests flow through your externally hosted service |
Component assets are hosted in Microsoft 365; connected data sources remain part of your solution architecture. |
| Reaching many tenants | Operate multi-tenant infrastructure or a deployment per customer | One package, deployed to any number of tenants |
Reuse one package across tenants
The same SPFx solution package can move through development, test, and production. Partners can also deploy a packaged solution to multiple customer tenants, where each customer runs it under its own governance.- Move through the delivery lifecycle. Deploy the same package to development, test, and production tenants without rebuilding a separate hosting environment.
- Deploy to customer tenants. Partners and ISVs can package a solution for multiple customers. Each deployment runs inside that customer’s tenant and follows its governance.
- Avoid separate component hosting. The SPFx model removes the need to operate a web server for each customer’s component.
Reuse the experience across Microsoft 365
The same web code can support experiences beyond Copilot. An SPFx investment can also be used in SharePoint, Teams, and Outlook where those surfaces fit the customer’s workflow:- Microsoft Copilot: as a Copilot UX component, inline or full screen.
- SharePoint: as a web part on your pages and portals.
- Microsoft Teams: as a tab.
- Outlook: as an app opened from the left navigation, in full-page view.
Availability at GA and what comes next
Available at GA- Copilot UX components are generally available worldwide with SPFx 1.24.
- Users need a Microsoft Copilot add-on license to use Copilot UX components in Copilot. Components do not render for users without the license - you will see a message explaining the license requirement.
- Using Copilot UX components does not itself incur consumption-based charges. If a component calls a consumption-based API, such as Work IQ, charges for that API may apply.
- Supported clients at GA: Microsoft Copilot in the browser and on desktop. Components also work when you are using Copilot through Microsoft Teams in both browser and desktop.
- Packaging at GA: a declarative agent and its Copilot UX components ship together in one SPFx solution. Copilot UX components are supported for SPFx solutions already in the SharePoint Store.
- Mobile support for Android and iOS.
-
Support for packaging agents and components with the new Copilot plug-in model, enabling components to appear directly in standard Copilot chat without switching to a specific agent, subject to your organization’s configuration.
- Support for Cowork and additional Copilot surfaces.
SharePoint Framework 1.24 is generally available
SPFx 1.24 delivers Copilot UX components for production use and updates the development platform:- Copilot UX components, production-ready: a predictable default display mode in the Copilot canvas, automatic Teams manifest version updates (no more version conflicts when updating a component), declarative agent manifest validation at build time, and new components scaffolded with declarative agent manifest v1.8.
- React 18: new SPFx solutions use React 18.x out of the box.
- Node.js 24 and Node.js 26: both are supported for SPFx development.
- Quality and security: fixes based on preview feedback and updates addressing npm audit findings.
Get started today
Start by trying a ready-to-deploy scenario sample in your tenant. The samples include solution packages, demo data, and setup steps, so a team can see how an interactive experience works in Copilot before building its own. Build your own in four steps:- Install SPFx 1.24:
npm install @microsoft/generator-sharepoint@latest --global
- Scaffold a new Copilot UX component and pick a template: Minimal, No framework, or React.
- Run and test it locally in the Copilot Workbench.
- Deploy the package to your tenant and surface it in Copilot.
- Get started - https://aka.ms/SPFx/Copilot
- Documentation - https://aka.ms/SPFx/Copilot/docs
- Sample gallery - https://aka.ms/SPFx/Copilot/Samples
- Videos - https://aka.ms/SPFx/Copilot/Videos
- SPFx 1.24 release notes
Thank you, and what’s next
Thank you to everyone who tried the samples, filed issues, joined community calls, and participated in the preview. Your feedback shaped this GA release. Earlier material may call this capability SharePoint Copilot Apps or Copilot Components; its current name is Copilot UX components. The GA release is a starting point. Mobile support, the new plug-in model, Cowork, and additional Copilot surfaces are planned as follow-on work. SPFx 1.25, planned for December 2026 or January 2027, will continue to evolve the model with follow up releases - based on your feedback and input. If you ran into any issues with the new build, please report them at aka.ms/spfx/issues - so that our engineering team can help you as fast as possible. Join our community calls at aka.ms/community/calls, and follow us on LinkedIn and X for the latest updates. Where should you start? Pick one task that people already ask Copilot about but still have to finish in another portal or app - a time-off request, an expense approval, a quick check of the sales numbers. Make it your first Copilot UX component: the data and the actions right in the conversation, ready to review and confirm. From walls of text to getting work done. 🤩 Happy coding! 🧡Post Updated on October 28, 2026 at 10:55AM
Thanks for reading
from devamazonaws.blogspot.com
Comments
Post a Comment