cleandataengineering.aiAgent Harness, drawn simply
You are here: Tech stack › 17 · Agent-to-agent

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.

AZURE OPTIONSAPI Center◐ planned: agent registryFoundry connected agents· considered: not pickedAgent Framework A2A· considered: not pickedOUR CHOICEA2A endpointsnot built yetAPI Center registryplannedOPEN-SOURCE OPTIONSA2A SDK◐ planned: chosenBackstage· considered: registry, not pickedWHO DOES THE WORKAzure gives 20% · we code once 60% · each agent team still does 20%
Dark boxes are what we run. Solid boxes are used or planned; dashed boxes were considered or dropped (crossed). The bar: grey is what Azure gives, dark is what we code once, hatched is what each agent team writes.
Why our choiceAn open protocol on our own compute keeps hand-offs typed, bounded and in one trace without tying them to Foundry.
OptionWhere fromVerdictWhy
A2A endpointsours✓ chosennot built yet
API Center registryours✓ chosenplanned
API CenterAzure◐ plannedagent registry
Foundry connected agentsAzure· considerednot picked
Agent Framework A2AAzure· considerednot picked
A2A SDKopen source◐ plannedchosen
Backstageopen source· consideredregistry, not picked

Not built yet in the claims assistant; designed in the Series.

Compared: How do agents hand work to other agents?

A2A SDK endpoints on …open sourcechosenFoundry connected age…Azureonly on FoundryMicrosoft Agent Frame…open source.NET teams onlyIn-process hand-off (…oursinside one agentAzure API Center (reg…Azurechosen
Dark: what we chose. Crossed and dashed: rejected or not for us. Added here (not a Series table).
OptionFromVerdictWhere agents runOpen protocolWorks across vendorsTyped hand-off and limitsStatus
A2A SDK endpoints on Container Appsopen sourcechosenour Container Appsyes: A2Ayesours: ticket, depth, fan-outfinal (design)
Foundry connected agentsAzureonly on FoundryFoundry Agent Serviceno: Foundry's ownFoundry agents onlyFoundry'sif the loop moves to Foundry
Microsoft Agent Framework A2Aopen source.NET teams onlyanywhereyes: A2A supportyespartly framework, partly ourslisted Azure option
In-process hand-off (one service)oursinside one agentone processnonooursfine within one agent
Azure API Center (registry)Azurechosenregistry, not a runtimelists A2A endpointsyesnofinal: 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.