Copilot Studio Workflows Designer: First Look and What the Billing Question Means

Microsoft’s automation landscape has been quietly fracturing for a while. Agent flows arrived in Copilot Studio and sat somewhere between Power Automate and fully autonomous agents. Now there is a Workflows Designer in preview, and it is worth a proper look.

It is more modern. It is more flexible. And the billing situation is starting to become a genuine problem for businesses that have invested in Power Platform.

What the Workflows Designer is

The Workflows Designer is a preview experience available at copilotstudio.preview.microsoft.com. Within Copilot Studio, creating a workflow has replaced creating an agent flow as the default new-flow experience.

The first thing you notice is the layout. Power Automate and agent flows run top to bottom. This canvas runs left to right. That sounds cosmetic but it makes complex branching considerably easier to read, particularly once a flow starts growing.

The second change is the trigger model. Instead of choosing a trigger type at the start and being locked into it, every workflow begins with a single configurable start node. Recurrence, HTTP request, connector-based and manual triggers are all handled from there.

What is genuinely new

Several capabilities stand out as meaningful improvements over anything available in agent flows or Power Automate.

The Microsoft 365 Copilot action lets you give Copilot a prompt directly from within the workflow and receive a response you can act on. You can direct the prompt to a specific agent you have access to rather than general Copilot. There is a toggle for synchronous or asynchronous execution and another that controls whether the conversation shows up in Copilot Chat. It is limited in its current form: you cannot target an existing conversation thread or manage multi-turn conversations from here, which is something agent flows already support. But as a first class action type within an automation canvas, it is new.

The agent node is the more interesting one. You can reference an existing agent from within a workflow, but you can also define an agent entirely on the canvas: its model, its instructions and its access to tools. The ability to design the agent in context, alongside the steps that come before and after it, changes how you think about the build. You are not jumping between tools to wire things together. It is all in one place.

This matters because the most common challenge in real process automation is not choosing between deterministic logic and AI reasoning. It is the fact that most processes need both. Some steps are rigid and must follow exact rules. Others involve judgement, context or fuzzy logic that deterministic automation cannot represent cleanly. The Workflows Designer lets you model both in a single canvas, which is a step forward.

The classifier action solves a long-standing problem with routing in Power Automate. Traditional routing through conditions and switches works, but the flows it produces are difficult to read and hard to maintain. The classifier uses AI to assess a previous output or trigger and routes accordingly. Each output can connect to different downstream paths, including paths that converge again later. You draw the lines where you want them and the workflow runs as you intend. That clarity has always been missing.

Per-action testing is the practical improvement that anyone who has spent time debugging Power Automate flows will appreciate most. Instead of running the entire flow to check whether one step worked, you can test individual actions as you build. Less waiting. Faster iteration. Less context lost between build and test.

Canvas notes, prompt actions addressed directly from the canvas and new functions including chunk text and document extraction round out the changes. The function additions in particular address a common frustration: moving content between Microsoft tools often meant format mismatches that required workarounds. These help with that.

What is still missing

This is a preview and there are gaps.

Multi-step approvals from agent flows are not here yet. Agent flows support two human-in-the-loop models: message-based review and multi-flow approvals. Only the message-based option is available in workflows at the moment.

MCP source addressability is also absent. Agent flows allow you to define an MCP target in natural language and connect it as an action. That capability does not carry over to workflows currently.

The prompt action has fewer model choices than in Power Automate. Foundry models are not available. This may be preview scoping but it is worth knowing if model flexibility matters to you.

The question that will not go away

If you look at the Workflows Designer and think it resembles a redesigned Power Automate more than something fundamentally new, that observation is fair.

On a technical level, it largely is. The actions on the workflows canvas are the same family of actions you can use in Power Automate. Some capabilities that appear entirely new here, such as the Microsoft 365 Copilot action, can technically be accessed from standard Power Automate too, though not through any supported route.

What Microsoft has built is a cleaner experience, with AI-native capabilities surfaced more directly, on the same technical foundations that Power Automate already uses.

That would be straightforward to welcome if the billing were not what it is.

The billing problem

The Workflows Designer is tied to Copilot Studio credits. A Power Automate Premium licence does not get you in. Copilot Studio consumption billing applies across the board.

Previously, the split made some sense. Agent flows were designed to run within the scope of a Copilot Studio agent conversation. Power Automate was for everything else. The billing boundary matched the use case boundary closely enough.

That logic does not hold anymore. The Workflows Designer is clearly intended as a general automation layer that can orchestrate agents, not a tool designed specifically to operate within agent conversations. It handles SharePoint triggers, scheduled runs and HTTP requests just as well as anything agent-related. It is a more capable version of the same tool most automation builders already use daily.

That puts businesses in a difficult position. If you have invested in Power Automate Premium and want the most modern building experience available, you now need additional Copilot Studio billing on top of what you already pay.

Where this probably goes

The Workflows Designer is preview. Where and how it lands at general availability is not fixed yet.

The most logical outcome would be for this building approach to become available regardless of what you are building, with Copilot Studio billing applying specifically to AI-intensive actions such as the classifier or the agent node. That is consistent with how premium connectors work in Power Automate today: most capabilities are included, specific ones carry additional cost.

Whether Microsoft takes that approach is an open question. If it does not, the organisations most likely to feel it are exactly the ones that have built heavily on Power Platform and would most naturally want to adopt what comes next.

What to do with this now

The Workflows Designer is worth exploring if you are already working in Copilot Studio. The canvas is more capable, the routing improvements are real and the ability to mix deterministic steps with agent reasoning in a single build is the right direction.

For organisations whose automation work sits primarily in Power Automate Premium, the smart move is to follow the preview closely and hold significant automation investment decisions until the licensing picture at general availability is clearer.

The direction Microsoft is taking here is right. The commercial model around access to it is the part that still needs work.