Cannot deploy SPFx Copilot Components in M365 Copilot

[yhabersaat]

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
• Node.js version: 22.22.2

Describe the bug / error

I have created a Copilot Component from scratch with no framework option and I cannot run it in M365 Copilot. When I select the agent in the Agents menu in M365 Copilot I'm getting the error "Something went wrong".

I have some errors in the console:

Debugging in the Copilot Workbench works well without any error.

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 can use the agent in M365 Copilot without any error.

[Ashlesha-MSFT]

Hello @yhabersaat,
Thank you for bringing this issue to our attention. We will look into it and get back to you shortly.

[a1mery]

I'm facing the same issue as well.

[jansenbe]

@a1mery / @yhabersaat : please create a fresh trace, and save the console output (log file) and network trace (HAR file) and send to me via bjansen@microsoft.com.

I've seen issues like this when updating agents, what can help is updating the manifest version of the included declarative agent (e.g. https://github.com/pnp/spfx-copilot-apps/blob/main/samples/time-off-absence/copilot/manifest.json) and rebuild the sppkg. Before pushing to teams again first uninstall the deployed agent via https://admin.cloud.microsoft/?#/agents/all.

Sometimes it takes a while before Copilot to pick up newly deployed versions, changing manifest version is recommended whenever you've made changes that impact the included DA (we might automate that in the future).

[yhabersaat]

@jansenbe : Thanks for looking into this. I updated the manifest and rebuilt the package, then uninstalled and reinstalled the agent, but I'm still seeing the same error. I've sent you the zip file with the logs and HAR capture by email for further investigation. Let me know if you need anything else.

[jansenbe]

@yhabersaat : try installing and pinning your new version via https://admin.cloud.microsoft/?#/agents/all. What you see can happen when the old version is still cached by Copilot client, selecting it will then always throw an error. When you install + pin you force the new version to show up.

You can also turn developer mode on in Copilot (https://learn.microsoft.com/en-us/microsoft-365/copilot/extensibility/debugging-agents-copilot-studio#use-developer-mode-in-copilot) and verify if you see the version you deployed showing up. Also your MCP tool call should be listed in the Actions pane. When Copilot did not yet pick up your MCP tool changes you'd see something like below:

If Copilot sees the added MCP tool calls you'd see something like below. The tool call is coming from https://github.com/pnp/spfx-copilot-apps/blob/main/samples/time-off-absence/src/copilotComponents/timeOffOverview/TimeOffOverviewCopilotComponent.manifest.json in below sample

[ferrarirosso]

Same issue here
I still see the same error after increasing the manifest version, removing the previous agent, redeploying, installing, and pinning the new version.

I found a workaround:

1. Start a normal Microsoft 365 Copilot chat.
2. Type @<agent name> and select the agent from the mention picker.

3. The agent appears as a selected chip in the composer. 4. Send the prompt normally.

Using this route, the agent works: Copilot invokes the SPFx component, and the component can send a follow-up back to Copilot.

Opening the same agent directly from the agent list still produces the Cannot read properties of undefined (reading 'map') error.

[yhabersaat]

@jansenbe : Still the same error after pinning the agent using Agent 365. But strange thing, I tried with another React-based component and it worked! The only way to make it working is to mention the agent with @ in Copilot Chat and write the prompt. When I click on the agent directly the same error appears.

[jansenbe]

@yhabersaat : updated agents stay visible for a while in the UX, hence the ask for bumping versions and installing that version + verifying with developer mode to see if you're loading the latest version. Eventually the stale agent will disappear from the UX, but agree this is annoying. Will start a thread with the Copilot team on this