Batch
228
Total Pages
164
Linux-Friendly Pages
64
Pages with Bias
28.1%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
156 issues found
Showing 1-25 of 156 flagged pages
Batch
Use multi-instance tasks to run MPI applications
...tDocs/azure-docs/blob/main/articles/batch/batch-mpi.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias: all code samples, walkthroughs, and tooling references are centered around Windows, MS-MPI, and Visual Studio. Linux alternatives (Intel MPI, Python) are mentioned only in passing, and no Linux-specific code samples or setup instructions are provided. The reader is guided through a complete Windows workflow, while Linux users are left to infer or seek external resources.
Recommendations
- Add parallel Linux-focused code samples using Intel MPI and Bash (or Python) for multi-instance tasks.
- Provide explicit instructions for creating pools with Linux VM images, including sample VirtualMachineConfiguration for Ubuntu or CentOS.
- Show how to install Intel MPI (or OpenMPI) on Linux nodes using a StartTask, with sample shell commands.
- Include Linux-specific coordination and application command examples (e.g., using mpiexec/mpirun in Bash).
- Reference Linux development tools (e.g., VS Code, gcc, Python) alongside Visual Studio.
- Reorder sections so Linux and Windows approaches are presented with equal prominence.
- Link to Linux sample repositories and provide step-by-step execution instructions for Linux users.
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 →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page is heavily biased toward Windows and PowerShell, with all code examples, certificate creation steps, and installation instructions using Windows-specific tools and PowerShell commands. There are no Linux or macOS equivalents provided for certificate generation, service principal creation, Key Vault access, or Azure CLI usage. The instructions for installing Azure PowerShell reference Windows Management Framework and MSI installers, which are not applicable to Linux/macOS environments.
Recommendations
- Provide equivalent examples using Azure CLI and/or Bash scripts for Linux/macOS users.
- Include instructions for generating certificates on Linux/macOS (e.g., using OpenSSL).
- Add steps for installing Azure PowerShell or Azure CLI on Linux/macOS nodes.
- Present cross-platform options side-by-side or clearly indicate platform-specific steps.
- Reference Linux/macOS documentation where relevant, especially for Batch pool setup and certificate assignment.
Batch
Monitor Batch with Azure Application Insights
...ob/main/articles/batch/monitor-application-insights.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. It exclusively references Windows tools (Visual Studio, WindowsServer VM images, cmd.exe), uses PowerShell for package installation, and only provides examples and instructions for Windows environments. There are no Linux/macOS equivalents or guidance for cross-platform scenarios, making it difficult for non-Windows users to follow or replicate the steps.
Recommendations
- Add instructions for installing Application Insights packages using cross-platform tools (e.g., dotnet CLI, NuGet CLI) instead of only PowerShell.
- Include examples for configuring and running Azure Batch pools with Linux VM images, and clarify any differences in Application Insights integration.
- Provide guidance for developing and deploying .NET applications on Linux/macOS, including alternative IDEs (e.g., VS Code) and build steps.
- Document how to run background telemetry processes on Linux nodes, including sample shell scripts and configuration.
- Ensure all code samples and configuration steps are platform-agnostic or provide parallel Linux/macOS instructions where necessary.
Batch
Use multi-instance tasks to run MPI applications
...tDocs/azure-docs/blob/main/articles/batch/batch-mpi.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias: all code samples and walkthroughs use Windows-specific tools (MS-MPI, cmd.exe), Windows VM images, and Batch .NET/C#. Linux alternatives (Intel MPI, Python) are mentioned only in passing, with no concrete examples or step-by-step guidance. The sample code, setup instructions, and troubleshooting are exclusively Windows/MS-MPI focused, leaving Linux users without actionable instructions.
Recommendations
- Add parallel Linux-focused code samples using Python and Intel MPI, including pool creation, StartTask for Intel MPI installation, and multi-instance task configuration.
- Provide step-by-step instructions for setting up a Linux pool, installing Intel MPI, and running an MPI application.
- Include equivalent Linux shell commands (bash) for coordination and application commands.
- Reference and link to Linux-specific sample repositories and walkthroughs as prominently as the Windows samples.
- Ensure that both Windows and Linux workflows are presented side-by-side or in separate, clearly labeled sections.
Batch
Use certificates and securely access Azure Key Vault with Batch
...lob/main/articles/batch/credential-access-key-vault.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page is heavily biased towards Windows and PowerShell. All code examples use PowerShell, and certificate creation is described only with Windows/PowerShell tools. Instructions for installing Azure PowerShell reference Windows Management Framework and MSI installers, with no mention of Linux or macOS equivalents. There are no Linux shell (bash/openssl/az CLI) examples or guidance for non-Windows users, making it difficult for Linux/macOS users to follow the steps.
Recommendations
- Add equivalent Linux/macOS instructions for certificate creation (e.g., using openssl).
- Provide az CLI or bash examples for service principal creation and Key Vault access.
- Include guidance for installing Azure CLI and PowerShell on Linux/macOS nodes.
- Explicitly mention cross-platform support and link to relevant Linux/macOS documentation.
- Reorder examples so that cross-platform or Linux instructions are presented alongside or before Windows-specific ones.
Batch
Monitor Batch with Azure Application Insights
...ob/main/articles/batch/monitor-application-insights.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. Windows-specific tools (Visual Studio, WindowsServer VM images, cmd, and WindowsServer NuGet packages) are referenced exclusively or before any Linux equivalents. All code and configuration examples assume a Windows environment, with no mention of Linux/macOS alternatives for development, deployment, or runtime. Package installation is shown only via PowerShell, and the VM pool configuration is Windows-only. There are no Linux/macOS instructions, examples, or troubleshooting notes.
Recommendations
- Add explicit instructions and examples for Linux/macOS environments, including development setup (e.g., VS Code, .NET CLI), package installation (dotnet CLI, apt, etc.), and runtime configuration.
- Provide Linux VM pool configuration examples (e.g., Ubuntu images) and show how to run Application Insights on Linux Batch nodes.
- Include cross-platform code snippets and clarify any OS-specific requirements or limitations.
- Mention and link to relevant Linux/macOS troubleshooting or documentation resources.
- Ensure parity in screenshots and portal instructions where OS differences exist.
Batch
Tutorial: Run a parallel workload using the .NET API
...s/blob/main/articles/batch/tutorial-parallel-dotnet.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Powershell Heavy
Summary
The documentation demonstrates a notable Windows bias throughout the tutorial. Windows-specific instructions, tools, and examples are presented exclusively or before any mention of Linux/macOS alternatives. The compute pool is configured with a Windows Server image only, and the ffmpeg application package referenced is the Windows build. The command line for running ffmpeg uses Windows-specific syntax (cmd /c and .exe), with no mention of how to adapt for Linux or macOS environments. There are no examples or guidance for using Linux VM images, Linux ffmpeg builds, or Bash command lines.
Recommendations
- Add explicit instructions and code samples for configuring Batch pools with Linux VM images (e.g., Ubuntu).
- Provide guidance on uploading and referencing Linux/macOS builds of ffmpeg as application packages.
- Include sample command lines for running ffmpeg on Linux (e.g., using Bash syntax and ffmpeg binary without .exe).
- Clarify how to adapt the .NET sample code and Batch task configuration for non-Windows environments.
- Present cross-platform examples side-by-side or indicate platform-specific steps clearly.
- Mention Linux/macOS prerequisites and tooling (e.g., Visual Studio Code, dotnet CLI on Linux).
Batch
Deploy application packages to compute nodes
...blob/main/articles/batch/batch-application-packages.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits Windows bias in several ways: all code examples are in C# and use Windows-centric constructs (e.g., 'cmd /c', Windows environment variable formats, Windows image references), with no Linux shell or cross-platform code samples. Windows node configuration and usage patterns are described first and in detail, while Linux equivalents are only briefly mentioned, often as afterthoughts. There is no example of deploying or running application packages on Linux nodes using Linux command lines or shell scripts. Windows-specific tools and patterns (e.g., 'cmd /c', Windows image references) are used exclusively in code samples.
Recommendations
- Provide equivalent Linux examples for deploying and running application packages, including shell script command lines (e.g., 'bash -c ...') and Linux image references.
- Include cross-platform code samples or highlight differences in API usage between Windows and Linux nodes.
- Document Linux-specific considerations (such as file paths, permissions, and environment variable usage) alongside Windows instructions.
- Avoid using Windows tools and patterns exclusively in examples; show parity by alternating or combining Windows and Linux scenarios.
- Add a section or table summarizing differences and best practices for both Windows and Linux compute nodes.
Batch
Copy applications and data to pool nodes
...ain/articles/batch/batch-applications-to-pool-nodes.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page exhibits Windows bias by referencing Windows-specific installation formats (.exe, .msi) and omitting Linux equivalents (such as .sh scripts or .deb/.rpm packages). There are no examples or mentions of Linux tools, patterns, or file formats, and Windows terminology appears first and exclusively in installation scenarios.
Recommendations
- Include Linux-specific examples, such as installing .sh scripts or .deb/.rpm packages using start tasks.
- Mention Linux tools and patterns (e.g., using bash scripts, apt/yum/zypper for package installation) alongside Windows examples.
- Provide parity in documentation by describing both Windows and Linux workflows for copying and installing applications and data.
- Avoid referencing only Windows file formats (.exe, .msi) and instead use generic terms or include Linux equivalents.
- Add explicit guidance for Linux users, such as how to set up permissions, run shell commands, or handle resource files on Linux nodes.
Batch
Azure Quickstart - Create a Batch account - Azure Resource Manager template
...docs/blob/main/articles/batch/quick-create-template.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by prioritizing the Azure portal (which is most commonly used on Windows) and referencing Azure PowerShell as a deployment method before mentioning Azure CLI or REST API. There are no explicit Linux or cross-platform command-line examples, and the links for further deployment methods point to PowerShell documentation first. No Linux-specific instructions or screenshots are provided.
Recommendations
- Add explicit Azure CLI examples for deploying the ARM template, including Linux/macOS terminal instructions.
- Reference Azure CLI before or alongside Azure PowerShell when listing deployment options.
- Include screenshots or instructions for using the Azure portal on Linux/macOS browsers, if relevant.
- Ensure links to deployment methods include both PowerShell and CLI documentation equally.
- Mention that all steps can be performed on Linux, macOS, and Windows, and clarify any platform-specific differences.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/accounts.md
...ftDocs/azure-docs/blob/main/articles/batch/accounts.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates Windows bias by referencing Windows-centric tools and patterns, such as the Azure portal and Batch Management .NET library, without mentioning Linux equivalents or cross-platform command-line options (e.g., Azure CLI, Azure PowerShell, REST API). No Linux-specific examples or guidance are provided for creating or managing Batch accounts, and the order of presentation favors Windows tools first.
Recommendations
- Include examples for creating and managing Batch accounts using cross-platform tools like Azure CLI and REST API.
- Mention Azure PowerShell and Azure CLI alongside .NET and portal options, and provide links to relevant documentation.
- Add explicit guidance or examples for Linux users, such as shell commands or scripts.
- Ensure that references to management tools are presented in a neutral or parallel order (e.g., 'You can use the Azure portal, Azure CLI, Azure PowerShell, or .NET SDK...').
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-aad-auth-management.md
.../blob/main/articles/batch/batch-aad-auth-management.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively providing .NET (C#) examples, referencing only the Azure portal (which is often Windows-centric in its UI instructions), and using Windows-specific terminology such as 'Windows Azure Service Management API.' There are no examples or guidance for Linux users, such as using cross-platform SDKs, command-line tools (e.g., Azure CLI), or alternative authentication flows suitable for non-Windows environments.
Recommendations
- Include examples using cross-platform tools such as Azure CLI or Azure PowerShell (which is available on Linux and macOS) for application registration and permission assignment.
- Provide code samples in additional languages (e.g., Python, Java) that are commonly used on Linux.
- Clarify that the Azure portal is accessible from any OS, and consider providing equivalent instructions for using the Azure CLI or REST API for app registration and permission management.
- Avoid Windows-specific terminology where possible (e.g., refer to 'Azure Service Management API' instead of 'Windows Azure Service Management API').
- Add a section or callout specifically addressing Linux/macOS developers, outlining any differences or additional steps required.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-applications-to-pool-nodes.md
...ain/articles/batch/batch-applications-to-pool-nodes.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page exhibits Windows bias by referencing Windows-specific file types and installation patterns (e.g., .exe, .msi) as primary examples, without providing equivalent Linux examples (such as .sh scripts or .deb/.rpm packages). There are no Linux-specific tools, commands, or file types mentioned, and the examples assume a Windows environment. This may lead Linux users to feel unsupported or unclear about how to adapt the instructions for their platforms.
Recommendations
- Include Linux-specific examples alongside Windows ones, such as installing .deb or .rpm packages, or running shell scripts (.sh) in start tasks.
- Mention Linux tools and patterns (e.g., using bash scripts, apt/yum/zypper for package installation) wherever Windows tools (.msi, .exe) are referenced.
- Provide explicit examples of start task command lines for both Windows (cmd/PowerShell) and Linux (bash/sh).
- Clarify that the methods described apply to both Windows and Linux nodes, and note any platform-specific considerations.
- Add a section or table summarizing common installation patterns for both Windows and Linux environments.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-container-isolation-task.md
.../main/articles/batch/batch-container-isolation-task.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates Windows bias by describing Windows-specific paths and mount patterns in detail, listing Windows host/container paths first and exclusively in the main table, and omitting explicit Linux path examples. There are no Linux-specific code or path examples, and the documentation assumes familiarity with Windows drive letters and conventions.
Recommendations
- Add a table or section showing equivalent Linux host and container paths for each Azure Batch data path, using Linux filesystem conventions (e.g., /mnt/batch/tasks/applications).
- Provide Linux-specific examples and explanations, including how to mount paths in Linux containers and what the default Linux paths are.
- Ensure that code samples and explanations are balanced, showing both Windows and Linux scenarios where applicable.
- Avoid listing Windows paths and patterns first or exclusively; present both platforms in parallel for clarity and parity.
- Clarify any platform-specific differences in behavior, such as mount modes or default directories, in a dedicated comparison section.
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
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation shows evidence of Windows bias in several areas. File path examples for uploading and downloading files use Windows-style paths (e.g., 'c:\source_videos\*.mp4') without providing Linux or macOS equivalents. The CLI file transfer commands only show Windows paths, and there are no explicit Linux shell examples or mentions of Linux-specific patterns for file operations. While the documentation does mention Linux in the context of VM pools and package installation, user-facing examples and instructions for local operations are Windows-centric.
Recommendations
- Provide parallel examples using Linux/macOS file paths (e.g., '~/source_videos/*.mp4' or '/home/user/source_videos/*.mp4') alongside Windows examples in all CLI command snippets.
- Explicitly mention that the Azure CLI and Batch CLI extension are cross-platform and supported on Windows, Linux, and macOS, including in the installation section.
- Add notes or callouts where file paths are used, clarifying the syntax differences between Windows and Unix-like systems.
- Include at least one end-to-end example workflow using Linux/macOS conventions (e.g., bash shell, forward slashes in paths) to demonstrate parity.
- Review all screenshots, code snippets, and instructions to ensure they are platform-agnostic or provide alternatives for both Windows and Linux users.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-custom-images.md
...e-docs/blob/main/articles/batch/batch-custom-images.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by consistently mentioning Windows (RDP) before Linux (SSH) when describing how to connect to VMs, providing only Windows-specific .NET SDK code samples (with 'batch.node.windows amd64' as the node agent SKU), and omitting explicit Linux-focused code examples or command-line walkthroughs. Additionally, there is no example of using Linux tools or scripts to create or manage images/pools, and the REST API example does not clarify Linux-specific values for nodeAgentSkuId.
Recommendations
- Provide parallel Linux-focused code samples (e.g., using 'batch.node.ubuntu' or other Linux nodeAgentSkuId values) alongside Windows examples in SDK and REST API sections.
- When describing how to connect to VMs, alternate or equally prioritize Linux (SSH) and Windows (RDP) instructions.
- Include explicit Linux command-line examples (e.g., using Bash/CLI) for preparing VMs, creating snapshots, and images.
- Clarify the nodeAgentSkuId values for common Linux distributions in REST API and SDK examples.
- Add references to Linux-specific documentation and tools where appropriate, not just Windows or generic Azure tools.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-job-prep-release.md
...ocs/blob/main/articles/batch/batch-job-prep-release.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively providing Windows command-line examples (using 'cmd /c', Windows environment variables, and Windows file paths), referencing Windows tools and patterns, and omitting any Linux or cross-platform equivalents. The code samples and output use Windows-style paths and commands, with no mention of Bash, Linux shell scripting, or POSIX environment variables. This may hinder Linux users from easily adapting the guidance to their environment.
Recommendations
- Provide equivalent Linux/Bash command-line examples alongside Windows examples, using Bash syntax, Linux environment variables, and POSIX file paths.
- Clearly indicate cross-platform support for job preparation and release tasks, and document any platform-specific considerations.
- Update code samples to show how to specify command lines for both Windows and Linux nodes, possibly using conditional logic or configuration.
- Include sample output using Linux-style paths and commands to illustrate parity.
- Reference Linux tools (e.g., 'rm', 'echo', shell scripts) and patterns where appropriate, and avoid assuming Windows as the default platform.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/managed-identity-pools.md
...ocs/blob/main/articles/batch/managed-identity-pools.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation shows evidence of Windows bias, primarily by presenting Windows/PowerShell examples before Linux/Bash equivalents, and referencing Windows tools and documentation first. The .NET example is also Windows-centric, and the Instance Metadata Service link points to the Windows-specific page. Linux is included, but often after Windows, and with less detail.
Recommendations
- Present Linux/Bash examples before or alongside Windows/PowerShell examples, or alternate their order in each section.
- Link to both Windows and Linux versions of the Instance Metadata Service documentation, or use a platform-neutral link.
- Include code examples using cross-platform tools (e.g., Azure CLI, REST API) and ensure parity in detail and explanation for both Windows and Linux.
- When referencing SDKs or libraries, clarify their cross-platform support and provide at least one example using a Linux-friendly language or tool.
- Avoid defaulting to Windows terminology or tools (e.g., PowerShell, .NET) without also providing Linux alternatives (e.g., Bash, Python).
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-parallel-node-tasks.md
.../blob/main/articles/batch/batch-parallel-node-tasks.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways. The primary code sample for the .NET SDK uses a Windows VM image (MicrosoftWindowsServer) and node agent, with no equivalent Linux example provided. The only full code walkthrough is in C#/.NET, which is most commonly used on Windows. The referenced GitHub sample is also a C# console application, reinforcing Windows-centric tooling. Although the REST API example uses Ubuntu, it is less detailed and not accompanied by a Linux-focused SDK sample or workflow. There are no Linux shell or Python examples, and Windows tools and patterns are mentioned first or exclusively throughout the page.
Recommendations
- Add equivalent .NET SDK code samples for Linux pools (e.g., using Ubuntu images and batch.node.ubuntu agent SKU).
- Provide Python SDK examples, which are popular on Linux, showing pool creation and task submission with Linux VM images.
- Include Linux shell (bash) or CLI examples for common operations, such as pool creation and task submission.
- Reference Linux-focused sample projects on GitHub, or add new ones if they do not exist.
- When listing VM images in examples, alternate or show both Windows and Linux options.
- Ensure that REST API examples are as detailed and complete for Linux as for Windows.
- Mention Linux tools and patterns (e.g., bash scripting, cron jobs) where relevant, not just Windows/PowerShell.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-mpi.md
...tDocs/azure-docs/blob/main/articles/batch/batch-mpi.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a strong Windows bias. All code samples, configuration snippets, and walkthroughs exclusively use Windows tools (MS-MPI, cmd.exe, Windows Server images) and Batch .NET, with no equivalent Linux or cross-platform examples. Linux and Intel MPI are only mentioned in passing or in notes, and no concrete Linux-based code or setup instructions are provided. The sample application and setup instructions are entirely Windows-centric, and the only referenced code sample for Linux is external and not integrated into the main documentation.
Recommendations
- Provide parallel Linux-based examples using Python or Bash, Intel MPI, and Ubuntu or other Linux VM images.
- Include code snippets for creating pools with Linux images and installing Intel MPI via a StartTask using Bash.
- Show how to configure and run multi-instance tasks using Linux command lines (e.g., using mpirun or mpiexec for Intel MPI) in addition to Windows/MS-MPI.
- Add a Linux-specific walkthrough for building, packaging, and running an MPI application (e.g., using gcc/mpicc and Python).
- Reference and integrate the Batch Linux MPI code sample directly in the main documentation, not just as a tip.
- Ensure that all sections (requirements, setup, execution, troubleshooting) have both Windows and Linux instructions/examples side by side.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-pool-compute-intensive-sizes.md
...n/articles/batch/batch-pool-compute-intensive-sizes.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation provides both Linux and Windows guidance, but there is a noticeable Windows bias. Windows examples and tools (e.g., PowerShell, Remote Desktop, Microsoft MPI) are often mentioned first or in more detail. The Windows example for installing GPU drivers is more step-by-step and includes a full command line, while the Linux example is less detailed and omits a direct command for driver installation. The Windows MPI example uses PowerShell and RDP, but there is no equivalent Linux MPI example. Windows-specific tools and patterns (e.g., MSI installers, RDP, PowerShell) are referenced without Linux equivalents.
Recommendations
- Ensure Linux and Windows examples are equally detailed and parallel in structure. For example, provide explicit Linux shell commands for driver installation, not just references.
- When listing OS-specific sections or tables, alternate the order or present Linux first in some cases to avoid 'windows_first' bias.
- For every Windows example (e.g., installing Microsoft MPI with PowerShell), provide a Linux equivalent (e.g., installing Intel MPI or OpenMPI with apt or yum).
- Reference Linux tools and patterns (e.g., SSH, bash scripts) wherever Windows tools (e.g., RDP, PowerShell) are mentioned.
- Expand the Linux MPI example to match the detail level of the Windows example, including explicit commands and configuration steps.
- Review for parity in troubleshooting and next steps sections, ensuring both OSes are equally represented.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-pool-update-properties.md
...ob/main/articles/batch/batch-pool-update-properties.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates Windows bias by providing only a C# SDK example that uses a Windows VM image (MicrosoftWindowsServer) and a Windows node agent SKU. There are no equivalent examples for Linux VM images, Linux node agent SKUs, or usage of Linux-specific tools. The only concrete code sample is Windows-centric, and Linux alternatives are neither mentioned nor demonstrated.
Recommendations
- Add equivalent examples for updating a pool with a Linux VM image (e.g., Ubuntu or CentOS) and the corresponding Linux node agent SKU in both C# and REST API sections.
- Explicitly mention Linux VM image options alongside Windows in descriptive text and code comments.
- Provide at least one example using a Linux-based tool or scripting environment (e.g., Azure CLI on Linux, Bash scripting) to update pool properties.
- Ensure that documentation references to VM images and node agent SKUs include both Windows and Linux options equally.
- Review all code snippets and ensure parity between Windows and Linux scenarios, including authentication and environment variable handling where relevant.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-rendering-storage-data-movement.md
...rticles/batch/batch-rendering-storage-data-movement.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows tools and patterns (such as cmdkey, net use, and Windows-style azcopy syntax) are presented in detail, with full command-line examples and configuration snippets. Linux equivalents (e.g., mounting Azure Files via CIFS, or using azcopy with Linux syntax) are either missing or only briefly mentioned. The section on Azure Files is explicitly focused on Windows, with no Linux mounting example provided. In the azcopy section, only the Windows command-line syntax is shown, and the Linux usage is not illustrated. Overall, Windows approaches are described first and in more depth, while Linux alternatives are less detailed or omitted.
Recommendations
- Provide parallel Linux examples for all Windows-specific instructions, especially for mounting Azure Files (e.g., using mount.cifs in a job preparation task).
- Include azcopy command-line examples using Linux syntax (e.g., azcopy cp source dest) and shell conventions.
- Ensure that for every Windows tool or command (e.g., cmdkey, net use), the Linux equivalent (e.g., mount, cifs-utils) is presented with equal detail.
- Reorganize sections to present Linux and Windows options with parity, or clearly separate them to avoid implicit prioritization.
- Expand the blobfuse section with more concrete Linux job/task configuration examples, similar to the detailed Windows Azure Files mounting example.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-sig-images.md
...zure-docs/blob/main/articles/batch/batch-sig-images.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows tools and patterns (such as RDP, PowerShell) are often mentioned before or more prominently than their Linux equivalents. Some examples and instructions are Windows-centric or list Windows tooling first, and there is a lack of parity in Linux-specific examples or guidance, especially for common administrative tasks.
Recommendations
- Ensure that Linux and Windows instructions are presented with equal prominence and in parallel where possible (e.g., 'Connect via RDP (Windows) or SSH (Linux)' should be consistently paired in all relevant sections).
- Provide Linux-specific examples and commands alongside PowerShell, such as Bash/CLI equivalents, especially in sections listing how to retrieve supported images or manage resources.
- When referencing tools (e.g., RDP, PowerShell), always mention the Linux alternatives (e.g., SSH, Bash) at the same time, not as an afterthought.
- Add explicit Linux-focused walkthroughs for tasks like preparing a VM, mounting disks, and verifying pool nodes, not just generic or Windows-first instructions.
- Review all code snippets and ensure that, for every Windows/PowerShell example, a Linux/Bash/CLI equivalent is provided.
- In portal instructions, clarify SSH login steps for Linux as thoroughly as RDP steps for Windows, including any differences in credential setup or troubleshooting.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-task-dependencies.md
...cs/blob/main/articles/batch/batch-task-dependencies.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a strong Windows bias by exclusively using Windows command-line syntax (cmd.exe) in all code examples and referencing Windows tools. There are no Linux/bash equivalents or examples, and the documentation does not mention cross-platform considerations. This may mislead users into thinking Azure Batch is Windows-only or make it harder for Linux users to adapt the examples.
Recommendations
- Provide equivalent examples using bash/sh syntax (e.g., 'bash -c "echo taskA"') alongside the Windows 'cmd.exe' examples.
- Explicitly mention that Azure Batch supports both Windows and Linux compute nodes, and clarify any platform-specific behaviors.
- Add a section or note on how to adapt task commands for Linux pools, including differences in shell invocation and script handling.
- Ensure that all code snippets and sample projects include both Windows and Linux variants where applicable.
- Avoid using only Windows-specific tools or patterns (like 'cmd.exe') in documentation intended for a cross-platform audience.