SPFx Copilot component not working in M365 Copilot

[HarminderSethi]

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

• browser version -150.0.7871.116
• SPFx version - 1.24.0-beta.2
• Node.js version 22.14

Describe the bug / error

I have created a Copilot Component from scratch with react framework option and I am not able to run it in M365 Copilot after deployment. It shows a blank screen

There is no error in the console but the Network call shows 404 for endpoint '/_api/mcp/beta/spfx'

Steps to reproduce

1. Create a new Copilot Component using the Yeoman generator
2. Build and package the component
3. Add the package to the tenant app catalog
4. Click "Add to Teams" button
5. Go to M365 Copilot and select the agent

Expected behavior

I should be able to use the agent in M365 Copilot without any error.

[jansenbe]

@HarminderSethi : this is a known issue we're working on. Can you try to first login to a SharePoint site and then open Copilot in that session.

[HarminderSethi]

@jansenbe I opened the Copilot from SharePoint Site's App launcher but still the component did not load. Also this time I did not see call to '/_api/mcp/beta/spfx' endpoint in the network tab

[jansenbe]

@HarminderSethi : thanks for the update, we've fixes coming for this. Part 1 has been merged, part 2 will be merged soon. This will take some time to reach production tenants (~a week at least). Please continue testing in workbench as work around, or alternatively check if another tenant works

[HarminderSethi]

@jansenbe- Thanks for the update. I have tested on two tenants but it is not woking yet so as you suggested I have to wait. One thing I have noticed is, whether I open the M365 copilot from the direct link or through SharePoint it is not making call to '/_api/mcp/beta/spfx' and the Iframe where the component should load has the src has URL like

{{tenant_rootsite}}/_layouts/15/PortableComponent.aspx?componentId=c10faeb8-a5e0-4877-8869-ab74b3622bd9&componentType=CopilotComponent&properties={{componentproperties}}

[jansenbe]

@HarminderSethi : the component will never make the call to the MCP server, the Copilot orchestrator tier is handling that. Based on information from today's sync we should have all related fixes in production deployed in ~2 weeks from now. Apologies for the delays in testing this is causing.