An advisory-defanged EspTerminalFailure (ContinueAnyway + AccountSetup entered) deliberately keeps the session non-terminal so the normal completion paths can still win. Session 8bc1180f showed the dead-end variant: AccountSetup/Apps failed (0x87d1041c), so AccountSetupProvisioningComplete can never arrive, the IME settle probe was starved by a never-started user app, and Hello was disabled - no completion path left. The session idled InProgress until the max-lifetime watchdog, which by design issues no session verdict. The advisory path now arms a 30-min AdvisoryCompletion deadline (AgentBoot- floored, not re-armed by enrichment duplicates). On fire the engine resolves the session either way: - Completed (through Finalizing) when the real-user conjunction holds: desktop_arrived (DAD-validated, defaultuser0/SYSTEM excluded at the detector) AND Hello resolved-or-policy-disabled AND the new ImeUserSessionCompletedUtc fact at-or-after AccountSetupEnteredUtc. The IME timestamp gate kills defaultuser0 ghosts - OOBE/technician IME sessions complete in the pre-AccountSetup frame and can never satisfy it. - Failed otherwise, un-defanging the advisory: enrollment_failed with reason=esp_terminal_failure and LastFailureTrigger=EspTerminalFailure so the EnrollmentTerminationHandler likely-stuck app promotion keeps firing. ImeUserSessionCompletedUtc is an additive nullable DecisionState fact (set-once in HandleImeUserSessionCompletedV1, serialized snapshot-compatible, surfaced in the signal census as ime_user_session_completed). DecisionCore.Tests 381/381 green. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Autopilot Monitor
Advanced monitoring and troubleshooting solution for Windows Autopilot deployments. Gain full visibility into every enrollment session with a detailed event timeline, fleet health dashboards, and session reporting. Define custom analysis rules to automatically detect issues and gather rules to collect targeted evidence. Retrieve diagnostics packages on demand, configure agent settings like auto-reboot behavior and automatic timezone adjustment — all managed centrally from the web dashboard.
Private Preview
Autopilot Monitor is currently running as a Private Preview. Visit autopilotmonitor.com to request access and learn more.
Overview
Autopilot Monitor provides real-time tracking, intelligent diagnostics, and automated troubleshooting for Windows Autopilot enrollment processes. It consists of:
- Bootstrap Script — PowerShell script deployed via Intune that starts monitoring early in the enrollment process
- Monitoring Agent — Lightweight .NET application that collects telemetry and evidence during enrollment
- Backend API — Azure Functions-based ingestion and processing pipeline
- Web Dashboard — Next.js application for real-time monitoring and fleet analytics
Architecture
For detailed information about the system architecture, components, and data flow, see Architecture Documentation.
Documentation
Full documentation is available at autopilotmonitor.com/docs
License
This project uses a split licensing model:
- MIT License — Agent (
src/Agent/) and Shared library (src/Shared/) — unrestricted use on end-user devices - AGPL-3.0 — Backend (
src/Backend/), Web Dashboard (src/Web/), and MCP Server (src/McpServer/) — server-side components remain open source
See LICENSE for full details.



