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 701-725 of 818 flagged pages
Virtual Machines
Prepare Linux for imaging
...ticles/virtual-machines/linux/create-upload-generic.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page is focused on preparing Linux for imaging in Azure, but it exhibits some Windows bias in the sections discussing disk conversion and resizing. Windows tools (Hyper-V Manager, Convert-VHD, Resize-VHD PowerShell cmdlets) are mentioned first and in detail, with Linux alternatives (qemu-img, vbox-manage) presented afterward. The explanations and examples for Linux tools are present and fairly comprehensive, but the initial framing and tool recommendations prioritize Windows environments.
Recommendations
- Present Linux-native tools (qemu-img, vbox-manage) before or alongside Windows tools when discussing disk conversion and resizing.
- Provide explicit step-by-step guides for Linux users for all disk operations, matching the detail given for Windows tools.
- Clarify that all required steps can be completed fully on Linux, and highlight any platform-specific caveats or bugs (as is done for qemu-img).
- Consider adding a summary table comparing Windows and Linux toolchains for common imaging tasks.
- Ensure that Linux examples are not only present but also given equal prominence and clarity as Windows examples.
Create Pull Request
Virtual Machines
Prepare a Debian Linux VHD
...les/virtual-machines/linux/debian-create-upload-vhd.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page is generally Linux-focused, but there is mild Windows bias in the 'Prerequisites' and 'Installation notes' sections. Hyper-V (a Windows tool) is mentioned as the only example for creating VHDs, and instructions for converting disk formats reference Hyper-V Manager and the Windows-only convert-vhd cmdlet before Linux alternatives. However, the main workflow and examples are entirely Linux-based, and Linux tools (qemu-img, azcopy, etc.) are used throughout.
Recommendations
- In the 'Prerequisites' section, mention Linux-native tools (e.g., qemu-img, VBoxManage, dd) for creating VHDs alongside Hyper-V.
- In 'Installation notes', provide Linux commands for converting disk formats (e.g., qemu-img convert) before or alongside Windows/Hyper-V instructions.
- Clarify that Hyper-V is just one of several options and link to Linux-based VHD creation guides.
- Consider reordering examples so Linux tools are presented first, given the Linux context of the page.
Virtual Machines
Upload a VHD to Azure or copy a disk across regions - Azure CLI
...machines/linux/disks-upload-vhd-to-managed-disk-cli.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias in the upload example section, where only a Windows-style AzCopy command ('AzCopy.exe') with a Windows file path is shown, and no explicit Linux/macOS AzCopy example is provided. The use of 'AzCopy.exe' and Windows paths may confuse Linux/macOS users. However, the rest of the CLI instructions and scripting are cross-platform and use bash syntax, which is more Linux/macOS friendly.
Recommendations
- Add a Linux/macOS AzCopy example (e.g., 'azcopy copy /home/user/mydisk.vhd ...') alongside the Windows example.
- Clarify that AzCopy is available for Linux/macOS and provide installation instructions or a link for those platforms.
- Use platform-neutral file paths in examples, or provide both Windows and Linux/macOS paths.
- Explicitly mention that the CLI and AzCopy commands work on Linux/macOS, not just Windows.
Virtual Machines
Learn about hibernating your Linux virtual machine
...icles/virtual-machines/linux/hibernate-resume-linux.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for enabling hibernation on Linux VMs, but PowerShell examples are consistently presented alongside or immediately after CLI examples, and sometimes with more detail. The REST API is also covered. There is no evidence of missing Linux-specific examples or exclusive use of Windows tools, but the prominence of PowerShell (a Windows-centric tool) and its parity with CLI may create minor friction for Linux/macOS users, especially as PowerShell is less commonly used on those platforms.
Recommendations
- Present Azure CLI examples before PowerShell examples in all sections, as CLI is more native to Linux/macOS.
- Clearly indicate that PowerShell is optional and primarily relevant for users who have it installed on Linux/macOS.
- Add explicit notes or links for installing/configuring PowerShell on Linux/macOS if PowerShell examples are retained.
- Consider providing Bash script examples for guest OS configuration steps, especially where CLI is used.
- Review screenshots and UI references to ensure they do not assume a Windows environment.
Virtual Machines
Azure VM Image Builder networking options
...les/virtual-machines/linux/image-builder-networking.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents both Windows and Linux options, but Windows examples and tools (PowerShell) are frequently mentioned first or in parallel, sometimes with more prominence. PowerShell examples are provided for most tasks, and Windows-specific configuration notes (e.g., WinRM) are highlighted. However, Linux parity is generally maintained with CLI examples and links.
Recommendations
- Alternate the order of Windows and Linux examples so Linux is sometimes presented first.
- Ensure Linux-specific notes (e.g., SSH configuration) are included where Windows-specific notes (e.g., WinRM) are present.
- Add Bash or shell script examples alongside PowerShell where appropriate.
- Clarify that Azure CLI is cross-platform and highlight its use for both Linux and Windows.
- Review linked example pages to ensure Linux instructions are as detailed as Windows ones.
Virtual Machines
Quickstart: Create a Linux VM cluster in Azure using Terraform
...rtual-machines/linux/quick-cluster-create-terraform.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for verifying results. However, the PowerShell example is included alongside the CLI example, which may suggest a slight Windows bias, especially since PowerShell is primarily a Windows tool (though now cross-platform). The CLI example is shown first, which helps reduce bias. No explicit Windows-only tools or instructions are present, and all Terraform code is platform-agnostic. There are no missing Linux/macOS examples, and no Windows-specific patterns or tools are mentioned elsewhere.
Recommendations
- Clarify that Azure PowerShell is available cross-platform, or note its primary use on Windows.
- Consider explicitly mentioning that all steps (including verification and cleanup) can be performed on Linux/macOS using the Azure CLI.
- If possible, add a Bash script example for verification to further reinforce Linux parity.
- Ensure that any references to PowerShell do not imply Windows exclusivity.
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 instructions for connecting to the VM via SSH, mentioning Windows/PowerShell first and giving explicit instructions for Windows users before Linux/macOS. The use of PowerShell is referenced for Windows, while Bash is referenced for Linux/macOS. However, the rest of the documentation is focused on Linux VMs, and installation instructions are provided for multiple Linux distributions. There are no Windows-only tools or patterns, and Linux users are able to complete all tasks.
Recommendations
- Present connection instructions for Linux/macOS and Windows in parallel, rather than mentioning Windows/PowerShell first.
- Explicitly mention that Linux/macOS users can use the terminal directly, and provide equal detail for both platforms.
- Consider providing screenshots or command examples for both Bash and PowerShell, or clarify that the SSH command is the same across platforms.
- Avoid language that prioritizes Windows users (e.g., 'If you're on a Windows machine...' before 'If you're on a Mac or Linux machine...').
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 focused on Linux VMs and provides Bash and Python examples, but PowerShell samples are included and are consistently presented before Linux Bash equivalents in code blocks. This ordering may subtly prioritize Windows tooling, despite the Linux context. There are no sections that are Windows-only, and Linux users can complete all tasks, but the inclusion and ordering of PowerShell examples may create minor friction for Linux/macOS users.
Recommendations
- List Bash (Linux) examples before PowerShell in all code blocks to reinforce Linux-first orientation.
- Clearly mark PowerShell examples as 'for Windows users' and Bash as 'for Linux/macOS users'.
- Consider omitting PowerShell examples from documentation focused on Linux VMs, or move them to an appendix or separate section for cross-platform reference.
- Ensure all CLI instructions reference Azure CLI (cross-platform) rather than PowerShell where possible.
Virtual Machines
Run scripts in a Linux VM in Azure using action Run Commands
...ob/main/articles/virtual-machines/linux/run-command.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page is focused on Linux VMs, but it frequently references PowerShell and Windows-centric tooling. PowerShell examples are provided alongside Azure CLI, and the PowerShell section refers to running PowerShell scripts (which is uncommon for Linux VMs). The troubleshooting section compares Linux logs to Windows logs, and Windows terminology (e.g., RDP, PowerShell) is mentioned before Linux equivalents (e.g., SSH, Bash). The extension removal instructions also present PowerShell before CLI. There are no missing Linux examples, but the presence and ordering of Windows tools and patterns create mild friction for Linux users.
Recommendations
- Prioritize Azure CLI and Bash examples over PowerShell for Linux VM documentation.
- Clarify that PowerShell examples are for cross-platform use, and provide Bash script examples when discussing script execution.
- Reduce references to Windows-specific tools and terminology unless directly relevant to Linux VM management.
- When comparing Linux and Windows logs, focus on Linux-specific troubleshooting steps and avoid unnecessary Windows log details.
- Ensure that Linux-native tools and workflows are presented first in all example sections.
Virtual Machines
Use a template to deploy Azure Spot Virtual Machines
.../main/articles/virtual-machines/linux/spot-template.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation mentions Azure PowerShell (Windows-centric) before Azure CLI in the 'Next steps' section, and links to a Windows-specific PowerShell guide. There are no Linux/macOS-specific examples or references to Linux-native tooling, although the template itself is for a Linux VM and the page is marked as Linux-related.
Recommendations
- List Azure CLI before Azure PowerShell in 'Next steps', as CLI is cross-platform.
- Include direct links to Linux/macOS-specific guides or CLI usage examples.
- Clarify that Azure CLI works on Linux/macOS and provide installation instructions or links.
- If PowerShell is mentioned, note that it is available cross-platform, or provide parity examples for Bash/CLI.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates mild Windows bias by consistently listing Windows tools (PowerShell) before Linux equivalents (CLI), referencing Windows-specific scheduled events before Linux, and linking to Windows documentation first. While Linux support is present and referenced, Windows examples and tools are given priority in ordering and mention.
Recommendations
- Alternate the order of CLI and PowerShell references so that Linux tools are sometimes listed first.
- Explicitly mention Linux/macOS compatibility for CLI commands and provide direct Linux/macOS usage examples where possible.
- Ensure that links to Linux documentation are given equal prominence and are not always listed after Windows links.
- Add explicit examples or callouts for Linux users in sections discussing tooling (e.g., show both CLI and PowerShell commands side-by-side).
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 provides both Azure CLI and PowerShell examples for exporting an image version to a managed disk. While the CLI section is presented first and is cross-platform, the PowerShell section is detailed and uses Windows-centric tools. There is a slight Windows bias in the prominence and depth of PowerShell instructions, but Linux users can fully complete the task using the CLI examples provided.
Recommendations
- Explicitly state that Azure CLI commands work on Linux, macOS, and Windows.
- Add a note clarifying that PowerShell examples are primarily for Windows users, and suggest using Azure CLI on Linux/macOS.
- Consider providing Bash script examples for Linux users, especially for tasks involving variables and loops.
- Ensure parity in explanation depth between CLI and PowerShell sections.
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 presents PowerShell (Windows-centric) instructions before CLI (cross-platform) instructions in sections for stopping and starting VMs and scale sets. No Linux/macOS-specific tools or examples are provided, but the CLI instructions do offer parity for non-Windows users. The bias is minor and mainly in ordering.
Recommendations
- Present CLI (az CLI) instructions before PowerShell, as CLI is cross-platform and more widely used on Linux/macOS.
- Explicitly mention that CLI commands work on Linux/macOS, and provide links to installation guides for those platforms.
- Add a brief note clarifying that PowerShell Core is available on Linux/macOS, if relevant, or clarify which instructions are Windows-only.
- Consider including example commands for both CLI and PowerShell in parallel, or in a tabbed format, to emphasize platform parity.
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 (such as 'Windows events', 'IIS logs', and references to Windows-specific log levels) is mentioned before Linux equivalents, and Windows tools (e.g., IIS logs, Windows event logs) are referenced more explicitly than Linux alternatives. The troubleshooting section links to a Windows-specific diagnostics guide, and some recommendations are phrased with Windows-first language. Linux is supported and mentioned, but often as a secondary consideration.
Recommendations
- Present Linux and Windows examples side-by-side, or alternate which OS is mentioned first.
- Include explicit Linux equivalents for Windows tools (e.g., mention Apache/Nginx logs alongside IIS logs).
- Provide links to Linux-specific troubleshooting guides (not just Windows).
- Clarify log collection recommendations for Linux (e.g., which syslog facilities and levels are most useful).
- Ensure all advanced/custom monitoring examples include both Windows and Linux scenarios.
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 consistently mentions PowerShell before CLI when describing how to create, assign, and delete maintenance configurations. This ordering suggests a Windows-first approach and may imply PowerShell is the primary or preferred method, even though Azure CLI is cross-platform and suitable for Linux/macOS users. No Linux-specific tools or shell examples (e.g., Bash) are provided, and PowerShell is not explicitly marked as Windows-only, potentially causing confusion for Linux users.
Recommendations
- List Azure CLI instructions before PowerShell, as CLI is cross-platform and more accessible to Linux/macOS users.
- Explicitly state that PowerShell examples are primarily for Windows users, and recommend CLI for Linux/macOS.
- Add Bash shell script examples where appropriate, especially for tasks like saving lists or mapping configurations.
- Clarify tool compatibility in each step (e.g., 'Use PowerShell on Windows, or CLI on any platform').
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 provides examples and references for both Linux and Windows virtual machines, but there is a subtle Windows bias. In several tables and lists, Windows-centric tools (PowerShell) are mentioned before Linux equivalents (Azure CLI), and PowerShell examples are given equal or greater prominence. Some sections, such as those listing ways to query locations or images, consistently list PowerShell before CLI, which is more commonly used by Linux/macOS users. There are no sections that are strictly Windows-only, and Linux-specific features like cloud-init are covered, but the ordering and emphasis may create friction for Linux users.
Recommendations
- Alternate the order of tool references so that Azure CLI (Linux/macOS friendly) is listed before or alongside PowerShell.
- Ensure that every example or instruction given for PowerShell is also provided for Azure CLI, with equal detail and prominence.
- Add explicit Linux/macOS context or notes where relevant, especially in sections discussing management tools.
- Consider grouping instructions by platform, or clearly labeling them, to avoid implicit prioritization of Windows tools.
- Review tables and lists for ordering bias and adjust to be platform-neutral or Linux-first where appropriate.
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 given equal prominence despite being Windows-specific. The CLI example is cross-platform, but the documentation does not clarify that PowerShell is Windows-centric or suggest Linux alternatives for PowerShell users. The ordering of examples is neutral, but the inclusion of PowerShell as a primary method may create friction for Linux/macOS users.
Recommendations
- Explicitly state that PowerShell examples are intended for Windows users and that Azure CLI is recommended for Linux/macOS.
- Add a note clarifying platform compatibility for each example.
- Consider placing the Azure CLI example first, as it is cross-platform.
- Provide links or guidance for installing Azure CLI on Linux/macOS.
- If possible, include bash or shell script examples for common quota queries.
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 displays mild Windows bias by listing PowerShell commands before Linux equivalents (Azure CLI), referencing Windows-specific tools (PowerShell), and mentioning WinRM (a Windows remote management protocol) in network isolation discussions. However, Linux/Azure CLI commands are present, and most instructions are platform-neutral. The page references Linux-specific troubleshooting and template documentation, but Windows tools and patterns are still presented first or exclusively in some cases.
Recommendations
- List Azure CLI commands before or alongside PowerShell commands to avoid Windows-first impression.
- Explicitly mention Linux/macOS compatibility for all command-line instructions.
- Provide Bash or shell script examples where PowerShell is shown.
- Clarify that WinRM is Windows-specific and provide SSH details for Linux VMs.
- Ensure all referenced troubleshooting and template documentation have Linux and Windows parity.
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page is largely neutral, focusing on VM size specifications and performance metrics. However, there is a subtle Windows bias in the 'Feature support' section, where nested virtualization is linked only to the Windows/Hyper-V documentation, and in the 'Bandwidth/Throughput testing' section, which references NTTTCPβa Microsoft tool with primary Windows supportβwithout mentioning Linux alternatives or parity. Windows terminology and links appear before or instead of Linux equivalents in these cases.
Recommendations
- Include links to nested virtualization documentation for Linux (e.g., KVM/QEMU on Azure) if supported.
- Mention and link to Linux-compatible bandwidth/throughput testing tools (such as iperf or Linux NTTTCP builds) alongside NTTTCP.
- Where features/tools are Windows-specific, clarify Linux support status and provide Linux alternatives or guidance.
- Ensure that documentation for features relevant to both OSes provides parallel instructions and references.
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 a subtle Windows bias in the 'Feature support' section, where the only linked resource for Nested Virtualization is a Windows/Hyper-V guide. Additionally, in the 'Network' section, the recommended bandwidth testing tool (NTTTCP) is a Microsoft/Windows-centric utility, and no Linux alternatives are mentioned. There are no command-line examples, but where tooling is referenced, Windows tools are prioritized or exclusively mentioned.
Recommendations
- Include links to Linux/KVM nested virtualization documentation or clarify if the feature is unavailable for all platforms.
- Mention Linux-compatible network bandwidth testing tools (e.g., iperf, netperf) alongside NTTTCP.
- Where platform-specific features are discussed, explicitly state applicability to Linux and Windows, and provide parity in references and resources.
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 mostly neutral and platform-agnostic, focusing on VM specifications and performance metrics. However, there is mild Windows bias in the 'Feature support' section, where nested virtualization is linked to a Windows-specific guide, and in the 'Networking' section, where bandwidth testing references NTTTCPβa Microsoft/Windows-centric toolβwithout mentioning Linux alternatives. Windows terminology and resources are mentioned before or instead of Linux equivalents.
Recommendations
- For nested virtualization, provide or link to equivalent Linux documentation or clarify Linux support status.
- In bandwidth testing, mention Linux-compatible tools (such as iperf3 or netperf) alongside NTTTCP, and provide links to relevant Linux usage guides.
- Where Windows-specific resources are referenced, ensure Linux/macOS equivalents are also listed, or clarify any platform limitations.
- Review all feature support links to ensure Linux parity in documentation coverage.
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 specifications. However, there are subtle signs of Windows bias: the only specific tool mentioned for bandwidth/throughput testing is NTTTCP, which is a Microsoft-developed tool primarily associated with Windows. Additionally, the link for nested virtualization points to a Windows/Hyper-V user guide, with no mention of Linux/KVM equivalents. In both cases, Linux alternatives or parity are not provided.
Recommendations
- Include Linux/KVM equivalents or references for nested virtualization, or clarify if the feature is Windows-only.
- When mentioning NTTTCP for bandwidth testing, also reference Linux-native tools such as iperf or netperf, and provide links to relevant guides.
- Where features are described as supported or unsupported, clarify platform-specific limitations (e.g., if a feature is only available on Windows, state so explicitly).
- Ensure that any tooling or optimization advice is provided for both Windows and Linux environments.
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation is mostly platform-neutral, focusing on VM 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 the bandwidth testing tool NTTTCP is referenced (a Microsoft/Windows-centric tool) without mentioning Linux alternatives. Windows and Linux disk encryption are both noted as unsupported, but the Windows reference appears first.
Recommendations
- For 'Nested Virtualization', add or link to Linux/KVM nested virtualization documentation if supported, or clarify platform limitations.
- In the 'Network' section, mention Linux-compatible bandwidth testing tools (e.g., iperf, netperf) alongside NTTTCP.
- When listing platform-specific features or restrictions, alternate the order or present both platforms together to avoid Windows-first bias.
- Explicitly state platform support or limitations for features where relevant (e.g., nested virtualization, disk encryption).
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page is largely neutral and platform-agnostic, focusing on VM size specifications and features. However, there is mild Windows bias in the 'Feature support' section, where the link for Nested Virtualization points only to the Windows/Hyper-V guide, and in the 'Bandwidth/Throughput testing' resource, which references NTTTCPβa Windows-centric toolβwithout mentioning Linux alternatives. Windows and Linux disk encryption restrictions are listed separately but equally. No command-line examples or PowerShell-specific instructions are present.
Recommendations
- For Nested Virtualization, add or link to equivalent Linux/KVM documentation if supported, or clarify platform limitations.
- In the Bandwidth/Throughput testing section, mention Linux-compatible tools (e.g., iperf, netperf) alongside NTTTCP.
- Where platform-specific features or limitations exist, clarify them for both Windows and Linux users.
- Ensure all referenced guides/tools have Linux equivalents or alternatives, and present them with equal prominence.
Virtual Machines
Mdsv3 Very High Memory size series
...al-machines/sizes/memory-optimized/mdsv3-vhm-series.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation lists compatible OS images for the Mdsv3-VHM series with Windows Server mentioned first, followed by Linux distributions. No usage examples, commands, or tooling are provided, so there is no evidence of Windows-only instructions or tools. The ordering of Windows before Linux is a minor bias.
Recommendations
- List Linux distributions before or alongside Windows Server when describing compatible images.
- Explicitly mention that all features and specifications apply equally to Linux and Windows unless noted.
- If future documentation adds usage examples or commands, ensure parity between Windows (PowerShell, CMD) and Linux (Bash, CLI) instructions.