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 251-275 of 436 flagged pages
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation provides both Windows and Linux command line examples for running tasks, but Windows examples (cmd.exe) are shown first. In the 'Start task' section, Windows-specific tools like 'robocopy', 'MSI', and 'setup.exe' are mentioned as typical usage patterns, with no Linux equivalents or alternatives suggested. This may create friction for Linux users who need to adapt these instructions to their environment.
Recommendations
- Alternate the order of Windows and Linux examples, or present them side-by-side to avoid implicit prioritization.
- In sections mentioning Windows tools (e.g., 'robocopy', 'MSI', 'setup.exe'), also mention common Linux alternatives such as 'cp', 'rsync', '.deb/.rpm installers', or shell scripts.
- Provide explicit Linux/macOS examples for file copying, application installation, and other setup tasks in the 'Start task' section.
- Add a note clarifying that tool choice depends on the OS of the compute node, and link to OS-specific guidance where available.
Create Pull Request
Batch
Deploy application packages to compute nodes
...blob/main/articles/batch/batch-application-packages.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a notable Windows bias. All code examples are in C# using the Batch .NET library, and the only VM configuration example uses a Windows image. Task command lines use Windows-specific syntax (cmd /c), and there are no Linux shell or cross-platform examples. Environment variable usage is explained for both platforms, but Windows is always presented first and in more detail. There is no mention of Linux-specific tools, patterns, or troubleshooting, and no sample code for Linux node configuration or task execution.
Recommendations
- Add Linux-specific examples for pool and task creation, including VM configuration using Linux images.
- Provide sample task command lines using Linux shell syntax (e.g., bash -c).
- Include code snippets in other supported languages (e.g., Python, REST API) that demonstrate Linux usage.
- Document differences in application package deployment and troubleshooting for Linux nodes.
- Present Windows and Linux examples side-by-side or alternate which is shown first.
Batch
Use Microsoft Entra ID to authenticate Batch Management solutions
.../blob/main/articles/batch/batch-aad-auth-management.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates notable Windows bias: all code samples use C#/.NET, which is most commonly associated with Windows development; the walkthrough references the Azure portal and the AccountManagement sample, which is a C# project with no mention of Linux or cross-platform usage. There are no examples or guidance for Linux/macOS users, such as using Python, Java, or CLI tools, nor is there mention of how to perform authentication outside the Windows/.NET ecosystem. The documentation refers to the 'Windows Azure Service Management API' and does not provide parity for Linux users.
Recommendations
- Add examples for authenticating with Microsoft Entra ID using cross-platform languages (e.g., Python, Java) and SDKs.
- Include instructions for registering applications and acquiring tokens using Azure CLI or REST APIs, which work on Linux/macOS.
- Reference Linux/macOS compatibility for the Batch Management library and clarify any platform-specific requirements.
- Provide links to sample projects or code for Linux/macOS environments.
- Avoid using 'Windows Azure Service Management API' terminology exclusively; clarify that the API is accessible from any OS.
Batch
Move an Azure Batch account to another region
...cs/azure-docs/blob/main/articles/batch/account-move.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively describes moving an Azure Batch account using the Azure portal GUI, which is platform-agnostic but most commonly associated with Windows environments. There are no command-line examples (such as Azure CLI, PowerShell, or Bash), nor any mention of Linux/macOS tools or workflows. The instructions and screenshots implicitly assume a Windows-centric user experience, with no guidance for users who prefer or require command-line or automation approaches common on Linux/macOS.
Recommendations
- Add equivalent instructions for moving a Batch account using Azure CLI, which is cross-platform and widely used on Linux/macOS.
- Include examples of exporting, modifying, and deploying ARM templates via command-line (az CLI, Bash, etc.), not just through the portal.
- Explicitly mention that the Azure portal is accessible from any OS/browser, and provide parity for users who prefer non-GUI workflows.
- If scripts are included in the exported zip, clarify their platform compatibility and provide Linux/macOS usage instructions if needed.
Batch
Create a Batch account in the Azure portal
...lob/main/articles/batch/batch-account-create-portal.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page primarily describes creating and managing Azure Batch accounts via the Azure portal, which is cross-platform. However, in the 'Accept legal terms' section, only PowerShell commands are provided, with no Azure CLI or REST API alternatives. The PowerShell examples are presented without Linux/macOS equivalents, and PowerShell is referenced before Azure CLI in the 'Other Batch account management options' section. This creates friction for Linux/macOS users who may not have PowerShell installed or prefer CLI tools.
Recommendations
- Add Azure CLI examples for accepting marketplace terms (e.g., using 'az vm image terms accept').
- Provide REST API or ARM template alternatives for steps currently shown only with PowerShell.
- In 'Other Batch account management options', list Azure CLI before PowerShell or present both equally.
- Explicitly mention that PowerShell commands can be run on Linux/macOS (if true), or provide platform-specific guidance.
- Ensure all critical configuration steps have CLI and/or portal alternatives, not just PowerShell.
Batch
Autoscale compute nodes in an Azure Batch pool
...cs/blob/main/articles/batch/batch-automatic-scaling.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in several areas: .NET/C# examples are presented first and most frequently, often referencing Windows-specific VM images and node agent SKUs. Windows tooling (e.g., PowerShell cmdlets) is mentioned before cross-platform alternatives. There is a lack of Linux/macOS-specific examples, especially for command-line or scripting scenarios, and no Bash or Linux shell examples are provided. Python examples do use Ubuntu images, but overall, Windows-centric patterns dominate.
Recommendations
- Add Linux/macOS-specific examples, such as Bash or shell commands for pool creation and autoscale configuration.
- Present cross-platform tools (e.g., Azure CLI) before or alongside Windows-specific tools like PowerShell.
- Balance .NET/C# examples with equivalent Python, Java, or REST API examples, and ensure Linux VM images are used in at least half of the code samples.
- Explicitly mention Linux/macOS compatibility in tool and API sections.
- Include troubleshooting or tips sections relevant to Linux/macOS users.
Batch
Use Azure Pipelines to build and deploy an HPC solution
...ocs/azure-docs/blob/main/articles/batch/batch-ci-cd.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a notable Windows bias. The core example deploys Windows software (FFmpeg for Windows) on Windows-based Batch nodes, and the ARM template for the pool hardcodes Windows images and node agent SKUs. The repository setup and build pipeline only reference the Windows version of FFmpeg, with no mention of Linux alternatives. The agent specification for the release pipeline is set to 'windows-latest', and all screenshots and instructions assume a Windows environment. There are no examples or instructions for deploying Linux software, using Linux-based Batch pools, or adapting the pipeline for Linux/macOS users.
Recommendations
- Add parallel examples for Linux: Provide ARM template snippets for Linux-based Batch pools (e.g., Ubuntu images and nodeAgentSkuId for Linux).
- Include instructions for downloading and packaging the Linux version of FFmpeg, and show how to set up the repository for Linux workloads.
- Show how to set the agent specification to 'ubuntu-latest' or other Linux agents in Azure Pipelines.
- Explicitly mention how to adapt the build and release pipelines for Linux/macOS users, including any differences in tasks or CLI usage.
- Present both Windows and Linux examples side-by-side, or clearly indicate which steps are OS-specific.
- Add notes or links to documentation on deploying Linux applications and using Linux Batch pools.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits Windows bias by providing only Windows-centric examples (e.g., C# SDK code using a Windows VM image), referencing Windows VM images and node agent SKUs exclusively, and omitting Linux-specific examples or guidance. No Linux VM image or node agent SKU is shown, and no Linux/macOS CLI or SDK usage is demonstrated. This may create friction for Linux users trying to update pool properties for non-Windows pools.
Recommendations
- Add parallel examples using Linux VM images and node agent SKUs in code samples.
- Include Linux/macOS CLI or SDK usage (e.g., Azure CLI, Python SDK) for updating pool properties.
- Explicitly mention how to update pools with Linux nodes, including image reference and agent SKU details.
- Ensure REST API examples use generic or both Windows and Linux VM image references.
- Provide guidance or links for Linux-specific pool configuration and update scenarios.
Batch
Copy applications and data to pool nodes
...ain/articles/batch/batch-applications-to-pool-nodes.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page exhibits a mild Windows bias by referencing Windows-specific installers (.exe, .msi) and omitting explicit Linux/macOS equivalents or examples. There are no examples of Linux package formats (e.g., .deb, .rpm) or installation commands (e.g., apt, yum, bash scripts). The mention of mapping a network share is also a pattern more common in Windows environments, with no reference to Linux file sharing (e.g., NFS, SCP, rsync).
Recommendations
- Include Linux/macOS installation examples, such as using .deb/.rpm packages or shell scripts in start tasks.
- Mention Linux file transfer tools (e.g., SCP, rsync, NFS) alongside network share mapping.
- Provide sample command lines for both Windows (PowerShell, .msi/.exe) and Linux (bash, apt/yum) in relevant sections.
- Clarify that application packages and resource files can contain Linux/macOS binaries and scripts, not just Windows executables.
Batch
Migrate Batch account certificates to Azure Key Vault
...in/articles/batch/batch-certificate-migration-guide.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation mentions both Windows and Linux support for the Azure Key Vault VM extension, but provides direct links to separate Windows and Linux documentation rather than including examples inline. Windows is mentioned first in the FAQ section, and there are no concrete Linux or Windows command examples given in the main migration steps. Linux-specific guidance is limited to describing the removal of an environment variable and general advice, without step-by-step instructions or code samples.
Recommendations
- Provide explicit step-by-step migration examples for both Windows and Linux Batch pools, including sample configuration and commands.
- Ensure Linux examples (e.g., how to configure certificateStoreLocation, file permissions, and access for non-admin users) are shown alongside or before Windows examples.
- Include sample scripts for both PowerShell (Windows) and Bash (Linux) where relevant.
- Clarify any platform-specific differences in the migration process, especially for Linux users losing $AZ_BATCH_CERTIFICATES_DIR.
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several areas: Windows VM sizes and references are listed before Linux equivalents, Cloud Services Configuration (Windows-only) is described in detail, and Windows OS families are enumerated with no Linux equivalents. The 'windowsConfiguration' section is present, but there is no corresponding 'linuxConfiguration' example or details. Linux-specific options and examples are missing or relegated to links, and the documentation structure prioritizes Windows terminology and features.
Recommendations
- Add explicit Linux configuration examples, including a 'linuxConfiguration' section analogous to 'windowsConfiguration'.
- Present Linux and Windows VM size links together, or list Linux first in some sections to balance representation.
- Include Linux OS image family/version details where Windows OS families are described.
- Clarify which features/settings are available for Linux pools, and provide example JSON for Linux pool creation.
- Note deprecated Windows-only features (Cloud Services Configuration) more prominently and guide users to Linux-compatible alternatives.
Batch
Use the Batch Management .NET library to manage account resources
...cs/blob/main/articles/batch/batch-management-dotnet.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively provides C#/.NET code samples and references Windows-centric authentication and tooling patterns (e.g., DefaultAzureCredential, BatchSharedKeyCredentials) without mentioning or demonstrating how to perform equivalent operations on Linux or macOS. There are no references to cross-platform command-line tools (such as Azure CLI or Bash scripts), nor are there any Linux/macOS-specific instructions or examples. The only alternative mentioned is the Azure portal, which is platform-agnostic, but all automation guidance is .NET-focused.
Recommendations
- Add equivalent examples using Azure CLI and/or REST API calls, which are cross-platform and commonly used on Linux/macOS.
- Explicitly state that the .NET library and code samples work on Linux/macOS (if true), and provide instructions for installing .NET SDK on those platforms.
- Include Bash or PowerShell Core (cross-platform) script examples for common tasks.
- Reference or link to documentation or samples for Python or other cross-platform SDKs where relevant.
- Clarify any platform limitations or prerequisites for running the .NET samples on Linux/macOS.
Batch
Use compute-intensive Azure VMs with Batch
...n/articles/batch/batch-pool-compute-intensive-sizes.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation provides both Windows and Linux guidance for configuring Azure Batch pools with HPC and GPU VM sizes. However, Windows examples and tooling (e.g., PowerShell, Remote Desktop, Microsoft MPI) are presented first and in greater detail, with explicit step-by-step instructions and command lines. Linux examples are present but less detailed, and some sections (e.g., installing MPI on Linux) are missing or referenced only via external links. Windows-specific tools and patterns (PowerShell, RDP) are mentioned without Linux equivalents (e.g., SSH, Bash).
Recommendations
- Provide Linux examples with equal detail and step-by-step instructions, including command lines for driver installation and MPI setup.
- Include Linux-specific tooling and workflows (e.g., SSH, Bash scripts) alongside Windows tools like PowerShell and RDP.
- Ensure that Linux examples are presented with parity in order and prominence to Windows examples.
- Add explicit instructions for installing and configuring MPI on Linux Batch pools, not just links.
- Where Windows-only extensions or tools are mentioned, clarify Linux alternatives or note if none exist.
Batch
Storage and data movement for rendering
...rticles/batch/batch-rendering-storage-data-movement.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation provides more detailed and explicit examples for Windows environments, particularly in the Azure Files section, where mounting instructions and command-line examples are Windows-centric (cmdkey, net use). Linux equivalents for mounting Azure Files are not provided, and Windows tools/patterns (cmdkey, net use) are described before any mention of Linux approaches. The azcopy examples use Windows-style syntax and switches, and there is no parity in showing Linux command-line usage or file system mounting for Azure Files. The blobfuse section is Linux-specific, but lacks the same level of step-by-step guidance and examples as the Windows Azure Files section.
Recommendations
- Add explicit Linux mounting instructions and command-line examples for Azure Files (e.g., using mount.cifs or SMB mounting commands).
- Provide azcopy command examples for both Windows and Linux, highlighting syntax differences.
- Ensure that for every Windows-specific tool or pattern mentioned (cmdkey, net use), the Linux/macOS equivalent is described and illustrated.
- Balance the depth of examples and guidance between Windows and Linux sections, especially for mounting and accessing file shares.
Batch
Create task dependencies to run tasks
...cs/blob/main/articles/batch/batch-task-dependencies.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively provides Windows-centric examples, using 'cmd.exe /c echo' in all code samples and referencing Windows command-line tools. There are no Linux or macOS shell examples (e.g., bash), nor any mention of cross-platform command patterns. This creates friction for users running Batch tasks on Linux pools, as they must adapt the examples themselves.
Recommendations
- Provide equivalent Linux/macOS shell examples (e.g., use '/bin/bash -c "echo ..."' alongside 'cmd.exe /c ...').
- Explicitly mention that the command line for CloudTask should match the OS of the target compute node.
- Add a section or note clarifying cross-platform considerations for task commands.
- Include at least one full example for Linux pools, demonstrating bash usage.
Batch
Persist output data to Azure Storage with Batch service API
...cs/blob/main/articles/batch/batch-task-output-files.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a notable Windows bias. All code samples use C# and Windows-style commands (e.g., 'cmd /c'), with no Linux shell equivalents provided. File path examples use backslashes by default, and Linux compatibility is only mentioned as a note to change slashes. The sample project requires Visual Studio and Windows application packaging, with no mention of Linux or cross-platform alternatives. No Bash or Linux command examples are given, and Windows tools and patterns are referenced exclusively or first.
Recommendations
- Provide equivalent Linux/Bash shell command examples for task creation and output file generation.
- Show file path examples using both Windows (\) and Linux (/) conventions, or use platform-agnostic notation.
- Include instructions for running the sample project on Linux/macOS, such as using .NET Core/SDK and VS Code.
- Reference Linux tools (e.g., tar, zip, bash) for file packaging and output management.
- Add explicit Linux/macOS code samples and clarify any platform-specific requirements or limitations.
Batch
Use the Azure Compute Gallery to create a custom image pool
...zure-docs/blob/main/articles/batch/batch-sig-images.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits moderate Windows bias. Windows tools (PowerShell, RDP) are mentioned before Linux equivalents (Azure CLI, SSH), and examples often reference Windows first. PowerShell is listed as the first way to enumerate supported images, and RDP is described before SSH in portal instructions. There is a lack of explicit Linux-specific command examples (e.g., mounting disks, formatting), and some steps assume familiarity with Windows workflows. While Linux is referenced, parity in examples and guidance is lacking.
Recommendations
- Provide Linux-specific command examples (e.g., mounting and formatting disks using Linux CLI commands).
- List Azure CLI before PowerShell when enumerating supported images, or present both equally.
- In portal instructions, mention SSH before or alongside RDP, and clarify Linux login steps.
- Include explicit Linux and macOS workflow examples where relevant, such as preparing VMs and troubleshooting.
- Ensure all tooling references (CLI, SDKs) are cross-platform and provide links to Linux/macOS installation guides.
Batch
Persist output data to Azure Storage with .NET File Conventions library
...n/articles/batch/batch-task-output-file-conventions.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily focused on .NET and Windows-centric workflows. All code samples are in C#, and instructions reference Visual Studio 2019, a Windows-only IDE. There are no Linux/macOS-specific examples, nor any mention of alternative development environments or tools. The use of WindowsAzure.Storage and lack of cross-platform guidance create friction for Linux/macOS users.
Recommendations
- Provide equivalent code samples for Linux/macOS environments, such as using .NET Core/SDK on Linux.
- Include instructions for running the sample project using cross-platform tools (e.g., VS Code, CLI, or JetBrains Rider).
- Mention how to install and use the Batch File Conventions library on Linux/macOS, including any platform-specific considerations.
- Clarify that the File Conventions library can be used with .NET Core/.NET 6+ on non-Windows platforms.
- Add guidance for building and running the sample project without Visual Studio, using the dotnet CLI.
- Reference alternative storage client libraries if WindowsAzure.Storage is deprecated or Windows-specific.
Batch
Provision a pool with Auto OS Upgrade
...-docs/blob/main/articles/batch/batch-upgrade-policy.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a notable Windows bias. All code examples (REST API and C# SDK) use Windows-specific images and node agent SKUs, with no mention or examples for Linux equivalents. The configuration properties and explanations focus on Windows settings (e.g., windowsConfiguration, enableAutomaticUpdates), and there are no Linux-specific instructions or parity examples. This creates friction for Linux users who may not know how to adapt the instructions for Linux pools.
Recommendations
- Add parallel examples for Linux pools, including REST API and SDK snippets using Linux images (e.g., Ubuntu, CentOS) and Linux node agent SKUs.
- Explicitly document Linux-specific configuration properties (e.g., linuxConfiguration) and any differences in upgrade behavior or requirements.
- Mention both Windows and Linux options in supported OS images and requirements sections.
- Ensure that the order of examples alternates or presents both platforms equally, rather than Windows-first.
- Clarify any platform-specific limitations or considerations for Auto OS Upgrade.
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page exhibits moderate Windows bias. Windows-specific tools (PowerShell) and examples are mentioned before or more prominently than Linux equivalents in several sections, especially in disk preparation and troubleshooting. Some sections provide detailed PowerShell guidance for Windows but only brief or less actionable instructions for Linux. In a few cases, Windows-specific patterns (directory junctions, Windows Services) are discussed in detail, while Linux alternatives (systemd, symlinks) are mentioned but not elaborated. There are also instances where Linux examples are missing or less complete compared to Windows.
Recommendations
- Ensure that Linux CLI and scripting examples (e.g., Bash, shell commands) are provided alongside PowerShell for all relevant operations, such as disk preparation and troubleshooting.
- Present Linux and Windows instructions in parallel, giving equal prominence and detail to both platforms.
- Where Windows-specific patterns (e.g., directory junctions, Windows Services) are discussed, provide equivalent Linux guidance (e.g., symlinks, systemd units) with actionable examples.
- Include sample scripts for Linux (e.g., mounting and formatting disks, collecting logs) similar to the PowerShell samples for Windows.
- Avoid presenting Windows tools or examples first unless there is a clear reason; alternate or combine both platforms in examples.
- Review all sections for parity in troubleshooting and operational guidance, ensuring Linux users can follow along without needing to infer steps from Windows instructions.
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
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively demonstrates creating a pool of Windows compute nodes and provides only Windows command-line examples (using 'cmd' and 'timeout'). There are no instructions, examples, or mentions of Linux pools, Linux VM images, or Linux-compatible task commands. This creates friction for users intending to use Linux nodes or run Linux scripts.
Recommendations
- Include instructions for creating a pool of Linux compute nodes, specifying a popular Linux VM image (e.g., Ubuntu).
- Provide Linux shell command examples (e.g., 'bash -c "env; sleep 90"') alongside Windows examples when demonstrating task creation.
- Explicitly mention that both Windows and Linux pools are supported, and link to documentation on choosing OS images.
- Clarify any differences in environment variables or task output handling between Windows and Linux nodes.
Batch
Persist job and task output to a data store
...ure-docs/blob/main/articles/batch/batch-task-output.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation subtly favors Windows by providing a Windows-specific example in the custom file movement section and omitting explicit Linux/macOS equivalents. No PowerShell or Windows-only tools are mentioned, but the only concrete example for executing post-task scripts is Windows-centric. There are no Linux/macOS shell script examples or references to cross-platform patterns.
Recommendations
- Add equivalent Linux/macOS shell script examples (e.g., using bash) alongside the Windows example in the custom file movement section.
- Explicitly mention that custom scripts can be written in any language and run on any supported OS, providing sample commands for both Windows and Linux/macOS nodes.
- Ensure that examples and instructions are presented in a cross-platform manner, or alternate between Windows and Linux/macOS examples.
- Reference cross-platform tools or patterns where possible.
Medium 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-specific tools and patterns (e.g., RDP, DPAPI, 'cmd.exe') are mentioned before their Linux equivalents, and several code examples default to Windows-centric commands. While Linux is supported and examples are present, Windows scenarios and terminology are often introduced first, and some sections (e.g., secrets management) reference Windows-only technologies without Linux alternatives.
Recommendations
- Ensure Linux and macOS examples are presented alongside Windows examples, ideally in parallel or with equal prominence.
- When mentioning Windows tools (e.g., DPAPI, RDP), immediately provide Linux/macOS equivalents (e.g., GnuPG, SSH, xrdp) and link to relevant documentation.
- Use platform-neutral commands in code samples where possible, or provide both Windows and Linux command-line examples (e.g., 'echo hello world' via 'cmd.exe' and '/bin/bash').
- Add explicit Linux/macOS instructions for secrets management and file sharing, not just Windows-specific solutions.
- Avoid using Windows terminology as the default (e.g., 'cmd.exe') in generic examples; clarify platform differences.
Batch
Use ephemeral OS disk nodes for Azure Batch pools
...b/main/articles/batch/create-pool-ephemeral-os-disk.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page references PowerShell as the only example for programmatically querying VM capabilities, and links to a PowerShell cmdlet in the FAQ. No equivalent Linux or cross-platform CLI (such as Azure CLI or Bash) examples are provided for this task. While the SDK code samples are platform-neutral (Python and C#), the operational guidance for checking VM support is Windows-centric.
Recommendations
- Add Azure CLI and/or Bash examples for querying VM capabilities, especially for 'EphemeralOSDiskSupported'.
- Reference cross-platform tools (Azure CLI, REST API) alongside PowerShell when describing how to check VM series support.
- Ensure that operational instructions do not assume a Windows environment; mention Linux/macOS options explicitly.
- Where PowerShell is referenced, provide equivalent commands for other platforms.
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation provides both Windows and Linux command line examples for task execution, but Windows examples are consistently shown first. Additionally, Windows-specific tools such as 'robocopy', 'MSI', and 'setup.exe' are mentioned as examples for start tasks, with no equivalent Linux tools (e.g., 'cp', 'tar', 'deb', 'rpm', or shell scripts) referenced. This creates a subtle bias toward Windows usage patterns and may leave Linux users without clear guidance for analogous workflows.
Recommendations
- Alternate the order of Windows and Linux examples, or present them side-by-side to avoid implicit prioritization.
- Include Linux equivalents for all Windows-specific tools and patterns mentioned (e.g., suggest 'cp' or 'rsync' instead of 'robocopy', mention '.deb' or '.rpm' packages alongside 'MSI' and 'setup.exe').
- Add explicit Linux/macOS examples for start tasks and other scenarios where only Windows tools are referenced.
- Clarify that all features and workflows are supported on both Windows and Linux compute nodes, and provide links to OS-specific guidance where appropriate.