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 376-400 of 815 flagged pages
Virtual Machines
Enable Azure Disk Encryption for Linux VMs
...les/virtual-machines/linux/disk-encryption-overview.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation is focused on Linux VMs, with all technical guidance, examples, and requirements tailored to Linux distributions and tools. However, there is minor evidence of Windows bias: PowerShell is mentioned alongside Azure CLI as a management tool, and PowerShell quickstart links are presented equally with CLI links. The 'Terminology' section includes 'PowerShell cmdlets' as a defined term, even though the primary audience is Linux users. Azure PowerShell is a cross-platform tool, but its inclusion may create confusion for Linux users unfamiliar with PowerShell.
Recommendations
- Clarify that Azure PowerShell is available and supported on Linux/macOS, not just Windows.
- Consider prioritizing Azure CLI examples and quickstarts, as CLI is more native to Linux environments.
- In the 'Terminology' section, explain the cross-platform nature of Azure PowerShell or consider removing 'PowerShell cmdlets' if not essential for Linux users.
- If PowerShell scripts are referenced, ensure they are tested and documented for Linux/macOS shells (e.g., bash, zsh) and PowerShell Core.
Create Pull Request
Virtual Machines
Expand Virtual Hard Disks on a Linux VM
...b/main/articles/virtual-machines/linux/expand-disks.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Summary
The documentation is overwhelmingly Linux-focused, with detailed, distribution-specific instructions for expanding disks on Linux VMs. However, there is a single section at the end that provides a PowerShell script for checking classic VM SKU support for expanding disks without downtime, without offering a Linux CLI or Bash equivalent. This section assumes Windows tooling and does not provide parity for Linux users.
Recommendations
- Provide an Azure CLI or Bash equivalent for checking classic VM SKU support for expanding disks without downtime.
- If PowerShell is required for certain Azure operations, clarify that this is a Windows-only step and offer guidance for Linux users (e.g., using Azure CLI or REST API).
- Consider adding a note or link to relevant Linux/CLI documentation for classic VM SKU checks.
Virtual Machines
Azure Disk Encryption scenarios on Linux VMs
...ticles/virtual-machines/linux/disk-encryption-linux.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all major operations, but PowerShell (a Windows-centric tool) is often mentioned first in critical backup/encryption steps and is referenced heavily throughout. Some instructions and warnings refer to PowerShell cmdlets before CLI equivalents, and PowerShell scripts are detailed with variable initialization, while CLI examples are more concise. However, Linux parity is generally maintained, as Azure CLI is cross-platform and all tasks can be completed using CLI. No Windows-only tools or patterns are used, and Linux-specific context is clear.
Recommendations
- Ensure that Azure CLI examples are shown before PowerShell examples, especially in critical steps, to reinforce Linux-first workflows.
- Expand CLI examples to include more detailed scripting where appropriate, matching the depth of PowerShell scripts.
- Clarify that PowerShell can be used cross-platform (via PowerShell Core), but highlight Azure CLI as the primary tool for Linux users.
- Review warnings and important notes to ensure CLI commands are referenced equally or before PowerShell cmdlets.
Virtual Machines
Verify encryption status for Linux - Azure Disk Encryption
...tual-machines/linux/how-to-verify-encryption-status.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for verifying disk encryption status on Linux VMs. However, the PowerShell section is presented before the Azure CLI section, and PowerShell examples are more detailed and numerous. This creates a minor Windows bias, as PowerShell is primarily a Windows-centric tool, even though it is available cross-platform. The CLI examples are present and functional, but PowerShell receives more prominence and depth.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is the default cross-platform tool for Linux users.
- Ensure CLI and PowerShell sections have parity in detail and coverage.
- Explicitly note that PowerShell examples are for users who prefer PowerShell (including on Linux/macOS), but Azure CLI is recommended for Linux environments.
- Consider adding Bash script examples for purely OS-level checks, where relevant.
Virtual Machines
Create and upload a Red Hat Enterprise Linux VHD for use in Azure
...les/virtual-machines/linux/redhat-create-upload-vhd.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation covers preparation of Red Hat Enterprise Linux VHDs for Azure using multiple hypervisors (Hyper-V, KVM, VMware, Kickstart). While all major Linux hypervisors are included, Windows-centric tools and workflows (Hyper-V Manager, PowerShell convert-vhd cmdlet) are often mentioned first or in more detail, and some conversion instructions reference Windows tools before Linux equivalents. However, Linux-native workflows are well-documented and parity is strong overall.
Recommendations
- Where disk conversion is discussed, mention Linux-native tools (e.g., qemu-img) before or alongside Windows tools (e.g., Hyper-V Manager, convert-vhd).
- Ensure that instructions for VMware and KVM are as detailed and prominent as those for Hyper-V.
- Consider adding a summary table or section at the top that lists all supported hypervisors and their respective workflows equally, rather than starting with Hyper-V.
- Where possible, avoid language that implies Hyper-V is the default or preferred option for Linux VHD creation.
Virtual Machines
Time sync for Linux VMs in Azure
...blob/main/articles/virtual-machines/linux/time-sync.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation is focused on Linux VM time synchronization in Azure and provides comprehensive Linux-specific guidance. However, the introductory section discusses Windows Server 2016 time sync improvements and references Windows documentation before Linux-specific details. All configuration examples, tools, and commands are Linux-centric, with only a single PowerShell example for base64 encoding cloud-init data (which is relevant for Azure ARM template usage, not VM configuration). There are no missing Linux examples or Windows-only tools for the core topic.
Recommendations
- Move or minimize Windows Server 2016 discussion in the introduction, focusing first on Linux time sync context.
- Add a brief explanation for the PowerShell example, noting its relevance for Azure template preparation and suggesting a Linux equivalent (e.g., using 'base64' command).
- Ensure Linux-specific guidance is always presented before any Windows references unless Windows context is strictly necessary.
Virtual Machines
Overview of Azure Disk Storage
...in/articles/virtual-machines/managed-disks-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Minor Windows Reference
Summary
The documentation provides a balanced overview of Azure Managed Disks for both Linux and Windows VMs. However, there are minor instances where Windows-specific tools, references, or examples are mentioned first or exclusively, such as links to Windows/PowerShell guides, references to Windows drive letters, and Windows partitioning documentation. Linux equivalents are present but sometimes appear after Windows examples or are less detailed.
Recommendations
- Ensure Linux and Windows examples/tools are presented together or in parallel, rather than Windows-first.
- Where Windows-specific documentation is linked (e.g., PowerShell), provide equivalent Linux (e.g., Bash/CLI) links alongside.
- When referencing disk partitioning or file systems, include Linux documentation and examples (e.g., GPT/MBR on Linux, /dev paths, fdisk/gdisk usage).
- Clarify Linux-specific behaviors (e.g., temporary disk location, partitioning) with equal detail as Windows.
- Review all linked guides to ensure Linux parity in depth and clarity.
Virtual Machines
Create an Azure Image Builder Bicep file or ARM template JSON template
.../articles/virtual-machines/linux/image-builder-json.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation covers both Linux and Windows VM image creation with Azure Image Builder, and provides parity in most areas. However, there are several instances of Windows bias: PowerShell examples and references are often shown before Linux equivalents, Windows-specific tools (e.g., Get-FileHash, PowerShell customizer, WindowsRestart/WindowsUpdate customizers) are discussed in detail, and instructions for generating checksums or running commands frequently reference Windows/PowerShell first. Some customizers (WindowsRestart, WindowsUpdate) are Windows-only, but this is clearly documented. Linux examples are present, but sometimes appear after Windows ones or are less detailed.
Recommendations
- Ensure Linux (Shell/bash) examples are presented alongside or before Windows/PowerShell examples, especially in sections where both are supported.
- When referencing tools for tasks like generating SHA256 checksums, mention Linux/macOS commands (e.g., sha256sum) before or alongside Windows tools (e.g., Get-FileHash).
- Where possible, provide Linux-focused troubleshooting and validator examples with equal detail to Windows.
- Explicitly note when a feature or customizer is Windows-only to avoid confusion.
- Review ordering of sections and examples to avoid implicit prioritization of Windows tools and patterns.
Virtual Machines
Create a Gallery for Sharing Resources
.../blob/main/articles/virtual-machines/create-gallery.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides examples for Azure Portal, Azure CLI, PowerShell, and REST API. PowerShell examples are included alongside CLI and REST, which is a Windows-centric tool. In most sections, PowerShell is presented after CLI, but its presence may signal a Windows bias. There are no Linux-specific shell examples (e.g., Bash), but the CLI examples are cross-platform. The documentation does not mention Windows tools or patterns exclusively, nor does it omit Linux equivalents for any critical step. However, PowerShell is included as a first-class option, which may create minor friction for Linux/macOS users.
Recommendations
- Clarify that Azure CLI examples are cross-platform and suitable for Linux/macOS users.
- Consider adding Bash shell scripting examples for Linux users, especially for resource group and gallery creation.
- Explicitly state that PowerShell examples are for Windows users, and CLI is recommended for Linux/macOS.
- If possible, provide links to Linux/macOS-specific guidance or troubleshooting.
Virtual Machines
Expand Virtual Hard Disks on a Linux VM
...b/main/articles/virtual-machines/linux/expand-disks.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Summary
The documentation is highly Linux-focused, with all core examples and instructions using Linux tools and commands. However, a single section at the end provides a PowerShell script for checking classic VM SKU support, without a Linux CLI equivalent. This is a minor instance of Windows bias.
Recommendations
- Provide an Azure CLI or Bash equivalent for checking classic VM SKU support, or clarify if PowerShell is required for this specific operation.
- If PowerShell is the only option, explicitly state that this step is Windows-specific and offer guidance for Linux users (e.g., using Azure Cloud Shell or PowerShell Core).
Virtual Machines
Support matrix for VM restore points
...n/articles/virtual-machines/concepts-restore-points.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation presents Windows operating system support before Linux in the 'Operating system support for application consistency' section. However, both Windows and Linux are covered with comparable detail, and no Windows-specific tools or examples are prioritized elsewhere. The 'Next steps' section lists CLI, Portal, and PowerShell equally, without favoring Windows tools.
Recommendations
- Present Linux and Windows operating system support in parallel or alphabetical order to avoid implicit prioritization.
- Consider merging the OS support sections or using a table for parity.
- Ensure future updates include Linux-specific examples or troubleshooting if Windows-specific guidance is added.
Virtual Machines
Server-side encryption of Azure Managed Disks
...blob/main/articles/virtual-machines/disk-encryption.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation covers both Linux and Windows VM scenarios and explicitly states applicability to both. However, there is a mild bias in the ordering of examples and links: Windows/PowerShell resources are consistently mentioned before Linux/CLI equivalents throughout the page, and PowerShell is referenced in some guidance (e.g., revoking access) before CLI. No critical functionality is Windows-only, and Linux users are provided with equivalent instructions and links.
Recommendations
- Alternate the order of Windows/PowerShell and Linux/CLI links and examples, or list them together without preference.
- Where possible, provide cross-platform command examples side-by-side (PowerShell and Bash/CLI).
- Ensure references to tools (e.g., Azure Key Vault PowerShell and CLI) are presented with equal prominence.
- Review for any subtle language implying Windows as the default or primary platform.
Virtual Machines
Enable on-demand disk bursting
...ain/articles/virtual-machines/disks-enable-bursting.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides examples for enabling on-demand disk bursting using the Azure portal, PowerShell, Azure CLI, and ARM templates. The PowerShell section is prominent and detailed, and PowerShell is a Windows-centric tool. The CLI section is present and covers Linux/macOS parity, but PowerShell is mentioned before CLI. There are no Linux-specific shell examples (e.g., Bash), but Azure CLI is cross-platform. There is minor bias in the ordering and emphasis on PowerShell.
Recommendations
- Consider presenting Azure CLI examples before PowerShell, as CLI is cross-platform and preferred by many Linux/macOS users.
- Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows.
- Add a Bash shell example for invoking Azure CLI, or clarify that CLI commands are suitable for Bash/terminal users.
- Ensure that references to Azure Cloud Shell highlight its availability for both Bash and PowerShell environments.
Virtual Machines
Restrict managed disks from being imported or exported
...tual-machines/disks-restrict-import-export-overview.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides links and examples for both Azure PowerShell and Azure CLI, but the custom RBAC role section links only to a PowerShell-based guide, and PowerShell is mentioned before CLI in the NetworkAccessPolicy section. This creates a mild Windows bias, as Linux users may prefer CLI or need explicit Linux instructions.
Recommendations
- Add a link to a Linux/CLI-based guide for creating custom RBAC roles, or clarify that the process is identical in CLI.
- Ensure CLI examples and links are presented alongside or before PowerShell examples, especially in sections relevant to both platforms.
- Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Where possible, provide sample commands for both PowerShell and CLI in critical configuration steps.
Virtual Machines
Secure Azure Managed Disk Downloads and Uploads
...icles/virtual-machines/disks-secure-upload-download.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for most tasks, but PowerShell examples are often presented before CLI examples. References to PowerShell are frequent, and in some sections (such as role assignment), PowerShell is mentioned before CLI. However, Linux parity is generally maintained, and CLI examples are included throughout. The 'Next steps' section lists Linux and Windows guides separately, but Windows PowerShell is referenced before Linux CLI in some links.
Recommendations
- Present Azure CLI and PowerShell examples in parallel or alternate their order to avoid Windows-first bias.
- Explicitly mention that Azure CLI works cross-platform (Linux/macOS/Windows) and is recommended for Linux/macOS users.
- Where possible, clarify which examples are platform-specific and which are cross-platform.
- Consider adding Bash or shell script examples for Linux users if relevant.
- Ensure that Linux/macOS users are not required to use PowerShell for any critical task.
Virtual Machines
Share an Azure Managed Disk across VMs
...cs/blob/main/articles/virtual-machines/disks-shared.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation covers both Windows and Linux platforms for Azure shared disks, but Windows examples and explanations are presented first in several sections, such as 'Sample workloads' and performance throttling examples. Linux information is present and detailed, but Windows scenarios are prioritized in ordering and example depth.
Recommendations
- Present Windows and Linux examples in parallel or alternate order to avoid implicit prioritization.
- Expand Linux workload examples to match the depth and specificity of Windows examples (e.g., provide step-by-step guides or templates for Pacemaker/Corosync clusters, as is done for WSFC and SoFS).
- Ensure that performance throttling examples include both Windows and Linux scenarios equally, possibly with diagrams for Linux as well.
- Where possible, provide links to Linux-specific templates or walkthroughs, similar to the Windows links.
Virtual Machines
What's new in Azure Disk Storage
...blob/main/articles/virtual-machines/disks-whats-new.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation is generally neutral and focused on Azure Disk Storage features, but there are a few instances where Windows-specific links or references are given before Linux equivalents, and some links point to Windows-specific documentation. For example, in the 'Live Resize' section, the link is to a Windows page, and in the 'Expand Ultra Disks and Premium SSD v2 without downtime' section, the Windows article is mentioned before the Linux article. There is also a reference to Azure PowerShell in the 'LastOwnershipUpdateTime' section, but Azure CLI is mentioned alongside it.
Recommendations
- Ensure that Linux and macOS examples and documentation links are provided alongside Windows/PowerShell examples, and are given equal prominence.
- Where possible, avoid linking only to Windows-specific documentation; include Linux/macOS documentation or clarify if a feature is platform-agnostic.
- When referencing both Windows and Linux documentation, alternate the order or present them together to avoid 'windows_first' bias.
- Review all links and ensure parity between Windows and Linux documentation coverage.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation covers ephemeral OS disks for both Linux and Windows VMs, with parity in most explanations and examples. However, there are minor signs of Windows bias: Windows image sizes are discussed first in the 'Size requirements' section, and PowerShell is mentioned before CLI in the 'Customer Managed key' section. Linux equivalents are present, but Windows tools and examples tend to be listed first.
Recommendations
- Alternate the order of Windows and Linux examples in sections to avoid implicit prioritization.
- In the 'Customer Managed key' section, mention Azure CLI (Linux) before PowerShell, or present both together.
- In 'Size requirements', discuss Linux image sizes before Windows, or present both together.
- Ensure that all code samples and links for Linux and Windows are equally prominent and accessible.
Virtual Machines
Azure VM Extensions and Features for Linux
...articles/virtual-machines/extensions/features-linux.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all major tasks, but consistently lists PowerShell examples after CLI, and sometimes gives them equal prominence. There are no Linux shell-specific examples beyond Azure CLI, but this is reasonable given the Azure context. No Windows-only tools or patterns are used, and all examples are relevant to Linux VMs. However, PowerShell is not natively available on most Linux systems, so its inclusion may be less useful for Linux-focused users.
Recommendations
- Clearly indicate that Azure PowerShell examples are optional for Linux users, and that Azure CLI is the recommended cross-platform tool.
- Consider adding Bash shell script examples for common extension management tasks (where appropriate) to further support Linux-native workflows.
- In sections where both CLI and PowerShell are shown, consider listing CLI first (as is mostly done), and clarify that PowerShell is primarily for users who prefer it or are on Windows.
- Add a brief note at the top explaining that Azure CLI is the primary tool for Linux VM management, with PowerShell as an alternative.
Virtual Machines
Azure Key Vault VM Extension for Linux
...rticles/virtual-machines/extensions/key-vault-linux.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation is generally Linux-focused, as expected for the Azure Key Vault VM Extension for Linux. However, there are minor signs of Windows bias: PowerShell examples are presented before Azure CLI examples in deployment and troubleshooting sections, and troubleshooting instructions reference Azure PowerShell first. Azure CLI (the cross-platform tool) is included, but is not always shown as the primary or first option. There are no missing Linux examples or Windows-only tools referenced.
Recommendations
- Present Azure CLI examples before PowerShell examples, as Azure CLI is cross-platform and more relevant for Linux users.
- Ensure troubleshooting instructions highlight Azure CLI as the primary method for Linux users.
- Consider adding explicit notes that Azure PowerShell is primarily for Windows, and recommend Azure CLI for Linux/macOS users.
- Where possible, use bash syntax for CLI examples instead of PowerShell-style backticks.
- Review and update any references or links that default to Windows-centric instructions, ensuring Linux parity.
Virtual Machines
NVIDIA GPU Driver Extension - Azure Linux VMs
...es/virtual-machines/extensions/hpccompute-gpu-linux.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation is focused on Linux Azure VMs, but includes PowerShell examples alongside Azure CLI and ARM template examples. The PowerShell example is presented before the Azure CLI example, which may create a perception of Windows-first bias. However, all critical instructions and examples are provided for Linux users, and Linux-specific tools and commands are well represented.
Recommendations
- Move the Azure CLI example before the PowerShell example, as Azure CLI is cross-platform and more commonly used on Linux.
- Clarify that PowerShell can be used on Linux, or explicitly note that the PowerShell example is optional for users who prefer it.
- Consider adding Bash shell script examples for common deployment scenarios, as Bash is native to Linux.
- Ensure troubleshooting and manual steps reference Linux-native commands and tools first.
Virtual Machines
Customer intent: As a cloud administrator, I want to benchmark disk performance using custom I/O workloads, so that I can optimize storage configurations for maximum read and write IOPS in my virtual machines.
...ncludes/virtual-machines-managed-disks-benchmarking.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation presents benchmarking instructions for both Windows (using DISKSPD) and Linux (using FIO), but the Windows section and tool are described first, with more detailed parameter explanations. Linux instructions are comprehensive and include job file examples, but appear after the Windows section. Both platforms are covered, but Windows is prioritized in ordering and parameter detail.
Recommendations
- Reorder sections so Linux and Windows instructions are presented in parallel or with Linux first if targeting cross-platform users.
- Provide equally detailed parameter explanations for FIO as are given for DISKSPD.
- Explicitly state that both DISKSPD and FIO are platform-specific tools, and clarify which tool to use for each OS at the start.
- Consider adding a summary table comparing DISKSPD and FIO usage for Windows and Linux VMs.
Virtual Machines
Create an image definition and image version
...s/blob/main/articles/virtual-machines/image-version.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides parity for both Linux and Windows image creation in Azure Compute Gallery, with CLI, PowerShell, REST, and Portal instructions. However, there is a mild Windows bias: PowerShell examples default to Windows OS, and Windows is often mentioned first in some sections. Linux-specific guidance is present and referenced, but PowerShell examples are Windows-centric and shown before Linux equivalents. CLI and REST examples are Linux-centric, balancing the bias.
Recommendations
- In PowerShell example blocks, provide Linux examples alongside Windows examples, or default to Linux where possible.
- Ensure that both Linux and Windows are equally represented in example code and explanations, especially in PowerShell sections.
- Where OS-specific steps are referenced, link to both Linux and Windows guidance equally.
- Consider alternating the order of OS mentions (Linux first in some sections, Windows first in others) to avoid implicit prioritization.
Virtual Machines
Azure Disk Encryption scenarios on Linux VMs
...ticles/virtual-machines/linux/disk-encryption-linux.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for all major operations, but PowerShell (a Windows-centric tool) is often mentioned first or in more detail. In several sections, PowerShell cmdlets are referenced before CLI commands, and there is frequent use of PowerShell-specific terminology and scripting patterns. However, Linux parity is generally maintained, as Azure CLI is cross-platform and all critical tasks have CLI equivalents. There are no Windows-only tools or missing Linux examples.
Recommendations
- Where possible, present Azure CLI examples before PowerShell examples, as CLI is more native to Linux/macOS users.
- Ensure that CLI instructions are as detailed as PowerShell instructions, including variable initialization and error handling.
- Clarify that PowerShell can be run cross-platform, but highlight that Azure CLI is the preferred tool for Linux/macOS environments.
- Consider adding bash shell scripting examples for advanced scenarios, especially for Linux administrators.
- Review terminology to avoid implying PowerShell is the default or preferred method for Linux users.