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 351-375 of 436 flagged pages
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-pool-create-event.md ...cs/blob/main/articles/batch/batch-pool-create-event.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing Windows VM sizes and OS families before Linux equivalents, and by providing detailed configuration options for Windows (e.g., windowsConfiguration) without corresponding Linux configuration details. There are references to deprecated Cloud Services pools that are exclusively Windows-based, and Linux-specific configuration examples or notes are missing.
Recommendations
  • Add explicit Linux configuration examples, such as a linuxConfiguration section analogous to windowsConfiguration.
  • Present Linux and Windows VM size references together, or list Linux first where appropriate.
  • Include notes or examples for configuring pools with Linux images, including relevant settings and options.
  • Clarify which features are available for Linux pools and provide parity in documentation coverage.
  • Deprecate or minimize references to Windows-only features (such as Cloud Services pools) and highlight Virtual Machine Configuration pools as the cross-platform standard.
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-pools-to-simplified-compute-node-communication-model-migration-guide.md ...ified-compute-node-communication-model-migration-guide.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. In the FAQ section, RDP (a Windows-specific remote access protocol) is mentioned before SSH (the Linux equivalent), and no concrete examples or commands for either platform are provided. Additionally, when discussing the Batch agent, the Windows executable (.exe) is listed after the cross-platform agent, but no further Linux-specific details or examples are given. There are no PowerShell-heavy examples or exclusive references to Windows tools, but Linux parity is not fully achieved due to lack of explicit examples and ordering.
Recommendations
  • Provide explicit Linux and Windows examples for connecting to nodes (e.g., SSH command for Linux, RDP instructions for Windows).
  • When listing remote access methods, mention SSH before or alongside RDP to avoid Windows-first ordering.
  • Include sample commands or configuration snippets for both Linux and Windows environments where relevant.
  • Clarify agent usage and differences for both operating systems, including file paths and invocation methods.
  • Ensure that any tooling or workflow references are cross-platform or have Linux equivalents clearly documented.
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/low-priority-vms-retirement-migration-guide.md ...s/batch/low-priority-vms-retirement-migration-guide.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for migrating Batch low-priority VMs to Spot VMs. However, PowerShell (a Windows-centric tool) is given as the only alternative automation method after CLI, with no mention of Linux-native scripting alternatives (e.g., Bash, shell scripts) or cross-platform SDK code samples. The CLI examples are cross-platform, but PowerShell is highlighted as the main alternative, and there are no Linux-specific troubleshooting or validation examples. The documentation does not mention Linux tools or patterns beyond the use of Ubuntu images in pool configuration.
Recommendations
  • Add explicit Bash/shell script examples for automation on Linux, especially for validation and troubleshooting steps.
  • Clarify that Azure CLI is cross-platform and can be used on both Windows and Linux.
  • Include examples using SDKs (Python, .NET, etc.) for pool creation and migration to provide parity for Linux and macOS users.
  • Mention Linux-native tools (e.g., jq for JSON parsing) in validation and troubleshooting sections.
  • If PowerShell is mentioned, also mention PowerShell Core (pwsh) is available cross-platform, or provide equivalent Bash commands.
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
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation generally maintains cross-platform parity, but there is a subtle Windows bias in the ordering and example selection. In the section on obtaining managed identity tokens, the Windows/PowerShell example is presented before the Linux/Bash example. Additionally, the documentation references the Azure Instance Metadata Service using a Windows-specific documentation link. However, both Windows and Linux methods are ultimately provided, and the rest of the documentation is platform-neutral.
Recommendations
  • Present Linux and Windows examples in parallel or alternate the order, rather than always listing Windows/PowerShell first.
  • When referencing the Azure Instance Metadata Service, link to both the Windows and Linux documentation, or to a platform-neutral overview.
  • Explicitly state that all features and examples apply equally to both Windows and Linux Batch nodes, where applicable.
  • Consider providing .NET code samples that show both Windows and Linux pool configurations, if there are any differences.
  • Audit other sections for subtle ordering or phrasing that may imply Windows is the default or primary platform.
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/network-security-perimeter.md ...blob/main/articles/batch/network-security-perimeter.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides step-by-step instructions for associating an Azure Batch account with a network security perimeter using the Azure portal, PowerShell, and Azure CLI. However, the PowerShell example is given before the Azure CLI example, which can be interpreted as a Windows-first bias. Additionally, the PowerShell section is detailed and uses Windows-centric tooling, which may not be as familiar or available to Linux users. There are no explicit Linux-specific examples or mentions of Linux shell scripting, and no mention of Bash or cross-platform scripting alternatives.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as Azure CLI is cross-platform and more accessible to Linux users.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide Bash-friendly command snippets where appropriate.
  • Consider adding Bash script examples for common automation scenarios.
  • Where PowerShell is referenced, clarify that PowerShell Core is available cross-platform, or provide equivalent Bash/CLI alternatives.
  • Review screenshots and UI references to ensure they are not Windows-specific (e.g., avoid showing only Windows UI elements if possible).
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/pool-endpoint-configuration.md ...lob/main/articles/batch/pool-endpoint-configuration.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation alternates between Windows (RDP) and Linux (SSH) examples, but consistently presents Windows/RDP examples before Linux/SSH ones in each section. The C# code samples are used for Windows pools (RDP), while Python is used for Linux pools (SSH), reinforcing a pattern of Windows-first presentation and tool/language association. No PowerShell-specific examples are present, but the ordering and language choice may subtly prioritize Windows environments.
Recommendations
  • Alternate the order of examples so that Linux/SSH is presented first in some sections, or present both examples side-by-side.
  • Explicitly state that both Windows and Linux pools are equally supported and that the choice of language (C# for Windows, Python for Linux) is arbitrary.
  • Provide equivalent code samples in both languages (C# and Python) for both Windows and Linux pool scenarios, to avoid reinforcing language/OS associations.
  • Include a note clarifying that the configuration principles apply equally to both operating systems and that users may choose their preferred language/tool regardless of OS.
  • Consider adding PowerShell and Bash/CLI examples for parity, if relevant.
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/quick-create-template.md ...docs/blob/main/articles/batch/quick-create-template.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by focusing exclusively on the Azure Portal for deployment and referencing Azure PowerShell before Azure CLI or REST API. There are no explicit Linux or cross-platform command-line examples (such as Azure CLI), and the only alternative deployment method linked is for PowerShell, with no direct mention or example of Linux-friendly tools or workflows.
Recommendations
  • Add explicit Azure CLI deployment instructions and examples alongside or before PowerShell, as Azure CLI is cross-platform and widely used on Linux.
  • Provide direct links to both PowerShell and Azure CLI deployment documentation, not just PowerShell.
  • Include a section or callout for Linux/macOS users, highlighting cross-platform tools and workflows.
  • Ensure that when listing alternative deployment methods, Azure CLI is mentioned before or alongside PowerShell to avoid the perception of Windows-first bias.
  • Consider adding bash shell script examples for automation, which are common in Linux environments.
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/simplified-node-communication-pool-no-public-ip.md ...tch/simplified-node-communication-pool-no-public-ip.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias in its troubleshooting section, where network connectivity testing is presented first with a Windows PowerShell command (Test-NetConnection), followed by the Linux equivalent (nc). No other command-line examples are provided, and the rest of the documentation is generally platform-neutral, focusing on Azure portal, REST API, and ARM templates. However, the order and prominence of Windows tooling in the example suggest a subtle preference for Windows users.
Recommendations
  • Present Linux and Windows troubleshooting commands side-by-side or alternate their order to avoid implicit prioritization.
  • Include more explicit Linux examples where relevant, such as using SSH from a Linux jumpbox, or other Linux-native tools for diagnostics.
  • Clarify that both Windows and Linux are supported equally for all operations, and provide parity in example commands and screenshots where possible.
  • Consider adding Bash/CLI examples for pool creation and diagnostics to complement PowerShell and portal instructions.
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-certificate-migration-guide.md ...in/articles/batch/batch-certificate-migration-guide.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page generally describes migration steps and alternatives for both Windows and Linux Batch pools. However, in the FAQ section, links to Windows documentation are presented before Linux equivalents, and there is a lack of concrete, step-by-step Linux-specific examples or commands (e.g., for certificate access or installation). The Linux guidance is less detailed and more abstract, while Windows is referenced first and more directly.
Recommendations
  • Present Windows and Linux documentation links together or alternate their order to avoid implicit prioritization.
  • Provide explicit Linux command-line examples (e.g., bash scripts, chmod/chown usage) for certificate installation and access.
  • Include sample configuration snippets for both Windows (PowerShell) and Linux (shell) environments.
  • Ensure that Linux-specific tools, patterns, and troubleshooting steps are covered with equal detail as Windows.
  • Add a dedicated section for Linux migration steps, mirroring any Windows-specific guidance.
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-pools-to-simplified-compute-node-communication-model-migration-guide.md ...ified-compute-node-communication-model-migration-guide.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page displays subtle Windows bias by mentioning RDP connectivity before SSH in the FAQ section and by not providing concrete examples or instructions for Linux users (e.g., SSH commands, Linux agent details). Windows terminology (RDP, .exe) is used before Linux equivalents, and there are no Linux-specific examples or guidance.
Recommendations
  • Provide explicit Linux examples alongside Windows ones, such as SSH commands for node access.
  • Mention Linux tools and patterns (e.g., shell commands, Linux agent names) before or alongside Windows equivalents.
  • Clarify agent naming and behavior for both Linux and Windows nodes, including file extensions and invocation details.
  • Ensure that documentation sections addressing connectivity, diagnostics, and migration steps include Linux-specific instructions and screenshots where applicable.
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-virtual-network.md ...docs/blob/main/articles/batch/batch-virtual-network.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page generally maintains platform neutrality, but there is evidence of Windows bias in the ordering and specificity of examples. In several places, Windows tools and patterns (such as RDP and port 3389) are mentioned before Linux equivalents (SSH and port 22), and remote access instructions reference Windows first. There are no explicit Linux or cross-platform command-line examples (e.g., Azure CLI, Bash), and the portal instructions do not mention Linux-specific considerations or alternatives. Additionally, while both Windows and Linux ports are referenced for NSG rules, the documentation does not provide parity in examples or troubleshooting for Linux users.
Recommendations
  • Present Linux and Windows examples side-by-side or alternate the order to avoid implicit prioritization.
  • Include explicit Azure CLI and Bash examples for pool and VNet provisioning, not just portal instructions.
  • Add troubleshooting and configuration notes specific to Linux environments (e.g., SSH key setup, SELinux/firewall considerations).
  • Reference Linux tools and patterns (e.g., SSH, scp, Linux file mounts) equally with Windows tools (e.g., RDP, SMB).
  • Ensure that all remote access instructions and NSG rules are equally detailed for both platforms, including multi-instance task scenarios common in Linux HPC workloads.
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/simplified-node-communication-pool-no-public-ip.md ...tch/simplified-node-communication-pool-no-public-ip.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page exhibits mild Windows bias in troubleshooting examples, where Windows PowerShell commands (Test-NetConnection) are listed before Linux equivalents (nc). There are no Linux-specific tools or patterns mentioned elsewhere, and no Linux-first examples. However, the main REST API and ARM template examples use Ubuntu images, which is positive for Linux parity.
Recommendations
  • Present troubleshooting command examples for both Windows and Linux side-by-side, or alternate which OS is listed first.
  • Include more Linux-specific tools (e.g., curl, telnet) in troubleshooting sections.
  • Add explicit Linux CLI (bash) examples for common tasks, such as connecting to compute nodes, in addition to Windows/PowerShell.
  • Ensure that any references to Azure CLI or PowerShell are balanced, and provide parity in example depth and clarity.
  • Consider adding a dedicated section for Linux users, highlighting best practices and common issues.
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-pool-create-event.md ...cs/blob/main/articles/batch/batch-pool-create-event.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias by listing Windows VM size documentation before Linux equivalents and providing detailed information about Windows OS families and configurations, while Linux-specific details and examples are minimal or absent. There are no Linux-specific configuration examples or references to Linux node settings, and the only OS-specific configuration section is for Windows.
Recommendations
  • Present Linux and Windows VM size documentation links together or list Linux first to balance ordering.
  • Add a Linux-specific configuration section (e.g., 'linuxConfiguration') analogous to 'windowsConfiguration', with details on supported settings.
  • Include example event bodies and configuration snippets for both Windows and Linux pools.
  • Provide information about supported Linux distributions, versions, and node agent SKUs.
  • Explicitly mention parity or differences in features/settings between Windows and Linux pools.
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/account-move.md ...cs/azure-docs/blob/main/articles/batch/account-move.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes using the Azure portal GUI for exporting and deploying ARM templates, with no mention of command-line alternatives. There are no examples using cross-platform CLI tools (such as Azure CLI or Azure PowerShell), nor are Linux-specific workflows or tools referenced. The instructions and screenshots implicitly assume a Windows-centric user experience, as the Azure portal is most commonly accessed from Windows environments, and no alternatives for Linux users are provided.
Recommendations
  • Add examples using Azure CLI commands for exporting, modifying, and deploying ARM templates, which work on both Windows and Linux.
  • Include instructions for using Azure PowerShell, but ensure Azure CLI examples are presented first or alongside them to avoid Windows-first bias.
  • Mention that the Azure portal is accessible from any OS, but provide guidance for users who prefer command-line or automation workflows.
  • Reference Linux shell commands (e.g., unzip, jq) for manipulating downloaded template files.
  • Clarify that the process is OS-agnostic and provide parity in tooling and examples for both Windows and Linux users.
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/low-priority-vms-retirement-migration-guide.md ...s/batch/low-priority-vms-retirement-migration-guide.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for migrating Batch pools to Spot VMs. However, PowerShell (a Windows-centric tool) is presented as the only alternative automation method, with no mention of Bash, shell scripting, or Linux-native tools. The PowerShell section is given equal prominence to Azure CLI, and there are no explicit Linux shell or scripting examples. Additionally, the documentation refers to PowerShell validation steps but does not provide equivalent Linux/Bash validation commands. The Azure portal instructions are platform-neutral, but the automation guidance leans toward Windows/PowerShell usage.
Recommendations
  • Add Bash/shell scripting examples for automation, especially for validation steps currently shown only in PowerShell.
  • Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
  • Include Linux-native automation alternatives (e.g., Bash scripts, cron jobs) alongside PowerShell.
  • Explicitly mention that PowerShell Core is available on Linux, or provide guidance for Linux users if PowerShell is required.
  • Ensure that troubleshooting and validation steps include both PowerShell and Bash/CLI commands.
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/quick-create-template.md ...docs/blob/main/articles/batch/quick-create-template.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page primarily demonstrates deploying an ARM template using the Azure Portal, with only a brief mention of alternative methods (Azure PowerShell, Azure CLI, REST API) at the end of the deployment section. The link provided for 'other deployment methods' points to a PowerShell-centric page, and there are no explicit Linux or cross-platform CLI examples given. This structure implicitly prioritizes Windows/Portal workflows and omits direct Linux or cross-platform command-line instructions.
Recommendations
  • Add explicit Azure CLI examples for deploying the ARM template, as Azure CLI is cross-platform and widely used on Linux.
  • When referencing 'other deployment methods,' provide direct links to both Azure CLI and PowerShell documentation, not just PowerShell.
  • Include a section or callout with step-by-step instructions for deploying the template using Azure CLI on Linux/macOS, alongside the existing portal instructions.
  • Ensure that any referenced scripts or commands are shown in both PowerShell and Bash (or at least CLI) formats where applicable.
  • Avoid defaulting to Windows/PowerShell terminology or links when cross-platform alternatives exist.
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/pool-endpoint-configuration.md ...lob/main/articles/batch/pool-endpoint-configuration.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation presents Windows (RDP) examples before Linux (SSH) examples in both the introductory text and code samples. The first example in each section is for Windows pools using RDP, followed by Linux pools using SSH. The terminology and structure consistently mention Windows endpoints and tools (RDP) before their Linux equivalents (SSH), indicating a subtle 'windows_first' bias. However, both platforms are covered with equivalent examples, and no platform is omitted.
Recommendations
  • Alternate the order of examples so that Linux (SSH) is presented first in some sections.
  • Explicitly state parity between Windows and Linux pools in the introduction, emphasizing equal support.
  • Provide a summary table comparing RDP (Windows) and SSH (Linux) endpoint configuration patterns.
  • Ensure that any tooling or terminology (e.g., RDP, SSH) is introduced in a neutral, platform-agnostic manner.
  • Consider including cross-platform scripting examples (e.g., Bash, PowerShell) for endpoint configuration if relevant.
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/manage-private-endpoint-connections.md .../articles/batch/manage-private-endpoint-connections.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents Windows-centric management options first, with the Azure portal and Az PowerShell module examples preceding Azure CLI examples. PowerShell is a Windows-native tool, and its usage is highlighted before the cross-platform Azure CLI, which is more common on Linux/macOS. No Linux-specific shell or tool examples (e.g., Bash scripting, native Linux tools) are provided.
Recommendations
  • Present Azure CLI examples before PowerShell examples to prioritize cross-platform usage.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
  • Include Bash script examples or notes for Linux users (e.g., variable syntax differences).
  • Add a section on managing private endpoint connections using REST API or SDKs, which are platform-agnostic.
  • Clarify that PowerShell is available on Linux/macOS, but CLI is typically preferred in those environments.
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-pools-to-simplified-compute-node-communication-model-migration-guide.md ...ified-compute-node-communication-model-migration-guide.md
Medium Priority View Details →
Scanned: 2026-01-06 18:15
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates subtle Windows bias by mentioning RDP connectivity before SSH in the FAQ section and by not providing explicit Linux-specific examples or instructions. While both Linux and Windows are referenced in the context of agent binaries, practical guidance (e.g., how to connect for diagnostics) is presented in a Windows-first order and lacks Linux parity in terms of example commands or troubleshooting steps.
Recommendations
  • Present SSH connectivity before or alongside RDP in diagnostic connection instructions to avoid Windows-first ordering.
  • Include explicit Linux examples, such as SSH command-line usage or troubleshooting steps for Linux nodes.
  • Provide parity in agent binary references, e.g., clarify the usage and location of agent binaries on both Linux and Windows.
  • Add Linux-specific networking configuration guidance where relevant, such as firewall or outbound access setup.
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-cli-templates.md ...e-docs/blob/main/articles/batch/batch-cli-templates.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page generally maintains cross-platform language and includes a Linux-based pool template example. However, in the section on file transfer, all CLI examples use Windows-style paths (e.g., c:\source_videos\*.mp4), with no Linux/macOS equivalents provided. This implicitly prioritizes Windows users and may confuse or exclude Linux/macOS users.
Recommendations
  • For every CLI example using a Windows file path, provide a Linux/macOS equivalent (e.g., /home/user/source_videos/*.mp4).
  • When referencing file paths, use platform-neutral language or clarify that the syntax differs by OS.
  • Consider alternating the order of examples or presenting both Windows and Linux/macOS commands side by side.
  • Explicitly state that the Azure CLI and Batch CLI extension are cross-platform and provide links to OS-specific installation instructions if needed.
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-pool-create-event.md ...cs/blob/main/articles/batch/batch-pool-create-event.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Windows Heavy
Summary
The documentation demonstrates a Windows-first bias by referencing Windows OS families and configurations in detail, providing explicit mapping to Windows Server versions, and including a dedicated section for Windows-specific configuration (windowsConfiguration). Linux-specific configuration is only mentioned indirectly (e.g., by exclusion), and there is no equivalent Linux configuration section or detailed mapping for Linux OS images. Additionally, the deprecated 'cloudServiceConfiguration' is exclusively Windows-based.
Recommendations
  • Add a 'linuxConfiguration' section parallel to 'windowsConfiguration', describing available Linux-specific settings for virtual machines.
  • Include explicit examples and documentation for Linux OS images, such as common publishers/offers/SKUs for popular Linux distributions.
  • Where OS families or versions are discussed, provide equivalent Linux information (e.g., mapping of common Linux image references, links to Linux release notes).
  • When referencing documentation for VM sizes, ensure Linux and Windows links are presented together or Linux-first, not Windows-first.
  • Clarify in notes and tables when a property is Windows-only, and provide Linux alternatives or state explicitly when Linux does not require a setting.
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-pool-node-error-checking.md .../main/articles/batch/batch-pool-node-error-checking.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page generally avoids platform-specific instructions or examples, but the only explicit OS-specific mention is for Windows pools in the 'Node OS updates' section. There are no Linux-specific instructions, examples, or parity notes. No shell or PowerShell commands are shown, but the only OS-specific configuration (automatic updates) is described for Windows, with no mention of Linux equivalents or differences.
Recommendations
  • Add a section or note describing how OS updates are handled for Linux pools, including default behaviors and configuration options.
  • Wherever Windows-specific behaviors or properties are mentioned (such as 'enableAutomaticUpdates'), include equivalent information for Linux pools, or explicitly state if not applicable.
  • If there are differences in troubleshooting steps, log file locations, or node management between Windows and Linux pools, provide parallel guidance or examples.
  • Consider including at least one example error or scenario that is specific to Linux pools to demonstrate parity and awareness of cross-platform usage.
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/manage-private-endpoint-connections.md .../articles/batch/manage-private-endpoint-connections.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents PowerShell examples before Azure CLI examples, which may suggest a Windows-first perspective. The PowerShell section is detailed and appears before the cross-platform Azure CLI section, potentially prioritizing Windows users. However, both PowerShell and CLI examples are provided, and the CLI examples use POSIX shell syntax, supporting Linux/macOS users.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples to avoid implying Windows is the primary platform.
  • Explicitly mention that Azure CLI commands are cross-platform and suitable for Linux, macOS, and Windows.
  • Consider adding a short note or table at the top summarizing tool parity and platform support.
  • Ensure that any screenshots or UI references are not Windows-specific (the current portal section is neutral).
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-service-workflow-features.md ...main/articles/batch/batch-service-workflow-features.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page describes the Azure Batch workflow and resources in a platform-neutral way, but there are subtle signs of Windows bias. The workflow and examples do not mention Linux-specific considerations, tools, or patterns, and the 'Next steps' section highlights the .NET client library (commonly associated with Windows) before Python. There are no explicit Linux or cross-platform examples, nor are Linux-specific tools or shell scripting mentioned.
Recommendations
  • Include explicit references to both Windows and Linux when discussing compute node OS selection, with examples for each.
  • Provide sample workflows or links to quickstarts for both Windows (PowerShell, .NET) and Linux (Bash, Python, etc.) environments.
  • Mention Linux-friendly tools and scripting options (e.g., Bash scripts) alongside Windows tools.
  • Ensure parity in the order of presenting SDKs and tools (e.g., list Python and .NET together or alternate their order).
  • Add a note or section highlighting cross-platform support and any OS-specific considerations for Batch tasks.
GitHub Create Pull Request
Batch https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/quick-create-template.md ...docs/blob/main/articles/batch/quick-create-template.md
Medium Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation primarily demonstrates deployment using the Azure Portal, and when mentioning alternative methods, it lists Azure PowerShell before Azure CLI and REST API. There are no explicit Linux or cross-platform command-line examples (e.g., Azure CLI or Bash), and the only linked deployment method is to a PowerShell-focused page, which may suggest a Windows-first or Windows-centric approach.
Recommendations
  • Provide explicit Azure CLI examples for deploying the ARM template, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • When listing alternative deployment methods, mention Azure CLI before or alongside Azure PowerShell to avoid the impression of Windows-first bias.
  • Include Bash shell or Linux terminal screenshots or instructions where relevant, to demonstrate parity.
  • Link to both PowerShell and CLI deployment documentation, or provide direct step-by-step instructions for both.
  • Explicitly state that all deployment methods are supported on Windows, Linux, and macOS where applicable.
GitHub Create Pull Request
← Previous Page 15 of 18 Next →