> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mithunai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Answer questions in Microsoft Teams

> Ask the bot in a chat or by mention and it replies from your knowledge with sources. Approve AI-employee actions from a card. Beta, on request.

The Microsoft Teams bot answers a question asked in a personal chat with it, or in a channel or group
chat that mentions it, with a reply grounded in your organisation's knowledge and a numbered list of
sources linking to each. When the knowledge you connected does not answer the question, it says
**"I don't know"** rather than guessing. It is the same assistant, knowledge and grounding as every
other channel.

> [!WARNING]
>
> Microsoft Teams is in beta and **access is on request**. It has not yet run against a real Teams
> tenant. Ask us if you would like to be among the first to use it.

## Connect your Teams organisation

1. An owner or admin opens **Integrations → Microsoft Teams**, chooses the assistant that should
   answer, and selects **Connect Microsoft Teams**.
2. Microsoft asks a **Microsoft Entra administrator** of your Teams organisation to consent to the bot
   for the whole organisation. Only an administrator can complete this step.
3. Microsoft sends you back to the console, which connects the Teams organisation Microsoft named --
   never one your browser or anyone else could choose.

Add the bot in Teams as your Teams administrator usually adds apps. Disconnecting from the console
stops it answering at once and unlinks every Teams account linked to it.

## What it can and cannot do

| | |
| - | - |
| **Reads** | A message in a personal chat with it, and a message in a channel or group chat that mentions it. Nothing else in Teams |
| **Writes** | One reply to the message it was asked in |
| **Answers from** | The one assistant chosen for your Teams organisation, and only your organisation's knowledge |
| **Asks as** | Your Teams organisation's connection, not as the person who asked: ask an assistant, and nothing more |
| **Records** | Each question as a conversation labelled *Asked in Teams*, under Conversations and in analytics. Each answer counts against your monthly allowance |

A Microsoft Teams organisation (a Microsoft Entra tenant) can be connected to one MITHUNAI
organisation, and an organisation to one Teams organisation.

## Approve AI-employee actions from Teams

When your deployment has it switched on, an AI employee's action that is waiting for approval can be
posted to Teams as a card with **Allow once**, **Always allow** and **Deny**.

* **Choose where cards go.** An owner or admin whose Teams account is linked types `approvals here`
  to the bot in the conversation that should receive them, and `approvals off` to stop.
* **Link your Teams account once.** Send the bot `link` in a personal chat. It replies with a link
  that works once, for fifteen minutes; open it signed in to the console, check the Teams name it
  shows, and continue. The console shows a six-digit code: send it to the bot in that same personal
  chat within ten minutes. Only then is your Teams account linked -- opening the link alone links
  nothing. You can unlink under **Integrations → Microsoft Teams**. Your Teams account is never
  matched to you by e-mail.
* **A card is decided as you.** Pressing a button decides as the person the Teams account is linked
  to, with that person's own permission to approve, exactly as in the console: the payload you saw,
  two-person rules and expiry all apply. Someone whose Teams account is not linked is told how to
  link, and nothing is decided.
* **Always allow is never offered** for an action that moves money, deletes, publishes or changes
  access, or one that always needs a person. The console refuses it too.

> [!WARNING]
>
> A link needs both sides: the person who opens it, signed in, and the Teams account that asked for
> it, which must send back the code that person was shown. A forwarded link opened by someone else
> links nobody unless the code reaches the Teams account too -- so send the code only from your own
> Teams account, and never give it to anyone.

## When it does not answer

* **No reply at all**: your Teams organisation is not connected, your deployment's operator limited
  the bot to other organisations, or your organisation is suspended.
* **"I can't answer right now"**: your monthly answer allowance is used up, or the assistant could
  not be reached. Try again later, or check **Analytics**.
* **"I don't know"**: the assistant found nothing in your knowledge that answers the question. See
  [Coverage gaps](https://docs.mithunai.com/analyze/coverage-gaps.md) for what to add.

## Security

* Every request from Microsoft is verified before anything in it is read: a token signed with a key
  Microsoft publishes, issued for your deployment's bot, unexpired, and issued for that very
  message. Anything else is refused.
* Replies go only to Microsoft's own Bot Connector, whatever a message says.
* The organisation and assistant always come from the connection, never from the message, so a
  message cannot reach another organisation's knowledge.
* A message is treated as a question and nothing more. Instructions inside it cannot change what the
  assistant may do.
* **Guests in your Teams** -- people from another company in a shared channel or invited as guests --
  are answered as your organisation, because Teams does not say in the message that they are guests.
  Keep that in mind before mentioning the bot in a shared channel.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.