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

# Snapshots

## What Is This Page?

**Snapshots** lets you capture a point-in-time copy of selected Intune/Entra resource configurations, independently of creating a monitor. A snapshot becomes available to use as a baseline the next time you create a monitor.

A **snapshot job** is the run that produces the snapshot — it has its own status and timestamps. A **snapshot** is the resulting data: the list of resources captured. One successful job produces one snapshot.

## How to Use It

1. Click **New Snapshot** to open the creation dialog.
2. Give it a name and optional description, and choose which resource types to capture.
3. Submit — the snapshot job runs asynchronously and appears in the jobs table with a status of Not Started or In Progress.
4. Click **Refresh** at any time to update the table, or click the eye icon on a job to see its full details.

Once a job succeeds, you can:

* Click the monitor icon on that row to jump straight into [Add Monitor](/intune-assistant/monitor/add-monitor.md) using this snapshot as the baseline.
* Click the trash icon to delete the job and its snapshot data. A confirmation dialog warns this cannot be undone.

## What You Will See

Three stat tiles: Succeeded, In Progress, and Failed.

The **Snapshot Jobs** table lists each job with:

| Column                 | What It Shows                                                         |
| ---------------------- | --------------------------------------------------------------------- |
| **Name / Description** | What you named the snapshot                                           |
| **Status**             | Not Started, In Progress, Succeeded, Partial, or Failed, with an icon |
| **Resources**          | Number of resource types requested                                    |
| **Created**            | When the job was submitted                                            |
| **Completed**          | When the job finished, if it has                                      |
| **Actions**            | View, create monitor from this snapshot, and delete                   |

The details dialog shows the job's status, snapshot ID, timestamps, the requested resource types, and — once complete — the actual captured resources (name and type), with a prompt to create a monitor from it.

If you have no snapshots yet, the table is replaced with a call-to-action to create your first one.

## Common Questions

**Why would I take a snapshot without immediately creating a monitor?**\
To capture a baseline now (for example, right after a change window) and decide later whether to turn it into an ongoing monitor.

**What happens if I delete a snapshot job that a monitor is using as its baseline?**\
Deleting a snapshot job only removes the job and its standalone snapshot record — it does not affect a monitor that was already created from it, since the monitor stores its own baseline at creation time.

## Related Pages

* [Add Monitor](/intune-assistant/monitor/add-monitor.md)
* [All Monitors](/intune-assistant/monitor/all-monitors.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/snapshots.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.