> 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/server/knowledge-base/how-to-articles/disable-microsoft-authentication-users-and-user-groups-cache.md).

# Disable Microsoft authentication users and user groups cache

Disable the Microsoft authentication users and user groups cache in Devolutions Server so it interacts directly with Entra ID without caching delays.

When creating or updating users and groups information in Entra ID, updating the ***Microsoft authentication users and user groups cache*** in Devolutions Server can take quite a while (sometimes a whole day!) if the Entra ID tenant contains a high number of users and groups.

When enabling Microsoft authentication during the creation of a new Devolutions Server instance, the cache feature is disabled so as not to impede the importation of users and groups.

{% hint style="warning" %}
The cache is enabled by default. To have to option to disable this feature, it is required to upgrade Devolutions Server to a later version.
{% endhint %}

To have Devolutions Server interact directly with Entra ID without relying on its ***Microsoft authentication users and user groups cache***, follow the steps below:

1. Go to ***Administration*** – ***Server settings*** – ***Authentication***, and click on the ***Microsoft authentication*** icon under the ***Configuration*** heading.
2. Next, uncheck the ***Enable cache feature*** options, and click the ***Save*** button (floppy disk icon).


---

# 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/server/knowledge-base/how-to-articles/disable-microsoft-authentication-users-and-user-groups-cache.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.