SharePoint / SharePoint/sp-dev-docs
Tool Invocation Fails in Deployed Declarative Agent but Succeeds in Copilot Workbench
@jansenbe is already working on this.
Since Jul 12, 2026.
- 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: 1.24 Beta 2
- NodeJS: 22.23.1
Describe the bug / error
The Copilot component was built and deployed to the Tenant App Catalog. I used the "Add to Teams" option and installed the agent from Agent365. However, when I try to invoke the agent from a Declarative Agent, the tool is not being called.
I tested both the out-of-the-box (OOTB) sample tools and custom tools, but neither of them works. The tools are invoked successfully in Copilot Workbench, but they do not work when the Declarative Agent is deployed.
Steps to reproduce
- Build and deploy the Copilot Component to the Tenant App Catalog.
- Use Add to Teams and verify the app is available.
- Install the agent from Agent365.
- Test the tool in Copilot Workbench – tool invocation works as expected.
- Open the deployed Declarative Agent in Teams/Microsoft 365 Copilot.
- Submit a prompt that should trigger the tool.
- Observe that the tool is not invoked.
Expected behavior
Tool should be invoked from the Declarative Agent.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.