Integrations › Microsoft Foundry Agent Service
IntegrationPut your Microsoft Foundry Agent Service agent in your meetings.
MeetCrew fronts an agent hosted in Microsoft Foundry Agent Service (formerly Azure AI Agent Service), part of Microsoft Foundry, as a named, disclosed teammate in Microsoft Teams, Zoom, Webex, and Google Meet meetings. Your agent supplies the reasoning; MeetCrew supplies the presence, the voice, the memory, and the disclosure.
Your Foundry agent, in the meeting.
MeetCrew is the meeting-presence layer around the agent you host in Microsoft Foundry. It calls your agent during the meeting and speaks its reply.
Fronts your hosted agent
Bind your Foundry Agent Service agent by its endpoint. When the teammate is addressed, MeetCrew calls the agent with the meeting context and speaks what it returns.
Memory over MCP
MeetCrew keeps a structured cross-meeting record on an MCP server and API. An agent reads it by signing in as a Microsoft Entra service principal you grant in the console.
Entra-governed, in Azure
MeetCrew calls your agent as a Microsoft Entra service principal you create for it. The call to your agent stays inside Azure, governed by Entra and disclosed.
Bind Microsoft Foundry Agent Service in a few steps.
- On the teammate’s Backend binding step, choose Microsoft Foundry Agent Service and supply the agent’s endpoint.
- Create a Microsoft Entra service principal for MeetCrew to call the agent with, and enter its tenant ID, client ID, and secret in the admin console as one credential.
- The teammate’s standing instructions are passed to the agent on each run, and MeetCrew’s in-meeting tools, such as memory queries, are offered alongside the agent’s own tools.
- Invite the teammate. It joins disclosed and speaks your agent’s reply in the room.
MeetCrew keeps the credential in a dedicated Azure Key Vault and never shows it again.
Send your Foundry agent into a meeting.
Start a pilot and we’ll connect your Azure-hosted agent to a disclosed teammate.