> 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/getting-started/portal-setup.md).

# Portal Setup

Before the agent can send any data to the portal, a few one-time steps are required in the portal itself.

## 1. Sign in — the first user becomes Tenant Admin

Open the portal and sign in with your Microsoft Entra ID account. The very first user to sign in for your organization is automatically granted **Tenant Admin** rights for your tenant.

{% hint style="info" %}
The Tenant Admin can later promote other users via **Settings → Access Management**. Users without a role only see the **Progress Portal** — a simplified view for tracking a specific device by serial number — and have no access to session details, diagnostics, or configuration. See [Roles & Permissions](/concepts/roles-and-permissions.md).
{% endhint %}

## 2. Enable Autopilot Device Validation

Navigate to **Settings → Configuration** and enable **Autopilot Device Validation**. This is required before the agent is permitted to send any session data — without it, all agent uploads are rejected.

{% hint style="warning" %}
**Why is this required?** The Autopilot device check ensures that only devices registered in your Intune tenant can register sessions, preventing unintended data from reaching your tenant. Enabling it requires admin consent for the Microsoft Graph permission `DeviceManagementServiceConfig.Read.All` (read-only), and it is your explicit confirmation that the agent may collect and transmit enrollment telemetry on behalf of your organization.
{% endhint %}

## 3. Ready

That's it — the portal can now receive data. [Deploy the agent](/getting-started/deploy-the-agent.md) via Intune, and sessions will start appearing on the dashboard as soon as devices begin enrolling.

## Recommended configuration

After the basic setup, consider enabling these features to get the most out of Autopilot Monitor:

1. **Agent Settings → Geo Location Detection + Set Timezone Automatically** — sets the device timezone correctly during enrollment. Without a location sensor, Windows defaults to Pacific Standard Time; this fixes the "every English device thinks it's in Redmond" effect and feeds the Geographic Performance view.
2. **Agent Analyzers** — enable the **Local Admin Analyzer** (configure your expected admin accounts to detect unauthorized local admins), **Software Inventory**, and the **Vulnerability Analyzer** for security insights during enrollment.
3. **Diagnostics Package** — automatically gathers log files from devices for troubleshooting. You choose the upload destination: your own Azure Blob Storage (Container SAS URL — data never leaves your tenant) or the built-in hosted storage (no storage account needed).

All settings are described in detail in the [Settings Reference](/reference/settings.md).


---

# 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/getting-started/portal-setup.md?ask=<question>&goal=<endgoal>
```

`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.