> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/pam/knowledge-base/troubleshooting-articles/jit-elevation-not-revoking-privileges-for-users.md).

# JIT elevation not revoking privileges for users

Fix JIT elevation privileges not revoking for Entra ID users in Devolutions Server 2023.3 by reviewing and correcting Azure group memberships after checkout.

In version 2023.3, privileges obtained through JIT elevation using an Entra ID (Azure) provider were not correctly revoked after elevation.

If the PAM check-in was done automatically by the scheduler (e.g., when the timer of a checkout was elapsed) it is possible the user is still part of the group it was originally elevated as.

### Solution

1. Log in with an administrator account in the web interface for Devolutions Server.
2. Go to ***Administration*** – ***Privileged Access*** – ***Providers***.
3. Click the ***Settings*** button on the Entra ID (Azure) provider.
4. Go to the Settings tab and review the groups in the ***Just-In-Time (JIT) elevation*** section.<br>
5. In Microsoft Azure go to ***Azure*** – ***Microsoft Entra ID*** – ***Groups***.
6. Review the desired group to make certain the user accounts used during the JIT elevation process are no longer part of the group(s).


---

# 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.devolutions.net/pam/knowledge-base/troubleshooting-articles/jit-elevation-not-revoking-privileges-for-users.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.