← Back to Dashboard
25
Pages Scanned
5
Pages Flagged
25
Changed Pages
20.0%
% Pages Flagged

Scan Information

Started At: 2026-01-24 00:00:10

Finished At: 2026-02-10 18:44:36

Status: completed

Target Repo: Azure Compute

Current Phase: discovery

Files Queued: 25

Files Completed: 25

Problematic Pages

5 issues found
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: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides both CLI and PowerShell examples for creating VMs from generalized images in an Azure Compute Gallery. However, the PowerShell examples are exclusively for Windows, with commands like Set-AzVMOperatingSystem -Windows and prompts for Windows credentials. There are no PowerShell examples for Linux VM creation, nor guidance for Linux-specific PowerShell usage. In CLI and REST sections, Linux is shown first, but PowerShell sections always default to Windows. This creates friction for Linux users who prefer PowerShell or need parity in automation scripts.
Recommendations
  • Add PowerShell examples for creating Linux VMs, using Set-AzVMOperatingSystem -Linux and appropriate credential handling.
  • Explicitly mention how to adapt PowerShell scripts for Linux VM creation, including SSH key configuration and Linux-specific parameters.
  • Ensure that both Windows and Linux scenarios are covered equally in PowerShell sections, similar to the parity shown in CLI and REST examples.
  • Consider adding a table or note summarizing differences in PowerShell usage for Windows vs. Linux VM creation.
GitHub 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 significantly more detailed and complex, including full network setup and VM configuration. CLI examples are much shorter and do not cover equivalent steps. PowerShell is a Windows-centric tool, and the lack of parity in example depth may disadvantage Linux/macOS users who rely on CLI or other scripting environments. Additionally, PowerShell examples are presented in every scenario, and in some sections, the PowerShell tab appears before CLI, reinforcing a Windows-first pattern. There are no Bash or Linux-native scripting examples for advanced scenarios.
Recommendations
  • Expand Azure CLI examples to include full VM creation workflows, including network setup and configuration, matching the detail of PowerShell examples.
  • Add Bash shell script examples for Linux/macOS users, especially for advanced scenarios.
  • Ensure CLI examples are presented before or alongside PowerShell examples to avoid a Windows-first impression.
  • Explicitly mention that PowerShell examples are primarily for Windows users and suggest CLI/Bash alternatives for Linux/macOS users.
GitHub Create Pull Request
Virtual Machines Create a Gallery for Sharing Resources .../blob/main/articles/virtual-machines/create-gallery.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides examples for creating an Azure Compute Gallery using the Portal, Azure CLI, PowerShell, and REST API. While the CLI and REST examples are cross-platform, PowerShell examples are included and shown in parity with CLI, but there is a subtle Windows bias: PowerShell is a Windows-centric tool and is presented alongside CLI, and in the first major section ('Create a private gallery'), the PowerShell example is shown before REST. Additionally, the ordering of examples is Portal > CLI > PowerShell > REST, which places Windows tools before REST, and PowerShell is not available natively on Linux/macOS (though PowerShell Core exists, it's less common for Azure tasks). No Linux-specific tools (e.g., Bash scripts) or explicit Linux/macOS guidance is provided.
Recommendations
  • Clarify that Azure CLI commands work on Windows, Linux, and macOS.
  • Consider mentioning PowerShell Core compatibility for non-Windows users if PowerShell is shown.
  • Ensure example ordering does not imply preference for Windows tools (e.g., CLI before PowerShell).
  • Optionally, add a note that Bash or shell scripting can be used with Azure CLI on Linux/macOS.
  • Explicitly state platform compatibility for each method.
GitHub 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 example is given equal prominence, and the CLI example is not explicitly labeled as Linux/macOS-friendly. The tab order presents CLI first, but the PowerShell section is detailed and assumes familiarity with Windows tooling. There is no explicit mention of Linux-specific tools or shell environments, nor are there notes clarifying cross-platform compatibility for the CLI commands.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and are the recommended cross-platform approach.
  • Add a note clarifying that PowerShell examples are primarily for Windows users, while Azure CLI is suitable for Linux/macOS.
  • Consider providing bash or shell script examples for Linux users, or at least mention that the CLI commands can be run in bash/zsh.
  • If possible, reorder tabs or add a 'Recommended for Linux/macOS' label to the CLI section.
GitHub Create Pull Request
Virtual Machines Enable Trusted launch on existing Gen2 VMs ...rticles/virtual-machines/trusted-launch-existing-vm.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides parity for both Linux and Windows VMs, explicitly stating applicability to both. However, there is a mild Windows bias in the ordering of connection instructions (RDP for Windows is mentioned before SSH for Linux), and PowerShell is used for ARM template deployment and VM deallocation/start examples, which may be less familiar or accessible to Linux/macOS users. The CLI examples are cross-platform, but PowerShell is referenced in several places without alternative Bash or shell scripting examples.
Recommendations
  • When showing connection instructions, alternate the order or explicitly show Linux-first examples in some sections (e.g., 'Verify that you can sign in to the VM by using SSH (for Linux VMs) or RDP (for Windows VMs)').
  • For ARM template deployment and VM management, provide equivalent Bash/Azure CLI scripts for Linux/macOS users alongside PowerShell examples.
  • Where PowerShell is used for deallocation/start, add Bash/Azure CLI alternatives, especially in the 'Template' tab.
  • Clarify that PowerShell examples are for users on Windows, and link to cross-platform CLI alternatives where possible.
GitHub Create Pull Request