Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Important
Some of the functionality described in this release plan has not been released. Delivery timelines may change and projected functionality may not be released (see Microsoft policy). Learn more: What's new and planned
| Enabled for | Public preview | General availability |
|---|---|---|
| Admins, makers, marketers, or analysts, automatically | 
Apr 1, 2026 |
Sep 2026 |
Business value
The agent node lets you embed reasoning directly into your 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.
Feature details
Workflows handle structured, repeatable processes well, but many business tasks also require judgment.
Reviewing an expense report against policy, preparing a meeting briefing from CRM data, or triaging a support ticket all involve reasoning that traditional automation can't deliver without extensive custom logic.
The agent node in Copilot Studio is a workflow action that lets you embed that intelligence directly into your workflow.
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 a person, 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.
It combines the agent's instructions, knowledge sources, tools, and reasoning into a single reusable action that accepts a message as input and returns a response for use in downstream steps.
How it works In the workflow designer, makers add the agent node from the action panel under AI capabilities.
They select a published Copilot Studio agent they have access to, compose a message (which can include dynamic content from previous steps), and optionally enable human escalation for cases where the agent cannot proceed on its own.
When the workflow runs, the node sends the message to the agent, waits for it to complete, and makes the agent's response available as dynamic content for subsequent actions, such as sending an email, updating a data source, or branching the flow based on the result.
Authentication and security The agent node executes using the credentials of the user who triggers the workflow.
If the triggering user does not have access to the referenced agent, the agent node action fails at runtime.
This ensures that existing permission boundaries and least-privilege principles are honored without additional configuration.
Administration and governance The agent node is enabled by default for all makers.
Administrators who need to restrict its use can do so through data loss prevention (DLP) policies. No additional setup is required to start using the feature.
Geographic areas
Visit the Explore Feature Geography report for Microsoft Azure areas where this feature is planned or available.
Language availability
Visit the Explore Feature Language report for information on this feature's availability.