What it does

The workflows experience brings deterministic, flow-style automation into the same designer you build agents in, so an agent's structured steps and its conversational logic sit together rather than living in a separate Power Automate tab.

Key facts

• Aims to unify agent authoring and workflow automation in one visual canvas.
• Gives you deterministic sequencing where you need it, alongside generative orchestration where you don't.
• Still sits on the Power Platform automation engine underneath, so the same connectors and licensing apply.
• A newer, evolving experience — details shift release to release, so confirm current behaviour before you commit a design.

When to use / skip

Use it when an agent needs reliable, ordered steps that must run the same way every time and you'd rather not bounce out to a separate flow. Skip it for purely conversational agents that don't automate anything downstream.

Configuration decisions

• Which parts of a process are deterministic workflow vs model-driven orchestration.
• Where workflow logic lives — inside the agent or as a reusable flow called as a tool.
• How workflows are packaged in solutions for deployment.

Gotchas

• It overlaps with classic Power Automate; decide your standard so teams don't build the same logic two ways.
• Being newer, capabilities and limits are still moving — don't assume parity with mature Power Automate.

Consultant notes

• Pin down whether new automation goes here or in standalone flows before makers pick their own path.
• Keep ALM consistent — workflows still need to travel through solutions and environments.
• Watch the roadmap; treat current limits as temporary and design with a fallback.

---

*Confirm against the latest Copilot Studio release notes