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 376-400 of 436 flagged pages
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/accounts.md
...ftDocs/azure-docs/blob/main/articles/batch/accounts.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page focuses on conceptual information about Azure Batch and Storage accounts, but where it mentions programmatic creation and management, it only references the Azure portal and the Batch Management .NET libraryβboth of which are more commonly associated with Windows environments. There are no examples or mentions of Linux-friendly tools (such as Azure CLI, Bash, or Python SDK), nor are cross-platform command-line options presented. This creates a subtle Windows-first bias and omits Linux parity in tooling guidance.
Recommendations
- Include examples and references for creating and managing Batch accounts using the Azure CLI, which is cross-platform and widely used on Linux.
- Mention and link to documentation for other SDKs (such as Python, Java, or Node.js) that are commonly used in Linux environments.
- When listing programmatic options, present cross-platform tools (like Azure CLI) before or alongside Windows-centric tools (like .NET library).
- Add explicit Linux/Bash command-line examples where relevant, especially for common tasks like associating storage accounts.
- Review and update the 'Next steps' section to include links to cross-platform management options, not just the portal and .NET.
Create Pull Request
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
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page lacks Linux-specific examples and mentions a Windows command-line pattern before any mention of Linux equivalents. There are no Linux or cross-platform command-line examples, and the only explicit example for running a custom script refers to a Windows node and Windows executables.
Recommendations
- Add equivalent Linux/bash examples wherever a Windows command-line or executable is referenced (e.g., show both 'doMyWork.exe && uploadMyFilesToSql.exe' and './doMyWork.sh && ./uploadMyFilesToSql.sh').
- Explicitly mention that custom file movement solutions can be implemented on both Windows and Linux nodes, and provide guidance for both.
- Include references or links to cross-platform tools and scripting practices, not just .NET/C# libraries.
- Ensure that examples and recommendations are presented in a platform-neutral manner, or that both Windows and Linux approaches are given equal prominence.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/account-move.md
...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 how to move an Azure Batch account using the Azure portal and ARM templates, with all instructions and UI references tailored to the Azure portal experience. There are no command-line examples (such as Azure CLI, PowerShell, or Bash scripts), and no mention of Linux or cross-platform tooling. The steps and screenshots implicitly assume a Windows-centric workflow, as the Azure portal is often associated with Windows users, and there is no guidance for users who prefer or require command-line or automation approaches common on Linux.
Recommendations
- Add equivalent instructions for moving a Batch account using the Azure CLI, which is cross-platform and widely used on Linux.
- Include PowerShell examples for Windows users, but ensure CLI/Bash examples are given equal prominence.
- Explicitly mention that the Azure portal is accessible from any OS, but provide alternative workflows for users who prefer not to use the portal.
- Provide downloadable sample scripts (Bash, CLI, PowerShell) for exporting, modifying, and deploying ARM templates.
- Ensure that any references to tools or workflows are not Windows-specific, or provide Linux/macOS alternatives where relevant.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-cli-templates.md
...e-docs/blob/main/articles/batch/batch-cli-templates.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page generally aims for cross-platform parity by referencing the Azure CLI and mentioning support for Windows, Mac, and Linux. However, in the file transfer section, all example paths use Windows-style paths (e.g., c:\source_videos\*.mp4), and there are no equivalent Linux/macOS path examples. This presents a subtle 'windows_first' and 'missing_linux_example' bias, as Linux users may not immediately recognize how to adapt the commands for their environment.
Recommendations
- For every CLI example that uses a Windows-style path, provide an equivalent Linux/macOS example (e.g., /home/user/source_videos/*.mp4).
- Explicitly mention that the Azure CLI commands work on all supported platforms and that file paths should be adapted to the user's OS.
- Where possible, use OS-agnostic placeholder paths in examples, or provide both Windows and Linux/macOS variants side by side.
- Add a note or callout reminding users to adjust file paths for their operating system.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-aad-auth.md
.../azure-docs/blob/main/articles/batch/batch-aad-auth.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page provides detailed authentication steps and code samples for .NET and Python, but all portal navigation and setup instructions assume use of the Azure Portal GUI, without mention of CLI or scripting alternatives. There are no examples using Bash, Azure CLI, or Linux-native tools, and no guidance for users working in non-Windows environments. The .NET code samples implicitly target Windows users, and the Python example, while cross-platform, does not address Linux-specific setup or authentication nuances. There are no PowerShell-specific examples, but the absence of Linux/CLI parity and the focus on GUI steps indicate a Windows-first, GUI-centric bias.
Recommendations
- Add equivalent instructions for registering applications, assigning permissions, and managing secrets using the Azure CLI (az) and/or Azure PowerShell, and present these before or alongside GUI steps.
- Include Bash or shell script examples for authentication flows, especially for unattended/service principal scenarios.
- Explicitly mention that the Python code is cross-platform and provide any Linux-specific notes (e.g., environment variable setup, dependency installation).
- Provide guidance for headless or non-GUI environments (common in Linux), such as using device code authentication or service principal flows via CLI.
- Where possible, balance the order of presentation so that CLI/Linux-native approaches are not always secondary to GUI/Windows-centric instructions.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-certificate-migration-guide.md
...in/articles/batch/batch-certificate-migration-guide.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation generally maintains platform neutrality but exhibits subtle Windows bias by listing the Windows documentation link before Linux in the FAQ and not providing concrete, step-by-step Linux command examples for certificate handling. Linux-specific guidance is less detailed, and practical examples for Linux users (such as shell commands or scripts) are missing.
Recommendations
- When referencing documentation for both Windows and Linux, alternate the order or present them together (e.g., 'See the documentation for Windows and Linux').
- Provide explicit, step-by-step examples for Linux users, such as sample shell commands for copying certificates, adjusting permissions, or accessing Key Vault from a Linux Batch pool.
- Ensure that all instructions and examples are equally detailed for both platforms, including code snippets or configuration samples for Linux where relevant.
- Highlight any platform-specific considerations in parallel, rather than focusing on one OS before the other.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-efficient-list-queries.md
...ob/main/articles/batch/batch-efficient-list-queries.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page exclusively provides examples and code samples using the Batch .NET SDK in C# and references to C# sample projects. There are no examples or code snippets for Linux-oriented tools (such as Azure CLI, Bash, Python SDK, or REST via curl), nor are there references to cross-platform scripting or command-line usage. The documentation assumes a Windows/.NET development environment, which may disadvantage Linux or cross-platform users.
Recommendations
- Add equivalent code samples using the Azure CLI to demonstrate efficient list queries for Batch resources, including filter, select, and expand usage.
- Provide examples using the Python SDK (azure-batch) to illustrate how to construct efficient queries in a cross-platform language.
- Include REST API usage examples with curl or HTTPie, showing how to construct filter, select, and expand query strings.
- Reference and link to sample projects or scripts that are cross-platform (e.g., Python, Bash) in addition to the C#/.NET samples.
- Explicitly mention that the concepts apply to all platforms and provide guidance for users on Linux or macOS.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-management-dotnet.md
...cs/blob/main/articles/batch/batch-management-dotnet.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page exclusively provides .NET (C#) code samples and instructions, which are typically associated with Windows development environments. There is no mention of Linux or cross-platform considerations, nor are there any examples or notes about running the .NET library or code on Linux systems. The only sample project referenced is in C#, and there are no alternative language or platform examples. This creates a subtle Windows bias by omission, as it assumes a Windows/.NET-centric development context and does not address Linux users or cross-platform usage.
Recommendations
- Explicitly state that the Batch Management .NET library and its code samples are cross-platform and can be used on Linux and macOS as well as Windows, especially since .NET Core/.NET 5+ is supported on these platforms.
- Provide instructions or notes for setting up the development environment on Linux (e.g., installing .NET SDK, using VS Code or other editors, running the code from the terminal).
- Include at least one example of running the code or configuring authentication on Linux (e.g., using environment variables for DefaultAzureCredential).
- Mention any Linux-specific considerations or troubleshooting tips, if applicable.
- Reference or link to equivalent documentation or samples in other languages that are popular on Linux (e.g., Python, Java), or at least mention their existence in the 'Next steps' section.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-pool-create-event.md
...cs/blob/main/articles/batch/batch-pool-create-event.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Heavy
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-related information and terminology. The 'cloudServiceConfiguration' section is exclusively Windows-focused, referencing only Windows Server OS families. The documentation provides more detail and explicit references for Windows (e.g., Windows Server versions, Windows-specific configuration), while Linux is only mentioned in passing (e.g., in a link to VM sizes and a note that 'windowsConfiguration' must not be set for Linux images). There are no Linux-specific configuration examples or details.
Recommendations
- Add a dedicated section for Linux configuration, similar to the 'windowsConfiguration' section, describing relevant Linux settings (e.g., SSH configuration, user setup, extensions).
- Provide explicit Linux OS family/version examples and references, not just Windows Server versions.
- Ensure that Linux and Windows VM size links are presented together and with equal prominence.
- Include example JSON snippets for both Windows and Linux pool configurations.
- Clarify in the documentation when a property is Linux-specific, Windows-specific, or applicable to both, to avoid implicit Windows-first assumptions.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-pool-node-error-checking.md
.../main/articles/batch/batch-pool-node-error-checking.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exhibits a mild Windows bias by mentioning Windows-specific configuration (automatic updates) without providing equivalent information for Linux pools. There are no OS-specific command-line examples, but the only explicit OS distinction is for Windows, and Linux parity is not addressed in those sections.
Recommendations
- Where Windows-specific settings are discussed (e.g., enableAutomaticUpdates), provide equivalent information for Linux pools, such as how updates are handled or configured on Linux nodes.
- Explicitly mention differences in node management, error states, or troubleshooting steps for Linux pools where applicable.
- If there are OS-specific behaviors (such as log file locations, update mechanisms, or disk management), include parallel guidance for both Windows and Linux.
- Consider adding examples or notes that clarify when instructions or recommendations apply to all OS types versus only Windows.
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
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both PowerShell and Azure CLI commands for listing VM sizes and images, but PowerShell (a Windows-centric tool) is consistently mentioned first in all lists and examples. There are no Linux-specific shell examples (e.g., Bash), and the documentation does not mention or demonstrate Linux-native tools or patterns, despite Azure CLI being cross-platform. This ordering and tool selection subtly prioritize Windows users and workflows.
Recommendations
- Alternate the order of PowerShell and Azure CLI in lists and examples, or list Azure CLI first to reflect its cross-platform nature.
- Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows, and provide Bash shell examples where appropriate.
- Where possible, include Linux-native command-line patterns (e.g., Bash scripting) alongside PowerShell examples.
- Add a note clarifying that PowerShell Core is available cross-platform, but that Azure CLI is the recommended tool for Linux users.
- Review other documentation pages for similar ordering and tool selection to ensure consistent cross-platform parity.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-service-workflow-features.md
...main/articles/batch/batch-service-workflow-features.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page does not provide explicit examples or instructions that are Windows-specific, but it does exhibit subtle Windows bias by referencing the Batch .NET client library before Python in the 'Next steps' section. There are no Linux-specific examples, tools, or workflows mentioned, and the documentation does not clarify cross-platform considerations or provide parity for Linux users.
Recommendations
- Present cross-platform SDKs and tools in a neutral or rotating order (e.g., list Python and .NET together, or alternate which is mentioned first).
- Explicitly mention that Batch supports both Windows and Linux compute nodes, and provide links to documentation or quickstarts for both platforms.
- Include examples or references for Linux users, such as Bash scripts or Linux command-line tools, where appropriate.
- Highlight any platform-specific considerations (e.g., differences in application packaging or node setup between Windows and Linux).
- Ensure that all referenced tools (such as Batch Explorer) are clearly marked as cross-platform or provide alternatives if they are Windows-only.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/error-handling.md
.../azure-docs/blob/main/articles/batch/error-handling.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation generally maintains OS neutrality, but in the 'Connect to compute nodes' section, Windows (RDP) is mentioned before Linux (SSH), and no concrete command-line examples are provided for either OS. In the troubleshooting section, instructions reference examining 'event logs' without clarifying this is a Windows-specific tool, and there are no Linux log equivalents or examples. There are no PowerShell-heavy or Windows-only tool references, but Linux-specific troubleshooting steps and examples are missing.
Recommendations
- When describing remote connection methods, present Linux (SSH) and Windows (RDP) options in parallel, or alternate their order in different sections.
- Provide explicit examples for both Windows (e.g., using RDP) and Linux (e.g., using SSH) for connecting to nodes, including sample commands.
- In troubleshooting sections, mention both Windows event logs and Linux log files (e.g., /var/log/syslog, /var/log/messages) for parity.
- Where possible, include code snippets or command-line examples for both platforms (e.g., using SSH to connect to Linux nodes, or using Windows Remote Desktop for Windows nodes).
- Clarify when instructions or tools are OS-specific, and provide equivalent guidance for the other OS.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/jobs-and-tasks.md
.../azure-docs/blob/main/articles/batch/jobs-and-tasks.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation generally maintains cross-platform language, but there are subtle signs of Windows bias. In the section on specifying the command line for tasks, the Windows example (cmd.exe) is listed before the Linux example (/bin/sh). Additionally, the 'robocopy' tool (Windows-specific) is mentioned as an example for copying files in a start task, without mentioning a Linux equivalent like 'cp' or 'rsync'. No Linux-specific tools are referenced in parallel, and the examples and tool mentions may lead Linux users to feel less directly supported.
Recommendations
- When providing command line examples, alternate the order or present Linux and Windows examples side by side, or even lead with Linux examples where appropriate.
- When referencing platform-specific tools (e.g., 'robocopy'), also mention Linux equivalents such as 'cp' or 'rsync' to ensure parity.
- Explicitly state that examples are provided for both Windows and Linux, and ensure that for every Windows-specific example or tool, a Linux counterpart is included.
- Consider including a table or section summarizing common commands and tools for both platforms in the context of Azure Batch tasks.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/manage-private-endpoint-connections.md
.../articles/batch/manage-private-endpoint-connections.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents PowerShell examples before Azure CLI, which may suggest a Windows-first perspective. The PowerShell section is detailed and uses Windows-centric tooling, while the CLI section, though present, comes after. There are no explicit Linux-only tools or shell patterns, but the ordering and emphasis could be perceived as favoring Windows users.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples, as Azure CLI is cross-platform and more familiar to Linux users.
- Explicitly mention that Azure CLI commands work natively on Linux, macOS, and Windows.
- Include bash-specific notes or examples (e.g., using export, or referencing Linux shell conventions) to reinforce Linux parity.
- If possible, add a short section or note about using these commands in Linux environments, including any prerequisites or differences.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/managed-identity-pools.md
...ocs/blob/main/articles/batch/managed-identity-pools.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation generally maintains cross-platform parity, but there is a subtle Windows bias in the ordering of examples and references. Specifically, in the section on obtaining managed identity tokens within Batch nodes, the PowerShell (Windows) example is presented before the Bash (Linux) example. Additionally, the reference link for the Azure Instance Metadata Service points to the Windows-specific documentation. However, both Windows and Linux examples are present, and the overall content does not omit Linux instructions or tools.
Recommendations
- Present Linux and Windows examples in parallel or alternate the order to avoid always listing Windows first.
- Use neutral or combined documentation links (e.g., a general Instance Metadata Service page, or both Windows and Linux links).
- Ensure that any code samples, tips, or references that are platform-specific are clearly labeled and that Linux is given equal prominence.
- Consider adding explicit notes about cross-platform support where relevant, to reassure users of Linux parity.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/network-security-perimeter.md
...blob/main/articles/batch/network-security-perimeter.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides step-by-step instructions for associating an Azure Batch account with a network security perimeter using the Azure portal, PowerShell, and Azure CLI. The PowerShell example is given before the Azure CLI example, which can be interpreted as a Windows-first ordering. The PowerShell section is detailed and uses Windows-centric tooling, which may be less familiar or accessible to Linux/macOS users. However, the inclusion of Azure CLI instructions does provide cross-platform coverage, as Azure CLI is available on all major operating systems. There are no Linux-specific shell (e.g., Bash) examples or explicit mention of Linux tools, but the CLI coverage partially mitigates this.
Recommendations
- Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and more inclusive for Linux/macOS users.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows to encourage non-Windows users.
- Optionally, include Bash script examples or notes for Linux users, especially for automation scenarios.
- Consider providing parity in troubleshooting or environment setup notes for both Windows (PowerShell) and Linux (Bash/CLI) environments.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/quick-create-template.md
...docs/blob/main/articles/batch/quick-create-template.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation primarily describes deployment using the Azure Portal and briefly mentions Azure PowerShell, Azure CLI, and REST API as alternatives. However, it links only to the PowerShell deployment guide and does not provide direct examples or links for Linux users (e.g., Bash/CLI instructions). The order of mention and linking prioritizes Windows-centric tools, and there are no Linux-specific examples or parity in guidance.
Recommendations
- Add explicit Azure CLI (Bash) deployment instructions or links alongside PowerShell, ensuring both Windows and Linux users are equally supported.
- When referencing alternative deployment methods, list Azure CLI before or alongside PowerShell, not after.
- Provide example commands for both PowerShell and Azure CLI in the documentation, or link to both sets of instructions.
- Include a note clarifying that the Azure CLI is cross-platform and suitable for Linux, macOS, and Windows users.
- Ensure that all referenced guides (such as 'Deploy templates') include both PowerShell and CLI tabs/examples.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/simplified-node-communication-pool-no-public-ip.md
...tch/simplified-node-communication-pool-no-public-ip.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation generally maintains cross-platform neutrality, but in the troubleshooting section, the Windows PowerShell command (Test-TcpConnection) is listed before the Linux equivalent (nc), and the Windows command is labeled with a platform-specific comment. This ordering and explicit mention of PowerShell can be interpreted as a subtle Windows-first and PowerShell-heavy bias. No other examples, tools, or instructions are Windows-specific, and Linux is mentioned where relevant (e.g., Ubuntu image in REST example).
Recommendations
- Present Linux and Windows command-line examples in parallel or alternate the order (e.g., show Linux first in some sections).
- Use neutral phrasing such as 'On Windows, use...' and 'On Linux, use...' instead of always listing Windows first.
- Where possible, provide cross-platform commands or scripts (e.g., using Azure CLI, which is available on both platforms) as primary examples.
- Ensure that any screenshots or UI references are not Windows-centric unless the feature is truly Windows-only.
- Review other sections for subtle ordering or terminology that may imply Windows is the default or preferred platform.
Batch
Batch security and compliance best practices
...cs/blob/main/articles/batch/security-best-practices.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation generally covers both Windows and Linux for Azure Batch, but there are subtle signs of Windows bias. Windows-specific tools (PowerShell) are mentioned before Azure CLI, and Windows OS configuration details (such as TLS settings) are described in more depth than Linux equivalents. Some links and examples reference Windows tools first, and Windows-specific configuration guidance is more detailed.
Recommendations
- Ensure that Linux examples and tools (such as Azure CLI) are presented alongside or before Windows/PowerShell equivalents.
- Provide equivalent Linux OS security guidance, especially for topics like TLS/cipher suite configuration, not just Windows registry settings.
- When referencing APIs or commands, include both PowerShell and Azure CLI examples, or clarify Linux/macOS usage.
- Balance the depth of OS-specific security recommendations for both Windows and Linux.
- Where possible, mention Linux distributions supported and provide links to their security documentation.
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation mentions Windows-specific tools such as PowerShell cmdlets and Remote Desktop (RDP) access before their cross-platform or Linux equivalents. PowerShell is listed first in the command-line tools section, and RDP is referenced for node access without mentioning SSH, which is the standard for Linux nodes. However, the Azure CLI and Batch Explorer are described as cross-platform, and the API/library coverage is broad and language-neutral.
Recommendations
- In the 'Batch command-line tools' section, list Azure CLI before PowerShell to emphasize cross-platform support.
- In the 'Other tools for application development' section, when discussing remote access to compute nodes, mention SSH for Linux nodes alongside RDP for Windows nodes.
- Where possible, clarify which tools and examples are applicable to Linux/macOS environments, and provide links or notes for Linux-specific workflows.
- Ensure that code samples and tutorials for Python, JavaScript, and Java are highlighted equally with .NET/C# examples.
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
Summary
The documentation provides both Windows (RDP) and Linux (SSH) examples for configuring node endpoints in Azure Batch pools. However, in each example pair, the Windows/RDP scenario and C# code are presented first, followed by the Linux/SSH scenario and Python code. This ordering may subtly prioritize Windows users, but both platforms are covered with equivalent detail and parity.
Recommendations
- Alternate the order of examples so that Linux/SSH scenarios are presented first in some sections.
- Explicitly state that both Windows and Linux pools are supported and that the configuration steps are analogous.
- Consider providing a summary table or section that highlights the equivalence of configuration for both platforms.
- If possible, provide code snippets in additional languages commonly used on Linux (e.g., Bash/CLI, or PowerShell for cross-platform use).
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 provides both Windows and Linux troubleshooting commands, but Windows/PowerShell examples are shown first and in more detail. In the troubleshooting section, the Windows command (Test-NetConnection) is presented before the Linux equivalent (nc), and the Windows command includes more flags and explanation. There are no explicit Linux/macOS examples for other tasks (e.g., connecting to compute nodes), and the documentation refers to Azure PowerShell before Azure CLI in the prerequisites, which may suggest a Windows-first approach.
Recommendations
- Present Linux/macOS commands and examples alongside Windows/PowerShell, or even first where appropriate.
- Ensure parity in detail and explanation for Linux/macOS commands (e.g., provide equivalent flags and troubleshooting steps for nc as for Test-NetConnection).
- Mention Azure CLI before or alongside Azure PowerShell in prerequisites and instructions, as CLI is cross-platform.
- Add explicit Linux/macOS guidance for connecting to compute nodes (e.g., SSH commands, credential handling).
Batch
Create a Batch pool with specified public IP addresses
...docs/blob/main/articles/batch/create-pool-public-ip.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation lists Windows-centric tools (Azure PowerShell) alongside cross-platform options (Azure CLI and Portal) for creating public IP addresses, with PowerShell mentioned last. No Linux-specific tools or examples are provided, but the main workflow is platform-neutral (REST API). There is a slight Windows bias in tool recommendations, but not in critical workflow steps.
Recommendations
- Explicitly mention that Azure CLI and Portal are cross-platform and suitable for Linux/macOS users.
- Add Linux/macOS-specific instructions or examples for creating public IP addresses (e.g., using Azure CLI from Bash).
- Clarify that Azure PowerShell is available on Linux/macOS, or provide Bash/CLI examples before PowerShell.
- Consider listing Azure CLI before PowerShell to signal cross-platform parity.
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation shows a mild Windows bias: Windows tools (cmd.exe) are consistently mentioned first when describing how to access environment variables and expand them in command lines. Windows-specific syntax and naming conventions (e.g., AZ_BATCH_APP_PACKAGE_FOO#1 for Windows, AZ_BATCH_APP_PACKAGE_FOO_1 for Linux) are explained, but Windows is usually presented before Linux. The directory structure examples use backslashes (Windows style) in some tables, and Linux equivalents are not always shown side-by-side. There are no PowerShell-specific examples, but the overall pattern prioritizes Windows terminology and tools.
Recommendations
- Present Linux and Windows examples side-by-side, or alternate which is shown first.
- Use neutral language and avoid always listing Windows tools (cmd.exe) before Linux tools (/bin/sh).
- Provide explicit Linux/macOS directory path examples alongside Windows ones, especially in tables.
- Clarify differences in environment variable naming conventions for both platforms in a dedicated section.
- Consider adding macOS notes if supported.