Hermes BibleUnofficial Docs
← All docs Docs / Messaging Platforms

Microsoft Teams

Microsoft Teams Setup Connect Hermes Agent to Microsoft Teams as a bot. Unlike Slack's Socket Mode, Teams delivers messages by calling a public HTTPS webhook ,

Messaging Platforms
Section
Messaging Platforms
Source
hermesbible.com/docs/user-guide/messaging/teams

Microsoft Teams Setup Connect Hermes Agent to Microsoft Teams as a bot. Unlike Slack's Socket Mode, Teams delivers messages by calling a public HTTPS webhook ,

Excerpt from the official Hermes Agent documentation, quoted for reference. View source

What this page covers

Section outline mirrored from the official Hermes Agent documentation. Follow any heading to read the complete text on the source site.

Upstream outline

  1. How the Bot Responds
  2. Step 1: Install the Teams CLI
  3. Step 2: Expose the Webhook Port
  4. Step 3: Create the Bot
  5. Step 4: Configure Environment Variables
  6. Step 5: Start the Gateway
  7. Step 6: Install the App in Teams
  8. Configuration Reference
  9. Environment Variables
  10. config.yaml
  11. Features
  12. Interactive Approval Cards
  13. Meeting Summary Delivery (Teams Meeting Pipeline)
  14. Production Deployment

Section map

How the Bot Responds

Maps how the bot responds to the Messaging Platforms documentation path, with the source page reserved for exact commands and updates.

Step 1: Install the Teams CLI

Maps step 1: install the teams cli to the Messaging Platforms documentation path, with the source page reserved for exact commands and updates.

Step 2: Expose the Webhook Port

Maps step 2: expose the webhook port to the Messaging Platforms documentation path, with the source page reserved for exact commands and updates.

Step 3: Create the Bot

Maps step 3: create the bot to the Messaging Platforms documentation path, with the source page reserved for exact commands and updates.

Step 4: Configure Environment Variables

Maps step 4: configure environment variables to the Messaging Platforms documentation path, with the source page reserved for exact commands and updates.

Step 5: Start the Gateway

Maps step 5: start the gateway to the Messaging Platforms documentation path, with the source page reserved for exact commands and updates.

Step 6: Install the App in Teams

Maps step 6: install the app in teams to the Messaging Platforms documentation path, with the source page reserved for exact commands and updates.

Configuration Reference

Maps configuration reference to the Messaging Platforms documentation path, with the source page reserved for exact commands and updates.

Implementation notes

  • Use this Messaging Platforms doc as a navigation page first: the local clone mirrors the source structure and links each heading back to the authoritative upstream section.
  • Primary decision areas: How the Bot Responds, Step 1: Install the Teams CLI, Step 2: Expose the Webhook Port, Step 3: Create the Bot, Step 4: Configure Environment Variables. Read those source anchors before changing installs, credentials, automation, or runtime configuration.
  • Useful search signals for this doc: microsoft, teams, setup, connect, unlike. These are derived from the public title and summary so the clone remains lightweight.

Decision table

Best fitMessaging Platforms documentation

Use when you need orientation for microsoft teams before applying exact upstream commands.

Verify firstHow the Bot Responds

Open the source anchor for How the Bot Responds and confirm platform-specific requirements before changing configuration.

Escalate to sourceCommands, credentials, runtime behavior

Use the upstream page as the authority for current syntax, release changes, and security-sensitive steps.

Verification checklist

  1. Use this page to orient yourself within Messaging Platforms, then open the linked source page for exact current syntax.
  2. Start with the source section for How the Bot Responds; do not rely on the local summary for commands or secrets.
  3. Check platform, install method, provider, and credential assumptions before changing a real environment.
  4. Review the source section for Step 1: Install the Teams CLI if the page involves setup, automation, messaging, or runtime behavior.
  5. After applying anything from the source, run the smallest relevant smoke test before widening scope.

Risk notes

Automation

Start with a bounded dry run, logs, and a manual stop path before enabling recurring or unattended execution.

External messages

Keep human review before sending public posts, customer messages, trading instructions, or team notifications.

Runtime access

Check filesystem, shell, browser, repository, and server permissions before granting the agent write access.

What this page covers

  • Core concept and where it fits in the Hermes Agent system.
  • Setup or operating context implied by the upstream page summary.
  • The source page link for full current details and updates.

Source mirror note

This page is generated from the public Hermes Bible index so the clone has the same route coverage and search surface. It stores the public title, category, summary, and source link locally; use the source page for full upstream text and updates.

Open source page