← Back to Dashboard
274
Pages Scanned
8
Pages Flagged
274
Changed Pages
2.9%
% Pages Flagged

Live Progress

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

Scan Information

Started At: 2026-02-11 00:00:06

Finished At: In Progress

Status: in_progress

Target Repo: Azure Compute

Current Phase: discovery

Files Queued: 274

Files Completed: 274

Problematic Pages

8 issues found
Virtual Machines Upgrade Gen1 VMs to Trusted launch ...s/virtual-machines/trusted-launch-existing-vm-gen-1.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation provides both Windows and Linux guidance for upgrading Gen1 VMs to Trusted launch, but Windows-specific tools (MBR2GPT.exe, Defrag, PowerShell) are mentioned first and in greater detail. The PowerShell upgrade example is shown before the CLI example, and ARM template deployment steps use PowerShell. Windows disk conversion and troubleshooting are much more detailed, while Linux instructions are brief and mostly validation steps. Windows tools and commands (MBR2GPT.exe, Defrag, reagentc) are referenced exclusively for disk conversion and troubleshooting, with no Linux disk conversion guidance provided.
Recommendations
  • Add Linux disk conversion guidance for cases where Gen1 Linux VMs do not have GPT/EFI (e.g., using gdisk, parted, or other tools).
  • Provide Linux-specific troubleshooting steps for disk layout and EFI partition issues.
  • Include ARM template deployment steps using Azure CLI, not just PowerShell.
  • Ensure Linux instructions are as detailed as Windows, especially for disk conversion and upgrade validation.
  • Consider showing CLI examples before PowerShell, or presenting them side-by-side.
GitHub Create Pull Request
Virtual Machines Resize a virtual machine ...blob/main/articles/virtual-machines/sizes/resize-vm.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation provides detailed PowerShell examples for resizing Azure VMs, including advanced scenarios (e.g., availability sets), while the Azure CLI section is less emphasized and lacks parity in depth and explanation. PowerShell is presented before CLI, and the Terraform example references a Windows-specific quickstart. There are no explicit Linux/macOS shell examples (e.g., Bash), and the Terraform code sample is Windows-focused. This creates friction for Linux/macOS users, who may prefer CLI or Bash-based workflows.
Recommendations
  • Provide Bash shell examples using Azure CLI for resizing VMs, with explanations matching the PowerShell section.
  • Ensure CLI examples cover advanced scenarios (e.g., availability sets) with the same level of detail as PowerShell.
  • Add a Linux-focused Terraform example or reference, or clarify that the steps are identical for Linux VMs.
  • Present CLI examples before PowerShell, or clarify that both are equally supported.
  • Avoid referencing only Windows-specific Terraform quickstarts; include or link to Linux quickstarts as well.
GitHub Create Pull Request
Virtual Machines FAQ for Trusted Launch ...b/main/articles/virtual-machines/trusted-launch-faq.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The FAQ for Trusted Launch covers both Windows and Linux VM scenarios, but there is a notable pattern where Windows/PowerShell examples and terminology are presented first or more prominently. CLI and PowerShell examples are given for most tasks, but Linux-specific CLI/bash examples are sometimes secondary or omitted. Windows terminology and links (e.g., Secure Boot, Hyper-V) appear before Linux equivalents, even when both are supported. However, Linux-specific guidance (e.g., SBInfo tool installation) is included, and the documentation does not exclude Linux users from completing tasks.
Recommendations
  • Ensure that Linux CLI/bash examples are presented alongside or before PowerShell/Windows examples where applicable.
  • Where possible, provide parity in example output for both Windows and Linux images (e.g., show both Windows and Linux sample JSON outputs).
  • Explicitly mention Linux tools and workflows in introductory sections, not just in troubleshooting.
  • Review the order of examples and links to avoid consistently prioritizing Windows/PowerShell.
  • Add more Linux-focused troubleshooting and validation steps where relevant.
GitHub Create Pull Request
Virtual Machines Trusted Launch for Azure VMs .../blob/main/articles/virtual-machines/trusted-launch.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation is generally cross-platform and explicitly states Trusted Launch applies to both Linux and Windows VMs. However, there are several subtle signs of Windows bias: Windows examples and references (such as ARM templates for Windows VMs) are listed first, links to Secure Boot and vTPM documentation point to Windows-focused resources, and virtualization-based security (VBS) and HVCI sections are Windows-only without clarifying their lack of Linux applicability. The only explicit example templates are for Windows VMs, with no Linux equivalents shown.
Recommendations
  • Add ARM template deployment examples for Linux VMs alongside Windows examples.
  • Include links to Linux-specific documentation for Secure Boot and vTPM, or clarify when referenced resources are Windows-only.
  • In sections describing features like VBS and HVCI, explicitly state that these are Windows-only and note Linux alternatives or limitations.
  • Ensure parity in example code, deployment walkthroughs, and troubleshooting steps for both Linux and Windows users.
GitHub Create Pull Request
Virtual Machines Deploy a Trusted Launch VM ...ain/articles/virtual-machines/trusted-launch-portal.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation covers Trusted Launch for both Linux and Windows VMs, with parity across portal, CLI, template, and PowerShell methods. However, PowerShell examples are Windows-centric and appear before Linux equivalents in some sections. In PowerShell sections, only Windows image/OS parameters are shown, and Linux PowerShell examples are missing. Additionally, PowerShell is presented as a primary automation method, which is more relevant to Windows users.
Recommendations
  • Add PowerShell examples for Linux VM deployment, including Linux image/OS parameters.
  • In PowerShell sections, clarify which steps are for Windows and which are for Linux, or provide parallel Linux-focused snippets.
  • Where possible, present Linux and Windows examples side-by-side or clearly label them.
  • Ensure that CLI and template examples continue to show Linux and Windows parity.
  • Consider mentioning cross-platform scripting tools (e.g., Bash, Python) for Linux users if relevant.
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: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Linux and Windows guidance, but PowerShell examples are heavily focused on Windows VM creation, with Windows-specific parameters (e.g., Set-AzVMOperatingSystem -Windows) and password authentication. Windows VM creation steps are shown first in PowerShell sections, and some network security group rules reference RDP (port 3389) before SSH (port 22). Linux examples are present (especially in CLI and REST), but Windows patterns and tools are often mentioned or demonstrated before Linux equivalents.
Recommendations
  • In PowerShell examples, provide explicit Linux VM creation steps (e.g., Set-AzVMOperatingSystem -Linux) alongside Windows examples, or clarify how to adapt for Linux.
  • When showing network security group rules, include SSH (port 22) examples before or alongside RDP (port 3389), and clarify Linux/Windows differences.
  • Ensure parity in authentication methods: demonstrate SSH key usage in PowerShell for Linux VMs, not just password-based authentication.
  • Where possible, alternate the order of Windows and Linux examples, or clearly label them to avoid implicit prioritization.
  • Add notes or links to Linux-specific guidance in sections where Windows patterns dominate.
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: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Azure CLI and PowerShell examples for creating VMs from specialized images, but the PowerShell sections are notably more detailed and extensive, including full network setup and VM configuration. CLI examples are concise and do not show equivalent network/resource configuration steps. Additionally, PowerShell examples (which are Windows-centric) are always present alongside CLI, but there are no bash or Linux shell script examples. In some sections, PowerShell is presented before Portal instructions, and the PowerShell examples use Windows conventions (e.g., RDP port blocking), which may not be relevant for Linux users.
Recommendations
  • Expand Azure CLI examples to include full VM/network setup steps, matching the detail of PowerShell examples.
  • Add bash/Linux shell script examples for common tasks, especially for network and VM configuration.
  • Clarify when PowerShell steps are Windows-specific or provide equivalent Linux-focused guidance (e.g., SSH port configuration).
  • Ensure CLI and PowerShell examples are equally detailed and placed in parallel, not favoring PowerShell.
  • Consider adding a section or note for Linux/macOS users about using Azure CLI in their environments.
GitHub Create Pull Request
Virtual Machines VM vCore Customization ...lob/main/articles/virtual-machines/vm-customization.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 VM vCore customization, but the PowerShell section is presented immediately after the CLI section and is detailed, which may suggest a slight Windows-first bias. However, the CLI example uses an Ubuntu image and is clearly cross-platform. There are no missing Linux examples, and no exclusive mention of Windows tools or patterns. The ARM template section is platform-neutral. The overall bias is minor and does not significantly impact Linux/macOS users.
Recommendations
  • Consider explicitly stating that Azure CLI commands are cross-platform and preferred for Linux/macOS users.
  • Add a brief note in the PowerShell section clarifying its Windows-centric nature.
  • Ensure parity in example detail between CLI and PowerShell sections.
  • Optionally, provide Bash shell scripting examples for Linux users, though Azure CLI already covers this.
GitHub Create Pull Request