19
Pages Scanned
3
Pages Flagged
19
Changed Pages
15.8%
% Pages Flagged
Scan Information
Started At: 2026-01-23 00:00:09
Finished At: 2026-02-10 18:00:39
Status: completed
Target Repo: Azure Compute
Current Phase: discovery
Files Queued: 19
Files Completed: 19
Problematic Pages
3 issues found
Virtual Machines
Create a VM from a specialized image version
...icles/virtual-machines/vm-specialized-image-version.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
missing_linux_example
Summary
The documentation provides both Azure CLI and PowerShell examples for creating VMs from specialized images, but the PowerShell examples are significantly more detailed and complex, including full networking setup and resource creation, while the CLI examples are minimal. PowerShell is a Windows-centric tool, and the lack of parity in CLI examples may disadvantage Linux/macOS users. Additionally, PowerShell examples are presented before CLI in some sections, and there are no Bash or Linux-native scripting examples for tasks like networking setup.
Recommendations
- Expand Azure CLI examples to include full resource setup (networking, NSG, NIC, etc.), matching the detail of PowerShell examples.
- Add Bash shell script examples for Linux/macOS users, especially for multi-step VM deployments.
- Ensure CLI examples are presented before or alongside PowerShell examples to avoid Windows-first impression.
- Explicitly mention that all CLI commands work on Linux/macOS and provide troubleshooting tips for non-Windows platforms.
Create Pull Request
Virtual Machines
Create a VM from a generalized image in a gallery
...icles/virtual-machines/vm-generalized-image-version.md
Medium Priority
View Details →
Detected Bias Types
powershell_heavy
windows_first
windows_tools
Summary
The documentation provides both CLI and PowerShell examples for creating VMs from generalized images in an Azure Compute Gallery. However, PowerShell examples are heavily focused on Windows-specific patterns (e.g., Set-AzVMOperatingSystem -Windows, Get-Credential for username/password), and the full parameter set for PowerShell only shows Windows VM creation. Windows-specific networking rules (RDP port 3389) are configured by default in PowerShell examples. While CLI examples default to Linux VM creation (with SSH keys), PowerShell examples default to Windows VM creation and do not show Linux VM creation or SSH key usage. REST and Portal instructions do show both Linux and Windows, but PowerShell coverage is notably Windows-centric.
Recommendations
- Add PowerShell examples for creating Linux VMs, including usage of SSH keys and Set-AzVMOperatingSystem -Linux.
- Show how to configure Linux-specific network security rules (e.g., SSH port 22) in PowerShell examples.
- Balance the order of examples so that Linux and Windows are equally represented, or clarify when an example is Windows-specific.
- In PowerShell sections, explicitly mention how to adapt commands for Linux VMs, including credential handling and OS configuration.
Low Priority
View Details →
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for checking vCPU quotas, but PowerShell (a Windows-centric tool) is given equal prominence and a dedicated tab. The CLI example is shown first, but the PowerShell section may imply parity between Windows and Linux tooling, even though PowerShell is less commonly used on Linux/macOS. No Linux/macOS-specific shell examples (e.g., Bash) are provided, but the Azure CLI is cross-platform.
Recommendations
- Clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Add a note indicating PowerShell is primarily for Windows users, though available on Linux/macOS.
- Consider including Bash script examples for Linux users, or explicitly state that Azure CLI commands work in Bash/zsh/fish shells.
- Ensure that CLI instructions are clearly marked as the recommended approach for non-Windows platforms.