Microsoft recently unveiled Workflows inside Copilot Studio—a sleek new automation builder that promises to simplify bot creation. But as with many shiny announcements, the real story lies beneath the surface. Workflows are not an entirely fresh invention; they are built on Power Automate, which itself traces its roots back to Azure Logic Apps. In fact, there are now five distinct ways to build your automation logic, ranging from the classic designer to code‑first editors. Each has its own strengths, quirks, and target audience. Understanding these options helps you pick the right tool for your scenario. Below we break down each milestone in the journey from Logic Apps to the modern Workflows experience.
1. The Foundation: Azure Logic Apps
Every flow you create in Power Automate is, under the hood, an Azure Logic App. The original Power Automate (then called Microsoft Flow) was simply a Logic App with a simplified interface and a few missing or extra connectors. Even the schema remained identical—the client data still references https://schema.management.azure.com/providers/Microsoft.Logic/schemas/2016‑06‑01/workflowdefinition.json. When Logic Apps transitioned to a fully client‑side V3 UI, Power Automate followed suit. The core engine, trigger types, actions, and even the billing logic are shared. So whether you build a flow in the classic designer, the new V3 interface, or directly in Copilot Studio, you are ultimately working with the same Logic Apps runtime. This common foundation is why flows built in different UIs are completely interchangeable at the definition level.
2. The Classic UI: A Developer Favorite That Still Lingers
For years, the original Logic Apps / Power Automate designer—now called the Classic UI—was the go‑to interface. Developers loved its straightforward layout: actions displayed as blocks with inline inputs. When Microsoft launched the new V3 designer, many features were missing, causing a slow migration. Microsoft even introduced a toggle to switch back. Today, even though V3 is the default, you’ll still encounter the Classic UI in Power Apps when selecting a flow, in some legacy logs, and randomly when creating a flow from a solution screen. Its persistence shows that a well‑loved tool doesn’t disappear overnight. The Classic UI remains available for those who prefer the old‑school workflow, though it lacks the modern side panel, Copilot integration, and advanced version control found in V3.
3. The New UI (V3): The Modern Face of Power Automate
The V3 designer is currently the standard interface for Power Automate. It is 100% client‑side, meaning all logic runs in the browser, and yet it produces identical flow definitions to the Classic UI. You cannot tell from the workflow table whether a flow was built in V3 or Classic—they are 100% interchangeable. The major change was the move from inline inputs and buttons inside actions to a side panel. This panel provides a fresh, modern look and introduces new capabilities like built‑in version control and Copilot integration. The side panel makes editing complex actions easier by keeping the main canvas uncluttered. Despite early feature gaps, V3 has matured and is now the recommended way to build Power Automate flows. It also supports a code editor (and even a VS Code extension) for those who prefer to work in code.
4. Agent Flows (Inline): Copilot Studio’s Special Automation Layer
When Copilot Studio was introduced, its automation builder looked identical to Power Automate’s V3 designer. The only difference was billing: Power Automate runs consume API allowances tied to the owner, while Agent Flows use Copilot Studio credits. That changed in August 2025 when Microsoft rolled out a different UI for Agent Flows—a hybrid of Classic and V3 elements. It features inline inputs (reminiscent of Classic) combined with a side panel and other V3 benefits. When you open the same flow in Power Automate, it falls back to the standard V3 designer. Interestingly, this “inline” UI was supposed to launch in Power Automate at the same time, but it was delayed to February and then pulled due to performance issues. It is now planned for late 2026. So for now, Agent Flows enjoy a unique design that bridges old and new.
5. Workflows: The Latest Automation Builder in Copilot Studio
Announced in early 2025, Workflows is a new automation builder inside Copilot Studio. Despite the fresh branding, it is fundamentally built on Power Automate flows—the same runtime we’ve been discussing. Workflows offer a streamlined, low‑code experience tailored for conversational AI scenarios, making it easier to chain actions like sending an email, updating a CRM record, or calling an API directly from a bot. Because they share the underlying Power Automate engine, you can export a Workflow and view it in the standard V3 designer. The real innovation is the inline editing experience that feels more natural within the Copilot Studio canvas. As of now, Workflows represent the fifth and newest way to build automations. They simplify the developer journey while staying fully compatible with the Logic Apps ecosystem. Looking ahead, expect more convergence between these interfaces as Microsoft continues to unify its automation platform.
In summary, the automation landscape inside Microsoft’s ecosystem has grown from a single root (Logic Apps) into five distinct paths: Classic UI, V3 UI, Agent Flows (Inline), and the latest Workflows. Each offers a unique user experience, but they all share the same powerful engine. Whether you are a seasoned developer or a business user, understanding these options lets you choose the right path for your project. As Microsoft evolves its rollout strategy—sometimes bumpy, as with the delayed inline UI—the underlying technology remains robust and interoperable. Keep an eye on future updates, because the line between these interfaces is likely to blur even further.