Agent Harness Tutorial · Architecture
The horizontal assets and the five families
The concerns fall into five families. Each family becomes a few horizontal assets that our platform team builds once on Azure and every agent reuses.
| Family | Asset | What every agent gets | On Azure | Owner |
|---|---|---|---|---|
| Think | Model gateway | any model, one door | APIM AI gateway → Foundry Models | Platform |
| Think | Knowledge & retrieval | policy wordings, SOPs | PostgreSQL + pgvector | Platform + data |
| Think | Memory & state | case, session | Azure Database for PostgreSQL | Platform |
| Act | Tool / MCP hub | typed actions | MCP servers on Container Apps + APIM | Platform + domain teams |
| Act | A2A handoff | agent to agent | A2A endpoints on Container Apps | Platform |
| Act | Channel adapters | chat, WhatsApp, email | Communication Services · Chatwoot · Teams | Platform + CX |
| Control | Identity & secrets | agents get own IDs | Entra · managed identity · Key Vault | Security |
| Control | Guardrails & policy | rules as code | Content Safety + our positioned rules | Security + risk |
| Control | Human desk & approvals | approvals, handoff | DBOS / Temporal + Teams cards | Platform + operations |
| See | Observability & replay | trace, replay | App Insights · Managed Prometheus · Grafana | Platform + SRE |
| See | Cost control | budget per agent | Our meter · APIM token limits · Cost Management | Platform + FinOps |
| Change | Eval library | golden sets, red-team | GitHub Actions · Foundry evaluation | Assurance team + QA |
| Change | Release & config | versions, rollback | App Configuration · revisions · ACR | Platform |
| Change | Agent registry | who exists, which version | API Center + catalogue in Git | Architecture board |
Want every detail? The long version is in the Series: the horizontal assets.