Copilot Studio can now read SharePoint Lists without an extra flow
Reviewed by Helen Jones
Microsoft added SharePoint Lists as a knowledge source in both the current and new Copilot Studio interfaces. Makers can now ask an agent to pull data directly from a list instead of routing the request through Power Automate. The change removes the need to build a separate flow that searches the list and returns results. Availability is confirmed for users who already have Copilot Studio licences. No other connectors or major interface changes were announced at the same time.
Until now the reader had one reliable pattern: a cloud flow with a SharePoint trigger or action, visible run history, and clear ownership. That pattern let them test the exact query, catch permission errors, and hand the flow to a colleague when they moved roles. The new direct source collapses that layer into the agent. The list query still happens, but the execution details, failure messages, and retry behaviour now sit inside Copilot Studio where the same maker has fewer tools to inspect or fix them.
Analysis
Keep any list lookup that matters to the business in a plain cloud flow with run-history alerts until Copilot Studio shows the same failure detail and ownership model. Test the new source only on non-critical lists first.
Pulse published by Collab365 Spaces, reviewed by Helen Jones on . Cite as "Copilot Studio can now read SharePoint Lists without an extra flow", Collab365 Spaces. 1 source referenced.