Microsoft Foundry — hosted agents & Azure OpenAI

Point Chamade at an agent you built in the Foundry portal, or at a plain Azure OpenAI deployment. Chamade dispatches each event to it and delivers the reply — no infra to run on your side.

What it is

Foundry speaks the OpenAI Responses API, so Chamade talks to it the same way it talks to OpenAI. Two shapes both work under the Microsoft Foundry preset:

• Azure OpenAI / Custom (Responses) — a model deployment. Chamade owns the persona (the system prompt) and can inject its tools. The simplest path.
• Foundry portal hosted agent — a no-code agent you build in ai.azure.com (instructions, model, portal tools). Chamade invokes its endpoint.

Either way: a human messages your agent, Chamade calls it with the message, and delivers whatever it replies. Memory is kept natively (OpenAI Conversations + per-tenant isolation).

Setup

1. Build your agent (Foundry portal) or pick a model deployment (Azure OpenAI).
2. Copy the endpoint URL and an API key (portal → Settings → Keys & endpoints).
3. In your dashboard → an agent → Microsoft Foundry preset → paste the URL + key + a model name → Create. Chamade probes it on save.

Region matters

The Responses API is region-gated. West Europe is not supported (you'll get a 404 if you try). Provision your Foundry / Azure OpenAI resource in a supported region — Sweden Central is the EU default; France Central, Germany West Central, UK South, Switzerland North and others also work.

Giving the agent Chamade's tools

Two complementary mechanisms:

• Act via the XML convention — your agent's reply text can carry inline tags (<write>, <say>, <dm>, <accept/>…) which Chamade executes. Works for every Foundry shape, zero setup. Each event already carries an [agent context] line with your accounts, so cross-target actions need no lookup.
• Read via Chamade's MCP — for the Azure OpenAI / Custom (Responses) preset, Chamade auto-injects its hosted MCP as a read backstop (default-on), so the agent can look up anything not pre-stuffed (transcripts, history, fresh state). The suggested system prompt encodes the rule: act with XML, read with MCP — so nothing fires twice.

For a portal hosted agent, Chamade can't inject the MCP (the portal owns the agent's tool list). To give it Chamade tools, add an MCP tool in the portal pointing at https://mcp.chamade.io/mcp/, authenticated with a project connection holding your agent's bearer (dashboard → agent → Internal bearer). Acting still works for free via XML.

Keyless (Microsoft Entra)

Chamade verifies Microsoft Entra tokens, so a Foundry agent can authenticate to the MCP with its managed identity — no key to copy. Configure the MCP tool's auth as Microsoft Entra targeting the audience shown in dashboard → agent → Identity auth, and authorize the agent's identity there.