A Microsoft Agent Framework workflow uses a classifier agent to label each incoming email…

How it works

In a Microsoft Agent Framework workflow, edges define how messages flow between executors. Edges can include conditions that control routing based on message contents. The framework has several edge types, each with a typical use case:

• Direct: simple one-to-one connections. Use case: linear pipelines.
• Conditional: edges with conditions that decide when messages flow. Use case: binary routing (if/else).
• Switch-case: route to different executors based on conditions. Use case: multi-branch routing.
• Multi-selection (fan-out): one executor sends messages to multiple targets. Use case: parallel processing.
• Fan-in: multiple executors send to a single target. Use case: aggregation.

This workflow has two steps. First, route each email to exactly one of three handlers based on the classifier's label: three-way, one target, so switch-case. The edges tutorial uses switch-case to replace multiple conditional edges for cleaner three-way routing. Second, send all handler outputs into one summary executor: fan-in.

The other options, and when you'd use them

• Group chat instead of edges: In group chat, agents collaborate in a shared conversation. This workflow needs deterministic routing between executors.
• Direct edges only: They're simple one-to-one connections with no routing logic.
• Multi-selection (fan-out): It sends one message to multiple targets for parallel processing. Each email must reach exactly one handler.

Exam tip

One of N by condition = switch-case. Many targets at once = fan-out. Many into one = fan-in. A to B = direct.

References

• Microsoft Agent Framework Workflows - Edges
• Workflow orchestrations