Microsoft 365 Copilot excels with language — but work isn't only words. Some tasks are faster to do than to describe: filing a document with the right metadata, or checking a price change before it reaches the catalog. You want to see it, act on it and confirm it, without leaving the conversation.

Copilot UX components (formerly SharePoint Copilot Apps) make that possible: SPFx components that render rich, interactive UI directly in the Microsoft 365 Copilot canvas, called as MCP tools by a declarative agent and hosted by SharePoint — no MCP server to run and no infrastructure to manage.

In this session we'll cover how declarative agents, plugins, MCP tools and components divide responsibility, why the tool schema is the prompt, and how display modes and state work. Then two deep-dives with live demos, one architecture: Document Intake, which files records into a SharePoint library (an open-source sample in the PnP gallery), and Catalog Manager, which browses, adds, updates and discontinues products in the AdventureWorks database on Azure SQL through Data API builder. Both follow the same pattern: Copilot pre-fills, a person reviews and confirms, and every change ends in a receipt. We'll close with field notes from a real tenant and the agent-driven process used to build them.

Level: 300 — Intermediate | Duration: 60 minutes | Tags: Microsoft 365 Copilot, Copilot UX Components, Declarative Agents, MCP, SharePoint Framework, SPFx, Azure SQL, Data API builder, Solution Architecture | Delivered at Day of Data St. Louis 2026 (earlier version at The Cloud & AI Summit 2026)