OpenClaw plugin
@komaa/openclaw-msteams-bridgeHermes plugin
hermes-msteams-bridgeElevenLabs bridge
@komaa/elevenlabs-msteams-bridgeLiveKit bridge
@komaa/livekit-msteams-bridgeOpenAI bridge
@komaa/openai-msteams-bridgeDeepgram bridge
@komaa/deepgram-msteams-bridgeCartesia bridge
@komaa/cartesia-msteams-bridgeWhat you will create
Three pieces, created once per bot identity:- A Microsoft Entra app registration - the bot’s identity (its client ID becomes your
botId). - An Azure Bot resource with the Microsoft Teams channel enabled - this is where you point Teams at StandIn’s calling webhook and (optionally) messaging endpoint.
- A Teams app package - a small zip (manifest + icons) that makes the bot callable in your tenant. You do not hand-build it: your StandIn dashboard generates it per identity, ready to upload.
You need rights to create resources in an Azure subscription, and a Teams / Entra admin
(or someone who can act for you) to grant admin consent and allow the custom app. Budget
20-30 minutes for the first run-through.
Setup path
Create the bot identity in Azure
Register the Entra app, create the Azure Bot resource, enable the Teams channel with calling,
and grant the Graph permissions. Follow Create the Azure bot.
Download the Teams app package
Grab the generated zip from your StandIn dashboard (or build it from the example manifest).
See Get the Teams app package.
Upload it to Teams
Upload the package as a custom app, or publish it to your organization. See
Upload to Teams and go live.
Connect your agent and call
Register your bridge’s Agent voice URL and shared secret in StandIn (the
quickstart covers pairing), then place a Teams call to your bot.