> ## 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. # Connection modes > Two ways to put your agent in Microsoft Teams: the StandIn AI Teammate app from the Microsoft Teams Store, or your own Azure bot. There are two ways to connect an agent to Microsoft Teams. They differ in **who owns the Microsoft Teams bot**, and that single difference decides how much Azure work you do. | | StandIn AI Teammate app | Bring your own Azure bot | | - | - | - | | Who owns the bot | StandIn | You | | Azure app registration | none | you create it | | App ID / client secret | none | you manage them | | Install | add **StandIn AI Teammate** from the [Microsoft Teams Store](https://teams.microsoft.com/l/app/efcbbdea-3d93-47f7-b106-f2c33126d0b5) | upload your own app package | | Identity in Microsoft Teams | appears as StandIn | appears as your own bot | | Best for | getting working quickly | full identity custody | Both modes connect **your own agent**: StandIn is the bridge, never the brain. And both need the same one-time admin consent before calling works - chat works without it. ## StandIn AI Teammate app StandIn publishes and operates one Microsoft Teams bot; your Microsoft organization is routed to your agent by a connection you create in the StandIn portal. 1. In Microsoft Teams, add **StandIn AI Teammate** from the Store: [open it in Microsoft Teams](https://teams.microsoft.com/l/app/efcbbdea-3d93-47f7-b106-f2c33126d0b5), or find it in [Microsoft Marketplace](https://marketplace.microsoft.com/en-us/product/office/WA200012046). 2. Type `signin` to the bot and sign in with your StandIn account. That link is how StandIn learns which Microsoft organization to connect - you do not type a tenant id anywhere. 3. In the StandIn portal, deploy an identity and choose **Use the StandIn AI Teammate app**. Paste your agent's address; the portal gives you back the secrets. 4. A Microsoft 365 administrator approves calling once for the organization. Chat works before this; calling switches on when the approval lands. You get a **connection secret**, and on this SDK it is one environment variable: ```bash theme={null} export STANDIN_SECRET='' ``` A StandIn AI Teammate app connection may issue a **second key for chat**. That is deliberate, not an oversight: each lane signs its own handshake, so two keys mean a key that can open one lane cannot open the other. If you are given one, export it as `STANDIN_CHAT_SECRET` and the chat lane signs with that instead. `ChatChannel` reads `STANDIN_CHAT_SECRET` first and falls back to `STANDIN_SECRET`, so when a single key covers both lanes there is nothing extra to set. The StandIn AI Teammate app is also what unlocks the SDK's chat lane. `ChatChannel` dials **out** to StandIn with whichever of those two keys it found, so chat needs no URL registered, no open port and no tunnel rule, and your agent never holds a Bot Framework credential. It needs no flag either: if the socket opens, you are on the StandIn AI Teammate app. One agent instance serves **one** connection. The secrets belong to a single Microsoft organization - run a second instance for a second organization, and never share a secret across tenants. ## Bring your own Azure bot You register a Microsoft Entra app, create an Azure Bot resource, and upload your own Microsoft Teams app package. The bot carries your name and lives entirely in your tenant. Follow [Azure bot setup](/teams/azure-bot) and [App package](/teams/app-package). This is the right choice when identity custody matters more than setup time, or when you need the bot to be visibly yours. ## Endpoints StandIn dials your worker, so the URL you save in the portal has to match the path the worker listens on. Give the portal a bare host and it fills in the default below; paste a full URL if the worker uses a different path. **Calling is the same in both modes.** Only chat differs: | Lane | Public contract | Auth | What you expose | | - | - | - | - | | Calling, both modes | WebSocket `wss://host/msteams/calling/{callId}` | HMAC handshake with `STANDIN_SECRET` | the call listener (`STANDIN_PORT` / `STANDIN_WS_PATH`, defaults `9442` and `/msteams/calling`) | | Chat, **StandIn AI Teammate app** | the worker dials `STANDIN_CHAT_URL` (default `wss://teams.standin.komaa.com/api/chat/channel`) | HMAC with `STANDIN_CHAT_SECRET`, else `STANDIN_SECRET` | nothing inbound | | Chat, **bring your own Azure bot** | the messaging URL on your Azure Bot | your Azure Bot credentials, not this SDK | not this SDK; the portal shows the value to register | A bring-your-own-bot identity answers Microsoft Teams chat on that Azure Bot messaging URL, not through `ChatChannel`. Calls still use the calling row. Take the URL the portal offers when you deploy the identity. The mount commands that publish the call path, what a healthy probe looks like, and the `--http1.1` gotcha that makes a working mount look broken. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.