> 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-dspamscanconfiguration.md).

# Get-DSPamScanConfiguration

### Synopsis

Get the PAM account discovery configurations

### Syntax

#### Name

```
Get-DSPamScanConfiguration [[-Name] <string>] [-CaseSensitive] [<CommonParameters>]
```

#### Literal

```
Get-DSPamScanConfiguration [-LiteralName] <string> [-CaseSensitive] [<CommonParameters>]
```

### Description

Get the PAM account discovery configurations, which can be filtered by name. Use the 'Name' parameter for wildcard searches, and the 'LiteralName' parameter for exact matches as it doesn't interpret characters as wildcards.

### Examples

#### Example 1

```powershell
PS C:\> $configurations = Get-DSPamScanConfiguration -Name 'Config*'
```

Get all PAM account discovery configurations with names starting with 'Config'

#### Example 2

```powershell
PS C:\> $configuration = Get-DSPamScanConfiguration -LiteralName 'Config [A]'
```

Get the PAM account discovery configuration named 'Config \[A]'. The 'LiteralName' parameter ensures that the characters '\[' and ']' are not treated as wildcards.

### Parameters

#### -CaseSensitive

Case sensitive search

```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: ''
```

#### -LiteralName

Filter the account discovery configurations by their name. No characters will be interpreted as wildcards.

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

#### -Name

Filter the account discovery configurations by their name

```yaml
Type: System.String
DefaultValue: ''
SupportsWildcards: false
Aliases: []
ParameterSets:
- Name: Name
  Position: 0
  IsRequired: false
  ValueFromPipeline: false
  ValueFromPipelineByPropertyName: false
  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).

### Notes

For more information, type "Get-Help Get-DSPamScanConfiguration -detailed". For technical information, type "Get-Help Get-DSPamScanConfiguration -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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.devolutions.net/powershell/powershell-commands/get-dspamscanconfiguration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.