> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/keeper-bridge/migrating-from-keeper-bridge-to-scim-provisioning.md).
# Migrating from Keeper Bridge to SCIM Provisioning
This documentation provides you with a detailed guide on how to decommission your Keeper Bridge server and transition to SCIM Provisioning.
### Disable Keeper Bridge Service
Close Keeper Bridge Application and **stop** and **disable** the service on the machine
Remove Bridge Provisioning from your Keeper Admin Console
### Move all users from sub-nodes to the top-level SSO node
Navigate to the lowest level of your node setup
Move all users from sub-nodes to the top-level SSO node
#### Using Keeper Commander
Moving users to other nodes can be labor-intensive at scale. We recommend using [Keeper Commander](/keeperpam/commander-cli/overview.md) to perform the move.
* Moving all users from node "Bridge" and its subnodes using `action-report`:
{% code overflow="wrap" %}
```
action-report --target all --node "Bridge" --recursive --apply-action move --target-node "SSO"
```
{% endcode %}
* Moving one or more users to a node using `enterprise-user`:
```
enterprise-user [user email] [user email] --node "SSO"
```
### Configure SCIM Provisioning for your IdP
Refer to the documentation to choose your identity provider (IdP) for SSO Connect, then follow the corresponding SCIM provisioning steps.
* [SSO Connect Cloud](/sso-connect-cloud/identity-provider-setup.md)
* [SSO Connect On-Prem](/sso-connect-on-prem/identity-provider-setup.md)
* [SCIM Provisioning](/enterprise-guide/user-and-team-provisioning/azure-ad-provisioning-scim.md)
---
# 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.keeper.io/keeper-bridge/migrating-from-keeper-bridge-to-scim-provisioning.md?ask=&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.
