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 more detailed attention, with specific sections and examples for each, and PowerShell is mentioned in CLI version requirements. Bash is covered, but Linux-specific shells beyond Bash (e.g., zsh, fish) are not mentioned. The order of presentation places Bash first, but PowerShell is referenced in requirements and receives more nuanced discussion. There is a subtle Windows bias in the prominence and detail given to Windows-native shells and tools.
Recommendations:
- Expand Linux parity by including examples for additional common Linux shells (e.g., zsh, fish) or explicitly stating that Bash examples apply to most POSIX shells.
- Clarify that the Azure CLI and its extensions are fully cross-platform, and highlight any Linux/macOS-specific considerations if they exist.
- Balance the depth of examples and troubleshooting tips between Bash and PowerShell/Windows CMD sections.
- In CLI version requirements, avoid referencing PowerShell specifically unless there is a unique requirement for it; otherwise, generalize to all supported shells.
- Consider adding a table summarizing shell-specific syntax differences for quick reference, ensuring equal visibility for Linux and Windows environments.
Create pull request
Scan History
| Date | Scan ID | Status | Bias Status |
|---|---|---|---|
| 2025-08-17 00:01 | #83 | in_progress | ✅ Clean |
| 2025-07-13 21:37 | #48 | completed | ✅ Clean |
| 2025-07-09 13:09 | #3 | cancelled | ✅ Clean |
| 2025-07-08 04:23 | #2 | cancelled | ❌ Biased |
Flagged Code Snippets
### 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:
>[!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:
### 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: