SharePoint Copilot Apps: What Admins and Developers Need

SharePoint Copilot Apps, announced on June 23, 2026, let organizations bring interactive components into Microsoft 365 Copilot instead of relying on chat text alone. Approving an expense, checking a leave balance or booking a desk can happen inside a Copilot conversation without switching tabs. Here’s what SharePoint Copilot Apps are, why Microsoft built them, and what SharePoint admins and developers should do to prepare.

What are SharePoint Copilot Apps?

They surface purpose-built user experiences directly in the Microsoft 365 Copilot canvas. Instead of describing a request in back-and-forth chat, users see a dashboard, form, list or chart where they’re already working. Microsoft’s framing is that chat is powerful but not always enough. Every hop to another app or portal breaks focus, and that cost adds up across an organization.

The feature is built on the SharePoint Framework (SPFx), which already powers custom experiences for tens of millions of users. In other words, it extends a platform organizations have invested in for years to a new surface.

How SharePoint Copilot Apps work for developers

Developers build the UX component and the platform handles the rest. SPFx supports any JavaScript library or framework, including React, Angular, Vue, Svelte or plain TypeScript.

  • Standard web stack: build with whatever framework your team already uses.
  • Open patterns: no proprietary platform.
  • Automatic hosting: components are hosted in the customer’s own Microsoft 365 tenant, with no external infrastructure.
  • Inherited security: governance and compliance controls come from SharePoint.
  • AI coding friendly: because it’s standard JavaScript, coding assistants can scaffold, generate and debug components in the IDE.

Under the hood, SharePoint Copilot Apps implement the MCP Apps model, an open standard for interactive experiences built on the Model Context Protocol. The difference from a typical MCP Apps implementation is that hosting and tool routing happen automatically.

Moreover, the same component isn’t tied to one surface. A team can write it once and expose it across Copilot, SharePoint and Microsoft Teams, which protects existing SPFx investments.

Example scenarios

Microsoft grouped early scenarios into three categories. It also noted that almost anything previously built as a SharePoint web part or Teams personal app is a candidate.

  • Line-of-business agents: sales figures, inventory, time-off requests, pay slips, help desk tickets and customer 360 views.
  • Corporate communications and services agents: personal dashboards, relevant news, onboarding tasks, directories and visual Q&A.
  • Management and governance agents: site provisioning, policy enforcement and operational dashboards for IT and compliance.

Microsoft also published a “My Day” example: one component summarizing a person’s schedule, tasks and outstanding approvals in a single interactive card.

Release timeline

Microsoft’s July 2026 SPFx roadmap update laid out this plan:

  • June 2026: SPFx 1.23.2, a quality update with issue fixes, npm audit fixes and groundwork for list and library panel overrides.
  • July 2026: SPFx 1.24 public preview, including the SharePoint Copilot Apps preview.
  • September 2026 (target): SPFx 1.24 general availability, with SharePoint Copilot Apps GA, SPFx CLI GA and navigation customizers.

Microsoft described “SharePoint Copilot Apps” as a working name during preview that could change at general availability. Check the latest SPFx roadmap update for current status.

How this connects to Copilot in SharePoint

SharePoint Copilot Apps followed Copilot in SharePoint (formerly AI in SharePoint, and before that the SharePoint Knowledge Agent). From mid-June 2026, Copilot in SharePoint moved from an opt-in to an opt-out preview. As a result, it appears for any user with a Microsoft 365 Copilot license unless an admin turns it off.

Licensed users see a Copilot button on SharePoint pages, libraries and lists. The chat respects existing permissions and only touches content the user can already view or edit. Admins control it through PowerShell, using the KnowledgeAgentScope parameter to include or exclude sites or opt out at the tenant level.

Together, the two updates push Copilot into SharePoint from both directions: conversational AI over existing content, and interactive components that developers build on top of it.

What admins and IT leaders should do

  • Confirm whether your tenant previously opted in or out of Copilot in SharePoint; those settings carry forward.
  • Review high-traffic or heavily customized sites to see how the Copilot entry points interact with existing layouts.
  • Brief SPFx developers so they can evaluate reusing existing web parts as Copilot components.
  • Note Microsoft’s guidance that building SharePoint Copilot Apps doesn’t need a Copilot license, since they build on declarative agents that work with a standard Microsoft 365 license.
  • Get governance right early. These components inherit SharePoint’s security and compliance model, so well-structured content and permissions directly improve the Copilot experience. Our Copilot Agent Builder governance guide covers the owner and review model.

For developers, the barrier to entry is low: no new platform to license and no Azure infrastructure to stand up. Everything is hosted in the organization’s own tenant, which keeps experimentation cheap. Still on-premises? These features only arrive in SharePoint Online, so see our SharePoint Server end of support guide.

Bottom line

SharePoint Copilot Apps are one of the most significant SPFx investments in years, and they arrive alongside the push to make Copilot in SharePoint the default. Organizations that brief their developers, try the components and clean up their SharePoint content now will get the most out of them. Microsoft is taking feedback through community calls and GitHub, so early adopters can still shape the developer experience.

Last reviewed: October 2026. Timeline details reflect Microsoft’s July 2026 roadmap.

Sources


Discover more from Cloud Osprey

Subscribe to get the latest posts sent to your email.

Cloud Osprey
Cloud Ospreyhttps://cloudosprey.com/about/
Hands-on Microsoft cloud practitioner writing practical, source-checked guides on Microsoft 365, SharePoint, Copilot, Entra ID, Power Platform and Azure. Formerly the author of SP Monkey, the SharePoint and Microsoft 365 blog, since 2016. Every guide links its sources and carries a "Last reviewed" date.

Recent Articles

Related Stories