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 301-325 of 436 flagged pages
Batch Provision a pool with Auto OS Upgrade ...-docs/blob/main/articles/batch/batch-upgrade-policy.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 code examples (REST API and C# SDK) exclusively use Windows OS images and Windows-specific node agent SKUs. There are no Linux equivalents or examples provided, nor is there guidance for Linux-specific configuration. Windows terminology and tooling (e.g., 'MicrosoftWindowsServer', 'batch.node.windows amd64', 'windowsConfiguration') are used throughout, with no mention of Linux images, agent SKUs, or configuration options.
Recommendations
  • Provide parallel examples for Linux pools, including REST API and SDK code snippets using Linux images (e.g., Ubuntu, CentOS) and Linux node agent SKUs.
  • Include documentation on Linux-specific configuration properties (such as 'linuxConfiguration') and any differences in upgrade behavior.
  • Mention Linux image publishers/offers/SKUs in supported OS images section.
  • Clarify any differences in automatic upgrade policies or requirements for Linux pools.
  • Ensure FAQs and requirements sections address Linux scenarios as well as Windows.
GitHub Create Pull Request
Batch Use ephemeral OS disk nodes for Azure Batch pools ...b/main/articles/batch/create-pool-ephemeral-os-disk.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page exhibits Windows bias by referencing PowerShell as the only example for programmatically querying VM capabilities (specifically 'EphemeralOSDiskSupported'). No equivalent Linux or cross-platform CLI example is provided. Additionally, Windows tooling is mentioned before any Linux alternatives, and the documentation does not clarify how Linux/macOS users can perform the same query.
Recommendations
  • Add Azure CLI and/or REST API examples for querying VM capabilities, especially for 'EphemeralOSDiskSupported', to ensure Linux/macOS users have clear guidance.
  • Explicitly mention cross-platform tools and provide example commands for both Windows (PowerShell) and Linux/macOS (Azure CLI, Bash, etc.).
  • Where PowerShell is referenced, include a note about equivalent steps for non-Windows environments.
  • Consider reordering examples so that cross-platform or Linux options are presented first or alongside Windows options.
GitHub Create Pull Request
Batch Run tasks under user accounts ...e-docs/blob/main/articles/batch/batch-user-accounts.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 displays a moderate Windows bias. Windows concepts and tools (e.g., RDP, DPAPI, 'cmd.exe') are introduced before their Linux equivalents, and some examples (such as command lines and secrets management) use Windows-specific tools or patterns. While Linux is mentioned and Linux-specific code samples are present, Windows examples and terminology are often presented first or exclusively, and Linux alternatives (e.g., for secrets management) are not discussed in detail.
Recommendations
  • Ensure Linux and macOS examples are presented alongside Windows examples, ideally in parallel sections.
  • When describing tools or APIs (e.g., DPAPI), mention Linux equivalents (such as GnuPG, OpenSSL, or other secrets management approaches).
  • Provide Linux-specific command line examples (e.g., using '/bin/bash -c' instead of 'cmd.exe /c') wherever Windows commands are shown.
  • Discuss SSH and Linux user management patterns with equal detail as Windows RDP and user management.
  • Avoid presenting Windows examples or terminology first; alternate or group by platform.
  • Add explicit guidance for Linux/macOS users in sections where only Windows tools are mentioned.
GitHub Create Pull Request
Batch Best practices .../azure-docs/blob/main/articles/batch/best-practices.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-specific tools (e.g., PowerShell) are referenced multiple times, sometimes before or in greater detail than their Linux equivalents. Examples for disk preparation and troubleshooting are more detailed for Windows (PowerShell cmdlets and scripts), while Linux instructions are present but less emphasized and sometimes lack concrete command examples. Windows-specific patterns (directory junctions, Windows Services) are discussed in dedicated sections, whereas Linux equivalents (systemd, symlinks) are mentioned but not explored as thoroughly. In some cases, Windows tooling is listed first or exclusively, and Linux users may need to infer or adapt instructions.
Recommendations
  • Provide Linux CLI or shell command examples wherever PowerShell is shown for Windows (e.g., disk enumeration, formatting, mounting).
  • Ensure Linux tools (e.g., fdisk, mkfs, lsblk) are given equal prominence and detailed usage instructions as Windows/PowerShell equivalents.
  • When listing tools or APIs, alternate the order or present both Windows and Linux options together.
  • Expand Linux-specific troubleshooting and operational guidance (e.g., handling services with systemd, dealing with symlinks, log collection).
  • Add explicit Linux/macOS examples for common tasks, not just references to external articles.
GitHub Create Pull Request
Batch Use extensions with Batch pools ...ocs/blob/main/articles/batch/create-pool-extensions.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 provides both Linux and Windows examples for creating Batch pools with extensions, but there is a slight Windows bias in the order and breadth of extension support. Windows-specific extensions (e.g., Antimalware, Diagnostics, HPC GPU for AMD) are listed without Linux equivalents, and Windows tools (certificateStoreLocation: LocalMachine, keyExportable) are mentioned. The troubleshooting section references logging into compute nodes but does not specify Linux troubleshooting steps or log locations. The Application Health extension section is platform-neutral, but overall, Windows extensions and tools are more prominently featured.
Recommendations
  • Ensure Linux and Windows examples are presented in parallel, with equal detail and order.
  • Add Linux equivalents for Windows-only extensions where possible, or clarify if not available.
  • Provide Linux-specific troubleshooting steps and log file locations.
  • Highlight platform differences explicitly and provide guidance for both OSes.
  • Avoid Windows-centric terminology (e.g., LocalMachine) without Linux analogs.
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-13 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 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 to the CLI, with no mention of Bash scripting or Linux/macOS-specific automation methods. The PowerShell section assumes a Windows environment, and there are no explicit Linux/macOS shell or scripting examples. Additionally, the PowerShell option is described as an 'alternative automation method' without clarifying cross-platform compatibility, which may cause friction for non-Windows users.
Recommendations
  • Add Bash shell scripting examples alongside PowerShell for automation, especially for common tasks like pool creation and validation.
  • Clarify that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS, and consider making this explicit in the documentation.
  • If PowerShell is included, mention that PowerShell Core is cross-platform, or provide equivalent Bash or Python automation examples.
  • In the 'Option 2' section, rename it to 'PowerShell (Windows and cross-platform)' and add a note about PowerShell Core compatibility, or provide a Linux/macOS alternative.
  • Ensure that any references to scripting or automation do not assume a Windows environment by default.
GitHub Create Pull Request
Batch Monitor Azure Batch ...s/azure-docs/blob/main/articles/batch/monitor-batch.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 moderate Windows bias. It references Windows-centric tools (Batch Explorer, Batch .NET library, Application Insights for .NET) and provides walkthroughs and code samples only for .NET (Windows-first technology stack). There are no examples or guidance for Linux/macOS users, such as using Python SDK, CLI, or cross-platform monitoring tools. The lack of Linux-specific or cross-platform examples may create friction for non-Windows users.
Recommendations
  • Add examples using Azure CLI and PowerShell side-by-side, or clarify that CLI is cross-platform.
  • Include sample code for monitoring Batch using Python SDK (azure-batch), which runs on Linux/macOS.
  • Reference cross-platform tools (e.g., azcopy, Azure Storage Explorer) for accessing diagnostic logs.
  • Provide guidance for integrating Application Insights with non-.NET (e.g., Python) Batch applications.
  • Explicitly mention Linux/macOS compatibility for Batch Explorer and other tools, or suggest alternatives if not supported.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation primarily demonstrates deployment via the Azure portal, which is platform-neutral, but when mentioning alternative deployment methods, it lists Azure PowerShell first, followed by Azure CLI and REST API. There are no explicit Linux/macOS examples, nor are Linux-specific tools or shell commands shown. The linked 'Deploy templates' page is referenced with a PowerShell-focused URL, further reinforcing a Windows-first perspective.
Recommendations
  • Explicitly provide example commands for both Azure CLI and PowerShell when discussing alternative deployment methods.
  • Reference Linux/macOS usage (e.g., Bash, Azure CLI on Linux) alongside Windows/PowerShell.
  • Ensure links to further documentation do not default to PowerShell tabs or examples; provide parity for CLI and REST API.
  • Consider adding a section or note for deploying via Azure CLI on Linux/macOS, with sample commands.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exhibits a notable Windows bias: compute nodes are created with Windows Server images only, and all task examples use Windows command-line tools (e.g., 'cmd /c type'). There are no examples or instructions for using Linux pools, Linux VM images, or Linux shell commands. The documentation also references Windows-centric development environments (Visual Studio) before mentioning cross-platform .NET CLI options.
Recommendations
  • Add explicit instructions and code samples for creating Linux-based pools (e.g., using Ubuntu or CentOS Marketplace images).
  • Provide Linux shell command equivalents for task execution (e.g., 'bash -c cat {filename}').
  • Show how to configure the VirtualMachineConfiguration for Linux nodes, including nodeAgentSkuId and ImageReference.
  • Ensure examples for building and running the app using the .NET CLI are given equal prominence to Visual Studio.
  • Clarify that both Windows and Linux pools are supported, and link to relevant documentation for Linux configuration.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides parity between Windows and Linux in terms of supported features and step-by-step instructions, but exhibits a moderate Windows bias in several areas. PowerShell is used as the primary automation example for both platforms, even though it is native to Windows and less common on Linux. Windows-specific tools and patterns (e.g., 'cmdkey', 'net use', RDP) are described in detail, often before Linux equivalents. Troubleshooting and manual mounting instructions are more verbose for Windows, and references to Windows tools appear first in several sections.
Recommendations
  • Provide native Bash or shell script examples for Linux, rather than relying solely on PowerShell for automation.
  • Present Linux and Windows instructions in parallel, or alternate which platform is shown first in each section.
  • Expand troubleshooting steps for Linux to match the detail given for Windows, including common Linux-specific errors and solutions.
  • Include more Linux-native tool references (e.g., 'mount', 'cifs-utils', 'nfs-common') and usage patterns.
  • Clarify when PowerShell is required on Linux, and offer alternatives for users who prefer Bash or other shells.
GitHub Create Pull Request
Batch Move an Azure Batch account to another region ...cs/azure-docs/blob/main/articles/batch/account-move.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes moving an Azure Batch account using the Azure portal, with all instructions and examples focused on GUI interactions. There are no command-line examples, and no mention of cross-platform tools such as Azure CLI or PowerShell. The workflow implicitly assumes a Windows environment, as the Azure portal is most commonly accessed from Windows, and there is no guidance for Linux users or those preferring automation via CLI tools.
Recommendations
  • Add equivalent instructions for moving a Batch account using Azure CLI, which is cross-platform and widely used on Linux.
  • Include PowerShell examples for users who prefer scripting, but ensure Azure CLI examples are presented first or alongside PowerShell to avoid Windows-first bias.
  • Explicitly mention that the Azure portal is accessible from any OS, and provide links or notes for Linux/macOS users.
  • Provide sample scripts for exporting, modifying, and deploying ARM templates using Azure CLI and/or PowerShell.
  • Clarify any OS-specific steps (e.g., unzipping files) and offer alternatives for Linux/macOS.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page generally covers both Windows and Linux Batch pools, but there is a subtle Windows bias: in the FAQ section, the link to Windows documentation is listed before the Linux equivalent, and there are no concrete Linux-specific command examples or step-by-step instructions, especially for certificate handling. Linux users are told to 'run such commands' without examples, while Windows users are implicitly prioritized in documentation references.
Recommendations
  • Provide explicit Linux command-line examples (e.g., bash scripts, chmod usage) for certificate installation and access.
  • Ensure Linux documentation links are presented alongside or before Windows links when discussing cross-platform support.
  • Include step-by-step instructions for Linux users on how to handle certificate permissions and access, not just general guidance.
  • Add sample start task/job prep scripts for Linux environments.
  • Review and balance the order of platform references throughout the documentation to avoid implicit prioritization.
GitHub Create Pull Request
Batch Configure node endpoints in Azure Batch pool ...lob/main/articles/batch/pool-endpoint-configuration.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation alternates Windows (RDP) and Linux (SSH) examples, but consistently presents Windows/RDP examples first in each section. The introductory text also mentions RDP before SSH. The C# code samples for Windows pools use RDP and the Python samples for Linux pools use SSH, but there is no explicit parity in tool or scripting language recommendations (e.g., PowerShell vs Bash). The documentation does not provide command-line examples for either OS, but the ordering and emphasis slightly favor Windows.
Recommendations
  • Alternate the order of Windows and Linux examples in each section, or present them side-by-side to avoid implicit prioritization.
  • Explicitly mention both RDP (Windows) and SSH (Linux) together in introductory and summary sections.
  • Provide equivalent command-line examples for both Windows (PowerShell) and Linux (Bash), if relevant to the audience.
  • Ensure that tooling and terminology for both OSes are introduced with equal prominence.
  • Consider adding a table or summary comparing endpoint configuration for Windows and Linux pools to reinforce parity.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page exclusively provides .NET (C#) code samples and instructions, which are most commonly used on Windows platforms. There are no Linux-specific examples, alternative tools, or cross-platform guidance. The documentation implicitly assumes a Windows development environment, with no mention of how to perform these tasks on Linux or using Linux-friendly tools (e.g., CLI, Bash, Python).
Recommendations
  • Add equivalent examples using Azure CLI and/or Bash scripts to demonstrate how to manage Batch accounts and quotas on Linux.
  • Include Python SDK examples, as Python is widely used on Linux and is mentioned in the 'Next steps' section.
  • Explicitly state cross-platform compatibility of the .NET SDK and provide guidance for Linux/Mac users (e.g., using .NET Core/.NET 6+ on Linux).
  • Reference Linux-friendly authentication methods and environment setup steps.
  • Balance the order of examples so that Windows and Linux approaches are presented equally, or clarify that the .NET SDK is cross-platform.
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-12 00:00
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 examples or details. There are no Linux-specific configuration examples or references to Linux tools or patterns.
Recommendations
  • Add explicit Linux configuration examples, such as a linuxConfiguration section analogous to windowsConfiguration, with details on settings relevant to Linux pools.
  • Ensure Linux VM sizes and configuration options are presented with equal prominence and detail as Windows options.
  • Provide links to Linux-specific documentation (e.g., Azure Linux VM images, configuration best practices) alongside Windows links.
  • Include example pool create event bodies for both Windows and Linux pools to illustrate parity.
  • Clarify in notes and tables which options are applicable to Linux, and provide guidance for Linux users where options differ.
GitHub Create Pull Request
Batch Migrate Azure Batch pools to the simplified compute node communication model ...ified-compute-node-communication-model-migration-guide.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page references Windows-specific tools (RDP) before Linux equivalents (SSH) and does not provide any OS-specific examples or guidance for either platform. The mention of agent binaries distinguishes between Windows (.exe) and Linux, but does not provide parity in examples or troubleshooting steps for Linux users. There is a subtle Windows-first ordering in connectivity instructions and tool naming.
Recommendations
  • Provide explicit examples for both Windows and Linux environments when discussing connectivity (e.g., show both RDP and SSH commands or configuration steps).
  • When mentioning agent binaries, clarify usage or troubleshooting for both platforms, not just naming conventions.
  • Ensure that Linux tools and patterns (such as SSH, Linux agent management, firewall configuration) are mentioned with equal prominence and detail as Windows equivalents.
  • Consider adding a dedicated section for platform-specific migration steps or FAQs, addressing common Linux scenarios.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents both Azure CLI and PowerShell methods for migrating Batch pools, but PowerShell (a Windows-centric tool) is given as the only alternative automation method after CLI, with no mention of Bash, Linux shell scripting, or cross-platform SDKs. PowerShell examples are provided in detail, while Linux-specific automation (e.g., Bash scripts) is absent. The CLI examples use Ubuntu images, but the automation tooling guidance is Windows-first, and PowerShell is highlighted before any Linux-native alternatives.
Recommendations
  • Add explicit Bash or shell script examples for Linux users, especially for automation tasks.
  • Mention cross-platform SDKs (e.g., Python, .NET, Java) as automation alternatives alongside PowerShell.
  • Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
  • If PowerShell is presented, also provide equivalent Bash or shell script snippets for parity.
  • Add troubleshooting and validation steps using Linux-native tools (e.g., jq, curl) where appropriate.
GitHub Create Pull Request
Batch Associate Azure Batch accounts with network security perimeter ...blob/main/articles/batch/network-security-perimeter.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias by listing PowerShell as a primary automation option before Azure CLI, and by providing detailed PowerShell examples alongside Azure CLI. There are no explicit Linux shell (bash) examples, nor are Linux-specific patterns or tools mentioned. The use of PowerShell may implicitly favor Windows users, as PowerShell is the default shell on Windows, while bash is more common on Linux. The Azure portal instructions are platform-neutral, but the scripting examples do not address Linux users directly.
Recommendations
  • Add bash shell examples for all CLI commands, showing usage in a typical Linux environment.
  • Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows, and provide any platform-specific notes if needed.
  • Where PowerShell is used, clarify that PowerShell Core is cross-platform, or provide equivalent bash scripts for Linux users.
  • Consider listing Azure CLI (bash) instructions before PowerShell, or present both side-by-side to avoid implicit prioritization.
  • Include troubleshooting or environment setup notes for Linux users, such as installing Azure CLI or configuring authentication.
GitHub Create Pull Request
Batch Configure managed identities in Batch pools ...ocs/blob/main/articles/batch/managed-identity-pools.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias. In the section on retrieving managed identity tokens within Batch nodes, the Windows/PowerShell example is presented before the Linux/Bash equivalent. Additionally, PowerShell is mentioned explicitly as the scripting tool for Windows, while Bash is used for Linux. However, both examples are present, and the rest of the documentation generally maintains cross-platform parity, including references to both Windows and Linux in pool creation and configuration steps.
Recommendations
  • Present Linux and Windows examples side-by-side or alternate which is shown first to avoid implicit prioritization.
  • Explicitly mention that both Windows and Linux nodes are supported throughout the documentation, especially in code and script examples.
  • Where possible, provide examples using cross-platform tools (e.g., Azure CLI) before platform-specific tools like PowerShell.
  • Include a table or section summarizing equivalent commands for both Windows and Linux to improve clarity for all users.
GitHub Create Pull Request
Batch Quickstart: Create an Azure Batch account using Terraform ...ocs/blob/main/articles/batch/quick-create-terraform.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
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 verifying results, but the PowerShell examples are given equal prominence and use Windows-specific syntax (e.g., `$variable=$(...)`), which is not portable to Linux/macOS. There is no explicit mention of Linux shell alternatives for PowerShell commands, and PowerShell is a Windows-centric tool. The documentation does not clarify which commands are cross-platform or provide bash/zsh equivalents for PowerShell-specific steps.
Recommendations
  • Clearly indicate which commands are cross-platform and which are Windows-specific.
  • For every PowerShell example, provide an equivalent bash/zsh (Linux/macOS) command if possible.
  • Note that Azure CLI is available on all platforms and recommend it as the default for cross-platform usage.
  • If PowerShell is mentioned, clarify that it is available on Linux/macOS, but provide bash syntax for variable assignment and command execution.
  • Add a section or callout for Linux/macOS users, highlighting any differences or additional steps required.
GitHub Create Pull Request
Batch Create a simplified node communication pool without public IP addresses ...tch/simplified-node-communication-pool-no-public-ip.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides troubleshooting commands for both Windows and Linux, but the Windows PowerShell example (Test-NetConnection) is listed first, and the command is more detailed. The Linux example (nc) is present but less emphasized. There are no other explicit Windows-only tools or patterns, and the rest of the documentation is platform-neutral, focusing on REST API, ARM templates, and Azure portal workflows.
Recommendations
  • Present Linux and Windows troubleshooting commands with equal detail and prominence, possibly side-by-side.
  • Expand Linux examples to match the verbosity and explanation given to Windows commands (e.g., explain nc output, add options for more detailed diagnostics).
  • Where possible, provide Bash/CLI equivalents for any PowerShell scripts or commands.
  • Consider listing Linux commands first or in parallel to avoid implicit prioritization of Windows.
  • Explicitly mention that all steps (portal, REST API, ARM templates) are cross-platform unless otherwise noted.
GitHub Create Pull Request
Batch Provision a pool in a virtual network ...docs/blob/main/articles/batch/batch-virtual-network.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page provides some evidence of Windows bias. In several places, Windows tools and patterns (such as RDP and port 3389) are mentioned before their Linux equivalents (SSH and port 22), and there are no explicit Linux-specific examples or instructions. The documentation does not provide parity in examples or guidance for Linux users, such as showing how to use Linux tools or command-line instructions for provisioning or managing Batch pools in a virtual network.
Recommendations
  • Present Linux and Windows options equally, listing SSH (port 22) before or alongside RDP (port 3389) when discussing remote access.
  • Include explicit Linux-focused examples, such as using Azure CLI or Bash scripts, for creating and managing Batch pools in a virtual network.
  • Add guidance for Linux users on configuring NSG rules, troubleshooting, and remote access, including references to Linux-specific tools and workflows.
  • Where screenshots or UI instructions are given, provide CLI alternatives that work on Linux systems.
  • Review and update terminology to avoid Windows-first ordering, ensuring Linux and cross-platform users are equally supported.
GitHub Create Pull Request
Batch Associate Azure Batch accounts with network security perimeter ...blob/main/articles/batch/network-security-perimeter.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
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 Azure Batch accounts with a network security perimeter using the Azure portal, PowerShell, and Azure CLI. PowerShell examples are given in detail and are presented before Azure CLI examples, which may indicate a Windows-first and PowerShell-heavy bias. There are no explicit Linux-specific shell examples (e.g., Bash scripts), nor is there mention of Linux tools or patterns. The CLI examples are generic and cross-platform, but the ordering and emphasis on PowerShell may signal a preference for Windows environments.
Recommendations
  • Provide Bash shell script examples alongside PowerShell, especially for steps involving Azure CLI.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide any platform-specific notes if needed.
  • Consider reordering the examples so that Azure CLI (cross-platform) instructions appear before PowerShell (Windows-centric) instructions.
  • Add notes or links for Linux users regarding prerequisites or environment setup for Azure CLI.
  • If there are any platform-specific behaviors or limitations, document them clearly for both Windows and Linux users.
GitHub Create Pull Request
Batch Move an Azure Batch account to another region ...cs/azure-docs/blob/main/articles/batch/account-move.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
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 (a web interface) for all steps, with no mention of command-line alternatives. While this avoids explicit Windows-only tools like PowerShell, it implicitly favors Windows users by omitting Linux-friendly CLI examples (such as Azure CLI or ARM template deployment via bash). There are no references to Linux tools, shell commands, or cross-platform automation patterns, and all instructions are GUI-based, which is more commonly associated with Windows workflows.
Recommendations
  • Add examples for moving a Batch account using Azure CLI commands, which work on both Windows and Linux.
  • Include instructions for exporting, modifying, and deploying ARM templates via command-line (e.g., using Bash or PowerShell), and present these alternatives alongside or before portal-based steps.
  • Reference automation options such as scripting with Azure CLI or PowerShell, and clarify that both are available cross-platform.
  • Explicitly mention that all steps can be performed on Linux, macOS, and Windows, and provide links to relevant CLI documentation.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page generally addresses both Windows and Linux Batch pools, but in the FAQ section, the link to Windows documentation is listed before Linux, and there are no concrete command-line examples for either platform. Linux-specific instructions are less detailed, and no Linux shell commands or code snippets are provided for certificate management tasks, while Windows is referenced first in cross-platform documentation links.
Recommendations
  • Provide explicit Linux shell command examples for certificate management tasks, such as copying certificates, adjusting file permissions, and accessing certificate stores.
  • Ensure Linux documentation links are listed alongside or before Windows links to avoid perceived prioritization.
  • Include sample scripts for both Windows (PowerShell) and Linux (Bash) in migration scenarios.
  • Clarify any platform-specific differences in the migration process with side-by-side examples.
  • Add troubleshooting tips for common Linux-specific issues, such as permissions and environment variable changes.
GitHub Create Pull Request
← Previous Page 13 of 18 Next →