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 176-200 of 436 flagged pages
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/network-security-perimeter.md ...blob/main/articles/batch/network-security-perimeter.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 First 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias by presenting PowerShell instructions before Azure CLI, and by providing detailed PowerShell examples alongside Azure CLI, but not including any Linux shell or Bash-specific guidance. The use of PowerShell as a primary scripting example and the ordering of PowerShell before CLI may suggest a preference for Windows environments. There are no explicit Linux/Bash examples or notes about cross-platform usage for non-Windows users.
Recommendations
  • Add explicit Bash/Linux shell examples where appropriate, especially for scripting scenarios.
  • Clarify that Azure CLI commands are cross-platform and can be run on Windows, Linux, and macOS.
  • Consider reordering the example sections to present Azure CLI before PowerShell, as CLI is more platform-agnostic.
  • Include notes or links for Linux/macOS users on how to install and use Azure CLI and/or PowerShell Core.
  • Where PowerShell is referenced, specify if the commands are compatible with PowerShell Core (cross-platform) or only Windows PowerShell.
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-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 exclusively provides code examples using Windows-specific tools (cmd.exe) and patterns, with no mention of Linux equivalents (such as bash). All task command lines use 'cmd.exe /c echo ...', and there is no guidance or example for Linux-based pools or shell commands. The documentation implicitly assumes a Windows environment, omitting Linux scenarios and tools.
Recommendations
  • Include equivalent Linux examples using bash (e.g., 'bash -c "echo ..."') alongside Windows examples.
  • Explicitly mention how to configure and run tasks on Linux pools, including any differences in command syntax or environment.
  • Clarify that Azure Batch supports both Windows and Linux compute nodes, and provide guidance for cross-platform compatibility.
  • Add notes or tables comparing Windows and Linux task command patterns, especially for common operations like echoing output.
  • Ensure that sample code and GitHub references include Linux-compatible scripts and instructions.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation page exhibits Windows bias by listing Azure PowerShell as a primary method for creating public IP addresses, alongside Azure CLI and the portal. PowerShell is a Windows-centric tool, and its mention before any Linux-specific alternatives (e.g., Bash scripts or Linux-native tools) reinforces a Windows-first approach. There are no Linux shell or Bash examples, and no mention of Linux-specific workflows for resource creation. The REST API example uses Ubuntu as the VM image, but this does not offset the bias in the tooling recommendations.
Recommendations
  • Add explicit Bash or shell script examples for creating public IP addresses using Azure CLI, tailored for Linux users.
  • Reorder the list of resource creation methods to mention Azure CLI before PowerShell, as CLI is cross-platform.
  • Include a note clarifying that Azure CLI works natively on Linux, macOS, and Windows, while PowerShell is primarily Windows-focused.
  • Provide links to Linux-specific documentation or tutorials for Azure resource management.
  • Avoid listing Windows tools (PowerShell) before cross-platform alternatives unless contextually necessary.
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-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. All code samples are in C# and use Windows-centric command syntax (e.g., 'cmd /v:ON /c'), with only a brief note for Linux users to change backslashes to forward slashes. The main sample project is a Visual Studio solution, and instructions reference Windows tools (Visual Studio, .exe files) exclusively. There are no Linux shell or cross-platform code examples, and Linux-specific considerations are not discussed beyond path delimiters.
Recommendations
  • Provide equivalent Linux shell (bash) command examples for task execution, not just Windows 'cmd' commands.
  • Include code samples in other languages commonly used on Linux, such as Python or bash scripts.
  • Offer instructions for running sample projects on Linux (e.g., using VS Code, .NET Core CLI, or other cross-platform tools), not just Visual Studio.
  • Discuss Linux-specific file system patterns and considerations, such as permissions and symbolic links.
  • Explicitly mention how to run and debug tasks on Linux pools, including troubleshooting steps relevant to Linux environments.
  • Add references to Linux tools and workflows (e.g., using zip/tar for file containers, mounting storage via FUSE, etc.).
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-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 Windows bias in several ways: Windows tools and concepts (such as RDP and DPAPI) are mentioned before or instead of Linux equivalents; code examples often use Windows-centric commands (e.g., 'cmd.exe /c echo') and only provide Windows-specific context before Linux; references to Windows features (DPAPI, RDP) are more detailed than their Linux counterparts; and some code snippets lack Linux-specific usage or examples (e.g., running tasks under named user accounts with Linux shell commands).
Recommendations
  • Provide Linux-first or parallel examples for all code snippets, especially where Windows commands (e.g., 'cmd.exe /c echo') are used. Include Linux shell equivalents (e.g., '/bin/bash -c "echo hello"').
  • Mention Linux tools and patterns (e.g., SSH, GPG, file permissions) alongside or before Windows tools like DPAPI and RDP.
  • Add explicit Linux usage scenarios, such as how to run tasks under named user accounts using Linux shell commands, and how to manage secrets or file shares on Linux nodes.
  • Ensure that references to remote access (RDP/SSH) are balanced, with equal detail and prominence for both Windows and Linux.
  • Where possible, use neutral terminology and avoid Windows-centric defaults in code and narrative (e.g., avoid assuming 'cmd.exe' as the default shell).
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-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 prioritizing Windows-centric tools and examples. The only client library explicitly mentioned is the Batch .NET library, with walkthroughs and code samples focused on .NET (a Windows-first technology). Application Insights integration is described solely in the context of a .NET solution, with no mention of Linux or cross-platform alternatives. There are no examples using Linux tools, Bash, or Python SDKs, nor any references to Linux-specific monitoring workflows. Batch Explorer is mentioned, but its cross-platform nature is not clarified, and no Linux command-line or scripting examples are provided.
Recommendations
  • Add examples using the Azure Batch Python SDK, including sample code for monitoring tasks and pools.
  • Include Bash or Azure CLI commands for accessing diagnostic logs and metrics, demonstrating Linux workflows.
  • Clarify whether Batch Explorer is cross-platform, and provide installation instructions for Linux and macOS.
  • Provide Application Insights integration examples for non-.NET languages (e.g., Python), and reference cross-platform instrumentation guides.
  • Mention Linux-compatible tools (such as jq for JSON parsing, or azcopy for blob access) alongside Windows tools.
  • Ensure that all code samples and walkthroughs have Linux equivalents, or explicitly state platform requirements.
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-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 exclusively using Windows Server for compute nodes, Windows command-line tools (cmd, type), and Windows-specific VM images. There are no examples or guidance for using Linux nodes, Linux command-line equivalents, or cross-platform task commands. The documentation assumes Windows as the default environment for both development and execution, despite mentioning .NET support for Linux.
Recommendations
  • Add examples for creating Batch pools with Linux VM images, including relevant ImageReference and nodeAgentSkuId values.
  • Provide Linux command-line equivalents for task execution (e.g., using bash and cat instead of cmd /c type).
  • Include instructions and code samples for running the quickstart app on Linux, highlighting any platform-specific considerations.
  • Mention cross-platform development environments (e.g., VS Code, JetBrains Rider) alongside Visual Studio.
  • Clarify that Azure Batch supports both Windows and Linux nodes, and link to documentation for Linux configuration.
  • Show how to select between Windows and Linux pools in the code, and discuss implications for task scripts.
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/create-pool-extensions.md ...ocs/blob/main/articles/batch/create-pool-extensions.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides parity between Linux and Windows in the main extension lists and example payloads, but there are signs of Windows bias. Several extensions are Windows-only (e.g., Antimalware, Diagnostics, DSC, multiple HPC GPU drivers), and Windows tools/extensions are listed before Linux equivalents in several places. There is no mention of Linux troubleshooting tools or log locations, while Windows-centric patterns (like certificateStoreLocation: LocalMachine) are highlighted. No Linux shell or command-line examples are provided for troubleshooting, and the Application Health extension section does not discuss Linux-specific health monitoring approaches.
Recommendations
  • Ensure Linux and Windows extensions are listed in alternating or grouped order to avoid implicit prioritization.
  • Add Linux-specific troubleshooting steps, including log file locations and common shell commands for investigating extension issues.
  • Provide parity in extension support where possible, or clearly indicate when an extension is Windows-only and suggest Linux alternatives.
  • Include Linux shell (bash) examples for interacting with extensions, not just REST API payloads.
  • Discuss Linux-specific health monitoring approaches in the Application Health extension section.
  • Where Windows tools or patterns are mentioned (e.g., certificateStoreLocation: LocalMachine), provide Linux equivalents or explanations.
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/jobs-and-tasks.md .../azure-docs/blob/main/articles/batch/jobs-and-tasks.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 Powershell Heavy
Summary
The documentation demonstrates mild Windows bias by mentioning Windows tools (e.g., robocopy, MSI, setup.exe) as examples for start tasks, and by listing Windows shell invocation (cmd.exe) before Linux (/bin/sh) in command line examples. Windows-specific patterns and tools are referenced without equivalent Linux alternatives, and Windows environment variable syntax is mentioned before Linux syntax.
Recommendations
  • Provide Linux tool examples alongside Windows ones (e.g., use rsync or cp instead of only robocopy, mention .sh scripts or tar.gz installers alongside MSI/setup.exe).
  • Alternate the order of Windows and Linux examples in command line and environment variable syntax to avoid implicit prioritization.
  • Explicitly mention Linux equivalents for all Windows-specific tools and patterns, ensuring parity in guidance for both platforms.
  • Include sample commands for common Linux distributions and shell environments where relevant.
  • Add notes or sections highlighting cross-platform considerations and differences, especially for task setup and resource management.
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-08 00:53
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, specifying Windows Server 2019 as the operating system. Task examples use Windows-specific command line syntax ('cmd /c', 'set', 'timeout /t 90 > NUL'), and there is no mention of Linux pools, Linux VM SKUs, or equivalent Linux shell commands. The documentation does not provide Linux alternatives or parity in examples, leading to a clear Windows bias.
Recommendations
  • Include parallel instructions for creating a pool of Linux compute nodes, specifying a popular Linux VM SKU (e.g., Ubuntu).
  • Provide Linux shell command examples for tasks (e.g., use 'bash -c "env; sleep 90"' instead of Windows 'cmd /c ...').
  • Add notes or sections highlighting differences and options for both Windows and Linux pools.
  • Ensure screenshots and walkthroughs show both Windows and Linux configuration paths in the Azure portal.
  • Mention considerations for choosing between Windows and Linux nodes, and link to documentation for both.
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-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 moderate Windows bias. Windows-specific executable types (e.g., .exe, .cmd, .bat, PowerShell scripts) are listed before Linux equivalents, and Windows tools (RDP, Windows Server 2016 Datacenter with Containers) are mentioned explicitly, sometimes without equal detail for Linux alternatives. Container support examples focus on Windows images first, and Linux-specific instructions or examples (e.g., mounting disks, container images) are referenced but not detailed. There is a lack of parity in example scripts and tooling between Windows and Linux, with Windows patterns often presented before or instead of Linux ones.
Recommendations
  • Present Linux and Windows examples side-by-side for all relevant operations (e.g., start tasks, application package installation, disk mounting).
  • List Linux script types (e.g., shell scripts, Python scripts) before or alongside Windows types when describing supported executables.
  • Include explicit instructions and examples for Linux remote access (SSH) and container support, matching the detail given for Windows (e.g., Docker setup on Ubuntu images).
  • Mention Linux VM images and configuration options with equal prominence as Windows equivalents.
  • Ensure references to tooling (e.g., RDP, PowerShell) are balanced with Linux alternatives (e.g., SSH, Bash).
  • Add example scaling formulas and node deallocation options using Linux-based pools.
GitHub Create Pull Request
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-08 00:53
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, and Windows-specific tools and patterns (such as 'cmdkey', 'net use', and drive letters like 'S:') are referenced frequently and often before their Linux equivalents. Windows troubleshooting steps and tools are often described in more detail or appear first. While Linux support is present and parity is generally good, the documentation tends to assume familiarity with Windows conventions and tools.
Recommendations
  • Provide native Bash or shell script examples for Linux scenarios, rather than only PowerShell, to better match common Linux administrator workflows.
  • When presenting parallel instructions for Windows and Linux, alternate which OS is presented first, or present both side-by-side to avoid implicit prioritization.
  • Where Windows-specific tools (e.g., 'cmdkey', 'net use') are described, ensure equivalent Linux tools and commands (e.g., 'mount', 'cifs-utils', 'smbclient') are given equal detail and prominence.
  • Clarify Linux-specific mount points and filesystem conventions (e.g., /mnt/batch/tasks/fsmounts/S) and avoid using Windows drive letters in Linux contexts.
  • Expand troubleshooting sections to include more Linux-specific error messages and solutions, matching the depth provided for Windows.
  • Link to Linux-focused external resources and documentation with the same frequency as Windows resources.
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-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 mild Windows bias. Windows-specific tools and documentation (e.g., PowerShell, Windows TLS registry settings) are referenced before or more prominently than Linux equivalents. Examples for discovering supported images mention PowerShell first, and Windows-specific security configuration guidance is detailed, while Linux-specific instructions are absent. There is a lack of parity in examples and references for Linux users, especially regarding OS-level security settings and CLI tooling.
Recommendations
  • Provide Linux-specific examples and references alongside Windows ones, such as using Bash or Azure CLI for supported image queries.
  • Include guidance for configuring SSL/TLS and cipher suites on Linux distributions, referencing relevant documentation (e.g., OpenSSL, systemd, or distro-specific guides).
  • When mentioning PowerShell, also mention Azure CLI and Bash alternatives for common tasks.
  • Ensure that security configuration instructions (e.g., OS patching, TLS settings) are provided for both Windows and Linux, with links to authoritative Linux documentation.
  • Avoid listing Windows tools or instructions before Linux equivalents unless there is a technical reason; strive for parallel presentation.
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-06 18:15
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits Windows bias by referencing Windows-specific installation patterns (e.g., .exe and .msi files) and omitting Linux equivalents (such as .sh scripts or .deb/.rpm packages). There are no examples or mentions of Linux tools, file formats, or installation commands. Windows terminology and scenarios are presented first and exclusively, with no parity for Linux users.
Recommendations
  • Include Linux-specific examples alongside Windows ones, such as using shell scripts (.sh), tarballs, or package managers (apt, yum) for installation.
  • Mention Linux file formats and installation patterns (e.g., .deb, .rpm, chmod +x, bash install.sh) when discussing application deployment.
  • Provide parallel examples for both Windows and Linux in sections describing start tasks, job preparation, and resource files.
  • Avoid using Windows-centric language exclusively (e.g., .msi, .exe) and clarify that Azure Batch supports both Windows and Linux nodes.
  • Add guidance on handling permissions and execution on Linux nodes (e.g., setting executable bit, using sudo).
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/accounts.md ...ftDocs/azure-docs/blob/main/articles/batch/accounts.md
High Priority View Details →
Scanned: 2026-01-06 18:15
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by referencing Windows-centric tools and workflows, such as the Azure portal and Batch Management .NET library, without mentioning Linux equivalents (e.g., Azure CLI, REST API, or Python SDK). There are no examples or instructions for creating or managing Batch accounts from Linux environments, nor is there mention of Linux-specific tooling or patterns. The documentation implicitly prioritizes Windows approaches and omits guidance for Linux users.
Recommendations
  • Include examples for creating and managing Batch accounts using cross-platform tools such as Azure CLI, REST API, or Python SDK.
  • Explicitly mention Linux compatibility and provide instructions or code samples that can be run on Linux systems.
  • Balance references to Windows-specific tools (like .NET and Azure portal) with equivalent Linux-friendly options (such as Bash scripts, CLI commands, or Python).
  • Add a section or callout highlighting cross-platform development and management options for Azure Batch accounts.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation exclusively demonstrates authentication using the .NET library and the C# AccountManagement sample, both of which are Windows-centric. There are no Linux or cross-platform code examples, nor is there mention of Linux-specific tools or workflows. The Azure portal instructions and terminology (e.g., 'Windows Azure Service Management API') further reinforce a Windows-first perspective.
Recommendations
  • Provide equivalent code samples in cross-platform languages (e.g., Python, Java) using their respective Azure SDKs.
  • Include instructions or references for registering and authenticating applications using CLI tools available on Linux, such as Azure CLI or PowerShell Core (cross-platform).
  • Mention and demonstrate how to run the sample or equivalent workflows on Linux or macOS environments.
  • Avoid using 'Windows' in API names or instructions unless strictly necessary, and clarify when something is cross-platform.
  • Add a section or links for Linux users, covering authentication and application registration steps relevant to their environment.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively providing .NET (C#) code samples, referencing Visual Studio as the development environment, and mentioning Windows-specific tools and workflows. There are no Linux or cross-platform examples, nor are alternative development environments or command-line workflows discussed. The documentation assumes the use of Windows-centric tools and patterns throughout.
Recommendations
  • Provide equivalent code samples using cross-platform .NET Core/.NET 6+ that can be run on Linux and macOS, not just Windows.
  • Include instructions for setting up and running the sample using cross-platform editors like VS Code or JetBrains Rider, and command-line tools (e.g., dotnet CLI) instead of only Visual Studio.
  • Add explicit guidance for running Azure Batch tasks on Linux pools, including any differences in environment variables, file paths, or runtime considerations.
  • Reference and link to Linux/macOS compatible Azure Storage client libraries and usage patterns.
  • Clarify that the File Conventions library and Azure Batch support both Windows and Linux compute nodes, and provide examples or notes for both.
  • If possible, provide a sample project or walkthrough that demonstrates persisting output from a Linux-based Batch task (e.g., using .NET on Ubuntu).
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: 2025-07-13 21:37
Reviewed by: Unknown
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 Windows command-line syntax (cmd.exe /c echo ...), with no mention of Linux or cross-platform shell equivalents. The documentation exclusively references Windows tools (cmd.exe), and does not provide any Linux/bash examples or guidance for non-Windows users. There is no mention of how to adapt the task commands or environment for Linux pools, which are common in Azure Batch scenarios.
Recommendations
  • For every example using Windows command-line syntax (e.g., cmd.exe /c echo ...), provide an equivalent Linux/bash example (e.g., /bin/bash -c 'echo ...').
  • Explicitly mention that Azure Batch supports both Windows and Linux pools, and clarify any differences in task command lines between platforms.
  • When referencing tools or shell environments (such as cmd.exe), provide Linux alternatives (such as /bin/bash) and explain how to select the appropriate shell for the pool OS.
  • Add a section or note about cross-platform considerations, including how to write portable task commands and how to detect the OS of the compute node.
  • Ensure that links to sample code or repositories include Linux examples or instructions for adapting to Linux environments.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a mild Windows bias. PowerShell cmdlets are listed as the first command-line tool, and the use of Remote Desktop (RDP) for accessing compute nodes is mentioned without reference to SSH or Linux alternatives. While the Azure CLI is described as cross-platform and Batch Explorer is available for all OSes, the prominence of PowerShell and RDP, both Windows-centric tools, suggests a preference for Windows workflows. There are no explicit Linux shell or Bash examples, and Linux-native troubleshooting or access patterns are not highlighted.
Recommendations
  • List Azure CLI before PowerShell in the command-line tools section to emphasize cross-platform parity.
  • Mention SSH as an alternative to RDP for accessing compute nodes, especially for Linux-based pools.
  • Include examples or references to Linux shell (Bash) usage where appropriate, such as troubleshooting or file access.
  • Ensure that all tooling and workflow descriptions explicitly note Linux compatibility or provide Linux-specific guidance where workflows differ.
  • Consider adding a note or section on best practices for Linux-based Batch pools, including access, debugging, and environment setup.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias primarily in the 'Configure user subscription mode' section, where only PowerShell cmdlets (Get-AzMarketplaceTerms, Set-AzMarketplaceTerms) are provided for accepting legal terms, with no equivalent Azure CLI or REST API examples. The rest of the page is Azure portal-focused and generally platform-neutral, but the only explicit command-line instructions are Windows/PowerShell-centric. Alternative tools like Azure CLI are only mentioned in a list at the end, not in the main workflow or examples.
Recommendations
  • Provide equivalent Azure CLI commands for all PowerShell examples, especially for accepting Marketplace legal terms (e.g., using 'az vm image terms accept').
  • When referencing command-line tools, mention both PowerShell and Azure CLI options together, or present Azure CLI first to avoid implicit Windows prioritization.
  • Include explicit Linux/macOS-compatible instructions and screenshots where relevant, or clarify that all steps are cross-platform unless otherwise noted.
  • Where possible, link to REST API documentation for users who may prefer scripting outside of PowerShell or CLI.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides both Linux and Windows configuration tables and some parity in example sections. However, there is a noticeable Windows bias: Windows examples (especially for installing drivers and MPI) are more detailed, appear first in example sections, and reference Windows-specific tools (e.g., PowerShell, Remote Desktop, Microsoft MPI) without always providing equivalent Linux command-line or tool examples. The Linux example for GPU drivers is less detailed and lacks explicit command-line instructions, while the Windows example includes a full start task command. There is also a reliance on Windows-centric patterns (e.g., RDP, PowerShell), and the documentation sometimes references Windows tools before Linux equivalents.
Recommendations
  • Provide Linux examples with the same level of detail as Windows, including explicit shell command lines for installing drivers and configuring pools.
  • When listing options or examples, alternate the order or present Linux and Windows in parallel to avoid 'windows_first' bias.
  • Include Linux-native tools and workflows (e.g., SSH, Bash scripts) in examples, not just Windows tools like PowerShell or RDP.
  • For each Windows-specific instruction (e.g., PowerShell commands, RDP), provide the Linux equivalent (e.g., Bash/CLI commands, SSH).
  • Ensure that all example tables (such as start task commands) include both Linux and Windows variants.
  • Link to up-to-date Linux documentation and avoid referencing EOL Linux versions.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a Windows bias by presenting .NET (C#) and Windows-specific examples and references before Linux or cross-platform alternatives. The .NET example uses a Windows Server image, and PowerShell cmdlets are mentioned as a primary tool. While a Python example with Ubuntu is included, it appears after the Windows/.NET example. There are no explicit Linux shell or CLI examples, and the documentation does not provide parity in tool coverage or ordering.
Recommendations
  • Provide Linux/Bash CLI examples alongside or before Windows/PowerShell/.NET examples.
  • Include explicit instructions and code samples for creating and managing autoscale pools using Azure CLI and Bash scripts, not just PowerShell or .NET.
  • When referencing VM images, alternate or equally present Ubuntu/Linux and Windows images in code samples.
  • Mention cross-platform tools (e.g., Azure CLI) before or alongside platform-specific tools (e.g., PowerShell).
  • Ensure that all SDK and API references (Python, Java, CLI) are given equal prominence and ordering as .NET/Windows.
  • Add a section or callout for Linux users, highlighting any differences or considerations.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a mild Windows bias. Windows tools and patterns (e.g., cmd.exe, drive letters, backslashes in paths) are often mentioned first or exclusively. Some examples and directory postfixes use Windows conventions (e.g., backslashes), and Linux equivalents are sometimes less detailed or presented second. There is also a lack of parity in some explanations, such as the use of drive letters for Windows mounts and the absence of explicit Linux mount path examples.
Recommendations
  • Present Linux and Windows examples in parallel, with equal detail and prominence.
  • Avoid using Windows path conventions (e.g., backslashes, drive letters) as the default; provide both Windows and Linux path formats in tables and examples.
  • When referencing tools (e.g., cmd.exe), always include the Linux equivalent (e.g., /bin/sh) with equal detail.
  • For environment variables or features that differ by OS (e.g., AZ_BATCH_APP_PACKAGE naming), provide clear, side-by-side examples for both platforms.
  • Where possible, use OS-agnostic language or clarify when something is OS-specific.
  • Ensure that all instructions, especially those involving directory structures or shell commands, have Linux equivalents and are not Windows-centric.
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: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias in several ways: Windows tools and patterns (such as cmdkey, net use, and Windows-style azcopy syntax) are presented in detail, with explicit examples and command lines. In contrast, Linux equivalents (such as mounting Azure Files with SMB or using azcopy with Linux syntax) are either missing or only briefly mentioned without examples. The order of presentation often places Windows solutions and tools before Linux ones, and there is a lack of parity in the depth of guidance for Linux users.
Recommendations
  • Provide Linux-specific command-line examples for azcopy, including syntax and parameters as used in bash.
  • Include explicit instructions and sample commands for mounting Azure Files shares on Linux VMs (e.g., using mount.cifs or SMB tools).
  • Balance the order of presentation so that Linux and Windows solutions are introduced together or alternate, rather than consistently leading with Windows.
  • Where Windows tools or patterns (e.g., cmdkey, net use) are described, provide the direct Linux equivalents (e.g., mount commands, credential handling) with equal detail.
  • Ensure that all tools mentioned (such as Azure CLI, azcopy, Storage Explorer) are described with usage notes for both platforms, and clarify any platform-specific limitations or differences.
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-custom-images.md ...e-docs/blob/main/articles/batch/batch-custom-images.md
High Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows terminology and examples. In the VM preparation section, RDP (Windows) is mentioned before SSH (Linux), and the only code sample for pool creation uses a Windows node agent SKU ('batch.node.windows amd64') with no Linux equivalent shown. There are no explicit Linux command-line or configuration examples, and the .NET SDK example is Windows-centric. While Linux is mentioned in passing, practical Linux guidance and parity in examples are lacking.
Recommendations
  • Provide parallel Linux examples wherever Windows-specific instructions or code samples are given (e.g., show both 'batch.node.windows amd64' and a Linux node agent SKU in code).
  • Instruct on connecting to VMs using SSH (Linux) before or alongside RDP (Windows), or present both equally.
  • Include Linux command-line examples (e.g., az CLI, Bash) for creating snapshots, images, and pools, not just general references.
  • Ensure all code samples and configuration snippets demonstrate both Windows and Linux scenarios, including REST and SDK usage.
  • Balance references to Windows and Linux documentation links, and avoid defaulting to Windows-first language or ordering.
GitHub Create Pull Request
← Previous Page 8 of 18 Next →