Virtual Machines
2112
Total Pages
1865
Linux-Friendly Pages
247
Pages with Bias
11.7%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
818 issues found
Showing 301-325 of 818 flagged pages
Virtual Machines
Create an encrypted image version with customer-managed keys
.../articles/virtual-machines/image-version-encryption.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples and references are presented first and in greater detail, with explicit mention of Windows-specific tools and APIs (e.g., 'Cryptography API: Next Generation'). Linux parity is present via Azure CLI examples, but PowerShell (a Windows-centric tool) is prioritized and referenced more often, and Windows terminology/tools are mentioned before Linux equivalents.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples to prioritize cross-platform usage.
- Include explicit notes or examples for Linux/macOS users, such as bash scripts or command-line patterns.
- Reduce references to Windows-specific APIs (e.g., CNG) or provide equivalent Linux cryptography documentation links.
- Clarify that Azure CLI is fully supported on Linux/macOS and highlight any platform-specific considerations.
- Ensure that prerequisite and limitation sections mention both PowerShell and CLI options equally.
Create Pull Request
Virtual Machines
Create an image definition and image version
...s/blob/main/articles/virtual-machines/image-version.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides parity between Windows and Linux in most CLI and REST examples, but PowerShell examples are exclusively Windows-focused, and Windows terminology (e.g., Sysprep, PowerShell cmdlets) is often mentioned before or more prominently than Linux equivalents. The PowerShell section uses Windows as the default, with Linux only mentioned as an alternative. Windows-specific tools and patterns (Sysprep, PowerShell) are referenced without equivalent Linux detail, and Windows is sometimes presented first in guidance.
Recommendations
- Add Linux-focused PowerShell examples (e.g., using -OsType Linux in PowerShell commands).
- Ensure Linux terminology (e.g., waagent -deprovision) is given equal prominence and order as Windows (Sysprep) in all sections.
- Where Windows tools or patterns are referenced, provide direct Linux equivalents and examples side-by-side.
- Consider alternating the order of Windows and Linux references to avoid 'Windows first' bias.
- Explicitly mention cross-platform compatibility for PowerShell commands, or clarify when commands are Windows-only.
Virtual Machines
Customer intent: As a system administrator, I want to hibernate and manage virtual machines using various tools, so that I can optimize resource usage and maintain system performance effectively.
...nes/includes/hibernate-resume-platform-instructions.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Windows Specific Note
Summary
The documentation provides parity between Azure Portal, CLI, PowerShell, and REST API for most VM hibernation tasks. However, PowerShell (a Windows-centric tool) is given equal prominence as Azure CLI, and some examples (e.g., PowerShell output) are more detailed. There is a Windows-specific note about page file location, but no equivalent Linux-specific guidance. The PowerShell example for image definition uses Windows as the OS type, while the CLI example uses Linux, but there is no explicit parity or explanation for Linux-specific requirements. The documentation does not mention Linux/macOS shell scripting or tools (e.g., Bash), nor does it provide troubleshooting or configuration notes for Linux guests.
Recommendations
- Add Linux-specific notes where Windows-specific configuration is discussed (e.g., page file location for hibernation).
- Provide Bash or shell scripting examples alongside PowerShell for users on Linux/macOS.
- Ensure that CLI and PowerShell examples are equally detailed, and clarify any OS-specific differences in output or behavior.
- Include troubleshooting or configuration steps for Linux guests, similar to the Windows note about page file location.
- Explicitly state OS support and requirements for both Windows and Linux in relevant sections.
Virtual Machines
Customer intent: "As an IT administrator, I want to troubleshoot common VM extension failures in Azure Resource Manager templates, so that I can ensure the proper deployment and functionality of IaaS infrastructure."
...des/virtual-machines-common-extensions-troubleshoot.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page references a Windows-specific template authoring guide and links to a Windows-focused resource, without mentioning or providing equivalent Linux guidance. This creates a subtle bias toward Windows, as Linux users may not find relevant information for their platform.
Recommendations
- Include links to Linux-specific template authoring documentation alongside Windows resources.
- Explicitly mention that extensions and troubleshooting steps may differ for Linux VMs and provide guidance or examples for Linux scenarios.
- Ensure that troubleshooting advice and examples cover both Windows and Linux VM extensions.
Virtual Machines
Customer intent: As a cloud security administrator, I want to configure Azure Key Vault and Disk Encryption Set so that I can securely manage encryption keys for our managed disks across multiple subscriptions in compliance with security policies.
...-machines-disks-encryption-create-key-vault-powershell.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation exclusively uses Azure PowerShell for all examples and instructions, with no mention of Azure CLI, Bash, or Linux/macOS workflows. All commands and setup steps are tailored to PowerShell, which is traditionally a Windows-centric tool, and there is no guidance for users on Linux or macOS platforms. This creates friction for non-Windows users and may prevent them from easily following the documentation.
Recommendations
- Provide equivalent Azure CLI examples for each PowerShell command, as Azure CLI is cross-platform and widely used on Linux/macOS.
- Add a section describing platform requirements and alternatives, clarifying that PowerShell Core is available cross-platform but Azure CLI may be preferable for Linux/macOS users.
- Reorder or parallelize examples so that both PowerShell and CLI/Bash instructions are presented side-by-side or in separate tabs.
- Explicitly mention installation and authentication steps for Azure CLI, not just PowerShell.
Virtual Machines
Customer intent: As a cloud administrator, I want to expand virtual machine disks efficiently, so that I can manage storage capacity without downtime and ensure optimal performance in my infrastructure.
...al-machines-disks-expand-without-downtime-restrictions.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation lists Azure PowerShell and the Azure Portal (which is Windows-centric) as primary tools for disk expansion, with Azure CLI mentioned but not emphasized. Windows rescan instructions and links are provided before Linux equivalents, and Windows-specific tools (like devcon) are referenced. Linux instructions are present but less detailed and appear after Windows instructions.
Recommendations
- Provide Linux examples and instructions with equal detail and prominence as Windows.
- List cross-platform tools (Azure CLI) first, and clarify their parity for both OSes.
- Include explicit Linux command-line examples (e.g., using 'lsblk', 'partprobe', or 'udevadm') for rescanning disks.
- Avoid referencing Windows-only tools (like devcon) without Linux equivalents.
- Ensure that troubleshooting steps and links are equally comprehensive for Linux users.
Virtual Machines
Customer intent: As a cloud architect, I want to understand the limitations of shared disks across different disk types, so that I can effectively design and implement scalable virtual machine solutions in the cloud environment.
.../includes/virtual-machines-disks-shared-limitations.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation repeatedly references Windows Server Failover Cluster as the only clustering solution, linking exclusively to Windows-specific resources. There is no mention of Linux clustering solutions (e.g., Pacemaker, Corosync), nor are Linux-specific limitations or examples provided. This creates the impression that shared disk scenarios are primarily or only relevant for Windows environments.
Recommendations
- Include references to Linux clustering solutions such as Pacemaker or Corosync, and discuss their compatibility or limitations with Azure shared disks.
- Provide links to Linux documentation or guides for setting up shared disks in Linux-based clusters.
- Clarify whether the listed limitations apply equally to Linux and Windows, or specify any differences.
- Add examples or scenarios for Linux users to ensure parity.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides both Azure CLI and PowerShell examples for installing VM Watch, but the PowerShell examples are extensive and detailed, while Linux-specific shell examples (e.g., Bash) are absent. Screenshots and references to Windows installations are consistently presented before Linux equivalents. PowerShell, a Windows-centric tool, is given equal or greater prominence than CLI, and no Linux-native scripting or automation patterns are discussed.
Recommendations
- Add Bash or shell script examples for Linux users alongside PowerShell, especially for automation tasks.
- Present Linux and Windows screenshots in alternating order, or group them together to avoid Windows-first bias.
- Explicitly mention that PowerShell Core is cross-platform, or clarify when examples are Windows-only.
- Include troubleshooting or validation steps specific to Linux environments (e.g., using SSH, checking extension status via Linux commands).
- Highlight Linux-specific considerations in prerequisites and installation steps, such as package requirements or permissions.
Virtual Machines
Use infrastructure automation tools
...articles/virtual-machines/infrastructure-automation.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation generally covers both Linux and Windows automation tools, but several sections show Windows bias. Windows-specific tools (PowerShell DSC) are highlighted, and in some cases, only Windows examples or links are provided (e.g., Chef and Puppet). Windows examples are sometimes listed before Linux equivalents, and some sections provide more detailed Windows instructions or links than for Linux.
Recommendations
- Ensure every tool section provides both Linux and Windows usage examples or links, especially for Chef and Puppet.
- Where possible, present Linux and Windows examples side-by-side or in parallel, rather than listing Windows first.
- Expand Chef and Puppet sections to include Linux installation/configuration links and examples.
- Balance the coverage of PowerShell DSC with equivalent Linux configuration management tools (e.g., more emphasis on cloud-init, Ansible, etc.).
- Review all 'Learn how to' lists to ensure parity in depth and number of examples for both platforms.
Virtual Machines
Create and upload a CentOS-based Linux VHD
...rticles/virtual-machines/linux/create-upload-centos.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias by exclusively referencing Hyper-V (a Windows virtualization tool) for VHD creation and management, providing links to Windows-centric instructions, and using Hyper-V Manager for VM operations. There are no examples or guidance for equivalent Linux virtualization tools (such as KVM, QEMU, or VirtualBox) for creating, managing, or converting VHDs, nor are Linux-native commands or workflows shown for these tasks. Windows tools and patterns are mentioned first and exclusively throughout the critical steps.
Recommendations
- Add equivalent instructions and examples for creating and managing VHDs using Linux-native virtualization tools (e.g., KVM, QEMU, VirtualBox).
- Include Linux command-line examples for converting disk formats (e.g., using qemu-img to convert raw disks to fixed VHD format).
- Provide parity in VM management steps, such as how to shut down or deprovision a VM using Linux tools.
- Reference Linux documentation and resources alongside or before Windows/Hyper-V links.
- Explicitly state that Hyper-V is optional and list alternative Linux-based workflows.
Virtual Machines
Create and upload an OpenBSD image
...ticles/virtual-machines/linux/create-upload-openbsd.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias primarily in the VHD creation and conversion steps. It exclusively recommends Hyper-V (a Windows virtualization tool) and provides only PowerShell examples for converting VHDX to VHD, with no mention of Linux/macOS alternatives (e.g., qemu-img, VirtualBox, or VBoxManage). The Windows/Hyper-V approach is presented first and as the default, potentially creating friction for Linux/macOS users who may not have access to Hyper-V or PowerShell.
Recommendations
- Add instructions and examples for creating and converting VHD files using Linux/macOS tools such as qemu-img and VBoxManage.
- Mention cross-platform virtualization solutions (e.g., VirtualBox, KVM, qemu) alongside Hyper-V, and provide links to their documentation.
- Present Linux/macOS alternatives before or alongside Windows-specific tools to avoid implying Windows is required.
- Include sample commands for VHD conversion on Linux/macOS (e.g., qemu-img convert -f raw -O vpc disk.img disk.vhd).
Virtual Machines
Azure Disk Encryption with Microsoft Entra App Linux IaaS VMs (previous release)
...es/virtual-machines/linux/disk-encryption-linux-aad.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for Linux VM disk encryption, but PowerShell (a Windows-centric tool) is heavily emphasized, with more detailed scripts and explanations. Some sections (e.g., pre-encrypted VHDs) only show PowerShell examples, and references to using PowerShell sessions are frequent. The use of Windows terminology (e.g., BitLocker, PowerShell cmdlets) and the lack of native Linux shell (bash) or platform-agnostic examples creates friction for Linux/macOS users. In some places, PowerShell is mentioned before CLI, and there are no bash or Linux-native command examples for tasks like mounting disks, formatting, or interacting with Azure APIs outside of CLI/PowerShell.
Recommendations
- Add bash and Linux-native shell examples for all major steps, especially for disk operations and Azure API interactions.
- Provide parity in detail between Azure CLI and PowerShell sections, ensuring CLI examples are as comprehensive as PowerShell ones.
- Avoid assuming users have PowerShell available; clarify when PowerShell is required and offer alternatives for Linux/macOS users.
- Where possible, use platform-agnostic language and tools (e.g., Azure CLI, REST API) before Windows-specific tools.
- Explicitly state when a step or tool is Windows-only, and offer Linux/macOS alternatives.
- Add a section on using Azure REST API or SDKs from Linux for advanced scenarios.
Virtual Machines
Azure Disk Encryption with Microsoft Entra app prerequisites (previous release)
...virtual-machines/linux/disk-encryption-overview-aad.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page, while focused on Linux VMs, contains notable Windows bias. Critical configuration details (TLS registry changes, BitLocker Group Policy) are provided only for Windows, with no Linux equivalents or guidance. Windows tools (PowerShell scripts) are mentioned explicitly, while Linux CLI scripts are listed after. There is no discussion of Linux-specific encryption tooling or troubleshooting.
Recommendations
- Add Linux-specific configuration guidance for TLS and encryption prerequisites, or clarify if these steps are not required for Linux.
- Provide Linux equivalents for registry changes, or explicitly state that these steps are Windows-only and not applicable to Linux.
- Include Linux-first examples and troubleshooting steps, especially for common issues encountered during disk encryption.
- List Linux CLI scripts before PowerShell scripts, or group them together with clear OS applicability.
- Expand on Linux encryption mechanisms (e.g., dm-crypt, cryptsetup) and how they interact with Azure Disk Encryption.
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 page demonstrates a moderate Windows bias by referencing Hyper-V (a Windows-only virtualization solution) as the primary example for creating VHDs, linking to Windows-specific instructions, and providing PowerShell/Hyper-V tools for VHD conversion without mentioning Linux alternatives. There are no examples or guidance for Linux-native tools (e.g., qemu-img, VirtualBox, KVM) for creating or converting VHDs, which may create friction for Linux/macOS users.
Recommendations
- Add instructions and examples for creating and converting VHDs using Linux-native tools such as qemu-img, VirtualBox, or KVM.
- Provide links to Linux documentation for virtualization and disk conversion processes.
- Present Linux and Windows options side-by-side, or list Linux alternatives before or alongside Windows tools.
- Clarify that Hyper-V is just one option and explicitly mention cross-platform alternatives.
Virtual Machines
Creating and configuring a key vault for Azure Disk Encryption with Microsoft Entra ID (previous release)
...irtual-machines/linux/disk-encryption-key-vault-aad.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation provides extensive PowerShell-based examples and scripts, including certificate management and disk encryption workflows, which are inherently Windows-centric. Many advanced scenarios (KEK, certificate-based authentication) are only shown with PowerShell, and some steps (like certificate handling) use Windows file paths and tools. While Azure CLI examples are present for basic operations, advanced examples and automation scripts are PowerShell-only. There is little to no mention of Linux-native tooling, shell scripting, or cross-platform certificate management, and certificate-based authentication is explicitly stated as unsupported on Linux VMs.
Recommendations
- Provide equivalent Bash/shell scripts for advanced scenarios, especially for KEK setup and disk encryption extension management.
- Include Linux-native certificate management instructions (e.g., using OpenSSL, PEM files, and Linux file paths) for certificate-based workflows.
- Clarify which steps are cross-platform and which are Windows-only, and offer alternative approaches for Linux users where possible.
- Reorder examples so that Azure CLI (cross-platform) instructions are presented before PowerShell, or at least in parallel.
- Explicitly state limitations for Linux users earlier in the document, and link to Linux-specific guidance or workarounds.
Virtual Machines
Expand Virtual Hard Disks on a Linux VM
...b/main/articles/virtual-machines/linux/expand-disks.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Summary
The documentation is strongly focused on Linux, with all operational examples using Linux commands and tools (bash, growpart, xfs_growfs, etc.). However, there is a single section at the end that provides a PowerShell script for determining classic VM SKU support for expanding disks without downtime. This script is Windows/PowerShell-specific and lacks a Linux CLI or Bash equivalent, which could hinder Linux users needing this information.
Recommendations
- Provide an equivalent Azure CLI or Bash script for Linux users to determine classic VM SKU support for expanding disks without downtime.
- If PowerShell is required for some Azure queries, clarify that PowerShell Core can be installed on Linux/macOS and provide installation guidance.
- Ensure that any critical information available only via PowerShell is also accessible via Azure CLI or REST API, with examples for Linux/macOS users.
Virtual Machines
Creating and configuring a key vault for Azure Disk Encryption
...es/virtual-machines/linux/disk-encryption-key-vault.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples and scripts, but PowerShell is mentioned frequently and is given equal prominence to CLI, despite the Linux focus. PowerShell scripts and modules are referenced alongside CLI scripts, and PowerShell connection instructions are shown immediately after CLI, which may create friction for Linux users who are less likely to use PowerShell. There is also a slight tendency to mention Windows-centric tools (PowerShell) and scripts, rather than focusing solely on Linux-native approaches.
Recommendations
- Prioritize Azure CLI examples and scripts in the main flow, as CLI is native to Linux.
- Move PowerShell references to a dedicated section for Windows users or as an alternative, rather than presenting them alongside CLI for Linux-focused documentation.
- Clarify that PowerShell is optional and primarily relevant for Windows users.
- Ensure that all automation and scripting examples are available in Bash/CLI and clearly marked as Linux-compatible.
- Highlight Linux-native installation and usage patterns before mentioning PowerShell.
Virtual Machines
Azure Disk Encryption scenarios on Linux VMs
...ticles/virtual-machines/linux/disk-encryption-linux.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Azure CLI and PowerShell examples for all major tasks, but PowerShell (a Windows-centric tool) is frequently mentioned first, and its cmdlets are referenced in critical workflow descriptions. There is a notable emphasis on PowerShell usage, including variable initialization and script blocks, which may be less familiar or accessible to Linux/macOS users. Additionally, references to 'PowerShell session' and the use of PowerShell-specific terminology (cmdlets, parameters) reinforce a Windows-centric approach, even though the content is for Linux VMs.
Recommendations
- Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and native to Linux/macOS.
- Minimize PowerShell-specific terminology in general workflow descriptions; use neutral or CLI-focused language.
- Clarify that Azure CLI is the recommended tool for Linux/macOS users and highlight its parity with PowerShell.
- Where variable initialization or scripting is shown, provide equivalent bash shell script examples alongside PowerShell.
- Review backup and snapshot instructions to ensure CLI and portal methods are equally emphasized, not PowerShell-first.
Virtual Machines
Enable Azure Disk Encryption for Linux VMs
...les/virtual-machines/linux/disk-encryption-overview.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
While the documentation is focused on Linux VMs and provides Linux-centric technical details and examples, it repeatedly references Azure PowerShell as a primary tool for managing disk encryption, including quickstart links and scripts. PowerShell is traditionally a Windows-first tool, and its prominence may create friction for Linux/macOS users who prefer native Linux tools or Azure CLI. Additionally, PowerShell is mentioned before Azure CLI in some places, and the terminology table includes 'PowerShell cmdlets' as a core concept, reinforcing the Windows-centric tooling bias.
Recommendations
- Prioritize Azure CLI examples and links before PowerShell, as CLI is natively supported on Linux/macOS.
- Clarify that PowerShell is cross-platform, but emphasize CLI as the default for Linux workflows.
- Expand terminology to include Bash scripting and Linux-native tools relevant to disk encryption.
- Ensure all scripts and automation examples are available in Bash/CLI as well as PowerShell.
- Add explicit guidance for Linux/macOS users on installing and using Azure CLI.
Virtual Machines
Troubleshooting Azure Disk Encryption for Linux VMs
...tual-machines/linux/disk-encryption-troubleshooting.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation is focused on Linux VMs and provides Linux-specific troubleshooting steps, but when discussing how to check encryption status and disable disk encryption, it consistently presents Azure PowerShell (Windows-centric) commands first and in detail, with Linux-friendly Azure CLI commands mentioned only briefly and after PowerShell. All example output is shown using PowerShell, and no CLI output or Linux-native tooling is demonstrated.
Recommendations
- Provide Azure CLI examples and output alongside or before PowerShell examples, as CLI is cross-platform and preferred by many Linux users.
- Explicitly mention that Azure CLI can be used on Linux/macOS and provide equivalent commands for all PowerShell instructions.
- Include sample output for Azure CLI commands to match the detail given for PowerShell.
- Where possible, reference Linux-native troubleshooting tools (e.g., shell commands, log locations) relevant to disk encryption status.
- Review the order of presentation so Linux-first or CLI-first examples are shown in documentation targeting Linux VMs.
Virtual Machines
Verify encryption status for Linux - Azure Disk Encryption
...tual-machines/linux/how-to-verify-encryption-status.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents both PowerShell and Azure CLI examples for verifying disk encryption status, but PowerShell (a Windows-centric tool) is introduced before Azure CLI, despite the Linux focus. The PowerShell section is more detailed and extensive, with multiple scenarios and verbose output formatting, while Azure CLI examples are somewhat less emphasized. No Linux-native tools (other than basic OS-level checks) are mentioned for interacting with Azure resources, and PowerShell is not natively available on most Linux distributions. The OS-level section uses Linux commands appropriately.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and native to Linux.
- Ensure Azure CLI coverage matches PowerShell in detail and scenarios.
- Clarify that PowerShell is optional and not required for Linux users.
- Consider removing or de-emphasizing PowerShell for Linux-focused documentation, or add a note about its installation on Linux.
- Add more Linux-native tooling or scripting examples for interacting with Azure resources, if available.
Virtual Machines
Azure VM Image Builder service DevOps task (preview)
...es/virtual-machines/linux/image-builder-devops-task.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific tools (PowerShell) and terminology are frequently mentioned first or exclusively, especially in code examples and customization sections. Windows scenarios (such as Windows Update and PowerShell scripts) are described in detail, while Linux equivalents are sometimes less detailed or presented after Windows. Some sections (e.g., Windows Update task) are Windows-only, and troubleshooting steps reference Windows paths and behaviors. However, Linux support is present, and most critical steps include Linux examples.
Recommendations
- Ensure Linux examples are presented alongside or before Windows examples, especially in code blocks.
- Expand Linux-specific guidance, such as handling build artifacts and customization scripts, to match the detail given for Windows.
- Avoid Windows-first ordering in lists and instructions; alternate or group by OS.
- Include troubleshooting steps and tips for Linux users, not just Windows.
- Clarify when features or limitations apply only to Windows or Linux, and provide parity 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
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation provides both Windows and Linux coverage, but there is a notable Windows bias: Windows-specific tools (PowerShell, WindowsUpdate, WindowsRestart) are described in detail, often with examples and troubleshooting guidance, while Linux equivalents are less emphasized or missing (e.g., no LinuxRestart customizer). PowerShell commands and references to Windows tools (Get-FileHash, Sysprep) appear before Linux alternatives (sha256sum, waagent), and some sections (such as validation and generalization) provide more comprehensive Windows examples. The documentation also introduces Windows-only features (WindowsRestart, WindowsUpdate) without Linux counterparts.
Recommendations
- Add Linux-first examples in sections where Windows examples are currently shown first, especially for validation and generalization.
- Provide parity in troubleshooting and guidance for Linux users (e.g., more details on waagent, Linux image generalization issues, and troubleshooting).
- Explicitly state when a feature is Windows-only and suggest Linux alternatives or workarounds (e.g., for restart customizer).
- Include Linux CLI commands and tools (e.g., sha256sum, wget/curl) alongside or before Windows tools.
- Balance the order of presentation so Linux and Windows are treated equally in all example blocks and explanations.
Virtual Machines
How to Connect to the Azure Image Builder build VM
...al-machines/linux/image-builder-connect-to-build-vm.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation exhibits a moderate Windows bias: Windows terminology (RDP, WinRM) is frequently mentioned, sometimes before or alongside Linux equivalents (SSH). Several links and instructions reference Windows-specific documentation or tools first, and Linux-specific instructions/examples are less detailed or appear later. The password reset instructions reference the Azure portal's 'Reset Password' blade, which is more commonly used for Windows VMs. The Azure Bastion section refers to connecting to a Windows VM using SSH or RDP, but does not provide explicit Linux SSH examples. The Serial Console documentation link points to a Windows-focused page. Linux connection methods are mentioned, but not as thoroughly or prominently.
Recommendations
- Provide explicit Linux SSH connection examples and links alongside Windows RDP/WinRM instructions.
- Ensure documentation links for Serial Console and Bastion include both Linux and Windows guides, or point to OS-neutral pages.
- Clarify that the 'Reset Password' blade works for both Linux and Windows, and provide Linux-specific instructions if there are differences.
- Present Linux and Windows options in parallel, rather than listing Windows tools or documentation first.
- Add troubleshooting notes or caveats specific to Linux VMs where relevant (e.g., SSH key management, password reset differences).
Virtual Machines
Create and upload an Oracle Linux VHD
...les/virtual-machines/linux/oracle-create-upload-vhd.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a Windows bias in several ways. Hyper-V (a Windows virtualization tool) is mentioned as the primary example for creating VHDs, with instructions and links provided only for Hyper-V. Steps for interacting with the VM (such as shutting down and connecting) are described exclusively using Hyper-V Manager, with no mention of Linux-native virtualization tools (like KVM, QEMU, or VirtualBox). There are no examples or guidance for Linux users on how to create, manage, or convert VHDs using Linux tools, nor are Linux alternatives mentioned alongside Windows-centric instructions.
Recommendations
- Add instructions and examples for creating and managing VHDs using Linux-native tools such as KVM, QEMU, or VirtualBox.
- Provide guidance on converting disk formats to fixed VHD using Linux command-line tools (e.g., qemu-img).
- Include steps for shutting down and managing VMs using Linux virtualization platforms.
- Mention Linux alternatives alongside Hyper-V throughout the documentation, ensuring parity in tool recommendations and instructions.