> ## 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.

# Receive an activity from Microsoft Teams

> The Azure Bot's messaging endpoint. Called by Microsoft's Bot Connector, never by your code.

This is the address the deployment's Azure Bot is given as its **Messaging endpoint**. Microsoft's
Bot Connector calls it; nothing else can, because every request must carry a Bot Framework token: a
JWT signed with a key the Bot Framework publishes, issued by `https://api.botframework.com` for the
deployment's bot, and unexpired. A request without one is refused with `401` before anything in its
body is read. The token must also have been issued for that very activity -- its channel and its
Bot Connector address -- or the request is refused with `401`.

* A message in a personal chat with the bot, or one that mentions it, from a Teams organisation
  connected to a MITHUNAI organisation is acknowledged at once and answered as a reply a moment
  later, from that organisation's assistant.
* Anything else is acknowledged with `200` and answered by nobody: another kind of activity, a Teams
  organisation nobody connected or the deployment does not allow, an organisation that is suspended,
  a redelivery of an activity already taken, a message a bot wrote, or a Bot Connector address that
  is not Microsoft's.

The organisation is always the one the Teams organisation is connected to. Nothing in the activity
can choose another.

> [!WARNING]
>
> Microsoft Teams in MITHUNAI is in **beta**, access on request. This route answers `404` until your
> deployment's operator registers the Azure Bot, and no Teams organisation can be connected yet, so
> every activity is acknowledged and answered by nobody. It has not yet run against a real tenant.

## Response

Returns `200` with no body.


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