cleandataengineering.aiAgent Harness, drawn simply
You are here: Architecture › On Azure › Big picture on Azure

Agent Harness Tutorial · Architecture

The big picture, on Azure

The same picture as the abstract big picture, with an Azure name in every box. Put the two side by side: the boxes don't move, only the names change.

LIFECYCLEIdea & risk tierBuildGitHub, ActionsOpen: EvaluateEvaluateFoundry + AgentTwinOpen: Red-teamRed-teamAI Red TeamingApproveOpen: ReleaseReleaserevisionsOpen: MonitorMonitorAzure MonitorOpen: LearnLearnmisses → golden setGOVERNANCEAzure Policyguardrails on resourcesPurviewdata governanceDefender for CloudthreatsEntra ID Governanceaccess reviewsResidencyregion pinnedOwner & risk tierin the registryEND USERS · WHO ASKSPolicyholdersEntra External IDBrokers & agentsExternal ID, partnerClaims handlersEntra ID, staffUnderwriters & opsEntra ID, staffCHANNELS · WHERE THEY ASKWeb & app chatwidget + ChatwootWhatsAppComm. ServicesEmailComm. ServicesContact centrevia handoffTeamsBot ServiceFRONT DOOR · CHECKS EVERY REQUESTOpen: EdgeEdgeFront Door + WAFOpen: Hidden instructions?Hidden instructions?Prompt ShieldsOpen: Personal data?Personal data?AI Language PIIOpen: In scope?In scope?our router rulesOpen: Fair shareFair shareAPIM rate + tokenORCHESTRATIONOpen: RouterRouterour code · Container AppsA2A handoffA2A over HTTPSAgent registryAPI Center + GitVERTICAL AGENTS · INSURANCE COMPANY · A CONTAINER APP EACHOpen: Claims FNOL intakeClaims FNOL intakeacts after checksClaims triagedrafts for a handlerFraud signalssuggests onlyUnderwriting assistantdraftsPolicy servicingacts after OKRenewals & retentiondraftsBroker deskanswersNext group companynew lanes plug in↓ every agent reuses the same assetsHORIZONTAL ASSETS · BUILD ONCE, REUSE EVERYWHERE · ON AZUREOpen: Model gatewayModel gatewayAPIM → FoundryKnowledgepgvectorOpen: Memory & stateMemory & statePostgreSQLOpen: Tool / MCP hubTool / MCP hubMCP + APIMChannel adaptersComm. ServicesOpen: Identity & accessIdentity & accessEntra · Key VaultOpen: GuardrailsGuardrailsContent Safety + rulesOpen: Human deskHuman deskworkflow + TeamsOpen: ObservabilityObservabilityApp Insights · PromOpen: Cost controlCost controlAPIM · Cost MgmtOpen: Eval libraryEval libraryFoundry + AgentTwinOpen: Release & configRelease & configApp Config · ACRSYSTEMS OF RECORD · VIA APIM AND PRIVATE LINKPolicy adminOpen: Claims systemClaims systemBilling & paymentsCRMDocumentsThird-party dataVAHAN, bureaus
Cells with a small circle open the design page for that piece.

Systems of record are reached through APIM and Private Link, always on the user's behalf. Model availability must be checked per Indian region.

Want every detail? The long version is in the Series: Azure on the big picture.

How it is done: the real code

Cut from the live repositories each time the site is built, so it always matches what runs.

config/azure.yaml:32One binding: the model port goes to the APIM AI gateway
  model:
    adapter: apim-ai-gateway
    base_url: {env: APIM_GROQ_BASE_URL}
    api_key: {key_vault: apim-subscription-key}