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

# Microsoft Teams

> Your assistant acts in Teams as its own connected Microsoft account

When you connect a **Microsoft 365** account for your assistant, it can work in
Microsoft Teams as *that account* — chatting, posting in channels, and hosting
meetings under its own Microsoft identity, the same way it works in the
[connected mailbox](/workspace/email).

This is the account-bound path. It's set up per assistant as part of the
[workspace connection](/workspace/connecting): pick **Microsoft 365** and the
**Teams** feature is included, so Teams is enabled the moment the account is
linked. It's distinct from the org-wide [Unify Teams app](/communication/microsoft-teams),
where the assistant appears as a shared bot rather than as a Microsoft user.

## Messaging

* **1:1 chat** — message your assistant in Teams like any colleague, and it
  replies as its connected account.
* **Group chats** — it can take part in group conversations with two or more
  people, and can start them too.
* **Channels** — @mention your assistant in a channel and it replies in the
  thread; it can also post to channels and even create new ones.
* **Attachments** — it can send files in Teams messages.

## Hosting meetings

Because it acts as a real Microsoft account, your assistant can **create**
Teams meetings, not just attend them:

* **Instant links** — "create a meeting link for me and Sam" gets you a
  ready-to-share Teams link on the spot.
* **Scheduled meetings** — it can put a Teams meeting on the calendar with a
  link and send invites to all attendees.

Joining a meeting is separate and doesn't require this connection — send any
Teams meeting link and your assistant joins with its voice. See
[Meetings](/workspace/meetings).

## Whose name is on it?

Just like [email](/workspace/email#whose-name-is-on-the-email), it depends on
the account you connected — see [whose account gets
connected](/workspace/overview#whose-account-gets-connected):

* **T-W1N** is connected to *your* account, so it chats and hosts meetings
  **as you** — your digital twin acting in your name.
* **A hired assistant** has its own dedicated account, so it shows up as
  **itself** — a named team member with its own Teams presence.

<Note>
  If you'd rather everyone in the org reach your assistants through one shared
  bot — including people who never see the assistant's Microsoft account — use
  the org-installed [Unify Teams app](/communication/microsoft-teams) instead.
  You can use either path, or both.
</Note>