> For the complete documentation index, see [llms.txt](https://docs.vectra.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vectra.ai/release-notes/respond-ux-rux-1/april-2025-release-notes.md).

# Apr 2025 Release Notes (RUX)

### The Respond UX April release (2025.04) includes:

**Improved Search by Sensor Name**

We've enhanced the search functionality on the Detections page to support searching by Sensor Name instead of the internal Sensor LUID. This update addresses customer feedback and makes it easier to find detections associated with specific sensors using recognizable names.

**Enhanced Detection for Copilot Abuse in M365**

In response to strong customer interest, we’re expanding protection against potential abuse of Microsoft Copilot. In addition to the existing M365 Suspicious Copilot Access detection (which flags access from unusual locations), we’re introducing a new detection: M365 Copilot Sensitive Data Discovery. This identifies attacker behavior attempting to locate sensitive documents through Copilot in Microsoft 365.


---

# 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://docs.vectra.ai/release-notes/respond-ux-rux-1/april-2025-release-notes.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.