Agent Harness Tutorial · Tech stack
17 · Agent-to-agent
Agents hand work to agents through typed, bounded, traced hand-offs. Family: Act · one turn, in order.
Why our choiceAn open protocol on our own compute keeps hand-offs typed, bounded and in one trace without tying them to Foundry.
| Option | Where from | Verdict | Why |
|---|---|---|---|
| A2A endpoints | ours | ✓ chosen | not built yet |
| API Center registry | ours | ✓ chosen | planned |
| API Center | Azure | ◐ planned | agent registry |
| Foundry connected agents | Azure | · considered | not picked |
| Agent Framework A2A | Azure | · considered | not picked |
| A2A SDK | open source | ◐ planned | chosen |
| Backstage | open source | · considered | registry, not picked |
Not built yet in the claims assistant; designed in the Series.
Compared: How do agents hand work to other agents?
| Option | From | Verdict | Where agents run | Open protocol | Works across vendors | Typed hand-off and limits | Status |
|---|---|---|---|---|---|---|---|
| A2A SDK endpoints on Container Apps | open source | chosen | our Container Apps | yes: A2A | yes | ours: ticket, depth, fan-out | final (design) |
| Foundry connected agents | Azure | only on Foundry | Foundry Agent Service | no: Foundry's own | Foundry agents only | Foundry's | if the loop moves to Foundry |
| Microsoft Agent Framework A2A | open source | .NET teams only | anywhere | yes: A2A support | yes | partly framework, partly ours | listed Azure option |
| In-process hand-off (one service) | ours | inside one agent | one process | no | no | ours | fine within one agent |
| Azure API Center (registry) | Azure | chosen | registry, not a runtime | lists A2A endpoints | yes | no | final: who exists, which version |
DecisionAgents hand off over the open A2A protocol on Container Apps, with our typed hand-off ticket, depth and fan-out limits and one trace, and are listed in API Center. Foundry connected agents would make sense only if the loop moved into Foundry.