Oliver Kieselbach
aadf18bbf8
Motivating incident — session 8f2bef72 (2026-05-19, OK's VM test): a Function App cold-start triggered by a fresh deploy stalled the agent's single-shot GetAgentConfig call for ~60 s; the client gave up, RemoteConfigService silently fell back to built-in defaults (ConfigVersion=0, SelfDestructOnComplete=true, DiagnosticsUploadMode=Off), and the entire enrollment ran the wrong policy with no wire-visible trace of the degraded mode. ReportAgentError (the emergency channel) was also racing the cold start and lost to 499. Three fixes: 1. Retry FetchConfigAsync on transient errors (3 attempts; 10/30/60 s linear backoff). BackendAuthException still bails immediately — 401/403 won't change with a retry and an operator needs the AuthCertificateRejected / DeviceNotRegistered distress signal fast. EmergencyReporter only fires on the final attempt to give the function time to warm. Live ServerAction rotate_config keeps single-shot so it doesn't block the action handler for ~100 s. 2. agent_started DataJson now carries configVersion + remoteConfigFetched + remoteConfigOutcome (Succeeded / FromCache / UsedDefaults / NotAttempted). Operators can tell at a glance whether the agent is running on fresh tenant config vs. defaults vs. stale cache without inferring from absence of expected tenant-controlled knobs. 3. New remote_config_fetch_failed Warning event emitted right after agent_started when the fallback path was taken. Carries attempts, failureType, failureMessage (truncated 512), and authStatusCode when relevant. Closes the blind spot — the only prior trace was a Warning in the local agent log which is gone after a SelfDestruct cleanup. V2 Agent suite: 1092/1092 (+16: 7 retry behaviour + 9 emitter shape). 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.