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 1-25 of 436 flagged pages
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 is heavily biased toward Windows and PowerShell. All code examples use PowerShell, and instructions reference Windows-specific tools (e.g., .msi installers, WMF 5, msiexec.exe). There are no Linux or cross-platform alternatives provided for certificate creation, service principal setup, Key Vault access, or Azure CLI usage. The guidance for installing Azure PowerShell is Windows-centric, and Linux users are left without clear instructions or examples.
Recommendations
- Add equivalent examples using Azure CLI and/or Bash scripts for certificate creation, service principal setup, and Key Vault access.
- Provide instructions for installing Azure PowerShell or Azure CLI on Linux nodes, including package manager commands (e.g., apt, yum).
- Mention and demonstrate cross-platform certificate creation tools (e.g., openssl) and how to use them with Azure.
- Reorder or balance examples so that Linux and Windows are presented equally, or clarify which steps are platform-specific.
- Explicitly note any differences or additional steps required for Linux/macOS users.
Create Pull Request
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 is heavily biased towards Windows and MS-MPI. All code samples, configuration snippets, and step-by-step instructions are exclusively for Windows nodes, using MS-MPI and Windows command-line tools (cmd.exe, mpiexec.exe, smpd.exe). Linux alternatives (Intel MPI, bash, Python) are mentioned only in passing, with no concrete examples or instructions. The code sample and walkthrough require Visual Studio and Windows executables, making it difficult for Linux/macOS users to follow or adapt the guidance.
Recommendations
- Provide equivalent Linux examples using Intel MPI, bash scripts, and Python, including pool creation, StartTask installation, and multi-instance task configuration.
- Include step-by-step instructions for setting up Linux pools, installing Intel MPI via StartTask, and running MPI applications with mpirun.
- Offer cross-platform code samples and clarify platform-specific differences in environment variables, resource files, and command lines.
- List Linux tools and patterns alongside Windows ones, not only as afterthoughts or in notes.
- Reference Linux-focused code samples and walkthroughs with equal prominence.
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. All code examples use PowerShell, and certificate creation is described only via 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 examples or guidance for performing these tasks on Linux or macOS, nor are cross-platform CLI tools (like Azure CLI or OpenSSL) mentioned.
Recommendations
- Add equivalent examples using Azure CLI and Bash for Linux/macOS users.
- Include instructions for generating certificates using OpenSSL, which is available on Linux/macOS.
- Provide guidance for installing Azure PowerShell or Azure CLI on Linux/macOS nodes.
- Explicitly mention cross-platform approaches and tools where possible.
- Reorder sections or add parallel instructions so that Linux/macOS methods are presented alongside Windows methods.
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 is heavily biased toward Windows and MS-MPI. All code samples, configuration snippets, and walkthroughs use Windows-specific tools (cmd, MS-MPI, .exe files), and the examples exclusively target Windows compute nodes. Linux and Intel MPI are mentioned only in passing, with no concrete examples, code snippets, or setup instructions for Linux users. The sample application and instructions require Visual Studio and Windows binaries, making it difficult for Linux/macOS users to follow along or replicate the workflow.
Recommendations
- Add equivalent code samples and walkthroughs for Linux compute nodes using Intel MPI and Bash commands.
- Provide instructions for installing Intel MPI on Linux nodes via StartTask, including sample shell scripts.
- Include a Linux-based sample MPI application (e.g., written in C/C++ or Python) and show how to package and deploy it.
- Demonstrate how to configure pools with Linux VM images and node agent SKUs.
- Offer guidance for users developing on macOS or Linux, including alternative IDEs and build instructions.
- Present Linux examples before or alongside Windows examples to avoid 'Windows-first' bias.
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 is heavily biased toward Windows environments. It exclusively references Windows tools (Visual Studio, WindowsServer VM images, cmd.exe), uses Windows-specific NuGet packages (Microsoft.ApplicationInsights.WindowsServer), and provides only PowerShell and Windows command-line examples. There is no mention of Linux/macOS equivalents, nor guidance for deploying or running Application Insights in non-Windows Batch pools.
Recommendations
- Add instructions and examples for Linux-based Batch pools, including VM image selection and configuration.
- Provide Linux/macOS equivalents for package installation (e.g., dotnet CLI, NuGet CLI) and command-line usage.
- Clarify whether Application Insights instrumentation works on Linux compute nodes, and if so, detail any differences (e.g., use Microsoft.ApplicationInsights instead of WindowsServer-specific package).
- Include cross-platform code samples and configuration steps.
- Mention and link to documentation for Application Insights support in non-Windows environments.
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 tutorial exhibits a notable Windows bias: it exclusively references Windows tools and patterns, such as using Windows Server VM images, Windows-specific ffmpeg builds, and Windows command-line syntax (cmd /c). There are no examples or instructions for running on Linux or macOS compute nodes, nor is there guidance for using Linux-compatible ffmpeg packages or shell syntax. The sample code and pool configuration are hardcoded for Windows environments, making it difficult for Linux users to follow or adapt the tutorial.
Recommendations
- Add explicit instructions and code samples for creating Linux-based pools (e.g., Ubuntu VM images) in Azure Batch.
- Provide Linux/macOS-compatible ffmpeg download links and usage examples.
- Show alternative command-line syntax for Linux (e.g., bash/sh) and update task creation code to support both platforms.
- Clarify in the prerequisites and throughout the tutorial that both Windows and Linux are supported, and highlight any differences.
- Include sample pool and job configurations for Linux nodes, and explain how to select the appropriate node agent SKU and image reference.
- Ensure that resource file paths and output file handling are cross-platform compatible.
Batch
Use Microsoft Entra ID to authenticate Batch Management solutions
.../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 page demonstrates a Windows bias by exclusively providing examples and instructions for the .NET library and C# sample code, which are traditionally Windows-centric. The registration and configuration steps are described using the Azure portal UI, which is most commonly accessed from Windows environments. There are no Linux-specific instructions, examples, or references to cross-platform alternatives (such as Python, Java, or CLI usage on Linux). The documentation also refers to the 'Windows Azure Service Management API' and does not mention Linux tools or shell commands.
Recommendations
- Include equivalent examples for Linux environments, such as using Azure CLI or PowerShell Core on Linux.
- Provide sample code in cross-platform languages (e.g., Python, Java) alongside .NET/C#.
- Explicitly mention that the Azure portal and MSAL libraries are accessible from Linux and macOS, and provide any necessary platform-specific notes.
- Add instructions for registering applications and acquiring tokens using command-line tools (Azure CLI, Bash scripts) that work on Linux.
- Reference Linux-compatible authentication flows and tools where appropriate.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page shows moderate Windows bias. PowerShell cmdlets are listed first in the command-line tools section, and Windows-specific tools like Remote Desktop (RDP) are mentioned for node access without Linux equivalents (e.g., SSH). The Azure portal example references downloading RDP files for node login, which is a Windows-centric workflow. While Azure CLI and cross-platform tools are mentioned, Windows tools and patterns are prioritized or exclusively described in some areas.
Recommendations
- List Azure CLI before PowerShell in the command-line tools section to emphasize cross-platform parity.
- Include SSH-based instructions or references for logging into Linux compute nodes, alongside RDP for Windows nodes.
- When describing troubleshooting (e.g., downloading stderr.txt), clarify that this applies to both Windows and Linux nodes.
- Add explicit examples or tutorials for Linux environments, especially for node access and management.
- Ensure that all tools and workflows described have Linux equivalents or alternatives mentioned where applicable.
Batch
Create a Batch account in the Azure portal
...lob/main/articles/batch/batch-account-create-portal.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several areas. The only command-line example provided for accepting marketplace terms uses PowerShell cmdlets, with no equivalent Azure CLI or Bash example for Linux users. References to command-line tooling (e.g., 'Batch PowerShell cmdlets') appear before Azure CLI in the list of management options. There are no explicit Linux-specific instructions or examples, and the documentation assumes familiarity with Windows-centric tools and workflows.
Recommendations
- Provide Azure CLI and Bash examples alongside PowerShell cmdlets for all command-line operations, especially for accepting marketplace terms.
- List Azure CLI management options before or alongside PowerShell cmdlets to avoid Windows-first ordering.
- Explicitly mention Linux compatibility and provide guidance for Linux users where relevant.
- Include screenshots or instructions that demonstrate usage from Linux environments, such as Azure Cloud Shell (Bash).
- Review all command references to ensure Linux users are not required to use Windows-only tools.
Batch
Deploy application packages to compute nodes
...blob/main/articles/batch/batch-application-packages.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a Windows bias by providing only Windows-centric code examples (e.g., C#/.NET, Windows VM images, Windows command lines), referencing Windows-specific tools (cmd.exe), and presenting Windows details before Linux equivalents. Linux-specific code samples, shell commands, and VM configuration examples are missing, and Linux environment variable usage is described only after Windows. The documentation does not offer parity in examples or guidance for Linux users.
Recommendations
- Add Linux-specific code samples, including shell (bash) command lines for task execution.
- Include examples of pool creation using Linux VM images (e.g., Ubuntu, CentOS) in addition to Windows.
- Show how environment variables are used in Linux tasks, with sample bash scripts referencing the application package paths.
- Present Windows and Linux instructions side-by-side or in parallel sections to ensure equal visibility.
- Reference cross-platform tools and APIs, and clarify any OS-specific differences in application package deployment and usage.
- Expand documentation to include .NET alternatives (e.g., Python SDK, REST API) with Linux-focused examples.
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 tools and patterns (e.g., .exe, .msi installers) without mentioning Linux equivalents. There are no examples or guidance for Linux application packaging or installation methods, and Windows terminology appears first and exclusively in relevant sections.
Recommendations
- Include examples for Linux application and data deployment, such as using .sh scripts, .deb/.rpm packages, or tarballs.
- Mention Linux installation patterns (e.g., using apt, yum, or custom shell scripts) alongside Windows (.msi/.exe) references.
- Provide guidance on handling Linux-specific scenarios, such as file permissions, symbolic links, and environment setup.
- Ensure that terminology and examples are balanced between Windows and Linux, or presented in parallel where appropriate.
Batch
Autoscale compute nodes in an Azure Batch pool
...cs/blob/main/articles/batch/batch-automatic-scaling.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits Windows bias in several ways: Windows-based VM images are used first and exclusively in .NET examples, with no Linux equivalent shown; PowerShell and Windows tools are referenced before or instead of cross-platform or Linux alternatives; C#/.NET examples dominate code samples, with limited Python coverage and no Linux shell/CLI examples; and there is a lack of explicit Linux-focused instructions or parity in SDK usage and pool configuration examples.
Recommendations
- Provide Linux VM configuration examples in .NET code samples, e.g., using Ubuntu or other Linux images, alongside Windows examples.
- Include Linux shell (bash) and Azure CLI examples for pool creation and autoscale configuration, not just PowerShell or .NET.
- Ensure that references to PowerShell are balanced with equivalent bash/CLI instructions, and mention Linux tools where appropriate.
- Add explicit instructions and code samples for enabling autoscale on Linux pools using .NET, Python, and CLI.
- Present Windows and Linux options side-by-side in tables and code blocks, rather than Windows-first or Windows-only.
- Reference cross-platform SDKs and tools (e.g., Azure CLI) before platform-specific ones, or at least equally.
Batch
Use Azure Pipelines to build and deploy an HPC solution
...ocs/azure-docs/blob/main/articles/batch/batch-ci-cd.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page demonstrates a clear Windows bias. The example solution exclusively deploys Windows software (FFmpeg for Windows) on Windows-based Batch nodes, with ARM templates specifying Windows images and node agents. The repository setup and build pipeline only reference the Windows version of FFmpeg. The agent pool for Azure Pipelines is set to 'windows-latest', and Azure CLI tasks are configured to use PowerShell Core, a Windows-centric scripting environment. There are no Linux equivalents or examples provided, and Linux support is only mentioned briefly in a note, without actionable guidance.
Recommendations
- Provide parallel examples for deploying Linux software on Linux-based Batch nodes, including ARM template snippets for Linux VM images and node agents.
- Include instructions for downloading and packaging the Linux version of FFmpeg, and update repository setup steps to show both Windows and Linux application folders.
- Demonstrate how to set the agent pool to 'ubuntu-latest' or another Linux agent in Azure Pipelines, with corresponding YAML and release pipeline steps.
- Show Azure CLI tasks using Bash scripts in addition to PowerShell Core, and clarify cross-platform compatibility.
- Add explicit guidance and code samples for users who wish to deploy HPC solutions on Linux, ensuring equal visibility and parity with Windows instructions.
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows tools and patterns (e.g., cmd.exe, drive letters, backslash paths) are mentioned first or exclusively in several places. Examples often use Windows conventions before Linux equivalents, and some explanations (such as app package environment variable naming) provide more detail for Windows than Linux. Linux-specific tools and patterns are sometimes mentioned secondarily or with less detail, and some examples (e.g., directory postfix tables) use Windows-style paths without Linux equivalents.
Recommendations
- Present Linux and Windows examples side-by-side, with equal detail and prominence.
- Ensure all tables and examples include both Windows and Linux path formats (e.g., use both backslash and forward slash, drive letters and mount points).
- When describing environment variable naming conventions, provide parallel details for both platforms.
- Avoid using Windows tools (cmd.exe, drive letters) as the default or primary example; alternate or combine with Linux tools (sh, mount points).
- Include Linux-specific notes where Windows-specific notes are given (e.g., for app package naming, directory structures).
- Review all examples and tables for parity, ensuring Linux users can easily find relevant information.
Batch
Use ephemeral OS disk nodes for Azure Batch pools
...b/main/articles/batch/create-pool-ephemeral-os-disk.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation page exhibits Windows bias by referencing PowerShell as the sole example for programmatically querying VM capabilities, without mentioning Linux alternatives such as Azure CLI or Bash. The mention of PowerShell comes before any code examples, and no Linux-specific tools or command-line patterns are provided. The SDK code examples themselves are cross-platform (Python and C#), but the operational guidance favors Windows tooling.
Recommendations
- Add Azure CLI and Bash examples for querying VM capabilities, alongside the PowerShell example.
- Explicitly mention that both Windows and Linux users can use the SDK code samples, and provide guidance for installing and running them on Linux.
- Where PowerShell is referenced, include equivalent commands for Linux shells (e.g., Bash, zsh) to ensure parity.
- Review other operational instructions to ensure Linux tools and workflows are represented equally and not as an afterthought.
Batch
Persist job and task output to a data store
...ure-docs/blob/main/articles/batch/batch-task-output.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates bias towards Windows by providing examples and references that are Windows-centric, such as referencing Windows executables in custom file movement solutions (e.g., 'doMyWork.exe && uploadMyFilesToSql.exe'), and omitting explicit Linux or cross-platform examples. The sample project linked is C#-based, which is most commonly used on Windows. There are no Linux shell or cross-platform scripting examples, nor are Linux-specific tools or patterns mentioned.
Recommendations
- Add explicit Linux and cross-platform examples for custom file movement, such as using bash scripts (e.g., './doMyWork.sh && ./uploadMyFilesToSql.sh') or Python scripts.
- Mention Linux tools and patterns for file movement, such as using 'scp', 'rsync', or Azure CLI commands.
- Provide sample projects or code snippets in languages commonly used on Linux (e.g., Python, bash) alongside C#.
- Clarify that the guidance applies to both Windows and Linux compute nodes, and highlight any platform-specific considerations.
- Ensure that references to executables or scripts are platform-neutral, or provide parallel examples for both Windows and Linux.
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 primarily describing deployment via the Azure portal (which is most commonly used on Windows), and referencing Azure PowerShell as an alternative before mentioning Azure CLI or REST API. There are no explicit Linux or cross-platform command-line examples, and the deployment instructions focus on GUI-based steps typical of Windows environments. Linux-specific tools or CLI examples are missing.
Recommendations
- Add explicit Azure CLI examples for template deployment, including commands for Linux/macOS users.
- Present deployment options in a cross-platform order (e.g., Azure CLI before PowerShell, or side-by-side).
- Include screenshots or instructions for using the Azure CLI on Linux/macOS.
- Clarify that the Azure portal and CLI tools are available on all major operating systems.
- Provide links to Linux-specific documentation or quickstarts where relevant.
Batch
Persist output data to Azure Storage with .NET File Conventions library
...n/articles/batch/batch-task-output-file-conventions.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 .NET/C# code samples, referencing Windows-specific tools (Visual Studio), and omitting Linux or cross-platform examples for persisting output data to Azure Storage with Azure Batch. There are no mentions of Linux development environments, alternative languages, or command-line workflows, and the instructions assume a Windows-centric development setup.
Recommendations
- Add equivalent code samples for Linux environments, such as using .NET Core on Linux, or other supported languages (Python, Java).
- Include instructions for setting up and running the sample project on Linux or macOS, such as using VS Code, JetBrains Rider, or command-line tools.
- Reference cross-platform tools and editors, not just Visual Studio.
- Provide guidance for developers using Linux containers or running Batch tasks on Linux nodes.
- Clarify that the File Conventions standard can be implemented in any language and provide links or samples for non-.NET implementations.
Batch
Create a Batch pool with specified public IP addresses
...docs/blob/main/articles/batch/create-pool-public-ip.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation displays Windows bias by listing Azure PowerShell as a method for creating public IP addresses alongside the Azure portal and CLI, with PowerShell mentioned explicitly and before any Linux-specific tools. No Linux shell or scripting examples (e.g., Bash) are provided, and the use of PowerShell is highlighted without equivalent Linux command-line alternatives. The documentation does not offer parity in examples or tooling for Linux users.
Recommendations
- Add explicit Bash shell examples for creating public IP addresses using Azure CLI, including sample commands.
- Reorder the list of public IP creation methods to mention cross-platform tools (Azure CLI) before platform-specific ones (PowerShell).
- Include notes or guidance for Linux users on how to install and use Azure CLI for these tasks.
- If PowerShell is mentioned, clarify that it is available cross-platform, or provide equivalent Linux-native commands.
- Ensure future examples and instructions are platform-neutral or provide both Windows and Linux variants.
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. Windows VM images and considerations are discussed before Linux equivalents in several sections, and Windows-specific tools, paths, and behaviors (e.g., C:\ProgramData\Docker, c:\app\myApp.exe) are referenced in examples and explanations. Most code samples use C# and Python, but all container configuration and task examples use Linux images and commands, with only one C# task example using a Windows path. There is a lack of explicit Linux shell command examples for troubleshooting and task execution, and Windows-specific limitations and behaviors are described in more detail than Linux equivalents.
Recommendations
- Ensure Linux and Windows examples are presented in parallel, with equal detail and order.
- Provide explicit Linux shell command examples for troubleshooting and task execution, not just C# or Python code.
- Include Windows PowerShell or CMD examples for container configuration and task execution, especially in troubleshooting sections.
- Clarify Linux-specific limitations and behaviors (e.g., working directory, file paths, environment variables) to match the detail given for Windows.
- Avoid referencing Windows tools and paths (e.g., C:\ProgramData\Docker, c:\app\myApp.exe) without providing Linux equivalents (e.g., /var/lib/docker, /app/myApp.sh).
- When discussing VM images, alternate the order of Windows and Linux, or present them together for parity.
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, setup instructions, and tooling references are focused on Windows environments, specifically using MS-MPI, Batch .NET, and Visual Studio. Windows-specific commands (cmd, .exe files) and resource files are used throughout, with no equivalent Linux code samples or step-by-step instructions. Linux and Intel MPI are mentioned only in passing, and Linux-specific guidance is relegated to notes or external links.
Recommendations
- Add parallel Linux-focused code samples using Python or Bash, demonstrating Intel MPI setup and execution.
- Include explicit instructions for creating pools with Linux VM images, including sample configuration code.
- Provide StartTask examples for installing Intel MPI on Linux nodes, using shell commands and package managers.
- Show application and coordination command lines for Linux (e.g., using mpiexec, referencing shell scripts, using $AZ_BATCH_TASK_SHARED_DIR).
- Offer a Linux-based walkthrough, including building and packaging an MPI application (e.g., with gcc and mpicc), uploading resources, and running tasks.
- Reference Linux development tools (e.g., VS Code, gcc, Python) alongside Visual Studio.
- Ensure that both Windows and Linux scenarios are presented side-by-side or in separate sections for parity.
Batch
Use compute-intensive Azure VMs with Batch
...n/articles/batch/batch-pool-compute-intensive-sizes.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Windows and Linux examples and tables, but Windows-specific tools and patterns (e.g., PowerShell, Remote Desktop, Microsoft MPI, Windows Server SKUs) are described in more detail and sometimes appear before Linux equivalents. The Windows example for installing GPU drivers is more step-by-step and uses Windows-centric tooling (cmd, MSI installers), while the Linux example is less detailed and omits command-line specifics. The Microsoft MPI example is only given for Windows, with no Linux MPI example. Windows pool configuration options and deprecated features are discussed in more depth than Linux equivalents.
Recommendations
- Provide equally detailed, step-by-step Linux examples for installing drivers and configuring pools, including command-line instructions (e.g., bash scripts, apt commands).
- Include a Linux MPI example (e.g., using Intel MPI or OpenMPI) with sample installation and pool configuration steps.
- Mention Linux tools and patterns (e.g., SSH, bash, Linux package managers) wherever Windows tools (PowerShell, RDP, MSI installers) are referenced.
- Ensure that Linux and Windows examples are presented in parallel, with neither platform consistently prioritized or described first.
- Expand Linux pool configuration options and troubleshooting guidance to match the depth provided for Windows.
Batch
Use the Azure Compute Gallery to create a custom image pool
...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 several forms of Windows bias. Windows and Windows-specific tools (PowerShell, RDP) are mentioned before or more prominently than their Linux equivalents. Examples and instructions often reference Windows first, and PowerShell is listed as a primary method for discovering supported images, with Linux alternatives (Azure CLI) mentioned second. The portal workflow emphasizes RDP for Windows and only briefly mentions SSH for Linux. There are missing Linux-specific examples for some steps, such as mounting and formatting disks, and the documentation does not provide parity in command-line or scripting examples for Linux users.
Recommendations
- Ensure that Linux-specific instructions and examples (e.g., mounting disks, SSH usage, CLI commands) are presented alongside or before Windows equivalents.
- Provide Bash shell and Linux CLI examples wherever PowerShell is used, and avoid listing PowerShell first unless there is a technical reason.
- Expand portal instructions to equally detail SSH connection steps for Linux, including troubleshooting and verification.
- Include explicit Linux-focused guidance for preparing VMs, such as commands for formatting and mounting disks, and avoiding Windows-centric terminology.
- Review all SDK code samples to ensure they are OS-agnostic or provide both Windows and Linux variants where OS-specific steps are required.
Batch
Persist output data to Azure Storage with Batch service API
...cs/blob/main/articles/batch/batch-task-output-files.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong Windows bias: all code samples use C# and Windows command syntax (cmd.exe), with no Linux shell equivalents provided. Visual Studio is referenced as the development environment, and .NET libraries are exclusively used. Linux usage is only briefly mentioned as a note to change path delimiters, but no Linux-specific code or workflow is shown. There are no examples using Bash, Linux tools, or cross-platform SDKs, and the documentation does not address how to persist output from Linux-based tasks in detail.
Recommendations
- Provide equivalent code samples using Bash shell commands for Linux tasks, demonstrating how to generate output files and persist them.
- Include examples using cross-platform SDKs (e.g., Azure SDK for Python, Java, or Node.js) to show how to interact with Azure Storage from non-Windows environments.
- Add instructions for setting up and running sample projects on Linux (e.g., using VS Code, JetBrains Rider, or CLI tools), not just Visual Studio.
- Explicitly document any differences in file path handling, environment setup, and authentication for Linux pools.
- Reference Linux tools (e.g., tar, zip, Bash scripting) for consolidating output files and troubleshooting.
- Ensure that all major steps (creating containers, generating SAS tokens, uploading files) have both Windows and Linux examples.
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates Windows bias by providing a C# SDK example that exclusively uses a Windows VM image (MicrosoftWindowsServer) and node agent SKU for Windows. There are no examples or references for updating pools with Linux VM images or Linux node agent SKUs. Additionally, the examples and property values are Windows-centric, and there is no parity shown for Linux scenarios.
Recommendations
- Add equivalent examples for updating pools with Linux VM images (e.g., Ubuntu, CentOS) and Linux node agent SKUs.
- Explicitly mention both Windows and Linux options when discussing VM image configuration and pool properties.
- Provide sample code snippets for Linux scenarios (e.g., using a Linux VM image in the C# SDK example).
- Ensure REST API examples include both Windows and Linux property values.
- Reference Linux-specific documentation or considerations where relevant.