Phase 6 (POST /api/agent/register-session with retry, outcome-based exit-code mapping, on-failure mTLS+API-client disposal) moves into Runtime/BackendSessionRegistration.cs. SessionRegistrationOutcomeResult is the discriminated outcome — Continue with the live SessionRegistrationResult (consumed downstream by PostSessionStartedSignal, PostAdminPreemptionSignal, WireTelemetryServerResponse, HandleAdminAction) or Exit with the V1-parity codes (6 = AuthFailed, 7 = anything else; the diag skill keys on the distinction in Scheduled-Task history). Disposal of mtlsHttpClient + auth.BackendApiClient on registration failure is preserved inside the factory, matching the original inline behaviour. RunAgent's Phase 6 block shrinks from ~20 lines to 8 lines (factory call + result destructuring). Tests: 4 new BackendSessionRegistrationTests (Exit-6, Exit-7, Continue, null-arg validation). Existing SessionRegistrationHelperTests cover the underlying retry/outcome behaviour. Full V2.Core suite 757/758 (1 known RecoveryPathTests threading flake, passes solo). 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.



