Teams

Crew can run as a Microsoft Teams bot. DM your agent from Teams with streaming replies and a typing indicator.

The Microsoft Bot Framework pushes activities to an endpoint you host. Crew:

1. Registers an inbound route: POST /api/messaging/teams
2. Validates every request's Authorization: Bearer <jwt> against Bot Framework signing keys before processing
3. Fast-acks with 200, runs the agent turn in the background, then sends the reply via the Bot Connector REST API

• A public HTTPS URL reaching your gateway (reverse proxy, dev tunnel, or public VM)
• The Teams extra installed: pip install "kirocrew[teams]"
• An Azure Bot registration with a Microsoft App ID and secret

1. Register an Azure Bot in the Azure Portal — create an Azure Bot resource, note the App ID, create a client secret, add the Microsoft Teams channel, and set the messaging endpoint to https://<your-host>/api/messaging/teams
2. Open Settings → Channels → Teams in the dashboard
3. Paste the App ID, App Password (client secret), and Tenant ID (or leave blank for multi-tenant)
4. Add your Azure AD email or object ID to the Allowed emails list
5. Click Save — the status badge turns green when the credentials validate

Then side-load a Teams app package (Developer Portal → new app → Bot with your App ID, scope Personal) and DM the bot.

In ~/.kiro/crew/.env:

MICROSOFT_APP_ID=<your app id>
MICROSOFT_APP_PASSWORD=<your client secret>
MICROSOFT_APP_TENANT_ID=<tenant id or leave unset>

In ~/.kiro/crew/config.json:

{
  "teams": {
    "enabled": true,
    "allowed_emails": ["you@yourcompany.com"]
  }
}

Install the Teams extra: pip install "kirocrew[teams]"

Then: kirocrew restart

• Webhook is exempt from dashboard cookie gate — performs its own Bot Framework JWT validation
• Authorization is deny-by-default on both the email allowlist and conversation scope (personal only)
• All denials recorded in the security event log
• App Password is marked sensitive and never logged

• 1:1 personal chat only — no team channels, group chats, or @mention handling
• No Adaptive Cards / tappable buttons (options delivered as plain text)
• No token-by-token streaming — typing indicator shown, final answer delivered in one message (chunked if long)