Backend binding overview

MeetCrew does not replace your chat agent. It fronts one you already run. Your backend supplies the reasoning and the answers; MeetCrew gives that agent a seat in the meeting, a voice, memory, and disclosure.

Bring your own backend

Each MeetCrew teammate is bound to a backend you choose: a Copilot Studio agent, an Microsoft Foundry Agent Service agent, any OpenAI-compatible endpoint, or a custom webhook. MeetCrew owns meeting presence. Your backend owns the thinking — it decides what to say, how to reason, and which of its own tools to call.

Binding is per deployment

You bind a backend to a specific teammate deployment in the admin console. The backend is one property of that deployment, alongside its name, character, voice, and standing instructions. You can reuse one backend across several teammates, each with its own identity and memory.

How a turn works

When a participant addresses the teammate by name during a meeting, MeetCrew calls your backend with the meeting context, then speaks the reply your backend returns. If the reply is empty, MeetCrew stays silent rather than inventing an answer.

Credentials stay in Key Vault

Backend credentials are never stored as raw secrets. The deployment holds Azure Key Vault secret references, and MeetCrew resolves them at invocation time.

Identity-only mode

A teammate can run identity-only. It has a name, character, and voice, but no backend bound yet. You can add a backend later without recreating the deployment.