Skip to main content
connic

Microsoft Teams

Let people chat with your connic agents in Microsoft Teams through your own Azure Bot. Agents answer in the conversation or post their results to a channel.

Modes
Inbound, Outbound
Set up in
Dashboard or connectors/*.yaml
Publisher
By connic

Answer chats and mentions

People write to the bot in a chat or mention it in a channel or group chat. Every agent linked to the inbound connector starts, and an outbound connector on the same Connection posts the answer in the conversation.

Chats, mentions or every channel message
Chats with the bot and mentions start runs. Turn on Receive all channel messages to get every message in the channels of a team.
One session per conversation
The conversation ID stays the same within a chat and a channel thread. Use it as the session key, and the agent remembers earlier messages.
Your tenant only, no double runs
Messages from other tenants are ignored, and a message that Teams delivers twice doesn't start a second run.
  1. Someone writes to the bot

    A message in a chat with the bot, or a mention in a channel or group chat.

    mentioned: true
  2. connic confirms it right away

    It checks that the message comes from Microsoft for your bot and answers Teams within the few seconds it allows.

  3. Linked agents start

    The run gets the text without the mention, a conversation ID, the sender, and the team and channel.

    conversation_id
  4. The answer lands in the conversation

    An outbound connector on the same Connection replies in the chat or in the channel thread.

Your own Azure Bot, packaged as a Teams app

connic works with a single-tenant Azure Bot in your Microsoft Entra tenant. It checks the bot's credentials and builds the Teams app package you upload.

Your bot, your tenant
The Microsoft App ID, tenant ID and client secret live in an encrypted Connection. connic signs in as the bot to check them before it saves.
A ready app package
Download the zip with the manifest and icons, then upload it in the Teams admin center or as a custom app in Teams.
Updates in place
A new bot name, App ID or channel message setting gives a new package version. Upload it as an update of the same app.
manifest.json
{
  "version": "1.0.2",
  "name": { "short": "Support Copilot", "full": "Support Copilot" },
  "icons": { "color": "color.png", "outline": "outline.png" },
  "bots": [
    {
      "botId": "<microsoft-app-id>",
      "scopes": ["personal", "team", "groupChat"],
      "supportsFiles": false
    }
  ],
  "authorization": {
    "permissions": {
      "resourceSpecific": [
        {
          "name": "ChannelMessage.Read.Group",
          "type": "Application"
        }
      ]
    }
  }
}

Reply in the conversation or post to a channel

An outbound Teams connector posts the agent's output, whether the run answers a message in Teams or comes from another connector or a schedule.

Routing
A run started from Teams on the same Connection gets its reply in that chat or channel thread. Any other run posts a new message in the connector's default channel.
Text and Markdown
Plain output becomes the message, and Teams renders Markdown. Send after every completed run, give the model a tool to call, or send from middleware.
Rate limits handled
Teams accepts 7 messages per second and 1,800 per hour per bot and conversation. When Teams asks to slow down, connic waits and sends again.
output.json
{
  "text": "**checkout-api 2.14.0**: faster refunds, EUR rounded once."
}
connectors/release-notes.yaml
type: teams
mode: outbound
connection: support-copilot
config:
  channel: "19:7c41e2a9b3d8@thread.tacv2"  # or a channel link
agents:
  - name: release-notes
    outbound: { usage: automatic }

Where Microsoft Teams fits

Pick a setup to see what reaches the agent and what it posts back to Teams.

Employees message the bot in a chat, and the agent answers from your IT guides.

Employee in a chat
Inbound Teams
it-helpdesk
Answer in the chat
teams-payload.json
{
  "text": "How do I connect to the office VPN from home?",
  "conversation_id": "teams:a:1Fz8Kq2Lr5Tw9Xb3Nc7Vd",
  "conversation_type": "personal",
  "mentioned": false,
  "sender": { "id": "29:1Hn4Pq7Rs2Tv", "name": "Jana Weber" },
  "team": null,
  "channel": null
}
output.json
{
  "text": "Open the VPN app, choose **Office** and sign in with your work account."
}

Someone mentions the bot in a channel, and the agent answers in the thread.

Mention in a channel
Inbound Teams
policy-assistant
Reply in the thread
teams-payload.json
{
  "text": "Can I carry unused vacation days into next year?",
  "conversation_id": "teams:19:4f2a9c1e@thread.tacv2;messageid=1794873600000",
  "conversation_type": "channel",
  "mentioned": true,
  "sender": { "id": "29:1Mk8Wd3Fq6Zr", "name": "Lukas Brandt" },
  "team": { "id": "19:8d3e5f7a@thread.tacv2", "name": "People" },
  "channel": { "id": "19:4f2a9c1e@thread.tacv2", "name": "Ask HR" }
}
output.json
{
  "text": "Up to 5 unused days carry over. They expire on March 31."
}

With all channel messages on, every post in a requests channel reaches the agent, which answers in the thread.

Post in a requests channel
Inbound Teams
request-triage
Next steps in the thread
teams-payload.json
{
  "text": "The meeting room screens on floor 3 don't turn on.",
  "conversation_id": "teams:19:b7e1d4c9@thread.tacv2;messageid=1794877200000",
  "conversation_type": "channel",
  "mentioned": false,
  "sender": { "id": "29:1Qs5Lv9Hm2Ct", "name": "Mara Schulz" },
  "team": { "id": "19:c2a6f8e1@thread.tacv2", "name": "Facilities" },
  "channel": { "id": "19:b7e1d4c9@thread.tacv2", "name": "Requests" }
}
output.json
{
  "text": "Thanks, Mara. Facilities checks the floor 3 screens today."
}

Your monitoring reports an error, and the agent posts a summary to the on-call channel.

Error monitoring
Inbound webhook
incident-summary
Post to the on-call channel
alert.json
{
  "service": "checkout-api",
  "error": "Payment provider timeout",
  "first_seen": "2026-11-17T09:12:04Z",
  "events_last_hour": 214
}
output.json
{
  "text": "**checkout-api**: 214 payment timeouts in the last hour, first at 09:12 UTC."
}

Microsoft Teams FAQ

You do. You create a single-tenant Azure Bot in your own Azure tenant, and connic signs in as that bot with its client secret. Microsoft no longer allows new multi-tenant bots, so every organization registers its own.

Only when you turn on Receive all channel messages. Then a team owner consents to the app reading the team's channel messages when adding it. Otherwise the bot gets chats with it and messages that mention it.

Teams expects an answer within seconds, which is often less than an agent needs. connic acknowledges every message right away, and an outbound Teams connector posts the agent's answer in the same conversation when the run is done.

Their messages start nothing. The bot serves only your tenant, and connic ignores messages from any other.

Yes, with type: teams and the name of a Teams Connection. The Connection itself, with its bot, is set up in the dashboard; until then, the deploy fails. Inbound connectors need no config, and outbound connectors take an optional default channel.