High Performance Computing

24
Total Pages
12
Linux-Friendly Pages
12
Pages with Bias
50.0%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

48 issues found
Showing 26-48 of 48 flagged pages
High Performance Computing Monitoring configuration ...performance-computing/lift-and-shift-step-2-monitor.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows/Azure-centric bias by exclusively providing examples and instructions for Azure cloud services and tools, with no mention of Linux-native monitoring tools or cross-platform alternatives. All setup and deployment steps focus on Azure portal navigation and Azure-specific services, and the only script example uses Azure CLI commands without showing Linux-specific monitoring or automation approaches. There are no references to Linux tools such as systemd, cron, collectd, Nagios, or native Prometheus deployments outside Azure, nor are there examples for configuring monitoring on Linux HPC clusters without Azure.
Recommendations
  • Include Linux-native monitoring tool examples (e.g., collectd, Nagios, Ganglia, or native Prometheus) and show how they can be integrated with Azure services.
  • Provide parallel instructions for configuring monitoring on Linux-based HPC clusters, including command-line and configuration file examples.
  • Add examples of setting up automated health checks using Linux tools such as cron jobs, systemd timers, or shell scripts.
  • Reference cross-platform open-source monitoring solutions and describe how to bridge them with Azure Monitor, Grafana, and Prometheus.
  • Ensure that examples and instructions are not exclusively Azure portal-based; include CLI and configuration file approaches common in Linux environments.
  • Explicitly mention Linux compatibility and provide troubleshooting tips for Linux-based HPC workloads.
GitHub Create Pull Request
High Performance Computing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/high-performance-computing/lift-and-shift-step-1-networking.md ...formance-computing/lift-and-shift-step-1-networking.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing example steps and patterns that are tailored to Azure portal workflows, which are more familiar to Windows administrators. There are no command-line examples (such as Bash or PowerShell), nor is there any mention of Linux-specific tools, SSH access, or CLI-based configuration, which are common in Linux-centric HPC environments. The use of Azure Bastion is described exclusively through portal navigation, with no reference to SSH tunneling or Linux-native access methods.
Recommendations
  • Add example steps for Linux users, such as how to connect to VMs using SSH (with or without Bastion) from a Linux terminal.
  • Include Azure CLI or Bash command examples for provisioning VMs and configuring network access, alongside portal instructions.
  • Mention Linux-native tools and workflows for managing network access, such as iptables, firewalld, or netplan, where relevant.
  • Clarify that Bastion can be used for SSH access from Linux and macOS clients, not just via the Azure portal.
  • Provide parity in documentation by listing both Windows and Linux approaches for each major configuration step.
GitHub Create Pull Request
High Performance Computing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/high-performance-computing/lift-and-shift-overview.md .../high-performance-computing/lift-and-shift-overview.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page describes HPC lift-and-shift migration in a platform-neutral way, but there is subtle Windows bias. Windows tools (such as Azure CycleCloud) are mentioned first and exclusively, with no Linux-specific examples or parity for Linux-native deployment tools. There are no explicit Linux CLI or configuration examples, nor references to Linux-specific patterns or tools, despite the prevalence of Linux in HPC environments.
Recommendations
  • Include Linux-specific examples for cluster deployment and management (e.g., using native Slurm/PBS/LSF installation on Linux VMs).
  • Mention Linux CLI tools and configuration steps alongside any Windows or Azure-specific tools.
  • Provide parity in quick start guides for Linux environments, such as scripts or templates for deploying HPC clusters on Linux VMs.
  • Reference open-source or cross-platform orchestration tools (e.g., Terraform, Ansible) for environment setup.
  • Clarify that Azure CycleCloud supports both Windows and Linux clusters, and provide links or examples for Linux-focused use cases.
GitHub Create Pull Request
High Performance Computing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/high-performance-computing/lift-and-shift-step-2-monitor.md ...performance-computing/lift-and-shift-step-2-monitor.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page focuses exclusively on Azure-native monitoring tools and workflows, with all example steps and scripts using Azure CLI and portal interfaces. There is no mention of Windows-specific tools (such as PowerShell), but the documentation does not provide any Linux-specific examples, nor does it reference Linux-native monitoring tools or patterns. The guidance is Azure-centric and assumes users are operating within the Azure ecosystem, with no parity for Linux command-line tools (e.g., systemd, collectd, Nagios) or open-source alternatives outside Azure. The only script example is a Bash script using Azure CLI, which is cross-platform but still Azure-specific.
Recommendations
  • Add examples of integrating Linux-native monitoring tools (e.g., collectd, Nagios, sysstat, atop) with Azure Monitor or Grafana.
  • Provide sample configurations for Linux HPC clusters using open-source monitoring solutions, and show how to export their metrics to Azure Monitor or Prometheus.
  • Include guidance for both Windows and Linux environments, such as using PowerShell for Windows and Bash/shell scripts for Linux, with equivalent examples.
  • Reference common Linux logging and alerting patterns (e.g., journald, rsyslog, logrotate) and how they can be incorporated into the Azure monitoring workflow.
  • Clarify which steps or tools are platform-agnostic and which require adaptation for Linux or Windows environments.
GitHub Create Pull Request
High Performance Computing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/high-performance-computing/performance-benchmarking/hpc-storage-options.md ...puting/performance-benchmarking/hpc-storage-options.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates subtle Windows bias by listing Windows protocols (SMB) alongside Linux protocols (NFS) but often mentions SMB before NFS, and does not provide explicit Linux-specific usage examples or guidance. While Linux protocols and workloads are referenced, there is a lack of parity in example depth, with no Linux command-line or workflow illustrations. The documentation also omits Linux-specific tools or patterns (e.g., mounting via CLI, integration with Linux-native utilities), and does not address Linux-specific performance tuning or troubleshooting.
Recommendations
  • Add explicit Linux usage examples, such as mounting Azure Files or NetApp Files via NFS on Linux using CLI commands.
  • Include Linux-specific performance optimization tips (e.g., tuning NFS client settings, using Lustre mount options).
  • Ensure protocol lists and integration notes mention Linux options first or equally, and clarify multiprotocol limitations for Linux and Windows.
  • Provide troubleshooting steps or best practices for Linux environments, such as SELinux considerations, systemd automount, or integration with Linux-based orchestration tools.
  • Reference Linux-native tools (e.g., BlobFuse2, FIO benchmarking on Linux) and provide sample commands.
GitHub Create Pull Request
High Performance Computing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/high-performance-computing/lift-and-shift-overview.md .../high-performance-computing/lift-and-shift-overview.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page describes the lift and shift process for HPC environments in a cloud context, referencing common job schedulers (Slurm, PBS, LSF) and tools like Azure CycleCloud. However, it lacks explicit examples or guidance for Linux-specific tools, commands, or deployment patterns, and does not mention Linux CLI workflows or provide parity for Linux administrators. The page does not provide any Windows-specific examples, but the absence of Linux-focused instructions and examples, especially in the context of HPC (which is predominantly Linux-based), suggests a subtle Windows-first bias.
Recommendations
  • Add explicit Linux CLI examples for common administrative tasks (e.g., cluster deployment, monitoring, troubleshooting).
  • Include references to Linux-native tools and workflows (such as SSH, Bash scripting, and Linux package managers) alongside any cloud or Windows tools.
  • Provide step-by-step guides for deploying and managing HPC clusters on Linux VMs, including integration with Slurm and other Linux job schedulers.
  • Ensure that any quick start or best practice guides include both Windows and Linux scenarios, with equal detail and visibility.
  • Highlight differences and considerations for Linux-based HPC environments during migration, such as file system compatibility, authentication methods, and monitoring solutions.
GitHub Create Pull Request
High Performance Computing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/high-performance-computing/lift-and-shift-step-1-networking.md ...formance-computing/lift-and-shift-step-1-networking.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively referencing Azure Bastion for VM access, which is typically associated with RDP (Windows) connections, and by omitting Linux-specific access patterns (such as SSH). No examples or instructions are provided for Linux users, nor are Linux command-line tools or SSH-based workflows mentioned. The examples and guidance implicitly assume a Windows-centric workflow.
Recommendations
  • Add explicit examples for Linux VM access, such as using SSH via Bastion or VPN Gateway.
  • Include command-line instructions for both Windows (PowerShell) and Linux (bash/ssh) environments.
  • Mention Linux-specific tools and patterns (e.g., OpenSSH, scp, Linux firewall configuration) alongside Windows equivalents.
  • Ensure that documentation steps and screenshots cover both Windows and Linux VM scenarios.
  • Clarify that Bastion supports both RDP (Windows) and SSH (Linux), and provide guidance for each.
GitHub Create Pull Request
High Performance Computing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/high-performance-computing/lift-and-shift-step-2-monitor.md ...performance-computing/lift-and-shift-step-2-monitor.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows/Azure-centric bias by exclusively providing examples and instructions for Azure tools and workflows, with no mention of Linux-native monitoring solutions or cross-platform alternatives. The step-by-step guides and scripts focus on Azure CLI and Azure-specific services, omitting Linux-specific tools (such as native Prometheus, Nagios, or sysstat) and failing to provide equivalent Linux command-line or open-source examples. The documentation also assumes the use of Azure portal and Azure Automation, which are more familiar to Windows administrators, and does not address Linux monitoring patterns or integration with Linux-native tools.
Recommendations
  • Include Linux-native monitoring examples, such as setting up Prometheus or Grafana on Linux VMs using systemd, Docker, or package managers.
  • Provide sample scripts using Linux tools (e.g., top, htop, sysstat, collectl, or custom bash scripts) for health checks and metric collection.
  • Add instructions for configuring open-source monitoring solutions (Nagios, Zabbix, etc.) on Linux HPC clusters, and how to integrate them with Azure services if desired.
  • Offer examples of configuring alerts and automated responses using Linux cron jobs, systemd timers, or shell scripts, not just Azure Automation.
  • Explicitly mention cross-platform compatibility and provide guidance for users migrating from Linux-based on-premises monitoring setups.
  • Balance references to Azure portal and CLI with Linux command-line alternatives and open-source dashboard solutions.
GitHub Create Pull Request
High Performance Computing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/high-performance-computing/lift-and-shift-step-3-overview.md ...erformance-computing/lift-and-shift-step-3-overview.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation page discusses storage migration in an HPC cloud context but does not provide any explicit examples or tool references for Linux environments. While it mentions protocols like NFS and SMB (which are cross-platform), it lacks concrete Linux-oriented guidance, examples, or tool recommendations. The mention of Bicep (an Azure-specific tool) and the absence of Linux-native automation or migration tools (like rsync, scp, or Linux CLI examples) suggest a subtle Windows/Azure-first bias.
Recommendations
  • Include explicit Linux command-line examples for common migration tasks (e.g., using rsync, scp, or Linux shell scripts).
  • Mention Linux-native tools and automation frameworks (such as Ansible, bash scripting, or Linux cron jobs) alongside Azure/Bicep/Terraform.
  • Provide parity in examples by showing both Windows (PowerShell, SMB) and Linux (bash, NFS, rsync) approaches for storage setup and migration.
  • Reference Linux best practices for storage management and migration in HPC environments.
  • Ensure that any Azure-specific tooling is contextualized with equivalent open-source or Linux-native alternatives where possible.
GitHub Create Pull Request
High Performance Computing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/high-performance-computing/lift-and-shift-step-1-storage.md ...performance-computing/lift-and-shift-step-1-storage.md
Medium Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation page demonstrates a bias towards Windows by only providing instructions and examples using the Azure Portal GUI, which is more commonly associated with Windows workflows. There are no command-line examples (such as Azure CLI or PowerShell), and notably, there are no Linux-specific tools, commands, or workflows mentioned. The absence of Linux CLI examples or references to Linux-native tools may make it less accessible for Linux users or those who prefer automation and scripting.
Recommendations
  • Add Azure CLI examples for each step, as the CLI is cross-platform and widely used on Linux.
  • Include sample scripts or commands for storage account creation, access control, and encryption verification using both Azure CLI and PowerShell, clearly labeling each.
  • Mention and link to relevant Linux tools or workflows (e.g., azcopy for Linux, mounting Azure Files on Linux).
  • Ensure that any GUI instructions are supplemented with equivalent command-line instructions to support automation and Linux-first workflows.
  • Explicitly state that all steps can be performed from Linux, macOS, or Windows, and provide guidance for each where appropriate.
GitHub Create Pull Request
High Performance Computing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/high-performance-computing/lift-and-shift-step-1-networking.md ...formance-computing/lift-and-shift-step-1-networking.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates bias by omitting Linux-specific examples and tools. All example steps focus on using the Azure Portal and Bastion, which are often associated with RDP (a Windows protocol) and do not mention SSH or Linux command-line workflows. There are no Linux-specific instructions or references to common Linux administration patterns (e.g., using SSH, CLI tools, or Linux firewall configuration).
Recommendations
  • Add example steps for connecting to Linux VMs using SSH via Azure Bastion, including both portal and CLI workflows.
  • Include references to Linux-native tools and patterns (e.g., iptables, firewalld, or ufw for network rules).
  • Provide parity in examples by showing both Windows (RDP) and Linux (SSH) connection scenarios.
  • Mention Azure CLI and Azure PowerShell equally, and provide command-line examples for both platforms.
  • Clarify that Bastion supports both RDP (Windows) and SSH (Linux), and show how to use each.
GitHub Create Pull Request
High Performance Computing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/high-performance-computing/lift-and-shift-step-1-storage.md ...performance-computing/lift-and-shift-step-1-storage.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation page focuses exclusively on Azure Portal GUI steps and general Azure concepts, without providing any command-line examples. There are no references to Linux tools, CLI commands, or cross-platform automation methods. The absence of Linux (or even Azure CLI) examples, while describing storage setup and management, results in a bias toward Windows-centric workflows, as the Azure Portal is often more familiar to Windows users and less scriptable for Linux automation.
Recommendations
  • Add Azure CLI and PowerShell command examples for all major storage setup and configuration steps, ensuring parity between Windows and Linux environments.
  • Include sample scripts for storage account creation, access control configuration, and encryption verification using both Azure CLI (cross-platform) and PowerShell.
  • Mention and link to documentation for automating storage setup from Linux shells, not just the Azure Portal.
  • Explicitly state that all steps can be performed from Linux, macOS, and Windows using the Azure CLI, and provide equivalent instructions.
GitHub Create Pull Request
High Performance Computing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/high-performance-computing/lift-and-shift-step-2-monitor.md ...performance-computing/lift-and-shift-step-2-monitor.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page focuses exclusively on Azure-native monitoring tools and workflows, with all step-by-step instructions and UI navigation based on the Azure Portal (a web interface, but often associated with Windows-centric workflows). There are no explicit Windows-only tools or PowerShell examples, but there is also a lack of Linux-specific examples, CLI alternatives, or mention of common open-source monitoring tools outside the Azure ecosystem. The only script example is a Bash script using the Azure CLI, but it is tightly coupled to Azure resources and does not demonstrate Linux-native monitoring practices or integration with non-Azure environments. There is no mention of Linux logging/monitoring tools (e.g., syslog, collectd, Nagios, etc.), nor are there instructions for configuring monitoring on Linux VMs outside of the Azure context.
Recommendations
  • Provide parallel examples for both Azure Portal (GUI) and Azure CLI for all setup steps, making it clear that CLI commands work cross-platform (including Linux).
  • Include examples or references for integrating Azure Monitor, Grafana, and Prometheus with Linux-native monitoring/logging tools (e.g., syslog, collectd, journald, or node_exporter).
  • Explicitly mention how to configure monitoring agents or exporters on Linux HPC nodes, including installation and configuration steps.
  • Add a section or examples for monitoring on-premises or hybrid Linux clusters, not just Azure-native resources.
  • Reference or link to documentation for open-source monitoring tools commonly used in Linux HPC environments, and describe how they can be integrated with Azure monitoring solutions.
GitHub Create Pull Request
High Performance Computing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/high-performance-computing/lift-and-shift-step-3-overview.md ...erformance-computing/lift-and-shift-step-3-overview.md
Medium Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation page discusses storage migration in HPC environments with a focus on Azure but does not provide any explicit examples or tool references for either Windows or Linux. However, the absence of Linux-specific tools, commands, or examples (such as rsync, scp, or Linux CLI patterns) and the mention of SMB (a Windows-centric protocol) before NFS (a Linux/UNIX-centric protocol) suggest a subtle Windows-first and missing Linux example bias.
Recommendations
  • Include explicit Linux-based migration tool examples (e.g., rsync, scp, lftp) alongside any Windows tools.
  • Provide sample commands or scripts for both Linux (bash) and Windows (PowerShell) environments in quick start sections.
  • When mentioning protocols, present NFS and SMB in a neutral or alternating order, or explain their relevance to both Linux and Windows environments.
  • Reference Linux-native automation tools (e.g., Ansible, shell scripts) alongside Terraform and Bicep.
  • Ensure that best practices and quick start guides address both Linux and Windows use cases equally.
GitHub Create Pull Request
High Performance Computing High-performance computing (HPC) performance and benchmarking applications ...rmance-computing-performance-benchmarking-applications.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation page lists both Windows and Linux resources in the 'Related resources' section, but the Windows VM link is presented before the Linux VM link. There are no explicit examples, commands, or tools shown in the main content, so no direct Windows-only bias is present. However, the ordering of resources subtly prioritizes Windows.
Recommendations
  • List Linux and Windows resources in alphabetical order or group them together as 'Operating System VM guides' to avoid implicit prioritization.
  • Ensure future documentation includes explicit examples for both Windows (PowerShell, CMD) and Linux (Bash, shell scripts) when showing commands or workflows.
  • If referencing tools or patterns, always mention Linux equivalents alongside Windows ones.
GitHub Create Pull Request
High Performance Computing High-performance computing (HPC) performance and benchmarking applications ...rmance-computing-performance-benchmarking-applications.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation page lists both Windows and Linux VM resources, but the 'Run a Windows VM on Azure' link is presented before the 'Run a Linux VM on Azure' link in the 'Related resources' section. No examples or tools are given that are specific to either platform, and the main content is neutral regarding OS-specific instructions.
Recommendations
  • Present Linux and Windows resources in parallel or alternate their order to avoid implicit prioritization.
  • Ensure that any future examples or guides include both Windows and Linux instructions side-by-side.
  • Explicitly mention that HPC workloads can be run on both Windows and Linux VMs, and provide links to relevant documentation for each.
GitHub Create Pull Request
High Performance Computing High-performance computing (HPC) performance and benchmarking applications ...rmance-computing-performance-benchmarking-applications.md
Low Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation page exhibits a mild Windows bias by listing the 'Run a Windows VM on Azure' resource before the 'Run a Linux VM on Azure' resource in the Related resources section. No explicit PowerShell-heavy examples, Windows-only tools, or missing Linux examples are present in the main content, but the ordering suggests a subtle prioritization of Windows over Linux.
Recommendations
  • List Linux and Windows resources together or alternate their order to avoid implicit prioritization.
  • Ensure that examples and guides for both Windows and Linux environments are equally represented and easy to find.
  • Explicitly mention cross-platform compatibility and provide links to both Windows and Linux instructions where relevant.
GitHub Create Pull Request
High Performance Computing High-performance computing (HPC) performance and benchmarking applications ...rmance-computing-performance-benchmarking-applications.md
Low Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation page lists both Windows and Linux resources, but in the 'Related resources' section, the link to 'Run a Windows VM on Azure' appears before 'Run a Linux VM on Azure'. No explicit examples, tools, or patterns are given for either platform in the main content, but the ordering of resources suggests a subtle Windows-first bias.
Recommendations
  • List Windows and Linux resources in alphabetical order or group them together to avoid implying priority.
  • Ensure that future documentation provides platform-specific examples for both Windows and Linux where relevant.
  • Explicitly mention support for both Windows and Linux HPC workloads in introductory sections to reinforce parity.
GitHub Create Pull Request
High Performance Computing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/high-performance-computing/performance-benchmarking/high-performance-computing-performance-benchmarking-applications.md ...rmance-computing-performance-benchmarking-applications.md
Low Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation page lists both Windows and Linux resources, but in the 'Related resources' section, the link to 'Run a Windows VM on Azure' is placed before 'Run a Linux VM on Azure', suggesting a subtle Windows-first ordering. There are no explicit examples, tools, or instructions that are Windows-specific, nor is there a lack of Linux content, but the ordering may imply a preference.
Recommendations
  • List Windows and Linux resources in alphabetical order or group them together under a neutral heading to avoid perceived prioritization.
  • Explicitly mention that HPC workloads are commonly run on both Windows and Linux, and provide equal visibility to both platforms in examples and resource links.
  • If possible, add example workloads or benchmarking results for both Windows and Linux environments to demonstrate parity.
GitHub Create Pull Request
High Performance Computing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/high-performance-computing/lift-and-shift-step-1-resource-group.md ...ance-computing/lift-and-shift-step-1-resource-group.md
Low Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation provides only Azure Portal (GUI) instructions for resource group configuration and does not include any command-line examples. There are no references to Windows-specific tools or PowerShell, but the absence of CLI examples (such as Azure CLI or Bash) means Linux users are not directly supported. This omission can be considered a subtle bias, as many HPC and Linux users prefer or require command-line instructions.
Recommendations
  • Add Azure CLI examples for all resource group operations (e.g., creating a resource group, adding resources, tagging).
  • Include both Windows PowerShell and Bash/Azure CLI command-line examples to ensure parity.
  • Explicitly mention that resource group management can be performed via command-line tools on both Windows and Linux.
  • Provide links to cross-platform command-line documentation in the Resources section.
GitHub Create Pull Request
High Performance Computing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/high-performance-computing/performance-benchmarking/high-performance-computing-performance-benchmarking-applications.md ...rmance-computing-performance-benchmarking-applications.md
Low Priority View Details →
Scanned: 2025-07-12 23:44
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation page lists both Windows and Linux resources in the 'Related resources' section, but 'Run a Windows VM on Azure' is mentioned before 'Run a Linux VM on Azure'. There are no explicit examples, tools, or patterns that are Windows-specific in the main content, but the ordering in the related links suggests a subtle Windows-first bias.
Recommendations
  • List Linux and Windows resources in a neutral or alternating order, or group them together under a common heading to avoid implying priority.
  • Where possible, provide explicit examples or guidance for both Windows and Linux environments in the main content, especially if future updates add command-line or tool-specific instructions.
  • Review linked articles to ensure parity in depth and quality of Linux and Windows guidance.
GitHub Create Pull Request
High Performance Computing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/high-performance-computing/lift-and-shift-overview.md .../high-performance-computing/lift-and-shift-overview.md
Low Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation provides a high-level overview of HPC lift-and-shift migration but does not include any platform-specific examples or commands. However, it omits concrete examples for both Windows and Linux, and does not mention any Windows-specific tools or patterns. The only product recommendation is Azure CycleCloud with Slurm, which is a Linux-native scheduler. There is a lack of explicit Linux command-line or configuration examples, which may leave Linux-focused administrators without actionable guidance.
Recommendations
  • Add explicit Linux-based examples for common HPC administrative tasks (e.g., sample Slurm configuration, Linux CLI commands for job submission, storage mounting, or monitoring).
  • Include references to Linux-native tools and workflows (such as SSH, rsync, or Linux scripting for automation).
  • Provide parity by ensuring that any product or tool recommendations (such as CycleCloud) are accompanied by Linux usage scenarios and step-by-step guides.
  • If Windows tools or PowerShell are not relevant, clarify that the guidance is platform-agnostic or primarily Linux-focused, to set expectations for the reader.
GitHub Create Pull Request
High Performance Computing https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/high-performance-computing/lift-and-shift-step-1-resource-group.md ...ance-computing/lift-and-shift-step-1-resource-group.md
Low Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation page provides only Azure Portal (GUI) instructions for resource group configuration and does not include any command-line examples. There is a lack of parity for Linux users, as no Azure CLI or Bash examples are provided, nor are there any PowerShell examples. The absence of Linux-friendly command-line instructions may disadvantage users who prefer or require CLI-based workflows, especially on Linux systems.
Recommendations
  • Add Azure CLI (az) command-line examples for all resource group operations, as the Azure CLI is cross-platform and works natively on Linux.
  • If PowerShell examples are added in the future, ensure that Azure CLI examples are always provided alongside them.
  • Explicitly mention that resource group management can be performed via the Azure CLI on Linux, macOS, and Windows.
  • Consider including Bash scripting examples for automation scenarios relevant to Linux users.
GitHub Create Pull Request
← Previous Page 2 of 2 Next →