> ## Documentation Index
> Fetch the complete documentation index at: https://docs.komaa.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Teams setup overview

> What you need to connect your agent to Microsoft Teams: an Azure bot identity, the StandIn app package, and a one-time upload to Teams.

StandIn is **bring-your-own-bot**: your tenant owns the bot identity, StandIn answers its calls, and
your bridge or plugin supplies the agent. The Teams side of the setup is **identical for all seven
open-source packages** - only the agent side differs.

<CardGroup cols={2}>
  <Card title="OpenClaw plugin" href="/openclaw/installation" icon="plug">
    `@komaa/openclaw-msteams-bridge`
  </Card>

  <Card title="Hermes plugin" href="/hermes/installation" icon="plug">
    `hermes-msteams-bridge`
  </Card>

  <Card title="ElevenLabs bridge" href="/elevenlabs/installation" icon="waveform-lines">
    `@komaa/elevenlabs-msteams-bridge`
  </Card>

  <Card title="LiveKit bridge" href="/livekit/installation" icon="video">
    `@komaa/livekit-msteams-bridge`
  </Card>

  <Card title="OpenAI bridge" href="/openai/installation" icon="bolt">
    `@komaa/openai-msteams-bridge`
  </Card>

  <Card title="Deepgram bridge" href="/deepgram/installation" icon="microphone-lines">
    `@komaa/deepgram-msteams-bridge`
  </Card>

  <Card title="Cartesia bridge" href="/cartesia/installation" icon="phone-volume">
    `@komaa/cartesia-msteams-bridge`
  </Card>
</CardGroup>

## What you will create

Three pieces, created once per bot identity:

1. **A Microsoft Entra app registration** - the bot's identity (its client ID becomes your `botId`).
2. **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.
3. **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.

<Note>
  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.
</Note>

## Setup path

<Steps>
  <Step title="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](/teams/azure-bot).
  </Step>

  <Step title="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](/teams/app-package).
  </Step>

  <Step title="Upload it to Teams">
    Upload the package as a custom app, or publish it to your organization. See
    [Upload to Teams and go live](/teams/publish).
  </Step>

  <Step title="Connect your agent and call">
    Register your bridge's **Agent voice URL** and shared secret in StandIn (the
    [quickstart](/quickstart) covers pairing), then place a Teams call to your bot.
  </Step>
</Steps>

<Tip>
  No Azure tenant handy? The [sandbox (community tier)](/community) lets you try StandIn with a
  shared bot in a public meeting - zero Azure setup, no app package needed.
</Tip>