> 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/archived-rux-release-notes/2025-release-notes-rux/feb-2025-release-notes-rux.md).

# Feb 2025 Release Notes (RUX)

### The Respond UX February release (2025.02) includes:

**Provide Support for Authentication via OAuth**

Vectra supports both the existing Personal Access Token (PAT) and Oauth2 flow in v2.x. The Oauth2 access token will be valid for 6 hours after which it will expire, and a new token will need to be requested using the API client credentials. API client creation must be done in the Vectra UI only. Accessing v2.x APIs older than v2.5 works the same way it does for v2.5. The public postman collection has been updated for all v2.x versions.

**M365 GCC Support**

Vectra now supports Microsoft 365 Government Community Cloud (GCC) environments. While support previously existed for GCC-High and Azure AD customers, this update extends coverage to customers operating in GCC environments—commonly used by U.S. state, local, and federal agencies. By integrating with Microsoft’s GCC-specific endpoints, Vectra AI ensures secure and compliant log aggregation to provide complete visibility and threat detection across all Microsoft government cloud tiers.

**Cybereason EDR Support**

Vectra added support for ingesting EDR alerts from Cybereason. Customers using Cybereason can now configure their integration within Cantina to enable alert ingestion and visibility.

**Altering Group Type**

Starting in 9.1, Vectra supports conversion between static and dynamic group types for QUX deployments. Existing triage filters that reference a static group, will continue to function without requiring any change after the group is redefined using a regex in the dynamic group configuration. This should allow for greater flexibility and ease of implementation as customers move to dynamic groups. For more information on dynamic groups see the [Dynamic Groups FAQ](https://support.vectra.ai/vectra/article/KB-VS-1839).


---

# 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/archived-rux-release-notes/2025-release-notes-rux/feb-2025-release-notes-rux.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.