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 151-175 of 436 flagged pages
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/virtual-file-mount.md ...re-docs/blob/main/articles/batch/virtual-file-mount.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 demonstrates a moderate Windows bias. PowerShell is used as the primary scripting interface for both Windows and Linux examples, rather than showing native Linux shell commands. Windows-specific tools and patterns (e.g., 'cmdkey', 'net use', drive letters) are described in detail, and Windows troubleshooting steps and terminology often appear before or more prominently than their Linux equivalents. Native Linux mounting commands (e.g., 'mount -t cifs', 'mount -t nfs') are not shown, and the Linux experience is consistently presented through a Windows-centric lens.
Recommendations
  • Provide native Linux shell (bash) command examples for mounting file systems, in addition to or instead of PowerShell, especially for manual mounting and troubleshooting.
  • Balance the order of presentation so that Linux and Windows instructions/examples are given equal prominence, or alternate which comes first.
  • Include Linux-native troubleshooting steps and commands (e.g., using 'mount', 'lsblk', 'dmesg', 'journalctl') alongside Windows tools.
  • Where Windows-specific tools (like 'cmdkey', 'net use') are mentioned, provide the Linux equivalents (e.g., 'mount -t cifs', 'mount -t nfs', 'cifs-utils', 'nfs-common') with example commands.
  • Clarify when PowerShell is being used on Linux, and consider whether bash or shell scripts would be more familiar to Linux users.
  • Link to both Windows and Linux official mounting documentation with equal visibility in the 'Next steps' and throughout the page.
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-applications-to-pool-nodes.md ...ain/articles/batch/batch-applications-to-pool-nodes.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 referencing Windows-specific file types (.exe, .msi) and installation patterns without mentioning Linux equivalents. There are no examples or guidance for Linux application packaging or installation methods (e.g., .sh scripts, .deb/.rpm packages), nor are Linux tools or patterns (such as chmod, tar, apt, yum) discussed. The page implicitly assumes Windows environments by default, omitting Linux-specific instructions and examples.
Recommendations
  • Add Linux-specific examples alongside Windows ones, such as installing .deb/.rpm packages, running shell scripts (.sh), or using tarballs.
  • Explicitly mention Linux installation patterns and tools (e.g., apt, yum, chmod, bash scripts) in relevant sections.
  • When referencing file types (e.g., .exe, .msi), also reference Linux equivalents (.sh, .deb, .rpm) and provide parallel instructions.
  • Include cross-platform sample commands for start tasks and job preparation tasks, showing both PowerShell/Batch and Bash/Shell script usage.
  • Clarify that Azure Batch supports both Windows and Linux nodes, and provide guidance for each OS where applicable.
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-08 00:53
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 examples for Windows OS images (MicrosoftWindowsServer) in both REST API and SDK code samples. There is no mention or example of Linux OS images or Linux-specific configuration properties. Additionally, Windows-specific properties (such as windowsConfiguration and enableAutomaticUpdates) are discussed, while Linux equivalents are omitted. No Linux tools, patterns, or examples are provided.
Recommendations
  • Add parallel examples for Linux pools, using popular Linux OS images (e.g., Ubuntu, CentOS) in both REST API and SDK sections.
  • Include Linux-specific configuration properties and explain their usage, such as linuxConfiguration and relevant agent SKUs.
  • Mention Linux patching/update mechanisms and how Auto OS Upgrade interacts with them.
  • Ensure that any references to OS-specific settings (e.g., enableAutomaticUpdates) are balanced with Linux equivalents or notes.
  • Provide guidance for both Windows and Linux users in all code and configuration samples.
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/credential-access-key-vault.md ...lob/main/articles/batch/credential-access-key-vault.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias: all code examples use PowerShell, certificate creation is described only with Windows tools, and installation instructions focus on Windows Management Framework and .msi installers. There are no Linux shell or cross-platform examples, nor any mention of Linux certificate creation or management tools. The workflow assumes a Windows environment throughout, and Linux parity is only referenced in a 'next steps' link, not in the main content.
Recommendations
  • Add equivalent Linux/bash examples for certificate creation (e.g., using openssl).
  • Provide instructions for creating and managing certificates on Linux Batch nodes.
  • Include Azure CLI examples alongside PowerShell for service principal and Key Vault access.
  • Describe how to install necessary libraries/tools on Linux nodes (e.g., Azure CLI, Python SDK).
  • Explicitly mention cross-platform support and note any differences in workflow for Linux nodes.
  • Reorder examples or provide parallel instructions so Windows and Linux users are equally supported.
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/managed-identity-pools.md ...ocs/blob/main/articles/batch/managed-identity-pools.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a mild Windows bias. In the section on obtaining managed identity tokens within Batch nodes, the PowerShell (Windows) example is presented before the Bash (Linux) example. Additionally, the documentation refers to the Azure Instance Metadata Service using a Windows-specific documentation link. While both Windows and Linux examples are ultimately provided, the ordering and reference patterns subtly prioritize Windows environments.
Recommendations
  • Present Linux and Windows examples in parallel or alternate which comes first, or explicitly state that both are equally supported.
  • When referencing the Azure Instance Metadata Service, use a neutral or dual-platform documentation link, or mention both Windows and Linux documentation.
  • Ensure that tooling and code samples (e.g., .NET, PowerShell) are balanced with equivalent CLI or SDK examples commonly used on Linux, such as Azure CLI or Python SDK.
  • Consider including explicit Linux-first examples in some sections, especially when the majority of Azure Batch pools may run Linux workloads.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a strong Windows bias. The tutorial exclusively uses Windows VM images for the compute pool, references only the Windows build of ffmpeg, and provides command-line examples using Windows syntax (cmd /c, .exe). There are no Linux VM pool configuration examples, nor any Linux shell command lines for running ffmpeg. The documentation does not mention how to adapt the workflow for Linux compute nodes, nor does it provide parity for Linux users in terms of setup or execution.
Recommendations
  • Add examples and instructions for creating a Batch pool with a Linux VM image (e.g., Ubuntu).
  • Provide guidance on downloading and packaging the Linux build of ffmpeg.
  • Include sample command lines for running ffmpeg on Linux (e.g., bash syntax, ./ffmpeg).
  • Clarify how to set up ApplicationPackageReference for Linux nodes.
  • Mention differences in environment variables and file paths between Windows and Linux nodes.
  • Ensure that all steps (pool creation, job/task creation, command lines) have Linux equivalents presented alongside Windows instructions.
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-account-create-portal.md ...lob/main/articles/batch/batch-account-create-portal.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a bias toward Windows by providing only PowerShell command examples for required configuration steps (such as accepting Marketplace terms), with no equivalent Bash, Azure CLI, or cross-platform alternatives. The only command-line tooling referenced for these steps is PowerShell, and there are no Linux-specific or cross-platform instructions for these critical setup tasks. Additionally, the 'Other Batch account management options' section lists PowerShell cmdlets before Azure CLI, and the .NET SDK is mentioned before Python, further reinforcing a Windows-centric perspective.
Recommendations
  • Provide Azure CLI command examples alongside PowerShell for all command-line steps, especially for accepting Marketplace terms and other configuration tasks.
  • Explicitly mention that PowerShell commands can be run on Linux/macOS using Azure PowerShell, or provide Bash/CLI equivalents where possible.
  • In 'Other Batch account management options', list Azure CLI before or alongside PowerShell cmdlets to emphasize cross-platform support.
  • Where .NET SDK is mentioned, ensure Python and other cross-platform SDKs are given equal prominence.
  • Add a note or section clarifying that all steps can be performed from any OS, and link to cross-platform tooling documentation.
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-08 00:53
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 mild Windows bias. Windows tools and patterns (e.g., cmd.exe, drive letters, backslash paths) are mentioned first or exclusively in several places. Examples for environment variable expansion and retrieval are given for both Windows and Linux, but Windows is consistently listed first. Some environment variable naming conventions and directory structures are described in detail for Windows, with Linux equivalents sometimes mentioned as an aside or in parentheses. The use of Windows-specific terminology (e.g., drive letters, backslashes) is more prominent than Linux equivalents, and some examples (such as path postfixes) use Windows-style formatting without parallel Linux examples.
Recommendations
  • Alternate the order of Windows and Linux examples throughout the documentation to avoid consistently prioritizing Windows.
  • Provide Linux-specific examples for all environment variable usages, including path formats and directory structures (e.g., show both /mnt/... and C:\... formats where relevant).
  • Explicitly mention Linux equivalents for all Windows-specific terminology (e.g., drive letters vs. mount points, backslashes vs. forward slashes).
  • Ensure that environment variable naming conventions and examples are given equal detail for both platforms, including casing and separator differences.
  • Consider adding a summary table or section that clearly contrasts Windows and Linux behaviors, tools, and conventions for Azure Batch environment variables.
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-application-packages.md ...blob/main/articles/batch/batch-application-packages.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 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 environment variable usage examples. Windows-specific tools and patterns (such as referencing 'cmd /c' and Windows path conventions) are presented without Linux alternatives, and Windows node configuration is shown before mentioning Linux differences.
Recommendations
  • Provide parallel Linux examples for all code snippets, including task command lines using bash/sh and Linux path conventions.
  • Show how to configure pools with Linux VM images (e.g., Ubuntu) in code samples, not just Windows.
  • Explicitly mention and demonstrate Linux environment variable usage and formatting in code, including how to reference installed applications in Linux tasks.
  • Balance the order of presentation so that Linux and Windows are treated equally (e.g., alternate examples or provide both side-by-side).
  • Reference Linux-specific considerations, such as file permissions, shell differences, and package extraction commands, where relevant.
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-aad-auth-management.md .../blob/main/articles/batch/batch-aad-auth-management.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Missing Linux Example Windows First 🔧 Windows Tools
Summary
The documentation is heavily focused on Windows-centric tools and workflows, specifically targeting .NET and referencing the Azure portal UI, with all code samples in C#. There are no examples or guidance for Linux users, non-.NET languages, or command-line alternatives (such as Azure CLI or PowerShell Core on Linux). The documentation uses terms like 'Windows Azure Service Management API' and does not mention Linux or cross-platform development explicitly.
Recommendations
  • Include equivalent examples using Azure CLI and/or REST API calls, which are cross-platform and commonly used on Linux.
  • Provide code samples in additional languages (such as Python or JavaScript) that are popular in Linux environments.
  • Mention that the Azure portal and Microsoft Entra ID are accessible from any OS, not just Windows.
  • Clarify that the .NET SDK and MSAL libraries are cross-platform and can be used on Linux and macOS as well as Windows.
  • Add a section or note on how to perform application registration and permission granting using CLI tools (e.g., az ad app create, az ad app permission add) for users who prefer or require non-GUI workflows.
  • Avoid using 'Windows Azure' terminology where 'Azure' suffices, to reduce the perception of Windows exclusivity.
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-apis-tools.md ...zure-docs/blob/main/articles/batch/batch-apis-tools.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates mild Windows bias, primarily through the prominent mention of PowerShell cmdlets as the first command-line tool for Azure Batch, and references to Windows-specific tools and workflows such as Remote Desktop (RDP) file downloads for node access. While the Azure CLI and cross-platform tools are mentioned, Windows-centric patterns and tools are introduced first or exclusively (e.g., PowerShell, RDP), with less emphasis on Linux-native equivalents or workflows.
Recommendations
  • Present Azure CLI as the primary cross-platform command-line tool before PowerShell, emphasizing its parity and suitability for both Linux and Windows users.
  • Include explicit examples or references for Linux-native access methods (e.g., SSH for node access) alongside or before Windows-specific methods like RDP.
  • Provide code samples and tutorials that highlight Linux usage, such as Bash scripts or Linux shell commands, to balance the existing PowerShell/C# focus.
  • Clarify that PowerShell is available cross-platform, but also offer Bash or shell script alternatives for common tasks.
  • Ensure that tool download links and instructions are equally visible for Mac and Linux users, not just Windows.
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-ci-cd.md ...ocs/azure-docs/blob/main/articles/batch/batch-ci-cd.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a clear Windows bias. The example solution 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 equivalents or examples provided, and the repository setup, build, and deployment instructions all assume Windows artifacts. The agent pool for pipelines is set to 'windows-latest', and scripting tasks use PowerShell Core, with no mention of Bash or Linux-based agents. Windows tools and patterns are referenced throughout, while Linux alternatives are missing.
Recommendations
  • Provide parallel examples for deploying Linux software (e.g., FFmpeg for Linux) on Linux-based Batch nodes.
  • Include ARM template snippets for Linux pool configuration (e.g., Ubuntu or CentOS images, Linux node agent SKU).
  • Show how to set up the repository and pipelines for Linux application packages, including build and artifact steps.
  • Offer instructions for using 'ubuntu-latest' or other Linux agents in Azure Pipelines, and demonstrate Bash scripting tasks.
  • Explicitly mention Linux support in relevant sections, and link to Linux-focused tutorials.
  • Balance screenshots and walkthroughs to show both Windows and Linux scenarios.
GitHub Create Pull Request
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-08 00:53
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 node agent SKUs are shown first and exclusively in .NET code examples, while Linux equivalents are only present in Python examples. Windows terminology (e.g., PowerShell cmdlets) is mentioned before cross-platform tools like the CLI. There are no explicit Linux-focused .NET or PowerShell examples, and sample code for .NET consistently uses Windows VM images. The documentation does not provide parity for Linux in .NET or PowerShell, nor does it highlight Linux usage patterns or troubleshooting.
Recommendations
  • Add .NET code examples that use Linux VM images (e.g., Ubuntu) and node agent SKUs for Linux.
  • Include PowerShell examples for creating and managing autoscale pools with Linux VM images.
  • Present cross-platform tools (CLI, REST API) before or alongside Windows-specific tools (PowerShell), and clarify their OS compatibility.
  • Explicitly mention Linux support and provide troubleshooting tips or notes for Linux pools where relevant.
  • Ensure that all SDK examples (including .NET and PowerShell) demonstrate both Windows and Linux pool creation and autoscaling.
  • Balance the order of presentation so that Linux and Windows are treated equally in examples and tool references.
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-08 00:53
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. The main examples, code snippets, and step-by-step instructions exclusively use Windows compute nodes, MS-MPI, and Windows-centric tools (cmd.exe, Visual Studio, .NET, etc.). Linux alternatives (Intel MPI, Python) are mentioned only in passing, with no equivalent code samples, setup instructions, or walkthroughs. The page assumes a Windows development environment and workflow, and Linux-specific guidance is relegated to brief notes or external links.
Recommendations
  • Provide parallel Linux-focused examples for each major section, including pool creation, MPI installation (using Intel MPI), and multi-instance task setup using Bash or Python.
  • Include code snippets for Linux environments (e.g., Bash scripts for installing Intel MPI, running mpiexec, and configuring coordination/application commands).
  • Offer step-by-step instructions for building and deploying MPI applications on Linux nodes, including compiling with gcc/mpicc and packaging for Azure Batch.
  • Reference Linux development tools (e.g., VS Code, gcc, mpicc) alongside Windows tools like Visual Studio.
  • Ensure that sample applications and walkthroughs are available for both Windows (MS-MPI) and Linux (Intel MPI/Python), with links to relevant GitHub repositories.
  • Reorder or balance the documentation so that Linux and Windows approaches are presented with equal prominence, rather than Windows-first.
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-08 00:53
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 VM sizes. However, there is a noticeable Windows bias: Windows examples and tools (such as PowerShell, Remote Desktop, and Microsoft MPI) are described in more detail and often appear before Linux equivalents. The Windows-specific example steps are more explicit, including command lines and tool usage, while Linux examples are less detailed and lack equivalent command-line instructions. Some configuration steps (e.g., using PowerShell or RDP) are only described for Windows, and Windows-centric tools are referenced without Linux alternatives.
Recommendations
  • Ensure Linux examples are as detailed as Windows ones, including explicit command-line instructions for driver installation and configuration.
  • Provide Linux-specific tooling examples (e.g., Bash scripts, SSH usage) where Windows uses PowerShell or RDP.
  • Present Linux and Windows examples in parallel, or alternate which comes first, to avoid 'windows_first' ordering.
  • Reference Linux equivalents for Windows tools (e.g., mention OpenMPI alongside Microsoft MPI, provide links to Linux documentation for remote management).
  • Where Windows-specific extensions or drivers are mentioned, ensure Linux alternatives are equally highlighted and described.
  • Add more scenario examples for Linux, such as configuring MPI workloads with OpenMPI, and provide troubleshooting steps for Linux pools.
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-08 00:53
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, mapped drives) are described in detail before Linux equivalents, with full command-line examples for Windows but none for Linux mounting of Azure Files. The azcopy examples use Windows-style syntax and switches, and there is no parity for Linux shell examples. The Azure Files section is focused on Windows, with only a brief mention of Linux options elsewhere. Linux-specific tools (e.g., blobfuse) are mentioned but not given the same depth of example or procedural detail.
Recommendations
  • Provide equivalent Linux shell command examples for azcopy usage, including syntax and switches.
  • Add detailed instructions and sample commands for mounting Azure Files shares on Linux (e.g., using SMB/CIFS mount commands).
  • Ensure that Linux tools and workflows (such as blobfuse and NFS mounting) are described with the same level of detail and example code as Windows tools.
  • When listing options or tools, present Windows and Linux approaches side-by-side or in parallel sections to avoid Windows-first ordering.
  • Include troubleshooting notes and best practices for Linux environments, matching those provided for Windows.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Windows Example 🔧 Windows Tools Windows Terms
Summary
The documentation page provides a balanced overview of both Windows and Linux support for container workloads on Azure Batch, but exhibits a subtle Windows bias in several areas. Windows is frequently mentioned first in lists and section headings (e.g., 'Windows support' precedes 'Linux support'), and Windows-specific terms (such as C:\ProgramData\Docker, Windows container limitations, and VM families with ephemeral disks) are referenced throughout. However, all code examples (Python and C#) use Linux images (Ubuntu) and Linux paths, with no concrete Windows container code samples provided. Windows-specific troubleshooting, configuration, or PowerShell examples are absent, but Windows terminology and considerations are present, sometimes without Linux equivalents.
Recommendations
  • Add concrete Windows container code examples (Python, C#, and/or PowerShell) showing how to configure and run Windows-based container pools and tasks, including Windows-specific image references and paths.
  • Provide Linux examples before Windows in lists and section headings to avoid 'windows_first' ordering bias.
  • Include troubleshooting and configuration steps for both Windows and Linux containers, ensuring parity in detail and coverage.
  • Explicitly mention Linux equivalents when discussing Windows-specific terms (e.g., ephemeral disk mapping, default Docker data root).
  • If referencing Windows tools or patterns (such as PowerShell), provide Linux CLI equivalents (e.g., bash scripts) alongside.
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-08 00:53
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 and patterns (PowerShell, RDP) are mentioned before or more prominently than Linux equivalents (Azure CLI, SSH). Example commands and instructions often reference Windows first, and some steps (such as connecting to nodes) give Windows instructions before Linux, or only mention Windows tools (RDP) explicitly. There is a lack of parity in some examples, such as not providing explicit Linux shell commands or focusing on Windows-centric workflows.
Recommendations
  • Ensure all command-line examples (PowerShell, CLI) are presented with Linux parity, e.g., provide Bash shell equivalents where appropriate.
  • When listing supported images or connection methods, mention Linux (SSH) and Windows (RDP) equally and in parallel, rather than Windows first.
  • Provide explicit Linux examples for VM preparation, such as mounting and formatting disks using Linux commands.
  • Include screenshots or instructions for both RDP (Windows) and SSH (Linux) when demonstrating portal workflows.
  • Review all references to tools and ensure Azure CLI (cross-platform) is given equal or greater prominence than PowerShell.
  • Where possible, use neutral language (e.g., 'connect via SSH or RDP') and avoid Windows-centric terminology as the default.
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-management-dotnet.md ...cs/blob/main/articles/batch/batch-management-dotnet.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates bias toward Windows environments by exclusively providing .NET (C#) code samples, referencing Windows-centric tools and workflows, and omitting any Linux-specific or cross-platform guidance. There are no examples for Linux command-line usage, Bash, or alternative SDKs (such as Python or CLI), and the sample project is C#-only. The documentation assumes the reader is using Windows or a Windows-like development environment, with no mention of Linux development patterns or tools.
Recommendations
  • Add equivalent code samples using Bash, Azure CLI, or PowerShell Core (cross-platform) to illustrate how Batch account management can be automated from Linux environments.
  • Include references to Python SDK usage for Batch Management, as Python is widely used on Linux.
  • Explicitly mention that the .NET library and Azure SDKs are cross-platform, and provide instructions for installing and running them on Linux.
  • Provide links to Linux-specific setup guides for Azure development, including authentication and environment configuration.
  • Ensure that sample projects and code snippets are available in multiple languages (e.g., Python, Bash, CLI) and not just C#.
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-08 00:53
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 examples and tooling. There are no mentions of Linux development environments, nor are there instructions or examples for using the Batch File Conventions standard from Linux or non-.NET languages, despite a brief note that other languages can implement the standard themselves.
Recommendations
  • Add code samples in other languages commonly used on Linux (e.g., Python, Java) that demonstrate persisting output data to Azure Storage using the Batch File Conventions standard.
  • Include instructions for setting up and running the sample project on Linux, such as using VS Code, JetBrains Rider, or command-line .NET tools (dotnet CLI), instead of only referencing Visual Studio.
  • Provide guidance or links for Linux users on installing the .NET SDK and running .NET code on Linux.
  • Mention cross-platform alternatives for uploading application packages (e.g., Azure CLI, azcopy) instead of only referencing the Azure portal.
  • Clarify that the File Conventions standard is language-agnostic and provide a reference implementation or sample 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-08 00:53
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 forms of Windows bias. Windows-specific tools (e.g., PowerShell) are mentioned before or more prominently than Linux equivalents, especially for discovering image and VM SKU EOL dates and preparing data disks. Examples for Windows (such as PowerShell commands) are given in detail, while Linux examples are fewer and less detailed. In some cases, Windows patterns (directory junctions, Windows Services, autouser accounts) are discussed at length, while Linux alternatives are only briefly mentioned or omitted. This prioritization may make it harder for Linux users to find relevant guidance.
Recommendations
  • Provide Linux CLI or shell script examples alongside PowerShell examples wherever Windows commands are shown.
  • Mention Linux tools (e.g., bash, systemd, lsblk, fdisk) before or alongside Windows tools, not after.
  • Ensure Linux-specific patterns (e.g., symlinks, systemd services, disk mounting) are described with equal detail and clarity as Windows equivalents.
  • Where Windows-specific features (like directory junctions or autouser accounts) are discussed, add parallel Linux guidance (e.g., symlinks, user management).
  • For API and CLI references, show both az CLI and bash usage, not just PowerShell.
  • Add more Linux-focused troubleshooting and operational tips, especially for common scenarios like disk management, service setup, and log collection.
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-08 00:53
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. There are no examples or explicit mentions of Linux VM images, node agent SKUs, or Linux-specific update scenarios. This may lead Linux users to feel unsupported or unclear about how to perform similar operations for Linux-based pools.
Recommendations
  • Add parallel examples for updating Linux-based pools, including Linux VM image references (e.g., Ubuntu, CentOS) and the appropriate node agent SKU (e.g., batch.node.ubuntu 20.04).
  • Explicitly mention that the update process applies to both Windows and Linux pools, and clarify any differences if they exist.
  • Where possible, provide code snippets or REST payloads for both Windows and Linux scenarios side by side.
  • Include references to Linux tools or command-line patterns (such as Bash or CLI commands) where relevant.
  • Review language throughout the documentation to ensure that Linux is not implicitly deprioritized or omitted.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page exhibits Windows bias by referencing PowerShell as the primary method for programmatically checking VM series support for ephemeral OS disks, without mentioning Linux alternatives (e.g., Azure CLI, Bash). The only tool explicitly mentioned for querying capabilities is PowerShell, and no Linux shell or cross-platform command-line examples are provided. This prioritizes Windows tools and patterns over Linux equivalents.
Recommendations
  • Add Azure CLI and Bash examples for querying VM series capabilities, alongside the PowerShell example.
  • Explicitly mention cross-platform tools and provide guidance for both Windows and Linux users.
  • Ensure that any code or command-line examples are presented in a platform-neutral order, or provide both Windows and Linux examples side by side.
  • Reference Linux documentation or tools where appropriate, such as az CLI, and avoid assuming PowerShell as the default scripting environment.
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-08 00:53
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 prioritizing Windows tools and patterns throughout. The prerequisites list only Visual Studio (Windows-centric), and the NuGet install example uses PowerShell syntax. The Application Insights package referenced is 'Microsoft.ApplicationInsights.WindowsServer', and the example pool configuration uses a Windows Server VM image exclusively. There are no Linux equivalents or examples provided, and Linux-compatible Application Insights packages or deployment patterns are not discussed.
Recommendations
  • Add Linux-specific prerequisites, such as instructions for using VS Code or .NET CLI on Linux.
  • Provide NuGet installation examples using the .NET CLI (e.g., 'dotnet add package') alongside PowerShell.
  • Mention and demonstrate the use of 'Microsoft.ApplicationInsights' or other cross-platform packages, not just 'WindowsServer'.
  • Include examples of configuring Azure Batch pools with Linux VM images, and show how to instrument .NET applications running on Linux nodes.
  • Discuss any differences in telemetry collection or configuration between Windows and Linux compute nodes.
  • Ensure screenshots and portal instructions are not Windows-specific, or clarify cross-platform applicability.
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-08 00:53
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 a specific example for custom file movement using Windows executables ('doMyWork.exe && uploadMyFilesToSql.exe'), without mentioning Linux equivalents. There are no Linux or cross-platform shell script examples, and the only sample project referenced is for C#/.NET, which is most commonly used on Windows. The documentation also references Windows nodes explicitly, while omitting Linux node scenarios.
Recommendations
  • Add equivalent Linux examples for custom file movement, such as using bash scripts (e.g., './doMyWork.sh && ./uploadMyFilesToSql.sh').
  • Explicitly mention both Windows and Linux nodes when discussing task execution and file movement.
  • Provide sample projects or code snippets for other languages/platforms commonly used on Linux, such as Python or bash.
  • Reference cross-platform tools (e.g., azcopy, curl, or Azure CLI) for uploading files, in addition to Windows-specific executables.
  • Ensure that documentation does not assume Windows as the default environment, and clarify instructions for both operating systems.
GitHub Create Pull Request
← Previous Page 7 of 18 Next →