> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/release-notes/enterprise/admin-console/admin-console-17.2.2.md).

# Admin Console 17.2.2

Released on April 9, 2025

### New Features

* [Azure Monitor Logs](/enterprise-guide/event-reporting/microsoft-sentinel/azure-monitor.md) SIEM integration

### Improvements

* Simplified [user statuses](/enterprise-guide/user-management-and-lifecycle.md#user-status)
* Risk Management Dashboard: ignored benchmarks can now be un-ignored
* The **Configuration** tab in the left-hand navigation bar is renamed to **Custom Branding**
* Compliance Reports now allows searching by user name in addition to user email
* Improved performance when adding users via SCIM
* MSPs can now configure custom branding for MCs

### Bug Fixes

* Resolved issue that caused the console to freeze when importing users from a TXT file
* Resolved issue that incorrectly allowed teams to be added to an admin role
* Resolved a **Reporting and Alerts** issue that caused webhook configuration to not save
* Resolved an issue that impacted Risk Management Dashboard report download
* Fixed various UI and styling issues


---

# 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.keeper.io/release-notes/enterprise/admin-console/admin-console-17.2.2.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.
