Microsoft Teams

{/* Generated by scripts/generate-integration-catalog.mjs. Do not edit by hand. */}

At a glance

  • Availability: Enabled by default.
  • Authentication: OAuth 2.0.
  • Connection: A user authorizes the connection in the provider's consent screen.
  • Scopes: Chat.Read, Chat.ReadWrite, ChannelMessage.Send, Channel.ReadBasic.All, Team.ReadBasic.All, offline_access.

Credentials

Set these per environment. See Connect an integration.

These variables are required only when you supply your own OAuth app. If a managed app is available, you can connect without setting them. Provider permissions and consent still apply.

VariableRequiredDescription
MICROSOFT_CLIENT_IDYesMicrosoft Azure App Client ID (Application ID) Docs.
MICROSOFT_CLIENT_SECRETYesMicrosoft Azure App Client Secret Docs.

Setup

  1. Choose who owns the Microsoft OAuth app: On hosted Veryfront, Microsoft Teams uses the Veryfront-managed Microsoft OAuth app: connect Microsoft Teams from the project's integrations and approve the Microsoft consent screen, no environment variables needed. Set MICROSOFT_CLIENT_ID and MICROSOFT_CLIENT_SECRET only to use your own Microsoft OAuth app, which is required for local and self-hosted runs.
  2. Register an app in Microsoft Entra: In the Microsoft Entra admin center, open App registrations and register a new application. For Supported account types, choose accounts in any organizational directory. Teams needs a work or school account.
  3. Add the redirect URIs: Under Authentication, add a Web platform. Add the redirect URI of the environment that completes the flow: https://api.veryfront.com/oauth/callback/teams for hosted Veryfront, or your app origin followed by /api/auth/teams/callback for a local or self-hosted app.
  4. Add Microsoft Graph permissions: Under API permissions, add these delegated Microsoft Graph permissions: Chat.Read, Chat.ReadWrite, ChannelMessage.Send, Channel.ReadBasic.All, Team.ReadBasic.All, offline_access. If your tenant does not let users consent to apps, an administrator must grant consent for the organization.
  5. Create a client secret: Under Certificates & secrets, create a client secret. Set MICROSOFT_CLIENT_ID and MICROSOFT_CLIENT_SECRET from the app's credentials. Client secrets expire, so rotate MICROSOFT_CLIENT_SECRET before the expiry date you choose.
  6. Verify access: Run List Teams (read-only). It returns the teams the connected user belongs to without changing them.

Provider notes

  • The connection requests Chat.Read, Chat.ReadWrite, ChannelMessage.Send, Channel.ReadBasic.All, Team.ReadBasic.All and offline_access. offline_access lets the connection refresh its access token.
  • Tools that create, update, send or delete data are marked as writes and need write authority; the other tools are read-only.

Provider API reference.

Tools

ToolAccessDescription
List Chats<br /><code className="reference-identifier">teams__list_chats</code>ReadList chats
Get Messages<br /><code className="reference-identifier">teams__get_messages</code>ReadGet messages
Send Channel Message<br /><code className="reference-identifier">teams__send_message</code>WriteSend channel message
Send Chat Message<br /><code className="reference-identifier">teams__send_chat_message</code>WriteSend chat message
List Teams<br /><code className="reference-identifier">teams__list_teams</code>ReadList joined teams
List Channels<br /><code className="reference-identifier">teams__list_channels</code>ReadList channels
Create Chat<br /><code className="reference-identifier">teams__create_chat</code>WriteCreate chat

Verify the connection

Call a read tool such as teams__list_chats with arguments for your account. Confirm that the result comes from the intended account or workspace before enabling write tools.