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 26-50 of 436 flagged pages
Batch Storage and data movement for rendering ...rticles/batch/batch-rendering-storage-data-movement.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides more detailed examples and instructions for Windows environments, especially for mounting Azure Files shares and copying files with azcopy. Windows-specific tools and commands (cmdkey, net use) are shown with explicit examples, while equivalent Linux instructions (e.g., mounting Azure Files via SMB on Linux) are missing. The azcopy examples use Windows-style syntax and parameters, and Linux equivalents are not provided. The Azure Files section is focused on Windows, with no mention of Linux mounting procedures or examples.
Recommendations
  • Add explicit Linux examples for mounting Azure Files shares (e.g., using mount.cifs or SMB on Linux).
  • Provide azcopy command examples using Linux syntax and parameters, including shell usage.
  • Include Linux equivalents for Windows-specific tools (e.g., alternatives to cmdkey and net use for credential management and mounting).
  • Ensure that instructions and examples for both platforms are presented in parallel, or at least mention Linux options where Windows tools are discussed.
  • Add sample job/task configuration snippets for Linux environments, similar to the detailed Windows examples.
GitHub Create Pull Request
Batch Create task dependencies to run tasks ...cs/blob/main/articles/batch/batch-task-dependencies.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias by exclusively providing examples that use Windows command-line tools (cmd.exe, echo), with no mention or examples for Linux shells or commands. All code snippets use Windows-specific patterns, and there is no guidance for users running Batch tasks on Linux nodes. The documentation implicitly assumes a Windows environment, omitting Linux equivalents and cross-platform considerations.
Recommendations
  • Add Linux shell examples (e.g., bash, sh) alongside Windows cmd.exe examples for all code snippets.
  • Explicitly mention that Azure Batch supports both Windows and Linux compute nodes, and clarify any platform-specific behaviors.
  • Provide guidance on writing cross-platform tasks, including how to specify commands for Linux nodes (e.g., using '/bin/bash -c' instead of 'cmd.exe /c').
  • Include notes or tables comparing Windows and Linux task configuration patterns.
  • Reference documentation or samples for Batch usage on Linux, and link to relevant resources.
GitHub Create Pull Request
Batch Provision a pool with Auto OS Upgrade ...-docs/blob/main/articles/batch/batch-upgrade-policy.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias by exclusively providing Windows-based examples in both the REST API and SDK (C#) sections. The image references, node agent SKUs, and configuration properties are all tailored to Windows (e.g., 'MicrosoftWindowsServer', 'batch.node.windows amd64', 'windowsConfiguration'). There are no Linux equivalents or examples, nor is there mention of Linux-specific configuration options or agent SKUs. Windows terminology and tools are used throughout, with no parity for Linux users.
Recommendations
  • Add Linux-based examples for both REST API and SDK sections, including image references (e.g., 'Canonical', 'UbuntuServer'), node agent SKUs (e.g., 'batch.node.ubuntu 20.04'), and relevant configuration properties.
  • Include documentation and guidance for configuring pools with Linux OS images, such as specifying 'linuxConfiguration' in the pool definition.
  • Mention Linux-specific considerations, such as patching and upgrade mechanisms, and clarify any differences in upgrade behavior between Windows and Linux pools.
  • Ensure that both Windows and Linux options are presented side-by-side or in parallel, rather than Windows-first or Windows-only.
  • Review and update FAQs and requirements to include Linux scenarios and terminology.
GitHub Create Pull Request
Batch Run tasks under user accounts ...e-docs/blob/main/articles/batch/batch-user-accounts.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits several forms of Windows bias. Windows-specific tools and APIs (such as Windows Data Protection API and RDP) are mentioned before or more prominently than their Linux equivalents. Code examples often use Windows-centric commands (e.g., 'cmd /c echo hello') and the .NET example for named user accounts is explicitly labeled as 'Windows' and appears before the Linux equivalent. There is a lack of parity in examples for Linux-specific scenarios (e.g., no Linux shell command examples for running tasks, limited discussion of Linux security tools). Windows terminology and patterns are introduced first or exclusively in several sections.
Recommendations
  • Provide Linux shell command examples (e.g., using bash/sh) alongside Windows 'cmd' examples for running tasks.
  • Mention Linux tools and APIs (such as GnuPG, OpenSSL, or native Linux file permissions) where Windows-specific tools like DPAPI are referenced.
  • Ensure that Linux and Windows examples are presented with equal prominence and in parallel, rather than Windows first.
  • Include more Linux-specific scenarios and best practices, such as SELinux/AppArmor, SSH key management, and Linux file sharing.
  • Where possible, use cross-platform language in code samples and documentation, or explicitly note differences between platforms.
  • Add explicit guidance for configuring user accounts and permissions on Linux, including security considerations unique to Linux environments.
GitHub Create Pull Request
Batch Best practices .../azure-docs/blob/main/articles/batch/best-practices.md
High Priority View Details →
Scanned: 2026-01-12 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 mentioned before or more prominently than Linux equivalents in several places, such as for discovering image EOL dates and preparing data disks. Windows examples (PowerShell) are provided in detail, while Linux examples are less frequent or less detailed. Some guidance is Windows-centric (directory junctions, Windows Services, user/group names) and appears before or in more detail than Linux alternatives. In some cases, Linux examples or commands are missing or less emphasized.
Recommendations
  • Ensure that Linux examples and tools (e.g., Bash, CLI, system utilities) are provided alongside Windows/PowerShell examples, with equal detail and prominence.
  • When mentioning tools for tasks (e.g., listing supported images/SKUs), list Azure CLI and Linux-native methods before or alongside PowerShell, not after.
  • Provide Linux-specific troubleshooting and best practice sections where Windows-specific advice is given (e.g., file cleanup, service management).
  • Avoid Windows-first ordering in lists and examples; alternate or group by OS where possible.
  • Where Windows-specific artifacts (users/groups, directory junctions) are discussed, ensure Linux equivalents are also described.
  • Expand Linux guidance for areas like disk preparation, log collection, and service management to match the depth of Windows coverage.
GitHub Create Pull Request
Batch Use extensions with Batch pools ...ocs/blob/main/articles/batch/create-pool-extensions.md
High Priority View Details →
Scanned: 2026-01-12 00:00
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 listing supported extensions and example payloads for both platforms. However, there is a slight bias toward Windows in the number of Windows-only extensions listed (e.g., Antimalware, Diagnostics, DSC, multiple GPU drivers), and some extension types (like Diagnostics and DSC) are only available for Windows. The troubleshooting section does not provide Linux-specific log file locations or commands, and there are no Linux shell or command-line examples (e.g., Bash, SSH) for interacting with extensions or troubleshooting, whereas Windows tools and patterns (such as certificateStoreLocation: LocalMachine) are mentioned. The Application Health section describes a generic HTTP server setup but does not provide Linux-specific guidance or examples.
Recommendations
  • Add Linux-specific troubleshooting steps, including log file locations and example commands for viewing logs (e.g., using journalctl, tail, or cat).
  • Provide shell/Bash examples for interacting with extensions, retrieving status, and troubleshooting on Linux nodes.
  • Ensure that extension documentation links are balanced, and highlight Linux equivalents where only Windows tools are mentioned (e.g., for Diagnostics, DSC, Antimalware).
  • If certain extensions are Windows-only, explicitly state this and suggest Linux alternatives or workarounds.
  • Include examples of using SSH to connect to Linux nodes for troubleshooting, alongside any Windows RDP/PowerShell guidance.
GitHub Create Pull Request
Batch Jobs and tasks in Azure Batch .../azure-docs/blob/main/articles/batch/jobs-and-tasks.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation generally presents Windows-specific tools and patterns before or more prominently than Linux equivalents. For example, in the section about invoking shells for task command lines, the Windows example (cmd.exe) is shown first, and in the start task section, Windows-specific tools like 'robocopy', 'MSI', and 'setup.exe' are mentioned exclusively. There is also a lack of parity in tool examples for Linux (e.g., no mention of 'cp', 'tar', or 'sh' for similar operations), and Windows environment variable syntax is listed before Linux. While Linux is acknowledged, the documentation tends to default to Windows-first explanations and tool references.
Recommendations
  • Provide Linux tool examples alongside Windows ones, such as mentioning 'cp' or 'rsync' in addition to 'robocopy', and '.sh' scripts in addition to '.exe' installers.
  • Alternate the order of Windows and Linux examples to avoid always listing Windows first.
  • Include explicit Linux shell command examples (e.g., using 'tar' for unzipping archives) where only Windows tools are currently mentioned.
  • When describing environment variable syntax, present both Windows (%VAR%) and Linux ($VAR) forms together or alternate their order.
  • Where possible, use cross-platform language and avoid assuming Windows as the default operating system.
GitHub Create Pull Request
Batch Provision a pool in a virtual network ...docs/blob/main/articles/batch/batch-virtual-network.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates subtle Windows bias. It references Windows-specific concepts and tools (e.g., RDP, port 3389) before Linux equivalents (SSH, port 22) in several places, and mentions Azure PowerShell as a primary method for creating resources before the Azure CLI. There are no explicit Linux command-line examples or references to Linux-native tooling, and remote access instructions focus on Windows (RDP) before Linux (SSH).
Recommendations
  • Present Linux and Windows examples side-by-side, or alternate which is listed first (e.g., mention SSH/port 22 before RDP/port 3389 in some sections).
  • Include explicit Azure CLI examples for all resource creation steps, not just mention it as an option.
  • Add Linux-specific guidance for remote access, such as SSH key setup and firewall configuration.
  • Reference Linux-native tools and patterns (e.g., bash scripting, cloud-init) where appropriate.
  • Ensure screenshots and UI instructions are platform-neutral or provide both Windows and Linux perspectives if relevant.
GitHub Create Pull Request
Batch Use certificates and securely access Azure Key Vault with Batch ...lob/main/articles/batch/credential-access-key-vault.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows and PowerShell bias. All code examples are provided exclusively in PowerShell, with no equivalent Bash, CLI, or Linux-native instructions. Windows-specific tools and patterns (such as .msi installers, Windows Management Framework, and PowerShell cmdlets) are referenced throughout, and there is no guidance for Linux users on how to generate certificates, install required libraries, or access Azure Key Vault from Linux-based Batch nodes.
Recommendations
  • Provide equivalent Bash/Azure CLI examples for certificate creation, service principal setup, and Key Vault access.
  • Include instructions for installing required Azure libraries (e.g., Azure CLI, Azure SDK for Python) on Linux Batch nodes.
  • Mention Linux-compatible certificate management tools (e.g., openssl) alongside PowerShell alternatives.
  • Clarify any differences in workflow or prerequisites for Linux nodes, such as file paths, environment setup, and authentication methods.
  • Ensure that Linux examples are presented with equal prominence and detail as Windows/PowerShell examples.
GitHub Create Pull Request
Batch Manage private endpoint connections with Azure Batch accounts .../articles/batch/manage-private-endpoint-connections.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation presents management operations for Azure Batch private endpoint connections. It lists Az PowerShell (Windows-centric) examples before Azure CLI (cross-platform), and provides detailed PowerShell commands, reinforcing a Windows-first and PowerShell-heavy bias. The page references Windows tools and patterns, with no mention of Linux-specific considerations or shell environments.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples to emphasize cross-platform support.
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and provide example shell environments (e.g., bash, zsh).
  • Include notes or sections for Linux/macOS users, such as environment setup or command differences if any.
  • Avoid implying PowerShell is the default or preferred method; clarify parity between tools.
  • Consider adding troubleshooting or tips relevant to Linux users (e.g., permissions, shell variable syntax).
GitHub Create Pull Request
Batch Monitor Batch with Azure Application Insights ...ob/main/articles/batch/monitor-application-insights.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias. All examples and tooling references are Windows-centric, including exclusive use of Visual Studio, PowerShell commands, Windows-specific NuGet packages (Microsoft.ApplicationInsights.WindowsServer), and Windows VM images for Azure Batch pools. There is no mention of Linux equivalents, nor are any Linux or cross-platform instructions, code samples, or troubleshooting steps provided.
Recommendations
  • Add Linux-specific prerequisites, such as instructions for using VS Code, JetBrains Rider, or .NET CLI on Linux.
  • Provide Linux-friendly package installation examples (e.g., using dotnet CLI: 'dotnet add package Microsoft.ApplicationInsights') instead of only PowerShell/NuGet Package Manager.
  • Include guidance for running Azure Batch pools with Linux VM images, and update code/configuration samples to show how to configure Application Insights on Linux nodes.
  • Mention cross-platform Application Insights packages and clarify which features/packages are Windows-only.
  • Add troubleshooting and deployment notes for Linux environments, including file staging, environment variables, and process management.
  • Ensure screenshots and portal instructions are not Windows-specific and clarify any OS-dependent behaviors.
GitHub Create Pull Request
Batch Plan to manage costs for Azure Batch ...-docs/blob/main/articles/batch/plan-to-manage-costs.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific resources and patterns first (e.g., linking to Windows VM pricing before Linux), mentioning Windows tools (such as Windows OS licensing), and omitting explicit Linux examples or cost considerations. There is no discussion of Linux-specific VM options, licensing differences, or cost-saving strategies unique to Linux workloads.
Recommendations
  • Include explicit examples and cost considerations for Linux-based Batch workloads, such as referencing Linux VM pricing and licensing differences.
  • Present both Windows and Linux options in parallel when discussing VM selection, cost estimation, and licensing impacts.
  • Add links to Linux VM documentation and highlight cost-saving strategies specific to Linux (e.g., no OS licensing fees, availability of certain VM sizes).
  • Ensure screenshots and walkthroughs demonstrate both Windows and Linux scenarios where applicable.
GitHub Create Pull Request
Batch Quickstart: Use the Azure portal to create a Batch account and run a job ...e-docs/blob/main/articles/batch/quick-create-portal.md
High Priority View Details →
Scanned: 2026-01-12 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 Windows bias by exclusively providing instructions and examples for creating pools of Windows compute nodes (specifically Windows Server 2019), and using Windows command-line tools (cmd, set, timeout) in task command lines. There are no examples or guidance for creating Linux-based pools or running Linux shell commands, nor is there mention of Linux options or parity.
Recommendations
  • Include instructions and examples for creating pools with Linux-based compute nodes, such as Ubuntu or CentOS images.
  • Provide Linux shell command examples (e.g., using bash, echo, sleep) alongside Windows cmd examples for task command lines.
  • Explicitly mention both Windows and Linux options when describing pool creation, and clarify how to select the OS type.
  • Add notes or sections highlighting differences in environment variables, command syntax, and output handling between Windows and Linux nodes.
  • Ensure screenshots and walkthroughs show both Windows and Linux pool creation and task execution where applicable.
GitHub Create Pull Request
Batch Monitor Azure Batch ...s/azure-docs/blob/main/articles/batch/monitor-batch.md
High Priority View Details →
Scanned: 2026-01-12 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 Windows bias by primarily referencing Windows-centric tools and patterns, such as the Batch .NET library and Application Insights integration with .NET solutions. There are no Linux-specific examples, nor is there mention of Linux command-line tools or SDKs (e.g., Python, Java) for monitoring Azure Batch. The documentation references Batch Explorer and .NET code samples, but does not provide parity for Linux users or alternative cross-platform approaches.
Recommendations
  • Include examples using cross-platform SDKs such as Python, Java, or Node.js for monitoring Batch resources.
  • Provide sample scripts for accessing diagnostic logs using Linux tools (e.g., Azure CLI, Bash, curl, jq) alongside any PowerShell or .NET examples.
  • Mention and demonstrate how to integrate Application Insights or other monitoring solutions in non-.NET environments (e.g., Python, Java).
  • Clarify Batch Explorer's platform support and offer guidance for Linux users if available.
  • Ensure that references to monitoring tools and libraries are not exclusively Windows/.NET-centric, and provide links to equivalent Linux documentation or samples.
GitHub Create Pull Request
Batch Nodes and pools in Azure Batch ...azure-docs/blob/main/articles/batch/nodes-and-pools.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. Windows-specific tools and patterns (such as .exe, .cmd, .bat, and PowerShell scripts) are listed before Linux equivalents when discussing supported executables. Windows remote access (RDP) is mentioned before Linux (SSH). Container support examples reference Windows Server images first, with no explicit Linux container example. There are no concrete Linux shell script or tool examples, and Linux-specific instructions are generally referenced via links rather than described inline.
Recommendations
  • List Linux script types (e.g., shell scripts, Python) before or alongside Windows types when discussing supported executables.
  • Provide explicit Linux examples (e.g., bash scripts, SSH commands) in relevant sections, not just links.
  • When discussing remote access, mention SSH for Linux first or equally with RDP for Windows.
  • Include Linux container pool creation examples and reference popular Linux container images.
  • Ensure parity in describing both Windows and Linux node setup, configuration, and troubleshooting steps.
  • Where possible, balance references to Windows and Linux tools (e.g., PowerShell vs. bash) and avoid defaulting to Windows-first language.
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
High Priority View Details →
Scanned: 2026-01-12 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 bias towards Windows by exclusively using Windows Server for compute nodes, Windows command-line tools (cmd, type), and providing examples that only work on Windows. There are no Linux equivalents or examples, and Windows is mentioned first and exclusively in several key steps.
Recommendations
  • Include examples for creating pools with Linux VM images, and explain how to select Linux Marketplace images in the pool configuration.
  • Provide sample task command lines using Linux shell commands (e.g., 'cat' instead of 'type'), and show how to specify them in the .NET API.
  • Clarify that Batch supports both Windows and Linux nodes, and discuss differences in configuration and scripting.
  • Add instructions for building and running the app on Linux (e.g., using dotnet CLI on Linux, or VS Code), and mention cross-platform development explicitly.
  • Where Windows tools or patterns are mentioned, provide Linux equivalents side-by-side.
GitHub Create Pull Request
Batch Batch security and compliance best practices ...cs/blob/main/articles/batch/security-best-practices.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits mild Windows bias. Windows-specific tools and resources (such as PowerShell and Windows registry settings for TLS) are mentioned before or more prominently than their Linux equivalents. Examples and links for discovering supported images use PowerShell first, with Azure CLI mentioned second. The section on OS-level TLS settings is Windows-centric, with no Linux-specific guidance. There are no explicit Linux command-line examples or references to Linux security configuration patterns, and Windows terminology (RDP, registry) appears more frequently than SSH or Linux equivalents.
Recommendations
  • Provide Linux-first or parallel examples where PowerShell is mentioned, such as showing both Azure CLI and PowerShell commands for listing supported images.
  • Add Linux-specific guidance for OS-level security configuration, such as instructions for configuring TLS/cipher suites on supported Linux distributions.
  • Ensure that references to remote access (RDP/SSH) are balanced, with equal detail for both Windows (RDP) and Linux (SSH) scenarios.
  • Include links to Linux documentation (e.g., OpenSSL, SSH hardening, Linux disk encryption) where Windows-specific resources are provided.
  • Review terminology to ensure Linux and Windows are treated equally throughout, and avoid defaulting to Windows-first phrasing.
GitHub Create Pull Request
Batch Tutorial: Run a parallel workload using the .NET API ...s/blob/main/articles/batch/tutorial-parallel-dotnet.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a strong Windows bias: it exclusively uses Windows VM images for compute pools, references only the Windows build of ffmpeg, and provides command-line examples using Windows syntax (cmd.exe). There are no examples or instructions for using Linux VM images, Linux-compatible ffmpeg builds, or Bash command lines, despite Azure Batch supporting Linux pools and .NET being cross-platform.
Recommendations
  • Add explicit instructions and code samples for creating Linux-based pools, including the use of Ubuntu or other supported Linux images.
  • Provide guidance on downloading and packaging the Linux build of ffmpeg, and reference its usage in the application package step.
  • Include alternative command-line examples using Bash syntax for running ffmpeg on Linux nodes.
  • Mention the differences in environment variables and file paths between Windows and Linux nodes, and how to handle them in cross-platform .NET code.
  • Update screenshots and walkthroughs to show both Windows and Linux pool/job/task creation and monitoring.
  • Clarify that Azure Batch supports both Windows and Linux, and encourage users to select the platform that best fits their workload.
GitHub Create Pull Request
Batch Mount a virtual file system on a pool ...re-docs/blob/main/articles/batch/virtual-file-mount.md
High Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is used as the primary scripting language for both Windows and Linux examples, even though Bash is more common for Linux. Windows-specific tools and patterns (e.g., 'cmdkey', 'net use', RDP) are described in detail, often before their Linux equivalents (e.g., 'cifs-utils', SSH). Troubleshooting and manual mounting instructions are more elaborate for Windows, with direct references to Windows tools and workflows. Some Linux-specific details, such as native Bash commands for mounting or troubleshooting, are missing or underrepresented.
Recommendations
  • Provide native Bash examples for Linux, especially for mounting and troubleshooting, rather than relying solely on PowerShell.
  • Present Linux and Windows instructions in parallel, ensuring equal detail and visibility for both platforms.
  • Include Linux-first or Linux-specific troubleshooting steps, such as using 'mount', 'df', 'lsblk', and examining system logs.
  • Reference Linux tools (e.g., 'mount', 'umount', 'journalctl') and workflows as prominently as Windows tools.
  • Clarify when PowerShell is required on Linux, and offer alternative Bash workflows where possible.
  • Ensure external links and references are balanced between Windows and Linux resources.
GitHub Create Pull Request
Batch Deploy application packages to compute nodes ...blob/main/articles/batch/batch-application-packages.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a Windows bias in several ways. Code examples for deploying and running application packages on compute nodes use Windows-specific constructs (e.g., 'cmd /c', Windows environment variable syntax, and Windows image references), with no equivalent Linux shell or environment variable usage shown. The documentation references Windows VM images first and exclusively in code, and the command-line examples are tailored to Windows (e.g., launching .exe files with Windows paths). Linux-specific instructions are limited to brief notes about environment variable formatting, without concrete Linux shell or application invocation examples. There is no demonstration of how to use Bash, Linux VM images, or Linux application binaries in the context of Azure Batch application packages.
Recommendations
  • Provide parallel Linux examples for all code snippets, including pool creation (using a Linux VM image), task command lines (using Bash syntax), and application execution (e.g., running a .sh or Linux binary).
  • Show how to reference environment variables in Bash (e.g., $AZ_BATCH_APP_PACKAGE_applicationid_version) and how to launch applications on Linux nodes.
  • When discussing application ID requirements, present Linux and Windows constraints side by side, and clarify differences.
  • Avoid presenting Windows examples first or exclusively; alternate or combine Windows and Linux instructions to ensure parity.
  • Include notes about differences in file paths, permissions, and application packaging for Linux nodes.
GitHub Create Pull Request
Batch Create a Batch pool with specified public IP addresses ...docs/blob/main/articles/batch/create-pool-public-ip.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation page demonstrates Windows bias by listing Azure PowerShell as a method for creating public IP addresses alongside Azure CLI and the portal, with PowerShell mentioned last but still present. There are no explicit Linux-specific tools or shell examples (e.g., Bash, cloud-init), and the only command-line examples provided are generic (REST API and Azure CLI), but the inclusion of PowerShell and lack of Linux-specific alternatives or parity in scripting tools suggests a subtle bias toward Windows users and workflows.
Recommendations
  • Add explicit Linux shell (Bash) examples for creating public IP addresses using Azure CLI.
  • Mention and provide parity for Linux automation tools (e.g., cloud-init, shell scripts) where relevant.
  • Clarify that Azure CLI is cross-platform and provide example commands for both Windows (PowerShell) and Linux (Bash) environments.
  • Consider listing Azure CLI before PowerShell to emphasize cross-platform support.
  • If PowerShell is mentioned, also mention Bash or other Linux-native tools to balance the presentation.
GitHub Create Pull Request
Batch Use certificates and securely access Azure Key Vault with Batch ...lob/main/articles/batch/credential-access-key-vault.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias by exclusively providing PowerShell commands and workflows, referencing Windows-specific tools (such as .msi installers and Windows Management Framework), and omitting any Linux or cross-platform command-line examples. There are no instructions or code samples for Linux users, and all automation is shown using Windows-centric patterns.
Recommendations
  • Provide equivalent Bash/CLI examples for certificate creation, service principal setup, and Key Vault access using Azure CLI and OpenSSL.
  • Include instructions for installing required libraries/tools on Linux nodes (e.g., Azure CLI, Python SDKs).
  • Mention Linux-compatible certificate storage locations and how to assign/import certificates on Linux Batch nodes.
  • Demonstrate how to authenticate and access Key Vault from Linux Batch nodes using cross-platform tools.
  • Reorder or parallelize examples so Windows and Linux instructions are presented together, ensuring parity.
GitHub Create Pull Request
Batch Use ephemeral OS disk nodes for Azure Batch pools ...b/main/articles/batch/create-pool-ephemeral-os-disk.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates Windows bias by referencing PowerShell as the primary method for programmatically querying VM capabilities (specifically 'EphemeralOSDiskSupported'), without mentioning Linux alternatives such as Azure CLI, Bash, or REST API. The only tool-specific example provided is PowerShell, and it is referenced before any cross-platform or Linux-native methods. No explicit Linux command-line examples are given for the same task.
Recommendations
  • Add Azure CLI and Bash examples for querying VM capabilities, alongside PowerShell.
  • Mention cross-platform tools (e.g., Azure CLI, REST API) before or alongside Windows-specific tools.
  • Include guidance for Linux users on how to perform the same operations, ensuring parity in instructions and tooling.
  • Clarify that PowerShell is available cross-platform, but also provide native Linux shell examples for completeness.
GitHub Create Pull Request
Batch Use Microsoft Entra ID to authenticate Batch Management solutions .../blob/main/articles/batch/batch-aad-auth-management.md
High Priority View Details →
Scanned: 2026-01-11 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 Windows bias by exclusively referencing Windows-centric tools (Azure portal, .NET library, C# code samples) and patterns. All code examples are in C#, with no mention of Linux-specific workflows, command-line registration, or cross-platform alternatives. The use of the Azure portal and references to 'Windows Azure Service Management API' further reinforce the Windows-first approach. There are no Linux or open-source tool examples, nor is there guidance for developers working outside the Windows/.NET ecosystem.
Recommendations
  • Include examples using cross-platform SDKs (e.g., Python, Java, Node.js) alongside .NET/C#.
  • Provide instructions for registering applications with Microsoft Entra ID using CLI tools (e.g., Azure CLI, which works on Linux, macOS, and Windows), not just the Azure portal.
  • Add sample code for authentication using MSAL in Linux-friendly languages and environments.
  • Mention and demonstrate how to use the Batch Management REST API directly, which is platform-agnostic.
  • Clarify that the process is not limited to Windows and .NET, and link to documentation for Linux and other platforms.
GitHub Create Pull Request
Batch Create a Batch account in the Azure portal ...lob/main/articles/batch/batch-account-create-portal.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily through the exclusive use of PowerShell commands for required configuration steps (e.g., accepting marketplace terms), mentioning PowerShell before Azure CLI, and not providing equivalent Linux/bash examples. The 'Other Batch account management options' section lists PowerShell cmdlets before Azure CLI, and there are no bash or Linux-specific command examples for key operations. This may hinder Linux users who prefer bash or CLI workflows.
Recommendations
  • Provide Azure CLI equivalents for all PowerShell command examples, especially for critical steps like accepting marketplace terms.
  • When listing management tools, mention Azure CLI before or alongside PowerShell to avoid Windows-first ordering.
  • Include bash/Linux shell command examples where applicable, and clarify cross-platform compatibility for all steps.
  • Add explicit notes or sections for Linux users, ensuring parity in instructions and troubleshooting.
  • Review all referenced links and ensure Linux/CLI examples are present and easy to find.
GitHub Create Pull Request
← Previous Page 2 of 18 Next →