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 176-200 of 815 flagged pages
Virtual Machines
Create and upload an Ubuntu Linux VHD in Azure
...rticles/virtual-machines/linux/create-upload-ubuntu.md
Medium Priority
View Details →
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 tools (Hyper-V, PowerShell's Convert-VHD), presents Windows/Hyper-V steps first or exclusively, and lacks equivalent Linux-native tooling guidance for critical steps such as VHD creation and conversion. Linux users may struggle to follow the process without additional research or tooling.
Recommendations
- Provide Linux-native instructions for creating and converting VHDs (e.g., using qemu-img, VBoxManage, or other open-source tools).
- Add examples for extracting and manipulating VHDs on Linux/macOS, not just referencing Windows/WSL.
- Mention Linux virtualization solutions (KVM, VirtualBox, QEMU) alongside Hyper-V, and link to relevant guides.
- Ensure PowerShell/Convert-VHD steps are accompanied by Linux alternatives.
- Clarify which steps are OS-agnostic and which are Windows-specific, and offer parity where possible.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page provides both Azure CLI and PowerShell links for configuring the NetworkAccessPolicy, but references to PowerShell and Windows-centric tools appear first and more prominently. The custom RBAC role section links only to a PowerShell-based guide, omitting CLI or ARM template alternatives. There are no explicit Linux/macOS examples or parity in the RBAC section, and PowerShell is mentioned before CLI in the network access policy section.
Recommendations
- Add links and examples for creating custom RBAC roles using Azure CLI and/or ARM templates, not just PowerShell.
- Ensure CLI and PowerShell examples are presented together, or alternate which comes first.
- Explicitly mention that all steps can be performed on Linux/macOS using Azure CLI, and provide sample commands.
- Review all sections for Windows-first language and ensure Linux/macOS parity.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides both Linux and Windows context and includes bash scripting for disk copy operations. However, the AzCopy example for uploading a VHD is shown only with a Windows-style path and AzCopy.exe invocation, with no explicit Linux/macOS equivalent. The AzCopy command is not shown with a Linux path or executable name, and there is no mention of how to run AzCopy on Linux/macOS. Additionally, the first and only explicit upload example uses Windows conventions, which may create friction for Linux/macOS users.
Recommendations
- Add explicit AzCopy upload examples for Linux/macOS, using a Linux path (e.g., '/home/user/mydisk.vhd') and the appropriate executable name (e.g., './azcopy' or 'azcopy').
- Clarify that AzCopy is cross-platform and provide download/run instructions for Linux/macOS.
- Where file paths are referenced, show both Windows and Linux/macOS path formats.
- Consider mentioning any Linux-specific considerations for preparing VHDs, if applicable.
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 →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
Although the page is focused on Linux VMs, there is notable Windows bias in several areas: PowerShell examples and tools (e.g., Set-AzVMRunCommand, New-AzStorageBlobSASToken) are heavily featured, often before or instead of Azure CLI equivalents. REST API and ARM template examples use Windows-centric script syntax (e.g., Write-Host, .ps1 files) without Linux/bash alternatives. Some explanations reference Windows-specific behaviors (e.g., 'Secondary Logon' service) and do not clarify Linux distinctions. Several advanced scenarios (streaming output to blobs, parameter passing) are only shown in PowerShell, with no CLI or Linux-native scripting examples.
Recommendations
- Add Azure CLI examples for all advanced scenarios currently only shown in PowerShell (e.g., streaming output/error to blobs, parameter passing, running as a different user).
- In REST API and ARM template sections, provide Linux/bash script examples alongside Windows/PowerShell (.ps1) examples.
- Clarify when instructions or notes are Windows-specific, and provide Linux alternatives or explanations.
- Ensure Linux/bash syntax is used in examples where the context is Linux VMs (e.g., use echo, bash scripts, .sh files instead of Write-Host, .ps1).
- Reorder sections so Azure CLI (Linux-friendly) examples appear before PowerShell, or at least equally.
- Where PowerShell tools are mentioned (e.g., New-AzStorageBlobSASToken), provide CLI alternatives or links.
Virtual Machines
Associate a virtual machine to a capacity reservation group
.../virtual-machines/capacity-reservation-associate-vm.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Arm Template Example
Summary
The documentation covers both Windows and Linux virtual machines, and provides parity across API, Portal, CLI, and PowerShell examples. However, the ARM template section only demonstrates Windows VM creation, omitting an explicit Linux VM example. Additionally, the ARM template parameters and image references are Windows-centric, and Windows images are listed first. CLI examples do use Ubuntu images, but the ARM template is Windows-only.
Recommendations
- Add an ARM template example for associating a Linux VM (e.g., Ubuntu) to a capacity reservation group, or extend the existing template to show both Windows and Linux image options.
- In the ARM template section, clarify that the template can be adapted for Linux VMs and provide guidance or links for doing so.
- Consider listing both Windows and Linux image options in the ARM template parameters, or provide a note about how to change the image for Linux VMs.
- When listing image references or parameters, alternate or balance Windows and Linux examples to avoid 'windows_first' bias.
Virtual Machines
Restrict managed disks from being imported or exported
...tual-machines/disks-restrict-import-export-overview.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation references both Azure CLI and Azure PowerShell for configuring the NetworkAccessPolicy, but the custom RBAC role creation link points only to a PowerShell-based guide, and PowerShell is mentioned before CLI in the NetworkAccessPolicy section. There is no explicit Linux example for custom role creation, and PowerShell is a Windows-centric tool, creating friction for Linux/macOS users.
Recommendations
- Add links or instructions for creating custom RBAC roles using Azure CLI or Azure Portal, not just PowerShell.
- Present Azure CLI and PowerShell examples side-by-side, or mention CLI first to improve parity.
- Clarify that Azure CLI is cross-platform and provide explicit Linux/macOS guidance where relevant.
Virtual Machines
Azure VM Extensions and Features for Linux
...articles/virtual-machines/extensions/features-linux.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples throughout, but PowerShell is featured equally or slightly more prominently than Azure CLI. In several sections, PowerShell examples are given immediately after CLI, and the PowerShell commands are Windows-centric (even though PowerShell Core is cross-platform, most Linux administrators use Bash/CLI). The documentation does not provide Bash-only or Linux-native command examples (other than waagent version check), and references to Azure PowerShell are frequent. While the page is focused on Linux VM extensions, the use of PowerShell and Windows-oriented tooling is notable.
Recommendations
- Prioritize Azure CLI examples and Bash scripts for Linux-focused documentation, as CLI is the primary tool for Linux users.
- Consider providing Bash-native examples for common operations (e.g., using curl/wget for script download, jq for JSON parsing).
- Move PowerShell examples to a secondary position or into expandable sections, making CLI the default.
- Clarify that Azure PowerShell can be used cross-platform, but highlight CLI as the recommended method for Linux users.
- Add troubleshooting and operational examples using Linux-native tools (e.g., systemctl, journalctl, grep) where relevant.
Virtual Machines
Create and upload an Ubuntu Linux VHD in Azure
...rticles/virtual-machines/linux/create-upload-ubuntu.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation, while focused on Ubuntu Linux VHD creation for Azure, frequently references Windows tools (Hyper-V, PowerShell Convert-VHD) as primary methods for VHD creation and conversion. Windows/Hyper-V steps are described first and in detail, with no equivalent Linux-native tooling or workflow provided for critical steps like VHD creation/conversion. Linux users are left to infer or seek external guidance for these tasks, creating friction and potential confusion.
Recommendations
- Add explicit instructions and examples for creating and converting VHDs on Linux (e.g., using qemu-img, VBoxManage, or other Linux-native tools).
- Mention Linux-native virtualization solutions (such as KVM, VirtualBox, or QEMU) alongside Hyper-V, and provide links to relevant guides.
- Provide PowerShell Convert-VHD alternatives for Linux (e.g., qemu-img convert) and clarify disk alignment requirements in Linux context.
- Ensure that critical steps (such as disk conversion and VM shutdown) are described for both Windows and Linux environments.
- Reorganize sections so that Linux-native approaches are presented first or equally with Windows methods.
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 →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
Although the documentation is focused on Linux VMs, there are several signs of Windows bias. PowerShell examples and references to Windows tools (e.g., PowerShell cmdlets, Windows-specific notes) are prominent and often precede or outnumber Linux/CLI examples. REST and ARM template examples use Windows-centric scripts (e.g., Write-Host, .ps1 files) without Linux shell script equivalents. Some explanations and notes reference Windows behaviors or tools before Linux, and some features (like SAS token generation) are described only with PowerShell commands. There are missing Linux shell script examples in several sections, especially in REST and ARM template usage.
Recommendations
- Provide Linux shell script examples alongside PowerShell/.ps1 examples in REST and ARM template sections.
- Ensure CLI and bash examples are given equal prominence and are not secondary to PowerShell.
- Clarify when a feature or example is Windows-only, and provide Linux alternatives where possible.
- Add instructions for generating SAS tokens and managing blobs using Azure CLI or bash, not just PowerShell.
- Review notes and explanations to ensure Linux behaviors are described first or equally.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides a Windows-style AzCopy example ('AzCopy.exe copy "c:\somewhere\mydisk.vhd" "sas-URI" --blob-type PageBlob') but does not show a Linux/macOS equivalent. The AzCopy command is presented in Windows syntax and path format, and the explicit example uses a Windows path. There is no Linux/macOS AzCopy example (e.g., using './azcopy' or '/home/user/mydisk.vhd'). The rest of the CLI commands are cross-platform, but the AzCopy section is notably Windows-centric.
Recommendations
- Add a Linux/macOS AzCopy example (e.g., './azcopy copy "/home/user/mydisk.vhd" "sas-URI" --blob-type PageBlob') alongside the Windows example.
- Clarify that AzCopy is cross-platform and provide download/install instructions for Linux/macOS.
- 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 AzCopy usage.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Windows and Linux coverage for Azure Image Builder, but there are several areas where Windows tools and examples are presented first or more prominently. PowerShell is frequently used for checksum generation and resource management, sometimes before Linux equivalents are mentioned. Windows-specific customizers (PowerShell, WindowsRestart, WindowsUpdate) are described in detail, while Linux equivalents are less emphasized or explicitly noted as unavailable. Some example commands and troubleshooting steps use PowerShell as the primary tool, with Linux alternatives provided but not always equally detailed.
Recommendations
- Ensure Linux/macOS commands (e.g., sha256sum, Azure CLI) are presented alongside or before Windows/PowerShell equivalents, especially in sections about checksum generation and resource management.
- Where PowerShell is used for examples (e.g., resource actions, validation), provide equivalent Bash/Azure CLI examples for Linux/macOS users.
- Expand explanations and examples for Linux-specific customizers and validators, matching the detail given to Windows customizers.
- Avoid language such as 'there is no Linux restart customizer' without offering Linux workarounds (e.g., using Shell customizer to run 'sudo reboot').
- In troubleshooting and operational sections, ensure Linux/macOS commands are as prominent as Windows commands.
- Consider alternating the order of Windows and Linux examples, or grouping them by OS for clarity.
Virtual Machines
Associate a virtual machine to a capacity reservation group
.../virtual-machines/capacity-reservation-associate-vm.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Arm Template Windows Only
Summary
The documentation covers both Windows and Linux VMs, and provides cross-platform guidance via Azure CLI, API, Portal, and PowerShell. However, there are signs of Windows bias: PowerShell examples and references are prominent, and ARM template examples are Windows-only (no Linux image or parameter options). Windows-specific parameters (e.g., OSVersion) are shown first and exclusively in ARM templates. The CLI examples do use Ubuntu images, but the ARM template and PowerShell sections focus on Windows. The ordering of examples sometimes puts Windows tools (PowerShell) before Linux-friendly ones (CLI).
Recommendations
- Add ARM template examples for Linux VMs, including parameters for Linux images and admin SSH keys.
- In ARM template sections, clarify how to adapt the template for Linux VMs (e.g., show both Windows and Linux imageReference blocks).
- Balance PowerShell and CLI coverage: ensure CLI examples are as detailed as PowerShell, and consider showing CLI before PowerShell.
- When referencing admin credentials, provide guidance for both password (Windows) and SSH key (Linux).
- Review ordering of examples to avoid always showing Windows tools first.
- Explicitly state that all steps apply to both Windows and Linux VMs, and highlight any differences.
Virtual Machines
Create and upload an Ubuntu Linux VHD in Azure
...rticles/virtual-machines/linux/create-upload-ubuntu.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation, while focused on Ubuntu Linux VHDs, repeatedly references Windows-centric tools (Hyper-V, Convert-VHD PowerShell cmdlet) and provides Windows-first guidance for creating and converting VHDs. Linux-native alternatives (such as qemu-img, KVM, VirtualBox, or Linux CLI conversion tools) are not mentioned, leaving Linux/macOS users without clear instructions for critical steps like VHD creation and conversion.
Recommendations
- Add instructions and examples for creating and converting VHDs using Linux-native tools (e.g., qemu-img, VirtualBox, KVM).
- Mention Linux/macOS alternatives alongside Windows tools, not after or instead of them.
- Provide links to Linux-specific guides for disk conversion and virtualization.
- Clarify that Hyper-V and Convert-VHD are Windows-only and offer parity for Linux/macOS users.
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 →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
Although the documentation is focused on Linux VMs, there is notable Windows bias in several areas. PowerShell examples and tools (e.g., Set-AzVMRunCommand, Get-AzVMRunCommand) are heavily featured alongside Azure CLI, and in some cases, Windows-specific instructions or terminology (such as PowerShell script references, Windows VM notes, and SAS token generation with PowerShell) are presented without equivalent Linux-native alternatives. REST and ARM template examples also use Windows-centric script samples (e.g., Write-Host, .ps1 files) instead of Linux shell scripts. The PowerShell section is much more extensive than the Azure CLI section, with more advanced scenarios only covered in PowerShell. Some notes and explanations reference Windows behaviors before Linux, and there are missing Linux-native examples for tasks like SAS token generation and blob management.
Recommendations
- Expand Azure CLI examples to cover all advanced scenarios currently only shown in PowerShell (e.g., streaming output to blob, running as a different user, passing parameters).
- Replace or supplement REST and ARM template script samples with Linux shell script examples (e.g., use 'echo Hello World!' or bash scripts instead of 'Write-Host' and .ps1 files).
- Provide Linux-native instructions for generating SAS tokens and managing blobs (e.g., using Azure CLI or azcopy), not just PowerShell.
- Ensure notes and explanations reference Linux behaviors first or equally, especially when describing parameter passing or script execution.
- Clarify when PowerShell commands are cross-platform (e.g., PowerShell Core on Linux) or provide explicit bash/CLI alternatives.
Virtual Machines
Associate a virtual machine to a capacity reservation group
.../virtual-machines/capacity-reservation-associate-vm.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation provides both CLI and PowerShell examples for associating a VM to a capacity reservation group. However, there is a notable Windows bias: PowerShell (a Windows-centric tool) is always presented as a primary automation option, and ARM template and API examples use Windows Server images by default. There are no explicit Linux-specific examples in ARM templates, and PowerShell is featured equally alongside the cross-platform Azure CLI, despite CLI being more common on Linux/macOS. The ARM template only shows Windows image SKUs, and the 'OSVersion' parameter is Windows-only, with no mention of Linux images or parameters.
Recommendations
- Add Linux image options and parameters to ARM template examples (e.g., include Ubuntu or other Linux distributions in 'imageReference' and 'OSVersion').
- Provide a Linux-focused ARM template example or at least a note on how to adapt the template for Linux VMs.
- Consider presenting Azure CLI examples before PowerShell, as CLI is cross-platform and more familiar to Linux/macOS users.
- Explicitly mention that PowerShell examples are for users who have PowerShell available, and that Azure CLI is recommended for Linux/macOS.
- Where possible, clarify that the steps apply to both Windows and Linux VMs, and highlight any OS-specific differences.
Virtual Machines
Create and upload an Ubuntu Linux VHD in Azure
...rticles/virtual-machines/linux/create-upload-ubuntu.md
Medium Priority
View Details →
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), and provides Windows/Hyper-V steps before mentioning or omitting Linux-native alternatives. Linux users are left without clear guidance for VHD creation and conversion, and the use of Windows tools is presented as the default or only option.
Recommendations
- Add instructions for creating and converting VHDs using Linux-native tools (e.g., qemu-img, VBoxManage, dd).
- Provide Linux-specific examples for extracting and manipulating VHDs, not just referencing Windows/WSL.
- Mention KVM, VirtualBox, or other Linux virtualization solutions alongside Hyper-V.
- Clarify which steps are Windows-specific and provide equivalent Linux/macOS workflows.
- Move Linux-native instructions and tools to the forefront, or at least present them equally with Windows options.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
Although the documentation is focused on Linux VMs, there are several signs of Windows bias: PowerShell examples are provided extensively and often before or alongside Azure CLI examples, even though PowerShell is not the default scripting environment for most Linux users. Windows-specific tools and terminology (e.g., 'ipconfig', 'Write-Host', '.ps1' scripts, 'New-AzStorageBlobSASToken') are referenced without clear Linux alternatives or context. REST and ARM template examples use Windows-style scripts (PowerShell), and some explanations default to Windows patterns. There are missing Linux-specific examples for certain advanced scenarios (e.g., parameter passing, blob SAS token generation, script URI usage).
Recommendations
- Provide Bash shell script examples in REST and ARM template sections instead of PowerShell (.ps1) scripts.
- Clarify when a command or tool is Windows-specific and offer Linux equivalents (e.g., use 'ifconfig' or 'ip a' instead of 'ipconfig').
- Add Linux-native instructions for generating SAS tokens (e.g., using Azure CLI or azcopy) instead of only referencing PowerShell tools.
- Ensure parameter passing examples show both Windows (argument style) and Linux (environment variable style) clearly.
- Where PowerShell is used, explain its applicability to Linux (e.g., PowerShell Core) and provide Bash alternatives.
- Review all sample scripts and outputs to ensure they use Linux conventions (e.g., .sh scripts, echo, id, etc.) and avoid Windows-centric language.
Virtual Machines
Create and upload an Ubuntu Linux VHD in Azure
...rticles/virtual-machines/linux/create-upload-ubuntu.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page, while focused on Ubuntu Linux VHD creation for Azure, exhibits notable Windows bias. Hyper-V (a Windows-only virtualization tool) is referenced as the primary example for creating VHDs, with links to Windows documentation. Steps involving VM management and VHD conversion are described using Hyper-V Manager and the Convert-VHD PowerShell cmdlet, with no Linux-native alternatives (such as qemu-img or KVM) provided. Windows tools and patterns are mentioned first and exclusively in several critical steps, creating friction for Linux/macOS users.
Recommendations
- Add Linux-native instructions for creating and managing VHDs (e.g., using qemu-img, KVM, or VirtualBox).
- Provide Linux/macOS alternatives for VHD conversion (e.g., qemu-img convert).
- Include steps for shutting down or managing VMs using Linux tools (e.g., virsh, virt-manager).
- Reorder examples so Linux-native tools are presented first or alongside Windows tools.
- Clarify that Hyper-V and Convert-VHD are Windows-specific, and link to Linux/macOS equivalents.
Virtual Machines
Create and upload a Red Hat Enterprise Linux VHD for use in Azure
...les/virtual-machines/linux/redhat-create-upload-vhd.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation provides comprehensive instructions for creating and uploading a Red Hat Enterprise Linux VHD for Azure, covering multiple hypervisors (Hyper-V, KVM, VMware, Kickstart). However, there is a notable Windows bias: Hyper-V (a Windows-only tool) is presented first in nearly every major section and is referenced as the primary example for VM creation and disk conversion. Windows tools and terminology (e.g., Hyper-V Manager, PowerShell cmdlets like 'convert-vhd') are mentioned before their Linux equivalents. Linux/KVM/VMware instructions are present and detailed, but the ordering and framing prioritize Windows/Hyper-V scenarios.
Recommendations
- Reorder sections so that Linux-native hypervisors (KVM, VMware, Kickstart) are presented before or alongside Hyper-V, especially since the audience is preparing Linux VMs.
- Where disk conversion is discussed, mention Linux tools (e.g., qemu-img) before or alongside Windows tools (e.g., Hyper-V Manager, convert-vhd).
- Clarify that Hyper-V steps are only required if using Windows, and highlight Linux-native workflows for users on Linux/macOS.
- Consider a summary table at the top showing all supported hypervisors and their OS requirements, helping users quickly find relevant instructions.
- Ensure that Linux/KVM/VMware instructions are equally prominent and not referenced as secondary or 'see also' content.
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 →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides both Linux and Windows coverage for Azure Image Builder, including examples for shell and PowerShell customizers, and validation steps. However, there is a notable Windows bias in several areas: PowerShell and Windows-specific tools (e.g., Get-FileHash, Invoke-WebRequest, Sysprep) are referenced more frequently and often before Linux equivalents; PowerShell commands for checksum generation and image operations are shown alongside Azure CLI, but Windows tools are sometimes mentioned first. Some customizers (WindowsRestart, WindowsUpdate) are Windows-only, but this is appropriate given their OS specificity. Linux examples are present but occasionally less detailed or appear after Windows examples.
Recommendations
- Ensure Linux tools and commands (e.g., sha256sum, wget/curl) are mentioned equally and before or alongside Windows tools in relevant sections.
- Where PowerShell is referenced for checksum generation, provide Linux/Mac equivalents (sha256sum) with equal prominence.
- For image build/cancel operations, show Azure CLI examples first or highlight their cross-platform nature.
- In sections where Windows-specific customizers are described, clarify that Linux alternatives (e.g., Shell customizer for reboots) are not available and suggest workarounds if possible.
- Expand Linux example coverage where possible, ensuring parity in detail and visibility.
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 →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
While the page is intended for Linux VMs, there is notable Windows bias in the documentation. PowerShell (Set-AzVMRunCommand, etc.) is heavily featured alongside Azure CLI, and many examples and notes reference Windows-specific tools, parameters, and patterns. Some examples use Windows-centric terminology (e.g., 'ipconfig' as a commandId, PowerShell script references in REST/ARM templates), and PowerShell is presented as a primary management method, even though Linux users are more likely to use Azure CLI or native Linux tools. There are also sections where Windows behaviors are described before Linux equivalents, and some REST/ARM examples use PowerShell scripts instead of shell scripts.
Recommendations
- Prioritize Azure CLI and Bash examples for Linux-focused documentation, and move PowerShell examples to a secondary position or a dedicated section.
- Ensure all REST/ARM template examples use shell scripts (e.g., 'echo Hello World!' or bash scripts) rather than PowerShell scripts.
- When referencing commandIds, use Linux-relevant commands (e.g., 'ifconfig') rather than Windows ones like 'ipconfig'.
- Clarify in notes and parameter explanations when a behavior is Windows-only, and provide Linux-specific guidance first.
- Where PowerShell is shown, explicitly note that it is cross-platform (if so), or provide Bash/CLI equivalents.
- Review all examples and ensure that Linux users can follow them without needing to interpret or translate Windows/PowerShell-specific instructions.
Virtual Machines
Share VM images in a compute gallery
...in/articles/virtual-machines/shared-image-galleries.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation covers both Windows and Linux VM images, but there are several signs of Windows bias. PowerShell examples and references are prominent and often appear before or alongside CLI examples, with some features and links (e.g., finding Marketplace images, uploading VHDs, creating specialized images) referencing Windows-specific pages first or exclusively. In some cases, Linux equivalents are mentioned but not always with equal detail or visibility. The FAQ and example sections tend to show Windows/PowerShell usage before Linux/CLI, and some links default to Windows guides.
Recommendations
- Ensure that Linux/CLI examples are provided wherever PowerShell/Windows examples are shown, and present them with equal prominence.
- When referencing guides or tutorials (e.g., uploading VHDs, creating specialized images), link to both Windows and Linux versions side-by-side, or use a neutral landing page.
- In tables and lists, alternate the order of Windows and Linux examples or group them together to avoid implicit prioritization.
- Expand Linux-specific troubleshooting, examples, and links to match the depth of Windows coverage.
- Review FAQ answers and ensure Linux scenarios are addressed with equal clarity and detail.
Virtual Machines
Associate a virtual machine to a capacity reservation group
.../virtual-machines/capacity-reservation-associate-vm.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation provides examples for both Windows and Linux VMs, but there are several areas of Windows bias. PowerShell examples are given equal prominence to Azure CLI, but PowerShell is a Windows-centric tool. The ARM template example is exclusively for Windows Server images, with no Linux image option shown. The portal instructions reference password complexity requirements typical for Windows, and the ARM template parameters and allowed values are all Windows versions. Linux-specific examples (e.g., ARM template for Ubuntu or Red Hat) are missing, and Windows terminology/tools (PowerShell, Windows images) are mentioned before or instead of Linux equivalents.
Recommendations
- Add ARM template examples for Linux VM images (e.g., Ubuntu, CentOS, Red Hat) alongside the Windows template.
- In portal instructions, clarify password requirements for Linux VMs (e.g., SSH key option, username restrictions).
- Ensure CLI and PowerShell examples show both Windows and Linux image creation, or clarify that the example is for a Linux VM when using Ubuntu.
- In ARM template parameters, include allowed values for popular Linux distributions.
- Where PowerShell is used, note that it is primarily for Windows users, and suggest Bash/CLI for Linux/macOS users.
Virtual Machines
Create and upload an Ubuntu Linux VHD in Azure
...rticles/virtual-machines/linux/create-upload-ubuntu.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation, while focused on Ubuntu Linux VHDs, repeatedly references Windows tools (Hyper-V, PowerShell Convert-VHD), presents Windows/Hyper-V steps first, and lacks parity for Linux-native workflows (e.g., creating/converting VHDs on Linux). Linux users are left without clear guidance for key steps such as VHD creation/conversion, making the process notably Windows-centric.
Recommendations
- Add instructions for creating and converting VHDs using Linux-native tools (e.g., qemu-img, VBoxManage, dd).
- Provide Linux-specific examples for extracting and preparing VHDs, not just referencing Windows/WSL.
- Mention and link to Linux virtualization solutions (e.g., KVM, VirtualBox) alongside Hyper-V.
- Reorganize sections so Linux-native workflows are presented before or alongside Windows/Hyper-V options.
- Clarify which steps are platform-agnostic and which are Windows-specific, and provide alternatives where possible.