> For the complete documentation index, see [llms.txt](https://docs.cipp.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cipp.app/user-documentation/security/incidents/list-alerts.md).

# Alerts

Review Microsoft 365 security alerts across your tenants.

Security alerts raised across the selected tenant's Microsoft 365 security products, listed newest first. Use it to see what has fired recently without moving between the individual security portals, and to move an alert on once you have dealt with it.

## Table Details

| Column          | Description                                                                                        |
| --------------- | -------------------------------------------------------------------------------------------------- |
| Event Date Time | When the earliest activity behind the alert took place. The table is sorted on this, newest first. |
| Status          | Where the alert sits in triage: `new`, `inProgress` or `resolved`.                                 |
| Title           | The alert's title, describing what was detected.                                                   |
| Severity        | The severity assigned to the alert by the product that raised it.                                  |
| Category        | The category the alert was raised under.                                                           |

The Extended Info flyout adds **Involved Users**, the user accounts recorded as evidence on the alert, so you can see who it concerns without opening the security portal.

{% hint style="info" %}
Selecting All Tenants queues a background job that collects alerts from every tenant, and the page tells you it is still loading. Come back in a few minutes for a complete list.
{% endhint %}

## Table Actions

<table><thead><tr><th>Action</th><th>Description</th><th data-type="checkbox">Bulk Action Available</th></tr></thead><tbody><tr><td>Set status to in progress</td><td>Marks the alert as being worked on.</td><td>true</td></tr><tr><td>Set status to resolved</td><td>Closes the alert.</td><td>true</td></tr><tr><td>More Info</td><td>Opens the Extended Info flyout with the full details for the selected row.</td><td>false</td></tr></tbody></table>

***

## Feature Requests / Ideas

We value your feedback and ideas. Please raise any [feature requests](https://github.com/CyberDrain/CIPP/issues/new?template=feature.yml) on GitHub.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cipp.app/user-documentation/security/incidents/list-alerts.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.