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 sends your agent what was said to it 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 Direct Line channel; MeetCrew authenticates with the channel secret.

What works differently on Copilot Studio

Two things differ from the other backends today. Your teammate’s standing instructions reach a Copilot Studio agent only through a variable: MeetCrew sets MeetCrewStandingInstructions at the start of each meeting, and you insert it in the agent’s instructions in Copilot Studio (create it as a global variable with “External sources can set value” ticked), so the agent’s own instructions take precedence. And the agent does not receive MeetCrew’s in-meeting tools, so it cannot leave the meeting or turn the camera on or off; it reaches memory a different way, below. Each teammate keeps one conversation with your agent for the length of a meeting, so a follow-up such as “and the second one?” arrives in the same conversation as the question before it; if Direct Line has expired that conversation, MeetCrew starts a new one.

Memory of earlier meetings

A Copilot Studio agent reads its teammate’s memory of earlier meetings (decisions, open questions, action items, statements and topics) through the MeetCrew Memory connector, a custom connector you add to your Power Platform environment. On the teammate’s Configuration tab, under Backend & behavior, the console offers the connector’s files, the setup steps and the teammate’s deployment ID.

The connector signs in as an app you register in your Microsoft Entra directory, with a client secret, and you set the agent’s tool to maker-provided credentials. A Tenant Administrator then grants that app Read only on that teammate, under Agent access (MCP) on the Workspace page. That grant is what keeps teammates apart, so give each teammate its own app and its own Copilot Studio agent. MeetCrew also sets a MeetCrewDeploymentId variable at the start of each meeting, for the agent’s instructions to reference.

Memory is written after a meeting ends, so the agent sees earlier meetings, not the one in progress. A turn that reads memory takes longer than one that does not, and its connector calls use your Copilot Studio capacity.

Credentials and identity

You enter the Direct Line secret once; MeetCrew keeps it in a dedicated Azure Key Vault and never shows it again. The teammate runs on Azure with Entra identity and per-tenant isolation.