Roadmap item 562222 lists the feature as launched, with April 2026 preview and September 2026 general-availability dates. Its stated scope is the web platform in Worldwide Standard Multi-Tenant environments. Those are roadmap metadata, not confirmation that every tenant has identical availability; Microsoft describes its roadmap dates as estimates subject to change.
What the agent node changes
The important distinction is between following a predefined sequence and delegating a bounded task. Microsoft describes Copilot Studio workflows as combining deterministic automation with AI-driven actions. The surrounding workflow still provides triggers and connector steps; the agent supplies reasoning within that process.
For administrators, the sensible design principle is to keep predictable operations predictable. Use an agent where interpretation adds value—not merely because another box on the canvas can now contain AI.
How to add and configure it
Microsoft Learn documents this setup path:
- Open Workflows in Copilot Studio and create or open a workflow.
- For an existing workflow, select Build.
- Select Agent in the Add panel.
- Choose a published agent or New agent for this workflow.
- Supply the task through Message for an existing agent, or Instructions for an inline agent. Insert dynamic content from earlier steps as needed.
Inline agents belong to their workflow and cannot be reused elsewhere. A published agent is the appropriate option when several workflows need the same capability. Output can be text, named structured fields, or a custom JSON-schema object; structured fields become downstream dynamic-content tokens.
Practical takeaway: decide what later steps need before writing the prompt. A routing decision benefits from explicit fields rather than a beautifully worded paragraph that another action must somehow decipher.
Test the handoff—and budget for it
Before publishing, select the node’s Test tab, provide inputs, and choose Run test. Confirm that the response has the expected form. The optional Request human assistance when unsure setting emails the connection owner and waits for a reply. Building, testing, evaluating, and using agents may consume Copilot Credits.
Treat that escalation option as a safety mechanism, not a substitute for defining which actions require approval.
Existing flows need a separate migration plan
Microsoft’s workflow FAQ supplies an important boundary: classic, standard-harness agent flows remain available, but there is currently no supported conversion from those flows to the newer workflow format. Power Automate cloud flows likewise cannot be converted directly into Copilot Studio workflows. Microsoft says workflows use Copilot Studio capacity without requiring a separate Power Automate license.
The bottom line: the agent node offers a useful way to insert judgment into automation. Its strongest deployment pattern is a narrowly defined task, an explicit output contract, and testing before downstream actions receive the keys.
References
- Microsoft Copilot Studio: Invoke agents as workflow steps with the agent node Microsoft 365 Roadmap · 2026-11-17T00:31:56.092066Z
- Add an agent node to a workflow (Microsoft Copilot) - Microsoft Copilot Studio | Microsoft Learn learn.microsoft.com
- AI at Work Roadmap | Microsoft 365 learn.microsoft.com