Batch
228
Total Pages
164
Linux-Friendly Pages
64
Pages with Bias
28.1%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
156 issues found
Showing 101-125 of 156 flagged pages
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-get-resource-counts.md
.../blob/main/articles/batch/batch-get-resource-counts.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page provides only C#/.NET code samples for counting task and node states in Azure Batch, with no Linux-specific examples, CLI commands, or cross-platform scripting options. While it mentions REST and other languages, no concrete examples are given. The exclusive use of .NET code (commonly associated with Windows environments) and lack of Linux/CLI examples indicate a Windows-first and missing Linux example bias.
Recommendations
- Add Azure CLI and Azure PowerShell examples for each operation, as both are cross-platform and widely used on Linux.
- Include REST API usage examples with curl or HTTPie commands to demonstrate platform-agnostic approaches.
- Provide Python SDK code samples, as Python is popular for automation on Linux.
- Explicitly mention that the .NET SDK can be used on Linux, if relevant, and provide instructions for doing so.
- Ensure that all code samples are balanced between Windows and Linux-friendly tools and languages.
Create Pull Request
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 using the Azure Portal (a web UI) for all steps and does not provide any command-line examples. While this avoids explicit Windows tool bias (such as PowerShell), it implicitly favors Windows users by omitting CLI-based workflows (e.g., Azure CLI, Bash scripts) that are common and preferred on Linux and macOS. There are no examples or instructions for performing these tasks via cross-platform tools, and no mention of Linux-specific considerations.
Recommendations
- Add parallel instructions and examples for moving a Batch account using the Azure CLI (az batch, az group deployment, etc.), which is cross-platform and widely used on Linux.
- Include sample Bash scripts or command-line snippets for exporting, modifying, and deploying ARM templates.
- Explicitly mention that all steps can be performed on Linux/macOS using the Azure CLI, and provide links to relevant CLI documentation.
- If PowerShell is referenced in other related docs, ensure Bash/Azure CLI equivalents are always provided.
- Clarify that the Azure Portal is web-based and platform-agnostic, but offer alternatives for users who prefer or require command-line automation.
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
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias primarily through its exclusive use of Azure Portal UI instructions and screenshots, which are tailored to the Windows-centric Azure Portal experience. There are no examples or instructions for Linux command-line tools (such as Azure CLI or PowerShell Core on Linux), nor are there references to Linux-specific workflows or authentication patterns. All code examples are platform-neutral (.NET and Python), but the setup and configuration steps assume use of the Azure Portal, which is most commonly accessed from Windows environments.
Recommendations
- Add equivalent instructions for registering applications, managing secrets, and assigning RBAC roles using Azure CLI and/or Azure PowerShell, which are available cross-platform.
- Include Linux shell (bash) examples for authentication flows, such as using environment variables or CLI commands to retrieve tenant IDs, client IDs, and secrets.
- Provide screenshots or terminal output examples from Linux environments where relevant.
- Explicitly mention that all steps can be performed from Linux or macOS using CLI tools, and link to relevant documentation.
- Ensure parity in code samples by showing how to use authentication libraries in Linux environments, including any OS-specific considerations.
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 exclusively provides C#/.NET code examples and references to the .NET library, with no mention of Linux-specific usage, cross-platform development, or equivalent command-line or scripting examples (e.g., Bash, CLI). The sample project and all code snippets are tailored to Windows-centric development environments, implicitly prioritizing Windows users and omitting guidance for Linux developers.
Recommendations
- Add equivalent examples using Azure CLI or Bash scripts for common tasks (e.g., creating/deleting Batch accounts, managing keys, checking quotas), which are natively cross-platform and widely used on Linux.
- Explicitly mention that the .NET SDK and C# code can be used on Linux (e.g., with .NET Core/SDK on Linux) and provide setup instructions for Linux environments.
- Include references or links to Python or other cross-platform SDKs for Batch Management, with example code snippets.
- Ensure that any sample projects or GitHub repositories referenced include instructions for running on Linux, or provide alternative samples for Linux users.
- Where possible, balance the order of presentation so that cross-platform or Linux-friendly tools (e.g., Azure CLI, REST API) are mentioned alongside or before Windows-specific approaches.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-pools-to-simplified-compute-node-communication-model-migration-guide.md
...ified-compute-node-communication-model-migration-guide.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation mentions RDP connectivity before SSH when discussing diagnostic access to nodes, which prioritizes the Windows method over the Linux equivalent. Additionally, there are no concrete examples or instructions for either platform, but the order and phrasing suggest a Windows-first perspective. There are no PowerShell-heavy sections or exclusive mentions of Windows tools, but the lack of Linux-specific examples or parity in example order is notable.
Recommendations
- Present SSH connectivity before or alongside RDP when discussing diagnostic access, to reflect equal support for Linux nodes.
- Include explicit examples or instructions for both Windows (RDP) and Linux (SSH) connectivity.
- Ensure any agent or tool references clarify usage for both platforms, with equal detail.
- Review other documentation pages linked from this one to ensure Linux parity in examples and troubleshooting steps.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-role-based-access-control.md
...main/articles/batch/batch-role-based-access-control.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page describes Azure Batch RBAC concepts and procedures exclusively using the Azure portal UI, without mentioning command-line or automation approaches. There are no examples using Azure CLI, PowerShell, or REST API. While PowerShell is not directly referenced, the absence of Azure CLI or Linux-oriented instructions means the documentation implicitly favors Windows users (who are more likely to use the portal or PowerShell), and does not provide parity for Linux users who typically use Azure CLI or REST API.
Recommendations
- Add step-by-step instructions for assigning RBAC roles using Azure CLI, including full command examples.
- Include PowerShell examples for parity, but ensure Azure CLI examples are presented first or alongside PowerShell.
- Reference REST API documentation for role assignment and provide sample requests.
- Explicitly mention that all procedures can be performed from Linux, macOS, or Windows using Azure CLI or REST API.
- Add a table or section comparing methods (Portal, CLI, PowerShell, REST) for assigning roles, with links to relevant documentation.
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 page exhibits mild Windows bias. In the 'Connect to compute nodes' section, instructions for connecting to Windows nodes (via RDP) are mentioned before Linux nodes (via SSH), and RDP is described in more detail. There are no explicit troubleshooting examples or tool references for Linux (e.g., examining Linux logs or using Linux-native commands), and the event log examination is mentioned generically without Linux equivalents. The page lacks concrete Linux-specific troubleshooting steps or examples.
Recommendations
- Provide Linux-specific troubleshooting examples, such as examining syslog, dmesg, or application logs in /var/log.
- Mention SSH connection steps and tools (e.g., using ssh command-line, Putty, etc.) with equal detail as RDP.
- Include references to Linux-native commands for node investigation (e.g., ps, top, journalctl) alongside Windows event log examination.
- Ensure that instructions for both OS types are presented in parallel, rather than Windows-first ordering.
- Add examples of handling exit codes and errors specific to Linux environments.
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. PowerShell instructions are given before Azure CLI, and there are detailed PowerShell code examples. This ordering and emphasis may indicate a Windows-first and PowerShell-heavy bias. However, Azure CLI (cross-platform) instructions are present and complete, and there are no exclusive references to Windows-only tools or missing Linux examples.
Recommendations
- Present Azure CLI instructions before PowerShell, as CLI is cross-platform and more commonly used on Linux/macOS.
- Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, to encourage non-Windows users.
- Consider adding Bash script examples or references to automation using Bash for Linux users.
- Where possible, provide parity in screenshots or UI walkthroughs for Azure Cloud Shell (which supports both Bash and PowerShell).
- Review language to ensure it does not imply PowerShell is the default or preferred method.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/tutorial-batch-functions.md
...s/blob/main/articles/batch/tutorial-batch-functions.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation primarily uses the Azure portal for all steps and does not provide command-line examples for either Windows (PowerShell/Command Prompt) or Linux (Bash/CLI). However, where OS-specific details are mentioned (e.g., VM image selection, start task commands), the examples use Ubuntu and Bash commands, not Windows. There is no explicit Windows bias in the form of PowerShell-heavy content or exclusive mention of Windows tools. However, the absence of any Linux CLI (e.g., Azure CLI) or cross-platform command-line examples means Linux users are not fully supported, and the portal-based workflow may be more familiar to Windows users.
Recommendations
- Add Azure CLI examples for creating Batch pools, jobs, and blob containers, showing both Windows and Linux command-line usage.
- Include Bash scripts for common tasks (e.g., uploading files, retrieving results) to support Linux users.
- Explicitly mention that the portal-based workflow is cross-platform, and provide links to Linux-friendly tools (e.g., Azure CLI, Storage Explorer for Linux).
- Where code or commands are shown (e.g., for the start task), clarify that they are for Ubuntu nodes, and provide Windows equivalents if relevant.
- Add a section or appendix with PowerShell and Bash equivalents for all major steps to ensure parity.
Low 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 task command line, the Windows example ('cmd /c MyTaskApplication.exe %MY_ENV_VAR%') is shown before the Linux example ('/bin/sh -c MyTaskApplication $MY_ENV_VAR$'). Additionally, in the 'Start task' section, the documentation suggests using 'robocopy' and 'setup.exe' or MSI installers as examples of setup operations, which are Windows-specific tools and formats. There are no Linux-specific tool examples (e.g., 'cp', 'tar', 'bash', '.sh' scripts) provided in these contexts.
Recommendations
- Alternate the order of Windows and Linux examples, or present them side by side to avoid implicit prioritization.
- When mentioning Windows-specific tools like 'robocopy' or 'setup.exe', also provide equivalent Linux examples such as 'cp', 'rsync', or '.sh' scripts.
- Explicitly state that the examples apply to both Windows and Linux nodes, and provide guidance or links for common Linux setup patterns.
- Where possible, use neutral language or clarify when an example is platform-specific.
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 parallel examples for both Windows (RDP) and Linux (SSH) pools, using C# for Windows and Python for Linux. However, in each example pair, the Windows/RDP example is presented first, followed by the Linux/SSH example. This ordering may subtly signal a Windows-first bias, though the technical content is balanced and both platforms are covered equally.
Recommendations
- Alternate the order of examples so that Linux/SSH examples are sometimes presented first.
- Add a brief statement at the start clarifying that Azure Batch supports both Windows and Linux pools equally.
- Consider providing both C# and Python code snippets for each scenario, regardless of OS, to further reinforce parity.
- Explicitly mention that the configuration approach is identical for both platforms, with only the protocol/port differing.
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 Linux and Windows for Azure Batch, but there are subtle signs of Windows bias. Windows-specific tools (PowerShell) and documentation links are mentioned before Linux equivalents in several places, and Windows OS configuration guidance is more detailed. For example, the section on discovering image EOL dates lists PowerShell before Azure CLI, and the TLS configuration section provides Windows registry links without Linux equivalents. The documentation also references RDP before SSH when discussing remote access. However, Linux is acknowledged as a supported platform and most guidance is applicable to both OS types.
Recommendations
- When listing tools or commands, alternate or list Linux/Azure CLI examples before or alongside Windows/PowerShell examples.
- Provide equivalent Linux guidance for OS-level security settings (e.g., TLS/cipher suite configuration) and link to relevant Linux documentation.
- When discussing remote access, mention SSH before or alongside RDP, and clarify Linux-specific procedures where relevant.
- Ensure that all examples and references to command-line tools include both PowerShell and Azure CLI (or Bash) options.
- Add explicit Linux security best practices where Windows-specific advice is given.
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 generally maintains cross-platform neutrality, but some sections show mild Windows bias. In troubleshooting, Windows PowerShell commands (Test-NetConnection) are presented before Linux equivalents (nc), and the Windows command is more verbose. There are no explicit Linux/macOS CLI examples for pool creation, and the Azure portal instructions do not mention platform-specific differences. REST API and ARM template examples use Ubuntu images, which is positive for Linux parity.
Recommendations
- Present Linux and Windows troubleshooting commands side-by-side, with equal detail and explanation.
- Include explicit Azure CLI examples for pool creation, showing both Windows and Linux usage.
- Ensure that command-line instructions and screenshots do not assume Windows as the default platform.
- Where PowerShell is mentioned, also mention Bash or other Linux-native tools if applicable.
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 Azure PowerShell as a method for creating public IP addresses alongside the Azure portal and Azure CLI, but does not mention Linux/macOS equivalents (such as Bash scripts or direct REST API usage) for PowerShell. The order of methods places the Azure portal (GUI, often Windows-centric) first, then CLI, then PowerShell, which may subtly prioritize Windows tooling. However, the main example for creating the Batch pool uses Ubuntu as the VM image, and the REST API is platform-neutral.
Recommendations
- Explicitly mention that Azure CLI is cross-platform and provide sample commands for both Windows (PowerShell) and Linux/macOS (Bash).
- Clarify that PowerShell is available on Linux/macOS, or provide Bash examples for Linux users.
- Consider listing CLI and REST API methods before PowerShell and portal to avoid Windows-first ordering.
- Add a note or section highlighting Linux/macOS workflows for creating public IP addresses.
Batch
Copy applications and data to pool nodes
...ain/articles/batch/batch-applications-to-pool-nodes.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page exhibits mild Windows bias by referencing Windows-specific installation formats (e.g., .exe, .msi) and omitting explicit Linux/macOS examples or tool references. Windows-centric terminology appears first in several sections, and there are no mentions of Linux package formats (e.g., .sh, .deb, .rpm) or cross-platform installation commands.
Recommendations
- Add examples for Linux/macOS application installation, such as using shell scripts (.sh), or package managers (apt, yum, etc.).
- Mention Linux/macOS equivalents alongside Windows examples (e.g., .deb/.rpm for .msi, bash scripts for PowerShell).
- Clarify that application packages and resource files can be used for any OS, and provide sample install commands for both Windows and Linux.
- Include notes or links to documentation on Linux/macOS node configuration and data transfer best practices.
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation page displays a mild Windows bias: Windows examples and tools (cmd.exe) are consistently mentioned before Linux equivalents, and Windows-specific patterns (e.g., environment variable naming conventions, file path separators) are described in detail. Linux is covered, but often as a secondary consideration, and some explanations (e.g., directory postfixes) use Windows-style paths by default.
Recommendations
- Present Linux and Windows examples side-by-side, or alternate which is shown first.
- Use neutral language when describing environment variable naming conventions and file paths, or provide both Windows and Linux formats explicitly.
- Clarify Linux-specific behaviors and provide Linux-first examples where appropriate.
- Ensure tables and examples include both Windows and Linux variants for all relevant variables and paths.
Batch
Choose VM sizes and images for pools
...e-docs/blob/main/articles/batch/batch-pool-vm-sizes.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both PowerShell and Azure CLI examples for listing VM sizes and images, but PowerShell (a Windows-centric tool) is consistently mentioned first in lists and tips. There are no Linux-specific shell examples (e.g., Bash), nor is there mention of Linux/macOS-specific tooling or patterns. However, Azure CLI is cross-platform and included in all example commands, and the documentation explicitly covers both Windows and Linux VM images.
Recommendations
- Alternate the order of PowerShell and Azure CLI examples, or list Azure CLI first to reflect its cross-platform nature.
- Add explicit Bash shell examples where relevant, especially for Linux/macOS users.
- Clarify that Azure CLI is available on Windows, Linux, and macOS.
- Include notes or links for installing and using Azure CLI on Linux/macOS.
- If PowerShell is mentioned, note that PowerShell Core is available cross-platform, or provide equivalent Bash commands.
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias. Windows tools (cmd.exe) and syntax are consistently mentioned before Linux equivalents, and Windows-specific details (such as path formats and environment variable naming conventions) are often foregrounded. Linux examples are present but typically follow Windows instructions, and some explanations (e.g., app package variable naming) are more detailed for Windows than Linux. There is a slight emphasis on Windows tools and patterns throughout.
Recommendations
- Present Linux and Windows examples side-by-side or alternate which is shown first.
- Ensure equal detail for both platforms when describing environment variable naming conventions and directory structures.
- Explicitly mention macOS where applicable, or clarify if only Linux/Windows are supported.
- Add a summary table comparing Windows and Linux environment variable usage and directory paths.
- Use neutral language when introducing platform-specific tools (e.g., 'On Windows, use cmd.exe; on Linux, use /bin/sh').
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
Powershell Heavy
Summary
The documentation lists Windows-centric tools (Azure PowerShell) alongside cross-platform options (Azure CLI and Portal) for creating public IP addresses, but PowerShell is mentioned last, and no Linux/macOS-specific tools or examples are provided. There are no explicit Linux/macOS command examples, and the documentation does not clarify platform parity for all steps. The REST API example uses Ubuntu, which is positive, but the overall guidance leans toward Windows tooling.
Recommendations
- Add explicit Linux/macOS command examples for creating public IP addresses (e.g., Azure CLI commands run on bash).
- Clarify that Azure CLI is cross-platform and provide usage instructions for Linux/macOS environments.
- Avoid listing Windows-specific tools (PowerShell) without equivalent Linux/macOS alternatives or context.
- Where possible, show examples in both bash (Linux/macOS) and PowerShell (Windows), or clarify platform neutrality.
- Consider listing cross-platform tools (CLI, Portal) before Windows-specific tools.
Batch
Migrate low-priority VMs to spot VMs in Batch
...s/batch/low-priority-vms-retirement-migration-guide.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for automation, but the PowerShell section is given as the second main automation method, and no explicit Linux shell (bash) or macOS-specific instructions are provided. PowerShell is a Windows-centric tool, and its inclusion without parity for Linux-native scripting (e.g., bash) or explicit mention of cross-platform compatibility introduces a mild Windows bias. However, the Azure CLI examples are cross-platform and shown first, and infrastructure-as-code examples (ARM, Terraform) are platform-neutral.
Recommendations
- Clarify that Azure CLI commands work on Linux, macOS, and Windows, and recommend bash/zsh for Linux/macOS users.
- Add explicit bash shell examples or notes for Linux/macOS users, especially for scripting and automation.
- Mention that PowerShell Core is available cross-platform, or provide links to Linux/macOS installation guides if PowerShell is recommended.
- Ensure troubleshooting and validation steps include Linux/macOS shell equivalents if PowerShell is used.
- Consider reordering sections so that cross-platform tools (CLI, REST, ARM, Terraform) are always presented before Windows-centric tools.
Batch
Configure managed identities in Batch pools
...ocs/blob/main/articles/batch/managed-identity-pools.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Windows (PowerShell) and Linux (Bash) examples for obtaining managed identity tokens, but the Windows/PowerShell example is presented first. There is a slight preference for Windows tools in the ordering, but Linux parity is generally maintained. No critical functionality is missing for Linux/macOS users.
Recommendations
- Alternate the order of Windows and Linux examples, or present them side-by-side to avoid perceived prioritization.
- Explicitly mention macOS where Linux instructions apply, to reassure users.
- Ensure that any referenced tooling or SDKs (e.g., .NET, Azure CLI) are cross-platform and clarify their compatibility.
- Add a brief note at the start of scripting sections indicating that both Windows and Linux are supported equally.
Batch
Persist job and task output to a data store
...ure-docs/blob/main/articles/batch/batch-task-output.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exhibits minor Windows bias. In the 'Custom file movement solution' section, the only explicit example provided is for Windows nodes, using Windows executables and command chaining syntax. There are no equivalent Linux/macOS examples or references to Linux shell commands, nor is there mention of Linux-specific tools or patterns. The overall guidance is platform-neutral, but examples and phrasing favor Windows.
Recommendations
- Add equivalent Linux/macOS examples in the 'Custom file movement solution' section, such as using shell scripts (e.g., './doMyWork.sh && ./uploadMyFilesToSql.sh') or common Linux utilities.
- Explicitly mention that custom scripts can be written for both Windows and Linux nodes, and provide sample commands for each.
- Reference cross-platform tools (e.g., azcopy, curl, bash scripts) where appropriate.
- Ensure that examples and sample projects include both Windows and Linux variants, or clarify platform applicability.
Batch
Provision a pool in a virtual network
...docs/blob/main/articles/batch/batch-virtual-network.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page generally maintains platform neutrality, but in several places Windows is mentioned before Linux (e.g., port 3389 for Windows, then port 22 for Linux), and remote access examples are described in terms of RDP (Windows) and SSH (Linux) without further Linux-specific guidance. There are no explicit command-line examples for either platform, but Windows terminology and port numbers are often listed first, and Linux-specific configuration details (such as SSH setup or troubleshooting) are not provided.
Recommendations
- Present Linux and Windows examples in parallel, or alternate which is listed first.
- Include explicit Linux/macOS command-line examples (e.g., Azure CLI commands for pool creation, NSG configuration, etc.).
- Add troubleshooting tips or configuration notes specific to Linux (e.g., SELinux, firewall, SSH key setup).
- Clarify that all steps and features apply equally to Linux and Windows nodes, and highlight any platform-specific caveats.
- Where remote access is discussed, provide equal detail for SSH (Linux/macOS) and RDP (Windows), including links to relevant documentation.
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Minor Rdp Bias
Summary
The documentation page demonstrates mild Windows bias. Batch PowerShell cmdlets are listed first among command-line tools, and RDP (a Windows-centric protocol) is mentioned as the only remote login method for compute nodes. While Azure CLI and cross-platform tools are referenced, Windows tools and patterns (PowerShell, RDP) are presented before Linux/macOS equivalents. No Linux-specific examples or SSH instructions are provided for node access.
Recommendations
- List Azure CLI before PowerShell in command-line tool sections to emphasize cross-platform support.
- Explicitly mention SSH as a method for logging into Linux compute nodes, alongside RDP for Windows nodes.
- Provide examples or links for Linux/macOS users where relevant (e.g., accessing nodes, troubleshooting).
- Clarify that Batch Explorer and Storage Explorer are available for all platforms, and provide platform-specific installation instructions if possible.
- Ensure code samples and tutorials include Linux/macOS usage notes where applicable.
Batch
Migrate Batch account certificates to Azure Key Vault
...in/articles/batch/batch-certificate-migration-guide.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides links to both Windows and Linux Key Vault VM extension guides, but Windows is mentioned first in the FAQ. There are no concrete code examples or step-by-step instructions for either platform, but Linux-specific guidance is relatively brief and lacks detailed examples, especially for certificate access and installation. The documentation does not show Powershell-heavy or Windows-only tools, but the ordering and lack of Linux parity in examples suggest a mild Windows bias.
Recommendations
- Present Windows and Linux documentation links in parallel or alternate order to avoid implicit prioritization.
- Add explicit, step-by-step examples for Linux certificate installation and access, including sample shell commands and configuration snippets.
- Include troubleshooting and best practices sections tailored for Linux users, especially regarding permissions and certificate file handling.
- Ensure that any references to environment variables or certificate storage paths for Linux are accompanied by clear migration instructions.