> For the complete documentation index, see [llms.txt](https://docs.intuneassistant.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intuneassistant.cloud/intune-assistant/monitor/monitor-details.md).

# Monitor Details

## What Is This Page?

The **Monitor Details** page shows everything about a single monitor: its baseline, every resource it watches, and every drift it has detected. You arrive here by clicking **View** on a row in [All Monitors](/intune-assistant/monitor/all-monitors.md) or [Global Overview](/intune-assistant/monitor/global-overview.md).

## What You Will See

### Header

The monitor's name and description, a **Refresh** button, a **Delete Monitor** button, and a **Back** button.

### Info Cards

Four cards show: Status (Active/Inactive), Run Frequency, Mode, and whether the monitor runs as the app's own service principal or on behalf of a specific user.

### Stat Cards

Total Resources, Active Drifts, Resources with Drifts, and Compliant Resources.

### Monitor Information

Monitor ID, Tenant ID, when and by whom it was created, when and by whom it was last modified, and — if applicable — who it is running on behalf of.

### Baseline Configuration

The name and description of the baseline this monitor checks against, collapsed by default to three summary tiles: Total, Compliant, and With Drifts.

Expand it to see a searchable, paginated table of every monitored resource — its name, type, number of properties, and a drift-status badge. Click **View Details** on any resource to open a dialog with its full, raw property values.

### Detected Drifts

One expandable card per detected drift, showing the resource name, an Active/Fixed status badge, how many properties drifted, the resource type, and when it was first reported.

Expand a drift to see a side-by-side comparison of every drifted property: its **current value** versus its **desired value** (from the baseline). When there are no drifts, this section shows a green "No Drifts Detected" state.

If a drifted change is actually correct, click **Accept Drift** on that card and provide a justification. This updates the monitor's baseline to match the current value and marks the drift resolved — see [Drifts](/intune-assistant/monitor/drifts.md#accepting-a-drift) for more detail.

## How to Use It

* Click **Refresh** to reload the monitor's current state.
* Expand or collapse the Baseline Configuration and Detected Drifts sections as needed.
* Click **Delete Monitor** to remove it — a confirmation dialog warns this cannot be undone, and you'll be taken back to the monitors overview afterward.

{% hint style="warning" %}
This page does not offer a way to edit the monitor's schedule, mode, or which resources it watches. If you need to change what's monitored, delete this monitor and create a new one from [Add Monitor](/intune-assistant/monitor/add-monitor.md).
{% endhint %}

## Common Questions

**What's the difference between "Total Resources" and "Compliant Resources"?**\
Total Resources is everything the baseline captured. Compliant Resources is the subset that still matches the baseline exactly — the difference between the two is your active drift count.

**Where do I see exactly what changed?**\
Expand the relevant card under Detected Drifts. Every changed property is listed with its current value next to its desired (baseline) value.

**What does "Accept Drift" do?**\
It updates the monitor's baseline so the drifted properties now match the resource's current live values, and marks the drift resolved. Use it when the change was intentional and you want it to become the new expected state.

## Related Pages

* [All Monitors](/intune-assistant/monitor/all-monitors.md)
* [Global Overview](/intune-assistant/monitor/global-overview.md)
* [Add Monitor](/intune-assistant/monitor/add-monitor.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.intuneassistant.cloud/intune-assistant/monitor/monitor-details.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.