> 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/cloud/fr/knowledge-base/troubleshooting-articles/entra-id-provisioning.md).

# Provisionnement Entra ID

Corrigez l'erreur Invalid SCIM Token dans le provisionnement Entra ID de Devolutions Cloud en régénérant le jeton et en le mettant à jour dans Entra ID.

Si la solution fournie ne résout pas votre problème, veuillez communiquer avec l'[équipe de soutien](mailto:service@devolutions.net) en fournissant une description détaillée de l'erreur ainsi que les journaux de provisionnement récents d'EntraID liés au problème.

#### Problème 1 - status":"401","detail":"Invalid SCIM Token"

**Cause** : Le jeton de provisionnement a expiré. Il doit être régénéré à partir de Devolutions Cloud et remplacé dans EntraID.

#### Étapes

1. Dans Devolutions Cloud, allez à **Administration** - **Authentification -** **Provisionnement**.
2. Régénérez le jeton.
3. Une fois le jeton généré, copiez-le.
4. Ouvrez l'application EntraID utilisée pour le provisionnement.
5. Repérez le champ **Secret Token** sous la section **Provisionnement**.
6. Collez le nouveau jeton dans ce champ pour remplacer celui qui a expiré.


---

# 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/cloud/fr/knowledge-base/troubleshooting-articles/entra-id-provisioning.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.