Microsoft Copilot Studio: Enabling makers to require human approval for tool calls
Copilot Studio now includes optional per-tool, per-agent approval controls allowing makers to require human sign-off before sensitive operations execute. This enables organizations to enforce guardrails for high-stakes actions like email sending, ticket closing, and payment processing while maintaining inline approval workflows in Teams and Microsoft 365 Copilot.
Microsoft's description
Copilot Studio now let’s makers require human approval before an agent runs specific tools. With a per-tool, per-agent toggle, any gated tool call pauses and shows an approval request describing what the agent intends to do, so a person can approve, approve for the session, or deny before the action runs. This gives organizations a deterministic guardrail for high-stakes or sensitive operations like sending emails, closing tickets, or processing payments, independent of the agent's instructions. Approval requests appear inline in the channel where the agent is deployed, including Microsoft Teams and Microsoft 365 Copilot.