Capabilities
| Feature | Supported |
|---|---|
| 1:1 chat | Yes |
| Channel messages | Yes |
| Adaptive Cards | Yes |
| Slash commands | Yes |
| File uploads | Yes |
| Teams meetings | No |
| OAuth install | Yes |
| Multi-tenant | Yes |
Setup
Register an Azure Bot
Go to portal.azure.com and create an Azure Bot resource.
- Set the messaging endpoint to:
https://your-domain.com/webhooks/teams - Choose Multi-tenant for use across multiple organizations
Create a Teams App
Use Teams Developer Portal or App Studio to create a Teams app manifest:
Environment Variables
Microsoft App ID (Bot Framework Application ID).
Microsoft App Password (client secret).
Azure AD Tenant ID. Use
common for multi-tenant apps.Comma-separated Team IDs to restrict access.
Comma-separated Channel IDs to restrict access.
Configuration Example
- .env
- settings.yml
Adaptive Cards
profClaw sends Adaptive Cards for rich interactive responses:Notes
- Requires a public HTTPS webhook URL - no socket/polling mode available.
- Bot Framework handles authentication with Microsoft’s OAuth.
TEAMS_TENANT_ID=commonallows the bot to work across any Microsoft 365 organization.- Single-tenant mode: set
TEAMS_TENANT_IDto your organization’s tenant ID. - The bot must be in the same Teams app as the channel for it to respond.
Related
- Chat Providers Overview - Compare all 27 supported channels
- Slack - Slack is the recommended alternative for teams not on Microsoft 365
- profclaw tunnel - Expose your local server for development webhook testing
- profclaw channels - Enable and test the Teams connection from the CLI