Virtual Machines
1073
Total Pages
1027
Linux-Friendly Pages
46
Pages with Bias
4.3%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
284 issues found
Showing 1-25 of 284 flagged pages
Virtual Machines
Automatic Guest Patching for Azure Virtual Machines and Scale Sets
...ticles/virtual-machines/automatic-vm-guest-patching.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits several signs of Windows bias. Windows-specific information, examples, and tooling (PowerShell, registry keys, Windows Update service) are presented more frequently and in greater detail than Linux equivalents. Windows patch orchestration modes are described first and in more depth, with Linux modes covered later and more briefly. PowerShell and CLI examples for Windows VMs are more numerous and detailed, while Linux examples are limited or missing in some sections (e.g., PowerShell usage for Linux VMs). Windows tools and concepts (registry keys, WSUS, KB IDs) are referenced without Linux analogs. The 'Next steps' section links only to Windows VM management, omitting Linux VM guidance.
Recommendations
- Ensure Linux examples are provided for every API, CLI, and PowerShell scenario, including VM creation, update, patch assessment, and patch installation.
- Present Linux and Windows instructions in parallel, or alternate their order to avoid Windows-first presentation.
- Include Linux-specific tooling and concepts (e.g., package managers, configuration files) where Windows-specific tools (registry, WSUS, KB IDs) are mentioned.
- Expand explanations of Linux patch orchestration modes to match the detail given for Windows.
- Add 'Next steps' links for Linux VM management alongside Windows VM links.
- Where PowerShell is used for Windows, clarify if and how PowerShell or other automation tools can be used for Linux VMs, or provide equivalent Bash/Ansible examples.
Create Pull Request
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. Windows-specific tools and patterns are referenced before or exclusively (e.g., nested virtualization links to Hyper-V on Windows), and bandwidth testing references NTTTCP, a Windows-centric tool, without mentioning Linux equivalents. There are no command-line examples, but where platform-specific features are discussed, Windows is mentioned first or exclusively. Linux parity is not fully addressed in feature support or tooling guidance.
Recommendations
- When referencing nested virtualization, include links to Linux/KVM documentation or clarify Linux support status.
- For bandwidth/throughput testing, mention Linux tools such as iperf or provide guidance for both Windows and Linux users.
- Where features are not supported for either platform (e.g., disk encryption), clarify the parity and provide links to both Windows and Linux documentation.
- Review all external links and ensure Linux equivalents are present and referenced with equal prominence.
- Consider adding example usage or optimization guidance for both Windows and Linux where relevant.
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page shows mild Windows bias. It references Windows-specific technologies (e.g., Hyper-V nested virtualization, NTTTCP for bandwidth testing) and links to Windows documentation before or instead of Linux equivalents. There are no explicit Linux command-line examples, and some features/tools are described only in a Windows context. Linux support is mentioned for disk encryption, but only to note that it is not supported.
Recommendations
- Provide Linux-specific examples and links alongside Windows ones, such as Linux nested virtualization guides and Linux bandwidth testing tools (e.g., iperf).
- Mention Linux tools and patterns (e.g., KVM, QEMU, Linux disk/network utilities) when describing features or performance testing.
- Ensure parity in documentation by including both Linux and Windows instructions for common VM management tasks.
- Where features are unsupported for Linux, provide context or alternatives for Linux users.
- Review and update resource links to include Linux documentation where available, not just Windows-centric guides.
Virtual Machines
Automatic Guest Patching for Azure Virtual Machines and Scale Sets
...ticles/virtual-machines/automatic-vm-guest-patching.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits several signs of Windows bias. Windows-specific examples (PowerShell, CLI) are provided before or in greater detail than Linux equivalents, especially in sections on patch orchestration modes and enablement. PowerShell commands are only given for Windows VMs, with no Linux PowerShell examples. Windows registry keys and tools (e.g., WSUS, Windows Update service) are discussed in detail, while Linux equivalents (e.g., yum, apt, packagekit) are mentioned briefly or not at all. Some sections, such as patch orchestration modes, provide more options and explanation for Windows than Linux, and the 'Next steps' link is Windows-focused.
Recommendations
- Provide Linux-specific PowerShell and CLI examples wherever Windows examples are given, including for enablement, assessment, and patch installation.
- Discuss Linux patching tools and mechanisms (e.g., apt, yum, zypper, packagekit) with parity to Windows Update/WSUS, including how automatic updates are managed and disabled.
- Ensure patch orchestration modes are explained with equal detail for Linux, including any limitations or differences.
- Add 'Next steps' links for Linux VM management, not just Windows.
- When listing supported images, present Linux and Windows lists with equal prominence and detail.
- Avoid referencing Windows registry keys or tools without providing Linux configuration file or service equivalents.
- Where possible, present examples for both OS types side-by-side, or alternate which OS is presented first.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/automatic-vm-guest-patching.md
...ticles/virtual-machines/automatic-vm-guest-patching.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits several signs of Windows bias. Windows-specific examples (PowerShell, CLI) are provided before or in greater detail than Linux equivalents. PowerShell commands are given for Windows VMs but not for Linux VMs in some sections. Windows registry keys and Windows Update service are discussed in detail, while Linux-specific configuration and troubleshooting are less emphasized. The 'Next steps' section links only to Windows VM management, omitting Linux. Some CLI and PowerShell examples for Linux are missing or less detailed.
Recommendations
- Provide PowerShell and CLI examples for Linux VMs wherever Windows examples are given.
- Ensure Linux-specific configuration and troubleshooting steps are as detailed as Windows (e.g., agent requirements, disabling automatic updates).
- Add a 'Next steps' link for Linux VM management alongside the Windows link.
- Present Windows and Linux instructions in parallel, rather than Windows-first ordering.
- Include Linux-specific tools and patterns (such as package managers, systemd, etc.) where relevant.
- Review all sections for parity in depth and clarity between Windows and Linux content.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/sizes/general-purpose/ddsv6-series.md
...virtual-machines/sizes/general-purpose/ddsv6-series.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page shows mild Windows bias. It references Windows-specific technologies (such as Hyper-V nested virtualization) and tools (NTTTCP for bandwidth testing) without mentioning Linux equivalents or alternatives. In the networking section, Windows is mentioned before Linux when discussing optimization, and only a Windows-centric tool (NTTTCP) is linked for bandwidth testing. There are no examples or instructions for either platform, but where platform-specific advice is given, Windows is prioritized or Linux is only mentioned secondarily.
Recommendations
- When referencing bandwidth/throughput testing, include Linux-native tools (e.g., iperf, netperf) alongside NTTTCP, and provide links to their usage in Azure.
- For nested virtualization, link to documentation for both Windows (Hyper-V) and Linux (KVM) nested virtualization, or clarify platform support.
- When discussing optimization or performance tuning, provide parity in guidance for both Windows and Linux, and avoid listing Windows first unless there is a technical reason.
- Where platform-specific features or restrictions are listed (e.g., disk encryption), ensure both Windows and Linux are equally described, and provide links to both sets of documentation.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/sizes/general-purpose/ddsv6-series.md
...virtual-machines/sizes/general-purpose/ddsv6-series.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page shows mild Windows bias. It references Windows-specific technologies (such as Hyper-V for nested virtualization) and Windows tools (NTTTCP for network testing) without mentioning Linux equivalents or alternatives. In several places, Windows features are listed before Linux ones, and some links point to Windows documentation first. There are no Linux-specific command-line examples, tools, or optimization guidance, and Linux parity is not explicitly addressed.
Recommendations
- Include Linux equivalents for referenced Windows tools (e.g., mention 'iperf' or 'nuttcp' for network testing alongside NTTTCP).
- Provide links to Linux-specific documentation where Windows documentation is referenced (e.g., nested virtualization on KVM/QEMU).
- Ensure Linux features and restrictions are listed before or alongside Windows ones, not after.
- Add Linux command-line examples or optimization tips where relevant (e.g., disk performance tuning, network throughput testing).
- Explicitly state Linux support and limitations in feature tables, not just in footnotes or restrictions.
- Review all external links to ensure Linux documentation is equally discoverable.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/automatic-vm-guest-patching.md
...ticles/virtual-machines/automatic-vm-guest-patching.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates several forms of Windows bias. Windows-specific examples (PowerShell, CLI) are provided before or in greater detail than Linux equivalents. PowerShell examples are given for Windows VMs but not for Linux VMs, and CLI examples for Windows VMs are more detailed. Windows registry keys and Windows Update service requirements are described explicitly, while Linux equivalents (such as disabling automatic updates) are less thoroughly explained. The 'Next steps' section links only to Windows VM management, omitting Linux VM guidance.
Recommendations
- Provide Azure PowerShell examples for Linux VMs where applicable, or clarify PowerShell usage for Linux.
- Ensure CLI examples for Linux VMs are as detailed as those for Windows VMs, including update and patching scenarios.
- Mention Linux-specific tools and configuration patterns (e.g., apt, yum, zypper, systemctl) with equal prominence to Windows tools (e.g., registry keys, Windows Update).
- Add a 'Next steps' link for Linux VM management, mirroring the Windows VM link.
- Where requirements or behaviors differ (e.g., disabling automatic updates), provide step-by-step instructions for both Linux and Windows, not just Windows.
- Present OS-specific information in parallel sections, or alternate the order between Windows and Linux to avoid implicit prioritization.
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.
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 First
Windows Tools
Summary
The documentation provides both Windows and Linux examples for Azure Image Builder, but there is a notable Windows bias in several areas. PowerShell is frequently referenced for checksum generation and image operations, often before Linux equivalents. Windows-specific customizers (PowerShell, WindowsRestart, WindowsUpdate) are described in detail, while Linux customizers (Shell) are covered but less prominently. Windows tools and commands (e.g., PowerShell cmdlets, Sysprep) are mentioned first or exclusively in some sections, and instructions for generating checksums or performing operations often default to Windows/PowerShell before Linux alternatives.
Recommendations
- Ensure Linux (bash/terminal) examples are provided alongside PowerShell examples for all operations, especially checksum generation and image template operations.
- Present Linux and Windows examples with equal prominence, alternating which is shown first or grouping by OS.
- Add more detailed Linux-specific guidance for customizers and validations, matching the depth given to Windows customizers.
- Where possible, reference cross-platform tools (e.g., Azure CLI) before platform-specific tools (e.g., PowerShell).
- Clarify in each section which features are Windows-only and which are cross-platform to avoid confusion.
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
Summary
While the documentation is focused on Linux VMs and provides comprehensive Azure CLI examples (which are cross-platform), the PowerShell section is disproportionately detailed, with many more examples and advanced usage patterns than the CLI section. Additionally, several PowerShell examples reference Windows-specific tools (e.g., ipconfig, .ps1 scripts, and Windows-specific parameter handling) and sometimes use Windows-centric terminology or defaults. REST API and ARM template examples also default to PowerShell/Windows script snippets (e.g., Write-Host, .ps1 files) rather than bash or sh scripts, despite the Linux focus. In some cases, Windows usage is described before Linux, or only Windows behaviors are explained in detail.
Recommendations
- Expand the Azure CLI section to include all advanced scenarios currently only covered in PowerShell (e.g., using script URIs, output/error blob streaming, parameters, running as a different user, scale set commands, etc.).
- Ensure REST API and ARM template examples use bash/sh scripts (e.g., echo Hello World!) rather than PowerShell (.ps1) scripts, or provide both Linux and Windows script examples where appropriate.
- When referencing built-in command IDs or parameter handling, clearly distinguish Linux and Windows behaviors, and provide Linux-first explanations and examples.
- Avoid using Windows-specific command IDs (e.g., ipconfig) or clarify their Linux equivalents (e.g., ifconfig or ip).
- Balance the depth of PowerShell and CLI coverage, ensuring Linux users can accomplish all tasks without needing to translate from PowerShell/Windows-centric instructions.
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
Powershell Heavy
Summary
The documentation covers both Windows and Linux VMs, but there are signs of Windows bias. PowerShell examples are provided alongside Azure CLI, but there are no explicit Bash or Linux shell script examples. The ARM template example is Windows-centric, with only Windows Server images and parameters. In some sections, Windows-specific terminology (e.g., password complexity, RDP port 3389) appears before Linux equivalents, and PowerShell is given equal prominence despite being Windows-focused. Linux users may need to adapt some steps or infer details for their environment.
Recommendations
- Add explicit Linux-focused examples in ARM templates (e.g., Ubuntu or CentOS images, SSH key authentication instead of password).
- Include Bash shell script examples for common operations, especially for associating VMs to capacity reservation groups.
- Clarify password/SSH authentication requirements for Linux VMs in portal and template instructions.
- Balance the order of CLI and PowerShell examples, or note that PowerShell is primarily for Windows users.
- In ARM templates, provide both Windows and Linux image references and OS configuration options.