SharePoint / SharePoint/sp-dev-docs

SPFx Copilot App - Agent doesn't see SPFx copilot component

Open
#10,997 5 comments 0 reactions 1 assignee View on GitHub

@Ashlesha-MSFT is already working on this.

Since Aug 21, 2026.

area:spfx area:spfx-copilot-apps sharepoint-developer-support status:fixed-next-drop status:working-on-it type:bug-suspected
Dominant language
PowerShell
Stars
1.4k
Forks
1.1k
Avg merge
4d 12h
Merged PRs (30d)
12

Description

Target SharePoint environment

SharePoint Online

What SharePoint development model, framework, SDK or API is this about?

💥 SharePoint Framework

Developer environment

Windows

What browser(s) / client(s) have you tested
  • 💥 Internet Explorer
  • 💥 Microsoft Edge
  • 💥 Google Chrome
  • 💥 FireFox
  • 💥 Safari
  • mobile (iOS/iPadOS)
  • mobile (Android)
  • not applicable
  • other (enter in the "Additional environment details" area below)
Additional environment details
  • SPFx version - 1.24.0-beta.2
Describe the bug / error

I've successfully developed (was working well in the SPFX Copilot Component Workbench) and deployed a custom SharePoint Framework Copilot App. I got the Agent installed for me and am able to see in in the "https://m365.cloud.microsoft/chat/agent" Copilot browser experience. Unfortunately, when I engage with the agent even with the built in prompts it does not surface the SPFx component but rather a text answer. The agent was installed more than 16h ago so this seems like more than enough time for things to wire themselves up. Please see attached developer diagnostics:

Image
Steps to reproduce
  1. Build a SPFx Copilot App Component
  2. Deploy it to production
  3. Install the agent
  4. Try any suggested prompt.
Expected behavior

Should show the SPFx component when prompted, not text answer.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.