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 26-50 of 815 flagged pages
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 in every disk type section, and the proximity placement group link uses a Windows-specific URL, suggesting Windows is the primary context.
Recommendations
- Add information about Linux-based clustering solutions (e.g., Pacemaker, Corosync) and their compatibility or limitations with Azure shared disks.
- Include links to Linux clustering documentation and requirements where Windows Failover Cluster is referenced.
- Clarify if shared disks are supported for Linux clusters, and if so, provide parity in limitations and guidance.
- Use neutral URLs for features like proximity placement groups, or provide both Windows and Linux links.
Create Pull Request
Virtual Machines
Create and upload an Ubuntu Linux VHD in Azure
...rticles/virtual-machines/linux/create-upload-ubuntu.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation, while focused on Ubuntu Linux, frequently references Windows-specific tools (notably Hyper-V and the Convert-VHD PowerShell cmdlet) for VHD creation and conversion, and provides detailed steps for using Hyper-V Manager. Equivalent Linux-native tooling (such as qemu-img or VBoxManage) is not mentioned or demonstrated. This creates friction for Linux/macOS users who may not have access to Windows environments.
Recommendations
- Add instructions and examples for creating and converting VHD files using Linux-native tools such as qemu-img or VBoxManage.
- Provide a Linux workflow for the VHD creation and conversion steps, including commands for converting raw disk images to fixed-size VHD.
- Reorder sections or provide parallel instructions so that Linux-native approaches are presented before or alongside Windows/Hyper-V/PowerShell methods.
- Clarify which steps are Windows-only and provide alternatives for Linux/macOS users where possible.
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 (using 'AzCopy.exe' and Windows file paths) but does not offer a Linux/macOS equivalent. The AzCopy upload command is shown only for Windows, and the file path syntax is Windows-specific. There is no explicit Linux/macOS AzCopy example, even though the rest of the CLI instructions use Bash syntax and variables. The Windows example is presented first and exclusively, creating friction for Linux/macOS users.
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 file path syntax differs between Windows and Linux/macOS.
- Consider showing both Windows and Linux/macOS AzCopy examples side-by-side.
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 templates, but there is a notable Windows bias in several areas. PowerShell commands and tools are frequently referenced, often before Linux equivalents. Windows-specific customizers (PowerShell, WindowsRestart, WindowsUpdate) are described in detail, while Linux customizers (Shell) are less prominent. SHA256 checksum generation is shown with PowerShell first, and Windows-specific troubleshooting and RBAC instructions are highlighted. Some sections (e.g., restart customizer) explicitly state Linux is not supported, but Linux alternatives or workarounds are not discussed.
Recommendations
- Ensure Linux and macOS command-line examples (e.g., Azure CLI, shell commands) are always provided alongside PowerShell, and shown first or equally.
- Add Linux-specific troubleshooting guidance and RBAC instructions where only Windows is mentioned.
- Where Windows customizers (e.g., WindowsRestart) are described, clarify Linux alternatives or explicitly state limitations.
- For checksum generation, provide Linux/macOS commands (e.g., sha256sum) before or alongside PowerShell.
- Balance the prominence of Windows and Linux customizer examples, ensuring Shell customizer usage is as detailed as PowerShell.
- Where Windows tools (e.g., Invoke-WebRequest) are mentioned, also reference Linux equivalents (e.g., wget, curl).
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
Summary
The documentation is focused on Linux VMs and provides comprehensive Azure CLI examples for Linux shell scripts. However, PowerShell examples are given equal or greater prominence, and some PowerShell sections reference Windows-specific tools and patterns (e.g., 'ipconfig', 'myscript.ps1', 'Secondary Logon' service). REST API and ARM template examples use Windows-centric script examples (e.g., 'Write-Host Hello World!', '.ps1' scripts) even though the page is about Linux VMs. The PowerShell section is extensive and sometimes references Windows-specific behaviors before Linux equivalents.
Recommendations
- Ensure REST API and ARM template examples use Linux shell scripts (e.g., 'echo Hello World!' or '.sh' files) instead of PowerShell scripts.
- Clarify in PowerShell examples when a command or parameter is Windows-only, and provide Linux-specific alternatives or explanations.
- Avoid referencing Windows tools (e.g., 'ipconfig') in Linux documentation; use Linux equivalents like 'ifconfig' or 'ip'.
- Where PowerShell is used, explicitly show Linux shell script usage and clarify cross-platform applicability.
- Review and adjust example ordering so Linux CLI and shell examples are shown first, with Windows/PowerShell as secondary.
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
Summary
The documentation is focused on Linux VMs and provides comprehensive Azure CLI examples, but PowerShell examples are given equal or greater prominence and detail. Several PowerShell commands reference Windows-specific tools and patterns (e.g., ipconfig, .ps1 scripts, Windows-specific parameter passing, and 'Secondary Logon' service), sometimes without clear Linux alternatives. REST and ARM template examples occasionally use Windows script syntax (.ps1) or Windows-centric command IDs. Some notes and explanations are written from a Windows perspective, and PowerShell is presented as a primary tool for Linux VM management, which may not align with typical Linux administrator workflows.
Recommendations
- Ensure all PowerShell examples referencing Windows-specific tools (e.g., ipconfig, .ps1 scripts) are clearly marked as Windows-only or provide Linux equivalents (e.g., ifconfig, .sh scripts).
- Where parameter passing differs between Windows and Linux, clarify the Linux-specific behavior and provide explicit Linux shell script examples.
- In REST and ARM template examples, use Linux shell script syntax (.sh) and Linux command IDs where appropriate.
- Present Azure CLI examples before PowerShell, as CLI is more commonly used by Linux administrators.
- Remove or minimize references to Windows-only services (e.g., 'Secondary Logon') in Linux-focused documentation, or clearly state their relevance.
- Add more Linux-native troubleshooting and scripting examples, such as bash scripts, and highlight Linux-specific best practices.
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
Powershell Heavy
Windows Tools
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying Premium SSD v2 disks, but the CLI examples default to Windows VM images (e.g., 'Win2016Datacenter') and use Windows-centric parameters (admin password, username, etc.). PowerShell is featured equally alongside CLI, and all scripts use Windows images by default. There are no explicit Linux VM deployment examples, and the documentation does not mention or show how to deploy or attach Premium SSD v2 disks to Linux VMs, nor does it show Linux-specific parameters or considerations. This creates a subtle but notable Windows bias, especially in the example scripts.
Recommendations
- Add explicit Linux VM deployment examples using popular Linux images (e.g., Ubuntu, CentOS) in the Azure CLI sections.
- In CLI scripts, show how to set up SSH authentication for Linux VMs (e.g., using --authentication-type ssh and --ssh-key-values).
- Clarify in each example that the disk can be attached to both Windows and Linux VMs, and provide at least one Linux-focused walkthrough.
- When initializing variables in CLI scripts, use a Linux image (e.g., 'UbuntuLTS') as the default or show both Windows and Linux alternatives.
- Mention any Linux-specific considerations for Premium SSD v2 disks, if applicable.
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
While the documentation claims to apply to both Windows and Linux VMs, there are several areas where a Windows bias is evident. PowerShell examples are consistently provided alongside Azure CLI, but there are no Bash or Linux shell script equivalents. In the ARM template section, only Windows images are referenced, and the default parameters and allowed values are exclusively for Windows Server SKUs. The PowerShell tab is always present, but there is no mention of Linux-native scripting tools. In some cases, Windows-centric terminology (e.g., password complexity for 'Administrator account') is used without clarifying Linux differences.
Recommendations
- In the ARM template section, provide an example or parameter set for deploying a Linux VM (e.g., using Ubuntu or CentOS images) alongside the Windows example.
- Where PowerShell examples are given, consider adding Bash or shell script equivalents for Linux users, or clarify that Azure CLI commands are cross-platform and can be run in Bash.
- In sections referencing 'Administrator account' and password requirements, clarify the differences for Linux VMs (e.g., SSH key usage, username restrictions).
- In the allowed values for OSVersion in ARM templates, include popular Linux distributions or provide a note/link to Linux image references.
- Review the ordering of examples/tabs to ensure CLI (cross-platform) is presented before PowerShell where possible.
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, but PowerShell (and Windows-centric tooling) is heavily emphasized. PowerShell examples are extensive and detailed, and Resource Manager template sections use PowerShell for feature registration and deployment. Windows VM images are used in PowerShell examples, while CLI examples use Ubuntu. The order of tabs puts Azure portal first, then CLI, then PowerShell, but PowerShell is given parity and more detail. Feature registration steps are only shown in PowerShell, with no Linux/bash equivalent. Resource Manager template deployment commands are PowerShell-only.
Recommendations
- Add bash/Linux shell equivalents for feature registration and Resource Manager template deployment (e.g., using Azure CLI or 'az deployment group create').
- Provide examples for deploying Windows VMs using Azure CLI, and Linux VMs using PowerShell, to show cross-platform parity.
- Clarify that PowerShell commands can be run on Linux/macOS (with PowerShell Core), or provide explicit bash alternatives.
- For Resource Manager template sections, show both PowerShell and Azure CLI deployment commands.
- Where possible, avoid using Windows-specific VM images in PowerShell examples unless demonstrating a Windows-only scenario.
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-centric examples (e.g., Win2016Datacenter image, password authentication, Windows admin username conventions) in all CLI and PowerShell code blocks. There are no Linux-specific VM image examples, nor guidance for Linux authentication or disk formatting. The Quickstart link in the Portal section points only to Windows VM creation. While the Azure CLI and PowerShell tools are cross-platform, the actual examples are Windows-only, creating friction for Linux users.
Recommendations
- Provide Linux VM image examples (e.g., Ubuntu, CentOS) alongside Windows examples in CLI and PowerShell sections.
- Include Linux authentication options (e.g., SSH key authentication) in CLI/PowerShell examples.
- Add links to Linux VM Quickstart documentation in the Portal section.
- Mention Linux disk initialization/formatting steps after disk attachment.
- Alternate Windows and Linux examples, or show both in parallel where possible.
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 step-by-step instructions for enabling Write Accelerator using PowerShell. Windows-specific tools (Chocolatey, cmd.exe, PowerShell) are referenced for installing armclient, with no mention of Linux/macOS alternatives. The PowerShell section is much more detailed than the Azure CLI section, which is brief and lacks full scripting examples. Windows tools and patterns are mentioned first and more prominently, even though the feature is available for both Linux and Windows VMs.
Recommendations
- Provide parity in scripting examples for Azure CLI, including full scripts for adding/enabling Write Accelerator on disks, similar to the PowerShell section.
- Mention and provide installation instructions for armclient on Linux/macOS (e.g., via npm or direct download), not just Chocolatey/Windows.
- When referencing disk/volume managers, ensure Linux tools (LVM, MDADM) are mentioned equally and provide links to relevant Linux documentation.
- Consider presenting Azure CLI examples before or alongside PowerShell examples, as CLI is cross-platform.
- Clarify that all steps and tools are available for both Linux and Windows users, and highlight any OS-specific differences.
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 exclusively to Windows-specific clustering requirements. There is no mention of Linux clustering solutions (such as Pacemaker or Corosync), nor any guidance for Linux users. Windows clustering is presented as the only relevant scenario for shared disks, creating a Windows-first bias.
Recommendations
- Add information about Linux-based clustering solutions (e.g., Pacemaker, Corosync) and their compatibility with Azure shared disks.
- Include links to Linux clustering documentation and requirements.
- Clarify whether shared disks are supported for Linux clusters, and if so, provide examples or limitations.
- If Windows Failover Cluster is the only supported scenario, explicitly state this to avoid confusion.
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 VHD creation, frequently references Windows-centric tools and workflows (notably Hyper-V and PowerShell's Convert-VHD), presents Windows/Hyper-V as the primary or only detailed method for VHD creation/conversion, and does not provide equivalent Linux-native tooling or workflows for these critical steps. This can create friction for Linux/macOS users attempting to follow the guide.
Recommendations
- Add instructions for creating and converting VHDs using Linux-native tools (e.g., qemu-img, VBoxManage, or dd) alongside or before Hyper-V/PowerShell steps.
- Explicitly mention and provide example commands for extracting and working with VHDs on Linux/macOS, not just in the context of WSL on Windows.
- Where Hyper-V or Windows tools are referenced, clarify that they are optional and provide parity for users on Linux/macOS.
- Link to or include references for open-source or cross-platform alternatives for each Windows-specific tool or step.
- Consider reordering sections so that Linux-native workflows are presented first, or at least in parallel with Windows/Hyper-V approaches.
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 command example ('AzCopy.exe copy "c:\somewhere\mydisk.vhd" "sas-URI" --blob-type PageBlob') and does not offer a Linux/macOS equivalent. The AzCopy CLI example uses Windows path syntax and executable naming, and the Linux/macOS usage (e.g., './azcopy' or '/home/user/mydisk.vhd') is not shown. The documentation otherwise uses Azure CLI commands, which are cross-platform, but the critical upload step is presented only in Windows format.
Recommendations
- Add a Linux/macOS AzCopy example, such as './azcopy copy "/home/user/mydisk.vhd" "sas-URI" --blob-type PageBlob'.
- Mention that AzCopy is cross-platform and provide download/install instructions for Linux/macOS.
- Clarify that file paths and executable names differ between Windows and Linux/macOS.
- Consider showing both Windows and Linux/macOS AzCopy commands side-by-side for parity.
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 provides both PowerShell and Azure CLI examples for verifying disk encryption status on Linux VMs. However, PowerShell examples are presented before Azure CLI examples, and the PowerShell section is more extensive, with detailed scripts and screenshots. This ordering and emphasis may create friction for Linux users, as PowerShell is not a native tool on most Linux distributions, whereas Azure CLI and Bash are more common. The OS-level section does use Bash commands, but platform-level validation is PowerShell-first.
Recommendations
- Present Azure CLI examples before PowerShell, as Azure CLI is more widely used and available on Linux.
- Expand Azure CLI sections to match the detail and coverage of PowerShell examples, including screenshots and explanations.
- Clearly indicate that PowerShell is optional and primarily for users who have it installed, while Azure CLI is recommended for Linux environments.
- Consider adding Bash-only or Python examples for querying Azure APIs, if relevant.
- Review and ensure parity in explanations and troubleshooting guidance for both CLI and PowerShell sections.
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 covers both Linux and Windows VM image creation with Azure Image Builder, but there is a notable Windows bias in several areas. PowerShell examples and references are frequent and often shown first, especially for checksum generation and image build operations. Windows-specific customizers (PowerShell, WindowsRestart, WindowsUpdate) are described in detail, while Linux equivalents (Shell) are less emphasized. Windows tools and patterns (e.g., Get-FileHash, Sysprep, PowerShell commands) are referenced more often than Linux tools, and Windows terminology appears before Linux in some sections.
Recommendations
- Where PowerShell examples are given for checksum generation, always provide the Linux/Mac equivalent (e.g., sha256sum) alongside or before the Windows example.
- Ensure that Linux shell customizer examples are as detailed and prominent as PowerShell customizer examples.
- When describing image build operations (start/cancel), show Azure CLI examples first or equally with PowerShell, since Azure CLI is cross-platform.
- For sections describing Windows-specific customizers (WindowsRestart, WindowsUpdate), explicitly note Linux alternatives or clarify their absence.
- Balance references to Windows tools (e.g., Get-FileHash, Sysprep) with Linux equivalents (e.g., waagent, sha256sum), and avoid assuming PowerShell as the default for cross-platform tasks.
- Consider alternating the order of Windows and Linux examples to avoid 'windows_first' bias.
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 provides examples for deploying Ultra Disks using Azure Portal, CLI, and PowerShell. However, throughout the CLI and PowerShell sections, the VM image used in all code samples is 'Win2016Datacenter', and there are no equivalent examples for Linux VM images (e.g., Ubuntu, CentOS). The Quickstart link in the Portal section also points to Windows VM creation. This creates friction for Linux users, as they must adapt the examples themselves. The documentation does state Ultra Disks apply to both Linux and Windows VMs, but practical Linux guidance is missing.
Recommendations
- Add Linux VM image examples (e.g., UbuntuLTS) alongside Windows examples in CLI and PowerShell sections.
- Provide a Quickstart link for creating a Linux VM in the Azure portal.
- Explicitly mention how to adapt the CLI/PowerShell commands for Linux VMs (e.g., changing the --image parameter).
- Ensure screenshots and portal instructions are not Windows-centric, or clarify that the steps are identical for Linux VMs.
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 (with 'AzCopy.exe' and Windows file paths), but does not offer a Linux/macOS equivalent. The AzCopy upload command is only shown for Windows, and Linux/macOS users are not given a corresponding example or guidance. Additionally, the Windows example appears before any mention of Linux usage, despite the page targeting both Linux and Windows VMs.
Recommendations
- Add an AzCopy upload example for Linux/macOS, using the 'azcopy' binary and typical Linux file paths (e.g., '/home/user/mydisk.vhd').
- Clarify that AzCopy is cross-platform and provide download/install instructions for Linux/macOS.
- Present both Windows and Linux/macOS examples side by side, or note any OS-specific syntax differences.
- Ensure that file size commands (e.g., 'wc -c', 'ls -al') are explained for both platforms, or provide Windows equivalents (e.g., 'dir').
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 Azure CLI and PowerShell examples for associating VMs to capacity reservation groups, but there is a notable Windows bias in several areas. PowerShell (a Windows-centric tool) is given equal prominence to the cross-platform Azure CLI, and in some cases, the ARM template and parameter defaults focus exclusively on Windows images. The ARM template example only covers Windows Server SKUs, and there are no explicit Linux ARM template examples. Additionally, some sections (like the ARM template) do not mention how to use a Linux image, and PowerShell is always presented as the only scripting alternative to CLI, with no mention of Bash or other Linux-native scripting approaches.
Recommendations
- Add ARM template examples for Linux VMs, or at least document how to modify the template to deploy a Linux image (e.g., Ubuntu).
- When showing parameter lists (such as OSVersion), include popular Linux distributions as allowed values, or provide a parallel Linux example.
- Consider presenting Azure CLI examples before PowerShell, as CLI is cross-platform and more accessible to Linux/macOS users.
- Where PowerShell is shown, mention that it is available cross-platform, but also suggest Bash or other Linux-native scripting approaches if relevant.
- Review the documentation for any assumptions that the user is on Windows (e.g., references to password complexity for Windows, or RDP ports), and clarify when steps are OS-agnostic or OS-specific.
Virtual Machines
Deploy a ZRS managed disk
...lob/main/articles/virtual-machines/disks-deploy-zrs.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Azure CLI (Linux/macOS-friendly) and Azure PowerShell (Windows-centric) examples for deploying ZRS managed disks. However, PowerShell examples are extensive, and some Resource Manager Template instructions rely on PowerShell commands for feature registration and deployment, with no Bash or cross-platform alternatives. Windows/PowerShell tools are mentioned first or exclusively in some sections, and the PowerShell examples use Windows VM images, while CLI examples use Ubuntu. The Azure portal instructions are platform-neutral.
Recommendations
- Add Bash or cross-platform alternatives for feature registration and ARM template deployment, especially for Linux/macOS users.
- Ensure that Resource Manager Template instructions include az CLI equivalents for feature registration and deployment.
- Balance the order of examples so that CLI (Linux/macOS) and PowerShell (Windows) are presented equally, or clarify platform applicability.
- Where possible, provide both Windows and Linux VM image examples in PowerShell sections, or clarify that PowerShell can be used for Linux VM deployments as well.
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
Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all programmatic steps, and also covers the Azure portal. However, in all CLI/PowerShell examples, the default VM image used is 'Win2016Datacenter', a Windows Server image. There are no explicit Linux VM image examples, and the variable names and instructions do not mention Linux. This creates a subtle Windows-first bias, as Linux users must know to substitute an appropriate Linux image. The use of PowerShell is not inherently biased, as Azure PowerShell is cross-platform, but the examples and context lean toward Windows usage patterns.
Recommendations
- In CLI and PowerShell examples, provide both Windows and Linux VM image examples (e.g., show 'UbuntuLTS' as an alternative to 'Win2016Datacenter').
- Explicitly mention that the VM image variable can be set to a Linux image and provide a sample value.
- Add a note or section clarifying how Linux users should adapt the examples, especially regarding authentication (e.g., SSH keys for Linux VMs instead of passwords).
- Where possible, show Linux-friendly authentication options (e.g., --authentication-type ssh for az vm create).
- Ensure that the documentation does not imply that only Windows VMs are supported or recommended.
Virtual Machines
Share an Azure Managed Disk across VMs
...cs/blob/main/articles/virtual-machines/disks-shared.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation covers both Windows and Linux usage of Azure shared disks, but Windows examples and tools (WSFC, CSV, Windows clustering, Windows-specific templates) are presented first and in greater detail. Windows clustering patterns (WSFC, CSV) are described before Linux equivalents (Pacemaker, Corosync), and Windows sample workloads are more numerous and detailed. Linux examples are present but less extensive, and Linux-specific tools/utilities are mentioned later and with less explanation.
Recommendations
- Present Linux and Windows examples in parallel, or alternate which platform is shown first in each section.
- Expand Linux sample workloads to match the detail and breadth of Windows examples (e.g., provide more Linux application templates or walkthroughs).
- Add more explicit Linux command-line examples for disk reservation and clustering (e.g., sg_persist, fence_scsi usage).
- Include links to Linux-specific documentation and templates as prominently as Windows equivalents.
- Clarify parity between Windows and Linux features and limitations, especially for clustering and disk sharing scenarios.
Virtual Machines
Enable shared disks for Azure Managed Disks
.../main/articles/virtual-machines/disks-shared-enable.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for all disk types and operations, but PowerShell (a Windows-centric tool) is given equal prominence and sometimes appears before CLI examples. There are no Linux-specific shell or tooling examples (e.g., Bash, cloud-init), and the 'Using Azure shared disks with your VMs' section only shows PowerShell for attaching disks, omitting Linux VM attachment methods. The documentation is not Windows-only, but the example tooling leans toward Windows/PowerShell, creating friction for Linux/macOS users.
Recommendations
- Add Bash or Linux-specific examples for attaching shared disks to VMs, such as using Azure CLI or cloud-init.
- Ensure Azure CLI examples are shown first or equally with PowerShell, as CLI is cross-platform.
- Include guidance or links for Linux VM disk attachment and SCSI PR command usage, referencing relevant Linux tools (e.g., sg_persist, udev).
- Clarify that PowerShell examples are for Windows users, and provide alternative steps for Linux users where applicable.
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 step-by-step instructions for enabling Write Accelerator. Azure CLI coverage is present but less detailed, and REST API instructions rely on Chocolatey and Windows-centric installation methods (cmd.exe, PowerShell), with no mention of Linux alternatives. Windows tools and patterns (e.g., Chocolatey, PowerShell) are referenced before Linux equivalents, and Linux-specific guidance is minimal or missing in scripting sections.
Recommendations
- Provide equivalent Azure CLI scripts and examples for all PowerShell scenarios, including step-by-step instructions for adding/enabling Write Accelerator disks.
- Include Linux-friendly installation instructions for armclient (e.g., via pip, npm, or manual download), and clarify how to use it on Linux/macOS.
- Ensure REST API usage examples include Linux shell commands (e.g., curl, wget) and instructions for updating VM configurations.
- Where disk/volume managers are referenced, ensure parity in guidance for Linux tools (e.g., LVM, MDADM) alongside Windows tools.
- Consider presenting Azure CLI examples before PowerShell, or side-by-side, to avoid Windows-first bias.
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 and prioritizes Windows-centric tools and workflows (notably Hyper-V and PowerShell's Convert-VHD) for VHD creation and conversion. Linux-native alternatives (such as qemu-img or VBoxManage) are not mentioned, and the only detailed VHD creation path is via Hyper-V, which is Windows-only. This may create friction for Linux/macOS users who do not have access to Hyper-V or PowerShell.
Recommendations
- Add instructions for creating and converting VHD files using Linux-native tools such as qemu-img or VBoxManage.
- Provide example workflows for preparing and converting VHDs entirely on Linux (and/or macOS) systems, including extraction, conversion, and validation steps.
- Mention Linux virtualization solutions (e.g., KVM, VirtualBox) alongside Hyper-V, and provide links to relevant documentation.
- Reorder or parallelize instructions so that Linux-native tools are presented before or alongside Windows tools, not only after.
- Clarify which steps are OS-agnostic and which are Windows-specific, to help users on non-Windows platforms navigate the process.