> 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/rdm/knowledge-base/how-to-articles/user-synchronization-with-active-directory-in-a-microsoft-sql-server-workspace.md).

# User synchronization with Active Directory in a Microsoft SQL Server workspace

Synchronize users from Active Directory into a Microsoft SQL Server workspace in Remote Desktop Manager and manage offboarding.

Remote Desktop Manager supports user synchronization with Active Directory (AD) for [Microsoft SQL Server workspaces](/rdm/getting-started/workspaces/workspace-types/alternative-workspaces/microsoft-sql-server.md). This feature allows administrators to automatically remove or deactivate users in Remote Desktop Manager who no longer exist in the AD environment.

Here are the steps to follow to synchronize users with AD:

1. Go to ***Administration*** – ***Users***, and click on the ***Sync users from AD*** button.
2. Enter the administration credentials for the domain from which to retrieve users. By default, the domain is retrieved based on the currently logged-in Windows user. Click on ***Ok***.
3. Select the ***Username source*** and ***Username format*** (only if ***Name*** is selected as the username source). Click on ***Ok***.

{% hint style="info" %}
***Username Source***determines the Active Directory (AD) account property from which the username is retrieved. Accounts without this property filled will not be synchronized.
{% endhint %}

4\. Specify which users will be added/deleted to the workspace, their ***Authentication type***, whether to create a database login/user for them, and which ***Offboarding*** method to use for deleted users (see table below for a description of the available options). Click on ***Synchronize***.

{% hint style="warning" %}
If ***Integrated security*** is not selected, a random password will be generated for each user. An administrator will then need to change that password before sending it to the users.
{% endhint %}

### Offboarding methods

| OPTIONS       | DESCRIPTION                                                                                                                                                   |
| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Prompt**    | <p>A prompt will appear for each deleted user, asking for a confirmation and<br>whether its user vault entries should be transferred to the shared vault.</p> |
| **Automatic** | The offboarding will execute without prompting, meaning all user vault entries will be transferred to the shared vault.                                       |
| **Skip**      | The users will be deleted without prompt and all user vault entries will be lost.                                                                             |


---

# 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/rdm/knowledge-base/how-to-articles/user-synchronization-with-active-directory-in-a-microsoft-sql-server-workspace.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.