Copilot Studio Rolling out #136

Microsoft Copilot Studio: Invoke agents as workflow steps with the agent node

Makers can add agent reasoning to workflow steps

The agent node in Microsoft Copilot Studio lets makers invoke agents as workflow steps and embed reasoning directly into workflows. The roadmap lists September 2026 as the general availability target.

Key points

  • Workflows can handle nuanced decisions without additional development effort.
  • The agent node is intended to reduce manual handoffs in end-to-end processes.
  • The listed platform is Web.
  • The listed cloud scope is Worldwide (Standard Multi-Tenant).

What to do

Identify workflows where manual handoffs or nuanced decisions are automation candidates. Check availability before planning adoption. Tell makers that the agent node embeds reasoning into workflow steps, but the available source does not specify licensing or admin controls.

Timeline

  1. April 2026 Preview (planned, not confirmed) Microsoft 365 Roadmap target: Preview target.
  2. 1 July 2026 Published
  3. September 2026 General availability (planned, not confirmed) Microsoft 365 Roadmap target: General availability target.
Speaker notes

The agent node brings agent reasoning into a workflow as a step. Microsoft describes it as a way to reduce manual handoffs and handle nuanced decisions without additional development effort. The roadmap lists an April 2026 preview target and a September 2026 general availability target. Although its status field is Launched, it does not contain an explicit statement confirming that general availability has happened. Treat those dates as targets rather than confirmed delivery milestones. The stated scope is Web and Worldwide (Standard Multi-Tenant), with no licensing requirements or admin settings described.

Sources and links

Area, status, change type, licence and flags are indicative. Always open the source before you act on a card.