The dynamic-client registry is in-memory, and the MCP server is stateless with scale-to-zero and possibly multiple replicas. Between /oauth/register (called by the client) and /oauth/authorize (opened later in the browser) the container can sleep or a different replica can serve the request, wiping the registry. /authorize then hard-failed with "invalid_client — Unknown client_id — register via /oauth/register first". /oauth/callback already tolerates this cold-start case (registry wiped -> fall back to the redirect_uri host allowlist). Mirror that at /authorize: an unknown client_id now proceeds on the host-allowlist gate (+ mandatory PKCE S256) instead of dead-ending. Known client_ids still get the exact per-client redirect_uri match. No weakening of the security model -- the host allowlist and PKCE were always the real gate; client_id matching is defense-in-depth. Co-Authored-By: Claude Opus 4.8 (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.



