MC1442981 High
Microsoft Copilot Studio - Invoke agents as workflow steps with the agent node
Summary AI-generated
Makers can now invoke agents as workflow steps using the agent node in Copilot Studio, enabling automated reasoning and streamlined end-to-end workflows.
Written by Azure OpenAI (gpt-4.1) from the text of the post below. It can be incomplete or wrong; the original post is authoritative.
Similar posts
Search for more like this- MC1442234 Microsoft Copilot Studio - New workflows designer
- MC1391947 Microsoft Copilot Studio - Use MCP-compliant tools in agent workflows
- MC1323229 Microsoft Copilot Studio - Automate web and desktop apps with computer use
- MC1471573 Copilot Studio - Use MCP-compliant tools in agent workflows
- MC1403399 Microsoft Copilot Studio - Create agents optimized for Microsoft 365 and Microsoft 365 Copilot users
- MC1403393 Microsoft Copilot Studio - Evaluate AI action outcome in workflows
Original post from Microsoft
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.