Batch

114
Total Pages
46
Linux-Friendly Pages
68
Pages with Bias
59.6%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

436 issues found
Showing 76-100 of 436 flagged pages
Batch Quickstart: Use the Azure portal to create a Batch account and run a job ...e-docs/blob/main/articles/batch/quick-create-portal.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively using Windows compute nodes, specifying Windows Server 2019 as the operating system, and providing only Windows command line examples (e.g., 'cmd /c', 'timeout'). There are no Linux pool options, nor are there any Linux shell (bash/sh) command examples or mentions of Linux-compatible tools or patterns.
Recommendations
  • Add instructions and screenshots for creating Linux-based pools (e.g., Ubuntu, CentOS) alongside the Windows example.
  • Provide Linux shell command examples (e.g., 'bash -c "env; sleep 90"') for tasks, and explain how to select the appropriate OS and command syntax.
  • Explicitly mention that Azure Batch supports both Windows and Linux compute nodes, and discuss considerations for each platform.
  • Where possible, present Windows and Linux options in parallel, rather than Windows-only or Windows-first.
  • Include notes or links to documentation on running cross-platform workloads and using platform-appropriate tooling.
GitHub Create Pull Request
Batch Azure Quickstart - Create a Batch account - Azure Resource Manager template ...docs/blob/main/articles/batch/quick-create-template.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by primarily referencing the Azure portal and mentioning Azure PowerShell before Azure CLI and REST API as deployment alternatives. There are no explicit Linux or cross-platform command-line examples, and the deployment workflow is centered on the portal, which is more commonly used in Windows environments. The absence of Linux-specific instructions or examples (such as Bash or CLI usage) further reinforces the bias.
Recommendations
  • Add explicit Azure CLI (bash) examples for template deployment, with step-by-step instructions.
  • Present deployment alternatives in a neutral order (e.g., CLI, PowerShell, REST API, Portal) or group them together.
  • Include screenshots or terminal output for Linux environments to illustrate parity.
  • Reference cross-platform tools and workflows, such as using VS Code on Linux or Mac, where relevant.
  • Ensure that links to further documentation (such as 'Deploy templates') point to both PowerShell and CLI instructions, or provide a direct link to CLI documentation.
GitHub Create Pull Request
Batch Quickstart: Use .NET to create a pool and run a job ...zure-docs/blob/main/articles/batch/quick-run-dotnet.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a Windows bias by exclusively using Windows Server images for the Batch pool, providing only Windows command-line examples (cmd /c type), and referencing Windows-specific tools and patterns (Visual Studio, Windows command line) without Linux equivalents or alternatives. There are no examples or instructions for using Linux compute nodes, nor are Linux shell commands or deployment patterns discussed.
Recommendations
  • Add parallel examples and instructions for creating Batch pools with Linux VM images, including code snippets for specifying Linux Marketplace images in VirtualMachineConfiguration.
  • Include Linux shell command examples (e.g., using bash and cat) for task CommandLine properties, alongside the Windows cmd examples.
  • Explicitly mention that both Windows and Linux nodes are supported, and provide guidance for choosing between them.
  • Provide instructions for building and running the app on Linux environments, such as using VS Code or command-line .NET tools, and clarify any platform-specific steps.
  • Ensure that resource file handling and output viewing examples work for both Windows and Linux nodes, and document any differences.
GitHub Create Pull Request
Batch Batch security and compliance best practices ...cs/blob/main/articles/batch/security-best-practices.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates several Windows biases. Windows-specific tools (PowerShell) are mentioned before their Linux equivalents (Azure CLI) when referencing how to discover supported images. The section on OS-level TLS settings provides detailed Windows guidance and links, while Linux configuration is not discussed. References to remote access mention RDP before SSH, and guidance for managing TLS settings is exclusively Windows-focused. There are no concrete Linux-specific examples or links for OS-level security configuration, and the documentation generally provides more detail for Windows scenarios.
Recommendations
  • When listing tools, mention Azure CLI before or alongside PowerShell, and provide equivalent command examples for both platforms.
  • Include Linux-specific guidance for OS-level security configuration, such as managing TLS settings, cipher suites, and patching, with relevant links to Linux documentation.
  • Provide SSH examples and guidance for remote access before or alongside RDP, and clarify Linux support for node agent features.
  • Add concrete Linux examples for discovering supported images and managing node security.
  • Ensure parity in detail and coverage between Windows and Linux throughout the documentation, especially in sections discussing OS-level configuration and security best practices.
GitHub Create Pull Request
Batch Mount a virtual file system on a pool ...re-docs/blob/main/articles/batch/virtual-file-mount.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation exhibits several Windows biases: PowerShell is the primary scripting language used for both Windows and Linux examples, rather than Bash for Linux; Windows-specific tools and commands (cmdkey, net use, RDP) are described in detail, often before their Linux equivalents; and troubleshooting and manual mounting instructions are more verbose and tool-centric for Windows. While Linux support is present and examples are provided, the overall structure and example selection favor Windows workflows and tools.
Recommendations
  • Provide Bash-based examples for Linux, especially for mounting and troubleshooting, rather than relying solely on PowerShell.
  • Present Linux and Windows instructions in parallel, ensuring equal detail and prominence for both platforms.
  • Include Linux-native troubleshooting steps and tools (e.g., dmesg, journalctl, mount, lsblk) alongside Windows tools.
  • Reference Linux documentation and community resources with the same frequency and visibility as Windows resources.
  • Clarify when features or commands are platform-specific, and avoid presenting Windows-first workflows unless justified by usage statistics.
  • Expand manual mounting instructions for Linux to include direct Bash commands and common troubleshooting patterns.
GitHub Create Pull Request
Batch Tutorial: Run a parallel workload using the .NET API ...s/blob/main/articles/batch/tutorial-parallel-dotnet.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits a Windows bias by exclusively using Windows-based VM images, referencing only the Windows version of ffmpeg, and providing command-line examples that use Windows syntax (cmd /c, .exe). There are no Linux VM pool configuration examples, nor any Linux shell command-line equivalents for running ffmpeg. The tutorial does not mention how to adapt the workflow for Linux compute nodes, despite Azure Batch supporting Linux pools.
Recommendations
  • Add explicit instructions and code samples for creating Linux-based pools (e.g., using Ubuntu or CentOS images) in addition to Windows.
  • Provide Linux-compatible ffmpeg application package references and download links.
  • Include Linux shell command-line examples (e.g., bash syntax, ./ffmpeg) for running ffmpeg tasks.
  • Discuss differences in environment variables and file paths between Windows and Linux nodes.
  • Clarify that the workflow is cross-platform and provide guidance for users who wish to use Linux compute nodes.
GitHub Create Pull Request
Batch Copy applications and data to pool nodes ...ain/articles/batch/batch-applications-to-pool-nodes.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits Windows bias by referencing Windows-specific tools and patterns (such as .exe and .msi installers) without mentioning Linux equivalents. There are no examples or guidance for Linux application packaging, installation, or common Linux file formats. Windows terminology and patterns are presented exclusively and/or before any cross-platform considerations.
Recommendations
  • Add explicit examples for Linux, such as using .sh scripts, .tar.gz archives, or package managers (apt, yum) in start tasks and job preparation tasks.
  • Mention Linux equivalents when discussing application installation (e.g., .deb, .rpm, or direct binary execution).
  • Provide sample command lines for both Windows (PowerShell, .exe/.msi) and Linux (bash, shell scripts, package managers) in relevant sections.
  • Clarify that Azure Batch supports both Windows and Linux nodes, and highlight any platform-specific considerations for resource files and application packages.
  • Avoid assuming Windows-first patterns; present cross-platform guidance or alternate between Windows and Linux examples.
GitHub Create Pull Request
Batch Update pool properties ...ob/main/articles/batch/batch-pool-update-properties.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by providing only Windows-based VM image update examples (using 'MicrosoftWindowsServer' and 'batch.node.windows amd64'), with no mention or example of Linux VM images or node agent SKUs. There are no Linux-specific code samples, nor is there guidance for updating pools with Linux configurations. Windows terminology and tools are referenced exclusively in the main example, and Linux alternatives are omitted.
Recommendations
  • Add parallel examples for updating pools with Linux VM images, including sample configurations using popular Linux distributions (e.g., Ubuntu, CentOS) and the appropriate node agent SKU.
  • Explicitly mention both Windows and Linux options when discussing VM image updates, and clarify any differences in update behavior or requirements.
  • Provide code samples or REST API payloads that demonstrate updating pool properties for Linux-based pools.
  • Include a table or section listing common VM image publishers/offers/SKUs for both Windows and Linux, with guidance on how to select and update them.
  • Review terminology throughout the documentation to ensure Windows-specific terms are balanced with Linux equivalents.
GitHub Create Pull Request
Batch Create task dependencies to run tasks ...cs/blob/main/articles/batch/batch-task-dependencies.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias by exclusively using Windows command-line examples (cmd.exe /c echo ...) in all code samples, without providing Linux or cross-platform alternatives. Windows tools and patterns (cmd.exe) are mentioned exclusively, and there is no reference to Linux shells (bash/sh) or their usage. The documentation does not acknowledge or demonstrate how to configure or run tasks using Linux commands, which are common in Azure Batch workloads, especially for big data and HPC scenarios.
Recommendations
  • Provide equivalent Linux shell examples (e.g., bash -c 'echo ...') alongside Windows cmd.exe examples in all code snippets.
  • Explicitly mention that Azure Batch supports both Windows and Linux compute nodes, and clarify how task commands should be specified for each OS.
  • Add a section or note describing OS-specific considerations for task commands, including how to detect or specify the target OS.
  • Ensure that sample projects and linked resources include Linux usage and examples.
  • Avoid using only Windows-centric terminology (cmd.exe) when describing generic task execution; use neutral language or mention both platforms.
GitHub Create Pull Request
Batch Jobs and tasks in Azure Batch .../azure-docs/blob/main/articles/batch/jobs-and-tasks.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias. In the section explaining how to invoke a shell for task command lines, the Windows example (cmd.exe) is listed first, and the Linux example is secondary. In the 'Start task' section, Windows-specific tools like 'robocopy', 'MSI', and 'setup.exe' are mentioned as examples, with no Linux equivalents provided. The documentation references Windows environment variable syntax before Linux syntax. There are no explicit PowerShell examples, but the pattern of Windows-first and Windows-tool references is clear. Linux tools and patterns are not given equal prominence or examples.
Recommendations
  • Alternate the order of Windows and Linux examples, or present both together to avoid Windows-first bias.
  • When mentioning Windows tools like 'robocopy', 'MSI', or 'setup.exe', also provide equivalent Linux tools (e.g., 'rsync', '.deb' or '.sh' installers).
  • Explicitly include Linux shell and command examples wherever Windows examples are given.
  • When referencing environment variable syntax, present both Windows (%VAR%) and Linux ($VAR) forms together.
  • Add a note or section highlighting cross-platform considerations and best practices for both Windows and Linux compute nodes.
GitHub Create Pull Request
Batch Use Microsoft Entra ID to authenticate Batch Management solutions .../blob/main/articles/batch/batch-aad-auth-management.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-centric tools (Azure portal, .NET library, C# code samples) and patterns. All code samples are in C#, with no mention of Linux, cross-platform, or non-Windows development environments. The workflow assumes use of the Azure portal (which is web-based but often documented with Windows-centric screenshots and terminology) and does not provide equivalent Linux or CLI-based instructions. There are no examples for Linux shell, Python, or other non-Windows languages, nor is there guidance for using open-source or cross-platform tools.
Recommendations
  • Add equivalent examples using Azure CLI and PowerShell, with explicit instructions for both Windows and Linux environments.
  • Provide code samples in additional languages (e.g., Python, Java) that are commonly used on Linux.
  • Include instructions and screenshots for registering applications and granting permissions using CLI tools (az command), not just the Azure portal.
  • Clarify that the authentication process is platform-agnostic and highlight any platform-specific considerations.
  • Reference Linux-compatible SDKs and libraries, and provide links to cross-platform sample projects.
GitHub Create Pull Request
Batch APIs and tools for developers ...zure-docs/blob/main/articles/batch/batch-apis-tools.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates some Windows bias, primarily through the emphasis on PowerShell cmdlets as the first command-line tool mentioned, and the use of Remote Desktop (RDP) for node access, which is a Windows-centric technology. While the Azure CLI is mentioned as cross-platform and Batch Explorer is available for all OSes, the documentation still prioritizes Windows tools and patterns, and does not provide Linux-specific examples or mention SSH access for Linux nodes.
Recommendations
  • Present Azure CLI before PowerShell in the command-line tools section to emphasize cross-platform usage.
  • Include examples or references for accessing Linux compute nodes via SSH, alongside or before RDP instructions.
  • Add Linux-specific troubleshooting steps, such as downloading log files from Linux nodes.
  • Ensure code samples and tutorials are balanced between Windows and Linux environments, and explicitly mention compatibility.
  • Highlight cross-platform capabilities in introductory sections to reinforce parity.
GitHub Create Pull Request
Batch Autoscale compute nodes in an Azure Batch pool ...cs/blob/main/articles/batch/batch-automatic-scaling.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits several signs of Windows bias. Windows-based VM images and tools are mentioned first and more prominently in code samples (especially in .NET/C#), with explicit references to 'MicrosoftWindowsServer' and 'batch.node.windows amd64'. PowerShell cmdlets are listed as a primary method for managing autoscale pools, while Linux equivalents (such as Bash or Linux CLI) are absent or less emphasized. Most code examples (especially in C#) use Windows-centric configurations, and there are no explicit Linux shell or CLI examples for pool creation or management. Although the Python example uses Ubuntu, it is presented after the Windows/.NET example, and there is no parity in showing Linux command-line or scripting approaches.
Recommendations
  • Provide Linux-first or at least Linux-parity examples in all SDK and code sample sections, including .NET and Python.
  • Include explicit Bash/CLI examples for pool creation, autoscale configuration, and management, alongside PowerShell cmdlets.
  • When showing VM image configuration, alternate or equally present both Windows and Linux image references, and clarify cross-platform options.
  • Add notes or sections highlighting differences and best practices for autoscale on Linux pools (e.g., node agent SKUs, OS-specific considerations).
  • Ensure that references to tools (PowerShell, CLI) are balanced and that Linux tools are not omitted or relegated to secondary status.
GitHub Create Pull Request
Batch Create a Batch account in the Azure portal ...lob/main/articles/batch/batch-account-create-portal.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page exhibits Windows bias primarily by providing only PowerShell examples for command-line operations (e.g., accepting marketplace terms), mentioning PowerShell cmdlets before Azure CLI in the 'Other Batch account management options' section, and omitting equivalent Linux/bash commands for key steps. There are no Linux-specific instructions or screenshots, and the documentation assumes familiarity with Windows tools and patterns.
Recommendations
  • Provide equivalent Azure CLI or Bash examples alongside PowerShell commands, especially for steps like accepting marketplace terms.
  • Mention Azure CLI before or alongside PowerShell in tool recommendations to reflect cross-platform parity.
  • Add explicit notes or sections for Linux/macOS users, including any platform-specific considerations or differences in workflow.
  • Include screenshots or instructions that are relevant for Linux users where applicable (e.g., terminal usage, Azure CLI output).
  • Ensure that all command-line instructions are available in both PowerShell and Bash/CLI formats.
GitHub Create Pull Request
Batch Deploy application packages to compute nodes ...blob/main/articles/batch/batch-application-packages.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a Windows bias by providing only Windows-centric code examples (e.g., using 'cmd /c' and Windows environment variable formats), referencing Windows VM images first and exclusively in code, and omitting equivalent Linux shell or usage examples. Windows-specific tools and patterns are mentioned (such as 'cmd /c'), while Linux alternatives (e.g., bash, sh) are not demonstrated. Linux-specific instructions are limited to brief notes about environment variable formatting, without practical code samples.
Recommendations
  • Provide equivalent Linux code examples alongside Windows examples, such as using bash/sh command lines and referencing Linux VM images in sample code.
  • Demonstrate how to access and use application packages on Linux nodes, including environment variable usage and command-line invocation.
  • Mention Linux VM configuration options and node agent SKUs in code samples, not just Windows.
  • Clarify any differences in application package deployment or usage between Windows and Linux nodes.
  • Ensure that all instructions and code samples are presented in parallel for both operating systems to improve parity and inclusivity.
GitHub Create Pull Request
Batch Container workloads on Azure Batch ...ain/articles/batch/batch-docker-container-workloads.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page presents both Windows and Linux support for container workloads in Azure Batch, but there is evidence of Windows bias. Windows support is described before Linux support in the 'Supported VM images' section, and Windows-specific tools and patterns (such as references to C:\ paths, Windows container limitations, and Windows container pool notes) are mentioned. While most code examples use Linux images (Ubuntu), there are no explicit examples for Windows container pools or tasks, and troubleshooting and configuration examples are Linux-centric. The documentation lacks parity in providing Linux and Windows-specific code samples and troubleshooting guidance.
Recommendations
  • Add explicit code examples for Windows container pools and tasks, including PowerShell and C# samples using Windows images.
  • Present Windows and Linux support in parallel, rather than listing Windows first.
  • Include troubleshooting steps and configuration examples for both Windows and Linux containers, such as how to inspect container images and set working directories on Windows.
  • Mention Linux tools and patterns where Windows tools are referenced, and vice versa, to ensure parity.
  • Clarify any differences in container configuration, environment variables, and file system paths between Windows and Linux pools.
GitHub Create Pull Request
Batch Use compute-intensive Azure VMs with Batch ...n/articles/batch/batch-pool-compute-intensive-sizes.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides both Linux and Windows guidance for configuring compute-intensive Azure Batch pools, but there is a noticeable Windows bias. Windows examples (e.g., installing GPU drivers, configuring MPI) are presented first and in greater detail, with explicit references to Windows-specific tools (PowerShell, Remote Desktop, Microsoft MPI). The Linux examples are present but less detailed, and some advanced configuration steps (e.g., using extensions) are described with more Windows-centric tooling. There is also a deprecated section for Windows Cloud Services pools, but no equivalent Linux section. In some cases, Linux instructions are less explicit or rely on external links, and Windows terminology (e.g., 'cmd', 'MSMpiSetup.exe') is used before Linux equivalents.
Recommendations
  • Ensure Linux examples are presented with equal detail and prominence as Windows examples, including step-by-step instructions for installing drivers and configuring MPI workloads.
  • Include Linux-first examples where appropriate, and avoid always listing Windows instructions first.
  • Provide explicit Linux command-line examples (e.g., Bash, apt, wget) for installing drivers and configuring Batch pools, not just links to external articles.
  • Add Linux equivalents for any Windows-specific tooling mentioned (e.g., PowerShell, Remote Desktop), such as SSH or Bash scripts.
  • Remove or balance deprecated Windows-only sections with Linux context or notes.
  • Where application packages or start tasks are described, provide Linux shell command examples alongside Windows 'cmd' examples.
  • Review and update references to Linux OS versions to ensure current, supported releases are used in examples.
GitHub Create Pull Request
Batch Use Azure Pipelines to build and deploy an HPC solution ...ocs/azure-docs/blob/main/articles/batch/batch-ci-cd.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias in several ways. The main example exclusively deploys Windows software (FFmpeg for Windows) on Windows-based Batch nodes, with ARM templates specifying Windows Server images and node agents. There are no Linux-based deployment examples, nor are Linux ARM template snippets or Linux FFmpeg package instructions provided. The build pipeline and repository setup only reference Windows artifacts. The agent pool for Azure Pipelines is set to 'windows-latest' without mention of Linux agents. Although a note states that Azure Batch supports Linux, no practical guidance or parity is offered for Linux users.
Recommendations
  • Add parallel Linux-based examples, including ARM templates for Ubuntu or other Linux VM images and node agents.
  • Provide instructions for downloading and packaging the Linux version of FFmpeg, and show how to upload it as an application package.
  • Demonstrate how to set up the Azure Pipelines agent pool using 'ubuntu-latest' or other Linux agents.
  • Include Linux-specific YAML pipeline snippets and CLI commands where relevant.
  • Explicitly mention Linux support in the repository structure and build/release pipeline setup.
  • Where possible, present Windows and Linux options side-by-side, or alternate which is shown first.
GitHub Create Pull Request
Batch Task runtime environment variables ...cles/batch/batch-compute-node-environment-variables.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: Windows tools (cmd.exe) and patterns are mentioned first and more prominently than Linux equivalents; command-line examples consistently lead with Windows syntax; references to Windows-specific environment variable naming conventions and file paths are more detailed than Linux ones; and some tables and explanations use Windows-centric terminology (e.g., drive letters, backslashes) without equal Linux coverage. Linux examples are present but often secondary or less detailed.
Recommendations
  • Present Linux and Windows examples side-by-side, or alternate which platform is listed first to avoid implicit prioritization.
  • Include PowerShell and Bash examples for environment variable access and expansion, not just cmd.exe and /bin/sh.
  • Clarify Linux-specific environment variable naming conventions and file path formats with equal detail as Windows.
  • Explicitly mention Linux equivalents for Windows concepts (e.g., mount points vs. drive letters) and provide corresponding examples.
  • Ensure all tables and explanations use platform-neutral terminology where possible, or provide both Windows and Linux variants.
  • Add more Linux-specific guidance, especially for advanced scenarios (e.g., using environment variables in Bash scripts, handling mounts on Linux).
GitHub Create Pull Request
Batch Use multi-instance tasks to run MPI applications ...tDocs/azure-docs/blob/main/articles/batch/batch-mpi.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias. All code samples, configuration snippets, and step-by-step instructions use Windows tools (MS-MPI, cmd.exe, Visual Studio), and Batch .NET APIs. Linux alternatives (Intel MPI, Python, Bash) are mentioned only in passing, with no concrete examples or walkthroughs. The guide assumes Windows as the default environment, and Linux support is relegated to notes and external links.
Recommendations
  • Provide parallel Linux-focused code samples using Bash, Python, and Intel MPI.
  • Include explicit instructions for creating Linux pools, installing Intel MPI, and running MPI applications on Linux nodes.
  • Offer a Linux walkthrough (e.g., using Python SDK, shell scripts) alongside the Windows/.NET example.
  • Reference Linux tools and patterns (e.g., mpirun, apt/yum installation) before or alongside Windows equivalents.
  • Add a Linux code sample repository link and highlight its usage in the main flow, not just as a tip.
  • Balance the use of Windows and Linux terminology and tools throughout the documentation.
GitHub Create Pull Request
Batch Storage and data movement for rendering ...rticles/batch/batch-rendering-storage-data-movement.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: Windows-specific tools and patterns (cmdkey, net use) are described in detail with explicit examples, while Linux equivalents (such as mounting Azure Files with SMB or NFS) are not provided. The azcopy usage examples use Windows-style syntax and switches, and the Windows mounting process is explained before any Linux mounting instructions. There is a lack of parity in example depth and step-by-step guidance for Linux users, especially regarding Azure Files and mounting procedures.
Recommendations
  • Add explicit Linux examples for mounting Azure Files shares (e.g., using smbclient, mount.cifs, or NFS) with step-by-step instructions.
  • Provide azcopy command examples using Linux syntax, including bash-style usage and relevant switches.
  • Ensure that for every Windows-specific tool or pattern mentioned (e.g., cmdkey, net use), the Linux equivalent is described with equal detail.
  • Reorder sections or provide parallel instructions so that Linux and Windows approaches are presented side-by-side, rather than Windows-first.
  • Include troubleshooting tips and best practices for Linux environments, such as permissions, automounting, and caching strategies.
GitHub Create Pull Request
Batch Persist output data to Azure Storage with .NET File Conventions library ...n/articles/batch/batch-task-output-file-conventions.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively providing .NET (C#) code samples, referencing Windows-specific tools (Visual Studio 2019), and omitting Linux or cross-platform alternatives. There are no examples or guidance for Linux users, such as using .NET Core/SDK on Linux, or alternative editors and workflows. The documentation also references the WindowsAzure.Storage package and assumes a Windows development environment throughout.
Recommendations
  • Add examples for using the Batch File Conventions library with .NET Core/.NET 6+ on Linux, including command-line workflows and editor alternatives (e.g., VS Code).
  • Include instructions for installing the .NET SDK and running sample code on Linux and macOS, not just Windows.
  • Reference cross-platform tools (e.g., VS Code, JetBrains Rider) alongside Visual Studio, and clarify that the library works on all major operating systems.
  • Provide sample scripts for Linux shells (bash/zsh) to demonstrate environment variable usage and file operations.
  • Mention that the Azure portal and Azure Storage are accessible from any OS, and clarify any OS-specific requirements or limitations.
  • Ensure that any references to Windows-specific packages (e.g., WindowsAzure.Storage) are updated to their cross-platform equivalents or alternatives.
GitHub Create Pull Request
Batch Persist job and task output to a data store ...ure-docs/blob/main/articles/batch/batch-task-output.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias by providing examples and references that are specific to Windows environments, such as referencing .exe files and Windows command patterns, without offering equivalent Linux examples or guidance. The documentation also mentions Windows nodes explicitly and does not provide parity for Linux users in terms of sample commands, scripts, or tool usage.
Recommendations
  • Include Linux-specific examples alongside Windows examples, such as shell scripts (.sh) and Linux command patterns.
  • When referencing custom file movement solutions, provide sample commands for both Windows (e.g., .exe) and Linux (e.g., bash scripts or Python scripts).
  • Explicitly mention Linux nodes and provide guidance for persisting output on Linux compute nodes.
  • Ensure that references to tools (such as Azure Storage Explorer) are cross-platform, and clarify usage on both Windows and Linux.
  • Add a sample project or code snippets for Linux environments, similar to the provided C#/.NET sample for Windows.
GitHub Create Pull Request
Batch Use the Azure Compute Gallery to create a custom image pool ...zure-docs/blob/main/articles/batch/batch-sig-images.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows tools and patterns (RDP, PowerShell) are mentioned before or more prominently than their Linux equivalents (SSH, Bash). For example, PowerShell is listed first when referencing APIs to list supported images, and RDP is described before SSH for node connection. The portal workflow emphasizes Windows (RDP) before Linux (SSH). There are no explicit Bash or Linux shell command examples, and PowerShell is referenced more than Linux CLI. No Linux-specific troubleshooting or patterns are discussed.
Recommendations
  • Present Linux and Windows tools/examples in parallel, or alternate which is listed first.
  • Add Bash or Linux shell command examples alongside PowerShell, especially for listing supported images and gallery definitions.
  • Include Linux-specific troubleshooting and best practices (e.g., SELinux, mounting disks, SSH key management).
  • In portal instructions, mention SSH connection for Linux nodes before or alongside RDP for Windows.
  • Ensure that references to OS-specific tools (e.g., RDP, PowerShell) are balanced with Linux equivalents (SSH, Bash, cloud-init).
  • Add explicit examples for Linux image creation and validation, including CLI commands and portal screenshots if possible.
GitHub Create Pull Request
Batch Persist output data to Azure Storage with Batch service API ...cs/blob/main/articles/batch/batch-task-output-files.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. All code samples use Windows-centric commands (e.g., 'cmd /v:ON /c'), and there are no Linux shell equivalents provided. The examples use C#/.NET libraries and reference Visual Studio as the development environment, with no mention of cross-platform alternatives or Linux tooling. Linux-specific instructions are limited to a single note about changing backslashes to forward slashes, and there are no Linux shell script examples or guidance for non-Windows environments.
Recommendations
  • Provide equivalent Linux shell (bash) examples for task commands, such as using 'bash -c' or similar.
  • Include code samples using cross-platform SDKs (e.g., Python, Java) and show how to persist output from Linux-based tasks.
  • Mention and demonstrate development environments available on Linux (e.g., VS Code, JetBrains Rider) alongside Visual Studio.
  • Explicitly address file path differences and provide examples for both Windows and Linux.
  • Reference Linux tools and patterns (e.g., tar, zip, bash scripting) in the section about consolidating output files.
  • Add troubleshooting steps and log file locations for Linux nodes, not just Windows.
  • Clarify that the Batch service API and Azure Storage libraries are cross-platform, and link to documentation for Linux usage.
GitHub Create Pull Request
← Previous Page 4 of 18 Next →