← Back to Dashboard
51
Pages Scanned
4
Pages Flagged
51
Changed Pages
7.8%
% Pages Flagged

Scan Information

Started At: 2026-01-13 00:00:08

Finished At: 2026-01-13 06:08:09

Status: completed

Target Repo: Azure Compute

Current Phase: discovery

Files Queued: 51

Files Completed: 51

Problematic Pages

4 issues found
Virtual Machines Automatic Guest Patching for Azure Virtual Machines and Scale Sets ...ticles/virtual-machines/automatic-vm-guest-patching.md
Medium 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 page exhibits moderate Windows bias. Windows-specific examples (PowerShell, CLI) are presented before Linux equivalents, and Windows tooling (PowerShell cmdlets, registry keys, WSUS) is referenced more frequently and in greater detail. Linux-specific examples are present but sometimes less detailed or appear after Windows instructions. Some sections (e.g., patch orchestration modes) provide more options and explanations for Windows than Linux. The 'Next steps' link is Windows-focused.
Recommendations
  • Present Linux and Windows examples side-by-side or alternate their order to avoid Windows-first bias.
  • Expand Linux-specific instructions and examples, especially for CLI and PowerShell usage.
  • Add parity for Linux in sections where only Windows options are described (e.g., patch orchestration modes, disabling automatic updates).
  • Include Linux-focused 'Next steps' links, such as guides for managing Linux VMs.
  • Where Windows registry keys or services are mentioned, provide equivalent Linux configuration details (e.g., for disabling automatic updates).
GitHub Create Pull Request
Virtual Machine Scale Sets Create a Virtual Machine Scale Set with instance mix ...cles/virtual-machine-scale-sets/instance-mix-create.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ windows_first
Summary
The documentation provides examples for Azure Portal, Azure CLI, Azure PowerShell, and REST API. While CLI and REST API are cross-platform, the PowerShell section is extensive and detailed, with multiple example scenarios and configuration objects, whereas the CLI section is brief and limited to basic usage. The prerequisites mention PowerShell and its module version before CLI, and PowerShell examples are given equal or greater prominence than CLI, which may indicate a Windows bias. There are no Linux-specific tools or shell examples (e.g., Bash scripts), and PowerShell is a Windows-centric tool, despite its cross-platform availability.
Recommendations
  • Expand the Azure CLI section to include advanced scenarios, such as using configuration objects and allocation strategies, matching the depth of PowerShell examples.
  • Add Bash script examples for Linux users, especially for tasks like parameter substitution and automation.
  • In prerequisites, mention CLI and PowerShell together, or list CLI first to avoid Windows-first perception.
  • Clarify that PowerShell is available cross-platform, but highlight Linux-native tools where possible.
  • Consider adding a section or tips for Linux/macOS users, such as SSH key management or environment setup.
GitHub Create Pull Request
Virtual Machines Instantly access managed disk snapshots ...les/virtual-machines/disks-instant-access-snapshots.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation provides both Azure CLI (cross-platform) and Azure PowerShell (Windows-centric) examples for creating instant access snapshots, but omits explicit Linux/macOS shell examples and does not mention platform-specific nuances. PowerShell instructions are given equal prominence to CLI, and there are no bash-specific or Linux/macOS workflow notes. The order of examples sometimes places PowerShell before or alongside CLI, and there is no mention of Linux tools or troubleshooting. No Linux/macOS-specific issues or guidance are discussed.
Recommendations
  • Add explicit bash/Linux/macOS shell examples, clarifying that Azure CLI commands work natively on these platforms.
  • Include notes about installing and using Azure CLI on Linux/macOS, and clarify that PowerShell is Windows-centric (though cross-platform PowerShell exists).
  • Highlight any platform-specific differences in disk attachment or hydration processes, if applicable.
  • Provide troubleshooting tips for Linux/macOS users, e.g., permissions, environment variables, or shell compatibility.
  • Consider listing Azure CLI (cross-platform) examples before PowerShell to reduce perceived Windows bias.
GitHub Create Pull Request
Virtual Machines Ddsv6 size series ...virtual-machines/sizes/general-purpose/ddsv6-series.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first
Summary
The documentation page is largely neutral, focusing on VM specifications and features. However, there is mild Windows bias in the 'Feature support' section, where 'Nested Virtualization' links to a Windows-specific guide, and in the 'Bandwidth/Throughput testing (NTTTCP)' reference, which is a Windows-centric tool. No Linux-specific examples or tools are mentioned, and Windows references appear before Linux equivalents (if any).
Recommendations
  • Include links to Linux-specific nested virtualization documentation or clarify Linux support status.
  • Mention Linux-compatible bandwidth/throughput testing tools (e.g., iperf, ntttcp-for-linux) alongside NTTTCP.
  • Where features/tools are OS-specific, explicitly state Linux/macOS alternatives or limitations.
  • Ensure parity in documentation references for both Windows and Linux environments.
GitHub Create Pull Request