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 126-150 of 815 flagged pages
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 Windows and Linux guidance for Azure Image Builder, but there are several areas where Windows-specific tools, commands, and examples are emphasized or presented first. PowerShell is frequently referenced for checksum generation, validation, and build operations, sometimes without equal prominence for Linux alternatives. Windows customizers (PowerShell, WindowsRestart, WindowsUpdate) are described in detail, while Linux equivalents are less extensive. Some sections (e.g., restart customizer) note the absence of Linux support, and Windows tools (PowerShell cmdlets) are often mentioned before Linux commands.
Recommendations
- Ensure Linux commands (e.g., sha256sum) are always presented alongside PowerShell alternatives for checksum generation and validation.
- Where PowerShell examples are given for build/cancel operations, provide equivalent Bash/Azure CLI scripts for Linux/macOS users.
- When describing customizers, balance the detail between Windows and Linux (e.g., Shell customizer usage, limitations, and troubleshooting).
- For sections where Windows tools are referenced (e.g., Get-FileHash, Start-Sleep), explicitly mention and link to Linux equivalents (e.g., sha256sum, sleep).
- Consider alternating the order of Windows and Linux examples to avoid 'windows_first' bias.
- Clarify limitations (such as lack of Linux restart customizer) and suggest Linux workarounds if possible.
Create Pull Request
Virtual Machines
Associate a virtual machine to a capacity reservation group
.../virtual-machines/capacity-reservation-associate-vm.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is intended for both Windows and Linux VMs, and the Azure CLI and API examples are platform-neutral. However, the ARM template example is Windows-centric, providing only Windows image SKUs and parameters, with no Linux equivalents or guidance. Additionally, in the ARM template, the default and allowed values for the OS image are exclusively Windows Server versions, and the storageProfile is hardcoded for Windows images. This creates friction for Linux users who wish to deploy Linux VMs using ARM templates with capacity reservation groups.
Recommendations
- Add a Linux-focused ARM template example, or at least document how to modify the template to deploy a Linux VM (e.g., using Ubuntu or CentOS images).
- In the ARM template parameters, include both Windows and Linux image SKUs and explain how to select the appropriate one.
- In the ARM template's storageProfile, provide examples for both Windows and Linux image references.
- Consider adding a note or section explicitly guiding Linux users on how to adapt the ARM template for their needs.
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, repeatedly references Windows-specific tools (Hyper-V, Convert-VHD PowerShell cmdlet) and provides Windows-centric instructions (e.g., Hyper-V Manager steps, Convert-VHD usage) without offering equivalent Linux alternatives or mentioning cross-platform options. Windows tools are mentioned first and sometimes exclusively, creating friction for Linux users who may not have access to Hyper-V or PowerShell.
Recommendations
- Provide instructions for creating and converting VHDs using Linux-native tools (e.g., qemu-img, VBoxManage, dd) alongside Hyper-V/PowerShell steps.
- Add guidance for extracting and preparing VHDs on Linux systems, not just Windows/WSL.
- Mention cross-platform alternatives for virtualization (e.g., VirtualBox, KVM) and disk conversion.
- Reorder sections so Linux-native workflows are presented first or in parallel with Windows options.
- Clarify which steps are Windows-only and offer Linux/macOS equivalents 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 Tools
Windows First
Summary
The documentation provides both Windows and Linux examples and covers Azure Image Builder features for both OS types. However, there are several areas where Windows-specific tools (PowerShell, WindowsRestart, WindowsUpdate customizers) are described in greater detail, and PowerShell is often used for checksum generation and image operations. Windows customizers are listed before Linux equivalents, and PowerShell commands are frequently shown first. Some features (restart customizer, update customizer) are Windows-only, but this is clearly stated. Linux examples are present but sometimes less emphasized or appear after Windows examples.
Recommendations
- Ensure Linux and macOS command-line examples (e.g., for checksum generation) are always provided alongside Windows/PowerShell equivalents.
- Where possible, present Linux and Windows examples in parallel, rather than listing Windows first.
- Expand Linux-specific guidance for customizers and validations (e.g., troubleshooting, best practices) to match the detail given for Windows.
- For sections where only Windows tools are mentioned (e.g., Get-FileHash), add Linux/macOS alternatives (e.g., sha256sum) with equal prominence.
- Consider adding a summary table of customizer types, clearly indicating OS support and parity.
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
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page is focused on Linux VMs and managed Run Command, but exhibits several Windows biases. PowerShell examples and tools (e.g., Set-AzVMRunCommand, Get-AzVMRunCommand) are heavily featured alongside Azure CLI, even though PowerShell is primarily a Windows-centric tool. Windows-specific terminology and tools (e.g., 'ipconfig', 'Write-Host', '.ps1' scripts, 'Secondary Logon' service) are mentioned or used in examples, sometimes before or instead of Linux equivalents. REST API and ARM template examples use Windows-style scripts (.ps1, Write-Host) without showing Linux shell script alternatives. Some explanations and notes reference Windows behaviors or tools without Linux parity. There are missing Linux-specific examples for REST API and ARM templates, and Windows terminology appears in Linux-focused sections.
Recommendations
- Add Linux shell script examples (e.g., using bash, sh, or .sh files) for REST API and ARM template sections, not just PowerShell/.ps1.
- When referencing command IDs or built-in scripts, ensure Linux equivalents (e.g., 'ifconfig', 'uname', 'ls') are shown alongside or before Windows ones.
- Clarify when PowerShell tools are cross-platform, and provide guidance for Linux users who may not have PowerShell installed.
- Avoid referencing Windows-specific services (e.g., 'Secondary Logon') in Linux documentation unless clearly marked as Windows-only.
- Show Linux CLI and shell script examples first in each section, and ensure Linux terminology is used throughout.
- Where possible, use generic scripting terminology (e.g., 'script', 'shell script') rather than Windows-centric terms (e.g., '.ps1', 'Write-Host').
Virtual Machines
Deploy a Premium SSD v2 managed disk
...n/articles/virtual-machines/disks-deploy-premium-v2.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Premium SSD v2 disks, but all CLI examples use Windows VM images (e.g., 'Win2016Datacenter') and Windows-centric variable names. There are no examples for deploying Linux VMs or using Linux-specific images, and the PowerShell examples are inherently Windows-focused. The CLI examples could be used on Linux/macOS, but they only show Windows VM deployment, creating friction for Linux users.
Recommendations
- Add Linux VM deployment examples alongside Windows examples in Azure CLI sections (e.g., use 'UbuntuLTS' or other popular Linux images).
- Explicitly mention that Azure CLI commands work cross-platform and provide sample variable values for Linux scenarios.
- In PowerShell sections, clarify that PowerShell is primarily for Windows users, and suggest Azure CLI for Linux/macOS users.
- Ensure parity in screenshots and portal instructions by referencing both Windows and Linux VM creation flows where relevant.
Virtual Machines
Deploy a ZRS managed disk
...lob/main/articles/virtual-machines/disks-deploy-zrs.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides parity between Azure CLI and Azure PowerShell examples, but PowerShell (a Windows-centric tool) is heavily featured, especially in the Resource Manager Template section and for feature registration. Windows/PowerShell commands are shown first in some sections, and ARM template deployment examples use PowerShell exclusively. There are no Linux-specific shell examples for ARM template deployment or feature registration, and the PowerShell examples use Windows VM images by default.
Recommendations
- Add Bash or cross-platform shell examples for ARM template deployment and feature registration (e.g., using Azure CLI or Bash scripts).
- Provide examples for deploying Linux VM images in PowerShell sections, or clarify how to do so.
- When showing PowerShell and CLI examples, alternate their order or explicitly note both are equally supported.
- For feature registration, show Azure CLI equivalents alongside PowerShell.
- Clarify that PowerShell examples can be run on Linux/macOS using PowerShell Core, if applicable.
Virtual Machines
Ultra Disks for VMs - Azure Managed Disks
...in/articles/virtual-machines/disks-enable-ultra-ssd.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is intended for both Linux and Windows VMs, but consistently uses Windows-specific VM images (e.g., 'Win2016Datacenter') in all CLI and PowerShell examples. There are no examples showing how to deploy Ultra Disks with a Linux VM image, nor any Linux-specific considerations or commands. The Quickstart link in the portal section also points only to Windows VM creation. This creates friction for Linux users, who must adapt the examples themselves.
Recommendations
- Provide parallel examples using a Linux VM image (e.g., 'UbuntuLTS') for Azure CLI and PowerShell sections.
- Add a Quickstart link for creating a Linux VM in the portal.
- Explicitly mention that the steps apply to both Linux and Windows, and highlight any OS-specific considerations.
- Where variables are set (e.g., --image), show both Windows and Linux options, or note that any supported image can be used.
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 PowerShell link is listed first and the custom RBAC role creation link points only to a PowerShell-based guide. There are no explicit Linux/macOS examples or links for custom role creation, and PowerShell is emphasized over CLI in some sections.
Recommendations
- Provide links to both Azure CLI and Azure PowerShell guides for custom RBAC role creation.
- Ensure Azure CLI examples and links are presented alongside or before PowerShell examples, especially for cross-platform tasks.
- Add explicit Linux/macOS instructions or links where relevant, such as for custom role creation and disk configuration.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides extensive Azure PowerShell examples and scripts, which are primarily Windows-centric, and references Windows tools (e.g., Chocolatey, PowerShell, cmd.exe) for installing the armclient. While Azure CLI and REST API methods are documented, the PowerShell section is significantly more detailed and presented first. Linux support is acknowledged throughout, but Linux-native installation methods and shell examples are missing or secondary.
Recommendations
- Add Bash shell examples for Azure CLI usage, showing Linux/macOS command syntax and environment.
- Provide Linux-native installation instructions for armclient (e.g., using pip, npm, or manual download), avoiding exclusive reliance on Chocolatey.
- Include parity in scripting examples for disk management, using Azure CLI or REST API in Bash, not just PowerShell.
- Clarify that PowerShell can be used cross-platform, but highlight any limitations or differences for Linux/macOS users.
- Consider reordering sections so Azure CLI and REST API methods are presented before or alongside PowerShell.
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
Windows First
Summary
The documentation repeatedly references Windows Server Failover Cluster and links to Windows-specific clustering requirements, without mentioning Linux equivalents (such as Linux clustering solutions or disk sharing limitations for Linux-based clusters). The proximity placement groups link is Windows-specific, and there are no Linux-focused examples or references. Windows clustering is discussed first and exclusively, creating a subtle Windows bias.
Recommendations
- Add information about shared disk limitations for Linux-based clustering solutions (e.g., Pacemaker, Corosync, or other Linux HA clusters).
- Include links to Linux documentation or guidance for configuring shared disks in Linux environments.
- Clarify if certain limitations (such as 'only basic disks can be used with some versions of Windows Server Failover Cluster') apply only to Windows, and provide Linux-specific guidance where relevant.
- Balance references to Windows and Linux clustering tools and scenarios.
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 include a Linux/macOS equivalent. The AzCopy command is shown only in Windows syntax, and the use of Windows paths ('c:\somewhere\mydisk.vhd') may confuse Linux/macOS users. Additionally, AzCopy is referenced as 'AzCopy.exe', which is specific to Windows, and there is no mention of how to run AzCopy on Linux/macOS or what the command would look like. The rest of the CLI examples are generic and compatible with all platforms, but the critical upload step is Windows-centric.
Recommendations
- Add a Linux/macOS AzCopy example, e.g., 'azcopy copy "/home/user/mydisk.vhd" "sas-URI" --blob-type PageBlob'.
- Clarify that AzCopy is cross-platform and provide download/install instructions for Linux/macOS.
- Mention that the path syntax differs between Windows and Linux/macOS, and show both formats.
- Use 'azcopy' (lowercase) for Linux/macOS and 'AzCopy.exe' for Windows, or note the difference.
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 both Windows and Linux coverage in the CLI and API sections, but exhibits some Windows bias in several areas: PowerShell is given equal prominence to the cross-platform Azure CLI, ARM template examples default to Windows images, and some parameter descriptions and allowed values are Windows-specific. Linux-specific examples (e.g., ARM template for Linux VMs) are missing, and Windows terminology and tools are often mentioned first or exclusively.
Recommendations
- Add explicit Linux VM examples in ARM template sections (e.g., provide an 'imageReference' for a popular Linux distribution such as Ubuntu).
- In ARM template parameters, include allowedValues and descriptions for common Linux images alongside Windows ones.
- When showing tabbed examples, alternate the order or clarify that both Windows and Linux are supported, and provide Linux-specific notes where relevant.
- Where PowerShell is used, clarify that it is primarily for Windows users, and highlight cross-platform alternatives (Azure CLI, REST API) for Linux/macOS users.
- Review parameter descriptions and default values to ensure Linux parity (e.g., adminPassword vs. SSH keys, port 3389 vs. 22).
Virtual Machines
Deploy a Premium SSD v2 managed disk
...n/articles/virtual-machines/disks-deploy-premium-v2.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Premium SSD v2 disks, but all CLI examples use Windows VM images (e.g., 'Win2016Datacenter') and do not show Linux VM deployment or disk attachment. PowerShell examples are inherently Windows-centric. There are no explicit Linux VM examples, nor are Linux-specific considerations or commands provided. The portal instructions are generic, but the scripting sections are Windows-focused.
Recommendations
- Add Azure CLI examples that deploy and attach Premium SSD v2 disks to Linux VMs (e.g., using 'UbuntuLTS' or other Linux images).
- Include Linux-specific notes or considerations, such as disk formatting or mounting steps for Linux VMs.
- Ensure variable names and instructions are not Windows-centric (e.g., avoid only referencing Windows images or admin credentials).
- Provide parity in scripting examples for both Linux and Windows VM scenarios.
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
Powershell Heavy
Windows First
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for creating encrypted image versions, but the PowerShell section is presented first and is more detailed, including additional VM creation steps and parameter explanations. The CLI section is present and functional, but less verbose. There is a reference to Windows cryptographic modules (CNG) in the introduction, but the overall feature is cross-platform. No Linux-specific examples or shell scripts are provided, and PowerShell is emphasized, which may create friction for Linux/macOS users.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is more universally available across platforms.
- Expand CLI examples to match the detail and completeness of the PowerShell section, including VM creation steps and parameter explanations.
- Add Bash shell scripting examples for common tasks, especially for Linux users.
- Clarify that PowerShell examples are cross-platform (if true), or note any limitations for Linux/macOS users.
- Where possible, avoid referencing Windows-specific cryptographic APIs unless they are relevant to Linux users.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides extensive Azure PowerShell examples and scripts, with detailed walkthroughs for enabling Write Accelerator using PowerShell. Windows-specific tools (Chocolatey, cmd.exe, PowerShell) are referenced for installing armclient, and installation instructions are Windows-centric. While Azure CLI and REST API methods are covered, PowerShell is presented first and in greater detail. Linux is mentioned as supported, but Linux-native installation methods and shell examples are missing.
Recommendations
- Add Linux/macOS instructions for installing armclient (e.g., via Homebrew or manual download), including bash/zsh shell commands.
- Provide examples using bash or Azure CLI for common tasks, and ensure parity with PowerShell scripts.
- Reorder sections so Azure CLI examples appear before or alongside PowerShell, or clearly state both are equally supported.
- Explicitly mention cross-platform compatibility for all tools and commands, and highlight any OS-specific limitations.
- Include troubleshooting or configuration notes for Linux users (e.g., permissions, disk manager integration).
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
Windows First
Summary
The documentation repeatedly references Windows Server Failover Cluster and links to Windows-specific clustering requirements. There are no equivalent mentions or links for Linux clustering solutions (such as Pacemaker or Corosync), nor are Linux-specific limitations or guidance provided. Windows clustering is mentioned as a limitation for all disk types, and the proximity placement group link is Windows-specific. This creates a Windows-first impression and omits Linux parity.
Recommendations
- Add information about Linux-based clustering solutions (e.g., Pacemaker, Corosync) and their compatibility or limitations with Azure shared disks.
- Include links to relevant Linux documentation or guidance for configuring shared disks in Linux clusters.
- Clarify whether the 'basic disks' limitation applies to Linux clusters, or if there are different requirements.
- Provide parity in proximity placement group documentation for Linux VMs, or clarify if this feature is Windows-only.
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-centric example for uploading a VHD using AzCopy.exe, referencing a Windows file path and executable, but does not offer a Linux/macOS equivalent. The AzCopy upload command is shown only for Windows, and the CLI script for copying disks uses Bash syntax, which is Linux-friendly, but the initial upload example is Windows-first and lacks parity for Linux/macOS users.
Recommendations
- Add a Linux/macOS AzCopy example, using the appropriate executable (e.g., ./azcopy or azcopy) and a Unix-style file path (e.g., /home/user/mydisk.vhd).
- Clarify that AzCopy is cross-platform and provide download/install instructions for Linux/macOS.
- Where possible, show both Windows and Linux/macOS commands side-by-side, or note differences in syntax and paths.
- Explicitly mention that the Bash script for copying disks is suitable for Linux/macOS environments, and provide a PowerShell equivalent for Windows users if desired.
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
The documentation is focused on Linux VMs and provides extensive Azure CLI examples, but PowerShell examples are also heavily featured. Several PowerShell commands and notes reference Windows-specific tools and patterns (e.g., 'New-AzStorageBlobSASToken', 'ipconfig', 'myscript.ps1'), and in some cases, Windows terminology or instructions are presented before or alongside Linux equivalents. REST API and ARM template examples sometimes use Windows-style scripts (PowerShell) or refer to '.ps1' files, even in Linux contexts.
Recommendations
- Ensure all script examples in REST API and ARM template sections use Linux shell scripts (e.g., '.sh') instead of PowerShell scripts ('.ps1') when targeting Linux VMs.
- Clarify when PowerShell commands are applicable to Linux VMs, and avoid referencing Windows-specific tools or patterns unless necessary.
- Provide Linux-specific instructions and examples before or alongside any Windows-related notes, especially in sections about parameters, script URIs, and command IDs.
- Review notes and examples for unnecessary references to Windows tools (e.g., 'ipconfig' instead of 'ifconfig', 'myscript.ps1' instead of 'myscript.sh').
- Where PowerShell is used, explicitly state its cross-platform support or recommend Azure CLI for Linux users.
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, but there is a notable Windows bias in several areas. PowerShell examples and references to Windows tools (such as Get-FileHash, Invoke-AzResourceAction, and Sysprep) are frequently given, sometimes before or instead of Linux equivalents. In some sections, Windows-specific customizers (PowerShell, WindowsRestart, WindowsUpdate) are described in detail, while Linux equivalents are less emphasized or missing (e.g., no Linux restart customizer). SHA256 checksum generation is shown with PowerShell first, and troubleshooting links often reference Windows-centric solutions. However, Linux support is present and described, and Linux examples are included, especially for shell customizers and validations.
Recommendations
- Ensure Linux and macOS examples are always provided alongside Windows/PowerShell examples, especially for checksum generation, image build/cancel commands, and troubleshooting.
- Present Linux (shell/bash) and Windows (PowerShell) examples in parallel, rather than Windows first.
- Add Linux-specific troubleshooting guidance and links where only Windows solutions are referenced.
- Clarify limitations (such as lack of Linux restart customizer) and suggest Linux workarounds (e.g., using shell scripts for reboot).
- Where PowerShell tools are referenced (e.g., Get-FileHash), provide equivalent Linux/macOS commands (e.g., sha256sum) with equal prominence.
Virtual Machines
Customer intent: "As an IT administrator managing Azure IaaS virtual machines, I want to implement a backup and disaster recovery plan for unmanaged disks, so that I can ensure data durability and high availability in the event of localized or regional failures."
...al-machines/page-blobs-backup-and-disaster-recovery.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Minor Missing Linux Example
Summary
The documentation covers both Linux and Windows VMs for Azure backup and disaster recovery, but there are several instances where Windows tools and patterns (such as PowerShell, Volume Shadow Service, and Windows-specific backup mechanisms) are mentioned first or exclusively, with Linux equivalents referenced later or less prominently. PowerShell is frequently cited for automation and recovery, while Linux CLI or scripting options are less detailed. Some links and examples (e.g., incremental snapshots) point to Windows-specific pages, and Linux-specific instructions are sometimes relegated to 'see also' or 'for Linux, see...' notes.
Recommendations
- Ensure Linux CLI (Azure CLI, Bash, etc.) examples are given equal prominence to PowerShell throughout the document, especially in automation and recovery sections.
- When referencing tools like Volume Shadow Service for Windows, provide parallel explanations and examples for Linux (e.g., fsfreeze, application-consistent backup methods) directly in the main text, not just as links.
- Where links point to Windows-specific guides (e.g., incremental snapshots), ensure Linux equivalents are linked with equal visibility.
- Add explicit Linux scripting examples for snapshot management, backup, and restore, not just references to Azure CLI.
- Review tables and summary sections to ensure Linux and Windows parity in tool recommendations and workflow descriptions.
Virtual Machines
Deploy a ZRS managed disk
...lob/main/articles/virtual-machines/disks-deploy-zrs.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying ZRS managed disks. However, PowerShell examples are heavily focused on Windows VM creation and use Windows-specific tools and patterns (e.g., Windows image references, Windows admin credentials, ConvertTo-SecureString). PowerShell sections consistently use Windows images and parameters, while Azure CLI examples use Ubuntu images. Resource Manager Template examples are also presented with PowerShell commands and Windows-centric parameters. The PowerShell and template sections are Windows-first and lack parity for Linux VM creation, making it harder for Linux users to follow equivalent workflows using PowerShell or ARM templates.
Recommendations
- Add PowerShell examples for deploying Linux VMs with ZRS disks, using Linux image references and Linux admin credential patterns.
- Update Resource Manager Template sections to include Linux VM deployment examples, or clarify how to adapt templates for Linux VMs.
- Ensure that PowerShell and ARM template instructions are not exclusively Windows-focused, and provide guidance for Linux scenarios.
- Where possible, use generic admin credential patterns or explain differences for Linux and Windows VM creation.
Virtual Machines
Ultra Disks for VMs - Azure Managed Disks
...in/articles/virtual-machines/disks-enable-ultra-ssd.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation covers Ultra Disks for both Linux and Windows VMs, but consistently uses Windows VM images (Win2016Datacenter) in all CLI and PowerShell examples. No examples are provided for deploying Ultra Disks with Linux VM images, nor are Linux-specific post-deployment instructions (such as partitioning/formatting disks on Linux) included. Windows VM creation is referenced first in portal instructions, and all code samples default to Windows VM images, creating friction for Linux users.
Recommendations
- Add parallel examples using Linux VM images (e.g., Ubuntu, CentOS) for Azure CLI and PowerShell commands.
- In portal instructions, reference both Windows and Linux VM creation quickstarts equally, or provide links to Linux VM creation guides.
- Include post-deployment steps for partitioning and formatting Ultra Disks on Linux (e.g., using fdisk, mkfs, etc.), alongside Windows instructions.
- Explicitly state that Ultra Disks are supported for both Linux and Windows VMs, and clarify any OS-specific requirements or limitations.
- Where variables are set (e.g., --image), show both Windows and Linux values, or note how to select the appropriate image for your OS.
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, repeatedly references Windows-centric tools (notably Hyper-V and PowerShell's Convert-VHD) as the primary or only method for creating and converting VHDs. It lacks equivalent Linux-native instructions for key steps such as VHD creation and conversion, and Windows tools are mentioned first and most prominently.
Recommendations
- Add instructions for creating and converting VHDs using Linux-native tools (e.g., qemu-img, VBoxManage, or vboxmanage convertfromraw).
- Provide Linux command-line examples for converting disk images to fixed-size VHD format.
- Mention KVM, VirtualBox, or other common Linux virtualization solutions alongside Hyper-V, and provide links to their documentation.
- When referencing PowerShell cmdlets (e.g., Convert-VHD), also reference equivalent Linux commands or tools in the same section.
- Consider reordering sections so that Linux-native workflows are presented first or at least in parallel with Windows-based ones.
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
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for verifying disk encryption status on Linux VMs, but the PowerShell section is presented before the Azure CLI section and contains more detailed, step-by-step examples. This may create friction for Linux users, as PowerShell is not the native or default scripting environment for Linux, and the CLI section, while present, is less comprehensive in some areas. The portal instructions are platform-neutral, and the OS-level checks use Linux-native tools, but the prominence and detail of PowerShell examples suggest a Windows bias.
Recommendations
- Present Azure CLI examples before PowerShell examples, as Azure CLI is more commonly used on Linux.
- Ensure Azure CLI examples are as detailed and comprehensive as PowerShell examples, covering all scenarios (single pass, dual pass, unattached disks, managed/unmanaged disks).
- Explicitly note that PowerShell examples are for users who have PowerShell Core installed on Linux, but Azure CLI is recommended for Linux environments.
- Consider adding Bash script examples for common tasks, where appropriate.
- Review and balance the depth of coverage between PowerShell and CLI sections.