Run all of this inside the full Agent OS — join the AI Profit Boardroom →

agentos.guide › blog

How To Set Up Hermes Agent Microsoft Teams In Your Agent OS: Connect The Bot, Add Meeting Summaries, Then Hand The Checks To Three Prompts

By Julian Goldie · 15 November 2026 · agentos.guide

Illustrated hero: a glowing Agent OS console on a dark aubergine background linked by gold lines to a chat bubble and a meeting calendar card

To set up hermes agent microsoft teams in your Agent OS, you connect one Hermes profile to Teams as a bot, then optionally add the meeting pipeline that turns finished Teams meetings into summaries in a channel.

This guide walks through both setups step by step, then gives you three prompts to paste into your agent and a weekly routine that keeps everything healthy.

Each setting below is taken from the Hermes docs: the Teams bot guide and the Teams meetings guide.

If you'd like help choosing which profile should face Teams, book a free SEO strategy session with my team.

Step By Step: Connect Your Agent OS To Teams As A Bot

  1. Install the Teams CLI and sign in. Microsoft's CLI registers the bot for you, so you never open the Azure portal. Note the AAD object ID that teams status --verbose prints.
  2. Open a tunnel to port 3978. Teams posts every message to a public HTTPS webhook, so the Agent OS machine has to be reachable; devtunnel, ngrok and cloudflared all work for testing.
  3. Create the bot. Give it an endpoint ending in /api/messages and save the client secret straight away, because the CLI shows it once.
  4. Fill the env file. Add TEAMS_CLIENT_ID, TEAMS_CLIENT_SECRET, TEAMS_TENANT_ID and TEAMS_ALLOWED_USERS to ~/.hermes/.env, then restart the gateway.
  5. Install and test. Open the install link, which jumps into the Teams client, and send the bot a direct message.
npm install -g @microsoft/teams.cli@preview
teams login
teams status --verbose
teams app create --name "Hermes" --endpoint "https://<tunnel>/api/messages"
hermes gateway restart
curl http://localhost:3978/health
teams app get <teamsAppId> --install-link

Or let the wizard drive: run hermes gateway setup and choose Microsoft Teams.

Keep TEAMS_ALLOWED_USERS filled from the first minute; the docs warn that an empty list lets anyone who finds the bot use it.

Going Live: From Tunnel To Your Own Domain

A tunnel is fine while you test the seat on your own machine.

For an always-on Agent OS, put a reverse proxy with a valid certificate in front of the gateway and forward plain HTTP to 127.0.0.1:3978.

Teams refuses self-signed certificates, and the Hermes listener never serves HTTPS itself.

Update the bot's address with teams app update and the new endpoint, then run the health check again.

The Graph listener follows the same pattern on port 8646: bind it to loopback behind the proxy, because a public bind needs allowed_source_cidrs set to Microsoft's ranges.

The webhook listener page also notes the listener won't start at all without its client state secret.

What The Teams Seat Can And Can't Do

Set your team's expectations before the first message.

In a personal chat, the profile answers everything it receives.

In group chats and channels, it stays silent until someone @mentions it, and Hermes strips the mention tag before your agent reads the request.

If you later grant the app resource-specific consent to read channel messages, Teams starts sending every message, so set require_mention: true to keep the same behaviour.

The platform table ticks images, threads and typing indicators for Teams, and leaves voice, files, reactions and streaming unticked.

Risky commands never run on a typed yes; they arrive as an Adaptive Card, and a click swaps the card for the outcome.

Set TEAMS_HOME_CHANNEL if you want your OS's scheduled jobs to report into Teams, and allowed users can even send /update from a chat to update Hermes.

🔥 Want the Agent OS with the gateway already running?

Boardroom members download the Agent OS itself, learn each piece through bite-sized video trainings, and get unstuck on four live calls a week with 3,400+ builders.

→ Join the AI Profit Boardroom

Opening The Teams Seat To Several Colleagues

Add each colleague's AAD object ID to TEAMS_ALLOWED_USERS, separated by commas, and restart the gateway.

Anyone left off the list is dropped silently, so a new starter who gets no reply is usually just missing from it.

Approvals need a decision too: the security docs say any admitted member can answer a pending approval by default.

Set approvals.approvers to an empty list to bind each card to the person who asked, or list the user IDs of the people who should sign off.

Step By Step: Add The Meeting Pipeline

This half needs a tenant admin, a Graph app from the registration guide, and Teams licences that produce transcripts.

Once those are ready, the order is short:

hermes plugins enable teams_pipeline

# ~/.hermes/.env
MSGRAPH_TENANT_ID=<tenant-id>
MSGRAPH_CLIENT_ID=<client-id>
MSGRAPH_CLIENT_SECRET=<secret-value>
MSGRAPH_WEBHOOK_ENABLED=true
MSGRAPH_WEBHOOK_PORT=8646
MSGRAPH_WEBHOOK_CLIENT_STATE=<openssl rand -hex 32>
MSGRAPH_WEBHOOK_ACCEPTED_RESOURCES=communications/onlineMeetings

hermes teams-pipeline validate

Then create Graph subscriptions for transcripts, and recordings if you want the speech-to-text fallback.

Choose a delivery mode under platforms.teams.extra: graph with a chat or a team and channel, or incoming_webhook with a Teams URL.

The pipeline can also write to Notion and Linear if those sinks are switched on.

Where Teams Sits In Your Agent OS

Your Agent OS runs Hermes, its gateway and a set of profiles on one machine.

The gateway is the single background process that connects your profiles to chat platforms, and Teams is one of the platforms it supports.

The messaging docs give the Teams channel the hermes-teams toolset, which means full tools, terminal included.

The meeting pipeline is separate: a bundled plugin that listens for Microsoft Graph events rather than chat messages.

So you end up with two inputs into the same OS: people typing in Teams, and Microsoft 365 reporting that a meeting produced a transcript.

Members of the AI Profit Boardroom get the installable Agent OS, so the gateway is already running before you add Teams.

Three Copy-Paste Prompts That Check The Setup For You

Once both halves are connected, hand the routine checks to your agent with these prompts.

Prompt 1: Confirm The Teams Seat Is Locked Down

Read ~/.hermes/config.yaml and list every setting under platforms.teams,
masking any secret values.
Then tell me, without printing secrets, whether TEAMS_ALLOWED_USERS and
TEAMS_ALLOW_ALL_USERS are set in ~/.hermes/.env, and whether that file's
permissions are 600.
Flag anything that would let an unlisted Teams user reach you.
Change nothing.

Run this from the CLI, not from Teams, so the answer stays on your machine.

If it reports that the env file is readable by others, fix it with chmod 600 ~/.hermes/.env, as the security section asks.

Prompt 2: Set Up The Renewal Job

Create ~/.hermes/scripts/maintain-teams-subscriptions.sh containing:
#!/usr/bin/env bash
exec hermes teams-pipeline maintain-subscriptions
Make it executable.
Then register a script-only cron job named
teams-pipeline-maintain-subscriptions that runs "0 */12 * * *"
with --no-agent and --deliver local.
Show me hermes cron list when you're done.

This one matters most.

Graph subscriptions expire within 72 hours, and the operator guide calls a missed renewal the number one failure mode.

Running it twice a day leaves about six times the headroom you need.

Prefer systemd? The same guide gives a timer unit, and a plain crontab line works if your cron environment can read the Graph credentials.

Prompt 3: The Morning Pipeline Check

Run these and summarise the results in five lines or fewer:
hermes teams-pipeline validate
hermes teams-pipeline token-health
hermes teams-pipeline maintain-subscriptions --dry-run
hermes teams-pipeline list --status failed
If any job failed, run hermes teams-pipeline show on it and tell me the
likely cause. Do not replay anything without asking me first.

The dry run should usually report nothing expiring soon.

A failed job can be replayed with hermes teams-pipeline run once you've fixed the cause, which is why the prompt asks the agent to stop and check with you.

📞 Want a second pair of eyes on your tenant?

Book a free strategy session and my team will walk through your Teams channels, Graph permissions and renewal plan with you.

→ Book a free SEO strategy session

The Weekly Routine

WhenWhat to run or checkWhy
DailyPrompt 3Catches failed jobs and expiring subscriptions early
WeeklyPrompt 1 and the allowlistPeople join and leave; the list should follow
After any config changehermes teams-pipeline validateThe operator guide says to run it first
Before a secret expiresAdd a second secret, update the env file, restart, delete the old oneThe rotation order in the Graph guide avoids downtime

My Verdict For Agent OS Users

Give Teams to one profile, not all of them, and keep its allowlist short.

Add the meetings seat once the chat seat has run cleanly for a week.

Scope the Graph app with an Application Access Policy, which the Graph guide recommends and Microsoft documents, so the profile can only read the meetings you choose.

For call joining, the official pipeline isn't the tool; the plugin catalog lists MeetStream as a community plugin for that, and our Grok Bot Microsoft Teams guide covers a hosted route.

Bring your setup to the AI Profit Boardroom coaching calls if you get stuck.

Also On Our Network

FAQ

Which Agent OS profile should get the Teams seat?

The profile your team already asks for everyday help, with an allowlist limited to the people who need it.

Do I need both quick starts?

No. The chat seat works on its own. The meetings seat adds Graph-driven summaries and needs a tenant admin and transcription-capable licences.

What does the renewal prompt protect against?

Graph subscriptions lapse within 72 hours. The cron job renews them twice a day so meeting notifications keep arriving.

Can my agent replay a failed summary on its own?

It can, with hermes teams-pipeline run, but Prompt 3 tells it to ask you first so you can fix the delivery target before a replay.

Why does a short /meet/ link fail in a manual fetch?

Graph rejects those links on the default endpoint. Rerun the fetch with --organizer-user-id and the organiser's Entra user ID.

Will the agent speak in our Teams calls?

Not through the official pipeline, which works from saved transcripts and recordings. MeetStream is a community plugin that says it joins calls.

Final word on How To Set Up Hermes Agent Microsoft Teams In Your Agent OS

Connect the bot today, paste Prompt 1, schedule Prompt 2 before your first subscription, and if you'd like help with the rest, my team can map it on a free SEO strategy session, or you can join the AI Profit Boardroom to run hermes agent microsoft teams inside your Agent OS.

About Julian

I'm Julian Goldie, an AI entrepreneur, SEO expert and the founder of the AI Profit Boardroom, which has 3,400+ members.

I help business owners scale with AI agents, automation and SEO.

My YouTube channel has 400,000+ subscribers, and I run Goldie Agency, a seven-figure SEO agency.

→ Get my best AI training inside the AI Profit Boardroom

Related guides on agentos.guide

→ Grok Bot Microsoft Teams: Plan The Rollout In Your Agent OS

→ Hermes Agent Cron Job: Schedule, Stop And Recover Jobs In Your Agent OS With 5 Copy-Paste Prompts

→ Hermes Webapp: Run Your Whole Agent OS From A Browser Tab, With Five Copy-Paste Prompts

→ Hermes Agent Video Analysis: How To Set It Up In Your Agent OS

Get the whole Agent OS

The installable system behind every guide on this site — dashboard, agents, memory and pipelines — updated as new tools land, with 3,400+ members and four coaching calls a week.

Join the AI Profit Boardroom →

📺 Video notes + links to the tools 👉

🎥 Learn how I make these videos 👉

🆓 Get a FREE AI Course + Community + 1,000 AI Agents 👉

← all guides on agentos.guide