Virtual Machines
2112
Total Pages
1865
Linux-Friendly Pages
247
Pages with Bias
11.7%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
818 issues found
Showing 101-125 of 818 flagged pages
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/snapshot-copy-managed-disk.md
...rticles/virtual-machines/snapshot-copy-managed-disk.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Linux Example Last
Summary
The documentation presents Windows/PowerShell examples and references before Linux/CLI equivalents in both the main instructions and the 'Next steps' section. PowerShell (a Windows-centric tool) is given prominence, and links to further examples for Windows are listed before Linux. There is also a slight emphasis on Windows tools and workflows.
Recommendations
- Present Azure CLI (cross-platform) examples before or alongside PowerShell examples to avoid Windows-first ordering.
- Ensure that 'Next steps' and further reading links for Linux are listed with equal prominence and before or alongside Windows links.
- Explicitly mention that Azure CLI commands work on both Linux and Windows to reinforce cross-platform parity.
- Where possible, add Bash or Linux shell-specific notes or troubleshooting steps, especially if there are differences.
- Review language to ensure it does not implicitly prioritize Windows tools or workflows over Linux equivalents.
Create Pull Request
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/ssh-keys-portal.md
...blob/main/articles/virtual-machines/ssh-keys-portal.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page provides only a PowerShell example for connecting to the VM, without mentioning or showing equivalent Linux/macOS terminal commands. The only explicit example for using SSH is shown in a PowerShell context, and the phrase 'open a PowerShell prompt' is used, which prioritizes Windows users. There are no Linux-specific instructions or screenshots, and the only reference to Linux is in the context of the VMs, not the client environment.
Recommendations
- Provide explicit Linux/macOS terminal examples alongside the PowerShell example, e.g., 'Open a terminal (Linux/macOS) or PowerShell (Windows) and type: ...'.
- Use more neutral language such as 'Open a terminal' instead of 'Open a PowerShell prompt', or clarify both options for different operating systems.
- Include screenshots or instructions that are relevant to Linux/macOS users where appropriate.
- Ensure that links to further documentation (e.g., 'Use SSH keys to connect to Linux VMs') include Linux client instructions, or add a direct section here.
- Consider adding a table or callout box that shows the SSH command usage on Windows (PowerShell), Linux, and macOS for parity.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/trusted-launch-existing-vm-gen-1.md
...s/virtual-machines/trusted-launch-existing-vm-gen-1.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several areas: Windows tools and patterns (such as MBR2GPT.exe, BitLocker, and PowerShell) are mentioned first or exclusively, with Linux equivalents either missing, less detailed, or referenced after Windows. The PowerShell and Windows-specific instructions are more comprehensive, while Linux instructions are less detailed and sometimes defer to external registration or validation steps. There are also sections where only Windows troubleshooting steps are provided, and Linux-specific upgrade scenarios are less supported or described.
Recommendations
- Provide equally detailed Linux instructions for disk layout conversion (MBR to GPT and EFI partition creation), including common commands and troubleshooting steps for popular distributions.
- Include Linux-specific troubleshooting sections similar to the Windows 'Known issues' (e.g., handling EFI partition issues, common errors during upgrade).
- When listing prerequisites or best practices, avoid mentioning Windows tools (e.g., BitLocker, Defrag) first or exclusively; instead, provide Linux equivalents or parallel guidance.
- In the 'Update Guest OS volume' section, add step-by-step instructions for converting MBR to GPT and adding EFI partitions on Linux, not just validation steps.
- Balance the use of PowerShell and CLI examples by providing Bash shell scripts or commands for Linux users where appropriate.
- Ensure that all sections referencing Windows tools or patterns (e.g., MBR2GPT.exe, Defrag, BitLocker) also mention or link to Linux alternatives (e.g., gdisk, parted, cryptsetup/LUKS).
- Add more Linux-focused examples and clarify support for distributions beyond the Azure Marketplace images, or provide guidance for custom images.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/trusted-launch-existing-vmss.md
...icles/virtual-machines/trusted-launch-existing-vmss.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation exhibits a Windows bias in several ways: Windows-based OS images (e.g., '2022-datacenter-azure-edition') are used as the default and only example in ARM template, CLI, and PowerShell code blocks. The ARM template quickstart link points to a Windows-specific template. PowerShell is heavily featured, and the CLI/PowerShell examples use Windows image SKUs without showing Linux equivalents. The Guest Attestation extension section lists both Windows and Linux publishers, but no Linux-specific example is provided. There are no explicit Linux OS image examples or instructions for enabling Trusted Launch on Linux-based scale sets.
Recommendations
- Provide parallel examples using Linux OS images (e.g., Ubuntu, RHEL) in all code snippets (ARM template, CLI, PowerShell) alongside or alternating with Windows examples.
- Include links to Linux-specific ARM template quickstarts, not just Windows.
- In the Guest Attestation extension section, show explicit examples for both Windows and Linux extension publishers.
- Clarify in each section that Trusted Launch is supported for both Windows and Linux, and highlight any Linux-specific considerations.
- Ensure that CLI and PowerShell examples use both Windows and Linux image SKUs, or alternate between them.
- Review and update screenshots and portal instructions to reflect Linux scenarios where applicable.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/virtual-machine-scale-sets-maintenance-control.md
...ines/virtual-machine-scale-sets-maintenance-control.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing PowerShell (a Windows-centric tool) in both the management options list and the 'Next steps' section, where only the PowerShell guide is directly linked. There are no explicit Linux/Unix shell examples or references, and the Azure CLI (which is cross-platform and more common on Linux) is listed after PowerShell. No Linux-specific guidance or parity is provided.
Recommendations
- Provide equal prominence to Azure CLI examples and documentation, especially in the 'Next steps' section (e.g., link to both PowerShell and CLI guides).
- Include explicit Linux/Unix shell examples or references where relevant.
- Consider listing Azure CLI before PowerShell in management options to reflect cross-platform parity.
- Add a note clarifying that all features are available via CLI on Linux and macOS, not just PowerShell on Windows.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/virtual-machines-create-restore-points.md
...ual-machines/virtual-machines-create-restore-points.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows-first bias by describing application consistency in detail for Windows (mentioning VSS writers) before Linux (which is only briefly referenced as using pre- and postscripts). Windows-specific tools (VSS) are mentioned explicitly, while Linux equivalents are not named or explained. There are no concrete examples or guidance for Linux users, and no Linux-specific tools or scripts are referenced.
Recommendations
- Provide equal detail for Linux application consistency, including naming common tools (e.g., fsfreeze, custom scripts) and describing their use.
- Include explicit Linux examples or references, such as sample pre- and post-scripts for achieving application consistency.
- Reorder or parallelize explanations so that Linux and Windows approaches are presented with equal prominence and detail.
- Link to Linux-specific documentation or resources for configuring application-consistent backups.
Virtual Machines
Create and upload an Ubuntu Linux VHD in Azure
...rticles/virtual-machines/linux/create-upload-ubuntu.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page, while focused on Ubuntu Linux VHD creation for Azure, exhibits Windows bias in several areas. Hyper-V (a Windows-only virtualization tool) is mentioned as the primary example for creating VHDs, and PowerShell's Convert-VHD cmdlet is referenced for disk conversion without providing Linux alternatives. Steps involving Hyper-V Manager are described in detail, but equivalent instructions for Linux-based virtualization tools (like qemu-img or VirtualBox) are missing. Windows extraction instructions are given (via WSL), but Linux-native extraction is not explicitly described. This bias may create friction for Linux/macOS users who do not have access to Windows tools.
Recommendations
- Add Linux-native instructions for creating and converting VHDs (e.g., using qemu-img or VBoxManage).
- Provide extraction steps for prebuilt images directly on Linux/macOS, not just via WSL on Windows.
- Include guidance for Linux-based virtualization platforms (such as KVM, VirtualBox, or QEMU) alongside Hyper-V.
- Reference Linux/macOS tools for disk conversion and management, and clarify which steps are platform-specific.
- Reorder sections so Linux-native approaches are presented first or in parallel with Windows-specific instructions.
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides detailed PowerShell examples for resizing Azure VMs, including scripts for both standalone VMs and those in availability sets. PowerShell is a Windows-centric tool, and its examples are more extensive and appear before Azure CLI and Terraform. The Terraform section references Windows VM quickstart code, and the CLI examples use Bash, but PowerShell is presented as the primary scripting method. There is no explicit Linux example (e.g., Bash or shell script) for resizing VMs outside of Azure CLI, and Windows tools/patterns are mentioned first and more thoroughly.
Recommendations
- Add parity between PowerShell and Azure CLI examples by providing equally detailed Bash/shell scripts for Linux/macOS users.
- In the Terraform section, reference both Windows and Linux VM quickstart code, not just Windows.
- Reorder sections so that Azure CLI (cross-platform) is presented before PowerShell.
- Explicitly mention that Azure CLI works on Linux/macOS and provide guidance for those environments.
- Where PowerShell is used, clarify that it is available on Linux/macOS, but provide Bash alternatives for common tasks.
Virtual Machines
Create a VM from a generalized image in a gallery
...icles/virtual-machines/vm-generalized-image-version.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for creating VMs from generalized images in a gallery. However, PowerShell examples are heavily focused on Windows-specific patterns (e.g., Set-AzVMOperatingSystem -Windows), and Windows VM creation is shown first or exclusively in several PowerShell sections. CLI examples generally default to Linux, but PowerShell sections do not offer Linux-specific instructions or parity. Additionally, PowerShell is a Windows-centric tool, and its usage is prominent throughout the page.
Recommendations
- Add explicit Linux VM creation examples in PowerShell sections, using Set-AzVMOperatingSystem -Linux.
- Clarify in PowerShell sections how to create Linux VMs, including SSH key authentication and Linux-specific configuration.
- Where possible, provide Bash or shell script equivalents for resource setup (network, NIC, etc.) for Linux users.
- Ensure that both CLI and PowerShell sections consistently mention Linux and Windows options, rather than defaulting to Windows in PowerShell.
- Consider adding a note that PowerShell is cross-platform, but highlight any Windows-specific limitations or patterns.
Virtual Machines
Deploy a Trusted Launch VM
...ain/articles/virtual-machines/trusted-launch-portal.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Linux and Windows guidance for deploying Trusted Launch VMs, but PowerShell examples are exclusively for Windows, and Windows is often the default in PowerShell and some template sections. CLI examples are Linux-focused, but PowerShell sections do not show Linux VM creation, and Windows images are used by default. In some multi-OS sections, Windows is shown first or exclusively in PowerShell, which may create friction for Linux users who prefer or require scripting via PowerShell.
Recommendations
- Add PowerShell examples for deploying Linux Trusted Launch VMs, including using Linux images and parameters.
- In PowerShell sections, provide both Linux and Windows variants, or clearly indicate that PowerShell is Windows-focused and recommend Azure CLI for Linux users.
- When showing multi-OS template or scripting examples, alternate the order or provide parallel Linux and Windows examples in each section.
- In PowerShell code, use Linux images and parameters where appropriate, or provide a toggle/tab for Linux/Windows.
- Explicitly mention in PowerShell sections that Linux users should use Azure CLI if PowerShell support is limited.
Virtual Machines
Create a VM from a specialized image version
...icles/virtual-machines/vm-specialized-image-version.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for creating VMs from specialized images, but the PowerShell examples are significantly more detailed and complex, including full network setup and VM configuration. CLI examples are simpler and less comprehensive. PowerShell is a Windows-centric tool, and its prominence may create friction for Linux/macOS users. Additionally, PowerShell examples are often presented immediately after CLI, which is a more cross-platform tool, but the CLI examples are less thorough.
Recommendations
- Expand Azure CLI examples to include full VM/network configuration steps, matching the detail level of PowerShell examples.
- Explicitly note that Azure CLI is cross-platform and recommend it for Linux/macOS users.
- Consider including Bash shell scripting examples for Linux users where appropriate.
- Ensure that all critical workflows shown in PowerShell are also available in CLI, with equivalent detail.
- Add a brief section clarifying tool parity and platform recommendations for users.
Virtual Machines
Create a VM from a generalized image in a gallery
...icles/virtual-machines/vm-generalized-image-version.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides both Azure CLI and PowerShell examples for creating VMs from generalized images in a gallery. However, PowerShell examples are heavily Windows-centric, with explicit use of Windows-only parameters (e.g., Set-AzVMOperatingSystem -Windows), and the full parameter set is demonstrated only for Windows VMs. Windows-specific networking rules (e.g., RDP port 3389) are configured by default, and password complexity requirements link to Windows documentation. In several sections, Windows VM creation is shown before or instead of Linux, and PowerShell examples do not show Linux VM creation or configuration.
Recommendations
- Add PowerShell examples for creating Linux VMs, including the use of Set-AzVMOperatingSystem -Linux and relevant Linux configuration options.
- In PowerShell sections, provide both Windows and Linux VM creation flows, or clarify when examples are Windows-only.
- When showing networking rules, include SSH (port 22) alongside RDP (port 3389) and clarify their relevance for Linux and Windows VMs.
- Ensure password complexity requirements reference both Windows and Linux documentation, or clarify differences.
- Where examples are given, alternate the order of Windows and Linux examples, or present both together for parity.
Virtual Machines
Create a VM from a specialized image version
...icles/virtual-machines/vm-specialized-image-version.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for creating VMs from specialized images, but the PowerShell examples are extensive and detailed, while the CLI examples are more concise. The PowerShell examples use Windows-centric tools and patterns (e.g., New-AzNetworkSecurityRuleConfig for RDP port 3389, Windows-style variable naming, and PowerShell-specific networking setup). There are no Linux shell (bash) or macOS-specific examples for tasks like networking setup, nor are there explicit Linux-focused CLI walkthroughs. PowerShell examples are given equal or greater prominence than CLI, which may create friction for Linux/macOS users who do not use PowerShell.
Recommendations
- Add detailed bash shell examples for networking and VM creation, matching the depth of the PowerShell walkthroughs.
- Ensure CLI examples cover all steps shown in PowerShell (e.g., network interface, NSG creation), not just the VM creation command.
- Clarify that PowerShell examples are primarily for Windows users, and provide parity for Linux/macOS users with bash/CLI scripts.
- Where possible, use cross-platform terminology and avoid Windows-centric patterns (e.g., RDP port blocking) unless relevant to both OS types.
Virtual Machines
Enable Trusted launch on existing Gen2 VMs
...rticles/virtual-machines/trusted-launch-existing-vm.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides parity for both Linux and Windows VMs in terms of feature applicability and mentions SSH for Linux and RDP for Windows. However, there is a notable bias in the scripting and automation sections: PowerShell is given a dedicated section, and ARM template deployment examples use PowerShell commands exclusively for deployment (e.g., New-AzResourceGroupDeployment), with no Bash or cross-platform CLI alternatives. In the 'Best practices' section, Linux-specific validation is mentioned, but in the main automation workflows, Windows/PowerShell tools are prioritized or exclusively shown. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer Bash/Azure CLI.
Recommendations
- Add Bash/Azure CLI examples for ARM template deployment (e.g., using az deployment group create) alongside PowerShell.
- Where PowerShell is used for automation, provide equivalent Bash or cross-platform CLI commands.
- In sections where PowerShell is shown first or exclusively, clarify that cross-platform alternatives exist and link to relevant documentation.
- Consider adding a short note or table summarizing which tools are cross-platform and which are Windows-only, to help users choose the best option for their OS.
Virtual Machines
Create a VM from a generalized image in a gallery
...icles/virtual-machines/vm-generalized-image-version.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides both Azure CLI and PowerShell examples for creating VMs from generalized images, but PowerShell examples are heavily Windows-centric, with explicit use of Windows-specific parameters (e.g., Set-AzVMOperatingSystem -Windows) and RDP-related network security rules. In several PowerShell code blocks, only Windows VM creation is shown, with no Linux equivalent. Additionally, in PowerShell sections, Windows configuration is presented first and exclusively, while CLI examples are more Linux-focused. REST and Portal instructions do cover both OS types, but PowerShell users on Linux/macOS are left without clear guidance.
Recommendations
- Add PowerShell examples for creating Linux VMs, using Set-AzVMOperatingSystem -Linux and relevant SSH configuration.
- In PowerShell sections, provide both Windows and Linux VM creation code blocks, or clarify how to adapt the examples for Linux.
- When showing network security rules, include SSH (port 22) examples alongside RDP (port 3389) for Linux scenarios.
- Explicitly note PowerShell cross-platform support and any differences for Linux/macOS users.
- Ensure parity in example coverage and ordering between Windows and Linux across all tooling sections.
Virtual Machines
Enable Trusted launch on existing Gen2 VMs
...rticles/virtual-machines/trusted-launch-existing-vm.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides instructions for enabling Trusted launch on Azure Gen2 VMs using multiple methods (Portal, CLI, PowerShell, ARM template). While the feature applies to both Linux and Windows VMs, there is a notable bias toward Windows tools and patterns: PowerShell is given equal prominence to CLI, and ARM template examples use PowerShell for deployment. In several places, PowerShell is used for actions that could be performed with cross-platform tools. Additionally, PowerShell is referenced before CLI in some sections, and the use of RDP (Windows) is mentioned before SSH (Linux) when verifying VM access.
Recommendations
- Provide Bash (or cross-platform) examples for ARM template deployment, not just PowerShell.
- When referencing remote access, list SSH (Linux) before RDP (Windows) or mention both equally.
- Ensure CLI and PowerShell examples are presented with equal prominence, or clarify that PowerShell is not required for Linux/macOS users.
- Where possible, use cross-platform tools (e.g., Azure CLI) in examples and deployment steps.
- Add explicit notes for Linux/macOS users about how to perform steps without PowerShell.
Virtual Machines
Create a VM from a specialized image version
...icles/virtual-machines/vm-specialized-image-version.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for all major workflows, but the PowerShell examples are significantly more detailed, including full network and VM configuration steps, while the CLI examples are minimal. PowerShell is a Windows-centric tool, and the CLI is cross-platform. Additionally, PowerShell examples are presented immediately after CLI examples, which is a common pattern but may reinforce Windows-first perceptions. There are no Linux/macOS-specific shell examples (e.g., Bash), and no explicit mention of Linux-specific considerations, but the CLI examples are suitable for Linux/macOS users.
Recommendations
- Expand CLI examples to include full VM and network configuration steps, matching the detail of PowerShell examples.
- Explicitly state that Azure CLI commands are cross-platform and suitable for Linux/macOS users.
- Consider providing Bash script examples for Linux users, especially for more complex workflows.
- Ensure parity in example detail and guidance between CLI and PowerShell sections.
- Add notes or links for Linux/macOS users about prerequisites or environment setup if relevant.
Virtual Machines
Create a VM from a specialized image version
...icles/virtual-machines/vm-specialized-image-version.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for creating VMs from specialized images, but the PowerShell examples are significantly more detailed and complex, including full networking setup and resource creation, while the CLI examples are minimal. PowerShell is a Windows-centric tool, and the lack of parity in CLI examples may disadvantage Linux/macOS users. Additionally, PowerShell examples are presented before CLI in some sections, and there are no Bash or Linux-native scripting examples for tasks like networking setup.
Recommendations
- Expand Azure CLI examples to include full resource setup (networking, NSG, NIC, etc.), matching the detail of PowerShell examples.
- Add Bash shell script examples for Linux/macOS users, especially for multi-step VM deployments.
- Ensure CLI examples are presented before or alongside PowerShell examples to avoid Windows-first impression.
- Explicitly mention that all CLI commands work on Linux/macOS and provide troubleshooting tips for non-Windows platforms.
Virtual Machines
Create a VM from a generalized image in a gallery
...icles/virtual-machines/vm-generalized-image-version.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides both CLI and PowerShell examples for creating VMs from generalized images in an Azure Compute Gallery. However, PowerShell examples are heavily focused on Windows-specific patterns (e.g., Set-AzVMOperatingSystem -Windows, Get-Credential for username/password), and the full parameter set for PowerShell only shows Windows VM creation. Windows-specific networking rules (RDP port 3389) are configured by default in PowerShell examples. While CLI examples default to Linux VM creation (with SSH keys), PowerShell examples default to Windows VM creation and do not show Linux VM creation or SSH key usage. REST and Portal instructions do show both Linux and Windows, but PowerShell coverage is notably Windows-centric.
Recommendations
- Add PowerShell examples for creating Linux VMs, including usage of SSH keys and Set-AzVMOperatingSystem -Linux.
- Show how to configure Linux-specific network security rules (e.g., SSH port 22) in PowerShell examples.
- Balance the order of examples so that Linux and Windows are equally represented, or clarify when an example is Windows-specific.
- In PowerShell sections, explicitly mention how to adapt commands for Linux VMs, including credential handling and OS configuration.
Virtual Machines
Create and upload a CentOS-based Linux VHD
...rticles/virtual-machines/linux/create-upload-centos.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page for creating and uploading a CentOS-based Linux VHD demonstrates a moderate Windows bias. It consistently references Hyper-V (a Windows virtualization tool) as the primary or sole example for creating VHDs, provides step-by-step instructions using Hyper-V Manager, and links to Windows-specific guides. While it mentions alternatives like VirtualBox and KVM, detailed instructions and examples for these Linux-native tools are missing. This creates friction for Linux/macOS users who may not have access to Hyper-V and need guidance for their platforms.
Recommendations
- Add detailed instructions and examples for creating and preparing VHDs using Linux-native tools such as qemu-img, KVM, and VirtualBox.
- Provide parity in step-by-step guidance for Linux and macOS users, including how to convert disk formats and manage VM lifecycle without Hyper-V.
- Include links to relevant Linux documentation and official guides for virtualization and disk preparation.
- Reorder sections so Linux-native tools are presented before or alongside Hyper-V, or clarify that Hyper-V is just one option.
Virtual Machines
Deploy a VM or Virtual Machine Scale Set with MSP
...tual-machines/metadata-security-protocol/greenfield.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by highlighting a Windows-specific feature (GuestProxyAgent enabled from ARM template) and explicitly noting that Linux requires a more complex, two-step process, but does not provide Linux-specific instructions or examples. All configuration and API examples are generic or Windows-named, with no Linux parity guidance.
Recommendations
- Add explicit Linux deployment instructions, detailing the two-step process required for enabling GuestProxyAgent on Linux VMs.
- Provide Linux-specific ARM template and REST API examples, including any necessary post-provisioning steps.
- Clarify any differences in validation or troubleshooting for Linux VMs.
- Ensure example resource names are not Windows-centric (e.g., 'GPAWinVM').
Virtual Machines
Move resources associated with a maintenance configuration to another region
...nes/move-region-maintenance-configuration-resources.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples are given first and in greater detail, with variable definitions using PowerShell syntax. The main migration step links to a Windows-specific tutorial (toc/breadcrumb paths reference Windows), and PowerShell-specific error handling is described. While Azure CLI examples are present, the overall flow and examples favor Windows/PowerShell users, and Linux/macOS users may need to adapt instructions.
Recommendations
- Provide variable definition examples in Bash syntax alongside PowerShell.
- Ensure migration tutorial links use platform-neutral or Linux/macOS-specific TOC/breadcrumb paths.
- Describe error handling for CLI commands, not just PowerShell.
- Explicitly mention that CLI commands work on Linux/macOS and provide Bash copy-paste examples.
- Balance the order of examples: show CLI (cross-platform) first, then PowerShell.
- Add notes or sections for Linux/macOS users where workflows or commands may differ.
Virtual Machines
Azure VM Extensions and Features for Linux
...articles/virtual-machines/extensions/features-linux.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
Although the documentation is focused on Linux VM extensions, it consistently presents both Azure CLI and Azure PowerShell examples side-by-side, with PowerShell examples given equal prominence. PowerShell is a Windows-centric tool, and its inclusion throughout may create friction for Linux/macOS users. Additionally, references to ARM templates link to Windows documentation first, and some terminology (such as 'publisher', 'extension type') is not clarified for Linux users. However, Linux-specific details (such as waagent, log locations, and Bash scripts) are present and correct.
Recommendations
- Prioritize Azure CLI examples over PowerShell, as CLI is cross-platform and native to Linux/macOS.
- Clearly indicate that PowerShell is optional and primarily for Windows users; consider moving PowerShell examples to a secondary section or appendix.
- Ensure ARM template links point to Linux-specific documentation when possible.
- Add explicit notes about tool availability and platform compatibility for each example.
- Review terminology to ensure it is clear for Linux users and not Windows-centric.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
All CLI examples use the Windows Server image ('Win2022DataCenter') and do not mention or provide examples for Linux VM images. There is no discussion of Linux-specific considerations, nor are Linux images (such as Ubuntu or CentOS) shown in any command. This creates a bias towards Windows usage and may cause confusion or friction for Linux users.
Recommendations
- Provide equivalent CLI examples using popular Linux images (e.g., '--image UbuntuLTS', '--image CentOS').
- Add a note clarifying that MSP is supported for both Windows and Linux VMs, if applicable.
- Mention any Linux-specific configuration steps or caveats, if they exist.
- Alternate examples between Windows and Linux, or show both side-by-side.
Virtual Machines
Metadata Security Protocol (MSP)
...irtual-machines/metadata-security-protocol/overview.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation lists Windows operating systems first in compatibility, and provides a warning that Windows users can enable GuestProxyAgent (GPA) directly from an ARM template, while Linux users must perform a two-step process. However, there are no Linux-specific instructions or examples provided, and no mention of Linux tooling or commands. This creates friction for Linux users who may need more guidance for the additional steps.
Recommendations
- Add explicit step-by-step instructions for enabling GPA on Linux, including any required commands or configuration files.
- Provide Linux-specific examples and tooling references (e.g., shell commands, systemd integration) alongside Windows/ARM template examples.
- List supported operating systems in alphabetical order or group by platform to avoid implicit prioritization.
- Clarify any differences in process between Windows and Linux with equal detail for both.