Copilot UX components bring business apps into Copilot

Key insights

• Components can display interfaces such as forms, dashboards, charts, and record views in Copilot.
• The development approach uses SharePoint Framework (SPFx) and packages solutions for deployment through the SharePoint App Catalog.
• The research notes report general availability worldwide with SPFx 1.24.
• The notes say users need a Microsoft 365 Copilot add-on license and an eligible base Microsoft 365 license.

Copilot UX components let organizations place interactive business interfaces, such as forms and dashboards, inside Microsoft Copilot conversations. They matter to developers building business experiences and to organizations that want users to review information or take actions without leaving Copilot. Microsoft is the source of the demonstration associated with this topic, but the supplied Short has no transcript or substantive description.

What's new

These components extend Copilot beyond text responses by letting it present an interactive interface when an agent determines that the experience fits a user's request. The interface can help a user inspect information, enter data, or act on a business record in the context of a conversation. Examples in the research notes include charts, customer views, help-desk experiences, employee services, and operational data.

The notes describe a development and deployment model based on SharePoint Framework (SPFx). An SPFx solution can include a declarative agent, which makes an experience available to Copilot, and one or more components that provide its interactive interface. The solution is packaged and deployed through the SharePoint App Catalog.

Who it is for and what you need

This approach is aimed at organizations and developers creating task-focused interfaces that connect Copilot conversations with business information or actions. The notes report that Copilot UX components are generally available worldwide with SPFx 1.24. They also list support for Copilot in web browsers, desktop clients, Teams clients, and Android and iOS clients.

According to the research notes, users need a Microsoft 365 Copilot add-on license as well as an eligible base Microsoft 365 license, with E3, E5, and E7 given as examples. The supplied material does not include a detailed licensing or rollout document, so administrators should verify current requirements before planning deployment.

How it works

1. A user describes a need in Microsoft Copilot.
2. An agent determines whether a component is relevant and presents its interface in the conversation.
3. The user reviews information or enters data in the component.
4. The component can call a business system or tool to complete the relevant action.

The key distinction is between a conversational answer and an interface that supports a task. A component can provide controls and structured information in the Copilot canvas, while a connected service supplies data or performs an action.

Limitations and open questions

The supplied Short transcript is empty, and the research notes do not provide implementation instructions, specific configuration steps, or detailed security and permission requirements. They describe the component model, SPFx packaging, licensing, and availability, but do not establish what setup is required for a particular business system.

The notes say the component itself does not create consumption-based charges, while separately metered services or APIs it calls may incur charges. They also describe components as focused interfaces, not replacements for large business applications. The supplied sources do not verify these details in a linked technical document.

Sources

• Microsoft website
• Microsoft YouTube Short

Frequently asked questions

What are Copilot UX components?

They are interactive interfaces that can appear in a Microsoft Copilot conversation, including forms, charts, dashboards, and record views.

What do developers use to build Copilot UX components?

The research notes describe building them with SharePoint Framework (SPFx), then packaging the solution for deployment through the SharePoint App Catalog.

What license do users need for Copilot UX components?

The notes say users need a Microsoft 365 Copilot add-on license plus an eligible base Microsoft 365 license, with E3, E5, and E7 listed as examples. The supplied sources do not include a detailed licensing document.

Are Copilot UX components generally available?

The research notes report worldwide general availability with SPFx 1.24. The supplied sources do not include a linked Microsoft rollout or availability page to verify the details.