Maintain Workflows in Microsoft Foundry
Unit 7 of 10 · Module 12: Build agent-driven workflows using Microsoft Foundry
Before you start
Short explainers for ideas this lesson builds on. Watch these first if they're new to you.
Read this lesson
Two views of one design
A workflow isn't finished when it first works; the business changes, and so do the models. Think of an architect's studio, where every building exists twice: as a scale model on the table and as a blueprint in the drawer. Foundry workflows also have two views. The visual canvas is best for understanding the flow, tracing paths, and working with others. YAML is the text version: good for detailed settings, tracking changes, and keeping in source control. Turn on the YAML view and edit either one; a change in one shows up in the other straight away.
Every save is a new drawing
Every time you save, Foundry keeps a new version that can't be changed afterwards, like a dated drawing filed in the plan chest. Open the version list next to the Save button to review earlier versions, compare them, or go back to one if a change breaks something. That history also shows teammates who changed what, and why.
Notes and tidy habits
Architects pin notes to their models, and you can add notes to the canvas too. Use them to explain a design decision, what a variable holds, or why a branch exists, so the next person doesn't have to guess. Keep a few habits. Review regularly for nodes you no longer use. Make sure structured agent outputs are handled the same way everywhere. Write your reasons down in notes, and lean on the version history to check each change.
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.