Document Details
Concepts Cli
❌
This page contains Windows bias
About This Page
This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.
Bias Analysis
Bias Types:
⚠️
windows_first
⚠️
powershell_heavy
⚠️
windows_tools
Summary:
The documentation provides examples and guidance for Bash, PowerShell, and Windows CMD environments. However, PowerShell and Windows CMD receive dedicated sections and examples, and PowerShell is mentioned early as a primary use case. There is an explicit mention of using Azure CLI with PowerShell as a requirement, and the Windows CMD section is present, but there is no equivalent section for native Linux shells beyond Bash (e.g., zsh, fish), nor is there parity in depth for Linux-specific environments. The order of presentation (Bash, then PowerShell, then Windows CMD) is reasonable, but the focus on PowerShell and Windows CMD, and the explicit mention of PowerShell in requirements, indicate a Windows-first and PowerShell-heavy bias.
Recommendations:
- Add examples and guidance for other common Linux shells (e.g., zsh, fish) if relevant.
- Clarify that the Azure CLI and its extensions are fully supported on Linux and macOS, not just Windows.
- In the CLI version requirements, avoid framing PowerShell as the default or primary shell; instead, mention Bash and other shells equally.
- Ensure that Linux and macOS users are given equal prominence in installation and usage instructions.
- Consider reordering sections or providing a table that summarizes shell-specific requirements for Bash, zsh, PowerShell, and CMD, to avoid implicit prioritization of Windows environments.
Create pull request
Scan History
| Date | Scan ID | Status | Bias Status |
|---|---|---|---|
| 2025-07-12 23:44 | #41 | in_progress | ❌ Biased |
| 2025-07-12 00:58 | #8 | cancelled | ✅ Clean |
| 2025-07-10 05:06 | #7 | processing | ✅ Clean |
Flagged Code Snippets
>[!TIP]
>Many of the commands that support inline JSON also support input as a file path, which can help you avoid shell-specific text requirements.
#### Queries
In many twin queries, the `$` character is used to reference the `$dtId` property of a twin. When using the [az dt twin query](/cli/azure/dt/twin#az-dt-twin-query) command to query in a PowerShell environment, escape the `$` character with a backtick character.
Here's an example of querying for a twin with a CLI command in PowerShell:
### PowerShell
Use these special character tips for PowerShell environments.
#### Inline JSON
Some commands, like [az dt twin create](/cli/azure/dt/twin#az-dt-twin-create), allow you to enter twin information in the form of inline JSON. When entering inline JSON in the PowerShell environment, escape double quote characters (`"`) inside the JSON with a backslash (`\`).
Here's an example of creating a twin with a CLI command in PowerShell:
### Windows CMD
Use these special character tips for the local Windows CMD.
#### Inline JSON
Some commands, like [az dt twin create](/cli/azure/dt/twin#az-dt-twin-create), allow you to enter twin information in the form of inline JSON. When entering inline JSON in a local Windows CMD window, enclose the parameter value with double quotes (`"`) instead of single quotes (`'`), and escape double quote characters inside the JSON with a backslash (`\`).
Here's an example of creating a twin with a CLI command in the local Windows CMD: