realvco Docs

Microsoft Teams setup

Microsoft Teams is the standard for enterprise internal collaboration. Hermes v0.12 ships native Teams support (via the new plugin mechanism), letting Vi join your company’s Teams workspace as an internal AI assistant.

Teams integration is Hermes-Agent only (Ada / Vi both come with Hermes-Agent and can connect to Teams). Rose (OpenClaw) cannot connect to Teams.

Flow Overview

① Microsoft 365 admin creates a Bot app                ← ~10 minutes
② Get three credentials from Azure / Teams Dev Portal  ← instant
③ Paste credentials into admin panel                   ← 30 seconds
④ Install the Bot to your Teams workspace              ← 1 minute
⑤ DM the Bot in Teams to start chatting                ← done!

Pre-requisites

You need:

  • Microsoft 365 admin rights (regular employees can’t register Bots)
  • Access to Teams Developer Portal or Azure Bot Service
  • realvco admin panel login
  • Vi (hm-3 container, Hermes v0.12 or later) on your host

Why admin rights are required: Teams Bots must be registered as an application under your company’s tenant — that’s a one-time IT action and a regular M365 account doesn’t have permission.

If you’re not the IT admin, forward this page to whoever is. Once they have the three credentials, hand them to you and you can finish the rest.

Step 1: Create a Bot in Teams Developer Portal

Go to Teams Developer Portal and sign in with your M365 admin account.

  1. Left sidebar Apps → + New app
  2. Name it realvco-vi-assistant (or whatever you like)
  3. Inside the app, Configure → Basic information:
    • Short name: the user-facing name (e.g. “Vi Assistant”)
    • Full name: full label
    • App ID: auto-generated, save this
  4. Switch to App features → Bot → Create new bot
  5. The system will create a Bot and route you to Azure Bot Service

In Azure Bot Service, record three values:

ValueWhere
App ID (Microsoft App ID)Bot detail page → Configuration
App Password (Client Secret)Click “Manage Microsoft App” → Certificates & secrets → New client secret. Shown only once — copy immediately.
Tenant IDAzure Portal → Microsoft Entra ID → Overview

App Password is shown only once. Save it somewhere safe right after generation. If you lose it, you’ll have to generate a new one.

Step 2: Configure in admin panel

hm-3 Settings sub-tab — full panel where Microsoft Teams is configured hm-3 Settings sub-tab — full panel where Microsoft Teams is configured
Paste the Microsoft Teams App ID / App Password / Tenant ID into the Messaging section of this hm-3 settings panel
  1. Sign in to admin panel
  2. Switch to the hm-3 (Vi) container
  3. Settings → Messaging → Microsoft Teams
  4. Paste in:
    • App ID
    • App Password
    • Tenant ID
  5. Click Save

The admin panel validates the credentials live. On success you’ll see:

  • ✅ Bot Display Name
  • ✅ Connection Status: Connected
  • ✅ Tenant authentication passed

Common failure modes:

  • App Password has expired or been revoked
  • Tenant ID typo (should be a GUID)
  • The Azure Bot’s Messaging endpoint hasn’t been opened (the v0.12 plugin handles this automatically, but if Azure has it manually locked, unlock it)

Step 3: Install the Bot to your Teams workspace

Back in Teams Developer Portal, find the app you just created:

  1. Publish → Publish to org (publish to your company tenant)
  2. Wait for the Teams admin to approve (if you’re the admin, you can self-approve)
  3. After approval, search the app name in the Teams app store and install

Faster shortcut: in Teams Developer Portal click Preview in Teams → install in your own Teams for testing immediately.

Step 4: Start chatting

In Teams, left sidebar Chat → search the Bot name (e.g. “Vi Assistant”) → click to start a private chat.

Vi will reply with a welcome message on first contact. Send any message to begin.

📷 The Teams chat window is native Teams UI — once the Bot is installed, search the bot name in the Teams Chat sidebar to open it.

Advanced configuration

Adding the Bot to Teams channels (groups)

To add the Bot to a Teams channel:

  1. Channel settings → Manage channel → Apps → add Bot
  2. By default the Bot only replies when @mentioned

To make the Bot reply to every message, ask Rose (or change it directly in admin panel):

“Please set Vi’s Teams channel XXX to reply without requiring @mention”

Allowlist (who can use it)

By default, anyone in the Teams workspace can DM the Bot. To restrict:

“Please limit Vi’s Teams to these three emails only: a@company.com / b@company.com / c@company.com”

Media support

Vi on Teams supports:

  • ✅ Text messages
  • ✅ Attached files (PDF / Word / Excel — auto-parsed)
  • ✅ Images (auto-analyzed)
  • ✅ Adaptive Cards (interactive card replies)
  • ✅ @mentions (both DM and channel)
  • ❌ Video calls (use the Google Meet integration instead)

FAQ

The Bot doesn’t reply

  1. Confirm credentials: admin panel’s Teams settings page should show “Connected”
  2. Confirm Bot is approved in your Teams workspace: check the Teams admin console
  3. Check Vi container status: admin panel → hm-3 → Home → container should be Running
  4. Check activity log: admin panel → hm-3 → Activity → see if messages arrived
  5. Restart the container: admin panel → hm-3 → Restart Container

admin panel shows “Connection Status: Failed”

Most common causes:

  • App Password expired: Azure Portal → your Bot app → Certificates & secrets → check expiry. Re-generate and update the admin panel.
  • Wrong Tenant ID: Azure Portal → Microsoft Entra ID → Overview, confirm it’s the company tenant.
  • Bot app permissions missing: Azure Bot Service → Configuration, confirm Messaging endpoint isn’t locked.

My company IT won’t grant admin rights

Fall back to Telegram or Slack — both can create Bots with personal accounts and don’t need IT involvement.

If you really need Teams, you can also use a personal Microsoft account + personal Teams (no company tenant), but only you will be able to use it.

Can one Vi connect to multiple Teams workspaces?

Yes. Vi is multi-tenant: just add multiple sets of Teams credentials in admin panel, one per workspace.

Removing the Teams integration later

admin panel → hm-3 → Settings → Messaging → Microsoft Teams → click Disconnect. The Bot stops responding in Teams; you can also uninstall the App from your Teams workspace if you want.

Next