← Back to Dashboard
25
Pages Scanned
4
Pages Flagged
25
Changed Pages
16.0%
% Pages Flagged

Scan Information

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

Finished At: 2026-02-10 18:00:39

Status: completed

Target Repo: Azure Compute

Current Phase: discovery

Files Queued: 25

Files Completed: 25

Problematic Pages

4 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: 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, but PowerShell examples are heavily Windows-centric, with explicit use of Windows-specific parameters (e.g., Set-AzVMOperatingSystem -Windows) and RDP-related network security rules. In several PowerShell code blocks, only Windows VM creation is shown, with no Linux equivalent. Additionally, in PowerShell sections, Windows configuration is presented first and exclusively, while CLI examples are more Linux-focused. REST and Portal instructions do cover both OS types, but PowerShell users on Linux/macOS are left without clear guidance.
Recommendations
  • Add PowerShell examples for creating Linux VMs, using Set-AzVMOperatingSystem -Linux and relevant SSH configuration.
  • In PowerShell sections, provide both Windows and Linux VM creation code blocks, or clarify how to adapt the examples for Linux.
  • When showing network security rules, include SSH (port 22) examples alongside RDP (port 3389) for Linux scenarios.
  • Explicitly note PowerShell cross-platform support and any differences for Linux/macOS users.
  • Ensure parity in example coverage and ordering between Windows and Linux across all tooling sections.
GitHub 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 instructions for enabling Trusted launch on Azure Gen2 VMs using multiple methods (Portal, CLI, PowerShell, ARM template). While the feature applies to both Linux and Windows VMs, there is a notable bias toward Windows tools and patterns: PowerShell is given equal prominence to CLI, and ARM template examples use PowerShell for deployment. In several places, PowerShell is used for actions that could be performed with cross-platform tools. Additionally, PowerShell is referenced before CLI in some sections, and the use of RDP (Windows) is mentioned before SSH (Linux) when verifying VM access.
Recommendations
  • Provide Bash (or cross-platform) examples for ARM template deployment, not just PowerShell.
  • When referencing remote access, list SSH (Linux) before RDP (Windows) or mention both equally.
  • Ensure CLI and PowerShell examples are presented with equal prominence, or clarify that PowerShell is not required for Linux/macOS users.
  • Where possible, use cross-platform tools (e.g., Azure CLI) in examples and deployment steps.
  • Add explicit notes for Linux/macOS users about how to perform steps without PowerShell.
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: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for all major workflows, but the PowerShell examples are significantly more detailed, including full network and VM configuration steps, while the CLI examples are minimal. PowerShell is a Windows-centric tool, and the CLI is cross-platform. Additionally, PowerShell examples are presented immediately after CLI examples, which is a common pattern but may reinforce Windows-first perceptions. There are no Linux/macOS-specific shell examples (e.g., Bash), and no explicit mention of Linux-specific considerations, but the CLI examples are suitable for Linux/macOS users.
Recommendations
  • Expand CLI examples to include full VM and network configuration steps, matching the detail of PowerShell examples.
  • Explicitly state that Azure CLI commands are cross-platform and suitable for Linux/macOS users.
  • Consider providing Bash script examples for Linux users, especially for more complex workflows.
  • Ensure parity in example detail and guidance between CLI and PowerShell sections.
  • Add notes or links for Linux/macOS users about prerequisites or environment setup if relevant.
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 presents both Azure CLI and PowerShell examples for checking vCPU quotas, but the PowerShell section is given equal prominence despite being Windows-centric. The CLI example is cross-platform, but PowerShell is Windows-first and may not be available or commonly used on Linux/macOS. The page does not provide Linux/macOS-specific shell examples (e.g., Bash), but the CLI example is sufficient for those platforms.
Recommendations
  • Clearly indicate that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Add a note clarifying that PowerShell examples are primarily for Windows users, and that Azure CLI works on all platforms.
  • Consider listing the CLI example first to emphasize cross-platform compatibility.
  • Optionally, provide Bash scripting examples for advanced Linux users.
GitHub Create Pull Request