channels: {
  msteams: {
    enabled: true,
    accounts: {
      forge: {
        appId: "...",
        appPassword: "...",
        tenantId: "...",
        webhook: { port: 3978, path: "/api/messages/forge" },
        dmPolicy: "allowlist",
        allowFrom: ["<aad-object-id>"]
      },
      boardkeeper: {
        appId: "...",
        appPassword: "...",
        tenantId: "...",
        webhook: { port: 3978, path: "/api/messages/boardkeeper" },
        dmPolicy: "allowlist",
        allowFrom: ["<aad-object-id>"]
      }
    }
  }
}


### Alternatives considered


**Alternatives considered**
```md
Run one OpenClaw gateway instance per Teams bot/app.

This works in theory, but it is heavier operationally: each Teams-facing agent needs its own gateway process, webhook port/path, reverse proxy rule, service config, health checks, secrets, and deployment lifecycle.

Use one Teams bot/app as a shared hub and route by conversation.

This is simpler at the infrastructure layer, but weaker when each agent should appear as a distinct Teams app/bot identity. It also makes permissions, install flow, branding, and deterministic agent routing less clear.

Manually swap the single `channels.msteams` config between apps.

This is only useful for testing. It cannot support multiple live Teams agents at the same time.


### Impact

Affected users/systems/channels:
- Teams users who want multiple OpenClaw agents exposed as separate Teams apps/bots
- Deployments that already use multiple Discord accounts/agents and want parity on Teams
- Single-gateway OpenClaw deployments with several agent personas

Severity:
- Blocks the intended Teams hub workflow when multiple agents need separate Teams identities.

Frequency:
- Always, for any deployment that needs more than one Teams bot/app connected to one gateway.

Consequence:
- Requires extra gateway instances or config swapping.
- Adds reverse proxy, service, port, secret, and deployment overhead.
- Makes Teams less ergonomic than Discord for multi-agent OpenClaw setups.


### Evidence/examples

Current Discord setup supports multiple accounts and bindings:

```text
main <- discord accountId=forge
boardkeeper <- discord accountId=boardkeeper
crm <- discord accountId=crm
radar <- discord accountId=radar


### Additional information

This should remain backward-compatible with the current single-account Teams config.

A migration path could treat existing `channels.msteams.appId/appPassword/tenantId/webhook` as the implicit `default` account, while allowing new deployments to opt into `channels.msteams.accounts`.