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 276-300 of 436 flagged pages
Batch Monitor Azure Batch ...s/azure-docs/blob/main/articles/batch/monitor-batch.md
Medium Priority View Details →
Scanned: 2026-01-14 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 a detailed walkthrough for integrating Application Insights specifically with a Batch .NET solution. There are no explicit Linux or cross-platform code examples, nor are alternative SDKs (Python, Java, etc.) or Linux command-line tools mentioned. The documentation assumes familiarity with Windows development patterns and tools, which may create friction for Linux/macOS users.
Recommendations
  • Include examples using cross-platform SDKs (e.g., Python, Java) for monitoring Batch resources.
  • Mention and provide guidance for using Azure CLI and REST APIs from Linux/macOS environments.
  • Highlight any Linux-compatible tools for monitoring (e.g., az CLI, PowerShell Core, or third-party tools).
  • Add sample code and walkthroughs for integrating Application Insights with non-.NET Batch applications.
  • Clarify that Batch Explorer is cross-platform (if true), or suggest alternatives for Linux/macOS users.
GitHub Create Pull Request
Batch Migrate low-priority VMs to spot VMs in Batch ...s/batch/low-priority-vms-retirement-migration-guide.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for automating the migration of low-priority VMs to Spot VMs in Azure Batch. However, the PowerShell examples are presented as the only alternative automation method after the CLI, with no mention of Bash, shell scripting, or Linux/macOS-specific automation approaches. The PowerShell section assumes the user is familiar with Windows tooling, and there are no explicit Linux/macOS command-line or scripting examples beyond the Azure CLI. Additionally, the PowerShell section is more detailed than the CLI section, and the ordering (CLI then PowerShell) is common but still may suggest a slight Windows-first bias.
Recommendations
  • Add explicit Bash/shell scripting examples for Linux/macOS users, especially for automation tasks.
  • Clarify that Azure CLI commands work cross-platform (Windows, Linux, macOS) and provide sample Bash scripts for common migration scenarios.
  • If PowerShell is included, consider also mentioning PowerShell Core (pwsh), which is cross-platform, and provide guidance for Linux/macOS users.
  • Ensure that all automation examples (CLI, PowerShell, ARM, Terraform) are equally detailed and that none assume a Windows-only environment.
  • Consider adding a short section or note for Linux/macOS users, highlighting any differences or confirming parity.
GitHub Create Pull Request
Batch Monitor Batch with Azure Application Insights ...ob/main/articles/batch/monitor-application-insights.md
Medium Priority View Details →
Scanned: 2026-01-14 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 exhibits a notable Windows bias. Windows tools (Visual Studio, WindowsServer VM images, cmd.exe) are referenced exclusively, and all code/package examples (e.g., PowerShell Install-Package, .NET WindowsServer NuGet package) are Windows-centric. There are no Linux/macOS equivalents or guidance for cross-platform scenarios, and the only VM image shown is for Windows. This creates friction for Linux/macOS users attempting to follow the guide.
Recommendations
  • Add Linux/macOS equivalents for prerequisites (e.g., mention VS Code, .NET CLI, Mono, or JetBrains Rider).
  • Provide instructions for installing Application Insights packages using dotnet CLI (e.g., 'dotnet add package') and/or NuGet CLI, not just PowerShell.
  • Include examples of configuring and running Application Insights on Linux-based Batch pools (e.g., Ubuntu VM images, bash command lines).
  • Clarify whether the Application Insights instrumentation and telemetry initializer code works on Linux compute nodes, and provide any necessary adjustments.
  • Show how to stage and execute tasks on Linux nodes, including sample bash scripts or Linux command lines.
  • Explicitly state platform compatibility and link to cross-platform documentation where relevant.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation primarily guides users to deploy the ARM template via 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-specific page, and there are no explicit Linux/macOS CLI examples or instructions. Windows-centric tools (PowerShell, portal) are referenced before cross-platform alternatives, and Linux/macOS users may need to search elsewhere for CLI-based deployment steps.
Recommendations
  • Add explicit Azure CLI deployment instructions and examples, as Azure CLI is cross-platform and widely used on Linux/macOS.
  • Provide links to both PowerShell and Azure CLI documentation for deploying ARM templates, not just PowerShell.
  • Include a section or code block showing how to deploy the template using Azure CLI (e.g., az deployment group create ...).
  • Clarify that Azure CLI and REST API are fully supported on Linux/macOS and provide parity with Windows tools.
  • Consider ordering deployment options so that cross-platform methods (CLI, REST API) are listed before or alongside Windows-specific tools.
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-14 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 exhibits a notable Windows bias. It exclusively demonstrates creating Batch pools with Windows Server images, uses Windows command-line tools (cmd /c type), and provides examples and code snippets that assume Windows environments. There are no Linux pool creation examples, nor any Linux command-line equivalents or cross-platform task instructions. Visual Studio is mentioned as the primary IDE, with only brief mention of .NET CLI for Linux. This bias may hinder Linux/macOS users from following the quickstart or adapting it to their platforms.
Recommendations
  • Add examples for creating Batch pools with Linux VM images, including the necessary configuration changes in code.
  • Provide Linux/macOS command-line equivalents for task execution (e.g., use 'cat' instead of 'type').
  • Show how to modify the app to run on Linux nodes, including changes to the command line and image reference.
  • Present cross-platform instructions and highlight any platform-specific steps or requirements.
  • Include screenshots or instructions for using .NET CLI and editors available on Linux/macOS, such as VS Code.
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-14 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 a notable Windows bias: it exclusively references Windows tools and patterns, such as using Windows Server VM images, Windows-specific ffmpeg builds, and Windows command-line syntax (cmd.exe). There are no examples or guidance for Linux-based pools, nor any mention of Linux-compatible ffmpeg packages or shell syntax. This may create friction for Linux/macOS users, who must adapt the instructions and code to work with non-Windows environments.
Recommendations
  • Add explicit instructions and code samples for creating Linux-based pools (e.g., Ubuntu VM images) in Azure Batch.
  • Include guidance on obtaining and packaging ffmpeg for Linux, with links to official Linux builds.
  • Provide example task command lines using Linux shell syntax (e.g., bash), and show how to invoke ffmpeg on Linux nodes.
  • Clarify which steps are OS-agnostic and which require adaptation, with notes or callouts for Linux/macOS users.
  • Show how to build and run the sample app on Linux/macOS, including any necessary changes to file paths or environment variables.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides both Windows and Linux instructions, but consistently presents Windows examples and tooling (PowerShell, cmdkey, net use) before Linux equivalents. PowerShell is used as the primary automation interface for both platforms, which is less common for Linux users. Troubleshooting and manual mounting sections also prioritize Windows tools and workflows, with Linux instructions following. References to Windows-specific tools (cmdkey, net use) are more detailed than Linux equivalents (mount, cifs-utils).
Recommendations
  • Provide Bash or native Linux CLI examples alongside or before PowerShell for Linux sections.
  • Where PowerShell is used for Linux, clarify that Bash or other native tools can be used and provide those examples.
  • Balance troubleshooting steps by giving equal detail for Linux (e.g., show mount command outputs, common Linux errors, and troubleshooting commands like dmesg or journalctl).
  • In manual mounting instructions, present Linux (Bash) and Windows (PowerShell) scripts in parallel, not sequentially.
  • Reference Linux documentation and tools (e.g., mount.cifs, mount.nfs, BlobFuse CLI) as prominently as Windows tools.
GitHub Create Pull Request
Batch Migrate Batch account certificates to Azure Key Vault ...in/articles/batch/batch-certificate-migration-guide.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation generally addresses both Windows and Linux Batch pools, but in the FAQs, the link to Windows documentation is listed before Linux. There are no explicit code examples or step-by-step instructions for either platform, but Linux-specific guidance is less detailed and lacks concrete examples, especially for certificate access and installation. The page does not provide parity in examples or troubleshooting steps for Linux users.
Recommendations
  • Provide explicit, step-by-step examples for both Windows and Linux, including code snippets (e.g., Powershell for Windows, Bash for Linux) for certificate migration and access.
  • List Linux and Windows documentation links in parallel or alternate their order to avoid implicit prioritization.
  • Include troubleshooting tips and common patterns for Linux users, such as handling permissions and certificate file locations.
  • Add a dedicated section for Linux-specific migration steps, especially regarding the removal of $AZ_BATCH_CERTIFICATES_DIR and alternatives.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively demonstrates creating pools of Windows compute nodes and provides only Windows command-line examples (using 'cmd' and 'timeout'). There is no mention of Linux pools, Linux VM images, or Linux shell commands, which may mislead users into thinking Azure Batch is Windows-centric or make it difficult for Linux/macOS users to follow the quickstart.
Recommendations
  • Add parallel instructions and screenshots for creating Linux-based pools (e.g., Ubuntu or CentOS images).
  • Provide Linux shell command examples (e.g., using 'echo' and 'sleep') for task command lines.
  • Explicitly mention that both Windows and Linux pools are supported, and link to documentation on choosing OS images.
  • Consider alternating or equally presenting Windows and Linux options throughout the quickstart.
GitHub Create Pull Request
Batch Create a Batch account in the Azure portal ...lob/main/articles/batch/batch-account-create-portal.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias, primarily in the 'Accept legal terms' section, where only PowerShell commands (Get-AzMarketplaceTerms, Set-AzMarketplaceTerms) are provided for accepting marketplace image terms. No equivalent Azure CLI or Bash examples are given, which can hinder Linux/macOS users. Additionally, the 'Other Batch account management options' lists PowerShell cmdlets before Azure CLI, and the overall documentation references Windows-centric tools and patterns more prominently.
Recommendations
  • Provide Azure CLI equivalents for all PowerShell commands, especially for accepting marketplace terms (e.g., az vm image terms accept).
  • Include Bash/Linux shell examples alongside PowerShell, or clarify cross-platform alternatives.
  • List Azure CLI and cross-platform tools before or alongside Windows-specific tools in the 'Other management options' section.
  • Add a note clarifying that all portal-based instructions are OS-agnostic, but command-line steps should be cross-platform.
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-13 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. In code examples, Windows and .NET (C#) are consistently presented first and in greater detail, including VM image references for Microsoft Windows Server. Windows-specific tools and patterns (e.g., PowerShell cmdlets, .NET SDK) are mentioned before their Linux equivalents, and Linux-specific examples (such as Python SDK usage with Ubuntu images) are present but less prominent and detailed. There are no explicit Linux shell or CLI examples, and PowerShell is referenced as a primary tool for interacting with Azure Batch, with no parity for Bash or other Linux-native tools.
Recommendations
  • Present Linux and macOS examples (e.g., Bash, Azure CLI) alongside or before Windows/PowerShell examples.
  • Expand Python and Linux VM examples to match the detail and coverage given to .NET/Windows.
  • Include explicit instructions and code snippets for creating and managing pools using Linux tools (e.g., Azure CLI, Bash scripts).
  • Reference Linux/macOS documentation and quickstart repositories as prominently as Windows/.NET resources.
  • Ensure VM image references in examples alternate between Windows and Linux distributions, or provide both in parallel.
GitHub Create Pull Request
Batch Use Microsoft Entra ID to authenticate Batch Management solutions .../blob/main/articles/batch/batch-aad-auth-management.md
Medium Priority View Details →
Scanned: 2026-01-13 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 examples and walkthroughs use the .NET library and reference the AccountManagement sample, which is a C#/.NET (Windows-centric) project. The Azure portal instructions and terminology (e.g., 'Windows Azure Service Management API') are Windows-oriented. There are no Linux/macOS-specific instructions, nor are alternative SDKs, tools, or authentication flows for non-Windows platforms mentioned. No parity is provided for Linux users wishing to use Python, Java, or REST APIs, nor are cross-platform CLI examples (e.g., Azure CLI) shown.
Recommendations
  • Add equivalent examples using cross-platform SDKs (e.g., Python, Java) and REST API calls.
  • Provide instructions for authenticating using Azure CLI, which is available on Linux/macOS.
  • Reference and link to Linux/macOS-compatible sample projects.
  • Clarify that the .NET library can be used on Linux/macOS via .NET Core/6+, if applicable, and provide setup instructions.
  • Avoid using 'Windows Azure' terminology exclusively; use 'Azure Resource Manager' or 'Azure Service Management API' where possible.
  • Explicitly state platform compatibility and provide guidance for non-Windows environments.
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-13 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 examples are in C# using the Batch .NET library, and the only VM configuration example uses a Windows image. Task command lines use Windows-specific syntax (cmd /c), and there are no Linux shell examples. The explanation of environment variables for Linux is present, but no practical Linux code samples or shell commands are provided. Windows node requirements and patterns are described first, and Linux equivalents are mentioned only as notes or afterthoughts.
Recommendations
  • Add equivalent Linux-focused code samples, such as using bash shell commands in task command lines.
  • Provide examples of creating pools with Linux VM images and node agent SKUs.
  • Include Linux-specific instructions for referencing application packages and environment variables in shell scripts.
  • Ensure that examples and explanations alternate or balance Windows and Linux scenarios, rather than presenting Windows first.
  • Mention cross-platform SDKs or REST API usage with examples for both Windows and Linux.
  • Clarify any differences in application ID requirements or environment variable formats with side-by-side examples.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a mild Windows bias by referencing Windows-specific installation formats (e.g., .exe and .msi files) as primary examples, without mentioning Linux equivalents (such as .sh scripts or .deb/.rpm packages). There are no explicit Linux/macOS examples or references to common Linux installation patterns, and the examples focus on Windows-centric tools and file types. This may create friction for Linux users seeking guidance on deploying applications or data to Batch nodes running Linux.
Recommendations
  • Add examples using Linux/macOS installation formats (e.g., shell scripts, .deb/.rpm packages) alongside Windows examples.
  • Explicitly mention that start tasks and job preparation tasks can run Linux commands and scripts, and provide sample command lines for both platforms.
  • Clarify that application packages and resource files are platform-agnostic and provide guidance for Linux-specific scenarios.
  • Include a note or section on cross-platform considerations, highlighting differences in application deployment between Windows and Linux nodes.
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-13 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 example solution exclusively deploys Windows software (Windows FFmpeg) on Windows-based Batch nodes, with ARM templates specifying Windows images only. The repository setup and build pipeline instructions focus solely on Windows binaries. The agent pool for pipelines is set to 'windows-latest' without mention of Linux alternatives. There are no examples or instructions for deploying Linux software, using Linux-based Batch pools, or handling Linux application packages, despite a brief note that Linux is supported.
Recommendations
  • Add parallel examples for deploying Linux software (e.g., Linux FFmpeg) on Linux-based Batch nodes.
  • Provide ARM template snippets for Linux pool configuration (e.g., Ubuntu or CentOS images).
  • Show repository structure and build pipeline steps for Linux binaries.
  • Mention and demonstrate how to select 'ubuntu-latest' or other Linux agents in Azure Pipelines.
  • Ensure all CLI and scripting instructions are OS-agnostic or provide both PowerShell and Bash examples.
  • Move the note about Linux support to a more prominent location and expand it with actionable guidance.
GitHub Create Pull Request
Batch Use the Batch Management .NET library to manage account resources ...cs/blob/main/articles/batch/batch-management-dotnet.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively provides C#/.NET code samples and references Windows-centric authentication and tooling patterns (e.g., DefaultAzureCredential, MSAL, Azure Resource Manager), without mentioning or demonstrating how to perform equivalent tasks on Linux or macOS. There are no examples or guidance for Linux-specific development environments, nor any mention of cross-platform considerations for .NET Core/.NET 6+ or alternative authentication flows on non-Windows systems.
Recommendations
  • Explicitly state that the .NET library and code samples are cross-platform and supported on Linux/macOS, not just Windows.
  • Add instructions for installing .NET SDK and running the samples on Linux/macOS, including any required environment variables or authentication setup.
  • Provide at least one example of running the code on Linux (e.g., Ubuntu), including terminal commands for setup and execution.
  • Mention any platform-specific caveats (e.g., certificate stores, MSAL browser authentication differences) for Linux/macOS users.
  • Reference or link to equivalent documentation for other languages (e.g., Python) with Linux/macOS examples, where appropriate.
GitHub Create Pull Request
Batch Azure Batch pool create event ...cs/blob/main/articles/batch/batch-pool-create-event.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-specific information and examples. Windows VM sizes and OS families are described in detail, with explicit references to Windows Server versions. The deprecated Cloud Services Configuration section is entirely Windows-focused, and the only OS-specific configuration example provided is for Windows (windowsConfiguration), with no equivalent Linux configuration or examples. References to Linux VM sizes are present but less prominent, and there are no Linux-specific configuration details or examples.
Recommendations
  • Add explicit Linux configuration examples, such as a linuxConfiguration section under virtualMachineConfiguration.
  • Provide parity in documentation for Linux OS images, including supported distributions, configuration options, and example values.
  • Ensure that references to VM sizes and OS images are presented in a balanced manner, with Linux and Windows information given equal prominence.
  • Include notes or links to Linux-specific documentation where appropriate, such as for node agent SKUs or image references.
  • If there are Linux-specific features or limitations, document them alongside Windows equivalents.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively provides Windows-centric examples, using 'cmd.exe /c echo ...' in all code snippets and referencing Windows command-line patterns. There are no Linux or macOS shell equivalents (e.g., '/bin/bash -c ...'), nor any mention of cross-platform scripting. The documentation implicitly assumes a Windows environment for task execution, which may confuse or hinder Linux/macOS users.
Recommendations
  • Provide parallel examples using Linux shell commands (e.g., '/bin/bash -c echo ...') alongside Windows examples.
  • Explicitly state that Azure Batch supports both Windows and Linux compute nodes, and clarify any differences in task command syntax.
  • Add notes or sections addressing cross-platform considerations, such as environment variables, file paths, and shell differences.
  • Ensure sample code and GitHub references include Linux-compatible scripts and instructions.
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-13 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 Windows and Linux information, but there are signs of Windows bias. Windows-specific details and caveats are often mentioned first or in more detail (e.g., ephemeral disk mapping, container runtime notes, default Docker data root paths). C# examples use Windows-style paths and commands, and the troubleshooting and container task sections show Windows-centric examples before or instead of Linux equivalents. There is a lack of parity in showing Linux-specific command-line examples (e.g., no bash or shell script examples for Linux containers in C#), and Windows tools/patterns (like C:\ paths and references to Windows container limitations) are more prominent.
Recommendations
  • Provide Linux-first or side-by-side examples for all code snippets, especially in C# and Python, including Linux-style paths and shell commands.
  • Balance the order of platform-specific notes so that Linux and Windows are treated equally, or group platform-specific guidance in dedicated sections.
  • Include troubleshooting steps and container task examples that use Linux containers and Linux command lines (e.g., bash scripts, /app paths) in C# and Python.
  • Explicitly mention Linux alternatives for any Windows-specific tools or patterns.
  • Add a table or matrix summarizing feature parity and limitations for both platforms.
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-13 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 Windows and Linux guidance for configuring compute-intensive Azure Batch pools, but there is a noticeable Windows bias. Windows examples (e.g., installing GPU drivers, configuring MPI) are presented first and in greater detail, including explicit PowerShell and RDP instructions. Linux examples are present but less detailed, and some advanced configuration steps (like custom image creation for MPI workloads) are only shown for Windows. Windows-specific tools and patterns (PowerShell, RDP, MSI installers) are mentioned without Linux equivalents or parity in example depth.
Recommendations
  • Provide Linux examples with equal detail and step-by-step instructions, especially for tasks like installing MPI and configuring RDMA drivers.
  • Include Linux-specific command-line instructions (e.g., Bash, SSH) where Windows uses PowerShell or RDP.
  • Ensure that advanced configuration scenarios (custom images, driver installation, application packaging) are covered for Linux as thoroughly as for Windows.
  • Present examples in parallel or alternate between Windows and Linux, rather than consistently listing Windows first.
  • Reference up-to-date Linux documentation and tools, and avoid referencing EOL Linux versions.
GitHub Create Pull Request
Batch Update pool properties ...ob/main/articles/batch/batch-pool-update-properties.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias primarily by providing only Windows-centric examples (e.g., C# SDK using a Windows VM image), referencing Windows VM images and node agent SKUs, and omitting Linux-specific examples or guidance. The first and only code sample uses Windows VM configuration, and there is no mention of Linux VM images, node agent SKUs for Linux, or Linux/macOS command-line tools. This may create friction for users managing Linux-based Batch pools.
Recommendations
  • Add parallel examples for updating pool properties using Linux VM images and node agent SKUs.
  • Include code samples using Linux/macOS tools (e.g., Azure CLI, Bash scripts) alongside C# SDK examples.
  • Explicitly mention Linux pool configuration options and provide REST API payloads for Linux VM images.
  • Ensure documentation references both Windows and Linux options equally, and avoid defaulting to Windows in examples.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific tools (cmdkey, net use) and examples are provided in detail for mounting Azure Files, while Linux equivalents (e.g., mounting SMB shares with mount.cifs) are absent. The azcopy examples use Windows-style syntax and switches, and Windows mounting instructions appear before Linux mounting instructions for file shares. Linux-specific solutions like blobfuse are mentioned, but lack step-by-step examples comparable to the Windows section. Overall, Linux users may need to seek additional resources to achieve parity.
Recommendations
  • Add explicit Linux mounting instructions for Azure Files (e.g., using mount.cifs or SMB on Linux).
  • Provide azcopy examples with Linux syntax and switches, and clarify any OS-specific differences.
  • Include Linux/macOS command-line examples for file operations alongside Windows examples.
  • Ensure parity in detail and step-by-step guidance for both Windows and Linux workflows.
  • Mention cross-platform tools and patterns first, or present them in parallel sections.
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-13 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 mentioned before Linux equivalents (CLI, SSH), and some examples or instructions (such as connecting to nodes) prioritize Windows workflows. PowerShell is listed before Azure CLI for image discovery, and RDP is described before SSH in portal instructions. There is a lack of explicit Linux shell examples (e.g., Bash) for key steps, and some references (like disk mounting/formatting) do not provide Linux-specific guidance.
Recommendations
  • Provide Linux shell (Bash) examples alongside PowerShell for listing supported images and other operations.
  • Ensure that Linux tools (e.g., SSH) are mentioned at least as prominently as Windows tools (e.g., RDP) in all relevant sections.
  • Add explicit Linux instructions for mounting and formatting data disks, including example commands.
  • Where Windows and Linux workflows diverge, offer parallel step-by-step instructions for both OS types.
  • In portal instructions, clarify Linux login steps (e.g., SSH key setup, username) with equal detail as Windows RDP.
  • Review and balance the order of presenting Windows and Linux examples/tools throughout the page.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a Windows bias by exclusively providing .NET (C#) code samples, referencing Windows-specific tools (Visual Studio 2019), and omitting any Linux/macOS-specific instructions, examples, or alternative tooling. There are no PowerShell examples, but the overall workflow assumes a Windows development environment and does not mention how to accomplish the same tasks on Linux or macOS (e.g., using .NET Core/SDK on Linux, VS Code, or command-line tooling).
Recommendations
  • Add explicit instructions and code samples for using the Batch File Conventions library with .NET Core/SDK on Linux and macOS, including command-line usage.
  • Include alternative tooling recommendations (e.g., VS Code, JetBrains Rider) and instructions for building and running the sample project on Linux/macOS.
  • Provide guidance for installing dependencies and running the PersistOutputs sample without Visual Studio, such as using 'dotnet build' and 'dotnet run'.
  • Clarify that the File Conventions library is cross-platform and provide links or sections for Linux/macOS users.
  • Add troubleshooting notes for common Linux/macOS issues (e.g., environment variables, file paths).
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-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias. All code samples use C# and Windows command syntax (cmd.exe), with no Linux shell equivalents provided. The main example uses Windows-specific command lines, and only a brief note mentions changing backslashes to forward slashes for Linux. The sample project is a Visual Studio solution, with instructions tailored for Windows development tools. There are no Linux or macOS-specific instructions, nor are there examples using Bash or other cross-platform shells.
Recommendations
  • Provide equivalent Linux/Bash command examples for task execution (e.g., using bash to write random numbers to output.txt).
  • Include instructions for running the sample project on Linux/macOS (e.g., using .NET Core CLI, VS Code, or other cross-platform tools).
  • Show file path examples using both Windows and Linux conventions, or use platform-agnostic path construction.
  • Mention and demonstrate how to use the Batch service API from other languages/platforms (e.g., Python, Java) with Linux/macOS.
  • Add troubleshooting and diagnostic steps relevant to Linux/macOS environments.
GitHub Create Pull Request
← Previous Page 12 of 18 Next →