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 351-375 of 815 flagged pages
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
Powershell Heavy
Windows Tools
Summary
The documentation presents benchmarking instructions for both Windows and Linux, but the Windows section (DISKSPD) appears first and is more prominent. Windows-specific tooling (DISKSPD) is introduced before Linux tooling (FIO), and the Windows section provides detailed command-line examples and parameter explanations. The Linux section follows, with equally detailed examples using FIO. There is a slight bias in ordering and tool prominence, but Linux parity is generally maintained.
Recommendations
- Consider presenting Windows and Linux sections in parallel or with equal prominence, possibly with a table or side-by-side comparison.
- Explicitly state that DISKSPD is Windows-focused and FIO is Linux-focused at the start of each section.
- Add a brief summary at the top clarifying that both Windows and Linux are covered, and users should select the relevant section for their OS.
- Ensure that parameter explanations and example detail are equally thorough for both tools.
- If possible, provide links to additional Linux benchmarking tools (e.g., ioping, dd) for broader coverage.
Create Pull Request
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 or in more detail, and some backup/encryption instructions reference PowerShell cmdlets before their CLI equivalents. There is a slight preference for PowerShell in explanations and script detail, which may create friction for Linux users, though all tasks are achievable via CLI and the documentation is clearly Linux-focused.
Recommendations
- Ensure Azure CLI examples are presented before or alongside PowerShell examples, especially in sections targeting Linux users.
- Where possible, provide parity in detail and explanation for Azure CLI commands as is given for PowerShell scripts.
- Clarify that Azure PowerShell can be run cross-platform, but highlight Azure CLI as the primary tool for Linux environments.
- Add explicit notes or guidance for Linux/macOS users on tool selection and usage.
- Review backup and snapshot instructions to ensure CLI options are equally emphasized.
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 First
Summary
The documentation is focused on enabling Azure Disk Encryption for Linux VMs and provides Linux-specific guidance throughout. However, in several places, Azure PowerShell is mentioned alongside Azure CLI as a management option for Linux VMs, and PowerShell examples/scripts are referenced equally with CLI examples/scripts. In the 'Next steps' and introductory sections, PowerShell is listed after CLI, but both are presented as options for Linux VM management, which may create minor confusion since PowerShell is traditionally associated with Windows. No critical Linux parity issues are present, and all technical guidance is Linux-centric.
Recommendations
- Clarify that Azure PowerShell can be used cross-platform (Linux, macOS, Windows) and is not Windows-only.
- Consider emphasizing Azure CLI as the primary tool for Linux users, with PowerShell as an alternative for those who prefer it.
- Add a short note explaining that both Azure CLI and PowerShell are supported on Linux, to avoid confusion for users who may associate PowerShell with Windows.
- Ensure that all example scripts and links are clearly labeled as cross-platform where applicable.
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
Windows Tools
Summary
The documentation is overwhelmingly Linux-focused, with detailed instructions for Ubuntu, SUSE, Red Hat (with and without LVM), and generic Linux disk expansion. However, there is a minor bias in the section 'Expand without downtime classic VM SKU support', which provides only a PowerShell script for checking SKU support, without a Linux/Azure CLI equivalent.
Recommendations
- Provide an Azure CLI or Bash equivalent for the PowerShell script used to check classic VM SKU support for disk expansion without downtime.
- Add a note clarifying if the PowerShell script is only relevant for users managing classic VMs from Windows, and suggest alternatives for Linux/macOS users if available.
- Ensure parity by mentioning cross-platform tools where possible, especially in sections referencing Azure management operations.
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 provides comprehensive instructions for preparing and uploading a Red Hat Enterprise Linux VHD for Azure, covering multiple hypervisors (Hyper-V, KVM, VMware, Kickstart). However, in several sections, Windows/Hyper-V instructions are presented first, and some steps reference Hyper-V Manager as the primary workflow, even when Linux-native hypervisors (KVM, VMware) are equally supported. There are no missing Linux examples, and Linux tools and patterns are well represented throughout.
Recommendations
- Reorder sections so that Linux-native hypervisors (KVM, VMware, Kickstart) are presented before or alongside Hyper-V, rather than always after.
- Clarify that Hyper-V Manager steps are only required for users on Windows, and highlight Linux-native workflows for users on Linux/macOS.
- Add a short summary or table at the top outlining which hypervisors are supported on which platforms, to help Linux/macOS users quickly identify relevant instructions.
- Ensure that conversion steps (e.g., VHD creation) reference Linux-native tools (qemu-img, guestfish) equally or before Windows tools.
- Where possible, avoid language that implies Hyper-V is the default or preferred workflow 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 thorough Linux-specific guidance, commands, and configuration examples. However, the introductory section discusses Windows Server 2016 time sync improvements and references Windows documentation before Linux-specific details, which may create a perception of Windows bias. All technical guidance, examples, and tools are Linux-centric and appropriate for the topic.
Recommendations
- Move Windows Server 2016 discussion and references to a background or infrastructure section, clarifying that it is relevant only as the Azure host OS and not for Linux VM configuration.
- Consider starting the page with Linux-specific context and requirements, only mentioning Windows infrastructure as necessary.
- Ensure that Linux guidance is always presented first and Windows references are clearly marked as background information.
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, terminology, or references are mentioned first or exclusively, such as links to Windows/PowerShell upload guides, Windows partitioning (MBR/GPT) documentation, and Windows drive letter conventions. Linux equivalents are present but sometimes mentioned after Windows, or referenced less directly.
Recommendations
- Ensure Linux and Windows examples/tools are presented together or Linux is not consistently secondary.
- Where Windows-specific links are given (e.g., PowerShell upload), ensure Linux/CLI links are equally prominent and described.
- When discussing disk partitioning (MBR/GPT), include links to Linux partitioning documentation or clarify that guidance applies to both OS types.
- When referencing drive letters (e.g., C: or D:), also mention Linux device paths (e.g., /dev/sda, /dev/disk/azure/resource) with equal clarity.
- Review all sections for balanced terminology and tool references, ensuring Linux users are not left to infer their equivalents.
Virtual Machines
Best practices for virtual machine cost optimization
...s/virtual-machines/cost-optimization-best-practices.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation generally maintains parity between Windows and Linux, but there is a minor bias in listing Windows-specific recommendations before Linux equivalents (e.g., 'Use at least B2 for Windows machines' without a similar Linux note). Windows and Linux pricing links are both provided, and Linux VM creation is referenced alongside Windows. No critical sections are Windows-only, and Linux users can complete all tasks.
Recommendations
- Where VM recommendations are given (e.g., 'Use at least B2 for Windows machines'), consider also specifying guidance for Linux machines, or clarify if the recommendation applies to both.
- Ensure that automation examples (e.g., Logic Apps, Azure Automation) mention cross-platform applicability or provide links to Linux-specific automation guidance if relevant.
- When listing pricing or VM size links, consistently mention both Windows and Linux together, rather than referencing Windows first.
- If disk or storage recommendations differ for Linux, explicitly state them.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation covers both Linux and Windows VM scenarios for ephemeral OS disks, including examples and sizing for Ubuntu and Windows Server images. However, there are minor signs of Windows bias: Windows-specific details (such as page file placement) are mentioned before Linux equivalents, and PowerShell is listed before CLI in the section on customer managed keys. Overall, Linux parity is good, but Windows examples and tools are sometimes prioritized.
Recommendations
- Ensure Linux and Windows examples are presented with equal prominence and in parallel, rather than Windows first.
- When referencing tools for configuration (e.g., PowerShell and CLI), list CLI (cross-platform) before PowerShell, or present both together.
- Add explicit Linux-specific details where relevant (e.g., swap file placement, disk partitioning) to match Windows-specific notes.
- Review the order of examples and tool mentions to avoid implicit prioritization of Windows.
Virtual Machines
Deploy Azure dedicated hosts
...in/articles/virtual-machines/dedicated-hosts-how-to.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides parity for both Linux and Windows users, with Azure CLI and PowerShell examples for all major operations. However, PowerShell examples are always present and CLI examples sometimes reference Windows-specific instructions (e.g., removing --generate-ssh-keys for Windows VMs). Portal instructions use generic steps, but the ordering of examples consistently places PowerShell after CLI, and CLI after Portal, which may subtly prioritize Windows users. There are no missing Linux examples, and Azure CLI is cross-platform, but PowerShell is Windows-centric (though now available on Linux/macOS).
Recommendations
- Explicitly state that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Where CLI examples reference Windows-specific steps (such as password prompts), clarify Linux/macOS differences.
- Consider alternating the order of CLI and PowerShell examples, or grouping them as 'Command-line' to avoid implicit prioritization.
- Add a brief note that PowerShell is available on Linux/macOS, but Azure CLI is generally preferred for Linux users.
- Ensure that all CLI examples are tested and work on Linux/macOS shells (bash/zsh), and clarify any OS-specific nuances.
Virtual Machines
Customer intent: "As a cloud architect, I want to develop a robust backup and disaster recovery strategy for my Azure VMs and their managed disks, so that my organization can ensure data availability and minimize downtime during outages or data loss incidents."
...s/backup-and-disaster-recovery-for-azure-iaas-disks.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides a generally balanced overview of backup and disaster recovery for Azure Managed Disks, explicitly stating applicability to both Linux and Windows VMs. However, there are subtle signs of Windows bias: Windows tools and patterns (such as Volume Shadow Service and SQL Server Always On) are mentioned before Linux equivalents, and Windows-specific examples (SQL Server) are more detailed. Linux tools (like fsfreeze) are referenced, but with less explanation and prominence. No Linux/Unix command-line examples or scripts are provided, and PowerShell or Windows-centric terminology appears more frequently.
Recommendations
- Provide Linux-specific examples and tools with equal detail and prominence as Windows tools (e.g., explain fsfreeze usage and limitations, mention other Linux backup coordination tools).
- Include sample Linux shell commands/scripts for snapshot coordination and backup automation, similar to PowerShell examples often found in Windows documentation.
- When referencing application-consistent backup, clarify how Linux workloads (such as PostgreSQL, MySQL, etc.) can achieve similar results, and link to relevant documentation.
- Ensure parity in database examples by including Linux-first workloads (e.g., PostgreSQL, MySQL) alongside SQL Server.
- Review the order of tool mentions to avoid always listing Windows solutions first.
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 server-side encryption for Azure Managed Disks and is explicitly applicable to both Linux and Windows VMs. However, throughout the page, Windows/PowerShell examples and links are consistently presented before Linux/CLI equivalents. References to Azure PowerShell are often given first, and in some cases, only PowerShell is mentioned in the context of revoking access, with CLI as a secondary mention. There is also a slight emphasis on Windows tools (e.g., BitLocker) in comparison sections, but Linux equivalents (DM-Crypt) are also referenced.
Recommendations
- Present Linux/CLI examples and links alongside or before Windows/PowerShell examples to avoid implicit prioritization.
- Ensure that all procedural references (such as revoking access) include both PowerShell and CLI options equally and clearly.
- Where possible, use neutral language and ordering when listing cross-platform tools or features.
- Consider adding explicit Linux/macOS command examples or clarifying parity in any ambiguous sections.
Virtual Machines
Benchmark your application on Azure Disk Storage
...lob/main/articles/virtual-machines/disks-benchmarks.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation mentions both Windows (DiskSpd) and Linux (FIO) benchmarking tools, but DiskSpd (Windows) is listed first and the overall tone slightly favors Windows by mentioning Windows tools and patterns before Linux equivalents. However, both platforms are acknowledged and tools for each are referenced. The actual benchmarking example details are not shown, so it's unclear if Linux examples are missing or less detailed.
Recommendations
- Ensure Linux (FIO) examples are as detailed and prominent as Windows (DiskSpd) examples.
- Consider alternating the order in which Windows and Linux tools are mentioned, or presenting them side-by-side.
- Explicitly state that both tools are equally supported and provide links to comprehensive usage guides for both.
- If possible, include sample command lines or scripts for both DiskSpd and FIO in the documentation.
Virtual Machines
Migrate Standard HDD OS disks by September 08, 2028
...n/articles/virtual-machines/disks-hdd-os-retirement.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides migration guidance for both Linux and Windows VMs, and explicitly states applicability to both. However, in the section describing how to list affected disks using Azure PowerShell and Azure CLI, the PowerShell example is mentioned first, which is a minor Windows-first bias. Both Linux-friendly (Azure CLI) and Windows-friendly (PowerShell) tools are referenced, and the examples are equivalent. No critical Windows-only tools or patterns are present, and Linux users can complete all tasks described.
Recommendations
- Present Azure CLI and PowerShell examples in parallel or alternate which is shown first.
- Explicitly note that Azure CLI is cross-platform and may be preferred for Linux/macOS users.
- Consider adding Bash or shell script snippets for bulk operations, if relevant.
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 ordering of examples places PowerShell before Azure CLI, which is more cross-platform. There are no explicit Linux/macOS-specific instructions or examples, but Azure CLI and ARM templates are inherently cross-platform. No Windows-only tools or patterns are exclusively mentioned, and Linux users can complete all tasks using Azure CLI or ARM templates.
Recommendations
- Consider placing Azure CLI examples before PowerShell, as CLI is cross-platform and more accessible to Linux/macOS users.
- Explicitly mention that Azure CLI and ARM templates can be used on Linux/macOS, and provide links to installation guides for those platforms.
- Add a note clarifying that PowerShell is available cross-platform, but Azure CLI is often preferred on Linux/macOS.
- Ensure parity in example detail between PowerShell and Azure CLI sections.
Virtual Machines
Enable end-to-end encryption using encryption at host - Azure portal - managed disks
...-machines/disks-enable-host-based-encryption-portal.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for enabling encryption at host, but PowerShell examples are consistently presented first. The 'Next steps' section links to a PowerShell-focused sample repository. There is a slight preference for Windows/PowerShell tools and ordering, though Linux parity is generally maintained via Azure CLI examples.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or present CLI examples first in some sections.
- Include links to Azure CLI sample repositories in the 'Next steps' section, not just PowerShell.
- Explicitly mention that Azure CLI commands work on Linux/macOS and Windows, and clarify any OS-specific nuances.
- Where possible, add screenshots or references for Linux/macOS users in portal walkthroughs.
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 references to both Azure PowerShell and Azure CLI for configuring disk restrictions, but the custom RBAC role section links only to a PowerShell-based guide. Additionally, PowerShell is mentioned before CLI in the section about configuring the NetworkAccessPolicy parameter, suggesting a Windows-first approach. Linux-specific examples or parity are not missing, but Windows tools are given prominence.
Recommendations
- Add a link to a custom RBAC role creation guide using Azure CLI or ARM templates, not just PowerShell.
- When mentioning configuration tools, list Azure CLI before PowerShell or equally, to avoid Windows-first bias.
- Where possible, provide explicit Linux/macOS command examples alongside PowerShell examples.
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 PowerShell and Azure CLI examples for securing managed disk downloads and uploads, but PowerShell examples are often presented before CLI examples. There is a slight preference for PowerShell (a Windows-centric tool) in ordering and prominence. However, Linux parity is generally maintained, with CLI examples and Linux-specific next steps included.
Recommendations
- Present Azure CLI and PowerShell examples side-by-side or alternate their ordering to avoid Windows-first bias.
- Explicitly mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Where possible, add Bash shell script examples for Linux users.
- Ensure screenshots and portal instructions are not Windows-centric.
- Review included files (prereqs/restrictions) to confirm Linux parity.
Virtual Machines
Enable InfiniBand on HPC VMs - Azure Virtual Machines | Microsoft Docs
...icles/virtual-machines/extensions/enable-infiniband.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation covers both Linux and Windows for enabling InfiniBand on Azure HPC VMs. However, there is mild bias in the 'InfiniBand Driver VM Extensions' section, where Windows extension details and PowerShell usage are mentioned before Linux equivalents, and PowerShell is presented as the primary tool for extension management. Linux examples are present and detailed, but Windows tools and patterns are referenced first in some sections.
Recommendations
- Present Linux and Windows instructions in parallel or clearly separated sections, avoiding Windows-first ordering.
- Include Azure CLI or ARM template examples for managing VM extensions, as these are cross-platform and commonly used on Linux/macOS.
- Explicitly mention Linux tools (e.g., az CLI) alongside PowerShell when discussing VM extension management.
- Ensure that Linux examples are as prominent and detailed as Windows examples throughout the documentation.
Virtual Machines
Azure Key Vault VM Extension for Linux
...rticles/virtual-machines/extensions/key-vault-linux.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation is focused on the Azure Key Vault VM Extension for Linux and provides both Azure CLI and Azure PowerShell deployment instructions. However, PowerShell examples and troubleshooting commands are presented first in several sections, and PowerShell-specific warnings are highlighted. While Azure CLI instructions are included and the extension is Linux-specific, the ordering and emphasis on PowerShell may create friction for Linux users, as PowerShell is not a native tool on most Linux distributions.
Recommendations
- Present Azure CLI examples before PowerShell in all sections, as CLI is more commonly used on Linux.
- Add explicit notes clarifying that PowerShell is optional and not required for Linux deployments.
- Highlight Azure CLI as the recommended method for Linux users.
- Where troubleshooting commands are shown, show Azure CLI first and PowerShell second.
- Consider removing PowerShell-specific warnings from the main flow or move them to a dedicated section for cross-platform users.
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 largely neutral and focused on Azure Disk Storage features, but there are a few minor signs of Windows bias. Some links and references point to Windows-specific documentation first or exclusively (e.g., 'expand with Ultra Disks and Premium SSD v2' links to a Windows page, and 'find-unattached-disks' documentation is Windows-focused). In one section, the Windows article is mentioned before the Linux equivalent for expanding disks without downtime. There is also a reference to Azure PowerShell in describing disk properties, which may be perceived as a Windows-centric tool, though Azure CLI is also mentioned.
Recommendations
- Ensure that all feature links referencing operational tasks (e.g., expanding disks, finding unattached disks) include both Windows and Linux documentation, or use a neutral landing page that covers both.
- When mentioning tools like Azure PowerShell, always mention Azure CLI alongside it, and clarify cross-platform support.
- When listing example articles for tasks, alternate the order or use a neutral phrasing (e.g., 'See the Windows and Linux articles' instead of 'See the Windows or Linux articles').
- Review linked documentation to ensure Linux parity and add missing Linux examples where only Windows is referenced.
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 VM GPU driver installation, but includes PowerShell examples for deploying the extension before Azure CLI examples. PowerShell is primarily a Windows tool, and its inclusion and placement before Linux-native tools (Azure CLI, Bash) may create friction for Linux users. However, Linux-specific instructions, examples, and troubleshooting steps are present throughout, and the extension itself is Linux-focused.
Recommendations
- Move Azure CLI examples before PowerShell examples, as Azure CLI is cross-platform and more commonly used by Linux/macOS users.
- Clarify that PowerShell is optional and primarily for Windows users; recommend Azure CLI for Linux/macOS users.
- Consider adding Bash script examples for common tasks (e.g., checking extension status, troubleshooting).
- Ensure screenshots and instructions are Linux-centric, as currently done.
Virtual Machines
Create an encrypted image version with customer-managed keys
.../articles/virtual-machines/image-version-encryption.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both PowerShell and Azure CLI examples for creating encrypted image versions with customer-managed keys. However, PowerShell examples are presented first and in greater detail, with more explanation and step-by-step variable setup, while the Azure CLI section is less detailed. There are no explicit Linux shell (bash) or macOS-specific examples, but the CLI commands are cross-platform. References to Windows-specific tools or patterns are minimal, and the feature itself applies to both Linux and Windows VMs.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and more accessible to Linux/macOS users.
- Ensure that CLI and PowerShell examples are equally detailed, with similar variable setup and explanation.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide a short note or link on how to install Azure CLI on non-Windows platforms.
- Where possible, add bash script examples for common tasks, or clarify that the CLI commands can be run in any shell.
- Avoid referencing Windows-specific cryptographic documentation (e.g., CNG) unless there is no cross-platform equivalent.
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 both Linux and Windows guidance, but there are subtle signs of Windows bias. In the PowerShell section, Windows examples are shown first and in more detail, while Linux is mentioned as an alternative. The CLI section is more neutral, but the PowerShell section is Windows-centric. The portal instructions are OS-agnostic. There are no missing Linux examples, and Linux-specific guidance is linked. Overall, the bias is minor and does not prevent Linux/macOS users from completing the task.
Recommendations
- In PowerShell examples, show Linux usage first or equally alongside Windows.
- Add explicit PowerShell examples for Linux image creation, not just mention '-OsType Linux'.
- Ensure parity in detail and explanation for both OS types in all example sections.
- Consider adding Bash scripting examples for Linux users, especially for automation.
- Review ordering of OS-specific guidance to avoid 'Windows first' impression.
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). However, the Windows section appears first and is more detailed in its explanation of command parameters, while the Linux section is presented second. Both platforms are covered with practical examples, but the ordering and slightly greater detail for Windows may create a minor perception of Windows bias.
Recommendations
- Present Linux and Windows benchmarking instructions in parallel or with equal prominence.
- Provide equally detailed explanations for Linux (FIO) command parameters as given for Windows (DISKSPD).
- Consider starting with a platform-neutral overview, then clearly separate Windows and Linux sections.
- Add a summary table comparing DISKSPD and FIO usage for quick reference.