Table of Contents

Diagnostics overview

There are two Teams bots in the platform, and they do different jobs. Keeping them separate is deliberate: the diagnostic bot is a read-only window onto the Reignite control plane, while the Teams bot is a multi-tenant service that stores its own installation records.

Component Job Repository
Diagnostic Bot Teams-facing diagnostics: read control-plane status, start an asynchronous diagnosis, render adaptive cards. Read-only. diagnostic-bot
Teams Bot Multi-tenant Teams bot service for Automaton; per-installation records in SQL Server. teams-bot
Control plane The API endpoints the diagnostic bot reads and asks to start a diagnosis. api
Media Bridge Windows-hosted Teams media path: joins a call, streams PCM audio, publishes a transcript via Azure Speech. media-bridge
Diagnostics Lab Experimental harness for exercising diagnostics with chaos and control-plane scenarios. diagnostics-lab
flowchart LR
  TeamsUser["Teams user"] --> BotFramework["Bot Framework"]
  BotFramework --> DiagnosticBot["Diagnostic Bot"]
  DiagnosticBot --> API["Reignite API"]
  API --> SQL[(Azure SQL Server)]
  BotFramework --> TeamsBot["Teams Bot"]
  TeamsBot --> SQL
  MediaBridge["Media Bridge"] --> Speech["Azure Speech"]
  MediaBridge --> Teams["Microsoft Teams"]
  Lab["Diagnostics Lab"] -.->|"experiments"| API

Security boundaries

  • Inbound Teams activities are JWTs. The diagnostic bot validates the Bot Framework token, the issuer and the audience (TeamsBot:BotAppId). A misconfigured deployment fails at startup rather than accepting tokens minted for another bot.
  • The bot's control-plane calls use a Bearer token. The token in the bot's DiagnosticsControlPlane:ApiToken must match the API deployment's expected token.
  • The bot is read-only. It can read status and start an asynchronous diagnosis; it never issues a destructive command.
  • Replies are posted, not returned in the HTTP body. Bot Framework treats the response to POST /api/teams/bot as an acknowledgement. The bot returns an empty 200 and posts the activity through the Bot Connector. A connector failure is logged, never rethrown, so Teams cannot replay the activity and start a duplicate diagnosis.
  • The Teams bot is least-privilege. Its DbContext maps only the teams schema it needs; it does not use the API's full SpeContext.