Microsoft Teams

v0.1 status — beta

The Teams adapter is code-complete and unit-tested but not yet validated end-to-end against real Azure AD tenants and enterprise policies. If you deploy it to a production Teams workspace and hit issues, file an issue — real-world test reports are the fastest path from beta to ready.

Teams integration uses the Microsoft Bot Framework — the same infrastructure that powers enterprise bots on Teams, Outlook, and Skype for Business.

What You Get

• Direct messages and channel mentions
• Adaptive Card rich replies (when needed)
• Works across Teams, Outlook, and Office 365 Groups
• Enterprise SSO-friendly (tied to Azure AD)

1. Register the Bot in Azure

1. Sign in to the Azure Portal with a work or school account
2. Create a new Azure Bot resource:
   • Bot handle: e.g. aibutler-yourorg
   • Subscription and Resource group: pick any
   • Type of App: Multi Tenant
3. In Configuration, copy the Microsoft App ID
4. Click Manage → Certificates & secrets → create a new Client secret and copy the value (shown once only)

2. Connect to Teams

1. In the bot resource, go to Channels
2. Click Microsoft Teams → agree to the terms → Apply
3. Under Messaging endpoint in Configuration, enter:

   https://your-host/webhook/teams

3. Store Credentials

aibutler vault set teams_app_id YOUR_APP_ID
aibutler vault set teams_app_password YOUR_CLIENT_SECRET

4. Enable the Channel

configurations:
  channels:
    active:
      - teams

5. Install to Teams

You need an app manifest to install the bot in a Teams workspace:

1. Use Developer Portal for Teams or Teams Toolkit
2. Create a new app with the App ID from step 1
3. Upload the app package (.zip) to your Teams tenant via Apps → Manage your apps → Upload a custom app

6. Restart

aibutler run

You should see teams: tools registered in the logs.

Features

Feature	Supported
1:1 chats	Yes
Group chats	Yes
Team channels	Yes (@mentions required)
Adaptive Cards	Yes
File attachments	Yes
Voice messages	No
Streaming replies	No
SSO	Inherited from Azure AD

Troubleshooting

Bot doesn’t show up in Teams. Double-check the app manifest matches the Azure Bot App ID, and that the tenant admin has approved custom app uploads (Teams admin center → Teams apps → Setup policies).

401 Unauthorized in logs. The client secret expired or was copied incorrectly. Regenerate it in Azure → Certificates & secrets.

Messages delivered but no reply. Teams requires HTTPS for the messaging endpoint. Self-signed certs won’t work — use a real cert via Let’s Encrypt or place the bot behind a reverse proxy like Caddy.