---
title: "Microsoft Copilot Studio: Enabling makers to require human approval for tool calls"
date: 2026-09-01
roadmap_id: "570434"
source: "https://www.microsoft.com/microsoft-365/roadmap?id=570434"
tags: ["Copilot Studio", "Copilot", "Agent", "Teams"]
slug: "microsoft-copilot-studio-enabling-makers-to-require-human-ap-570434"
image: "/assets/img/blog/microsoft-copilot-studio-enabling-makers-to-require-human-ap-570434.png"
audio: "/assets/audio/blog/microsoft-copilot-studio-enabling-makers-to-require-human-ap-570434.wav"
---

# Microsoft Copilot Studio: Enabling makers to require human approval for tool calls

**Ship Outcomes, Not Chat** — a short read on a Microsoft 365 roadmap item.

## What it is

Microsoft Copilot Studio: Enabling makers to require human approval for tool calls (Copilot Studio, Copilot, Agent, Teams). Roadmap id `570434`.

## What it does

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,…

## What to worry about

Human approval gates are good — unless they become permanent babysitting. Close the feedback loop.

## What it means for users

Makers and CoE leads get clearer levers on agent lifecycle cost and behaviour — use them to prove effectiveness, not just publish bots.

---

Source: [Microsoft 365 Roadmap](https://www.microsoft.com/microsoft-365/roadmap?id=570434)