Oliver Kieselbach
7abbd59333
Reverts: -8dacce5c"chore(backend): bump optional NuGet patches + fix SYSLIB0057" -2f68fe69"chore(backend): upgrade Functions from .NET 8 to .NET 10 isolated" After deploy succeeded and the Flex Consumption stack was switched to .NET 10 Isolated in the portal, the dotnet-isolated worker died on every boot with: dotnet exited with code 150 (FrameworkMissingFailure) and "Exceeded language worker restart retry count for runtime:dotnet-isolated". The deployed package was correct (TFM net10.0, FrameworkReference 10.0.0, all package bumps applied) and the runtime stack property was set to dotnet-isolated 10.0, but the .NET 10 runtime is not present on the Flex Consumption stamp in West Europe even though Microsoft lists DOTNET-ISOLATED|10.0 as supported. Restart and stop+start did not help. Recovery sequence: 1. Stack switched back to .NET 8 Isolated (manual portal action). 2. Re-deployed last known-good net8.0 commit637bd9a1via temp branch rollback-net8 (now safe to delete). 3. /api/health back to 200. Follow-ups: - Re-apply security fixes (DataProtection 10.0.7 pin GHSA-9mv3-2cwr-p262, SYSLIB0057 X509CertificateLoader migration) on net8.0 in a separate PR. - Open Microsoft support: ".NET 10 Isolated worker on Flex Consumption WestEurope fails with FrameworkMissingFailure despite stack listed as supported." 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.