> For the complete documentation index, see [llms.txt](https://docs.autopilotmonitor.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.autopilotmonitor.com/troubleshooting-and-support/faq.md).
# FAQ
## General
What is Autopilot Monitor?
Autopilot Monitor gives IT admins real-time visibility into Windows Autopilot enrollments. A lightweight, temporary agent runs on devices during enrollment and streams events to a web portal where you can watch progress live, diagnose failures with automated rule analysis, and review historical sessions. See [How Autopilot Monitor Works](/getting-started/how-it-works.md).
Which Autopilot scenarios are supported?
**User-Driven** and **Pre-Provisioned** (White Glove) Windows Autopilot flows are fully supported, as are self-deploying/kiosk profiles. **Autopilot Device Preparation** is supported in early testing.
Is Autopilot Monitor free?
Yes — the **Community plan is free and stays free**. It is currently in Private Preview (access after approval, see [Requirements & Access](/getting-started/requirements-and-access.md)). A commercial **Enterprise plan** is coming later for organizations that need more — see [Plans](/plans.md).
Where is my data stored?
Session data is stored in Azure, **West Europe** region (Azure Functions + Azure Table Storage). Data retention is [configurable per tenant](/reference/settings.md#data-management) (default 90 days), and a tenant can [offboard](/reference/settings.md#danger-zone) — irreversibly deleting all its data — at any time. Diagnostics packages can be kept entirely in **your own** Azure Blob Storage.
## Setup & Agent
How do I deploy the agent?
Via an Intune platform script — the [Deploy the Agent](/getting-started/deploy-the-agent.md) guide covers it step by step, including the safety guards and a dry-run tester.
Does the agent run permanently on the device?
No. The agent only exists during the enrollment window: it self-destructs after completion, stops at its 6-hour maximum lifetime, and — as an unconditional backstop — removes itself 48 hours after installation no matter what. It never runs as a persistent background service. See [Agent Lifecycle & Security](/concepts/agent-lifecycle-and-security.md).
What data does the agent collect?
Enrollment telemetry only: ESP phases, app and script installations, IME log entries, device information, performance snapshots, and security posture. It does **not** collect personal user data, user files, or browsing history. Optional collectors (geo location, software inventory, diagnostics package) are controlled by your tenant settings. See [the full list](/concepts/agent-lifecycle-and-security.md#what-data-is-collected).
How does the agent authenticate?
With the device's **MDM client certificate** issued by Intune, over TLS. The backend additionally validates each device against your Intune tenant (Autopilot registration or corporate identifiers) before accepting any data — only devices under your management can send telemetry. See [Authentication](/concepts/agent-lifecycle-and-security.md#authentication).
## Portal & Features
What are Gather Rules and Analyze Rules?
**Gather Rules** collect custom evidence from devices during enrollment (registry, WMI, files, allow-listed commands). **Analyze Rules** automatically evaluate every session and surface findings with explanations and remediation steps. They work best together — see [How Rules Work Together](/rules/overview.md).
Can I export or download diagnostics data?
Yes — when the [Diagnostics Package](/troubleshooting-and-support/diagnostics-and-log-collection.md) feature is enabled, each session detail view offers a download of the collected log bundle. Session reports and timeline exports are available from the session's **Report** action.
## Troubleshooting
The agent is deployed but I don't see any sessions.
Work through the checklist in [Common Problems → No sessions appear](/troubleshooting-and-support/common-problems.md#no-sessions-appear-in-the-portal).
A session shows "In Progress" but the enrollment already finished.
The completion signal was missed — for example the device rebooted before the agent could detect the final state. The session resolves automatically: after the configured session timeout (default 5 hours) the backend reclassifies it from its evidence to **Awaiting User** or **Incomplete** (a timeout is no longer treated as a failure), and reconciles it to **Succeeded** if a genuine completion later arrives. You can also mark it succeeded/failed manually via [Admin Mode](/concepts/roles-and-permissions.md#admin-mode). See [Sessions & Statuses → Timeouts](/concepts/sessions-and-statuses.md#timeouts-what-happens-to-stuck-sessions).
Where are the agent's own log files?
`%ProgramData%\AutopilotMonitor\Logs` on the device — startup, event collection, and backend communication are all logged there. Log verbosity is a [tenant setting](/reference/settings.md#agent-parameters). Note the logs are removed by self-destruct unless **Keep Log File** is enabled.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.autopilotmonitor.com/troubleshooting-and-support/faq.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.