Govern Copilot Studio agents with narrow permissions
Diesen Beitrag auf Deutsch lesen
A Copilot Studio renewal workflow separates read-only advice, quote creation and email drafting into specialist agents.
TL;DR
A Copilot Studio Renewal Desk routes work to three specialist agents. The Commercial Advisor has read-only Dataverse access, Quote Operations can only run a draft-quote workflow, and Customer Comms can draft but cannot send email. A salesperson reviews the outbound draft before it leaves.
Original by Karl-Johan Spiik, on Karl-Johan Spiik, Microsoft MVP. Read the original
This is our own summary, not a republication or full translation.
Governance takeaway
- Makers: Separate agent responsibilities and give each connected agent only the tools needed for its defined task.
- Admins/CoE: Prefer constrained workflows for single actions such as draft quote creation, rather than broad MCP access.
- Security/Compliance: Keep outbound email as a draft requiring human review, so an agent cannot send customer communications itself.
Frequently asked questions
How should the Unicorn Renewal Desk orchestrator be given tool access?
The orchestrator has no tools or MCP servers. It only routes a request to the specialist agent that handles that task.
What Dataverse permissions does the Unicorn Commercial Advisor use?
It uses an MCP server with read access to Dataverse. It can retrieve agreements, policies and previous quotes, but cannot write.
Can the Unicorn Customer Comms agent send the renewal email?
No, it can only draft the email using customer contact data and a Work IQ mail MCP server. The salesperson reviews the draft before anything is sent.