Microsoft Teams
AI assistant in Microsoft Teams
OpenClaw Microsoft Teams Integration
Bring your AI assistant into Microsoft Teams ā the collaboration hub for Microsoft 365 environments. Send messages, manage channels, access SharePoint files, and automate workflows through natural language.
Setup
Step 1: Register Azure App
- Go to portal.azure.com ā Azure Active Directory ā App registrations ā New registration
- Name: "OpenClaw Assistant"
- Redirect URI:
http://localhost:3000/callback
Step 2: Configure API Permissions
Add Microsoft Graph permissions:
ChannelMessage.SendChannel.ReadBasic.AllChat.ReadWriteTeam.ReadBasic.AllFiles.ReadWrite.All(for SharePoint)Calendars.ReadWrite
Grant admin consent.
Step 3: Get Credentials
- Application (client) ID
- Directory (tenant) ID
- Create client secret: Certificates & secrets ā New client secret
Step 4: Configure OpenClaw
integrations: microsoftTeams: enabled: true clientId: "YOUR_CLIENT_ID" clientSecret: "YOUR_CLIENT_SECRET" tenantId: "YOUR_TENANT_ID" defaultTeam: "Engineering" defaultChannel: "General"Messaging
Post to #engineering: Deployment starting in 5 minutesā Posted āSend a direct message to John: Can we sync at 2pm?ā Message sent āWhat's the latest in the #design channel?ā Last 5 messages: Lisa shared wireframes, Tom approved layout...File Access
Find the Q1 report in the Marketing teamā Found: Q1 Marketing Report.xlsx (last modified by Sarah, 2 days ago)Share the project brief in #generalā File shared in Engineering > General āMeeting Integration
Works alongside the Outlook/Zoom integrations:
Schedule a Teams meeting with the design team Friday at 2pmā Meeting created in Teams calendar, link sent āNotifications & Monitoring
Alert me in Teams when a Jira ticket is assigned to meā Notification rule created āPost daily standup reminders to #engineering at 9:45amā Recurring message scheduled āTroubleshooting
Permission denied? Teams permissions require admin consent from your Microsoft 365 admin. Share the app manifest with your IT team.
Team not found? Team names are case-sensitive. Use the exact display name from Teams.
Message not delivered? Check the bot has been added to the team/channel. Admins must allow external apps in Teams admin center.
Features
Channel messaging
Post messages and updates to Teams channels programmatically
Direct messages
Send DMs to team members from your AI assistant
File management
Access and share SharePoint files directly from Teams
Channel monitoring
Get summaries of activity in specific channels
Meeting scheduling
Create Teams meetings with calendar integration
Custom notifications
Set up automated alerts and scheduled messages
Use Cases
Team updates
Post automated deployment, release, and status updates to channels
File sharing
Find and share SharePoint files via natural language
Meeting coordination
Schedule Teams meetings and manage attendees from chat
Channel monitoring
Get summaries of what happened in key channels while away
Setup Guide
Requirements
- āMicrosoft 365 tenant with Teams enabled
- āAzure subscription for Bot Framework registration
- āAzure AD (Entra ID) app registration
- āIT/Admin approval for custom app deployment
- āOpenClaw running on a server accessible from Azure
Register an Azure AD application
In the Azure Portal, go to Azure Active Directory > App registrations > New registration. Configure it as a multi-tenant app with Web platform. Note the Application (client) ID and create a client secret.
Create a Bot Framework registration
In Azure Portal, create an Azure Bot resource. Link it to your Azure AD app registration. Configure the messaging endpoint to point to your OpenClaw server (https://your-server.com/api/teams/messages).
Configure OpenClaw
Add the Teams configuration to your OpenClaw config with the Azure AD app ID, client secret, and bot ID. Enable the Teams channel plugin.
Create the Teams app package
Create a manifest.json with your bot details, icons, and permissions. Package as a .zip file for upload to Teams.
Submit for IT approval
Upload the app package to your organizations Teams Admin Center. Work with IT to review permissions and approve for deployment.
Deploy to users
Once approved, publish to your orgs app catalog. Users can then add the assistant from the Apps section in Teams.
Configuration Example
teams: appId: "your-azure-ad-app-id" appSecret: "your-client-secret" botId: "your-bot-id" tenantId: "your-tenant-id" # Optional: restrict to single tenant
Limitations
- ā ļøRequires IT admin approval in most organizations
- ā ļøInitial Azure setup has multiple steps
- ā ļøBot must be published to your orgs app catalog
- ā ļøSome features require Teams Premium or specific M365 licenses
Frequently Asked Questions
How do I get IT approval for this?
Prepare a security review document covering: data handling (OpenClaw processes data on your infrastructure, not third-party), authentication (uses your existing Azure AD), compliance (supports audit logging), and access control (you control who can use it). Most IT teams appreciate that its self-hosted rather than a SaaS dependency.
Does it work with Microsoft 365 GCC or GCC High?
Yes, with additional configuration. Government cloud deployments require specific Azure endpoints and may have additional compliance requirements. Contact your Microsoft representative for guidance.
Can I restrict which users can access the assistant?
Absolutely. Use Azure AD groups to control access. You can also configure allowedUsers in OpenClaw to restrict by Azure AD user ID or email domain.
Is conversation data stored by Microsoft?
Teams message data is subject to your M365 retention policies. OpenClaw processes messages but can be configured to not retain conversation history. Your data stays in your infrastructure.
Can it access SharePoint and OneDrive files?
Files shared directly in Teams chat are accessible. For broader SharePoint/OneDrive access, configure additional Microsoft Graph API permissions in your Azure AD app.
What about data residency requirements?
Since OpenClaw runs on your infrastructure, you control data residency. Deploy to your preferred Azure region or on-premises to meet GDPR, data sovereignty, or industry-specific requirements.
How does this compare to Microsoft Copilot?
Microsoft Copilot is Microsofts built-in AI. OpenClaw gives you a self-hosted alternative with full control over the AI model, prompts, integrations, and data. Many organizations use both for different purposes.
Can multiple departments have different assistants?
Yes. Deploy multiple bot registrations with different configurations. IT could have a technical assistant while HR has one trained on people policies.
š„ Your AI should run your business, not just answer questions.
We'll show you how.Free to join.
Related Integrations
š Learn More
OpenClaw Self-Audit: The Prompt That Checks Your Own Security Setup
Most people set up OpenClaw, lock things down as best they can, and never check again. Meanwhile, configs drift, updates change settings, and new integration...
OpenClaw Installation Guide ā All Platforms (Linux, macOS, Unraid)
Complete installation guide covering gateway setup, Ollama integration, systemd services, and troubleshooting common setup errors like ECONNREFUSED and model loading issues.
How to Connect Gmail to Your AI Assistant (Complete Integration Guide)
Turn Gmail into an AI-powered inbox. Summarize threads, draft replies, auto-categorize messages, and search your email with natural language.
Tabnine vs GitHub Copilot
Privacy-first AI coding vs ecosystem integration
š Your AI should run your business.
Weekly live builds + template vault. We'll show you how to make AI actually work.Free to join.
Join Vibe Combinator ā