Microsoft Copilot Studio - Invoke agents as workflow steps with the agent node
AI summary
Invoke Copilot Agents directly as workflow steps
Agenten als Workflow-Schritt in Copilot Studio
Rollout dates
- Standard release (GA):
Extracted from the announcement text; the Microsoft text is authoritative.
Impact
ChangeCockpit assessment (admin, user and compliance impact).
Microsoft announcement
We are announcing the ability to invoke agents as workflow steps with the agent node in Microsoft Copilot Studio. This feature will reach general availability on September 1, 2026.
How does this affect me?
This feature enables makers to embed reasoning directly into a workflow. This means fewer manual handoffs, faster processing times, and workflows that can handle nuanced decisions without additional development effort, helping teams automate more of their end-to-end processes and reduce operational overhead.
The agent node, available in Copilot Studio workflows (also referred to as agent flows), lets makers call any published Copilot Studio agent as a step within an automated workflow. Instead of building complex branching rules or routing work to an individual, your makers can add a single step that calls a Copilot Studio agent to reason, retrieve knowledge, and use tools on behalf of the user. The workflow stays in control of sequencing and reliability, while the agent handles the parts that require understanding.
What action do I need to take?
This message is for awareness, and no action is required.
How does this affect me?
This feature enables makers to embed reasoning directly into a workflow. This means fewer manual handoffs, faster processing times, and workflows that can handle nuanced decisions without additional development effort, helping teams automate more of their end-to-end processes and reduce operational overhead.
The agent node, available in Copilot Studio workflows (also referred to as agent flows), lets makers call any published Copilot Studio agent as a step within an automated workflow. Instead of building complex branching rules or routing work to an individual, your makers can add a single step that calls a Copilot Studio agent to reason, retrieve knowledge, and use tools on behalf of the user. The workflow stays in control of sequencing and reliability, while the agent handles the parts that require understanding.
What action do I need to take?
This message is for awareness, and no action is required.
Change history
- 2026-07-30 · Created · All