Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Workflows are UI-based tools in Microsoft Foundry. Use them to create declarative, predefined sequences of actions that orchestrate agents and business logic in a visual builder.
Workflows enable you to build intelligent automation systems that seamlessly blend AI agents with business processes in a visual manner. Traditional single-agent systems are limited in their ability to handle complex, multifaceted tasks. By orchestrating multiple agents, each with specialized skills or roles, you can create systems that are more robust, adaptive, and capable of solving real-world problems collaboratively.
Prerequisites
- An Azure account with an active subscription. If you don't have one, create a free Azure account, which includes a free trial subscription.
- A project in Microsoft Foundry. For more information, see Create projects.
- Access to create and run workflows in your Foundry project. For more information, see Azure role-based access control (RBAC) in Foundry.
Decide when to use workflows
Workflows are ideal for scenarios where you need to:
- Orchestrate multiple agents in a repeatable process.
- Add branching logic (for example, if/else) and variable handling without writing code.
- Create human-in-the-loop steps (for example, approvals or clarifying questions).
If you want to edit workflow YAML in Visual Studio Code or run workflows in a local playground, see:
- Work with Declarative (Low-code) Agent workflows in Visual Studio Code
- Work with Hosted (Pro-code) Agent workflows in Visual Studio Code
Understand workflow patterns
Foundry provides templates for common orchestration patterns. Start with a blank workflow or select a template:
| Pattern | Description | Typical use case |
|---|---|---|
| Human in the loop | Asks the user a question and awaits user input to proceed | Creating approval requests during workflow execution and waiting for human approval, or obtaining information from the user |
| Sequential | Passes the result from one agent to the next in a defined order | Step-by-step workflows, pipelines, or multiple-stage processing |
| Group chat | Dynamically passes control between agents based on context or rules | Dynamic workflows, escalation, fallback, or expert handoff scenarios |
For more information, see Microsoft Agent Framework workflow orchestrations.
Create a workflow
This procedure shows how to create a sequential workflow. The same general steps apply to other workflow types.
-
Sign in to Microsoft Foundry. Make sure the New Foundry toggle is on. These steps refer to Foundry (new).
On the upper-right menu, select Build.
Select Create new workflow > Sequential.
Assign an agent to the agent nodes by selecting each agent node in the workflow and either selecting the desired agent or creating a new one. For more information, see Add agents later in this article.
Select Save in the visualizer to save the changes.
Important
Foundry doesn't save workflows automatically. Select Save after every change to preserve your work.
Select Run Workflow.
Interact with the workflow in the chat window.
Optionally, add new nodes to your workflow. The next section in this article provides information about nodes.
Verify your workflow run
After you select Run Workflow, verify that:
- Each node completes in the visualizer.
- You see the expected responses in the chat window.
- Any variables you save (for example, JSON output from an agent node) contain the values you expect.
Add nodes
Nodes are the building blocks of your workflow. Each node performs a specific action in sequence.
Common node types include:
- Agent: Invoke an agent.
- Logic: Use if/else, go to, or for each.
- Data transformation: Set a variable or parse a value.
- Basic chat: Send a message or ask a question to an agent.
When you select a prebuilt workflow, the builder displays the nodes in sequence. To reorder nodes, select the three dots on a node and then select move. To add nodes, select the plus (+) icon in the workspace.
Add agents
Add any Foundry agent from your project to the workflow. Agent nodes also let you create new agents with customized capabilities by configuring their model, prompt, and tools.
For advanced agent creation options, go to the Foundry Agent tab in the Foundry portal.
Add an existing agent
In the workflow visualizer, select the plus sign.
In the pop-up dropdown list, select Invoke agent.
In the Create new agent window, select existing.
Enter the agent name to search for existing agents in your Foundry project.
Select the desired agent to add it into your workflow.
Create a new agent
In the workflow visualizer, select the plus sign.
In the pop-up dropdown list, select Invoke agent.
Enter an agent name and description of what the agent does.
Select Add.
In the Invoke an agent window, configure the agent.
Select Save.
Configure an output response format
To configure an agent to return structured JSON output:
In the Invoke agent configuration window, select Create a new agent.
Configure the agent to send output as a JSON schema:
- Select Details.
- Select the parameter icon.
- For Text format, select JSON Schema.
Copy the desired JSON schema and paste it in the Add response format window. The following screenshot shows a math example. Select Save.
Important
Don't include secrets (passwords, keys, tokens) in JSON schemas, prompts, or saved workflow variables.
{
"name": "math_response",
"schema": {
"type": "object",
"properties": {
"steps": {
"type": "array",
"items": {
"type": "object",
"properties": {
"explanation": {
"type": "string"
},
"output": {
"type": "string"
}
},
"required": [
"explanation",
"output"
],
"additionalProperties": false
}
},
"final_answer": {
"type": "string"
}
},
"additionalProperties": false,
"required": [
"steps",
"final_answer"
]
},
"strict": true
}
Select Action settings. Then select Save output json_object/json_schema as.
Select Create new variable. Choose a variable name, and then select Done.
Configure additional features
YAML visualizer view: Set the YAML Visualizer View toggle to On to store the workflow as a YAML file. Edit in either the visualizer or the YAML view. Saving creates a new version with full version history.
Both the visualizer and YAML are editable. Changes to the YAML file appear immediately in the visualizer.
Versioning: Each save creates a new, unchangeable version. To view version history or delete older versions, open the Version dropdown list to the left of the Save button.
Notes: Add notes to the workflow visualizer for extra context. In the upper-left corner of the visualizer, select Add note.
Create expressions with Power Fx
Power Fx is a low-code language that uses Excel-like formulas. Use Power Fx to create complex logic that lets your agents manipulate data. For example, a Power Fx formula can set a variable value, parse a string, or evaluate a condition. For more information, see the Power Fx overview and formula reference.
Use variables in a formula
To use a variable in a Power Fx formula, you must add a prefix to its name to indicate the variable's scope:
- For system variables, use
System. - For local variables, use
Local.
Here are the system variables:
| Name | Description |
|---|---|
Activity |
Information about the current activity |
Bot |
Information about the agent |
Conversation |
Information about the current conversation |
Conversation.Id |
Unique ID of the current conversation |
Conversation.LocalTimeZone |
Time zone of the user, in the IANA Time Zone Database format |
Conversation.LocalTimeZoneOffset |
Time offset from UTC for the current local time zone |
Conversation.InTestMode |
Boolean flag that represents if the conversation is happening on a test canvas |
ConversationId |
Unique ID of the current conversation |
InternalId |
Internal identifier for the system |
LastMessage |
Information about the previous message that the user sent |
LastMessage.Id |
ID of the previous message that the user sent |
LastMessage.Text |
Previous message that the user sent |
LastMessageId |
ID of the previous message that the user sent |
LastMessageText |
Previous message that the user sent |
Recognizer |
Information about intent recognition and the triggering message |
User |
Information about the user currently talking to the agent |
User.Language |
User language locale per conversation |
UserLanguage |
User language locale per conversation |
Use literal values in a formula
In addition to using variables in a Power Fx formula, you can enter literal values. To use a literal value in a formula, you must enter it in the format that corresponds to its type.
The following table lists the data types and the format of their corresponding literal values:
| Type | Format examples |
|---|---|
| String | "hi", "hello world!", "copilot" |
| Boolean | Only true or false |
| Number | 1, 532, 5.258,-9201 |
| Record and table | [1], [45, 8, 2], ["cats", "dogs"], { id: 1 }, { message: "hello" }, { name: "John", info: { age: 25, weight: 175 } } |
| Date and time | Time(5,0,23), Date(2022,5,24), DateTimeValue("May 10, 2022 5:00:00 PM") |
| Choice | Not supported |
| Blank | Only Blank() |
Common Power Fx formulas
The following table lists the Power Fx formulas that you can use with each data type.
Set a variable with Power Fx
This example shows how to store and output a customer's name in capital letters:
Create a workflow and add an Ask a question node.
On the pane that appears, in the Ask a question box, enter What is your name? or another message. In the Save user response as box, enter a variable name; for example,
Var01. Then select Done.Add a Send message action. On the pane that appears, in the Message to send area, enter
{Upper(Local.Var01)}. Then select Done.Select Preview.
On the preview pane, send a message to the agent to invoke the workflow.
Create if/else flows with Power Fx
This example shows how to add an if/else flow and build a condition with system variables.
Create a workflow and add an Ask a question node.
Select the + icon and add an if/else flow.
Type
System.in the Condition box to build a condition statement for each if/else branch.Select a Next Action for the next step in the workflow.
Select Done. Select Save to save your workflow.
Troubleshooting
| Issue | Solution |
|---|---|
| Workflows option not visible or can't create/edit workflows | Confirm you have the Contributor role or higher on your project. See Azure role-based access control (RBAC) in Foundry. |
| Changes don't appear after editing | Select Save in the visualizer. Foundry doesn't save changes automatically. |
| Workflow run produces unexpected output | Verify each agent node has an agent assigned. Check that saved outputs (JSON schema) are valid. |
| Power Fx formula error: "Name isn't valid" | Add the correct scope prefix. Use System. for system variables and Local. for local variables. |
| Power Fx formula error: "Type mismatch" | Verify the variable type matches the expected input. Use conversion functions like Text() or Value() if needed. |
| Workflow times out | Break complex workflows into smaller segments. Check that external services respond within expected timeframes. |
Clean up resources
To delete a workflow you no longer need:
- Open the workflow in the Foundry portal.
- Select the Version dropdown list to the left of the Save button.
- Select Delete for the version you want to remove.