← Back to Dashboard
45
Pages Scanned
2
Pages Flagged
45
Changed Pages
4.4%
% Pages Flagged

Scan Information

Started At: 2026-01-08 00:53:04

Finished At: 2026-01-08 22:14:25

Status: completed

Target Repo: Azure Compute

Current Phase: discovery

Files Queued: 45

Files Completed: 45

Problematic Pages

2 issues found
Virtual Machines https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/sizes/general-purpose/ddsv6-series.md ...virtual-machines/sizes/general-purpose/ddsv6-series.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page shows mild Windows bias. It references Windows-specific technologies (such as Hyper-V for nested virtualization) and Windows tools (NTTTCP for network testing) without mentioning Linux equivalents or alternatives. In several places, Windows features are listed before Linux ones, and some links point to Windows documentation first. There are no Linux-specific command-line examples, tools, or optimization guidance, and Linux parity is not explicitly addressed.
Recommendations
  • Include Linux equivalents for referenced Windows tools (e.g., mention 'iperf' or 'nuttcp' for network testing alongside NTTTCP).
  • Provide links to Linux-specific documentation where Windows documentation is referenced (e.g., nested virtualization on KVM/QEMU).
  • Ensure Linux features and restrictions are listed before or alongside Windows ones, not after.
  • Add Linux command-line examples or optimization tips where relevant (e.g., disk performance tuning, network throughput testing).
  • Explicitly state Linux support and limitations in feature tables, not just in footnotes or restrictions.
  • Review all external links to ensure Linux documentation is equally discoverable.
GitHub Create Pull Request
Virtual Machines https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/automatic-vm-guest-patching.md ...ticles/virtual-machines/automatic-vm-guest-patching.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation demonstrates several forms of Windows bias. Windows-specific examples (PowerShell, CLI) are provided before or in greater detail than Linux equivalents. PowerShell examples are given for Windows VMs but not for Linux VMs, and CLI examples for Windows VMs are more detailed. Windows registry keys and Windows Update service requirements are described explicitly, while Linux equivalents (such as disabling automatic updates) are less thoroughly explained. The 'Next steps' section links only to Windows VM management, omitting Linux VM guidance.
Recommendations
  • Provide Azure PowerShell examples for Linux VMs where applicable, or clarify PowerShell usage for Linux.
  • Ensure CLI examples for Linux VMs are as detailed as those for Windows VMs, including update and patching scenarios.
  • Mention Linux-specific tools and configuration patterns (e.g., apt, yum, zypper, systemctl) with equal prominence to Windows tools (e.g., registry keys, Windows Update).
  • Add a 'Next steps' link for Linux VM management, mirroring the Windows VM link.
  • Where requirements or behaviors differ (e.g., disabling automatic updates), provide step-by-step instructions for both Linux and Windows, not just Windows.
  • Present OS-specific information in parallel sections, or alternate the order between Windows and Linux to avoid implicit prioritization.
GitHub Create Pull Request