Tutorial

OpenClaw Microsoft Teams Integration Guide

February 21, 20263 min readReviewed March 8, 2026

OpenClaw supports Microsoft Teams with a policy model that defaults to safer behavior in group contexts, including mention-sensitive responses and explicit allowlisting for broader participation[1].

Deployment Inputs

Azure app registration and Graph permissions for the bot identity[2].
OpenClaw Teams channel config with tenant/app credentials[1].
Pairing policy for DM sender approval[3].

Safe Starting Configuration

{
  "channels": {
    "msteams": {
      "dmPolicy": "pairing",
      "groupPolicy": "allowlist",
      "requireMention": true
    }
  }
}

Operational Verification

openclaw channels list
openclaw channels status --probe
openclaw channels capabilities --channel msteams
openclaw logs --follow

This gives a complete readiness snapshot: registration, liveness, supported actions, and runtime errors[4].

DM Pairing Approval

openclaw pairing list msteams
openclaw pairing approve msteams <CODE>

Files in Group Chats

Teams group file send flows can require SharePoint/Graph permission wiring. Validate file behavior in a staging team before enabling high-volume production channels[1][2].

Troubleshooting Priorities

Auth and token refresh failures in logs.
Scope mismatch between app permissions and desired actions.
Message policy mismatch (mention required vs expected always-on behavior)[1][5].

References

OpenClaw Docs: Microsoft Teams Channel - Accessed February 21, 2026
Microsoft Graph: Teams Concepts - Accessed February 21, 2026
OpenClaw Docs: Pairing - Accessed February 21, 2026
OpenClaw Docs: CLI Channels - Accessed February 21, 2026
OpenClaw Docs: Group Policy and Mention Behavior - Accessed February 21, 2026