Copilot Studio

If your reasoning lives in a Microsoft Copilot Studio agent, MeetCrew fronts it directly. Your agent answers; MeetCrew carries those answers into the meeting. Direct Microsoft 365 Copilot binding is on the way — the adapter is in beta today.

The Microsoft-native path

A published Copilot Studio agent is a first-class backend. You bind it to a teammate deployment in the admin console. During a meeting, when the teammate is addressed by name, MeetCrew calls your agent with the meeting context and speaks the reply it returns.

Connecting a tenant Microsoft Copilot — coming soon

Direct Microsoft 365 Copilot binding is in beta and not yet available for production: the adapter doesn’t support Microsoft Entra service-principal authentication yet, which MeetCrew requires for governed access. Until it ships, front a Copilot Studio agent for the same Microsoft-native path — we’ll note here the moment it’s production-ready.

Connecting a Copilot Studio agent

Bind your Copilot Studio agent through its endpoint, authenticated with the agent’s configured authentication. Your teammate’s identity instructions — name, role, and tone — are injected through the agent’s instructions surface, and MeetCrew’s tools are surfaced to the agent as topics.

Credentials and identity

Backend credentials are stored as Azure Key Vault secret references, never as raw secrets. The teammate runs on Azure with Entra identity and per-tenant isolation.