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 676-700 of 815 flagged pages
Virtual Machines
Deprovision or generalize a VM before creating an image
...docs/blob/main/articles/virtual-machines/generalize.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides clear, separate instructions for both Linux and Windows VM generalization. However, the Windows section includes more detailed prerequisites and troubleshooting steps, and Windows PowerShell/Command Prompt examples are shown before Linux equivalents in some sections. The Windows example for marking a VM as generalized uses PowerShell, while the Linux example uses Azure CLI, potentially causing friction for cross-platform users. Overall, Linux instructions are present and functional, but Windows receives slightly more attention and detail.
Recommendations
- Ensure Linux and Windows sections have parity in detail and troubleshooting guidance.
- Provide Azure CLI examples for Windows VM generalization, not just PowerShell.
- Consider presenting Linux and Windows instructions in parallel or with equal prominence.
- Add troubleshooting tips for Linux deprovisioning similar to those given for Windows Sysprep.
Create Pull Request
Virtual Machines
Azure VM Extensions and Features for Linux
...articles/virtual-machines/extensions/features-linux.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples throughout, but PowerShell examples are always given alongside CLI and never omitted. However, PowerShell is featured equally and sometimes before CLI, despite the Linux focus. The documentation references Azure PowerShell as a primary tool for managing Linux VM extensions, which is more commonly used on Windows. There are no missing Linux examples, and all sample scripts and ARM templates are Linux-centric. The severity of bias is low, as Linux users can complete all tasks using CLI, ARM templates, or portal, but the prominence of PowerShell may cause minor confusion or friction.
Recommendations
- Feature Azure CLI examples before Azure PowerShell examples, as CLI is the cross-platform default for Linux users.
- Clarify that Azure PowerShell is optional and primarily for users who prefer it, not required for Linux VM management.
- Consider grouping CLI and PowerShell examples under clear tabs, with CLI as the default/first tab.
- Add explicit notes that Azure CLI is recommended for Linux/macOS environments.
- Review and minimize references to PowerShell unless necessary for 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 clearly focused on Linux VMs, with extensive Linux-specific instructions and examples. However, PowerShell examples are provided alongside Azure CLI and ARM template examples, and PowerShell is mentioned before Azure CLI in the deployment section. There are no missing Linux examples or Windows-only tools, but the ordering and inclusion of PowerShell (a Windows-centric tool) may create minor friction for Linux users.
Recommendations
- Move Azure CLI examples before PowerShell examples, as Azure CLI is more commonly used on Linux.
- Clarify that PowerShell examples are optional and primarily for users on Windows or cross-platform PowerShell Core.
- Consider providing Bash script examples for common deployment scenarios.
- Explicitly note that Azure CLI is the recommended tool for Linux users.
Virtual Machines
HBv3-series virtual machine (VM) overview, architecture, topology - Azure Virtual Machines | Microsoft Docs
...main/articles/virtual-machines/hbv3-series-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is largely cross-platform and includes both Linux and Windows support. However, there is a subtle Windows-first bias: the 'Recommended OS for Performance' is listed as 'Windows Server 2019+' without a Linux equivalent, and the temporary storage section uses the term 'page file' (a Windows concept) without mentioning the Linux swap partition. While Linux tools (like lstopo) are shown, there are no Windows equivalents or instructions for Windows users to inspect NUMA topology, which could be a minor omission for parity.
Recommendations
- In the 'Recommended OS for Performance' row, also recommend a specific Linux distribution/version for optimal performance (e.g., RHEL 8.x, Ubuntu 20.04+).
- In the temporary storage section, clarify the equivalent Linux concept (e.g., swap partition) alongside 'page file'.
- If possible, provide Windows-native tooling or instructions (e.g., using 'coreinfo' or Windows System Information) for inspecting NUMA topology, or explicitly state that such tools are not available if that's the case.
- Ensure that examples and recommendations are balanced for both Linux and Windows, especially in sections where performance tuning or system inspection is discussed.
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 Reference
Powershell Example
Summary
The documentation is focused on Linux VM time synchronization in Azure and provides Linux-centric guidance, commands, and examples. However, it references Windows Server 2016 improvements and links to Windows documentation in the introduction and conclusion. Additionally, a PowerShell example is provided for base64 encoding a cloud-init file, which is a Windows-centric tool, even though the rest of the guidance is Linux-focused.
Recommendations
- Move Windows references to a background section or footnote, clarifying their relevance to Linux VM time sync.
- Provide a Linux equivalent for the PowerShell base64 encoding example, such as using 'base64' or 'openssl' on Linux.
- Ensure that all examples and tooling instructions are available for Linux users, especially for tasks like preparing cloud-init files.
- Clarify that the PowerShell example is optional and provide context for users on non-Windows platforms.
Virtual Machines
Create a Gallery for Sharing Resources
.../blob/main/articles/virtual-machines/create-gallery.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides examples for creating an Azure Compute Gallery using the Azure Portal, Azure CLI, PowerShell, and REST API. While all major cross-platform tools are covered, the PowerShell example is given equal prominence alongside CLI and REST, and the ordering of examples sometimes places PowerShell before REST. However, the CLI examples (which are cross-platform) are present and complete. There is no evidence of exclusive Windows tooling or missing Linux/macOS examples, but PowerShell is included as a first-class option, which may be unnecessary for Linux/macOS users.
Recommendations
- Consider listing Azure CLI examples before PowerShell examples, as CLI is cross-platform and more relevant for Linux/macOS users.
- Explicitly note that PowerShell is primarily for Windows users, and recommend Azure CLI for Linux/macOS.
- Ensure that all CLI examples are as detailed as PowerShell examples.
- If possible, add Bash scripting examples for Linux users, or clarify that Azure CLI commands can be run in Bash.
Virtual Machines
Instantly access managed disk snapshots
...les/virtual-machines/disks-instant-access-snapshots.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI (bash/shell) and PowerShell examples for creating instant access snapshots, but PowerShell is presented immediately after CLI and before Resource Manager Template and Portal instructions. There are no Linux-specific tools or patterns mentioned, but the ordering of examples (CLI, PowerShell, Portal, ARM) may subtly prioritize Windows users. All CLI examples use bash syntax, which is cross-platform, but PowerShell is highlighted as a separate tab, which may reinforce Windows-centric workflows. No Linux/macOS-specific issues or missing examples are detected.
Recommendations
- Consider explicitly noting that Azure CLI commands work on Linux, macOS, and Windows, to reinforce cross-platform support.
- If possible, provide example CLI commands using both bash and PowerShell syntax, or clarify that PowerShell examples are for Windows users while CLI is for all platforms.
- Ensure that Linux/macOS users are aware that all tasks can be completed using Azure CLI, and that PowerShell is optional.
- If there are any Linux-specific considerations (e.g., file permissions, shell differences), mention them.
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 primarily focused on Linux, as indicated by the title and content. However, PowerShell examples are provided alongside Azure CLI and ARM template examples, and PowerShell is presented before Azure CLI in the deployment section. There is a brief mention of a Windows extension, but no Windows-specific tools or patterns dominate the content. All technical instructions, troubleshooting, and known issues are Linux-centric, and Linux tools and commands are used throughout.
Recommendations
- Move Azure CLI examples before PowerShell examples, as CLI is cross-platform and more relevant for Linux users.
- Clarify that PowerShell examples are optional and primarily for users on Windows or those who prefer PowerShell.
- Consider adding Bash script examples for automation, as Bash is the default shell for most Linux distributions.
- Ensure that all screenshots and command snippets are clearly labeled as Linux-specific to avoid confusion.
Virtual Machines
HBv3-series virtual machine (VM) overview, architecture, topology - Azure Virtual Machines | Microsoft Docs
...main/articles/virtual-machines/hbv3-series-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is generally cross-platform and provides technical details relevant to both Linux and Windows users. However, there is a subtle bias in the 'Recommended OS for Performance' row, which lists 'Windows Server 2019+' as the recommended OS without a Linux equivalent or guidance. Additionally, while Linux tools (like lstopo) are referenced and Linux OS support is listed, there are no explicit examples or recommendations for optimal Linux distributions or configurations, whereas Windows is specifically recommended.
Recommendations
- Add a recommended Linux distribution (or distributions) for performance parity in the 'Recommended OS for Performance' row, such as 'RHEL 8.6+', 'Ubuntu 20.04+', or similar, based on Azure's own benchmarking or support statements.
- If Windows Server 2019+ is recommended for specific features, clarify what those features are and whether equivalent features or performance can be achieved on Linux.
- Where possible, provide Linux-specific configuration tips or references, especially for HPC workloads (e.g., kernel tuning, NUMA awareness, or driver installation best practices).
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 throughout, but PowerShell examples are always given immediately after CLI, and often with equal prominence. There is a slight 'windows_first' bias in that PowerShell (a Windows-centric tool, though now cross-platform) is always paired with CLI, and never omitted or de-emphasized. However, all examples and explanations are clearly tailored for Linux VMs, and the CLI is always presented first. No Windows-only tools or patterns are mentioned, and Linux-specific tools (like waagent) are referenced. There are no missing Linux examples, and no Windows tools are prioritized over Linux equivalents.
Recommendations
- Consider explicitly noting that Azure PowerShell is cross-platform and can be used on Linux/macOS, to avoid confusion for Linux users.
- Where possible, highlight Bash/CLI as the primary method for Linux users, and clarify PowerShell is optional.
- Add brief guidance for users who may not have PowerShell installed on Linux, linking to installation instructions.
- Ensure that CLI examples are always shown first (as is currently the case), and consider grouping PowerShell examples in a separate section for users who prefer it.
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 focused on Linux, but there are several sections where Windows-oriented tools (PowerShell) are presented first or in greater detail than Linux-native equivalents. Azure PowerShell deployment instructions and troubleshooting are given before Azure CLI, and PowerShell is referenced in warnings and notes. However, Linux-specific instructions and paths are present throughout, and Azure CLI examples are provided. There are no missing Linux examples or Windows-only tools.
Recommendations
- Present Azure CLI instructions before Azure PowerShell, as CLI is more cross-platform and native to Linux/macOS.
- Add explicit notes clarifying that PowerShell is optional and not required for Linux users.
- Where warnings reference PowerShell-specific issues (e.g., escaping in settings.json), clarify that these are only relevant if using PowerShell, and provide Linux/CLI-specific troubleshooting if applicable.
- Ensure troubleshooting and support sections reference both CLI and PowerShell equally, with CLI first.
- Consider adding Bash or shell script deployment examples for Linux users, if relevant.
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 throughout, with CLI and REST examples defaulting to Linux, but PowerShell examples defaulting to Windows. Windows is sometimes mentioned first in PowerShell examples, and PowerShell is given its own section with Windows-centric parameters. However, Linux is well-represented in CLI and REST, and the 'Before you begin' section lists Linux guidance first. No critical tasks are Windows-only.
Recommendations
- In PowerShell example blocks, show both Linux and Windows variants, or default to Linux as in CLI/REST.
- When listing OS-specific steps or parameters, alternate the order or clarify parity.
- Explicitly note that PowerShell can be used for Linux images, and provide a Linux example.
- Ensure that all example code blocks (especially PowerShell) demonstrate both Linux and Windows usage.
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 creating and uploading a Red Hat Enterprise Linux VHD for Azure across multiple hypervisors (Hyper-V, KVM, VMware, Kickstart). However, in most sections, Hyper-V (a Windows-native hypervisor) is presented first, and references to Windows tools (e.g., Hyper-V Manager, convert-vhd cmdlet) appear before Linux alternatives. The introductory notes mention Hyper-V tools before Linux/KVM/VMware, and the step-by-step guides for each RHEL version begin with Hyper-V before Linux-native options. All necessary Linux-native instructions are present, but Windows/Hyper-V is prioritized in ordering and framing.
Recommendations
- Reorder sections so that Linux-native hypervisors (KVM, VMware, Kickstart) are presented before Hyper-V, or at least alternate the order to avoid implicit prioritization.
- In introductory notes, mention Linux-native tools (e.g., qemu-img, KVM, VMware) alongside or before Windows tools like Hyper-V Manager and convert-vhd.
- Ensure that Linux-native conversion instructions (e.g., qemu-img) are as prominent as Windows/Hyper-V instructions.
- Consider adding a summary table or navigation section that equally highlights all supported hypervisors and platforms.
- Clarify that Hyper-V is not required for Linux users, and that all steps can be completed on Linux-native platforms.
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 sync in Azure and provides comprehensive Linux-specific guidance, examples, and commands. However, the introductory sections discuss Windows Server 2016 time sync improvements and reference Windows documentation before Linux-specific details. This is a minor 'windows_first' bias in the narrative, but all technical guidance and examples are Linux-centric.
Recommendations
- Move Windows Server 2016 discussion and links to a background or context section, or after Linux-specific information.
- Begin the page with Linux time sync context and Azure-specific Linux features before referencing Windows infrastructure.
- Ensure that Linux documentation links and examples are presented before any Windows references, unless Windows context is strictly necessary.
Virtual Machines
Share VM images in a compute gallery
...in/articles/virtual-machines/shared-image-galleries.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation covers both Linux and Windows VM images, but there are signs of Windows bias. PowerShell examples are provided alongside Azure CLI, and Windows-specific references (e.g., Sysprep, Windows upload instructions) are sometimes mentioned before Linux equivalents. Some links and examples reference Windows paths or tools first. However, Linux is also covered, and CLI examples are present.
Recommendations
- Ensure Linux and Windows examples are presented with equal prominence, alternating their order where possible.
- Provide Bash/Linux shell examples alongside PowerShell, especially in FAQ and walkthroughs.
- Where referencing upload instructions or tools, mention Linux and Windows equally and avoid defaulting to Windows-first ordering.
- Review linked pages to ensure Linux parity in referenced content.
- Clarify when a feature or step is OS-agnostic, and avoid unnecessary Windows-centric language.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for checking vCPU quotas, but PowerShell is featured as a primary tab, and its inclusion may be unnecessary for Linux users. The CLI example is generic and cross-platform, but PowerShell is a Windows-centric tool. There are no Linux-specific shell examples (e.g., Bash), and PowerShell is presented equally alongside CLI, which may create friction for Linux/macOS users.
Recommendations
- Clarify that PowerShell is primarily for Windows users, and Azure CLI is recommended for Linux/macOS.
- Consider presenting Azure CLI examples first, as it is cross-platform.
- Add explicit Bash shell examples or notes for Linux users, if relevant.
- Mention that PowerShell Core is available cross-platform, but most Linux users prefer CLI.
- Add a short section or note indicating which tools are best for each OS.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for checking vCPU quotas. However, the PowerShell section is given equal prominence to the CLI, despite PowerShell being primarily a Windows tool. The CLI example is shown first, which is positive, but the PowerShell section is still highlighted as a main method, which may create friction for Linux/macOS users who do not use PowerShell. No Linux-specific tools or shell commands are mentioned, but the CLI example is cross-platform.
Recommendations
- Clearly indicate that Azure CLI is the recommended cross-platform method for Linux/macOS users.
- Add a note clarifying that PowerShell is primarily for Windows users, and that Azure CLI works on all platforms.
- Consider providing Bash shell script examples for common quota-checking tasks, or referencing how to install Azure CLI on Linux/macOS.
- If possible, link to Azure CLI installation guides for Linux/macOS in the 'Related content' section.
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 between Linux and Windows in most sections, including CLI, REST, and portal instructions. However, there is a mild Windows bias in the PowerShell examples, which default to Windows OS and show Windows-specific parameters first. Additionally, in some sections, Windows is mentioned before Linux, and PowerShell examples are more prominent than Bash or Linux shell alternatives.
Recommendations
- In PowerShell examples, show both Linux and Windows OS types equally, or default to Linux where appropriate.
- Ensure that Linux and Windows examples are presented in parallel, rather than defaulting to Windows in PowerShell sections.
- Where possible, provide Bash or shell script equivalents for PowerShell commands, especially for Linux users.
- Review order of OS mentions to avoid always listing Windows first.
- Add explicit notes or examples for Linux-specific scenarios in PowerShell sections, if relevant.
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 is generally Linux-focused and provides comprehensive guidance for Linux VM extensions in Azure. However, in several sections, Azure PowerShell examples are presented alongside Azure CLI examples, sometimes with PowerShell shown first or with equal prominence. This could create minor friction for Linux users, as PowerShell is less commonly used on Linux compared to Azure CLI. All example scripts and ARM templates are Linux-centric, and no Windows-only tools or patterns are promoted.
Recommendations
- Where both Azure CLI and PowerShell examples are shown, consider listing Azure CLI first, as it is the more common tool for Linux users.
- Explicitly note that PowerShell examples are optional for Linux users and that Azure CLI is the primary cross-platform tool.
- Where possible, provide Bash script examples for local troubleshooting or automation tasks, in addition to Azure CLI.
- If PowerShell is included, clarify its cross-platform availability but emphasize CLI for Linux workflows.
Virtual Machines
Create a Gallery for Sharing Resources
.../blob/main/articles/virtual-machines/create-gallery.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides examples for Azure Portal, Azure CLI, PowerShell, and REST API. PowerShell is presented as a distinct example, but it is not prioritized over cross-platform tools. However, in the 'Create a private gallery' section, the PowerShell example is shown after CLI and Portal, which is appropriate. All CLI examples use Azure CLI, which is cross-platform and works on Windows, Linux, and macOS. There are no Windows-specific tools or patterns mentioned, and Linux/macOS users are not excluded from any critical steps. The only minor bias is that PowerShell is included as a separate example, which may be unnecessary given Azure CLI's cross-platform nature, but it is not shown first.
Recommendations
- Clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Consider adding a note that PowerShell examples are primarily for Windows users, but PowerShell Core is available cross-platform.
- Ensure that CLI examples are always shown before PowerShell, as is currently done.
- Optionally, add Bash shell script examples for Linux users, though Azure CLI covers most needs.
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 alongside Azure CLI and ARM templates. The PowerShell example is presented before the Azure CLI example, which is more relevant for Linux users. There is also a brief mention of a Windows extension, but it is clearly separated and not the main topic. No Windows-only tools or patterns are prioritized, and Linux-specific commands and troubleshooting are well covered.
Recommendations
- Move the Azure CLI example before the PowerShell example, as Azure CLI is more commonly used for Linux VM management.
- Clarify that PowerShell is primarily for users managing Azure from Windows environments, and highlight Azure CLI as the preferred cross-platform tool.
- Consider adding Bash shell script examples for advanced automation, if relevant.
- Ensure all screenshots and instructions are Linux-specific (which they currently are).
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 generally Linux-focused and covers Linux-specific extension details, paths, and certificate handling. However, in deployment and troubleshooting sections, Azure PowerShell examples are presented first and in greater detail, with explicit warnings about PowerShell quirks. Azure CLI examples are present but often shown after PowerShell, and troubleshooting instructions reference PowerShell before CLI. There are no missing Linux examples, but the ordering and emphasis may create friction for Linux users who typically prefer CLI or shell-based workflows.
Recommendations
- Present Azure CLI examples before PowerShell in deployment and troubleshooting sections, as CLI is more commonly used on Linux.
- Expand CLI troubleshooting instructions to match the detail provided for PowerShell.
- Add a brief note clarifying that both Azure CLI and PowerShell are supported, but CLI is recommended for Linux environments.
- Ensure all JSON and shell examples use Linux-friendly syntax and paths (which is already mostly the case).
Virtual Machines
Share VM images in a compute gallery
...in/articles/virtual-machines/shared-image-galleries.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Minor Windows Tools
Summary
The documentation covers both Linux and Windows VM images, but there are several signs of Windows bias. PowerShell examples are provided alongside Azure CLI, and Windows terminology/tools (e.g., Sysprep, Windows upload links) are often mentioned first or more prominently. In some cases, Windows-specific links or examples precede Linux equivalents, and PowerShell is referenced in feature explanations and sharing instructions. However, Linux is explicitly supported and referenced throughout, and CLI examples are present.
Recommendations
- Ensure Linux and Windows examples are given equal prominence, alternating order where possible.
- Provide Bash/Linux shell examples alongside PowerShell, especially in sections where only PowerShell is shown.
- When referencing upload or creation guides, mention Linux and Windows links together, not with Windows first.
- Clarify that both Linux and Windows tools (waagent, Sysprep) are required for generalization, and provide links for both.
- Where PowerShell is referenced for sharing or management, ensure CLI/Bash alternatives are equally visible.
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
Windows Tools
Summary
The documentation provides step-by-step instructions for preparing and uploading a Red Hat Enterprise Linux VHD for Azure using multiple hypervisors, including Hyper-V (Windows), KVM (Linux), VMware, and Kickstart. However, in most sections and workflows, Hyper-V (a Windows-based tool) is presented first, and Windows-centric terminology (e.g., Hyper-V Manager, VHD conversion using Windows tools) is prominent. Linux alternatives (KVM, VMware, Kickstart) are covered in detail, but Windows/Hyper-V instructions are consistently prioritized and referenced as the primary workflow. Some conversion steps mention Windows tools (e.g., Hyper-V Manager, convert-vhd cmdlet) before Linux equivalents (e.g., qemu-img), and the overall structure puts Windows/Hyper-V steps before Linux/KVM/VMware steps.
Recommendations
- Reorder sections so that Linux-native hypervisors (KVM, VMware, Kickstart) are presented before or alongside Hyper-V, rather than always after.
- Where disk conversion is discussed, mention Linux tools (qemu-img) before or alongside Windows tools (Hyper-V Manager, convert-vhd).
- Add a summary table or navigation at the top to help Linux users quickly find their relevant workflow.
- Ensure that Linux-specific terminology and tools are not overshadowed by Windows/Hyper-V references.
- Consider adding explicit notes that all workflows are equally supported, and none is preferred based on OS.