There are four ways to set up hermes agent microsoft teams, and the right one depends on whether you want people chatting with the agent, meeting summaries, Teams actions from another app, or an agent sitting in live calls.
This guide compares the four routes in one table, then walks through the setup for each, using the official Hermes Teams setup page, the Teams Meetings page and each third-party vendor's own instructions.
Most readers want route one, the native Teams bot, so it gets the most detail.
If you'd rather talk your choice through first, book a free SEO strategy session with my team.
The Four Routes Side By Side
| Route | What it does | What it needs | Best for |
|---|---|---|---|
| 1. Native Teams bot (Hermes gateway) | Staff message Hermes in private chats, group chats and channels; risky commands ask for approval on a card | Teams CLI, a public HTTPS address, three bot credentials, an allowlist | Teams-first companies that want the agent where people already talk |
| 2. Teams meeting pipeline (bundled plugin) | Reads meeting transcripts through Microsoft Graph and posts summaries to Teams, Notion or Linear | Tenant admin, Graph app with admin consent, licences that produce transcripts, a renewal job | Firms that want written follow-ups after Teams meetings |
| 3. Composio Microsoft Teams MCP | Gives Hermes Teams tools through an MCP server, so the agent can act in Teams from wherever you chat with it | A Composio account and API key, an entry under mcp_servers in config.yaml, a sign-in to Teams when prompted | People who run Hermes from the CLI or another chat app and want it to post or read in Teams |
| 4. MeetStream (community plugin) | Says it joins Zoom, Google Meet and Teams calls as a visible bot that records, transcribes and answers meeting-chat questions | The plugin from the community tier of the catalog and its own setup | Teams that want an agent present during live calls |
Routes one and two are from Nous Research and are documented in the Hermes docs.
Route three is documented by Composio on its Hermes and Microsoft Teams page.
Route four is listed in the Hermes plugin catalog under the community tier, maintained by MeetStream, not Nous.
Routes one and two work well together, because the pipeline can post its summaries through the same Teams platform entry the bot uses.
Route 1: Connect Hermes To Teams As A Bot
The guided option is hermes gateway setup, then pick Microsoft Teams.
The manual setup takes six moves:
- Install and sign in to the Teams CLI:
npm install -g @microsoft/teams.cli@preview, thenteams login. Runteams status --verbosefor your AAD object ID. - Expose port
3978through devtunnel, ngrok or cloudflared, because Teams can't reachlocalhost. - Create the bot with
teams app create --name "Hermes"and an--endpointending in/api/messages. Save the client secret; it prints once. - Put
TEAMS_CLIENT_ID,TEAMS_CLIENT_SECRET,TEAMS_TENANT_IDandTEAMS_ALLOWED_USERSin~/.hermes/.env. - Run
hermes gateway restartand checkcurl http://localhost:3978/healthprintsok. - Run
teams app get <teamsAppId> --install-link, open the link, and message the bot.
The CLI handles bot registration, so the Azure portal never comes into it.
Microsoft's Teams bot overview explains the bot model the Hermes adapter plugs into.
How The Bot Behaves Once It's Connected
In a personal chat it replies to every message.
In group chats and channels it replies only when @mentioned.
If the app manifest later gains resource-specific consent to read all messages, set TEAMS_REQUIRE_MENTION=true so that stays true.
Dangerous commands arrive as an Adaptive Card offering Allow Once, Allow Session, Always Allow and Deny.
The messaging docs tick images, threads and typing indicators for Teams, and leave voice, files, reactions and streaming unticked.
Set TEAMS_HOME_CHANNEL if you want Hermes cron jobs to post into a channel.
๐ฅ Want help picking and building your Teams route? Inside the AI Profit Boardroom you can copy our tested Agent OS, watch guided video builds, and get your setup reviewed on one of four weekly coaching calls with 3,400+ members. โ Join the AI Profit Boardroom
Setting It Up For Multiple Users
Teams is shared by nature, so plan for more than one person from the start.
TEAMS_ALLOWED_USERS takes a comma-separated list of AAD object IDs; add one per colleague.
Anyone missing from that list is ignored without a reply, which is the most common reason a new user thinks the bot is broken.
TEAMS_ALLOW_ALL_USERS opens the bot to everyone, and the docs mark it as a development setting.
Approvals need thought too: by default, per the security docs, anyone admitted to the chat may answer one.
Set approvals.approvers to an empty list and each approval is bound to the person who asked; a colleague who taps it then gets a private Teams card response instead.
Or list specific user IDs as approvers, which suits a team lead who signs off on risky work.
Route 2: Add The Teams Meeting Pipeline
This route needs a tenant admin and a Graph app built from the Graph app registration guide.
The tenant needs Teams Premium or other Teams licences that create transcripts and recordings.
- Register a single-tenant app in entra.microsoft.com and copy the secret's Value, not its ID.
- Add
OnlineMeetings.Read.AllandOnlineMeetingTranscript.Read.All, plus the recording permissions if you want a fallback, then grant admin consent. - Restrict the app to named users with an Application Access Policy in PowerShell.
- Run
hermes plugins enable teams_pipelineand add theMSGRAPH_credentials to the env file. - Turn on the
msgraph_webhooklistener on port 8646 with a client state secret. - Choose
graphorincoming_webhookdelivery, then create subscriptions withhermes teams-pipeline subscribe.
The pipeline reads the transcript first and falls back to the recording plus speech-to-text, which needs ffmpeg.
The operator guide then has you schedule hermes teams-pipeline maintain-subscriptions every 12 hours, because Graph subscriptions lapse within 72 hours.
Route 3: Connect Through The Composio Teams MCP
Hermes speaks MCP natively, and its MCP docs say servers go under mcp_servers in ~/.hermes/config.yaml, with tools discovered at startup.
Composio's own instructions follow that pattern:
- Copy your Connect MCP URL and API key from the Composio dashboard.
- Open
~/.hermes/config.yaml. - Add a
composioentry undermcp_serverswith the URL and your key in thex-consumer-api-keyheader. - Restart Hermes.
- Ask the agent for a Teams task; Composio prompts you to sign in and authorise access.
This route doesn't give your staff a bot inside Teams.
It gives the agent Teams tools, so you can ask it from the CLI or another chat app to work with Teams for you.
Composio says it manages the OAuth, tokens and scopes, which means your Teams access runs through a third party you'll want to vet first.
๐ Not sure which route fits your company? Book a free SEO strategy session and we'll match a route to how your team actually uses Teams. โ Book your free strategy call
Route 4: MeetStream For Live Calls
The official pipeline only works after a meeting ends.
If you need the agent present while people talk, the catalog's MeetStream entry describes a plugin that joins Teams, Zoom and Google Meet calls as a visible bot, records and transcribes them, and answers questions typed in the meeting chat while the gateway runs.
It's a community plugin from MeetStream, so its setup, support and data handling are set by MeetStream, not by the Hermes docs.
Read its README before you put it in client calls, and tell attendees a bot is present.
What Each Route Asks Of Your Microsoft 365 Tenant
People searching for Hermes and Microsoft 365 usually want to know how much admin work is involved.
Route one asks the least: the person running the Teams CLI signs in with their own account, creates the bot and installs it from a link.
Route two asks the most: a tenant admin grants application permissions that cover meetings tenant-wide, then scopes them with a PowerShell policy that can take up to 30 minutes to apply.
Microsoft documents how those application access policies limit an app to the users it's granted to.
Route three depends on Composio's sign-in flow, which you approve when the agent first asks for Teams access.
Route four follows whatever MeetStream's own setup requires.
If your company's IT team controls app installs, ask them before you start, because a blocked install link stops route one at the last step.
Common Mistakes, And The Fix For Each
- An empty allowlist. The docs warn that without
TEAMS_ALLOWED_USERS, anyone who finds the bot can use it. Fill it before the install link goes out. - HTTPS sent to the listener. Port 3978 is plain HTTP. A tunnel or proxy that forwards HTTPS gives 400 errors in the log.
- A tunnel URL that keeps changing. ngrok and cloudflared issue a new address each run unless you pay for a fixed one; a named devtunnel keeps its URL. Update the bot with
teams app updatewhen it moves. - A self-signed certificate in production. Teams rejects it. Use a valid certificate on a reverse proxy.
- No renewal job. Meeting notifications stop after about three days. Schedule
maintain-subscriptionsthe day you subscribe. - Tenant-wide meeting access. Without an Application Access Policy, the Graph app can read every meeting in the company.
- Copying the Secret ID. The Graph guide says to copy the Value column instead.
One Microsoft-side surprise: Microsoft Learn says that if an admin switches off Graph access to transcripts, transcript subscriptions fail with a 403.
Which Route Suits Which Team
- A small office on Teams: route one, in one channel, with a short allowlist.
- A firm with client meetings and an IT admin: routes one and two together, summaries posted into the matching channel.
- A solo operator who lives in the terminal: route three, so Hermes can post to Teams without a bot to host.
- A team that wants an agent in the call itself: route four, after checking the plugin's own docs.
Comparing Hermes with a hosted agent? Our Grok Bot Microsoft Teams guide covers how that one connects.
My Pick: Where To Start
Start with route one, because it's the documented, built-in way to put Hermes inside Teams and its approval cards keep shared channels safe.
Add route two once you have the licences, an admin and a renewal schedule.
Reach for routes three and four only when you need what they add.
To learn each route with other operators, join the AI Profit Boardroom, or book a free SEO strategy session for a plan around your tenant.
Also On Our Network
- ๐ The nine-step operator build for a Hermes Teams bot and its meeting pipeline
- ๐ Plain-English steps to set up a Hermes agent in Microsoft Teams for a small firm
- ๐ How to set up a Hermes Teams bot inside your Agent OS, step by step
- ๐ A two-stage Hermes Microsoft Teams setup, with a short model pick at the end
- ๐ The complete Hermes Agent Microsoft Teams guide on AI Profit Boardroom
FAQ: Hermes Agent Microsoft Teams
What is the main way to connect Hermes Agent to Microsoft Teams?
The native Teams bot in the Hermes gateway. You register it with the Teams CLI, add its credentials and an allowlist to ~/.hermes/.env, and restart the gateway.
How is the Composio Teams MCP different from the native bot?
Composio adds Teams tools to Hermes through an MCP server in config.yaml. The native bot puts Hermes inside Teams so staff can message it.
Can several people use the Hermes Teams bot?
Yes. List each person's AAD object ID, comma-separated, in TEAMS_ALLOWED_USERS. Anyone not listed is ignored.
Which route gives me meeting summaries?
The bundled teams_pipeline plugin. It reads transcripts through Microsoft Graph after a meeting and posts summaries to Teams, Notion or Linear.
Can Hermes sit in a live Teams call?
Not with the official routes. MeetStream, a community plugin in the Hermes catalog, says it joins calls as a visible bot.
What is the most common setup mistake?
Forgetting the allowlist on the bot, or forgetting the subscription renewal job on the meeting pipeline.
๐บ Video notes + links to the tools ๐
๐ฅ Learn how I make these videos ๐
๐ Get a FREE AI Course + Community + 1,000 AI Agents ๐
About Julian
I'm Julian Goldie, an SEO entrepreneur, author and founder of the AI Profit Boardroom, which has 3,400+ members.
I help business owners scale with AI agents, automation and SEO.
- I've built a 7-figure SEO and link building agency, Goldie Agency, with a team of 70+ SEO experts.
- I've grown a YouTube channel to 400,000+ subscribers.
- I wrote "Link Building Mastery".
- My Udemy courses have taught over 29,000 students.
โ Get my best AI training inside the AI Profit Boardroom
Pick your route from the table, set up the bot first, add meetings when your admin is ready, and if you want a hand, book a free SEO strategy session or ask inside the AI Profit Boardroom as you connect hermes agent microsoft teams.











