> 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/powershell/powershell-commands/get-rdmimportableuser.md).

# Get-RDMImportableUser

Get-RDMImportableUser retrieves the users an identity provider makes available for import into a Remote Desktop Manager workspace.

### Synopsis

Retrieve the users available for import from an identity provider.

### Syntax

#### \_\_AllParameterSets

```
Get-RDMImportableUser [-Provider] <ServerUserType> [-DomainName <string[]>] [-GroupFilter <string>]
 [-IncludeExisting] [-ForcePromptAnswer <DialogResult[]>] [<CommonParameters>]
```

### Description

Retrieve the users an identity provider makes available for user import. Candidates already present on this workspace are excluded by default; use -IncludeExisting to see them too. Pipe the result to Import-RDMUser to create the selected users. Requires a Devolutions Server workspace.

### Examples

#### Example 1

```powershell
PS C:\> Get-RDMImportableDomain -Provider Domain | Get-RDMImportableUser
```

Retrieve the importable users of every configured Active Directory domain.

#### Example 2

```powershell
PS C:\> Get-RDMImportableUser -Provider Domain -DomainName 'contoso.com' -GroupFilter 'IT Admins'
```

Retrieve the importable users of a specific domain who belong to the IT Admins group.

#### Example 3

```powershell
PS C:\> Get-RDMImportableUser -Provider AzureAD -IncludeExisting
```

Retrieve every Microsoft Entra ID user, including the ones already present on this workspace.

### Parameters

#### -DomainName

The domain(s) to browse. Required for the Domain provider; ignored by AzureAD, Okta and PingOne.

```yaml
Type: System.String[]
DefaultValue: ''
SupportsWildcards: false
Aliases: []
ParameterSets:
- Name: (All)
  Position: Named
  IsRequired: false
  ValueFromPipeline: false
  ValueFromPipelineByPropertyName: true
  ValueFromRemainingArguments: false
DontShow: false
AcceptedValues: []
HelpMessage: ''
```

#### -ForcePromptAnswer

Switch to use with caution. It will automatically answer prompt asking yes/no, yes/no/cancel, or ok/cancel questions. In case of multiple prompts, multiple values can be passed to this parameter. Here are the accepted values:

* Yes: Accept the prompt. Cover the OK and Automatic value.
* No: Refuse the yes/no/cancel prompt. "Cancel" is the fallback option if there is no "No" option.
* Cancel: Cancel the yes/no/cancel prompt. "No" is the fallback option if there is no "Cancel" option.

```yaml
Type: System.Windows.Forms.DialogResult[]
DefaultValue: ''
SupportsWildcards: false
Aliases: []
ParameterSets:
- Name: (All)
  Position: Named
  IsRequired: false
  ValueFromPipeline: false
  ValueFromPipelineByPropertyName: false
  ValueFromRemainingArguments: false
DontShow: false
AcceptedValues: []
HelpMessage: ''
```

#### -GroupFilter

Only return users belonging to this group. Ignored by the AzureAD provider. For the Domain provider, also excludes any user missing a UPN attribute.

```yaml
Type: System.String
DefaultValue: ''
SupportsWildcards: false
Aliases: []
ParameterSets:
- Name: (All)
  Position: Named
  IsRequired: false
  ValueFromPipeline: false
  ValueFromPipelineByPropertyName: false
  ValueFromRemainingArguments: false
DontShow: false
AcceptedValues: []
HelpMessage: ''
```

#### -IncludeExisting

Include the candidates that already exist on this workspace.

```yaml
Type: System.Management.Automation.SwitchParameter
DefaultValue: ''
SupportsWildcards: false
Aliases: []
ParameterSets:
- Name: (All)
  Position: Named
  IsRequired: false
  ValueFromPipeline: false
  ValueFromPipelineByPropertyName: false
  ValueFromRemainingArguments: false
DontShow: false
AcceptedValues: []
HelpMessage: ''
```

#### -Provider

The identity provider to browse.

```yaml
Type: Devolutions.RemoteDesktopManager.ServerUserType
DefaultValue: ''
SupportsWildcards: false
Aliases: []
ParameterSets:
- Name: (All)
  Position: 0
  IsRequired: true
  ValueFromPipeline: false
  ValueFromPipelineByPropertyName: true
  ValueFromRemainingArguments: false
DontShow: false
AcceptedValues: []
HelpMessage: ''
```

#### CommonParameters

This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutBuffer, -OutVariable, -PipelineVariable, -ProgressAction, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about\_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).

### Outputs

#### RemoteDesktopManager.PowerShellModule.PSOutputObject.PSImportableUser

### Notes

For more information, type "Get-Help Get-RDMImportableUser -detailed". For technical information, type "Get-Help Get-RDMImportableUser -full".


---

# 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/powershell/powershell-commands/get-rdmimportableuser.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.