Virtual Machines
2112
Total Pages
1865
Linux-Friendly Pages
247
Pages with Bias
11.7%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
818 issues found
Showing 776-800 of 818 flagged pages
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Windows and Linux parity for the core installation steps, with CLI and ARM template examples that apply to both platforms. However, there is a subtle Windows bias: Windows screenshots are shown before Linux ones, and PowerShell examples (Windows-centric) are provided alongside CLI and ARM template, but no Linux shell-specific examples (e.g., Bash scripting) are included. The quickstart links for VM creation are presented with Windows first, then Linux. No critical Linux functionality is missing, but the ordering and example types favor Windows.
Recommendations
- Alternate the order of Windows and Linux screenshots, or present them side-by-side.
- Provide Bash shell scripting examples for Linux users alongside PowerShell examples.
- Present quickstart links for Windows and Linux together, or alternate their order.
- Explicitly state that CLI and ARM template examples are cross-platform and suitable for Linux/macOS users.
- Consider adding a Linux/macOS validation workflow (e.g., using SSH or Bash) for confirming extension installation.
Create Pull Request
Virtual Machines
Azure Instance Metadata Service for virtual machines
...articles/virtual-machines/instance-metadata-service.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Windows (PowerShell) and Linux (bash/curl) examples for all major usage scenarios, but consistently lists Windows/PowerShell examples before Linux equivalents. Troubleshooting and routing table sections also show Windows commands and outputs first, and use PowerShell for Azure CLI examples, even in Linux sections. There is a slight emphasis on Windows tools (PowerShell, route print, ipconfig) and patterns, with Linux alternatives provided but sometimes as secondary. No critical Linux gaps are present; all tasks can be completed on Linux.
Recommendations
- Alternate the order of Windows and Linux examples, or present Linux examples first in sections marked as 'linux-related-content'.
- Use cross-platform Azure CLI examples (az CLI) instead of PowerShell CLI in Linux troubleshooting sections.
- Where possible, provide more detailed Linux troubleshooting steps and outputs, matching the depth of Windows sections.
- Explicitly mention macOS compatibility in Linux examples, or provide macOS-specific notes where command syntax may differ.
- Review sample code and links to ensure parity in language and platform support.
Low Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation provides both Linux/macOS and Windows-specific instructions for connecting to a Linux VM via SSH. While Linux instructions are thorough and presented first, the Windows section relies heavily on PowerShell/Azure PowerShell for certain operations (such as obtaining the host fingerprint via the portal), and references Windows-specific tools (cmd.exe, PowerShell). There is a slight bias in that the Windows tab uses Azure PowerShell for host fingerprint validation, whereas the Linux tab uses direct SSH commands. However, both platforms are covered with parity in most core steps.
Recommendations
- Provide a direct, non-PowerShell method for Windows users to obtain the host fingerprint, such as using PuTTY or Windows-native OpenSSH.
- Include examples for popular Windows SSH clients (e.g., PuTTY) alongside PowerShell/cmd.exe.
- Clarify that Windows 10 and later include OpenSSH, and show how to use it in cmd.exe or PowerShell without requiring Azure PowerShell.
- Ensure troubleshooting steps and links are equally accessible and detailed for both platforms.
- Consider listing Linux/macOS instructions before Windows only if the majority of users are expected to be on those platforms, otherwise present both tabs equally.
Virtual Machines
Enable Azure Disk Encryption for Linux VMs
...les/virtual-machines/linux/disk-encryption-overview.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation is focused on enabling Azure Disk Encryption for Linux VMs and is generally Linux-centric. However, there is evidence of Windows bias in the form of frequent references to PowerShell and Azure PowerShell cmdlets, with PowerShell examples and quickstarts mentioned alongside (and sometimes before) Azure CLI equivalents. The 'Next steps' section lists both CLI and PowerShell quickstarts, and the terminology table includes 'PowerShell cmdlets' as a primary concept, despite the Linux focus. There are no missing Linux examples or exclusive references to Windows tools, but the prominence of PowerShell may create friction for Linux users who prefer native Linux tooling.
Recommendations
- Prioritize Azure CLI examples and quickstarts before PowerShell in all lists and sections, as CLI is more native to Linux environments.
- Clarify that PowerShell is cross-platform, but emphasize CLI as the recommended approach for Linux users.
- Remove or de-emphasize 'PowerShell cmdlets' from the terminology table unless specifically relevant to Linux users.
- Ensure that all scripts and examples are available in Bash/CLI format, and highlight these as the default for Linux documentation.
- Add a note explaining the differences between CLI and PowerShell usage on Linux, and recommend CLI for most users.
Virtual Machines
Expand Virtual Hard Disks on a Linux VM
...b/main/articles/virtual-machines/linux/expand-disks.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Summary
The documentation is strongly focused on Linux, with all operational examples and procedures using Linux commands and tools. However, a single section at the end provides a PowerShell script for checking classic VM SKU support for expanding disks without downtime, with no equivalent Bash/Azure CLI example for Linux users.
Recommendations
- Provide an equivalent Bash/Azure CLI script for Linux users to check classic VM SKU support for expanding disks without downtime.
- Clarify whether the PowerShell script is only necessary for Windows users, or if Linux users should use an alternative method.
- If the check is relevant for Linux VM administrators, ensure parity by offering platform-agnostic or Linux-native instructions.
Virtual Machines
Configure LVM and RAID on encrypted devices - Azure Disk Encryption
...l-machines/linux/how-to-configure-lvm-raid-on-crypt.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both PowerShell and Azure CLI examples for VM deployment, disk attachment, and encryption steps, with PowerShell (Windows) examples consistently presented first. However, all OS-level configuration, LVM, and RAID instructions are Linux-specific, and no Windows-only tools or patterns are used for the core storage management tasks. The overall bias is minor and limited to the ordering and prominence of Windows-centric Azure management commands.
Recommendations
- Present Azure CLI (Linux/macOS-friendly) examples before PowerShell examples, or alternate the order to avoid implicit prioritization.
- Explicitly state that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Consider grouping Azure CLI and PowerShell examples together, or use tabs to allow users to select their preferred environment.
- Add a brief note clarifying that PowerShell examples are for users on Windows, while Azure CLI is recommended for Linux/macOS.
Virtual Machines
Verify encryption status for Linux - Azure Disk Encryption
...tual-machines/linux/how-to-verify-encryption-status.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
Although the documentation is targeted at Linux VMs, the PowerShell section is presented before the Azure CLI section, and PowerShell examples are extensive and detailed. This ordering and emphasis may create friction for Linux users, who are more likely to use Bash and Azure CLI. However, Linux-native commands (lsblk, cryptsetup) and Azure CLI examples are present and comprehensive, so Linux users can still complete all tasks.
Recommendations
- Move the Azure CLI section before the PowerShell section to prioritize Linux-friendly tooling.
- Add a note clarifying that PowerShell examples are primarily for users managing Linux VMs from Windows or cross-platform environments.
- Consider reducing the length and detail of PowerShell examples, or providing parity in Azure CLI/Bash examples.
- Explicitly state that all Azure CLI commands are intended for Bash or Linux shell environments.
- Highlight Linux-native commands and workflows (lsblk, cryptsetup) earlier in the document.
Virtual Machines
Quickstart - Create a Linux VM in the Azure portal
...articles/virtual-machines/linux/quick-create-portal.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Windows (PowerShell) and Linux/macOS (Bash) instructions for connecting to the VM via SSH, but Windows/PowerShell is mentioned first. The only explicit tool mentioned for Windows is PowerShell, while Bash is referenced for Linux/macOS. There are no missing Linux examples, and the overall flow is Linux-focused, but the order and explicit mention of PowerShell create minor Windows bias.
Recommendations
- Present Bash (Linux/macOS) and PowerShell (Windows) instructions in parallel or in tabs, rather than listing Windows first.
- Explicitly mention common Linux terminal emulators (e.g., GNOME Terminal, Konsole) and macOS Terminal when referencing Bash.
- Consider providing screenshots for both Windows and Linux/macOS terminal environments.
- Clarify that the SSH command works identically across platforms, and highlight any platform-specific steps (e.g., setting file permissions) in a dedicated section.
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation is primarily focused on Linux, but there are instances where Windows tools and patterns are mentioned before or in addition to Linux equivalents. Specifically, SSH usage from Windows is highlighted with a dedicated link, and Azure PowerShell examples (Windows-centric) are provided alongside Azure CLI. The reference to the Azure portal for creating NSG rules links to a Windows-specific quickstart. These sections may create minor friction for Linux/macOS users.
Recommendations
- Provide equivalent guidance for SSH usage from Linux/macOS, not just Windows.
- When referencing Azure portal documentation, link to Linux-specific or neutral guides rather than Windows-specific ones.
- Present Azure CLI (cross-platform) examples before Azure PowerShell (Windows-centric) examples, or clarify platform applicability.
- Ensure troubleshooting and next steps include parity for Linux/macOS users where Windows-specific instructions are given.
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
Windows Reference
Powershell Example
Summary
The documentation is focused on Linux VM time sync in Azure and provides thorough Linux-specific guidance and examples. However, it repeatedly references Windows Server 2016 improvements and links to Windows documentation before or in parallel with Linux explanations. There is a PowerShell example for base64 encoding cloud-init, but no Linux shell equivalent. The page does not provide Windows-only instructions, but Windows context and tooling are mentioned first or exclusively in some places.
Recommendations
- Move Windows-specific context and references to a background or separate section, focusing the main content on Linux.
- Provide a Linux shell (e.g., base64) example for encoding cloud-init, not just PowerShell.
- When referencing time sync improvements, highlight Linux-specific mechanisms first, and only mention Windows as underlying infrastructure if necessary.
- Ensure all examples and tooling instructions are available for Linux users, especially for tasks like ARM template preparation.
- Add parity in cross-references: link to Linux time sync documentation as prominently as Windows references.
Virtual Machines
Scheduled Events for Linux VMs in Azure
...in/articles/virtual-machines/linux/scheduled-events.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation is generally Linux-focused and provides Bash and Python examples, but PowerShell samples are consistently presented alongside or immediately after Bash, and in some cases before Python. In the 'Query for events' and 'Start an event' sections, PowerShell is given equal prominence to Bash, despite PowerShell being a Windows-centric tool (even though it is available on Linux, Bash is far more common in Linux environments). There is a slight 'windows_first' bias in the order of links and references, such as the 'Platform initiated maintenance' link using Windows breadcrumbs/toc, and PowerShell examples being shown before Python. No critical Linux examples are missing, and all tasks can be completed using Linux-native tools.
Recommendations
- Present Bash examples first in all code sample sections, followed by Python, and then PowerShell (if included at all).
- Clarify that PowerShell is optional and less common on Linux, and recommend Bash for Linux users.
- Ensure all internal links and breadcrumbs reference Linux documentation first when the page is Linux-focused.
- Consider adding more Linux-native tool examples (e.g., using wget or other CLI utilities) if relevant.
- Explicitly state that PowerShell is cross-platform but Bash is the default for Linux.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias by consistently listing Windows tools (PowerShell) before Linux equivalents (CLI), referencing 'Scheduled Events for Windows' before Linux, and providing links to Windows-specific pages first. There are no explicit Linux command examples or Linux-first instructions, and PowerShell is mentioned as a primary tool for managing maintenance, which may create friction for Linux users.
Recommendations
- Alternate the order of CLI and PowerShell references so that Linux tools are sometimes listed first.
- Provide explicit Linux command examples and walkthroughs, not just links.
- Ensure that references to 'Scheduled Events' and other features mention Linux and Windows equally, or use neutral phrasing.
- Add direct links to Linux-specific documentation where appropriate, and clarify parity between Windows and Linux features.
- Consider including bash or shell script examples alongside PowerShell.
Virtual Machines
Export an image version to a managed disk
...es/virtual-machines/managed-disk-from-image-version.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents both Azure CLI and PowerShell examples for exporting an image version to a managed disk. However, the PowerShell section is given equal prominence to the CLI, despite PowerShell being primarily a Windows-centric tool. The CLI examples use Bash-style syntax, which is cross-platform, but the PowerShell examples are detailed and extensive, potentially signaling a Windows-first approach. There are no Linux-specific tools or shell examples (e.g., Bash scripts), nor is there any mention of macOS. The CLI section is presented first, which helps mitigate bias, but the inclusion and detail of PowerShell examples may create friction for Linux/macOS users unfamiliar with PowerShell.
Recommendations
- Clarify that Azure CLI commands work on Linux, macOS, and Windows, and are the recommended cross-platform approach.
- Consider adding Bash script examples or notes for Linux/macOS users.
- Explicitly state PowerShell is optional and primarily for Windows users.
- Add a note about Azure CLI installation and usage on Linux/macOS.
- Ensure parity in example depth and explanation between CLI and PowerShell sections.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation presents the Windows ARM template example before the Linux example, despite both being equally supported. No Windows-specific tools, PowerShell commands, or exclusive patterns are present, and both platforms have full template parity. However, the ordering may subtly signal a Windows preference.
Recommendations
- Present Windows and Linux examples in parallel or alternate the order in different sections.
- Explicitly state that both Windows and Linux are equally supported.
- Consider adding a summary table comparing key differences between the templates for both platforms.
Virtual Machines
Azure Dedicated Host SKU Retirement Migration Guide
...l-machines/migration/dedicated-host-migration-guide.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides examples for stopping and starting VMs using PowerShell, CLI, and Portal. PowerShell (a Windows-centric tool) is listed first in each case, followed by CLI and Portal. No explicit Linux/macOS bias is present, but the ordering gives Windows tools priority, which may subtly signal preference for Windows users.
Recommendations
- Rotate the order of example tabs so CLI (cross-platform) appears first, or list CLI before PowerShell to emphasize platform neutrality.
- Explicitly state that Azure CLI works on Windows, Linux, and macOS, and provide installation links for each platform.
- Add brief notes or links for Bash scripting or other Linux-native tools if relevant.
- Ensure that all referenced commands and guides are equally accessible and clear for Linux/macOS users.
Virtual Machines
Monitor Azure Virtual Machines
...docs/blob/main/articles/virtual-machines/monitor-vm.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias. Windows terminology (e.g., 'Windows events', IIS logs) is mentioned before Linux equivalents (Syslog, SNMP), and Windows-specific tools (Performance Diagnostics, IIS logs) are highlighted. The troubleshooting section links primarily to Windows documentation, and examples or recommendations often mention Windows first or in more detail. Linux is supported, but coverage is less detailed and sometimes secondary.
Recommendations
- Ensure Linux examples and terminology (e.g., Syslog, SNMP, Apache/Nginx logs) are presented alongside or before Windows equivalents.
- Provide equal detail for Linux troubleshooting tools and workflows, including direct links to Linux-specific documentation.
- Include Linux/macOS screenshots and walkthroughs in sections describing portal or agent onboarding.
- Clarify parity in supported features (e.g., which logs, metrics, and diagnostics are available for Linux VMs).
- Add explicit examples for configuring monitoring and alerts on Linux VMs, not just Windows.
Virtual Machines
Move a maintenance configuration to another Azure region
...tual-machines/move-region-maintenance-configuration.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation repeatedly mentions PowerShell before CLI when describing how to create, assign, and delete maintenance configurations. This ordering subtly prioritizes Windows tooling. However, CLI examples are present and shown in detail, including in the main workflow, which supports Linux/macOS users. No exclusively Windows-only tools or missing Linux examples are found.
Recommendations
- List CLI before PowerShell in instructions, as CLI is cross-platform and preferred by many Linux/macOS users.
- Explicitly note that CLI commands work on Linux/macOS and Windows.
- Add Bash or shell script examples where appropriate to further support Linux users.
- Consider a dedicated section for Linux/macOS users if any platform-specific caveats exist.
Virtual Machines
Overview of virtual machines in Azure
...e-docs/blob/main/articles/virtual-machines/overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation generally maintains parity between Windows and Linux, but there are several instances of Windows bias. PowerShell is frequently mentioned and listed before Azure CLI in tables describing how to query locations and VM images, and Windows tools (PowerShell) are often referenced alongside or before Linux-friendly tools (CLI). Some examples and instructions are presented in a Windows-first order, and PowerShell is sometimes given more detailed coverage than CLI. However, Linux-specific sections and links are present, and Linux is clearly supported.
Recommendations
- List Azure CLI and Linux examples before or alongside PowerShell examples in tables and instructions.
- Ensure that all examples and instructions are provided for both CLI and PowerShell, with equal detail.
- Highlight Linux-specific management tools and workflows where relevant.
- Add explicit Linux/macOS command-line examples where only PowerShell is shown.
- Review ordering in tables and lists to avoid consistently putting Windows/PowerShell first.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for checking vCPU quotas, but the PowerShell example is presented second and is Windows-specific. There is a slight bias towards Windows by including PowerShell as a dedicated example tab, which is only relevant for Windows users, while Linux/macOS users are limited to the Azure CLI. No Linux-specific tools or shell examples are given, and PowerShell is presented as an equal alternative despite its platform specificity.
Recommendations
- Explicitly note that PowerShell is Windows-only and Azure CLI is cross-platform.
- Add Bash or shell script examples for Linux/macOS users where relevant.
- Consider listing CLI examples first, as they are cross-platform.
- If PowerShell Core is supported on Linux/macOS, clarify this and provide installation instructions or usage notes.
Virtual Machines
Isolated Image Builds for Azure VM Image Builder
...chines/security-isolated-image-builds-image-builder.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation page demonstrates mild Windows bias primarily in its instructions for registering the Microsoft.ContainerInstance provider, where both Azure CLI and PowerShell commands are given, but PowerShell is mentioned second. The use of PowerShell as an example tool and the lack of explicit Linux shell (bash) or macOS instructions may create minor friction for non-Windows users. However, the rest of the documentation is platform-neutral, focusing on Azure concepts and resources without OS-specific tooling or examples.
Recommendations
- Include bash (Linux/macOS) equivalents for all command-line instructions, especially for resource provider registration.
- Explicitly mention that Azure CLI works cross-platform and provide examples for Linux/macOS users.
- Where PowerShell is referenced, clarify its availability on Linux/macOS or provide alternative commands.
- Review troubleshooting and best practices links to ensure Linux/macOS parity in examples and instructions.
Virtual Machines
Share Resources in Azure Compute Gallery
...s/blob/main/articles/virtual-machines/share-gallery.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides examples for Azure Portal, Azure CLI, and PowerShell. While Azure CLI is cross-platform, PowerShell is primarily associated with Windows, and its inclusion as a dedicated example may signal a Windows bias. Additionally, PowerShell examples are given equal prominence to CLI, and there are no Linux/macOS-specific shell examples (e.g., Bash scripts), nor is there mention of Linux-specific considerations. The ordering of examples (Portal, CLI, then PowerShell) is standard, but the presence of PowerShell without a Linux shell equivalent suggests a mild Windows bias.
Recommendations
- Add explicit Bash or shell script examples for Linux/macOS users, especially for tasks involving Azure CLI.
- Clarify that Azure CLI commands work on Linux/macOS and Windows equally.
- Consider mentioning cross-platform compatibility in the introduction to reassure non-Windows users.
- If PowerShell is included, note that PowerShell Core is available on Linux/macOS, or provide equivalent Bash commands.
Virtual Machines
Dldsv6 size series (Preview)
...irtual-machines/sizes/general-purpose/dldsv6-series.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page is largely platform-neutral, focusing on VM specifications and features. However, the only specific tooling mentioned for network performance testing is NTTTCP, a Microsoft-developed tool that is primarily Windows-focused (though it does have a Linux port, this is not mentioned). Additionally, the link for nested virtualization support points to a Windows/Hyper-V guide, with no mention of KVM or Linux equivalents. No Linux/macOS-specific tools or examples are provided, and Windows references appear first or exclusively in these cases.
Recommendations
- Explicitly mention Linux-compatible tools for bandwidth testing, such as iperf3, and provide links to their usage.
- For nested virtualization, clarify Linux support and link to relevant KVM documentation if supported.
- Where tooling is referenced, provide both Windows and Linux/macOS options, or clarify cross-platform availability.
- Add notes or examples for Linux/macOS users where applicable, especially in sections referencing tools or features that may differ by OS.
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page is generally platform-neutral, focusing on VM size specifications and features. However, there is mild Windows bias in the 'Feature support' section, where 'Nested Virtualization' links only to a Windows/Hyper-V guide, and in the 'Network' section, where bandwidth testing references NTTTCP, a tool originally developed for Windows. There are no Linux-specific examples, tools, or links, and Windows terminology appears first or exclusively in these contexts.
Recommendations
- Include links or references to Linux/KVM nested virtualization documentation if supported or clarify if only Windows is supported.
- Mention Linux-compatible bandwidth testing tools (e.g., iperf, netperf) alongside NTTTCP, and provide relevant links.
- Where features/tools are Windows-only, explicitly state Linux support status to avoid ambiguity.
- Add Linux-specific optimization guidance or examples where relevant.
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page is largely platform-neutral, focusing on VM specifications and features. However, there is mild Windows bias in the 'Feature support' section, where 'Nested Virtualization' links to a Windows-specific (Hyper-V) guide, and in the 'Bandwidth/Throughput testing' section, which references NTTTCP—a Microsoft tool most commonly used on Windows. No Linux-specific examples, tools, or links are provided, and Windows tools/patterns are mentioned before Linux equivalents (if any).
Recommendations
- Include links to Linux-specific nested virtualization documentation (e.g., KVM/QEMU guides) alongside the Windows Hyper-V link.
- Mention and link to Linux-compatible network throughput testing tools (e.g., iperf, netperf) in the networking section.
- Ensure that any referenced tools or guides are available and documented for both Windows and Linux platforms.
- Where features differ by OS (e.g., disk encryption), provide clear guidance and parity in documentation for both Windows and Linux users.
Virtual Machines
NC_RTXPRO6000BSE_v6 size series
...s/sizes/gpu-accelerated/nc-rtxpro6000-bse-v6-series.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page is largely neutral and platform-agnostic, focusing on VM sizes and hardware specifications. However, there is mild Windows bias in the 'Feature support' section, which links to Windows-specific nested virtualization documentation before mentioning Linux, and in the networking sections, which reference NTTTCP (a Windows tool) for bandwidth testing without mentioning Linux alternatives. No command-line examples are present, so there is no Powershell or CLI bias.
Recommendations
- When referencing tools like NTTTCP, explicitly mention Linux alternatives (e.g., iperf, netperf) and provide links to relevant documentation.
- In feature support lists, present Windows and Linux features in parallel, or mention Linux first where appropriate.
- If discussing nested virtualization, include links to both Windows and Linux guides, or clarify platform applicability.
- Ensure that any future examples or instructions include both Windows and Linux variants.