Virtual Machines

1080
Total Pages
1005
Linux-Friendly Pages
75
Pages with Bias
6.9%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

815 issues found
Showing 151-175 of 815 flagged pages
Virtual Machines Associate a virtual machine to a capacity reservation group .../virtual-machines/capacity-reservation-associate-vm.md
Medium Priority View Details →
Scanned: 2026-02-26 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Minor Windows Arm Template
Summary
The documentation covers both Windows and Linux VMs, with parity in CLI and API instructions. However, PowerShell examples are provided alongside CLI, and ARM template examples are heavily Windows-centric (defaulting to Windows images and parameters). Windows-specific tools (PowerShell) are featured equally with cross-platform CLI, and ARM template parameters focus on Windows OS versions, with no Linux ARM template shown. Portal instructions are neutral. The CLI examples do use a Linux image (Ubuntu2204), but the ARM template is Windows-only.
Recommendations
  • Add ARM template examples for Linux VMs (e.g., Ubuntu, CentOS) alongside the Windows ARM template.
  • Clarify in the ARM template section that Linux images can be used, and provide parameter options for Linux OS.
  • Consider showing CLI examples for both Windows and Linux images, or explicitly state that the CLI works for both.
  • If PowerShell is shown, also mention Bash or other Linux-native scripting options where relevant.
  • Ensure that cross-platform tools (CLI, API, Portal) are always presented before Windows-specific tools (PowerShell).
GitHub Create Pull Request
Virtual Machines Restrict managed disks from being imported or exported ...tual-machines/disks-restrict-import-export-overview.md
Medium Priority View Details →
Scanned: 2026-02-26 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Azure CLI and PowerShell options for configuring the NetworkAccessPolicy, but references to PowerShell and Windows-centric links (e.g., custom roles via PowerShell) appear first or are emphasized. The custom RBAC role section links only to a PowerShell-based guide, and the PowerShell module is mentioned alongside Azure CLI, but not after or equally. There are no explicit Linux-only examples or links, and the CLI link for private links is labeled 'linux', but the main guidance is not Linux-focused.
Recommendations
  • Add links to custom RBAC role creation using Azure CLI and/or Azure Portal, not just PowerShell.
  • Ensure Azure CLI examples are presented before or equally with PowerShell examples.
  • Clarify that both Azure CLI and PowerShell are cross-platform, and provide explicit Linux/macOS guidance where relevant.
  • Where possible, provide portal-based instructions for users on any platform.
GitHub Create Pull Request
Virtual Machines Create and upload an Ubuntu Linux VHD in Azure ...rticles/virtual-machines/linux/create-upload-ubuntu.md
Medium Priority View Details →
Scanned: 2026-02-26 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation, while focused on Ubuntu Linux VHDs, repeatedly references Windows-centric tools and workflows (Hyper-V, PowerShell's Convert-VHD) as primary methods for creating and converting VHDs. Windows/Hyper-V steps are described first and in detail, with no equivalent Linux-native tooling or instructions for VHD creation/conversion. Linux users are left without clear guidance for critical steps such as converting disk formats or creating VHDs, creating friction and potential blockers.
Recommendations
  • Add instructions and examples for creating and converting VHDs using Linux-native tools (e.g., qemu-img, VBoxManage, dd).
  • Provide Linux CLI alternatives for disk conversion and VM preparation, not just referencing Hyper-V and PowerShell.
  • Mention and link to relevant Linux virtualization solutions (e.g., KVM, VirtualBox, QEMU) alongside Hyper-V.
  • Ensure that Linux steps are presented first or in parallel with Windows steps, given the Linux-focused topic.
  • Clarify that Hyper-V and PowerShell are optional and provide parity for Linux/macOS users.
GitHub Create Pull Request
Virtual Machines Create an Azure Image Builder Bicep file or ARM template JSON template .../articles/virtual-machines/linux/image-builder-json.md
Medium Priority View Details →
Scanned: 2026-02-26 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation covers both Linux and Windows VM image creation with Azure Image Builder, providing parity in most sections. However, there are several areas where Windows bias is evident: PowerShell examples and tools (e.g., Get-FileHash) are often shown first or exclusively, especially for checksum generation and generalization steps; Windows customizers (PowerShell, WindowsRestart, WindowsUpdate) are described in more detail, and Windows-specific commands are presented before Linux equivalents. Linux examples are present but sometimes appear after Windows ones or lack equivalent detail. Some tool references (e.g., PowerShell for checksum) do not mention Linux alternatives alongside.
Recommendations
  • Ensure Linux (bash/terminal) examples are shown alongside or before Windows/PowerShell examples, especially for common tasks like checksum generation.
  • When referencing tools (e.g., Get-FileHash), always mention the Linux/macOS equivalent (e.g., sha256sum) in the same context.
  • Provide equal detail for Linux customizers and validation steps as for Windows (e.g., Shell customizer, Linux restart guidance).
  • Where Windows customizers are described (e.g., WindowsRestart), clarify Linux alternatives or explicitly state limitations.
  • Review ordering of examples and tool references to avoid Windows-first presentation.
GitHub Create Pull Request
Virtual Machines Azure Disk Encryption scenarios on Linux VMs ...ticles/virtual-machines/linux/disk-encryption-linux.md
Medium Priority View Details →
Scanned: 2026-02-26 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all major operations, but PowerShell cmdlets and patterns are heavily emphasized throughout, including frequent references to PowerShell-specific parameters and behaviors. PowerShell examples are often given equal or greater prominence than Azure CLI, despite the Linux focus. There are also multiple references to using PowerShell locally, which is a Windows-centric tool, and some instructions assume familiarity with PowerShell scripting conventions. Additionally, PowerShell is mentioned first in several sections, and some backup/restore instructions reference PowerShell cmdlets before CLI equivalents.
Recommendations
  • Prioritize Azure CLI examples and instructions before PowerShell, as CLI is cross-platform and native to Linux/macOS.
  • Clarify that PowerShell can be run on Linux/macOS, but recommend Azure CLI as the default for Linux users.
  • Add explicit guidance for Linux users on installing and using Azure CLI, including troubleshooting for common Linux issues.
  • Where PowerShell-specific behaviors are discussed (e.g., sequence version handling), provide equivalent CLI notes or highlight CLI's advantages for Linux users.
  • Reduce reliance on PowerShell scripting conventions in example scripts; use CLI syntax and patterns where possible.
  • Ensure backup/restore instructions reference CLI and portal options before PowerShell.
GitHub Create Pull Request
Virtual Machines Upload a VHD to Azure or copy a disk across regions - Azure CLI ...machines/linux/disks-upload-vhd-to-managed-disk-cli.md
Medium Priority View Details →
Scanned: 2026-02-26 00:00
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 and Bash scripting examples, but the AzCopy upload example is given only for Windows (using AzCopy.exe and a Windows file path). There is no explicit Linux/macOS AzCopy example, and the Windows-style example is shown first. The documentation mentions using 'wc' and 'ls' for file size, which are Linux commands, but does not provide a PowerShell equivalent for Windows users. Overall, the AzCopy upload step is Windows-centric, creating friction for Linux/macOS users.
Recommendations
  • Add a Linux/macOS AzCopy example (using './azcopy' and a Unix-style file path, e.g., '/home/user/mydisk.vhd').
  • Clarify that AzCopy is cross-platform and provide download/install instructions for Linux/macOS.
  • Mention that Bash scripts and Azure CLI commands work on both Linux and Windows, and provide PowerShell equivalents for file size calculation for Windows users.
  • Present both Windows and Linux/macOS examples side-by-side, or note differences where relevant.
GitHub Create Pull Request
Virtual Machines Run scripts in a Linux VM in Azure using managed Run Commands ...articles/virtual-machines/linux/run-command-managed.md
Medium Priority View Details →
Scanned: 2026-02-26 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
While the documentation is focused on Linux VMs, there is notable bias toward Windows tooling and PowerShell usage. PowerShell examples are provided extensively, sometimes before or instead of Azure CLI examples. Windows-specific tools and patterns (e.g., PowerShell cmdlets, SAS token generation via PowerShell, REST API examples using PowerShell scripts) are referenced frequently. There are missing or minimal Linux-native scripting examples (e.g., bash, shell scripting), and some sections use Windows terminology or tools first. REST API and ARM template examples often use PowerShell scripts (.ps1) as the default, rather than shell scripts (.sh).
Recommendations
  • Provide more bash/shell script examples alongside PowerShell, especially in REST API and ARM template sections.
  • Ensure Azure CLI examples are given equal prominence and detail as PowerShell examples.
  • When referencing SAS token generation or blob operations, include CLI or Linux-native methods (e.g., az storage blob generate-sas) in addition to PowerShell.
  • Use .sh scripts as the default in Linux-focused examples, or show both .ps1 and .sh variants.
  • Clarify when a tool or method is Windows-specific, and offer Linux alternatives where possible.
  • Review and adjust ordering so Linux-native tools and examples are presented first or equally.
GitHub Create Pull Request
Virtual Machines Customer intent: "As an IT administrator managing Azure IaaS virtual machines, I want to implement a backup and disaster recovery plan for unmanaged disks, so that I can ensure data durability and high availability in the event of localized or regional failures." ...al-machines/page-blobs-backup-and-disaster-recovery.md
Medium Priority View Details →
Scanned: 2026-02-26 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation covers backup and disaster recovery for Azure unmanaged disks and is intended for both Linux and Windows VMs. However, there are several instances where Windows tools (e.g., PowerShell, Volume Shadow Service) are mentioned first or exclusively, and Linux equivalents are referenced later or less prominently. Some example links and instructions (e.g., incremental snapshots, SQL Server backup) point to Windows-specific pages or tools, and PowerShell is often listed as the primary scripting option, with less emphasis on Azure CLI or Linux-native tools. Application-consistent backup for Linux is referenced but not explained in detail. There are also references to Windows-specific backup mechanisms (e.g., VSS) without clear Linux alternatives.
Recommendations
  • Ensure Linux and Azure CLI examples are provided alongside PowerShell, especially in sections about scripting and automation.
  • When mentioning Windows tools (e.g., Volume Shadow Service), immediately provide Linux equivalents (e.g., fsfreeze, application-consistent backup for Linux) and link to relevant Linux documentation.
  • Balance references to Windows and Linux in tables and step-by-step instructions, avoiding Windows-first ordering.
  • Add explicit Linux examples for incremental snapshots and backup/restore workflows, including links to Linux-specific guides.
  • Clarify and expand on application-consistent backup for Linux, including how to achieve it and any limitations.
GitHub Create Pull Request
Virtual Machines Upload a VHD to Azure or copy a disk across regions - Azure CLI ...machines/linux/disks-upload-vhd-to-managed-disk-cli.md
Medium Priority View Details →
Scanned: 2026-02-25 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides a Windows-centric AzCopy example (using AzCopy.exe and Windows file paths) for uploading a VHD, without showing a Linux/macOS equivalent. The only explicit upload command uses Windows syntax, and there is no mention of how to run AzCopy on Linux/macOS or what the command would look like. The rest of the CLI instructions are cross-platform, but the upload step is critical and lacks Linux parity.
Recommendations
  • Add a Linux/macOS AzCopy example (using ./azcopy and POSIX file paths, e.g., /home/user/mydisk.vhd).
  • Clarify that AzCopy is cross-platform and provide download/install instructions for Linux/macOS.
  • Mention any OS-specific considerations (such as file permissions or path formats) for AzCopy usage.
  • Consider showing both Windows and Linux/macOS examples side-by-side for key steps.
GitHub Create Pull Request
Virtual Machines Associate a virtual machine to a capacity reservation group .../virtual-machines/capacity-reservation-associate-vm.md
Medium Priority View Details →
Scanned: 2026-02-25 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Arm Template Windows
Summary
The documentation provides parity for both Windows and Linux VMs, as indicated in the 'Applies to' section and CLI examples (with Ubuntu image). However, there are signs of Windows bias: PowerShell examples are always present, ARM template examples are Windows-centric (only Windows images and OS versions), and Windows-specific parameters are used in templates. The ARM template section lacks Linux image examples or parameters. Additionally, Windows terminology and tools (PowerShell) are referenced throughout, and in some sections (ARM template), Windows is the default or only option.
Recommendations
  • Add Linux image options and parameters to ARM template examples (e.g., Ubuntu, CentOS, etc.).
  • Include Linux-specific OSVersion values and imageReference blocks in ARM templates.
  • Clarify that PowerShell examples are for Windows users and provide Bash or shell script equivalents for Linux/macOS users where relevant.
  • Ensure that CLI and API examples consistently use both Windows and Linux VM images, or alternate between them.
  • Consider providing a sample ARM template for a Linux VM alongside the Windows example.
GitHub Create Pull Request
Virtual Machines Create and upload an Ubuntu Linux VHD in Azure ...rticles/virtual-machines/linux/create-upload-ubuntu.md
Medium Priority View Details →
Scanned: 2026-02-25 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page, while focused on Ubuntu Linux, repeatedly references Windows-specific tools and workflows (notably Hyper-V and PowerShell's Convert-VHD) as primary methods for creating and converting VHDs. Windows/Hyper-V steps are described first and in detail, with no equivalent Linux-native tooling or workflows provided for critical steps like VHD creation and conversion. This creates friction for Linux users, who may not have access to Hyper-V or PowerShell.
Recommendations
  • Add instructions for creating and converting VHDs using Linux-native tools (e.g., qemu-img, VBoxManage, or dd).
  • Provide example workflows for preparing and converting disks on Linux hosts, including alignment and format conversion.
  • Mention Linux virtualization solutions (e.g., KVM, VirtualBox) alongside Hyper-V, and link to relevant guides.
  • Ensure that all critical steps (such as VHD conversion to fixed size) have Linux alternatives documented.
  • Clarify that Hyper-V and PowerShell are optional, not required, and highlight cross-platform approaches.
GitHub Create Pull Request
Virtual Machines Run scripts in a Linux VM in Azure using managed Run Commands ...articles/virtual-machines/linux/run-command-managed.md
Medium Priority View Details →
Scanned: 2026-02-25 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation is primarily focused on Linux VMs, but there is notable Windows bias in several areas. PowerShell examples and tools (e.g., Set-AzVMRunCommand, Get-AzVMRunCommand, New-AzStorageBlobSASToken) are heavily featured, sometimes with Windows-specific notes and terminology. REST and ARM template examples occasionally use Windows-centric script syntax (e.g., Write-Host, .ps1 files) and refer to Windows behaviors. In some sections, Windows tools and patterns (PowerShell, SAS token generation) are mentioned before or instead of Linux-native alternatives. However, the Azure CLI section is well-represented for Linux users, and most examples are applicable to Linux VMs.
Recommendations
  • Ensure REST and ARM template examples use Linux shell script syntax (e.g., 'echo Hello World!' or .sh files) rather than PowerShell/Windows scripts.
  • Clarify when PowerShell examples are cross-platform (usable on macOS/Linux) and when they are Windows-only.
  • Add explicit bash or Linux-native command-line examples for SAS token generation and blob management (e.g., using Azure CLI or azcopy), not just PowerShell.
  • Review notes and parameter descriptions to avoid Windows-centric language (e.g., referencing 'myscript.ps1' or 'Write-Host') when the context is Linux.
  • Where possible, show Linux examples first or equally alongside Windows/PowerShell examples.
GitHub Create Pull Request
Virtual Machines Associate a virtual machine to a capacity reservation group .../virtual-machines/capacity-reservation-associate-vm.md
Medium Priority View Details →
Scanned: 2026-02-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation covers both Windows and Linux VMs, but several sections show Windows bias. PowerShell examples are provided alongside CLI, but there are no Bash or Linux shell script equivalents. The ARM template example is Windows-only, with no Linux image option. In some cases, Windows terminology (e.g., password complexity, OSVersion) is emphasized or appears first. While Azure CLI is cross-platform and Linux is mentioned, Linux-specific examples and parity in templates are lacking.
Recommendations
  • Add Linux-specific ARM template examples, including Ubuntu or other popular Linux distributions in the 'imageReference' section.
  • Provide Bash or Linux shell script examples where PowerShell is used, or clarify that PowerShell is available cross-platform.
  • Ensure password/account creation instructions are inclusive of Linux (e.g., SSH key setup for Linux VMs, not just username/password).
  • Balance the order of examples so Linux and Windows are equally represented, or alternate which appears first.
  • Clarify in each section that the instructions apply to both Windows and Linux VMs, and highlight any OS-specific differences.
GitHub Create Pull Request
Virtual Machines Restrict managed disks from being imported or exported ...tual-machines/disks-restrict-import-export-overview.md
Medium Priority View Details →
Scanned: 2026-02-23 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Azure CLI and PowerShell options for configuring the NetworkAccessPolicy, but references to PowerShell and Windows-centric links appear before Linux equivalents. The custom RBAC role section links to a PowerShell-based guide, and PowerShell is mentioned alongside CLI, potentially creating friction for Linux/macOS users. However, CLI options are present, and the topic is not inherently Windows-specific.
Recommendations
  • Ensure that Linux/CLI examples and links are given equal prominence and placement as PowerShell/Windows examples.
  • Add explicit Linux/macOS instructions or links for custom RBAC role creation, not just PowerShell.
  • Where possible, provide cross-platform guidance (e.g., Bash, CLI, PowerShell) side-by-side.
  • Review linked articles to ensure Linux parity and update main page to reference them equally.
GitHub Create Pull Request
Virtual Machines Create and upload an Ubuntu Linux VHD in Azure ...rticles/virtual-machines/linux/create-upload-ubuntu.md
Medium Priority View Details →
Scanned: 2026-02-23 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation, while focused on Ubuntu Linux, frequently references Windows-centric tools and workflows (notably Hyper-V and PowerShell's Convert-VHD) for creating and managing VHDs. Windows/Hyper-V instructions are given first and in detail, with no Linux-native alternatives for key steps such as VHD creation/conversion and VM management. This creates friction for Linux/macOS users who may not have access to Windows tools or environments.
Recommendations
  • Provide Linux-native instructions and examples for creating and converting VHDs (e.g., using qemu-img, VBoxManage, or other open-source tools).
  • Include guidance for managing and shutting down VMs using Linux-based virtualization platforms (such as KVM/QEMU, VirtualBox, or VMware Workstation).
  • Offer parity in example commands for extracting and preparing images, ensuring Linux/macOS users can follow all steps without relying on Windows/Hyper-V.
  • Clarify which steps are Windows-specific and provide equivalent Linux/macOS workflows where possible.
  • Move Linux-native instructions to the forefront, or at least present them alongside Windows instructions.
GitHub Create Pull Request
Virtual Machines Upload a VHD to Azure or copy a disk across regions - Azure CLI ...machines/linux/disks-upload-vhd-to-managed-disk-cli.md
Medium Priority View Details →
Scanned: 2026-02-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides a Windows-style AzCopy example (using 'AzCopy.exe' and Windows file paths) but does not show a Linux/macOS equivalent. The AzCopy upload command is only demonstrated with Windows syntax and paths, and there is no explicit Linux/macOS example or mention of how to run AzCopy on those platforms. The rest of the CLI commands are cross-platform, but the upload step is Windows-centric.
Recommendations
  • Add a Linux/macOS AzCopy example, e.g., 'azcopy copy /home/user/mydisk.vhd "sas-URI" --blob-type PageBlob'.
  • Clarify that AzCopy is available for Linux/macOS and provide download/install instructions for those platforms.
  • Mention that file paths and command syntax differ between Windows and Linux/macOS.
  • Consider showing both Windows and Linux/macOS examples side by side for critical steps.
GitHub Create Pull Request
Virtual Machines Verify encryption status for Linux - Azure Disk Encryption ...tual-machines/linux/how-to-verify-encryption-status.md
Medium Priority View Details →
Scanned: 2026-02-23 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for verifying disk encryption status on Linux VMs, but consistently presents PowerShell examples before CLI examples. The PowerShell section is notably more detailed, with more granular examples and explanations, while the CLI section, although comprehensive, appears after PowerShell. There are no missing Linux-specific examples, and OS-level Linux commands are included. However, the ordering and depth of PowerShell content may create friction for Linux users, as PowerShell is less commonly used on Linux than Azure CLI or Bash.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is the default and most common tool for Linux users.
  • Ensure parity in detail and explanation between PowerShell and Azure CLI sections.
  • Explicitly note that PowerShell is optional and that Azure CLI is recommended for Linux environments.
  • Consider grouping CLI and PowerShell examples together, or providing a clear navigation for Linux users to skip PowerShell sections.
  • Add a brief rationale for tool selection, highlighting CLI as the preferred cross-platform solution.
GitHub Create Pull Request
Virtual Machines Run scripts in a Linux VM in Azure using managed Run Commands ...articles/virtual-machines/linux/run-command-managed.md
Medium Priority View Details →
Scanned: 2026-02-23 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation is focused on Linux VMs, but exhibits several Windows biases: PowerShell examples and tooling are heavily featured, some command references and tooling (e.g., Get-AzVMRunCommandDocument, New-AzStorageBlobSASToken) are Windows-centric or PowerShell-only, and REST/ARM template examples use Windows-style scripts (e.g., Write-Host, .ps1 files) without Linux shell script equivalents. In several places, Windows terminology and patterns are mentioned before Linux, and Linux-specific examples (e.g., bash script, .sh files) are missing or less prominent.
Recommendations
  • Provide Linux shell (.sh) script examples alongside PowerShell (.ps1) examples in REST and ARM template sections.
  • Clarify which tools and commands are cross-platform, and offer Linux-native alternatives where possible (e.g., az CLI for listing command IDs, SAS token generation).
  • Ensure that Linux-specific usage patterns (environment variables, script arguments, file types) are explained and demonstrated equally to Windows patterns.
  • Reorder sections or examples to show Linux CLI usage first, or at least equally, especially in documentation for Linux VMs.
  • Add explicit notes when a command/tool is Windows-only or PowerShell-only, and provide Linux alternatives.
GitHub Create Pull Request
Virtual Machines Associate a virtual machine to a capacity reservation group .../virtual-machines/capacity-reservation-associate-vm.md
Medium Priority View Details →
Scanned: 2026-02-22 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation is intended for both Windows and Linux virtual machines, as stated at the top. Most command-line examples (Azure CLI, API, PowerShell) are generic and applicable to both OS types. However, the ARM template example is Windows-specific: it only provides parameters and configuration for Windows Server images, with no Linux image options or guidance. Additionally, the ARM template section presents Windows as the default, which may create friction for Linux users seeking parity.
Recommendations
  • Add ARM template examples or parameters for Linux VM images (e.g., Ubuntu, CentOS) alongside Windows examples.
  • Clarify in the ARM template section that Linux images are supported and provide guidance or links for Linux VM ARM template configuration.
  • Consider alternating the order of examples or explicitly stating that CLI and API methods are OS-agnostic.
  • If possible, provide PowerShell and CLI examples for both Windows and Linux VM creation (e.g., using --image Ubuntu2204 and Windows image).
GitHub Create Pull Request
Virtual Machines Deprovision or generalize a VM before creating an image ...docs/blob/main/articles/virtual-machines/generalize.md
Medium Priority View Details →
Scanned: 2026-02-22 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides clear, separate instructions for both Linux and Windows VMs. However, the Windows section includes more detailed prerequisites and uses PowerShell-specific commands (Set-AzVm) without mentioning Azure CLI equivalents. The Windows example for marking a VM as generalized uses PowerShell, while the Linux section uses Azure CLI. The Windows section also appears after the Linux section, but the PowerShell example is not accompanied by a CLI equivalent, which could create friction for users on Linux/macOS who manage Windows VMs.
Recommendations
  • Add Azure CLI equivalents for Windows VM steps, especially for marking a VM as generalized (e.g., 'az vm generalize').
  • Mention that Azure CLI can be used cross-platform for Windows VM management, not just PowerShell.
  • Consider providing both PowerShell and CLI examples side-by-side for Windows VM steps.
  • Ensure parity in detail between Linux and Windows sections, especially regarding prerequisites and commands.
GitHub Create Pull Request
Virtual Machines Run scripts in a Linux VM in Azure using managed Run Commands ...articles/virtual-machines/linux/run-command-managed.md
Medium Priority View Details →
Scanned: 2026-02-22 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
While the documentation is focused on Linux VMs, there is notable Windows bias in several areas: PowerShell examples and tooling are heavily featured alongside Azure CLI, with PowerShell-specific commands and SAS token generation instructions dominating. Windows tools (e.g., PowerShell, 'New-AzStorageBlobSASToken') are referenced without Linux equivalents or alternatives. In some sections, Windows patterns (such as script parameter passing) are explained first or exclusively. REST API and ARM template examples use Windows-style scripts (e.g., 'Write-Host', '.ps1' files), and there is a lack of explicit Linux/bash script examples in these areas.
Recommendations
  • Add Linux/bash script examples in REST API and ARM template sections (e.g., use 'echo Hello World!' or '.sh' files instead of 'Write-Host' and '.ps1').
  • Provide Linux-native alternatives for SAS token generation (e.g., Azure CLI commands instead of 'New-AzStorageBlobSASToken').
  • Clarify when PowerShell commands are Windows-specific and offer equivalent Azure CLI or bash commands for Linux users.
  • Ensure script parameter passing examples are shown for both Windows (.ps1) and Linux (.sh) scripts, with clear distinctions.
  • Review and update documentation to avoid referencing Windows tools or patterns before Linux equivalents, especially in Linux-focused content.
GitHub Create Pull Request
Virtual Machines Create and upload an Ubuntu Linux VHD in Azure ...rticles/virtual-machines/linux/create-upload-ubuntu.md
Medium Priority View Details →
Scanned: 2026-02-22 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation, while focused on Ubuntu Linux VHD creation, frequently references Windows-centric tools and workflows (Hyper-V, PowerShell's Convert-VHD) and presents Windows/Hyper-V steps before mentioning or omitting Linux-native alternatives. Linux users are left without clear guidance for VHD creation, conversion, or VM management, creating friction for non-Windows environments.
Recommendations
  • Add instructions for creating and converting VHDs using Linux-native tools (e.g., qemu-img, VBoxManage, KVM).
  • Provide examples for extracting and manipulating VHDs on Linux without referencing Hyper-V or Windows PowerShell.
  • Reorganize prerequisite and manual steps to prioritize Linux workflows, or at least present Linux and Windows options equally.
  • Clarify which steps are Windows-only and offer Linux alternatives wherever possible (e.g., disk conversion, VM management).
  • Link to Linux-specific guides for virtualization and VHD management.
GitHub Create Pull Request
Virtual Machines Upload a VHD to Azure or copy a disk across regions - Azure CLI ...machines/linux/disks-upload-vhd-to-managed-disk-cli.md
Medium Priority View Details →
Scanned: 2026-02-22 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides a Windows-centric example for uploading a VHD using AzCopy, specifically referencing 'AzCopy.exe' and a Windows file path ('c:\somewhere\mydisk.vhd'), without offering a Linux/macOS equivalent. The AzCopy command is shown only in Windows syntax, and there is no explicit example for Linux/macOS users, even though the page is intended for both Linux and Windows VMs. Additionally, the Windows example appears before any mention of Linux usage patterns.
Recommendations
  • Add a Linux/macOS AzCopy example, e.g., 'azcopy copy /home/user/mydisk.vhd "sas-URI" --blob-type PageBlob'.
  • Clarify that AzCopy is cross-platform and provide download/install instructions for Linux/macOS.
  • Use generic file paths or show both Windows and Linux/macOS paths in examples.
  • Ensure that CLI examples and scripts are platform-neutral or provide variants for each OS.
GitHub Create Pull Request
Virtual Machines Create an Azure Image Builder Bicep file or ARM template JSON template .../articles/virtual-machines/linux/image-builder-json.md
Medium Priority View Details →
Scanned: 2026-02-22 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation covers both Linux and Windows VM image creation with Azure Image Builder, but there is a notable Windows bias in several areas. PowerShell examples and references are frequently given, sometimes before or instead of Linux equivalents. Windows-specific tools (e.g., Get-FileHash, Sysprep) are mentioned with detailed instructions, while Linux tools (e.g., sha256sum, waagent) are referenced but less emphasized. Some customizers (WindowsRestart, WindowsUpdate, PowerShell) are Windows-only, and this is clearly documented. However, in sections like checksum generation, Windows/PowerShell instructions are often more prominent or detailed than Linux equivalents.
Recommendations
  • Ensure Linux (bash/terminal) examples are provided alongside PowerShell examples, especially for checksum generation and image build operations.
  • Present Linux and Windows examples in parallel or alternate order, rather than defaulting to Windows/PowerShell first.
  • Expand Linux tool instructions (e.g., explain how to use sha256sum, wget, curl) with the same detail as Windows tools.
  • Where possible, clarify when a feature or customizer is Windows-only, and offer Linux alternatives or workarounds if available.
  • Add explicit bash/terminal commands for common operations (e.g., starting/cancelling builds, querying resources) alongside Azure CLI/PowerShell.
  • Review the order and prominence of Windows vs. Linux content to ensure parity.
GitHub Create Pull Request
Virtual Machines Associate a virtual machine to a capacity reservation group .../virtual-machines/capacity-reservation-associate-vm.md
Medium Priority View Details →
Scanned: 2026-02-21 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation covers both Windows and Linux VMs, and provides parity in API, Portal, CLI, and PowerShell instructions. However, the ARM template example is Windows-centric: it only shows Windows image SKUs and parameters, with no Linux image option or example. Additionally, the ARM template section does not mention how to deploy a Linux VM, and the PowerShell examples (which are inherently Windows-focused) are presented alongside CLI examples, but CLI examples do include Linux (Ubuntu) images. The ordering of examples is generally neutral, but the ARM template bias is notable.
Recommendations
  • Add a Linux VM ARM template example, or at least show how to modify the template to deploy a Linux VM (e.g., using Ubuntu or other popular Linux distributions).
  • In the ARM template parameters, include both Windows and Linux image options, or provide guidance for Linux users.
  • Clarify in the ARM template section that the example is for Windows, and provide a link or snippet for Linux VM ARM templates.
  • Ensure that all examples (especially templates) are inclusive of both Windows and Linux scenarios, as the feature applies to both.
GitHub Create Pull Request
← Previous Page 7 of 33 Next →