> For the complete documentation index, see [llms.txt](https://docs.oort.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oort.io/release-notes/2022/week-35-2022.md).
# Week 35, 2022
**New Features**
**Allow & Block Lists Now Bi-Directional**
You can now toggle your lists to ‘Allow’ or ‘Block’ certain email domains or browser types. Setting these lists will help security analysts quickly identify authentication behavior that is out of policy for your organization by failing its respective checks when any of the criteria are met.
**Filter Panel Now Actionable**
You can now take action to include or exclude filters from the side panel when viewing the Users list. This enables specific populations of users to be shown in the results without having to enter a query in the search bar.
\
\
**Behavioral Check Failures Now Explained**
You can now see the reason why a behavioral check failed. Navigate to any user, click the ‘Activity’ tab, then click the event in the table. The sidebar will open up with details of what behavior triggered the check failure.
**▶️ EventHub Integration Now Available for Azure AD**
You can now configure your Azure AD instance to utilize the EventHub streaming service. Using EventHub reduces the likelihood that your organization will hit any sort of rate limit when collecting logs. To enable EventHub, go to the “Integrations” tab, select your Azure AD instance, then click the “Event Streaming” tab. Enter your information and click Save.
**Improvements**
👌🏻Customers using OIE can now enable collections for “Devices” and “Authenticators”
👌🏻 The Identity Security Check for “Risky Parallel Sessions” has been optimized to remove obvious machine communications
---
# 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.oort.io/release-notes/2022/week-35-2022.md?ask=&goal=
```
`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.
