Identify Workflow Patterns
Unit 3 of 10 · Module 12: Build agent-driven workflows using Microsoft Foundry
Read this lesson
Three ways to play
The shape of a workflow matters as much as the agents inside it. Think of a school sports day, where each event has its own rules for who moves when. Foundry gives you templates for three common shapes, so you can pick one before you design anything.
The relay race
A sequential workflow is a relay race. Each runner takes the baton, runs their leg, and hands it to the next, always in the same order. In a workflow, each step passes its output to the next one. That's perfect for pipelines with stages, like checking the input, adding extra details, and then writing the final answer. It's predictable and easy to follow, which makes it the best place to start.
The judge's whistle
A human in the loop workflow stops for a person. Picture a judge who has to confirm a close finish before the results go up. The workflow asks a question, waits for the answer, and then carries on based on what the person said. Use it for approvals, confirmations, or whenever a person has to supply something the agents don't know.
The passing game
A group chat workflow is more like a football match. There's no fixed order: the ball goes to whichever player is best placed, based on what's happening. Here, control moves between specialist agents according to the context, some rules, or earlier results. That suits customer support, handing off to an expert, falling back when one agent can't help, or questions that span several subjects. Pick the shape that matches how decisions get made in your scenario, and then start building.
Facts from Microsoft's documentation: Build a workflow in Microsoft Foundry (Preview) (CC BY 4.0), rewritten in Loop's own words and examples. Narration, animation, and quiz by Loop. Microsoft, Azure, and Microsoft Foundry are trademarks of Microsoft. Loop is independent and not affiliated with or endorsed by Microsoft.