Build a SharePoint-grounded Copilot Studio agent for Teams
Diesen Beitrag auf Deutsch lesen
Create a focused Copilot Studio agent with selected SharePoint sources, explicit fallback rules, and a Teams publishing path.
TL;DR
Copilot Studio can create a custom intranet agent grounded in selected SharePoint sites or document libraries. Configure a specific name, instructions and fallback behaviour, then publish the tested agent to Teams and optionally surface it through a Viva Connections dashboard card.
Original by Anouck, on 365-ANOUCK. Read the original
This is our own summary, not a republication or full translation.
Why it matters
- Makers: Restrict knowledge to the relevant SharePoint sites or libraries, then add instructions for scope, source links, language and unanswered questions.
- Makers: Test the agent before publishing it to Teams, and pin it where employees already work, such as the relevant team or channel.
- Admins/IT: Remember that SharePoint permissions continue to apply, avoid shared OneDrive as grounding, and communicate that content refresh is not instant.
Frequently asked questions
How do I limit a Copilot Studio intranet agent to HR SharePoint content?
Add only the relevant SharePoint sites or document libraries as knowledge sources. Use agent instructions to restrict answers to HR topics and redirect unrelated questions.
Do SharePoint permissions still apply to a Copilot Studio agent?
Yes, users receive answers only from SharePoint content they already have permission to access. The agent inherits those access boundaries.
Where can I publish a SharePoint-grounded Copilot Studio agent for employees?
Publish the tested agent to Microsoft Teams. It can be pinned to a relevant team or channel and added as a Viva Connections dashboard card.