Connect Microsoft Teams to OpenClaw

Microsoft Teams setup crosses OpenClaw, a Microsoft tenant, and the bot or app registration. Treat each boundary separately so a tenant permission problem is not mistaken for a Gateway routing problem.

Prepare the tenant application

Follow the current official channel guide for the supported app registration, credentials, callback or event endpoint, and Teams installation package. Use a dedicated application with the minimum required permissions.

On the Gateway host, inspect the channel and plugin:

openclaw plugins list
openclaw channels status --probe
openclaw logs --follow

Keep tenant identifiers, client secrets, and certificates out of committed configuration and issue screenshots.

Configure policy before rollout

Begin with one operator and one test conversation. Decide which users, teams, or channels may trigger the agent and whether group messages require a mention. Do not install broadly across the tenant until the routing and data boundary are understood.

Verify the full path

Send one test message, confirm the event reaches the Gateway, and verify the intended agent handles it. Send a reply and check the correct Teams conversation receives it. Then test a user or team outside the allowlist.

Expected result

• Tenant authentication and channel probe succeed.
• The permitted conversation reaches one intended agent.
• Replies remain in the correct Teams context.
• Unapproved users or teams do not trigger work.
• Credentials survive the intended service restart without appearing in logs.

Use live logs to distinguish Microsoft delivery errors from OpenClaw routing or model failures.