Scan Details - Linux-first Docs for Azure

Virtual Machines Create a VM from a generalized image in a gallery ...icles/virtual-machines/vm-generalized-image-version.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first ⚠️ windows_tools

Summary

The documentation provides both Azure CLI and PowerShell examples for creating VMs from generalized images in a gallery. However, PowerShell examples are heavily Windows-centric, with explicit use of Windows-only parameters (e.g., Set-AzVMOperatingSystem -Windows), and the full parameter set is demonstrated only for Windows VMs. Windows-specific networking rules (e.g., RDP port 3389) are configured by default, and password complexity requirements link to Windows documentation. In several sections, Windows VM creation is shown before or instead of Linux, and PowerShell examples do not show Linux VM creation or configuration.

Recommendations

Add PowerShell examples for creating Linux VMs, including the use of Set-AzVMOperatingSystem -Linux and relevant Linux configuration options.
In PowerShell sections, provide both Windows and Linux VM creation flows, or clarify when examples are Windows-only.
When showing networking rules, include SSH (port 22) alongside RDP (port 3389) and clarify their relevance for Linux and Windows VMs.
Ensure password complexity requirements reference both Windows and Linux documentation, or clarify differences.
Where examples are given, alternate the order of Windows and Linux examples, or present both together for parity.

Create Pull Request

Virtual Machines Create a VM from a specialized image version ...icles/virtual-machines/vm-specialized-image-version.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

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 extensive and detailed, while the CLI examples are more concise. The PowerShell examples use Windows-centric tools and patterns (e.g., New-AzNetworkSecurityRuleConfig for RDP port 3389, Windows-style variable naming, and PowerShell-specific networking setup). There are no Linux shell (bash) or macOS-specific examples for tasks like networking setup, nor are there explicit Linux-focused CLI walkthroughs. PowerShell examples are given equal or greater prominence than CLI, which may create friction for Linux/macOS users who do not use PowerShell.

Recommendations

Add detailed bash shell examples for networking and VM creation, matching the depth of the PowerShell walkthroughs.
Ensure CLI examples cover all steps shown in PowerShell (e.g., network interface, NSG creation), not just the VM creation command.
Clarify that PowerShell examples are primarily for Windows users, and provide parity for Linux/macOS users with bash/CLI scripts.
Where possible, use cross-platform terminology and avoid Windows-centric patterns (e.g., RDP port blocking) unless relevant to both OS types.

Create Pull Request

Virtual Machines Enable Trusted launch on existing Gen2 VMs ...rticles/virtual-machines/trusted-launch-existing-vm.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first ⚠️ windows_tools

Summary

The documentation provides parity for both Linux and Windows VMs in terms of feature applicability and mentions SSH for Linux and RDP for Windows. However, there is a notable bias in the scripting and automation sections: PowerShell is given a dedicated section, and ARM template deployment examples use PowerShell commands exclusively for deployment (e.g., New-AzResourceGroupDeployment), with no Bash or cross-platform CLI alternatives. In the 'Best practices' section, Linux-specific validation is mentioned, but in the main automation workflows, Windows/PowerShell tools are prioritized or exclusively shown. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer Bash/Azure CLI.

Recommendations

Add Bash/Azure CLI examples for ARM template deployment (e.g., using az deployment group create) alongside PowerShell.
Where PowerShell is used for automation, provide equivalent Bash or cross-platform CLI commands.
In sections where PowerShell is shown first or exclusively, clarify that cross-platform alternatives exist and link to relevant documentation.
Consider adding a short note or table summarizing which tools are cross-platform and which are Windows-only, to help users choose the best option for their OS.

Create Pull Request

Virtual Machines vCPU quotas ...ute-docs/blob/main/articles/virtual-machines/quotas.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy

Summary

The documentation provides both Azure CLI and PowerShell examples for checking vCPU quotas, but the PowerShell section is presented second and is focused on the Windows-specific PowerShell tool. There is a slight bias in that PowerShell (a Windows-centric tool) is given its own section, and the CLI example is presented first, which is more cross-platform. No Linux-specific commands or tools are missing, but the PowerShell section may be less relevant for Linux/macOS users.

Recommendations

Clarify that PowerShell examples are primarily for Windows users, and note that Azure CLI is recommended for Linux/macOS.
Consider adding a note that Azure CLI works natively on Linux/macOS and is the preferred cross-platform tool.
If relevant, mention that PowerShell Core is available on Linux/macOS, but most users on those platforms use Azure CLI.
Ensure that CLI examples remain prominent and up-to-date for Linux parity.

Create Pull Request

Scan Information

Problematic Pages