How It Works
Quick Start
RFC Status: Draft | Priority: High | Timeline: Q2 2026
Overview
This RFC proposes Microsoft Teams as a first-class PraisonAI messaging channel for enterprise RFPs and Microsoft 365-first organisations.Success Criteria
- Full BotOS protocol compatibility
- Multi-agent deployment in Teams channels
- Enterprise security and compliance features
- Rich message formatting and adaptive cards
- SSO and Azure AD integration
Architecture
Configuration
Implementation Plan
| Phase | Duration | Scope |
|---|---|---|
| 1 — Core Messaging | 4 weeks | Bot Framework SDK, send/receive, BotOS protocol |
| 2 — Advanced Features | 3 weeks | Adaptive cards, Azure AD, audit logging |
| 3 — Production | 2 weeks | Test suite, security audit, documentation |
Security
| Layer | Implementation |
|---|---|
| Authentication | Azure AD OAuth 2.0 |
| Encryption | TLS 1.3 + Azure Key Vault |
| Audit trail | Azure Monitor + PraisonAI logs |
| Rate limiting | Azure API Management |
Best Practices
Use Azure Key Vault for credentials
Use Azure Key Vault for credentials
Store
TEAMS_APP_ID and TEAMS_APP_PASSWORD in Key Vault — never commit secrets to source control.Deploy AgentTeam across channels
Deploy AgentTeam across channels
Use
AgentTeam for multi-agent Teams channels with session management per conversation.Enable SSO for enterprise tenants
Enable SSO for enterprise tenants
Configure Azure AD SSO so users authenticate with existing Microsoft 365 credentials.
Use adaptive cards for approvals
Use adaptive cards for approvals
Human-in-the-loop workflows map cleanly to Teams adaptive card submit actions.
Related
Messaging Channels Strategy
Overall messaging platform roadmap
Agent Server
Deploy agents with HTTP APIs
Review & Feedback: Comment on GitHub issue #1311 with questions or suggestions.

