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 401-425 of 436 flagged pages
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 generally maintains OS neutrality, but in some key areas, Windows is mentioned before Linux (e.g., remote access ports: 3389 for Windows, 22 for Linux), and there are no explicit Linux/macOS-specific examples or CLI commands. While the portal workflow is platform-agnostic, there is a lack of parity in showing Linux-first or Linux-specific instructions, and no PowerShell or Windows tool bias is present.
Recommendations
- Alternate the order of mentioning Windows and Linux ports to avoid Windows-first bias.
- Add explicit Linux/macOS command-line examples (e.g., Azure CLI usage for pool creation and network configuration).
- Include references to Linux-specific networking considerations or troubleshooting steps.
- Ensure screenshots and walkthroughs include Linux/macOS environments where applicable.
Create Pull Request
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 consistently lists PowerShell (a Windows-centric tool) as the first example for querying VM sizes and images, and provides explicit PowerShell commands alongside Azure CLI and API options. While Linux is mentioned as a supported platform and Azure CLI examples are provided, the ordering and prominence of PowerShell may subtly signal a Windows-first approach. There are no Linux/macOS-specific shell examples (e.g., Bash), nor are Linux-specific tools or patterns discussed.
Recommendations
- Alternate the order of example tools so that Azure CLI (cross-platform) is listed before PowerShell.
- Add explicit Bash shell examples where appropriate, especially for Linux/macOS users.
- Include notes or sections highlighting Linux/macOS usage patterns or considerations, such as environment variables, file system paths, or troubleshooting.
- Clarify that all commands (Azure CLI, API) are cross-platform and provide guidance for Linux/macOS users where PowerShell is mentioned.
- Consider adding screenshots or walkthroughs from a Linux/macOS perspective.
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 alternates between Windows (RDP) and Linux (SSH) examples, but consistently presents Windows/RDP examples first in each section. There is no exclusive use of Windows tools or missing Linux examples, but the ordering may subtly prioritize Windows users.
Recommendations
- Alternate the order of examples so that Linux/SSH is presented first in some sections.
- Add a brief note clarifying that all features and configuration steps apply equally to both Windows and Linux pools.
- Consider grouping examples by OS or providing a summary table for parity.
- Ensure future updates maintain balanced representation and ordering.
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
Summary
The documentation provides both Windows (PowerShell) and Linux (nc) examples for network troubleshooting, but the Windows example is shown first. There is a slight emphasis on Windows tools and patterns, such as referencing PowerShell's Test-NetConnection before Linux's nc. No other sections show Windows-only bias, and examples for pool creation use platform-neutral methods (REST API, ARM templates, Azure portal).
Recommendations
- Present Linux and Windows troubleshooting commands side-by-side or alternate which is shown first.
- Explicitly mention that both Windows and Linux are supported for all steps, especially in troubleshooting.
- Where possible, provide Bash/CLI equivalents for any PowerShell commands.
- Add a note clarifying that all instructions apply equally to Linux and macOS environments unless otherwise stated.
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Minor Rdp Bias
Summary
The documentation page shows mild Windows bias, primarily through the prioritization and explicit mention of Windows-centric tools like PowerShell and Remote Desktop (RDP). PowerShell cmdlets are listed first among command-line tools, and RDP is referenced as the example for remote access to compute nodes, which is a Windows-specific protocol. However, cross-platform options like Azure CLI and Batch Explorer are also mentioned, and tutorials and SDKs for Python, JavaScript, and Java are provided, supporting Linux/macOS users.
Recommendations
- List Azure CLI before PowerShell in the command-line tools section to emphasize cross-platform support.
- Explicitly mention SSH as an alternative to RDP for accessing Linux compute nodes.
- Provide examples or links for Linux/macOS users where Windows-specific tools (e.g., PowerShell, RDP) are referenced.
- Ensure that code samples and tutorials are equally available and discoverable for Linux/macOS environments.
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation provides both Windows and Linux information, but there are signs of Windows bias. Windows VM images and considerations are described before Linux equivalents in the 'Supported VM images' section. Windows-specific tooling and paths (e.g., C:\ProgramData\Docker, c:\app\myApp.exe) are referenced, and C# examples use Windows-style paths and commands. Troubleshooting and container task examples include Windows-centric details, while Linux alternatives are present but less emphasized. No PowerShell examples are given, but the overall structure and example order favor Windows.
Recommendations
- Present Linux and Windows instructions/examples in parallel, or alternate which comes first in each section.
- Add explicit Linux shell command examples where Windows paths or commands are shown.
- Where Windows-specific tooling or paths are mentioned, immediately provide the Linux equivalent.
- Ensure troubleshooting and configuration advice is equally detailed for Linux and Windows.
- Add a summary table comparing Windows and Linux support/features for quick reference.
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Summary
The documentation provides parity between Linux and Windows in most extension examples, but there is a slight Windows bias: Windows-only extensions are listed, Windows tools (e.g., certificateStoreLocation: LocalMachine) are referenced, and Windows examples are given equal or slightly more prominence. Some extension types (e.g., Antimalware, Diagnostics, DSC, HPC GPU for AMD) are Windows-only, and troubleshooting steps reference Windows-specific concepts. However, Linux examples are present and shown first in critical sections.
Recommendations
- Clearly indicate which extensions are Windows-only and which are Linux-only in the Supported Extensions section.
- Provide Linux equivalents or alternatives for Windows-only extensions (e.g., Diagnostics, Antimalware, DSC) or explain their absence.
- Add troubleshooting steps and log locations for both Linux and Windows nodes, not just generic or Windows-centric advice.
- Ensure parity in example depth and troubleshooting for both platforms.
- Consider listing Linux extensions/examples first if the audience is mixed or Linux-focused.
Batch
Manage private endpoint connections with Azure Batch accounts
.../articles/batch/manage-private-endpoint-connections.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure PowerShell and Azure CLI examples, but PowerShell examples are presented before CLI, and the PowerShell module is highlighted with a direct link. This ordering and emphasis can be interpreted as a mild Windows bias, as PowerShell is primarily a Windows-centric tool (though cross-platform now), and many Linux/macOS users prefer CLI. No Linux/macOS-specific tools or shell patterns are mentioned, but CLI examples are present and correct.
Recommendations
- Present Azure CLI examples before PowerShell examples, as CLI is more universally available across platforms.
- Explicitly mention that Azure CLI works on Linux/macOS and Windows, and that PowerShell Core is cross-platform.
- Consider adding a note about installing Azure CLI on Linux/macOS.
- If relevant, provide bash/zsh-specific tips or troubleshooting for Linux/macOS users.
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
Summary
The documentation provides both Windows (PowerShell) and Linux (Bash) examples for obtaining managed identity tokens, but the Windows example is presented first. There are no exclusive Windows tools or missing Linux examples, and the rest of the documentation is platform-neutral.
Recommendations
- Present Linux and Windows examples side-by-side or alternate which is shown first to avoid implicit prioritization.
- Explicitly state that all steps and code samples are applicable to both Windows and Linux nodes unless otherwise noted.
- Where possible, provide cross-platform CLI examples (e.g., Azure CLI) before platform-specific scripts.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page generally maintains OS neutrality, but there are subtle signs of Windows bias. Windows-specific executable types (e.g., .exe, .cmd, .bat, PowerShell scripts) are listed before Linux equivalents. Remote access methods mention RDP (Windows) before SSH (Linux). Container support details focus on Windows Server 2016 with Containers, with less emphasis on Linux container images. The mention of Docker installation for custom images is generic, but the only explicit example is Windows. No explicit Linux shell command or example is provided, and Windows tools/patterns are referenced first in several places.
Recommendations
- List Linux script types (e.g., shell, Python) before or alongside Windows types to avoid ordering bias.
- Provide explicit Linux examples for container support (e.g., Ubuntu images with Docker pre-installed).
- Mention SSH (Linux/macOS) before or alongside RDP (Windows) when discussing remote access.
- Include sample Linux commands or configuration snippets where applicable.
- Ensure parity in tool references (e.g., mention both PowerShell and Bash for scripting).
Batch
Associate Azure Batch accounts with network security perimeter
...blob/main/articles/batch/network-security-perimeter.md
Low 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 in detail and is presented before the Azure CLI example, which may indicate a Windows-first bias. There are no Linux-specific tools or shell examples (e.g., Bash scripts), and the CLI example is generic, but PowerShell is highlighted as a primary automation method. No explicit Linux/macOS limitations are present, but the ordering and emphasis may create friction for non-Windows users.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred by many Linux/macOS users.
- Add Bash script examples for common operations, especially for associating resources.
- Explicitly mention that Azure CLI works on Linux/macOS and provide installation links.
- If PowerShell is shown, clarify that PowerShell Core is available on Linux/macOS, or provide Bash alternatives.
- Avoid language or ordering that implies PowerShell is the default or preferred method.
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 deploying and managing resources. However, PowerShell examples are given equal prominence to CLI, and PowerShell is a Windows-centric tool. The CLI examples are cross-platform, but PowerShell is not natively available on Linux/macOS (though PowerShell Core exists, it's less commonly used). There is a slight bias in presenting PowerShell as a primary option alongside CLI, which may confuse or inconvenience Linux/macOS users.
Recommendations
- Clearly indicate that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Add a note specifying that PowerShell examples are primarily for Windows users, and that PowerShell Core is required on Linux/macOS.
- Consider listing CLI examples first, as they are universally applicable.
- Optionally, provide bash script examples for common tasks to further improve Linux parity.
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 demonstrates mild Windows bias in several areas. References to PowerShell and Windows-specific tools appear before their Linux equivalents, and Windows OS configuration details (such as TLS settings) are discussed in greater depth than Linux. While Linux is acknowledged as a supported platform, examples and links (e.g., for discovering supported images) prioritize Windows tools like PowerShell, and Windows configuration guidance is more detailed. No critical functionality is Windows-only, but Linux users may experience minor friction due to the ordering and emphasis.
Recommendations
- Provide Linux-specific examples and links (e.g., show Azure CLI usage before or alongside PowerShell for listing supported images).
- Balance OS-specific configuration guidance, such as including details for managing TLS/cipher suites on Linux distributions.
- Ensure that references to tools and commands are presented in a cross-platform manner, or at least alternate the ordering between Windows and Linux.
- Explicitly mention supported Linux distributions and provide links to relevant documentation for Linux security hardening.
- Where possible, include example commands for both Windows and Linux/macOS users.
Batch
Quickstart: Create an Azure Batch account using Terraform
...ocs/blob/main/articles/batch/quick-create-terraform.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for verifying results, but the PowerShell example is given equal prominence and detail as the CLI example. The PowerShell tab is present, which may indicate a Windows-centric approach, but the CLI example is shown first. There are no Linux-specific tools or instructions, but the use of Azure CLI covers cross-platform users. No critical steps are Windows-only, and Linux/macOS users can follow the guide without significant friction.
Recommendations
- Explicitly mention that Azure CLI commands work on Linux/macOS and Windows.
- Add a note clarifying that PowerShell is primarily for Windows, but PowerShell Core is available cross-platform.
- Consider including a Bash shell example for resource verification to further demonstrate Linux parity.
- If possible, indicate which steps are OS-agnostic and which are Windows-specific.
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 explicit Linux/macOS shell examples (e.g., Bash), and no mention of Linux-specific tools or patterns. However, Azure CLI is cross-platform and included in all examples, and the documentation refers to both Windows and Linux VM images as supported.
Recommendations
- List Azure CLI examples before PowerShell to reflect cross-platform usage.
- Explicitly mention that Azure CLI works on Linux/macOS and provide Bash shell example syntax where relevant.
- Add a note clarifying that PowerShell Core is available cross-platform, but most Linux users will prefer Azure CLI.
- Ensure that any references to tools or APIs do not assume a Windows environment.
- Consider adding screenshots or terminal output examples from Linux/macOS environments.
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 mild Windows bias by providing a Windows-specific example in the 'Custom file movement solution' section and omitting equivalent Linux/macOS examples. Additionally, the only explicit command-line example references Windows executables and patterns, with no mention of Linux shell scripts or commands.
Recommendations
- Add Linux/macOS equivalents alongside Windows examples, such as shell script usage (e.g., `./doMyWork.sh && ./uploadMyFilesToSql.sh`).
- Explicitly mention that custom scripts can be written in Bash or other Linux-compatible languages, not just Windows executables.
- Provide cross-platform sample commands or clarify that the approach applies to both Windows and Linux nodes.
- Ensure that examples and recommendations do not default to Windows terminology or tools unless necessary.
Batch
Manage private endpoint connections with Azure Batch accounts
.../articles/batch/manage-private-endpoint-connections.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation presents Az PowerShell examples before Azure CLI, which may indicate a Windows-first bias. The PowerShell section is detailed and uses Windows-centric tooling, while the CLI section is present and provides parity for Linux/macOS users. No critical functionality is missing for Linux/macOS users, but the ordering and emphasis may create minor friction.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is cross-platform and preferred by many Linux/macOS users.
- Explicitly mention that both PowerShell and CLI examples are equivalent and available for all platforms.
- Add a note clarifying platform compatibility for each tool.
- Consider including Bash script examples or links to Linux/macOS-specific guidance.
Batch
Quickstart: Create an Azure Batch account using Terraform
...ocs/blob/main/articles/batch/quick-create-terraform.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents both Azure CLI and Azure PowerShell verification steps, but the Azure CLI tab is shown first, followed by Azure PowerShell. There is a slight bias toward Windows environments due to the inclusion of PowerShell examples and the use of PowerShell-specific syntax. However, Linux users are not blocked, as the CLI instructions are cross-platform and shown first.
Recommendations
- Explicitly state that Azure CLI commands work on Linux, macOS, and Windows.
- Clarify that PowerShell examples are primarily for Windows users, and suggest Bash for Linux/macOS users.
- Add a Bash-specific verification tab or section to reinforce Linux parity.
- Where variables are set, show both Bash and PowerShell syntax side-by-side.
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 references both Windows and Linux in some contexts (e.g., port 3389 for Windows RDP, port 22 for Linux SSH), but Windows is consistently mentioned first and there are no explicit Linux/macOS-specific examples, commands, or screenshots. There are no PowerShell-heavy or Windows tool-specific instructions, but the lack of parity in examples and ordering may create minor friction for Linux/macOS users.
Recommendations
- Alternate the order of Windows and Linux mentions, or mention Linux/macOS first in some sections.
- Provide explicit Linux/macOS command-line examples (e.g., Azure CLI, Bash) alongside any portal or Windows-centric instructions.
- Include screenshots or walkthroughs for Linux/macOS environments where relevant.
- Clarify that all steps are applicable to both Windows and Linux pools, and highlight any OS-specific considerations.
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Minor Rdp Bias
Summary
The documentation page generally presents cross-platform APIs and tools, but there is a mild Windows bias in the command-line tools section, where PowerShell cmdlets are listed before Azure CLI, and PowerShell is described in detail. The mention of downloading RDP files for node access is also Windows-centric, as RDP is primarily used on Windows. However, Azure CLI and Batch Explorer are highlighted as cross-platform, and code samples/tutorials are provided for multiple languages. There are no critical omissions for Linux/macOS users.
Recommendations
- List Azure CLI before PowerShell in the command-line tools section to emphasize cross-platform parity.
- Explicitly mention SSH as an alternative to RDP for accessing compute nodes from Linux/macOS.
- Provide examples or links for using Azure CLI to manage Batch resources, alongside PowerShell examples.
- Clarify that Batch Explorer and Storage Explorer are available for all major platforms.
- Ensure that tutorials and code samples include Linux/macOS usage notes where relevant.
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) and Windows-specific patterns (e.g., environment variable syntax, directory path examples) are presented first in examples. Windows-specific details (like drive letters for mounts and app package naming conventions) are described before Linux equivalents. Linux examples are present but often secondary, and PowerShell/cmd usage is assumed for command-line expansion, with Linux shell usage mentioned as an alternative.
Recommendations
- Present Linux and Windows examples side-by-side or alternate which is shown first.
- Include explicit Linux/macOS command-line examples (e.g., bash, sh) wherever Windows cmd examples are given.
- Clarify Linux/macOS-specific behaviors and paths in tables and explanations, not just as afterthoughts.
- Add a section summarizing differences and best practices for Linux/macOS users.
- Avoid Windows-centric terminology (e.g., 'drive letter') without Linux equivalents.
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 Azure CLI and Portal, but does not mention Linux-native tools (e.g., Bash, SDKs) or provide parity for Linux/macOS users. PowerShell is referenced before any Linux-specific alternatives, and no explicit Linux/macOS command-line examples are given.
Recommendations
- Add explicit Linux/macOS command-line examples using Azure CLI (az) for creating public IP addresses.
- Clarify that Azure CLI is cross-platform and provide example commands for both Windows (PowerShell) and Linux/macOS (Bash).
- If possible, include SDK or REST API examples for IP address creation to ensure platform neutrality.
- List Azure CLI before PowerShell to reflect its cross-platform nature.
- Note any OS-specific caveats or requirements for each tool.
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation provides both Windows and Linux command line examples for task execution, but Windows syntax and tools (e.g., 'cmd.exe', 'robocopy', 'setup.exe', MSI) are mentioned first and more prominently. Windows-specific tools are referenced without Linux equivalents, and Windows command line syntax is shown before Linux in key explanatory sections.
Recommendations
- Alternate the order of Windows and Linux examples, or present them side-by-side to avoid implicit prioritization.
- When referencing Windows-specific tools (e.g., 'robocopy', 'setup.exe', MSI), also mention common Linux equivalents (e.g., 'cp', 'rsync', '.sh scripts', 'deb/rpm packages').
- Include explicit Linux/macOS examples for file operations and application installation in start tasks.
- Clarify that all features and workflows are equally supported on Linux/macOS nodes, and link to OS-specific guidance where relevant.
Batch
Associate Azure Batch accounts with network security perimeter
...blob/main/articles/batch/network-security-perimeter.md
Low 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 in detail and before the Azure CLI example, which may indicate a Windows-first bias. There are no Linux/macOS-specific instructions or notes, and PowerShell is primarily a Windows tool, though it is available cross-platform. The CLI example is present and accurate, but the ordering and emphasis may create friction for Linux/macOS users.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is more universally available across platforms.
- Explicitly note that Azure CLI works on Linux/macOS and provide installation links.
- If PowerShell is mentioned, clarify that PowerShell Core is available for Linux/macOS and provide installation guidance.
- Consider adding bash script examples for common tasks, or at least acknowledge Linux/macOS workflows.
- Add a table comparing tool availability and platform support.
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
Summary
The documentation generally maintains good cross-platform parity, but in the section on obtaining managed identity tokens within Batch nodes, the Windows (PowerShell) example is presented before the Linux (Bash) example. No other significant Windows bias is present: both Azure CLI and PowerShell are mentioned for identity creation, and code samples use cross-platform .NET. All critical steps are accessible to Linux/macOS users.
Recommendations
- Present Linux/Bash and Windows/PowerShell examples side-by-side or alternate which is shown first to avoid implicit prioritization.
- Explicitly mention that all steps and code samples are applicable to both Windows and Linux Batch nodes where relevant.
- Where possible, provide Azure CLI examples before or alongside PowerShell to reflect common cross-platform usage.