AGENTMESH
agentmesh · running it from a microsoft shop

Your company runs on Azure.
Here is exactly what the mesh touches.

Tom's week tells this story without naming a vendor. This page tells it for a Microsoft shop: the agent you already have, the few places the mesh touches it, and a page in the menu for each decision. Renwick Mutual is the whole thing run end to end.

Agent Builder and Copilot Studio produce agents that live inside Microsoft's own surfaces; Microsoft Foundry Agent Service and the Microsoft Agent Framework produce agents with an address of their own, and that difference decides most of what follows here.

the starting point

The agent you already have

Concretely, the thing most Microsoft shops mean when they say agent:

a typical azure agent · before the mesh knows it exists
  • Built with the Microsoft Agent Framework or the Semantic Kernel code that came before it, reasoning on models in Microsoft Foundry
  • Answering over HTTPS from Container Apps, AKS or App Service, often behind API Management
  • Running as a managed identity with Microsoft Entra ID deciding what its tools may touch
  • Using your tools and data internal APIs, Fabric, SQL, whatever the job needs
  • Watched in Application Insights like every other service you run
  • Secrets in Key Vault rotated on your existing runbook

the touch points

Where the mesh touches it

The mesh touches this agent in a small number of places, each one a decision with its own page in the menu. Everything else, the model, the prompts, Microsoft Entra ID, the tools, where it runs, stays exactly as your team built it.

its agent card Read once over HTTPS, when the gateway starts standing in front of the agent. The agent itself changes not at all, and this is where most shops start. decision 02
its code Touched only when the agent must start work rather than answer it: one SDK library, one outbound WebSocket held by the agent's own process. decision 02
its runtime Unchanged while the gateway is fronting it. Holding a mesh connection of its own means staying resident: one replica on AKS, one always-on revision on Container Apps. decision 03
its network One outbound flow on 443. Nothing listens, no inbound rule, no public address. decision 04
its secrets One mesh credential in Key Vault beside the ones already there, born from a single-use key and renewing itself. decision 05
its traces The hop between companies reaches the Application Insights resource you already open, as ordinary OTLP spans. decision 06
its inbox Mail from other companies' agents goes past a screener you name before the agent sees it. decision 07
all of the above Points at the public instance by default, or at a mesh you run yourself. decision 01

To see the whole thing as one story with every command, Renwick Mutual takes its triage agent from attached to full node to traced, end to end.