# Microsoft Teams

Use Microsoft Teams to find chats or channels, read messages and threads, search discussions, and send a reviewed update to a selected destination.

## Before you start

Open **Customize → Plugins** and select this plugin. **Add** installs an available package; **Uninstall** means it is already installed. An offered **Update** refreshes its package version. Your deployment and administrator policy determine availability.

When **Add Account** is offered, follow its connection instructions using an authorized account that owns or can access the intended resource. If several accounts are connected, check the selected account and **Default** before the task. **Reconnect** refreshes an expired connection; an administrator setup notice needs administrator configuration.

Enable the plugin for the selected agent or task. On an installed plugin's **Tools** table, check **Enabled** and the **Approval** setting for the operations you intend to use. New tasks use these settings; a pending approval still needs a decision. See [agent setup](/agents/create/) and [action approvals](/threads/approvals/).

![Use Microsoft Teams plugin in Redbelt](/screenshots/current/plugin-microsoft-teams.png)

Plugin details under **Customize → Plugins**. The button shows the current installation state.

## Send a launch status update

1. Ask Redbelt to discover the intended chat, or list channels for a known team.
2. Read recent messages in the selected destination and inspect relevant message references.
3. Draft a concise update using the milestones in those messages.
4. Review the exact target type, chat or team/channel IDs, and message content.
5. Request sending through the enabled send operation, then read the destination to confirm the message.

> List my Teams destinations and ask me which channel or chat to use. Read its recent messages and summarize unresolved milestones. Draft an update using the deadlines stated in those messages. Show me the exact destination and message before sending it.

## Use returned message references

Message search returns references that the read operations can resolve. Batch reading takes message references, not arbitrary browser links. Discovery and pagination determine the coverage of a result; a partial listing is not the whole team's history.

The enabled send tool supports chat and channel destinations with the appropriate target identifiers. Specify which type you intend. A chat ID does not identify a channel, and a channel normally also needs its team context.

Older joined-team, chat-message, channel-message, and separate send entries remain in the catalog but are disabled. Use the enabled unified message tools listed below. If you do not know a team ID, provide the intended team's reference or ask an administrator to help identify it rather than guessing.

## Tool Reference

Thread and workflow availability are listed separately. A tool must also be enabled for your task and allowed by its account and administrator policy. [Configure workflow app actions](/workflows/apps/) using only actions offered by the current picker.

### Available Tools

| Tool                                 | Required Fields               | Thread | Workflow |
| ------------------------------------ | ----------------------------- | ------ | -------- |
| `microsoft_teams.list_chats`         | No mandatory top-level fields | Yes    | No       |
| `microsoft_teams.list_messages`      | No mandatory top-level fields | Yes    | Yes      |
| `microsoft_teams.list_team_channels` | `team_id`                     | Yes    | No       |
| `microsoft_teams.read_message`       | `message_ref`                 | Yes    | No       |
| `microsoft_teams.read_message_batch` | `message_refs`                | Yes    | No       |
| `microsoft_teams.search_messages`    | `query_text`                  | Yes    | Yes      |
| `microsoft_teams.send_message`       | `content`                     | Yes    | Yes      |

Required fields above are the schema minimum. The target, selected operation, or account can impose additional requirements.

**`microsoft_teams.list_chats`** — List chats the user is part of, with each chat's type, topic, and other members, so a direct message can be matched to a person.
Optional fields: `top`.

**`microsoft_teams.list_messages`** — List Teams messages with chat/channel mode selection.
Optional fields: `channel_id`, `chat_id`, `relative_date_range`, `target_type`, `team_id`, `top`.

**`microsoft_teams.list_team_channels`** — List channels in a team.

**`microsoft_teams.read_message`** — Read a full Teams message from a message reference token.

**`microsoft_teams.read_message_batch`** — Read several full Teams messages returned by Teams search or list tools.

**`microsoft_teams.search_messages`** — Search across Teams chat messages.
Optional fields: `channel_id`, `chat_id`, `from_index`, `is_mentioned`, `is_read`, `relative_date_range`, `size`, `target_type`, `team_id`.

**`microsoft_teams.send_message`** — Send Teams messages with chat/channel mode selection.
Optional fields: `channel_id`, `chat_id`, `target_type`, `team_id`.

## Troubleshoot

If a message reference fails, refresh the destination listing or search and use the returned reference. If the target is absent, check account membership and organization permissions.

Provider details: [Microsoft Teams documentation](https://support.microsoft.com/en-us/teams/).
