> 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-threat-report.md).

# The Threat Report

The Threat Report is a point-in-time snapshot of a Microsoft tenant's overall security posture. Where the [Summary Report](/reports/the-summary-report.md) tracks change over time, the Threat Report captures where things stand right now.

## Common uses

* Cyber security risk assessments for prospective customers (a "pre-sales report").
* Quarterly business reviews with existing customers.
* Ongoing, consistent security updates through [Scheduled Reports](/reports/scheduled-reports.md).

## What the report includes

| Section                     | What it shows                                         |
| --------------------------- | ----------------------------------------------------- |
| Total Risk Detections       | Overall count of risk detections on the account       |
| Location of Risk Detections | Where those detections originated                     |
| Microsoft Secure Score      | The tenant's current Secure Score                     |
| Microsoft Identity Score    | The tenant's current Identity Score                   |
| Top 5 Risky Accounts        | The five accounts with the highest risk in the tenant |
| Inactive Accounts           | Accounts with no recent activity                      |

{% hint style="warning" %}
Inactive Accounts requires the tenant to have at least a Microsoft P1 license. Without P1, this section won't populate.
{% endhint %}

## Pre-sales use

Partners commonly request a Threat Report be run for a prospective customer before onboarding them, as part of a security assessment during the sales process — this works the same way whether the tenant is a paying customer or a prospect connected via GDAP/direct integration.

## A gotcha: Threat Report vs. Compliance Audit inactive-account counts

Support has seen cases where the Threat Report's Inactive Accounts count for a tenant doesn't match the Inactive Accounts check in a Compliance Audit for the same tenant, on the same day — sometimes by a large margin. This generally comes down to the two features using different scopes or definitions of "inactive" (for example, different lookback windows, or different license-gating), not a data error. If you need a number for a customer conversation, pick one report and be consistent about which one you're quoting, and don't assume the two should reconcile to the same figure.

{% hint style="warning" %}
The exact query logic and scope differences behind the Threat Report vs. Compliance Audit inactive-account counts weren't independently verifiable against the codebase this session. If this discrepancy comes up on a live tenant, confirm the specific cause with Augmentt Support rather than assuming which number is "right."
{% 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-threat-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.