Skip to content
Chatvia Docs
On this page

Workspace

Microsoft Teams

Get in touch: Ahmad Mayahi, creator of Chatvia, Spectra and Shakomako

Connect an Azure bot to your agent. People chat with the bot in Microsoft Teams, in a personal chat, a group chat, or a channel, and your agent answers with the same knowledge, guardrails, history, and message limits as every other channel. The reply streams in live: the bot posts a message right away and keeps updating it as the answer is generated.

For example, an IT team trains an agent on its internal how-to pages. A colleague opens a chat with the bot in Teams and asks "How do I connect to the office VPN?". The answer appears in the chat and fills in as the agent writes it.

Microsoft Teams is available for public agents only. A Teams sender is not signed in to Chatvia, so a protected agent cannot answer there. To make an agent public, open Security → Identity and turn on Make agent public. See Messaging channels for what all channels have in common.

You set up Teams yourself on the agent's Channels page. Nobody needs to touch the Chatvia admin panel.

Before you start

You need:

  • A Microsoft Azure account with permission to create resources (portal.azure.com).
  • About 10 minutes for the one-time Azure setup.

The Azure Bot resource itself is free on the Standard channels (Teams is one of them). You do not need any other Azure service.

Step 1: Create an Azure Bot

In the Azure portal, search for Azure Bot in the Marketplace and click Create.

  • Give the bot a handle and pick (or create) a resource group.
  • For Pricing tier, the free tier is fine.
  • For Type of App, pick Multi Tenant (simplest) or Single Tenant.
  • Leave Creation type on Create new Microsoft App ID.

Click Review + create and wait for the deployment to finish.

Step 2: Copy the App ID and create a client secret

Open the new bot resource and go to its Configuration page.

  • Copy the Microsoft App ID (a GUID).
  • Click Manage Password next to it. This opens the app registration's Certificates & secrets page. Click New client secret and copy the secret Value right away. Azure shows it only once.
  • If you picked Single Tenant, also copy the Directory (tenant) ID from the app registration's Overview page.

Step 3: Connect in Chatvia

In Chatvia, open your agent, click Channels in the left menu, and click Setup on the Microsoft Teams card. Paste the values:

Field Where to find it
Microsoft App ID Azure Bot → Configuration
Client secret App registration → Certificates & secrets (the Value, not the ID)
Tenant ID Only for Single Tenant bots: app registration → Overview

Leave Tenant ID empty for a Multi Tenant bot. Click Connect. Chatvia checks the credentials with Microsoft. The card then shows Connected and the bot's App ID.

Step 4: Point the bot at Chatvia

After connecting, the Microsoft Teams card shows a Messaging endpoint. Copy it, go back to your Azure Bot's Configuration page, paste it into Messaging endpoint, and click Apply.

Step 5: Add the Teams channel

In your Azure Bot, open Channels, pick Microsoft Teams, accept the terms, and click Apply. This is what lets Teams talk to the bot.

Step 6: Test it

Click Open a chat with your bot in Teams on the Chatvia card (or open https://teams.microsoft.com/l/chat/0/0?users=28:<your-app-id> in Teams). Send a message. The bot posts a reply immediately and the text streams in as the agent thinks. The conversation appears in your agent's Chatlog with a Teams badge.

To use the bot in a channel or group chat, add it to the team and @mention it by its name.

Troubleshooting

Problem Likely cause
"Microsoft rejected those credentials." Wrong App ID or secret, or you pasted the secret's ID instead of its Value. For Single Tenant bots: the tenant ID is missing or wrong.
No reply in Teams The messaging endpoint was not saved in Azure, or the Microsoft Teams channel was not added under Channels.
Replies stopped after months The client secret expired (Azure secrets have an end date). Create a new secret and reconnect in Chatvia.
Bot ignores channel messages In channels the bot only answers when it is @mentioned.
Stopped answering after reconnecting Reconnecting creates a new messaging endpoint. Paste the new one into your Azure Bot's Configuration page.
"This assistant isn't available on Microsoft Teams right now." The agent was made protected after connecting. Make it public again on Security → Identity.

How replies behave

  • The reply streams: the bot posts a placeholder right away and edits it in place as the answer is generated.
  • The agent's formatting renders natively in Teams: bold, italic, lists, links, and code blocks. Headings are shown as bold lines.
  • Each personal chat, group chat, or channel thread keeps its own ongoing conversation, so the agent remembers earlier messages in that thread.
  • Only text is answered. Files, images and reactions are ignored.
  • If your agent's guardrails check answers Before showing them, the reply does not stream. It appears all at once after the check.

Good to know

  • Reconnecting changes the messaging endpoint. If you disconnect and connect again, Chatvia makes a new Messaging endpoint. Paste it into your Azure Bot's Configuration page again.
  • Disconnect stops the agent from answering. The Azure Bot stays in Azure. Delete it there if you no longer need it.

Search guides, settings and commands.