Microsoft Teams

Overview

The Microsoft Teams connector adds a Tessel bot to the teams you choose. Workflows post Adaptive Cards to channels or one-to-one chats, and approval steps wait for a named person to respond. Message triggers come from Microsoft Graph change notifications, delivered as typed events.

Teams use it to approve access requests from Entra ID, to post daily Snowflake summaries to an operations channel and to escalate Zendesk tickets that breach their SLA.

Supported plans

• Microsoft 365 Business Basic, Standard and Premium

• Microsoft 365 E3 and E5, and Office 365 E1 to E5

• Commercial cloud tenants, with GCC on request

How approvals work

Tessel sends an Adaptive Card with Approve and Reject actions. When the approver submits, the Bot Framework sends an invoke activity to Tessel, which checks the user's Entra object ID against the approver list. The card then refreshes in place to show who decided and when.

{
  "type": "Action.Execute",
  "verb": "approve",
  "title": "Approve refund",
  "data": { "runId": "run_8f2c", "step": "refund" }
}

{
  "type": "Action.Execute",
  "verb": "approve",
  "title": "Approve refund",
  "data": { "runId": "run_8f2c", "step": "refund" }
}

{
  "type": "Action.Execute",
  "verb": "approve",
  "title": "Approve refund",
  "data": { "runId": "run_8f2c", "step": "refund" }
}

Subscription renewal

Graph subscriptions for channel messages expire after an hour. Tessel renews them in the background and replays any notification missed during a renewal gap.

Permissions needed

A tenant admin grants consent once. The bot needs application permissions to read channel messages and delegated permissions to post as the app. Tessel never reads chats it was not added to.

• ChannelMessage.Read.All for channel message triggers

• ChannelMessage.Send and Chat.ReadWrite to post and reply

• TeamsAppInstallation.ReadWriteSelfForTeam to install the bot