Skip to content

Commit 026d96a

Browse files
committed
reconfiguring
1 parent d437e78 commit 026d96a

File tree

1 file changed

+18
-12
lines changed

1 file changed

+18
-12
lines changed

articles/ai-services/agents/concepts/multi-agent-workflows.md

Lines changed: 18 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -17,25 +17,31 @@ Use this article to learn about how to streamline complex processes by utilizing
1717

1818
Multi-agent workflows involve the coordinated efforts of multiple AI agents, each specializing in different tasks or possessing distinct capabilities. These agents communicate and collaborate to complete intricate processes that would be challenging for a single agent to handle.
1919

20-
Multi-agent workflows consist of:
20+
## Solutions
2121

22-
* A main agent: These agents act as the primary interaction point with end-users. The agent manages the workflow, determining which (if any) connected agents are called and that tasks are delegated appropriately.
23-
* Task-specific connected agents: These agents focus on specific tasks such as data extraction, analysis, or decision-making. They are called by the main agent to perform their task and return outputs.
22+
AI Foundry Agent Service enables you to develop multi-agent applications in the following ways.
2423

25-
:::image type="content" source="../media/multi-agent/agent-tree.png" alt-text="A diagram showing a main agent and several sub agents.":::
24+
### Connected agents
2625

27-
Agent coordination is responsible for defining and executing the sequence of tasks within a workflow. An event-driven architecture is used to trigger actions based on specific events. In a basic implementation, for example, all user interaction goes through the main agent, which then hands-off to connected agents. When the connected agent completes a task, the output is passed back to the main agent.
26+
The [connected agents](../how-to/connected-agents.md) feature lets you define and manage one or more specialized agents, and handles agent-to-agent communication. The benefit of using the connected agents feature is that orchestration is handled for you, and you can use the AI Foundry portal or a code-based approach to configure your agent setup.
2827

29-
:::image type="content" source="../media/multi-agent/example-thread.png" alt-text="A diagram showing a main agent and several sub agents.":::
28+
### Semantic Kernel
3029

31-
## Multi-agent solutions in AI Foundry Agent Service
30+
[Semantic Kernel](/semantic-kernel/overview/) is an open-source SDK that lets you build AI agents with the flexibility to define custom agent orchestration, making it useful for more complex multi-agent interactions. The `AzureAIAgent` in the [Semantic Kernel framework](/semantic-kernel/frameworks/agent/azure-ai-agent) lets you integrate the AI Foundry Agent Service into your applications, and provides tools for creating a [multi-agent solution](/semantic-kernel/frameworks/agent/agent-chat).
3231

33-
AI Foundry Agent Service enables you to develop multi-agent solutions in two ways: The connected agent feature, and using the Semantic kernel.
32+
### Agent catalog
3433

35-
### Connected agents
34+
The [Agent catalog](../how-to/agent-catalog.md) provides a number of preconfigured multi-agent code samples to help streamline agent deployment for several domains. These code samples include setup instructions and configuration files, including tools where necessary.
3635

37-
The [connected agents](../how-to/connected-agents.md) feature lets you define and manage one or more specialized agents, and handles agent-to-agent communication. The benefit of using the connected agents feature is that orchestration is handled for you, and you can use the AI Foundry portal or a code-based approach to configure your agent setup.
36+
## Understanding multi-agent workflows
3837

39-
### Semantic Kernel
38+
Multi-agent workflows consist of:
39+
40+
* A main agent: These agents act as the primary interaction point with end-users. The agent manages the workflow, determining which (if any) connected agents are called and that tasks are delegated appropriately.
41+
* Task-specific connected agents: These agents focus on specific tasks such as data extraction, analysis, or decision-making. They are called by the main agent to perform their task and return outputs.
4042

41-
[Semantic Kernel](/semantic-kernel/overview/) is an open-source SDK that lets you build AI agents with the flexibility to define custom agent orchestration, making it useful for more complex multi-agent interactions. The `AzureAIAgent` in the [Semantic Kernel framework](/semantic-kernel/frameworks/agent/azure-ai-agent) lets you integrate the AI Foundry Agent Service into your applications, and provides tools for creating a [multi-agent solution](/semantic-kernel/frameworks/agent/agent-chat).
43+
:::image type="content" source="../media/multi-agent/agent-tree.png" alt-text="A diagram showing a main agent and several sub agents.":::
44+
45+
Agent coordination is responsible for defining and executing the sequence of tasks within a workflow. An event-driven architecture is used to trigger actions based on specific events. In a basic implementation, for example, all user interaction goes through the main agent, which then hands-off to connected agents. When the connected agent completes a task, the output is passed back to the main agent.
46+
47+
:::image type="content" source="../media/multi-agent/example-thread.png" alt-text="A diagram showing a main agent and several sub agents.":::

0 commit comments

Comments
 (0)