Skip to main content
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.
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.

​
Choose a path

Microsoft documents these separately as tabs, Communication Services interoperability, and application-hosted media bots.

​
Prepare the review

1

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

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

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

No. Embedding a webpage does not grant access to meeting audio.
No released app package is documented. Use the relevant preparation guide to define the required implementation.