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 426-436 of 436 flagged pages
Batch
Azure Quickstart - Create a Batch account - Bicep file
...re-docs/blob/main/articles/batch/quick-create-bicep.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment, validation, and cleanup tasks. However, PowerShell examples are given equal prominence to CLI, and PowerShell is a Windows-centric tool. The CLI examples are cross-platform, but in each section, PowerShell is presented as an alternative tab, which may subtly suggest parity or priority. There are no Linux-specific tools or shell examples (e.g., Bash), nor is there explicit mention that Azure CLI is preferred for Linux/macOS users.
Recommendations
- Explicitly state that Azure CLI is cross-platform and recommended for Linux/macOS users.
- Consider listing CLI examples before PowerShell, or labeling PowerShell as 'Windows only'.
- Add a note clarifying that PowerShell examples are for Windows users, while CLI works on all platforms.
- Optionally, provide Bash shell script examples for Linux users, especially for multi-step workflows.
Create Pull Request
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias. Windows-specific executable types and tools (e.g., .exe, .cmd, .bat, PowerShell) are listed first and in more detail than Linux equivalents. Container support examples mention Windows Server images before Linux options. Remote access methods list RDP (Windows) before SSH (Linux). There are no explicit Linux shell command examples or references to Linux-specific tools, and some sections (e.g., container support) focus on Windows images and Docker for Windows, with Linux support only implied or referenced via links.
Recommendations
- List Linux script types (e.g., .sh, bash, Python) before or alongside Windows types when discussing supported executables.
- Provide explicit Linux examples and references, such as shell commands for mounting disks, or using SSH for remote access.
- In sections about container support, mention Linux container images and Docker on Linux first or equally, and provide links to Linux-specific guidance.
- Ensure parity in tool and pattern references (e.g., mention Linux package managers, configuration files, and troubleshooting steps).
- Add Linux-focused examples throughout, especially in sections where only Windows tools or workflows are described.
Batch
Configure node endpoints in Azure Batch pool
...lob/main/articles/batch/pool-endpoint-configuration.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation alternates between Windows (RDP) and Linux (SSH) examples, but consistently presents Windows/RDP examples first in each section. C# is used for Windows pool examples and Python for Linux pool examples, reflecting common platform choices. There is a slight Windows bias in ordering and language/tool selection, but Linux parity is maintained with equivalent examples and explanations.
Recommendations
- Alternate the order of examples so that Linux/SSH examples are sometimes presented first.
- Explicitly state that both C# and Python can be used for either pool type, and provide cross-language code samples where possible.
- Add a summary table comparing RDP (Windows) and SSH (Linux) endpoint configuration to reinforce parity.
- Ensure that introductory sections do not imply Windows is the default or primary use case.
Batch
Batch security and compliance best practices
...cs/blob/main/articles/batch/security-best-practices.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation page generally maintains cross-platform parity, but there are subtle signs of Windows bias. References to Windows-specific tools (such as PowerShell) and documentation links for Windows OS configuration (TLS settings) are more prominent than their Linux equivalents. Windows registry settings and cipher suite ordering are discussed in detail, while Linux-specific security configuration is not. PowerShell is mentioned as a way to discover supported images, with Azure CLI listed second. Windows OS details (such as automatic updates and TLS management) are described before Linux, and links to Windows documentation are provided without Linux counterparts.
Recommendations
- Include Linux-specific examples and links for OS-level security configuration, such as TLS/cipher suite management.
- Provide parity in tooling references: mention Azure CLI before or alongside PowerShell, and include Bash or shell script examples where relevant.
- Balance the order of OS discussions, alternating between Windows and Linux or grouping OS-specific guidance together.
- Add references to Linux documentation for managing security settings (e.g., OpenSSL, SSH, iptables, etc.).
- Clarify which features or recommendations apply equally to both Windows and Linux, and note any differences.
Batch
Create a simplified node communication pool without public IP addresses
...tch/simplified-node-communication-pool-no-public-ip.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits mild Windows bias in troubleshooting sections, where Windows PowerShell commands (Test-NetConnection) are shown before Linux equivalents (nc), and the Windows command is more fully documented. There are no Linux/macOS-specific examples for other tasks, such as connecting to compute nodes, and remote connection patterns (jumpbox, Bastion) are described generically without OS-specific guidance. The main configuration and API examples use cross-platform tools (REST API, ARM templates), but command-line troubleshooting leans Windows-first.
Recommendations
- Present Linux/macOS command-line examples before or alongside Windows equivalents, with equal detail.
- Include explicit Linux/macOS instructions for connecting to compute nodes (e.g., using SSH from a jumpbox).
- Where PowerShell is mentioned, also provide Bash or other shell examples for parity.
- Clarify that Azure CLI and portal steps are cross-platform, and note any OS-specific caveats.
- Expand troubleshooting steps to cover common Linux/macOS diagnostic tools (e.g., curl, telnet, dig for DNS).
Batch
Role-based access control for Azure Batch service
...main/articles/batch/batch-role-based-access-control.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation page does not provide any command-line examples, scripts, or tooling instructions for either Windows (e.g., PowerShell) or Linux (e.g., Bash, CLI). All instructions are given via the Azure Portal GUI, which is cross-platform. However, there is a notable absence of any CLI-based examples (such as Azure CLI or Azure PowerShell), which are commonly used on both Windows and Linux. This omission can be considered a 'missing_linux_example' bias, as Linux users often rely on CLI instructions for automation and scripting, and the absence of such examples may hinder parity.
Recommendations
- Add Azure CLI examples for all major tasks (e.g., assigning RBAC roles, listing roles, creating custom roles) alongside portal instructions. Azure CLI is cross-platform and widely used on Linux.
- If including PowerShell examples, ensure equivalent Bash/Azure CLI examples are provided and presented with equal prominence.
- Explicitly mention that all portal instructions are applicable from any OS, but provide links or inline examples for CLI-based workflows to support automation and Linux-first users.
- Consider a 'Command-line' section for each major operation, showing both Azure CLI and PowerShell (if relevant), to ensure Linux and Windows users have clear, platform-agnostic guidance.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/account-key-rotation.md
...-docs/blob/main/articles/batch/account-key-rotation.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation page describes how to rotate Batch account shared keys, but only provides instructions for using the Azure portal and does not include any command-line examples. There is no mention of platform-specific tools, but the absence of CLI (such as Azure CLI or PowerShell) examples means there is no parity for users who may prefer or require Linux-based workflows.
Recommendations
- Add Azure CLI examples for key rotation, as the Azure CLI is cross-platform and commonly used on Linux.
- If PowerShell examples are added, ensure they are accompanied by equivalent Azure CLI commands.
- Explicitly mention that the procedure can be performed from any OS using the Azure CLI, and provide sample commands.
- Consider including REST API examples for advanced users or automation scenarios, which are also platform-agnostic.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/pool-endpoint-configuration.md
...lob/main/articles/batch/pool-endpoint-configuration.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation alternates between Windows (RDP) and Linux (SSH) examples, but consistently presents Windows/RDP examples before Linux/SSH examples in each section. Both platforms are covered with equivalent code samples and explanations, and there are no missing Linux examples or exclusive references to Windows tools or PowerShell. However, the ordering may subtly prioritize Windows scenarios.
Recommendations
- Alternate the order of examples in each section, sometimes presenting Linux/SSH first.
- Add a short statement at the beginning clarifying that both Windows and Linux pools are equally supported, and that examples are provided for both.
- Ensure parity in the depth and detail of examples for both platforms.
- Consider grouping examples by scenario (e.g., 'Allow remote access', 'Deny remote access') and presenting both Windows and Linux code side by side for each scenario.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/account-key-rotation.md
...-docs/blob/main/articles/batch/account-key-rotation.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any command-line examples or tooling instructions for rotating Batch account keys, nor does it mention any platform-specific tools. However, it also does not provide any examples for Linux or cross-platform command-line usage, such as Azure CLI or Bash, which are commonly used on Linux. The only method described is via the Azure portal, which is platform-agnostic, but the absence of CLI or script-based examples may disadvantage Linux users who prefer or require automation.
Recommendations
- Add Azure CLI examples for rotating Batch account keys, as the CLI is cross-platform and widely used on Linux.
- Include PowerShell examples only if paired with equivalent Bash or CLI examples.
- Explicitly mention that the Azure portal method works on all platforms, but provide automation options for users who do not use a GUI.
- Consider adding a section on scripting key rotation for CI/CD pipelines, with both Linux (Bash/CLI) and Windows (PowerShell) examples.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/pool-file-shares.md
...zure-docs/blob/main/articles/batch/pool-file-shares.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation claims to cover both Linux and Windows pools but does not provide any concrete examples or instructions for either platform. However, it notably lacks any Linux-specific guidance or examples for mounting Azure file shares, which is a common area where Windows/PowerShell examples are often prioritized or exclusively provided.
Recommendations
- Add explicit, step-by-step instructions for mounting Azure file shares on Linux Batch pool nodes, including example commands (e.g., using mount.cifs or SMB utilities).
- Ensure parity by providing both Linux (bash/CLI) and Windows (PowerShell/GUI) examples side by side.
- Reference Linux-specific troubleshooting and best practices for Azure Files (e.g., required packages, handling credentials securely).
- Clearly indicate in each section which instructions apply to Linux, Windows, or both.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/resource-files.md
.../azure-docs/blob/main/articles/batch/resource-files.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides only C# code examples and general Azure Batch concepts, with no mention of Windows-specific tools or patterns. However, it lacks any Linux- or cross-platform-specific examples, shell commands, or references to Linux environments, which may make it less accessible to users working in Linux or non-Windows environments.
Recommendations
- Add equivalent Linux shell (bash) or Python examples for creating and using resource files, especially for common scenarios like downloading files from Azure Storage.
- Include notes or sections on how resource files are handled on Linux Batch nodes, such as file permissions, path conventions, or troubleshooting tips.
- Reference cross-platform tools (e.g., az CLI, curl, wget) alongside or instead of Windows-centric tools.
- Explicitly state that the examples are cross-platform where applicable, or provide guidance for both Windows and Linux users.
- If PowerShell or Windows command-line examples are added in the future, ensure Linux equivalents are provided in parallel.