V2 had drifted to a renamed bucket schema (installedApps/failedApps/...) plus nested perApp/byPhase. The nested objects were dead — no Web component or rule consumed them — and the renamed counters needed a fallback chain in every reader. Single flat schema is simpler: - Builder rewritten to emit only the flat V1 keys: installed/failed/ skipped/postponed (final), downloading/installing/pending (live), errorCount/deviceErrors/userErrors/hasErrors/isAllCompleted/ ignoredCount (aggregate helpers), plus name lists per bucket (installedNames/failedNames/skippedNames/postponedNames/pendingNames). perApp + byPhase removed. The includePerAppDetail flag is gone — all emits ship the same shape (live snapshots stay cheap because the names lists are short strings, not per-app timing objects). - ignoredCount needed a separate accessor: it lives on the live AppPackageStateList, not on the deduped phase-snapshot+live union used by the termination accessor. New ImeIgnoredCount property on DefaultComponentFactory + ignoredCountAccessor parameter on EnrollmentTerminationHandler.ctor (default () => 0 keeps existing test rigs unaffected). - ANALYZE-APP-007.dataField back to errorCount (flat), dist regenerated. - Web hooks (useSessionDerivedData, useProgressDerivedData) drop the V2 fallback chain — single-schema reads only. - Tests rewritten for V1 schema: counter validation, device/user error split, hasErrors/isAllCompleted bool helpers, name-list population per bucket. EnrollmentTerminationHandlerTests collapsed the three V2-perApp tests into one V1-counts+split-errors test; per-app timing detail now lives only in FinalStatusBuilder / final-status.json, not in the event payload. Per-transition emit cadence and ImmediateUpload=false on live snapshots are unchanged from the previous commit. Co-Authored-By: Claude Opus 4.7 (1M context) <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.



