Microsoft Teams

OpenClaw Microsoft Teams channel plugin. Enterprise team communication integration.

The Microsoft Teams plugin brings OpenClaw into the enterprise collaboration platform used by hundreds of millions of people worldwide. Available as a plugin-only channel since January 2026, it enables thread-aware conversations and @mention support directly within Teams channels and chats. The plugin integrates via Microsoft's Bot Framework, requiring an Azure Bot registration and App ID/Secret pair. Messages flow through Microsoft's Bot Connector service to your OpenClaw gateway, which processes them and sends responses back through the same channel. The architecture supports personal chats, group conversations, and channel mentions in Teams workspaces. Getting Teams working with OpenClaw has historically been one of the trickier setups due to Microsoft's multi-layered auth requirements (Azure AD, Bot Framework, Teams app manifest). The community has rallied around this — notably Brad Groux (@bradgroux), who became a dedicated maintainer for the Teams integration and actively helps users troubleshoot setup issues. His presence has significantly improved the Teams experience for OpenClaw users. This plugin is particularly valuable for organizations where Teams is the mandated communication platform and alternatives like Discord or Telegram aren't options. Thread awareness means conversations stay organized, and @mention support lets users invoke the bot naturally in group chats without disrupting workflow.

Tags: channel, messaging, enterprise

Use Cases

  • Enterprise AI assistant in Teams channels for employees who can't use external messaging platforms
  • IT helpdesk bot in Teams that answers common technical questions and creates support tickets
  • Project management assistant that provides status updates and summaries in Teams channels
  • Meeting preparation bot that summarizes documents and generates agendas before Teams meetings
  • Internal knowledge base search assistant for organizations using Microsoft 365 and SharePoint

Tips

  • Follow Brad Groux's (@bradgroux) setup guide and reach out to him on GitHub for Teams-specific issues
  • Start with a single-tenant Azure AD app for testing before going multi-tenant
  • Use Azure Bot Service (managed) instead of self-hosting the Bot Framework connector to simplify deployment
  • Get your IT/security team involved early — enterprise environments often require approval for custom bots
  • Test in a personal Teams tenant or developer sandbox before deploying to your organization
  • Use @mention in group chats to trigger the bot — it won't respond to every message by default
  • Pin the bot as a tab in Teams channels for quick access

Known Issues & Gotchas

  • Azure Bot registration requires a Microsoft Azure account — you can't skip this step even for testing
  • The Teams app manifest must specify your OpenClaw gateway's public HTTPS URL as the messaging endpoint
  • Tenant admin approval is often required — plan for IT review cycles in enterprise environments
  • Security teams may flag OpenClaw as unauthorized software — get pre-approval before deploying in corporate environments
  • Thread context works differently in Teams than Discord — ensure your allowlists account for both channels and personal chats
  • The Bot Framework SDK version must match what the plugin expects — check compatibility before upgrading
  • Multi-tenant vs single-tenant bot registration affects who can install your app
  • Rate limiting from Microsoft's Bot Connector can cause delays during burst messaging

Alternatives

  • Slack (built-in)
  • Discord (@openclaw/discord)
  • Google Chat

Community Feedback

I am a contributor, and now maintainer for OpenClaw focusing on the Microsoft Teams plugin and integration. Anyone who has tried to use Teams with OpenClaw has likely had some issues, and I'd like to help.

— Reddit r/openclaw

Microsoft Teams — plugin-only channel since Jan 2026. Thread awareness, mention support. Only way in if you use Teams.

— Reddit r/openclaw

Using this in an enterprise environment is currently a horrible idea. It can act as an authorized user and do anything an authorized user can do.

— Reddit r/ClaudeCode

OpenClaw is being detected on enterprise networks. We are detecting hundreds of deployments across our accounts.

— Reddit r/threatintel

Frequently Asked Questions

How do I register an Azure Bot for OpenClaw Teams integration?

Go to the Azure Portal, create a new Bot Channels Registration resource, configure the messaging endpoint to point to your OpenClaw gateway's public URL, and note the App ID and Secret. Then create a Teams app manifest referencing this bot registration.

Why is Teams setup harder than other OpenClaw channels?

Microsoft's enterprise security model requires Azure AD registration, Bot Framework setup, and often tenant admin approval. This multi-layer auth is by design for enterprise environments but adds complexity compared to Telegram or Discord's simple token-based setup.

Will my IT security team flag OpenClaw?

Possibly. Security teams have been detecting OpenClaw on enterprise networks. Get pre-approval from your IT department, use tenant-restricted bot registration, and follow your organization's security policies for custom app deployments.

Does the Teams plugin support @mentions?

Yes. Users can @mention the bot in Teams channels to trigger responses. You can configure mentionOnly mode so the bot only responds when explicitly mentioned, keeping group chats clean.

Can I use the Teams bot in personal chats?

Yes. The bot supports both 1:1 personal chats and group channel conversations. Personal chats don't require @mentions — every message is routed to OpenClaw directly.

Who maintains the Teams plugin?

Brad Groux (@bradgroux on GitHub) is the dedicated maintainer for the Microsoft Teams plugin. Tag him on GitHub issues or reach out via Twitter/Discord for Teams-specific support.

Configuration Examples

Basic Teams Bot Setup

channels:
  msteams:
    enabled: true
    appId: ${TEAMS_APP_ID}
    appSecret: ${TEAMS_APP_SECRET}

Teams with Tenant Restriction

channels:
  msteams:
    enabled: true
    appId: ${TEAMS_APP_ID}
    appSecret: ${TEAMS_APP_SECRET}
    tenantId: ${TEAMS_TENANT_ID}
    allowedTenants:
      - 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx'

Teams with Thread Awareness

channels:
  msteams:
    enabled: true
    appId: ${TEAMS_APP_ID}
    appSecret: ${TEAMS_APP_SECRET}
    tenantId: ${TEAMS_TENANT_ID}
    threads:
      enabled: true
      isolate: true
    mentionOnly: true

Installation

openclaw plugins install @openclaw/msteams