Copilot UX components is the final name for SharePoint Copilot Apps
The capability that shipped as "SharePoint Copilot Apps" in the July public preview, then became "Copilot Components" in August, is now finalized as "Copilot UX components": SPFx-built interactive components implementing the MCP Apps model that render charts, maps, KPIs, forms and approvals inside the Microsoft 365 Copilot canvas. The refreshed docs confirm SharePoint hosts component assets automatically and, depending on tenant configuration, can serve them through the Microsoft 365 CDN, and that an admin must explicitly select "Add to Teams" after uploading the package to sync the agent. No Microsoft 365 Copilot license is needed to develop or test during public preview; GA licensing is still undecided.
Why it matters: teams building Copilot UI surfaces should settle on the final name now and plan for the explicit "Add to Teams" deployment step, which is easy to miss and leaves the agent unsynced.
learn.microsoft.com