Microsoft Foundry Agent Service

If your agent runs in Microsoft Foundry Agent Service (formerly Azure AI Agent Service), MeetCrew fronts it as a meeting teammate. Your Agent Service agent supplies the reasoning; MeetCrew supplies the presence and the voice.

A first-class Azure backend

Microsoft Foundry Agent Service is a first-class backend. You bind your agent to a teammate deployment in the admin console. When the teammate is addressed by name in a meeting, MeetCrew calls your agent with the meeting context and speaks the reply it returns.

Connecting your agent

Bind the agent through its Agent Service endpoint. Authentication runs through your Azure subscription credentials; managed identity is preferred where your setup supports it. Your teammate’s identity instructions — name, role, and tone — are injected through the agent’s instruction surface, and MeetCrew’s teammate-side tools, such as memory queries, are registered so your agent can call them during a turn.

Credentials stay in Key Vault

Backend credentials are stored as Azure Key Vault secret references, never as raw secrets. MeetCrew resolves them at invocation time. The teammate runs on Azure with Entra identity and per-tenant isolation, uses no voiceprints, and keeps disclosure on by default.