[ ABORT TO HUD ]
SEQ. 1
SEQ. 2
SEQ. 3

Runtime Execution Loop & State Machine

⚙️ Copilot Studio Runtime & Dynamic Chaining⏱ 15 min⭐ 150 BASE XP⌨ HANDS-ON LAB

The Copilot Studio Runtime Engine

The Copilot Studio Runtime operates on an event-driven adaptive dialog engine. When an activity (message, event, or invoke) arrives from any channel (Teams, Web, M365), the runtime pipeline executes four discrete phases:

  1. Intent Classification: Fast embeddings rank matching topics or trigger generative dynamic chaining.
  2. Entity Extraction & Slot Filling: Extracts recognized entities (dates, tracking IDs, amounts) and assigns them to typed variables.
  3. Adaptive Dialog Execution: Executes step nodes, conditions, and tool executions.
  4. Response Generation: Emits adaptive cards, speech SSML, or streaming tokens.
⌨ HANDS-ON LABInspect Copilot Session State & Memory Variables
⭐ +150 XP

Query active Copilot Studio conversation session state and verify runtime system variables like System.Conversation.Id and User.DisplayName.

1Query session execution telemetry using PAC CLI.
lab-sandbox — simulated environment
INFINITY LAB SANDBOX v2.6 — simulated shell
Type the command for the current objective. Helpers: "hint", "solution", "clear".
$
OBJECTIVE 1 / 1 — type "hint" if stuck
SYNAPSE VERIFICATION
QUERY 1 // 1
What is the scope of a Topic variable in the Copilot Studio Runtime?
Persists permanently across all user sessions
Scoped only to the execution lifecycle of the specific active topic
Shared across all bots in the tenant
Accessible by external HTTP webhooks without authentication