Microsoft Teams
Microsoft Teams (Bot Framework) integration for sending and receiving Teams messages via your Azure bot
The Microsoft Teams integration lets your agents send and receive messages in Teams — direct chats, group chats, and channels the bot has been added to. It's a credentials container that powers the participant dispatcher; no agent-facing tools are exposed yet.
Prerequisites
You need an Azure Bot registration:
- In the Azure Portal, create an Azure Bot resource (Bot Framework).
- Note the App (Client) ID and create a Client Secret (App Password).
- Add the Microsoft Teams channel to the bot.
- Once you have a Fruxon Teams config, point the bot's Messaging endpoint at the webhook URL Fruxon generates for the participant binding.
Setup
- Open Integrations and select Microsoft Teams.
- Click Add Integration Config.
- Give the config a display name (e.g., "Teams — Company Tenant").
- Choose App ID + App Password and paste:
- App (Client) ID from your Azure Bot registration
- Client Secret you created in Azure
- Save the config.
Channels
Teams exposes a single channel descriptor:
| Channel | Description |
|---|---|
channel | A Teams conversation — a channel inside a team, a group chat, or a 1:1 chat. Identified by a Bot Framework conversation ID (e.g. 19:abc123…@thread.tacv2). |
To let your agents send messages and receive replies through Teams, give the person or group a Teams address (the conversation ID) in the Directory — on Add person or Add group, or later with Edit on their Identity & reach tab. For an Application's agents to serve them, add them under that Application's People.
Triggers
| Trigger | Description |
|---|---|
teams.message.received | Fires when a Teams user sends a message the bot can see — direct chats, group chats, or any channel the bot has been added to. |
The trigger payload includes the standard inbound-message fields (payload.text, payload.from, payload.from_name, payload.conversation_name, payload.conversation_address, payload.session_id, payload.event_type) plus a Teams-specific payload.message_attributes.conversation_id containing the Bot Framework conversation id.
Available Tools
No tools yet. This integration currently exists as a credentials container for the outbound message dispatcher. Tool support (send message, list channels, etc.) will land in a follow-up.