> 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/identity/administration/roles/role/audit.md).

# Role Audit

The Audit tab lists the directory audit events Entra recorded against this role over the last 30 days, so a change in who holds a role can be traced back to who made it and when. It opens from the [View Individual Role](/user-documentation/identity/administration/roles/role.md) header tabs and needs a single tenant selected.

Events come from the tenant's own audit log, which Entra retains for a limited period, so an older change may have aged out even though it sits inside the 30 day window.

## Table Details

| Column           | Description                                                                             |
| ---------------- | --------------------------------------------------------------------------------------- |
| Date             | When the event was recorded, newest first.                                              |
| Activity         | What happened, as Entra names it, for example adding a member to a role.                |
| Category         | The area of the directory the event belongs to.                                         |
| Result           | Whether the operation succeeded or failed.                                              |
| Initiated By     | The user principal name of whoever carried it out, where a user was responsible.        |
| Target Resources | What the event acted on, which for these events is the role and the principal involved. |

Selecting a row opens the complete event as it was recorded, including the old and new values Entra captured, which is where the detail of a change lives when the summary columns are not specific enough.

***

## 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/identity/administration/roles/role/audit.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.