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. MeetCrew authenticates as a Microsoft Entra service principal you create for the purpose; you enter its tenant ID, client ID, and client secret together in the admin console as one credential. Your teammate’s standing instructions are passed to the agent as additional instructions on each run. Each run also offers MeetCrew’s in-meeting tools, such as memory queries, as function tools, and the agent keeps its own tools alongside them. When the agent calls a MeetCrew tool, MeetCrew runs it and submits the result back to the run, once per question. MeetCrew cannot run the agent’s own client-side functions, so a run that asks only for those is treated as a failed turn.

Credentials are write-only

MeetCrew keeps the credential in a dedicated Azure Key Vault and never shows it again. The teammate runs on Azure with Entra identity and per-tenant isolation, uses no voiceprints, and keeps disclosure on by default.