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 551-575 of 815 flagged pages
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 the PowerShell section is given equal prominence despite PowerShell being primarily a Windows tool. There is no explicit Linux example (e.g., Bash), but the CLI example is cross-platform. The CLI section appears first, which is positive, but the PowerShell section may create friction for Linux/macOS users unfamiliar with PowerShell.
Recommendations
- Clarify that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
- Add explicit Bash shell examples (even if they mirror the CLI usage) to reinforce Linux parity.
- Mention that PowerShell Core is available on Linux/macOS, if relevant, but note its Windows origins.
- Consider adding a note about the platform compatibility of each tool.
Create Pull Request
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 is generally cross-platform, explicitly stating applicability to both Linux and Windows VMs. However, there are a few sections where Windows tools, terminology, or references are presented first or exclusively, such as links to Windows documentation before Linux equivalents, and Windows partitioning concepts (MBR/GPT) are emphasized. The 'Upload your VHD or VHDX' section links to both Azure CLI (Linux) and PowerShell (Windows) guides, but the Windows link is listed second. The OS disk section references Windows drive letters and partitioning, with Linux equivalents not always given equal detail.
Recommendations
- Ensure Linux and Windows examples, tools, and terminology are presented with equal prominence.
- When discussing disk partitioning (MBR/GPT), include Linux-specific guidance or links alongside Windows references.
- In sections referencing drive letters or Windows-specific paths, add Linux equivalents (e.g., mount points, device names) for clarity.
- Where links to platform-specific guides are given, list Linux and Windows options together or alternate their order.
- Review all references to Windows tools (e.g., PowerShell) and ensure Linux tools (e.g., Azure CLI, Bash) are equally mentioned.
Virtual Machines
Azure premium storage: Design for high performance
...ticles/virtual-machines/premium-storage-performance.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Linux and Windows guidance, but there are several instances where Windows tools (e.g., PerfMon, Storage Spaces, PowerShell) are mentioned first or in more detail, and Windows-specific patterns are described with more depth. Linux equivalents are present but sometimes less emphasized or referenced after Windows. Some sections (e.g., disk striping, performance counters) give more detailed or prominent instructions for Windows users, with Linux instructions present but less detailed or referenced via external links.
Recommendations
- Ensure Linux and Windows examples are presented with equal prominence and detail, ideally side-by-side.
- When mentioning tools (e.g., PerfMon/iostat, Storage Spaces/MDADM), list both platforms together or alternate which is mentioned first.
- Expand Linux-specific instructions (e.g., for disk striping, benchmarking, and performance tuning) to match the depth provided for Windows.
- Where PowerShell is used for Windows, provide equivalent CLI/bash commands for Linux.
- Add more direct Linux examples inline, rather than primarily referencing external links.
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 presents cost optimization practices for Azure virtual machines in a platform-neutral way, but there is a minor bias where Windows-specific guidance (e.g., 'Use at least B2 for Windows machines') is mentioned before Linux equivalents, and Windows pricing links are listed before Linux pricing links. No critical sections are Windows-only, and Linux users can follow all recommendations.
Recommendations
- When mentioning VM sizing recommendations, provide equivalent guidance for Linux (e.g., 'Use at least B2 for Windows machines; for Linux, refer to performance requirements').
- Present Windows and Linux pricing links together or in parallel, rather than listing Windows first.
- Where automation or scheduling is discussed, clarify that solutions like Azure Automation and Logic Apps are cross-platform.
- Ensure examples and recommendations are equally applicable to Linux and Windows, or explicitly note any platform-specific differences.
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 CLI or Portal. However, the PowerShell example is included alongside CLI and REST, which are cross-platform, but PowerShell is primarily a Windows tool. The CLI examples are shown before PowerShell, and there are no Windows-specific tools or patterns prioritized. No Linux/macOS-specific examples (e.g., Bash scripts) are given, but the CLI commands are cross-platform and suitable for Linux/macOS users. The only minor bias is the inclusion of PowerShell as a separate example, which may be unnecessary for Linux users, but it does not impede their ability to complete the task.
Recommendations
- Clarify that Azure CLI commands are cross-platform and suitable for Linux/macOS users.
- Consider adding Bash shell scripting examples for Linux users, or explicitly mention that PowerShell is Windows-centric.
- If possible, note that PowerShell Core is available cross-platform, but most users on Linux/macOS will use Azure CLI.
- Ensure that CLI examples use variables and syntax compatible with Bash as well as Windows CMD.
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
Windows Tools
Summary
The documentation provides backup and disaster recovery guidance for Azure Managed Disks on both Linux and Windows VMs. However, in several places, Windows tools and patterns (such as Volume Shadow Service for application-consistent snapshots) are mentioned first or exclusively, with Linux equivalents (like fsfreeze) referenced secondarily and with less detail. SQL Server (a Windows-centric example) is highlighted more than Linux database solutions. Overall, Linux is supported, but Windows examples and tools are prioritized.
Recommendations
- Provide equal detail for Linux tools (e.g., elaborate on fsfreeze usage and limitations, and mention other Linux backup coordination tools such as LVM snapshots or application-specific solutions).
- Include Linux-first examples in backup scenarios, such as PostgreSQL or MySQL running on Linux VMs, and describe their backup strategies.
- When discussing application-consistent backups, clarify the limitations for Linux and suggest best practices or third-party solutions for Linux workloads.
- Balance the mention of Windows and Linux tools/patterns in each section, ensuring Linux solutions are not secondary.
- Add links to Linux-specific documentation or guides for backup and disaster recovery.
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 details before Linux, but provides parity in information for both platforms. No Windows-specific tools, examples, or patterns are prioritized elsewhere, and Linux support is clearly described. No critical sections are Windows-only, and Linux users can fully understand and use VM restore points.
Recommendations
- Consider listing Linux operating system support before or alongside Windows to avoid implicit prioritization.
- Ensure future updates maintain parity in detail and clarity for both Windows and Linux sections.
- If CLI or PowerShell examples are provided elsewhere, ensure Linux shell (bash) examples are also included.
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 for Azure Managed Disk encryption, but there is a consistent pattern of Windows/PowerShell examples and links being presented before Linux/CLI equivalents. References to PowerShell are frequent and often appear first in lists, while Linux/CLI links are included but secondary. No critical steps are Windows-only, and Linux parity is generally maintained, but the ordering and emphasis may create friction for Linux users.
Recommendations
- Alternate the order of Windows/PowerShell and Linux/CLI examples and links so Linux users are not always presented second.
- Explicitly state that all features and procedures are supported on both Linux and Windows VMs at the start of the article.
- Where possible, provide combined examples or parallel instructions for both platforms in the same section.
- Ensure that references to tools (PowerShell, CLI) are balanced and not disproportionately focused on Windows/PowerShell.
- Consider adding a summary table or section that clearly maps procedures to both Windows and Linux environments.
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 focused on Linux VM extensions, but consistently presents both Azure CLI and Azure PowerShell examples side-by-side. In several sections, PowerShell examples are given equal prominence to CLI, despite PowerShell being primarily a Windows-centric tool. In some cases, PowerShell examples are shown before or alongside CLI, which may create friction for Linux users. However, all examples and guidance are applicable to Linux, and Linux-specific tools (Azure CLI, Bash, waagent) are well represented.
Recommendations
- Consider presenting Azure CLI examples first in each section, as CLI is the primary cross-platform tool for Linux users.
- Clearly indicate that PowerShell is optional and primarily for users on Windows or those who have installed PowerShell Core on Linux.
- Add explicit notes or guidance for Linux users about the recommended tooling (Azure CLI, Bash) and clarify PowerShell's cross-platform status.
- Where possible, minimize PowerShell examples or move them to secondary tabs/sections for Linux-focused documentation.
- Ensure that troubleshooting and operational guidance always includes Bash/CLI commands as the default for Linux.
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 thorough Linux-specific guidance. However, the introductory section discusses Windows Server 2016 time sync improvements and references Windows documentation before explaining Linux mechanisms. All configuration and command examples are Linux-centric, and Linux tools (chrony, ntpd, systemd-timesyncd, cloud-init) are covered in detail. The only minor bias is the Windows context and links appearing first, which may confuse readers expecting Linux-only content.
Recommendations
- Move the Windows Server 2016 discussion and links to a background or 'Azure host infrastructure' section, clarifying that this is context for Azure hosts, not for Linux VM configuration.
- Add a brief statement at the start explaining that while Azure hosts use Windows Server 2016 for time sync, this page is focused on Linux VM configuration.
- Ensure Linux-specific guidance is presented before any Windows context to reinforce the Linux focus.
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 minor signs of Windows bias. In several sections, Azure PowerShell deployment instructions and troubleshooting commands are presented before their Azure CLI equivalents, despite CLI being more cross-platform and native to Linux. PowerShell is referenced heavily, and warnings about PowerShell-specific issues are included, even though Linux users are unlikely to use PowerShell. However, all examples and instructions are ultimately Linux-centric, and Linux tools and paths are consistently used.
Recommendations
- Present Azure CLI instructions before Azure PowerShell in deployment and troubleshooting sections, as CLI is native to Linux.
- Clarify that PowerShell instructions are optional for Linux users and highlight Azure CLI as the recommended method.
- Reduce PowerShell-specific warnings or move them to a dedicated section for users who choose PowerShell on Linux.
- Ensure all troubleshooting and deployment examples are available and prioritized for Azure CLI.
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 CLI or Portal. However, the PowerShell example is included alongside CLI and REST, which are cross-platform, but PowerShell is primarily a Windows-centric tool. The CLI examples are shown before PowerShell, and there are no Windows-specific tools or patterns mentioned exclusively. There is minor bias in the inclusion of PowerShell, but Linux parity is maintained through CLI and REST examples.
Recommendations
- Clarify that PowerShell is primarily for Windows users, and recommend Azure CLI for cross-platform usage.
- Consider adding notes for macOS/Linux users about PowerShell Core compatibility if relevant.
- Ensure that CLI examples are always presented before PowerShell to reinforce cross-platform parity.
- Explicitly mention that Azure CLI and REST API are fully supported on Linux/macOS.
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 primarily a changelog/news summary for Azure Disk Storage features and enhancements. While most content is platform-neutral, there are a few instances where Windows-related links or terminology are presented before Linux equivalents, and references to Windows tools (e.g., Azure PowerShell) are made without equal mention of Linux alternatives. For example, in the 'Live Resize' feature, the link points to a Windows-specific article, and in disk conversion and expansion, Windows documentation is listed before Linux. The 'LastOwnershipUpdateTime' property mentions Azure PowerShell and Azure CLI, but only links to Windows documentation.
Recommendations
- Ensure that links to Linux documentation are provided alongside Windows documentation, especially for features that are not Windows-specific.
- When referencing tools, mention both Azure PowerShell and Azure CLI equally, and clarify their cross-platform availability.
- Present Linux and Windows examples in parallel, or alternate their order to avoid implicit prioritization.
- Where possible, include macOS guidance if relevant.
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 and Azure PowerShell examples for creating instant access snapshots, but the PowerShell example is given equal prominence to the CLI example and is presented immediately after it. There is no explicit Linux/macOS bias, but the ordering and inclusion of PowerShell (a Windows-centric tool) alongside CLI may subtly favor Windows users. All examples use cross-platform tools (Azure CLI, ARM templates), but PowerShell is still primarily used on Windows. No Linux-specific commands, tools, or troubleshooting are provided.
Recommendations
- Present Azure CLI examples first, as CLI is cross-platform and more accessible to Linux/macOS users.
- Explicitly note that Azure CLI works on Linux/macOS and provide links to installation instructions for those platforms.
- Consider including Bash shell scripting examples for disk snapshot operations, especially for automation scenarios.
- Add troubleshooting tips or notes for Linux/macOS users if there are known issues or differences.
- Clarify that PowerShell is available cross-platform, but highlight CLI as the default for Linux/macOS environments.
Virtual Machines
Secure Azure Managed Disk Downloads and Uploads
...icles/virtual-machines/disks-secure-upload-download.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for securing managed disk uploads/downloads, but PowerShell (a Windows-centric tool) is presented before CLI in several sections. References to role assignment and policy assignment also list PowerShell before CLI. However, Linux-specific links and CLI examples are present, and the documentation is not Windows-only.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and more accessible to Linux/macOS users.
- Explicitly mention that Azure CLI commands work on Linux/macOS, and consider adding Bash shell examples where relevant.
- Ensure parity in screenshots and UI descriptions for portal steps, noting any OS-specific differences.
- Review linked articles to confirm Linux/macOS users are not directed to Windows-only instructions.
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, but provides parity in listing supported Linux distributions and requirements. No Windows-specific tools, examples, or patterns are favored. Both Windows and Linux are covered in the support matrix and limitations. The 'Next steps' section references CLI, Portal, and PowerShell, but does not prioritize Windows tools.
Recommendations
- Consider listing Linux operating system support before or alongside Windows to avoid perceived prioritization.
- Ensure that CLI and PowerShell guidance is equally accessible and that Linux-specific examples are included in linked pages.
- Explicitly mention macOS where relevant, or clarify if only Linux and Windows are supported.
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 focused on Linux VM extensions, but consistently presents Azure PowerShell examples alongside Azure CLI, sometimes listing PowerShell examples before CLI or giving them equal prominence. There are no missing Linux examples, but the frequent inclusion of PowerShell commands (which are more commonly used on Windows) may create friction for Linux users, especially since Azure CLI is the more native tool for Linux environments. The documentation does not reference Windows tools or patterns exclusively, and all examples are applicable to Linux VMs.
Recommendations
- Prioritize Azure CLI examples before Azure PowerShell in all sections, as CLI is the default for Linux users.
- Consider marking PowerShell examples as 'optional' or 'for cross-platform users' to clarify their relevance.
- Add brief notes explaining that Azure PowerShell can be used on Linux, but Azure CLI is recommended for native Linux workflows.
- Where possible, include Bash shell script examples for common tasks (e.g., checking agent version, troubleshooting) to further support Linux users.
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, but includes PowerShell examples for deploying the extension and troubleshooting, even though PowerShell is primarily a Windows tool. The PowerShell example is presented before the Azure CLI example, which is more commonly used on Linux. However, all core instructions and examples are provided for Linux, and Linux-specific tools and commands are included throughout.
Recommendations
- Move Azure CLI examples before PowerShell examples, as CLI is the primary cross-platform tool for Linux users.
- Clarify that PowerShell examples are optional and mainly for users who prefer PowerShell on Linux or are working in cross-platform environments.
- Consider adding Bash script examples for deployment and troubleshooting, as Bash is native to Linux.
- Explicitly state that Azure CLI is recommended for Linux users.
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 comprehensive Linux-specific guidance. However, there is evidence of Windows bias in the deployment and troubleshooting sections: PowerShell examples are presented before Azure CLI examples, and PowerShell is referenced as a primary tool for deployment and troubleshooting, despite Linux users typically preferring Azure CLI or shell scripting. There are also warnings and notes about PowerShell-specific issues, which may not be relevant for Linux users.
Recommendations
- Present Azure CLI examples before PowerShell examples, as CLI is more commonly used on Linux.
- Clearly indicate which sections are relevant for Windows users and which are for Linux users, especially in troubleshooting.
- Add Bash shell scripting examples for deployment and troubleshooting, or clarify that Azure CLI commands are cross-platform.
- Reduce PowerShell-specific warnings or move them to a dedicated Windows section.
- Ensure all example commands use Linux-appropriate syntax (e.g., avoid PowerShell backticks in Azure CLI examples).
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 a PowerShell example for marking the VM as generalized, while the Linux section uses Azure CLI. The Windows section also appears after the Linux section, but the PowerShell example is not matched with an Azure CLI equivalent for Windows. The Linux section is comprehensive and includes links to distro-specific guides, but the Windows section could benefit from parity in Azure CLI usage.
Recommendations
- Add Azure CLI examples for Windows VM generalization alongside the PowerShell example, so Windows users can use either tool.
- Ensure that both Linux and Windows sections provide equivalent steps for marking the VM as generalized, using both Azure CLI and PowerShell where appropriate.
- Consider listing both Linux and Windows examples in parallel or in a table for easier comparison.
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, examples, and tooling. However, the introductory section discusses Windows Server 2016 improvements and references Windows documentation before Linux-specific details, which may create a minor perception of Windows bias. All configuration examples, commands, and tools are Linux-centric, with only a single PowerShell snippet for base64 encoding cloud-init (which is relevant for Azure ARM templates, not VM configuration). No critical Linux examples are missing, and Linux tools are prioritized throughout.
Recommendations
- Move Windows Server 2016 discussion and references to a background or context section, or clarify that it's for Azure host infrastructure only.
- Add a brief summary at the start emphasizing that the guide is Linux-focused and all examples are for Linux VMs.
- Replace the PowerShell base64 example with a Linux equivalent (e.g., 'base64 cloud-config.txt') or provide both Windows and Linux options.
- Ensure that Linux documentation links are as prominent as Windows links in the 'Next steps' 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 both Linux and Windows guidance, but in several places Windows terminology, tools, and examples are presented first or more prominently. PowerShell examples are included alongside CLI and REST, but Windows-specific terms (e.g., Sysprep) are mentioned before Linux equivalents. The PowerShell section uses Windows as the default in its example, while the CLI section uses Linux. Overall, Linux parity is good, but Windows is sometimes prioritized in ordering and example selection.
Recommendations
- Alternate the order of Windows and Linux examples to avoid implicit prioritization.
- In PowerShell sections, provide Linux examples as the default or alongside Windows examples.
- Ensure that both Linux and Windows terminology are introduced together, e.g., mention 'waagent -deprovision' and 'Sysprep' in the same sentence.
- Review example ordering to avoid always showing Windows first.
- Add explicit notes clarifying parity between Linux and Windows where applicable.
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 enabling Azure Disk Encryption for Linux VMs and provides Linux-centric instructions and examples. However, there are minor instances of Windows bias: PowerShell is mentioned alongside Azure CLI as a management tool, and PowerShell examples/scripts are referenced in the 'Next steps' section before or alongside Linux CLI equivalents. The 'Terminology' table includes 'PowerShell cmdlets' as a term, even though the primary audience is Linux users.
Recommendations
- In the 'Terminology' section, clarify that PowerShell can be used cross-platform, or consider omitting it if not directly relevant to Linux VM management.
- In the 'Next steps' section, list Azure CLI quickstart and scripts before PowerShell equivalents to prioritize Linux-native tools.
- Where PowerShell is referenced, explicitly note its cross-platform support or provide context for Linux users who may prefer CLI/bash.
- Ensure that all examples and scripts for Linux VM management are available in bash/CLI, and PowerShell is presented as an optional alternative.
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). However, Windows tools and patterns (Hyper-V Manager, Windows-centric terminology) are presented first in each major section and tab, and instructions for using Hyper-V Manager are often more detailed and prominent. Linux-native hypervisors (KVM, VMware on Linux, Kickstart) are covered thoroughly, but their sections appear after Hyper-V and are sometimes referenced as secondary. There are no missing Linux examples or PowerShell-heavy instructions; all critical steps are provided for Linux users.
Recommendations
- Reorder sections so Linux-native hypervisors (KVM, VMware on Linux, Kickstart) are presented before or alongside Hyper-V instructions, rather than after.
- Add a brief summary or table at the top outlining parity and equivalence between Windows and Linux workflows.
- Clarify that all workflows are equally supported and that Hyper-V is not required for Linux VHD creation.
- Where possible, avoid referencing Windows tools (Hyper-V Manager) as the default or primary method.
- Ensure that Linux-native terminology is used consistently and that Linux instructions are not dependent on Windows tools.
Virtual Machines
Migrate from Amazon Elastic Compute Cloud (Amazon EC2) to Azure Virtual Machines
...ion/migrate-from-elastic-compute-cloud-architecture.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides migration guidance from Amazon EC2 to Azure Virtual Machines and covers both Windows and Linux workloads in a generic manner. However, in sections discussing image generalization and agent installation, Windows-specific instructions (Sysprep) are mentioned first, while Linux instructions (waagent) are secondary. There are no explicit Linux command-line examples or Linux-specific migration tooling details, and some steps (such as image customization) could benefit from more Linux-focused guidance. The bias is minor and does not prevent Linux users from completing the migration, but it creates slight friction due to lack of parity in examples and ordering.
Recommendations
- Provide Linux-specific migration examples and command-line instructions (e.g., using Azure CLI, shell scripts, or Linux tools) alongside Windows/PowerShell equivalents.
- Ensure Linux agent installation and image generalization steps are described with equal prominence and detail as Windows Sysprep.
- Include references to Linux migration tooling (such as cloud-init, waagent configuration, or Linux image builder pipelines) where relevant.
- Where possible, show Linux examples first or in parallel with Windows examples to reinforce parity.