Skip to content
Verbatik

Integrations

Microsoft Teams

Connect Microsoft Teams, obtain the required access and configure permitted actions.

The API adapter is implemented. Validate your own account and authorized actions before routing production calls.

Before you start

Connect the account belonging to this business and workspace. Vendor subscriptions, API limits and role permissions still apply.

API: Microsoft Graph v1.0 Teams channel messages

Authentication: Delegated Microsoft work/school OAuth access token

Get access and connect

  1. Register an Entra application and add delegated Microsoft Graph User.Read and ChannelMessage.Send permissions.
  2. Use the application's authorization-code flow with offline_access to authorize a work/school user who can access the channel; copy the delegated access token into the connection.
  3. For automatic token renewal, add the delegated refresh token, application client ID and tenant ID, plus a client secret for confidential web clients. Rotated refresh tokens are saved encrypted.
  4. Obtain the Team ID and channel ID from a Teams channel link or Microsoft Graph and enter both settings.
  5. Test the identity, enable changes, and attach the call summary action. Without a refresh token, renew the supplied access token manually when it expires.

Account requirements

  • A Microsoft 365 work/school tenant, Teams membership and any tenant-required admin consent.
  • Application-only normal channel message posting is unsupported; old Office 365 connector webhooks are retired.

Permissions

  • User.Read
  • ChannelMessage.Send
  • offline_access (for renewal)

Grant the subset needed for the actions you enable. API scopes do not override the connected user’s record permissions or vendor validation rules.

Connection fields

  • accessToken — Delegated Microsoft Graph access token (required). Secret fields are saved as workspace credentials.
  • refreshToken — Delegated refresh token (optional) (optional). Secret fields are saved as workspace credentials.
  • clientId — Entra application client ID (for token renewal) (optional). Secret fields are saved as workspace credentials.
  • clientSecret — Entra application client secret (for confidential clients) (optional). Secret fields are saved as workspace credentials.
  • teamId — Team ID (required).
  • channelId — Channel ID (required).
  • tenantId — Entra tenant ID (for token renewal) (optional).

Available actions

  • test_connection — Read. Read the delegated Microsoft Graph user identity. Channel posting also needs ChannelMessage.Send permission.
  • send_call_outcome — Write · available for after-call automation. Post a completed call summary to the configured Teams channel as the delegated user. Only include information the channel's members may see.

Verify before going live

Run Test connection and one read action against a known permitted record. Then test each intended write in an authorized sandbox. Check the provider’s own record and the Verbatik receipt. Publish the agent after assigning its tools. If a write has an unknown outcome, reconcile it with the vendor before trying again.

Vendor documentation

Verbatik documentation · Updated November 5, 2026