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

Scan Information

Started At: 2026-01-26 00:00:07

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 Gallery for Sharing Resources .../blob/main/articles/virtual-machines/create-gallery.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides examples for creating Azure Compute Galleries using the Portal, Azure CLI, PowerShell, and REST API. While the CLI and REST examples are cross-platform, PowerShell is a Windows-centric tool and is presented as a primary method. Additionally, PowerShell examples are given equal prominence as CLI, and are not marked as Windows-only, which may create friction for Linux/macOS users. The ordering of examples sometimes places PowerShell before REST, and there is no mention of Linux/macOS equivalents to PowerShell.
Recommendations
  • Clearly label PowerShell examples as Windows-only or for Windows users.
  • Present Azure CLI examples first, as it is cross-platform and preferred for Linux/macOS users.
  • Add a note for Linux/macOS users recommending Azure CLI or REST API for automation.
  • Consider omitting PowerShell examples or moving them to a dedicated Windows section if parity is not possible.
  • Ensure that all code snippets and instructions are platform-neutral unless a platform-specific tool is required.
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 networking setup, while the CLI examples are minimal. PowerShell is a Windows-centric tool, and the lack of parity in example depth and coverage creates friction for Linux/macOS users. Additionally, PowerShell examples are presented before CLI in some sections, and there are no Bash or Linux-native scripting examples for advanced scenarios.
Recommendations
  • Expand Azure CLI examples to include full VM creation workflows, including networking setup, to match the detail provided in PowerShell examples.
  • Add Bash shell scripting examples for Linux/macOS users, especially for advanced scenarios.
  • Ensure CLI examples are presented before or alongside PowerShell examples to avoid Windows-first perception.
  • Explicitly mention cross-platform compatibility for CLI commands and clarify that PowerShell examples are primarily for Windows users.
GitHub Create Pull Request
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 in an Azure Compute Gallery. However, PowerShell examples are heavily focused on Windows workflows, with parameters and cmdlets (e.g., Set-AzVMOperatingSystem -Windows) that are specific to Windows VM creation. Windows-centric networking (RDP port 3389) and credential prompts are shown by default. In several sections, Windows VM creation is described first or exclusively in PowerShell, while Linux is only mentioned as an alternative in CLI examples. There is limited guidance for Linux VM creation using PowerShell, and the REST and Portal instructions tend to treat Windows and Linux equally, but PowerShell sections are notably Windows-biased.
Recommendations
  • Add explicit PowerShell examples for creating Linux VMs, including the use of Set-AzVMOperatingSystem -Linux and SSH key authentication.
  • In PowerShell code blocks, clarify which parameters or cmdlets are for Windows and which are for Linux, and provide both variants.
  • When showing networking rules, include examples for both SSH (port 22) and RDP (port 3389), not just RDP.
  • Ensure that Linux VM creation is described with equal prominence in PowerShell sections, not just as a CLI alternative.
  • Consider alternating the order of Windows and Linux examples, or grouping them together for parity.
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 PowerShell (a Windows-centric tool) is given equal prominence and a dedicated tab. The CLI example is shown first, which is positive for Linux parity, but the presence of PowerShell examples may suggest a slight Windows bias, especially since no Linux-specific shell (e.g., Bash) or macOS-specific notes are included.
Recommendations
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows equally.
  • Add a note for Linux/macOS users confirming that Azure CLI is the recommended cross-platform tool.
  • Consider mentioning Bash scripting or providing example output from a Linux terminal to reinforce parity.
  • If possible, include a brief section on installing Azure CLI on Linux/macOS.
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 when enabling Trusted launch, with clear statements that the feature applies to both. However, there is mild Windows bias in the ordering and tooling: PowerShell examples are provided and referenced before Linux alternatives, and PowerShell is used for ARM template deployment and VM deallocation, even though Linux users would likely prefer Bash or Azure CLI. The verification step mentions RDP (Windows) before SSH (Linux) throughout. There are no missing Linux examples, and the CLI instructions are cross-platform.
Recommendations
  • Provide Bash shell examples for ARM template deployment and VM deallocation alongside PowerShell, or clarify that PowerShell commands can be run on Linux/macOS using PowerShell Core.
  • Alternate the order of RDP/SSH mentions, or mention SSH first in Linux-specific contexts.
  • Explicitly state that all CLI and template steps are cross-platform and can be performed from Linux/macOS.
  • For template deployment, offer Azure CLI examples in addition to PowerShell.
GitHub Create Pull Request