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 201-225 of 436 flagged pages
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/create-pool-ephemeral-os-disk.md
...b/main/articles/batch/create-pool-ephemeral-os-disk.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation shows a Windows bias by referencing PowerShell as the only example for programmatically checking VM series support for ephemeral OS disks, without mentioning or providing equivalent Linux/CLI commands. The mention of PowerShell occurs before any cross-platform alternatives, and there are no Linux shell or Azure CLI examples for this task. While the code examples for SDK usage are cross-platform (Python and C#), the operational guidance and tooling references are Windows-centric.
Recommendations
- Provide equivalent Azure CLI and/or Bash examples for checking VM series support for ephemeral OS disks, alongside or before PowerShell examples.
- Explicitly mention that PowerShell is available cross-platform, or clarify if the example is Windows-only.
- Ensure that operational instructions reference both Windows and Linux tools where applicable.
- Add a note or section for Linux users, highlighting how to perform the same checks and configurations using Linux-native tools.
Create Pull Request
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/quick-create-portal.md
...e-docs/blob/main/articles/batch/quick-create-portal.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by exclusively guiding users to create a pool of Windows compute nodes, specifying Windows Server 2019 as the OS, and providing only Windows command-line examples (using 'cmd', 'set', and 'timeout'). There is no mention of Linux node options, nor are there equivalent Linux shell command examples. The documentation does not mention or demonstrate how to use Linux-based pools or tasks, nor does it provide parity for Linux users.
Recommendations
- Include instructions for creating a pool of Linux compute nodes, specifying a common Linux distribution (e.g., Ubuntu).
- Provide Linux shell command equivalents for the task command line (e.g., using 'bash', 'env', and 'sleep').
- Present both Windows and Linux options side by side or clearly indicate how to adapt the steps for Linux environments.
- Mention that Azure Batch supports both Windows and Linux pools, and link to documentation for both.
- Ensure screenshots and UI steps clarify where OS selection can be changed, and what options are available.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-pool-vm-sizes.md
...e-docs/blob/main/articles/batch/batch-pool-vm-sizes.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation consistently lists PowerShell (a Windows-centric tool) as the first example for querying supported VM sizes and images, and refers to PowerShell-specific cmdlets throughout. While Azure CLI (cross-platform) and REST API options are also provided, there are no Linux shell or scripting examples, and the ordering and emphasis suggest a Windows-first perspective. There is no mention of Linux-native tools or patterns for interacting with Azure Batch, nor any Linux-specific considerations or examples.
Recommendations
- Alternate the order of examples so that Azure CLI (which is cross-platform and popular on Linux) appears before PowerShell, or present both together without prioritizing one.
- Include Linux shell (bash) scripting examples for querying and processing Azure Batch information, such as using jq to parse JSON output from Azure CLI.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide example shell prompts (e.g., $ for bash) to reinforce cross-platform usage.
- If relevant, add Linux-specific considerations or tips (e.g., environment variable handling, file system paths) when discussing VM images or node configuration.
- Avoid referring to PowerShell as the primary or default tool, and instead present it as one of several options.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-ci-cd.md
...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
Summary
The documentation demonstrates a Windows bias by exclusively using Windows-based Batch pools and Windows application packages (specifically the Windows 64-bit version of FFmpeg). ARM templates are configured for Windows nodes only, and there are no Linux pool or application examples. The build and deployment steps focus on Windows artifacts, and the agent specification is set to 'windows-latest' without mention of Linux alternatives. While there is a brief note that Azure Pipelines and Batch support Linux, no Linux-specific instructions, templates, or examples are provided.
Recommendations
- Provide parallel examples for Linux-based Batch pools, including ARM templates with Linux VM images and nodeAgentSkuId for Linux.
- Include instructions for downloading and packaging the Linux version of FFmpeg, and show how to deploy it to Linux nodes.
- Demonstrate how to set the agent specification to 'ubuntu-latest' or another Linux agent in Azure Pipelines.
- Add Linux-specific YAML build and deployment steps, highlighting any differences in file packaging or deployment.
- Wherever Windows-specific tools or patterns are mentioned (such as PowerShell Core), offer equivalent Bash or Linux shell alternatives.
- Ensure screenshots and code snippets reflect both Windows and Linux scenarios where applicable.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-task-output.md
...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 a Windows bias by providing a command-line example only for Windows nodes (using .exe files), omitting equivalent Linux/bash examples. The only explicit example of invoking a custom script is for Windows, and there is no mention of Linux shell scripts or Linux-specific patterns. Additionally, the documentation refers to .NET and C# libraries first, with no parity for other languages or platforms, and does not mention Linux tools or patterns.
Recommendations
- Provide equivalent Linux/bash examples alongside Windows examples, e.g., show how to call a shell script (e.g., './doMyWork.sh && ./uploadMyFilesToSql.sh') after the Windows .exe example.
- Mention both Windows and Linux nodes explicitly when discussing custom file movement solutions, and provide guidance for both environments.
- Include references to cross-platform tools and patterns, not just .NET/C# libraries, and highlight any SDKs or libraries available for other languages.
- Where possible, present examples in a platform-neutral way, or always provide both Windows and Linux variants.
- Clarify that Azure Batch supports both Windows and Linux nodes, and link to relevant documentation for each.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-virtual-network.md
...docs/blob/main/articles/batch/batch-virtual-network.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. While it is mostly platform-agnostic in its main guidance, several sections either mention Windows tools or patterns first, provide more detail for Windows, or lack parity in Linux-specific examples. For example, remote access ports are listed as '3389 (Windows), 22 (Linux)', with Windows mentioned first. There are references to PowerShell and RDP (Windows Remote Desktop) without equivalent Linux command-line or SSH examples. The prerequisites mention Azure PowerShell before Azure CLI, and there are no explicit Linux command-line or shell examples for creating or managing resources. The documentation assumes familiarity with Windows-centric tooling and patterns, and Linux users may find the guidance less tailored to their workflows.
Recommendations
- When listing remote access ports, alternate the order or mention Linux (SSH/22) first in some places to balance visibility.
- Provide explicit Linux command-line (bash/CLI) examples alongside or before PowerShell examples, especially in prerequisites and resource creation steps.
- Mention Azure CLI as prominently as Azure PowerShell in all relevant sections, and provide equivalent instructions for both.
- Reference SSH and Linux-native tools (e.g., scp, sftp) alongside RDP and Windows tools when discussing remote access.
- Where screenshots or UI elements are shown, clarify that the instructions are platform-neutral or provide notes for Linux users if there are differences.
- Add a section or callout for Linux users, highlighting any special considerations or best practices for Linux-based Batch pools.
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 exhibits a Windows bias by providing only a Windows-based VM image example (MicrosoftWindowsServer) and node agent SKU (batch.node.windows amd64) in the code sample, with no equivalent Linux example or mention. The example uses Windows-specific values and does not demonstrate how to update a pool to use a Linux image or node agent. There is no discussion of Linux VM images, node agent SKUs, or Linux-specific considerations, and the only concrete example is for Windows. This may lead Linux users to feel unsupported or unclear about the process for Linux pools.
Recommendations
- Add a parallel example demonstrating how to update a pool to use a Linux VM image and the appropriate Linux node agent SKU.
- Explicitly mention both Windows and Linux options in all relevant sections, including lists of supported publishers, offers, and SKUs.
- In code samples, provide both Windows and Linux variants, or use a generic template with comments explaining how to substitute for either OS.
- Include a table or section listing common Windows and Linux VM image references and node agent SKUs for Batch pools.
- Review all examples and ensure Linux is given equal prominence and clarity as Windows.
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 mild Windows bias. Windows tools and patterns (e.g., PowerShell, RDP) are often mentioned first or exclusively, and some examples or instructions are more detailed for Windows than Linux. While Linux is referenced, parity in examples and tool coverage is lacking in some sections.
Recommendations
- When listing supported images or tools, present Azure CLI (cross-platform) examples before or alongside PowerShell, and ensure both Windows and Linux are equally represented.
- Provide explicit Linux command-line examples (e.g., SSH connection commands, Linux-specific disk mounting instructions) where only Windows (RDP) or PowerShell examples are given.
- In portal instructions, detail both RDP (Windows) and SSH (Linux) connection steps, including example commands for SSH.
- Ensure that all code snippets and tool references (e.g., for checking purchase plan info, mounting disks, etc.) have both Windows and Linux variants, or clarify when a step is OS-agnostic.
- Where possible, use neutral language (e.g., 'Connect via RDP (Windows) or SSH (Linux)') and avoid always listing Windows first.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-application-packages.md
...blob/main/articles/batch/batch-application-packages.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias in several ways: all code examples are in C# and use Windows-centric command lines (e.g., 'cmd /c'), with no Linux shell equivalents provided. The only detailed example of application execution uses Windows paths and environment variable conventions first, with Linux differences mentioned only as an aside. There are no Linux-specific code snippets or shell command examples, and the documentation consistently references Windows node configuration and tools before Linux. This may hinder Linux users from easily applying the guidance.
Recommendations
- Provide parallel Linux/bash examples for all command-line and code snippets, especially for task command lines and environment variable usage.
- Include at least one example of deploying and executing an application package on a Linux compute node, using bash syntax and Linux file paths.
- When describing environment variables and application package paths, present Linux and Windows formats side-by-side, rather than Windows first.
- Mention Linux node configuration and requirements with equal prominence as Windows, including any differences in application ID rules or file system layout.
- If possible, include code samples in additional languages (e.g., Python) that are popular in Linux environments, or at least reference their documentation.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-upgrade-policy.md
...-docs/blob/main/articles/batch/batch-upgrade-policy.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only Windows-based examples for both REST API and SDK usage. The sample configurations and code exclusively reference Windows images (e.g., MicrosoftWindowsServer, WindowsServer, batch.node.windows amd64) and Windows-specific properties (windowsConfiguration, enableAutomaticUpdates). There are no examples or guidance for provisioning Linux-based pools, nor are Linux image references or configuration options discussed. The documentation also references Windows Update and in-VM patching in a way that is specific to Windows, without mentioning the Linux equivalents.
Recommendations
- Add parallel examples for Linux pools, including REST API and SDK (C#) snippets that use Linux image references (e.g., Ubuntu, CentOS) and nodeAgentSkuId values appropriate for Linux.
- Explicitly document Linux-specific configuration options, such as linuxConfiguration blocks, and discuss any differences in automatic OS upgrade behavior between Windows and Linux.
- Mention Linux update mechanisms (e.g., package manager updates) where Windows Update is discussed, or clarify if/how automatic upgrades differ for Linux nodes.
- Ensure that references to image publishers, offers, and SKUs include both Windows and Linux options, and provide guidance for selecting Linux images.
- Where Windows-specific properties are required (e.g., windowsConfiguration), clarify their Linux equivalents or state when they are not applicable.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/best-practices.md
.../azure-docs/blob/main/articles/batch/best-practices.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. In several sections, Windows tools (such as PowerShell) are mentioned before or more prominently than their Linux equivalents. Some examples and guidance are provided only for Windows (e.g., using PowerShell cmdlets to enumerate disks), while Linux examples are less detailed or missing. Additionally, certain recommendations (like using pool scope for short tasks) specifically reference Windows nodes, and Windows-specific issues (directory junctions, Windows Services) are discussed in more detail than their Linux counterparts.
Recommendations
- Ensure that for every Windows/PowerShell example or tool mentioned, a Linux/bash equivalent is provided with equal detail and prominence.
- When listing tools or APIs (e.g., for discovering EOL dates), mention cross-platform options first (such as Azure CLI or REST API), or present both Windows and Linux options together.
- Expand sections that currently only provide Windows-specific guidance (e.g., disk preparation, directory management) to include equivalent Linux commands and best practices.
- Balance the discussion of OS-specific pitfalls (e.g., directory junctions in Windows) with Linux-specific considerations (e.g., symlink handling, systemd service management).
- Where recommendations are OS-specific (such as 'Use pool scope for short tasks on Windows nodes'), clarify if and how they apply to Linux nodes.
- Review for any missing Linux examples, especially in sections where only PowerShell or Windows tools are referenced, and add bash or Linux-native command examples.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-user-accounts.md
...e-docs/blob/main/articles/batch/batch-user-accounts.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation exhibits a Windows-first bias in several areas. Windows tools and patterns (such as 'cmd.exe', 'cmd /c', and references to Windows Data Protection API) are used in code examples and scenarios, often without Linux equivalents or with Linux-specific details provided later or omitted. Powershell/Windows command patterns are used in code snippets for .NET, Java, and Python, and Windows terminology is frequently introduced before Linux alternatives. Some Linux-specific configuration is present, but Linux command-line examples are missing, and Windows tools are referenced without Linux alternatives.
Recommendations
- Provide Linux shell command examples (e.g., using '/bin/bash -c' instead of 'cmd /c') alongside or before Windows examples in all code snippets.
- When referencing Windows-specific tools (such as DPAPI), include equivalent Linux approaches (e.g., GnuPG, file permissions, or other secret management solutions).
- Ensure that all code samples that show Windows VM configuration also show Linux VM configuration, and vice versa, with parity in detail and explanation.
- Avoid using Windows terminology or tools as the default; instead, present both Windows and Linux options equally, or alternate which is presented first.
- In the 'Update your code' section, provide Linux-specific migration guidance if any differences exist.
- Add explicit Linux SSH usage examples for running tasks and managing user accounts, not just configuration.
- Review all scenarios and ensure Linux is treated as a first-class platform, not an afterthought.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/virtual-file-mount.md
...re-docs/blob/main/articles/batch/virtual-file-mount.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is used as the primary scripting interface for both Windows and Linux examples, rather than showing native Linux shell commands. In several sections, Windows-specific tools and patterns (such as 'cmdkey', 'net use', and RDP) are described in detail, sometimes before their Linux equivalents. Troubleshooting and manual mounting instructions also emphasize Windows tools and workflows, with Linux alternatives provided but less prominently. Native Linux command-line examples (e.g., using 'mount' or 'smbclient') are missing.
Recommendations
- Provide native Linux shell (bash) command examples for mounting file systems, in addition to or instead of PowerShell for Linux.
- When describing mounting and troubleshooting workflows, present Linux and Windows instructions in parallel, or lead with Linux examples where appropriate.
- Include Linux-native troubleshooting steps (e.g., using 'mount', 'dmesg', 'journalctl', or 'lsblk') alongside Windows tools.
- Reference Linux documentation and tools (such as 'mount.cifs', 'smbclient', or 'systemctl') as prominently as Windows tools.
- Ensure that all code samples and manual steps are equally detailed for both platforms, and avoid assuming PowerShell is the default interface for Linux users.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-ci-cd.md
...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
Summary
The documentation demonstrates a Windows bias in several ways: it explicitly states that the example deploys Windows software on Windows-based Batch nodes, uses a Windows-specific FFmpeg build, and the ARM template for the Batch pool is hardcoded to use Windows Server images. There are no parallel Linux examples, and the repository setup and pipeline instructions only reference Windows artifacts. Additionally, the agent specification in the pipeline is set to 'windows-latest', and PowerShell Core is used for scripting, with no mention of Bash or Linux agents.
Recommendations
- Provide parallel Linux-based examples throughout the documentation, including ARM templates for Linux Batch pools (e.g., using Ubuntu images) and instructions for deploying Linux software.
- Include instructions for downloading and packaging a Linux build of FFmpeg, and update the repository structure to accommodate both Windows and Linux application packages.
- Show how to set up the pipeline using a Linux agent (e.g., 'ubuntu-latest') and provide Bash script alternatives for Azure CLI tasks.
- Clearly state at the beginning that both Windows and Linux are supported, and offer readers a choice of which path to follow.
- Where possible, use OS-agnostic language and tools, or provide both Windows and Linux command examples side by side.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-account-create-portal.md
...lob/main/articles/batch/batch-account-create-portal.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a bias toward Windows by providing only PowerShell commands (Get-AzMarketplaceTerms, Set-AzMarketplaceTerms) for accepting legal terms, without offering equivalent Azure CLI or Bash examples. The 'Other Batch account management options' section lists PowerShell cmdlets before Azure CLI, and no Linux shell or cross-platform command-line examples are given for key configuration steps. This may hinder Linux users or those preferring cross-platform tools.
Recommendations
- Provide equivalent Azure CLI commands for all PowerShell examples, especially for accepting legal terms and managing Batch accounts.
- When listing management tools, mention Azure CLI before or alongside PowerShell cmdlets to avoid implying a Windows-first approach.
- Include Bash or shell script examples where appropriate, or clarify that steps can be performed from any OS using the Azure CLI.
- Explicitly state that all portal-based steps are OS-agnostic, and provide links to cross-platform documentation where available.
- Consider adding a table or section summarizing command-line options for both Windows (PowerShell) and Linux/macOS (Azure CLI/Bash).
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-apis-tools.md
...zure-docs/blob/main/articles/batch/batch-apis-tools.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates a mild Windows bias. PowerShell cmdlets are listed first among command-line tools, and the use of Remote Desktop (RDP) for node access is highlighted without mentioning SSH as a Linux equivalent. While the Azure CLI is described as cross-platform and Batch Explorer is available for all OSes, the overall pattern places Windows tools and workflows before Linux alternatives, and omits explicit Linux-native examples or instructions.
Recommendations
- List Azure CLI before PowerShell in the command-line tools section to emphasize cross-platform parity.
- When mentioning RDP for node access, also mention SSH for Linux nodes, with a link to instructions for SSH access.
- Include explicit examples or references for Linux users, such as Bash scripts or Linux shell commands, alongside or before Windows/PowerShell examples.
- Ensure that any tool or workflow described (such as file downloads or node access) includes Linux-relevant instructions or notes.
- Consider adding a table or section that summarizes OS-specific guidance for common developer tasks in Azure Batch.
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 First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific file types and installation methods (such as .exe and .msi files) without providing equivalent Linux examples or mentioning Linux package formats. There are no examples or guidance for Linux tools, commands, or installation patterns, and the only executable and installer formats mentioned are Windows-centric.
Recommendations
- Include Linux-specific examples alongside Windows ones, such as referencing .sh scripts, .tar.gz archives, or .deb/.rpm packages.
- When discussing installation commands, provide both Windows (e.g., msiexec, .exe) and Linux (e.g., bash install.sh, dpkg -i, rpm -i) equivalents.
- Mention Linux tools and patterns for copying and installing applications, such as using wget, curl, scp, or package managers (apt, yum).
- Avoid assuming the use of Windows by default; explicitly state that the guidance applies to both Windows and Linux nodes, and clarify any differences.
- Provide example start task command lines for both Windows (cmd, PowerShell) and Linux (bash, shell scripts).
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
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page focuses exclusively on .NET and C# examples, which are most commonly associated with Windows development. It references the Azure portal and uses terminology such as 'Windows Azure Service Management API', and all code samples are in C#. There are no examples or guidance for Linux users, such as command-line registration with Azure CLI, nor are there any cross-platform code samples (e.g., Python, Java, or REST). The documentation implicitly assumes a Windows development environment and does not address Linux or macOS workflows.
Recommendations
- Include examples for registering applications using the Azure CLI and Azure PowerShell, making clear which commands work cross-platform.
- Provide code samples in additional languages (such as Python or Java) that are commonly used on Linux.
- Clarify that the .NET library and authentication flows are supported on Linux and macOS, and provide any necessary setup instructions.
- Reference cross-platform tools and workflows (such as VS Code, Docker, or REST API usage) alongside or before Windows-specific tools.
- Avoid using 'Windows Azure' terminology unless specifically referring to legacy services; use 'Azure' for modern, cross-platform services.
- Add a section or callout for Linux/macOS users, highlighting any differences or additional steps required.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-application-packages.md
...blob/main/articles/batch/batch-application-packages.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a clear Windows bias. All code examples are in C# and use Windows-centric command lines (e.g., 'cmd /c'), with no Linux shell equivalents provided. The only virtual machine image example is for Windows Server, and environment variable usage is explained for both platforms, but only Windows command syntax is shown in executable examples. There are no Linux-specific code samples, shell commands, or references to Linux tools or patterns.
Recommendations
- Provide parallel Linux examples for all code snippets, especially for task command lines (e.g., show both 'cmd /c ...' and '/bin/bash -c ...').
- Include examples of creating pools with Linux VM images (e.g., Ubuntu) alongside the Windows example.
- Demonstrate how to reference and execute installed applications on Linux nodes using appropriate shell syntax.
- Mention Linux-specific considerations (such as file permissions, path separators, and case sensitivity) where relevant.
- Balance the order of presentation so that Linux and Windows are treated equally (e.g., alternate or combine examples, rather than always presenting Windows first).
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
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation exhibits a Windows bias by presenting Windows terminology and tools first (e.g., RDP before SSH), providing code examples that default to Windows node agent SKUs, and omitting explicit Linux-specific examples or commands. References to Windows-specific tools and patterns (such as RDP and nodeAgentSkuId for Windows) are more prominent, while Linux equivalents are only mentioned in passing or as secondary options.
Recommendations
- Provide parallel Linux-focused examples alongside Windows ones, including explicit nodeAgentSkuId values for Linux pools.
- When listing connection methods, mention SSH (Linux) before or alongside RDP (Windows), or present both equally.
- Include sample code snippets and REST API request bodies for creating Linux-based pools, not just Windows.
- Reference Linux tools and workflows (e.g., bash, Linux CLI commands) explicitly in relevant sections.
- Ensure that all guidance (such as for Packer or image preparation) includes both Linux and Windows links and steps, not just Windows or generic instructions.
- Avoid defaulting to Windows-specific values (like 'batch.node.windows amd64') in code samples; provide Linux alternatives or clarify how to select the appropriate value.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-compute-node-environment-variables.md
...cles/batch/batch-compute-node-environment-variables.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation generally presents Windows tools and patterns before Linux equivalents, such as listing 'cmd.exe' before '/bin/sh' and using Windows-style path examples and syntax. There is a tendency to describe Windows-specific details first, and some examples (e.g., directory postfixes) use Windows path separators without showing Linux equivalents. There are also references to Windows-specific environment variable naming conventions and tools, with less emphasis or detail for Linux.
Recommendations
- Present Linux and Windows examples side-by-side, or alternate which platform is shown first to avoid implicit prioritization.
- For directory and path examples, always show both Windows (backslash) and Linux (slash) formats.
- Where environment variable naming conventions differ (e.g., underscores vs. hash), clearly document both and provide explicit Linux examples.
- Expand Linux-specific guidance, such as showing how to use shells other than /bin/sh (e.g., bash), and clarify any differences in behavior.
- Avoid using only Windows tools (e.g., 'cmd.exe') in explanations; always provide the Linux equivalent with equal prominence.
- Include Linux-specific notes where features are not available or behave differently, and ensure parity in example depth and clarity.
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 a Windows bias by describing Windows-specific paths and behaviors first and in more detail, providing a detailed table of Windows host/container paths, and omitting equivalent Linux path mappings. There are no Linux-specific code or path examples, and the documentation references Windows drive letters and conventions exclusively in path tables.
Recommendations
- Add a parallel table showing 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 for configuring container isolation, including sample paths and mount behaviors.
- Ensure that explanations and examples are presented in a platform-neutral order or provide Linux and Windows information side by side.
- Reference Linux tools and conventions where appropriate, not just Windows drive letters and paths.
- Clarify any platform-specific differences in behavior, and provide guidance for both Windows and Linux users equally.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-automatic-scaling.md
...cs/blob/main/articles/batch/batch-automatic-scaling.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a Windows bias in several ways: .NET (C#) and Windows-centric examples are consistently presented first and in greater detail, including code snippets that use Windows VM images (e.g., MicrosoftWindowsServer) and node agent SKUs for Windows. PowerShell and .NET SDKs are emphasized, with only a single Python example provided for Linux (Ubuntu) and no Bash/CLI or Linux shell examples. There are no explicit Linux command-line or scripting examples, and Windows terminology and tools are referenced more frequently and prominently than their Linux equivalents.
Recommendations
- Provide Linux-first or side-by-side examples for all SDKs, including Bash/CLI and Python, not just .NET/C#.
- Include explicit Linux VM image references and node agent SKUs in .NET and other language examples, not just Windows.
- Add examples using Azure CLI and Bash scripts for common operations (e.g., creating pools, enabling autoscale), to complement PowerShell and .NET code.
- Ensure that Linux tools and workflows are mentioned with equal prominence and detail as Windows/PowerShell/.NET equivalents.
- Review terminology and ordering to avoid always listing Windows/PowerShell/.NET first; alternate or parallelize with Linux/Python/CLI where possible.
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' and Windows environment variable syntax), referencing Windows file paths (with backslashes), and omitting any Linux or cross-platform shell examples. There is no mention of Bash, sh, or Linux-specific command lines, nor are there notes about cross-platform compatibility or how to adapt the examples for Linux compute nodes.
Recommendations
- Provide parallel Linux/Bash shell examples for all command-line snippets (e.g., use 'bash -c' or 'sh -c' and appropriate environment variable and path syntax).
- Explicitly mention that Batch compute nodes can run both Windows and Linux, and clarify any differences in job preparation/release task scripting.
- Add a section or callout explaining how to write cross-platform scripts for job preparation and release tasks, including tips for detecting the OS and using portable commands.
- Update sample output and file paths to include Linux-style paths (forward slashes) and environment variable syntax ($VAR).
- Where Windows tools or patterns are mentioned, provide Linux equivalents (e.g., 'del' vs. 'rm', '%VAR%' vs. '$VAR').
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
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-based examples and tools. The only detailed code samples are in C# using the Batch .NET library, which is most commonly used on Windows. The .NET example for pool creation uses a Windows Server image, and there are no equivalent Linux-focused .NET code samples. While the REST API example uses Ubuntu, there are no Linux shell, Bash, or cross-platform scripting examples. The GitHub sample project is a C# console application, further reinforcing the Windows/.NET focus. There is no mention of Linux-specific tools, shell commands, or cross-platform SDKs (e.g., Python, CLI).
Recommendations
- Add Linux-focused .NET code samples, e.g., using an Ubuntu image in the VirtualMachineConfiguration section.
- Provide equivalent examples using the Azure Batch Python SDK, which is widely used on Linux.
- Include Bash or shell command examples for common operations (e.g., using Azure CLI to create pools and tasks).
- Mention and link to cross-platform tools (such as Azure CLI and Python SDK) alongside or before Windows/.NET tools.
- Ensure that code snippets and sample projects are available in multiple languages and platforms, not just C#/.NET.
- Explicitly state that Azure Batch supports both Windows and Linux nodes, and provide parity in documentation examples.