Copilot Studio freezes when adding SharePoint "Get items" tool to a topic

(0) Share

Report

Posted on by JT-04090902-0

Hi,

I'm currently experiencing what appears to be a reproducible issue with the native SharePoint connector in Copilot Studio.

When I go to:

Topic → Add a tool → Connector → SharePoint → Get items

Copilot Studio freezes completely while trying to add/configure the Get items action.

I have reproduced the issue across:

Multiple Copilot Studio agents
Multiple Power Platform environments, including Default and Sandbox
Completely different Microsoft accounts
Different Microsoft 365 tenants
Different SharePoint tenants/sites
Multiple browsers, including Firefox, Brave and Chrome

The behaviour is identical in every case.

Other connectors appear to work. For example, I can add and use Excel connector actions. The problem appears to be specifically related to the SharePoint connector, particularly Get items.

There have been no VPNs or unusual network configurations involved, and since the issue can be reproduced across different tenants, environments, accounts and browsers, it does not appear to be related to a specific agent, connection or tenant configuration.

Has anyone else started seeing this recently?

It seems there have also been other recent reports of problems when adding SharePoint GetItems/Create Item actions as tools in Copilot Studio, so this may be a current regression in the SharePoint connector integration.

All responses (2)

Answers (0)

Sort by

Suggested answer

chiaraalina 2,529 Super User 2026 Season 2 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @JT-04090902-0

I just tested it and was not able to reproduce the issue. So it worked for me. I am able to add and configure without freezing.

I tested in environment region Europe and US. Which environment region are you using?
Suggested answer

BilalDev_01 72 on at

Like
a
(0)

Report
Copy link

Link copied!

I’m seeing similar behavior with the SharePoint connector in Copilot Studio, particularly when adding Get items as a tool to a topic.

Since you’ve already reproduced it across different agents, environments, tenants, accounts, browsers, and SharePoint sites, it does seem less likely to be a local configuration or connection issue.

It could be a recent regression in the SharePoint connector/tool integration. Hopefully Microsoft can confirm whether there’s an active incident or known issue.

As a temporary workaround, you could try calling the SharePoint action through a Power Automate flow and expose the flow to the agent instead of adding the connector action directly.

Thanks for documenting the steps so clearly — this should make the issue easier to investigate.