55
Pages Scanned
6
Pages Flagged
55
Changed Pages
10.9%
% Pages Flagged

Scan Information

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

Finished At: 2026-01-22 00:28:14

Status: completed

Target Repo: Azure Compute

Current Phase: discovery

Files Queued: 55

Files Completed: 55

Problematic Pages

6 issues found
Virtual Machine Scale Sets Creating and configuring a key vault for Azure Disk Encryption ...irtual-machine-scale-sets/disk-encryption-key-vault.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 mentions both Azure CLI and Azure PowerShell as supported tools, but PowerShell is listed before CLI in several places, and the 'Next steps' section gives PowerShell examples equal prominence to CLI. There is no explicit Linux/macOS example or guidance, and PowerShell is a Windows-centric tool, potentially creating friction for Linux/macOS users.
Recommendations
  • List Azure CLI before PowerShell in tool recommendations and examples, as CLI is cross-platform.
  • Explicitly state that Azure CLI works on Linux/macOS and provide links or notes for installation on those platforms.
  • Ensure examples and walkthroughs are available for both Azure CLI and PowerShell, with clear labeling for platform compatibility.
  • Add a brief section or note for Linux/macOS users, confirming parity and pointing to relevant CLI documentation.
Virtual Machine Scale Sets Use Azure Log Analytics to monitor standby pool events ...achine-scale-sets/standby-pools-monitor-pool-events.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 configuring diagnostic settings, but PowerShell is given equal prominence despite being Windows-centric. There is no explicit Linux shell (bash) example, and PowerShell is listed as a primary method alongside CLI and REST. The guidance does not mention Linux-specific considerations or alternative Linux-native tools, and PowerShell is presented as a recommended SDK for non-portal configuration, which may create friction for Linux/macOS users.
Recommendations
  • Add explicit bash shell examples for configuring diagnostic settings using Azure CLI, demonstrating usage on Linux/macOS.
  • Clarify that PowerShell examples are for Windows users, and recommend Azure CLI for cross-platform usage.
  • Reorder examples to present CLI (cross-platform) before PowerShell, and explicitly state CLI is recommended for Linux/macOS.
  • Include a note about installing and using Azure CLI on Linux/macOS.
  • If PowerShell is required for any advanced scenario, explain how to use PowerShell Core on Linux/macOS.
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation provides detailed PowerShell examples for checking and initiating maintenance on Virtual Machine Scale Sets, with CLI equivalents included. However, PowerShell is featured first and in more detail, and there are no explicit Bash or Linux shell script examples. References to 'scheduled events' link to Windows-specific documentation, and there is no mention of Linux-specific guidance or parity for those features.
Recommendations
  • Add explicit Bash or shell script examples for common Linux environments, especially for querying maintenance status and initiating maintenance using the Azure CLI.
  • When referencing 'scheduled events', include or link to Linux/macOS documentation (e.g., scheduled events for Linux VMs) alongside or before Windows links.
  • Present CLI examples before PowerShell, or at least in parallel, to avoid the impression that PowerShell is the primary or preferred method.
  • Clarify that all CLI commands work cross-platform (Windows, Linux, macOS), and provide any Linux/macOS-specific notes if needed.
Virtual Machines Create and upload a CentOS-based Linux VHD ...rticles/virtual-machines/linux/create-upload-centos.md
Medium 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 for creating and uploading a CentOS-based Linux VHD demonstrates a moderate Windows bias. It consistently references Hyper-V (a Windows virtualization tool) as the primary or sole example for creating VHDs, provides step-by-step instructions using Hyper-V Manager, and links to Windows-specific guides. While it mentions alternatives like VirtualBox and KVM, detailed instructions and examples for these Linux-native tools are missing. This creates friction for Linux/macOS users who may not have access to Hyper-V and need guidance for their platforms.
Recommendations
  • Add detailed instructions and examples for creating and preparing VHDs using Linux-native tools such as qemu-img, KVM, and VirtualBox.
  • Provide parity in step-by-step guidance for Linux and macOS users, including how to convert disk formats and manage VM lifecycle without Hyper-V.
  • Include links to relevant Linux documentation and official guides for virtualization and disk preparation.
  • Reorder sections so Linux-native tools are presented before or alongside Hyper-V, or clarify that Hyper-V is just one option.
Virtual Machines Azure Disk Encryption scenarios on Linux VMs ...ticles/virtual-machines/linux/disk-encryption-linux.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
While the documentation is focused on Azure Disk Encryption for Linux VMs and provides both Azure CLI and PowerShell examples, there is a notable tendency to mention PowerShell cmdlets and workflows first or more prominently in several sections. PowerShell is a Windows-centric tool, and its usage is emphasized alongside CLI, sometimes with more detailed scripts and explanations. In some places, PowerShell is referenced before CLI, and backup/restore instructions often cite PowerShell cmdlets before CLI equivalents. However, Linux users are not blocked from completing any tasks, as CLI examples are present for all major operations.
Recommendations
  • Ensure CLI examples are presented before or alongside PowerShell examples, especially in introductory and critical workflow sections.
  • Where PowerShell scripts are shown in detail, provide equally detailed CLI command sequences and context.
  • Clarify that PowerShell can be run cross-platform (including on Linux/macOS), but highlight CLI as the native choice for Linux users.
  • Review backup/restore and prerequisite instructions to ensure CLI commands are not omitted or relegated to secondary status.
  • Add explicit guidance for Linux users on choosing between CLI and PowerShell, mentioning that CLI is typically pre-installed or easier to set up on Linux.
Virtual Machines Migrate Managed image to Compute gallery ...igration/migration-managed-image-to-compute-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 migration steps for both Linux and Windows VMs, and offers examples for Portal, Azure CLI, and PowerShell. However, PowerShell examples are included alongside CLI, and the CLI example uses backticks (`) for line continuation, which is a Windows shell convention. The PowerShell section is given equal prominence, and the CLI example does not clarify Linux/macOS usage (e.g., line continuation, authentication differences). There is a slight Windows-first bias in example formatting and tool choice, but Linux users can complete the task using the CLI.
Recommendations
  • Clarify CLI example line continuation for Linux/macOS (use '\' instead of '`').
  • Add explicit notes or examples for Linux/macOS shell usage in CLI section.
  • Consider mentioning Bash or Cloud Shell as alternatives for Linux/macOS users.
  • Ensure CLI examples are cross-platform and avoid Windows-specific syntax.
  • Add a note that PowerShell is available cross-platform, but clarify usage differences if any.