FruxonDocs

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:

  1. In the Azure Portal, create an Azure Bot resource (Bot Framework).
  2. Note the App (Client) ID and create a Client Secret (App Password).
  3. Add the Microsoft Teams channel to the bot.
  4. Once you have a Fruxon Teams config, point the bot's Messaging endpoint at the webhook URL Fruxon generates for the participant binding.

Setup

  1. Open Integrations and select Microsoft Teams.
  2. Click Add Integration Config.
  3. Give the config a display name (e.g., "Teams — Company Tenant").
  4. Choose App ID + App Password and paste:
    • App (Client) ID from your Azure Bot registration
    • Client Secret you created in Azure
  5. Save the config.

Channels

Teams exposes a single channel descriptor:

ChannelDescription
channelA 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).

Bind participants to a Teams channel under Network → Participants to let your agents send messages and receive replies through Teams.

Triggers

TriggerDescription
teams.message.receivedFires 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.

On this page