Back to the canvas
Architecture
Enterprise chat on Azure
A private chat front end on Azure: gateway, private network, agent, search and model.
What it shows
The shape of production enterprise chat on Azure: one public entry point, and everything else private. The user reaches an application gateway with a web application firewall; behind it, the chat UI runs inside a private network.
The UI calls an agent with a managed identity. The agent reaches the model, the search index used for grounding and the state store over private endpoints, and external tools only through a firewall.
Key decisions
- One public front door; every other service is reachable only from the private network.
- Services authenticate with managed identities, so there are no keys to leak.
- Calls to external tools leave through a firewall, which is where they can be allowed, logged or denied.