OpenClaw Microsoft Teams Integration: Enterprise Setup Guide

Microsoft Teams is the dominant workplace communication platform for enterprises. If your organization runs on Microsoft 365, integrating OpenClaw with Teams lets your team access AI-powered automation without leaving their primary work environment.

The Teams integration uses Microsoft's Bot Framework, which provides enterprise-grade authentication, compliance logging, and admin-managed deployment. This guide covers the complete setup process.

What Does the OpenClaw Teams Integration Do?

The Teams integration brings OpenClaw into your Microsoft workspace. Team members can chat with the bot in 1-on-1 conversations, add it to group chats, or install it in channels for team-wide access.

• 1-on-1 chat — private conversations with the AI assistant
• Channel bot — responds to @mentions in team channels
• Adaptive Cards — rich interactive cards with buttons, forms, and formatted output
• File handling — process uploaded documents and share files back
• Task modules — pop-up forms for structured data entry
• SSO integration — leverages Azure AD for authentication

What Do You Need Before Starting?

• A running OpenClaw instance with a public HTTPS endpoint
• An Azure subscription (free tier works for bot registration)
• Microsoft 365 tenant with Teams enabled
• Teams admin access for organization-wide deployment (or developer sideloading for testing)

How Do You Set Up OpenClaw With Microsoft Teams?

Step 1 — Register a bot in Azure

Go to the Azure Portal and create a new Azure Bot resource. Choose "Multi Tenant" for the bot type. Note the Microsoft App ID and generate a client secret.

Step 2 — Configure the messaging endpoint

In the Azure Bot settings, set the Messaging endpoint to your OpenClaw server's public URL:

https://yourdomain.com/api/teams/messages

Step 3 — Enable the Teams channel

In the Azure Bot resource, go to Channels and add Microsoft Teams. Accept the terms of service.

Step 4 — Configure OpenClaw

gateways:
  teams:
    enabled: true
    app_id: "YOUR_AZURE_APP_ID"
    app_secret: "YOUR_CLIENT_SECRET"
    tenant_id: "YOUR_TENANT_ID"
    endpoint: "/api/teams/messages"
    adaptive_cards: true
    allowed_users: []        # empty = all users in tenant

Step 5 — Create the Teams app manifest

Create a manifest.json file for your Teams app:

{
  "$schema": "https://developer.microsoft.com/json-schemas/teams/v1.17/MicrosoftTeams.schema.json",
  "manifestVersion": "1.17",
  "version": "1.0.0",
  "id": "YOUR_APP_ID",
  "developer": {
    "name": "Your Organization",
    "websiteUrl": "https://yourdomain.com",
    "privacyUrl": "https://yourdomain.com/privacy",
    "termsOfUseUrl": "https://yourdomain.com/terms"
  },
  "name": { "short": "OpenClaw", "full": "OpenClaw AI Assistant" },
  "description": { "short": "AI assistant powered by OpenClaw", "full": "An AI assistant that helps with tasks, research, and automation." },
  "bots": [{
    "botId": "YOUR_AZURE_APP_ID",
    "scopes": ["personal", "team", "groupChat"],
    "commandLists": [{
      "scopes": ["personal"],
      "commands": [
        { "title": "help", "description": "Show available commands" },
        { "title": "brief", "description": "Get your daily briefing" }
      ]
    }]
  }]
}

Package the manifest with two icon files (color and outline) into a ZIP file and upload it to your Teams Admin Center or sideload it for testing.

Step 6 — Start and test

openclaw start --gateway teams

In Teams, search for your bot by name and start a chat. Send a test message to confirm the integration is working.

What Are the Best Teams Use Cases?

• Enterprise knowledge base — employees ask the bot about HR policies, IT procedures, and company information
• Meeting assistant — summarize meeting transcripts, extract action items, and post them to the team channel
• IT helpdesk — first-line support for common IT issues with escalation to human agents
• Project updates — pull status from project management tools and post summaries on a schedule
• Onboarding — guide new employees through setup checklists and answer common questions

How Do You Fix Common Teams Issues?

• Bot not responding: Verify the messaging endpoint URL is correct and publicly accessible. Check that the App ID and secret match between Azure and your OpenClaw config.
• "App not found" in Teams: The app manifest may not be deployed. Check the Teams Admin Center under Manage Apps or sideload the app ZIP file directly in Teams.
• 401 Unauthorized errors: The client secret may have expired. Generate a new one in the Azure Portal under Certificates & secrets and update your OpenClaw config.
• Bot works in 1-on-1 but not in channels: Ensure the manifest includes "team" in the bot scopes. The bot must be @mentioned in channels to receive messages.
• Adaptive Cards not rendering: Verify your card JSON is valid using the Adaptive Cards Designer. Teams supports Adaptive Cards v1.5.

FAQ

Does the Teams integration require an Azure subscription?

Yes. Microsoft requires bot registration through Azure Bot Service, which needs an active Azure subscription. The bot registration itself is free, but you need the subscription to create it. If your organization already uses Microsoft 365, you likely have access.

Can OpenClaw work with Teams channels and group chats?

Yes. OpenClaw supports 1-on-1 chats, group chats, and Teams channels. In channels, the bot responds when @mentioned. In group chats, you can configure it to respond to all messages or only when mentioned.

Does the Teams admin need to approve the bot?

For organization-wide deployment, yes. A Teams admin must approve the custom app through the Teams Admin Center. For testing, developers can sideload the app in their own Teams client without admin approval.

Can I use OpenClaw with Teams on mobile?

Yes. Once the bot is installed in Teams, it works on all Teams clients — desktop, web, iOS, and Android. The experience is identical across platforms.

*Last updated: March 2026. Published by the Remote OpenClaw team at remoteopenclaw.com.*