Microsoft Teams

This is a shipped config-backed outbound surface. Microsoft teams incoming webhook surface is outbound-only today

At A Glance

Field	Value
Catalog id	`teams`
Config key	`teams`
Implementation status	`config_backed`
Transport	`microsoft_teams_incoming_webhook`
Aliases	`msteams`, `ms-teams`
Default send target kind	`endpoint`, `conversation`

[teams]
enabled = true
webhook_url_env = "TEAMS_WEBHOOK_URL"

loong channels send teams --text "hello from loong"

Operation	Command	Usage or status
incoming webhook send	`channels send teams`	Usage: loong channels send teams [OPTIONS] —text <TEXT>
bot event service	`channels serve teams`	microsoft teams incoming webhook surface is outbound-only today

Requirement	Config paths	Env pointer paths	Default env
channel enabled	`teams.enabled` `teams.accounts.<account>.enabled`	none	none
incoming webhook url	`teams.webhook_url` `teams.accounts.<account>.webhook_url`	`teams.webhook_url_env` `teams.accounts.<account>.webhook_url_env`	`TEAMS_WEBHOOK_URL`

This surface is a direct-send delivery lane. It does not join gateway run or the gateway-owned reply-loop contract today.

Microsoft Teams is the incoming webhook send surface today. Bot-runtime fields remain reserved for a planned serve path and should not be documented as shipped support.