Getting Started

This walks you from nothing to a working Teams voice call with your OpenClaw agent.

Two ways to connect

Pick one before you start - they differ in who owns the Teams bot, and that decides how much Azure work you do.

	StandIn Managed Bot	Bring your own Azure bot
Who owns the bot	StandIn	You
Azure app registration	none	you create it
Teams channel in OpenClaw	not needed	required
What you paste here	one secret	the same secret + your bot’s app id, password and tenant id
Chat relay	included, same secret	your own Teams channel

Managed Bot is the short path. Install StandIn from the Teams Store, connect this agent in the portal, and paste the one secret it gives you:

{
  "plugins": {
    "entries": {
      "msteams-bridge": {
        "config": {
          "enabled": true,
          // Covers BOTH lanes: calling and messages.
          "secret": "paste-the-value-from-the-StandIn-portal"
        }
      }
    }
  }
}

Then register the two endpoints on your StandIn connection - Agent calling URL (wss://<host>/msteams/calling) and Agent messages URL (https://<host>/msteams/messages) - and skip the Teams-channel prerequisite below. The rest of this page is the BYO path.

Prerequisites

• An OpenClaw install, host >= 2026.6.10. Follow docs.openclaw.ai.
• Microsoft Teams set up as an OpenClaw channel (the chat channel). This plugin adds voice/video on top of it. See the OpenClaw Teams channel docs.
• A StandIn connection. The sandbox is free and needs no Teams bot of your own - perfect for a first call. See Connecting to StandIn.
• For realtime mode, a realtime voice provider key (OpenAI or Azure OpenAI). For streaming mode, your OpenClaw-configured STT/TTS/agent is enough.

1. Install the plugin

The one-line installer detects your OpenClaw install and walks you through the config (mode, shared secret, provider key), then prints next steps:

curl -fsSL https://standin.komaa.com/install.sh | bash

Prefer to do it by hand?

openclaw plugins install npm:@komaa/openclaw-msteams-bridge
openclaw gateway restart

It is also on ClawHub: openclaw plugins install clawhub:@komaa/msteams-bridge (OpenClaw falls back to npm automatically). The package ships prebuilt (v0.1.10+) - no build step either way.

2. Try it on the StandIn sandbox

The sandbox is the fastest path to a first call and needs no Azure/Teams bot of your own:

1. Open standin.komaa.com/sandbox and follow it to generate a Teams meeting link. It gives you a shared secret for the session.
2. Put that secret in your plugin config as secret (below).
3. Join the meeting yourself; the shared StandIn bot joins and connects to your plugin.

Tip

The sandbox is time-limited (about 5 minutes/day per session) - enough to see it end to end. When the limit is reached, the agent speaks a short goodbye and the call ends gracefully.

3. Minimal configuration

Config lives under plugins.entries."msteams-bridge".config. A minimal realtime setup:

{
  "plugins": {
    "entries": {
      "msteams-bridge": {
        "config": {
          "enabled": true,
          "mode": "realtime",
          "bindAddress": "0.0.0.0",          // so the hosted bridge can reach the plugin
          "port": 9442,
          "secret": "<the secret from StandIn>",
          "inboundPolicy": "open",           // first-call testing; lock down after (see below)
          "realtime": {
            "provider": "openai",
            "providers": { "openai": { "apiKey": "<key>", "model": "gpt-realtime" } }
          }
        }
      }
    }
  }
}

• bindAddress: "0.0.0.0" lets the hosted bridge connect (the default 127.0.0.1 only accepts local connections).
• secret must match the value StandIn uses, or the handshake is rejected.
• inboundPolicy must be set to receive calls at all: when it is unset, every inbound call is denied. open is fine for the first sandbox call.
• Leave mode out to auto-select: realtime if a provider resolves, otherwise streaming.

Lock down after the first call

inboundPolicy: "open" accepts any caller. Once the sandbox call works, switch to "inboundPolicy": "allowlist" and put the allowed callers’ AAD object ids in allowFrom. See Connecting to StandIn.

See the full Configuration Reference for every option, and Realtime & Streaming Modes for provider setup.

4. Restart and call

Restart the gateway so the config takes effect:

openclaw gateway restart

Then place (or join) the Teams call. You should hear the agent, see its avatar, and - if you turn on your camera or share your screen - it can see you too.