Oliver Kieselbach 22427e24c5 perf(web,backend): finish off the duplicate-fetch + response-header fixes
Post-deploy re-validation in the browser surfaced two issues that the
previous commit did not actually solve:

- Timing-Allow-Origin was still missing on every API response (curl
  confirmed) and X-Correlation-ID was missing too — a preexisting bug.
  Both middlewares used httpContext.Response.OnStarting() to attach the
  header, but that callback is not reliably triggered in the .NET 8
  isolated worker: the host bridges the worker's response to the wire,
  so OnStarting fires on a shadow object that never reaches the client.
  UserRateLimitMiddleware already writes X-RateLimit-* directly on
  Response.Headers before calling next(), and those headers do come
  through in production. Switching both header-emitting middlewares
  to that pattern.

- /dashboard kept firing /api/config/<t>/feature-flags twice. The
  earlier dep-stabilization on useTenantSecurityConfig was incomplete:
  the effect fires once on initial render with user=null (deps
  [tenantId, undefined, undefined, undefined]) and once after AuthContext
  resolves user (deps [tenantId, bool, bool, role]) — two distinct dep
  tuples, two fetches. The user=null path also bypassed the role gate
  (the guard was `if (user && ...) return`). Adding `!user` to the
  early-return at the top of the effect collapses to one fetch and
  also drops the would-be 401 we were producing during the loading
  window.

Backend tests 1058/1058, web vitest 249/249, tsc clean.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-07 14:01:09 +02:00
2026-04-29 09:00:52 +02:00
2026-03-17 18:24:01 +01:00
2026-03-26 07:02:33 +01:00
2026-05-07 08:51:22 +02:00

Autopilot Monitor

Status License Website

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.

S
Description
Windows Autopilot & Intune enrollment monitoring: live session timelines, fleet health, diagnostics, and an MCP server for AI-assisted troubleshooting.
Readme AGPL-3.0 60 MiB
Languages
C# 72.7%
TypeScript 25.7%
PowerShell 1%
JavaScript 0.5%