Log in

Integrations › Microsoft Copilot

Integration · Coming soon

Microsoft Copilot support is on the way.

MeetCrew will front the Microsoft 365 Copilot you already run as a named, disclosed teammate in Microsoft Teams, Zoom, Webex, and Google Meet meetings. The adapter is in beta today — not yet cleared for production, and it doesn’t support Microsoft Entra service-principal authentication yet, which MeetCrew requires for governed access. That’s the work we’re finishing now.

If your reasoning lives in Microsoft Copilot Studio, that path is fully supported today — same Copilot family, same Microsoft 365 grounding, in production now.

What’s coming

Your Copilot, with a seat in the room.

MeetCrew is the meeting-presence layer, not another agent. When the adapter ships, Microsoft Copilot will supply the reasoning; MeetCrew supplies presence, a voice, memory, and disclosure.

Front the Copilot you run Beta

Bind your tenant Microsoft Copilot as the teammate’s backend. Addressed by name, MeetCrew will call Copilot and speak the reply — grounded in the Microsoft 365 context it already has.

Memory back over MCP

MeetCrew keeps a structured record of every meeting — decisions, open questions, action items — and exposes it to your Copilot over an MCP server, so it can act on what the meeting decided.

Service-principal auth — in progress

MeetCrew governs backend access through a Microsoft Entra service principal. The Copilot adapter doesn’t support that yet — it’s the last piece before we open it for production.

Want Microsoft Copilot support?

Tell us and we’ll let you know the moment the adapter is production-ready. Today, Copilot Studio gives your agent the same seat in the meeting.