SharePoint Metadata Filtering in Copilot Studio: Agent Decisions
Diesen Beitrag auf Deutsch lesen
GitHub Copilot harness agents filter SharePoint files by metadata, pass matching URLs to knowledge search, and preserve SharePoint permission trimming for scoped answers.
TL;DR
GitHub Copilot harness agents can use SharePoint columns such as Country, approval status, department, owner, and review date to identify applicable files. The sharepoint_metadata_filter tool returns matching URLs and counts; knowledge_search_sharepoint then searches those URLs. Metadata filtering supports inventory and scoped answers, but does not replace permissions, and the internal tool contract may change.
Original by Adi Leibowitz, on The Custom Engine (Microsoft Copilot Studio CAT). Read the original
This is our own summary, not a republication or full translation.
Governance takeaway
- Admins/CoE: keep SharePoint metadata like country, approval status, department, owner, and review date accurate, since agents use it to exclude drafts, retired content, or the wrong audience before retrieval even starts.
- Security/Compliance: confirm permission trimming stays the actual access boundary — metadata filtering narrows what gets searched, it doesn’t grant or restrict access on its own.
- Makers: building on this should not treat the documented sharepoint_metadata_filter and knowledge_search_sharepoint tool names as a stable public API, since Microsoft flags the internal contract may change.
Frequently asked questions
What does the SharePoint metadata filter tool do in Copilot Studio?
It filters documents by author, editor, date, file type, folder or custom columns and returns filenames, URLs, column values, available columns, match counts and grouped totals.
How does the agent combine metadata filtering and content search to find policies for Canada?
It first filters the library on the Country column for the value Canada and receives the URLs of the matching files.
Does metadata filtering in Copilot Studio override SharePoint permissions?
No. Filtering only narrows the content scope and does not replace access control.