Connect Microsoft Teams Meetings to Your AI Agent

Start With Teams Chat

The meeting features reuse the bot registration and credentials from the ordinary Teams setup. If you have not done that yet, follow connecting Microsoft Teams first and come back — nothing here works without it.

What You Need

• Microsoft Graph application credentials, with the permissions for the meeting resources you intend to subscribe to. Graph permissions are granted per resource type, so decide what the agent should see before requesting them.
• An administrator who can consent to those permissions in your tenant. Meeting data is sensitive and consent is not something a normal user grants.

Add the Graph Credentials

From your instance's Web Terminal, run the guided setup and pick Teams Meetings:

hermes gateway setup

Or set them directly:

MSGRAPH_TENANT_ID=<tenant-id>
MSGRAPH_CLIENT_ID=<client-id>

Enable the Pipeline Plugin

The meeting operator commands live in a plugin that is off by default. Turn it on:

hermes plugins enable teams_pipeline

Then validate the configuration before relying on it:

hermes teams-pipeline validate
hermes teams-pipeline list

The validate step is worth running properly. It is the difference between finding a missing Graph permission now and finding it when a meeting you cared about produced nothing.

Keep Subscriptions Alive

Microsoft Graph subscriptions expire and have to be renewed. There is a maintenance command for exactly that:

hermes teams-pipeline maintain-subscriptions

Run it on a schedule. An expired subscription does not raise an error anywhere obvious — the agent simply stops seeing meetings, which is the quietest possible failure and the one most likely to go unnoticed for a week.

A Word on Consent

Meeting content is some of the most sensitive data in an organisation. Before pointing an agent at it, be clear with your colleagues about what is being processed and check it against whatever policy governs recordings and transcripts where you are. Technical permission from Graph is not the same as permission from the people in the meeting.

Troubleshooting

• Commands are not found. The teams_pipeline plugin is not enabled.
• Validation fails on permissions. The Graph app is missing a permission, or admin consent was never granted for it.
• It worked and then went quiet. A subscription expired. Run the maintenance command and schedule it.
• Nothing appears for a specific meeting. Check the resource type is one your permissions actually cover.

Need a Hand?

Contact support from your dashboard. We can configure the agent side; the Graph app registration and admin consent must come from someone with rights in your tenant.