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 51-75 of 818 flagged pages
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Windows and Linux parity in terms of instructions and code samples, but there is a subtle Windows bias. Windows is mentioned first in quickstart links, screenshots, and examples. PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, but no Linux-native shell examples (e.g., Bash) are provided. Screenshots and validation steps consistently show Windows first, and PowerShell is presented as a main automation method, which may not be as familiar to Linux users.
Recommendations
- Alternate the order of Windows and Linux references, so Linux is sometimes mentioned first.
- Add Bash shell examples alongside PowerShell for Linux users, especially for automation tasks.
- Ensure screenshots and walkthroughs alternate or equally represent Linux and Windows environments.
- Explicitly state that PowerShell is cross-platform, or provide links to Linux-native equivalents where appropriate.
- Highlight Linux-specific considerations or troubleshooting steps, if any, to ensure parity.
Create Pull Request
Virtual Machines
Use infrastructure automation tools
...articles/virtual-machines/infrastructure-automation.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation generally covers both Linux and Windows automation tools, but there are several areas where Windows examples, tools, or instructions are presented before or instead of Linux equivalents. Some sections (Chef, Puppet) provide only or primarily Windows-focused links, and in others (Azure Resource Manager template, Azure Automation) Windows examples are listed before Linux ones. There is also a tendency to mention Windows-specific tools (PowerShell DSC) more prominently, with Linux support as a secondary note.
Recommendations
- Ensure that examples and instructions for Linux are provided alongside Windows, especially for tools like Chef and Puppet.
- Present Linux and Windows examples in parallel or alternate order to avoid implicit prioritization.
- Where Windows-specific tools are discussed (e.g., PowerShell DSC), highlight Linux equivalents (e.g., cloud-init) with equal prominence.
- Add links to Linux-focused documentation for Chef and Puppet, not just Windows install guides.
- Review the ordering of examples and links to avoid listing Windows first by default, especially in sections like Azure Resource Manager template and Azure Automation.
- Explicitly state Linux support and provide Linux-specific instructions for all tools where applicable.
Virtual Machines
Create and upload an Oracle Linux VHD
...les/virtual-machines/linux/oracle-create-upload-vhd.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a Windows bias by consistently referencing Hyper-V (a Windows virtualization tool) as the primary example for creating VHDs, providing links to Windows-centric instructions, and using Hyper-V Manager for VM management steps. There are no examples or instructions for equivalent Linux-based tools (such as KVM, qemu-img, or VirtualBox) for creating or managing VHDs, nor are Linux workflows mentioned for converting or uploading VHDs. The steps for preparing the Oracle Linux VM are presented in the context of Hyper-V, with no Linux-native alternatives provided.
Recommendations
- Add examples and instructions for creating and managing VHDs using Linux-native tools such as KVM, qemu-img, or VirtualBox.
- Include Linux command-line workflows for converting disk formats (e.g., using qemu-img to convert raw disks to fixed VHD).
- Provide guidance for managing and shutting down VMs using Linux virtualization platforms (e.g., virsh, virt-manager) alongside Hyper-V instructions.
- Reference documentation or tutorials for installing and configuring Oracle Linux VMs on Linux hosts, not just Windows/Hyper-V.
- Ensure parity in tool recommendations and example order, presenting Linux options before or alongside Windows tools.
Virtual Machines
Manage Virtual Machine restore points
...ain/articles/virtual-machines/manage-restore-points.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page exclusively provides Azure PowerShell examples for managing VM restore points, without any equivalent examples for Linux users (e.g., Azure CLI, Bash, or REST API usage). Windows-centric tools and patterns are presented first and solely, which may disadvantage users on Linux or macOS platforms.
Recommendations
- Add Azure CLI examples for all PowerShell commands, demonstrating equivalent operations for Linux/macOS users.
- Include REST API sample requests and responses where relevant, to provide platform-neutral guidance.
- Explicitly mention cross-platform options (PowerShell, CLI, REST) at the start of each procedural section.
- Where scripts are shown, provide both PowerShell and Bash/CLI versions side-by-side.
- Clarify that the steps can be performed on any OS using appropriate tools, not just Windows.
Virtual Machines
Export an image version to a managed disk
...es/virtual-machines/managed-disk-from-image-version.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for exporting an image version to a managed disk. However, the PowerShell section is extensive and uses Windows-centric tooling (PowerShell cmdlets), which are primarily used on Windows. There is no mention of Bash or Linux shell scripting, nor are Linux-specific tools or patterns discussed. The PowerShell section is detailed and appears after the CLI section, but the CLI examples use syntax compatible with both Windows and Linux, while the PowerShell examples are exclusively Windows-oriented.
Recommendations
- Add explicit Bash examples for Linux users, showing variable assignment and command usage in a Linux shell.
- Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and provide notes or examples for common Linux shell environments.
- Consider including Linux-specific troubleshooting tips or notes about environment differences (e.g., quoting, environment variables).
- Balance the depth of PowerShell and CLI sections, ensuring Linux users have equally detailed guidance.
- If possible, mention cross-platform alternatives to PowerShell for scripting these operations.
Virtual Machines
Specify Marketplace purchase plan information using Azure PowerShell
...b/main/articles/virtual-machines/marketplace-images.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily focused on Azure PowerShell, with all command-line examples using PowerShell cmdlets and no equivalent Azure CLI or Bash examples provided. The referenced links and examples (such as network security rules for RDP port 3389) are Windows-centric, and Linux-specific scenarios are not demonstrated, despite the documentation claiming applicability to Linux VMs. There is no mention of Linux tools, shell commands, or patterns, and the ARM template example uses a Windows VM name and RDP port, further reinforcing a Windows-first bias.
Recommendations
- Add equivalent Azure CLI and Bash examples for all PowerShell commands, especially for Linux users.
- Include Linux-specific scenarios, such as SSH port configuration and Linux VM naming conventions, in both code and ARM template examples.
- Reference documentation and examples that are platform-neutral or provide both Windows and Linux paths (e.g., links to Linux-focused image finding guides).
- Explicitly show how to retrieve and use purchase plan information for Linux VMs, including relevant differences.
- Avoid using Windows-specific ports (like 3389 for RDP) in generic examples; use SSH (port 22) for Linux or provide both.
Virtual Machines
Advanced Configuration for MSP
...s/metadata-security-protocol/advanced-configuration.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation provides a detailed example for a Windows process (WinPA) with explicit Windows paths and process names, while the Linux example is less prominent and not as detailed. Windows-specific tools and patterns (e.g., C:\Windows\OEM\Unattend.wsf.exe, SYSTEM user) are mentioned, but there is no equivalent Linux example for common Linux provisioning agents or system users. The Windows example appears before any Linux-specific example, and there is a lack of parity in showcasing Linux tools or patterns.
Recommendations
- Add a Linux-focused example for a common provisioning agent (e.g., cloud-init) with typical Linux paths, process names, and users/groups.
- Ensure that examples for both Windows and Linux are presented with equal prominence and detail.
- Mention Linux system users (e.g., root) and common Linux agent processes in the same context as Windows examples.
- Where Windows-specific tools or patterns are referenced, provide the Linux equivalents alongside.
- Consider alternating the order of Windows and Linux examples to avoid implicit prioritization.
Virtual Machines
Azure Dedicated Host SKU Retirement Migration Guide
...l-machines/migration/dedicated-host-migration-guide.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides migration instructions for Azure Dedicated Host SKUs, but consistently lists PowerShell (a Windows-centric tool) before CLI options and does not mention Linux-specific tools or workflows. There are no examples for Bash, Linux shell scripts, or references to Linux admin patterns. The CLI instructions are present, but PowerShell is always listed first, and there is no explicit guidance for Linux users.
Recommendations
- Alternate the order of PowerShell and CLI instructions, or list CLI first to avoid Windows-first bias.
- Include Bash or Linux shell script examples for common operations (e.g., stopping/starting VMs, managing scale sets).
- Explicitly mention that the Azure CLI is cross-platform and provide Linux-specific usage notes or troubleshooting tips.
- Add references to Linux admin documentation or best practices for migration.
- Clarify that PowerShell examples are primarily for Windows users, and provide parity for Linux users where possible.
Virtual Machines
Migrate Managed image to Compute gallery
...igration/migration-managed-image-to-compute-gallery.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page provides both Azure CLI and PowerShell examples for migrating managed images to Azure Compute Gallery, but the PowerShell example is given equal prominence despite PowerShell being a Windows-centric tool. The CLI example uses Azure CLI, which is cross-platform, but there is no explicit mention or example of Linux shell usage (e.g., bash), nor guidance for Linux-specific environments. The presence of PowerShell and lack of Linux shell examples or notes may indicate a subtle Windows bias.
Recommendations
- Add explicit bash shell examples for Azure CLI commands, showing usage in Linux environments.
- Clarify that Azure CLI commands can be run on Linux, macOS, and Windows, and provide any Linux-specific notes (e.g., environment variables, authentication differences).
- If PowerShell is shown, consider also showing bash/zsh equivalents for parity.
- Mention cross-platform compatibility in the prerequisites and tool selection guidance.
- Ensure screenshots and UI instructions do not assume Windows unless necessary; add notes for Linux users where relevant.
Virtual Machines
NV series migration guide
...-machines/migration/sizes/nv-series-migration-guide.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates Windows bias by exclusively referencing Windows guest OS support for NVv4 VMs, linking only to Windows-specific driver setup guides and extensions, and omitting Linux migration steps, driver installation instructions, or Linux-specific considerations. Linux tools, patterns, or examples are not mentioned, and Windows is presented as the default or only supported platform for key VM series and migration actions.
Recommendations
- Add explicit Linux migration instructions, including driver installation and removal steps for supported VM series.
- Provide links to Linux-specific GPU driver setup guides and extension documentation where available.
- Clarify OS support for each VM series, including any limitations or future plans for Linux support.
- Include Linux command-line examples (e.g., Bash, Azure CLI) alongside or before Windows/Powershell examples.
- Mention Linux tools and patterns for GPU workload management and migration, ensuring parity with Windows guidance.
Virtual Machines
Move a maintenance configuration to another Azure region
...tual-machines/move-region-maintenance-configuration.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by repeatedly referencing PowerShell as a primary tool for creating, assigning, and deleting maintenance configurations, alongside Azure CLI. No Linux-specific shell examples (e.g., Bash) are provided, and PowerShell is mentioned before CLI in each step, suggesting a Windows-first approach. There are no explicit Linux command-line examples or guidance tailored to Linux users.
Recommendations
- Provide Bash shell examples for each step, especially for creating, assigning, and deleting maintenance configurations using Azure CLI.
- Mention CLI before PowerShell, or present both options equally, to avoid implying PowerShell is the preferred or default method.
- Clarify that all CLI commands work natively on Linux and macOS, and provide any necessary notes for Linux users (e.g., environment variable syntax differences).
- Include explicit instructions or links for Linux users on installing and using Azure CLI.
- Review linked articles to ensure Linux parity in examples and instructions.
Virtual Machines
Use a VHD snapshot to create multiple identical managed disks (Windows) - PowerShell
...al-machines-powershell-sample-create-snapshot-from-vhd.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exclusively provides PowerShell-based instructions and examples for Windows environments. There are no references to Linux tools, Bash, or CLI equivalents, and the content is explicitly targeted at Windows users. All sample scripts, next steps, and additional resources focus solely on Windows and PowerShell, omitting Linux parity.
Recommendations
- Add equivalent Bash or Azure CLI examples for Linux users.
- Include references to Linux VM documentation and script samples.
- Provide guidance for performing the same tasks on Linux, including any differences in workflow or tooling.
- Clearly indicate cross-platform support and limitations, if any.
- Reorganize content to present both Windows and Linux options in parallel, rather than focusing exclusively on Windows.
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page generally covers both Windows and Linux VMs, but there are several instances of Windows bias. Windows tools (PowerShell) are mentioned before Linux equivalents (CLI), especially in the Key Vault section. Some features, such as Microsoft Antimalware, are described with a Windows focus and lack Linux alternatives or examples. In several places, Windows terminology and tools are introduced first, and Linux examples are sometimes missing or referenced secondarily.
Recommendations
- Ensure that Linux tools (e.g., Azure CLI) are mentioned alongside or before Windows tools (PowerShell) when describing procedures.
- Provide explicit Linux examples and command snippets wherever Windows examples are given.
- Where features are Windows-only (e.g., Microsoft Antimalware), suggest Linux alternatives or clarify Linux security recommendations.
- Balance references to documentation links so that Linux and Windows guides are equally visible and accessible.
- Use neutral language when introducing cross-platform features, avoiding Windows-first ordering.
Virtual Machines
Set up Azure HPC or AI VMs
.../blob/main/articles/virtual-machines/set-up-hpc-vms.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates mild Windows bias. While it references both Linux and Windows quickstarts and driver installation guides, Windows examples and links are often listed before Linux equivalents (e.g., in the driver installation section). There is a lack of Linux-specific examples for AMD GPU drivers, and some instructions (such as SSH key generation and download) use patterns more common in Windows-centric workflows. Additionally, the page references connecting via SSH from Windows, but does not mention Linux-native tools or workflows in detail.
Recommendations
- Ensure Linux and Windows examples are presented in parallel, with equal detail and prominence.
- Add Linux-specific instructions for AMD GPU driver installation, matching the detail provided for Windows.
- When listing links or instructions, alternate the order (Linux first in some sections, Windows first in others) or present both together.
- Include Linux-native tooling and workflows (e.g., mention using ssh-keygen on Linux, or connecting via terminal) where relevant.
- Review all examples and ensure that Linux users have clear, step-by-step guidance matching Windows parity.
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. In the 'Feature support' section, nested virtualization is linked only to the Windows/Hyper-V documentation, with no mention of Linux/KVM equivalents. In the 'Network' section, bandwidth/throughput testing references NTTTCP, a Microsoft/Windows-centric tool, without mentioning Linux alternatives. There are no command-line examples, but where tooling or guides are referenced, Windows is prioritized or Linux is omitted.
Recommendations
- Add references to Linux/KVM nested virtualization documentation alongside the Windows/Hyper-V link.
- Mention Linux network testing tools (e.g., iperf, netperf) in addition to NTTTCP for bandwidth/throughput testing.
- Where features/tools are OS-specific, clarify applicability for both Windows and Linux, and provide parity in documentation links.
- Consider including example commands or usage patterns for both Windows (PowerShell/NTTTCP) and Linux (bash/iperf) where relevant.
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. Windows-specific features and tools (such as Hyper-V nested virtualization and NTTTCP for bandwidth testing) are mentioned or linked before or exclusively, with Linux equivalents either omitted or referenced only as 'Linux or Windows' without detail. There are no Linux-specific examples, tools, or optimization guidance, and the only Linux mention is in the context of unsupported disk encryption.
Recommendations
- Include Linux-specific examples and tools for performance testing (e.g., mention 'iperf' or 'fio' alongside NTTTCP).
- Provide links to Linux nested virtualization documentation (e.g., KVM or QEMU) in addition to Hyper-V.
- Add guidance or optimization tips for Linux VMs, similar to those provided for Windows.
- Ensure parity in feature support tables by listing both Linux and Windows features, and clarify any differences.
- Where features/tools are Windows-specific, explicitly state Linux alternatives or note their absence.
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page shows mild Windows bias. References to Windows technologies (e.g., Hyper-V nested virtualization, NTTTCP for bandwidth testing) are present, and Windows is mentioned before Linux in some feature lists and optimization notes. There are no explicit Linux command examples or Linux-specific tools highlighted, and some features/tools (like NTTTCP) are Windows-centric without Linux alternatives or parity guidance.
Recommendations
- Add Linux-specific examples and tools where Windows tools are mentioned (e.g., include Linux equivalents for NTTTCP, such as iperf or netperf).
- When listing features or optimization guidance, alternate or balance the order of Windows and Linux mentions, or group them together to avoid Windows-first impression.
- Provide links to Linux documentation and troubleshooting guides alongside Windows ones, especially for features like nested virtualization or disk encryption.
- Explicitly note Linux support and best practices for performance optimization, not just Windows.
- Ensure that any referenced tools or patterns (such as NVMe support, disk encryption, network testing) include Linux usage instructions or alternatives.
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias. It references Windows-specific technologies (such as Hyper-V nested virtualization and NTTTCP for bandwidth testing) and links to Windows documentation before or instead of Linux equivalents. There are no Linux-specific examples or tools mentioned for virtualization or network testing, and some features are described with a Windows-first perspective (e.g., nested virtualization). Linux support is mentioned only in the context of restrictions or lack of support (e.g., Azure Disk Encryption for Linux VMs: Not Supported), rather than providing positive Linux guidance or parity.
Recommendations
- Include Linux-specific examples and tools for network testing (e.g., iperf, netperf) alongside NTTTCP.
- Reference Linux virtualization documentation (e.g., KVM nested virtualization) in addition to or before Windows Hyper-V.
- Provide positive Linux guidance and feature parity notes, not just restrictions.
- Ensure that feature support tables and resource links mention both Windows and Linux options equally.
- Add links to Linux-focused documentation for VM optimization and performance testing.
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias. References to Windows-specific features (e.g., nested virtualization linking to Hyper-V on Windows) and tools (NTTTCP for bandwidth testing, which is a Windows tool) are present. Windows features are mentioned before Linux equivalents in some cases, and there are no explicit Linux command examples or Linux-specific tooling mentioned. While the page states applicability to both Linux and Windows VMs, practical guidance and links favor Windows environments.
Recommendations
- Include Linux-specific examples and links where Windows tools are referenced (e.g., mention Linux alternatives to NTTTCP such as iperf or netperf for bandwidth testing).
- When referencing virtualization features, provide parity by linking to Linux nested virtualization documentation or clarifying Linux support status.
- Ensure that feature support tables and notes mention both Linux and Windows equivalently, and avoid listing Windows features or tools first unless there is a technical reason.
- Add Linux command-line examples (e.g., using Azure CLI or Linux disk/network benchmarking tools) alongside any Windows/PowerShell examples.
- Review linked resources to ensure Linux documentation is referenced where available, not just Windows-centric guides.
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias. It references Windows-specific technologies (e.g., nested virtualization links to Hyper-V on Windows), and in the networking section, bandwidth/throughput testing is described using NTTTCP, a tool primarily associated with Windows. There are no explicit Linux or cross-platform command examples, and Windows tools/patterns are mentioned before or instead of Linux equivalents. No Linux-specific guidance or parity is provided for features like nested virtualization or performance testing.
Recommendations
- Include Linux equivalents or cross-platform alternatives for referenced tools (e.g., mention 'iperf' or 'netperf' for bandwidth testing alongside NTTTCP).
- Provide links to Linux documentation for nested virtualization (e.g., KVM or other supported hypervisors on Azure).
- Add explicit Linux command-line examples or references where applicable, especially in sections discussing optimization, performance testing, or feature support.
- Ensure that documentation for features (such as network optimization or disk performance) includes both Windows and Linux guidance, or clarifies platform-specific differences.
- Review all external links to ensure Linux parity and add Linux-focused resources where missing.
Virtual Machines
Use Azure Spot Virtual Machines
...e-docs/blob/main/articles/virtual-machines/spot-vms.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation generally maintains cross-platform language, but there is evidence of Windows bias. PowerShell is mentioned explicitly in the 'Next steps' section, with a direct link to Windows/PowerShell instructions, while Linux CLI and ARM template links are grouped separately. The order of presentation in 'Next steps' places CLI (Linux), portal, ARM template (Linux), and then PowerShell (Windows), which is more balanced, but the explicit mention of PowerShell and the existence of a dedicated Windows/PowerShell page, without a similar dedicated Bash or Linux shell page, suggests a slight bias. There are no explicit Linux shell command examples or screenshots, and some references (such as scheduled events) link to Linux documentation but do not provide in-page Linux-specific examples. No Windows-only tools are promoted, but Linux parity in examples and tooling is not fully achieved.
Recommendations
- Add explicit Linux shell (Bash) command examples for common Spot VM operations, similar to the PowerShell examples.
- Provide dedicated Linux/Bash documentation pages, analogous to the Windows/PowerShell page.
- Include screenshots or walkthroughs for Linux users in the portal and CLI sections.
- Ensure that all references to tooling (CLI, ARM, PowerShell) are presented with equal prominence and detail.
- Where possible, provide side-by-side examples for both Windows (PowerShell) and Linux (Bash/CLI) in relevant sections.
Virtual Machines
Create SSH keys in the Azure portal
...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 exhibits Windows bias by providing only a PowerShell example for connecting to the VM, without any Linux or macOS terminal equivalents. The instructions for using SSH keys locally assume a Windows environment, and the only explicit command-line example is shown in a PowerShell context. There are no Linux shell (bash) or macOS Terminal instructions, nor is there mention of Linux-specific SSH client usage or file permissions (e.g., chmod). References to further documentation also point to 'ssh-from-windows.md', reinforcing a Windows-first perspective.
Recommendations
- Add Linux and macOS terminal examples for connecting to the VM using SSH, such as using bash/zsh.
- Include notes on setting appropriate file permissions for the private key (e.g., 'chmod 600 mySSHKey.pem') on Linux/macOS.
- Provide parity in instructions for moving and storing the SSH key on Linux/macOS systems.
- Reference documentation that covers both Windows and Linux workflows, or split links to OS-specific guides.
- Avoid presenting Windows/Powershell examples exclusively or before Linux equivalents; instead, show both side-by-side or in parallel sections.
Virtual Machines
Enable Trusted launch on existing Uniform scale set
...icles/virtual-machines/trusted-launch-existing-vmss.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page exhibits a Windows bias in several areas: Windows OS images are used as the primary example in ARM templates, CLI, and PowerShell sections; Linux-specific examples and instructions are missing or only referenced in passing (e.g., extension publisher names); PowerShell is given equal or greater prominence compared to CLI, and Windows tooling and patterns (such as WindowsServer images and PowerShell commands) are presented before or instead of Linux equivalents.
Recommendations
- Provide explicit Linux examples alongside Windows examples in all code blocks (ARM template, CLI, PowerShell), including Linux image references and SKU values.
- Add instructions and sample commands for enabling Trusted launch on Linux-based scale sets, including any Linux-specific considerations (e.g., custom kernels, unsigned drivers).
- In ARM template and CLI sections, alternate or parallelize Windows and Linux examples, rather than defaulting to Windows first.
- Clarify extension publisher usage by showing full Linux extension configuration, not just a table.
- Ensure parity in troubleshooting, validation, and rollback steps for Linux scale sets.
- Review screenshots and portal instructions to confirm they are applicable to both Windows and Linux, or provide Linux-specific visuals where needed.
Virtual Machines
Overview of Maintenance control for OS image upgrades on Azure Virtual Machine Scale Sets
...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 bias towards Windows by prioritizing PowerShell in both the management options list and the 'Next steps' section. PowerShell, a Windows-centric tool, is mentioned first, and the only direct example link provided is for PowerShell. There are no explicit Linux-specific examples or references to Bash or Linux-native tools, and Azure CLI (which is cross-platform and commonly used on Linux) is listed after PowerShell and not highlighted in the 'Next steps'.
Recommendations
- Provide equal prominence to Azure CLI examples, especially in the 'Next steps' section, as CLI is widely used on Linux.
- Include explicit Bash/Linux shell examples or links to Linux-specific documentation where relevant.
- Alternate the order of management options or clarify that both PowerShell and CLI are supported equally across platforms.
- Add a note or section highlighting cross-platform compatibility and usage scenarios for Linux administrators.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/linux/use-remote-desktop.md
.../articles/virtual-machines/linux/use-remote-desktop.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation is generally Linux-focused but exhibits Windows bias in several areas: Windows and PowerShell examples for Azure network security group (NSG) rules are provided before Linux equivalents, and Windows-specific tools and patterns (such as PowerShell and references to using SSH from Windows) are mentioned prominently. There is also a tendency to reference Windows workflows (e.g., using the Azure portal, PowerShell) alongside or before Linux-native approaches.
Recommendations
- Present Linux/Azure CLI examples before Windows/PowerShell examples, especially in sections about Azure resource management.
- Clearly separate Windows-specific guidance (such as PowerShell commands or SSH from Windows) into optional or 'additional information' sections, rather than interleaving them with core Linux instructions.
- Add parity by including Linux-native tools and workflows for all steps, and ensure that Linux examples are primary and complete.
- Where Windows tools or patterns are referenced (e.g., Azure PowerShell), provide equivalent Linux-native alternatives (e.g., Bash scripts, Azure CLI) first.
- Review and adjust the order of instructions and references so that Linux users are not required to sift through Windows-specific content to find relevant information.