Microsoft Teams

​

Example use cases

• “@Releaser time to cut a new release” — triggers your deployment agent directly in a channel
• “@Researcher summarise everything we know about Acme Corp” — kicks off a research agent from Teams
• “@Standup post a daily standup summary to the Engineering channel every morning”

​

Prerequisites

• Access to the Teams Developer Portal at dev.teams.microsoft.com
• Microsoft Entra admin center access (to copy the app registration’s IDs)
• Microsoft Teams Admin Center access (Teams administrator role)
• The Abundly agent you want to connect

​

How to connect

{
  "$schema": "https://developer.microsoft.com/en-us/json-schemas/teams/v1.29/MicrosoftTeams.schema.json",
  "version": "1.0.0",
  "manifestVersion": "1.29",
  "id": "YOUR-TEAMS-APP-GUID",
  "name": {
    "short": "YOUR-AGENT-NAME",
    "full": "YOUR-AGENT-NAME"
  },
  "developer": {
    "name": "YOUR-COMPANY-NAME",
    "websiteUrl": "https://your-company.com",
    "privacyUrl": "https://your-company.com/privacy",
    "termsOfUseUrl": "https://your-company.com/terms"
  },
  "description": {
    "short": "Abundly agent bot",
    "full": "Abundly agent bot for Microsoft Teams"
  },
  "icons": {
    "outline": "outline.png",
    "color": "color.png"
  },
  "accentColor": "#ffffff",
  "supportsChannelFeatures": "tier1",
  "bots": [
    {
      "botId": "YOUR-BOT-ID-GUID",
      "scopes": ["personal", "team", "groupChat"],
      "isNotificationOnly": false,
      "supportsFiles": false,
      "supportsTargetedMessages": true,
      "commandLists": [
        {
          "scopes": ["personal", "groupChat"],
          "triggers": ["slash", "mention"],
          "commands": [
            {
              "title": "compact",
              "description": "Start a new chat that begins with a summary of this one"
            }
          ]
        }
      ]
    }
  ],
  "webApplicationInfo": {
    "id": "YOUR-BOT-ID-GUID",
    "resource": "api://botid-YOUR-BOT-ID-GUID"
  },
  "authorization": {
    "permissions": {
      "resourceSpecific": [
        { "type": "Application", "name": "ChannelMessage.Read.Group" },
        { "type": "Application", "name": "ChatMessage.Read.Chat" },
        { "type": "Application", "name": "ChannelSettings.Read.Group" },
        { "type": "Application", "name": "ChannelMember.Read.Group" }
      ]
    }
  },
  "validDomains": []
}

​

How conversations work

• Channel @mentions start a new chat — the agent replies in the thread with full context.
• Follow-up replies in a thread the agent already joined continue the same chat without needing to @mention again.
• Group chats map to persistent chats — every message reaches the agent directly.
• 1:1 personal chats (DMs) also map to persistent chats — the agent replies naturally.
• In 1:1 chats, the agent’s reply streams in as it is written, with short status updates while it works.
• The agent reacts with 👀 to a message while it is working on it and removes the reaction when it has answered.
• Replies carry Teams’ “AI generated” label.
• In 1:1 and group chats, type /compact (or ask the agent to start fresh) to begin a new chat that starts with a summary of the current one. It takes a minute or two, and messages sent meanwhile are not answered. The previous chat stays readable in the portal. In a 1:1 chat the command is also listed under View prompts above the compose box; in group chats it appears in the / menu once you type /.
• You can tell an agent to leave a channel thread — say it’s no longer needed and it steps out, so it stops being woken by every following message. It says so in the thread before going quiet, and an @mention brings it straight back, caught up on what it missed. Agents are told not to leave on their own initiative: if one thinks it’s done, it asks or says so first. Group chats and personal chats can’t be left, so an agent is always reachable there.

​

Private and shared channels

1. Make sure the app is installed in the channel’s host team (step 6 above).
2. Open the private or shared channel and add the app to it — a channel member does this from the channel’s app management (for example ⋯ → Manage channel → Apps, or by choosing the channel when adding the app).
3. The channel-level add grants the app’s RSC permissions for that channel only.

​

Optional: tenant-wide Graph permissions

​

Updating an existing install

1. Bump the manifest version in the Teams Developer Portal (e.g. 1.0.0 → 1.0.1) and re-publish the app to your org
2. In each team that has the bot installed: Manage team → Apps → trash icon next to the bot → Remove
3. Re-add the bot following step 6 above

​

Things to know

​

Troubleshooting