Batch

228
Total Pages
164
Linux-Friendly Pages
64
Pages with Bias
28.1%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

156 issues found
Showing 51-75 of 156 flagged pages
Batch Azure Batch pool create event ...cs/blob/main/articles/batch/batch-pool-create-event.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page shows a notable Windows bias. Windows-specific concepts (such as Cloud Services pools, Guest OS families, and windowsConfiguration) are described in detail, while Linux equivalents are either missing or referenced only briefly. Windows VM sizes and OS families are discussed first and at length, with Linux information relegated to links or notes. There are no Linux-specific configuration examples or explanations for Linux node settings.
Recommendations
  • Add explicit examples and explanations for Linux pool configurations, including Linux-specific node agent IDs and imageReference values.
  • Provide parity in documentation for Linux operating system settings, similar to the windowsConfiguration section.
  • Reorder sections to present Linux and Windows options equally, or provide side-by-side comparisons.
  • Clarify which configuration options apply to Linux pools and provide links to relevant Linux documentation.
  • Include a Linux-focused example event body and configuration walkthrough.
GitHub Create Pull Request
Batch Copy applications and data to pool nodes ...ain/articles/batch/batch-applications-to-pool-nodes.md
Medium Priority View Details →
Scanned: 2026-01-12 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 a Windows bias by referencing Windows-specific file types (.exe, .msi) and installation patterns, such as installing applications with .msi files and referencing .exe executables. There are no examples or mentions of Linux/macOS equivalents (e.g., .sh scripts, tarballs, or package managers), nor are there instructions or examples for Linux-specific application deployment. The examples and terminology assume a Windows environment, making it less accessible for Linux/macOS users.
Recommendations
  • Include examples for Linux/macOS, such as installing applications via shell scripts (.sh), using tarballs, or leveraging package managers (apt, yum).
  • Mention Linux/macOS file types and installation patterns alongside Windows examples.
  • Provide guidance on setting up start tasks and job preparation tasks for Linux nodes, including sample command lines.
  • Clarify that Azure Batch supports both Windows and Linux nodes, and highlight any differences in application/data deployment between platforms.
  • Avoid using Windows-specific terminology exclusively (e.g., .msi, .exe) or ensure Linux/macOS equivalents are presented in parallel.
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
Medium Priority View Details →
Scanned: 2026-01-12 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 notable Windows bias. The main example deploys Windows software (FFmpeg for Windows) on Windows-based Batch nodes, and the ARM template for the Batch pool is hardcoded to use Windows Server images. The repository setup and build pipeline instructions exclusively reference the Windows version of FFmpeg, with no mention of Linux alternatives or how to adapt the process for Linux-based Batch nodes. The agent pool for the release pipeline is set to 'windows-latest', and all screenshots and instructions implicitly assume a Windows environment. There are no Linux or cross-platform examples, nor guidance for users wishing to deploy Linux applications or use Linux Batch pools.
Recommendations
  • Add parallel examples for deploying Linux software (e.g., FFmpeg for Linux) on Linux-based Batch nodes.
  • Provide ARM template snippets for creating Batch pools with Linux VM images (e.g., Ubuntu).
  • Include instructions for downloading and packaging Linux versions of FFmpeg, and clarify any differences in build/release pipeline steps.
  • Mention how to select 'ubuntu-latest' or other Linux agent pools in Azure Pipelines.
  • Add notes or sections highlighting cross-platform support and how to adapt the process for Linux/macOS users.
  • Ensure screenshots and YAML examples show both Windows and Linux agent pool options.
GitHub Create Pull Request
Batch Deploy application packages to compute nodes ...blob/main/articles/batch/batch-application-packages.md
Medium Priority View Details →
Scanned: 2026-01-12 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 exhibits a notable Windows bias. Code examples for deploying and executing application packages on compute nodes are exclusively in C# using the Batch .NET library, with all sample VM configurations and command lines referencing Windows (e.g., WindowsServer images, 'cmd /c', Windows-style environment variables, and .exe files). Linux equivalents (such as using a Linux VM image, bash command lines, or Linux application binaries) are not provided, and Windows-specific patterns and tools are mentioned first or exclusively. While the documentation does mention Linux nodes in passing (e.g., environment variable formatting), it does not provide concrete Linux-focused examples or guidance.
Recommendations
  • Add parallel Linux examples for all code snippets, including pool creation with a Linux VM image and task command lines using bash (e.g., '/bin/bash -c ...') and Linux application binaries.
  • Show how environment variables and application package paths should be used on Linux nodes, with sample command lines.
  • Include guidance on differences in application ID restrictions and environment variable formatting for Linux, with practical examples.
  • Reference and provide examples using cross-platform SDKs (e.g., Python, REST API) where possible, not just .NET.
  • Explicitly mention Linux/macOS support and any caveats or best practices for those platforms.
GitHub Create Pull Request
Batch Autoscale compute nodes in an Azure Batch pool ...cs/blob/main/articles/batch/batch-automatic-scaling.md
Medium Priority View Details →
Scanned: 2026-01-12 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 a moderate Windows bias. Windows and .NET examples are presented first and in greater detail, with C# code snippets dominating the SDK sections. The .NET example uses a Windows Server VM image, while the Python example uses Ubuntu, but overall, Windows tooling and terminology (e.g., PowerShell cmdlets, .NET APIs) are referenced more frequently and with more guidance. There are no explicit Linux shell or CLI examples, and PowerShell is mentioned as a primary tool for Batch management, with no parity for Bash or Linux-native tools.
Recommendations
  • Provide Linux/Bash CLI examples alongside PowerShell, especially for common tasks like pool creation and autoscale configuration.
  • Alternate the order of examples so that Linux and Windows are equally represented (e.g., show Python/Ubuntu first in some sections).
  • Include explicit instructions for using Azure Batch CLI on Linux/macOS, with sample commands.
  • Reference Linux-native tools (e.g., Bash scripts, Azure CLI) where PowerShell is mentioned.
  • Ensure that VM image references are balanced (e.g., show both Windows and Linux VM configuration snippets in .NET and Python examples).
GitHub Create Pull Request
Batch Use compute-intensive Azure VMs with Batch ...n/articles/batch/batch-pool-compute-intensive-sizes.md
Medium Priority View Details →
Scanned: 2026-01-12 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 Azure Batch pools with HPC and GPU VM sizes, but there is a notable Windows bias. Windows examples and tools (such as PowerShell and Remote Desktop) are described in more detail and appear first in several sections. The example for installing NVIDIA GPU drivers on Windows is more explicit and step-by-step than the Linux equivalent, which is more abstract and refers to external links. The Microsoft MPI example is Windows-only, with no Linux MPI installation walkthrough. Windows-specific tools and patterns (PowerShell, RDP, MSI installers) are mentioned without Linux equivalents (e.g., SSH, shell scripts).
Recommendations
  • Provide Linux-first or parallel examples for all major scenarios, especially for MPI workloads and driver installation.
  • Include explicit Linux command-line instructions (e.g., using SSH, Bash scripts) where Windows uses PowerShell or RDP.
  • Add a step-by-step example for installing Intel MPI or OpenMPI on Linux pools, mirroring the Windows MPI example.
  • Ensure that Linux tools and workflows (e.g., apt, wget, shell scripting) are mentioned and demonstrated alongside Windows tools.
  • Clarify any differences in driver installation or configuration between Linux and Windows, and provide troubleshooting tips for both.
GitHub Create Pull Request
Batch Storage and data movement for rendering ...rticles/batch/batch-rendering-storage-data-movement.md
Medium Priority View Details →
Scanned: 2026-01-12 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 more detailed and explicit examples for Windows environments, especially in the Azure Files section, where only Windows mounting instructions and command-line examples (cmdkey, net use) are given. Linux equivalents (e.g., mounting Azure Files via SMB/cifs) are not described or referenced. In the azcopy section, Windows-style command syntax is shown first, and there is no explicit Linux shell example. Windows tools and patterns (cmdkey, net use, mapped drives) are mentioned exclusively or before Linux alternatives. The blobfuse section is Linux-specific, but lacks parity in example depth compared to Windows Azure Files mounting. Overall, Linux users may need to seek external resources to complete equivalent tasks.
Recommendations
  • Add explicit Linux mounting instructions for Azure Files (e.g., using mount.cifs or SMB tools) with sample commands.
  • Provide Linux shell examples for azcopy usage, showing syntax differences if any.
  • Ensure that for every Windows-specific tool or pattern (cmdkey, net use), the Linux/macOS equivalent is described and demonstrated.
  • Balance example depth and clarity between Windows and Linux sections, especially for mounting and accessing file shares.
  • Consider reordering or parallelizing examples so that Windows and Linux instructions are presented side-by-side where possible.
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
Medium Priority View Details →
Scanned: 2026-01-12 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 a moderate Windows bias. Windows tools (PowerShell, RDP) are frequently mentioned first or exclusively, and some examples or instructions prioritize Windows scenarios. Linux equivalents (SSH, CLI) are present but often secondary, and some steps lack explicit Linux guidance or examples.
Recommendations
  • Present Linux and Windows examples side-by-side, or alternate which is shown first.
  • Include explicit Linux command-line examples (e.g., mounting disks, SSH instructions) wherever Windows (RDP, PowerShell) is mentioned.
  • Expand on Linux-specific considerations (e.g., file system formatting, OS disk requirements) in the VM preparation section.
  • Reference Linux tools (e.g., Bash, cloud-init) alongside Windows tools (PowerShell, RDP) in relevant steps.
  • Clarify any OS-specific requirements or differences in the pool creation and image preparation process.
GitHub Create Pull Request
Batch Update pool properties ...ob/main/articles/batch/batch-pool-update-properties.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides code examples exclusively for Windows environments (C# SDK using Windows VM image and node agent SKU), with no equivalent Linux or cross-platform examples. The VM image update example explicitly uses a Windows image and node agent, and there are no Linux VM image or Linux node agent examples. This may create friction for Linux users who need guidance for their platform.
Recommendations
  • Include parallel examples for updating pools with Linux VM images and node agent SKUs.
  • Provide code samples in cross-platform languages (e.g., Python, CLI) and show both Windows and Linux configurations.
  • Explicitly mention Linux support and provide guidance for Linux-specific scenarios.
  • Ensure REST API examples show both Windows and Linux pool property updates.
GitHub Create Pull Request
Batch Create task dependencies to run tasks ...cs/blob/main/articles/batch/batch-task-dependencies.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively provides examples using Windows tools (cmd.exe), with all code snippets invoking 'cmd.exe /c echo ...' for task commands. There are no Linux or macOS shell examples (e.g., bash), nor any mention of cross-platform command patterns. The documentation implicitly assumes a Windows environment, which may create friction for Linux/macOS users.
Recommendations
  • Add equivalent Linux/macOS shell examples (e.g., 'bash -c "echo Flowers"') alongside Windows examples in all code snippets.
  • Explicitly mention that the task command can be any shell supported by the compute node OS, and provide guidance for both Windows and Linux pools.
  • Clarify that 'cmd.exe' is specific to Windows nodes, and suggest using '/bin/bash' or '/bin/sh' for Linux nodes.
  • Include a section or note on cross-platform task command authoring, highlighting differences and best practices.
GitHub Create Pull Request
Batch Use ephemeral OS disk nodes for Azure Batch pools ...b/main/articles/batch/create-pool-ephemeral-os-disk.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits Windows bias by referencing PowerShell as the only example for programmatically querying VM capabilities and mentioning Windows-centric tools without providing Linux or cross-platform alternatives. There are no CLI (az), Bash, or Linux-specific examples for key tasks such as checking VM support for ephemeral OS disks, which may hinder Linux/macOS users.
Recommendations
  • Provide equivalent Azure CLI (az) or Bash examples for querying VM capabilities, alongside PowerShell.
  • Explicitly mention cross-platform tools and commands where possible, not just Windows/PowerShell options.
  • Ensure that any referenced scripts or commands are available and documented for Linux/macOS users.
  • Consider listing CLI or REST API examples before or alongside PowerShell to promote platform neutrality.
GitHub Create Pull Request
Batch Use extensions with Batch pools ...ocs/blob/main/articles/batch/create-pool-extensions.md
Medium Priority View Details →
Scanned: 2026-01-12 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 provides examples and references for both Linux and Windows, but there is a slight bias towards Windows. Windows-specific extensions and tools are listed before or more frequently than their Linux equivalents, and some extension types (e.g., diagnostics, antimalware, HPC GPU drivers) are Windows-only or Windows-first. Troubleshooting and health monitoring sections do not provide explicit Linux-specific guidance or examples, and the Application Health extension description is generic but lacks Linux-specific considerations.
Recommendations
  • Ensure Linux and Windows extensions are listed in parallel, with equal detail and order.
  • Add explicit Linux troubleshooting steps and log file locations for extensions, matching the Windows guidance.
  • Provide Linux-specific examples for health monitoring and diagnostics, including relevant tools and log paths.
  • Highlight any extension features or limitations that differ between Linux and Windows.
  • Where extensions are Windows-only, clearly state Linux alternatives or note the absence.
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
Medium Priority View Details →
Scanned: 2026-01-12 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 any Linux/macOS-specific instructions or examples. All sample code assumes a Windows development environment and does not mention how to use the Batch File Conventions standard or library from Linux or macOS, nor does it provide guidance for cross-platform development or alternative languages. The instructions for running the sample project are tailored to Windows users, with no mention of Linux-compatible IDEs or command-line usage.
Recommendations
  • Provide equivalent code samples for Linux/macOS environments, such as using .NET Core/SDK on Linux, or alternative languages that support the Batch File Conventions standard.
  • Include instructions for setting up and running the sample project on Linux/macOS, such as using VS Code, JetBrains Rider, or the dotnet CLI.
  • Mention cross-platform compatibility of the File Conventions library and clarify any OS-specific limitations.
  • Add references to Linux/macOS tools and workflows (e.g., how to install dependencies, run the sample, or use Azure CLI).
  • Explicitly state that the library and samples can be used on non-Windows platforms if applicable.
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
Medium Priority View Details →
Scanned: 2026-01-12 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 exhibits a notable Windows bias: all code samples use C# and Windows command syntax (cmd.exe), with no Linux shell equivalents provided. Windows-specific tools (Visual Studio, .exe files) are referenced exclusively, and instructions for running samples assume a Windows environment. Linux is only mentioned in a note about changing path separators, with no Linux/macOS shell or tool examples. There are no Bash or cross-platform code samples, and the Batch File Conventions library is only available for .NET.
Recommendations
  • Provide Linux/macOS shell (e.g., Bash) equivalents for task command lines, including examples using sh/bash syntax.
  • Include instructions for running sample projects on Linux/macOS, possibly using .NET Core/SDK and VS Code.
  • Show how to create containers and SAS tokens using Azure CLI or SDKs in Python/JavaScript, not just .NET.
  • Reference cross-platform tools and editors (e.g., VS Code) alongside Visual Studio.
  • Clarify how Linux users can implement file conventions and output persistence, with sample code in other languages.
  • Add explicit Linux/macOS code samples for key steps, such as uploading files and handling output patterns.
GitHub Create Pull Request
Batch Provision a pool with Auto OS Upgrade ...-docs/blob/main/articles/batch/batch-upgrade-policy.md
Medium Priority View Details →
Scanned: 2026-01-12 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 notable Windows bias. All example configurations (REST API and C# SDK) use Windows-specific images (MicrosoftWindowsServer), Windows node agent SKUs, and Windows configuration properties. There are no Linux image examples, nor any mention of Linux-specific configuration options or node agent SKUs. The only OS-specific property discussed is 'windowsConfiguration.enableAutomaticUpdates', with no Linux equivalent or guidance. This creates friction for Linux users seeking parity or guidance.
Recommendations
  • Add parallel examples using Linux images (e.g., Ubuntu, CentOS) in both REST API and SDK sections.
  • Document Linux-specific configuration properties, such as 'linuxConfiguration', and node agent SKUs for Linux pools.
  • Explicitly mention supported Linux OS images and provide links or lists.
  • Clarify any differences in upgrade behavior or requirements for Linux pools.
  • Ensure that Linux examples are presented alongside or before Windows examples to avoid implicit prioritization.
GitHub Create Pull Request
Batch Run tasks under user accounts ...e-docs/blob/main/articles/batch/batch-user-accounts.md
Medium Priority View Details →
Scanned: 2026-01-12 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 demonstrates a moderate Windows bias. Windows-specific tools and patterns (e.g., RDP, DPAPI, 'cmd /c echo', Windows VM image references) are mentioned before or more prominently than Linux equivalents. Code examples often use Windows-centric commands, and the initial named user account example is for Windows. Linux-specific details (e.g., SSH, Linux VM configuration) are present but less emphasized and sometimes appear after Windows examples. Some scenarios (like DPAPI usage) reference Windows-only solutions without Linux alternatives.
Recommendations
  • Ensure Linux examples are presented alongside Windows examples, not after them.
  • Provide Linux-specific command line examples (e.g., use 'bash -c "echo hello"' instead of 'cmd /c echo hello').
  • Mention Linux tools and patterns (e.g., SSH, file permissions) with equal prominence to Windows tools (e.g., DPAPI, RDP).
  • Where Windows-only solutions are referenced (e.g., DPAPI), provide Linux alternatives or explicitly state the Linux approach.
  • In code snippets, alternate the order of Windows and Linux examples, or present them together.
  • Add more context and examples for Linux-specific user account configuration and usage.
GitHub Create Pull Request
Batch Best practices .../azure-docs/blob/main/articles/batch/best-practices.md
Medium Priority View Details →
Scanned: 2026-01-12 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 a moderate Windows bias. Windows-specific tools (PowerShell) and examples are mentioned first or exclusively in several places, especially for tasks like discovering image EOL dates and preparing data disks. Linux equivalents are sometimes mentioned, but not always with equal detail or prominence. Some sections provide Windows-only examples or scripts, while Linux instructions are less detailed or omitted.
Recommendations
  • Ensure that every Windows-specific example (e.g., PowerShell commands) is paired with an equivalent Linux example (e.g., Bash/CLI commands) and vice versa.
  • Present Linux and Windows tooling in parallel, rather than listing Windows tools first.
  • Provide sample scripts for Linux where PowerShell scripts are given for Windows (e.g., disk initialization).
  • Where Windows-specific issues (e.g., directory junctions) are discussed, include Linux-specific filesystem notes for parity.
  • Explicitly mention cross-platform alternatives for all management tasks (e.g., using Azure CLI, REST API, or Bash scripts).
GitHub Create Pull Request
Batch Monitor Azure Batch ...s/azure-docs/blob/main/articles/batch/monitor-batch.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. It references Windows-centric tools such as Batch Explorer and the Batch .NET library, and provides walkthroughs and code samples specifically for .NET (a Windows-first technology). There are no examples or guidance for Linux/macOS users, such as using Python SDKs, CLI commands, or cross-platform monitoring tools. The documentation does not mention Linux-specific patterns or alternatives, and Windows tools are presented as the default or only option.
Recommendations
  • Add examples using cross-platform tools, such as Azure CLI or PowerShell Core (which runs on Linux/macOS).
  • Include sample code for monitoring Batch using the Python SDK, which is widely used on Linux/macOS.
  • Mention and provide links to Linux-compatible monitoring and diagnostic tools, such as azcopy, Azure Storage Explorer (cross-platform), or REST API usage from Bash.
  • Clarify that Batch Explorer is available for Windows, macOS, and Linux (if true), or suggest alternatives for non-Windows users.
  • Provide guidance for integrating Application Insights or other monitoring solutions in non-.NET languages (e.g., Python, Java).
GitHub Create Pull Request
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
Medium Priority View Details →
Scanned: 2026-01-12 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 notable Windows bias. The compute pool is created with Windows Server nodes only, and all task command line examples use Windows-specific tools (cmd, set, timeout). There are no Linux pool creation instructions, nor any Linux shell (bash/sh) command examples. This may create friction for users intending to use Linux nodes or familiar with Linux scripting.
Recommendations
  • Add instructions for creating a pool of Linux compute nodes, including selecting a Linux image in the portal.
  • Provide equivalent Linux shell command line examples for tasks (e.g., using bash to display environment variables and sleep).
  • Explicitly mention that both Windows and Linux pools are supported and link to relevant documentation for Linux usage.
  • Consider presenting both Windows and Linux examples side-by-side, or allow users to select their preferred OS for examples.
GitHub Create Pull Request
Batch Mount a virtual file system on a pool ...re-docs/blob/main/articles/batch/virtual-file-mount.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is used as the primary scripting language for both Windows and Linux examples, rather than showing native Bash or shell commands for Linux. Windows-specific tools and patterns (e.g., 'cmdkey', 'net use', RDP) are described in detail, sometimes before their Linux equivalents. Troubleshooting and manual mounting instructions are more verbose and tool-centric for Windows, with Linux instructions following a similar structure but lacking native Linux command examples. The documentation does provide Linux parity in most sections, but the overall approach and example ordering favor Windows users.
Recommendations
  • Provide native Bash or shell script examples for Linux, especially for mounting and troubleshooting steps, rather than relying solely on PowerShell.
  • Include Linux-first examples in relevant sections, or alternate the order to avoid always presenting Windows first.
  • Expand troubleshooting steps for Linux to include common Linux commands (e.g., 'mount', 'ls', 'cat') and typical error messages.
  • Reference Linux-specific tools and documentation (e.g., 'mount.cifs', 'mount.nfs', 'blobfuse') more prominently.
  • Clarify when PowerShell is required on Linux, and offer alternatives for users who prefer native Linux tools.
GitHub Create Pull Request
Batch Azure Quickstart - Create a Batch account - Azure Resource Manager template ...docs/blob/main/articles/batch/quick-create-template.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation primarily describes deploying an ARM template using the Azure portal, with only a brief mention of alternative methods (Azure PowerShell, Azure CLI, REST API) in a single sentence. The link for further deployment methods points to a PowerShell-focused page, and there are no explicit Linux/macOS CLI examples or screenshots. Windows-centric tools and patterns (portal, PowerShell) are mentioned before Linux-friendly options (CLI), and Linux users are not shown parity in deployment steps.
Recommendations
  • Add explicit step-by-step instructions for deploying the ARM template using Azure CLI, including example commands.
  • Provide links to Linux/macOS-specific documentation or ensure referenced pages cover both PowerShell and CLI equally.
  • Include screenshots or terminal output examples for Azure CLI on Linux/macOS.
  • Mention cross-platform tools (e.g., Azure CLI) before or alongside Windows-specific tools (PowerShell, portal).
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
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example Powershell Heavy
Summary
The documentation is notably Windows-centric: it exclusively demonstrates creating pools of Windows Server nodes, uses Windows command-line tools (e.g., 'cmd /c type'), and provides only Windows VM image references. There are no Linux pool or command-line examples, and the workflow assumes Windows environments for both compute nodes and task execution. While .NET and Visual Studio are cross-platform, the quickstart does not show how to use Linux VMs or run Linux commands, nor does it mention Linux-specific considerations for Batch jobs.
Recommendations
  • Add examples for creating Batch pools with Linux VM images (e.g., Ubuntu, CentOS) using VirtualMachineConfiguration.
  • Provide sample code for tasks that run Linux shell commands (e.g., 'bash -c cat {filename}') in the CommandLine property.
  • Clarify that Azure Batch supports both Windows and Linux compute nodes, and link to documentation on Linux pool configuration.
  • Show how to build and run the sample app on Linux/macOS (e.g., using dotnet CLI), and mention any platform-specific requirements.
  • Present Windows and Linux options side-by-side, or alternate which is shown first in examples.
GitHub Create Pull Request
Batch Batch security and compliance best practices ...cs/blob/main/articles/batch/security-best-practices.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation page is generally cross-platform, but there are several signs of Windows bias. Windows-specific tools (such as PowerShell) are mentioned for discovering supported images, with no equivalent Linux CLI example given. Windows OS configuration details (TLS/cipher suites) are discussed in depth, with direct links to Windows Server documentation, while Linux equivalents are not covered. In some sections, Windows is referenced first or exclusively, and Windows management tools are highlighted before Linux alternatives.
Recommendations
  • Provide Azure CLI examples alongside PowerShell for tasks such as listing supported images.
  • Include Linux-specific guidance for OS-level security settings (e.g., configuring TLS/cipher suites on Linux nodes).
  • When discussing OS support or configuration, present Linux and Windows information in parallel, rather than focusing on Windows first.
  • Add references to Linux documentation for security hardening and compliance.
  • Ensure that any Windows-specific links or instructions are matched with Linux equivalents where possible.
GitHub Create Pull Request
Batch Tutorial: Run a parallel workload using the .NET API ...s/blob/main/articles/batch/tutorial-parallel-dotnet.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example Powershell Heavy
Summary
The tutorial exhibits notable Windows bias: it exclusively references Windows 64-bit ffmpeg builds, configures Azure Batch pools with Windows Server images only, and provides command-line examples using Windows-specific syntax (cmd /c, .exe paths). There are no Linux/macOS pool configuration examples, nor guidance for using Linux-compatible ffmpeg packages or shell syntax. The sample app and workflow are tailored to Windows environments, creating friction for Linux/macOS users.
Recommendations
  • Add explicit instructions and examples for configuring Azure Batch pools with Linux VM images (e.g., Ubuntu).
  • Provide guidance for downloading and packaging Linux-compatible ffmpeg builds.
  • Include sample task command lines using Linux shell syntax (e.g., bash, ./ffmpeg) alongside Windows examples.
  • Clarify how to adapt the sample code and application package references for Linux pools.
  • Mention cross-platform considerations for .NET SDK usage and ffmpeg invocation.
  • Present Linux/macOS examples in parallel with Windows, not as an afterthought.
GitHub Create Pull Request
Batch Container workloads on Azure Batch ...ain/articles/batch/batch-docker-container-workloads.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation provides both Windows and Linux information, but there are signs of Windows bias: Windows VM images and considerations are often mentioned first or in more detail; Windows-specific tooling and paths (e.g., C:\ProgramData\Docker) are referenced alongside Linux equivalents; C# examples use Windows-style paths and commands; troubleshooting and working directory sections reference Windows container limitations and behaviors before Linux. There are no explicit PowerShell examples, but the overall pattern and language favor Windows, and Linux-specific examples (e.g., for troubleshooting, custom images, or start tasks) are less prominent.
Recommendations
  • Ensure Linux examples and references are presented before or alongside Windows equivalents, especially in code and configuration sections.
  • Provide Linux-specific troubleshooting steps and examples, such as inspecting containers, managing permissions, and handling working directories.
  • Include Linux shell command examples (e.g., bash) where Windows commands are shown, especially in C# code snippets.
  • Clarify differences in container runtime and configuration between Windows and Linux, with equal detail for both.
  • Add explicit Linux start task examples and more guidance for custom Linux images, including common issues and solutions.
GitHub Create Pull Request
← Previous Page 3 of 7 Next →