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 126-150 of 436 flagged pages
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-automatic-scaling.md ...cs/blob/main/articles/batch/batch-automatic-scaling.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 Windows bias in several ways. Windows-based VM images and configuration patterns are presented first and in more detail, especially in .NET/C# examples. Windows-specific tools (PowerShell cmdlets) are mentioned before cross-platform alternatives, and C#/.NET examples use Windows VM images by default. There is a lack of parity in Linux-focused examples, especially in the .NET section, and no explicit Linux shell or CLI examples are provided. Python examples do use Ubuntu images, but overall, Windows is prioritized and Linux usage is not equally represented.
Recommendations
  • Provide .NET/C# examples that use Linux VM images (e.g., Ubuntu or other supported distros) alongside Windows examples.
  • Ensure that references to tools (PowerShell, CLI) are balanced, and include Linux shell (bash) or cross-platform CLI examples where possible.
  • When listing SDKs and APIs, avoid mentioning Windows-specific tools first; present cross-platform options together or alternate order.
  • Add explicit Linux-focused configuration and usage examples for all major SDKs, including REST, .NET, and Python.
  • Clarify that autoscale features work equally well with both Windows and Linux pools, and link to documentation for Linux node setup.
  • Include troubleshooting or tips sections for both Windows and Linux environments.
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-docker-container-workloads.md ...ain/articles/batch/batch-docker-container-workloads.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 some Windows bias. Windows VM images and considerations are presented before Linux equivalents in the 'Supported VM images' section. There are several references to Windows-specific paths (e.g., C:\ProgramData\Docker, c:\app\myApp.exe) and behaviors (ephemeral disk mapping, Windows container limitations) without equivalent Linux details. Example code for container tasks includes a Windows path and command line, but does not provide a Linux shell example for the same scenario. There is also a lack of parity in troubleshooting and advanced configuration examples, which tend to reference Windows specifics more than Linux.
Recommendations
  • Ensure Linux examples are presented alongside Windows examples, especially for container task command lines and working directory configuration.
  • Provide equivalent Linux shell command examples where Windows paths and commands are shown (e.g., show '/app/myApp' and '/bin/bash' examples next to 'c:\app\myApp.exe').
  • Balance the order of presentation so that Linux and Windows are treated equally in lists and explanations, rather than Windows-first.
  • Add troubleshooting steps and advanced configuration examples for Linux containers, not just Windows.
  • Where Windows-specific limitations or behaviors are described, include Linux-specific notes for parity.
  • Avoid using only Windows paths in code samples; provide Linux alternatives or use platform-neutral notation.
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-compute-node-environment-variables.md ...cles/batch/batch-compute-node-environment-variables.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 Windows bias by consistently listing Windows tools and patterns before their Linux equivalents, such as referencing 'cmd.exe' before '/bin/sh' and using Windows-style environment variable syntax and examples first. Windows-specific details (e.g., drive letters, app package naming conventions) are described in greater depth, while Linux examples are less prominent or missing in some cases. There is a lack of parity in example coverage and explanation for Linux users.
Recommendations
  • Alternate the order of Windows and Linux examples throughout the documentation, or present them side-by-side.
  • Provide equal detail for Linux-specific environment variable naming conventions and usage patterns.
  • Include explicit Linux command-line examples wherever Windows examples are given (e.g., show both 'cmd /c set' and 'printenv' for variable inspection).
  • Clarify Linux-specific behaviors for file paths, mounts, and application package installation.
  • Add a dedicated section summarizing Linux usage patterns and caveats, similar to any Windows-focused sections.
  • Ensure all environment variable examples and directory postfix tables include both Windows and Linux formats.
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-pool-compute-intensive-sizes.md ...n/articles/batch/batch-pool-compute-intensive-sizes.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 Windows and Linux guidance for configuring Azure Batch pools with HPC and GPU VMs, but there are several signs of Windows bias. Windows examples and tools (such as PowerShell, Remote Desktop, Microsoft MPI) are presented in detail and sometimes before Linux equivalents. The Windows pool configuration section is longer and includes deprecated options not mirrored for Linux. Example walkthroughs for Windows (including PowerShell commands and RDP) are more explicit, while Linux examples are less detailed and lack step-by-step commands. Some references and links (e.g., for MPI jobs) prioritize Windows or use older Linux content. There is also a tendency to mention Windows tools and patterns (e.g., application package install via cmd) before or instead of Linux equivalents.
Recommendations
  • Ensure Linux examples are as detailed as Windows, including explicit step-by-step instructions and command-line samples (e.g., Bash commands for installing drivers, using SSH, etc.).
  • Present Linux and Windows options in parallel, rather than listing Windows first or in more depth.
  • Include Linux-specific tools and workflows (e.g., using apt, wget, SSH, Bash scripts) in example sections.
  • Avoid referencing deprecated Windows-only features (like Cloud Services Configuration pools) without Linux context.
  • Update links to Linux MPI documentation to point to current, official sources rather than archived blogs.
  • Where PowerShell or Windows-specific commands are shown, provide equivalent Bash/Linux commands.
  • Highlight Linux Marketplace images and extensions with the same prominence as Windows options.
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-mpi.md ...tDocs/azure-docs/blob/main/articles/batch/batch-mpi.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 are exclusively for Windows environments, using MS-MPI, Windows Server VM images, and Windows command-line tools (cmd.exe). The only references to Linux or Intel MPI are brief notes, with no Linux-specific code samples, installation instructions, or walkthroughs. The page assumes use of Visual Studio and Windows-centric development workflows, and does not provide parity for Linux users.
Recommendations
  • Add Linux-specific code samples using Python or Bash, demonstrating Intel MPI setup and usage.
  • Provide instructions for creating pools with Linux VM images, including relevant configuration properties.
  • Include StartTask examples for installing Intel MPI on Linux nodes, using shell commands.
  • Show equivalent multi-instance task configuration and execution commands for Linux (e.g., using mpiexec/mpirun in Bash).
  • Offer guidance for Linux-based development environments (e.g., VS Code, CLI tools) and alternative to Visual Studio.
  • Ensure that Linux examples are presented alongside Windows examples, not just as afterthoughts or notes.
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-rendering-storage-data-movement.md ...rticles/batch/batch-rendering-storage-data-movement.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 and patterns (cmdkey, net use) are described in detail with explicit examples, while Linux equivalents (such as mounting Azure Files via SMB or NFS) are not provided. The azcopy examples use Windows-style syntax and switches, and Windows mounting instructions precede any Linux mounting guidance. There is a lack of parity in example depth and clarity for Linux users, especially regarding mounting Azure Files and file system operations.
Recommendations
  • Add explicit Linux examples for mounting Azure Files shares (e.g., using mount.cifs or NFS) in Batch pool VMs, including sample command lines and configuration steps.
  • Provide azcopy examples using Linux shell syntax and flags, clarifying differences in usage between platforms.
  • Ensure that for every Windows-specific tool or pattern mentioned (cmdkey, net use), the Linux equivalent is described with equal detail and visibility.
  • Reorder sections or provide parallel instructions so that Linux and Windows approaches are presented side-by-side, improving discoverability for Linux users.
  • Include troubleshooting tips and best practices for Linux environments, such as permissions, credential management, and persistent mounts.
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-sig-images.md ...zure-docs/blob/main/articles/batch/batch-sig-images.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits a moderate Windows bias. Windows tools and patterns (e.g., RDP, PowerShell) are mentioned before or more prominently than their Linux equivalents (e.g., SSH, Bash). PowerShell is listed as the first API/tool for listing supported images, and RDP is described before SSH in portal instructions. There are references to Windows-specific practices (RDP, temp drive expectations) and tools (PowerShell cmdlets) without equal emphasis on Linux alternatives. Some examples and notes are Windows-centric, and Linux-specific guidance is less detailed or appears after Windows instructions.
Recommendations
  • Present Linux and Windows examples in parallel, or alternate which is listed first.
  • Include Bash or shell script examples alongside PowerShell where relevant.
  • When listing tools/APIs, mention Azure CLI and REST API before or alongside PowerShell.
  • In portal instructions, describe SSH login for Linux before or equally with RDP for Windows.
  • Expand Linux-specific guidance (e.g., mounting disks, temp drive expectations) to match Windows detail.
  • Ensure that all steps and notes are equally applicable to both OS types, or provide OS-specific sections.
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-pool-update-properties.md ...ob/main/articles/batch/batch-pool-update-properties.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 providing only a Windows-based VM image update example (using MicrosoftWindowsServer and batch.node.windows amd64), with no Linux equivalent shown. The C# SDK example exclusively references Windows images and node agent SKUs, and there are no Linux or cross-platform code samples. Windows terminology and tools are mentioned first and exclusively in the example sections.
Recommendations
  • Provide parallel examples for updating Linux-based pools, including Linux VM image references and node agent SKUs in code samples.
  • Include at least one example using a Linux image (e.g., Ubuntu, CentOS) in both the C# SDK and REST API sections.
  • Use more neutral or cross-platform language in examples and explanations, or explicitly show both Windows and Linux options.
  • If referencing Windows-specific tools or patterns, ensure Linux equivalents are also mentioned and documented.
  • Consider adding a table or section comparing Windows and Linux pool property update considerations, if any differences exist.
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-task-dependencies.md ...cs/blob/main/articles/batch/batch-task-dependencies.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exclusively provides examples using Windows-specific tools (cmd.exe), and all code samples use Windows command syntax. There are no Linux/bash equivalents, nor any mention of cross-platform considerations. The documentation implicitly assumes a Windows environment, which may mislead or inconvenience Linux users.
Recommendations
  • Include Linux/bash equivalents alongside Windows examples (e.g., use 'bash -c "echo Flowers"' or 'sh -c "echo Flowers"' in addition to 'cmd.exe /c echo Flowers').
  • Add a section discussing cross-platform task execution, clarifying how to specify commands for Linux compute nodes.
  • Explicitly mention that Azure Batch supports both Windows and Linux pools, and provide guidance on writing portable task commands.
  • Where possible, use generic command examples or highlight differences between Windows and Linux task configuration.
  • Ensure that sample projects and code snippets demonstrate both Windows and Linux scenarios.
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-task-output-files.md ...cs/blob/main/articles/batch/batch-task-output-files.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 strong Windows bias: all code samples use C# and Windows command syntax (cmd.exe), with no Linux shell or cross-platform examples. Windows-specific tools (Visual Studio, .exe files) are referenced exclusively, and Linux considerations are only mentioned as afterthoughts (e.g., 'change backslashes to forward slashes'). There are no examples for Linux shells (bash), nor guidance for running on Linux nodes. The documentation assumes development on Windows with .NET and Visual Studio, omitting parity for Linux environments.
Recommendations
  • Provide equivalent Linux shell (bash) command examples for task execution, demonstrating how to generate output files on Linux nodes.
  • Include code samples using cross-platform languages (e.g., Python) and SDKs, not just C#/.NET.
  • Add instructions for running sample projects on Linux (e.g., using VS Code, CLI tools, or other IDEs), not just Visual Studio.
  • Explicitly document file path differences and provide examples using forward slashes and Linux conventions.
  • Reference Linux-compatible application packaging and deployment methods, not just Windows .exe and zip.
  • Clarify any platform-specific limitations or requirements for persisting output, and provide troubleshooting steps for Linux environments.
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-task-output-file-conventions.md ...n/articles/batch/batch-task-output-file-conventions.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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), and omitting Linux or cross-platform usage instructions. There are no examples or guidance for using the Batch File Conventions library from Linux environments, nor any mention of alternative development tools or shell environments. The instructions and samples assume a Windows development workflow, which may hinder Linux users from adopting the library or Azure Batch features.
Recommendations
  • Add explicit instructions and code samples for using the Batch File Conventions standard from Linux environments, such as with .NET Core/SDK on Linux, or via other languages (e.g., Python, Java).
  • Include guidance for setting up development environments on Linux, such as using VS Code, JetBrains Rider, or command-line .NET tools.
  • Provide sample scripts for common Linux shells (bash/zsh) to demonstrate environment variable usage and file handling.
  • Reference cross-platform package managers and installation methods (e.g., dotnet CLI, apt-get, yum) for .NET SDK and Azure libraries.
  • Clarify that the File Conventions standard can be implemented in any language and provide links or examples for non-.NET implementations.
  • Avoid language in instructions that assumes Windows-only workflows (e.g., "Open the project in Visual Studio 2019") and offer alternatives for Linux/Mac users.
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-task-output.md ...ure-docs/blob/main/articles/batch/batch-task-output.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 instructions that reference Windows-specific patterns (e.g., .exe files, Windows command syntax) without offering equivalent Linux examples. The sample command for custom file movement only mentions Windows executables, and there is no mention of Linux shell scripts or tools. Additionally, there is an emphasis on .NET and C# libraries, which are more commonly used on Windows, with no parity for Linux-native languages or tools.
Recommendations
  • Include Linux-specific examples alongside Windows ones, such as using shell scripts (.sh) and Linux command syntax.
  • Mention Linux equivalents when discussing custom file movement solutions, e.g., 'doMyWork.sh && uploadMyFilesToSql.sh' for Linux nodes.
  • Provide guidance or sample code for persisting output using Python, Bash, or other Linux-friendly languages.
  • Clarify that the Batch File Conventions standard can be implemented in any language and provide a cross-platform sample.
  • Ensure that references to tools (such as Azure Storage Explorer) are presented as cross-platform where applicable.
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-user-accounts.md ...e-docs/blob/main/articles/batch/batch-user-accounts.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 several types of Windows bias. Windows-specific tools and APIs (such as Windows Data Protection API and RDP) are mentioned before or instead of Linux equivalents. Example code and scenarios often use Windows-centric command lines (e.g., 'cmd /c echo') and VM images (WindowsServer) before Linux examples. There is a lack of parity in showing Linux-specific commands or tools, and the documentation does not provide Linux shell command examples for tasks, nor does it mention Linux alternatives to Windows-specific APIs. The initial connection instructions also prioritize RDP for Windows before SSH for Linux.
Recommendations
  • Provide Linux shell command examples (e.g., 'bash -c "echo hello"') alongside Windows 'cmd /c' examples in all code snippets.
  • Mention Linux tools and APIs (such as GnuPG, OpenSSL, or Linux file permissions) when discussing scenarios like secret sharing, in addition to Windows DPAPI.
  • Ensure Linux connection instructions (SSH) are presented before or alongside Windows (RDP) instructions.
  • Include Linux-specific code snippets and configuration details for all supported languages, not just for pool creation but also for task execution.
  • Balance the order of presentation so that Linux and Windows scenarios/examples are given equal prominence.
  • Add references to Linux security practices and isolation mechanisms where Windows-specific security notes are present.
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-upgrade-policy.md ...-docs/blob/main/articles/batch/batch-upgrade-policy.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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-based examples for pool creation (both REST and SDK), referencing Windows-specific properties and images, and omitting any Linux equivalents or examples. The REST and C# SDK examples exclusively use MicrosoftWindowsServer images and Windows-specific configuration fields, with no mention of Linux images, agent SKUs, or configuration options. The requirements section discusses Windows Update and Windows-specific patching, without addressing Linux update mechanisms.
Recommendations
  • Include parallel examples for Linux pool creation, showing how to use Ubuntu or other supported Linux images in both REST and SDK sections.
  • Document Linux-specific configuration options, such as nodeAgentSKUId for Linux and any relevant OS update/patching settings.
  • Add notes or sections describing differences in OS upgrade behavior between Windows and Linux pools.
  • Ensure that references to supported OS images explicitly mention Linux options and provide links or lists.
  • Balance the order of presentation so that Linux is mentioned alongside Windows, rather than only after or not at all.
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/create-pool-ephemeral-os-disk.md ...b/main/articles/batch/create-pool-ephemeral-os-disk.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing PowerShell as the primary method for programmatically checking ephemeral OS disk support, without mentioning Linux alternatives (such as Azure CLI or Bash). The only tool-specific example is PowerShell, and no Linux shell or cross-platform command is provided. Additionally, Windows tools and patterns are mentioned before any Linux equivalents, and there are no explicit Linux-oriented examples for querying VM capabilities.
Recommendations
  • Provide Azure CLI and Bash examples for querying VM capabilities and ephemeral OS disk support, alongside the PowerShell example.
  • Mention cross-platform tools (e.g., Azure CLI) before or alongside Windows-specific tools like PowerShell.
  • Add explicit notes or sections for Linux users, clarifying how to perform the same tasks on Linux systems.
  • Ensure that code and command-line examples are balanced between Windows and Linux environments to improve parity.
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/create-pool-public-ip.md ...docs/blob/main/articles/batch/create-pool-public-ip.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates bias toward Windows by listing Azure PowerShell as a method for creating public IP addresses alongside Azure CLI and the portal, with PowerShell mentioned explicitly and without equivalent Linux shell examples. The order of tools places PowerShell after CLI, but the lack of Linux-specific shell (e.g., Bash) or scripting examples, and no mention of Linux-native tools or patterns, reinforces a Windows-centric approach. Additionally, no Linux command-line examples (such as Bash scripts or references to Linux package managers) are provided, and the documentation does not clarify cross-platform compatibility for the listed tools.
Recommendations
  • Include explicit Bash or Linux shell examples for creating public IP addresses using Azure CLI.
  • Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
  • Add guidance or links for installing and using Azure CLI on Linux systems.
  • Avoid listing PowerShell as a primary method unless parity is provided for Linux users (e.g., Bash equivalents).
  • Consider reordering tool lists to start with platform-neutral or Linux-friendly options (e.g., Azure CLI, Bash) before mentioning PowerShell.
  • Add notes or sections highlighting Linux usage patterns and best practices for Azure Batch pool creation.
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/monitor-application-insights.md ...ob/main/articles/batch/monitor-application-insights.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 strong Windows bias. All examples and instructions assume a Windows environment, including exclusive use of Visual Studio, Windows-specific NuGet packages (Microsoft.ApplicationInsights.WindowsServer), PowerShell commands, and Windows VM images for Azure Batch pools. There are no Linux equivalents or cross-platform instructions, and Linux tools or patterns are not mentioned.
Recommendations
  • Provide Linux-specific instructions for setting up Application Insights in Azure Batch, including using .NET Core/SDK on Linux.
  • Include examples for installing NuGet packages via the dotnet CLI (e.g., 'dotnet add package') and shell commands, not just PowerShell.
  • Mention and demonstrate how to configure and run Application Insights on Linux-based compute nodes, including using Linux VM images in Azure Batch pools.
  • Clarify whether the sample code and configuration are compatible with Linux, and if not, provide guidance or alternative samples.
  • Reference cross-platform development tools (e.g., VS Code, JetBrains Rider) alongside Visual Studio.
  • Add notes or sections highlighting differences or additional steps required for Linux environments.
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/best-practices.md .../azure-docs/blob/main/articles/batch/best-practices.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates moderate Windows bias. Windows-specific tools (PowerShell) and patterns are mentioned before or more prominently than Linux equivalents in several places, especially in disk preparation and troubleshooting. Some examples and recommendations are Windows-centric, with Linux alternatives provided later or less thoroughly. Certain sections, such as directory junctions and service management, focus on Windows-specific issues or solutions, while Linux guidance is less detailed or omitted.
Recommendations
  • Ensure Linux and Windows examples are presented with equal prominence and detail, ideally side-by-side.
  • When referencing tools (e.g., PowerShell), also mention equivalent Linux commands (e.g., bash scripts, fdisk, mkfs) in the same context.
  • Provide sample scripts for both Windows (PowerShell) and Linux (bash) for common operations such as disk initialization, log collection, and service management.
  • Avoid Windows-first ordering in lists and examples; alternate or group by OS where possible.
  • Expand Linux-specific troubleshooting and best practices sections to match the depth provided for Windows.
  • Where Windows-only issues are discussed (e.g., directory junctions), provide equivalent Linux guidance (e.g., symlinks, mount points) for parity.
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/manage-private-endpoint-connections.md .../articles/batch/manage-private-endpoint-connections.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by presenting PowerShell examples before Azure CLI, referencing the Az PowerShell module prominently, and using Windows-centric scripting patterns. The Azure portal instructions also implicitly favor Windows users. There are no explicit Linux shell examples (e.g., Bash-specific syntax), nor is there mention of Linux-specific tooling or usage patterns.
Recommendations
  • Alternate the order of PowerShell and Azure CLI examples, or present CLI examples first to improve parity.
  • Explicitly mention that Azure CLI commands work cross-platform (Windows, Linux, macOS) and provide Bash-specific variable syntax where appropriate.
  • Include Linux/Bash-specific notes, such as differences in environment variable usage or shell quoting.
  • Add a section or note highlighting Linux compatibility and usage patterns for managing private endpoint connections.
  • Consider providing examples using other automation tools common on Linux (e.g., scripting with Bash, using REST API via curl).
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/nodes-and-pools.md ...azure-docs/blob/main/articles/batch/nodes-and-pools.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 mild Windows bias. Windows-specific tools and patterns (such as PowerShell scripts, .exe, .cmd, .bat files, and RDP for remote access) are mentioned before their Linux equivalents. Examples and explanations often list Windows formats first, and container support highlights Windows Server 2016 Datacenter with Containers before mentioning custom Linux images. There is a lack of explicit Linux command/script examples, and Linux tooling is referenced less frequently or only as a secondary option.
Recommendations
  • Ensure Linux examples (e.g., shell scripts, Python scripts) are provided alongside Windows examples in relevant sections.
  • Mention Linux tools (e.g., SSH for remote access, shell scripting) before or equally with Windows tools (e.g., RDP, PowerShell).
  • Provide explicit Linux container image examples and instructions, not just Windows Server-based ones.
  • Add more references to Linux-specific documentation and workflows, such as mounting and formatting disks using Linux commands.
  • Balance the order of OS mentions so that Windows and Linux are treated equally throughout the documentation.
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/monitor-batch.md ...s/azure-docs/blob/main/articles/batch/monitor-batch.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 primarily referencing Windows-centric tools and libraries (such as Batch Explorer and the Batch .NET library) and providing examples and walkthroughs only for .NET (Windows-first) solutions. There are no Linux-specific examples, nor are cross-platform or Linux command-line tools (such as Azure CLI, Bash, or Python SDK) mentioned or demonstrated. The Application Insights integration walkthrough is exclusively for .NET, with no mention of Linux or cross-platform alternatives.
Recommendations
  • Add examples using Azure CLI and/or PowerShell, and ensure both are presented side-by-side or with equal prominence.
  • Include sample code and walkthroughs for monitoring Batch using Python SDK, which is cross-platform and widely used on Linux.
  • Reference and demonstrate Linux-native tools and workflows, such as Bash scripts for accessing storage logs, or using jq for JSON parsing.
  • Provide Application Insights integration examples for non-.NET languages (e.g., Python, Java) and clarify platform support.
  • Explicitly mention cross-platform compatibility for tools like Batch Explorer, and provide installation instructions for Linux/macOS.
  • Where .NET is referenced, also mention alternative SDKs (Python, Java) and link to their documentation.
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/security-best-practices.md ...cs/blob/main/articles/batch/security-best-practices.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. Windows-specific tools (such as PowerShell) are mentioned for discovering supported images, and Windows OS-specific configuration (TLS/cipher suites) is discussed in detail, with direct links to Windows documentation. Linux is acknowledged as supported, but Linux-specific examples, tools, or configuration guidance are missing or less prominent. Windows tools and patterns are referenced before Linux equivalents, and there is a lack of parity in example coverage and operational details for Linux environments.
Recommendations
  • Provide Linux-specific examples and guidance for key operations, such as discovering supported images (e.g., using Bash, Azure CLI, or REST API from Linux).
  • Include links to Linux documentation for configuring SSL/TLS and cipher suites, similar to the Windows section.
  • Ensure parity in operational details for both Windows and Linux, such as how to manage OS-level security settings, automatic updates, and custom images.
  • When referencing tools (e.g., PowerShell), also mention and provide examples for Azure CLI and Bash scripts.
  • Balance the order of presentation so that Linux and Windows are treated equally, or alternate which is presented first.
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/quick-create-portal.md ...e-docs/blob/main/articles/batch/quick-create-portal.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively demonstrates creating a pool of Windows compute nodes and provides only Windows command-line examples (using 'cmd' and 'timeout'). There is no mention of Linux node options, nor are Linux shell commands or patterns shown. The quickstart implicitly assumes a Windows environment for both node configuration and task execution.
Recommendations
  • Include instructions and screenshots for creating a pool of Linux compute nodes, such as selecting an Ubuntu or CentOS image.
  • Provide equivalent Linux shell command examples for tasks (e.g., using 'bash -c "env; sleep 90"').
  • Explicitly mention that both Windows and Linux nodes are supported, and guide users on choosing the appropriate OS for their workloads.
  • Add notes or sections highlighting differences in environment variables, command syntax, and output locations between Windows and Linux nodes.
  • Ensure parity in examples and guidance for both platforms throughout the quickstart.
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/quick-run-dotnet.md ...zure-docs/blob/main/articles/batch/quick-run-dotnet.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 Server images for compute nodes, Windows command-line tools (cmd /c type), and Windows-specific VM configuration in code examples. There are no Linux equivalents or examples provided, and Windows patterns are mentioned first and exclusively throughout the quickstart.
Recommendations
  • Include examples for creating pools with Linux VM images, such as Ubuntu or CentOS, alongside the Windows example.
  • Provide sample task command lines using Linux shell commands (e.g., bash -c 'cat <filename>') in addition to Windows cmd examples.
  • Explicitly mention that Batch supports both Windows and Linux nodes, and guide users on how to select and configure Linux pools.
  • Show code snippets for specifying Linux nodeAgentSkuId and ImageReference for popular Linux distributions.
  • Add notes or sections on differences in task deployment and script execution between Windows and Linux nodes.
  • Ensure parity in troubleshooting and output viewing instructions for both operating systems.
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/tutorial-parallel-dotnet.md ...s/blob/main/articles/batch/tutorial-parallel-dotnet.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows bias by exclusively using Windows Server VM images for the compute pool, referencing only Windows builds of ffmpeg, and providing command-line examples that use Windows-specific syntax (cmd.exe). There are no Linux VM pool configuration examples, nor any Linux/Unix shell command-line equivalents for running ffmpeg. The tutorial does not mention how to use Linux images or ffmpeg on Linux nodes, nor does it provide parity for Linux users in the sample code or instructions.
Recommendations
  • Add examples and instructions for configuring a Batch pool with a Linux VM image (e.g., Ubuntu).
  • Include sample code and command-line syntax for running ffmpeg on Linux nodes (e.g., using bash and ./ffmpeg).
  • Provide download links and instructions for obtaining ffmpeg for Linux, alongside the Windows version.
  • Show how to set up the ApplicationPackageReference for Linux pools, including any differences in path or execution.
  • Explicitly mention cross-platform support and clarify any differences in setup or execution between Windows and Linux nodes.
  • Where possible, use platform-agnostic code and instructions, or provide side-by-side examples for both Windows and Linux.
GitHub Create Pull Request
← Previous Page 6 of 18 Next →