Table of Contents

Diagnostic bot request

How a Teams message becomes a control-plane read or an asynchronous diagnosis.

sequenceDiagram
  autonumber
  participant p_teams_user as Teams User
  participant p_bot_framework as Bot Framework
  participant p_diagnostic_bot as Diagnostic Bot
  participant p_api as Reignite API
  participant p_sql_database as Azure SQL Server
  p_teams_user->>p_bot_framework: Sends a message to the diagnostic bot [Teams]
  p_bot_framework->>p_diagnostic_bot: POST /api/teams/bot with a Bot Framework JWT [HTTPS]
  p_diagnostic_bot->>p_diagnostic_bot: Validate the JWT and route the intent [in-process]
  p_diagnostic_bot->>p_api: GET /api/diagnostics/control-plane/* [HTTPS / Bearer token]
  p_api->>p_sql_database: Read control-plane state [EF Core]
  p_api->>p_diagnostic_bot: Return status or a diagnosis correlation id [HTTPS / JSON]
  p_diagnostic_bot->>p_bot_framework: POST /v3/conversations/{id}/activities [Bot Connector]
  p_bot_framework->>p_teams_user: Render an adaptive card [Teams]

The bot returns an empty 200 to Bot Framework and posts the reply through the Bot Connector. A connector failure is logged, never rethrown, so Teams cannot replay the activity and start a duplicate diagnosis.

Back to all flows

This diagram is generated from architecture/model.yaml. Edit the model, not this page.