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

# Microsoft Teams

> Choose between a Teams tab, Azure Communication Services, and a Graph media bot when preparing a future integration.

Choose a Teams integration by the interaction you need. Displaying an assistant page, joining a meeting through a custom application, and processing live call media require different platform capabilities.

<Note>
  Threetone does not provide a released Teams app package, Teams media bot, or Azure Communication Services adapter. Use these guides to prepare the implementation and tenant review.
</Note>

## Choose a path

| Need | Preparation guide | Boundary |
| - | - | - |
| Show a web experience inside Teams | [Widget tab](/agents-platform/deploy/telephony/microsoft-teams/widget-tab) | Embedded web content does not receive meeting audio automatically. |
| Build a custom application that interoperates with Teams | [Azure Communication Services](/agents-platform/deploy/telephony/microsoft-teams/azure-communication-services) | Identity model, supported scenarios, and tenant policies determine behavior. |
| Process call or meeting media in an application | [Graph media bot](/agents-platform/deploy/telephony/microsoft-teams/graph-media-bot) | Requires a dedicated application-hosted media service. |

Microsoft documents these separately as [tabs](https://learn.microsoft.com/en-us/microsoftteams/platform/tabs/what-are-tabs), [Communication Services interoperability](https://learn.microsoft.com/en-us/azure/communication-services/concepts/teams-interop), and [application-hosted media bots](https://learn.microsoft.com/en-us/microsoftteams/platform/bots/calls-and-meetings/requirements-considerations-application-hosted-media-bots).

## Prepare the review

<Steps>
  <Step title="Name the user action">Specify whether a user opens a page, joins a meeting, starts a call, or invites a bot. Avoid treating these as one generic connection flow.</Step>
  <Step title="Identify administrative ownership">Record the tenant, application registration owner, required installation or consent decisions, and the application backend owner. Request only permissions justified by the selected design.</Step>
  <Step title="Define release evidence">Require a supported Threetone session interface, a verified Microsoft-side design, identity checks, and clear disconnect behavior. Include a way for the user to recover if the integration is unavailable.</Step>
</Steps>

If a test fails, identify whether the failure is app loading, identity, meeting admission, call control, or media. Each belongs to a different part of the integration.

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Will a Teams tab hear the current meeting?" id="teams-overview-faq-audio">No. Embedding a webpage does not grant access to meeting audio.</Accordion>
  <Accordion title="Can I install a ready-made Threetone Teams app?" id="teams-overview-faq-package">No released app package is documented. Use the relevant preparation guide to define the required implementation.</Accordion>
</AccordionGroup>


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