> For the complete documentation index, see [llms.txt](https://helpdesk.augmentt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdesk.augmentt.com/reports/the-summary-report.md).

# The Summary Report

The Summary Report shows how a tenant's overall Microsoft 365 security posture has changed over time. Where the [Threat Report](/reports/the-threat-report.md) is a point-in-time snapshot, the Summary Report is the trend line.

{% hint style="info" %}
Some partners refer to this internally as the "why you're paying us" report — it's built to make the value of ongoing security work visible, not just to list current risk.
{% endhint %}

## What it's used for

* Explaining the security work done on an account during quarterly business reviews.
* Giving a customer consistent, recurring visibility into their security trend via [Scheduled Reports](/reports/scheduled-reports.md).
* Exporting a one-to-three month view of progress on demand.

## What the report includes

| Section                         | What it shows                                                             |
| ------------------------------- | ------------------------------------------------------------------------- |
| Total Prevented Incidents       | Count of incidents Augmentt identified and helped prevent over the period |
| MFA Status and change over time | How MFA coverage has trended                                              |
| Microsoft Secure Score          | Trend of the tenant's Secure Score                                        |
| Microsoft Identity Score        | Trend of the tenant's Identity Score                                      |
| Intercepted Risky Sign-ins      | Risky sign-ins flagged over the period                                    |
| Prevented Incidents             | Detail behind the top-line prevented-incident count                       |

## A note on the Monitored Events sections

Support has fielded questions where a customer reviewing the "Monitored Events" section of a Summary Report — risky sign-ins, risky countries/IPs, risky users — can't find the matching events when they look directly in the M365 tenant afterward. This is generally because the report reflects detections captured at the time they occurred; if a user's risk state is later remediated, dismissed, or ages out in Microsoft's own risk views, it can still show up in a historical Summary Report covering that period even though it's no longer visible live in the tenant. If the numbers on a report look inconsistent with what you see in the tenant today, check the date range on the report first — you're often looking at two different points in time, not two different sources of truth.

{% hint style="warning" %}
The precise data source and refresh timing behind each Summary Report section wasn't independently verifiable against the codebase this session. Treat the explanation above as the general pattern support has seen, and confirm specifics with Augmentt Support for a given discrepancy.
{% endhint %}


---

# 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://helpdesk.augmentt.com/reports/the-summary-report.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.