> For the complete documentation index, see [llms.txt](https://docs.sonarsource.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sonarsource.com/sonarqube-server/analyzing-source-code/languages/powershell.md).

# PowerShell

Language-specific information about the way that SonarQube Server 2026.5 supports the analysis of PowerShell.

## Analysis Overview

The PowerShell analyzer is designed to perform static code analysis on PowerShell source code and scripts.

## Language-specific properties

You can discover and update the PowerShell-specific properties in *Your project* > **Administration** > **General Settings** > **Languages** > **PowerShell**. See [Configuration methods](/sonarqube-server/server-installation/system-properties/configuration-methods.md) for more information about setting properties.<br>

## In-line suppression of issues <a href="#in-line-suppression-of-issues" id="in-line-suppression-of-issues"></a>

Adding the #NOSONAR comment at the end of the line will suppress all issues on that line.

### SuppressMessage attribute

Use `Diagnostics.CodeAnalysis.SuppressMessageAttribute` to suppress a specific rule for a script, function, or parameter. The first argument is the rule key and the second argument should be an empty string.

```powershell
function Invoke-Example {
    [Diagnostics.CodeAnalysis.SuppressMessageAttribute('SXXXX', '', Justification = 'Because ...')]
    param()

    # ...
}
```

{% hint style="warning" %}
Rather than relying on this method, we suggest refining your analysis scope to avoid creating major gaps in your code review. Because the `NOSONAR` comment silences all current and future issues on a line without regard for their severity, it is an imprecise tool. Even if you only intend to hide a minor stylistic point, you could unintentionally obscure a serious security flaw.
{% endhint %}


---

# 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.sonarsource.com/sonarqube-server/analyzing-source-code/languages/powershell.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.