Skip to main content
Apragya AI
Docs · Integrations

Microsoft Teams: setup, notifications, and bot deployment

Connect Microsoft Teams to your tenant - OAuth flow with Azure AD, channel-mapping rules, bot deployment for agent-driven workflows.

The Microsoft Teams connector covers three jobs: outbound notifications from agents and apps, inbound message capture for tickets / CRM activity, and a deployable Apragya bot that surfaces approvals and HITL reviews inside Teams. All three share one OAuth setup with your tenant's Azure AD.

Connect Microsoft Teams

  • Sidebar > Integrations > Connectors > Microsoft Teams > Connect
  • Microsoft 365 admin consents to the Apragya AI app (Calendar.Read, ChannelMessage.Send, ChatMessage.Send, TeamMember.Read.All)
  • Pick the default team + channel for un-routed notifications (acts as the catch-all)

Configure channel mappings

Sidebar > Integrations > Channel Mappings. Map agent events, app events, or notification categories to specific Teams channels. The mapping is many-to-one - lots of events can land in one channel, but each event has exactly one home.

  • Per agent: invoice.review.required -> #ap-team
  • Per app: crm.deal.won -> #wins-celebration
  • Per category: hitl.escalation -> direct message to the named approver

Deploy the Apragya bot

Sidebar > Integrations > Microsoft Teams > Deploy Bot. Pushes the Apragya bot to your Teams tenant. Once deployed, users can approve HITL reviews, accept invoice line items, and trigger agent runs from Teams without switching to the Apragya web app.

Inbound capture (turning Teams messages into Apragya tickets) requires the Graph API ChannelMessage.Read.All permission - your Microsoft 365 admin needs to consent to this explicitly. Without it, the connector still does outbound notifications + bot deployment, just not inbound message capture.

Limits to know

  • Outbound rate: 50 messages/sec/tenant per Microsoft Graph throttling
  • Bot adaptive cards: limited to 25 actions per card; longer flows need a multi-step bot conversation
  • File attachments: cap at 250MB per file (Microsoft Graph upload session)

Need help building this? Talk to a real engineer

← All docs
Ask Vippy anything