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 51-75 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 as the primary clustering solution when discussing shared disk limitations. All links and examples related to clustering are Windows-centric, with no mention of Linux clustering solutions (such as Pacemaker or Corosync) or their compatibility with shared disks. The proximity placement group link is also Windows-specific, and Windows terminology is used throughout.
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 where relevant.
- Clarify whether limitations (such as 'only basic disks can be used') apply to Linux clusters, or if they are Windows-specific.
- Provide parity in terminology and examples for Linux users, avoiding Windows-centric language unless the feature is Windows-only.
Create Pull Request
Virtual Machines
Run scripts in a Linux VM in Azure using managed Run Commands
...articles/virtual-machines/linux/run-command-managed.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
While the documentation is focused on Linux VMs, there is notable Windows bias in several areas: PowerShell examples and tools (e.g., Set-AzVMRunCommand, Get-AzVMRunCommand) are heavily featured alongside Azure CLI, and Windows-specific terminology and tools (such as PowerShell cmdlets and references to Windows VM behaviors) are present. REST API and ARM template examples sometimes use PowerShell script syntax (Write-Host, .ps1) even in Linux contexts. In some sections, Windows tools and patterns are mentioned before their Linux equivalents, and there are references to Windows-specific behaviors (e.g., 'Secondary Logon' service). However, Linux parity is generally maintained, and Linux-specific details are provided.
Recommendations
- Ensure REST API and ARM template examples use Linux shell script syntax (e.g., 'echo Hello World!' or '.sh' files) when the context is Linux VMs.
- Clarify in PowerShell sections which cmdlets are cross-platform and which are Windows-only; add notes for Linux users where relevant.
- Where Windows-specific tools or services are mentioned (e.g., 'Secondary Logon'), clearly indicate their irrelevance for Linux users.
- Consider showing Azure CLI examples before PowerShell examples, as CLI is more platform-neutral and widely used for Linux.
- Review all example scripts and ensure Linux shell script (.sh) syntax is used for Linux VM scenarios.
- Add explicit Linux-focused troubleshooting steps and examples where possible.
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 both Azure CLI and PowerShell examples for deploying and managing Ultra Disks, but all VM creation examples use Windows images (e.g., Win2016Datacenter) and reference Windows-specific quickstarts. There are no Linux VM image examples or Linux-specific guidance, despite the feature supporting both Linux and Windows VMs. This creates friction for Linux users, who must adapt the instructions themselves.
Recommendations
- Add Linux VM image examples (e.g., Ubuntu, CentOS) alongside Windows examples in all CLI and PowerShell sections.
- Reference Linux VM quickstart documentation in the portal section, not just Windows.
- Explicitly note any differences or considerations for Linux VMs, such as disk partitioning and formatting steps.
- Ensure that CLI and PowerShell scripts are generic or provide both Windows and Linux variants where relevant.
Virtual Machines
Create and upload an Ubuntu Linux VHD in Azure
...rticles/virtual-machines/linux/create-upload-ubuntu.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation, while focused on Ubuntu Linux, repeatedly references and prioritizes Windows/Hyper-V tooling (e.g., Hyper-V Manager, Convert-VHD PowerShell cmdlet) for VHD creation and conversion. Instructions for creating and converting VHDs are Windows-centric, with no Linux-native alternatives provided. Linux users are left without guidance for performing critical steps (such as converting disk formats) using Linux tools.
Recommendations
- Add instructions for creating and converting VHD files using Linux-native tools (e.g., qemu-img, VBoxManage) alongside or in place of Hyper-V/PowerShell steps.
- Mention Linux virtualization solutions (e.g., KVM, VirtualBox) as alternatives to Hyper-V for VHD creation.
- Provide Linux command-line examples for extracting, converting, and preparing VHDs, not just referencing Windows tools.
- Reorder sections or clearly separate Windows-specific and Linux-specific instructions to avoid implying Windows is required.
Virtual Machines
Customer intent: "As a cloud architect, I want to develop a robust backup and disaster recovery strategy for my Azure VMs and their managed disks, so that my organization can ensure data availability and minimize downtime during outages or data loss incidents."
...s/backup-and-disaster-recovery-for-azure-iaas-disks.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation covers backup and disaster recovery strategies for Azure Managed Disks on both Linux and Windows VMs. While most guidance is platform-neutral, there are instances where Windows tools and patterns (such as Volume Shadow Service and SQL Server Always On) are mentioned first or exclusively, with Linux equivalents (like fsfreeze) referenced later and with less detail. The SQL Server backup section is Windows-centric, and application-consistent backup guidance is more detailed for Windows than Linux.
Recommendations
- Provide equal detail for Linux backup coordination tools (e.g., expand on fsfreeze, mention LVM snapshots, or other Linux-native solutions for application-consistent backups).
- Include examples or links for Linux database backup and disaster recovery (e.g., Oracle, PostgreSQL, MySQL) alongside SQL Server.
- When mentioning Windows tools (like Volume Shadow Service), immediately follow with Linux equivalents and clarify their limitations or differences.
- Add links to Linux-specific documentation for backup and disaster recovery of common workloads.
- Ensure parity in guidance for both OS types in tables and comparison sections.
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
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
While the documentation covers both Windows and Linux VMs, there are several signs of Windows bias: PowerShell examples are always present and often detailed, ARM template and parameter defaults are Windows-centric, and Windows tools and patterns (like PowerShell and Windows image SKUs) are emphasized. Linux-specific details and parity in examples are lacking, especially in ARM templates and parameterization.
Recommendations
- In ARM template examples, provide both Windows and Linux image options, or show how to parameterize for either OS.
- When listing allowed values for parameters like OSVersion, include common Linux distributions (e.g., Ubuntu, CentOS) alongside Windows.
- In PowerShell sections, clarify that PowerShell Core (pwsh) is cross-platform, or provide Bash/Cloud Shell alternatives where possible.
- Ensure CLI examples use both Windows and Linux images (not just Ubuntu in CLI and Windows in ARM).
- Add explicit notes or tabs for Linux-specific considerations or differences, if any.
- Balance the order of examples so that CLI (cross-platform) is shown before PowerShell, or alternate the order.
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 (a Windows-centric tool) is heavily featured, especially in the Resource Manager Template section and for feature registration. Windows/PowerShell examples are shown before Linux equivalents in some sections, and PowerShell commands are used for ARM template deployment and feature registration without Linux/bash alternatives. The CLI examples use Ubuntu images, but the PowerShell examples default to Windows images, and the registration steps are only shown in PowerShell.
Recommendations
- Add bash or Azure CLI equivalents for feature registration and ARM template deployment steps.
- Ensure that Linux/CLI examples are presented before or alongside Windows/PowerShell examples in each section.
- Provide PowerShell examples using Linux VM images, or clarify that PowerShell can be used cross-platform.
- Explicitly mention that Azure CLI works on Linux/macOS and provide instructions for those platforms.
- Add links or notes about using Azure Cloud Shell, which supports both Bash and PowerShell.
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
Powershell Heavy
Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for all major steps, but the CLI examples consistently use Windows-centric defaults (e.g., Win2016Datacenter as the VM image, password authentication, and variable syntax). There are no explicit Linux-specific examples (such as using a Linux VM image or SSH authentication), and PowerShell is given equal prominence to Azure CLI, which may not be as relevant for Linux/macOS users. The documentation does not provide any Bash scripting or Linux-native command-line patterns, and all variable examples and VM creation scripts default to Windows VMs.
Recommendations
- Add explicit Linux VM deployment examples in the Azure CLI sections (e.g., use Ubuntu or CentOS images, SSH authentication).
- Clarify that Azure CLI commands are cross-platform and provide Bash-friendly variable syntax where appropriate.
- Include at least one end-to-end example for deploying and attaching a Premium SSD v2 disk to a Linux VM.
- In the PowerShell sections, clarify that these are primarily for Windows users, and recommend Azure CLI for Linux/macOS users.
- In the 'Next steps' section, ensure Linux and Windows parity in links and instructions.
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 parity between Azure CLI and PowerShell for all disk operations, but PowerShell examples are heavily featured and often shown before CLI examples. PowerShell is a Windows-centric tool, while Azure CLI is cross-platform. There are no Linux-specific examples or guidance, and PowerShell is referenced as a primary scripting option, which may create friction for Linux/macOS users.
Recommendations
- Show Azure CLI examples before PowerShell examples, as CLI is cross-platform and preferred for Linux/macOS users.
- Add explicit notes clarifying that Azure CLI is fully supported on Linux/macOS and is the recommended option for non-Windows users.
- Include sample bash scripts or Linux shell usage where relevant (e.g., mounting disks, interacting with SCSI PR commands).
- Consider adding links or references to Linux-specific disk management guidance, especially for clustered applications.
- Reduce PowerShell-centric language and ensure CLI instructions are equally prominent.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides extensive Azure PowerShell examples and scripts for enabling Write Accelerator, with detailed step-by-step instructions and code. Azure CLI is covered, but with much less detail and fewer examples. The REST API section requires installation of 'armclient' via Chocolatey, a Windows-only package manager, and installation instructions are only for Windows (cmd.exe/PowerShell). There are no Linux-specific installation instructions for 'armclient', nor is there mention of Linux package managers or alternatives. Windows tools and patterns (PowerShell, Chocolatey) are mentioned exclusively or before Linux equivalents. However, the feature itself is cross-platform (Linux and Windows VMs), and Azure CLI and REST API methods are documented, so Linux users can complete the task with some friction.
Recommendations
- Provide parity in example detail for Azure CLI, including full scripts for common scenarios (adding/enabling/disabling Write Accelerator disks).
- For REST API/armclient, include installation instructions for Linux (e.g., via dotnet, manual download, or Linux package managers if available), or mention cross-platform alternatives.
- Clarify that PowerShell examples are usable on Linux via Azure PowerShell (if true), or provide Bash/CLI equivalents.
- Mention that Chocolatey is Windows-only and provide alternative installation methods for Linux/macOS users.
- Where possible, show CLI examples before or alongside PowerShell to avoid Windows-first bias.
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 PowerShell and Azure CLI examples for creating encrypted image versions with customer-managed keys. However, the PowerShell example is presented first and in greater detail, and PowerShell is a Windows-centric tool. There is no explicit Bash or Linux shell scripting example, though Azure CLI is cross-platform. References to enabling customer-managed keys and double encryption in the prerequisites section link to PowerShell guides before CLI or Bash equivalents. There are no Linux-specific tools or workflows highlighted.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and more accessible to Linux/macOS users.
- Add explicit Bash or shell scripting examples where possible, especially for automation scenarios.
- Ensure that all prerequisite links include Azure CLI or Bash-based guides, not just PowerShell.
- Clarify in the introduction that both Windows and Linux users can follow the CLI and Portal instructions equally.
- Where PowerShell is referenced, note that it is available cross-platform, or provide a direct link to Azure CLI/Bash alternatives.
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 as a scenario for shared disks, linking to Windows-specific clustering requirements. There are no equivalent mentions or links for Linux clustering solutions (such as Pacemaker, Corosync, or other Linux HA stacks). The proximity placement group link is also Windows-specific, and Windows clustering is mentioned before any Linux alternatives, suggesting a Windows-first bias.
Recommendations
- Add references and links to Linux-based clustering solutions (e.g., Pacemaker, Corosync) and their compatibility with Azure shared disks.
- Clarify whether shared disks are supported for Linux-based clusters and provide any relevant limitations or guidance.
- Update proximity placement group documentation links to include Linux VM scenarios, not just Windows.
- Ensure examples and limitations are presented for both Windows and Linux environments where applicable.
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 command is shown only in Windows syntax, and there is no mention of how to run AzCopy on Linux or macOS, nor are Linux file paths or shell usage demonstrated. The rest of the CLI examples are cross-platform, but the critical upload step is Windows-biased.
Recommendations
- Add AzCopy command examples for Linux/macOS, using './azcopy' and typical Linux file paths (e.g., '/home/user/mydisk.vhd').
- Clarify that AzCopy is available for Linux/macOS and provide download/install instructions or a link for those platforms.
- Mention that the AzCopy syntax is the same across platforms, but file paths and executable names differ.
- Consider showing both Windows and Linux/macOS examples side-by-side for the upload step.
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 Tools
Windows First
Summary
The documentation page, while focused on Linux VM disk encryption, presents PowerShell examples and tools prominently and extensively, often before or alongside Azure CLI and Linux-native commands. PowerShell is a Windows-centric tool, and its heavy usage may create friction for Linux users. The Azure CLI and OS-level Linux commands are provided, but PowerShell sections are longer, more detailed, and appear before CLI in several cases.
Recommendations
- Move Azure CLI examples before PowerShell examples, as CLI is more native to Linux environments.
- Reduce the prominence and length of PowerShell sections, or clearly mark them as optional for users who prefer PowerShell.
- Expand Linux OS-level command examples (e.g., using bash, lsblk, cryptsetup) to cover more verification scenarios.
- Add a short note clarifying that PowerShell is optional and that Azure CLI is recommended for Linux users.
- Where possible, provide parity in detail and output examples for Azure CLI and Linux commands, matching those given for PowerShell.
Virtual Machines
Create an Azure Image Builder Bicep file or ARM template JSON template
.../articles/virtual-machines/linux/image-builder-json.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides both Windows and Linux examples for Azure Image Builder, but there is a notable Windows bias. PowerShell commands and Windows-specific tools (e.g., Get-FileHash) are frequently mentioned, often before their Linux equivalents. Windows customizers (PowerShell, WindowsRestart, WindowsUpdate) are described in detail, while Linux customizers (Shell) are covered but less emphasized. Some sections (e.g., restart customizer) explicitly state there is no Linux equivalent. SHA256 checksum generation is shown with PowerShell first, then Linux. In validation examples, Windows/PowerShell is presented before Linux/Shell. The documentation is usable for Linux users, but Windows patterns and tools are more prominent.
Recommendations
- Ensure Linux examples and tools (e.g., sha256sum, wget/curl) are presented alongside or before Windows equivalents.
- Provide more detailed Linux-specific customizer examples, including common patterns for Linux image customization.
- Balance the order of examples so that Linux and Windows are equally represented, or alternate which comes first.
- Where a feature is Windows-only (e.g., WindowsRestart customizer), explicitly state alternatives or workarounds for Linux users.
- Include links to Linux troubleshooting and scripting resources, similar to Windows/PowerShell links.
Virtual Machines
Run scripts in a Linux VM in Azure using managed Run Commands
...articles/virtual-machines/linux/run-command-managed.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation is focused on running scripts in Azure Linux VMs, but it exhibits several Windows biases. PowerShell examples and tools (e.g., Set-AzVMRunCommand, Get-AzVMRunCommand, New-AzStorageBlobSASToken) are heavily featured and often presented before or alongside Azure CLI examples. Some explanations and sample scripts reference Windows-specific concepts (e.g., 'ipconfig', 'myscript.ps1', 'Secondary Logon' service) without clear Linux equivalents or clarification. REST API and ARM template examples use Windows-style scripts (PowerShell) and file extensions (.ps1) instead of Linux shell scripts (.sh), and there are missing Linux-specific examples for certain advanced scenarios (e.g., parameter passing, blob streaming, sequential execution).
Recommendations
- Provide Linux shell script (.sh) examples in REST API and ARM template sections instead of or alongside PowerShell (.ps1) scripts.
- Clarify when a command or parameter is Windows-only, and offer Linux equivalents where possible (e.g., replace 'ipconfig' with 'ifconfig' or 'ip a' for Linux).
- Use Linux tools and patterns (e.g., az CLI, bash scripting, Linux file extensions) as the default or primary examples, especially since the page is Linux-focused.
- Add explicit Linux-focused walkthroughs for advanced scenarios (e.g., streaming output to blobs, parameter passing, running as a different user) using Azure CLI and bash.
- Ensure terminology and instructions are Linux-centric (e.g., referencing Linux user management, not Windows services like 'Secondary Logon').
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 for VM creation and disk attachment (e.g., 'Win2016Datacenter' as the VM image in CLI and PowerShell commands). There are no explicit Linux VM image examples or Linux-specific guidance, despite the article stating applicability to Linux VMs. This creates friction for Linux users, who must infer the necessary changes for their environment.
Recommendations
- Provide parallel examples for Linux VM creation and disk attachment, using a Linux image (e.g., 'UbuntuLTS' or 'CentOS') in CLI and PowerShell commands.
- Explicitly mention how to adapt commands for Linux VMs, including authentication options (e.g., SSH keys instead of passwords).
- Add a note or section clarifying any OS-specific considerations for Ultra Disks, such as filesystem formatting or disk partitioning steps for Linux.
- Ensure that all code snippets and instructions are equally applicable to both Linux and Windows, or provide separate tabs/examples for each.
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
Missing Linux Example
Summary
The documentation lists Azure PowerShell before Linux-native tools (Azure CLI), and provides a direct link to a Windows rescan function, but only a generic link for Linux. There are no explicit Linux shell/command examples, and the rescan process for Linux is less detailed than for Windows.
Recommendations
- Provide explicit Linux shell command examples for rescanning disks (e.g., using 'echo 1 > /sys/class/block/<device>/device/rescan' or 'lsblk').
- List Azure CLI (cross-platform) before Azure PowerShell to avoid Windows-first impression.
- Include parity in detail for both Linux and Windows rescan steps, possibly with example commands and expected outputs.
- Clarify that both Azure CLI and PowerShell are cross-platform, but highlight native Linux tools 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 AzCopy example ('AzCopy.exe copy "c:\somewhere\mydisk.vhd" "sas-URI" --blob-type PageBlob') and does not show a Linux/macOS equivalent. The AzCopy command is given only in Windows syntax, and the Windows path is used. While the rest of the CLI instructions are cross-platform, the upload step is biased toward Windows users, potentially confusing Linux/macOS users who need to use AzCopy differently.
Recommendations
- Add a Linux/macOS AzCopy example, e.g., '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 the AzCopy command syntax and path format differ between Windows and Linux/macOS.
- Consider showing both Windows and Linux/macOS AzCopy commands side-by-side.
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 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 detailed, with multiple scenarios and screenshots. This ordering and emphasis may create friction for Linux users, as PowerShell is not a native tool on Linux and Azure CLI is more commonly used in Linux environments. The OS-level section does provide Linux-native commands, but platform-level validation is PowerShell-first.
Recommendations
- Present Azure CLI examples before PowerShell, as Azure CLI is the default cross-platform tool and more relevant for Linux users.
- Ensure Azure CLI coverage is as detailed as PowerShell, including all scenarios and screenshots.
- Clearly indicate that PowerShell is optional and primarily for users who prefer it, not required for Linux VM management.
- Add explicit guidance for Linux users on installing and using Azure CLI if not already present.
- Consider grouping PowerShell and Azure CLI examples together, or providing tabs for each tool, to avoid implicit prioritization.
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 covers both Linux and Windows VM image creation with Azure Image Builder, and provides parity for most features and examples. However, there is a notable Windows bias in several areas: PowerShell is frequently referenced for checksum generation and operational commands, Windows-specific customizers (PowerShell, WindowsRestart, WindowsUpdate) are described in detail, and Windows tools (e.g., PowerShell cmdlets) are often mentioned before or instead of Linux equivalents. While Linux examples and shell customizers are present, instructions for generating checksums and some operational steps (e.g., validation, generalization) prioritize Windows/PowerShell. Windows customizer types are more numerous and described in greater detail than Linux equivalents.
Recommendations
- Provide Linux/macOS equivalents for all PowerShell commands, especially for checksum generation (e.g., always mention 'sha256sum' alongside 'Get-FileHash').
- Ensure Linux shell customizer examples are as detailed as Windows PowerShell examples, including advanced usage (e.g., error handling, exit codes).
- When listing customizer types, avoid listing Windows types first unless there is a technical reason; alternate or group by OS.
- For operational steps (e.g., starting/cancelling builds), ensure Azure CLI examples are shown before or alongside PowerShell, and clarify CLI works cross-platform.
- Where Windows-only customizers exist (e.g., WindowsRestart, WindowsUpdate), explicitly state Linux alternatives or limitations.
- Expand Linux validation examples to match the detail of Windows validation (e.g., show advanced shell validation scenarios).
Virtual Machines
Run scripts in a Linux VM in Azure using managed Run Commands
...articles/virtual-machines/linux/run-command-managed.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
Although the page is focused on Linux VMs, there is notable Windows bias in several areas. PowerShell examples and tooling (e.g., Set-AzVMRunCommand, Get-AzVMRunCommand) are presented extensively, sometimes before or alongside Azure CLI examples. Windows-specific tools and patterns (such as PowerShell scripts, SAS token generation via PowerShell, and REST/ARM template examples referencing .ps1 scripts) are used without Linux/bash equivalents. Some explanations and examples reference Windows behaviors or tools (e.g., 'ipconfig' as a commandId, referencing Windows VM usage, and script examples using Write-Host or .ps1 files), and there are missing Linux/bash script examples in REST and ARM template sections.
Recommendations
- Ensure REST API and ARM template script examples use Linux/bash scripts (e.g., .sh files, echo/ls/id commands) instead of PowerShell/.ps1.
- Where PowerShell tooling is referenced, provide equivalent Azure CLI or bash examples for Linux users, especially for SAS token generation and blob operations.
- Clarify when a command or parameter is Windows-specific (e.g., 'ipconfig' commandId) and provide Linux alternatives (e.g., 'ifconfig', 'ip').
- In sections describing parameter passing, show explicit Linux/bash script examples and clarify differences in script invocation.
- Avoid referencing Windows VM behaviors (e.g., 'Secondary Logon' service) unless necessary, and clearly separate Linux and Windows instructions.
- Present Azure CLI examples before PowerShell, as CLI is more cross-platform and native for Linux users.
Virtual Machines
Associate a virtual machine to a capacity reservation group
.../virtual-machines/capacity-reservation-associate-vm.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Summary
The documentation covers both Windows and Linux VMs in its scope and provides Azure CLI, PowerShell, Portal, API, and ARM template instructions. However, there are signs of Windows bias: ARM template and some examples default to Windows images, and PowerShell is given equal prominence to CLI (which is cross-platform), but there are no explicit Bash or Linux shell script examples. The ARM template only shows Windows image configuration, and password-based admin setup is described, which is more common for Windows VMs. Linux-specific details (e.g., SSH keys, Linux image references) are missing in ARM and Portal steps.
Recommendations
- Add explicit Linux ARM template examples, including a Linux image reference and SSH key authentication.
- In the ARM template, provide a parameter or example for a Linux image (e.g., Ubuntu) and show how to configure SSH authentication.
- In the Portal steps, mention SSH key setup for Linux VMs, not just username/password.
- Where PowerShell is shown, clarify that Azure CLI is cross-platform and can be used on Linux/macOS, and consider adding Bash script examples for common tasks.
- Ensure that examples and screenshots (if any) alternate or show parity between Windows and Linux VM creation and management.
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 extensive, use Windows-specific patterns (e.g., ConvertTo-SecureString, System.Management.Automation.PSCredential), and are presented immediately after the Azure CLI section. Resource Manager Template examples are also shown using PowerShell commands for deployment, rather than cross-platform CLI or ARM template JSON. The 'Next steps' section links to a PowerShell-focused sample repository. There is no explicit Linux/macOS bias, but Windows/PowerShell tools and patterns are featured heavily and often first.
Recommendations
- Add explicit Linux/macOS guidance for running Azure CLI commands, including notes about shell differences and SSH key generation.
- Provide Resource Manager Template deployment examples using Azure CLI (az deployment group create) instead of only PowerShell.
- Clarify that PowerShell examples are for Windows users, and suggest cross-platform alternatives for Linux/macOS users.
- Link to cross-platform sample repositories or documentation in 'Next steps', not only PowerShell-focused resources.
- Consider balancing the order of examples so that CLI and PowerShell are presented equally, or alternate which comes first.
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 provides both Azure CLI and PowerShell options for configuring the NetworkAccessPolicy, but references to PowerShell and Windows-centric links appear first and more prominently. The custom RBAC role section links only to a PowerShell-based guide, potentially creating friction for Linux/macOS users. However, CLI options are mentioned for some tasks, and the feature itself is not Windows-specific.
Recommendations
- Add links and examples for creating custom RBAC roles using Azure CLI and/or Azure Portal, not just PowerShell.
- Ensure CLI and PowerShell options are presented equally, ideally side-by-side or with CLI first for cross-platform parity.
- Where possible, provide Linux/macOS-specific guidance or clarify that CLI commands work across platforms.