> For the complete documentation index, see [llms.txt](https://docs.elimity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.elimity.com/ms-entra-pim-groups/v2.0.0/release-notes.md).

# Release notes

Releases of the MS Entra PIM Groups gateway, newest first. Every major version has its own version in the dropdown at the top. To get notified of new releases, see [Subscribe to releases](https://docs.elimity.com/ms-entra-pim-groups/v2.0.0/subscribe.md).

{% updates format="full" %}
{% update date="2026-11-09" %}

## v2.0.0

Container image tag `v2.0.0`. **Breaking:** the source needs SDK version 2 and the new configuration value `Request Timeout Seconds`.
{% endupdate %}
{% endupdates %}

<details>

<summary>New functionality</summary>

**The import is split into short requests**

In v1 the whole tenant was imported in one request, probing one group after the other. In large tenants that request ran for hours, longer than proxies and Elimity Insights allow. The first request now lists the tenant's groups, and the next requests probe them 8 at a time, each handing the groups it did not get to on to the next one. See [step 5.1 of the deployment guide](https://docs.elimity.com/ms-entra-pim-groups/v2.0.0/step-by-step-deployment-guide.md).

**A hard limit on every request**

The new `Request Timeout Seconds` configuration value is a hard limit on each request: when it is reached, what finished is imported and the rest is handed on to the next request. A group only sends its data once it is complete, so nothing is imported half.

</details>

<details>

<summary>Bug fixes &#x26; improvements</summary>

**Throttled groups are retried instead of skipped**

In v1 a group that Microsoft Graph throttled was skipped, and the import could report success with that group's access missing. The gateway now waits as long as Graph asks (`Retry-After`) and retries; if Graph keeps throttling, the import fails instead of importing incomplete data.

**No known vulnerabilities with a fix available**

The container image is scanned as described in our [container scanning policy](https://docs.elimity.com/technical-guides/working-with-containers/container-scanning-policy). The earlier images contained Node.js libraries and operating system packages with known vulnerabilities (CVEs) for which a fix exists, among them proxy-addr, body-parser, qs, zod and zlib. v2.0.0 updates them, and the scan finds no critical, high or medium vulnerability with a fix available.

**A smaller container image**

The image is now based on a slim Node.js image and only contains what the gateway needs at runtime, without build and development tools.

</details>

<details>

<summary>Deployment changes</summary>

**SDK version 2**

Set **SDK version** to `2` in the source's custom gateway configuration. With SDK version 1, the import fails before any data is retrieved.

**New required configuration value `Request Timeout Seconds`**

Add `Request Timeout Seconds` (type `Text`) to the source, at least `120` and below the request limits of the platform the gateway runs on (on Azure Container Apps at most `terminationGracePeriodSeconds`). Without it, the import fails at the start with `Invalid configuration: Request Timeout Seconds is required`.

**Container image**

Use the container image tag `v2.0.0`. See [Installation](https://docs.elimity.com/ms-entra-pim-groups/v2.0.0/installation.md).

**Upgrading from v1**

1. Set the source's **SDK version** to `2`.
2. Add the configuration value `Request Timeout Seconds`.
3. Switch the gateway to image tag `v2.0.0`.

The data model is unchanged.

</details>


---

# 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.elimity.com/ms-entra-pim-groups/v2.0.0/release-notes.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.
