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

# Entra ID provisioning

Fix the Invalid SCIM Token error in Devolutions Cloud Entra ID provisioning by regenerating the token and updating it in Entra ID.

If the solution provided does not resolve your issue, please contact the [support team](mailto:service@devolutions.net) with a detailed error description and the recent provisioning logs from EntraID related to the problem.

#### Issue 1 - status":"401","detail":"Invalid SCIM Token"

**Cause**: The provisioning token has expired. It needs to be regenerated from Devolutions Cloud and replaced in EntraID.

#### Steps

1. In Devolutions Cloud, navigate to **Administration** - **Authentication -** **Provisioning**.
2. Regenerate the token.
3. Once the token is generated, copy it.
4. Open the EntraID application used for provisioning.
5. Locate the **Secret Token** field under the **Provisioning** section.
6. Paste the new token into this field to replace the expired one.


---

# 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/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.