Document Details
Explore Resources
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
Detected Bias Types
windows_first
powershell_heavy
windows_tools
missing_linux_example
Summary
The documentation presents both Azure CLI and Azure PowerShell examples for all queries, but there is a notable bias toward Windows/PowerShell patterns. PowerShell examples are always present and sometimes explained in more detail (e.g., use of ConvertTo-Json and depth), and Windows-centric tools and patterns (PowerShell variables, cmdlets) are used throughout. In the multi-step public IP address example, the Azure CLI workflow uses Unix tools (awk, sed, tail), but there is no explicit mention of Linux shell environments or guidance for Linux users. The JSON output examples use Windows-centric values (e.g., WindowsServer images, osType: Windows), and there is no mention of Linux VMs or their properties.
Recommendations
- Add explicit Linux/Unix shell examples (e.g., bash, zsh) for workflows involving Azure CLI, especially for variable handling and file manipulation.
- Include examples or notes for querying Linux virtual machines (e.g., using 'osType: Linux', 'publisher: Canonical', etc.) in JSON and queries.
- Balance explanations between PowerShell and CLI, ensuring that CLI examples are as detailed and accessible as PowerShell ones.
- When discussing output formatting (e.g., ConvertTo-Json in PowerShell), provide equivalent CLI/jq or other Linux-friendly alternatives.
- Avoid Windows-centric sample data where possible, or provide parallel Linux examples (e.g., show both Windows and Linux VM JSON).
- Clarify in notes or callouts when CLI examples assume a Unix-like shell, and provide Windows CMD or PowerShell equivalents if needed.
Create Pull Request
Scan History
| Date | Scan | Status | Result |
|---|---|---|---|
| 2026-01-14 00:00 | #250 | in_progress |
Biased
|
| 2026-01-13 00:00 | #246 | completed |
Biased
|
| 2026-01-11 00:00 | #240 | completed |
Biased
|
| 2026-01-10 00:00 | #237 | completed |
Biased
|
| 2026-01-09 00:34 | #234 | completed |
Biased
|
| 2026-01-08 00:53 | #231 | completed |
Biased
|
| 2026-01-06 18:15 | #225 | cancelled |
 Clean
|
| 2025-08-17 00:01 | #83 | cancelled |
Clean
|
| 2025-07-13 21:37 | #48 | completed |
Biased
|
| 2025-07-12 23:44 | #41 | cancelled |
Biased
|
Flagged Code Snippets
# Use Resource Graph to get all NICs and store in the $nics variable $nics = (Search-AzGraph -Query "Resources | where type =~ 'Microsoft.Compute/virtualMachines' | project nic = tostring(properties['networkProfile']['networkInterfaces'][0]['id']) | where isnotempty(nic) | distinct nic | limit 20").Data # Review the output of the query stored in the variable $nics.nic