← Back to Dashboard
19
Pages Scanned
4
Pages Flagged
19
Changed Pages
21.1%
% Pages Flagged

Live Progress

🔴 Connecting...
100%
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:08 Scan started

Scan Information

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

Finished At: 2026-01-23 18:07:07

Status: failed

Target Repo: Azure Compute

Current Phase: discovery

Files Queued: 19

Files Completed: 19

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: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
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 Windows-centric, with explicit use of Windows-specific parameters (e.g., Set-AzVMOperatingSystem -Windows) and RDP-related networking rules. In several PowerShell code blocks, only Windows VM creation is shown, while Linux VM creation is not addressed. Additionally, PowerShell examples appear before REST and Portal instructions, and often before CLI in some sections, which may reinforce a Windows-first perspective. CLI and REST examples do include Linux scenarios, but PowerShell is presented as the default for Windows, with no Linux PowerShell parity.
Recommendations
  • Add PowerShell examples for creating Linux VMs, using Set-AzVMOperatingSystem -Linux and appropriate credential handling.
  • In PowerShell networking examples, show how to open SSH (port 22) for Linux VMs, not just RDP (port 3389) for Windows.
  • Clearly label CLI and PowerShell examples as Linux or Windows, and provide both where possible.
  • Ensure that Linux scenarios are equally represented in PowerShell sections, not only in CLI/REST.
  • Consider alternating the order of CLI and PowerShell tabs, or defaulting to CLI (cross-platform) first.
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 network setup, while CLI examples are minimal. PowerShell is a Windows-centric tool, and there are no equivalent Linux shell (bash) or cross-platform scripting examples for the detailed VM/network configuration steps. In several sections, PowerShell examples are presented immediately after CLI, and the CLI examples are much shorter. There are no explicit Linux-specific command-line examples beyond Azure CLI, nor any mention of Linux-native tools or scripting patterns.
Recommendations
  • Provide detailed bash (Linux shell) scripting examples for VM and network resource creation, matching the depth of the PowerShell examples.
  • Clarify that Azure CLI is fully cross-platform and can be used on Linux/macOS, and offer sample scripts for those environments.
  • Where PowerShell is used for complex resource setup, offer equivalent Azure CLI commands or bash scripts to ensure Linux users can follow along without needing PowerShell.
  • Add notes or links to Linux/macOS-specific guidance for users who do not use PowerShell.
GitHub Create Pull Request
Virtual Machines Create a Gallery for Sharing Resources .../blob/main/articles/virtual-machines/create-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 examples for creating an Azure Compute Gallery using the Portal, Azure CLI, PowerShell, and REST API. While the CLI and REST examples are cross-platform, PowerShell examples are included and presented before REST, and the PowerShell section is Windows-centric. The ordering of examples places PowerShell before REST, which may subtly prioritize Windows tooling. However, Linux/macOS users can fully complete all tasks using the CLI or REST, and no critical functionality is missing for non-Windows platforms.
Recommendations
  • Explicitly note that PowerShell examples are for Windows users, and that Azure CLI and REST are cross-platform.
  • Consider placing CLI examples before PowerShell to emphasize cross-platform tooling.
  • Add a brief statement at the top clarifying that all tasks can be completed on Linux/macOS using CLI or REST.
  • Where possible, link to Azure CLI installation guides for Linux/macOS users.
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 the PowerShell example is given equal prominence despite being Windows-specific. The CLI example is cross-platform, but the tab order and structure may suggest Windows-first thinking. There are no Linux-specific command-line examples beyond Azure CLI, and PowerShell is highlighted as a primary method, which may create friction for Linux/macOS users.
Recommendations
  • Make it clear that Azure CLI is cross-platform and recommended for Linux/macOS users.
  • Consider listing the CLI example first, or explicitly noting platform compatibility for each method.
  • Add a brief note that PowerShell Core is available on Linux/macOS, but Azure CLI is typically preferred on those platforms.
  • If possible, include example output from Linux/macOS terminals to reinforce parity.
GitHub Create Pull Request