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 526-550 of 818 flagged pages
Virtual Machines
DNS Name resolution options for Linux VMs
...blob/main/articles/virtual-machines/linux/azure-dns.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation is focused on Linux VM DNS configuration, but there are subtle signs of Windows bias. Windows retry logic is described first and in more detail than Linux, and Windows-specific tools (PowerShell) are mentioned for determining DNS suffixes, while Linux alternatives are not provided. There are no PowerShell-heavy examples or missing Linux examples, but Windows patterns/tools are referenced before Linux equivalents.
Recommendations
- When describing DNS client retry logic, present Linux and Windows behaviors with equal detail and consider listing Linux first, given the page's Linux focus.
- When mentioning tools for querying Azure resources (such as DNS suffixes), provide Linux-native alternatives (e.g., Azure CLI, REST API examples with curl/jq) alongside or before PowerShell.
- Ensure that any references to Windows tools or patterns are balanced with Linux equivalents, especially in sections targeting Linux administrators.
- Consider adding explicit Linux command examples for tasks currently only described with PowerShell or Windows-centric tools.
Create Pull Request
Virtual Machines
Azure VM Image Builder networking options
...les/virtual-machines/linux/image-builder-networking.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page presents both Windows and Linux options, but there is a subtle Windows bias. Windows examples and tools (PowerShell) are mentioned before Linux equivalents in several places, and PowerShell is given equal prominence to Azure CLI, even though CLI is more cross-platform. Windows-specific configuration notes (WinRM) are highlighted, while Linux-specific notes are less emphasized.
Recommendations
- Present Linux and Windows examples in parallel, or alternate which is listed first to avoid implicit prioritization.
- Where possible, use Azure CLI as the primary example, since it is cross-platform, and mention PowerShell as an alternative for Windows users.
- Add Linux-specific configuration notes where relevant, to match the detail given for Windows (e.g., SSH configuration).
- Ensure that all tooling and command examples are available for Linux users, and clearly mark any Windows-only steps.
- Review the order of example links and checklist items to avoid always listing Windows/PowerShell first.
Virtual Machines
Use Azure VM Image Builder for Linux VMs to access an existing Azure virtual network
.../articles/virtual-machines/linux/image-builder-vnet.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows Reference
Summary
The documentation is focused on Linux VM scenarios and uses Azure CLI and Bash throughout, which are cross-platform and Linux-friendly. However, there are minor references to Windows-specific ports and a link to a Windows-specific managed identity guide. There is also mention of PowerShell in a 'For more information' section, but no PowerShell examples are given, nor is PowerShell prioritized over CLI. No Linux examples are missing, and the workflow is Linux-first.
Recommendations
- Replace the link to the Windows-specific managed identity guide with a Linux/Azure CLI equivalent, or provide both links for parity.
- Clarify port usage for Windows and Linux in a way that doesn't prioritize Windows (e.g., list Linux port first, or explain both equally).
- If mentioning PowerShell as an alternative, provide a Linux equivalent (e.g., Bash or CLI) in parallel, or clarify that CLI is recommended for Linux users.
- Ensure that all references to Windows tools or patterns are balanced with Linux equivalents, even in 'For more information' sections.
Virtual Machines
Deploy a VM or Virtual Machine Scale Set with MSP
...tual-machines/metadata-security-protocol/greenfield.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by describing the Windows deployment process first and in more detail, while Linux deployment is mentioned only in a warning and not elaborated with examples or step-by-step instructions. There are no Linux-specific configuration examples, and the provided REST API example uses a Windows VM name ('GPAWinVM'), further reinforcing the Windows focus.
Recommendations
- Add explicit Linux deployment examples, including ARM template and REST API payloads tailored for Linux VMs.
- Provide step-by-step instructions for the two-step Linux process mentioned in the warning, ensuring parity with the Windows guidance.
- Use neutral VM naming conventions in examples (e.g., 'GPA-VM') instead of Windows-specific names.
- Include validation steps specific to Linux environments, if they differ from Windows.
- Mention Linux tools or commands where relevant, and ensure that any Windows-specific tools or patterns are matched with Linux equivalents.
Virtual Machines
Metadata Security Protocol (MSP)
...irtual-machines/metadata-security-protocol/overview.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exhibits Windows bias by listing Windows operating systems before Linux equivalents in the compatibility section and providing a warning that describes a simpler, single-step process for enabling GuestProxyAgent (GPA) on Windows, while Linux requires a more complex, two-step process. No Linux-specific examples or guidance are provided to help Linux users navigate the additional steps.
Recommendations
- Provide step-by-step instructions or examples for enabling GPA on Linux, including any required commands or configuration files.
- List supported operating systems in a neutral or alphabetical order to avoid prioritizing Windows.
- Include troubleshooting tips or automation guidance for Linux users to streamline the GPA setup process.
- Explicitly mention any Linux tools or patterns (e.g., systemd, shell scripts) that can be used to configure GPA, similar to ARM template usage on Windows.
Virtual Machines
Isolated Image Builds for Azure VM Image Builder
...chines/security-isolated-image-builds-image-builder.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page exhibits mild Windows bias. While the content is generally platform-neutral, the only explicit command-line example for registering the Microsoft.ContainerInstance provider is given in both Azure CLI and PowerShell, with PowerShell (a Windows-centric tool) mentioned second but still present. There are no Linux shell (bash) equivalents provided, and no Linux-specific tools or examples are referenced. The troubleshooting and template references are linked under 'linux/', but the main body does not provide parity in command-line examples or mention Linux-first workflows.
Recommendations
- Add bash/Azure CLI examples alongside PowerShell for all command-line instructions, especially for provider registration.
- Explicitly mention Linux shell usage where appropriate, and provide examples for both Windows and Linux environments.
- Ensure that references to troubleshooting and template guides clarify platform applicability (e.g., if a guide is Linux-specific, note Windows equivalents or parity).
- Review all command-line and tooling references to ensure Linux users are not required to use Windows-centric tools like PowerShell.
Virtual Machines
Set up InfiniBand on HPC VMs - Azure Virtual Machines | Microsoft Docs
...lob/main/articles/virtual-machines/setup-infiniband.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation generally maintains OS parity, mentioning both Linux and Windows support for InfiniBand on Azure HPC VMs. However, there is a subtle Windows bias: Microsoft HPC Pack (a Windows-centric tool) is highlighted as a cluster option, and its usage is described before Linux alternatives. The reference to MS-MPI and HPC Pack, which are traditionally Windows tools, is more prominent than Linux-native cluster management or MPI solutions. There are no explicit Linux command examples, and the documentation does not provide Linux-specific configuration steps or tools, whereas Windows tools are named and linked.
Recommendations
- Add explicit Linux cluster management options (e.g., Slurm, OpenMPI, Warewulf) alongside or before Microsoft HPC Pack.
- Provide Linux-specific configuration and deployment examples, including command-line instructions for popular distributions.
- Balance tool recommendations by mentioning Linux-native MPI stacks and cluster orchestration tools with equal detail and prominence.
- Include links to Linux documentation and community resources for InfiniBand and HPC setup.
- Ensure that examples and guidance are presented in a way that does not assume Windows-first workflows.
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page shows mild Windows bias. In the 'Feature support' section, nested virtualization is linked to a Windows-specific Hyper-V guide, with no mention of Linux alternatives (e.g., KVM). In the networking section, bandwidth/throughput testing references NTTTCP, a Microsoft/Windows-centric tool, without mentioning Linux-native equivalents. In both cases, Windows tools and documentation are referenced exclusively or before Linux equivalents.
Recommendations
- For nested virtualization, add links or notes about Linux support (e.g., KVM on Ubuntu) and provide relevant documentation.
- In the networking section, mention Linux-native bandwidth testing tools (e.g., iperf, netperf) alongside NTTTCP, and provide links to their usage in Azure.
- Review all feature support and tooling references to ensure Linux parity, adding Linux-specific examples and documentation where appropriate.
- Where possible, avoid referencing only Windows documentation or tools; always include Linux equivalents or clarify OS-specific limitations.
Virtual Machines
Dlsv6 size series (Preview)
...virtual-machines/sizes/general-purpose/dlsv6-series.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page shows mild Windows bias. The only tool mentioned for bandwidth/throughput testing is NTTTCP, which is a Microsoft-developed tool primarily associated with Windows. The link for nested virtualization support points to a Windows-specific guide. In the network section, optimization guidance refers to both Linux and Windows, but the only explicit test tool mentioned is Windows-centric. No Linux-specific tools (e.g., iperf, fio) or Linux documentation links are provided, and Windows tools/guides are referenced before any Linux equivalents.
Recommendations
- Include Linux-specific tools and examples for bandwidth/throughput testing, such as iperf or fio.
- Provide links to Linux documentation for nested virtualization and other features where Windows guides are referenced.
- When listing tools or guides, mention both Windows and Linux options, or present them in parallel rather than Windows-first.
- Add explicit Linux usage notes or examples where relevant, especially in performance optimization and feature support sections.
Virtual Machines
NC_RTXPRO6000BSE_v6 size series
...s/sizes/gpu-accelerated/nc-rtxpro6000-bse-v6-series.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page exhibits mild Windows bias. It references Windows-specific technologies (e.g., Hyper-V nested virtualization) and Windows tools (NTTTCP for bandwidth testing) without mentioning Linux equivalents or alternatives. In the feature support section, the link for nested virtualization points only to the Windows/Hyper-V guide, and in networking, NTTTCP is referenced for both Linux and Windows but is a Windows-origin tool. There are no command-line examples, but where tooling is mentioned, Windows is prioritized or Linux is omitted.
Recommendations
- For nested virtualization, add or link to Linux/KVM documentation or explicitly state Linux support status.
- When referencing bandwidth testing tools, mention Linux-native options (e.g., iperf3) alongside NTTTCP, and provide links to usage guides for both platforms.
- Where features differ between Windows and Linux (e.g., disk encryption), clarify parity and link to both sets of restrictions.
- Review all referenced guides and ensure Linux-specific instructions and examples are included or linked, especially for performance optimization and troubleshooting.
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page demonstrates mild Windows bias. In the 'VM Basics resources' section, Windows Server is listed first among supported guest OS versions for large vCPU counts, ahead of Linux distributions. In the 'Feature support' section, the link for Nested Virtualization points specifically to Hyper-V on Windows, with no mention of KVM or other Linux virtualization technologies. In the networking section, the bandwidth/throughput testing tool referenced (NTTTCP) is a Windows-centric tool, with no mention of Linux alternatives like iperf or netperf.
Recommendations
- List supported Linux distributions before or alongside Windows Server in guest OS requirements to avoid Windows-first ordering.
- When referencing virtualization features, include Linux equivalents (e.g., KVM nested virtualization) and link to relevant documentation.
- In networking sections, mention and link to Linux-native bandwidth testing tools (such as iperf or netperf) alongside NTTTCP.
- Review all feature support and tooling references to ensure Linux parity and avoid exclusive focus on Windows technologies.
Virtual Machines
Mdsv3 Very High Memory size series
...al-machines/sizes/memory-optimized/mdsv3-vhm-series.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page exhibits a mild Windows bias. In the list of supported OS images, Windows Server is mentioned first, ahead of Linux distributions. The only external tool referenced for bandwidth/throughput testing is NTTTCP, which is a Microsoft-developed tool primarily for Windows. No Linux-specific tools or examples are provided, and there are no command-line examples (PowerShell, Bash, etc.) for either platform. However, Linux compatibility is clearly stated for several distributions.
Recommendations
- List supported Linux images before or alongside Windows images, or alphabetically, to avoid implicit prioritization.
- Mention Linux equivalents for network testing tools, such as iperf or netperf, alongside NTTTCP.
- Provide example commands or usage patterns for both Windows (PowerShell) and Linux (Bash/CLI) where relevant, such as for checking quotas, optimizing performance, or testing network throughput.
- Ensure that any references to external documentation or guides include both Windows and Linux procedures.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page generally addresses both Linux and Windows VMs, but there is subtle bias in the ordering and example parity. In the 'Reduce downtime' section, scheduled events for Linux are mentioned after Windows, and there are no concrete examples or commands for either OS. The page does not provide OS-specific troubleshooting steps or tools, and does not mention Linux-specific patterns or utilities (e.g., systemd, journalctl) that administrators might use to investigate reboots, nor does it reference Windows tools (e.g., Event Viewer, PowerShell), but the ordering and lack of Linux-specific guidance suggests a slight Windows-first bias.
Recommendations
- Ensure Linux and Windows examples are presented with equal prominence and detail.
- Provide concrete troubleshooting steps or commands for both Linux (e.g., checking /var/log/syslog, using journalctl) and Windows (e.g., Event Viewer, PowerShell commands) when discussing VM reboots.
- Alternate the order of Linux and Windows references, or present them side-by-side, to avoid implicit prioritization.
- Include links to OS-specific documentation for investigating and responding to reboots.
Virtual Machines
List, update, and delete resources
...in/articles/virtual-machines/update-image-resources.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for managing Azure Compute Gallery resources. However, PowerShell examples are given equal prominence to CLI, and PowerShell is a Windows-centric tool. There are no Linux shell-specific examples (e.g., bash scripting, use of Linux tools), nor is there mention of Linux-specific patterns or considerations. The CLI examples are cross-platform, but the presence and parity of PowerShell examples may signal a Windows bias, especially since PowerShell is traditionally associated with Windows environments.
Recommendations
- Clarify that Azure CLI commands are cross-platform and can be run on Linux, macOS, and Windows.
- Add explicit bash shell examples where scripting or environment variables are used, to demonstrate Linux usage (e.g., export, variable substitution).
- Mention installation and usage of Azure CLI on Linux systems, including package manager instructions.
- If PowerShell examples are provided, consider also providing bash equivalents for common scripting tasks.
- Avoid implying PowerShell is required for resource management; highlight CLI as the default for cross-platform scenarios.
- Include troubleshooting or usage notes relevant to Linux users (e.g., file permissions, shell differences).
Virtual Machines
User data for Azure Virtual Machine
...-docs/blob/main/articles/virtual-machines/user-data.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exhibits Windows bias by providing JSON examples that specify Windows OS types, Windows disk images, and Windows-specific configuration fields (e.g., 'windowsConfiguration', 'timeZone', 'MicrosoftWindowsServer'). There are no equivalent Linux-focused examples, nor are Linux-specific configuration fields or images shown. The ordering and content of examples prioritize Windows, despite the page being for 'virtual-machines-linux'.
Recommendations
- Add parallel examples using Linux OS types (e.g., 'osType': 'Linux'), Linux disk images, and Linux-specific configuration fields (such as 'linuxConfiguration').
- Include sample ARM templates and REST API payloads for provisioning Linux VMs and VMSS, with appropriate image references (e.g., Ubuntu, CentOS).
- Ensure that both Windows and Linux examples are presented side-by-side or in alternating order, or prioritize Linux examples when the documentation is for Linux services.
- Explicitly mention Linux-specific considerations or differences in user data handling, if any.
- Review all code samples and configuration blocks to ensure Linux parity and visibility.
Virtual Machines
Deploying disks with Azure Resource Manager templates
...l-machines/using-managed-disks-template-deployments.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by consistently using Windows VM templates and Windows-specific image references in all code examples. The referenced templates and examples exclusively use 'MicrosoftWindowsServer' as the image publisher and 'WindowsServer' as the offer, with parameters for 'windowsOSVersion'. There are no Linux VM template examples, nor is there any mention of Linux image references or parameters. The only mention of Linux is in the 'Next steps' section, which links to a Linux template, but no Linux-specific example is shown or discussed in the main content.
Recommendations
- Include parallel Linux VM template examples alongside Windows examples, using 'Canonical' or other Linux publishers and appropriate offers/skus.
- Show how to specify Linux OS images in the 'imageReference' section of the template.
- Add Linux-specific configuration notes where relevant (e.g., differences in OS disk settings, diagnostics, or data disk attachment).
- Ensure that both Windows and Linux examples are presented with equal prominence throughout the documentation, not just in external links.
- Clarify any differences in disk provisioning or template structure that may apply to Linux VMs.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/linux/time-sync.md
...blob/main/articles/virtual-machines/linux/time-sync.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page is focused on Linux VM time synchronization in Azure and provides comprehensive Linux-specific guidance and examples. However, it opens with a lengthy discussion of Windows Server 2016 time sync improvements, including links to Windows documentation, and references to Windows infrastructure and tools before discussing Linux-specific mechanisms. There are no PowerShell or Windows command examples for Linux, but the initial context and references are Windows-centric, which may give the impression that Windows is the primary or default platform. The only PowerShell example is for encoding cloud-init data, which is a cross-platform Azure deployment detail, not a time sync operation.
Recommendations
- Move or minimize the Windows Server 2016 discussion to a background or reference section, focusing the introduction on Linux time sync requirements and mechanisms.
- If mentioning Azure's host OS, clarify that the underlying host time is provided to all guest OSes (Linux and Windows) equally, and that the Linux mechanisms are distinct.
- Prioritize Linux-specific tools, services, and configuration examples in the introduction and throughout the document.
- Provide Linux command-line examples exclusively (as is already done), and only include Windows/PowerShell examples if strictly necessary for cross-platform deployment scenarios, clearly labeling them as such.
- Add a brief summary or table comparing Linux and Windows time sync approaches in Azure, if cross-platform context is needed, but keep Linux as the focus.
- Ensure that all external links in the 'Next steps' or 'More information' sections are relevant to Linux, or clearly separate Windows references.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/metadata-security-protocol/faq.md
...les/virtual-machines/metadata-security-protocol/faq.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exhibits Windows bias by referencing Windows provisioning philosophy as the default and not providing Linux-specific usage examples or tools. Windows patterns are described first, and Linux is discussed mainly in terms of limitations. There are no Linux command-line or tool examples, and the documentation does not mention Linux equivalents for checking MSP status or managing the GPA.
Recommendations
- Add Linux-specific examples for checking MSP status, such as using curl, jq, or other Linux-native tools to query the VM API or instance view.
- Provide guidance on installing and managing the Guest Proxy Agent on Linux, including package management commands (e.g., apt, yum) and service management (systemd).
- Clarify Linux provisioning workflows and offer parity with Windows documentation, including any available VM extensions or automation options.
- Avoid framing Windows philosophy as the default; present both Windows and Linux approaches equally and in parallel.
- Include troubleshooting steps and health checks using Linux tools (e.g., journalctl, systemctl) for the GPA.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/migration/dedicated-host-migration-guide.md
...l-machines/migration/dedicated-host-migration-guide.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides command-line examples for both PowerShell and Azure CLI, but PowerShell is consistently listed first in all tabbed sections. This ordering can subtly prioritize Windows users, as PowerShell is more closely associated with Windows environments. There are no explicit Linux shell (bash) examples or mentions of Linux-specific tools, though Azure CLI is cross-platform. No Windows-only tools are referenced, but the absence of bash or Linux-native command examples may disadvantage Linux users.
Recommendations
- Alternate the order of PowerShell and CLI tabs, or list CLI first in some sections to avoid implicit Windows prioritization.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide bash examples where appropriate.
- Add a short note or section for Linux users, clarifying that all CLI instructions are fully supported on Linux systems.
- Consider including bash script snippets for common migration tasks, especially for users who automate with shell scripts.
- Review for any subtle language that assumes a Windows environment and adjust to be OS-neutral.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/network-security-group-test.md
...ticles/virtual-machines/network-security-group-test.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exhibits a Windows bias by focusing its main example on testing RDP (Remote Desktop Protocol) connectivity, which is specific to Windows VMs. There are no equivalent examples for common Linux connectivity scenarios (such as SSH), and the only explicit example provided is for RDP. While the prerequisites mention both Linux and Windows VMs, the step-by-step instructions and screenshots are tailored to a Windows-centric use case, and no Linux-specific protocols or ports are demonstrated.
Recommendations
- Provide parallel examples for Linux VMs, such as testing SSH (port 22) connectivity, alongside the RDP example.
- In the 'Test inbound connections' section, add a table row and screenshot for SSH (Linux) in addition to RDP (Windows).
- Explicitly mention that the steps apply to both Linux and Windows VMs, and clarify which service types (RDP, SSH, etc.) are relevant for each OS.
- Ensure that the documentation alternates or balances the order of Windows and Linux examples, or presents them together, to avoid the perception of Windows-first bias.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/setup-infiniband.md
...lob/main/articles/virtual-machines/setup-infiniband.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation generally maintains OS neutrality but shows mild Windows bias by listing Windows Server alongside Linux distributions in the OS support section, and by mentioning Microsoft HPC Pack (a Windows-centric tool) as a primary cluster option. Linux tools and patterns are referenced, but Windows tools (HPC Pack, MS-MPI) are given equal or slightly more prominent placement, and the only explicit cluster management tool described in detail is Microsoft HPC Pack. There are no explicit command-line examples, but the mention of Windows tools without equal Linux alternatives in some sections suggests a subtle bias.
Recommendations
- Provide explicit Linux-based cluster management options (e.g., Slurm, OpenHPC) alongside Microsoft HPC Pack in the cluster configuration section.
- When listing supported operating systems, consider listing Linux distributions first, as they are more commonly used for HPC workloads.
- Include example workflows or references for configuring InfiniBand and MPI on Linux, not just links to generic setup pages.
- If mentioning Windows-specific tools like HPC Pack, also mention and link to Linux-native alternatives and guides.
- Ensure parity in detail and guidance for both Linux and Windows users throughout the documentation.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/sizes/compute-optimized/faldsv7-series.md
...ual-machines/sizes/compute-optimized/faldsv7-series.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page is largely neutral and platform-agnostic, but there are subtle signs of Windows bias. In the 'Feature support' section, Windows features are listed before Linux equivalents. In the networking section, the only bandwidth/throughput testing tool mentioned is NTTTCP, which is a Windows-native tool (though it has a Linux port, it's primarily associated with Windows). There are no explicit Linux command-line examples or Linux-specific tools referenced, and the only mention of Linux is in the context of unsupported disk encryption.
Recommendations
- When listing feature support, alternate the order of Windows and Linux features or group them together to avoid implying priority.
- In the networking section, mention Linux-native tools for bandwidth testing (e.g., iperf3, netperf) alongside NTTTCP, and provide links to their usage.
- Where relevant, provide both Windows and Linux command-line examples or references for common VM operations.
- Add explicit references to Linux documentation or best practices, especially in sections discussing optimization, troubleshooting, or feature support.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/sizes/general-purpose/dadsv7-series.md
...irtual-machines/sizes/general-purpose/dadsv7-series.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page shows mild Windows bias. In the 'Feature support' section, the Windows disk encryption feature is listed before the Linux equivalent. In the 'Nested Virtualization' feature, only a Windows/Hyper-V link is provided. In the networking section, the only bandwidth testing tool mentioned is NTTTCP, which is a Windows-centric tool, and no Linux alternatives are referenced. No explicit Linux command-line or tool examples are given, and Linux is only mentioned in passing.
Recommendations
- In the 'Feature support' section, list Linux and Windows features in parallel or alphabetically, and provide equivalent detail and links for both platforms.
- For 'Nested Virtualization', add a reference or guidance for nested virtualization on Linux (e.g., KVM/QEMU), or clarify if it's not supported.
- In the networking section, mention Linux bandwidth testing tools such as iperf or netperf alongside NTTTCP, and provide links to relevant Linux documentation.
- Wherever possible, ensure that examples, tools, and troubleshooting steps are provided for both Windows and Linux environments.
- Review all resource links and ensure Linux-specific documentation is included where relevant.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/sizes/general-purpose/daldsv6-series.md
...rtual-machines/sizes/general-purpose/daldsv6-series.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page shows mild Windows bias. It references Windows-specific tools (e.g., NTTTCP for bandwidth testing) and links to a Windows-specific nested virtualization guide before any Linux equivalent. There are no explicit Linux command-line examples or Linux-first guidance, and Linux is only mentioned in passing (e.g., 'Azure Disk Encryption for Linux VMs').
Recommendations
- Include Linux equivalents for all Windows-specific tools mentioned (e.g., mention iPerf or netperf for bandwidth testing alongside NTTTCP).
- Add links to Linux-specific documentation for features like nested virtualization, or clarify Linux support status.
- Where possible, provide both Linux and Windows examples or guidance in parallel, especially for performance testing and optimization.
- Review all feature support and resource lists to ensure Linux and Windows are given equal prominence and detail.
- If a feature is not supported on Linux or Windows, provide a brief explanation or link to more information for both platforms.
Virtual Machines
https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/virtual-machines/sizes/general-purpose/dldsv6-series.md
...irtual-machines/sizes/general-purpose/dldsv6-series.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page is largely neutral and platform-agnostic, 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 'Bandwidth/Throughput testing (NTTTCP)' resource, which references a Windows-centric tool before mentioning Linux compatibility. No Linux-specific examples, tools, or guides are provided, and Windows resources are mentioned first or exclusively in relevant contexts.
Recommendations
- Add equivalent Linux documentation links for features like Nested Virtualization (e.g., KVM or nested virtualization on Linux in Azure).
- When referencing tools like NTTTCP, clarify Linux support and provide direct links to Linux usage guides or alternative Linux-native tools (e.g., iperf, netperf).
- Ensure that feature support sections mention both Windows and Linux resources equally, or provide parity in documentation links.
- Where features are not supported for either OS (e.g., Azure Disk Encryption), clarify restrictions for both platforms and link to both Windows and Linux documentation.