
Copilot Studio workflows can now run an agent as one step
Microsoft has added an agent node to workflows in Copilot Studio, according to the Microsoft 365 Copilot release notes dated November 17. It is on the web.
A workflow in Copilot Studio is a chain of steps that runs a business process. Before, a step that needed judgment, such as reading data, calling a tool and writing an answer, took several steps and often a person to pass the work along. Now you can drop one agent node on the workflow canvas. The agent reasons over the data, calls the tools you set, and returns a response, all inside that single step.
Microsoft says this means fewer manual handoffs, faster runs, and workflows that can make nuanced decisions without extra development work.
What it means for your work
Look at a workflow your team already runs where someone reads an item and decides what happens next, such as sorting requests or checking an invoice against a rule. That decision is a good first place for an agent node.
Add the node, give it only the tools it needs, and run the workflow on a few test items before you let it handle real ones. Check what the agent decided in each run, and keep a person on the step until the answers are steady.
For the other Copilot Studio changes from Ignite, see Copilot Studio adds apps, Cowork-built agents and agent accounts.