> 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-azure-resources/v1.0.0/release-notes.md).

# Release notes

Releases of the MS Entra PIM Azure Roles gateway, newest first. Every release 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-azure-resources/v1.0.0/subscribe.md).

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

## v1.0.0

Container image tag `v1.0.0`, the first versioned release.
{% endupdate %}
{% endupdates %}

<details>

<summary>New functionality</summary>

**Import of PIM for Azure roles**

The gateway imports Azure role definitions and the active and eligible PIM role assignments of a tenant, for every scope: the root scope, the root management group and every management group, subscription, resource group and resource below it. See the [step-by-step deployment guide](https://docs.elimity.com/ms-entra-pim-azure-resources/v1.0.0/step-by-step-deployment-guide.md).

**Client secret authentication**

The gateway authenticates as an app registration with a client secret (`clientSecret`).

</details>

<details>

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

**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 `v1.0.0-alpha` images contained Node.js libraries with known vulnerabilities (CVEs) for which a fix exists, among them proxy-addr, path-to-regexp, body-parser, qs and lodash. v1.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: 328 MB instead of 1.43 GB.

</details>

<details>

<summary>Deployment changes</summary>

**SDK version 1**

The gateway uses SDK version 1. Keep 'SDK version' at `1` in the custom gateway configuration of the source.

**Container image**

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

**Upgrading from v1.0.0-alpha.1, alpha.2 or alpha.3**

These images authenticated with a certificate (`clientCertificate`). v1.0.0 uses a client secret again:

1. Add a client secret to the app registration, see step 3 of the [step-by-step deployment guide](https://docs.elimity.com/ms-entra-pim-azure-resources/v1.0.0/step-by-step-deployment-guide.md).
2. On the source, delete the configuration value `clientCertificate` and add `clientSecret` (type `Password`) with the secret's value.
3. Switch the gateway to image tag `v1.0.0`.

Without these steps the import fails with `Unrecognized key: "clientCertificate"`.

</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-azure-resources/v1.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.
