> 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/drifts.md).

# Drifts

## What Is This Page?

**Drifts** lists every configuration drift IntuneAssistant has detected across all your monitors. A drift is a difference between a monitor's saved baseline and the resource's current, live state in Intune or Entra ID.

## How to Use It

Data is not loaded automatically — click **Load Drifts** to fetch the current list. You can cancel a load in progress, and click **Refresh** afterward to pull the latest results.

Once loaded, use the filter bar to narrow the list by:

* **Monitor** — show drifts from one monitor only
* **Status** — Active or Fixed
* **Resource Type** — the kind of Intune/Entra resource affected

Click **Show Details** on any drift card to expand a full before/after comparison of every property that changed.

### Accepting a Drift

If a detected change is actually correct — for example, someone intentionally updated a setting and the baseline should now reflect that — click **Accept Drift** on the drift card. You'll be asked to provide a short justification explaining why the change is being accepted; this is required and is recorded for audit purposes.

Accepting a drift updates the monitor's baseline so the changed properties now match the resource's current live values. The drift is then marked resolved, since there is no longer a difference to detect.

{% hint style="warning" %}
Accepting a drift is different from fixing the underlying resource. It permanently changes what the monitor expects going forward — use it when the current state is the one you want to keep, not as a way to temporarily silence an alert.
{% endhint %}

## What You Will See

A stats row shows Total Drifts, Active Drifts, Fixed Drifts, Total Monitors, and Monitors with Drifts.

Below the filter bar, each drift is shown as a card with:

* The affected resource's display name
* An **Active** / **Fixed** status badge
* Which monitor flagged it
* The resource type
* How many properties changed
* When it was first detected

Expanding a card shows every drifted property with its **current value** and **desired value** (from the baseline) side by side.

{% hint style="info" %}
Before you click **Load Drifts**, the page shows a "Ready to view configuration drifts" prompt rather than an empty list — this is different from loading and finding zero drifts.
{% endhint %}

## Common Questions

**What does "Fixed" mean for a drift?**\
The resource's live configuration now matches the baseline again, so the drift is no longer active.

**Can I accept a drift as the new expected state instead of reverting it?**\
Yes. Click **Accept Drift**, provide a justification, and the monitor's baseline is updated to match the current value. Use this when the change was intentional and you want the monitor to stop flagging it.

**What's the difference between fixing a drift and accepting it?**\
Fixing a drift means changing the resource in Intune/Entra back to match the baseline — the monitor will then report it as Fixed on its next check. Accepting a drift instead changes the baseline to match the resource, keeping the new configuration going forward.

## Related Pages

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