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 76-100 of 156 flagged pages
Batch
Persist output data to Azure Storage with .NET File Conventions library
...n/articles/batch/batch-task-output-file-conventions.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a Windows bias by exclusively providing .NET (C#) code samples, referencing Visual Studio 2019 for running the sample project, and omitting any Linux/macOS-specific instructions or alternative tooling. All examples and tooling are oriented toward Windows environments, with no mention of cross-platform development or how to use the library on Linux or macOS. There are no PowerShell-specific examples, but the overall workflow assumes a Windows developer experience.
Recommendations
- Add explicit instructions and examples for using the Batch File Conventions library on Linux and macOS, including how to run .NET Core/.NET 6+ code outside of Visual Studio (e.g., using VS Code, JetBrains Rider, or CLI tools).
- Provide sample commands for installing the library and running code on Linux/macOS (e.g., dotnet CLI usage).
- Clarify that the library is compatible with .NET Core/.NET 6+ and can be used cross-platform, not just in Windows/Visual Studio environments.
- Include references to alternative editors and development environments suitable for Linux/macOS users.
- If there are platform-specific considerations (e.g., environment variables, file paths), document these for Linux/macOS.
Create Pull Request
Batch
Provision a pool with Auto OS Upgrade
...-docs/blob/main/articles/batch/batch-upgrade-policy.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively providing examples for provisioning Azure Batch pools with Windows OS images (e.g., 'MicrosoftWindowsServer', 'WindowsServer', 'batch.node.windows amd64') in both REST API and SDK (C#) sections. There are no equivalent examples or guidance for Linux-based pools, nor are Linux-specific node agent SKUs or image references mentioned. The requirements section references Windows-specific properties (e.g., 'enableAutomaticUpdates') and 'Windows Update', without discussing Linux update mechanisms or configuration. This bias may create friction for users seeking to provision Linux pools with Auto OS Upgrade.
Recommendations
- Add parallel examples for provisioning Linux-based pools, including REST API and SDK (C#) code snippets using Linux image references (e.g., 'Canonical', 'UbuntuServer', 'batch.node.ubuntu 20.04').
- Document Linux-specific configuration requirements, such as update mechanisms and relevant properties for Linux pools.
- Explicitly mention supported Linux OS images and node agent SKUs in the 'Supported OS images' and requirements sections.
- Ensure that both Windows and Linux pool creation workflows are covered equally, ideally presenting them side-by-side or in separate subsections.
Batch
Associate Azure Batch accounts with network security perimeter
...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 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), and the CLI instructions are generic but do not address Linux/macOS specifics or differences. The presence of detailed PowerShell instructions and their order of presentation suggest a moderate Windows bias.
Recommendations
- Add explicit Bash examples for Linux/macOS users where appropriate, especially for Azure CLI commands.
- Clarify that Azure CLI commands work cross-platform and mention any OS-specific considerations.
- Consider presenting Azure CLI instructions before PowerShell, as CLI is more universally available.
- If relevant, mention Linux/macOS tools or workflows for managing Azure resources.
- Add notes or links for Linux/macOS users about installing and using Azure CLI.
Batch
Use Microsoft Entra ID to authenticate Batch Management solutions
.../blob/main/articles/batch/batch-aad-auth-management.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily focused on Windows-centric tools and workflows. All code samples use C#/.NET, and the walkthrough references the AccountManagement sample, which is a C#/.NET project. The instructions and screenshots are based on the Azure portal, which is cross-platform, but there are no examples or guidance for Linux/macOS users, such as using Python, Java, or CLI tools. The documentation refers to the 'Windows Azure Service Management API' and does not mention Linux equivalents or alternative authentication flows for non-.NET environments.
Recommendations
- Add examples using cross-platform languages (e.g., Python, Java) and libraries for authenticating with Microsoft Entra ID.
- Include instructions for using Azure CLI or PowerShell Core (which is cross-platform) to register applications and grant permissions.
- Provide sample code and walkthroughs for Linux/macOS environments, including environment setup and authentication flows.
- Clarify that the process is not limited to Windows and .NET, and highlight platform-agnostic approaches where possible.
Batch
Create a Batch account in the Azure portal
...lob/main/articles/batch/batch-account-create-portal.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias, primarily in the 'Accept legal terms' section, where only PowerShell commands are provided for accepting marketplace terms, with no Azure CLI or Bash equivalents. The order of tool recommendations lists PowerShell first, and there are no explicit Linux/macOS examples for command-line operations. However, the main workflow uses the Azure portal, which is cross-platform.
Recommendations
- Provide Azure CLI and Bash equivalents for all PowerShell command examples, especially for accepting marketplace terms.
- When listing management tools, present Azure CLI before or alongside PowerShell to signal equal support.
- Explicitly mention that all portal steps are OS-agnostic, and link to Linux/macOS-specific guidance where relevant.
- Add a note or section for Linux/macOS users on how to perform prerequisite steps (e.g., marketplace terms acceptance) using their preferred tools.
Batch
Deploy application packages to compute nodes
...blob/main/articles/batch/batch-application-packages.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits a notable Windows bias. All code examples use C#/.NET and reference Windows-specific constructs (e.g., 'cmd /c', Windows image references, Windows environment variable formats) without providing Linux or cross-platform equivalents. The documentation discusses Windows node configuration and environment variable formats first, with Linux details presented only as a secondary note. There are no Linux shell (bash) examples, nor guidance for Linux-specific deployment patterns. The use of Windows-centric tools and patterns (e.g., referencing 'cmd /c', Windows VM images) further increases friction for Linux users.
Recommendations
- Provide parallel Linux examples for all code snippets, including shell/bash command lines and Linux VM image references.
- Show how to configure application packages for Linux pools, including specifying Linux VM images in code.
- Document the differences in environment variable formatting and usage for Linux nodes with explicit examples.
- Include guidance for deploying and executing applications on Linux nodes, such as using bash scripts instead of 'cmd /c'.
- Ensure that cross-platform APIs (e.g., REST, Python, Java) are referenced and exemplified, not just .NET.
Batch
Use Azure Pipelines to build and deploy an HPC solution
...ocs/azure-docs/blob/main/articles/batch/batch-ci-cd.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation demonstrates a notable Windows bias. The example solution exclusively deploys Windows software (FFmpeg) on Windows-based Batch nodes, with ARM templates specifying Windows Server images only. The instructions for uploading the application package direct users to download the Windows 64-bit version of FFmpeg, with no mention of Linux alternatives. The build and release pipeline agent specification is set to 'windows-latest', and Azure CLI tasks are configured to use PowerShell Core, which, while cross-platform, is more commonly associated with Windows workflows. There are no examples or guidance for deploying Linux-based applications or configuring Linux Batch pools, despite a brief note that Linux is supported.
Recommendations
- Provide parallel examples for Linux: Include instructions and ARM template snippets for deploying Linux-based Batch pools (e.g., using Ubuntu or CentOS images).
- Offer Linux application packaging guidance: Demonstrate how to download, package, and deploy the Linux version of FFmpeg, or another open-source application, to Batch nodes.
- Show agent pool selection for Linux: Add steps for configuring the pipeline to use 'ubuntu-latest' or another Linux agent specification.
- Balance examples: Present both Windows and Linux scenarios side-by-side, or alternate which is shown first.
- Clarify cross-platform support: Expand on the note about Linux support, providing links or references to Linux-specific documentation.
Batch
Autoscale compute nodes in an Azure Batch pool
...cs/blob/main/articles/batch/batch-automatic-scaling.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page exhibits a moderate Windows bias. Windows/.NET examples are presented first and in greater detail, with C# code snippets and references to Windows VM images. PowerShell and .NET SDKs are emphasized, while Linux/Python examples are present but less prominent and appear after Windows/.NET content. Windows-specific VM configuration is shown in the .NET example, and Windows terminology is used throughout. There is no mention of Linux command-line tools or shell usage, and REST API/CLI coverage is minimal.
Recommendations
- Present Linux/Python examples before or alongside Windows/.NET examples to ensure parity.
- Include explicit Linux VM configuration examples in .NET and REST API sections.
- Add Azure CLI and REST API examples for autoscale pool creation and management, with Linux-friendly shell commands.
- Reference Linux-specific documentation and quickstart repositories more prominently.
- Ensure that all SDK and API sections include both Windows and Linux VM configuration samples.
- Avoid using Windows terminology exclusively (e.g., PowerShell, WindowsServer images) in general guidance.
Batch
Use the Batch Management .NET library to manage account resources
...cs/blob/main/articles/batch/batch-management-dotnet.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively provides C#/.NET code samples and references to Windows-centric authentication and tooling patterns, without mentioning or demonstrating Linux/macOS-specific workflows, environment setup, or cross-platform considerations. There are no examples or guidance for running the .NET library on Linux or macOS, nor any mention of platform-specific differences or requirements.
Recommendations
- Add explicit statements confirming .NET and Azure SDK support for Linux/macOS, including any prerequisites or platform-specific caveats.
- Provide example commands for installing the .NET SDK on Linux/macOS and running the sample code in those environments.
- Include notes or sections on authenticating with Microsoft Entra ID from Linux/macOS, highlighting any differences in credential acquisition or environment variables.
- Reference cross-platform tooling (e.g., Azure CLI, Bash) where appropriate, or link to equivalent Linux/macOS guides.
- Ensure that sample projects and code snippets are tested and confirmed to work on Linux/macOS, and mention this in the documentation.
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits a Windows bias by prioritizing Windows-related information and examples. Windows VM sizes and OS families are described in detail, with Cloud Services pools referencing only Windows Server versions. The 'windowsConfiguration' section is present, but there is no equivalent 'linuxConfiguration' section or example. Links to VM sizes are provided for both Linux and Windows, but Windows information is often presented first or exclusively in key sections. No Linux-specific configuration examples or notes are given.
Recommendations
- Add explicit examples and documentation for Linux pool configurations, such as a 'linuxConfiguration' section analogous to 'windowsConfiguration'.
- Ensure that references to VM sizes and OS families are balanced, with Linux options described in equal detail and order.
- Provide Linux-specific notes and guidance where Windows-specific details are given (e.g., automatic updates, agent SKUs).
- Where possible, present Linux and Windows options side-by-side rather than Windows-first.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides code examples that exclusively use Windows-centric technologies (C# SDK and Windows VM image), and does not offer Linux/macOS equivalents or examples. The VM image update example specifically references a Windows image and node agent, with no mention of Linux images or how to update pools for Linux nodes. There are no PowerShell examples, but the overall example selection and ordering favor Windows.
Recommendations
- Add example code for updating pools with Linux VM images, including the appropriate node agent SKU.
- Provide sample requests or SDK usage in languages/environments common on Linux/macOS (e.g., Python, Bash, CLI).
- Include Linux-first or cross-platform examples alongside Windows examples, and clarify any OS-specific requirements.
- Explicitly mention how to update pools for Linux nodes, including relevant image references and agent SKUs.
Batch
Use compute-intensive Azure VMs with Batch
...n/articles/batch/batch-pool-compute-intensive-sizes.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation provides both Windows and Linux guidance for configuring Azure Batch pools with HPC and GPU VM sizes, but there is a notable Windows bias. Windows examples (including PowerShell and RDP instructions) are more detailed and appear first in several sections. The example for installing Microsoft MPI is Windows-only, with no equivalent Linux MPI example. Windows-specific tools and patterns (PowerShell, RDP, MSI installers) are described in detail, while Linux instructions are less explicit and rely on external links. Some example tables and step-by-step guides focus on Windows before Linux, and the Linux MPI workflow is only referenced via an external blog link.
Recommendations
- Add a detailed, step-by-step example for installing and configuring MPI workloads on Linux Batch pools, including driver installation and pool setup.
- Provide Linux command-line equivalents for PowerShell and RDP steps (e.g., SSH, Bash scripts) in relevant sections.
- Ensure Linux examples are presented alongside or before Windows examples in each section to avoid ordering bias.
- Expand Linux-specific troubleshooting and configuration guidance, matching the depth of Windows instructions.
- Include explicit instructions for using Linux tools (e.g., apt, wget, SSH) where Windows tools (PowerShell, RDP) are mentioned.
Batch
Storage and data movement for rendering
...rticles/batch/batch-rendering-storage-data-movement.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation provides detailed, step-by-step examples for Windows scenarios (e.g., mounting Azure Files with cmdkey and net use, using Windows paths and tools), while Linux equivalents (such as mounting Azure Files via SMB/cifs or using blobfuse) are mentioned but lack comparable example depth. Windows-specific tools and patterns (cmdkey, net use, Windows path syntax) are presented before or instead of Linux alternatives, and Linux mounting instructions for Azure Files are missing. Azcopy examples use Windows-style syntax and switches, with no Linux shell equivalents shown.
Recommendations
- Add explicit Linux mounting instructions for Azure Files (e.g., using mount.cifs or SMB credentials in a job preparation task).
- Provide azcopy command examples using Linux shell syntax and switches.
- Include Linux/macOS-specific examples for copying files, mounting shares, and running rendering jobs.
- Ensure parity in example depth and clarity for both Windows and Linux workflows.
- Present cross-platform tools and commands in a neutral order, or group by OS for clarity.
Batch
Create task dependencies to run tasks
...cs/blob/main/articles/batch/batch-task-dependencies.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively provides Windows-centric examples, specifically using 'cmd.exe /c echo ...' for task commands. No Linux or cross-platform shell examples (e.g., bash) are given, and Windows command-line tools are referenced throughout. This creates friction for Linux/macOS users who must adapt examples to their environment.
Recommendations
- Provide equivalent Linux/macOS examples using bash (e.g., 'bash -c "echo Flowers"') alongside Windows examples.
- Explicitly mention that the command line for tasks can be platform-specific and provide guidance for both Windows and Linux pools.
- Add a section or note clarifying how to adapt examples for Linux/macOS compute nodes.
- Ensure code samples and illustrations are platform-neutral or show both Windows and Linux variants.
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation displays a moderate Windows bias. Windows-specific tools (e.g., Data Protection API, RDP) are mentioned before or exclusively compared to Linux equivalents. Code examples and explanations often use Windows-centric command lines (e.g., 'cmd /c echo') and VM images (WindowsServer) before Linux alternatives. Some sections, such as running tasks under named user accounts, provide more detailed Windows examples, with Linux examples appearing later or being less emphasized. References to Windows-specific features (DPAPI, RDP) are present, while Linux alternatives (e.g., SSH, file permissions) are less detailed or only briefly mentioned.
Recommendations
- Ensure Linux examples are presented alongside Windows examples, not after or as an afterthought.
- Provide Linux-specific command line examples (e.g., 'bash -c "echo hello"') in code snippets.
- Mention Linux tools and patterns (e.g., GPG, file permissions, SSH) when discussing secrets and access control, not just Windows DPAPI.
- Balance references to RDP and SSH, and provide links to both in equal prominence.
- Where Windows-specific features are discussed, add Linux equivalents or note differences explicitly.
- Consider starting sections with cross-platform neutral explanations before diving into OS-specific details.
Batch
Persist output data to Azure Storage with Batch service API
...cs/blob/main/articles/batch/batch-task-output-files.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong Windows bias: all code samples use C# and Windows-style commands (e.g., 'cmd /c'), with no Linux shell equivalents provided. File path examples use backslashes by default, with only a brief note for Linux users to convert them. The main sample project is a Visual Studio solution, implying Windows development tools. There are no Bash or Linux-native code samples, and Linux/macOS users must infer adaptations themselves.
Recommendations
- Provide equivalent Bash/Linux shell command examples for task commands (e.g., instead of 'cmd /c', show 'bash -c' or similar).
- Show file path examples using forward slashes for Linux/macOS, or use platform-agnostic path construction.
- Include sample projects or instructions for Linux/macOS development environments (e.g., VS Code, CLI).
- Add explicit code samples in other languages/platforms (e.g., Python, Java) that run on Linux.
- Document any platform-specific caveats or differences more thoroughly, not just as a brief note.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates moderate Windows bias in several areas. Windows-specific tools (PowerShell) and examples are mentioned or shown before their Linux equivalents, particularly in sections about discovering EOL dates and preparing data disks. Some guidance is Windows-centric (e.g., directory junctions, Windows Services, autouser pool scope for Windows nodes), and PowerShell is referenced more frequently than Linux shell commands. Linux examples are present but less detailed or appear after Windows instructions.
Recommendations
- Ensure Linux and macOS examples are provided alongside Windows/PowerShell examples, especially for critical tasks like disk preparation and resource discovery.
- Present Linux and Windows instructions in parallel, or alternate which platform is shown first in examples.
- Include equivalent Linux shell commands (e.g., bash, CLI) wherever PowerShell is referenced.
- Expand on Linux-specific best practices (e.g., systemd usage, disk mounting) to match the detail given for Windows.
- Add explicit macOS notes where relevant, or clarify platform limitations.
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation provides both Windows and Linux command line examples, but Windows examples (cmd.exe) are consistently shown first. Windows-specific tools such as 'robocopy', 'MSI', and 'setup.exe' are mentioned for start tasks, with no Linux equivalents or alternatives provided. The documentation references Windows environment variable syntax before Linux, and generally presents Windows-centric patterns and tools without equal Linux/macOS coverage.
Recommendations
- Alternate the order of Windows and Linux examples, or present both together to avoid implicit prioritization.
- Include Linux/macOS equivalents for Windows-specific tools mentioned (e.g., suggest 'cp' or 'rsync' instead of 'robocopy', '.sh' scripts instead of 'MSI/setup.exe').
- Provide explicit Linux/macOS examples for common setup and deployment tasks, such as unzipping archives or installing dependencies.
- Reference environment variable syntax for both platforms equally, and clarify platform-specific differences where relevant.
- Add links or notes for Linux/macOS users on best practices for application deployment and node configuration.
Batch
Use ephemeral OS disk nodes for Azure Batch pools
...b/main/articles/batch/create-pool-ephemeral-os-disk.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page references PowerShell as the example tool for programmatically querying VM capabilities, without mentioning or providing equivalent Linux/macOS CLI or SDK examples. The only tooling example given is Windows-centric, and there is no parity for Linux users in this section. However, the code samples for pool creation are platform-neutral (Python and C# SDK usage).
Recommendations
- Add equivalent Azure CLI and/or Bash examples for querying VM capabilities, especially for checking 'EphemeralOSDiskSupported'.
- Explicitly mention cross-platform tools (e.g., Azure CLI, REST API) alongside PowerShell, and provide links or code snippets for Linux/macOS users.
- Ensure that all tooling instructions are presented in a platform-neutral way, or provide alternatives for each major OS.
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page for monitoring Azure Batch shows a moderate Windows bias. It references Windows-centric tools (Batch Explorer, Batch .NET library, Application Insights for .NET) and provides walkthroughs and code samples only for .NET (Windows-first), with no mention of Linux/macOS equivalents or cross-platform SDKs. There are no examples using Linux tools, CLI, or Python SDKs, and no guidance for accessing logs or monitoring from Linux/macOS environments.
Recommendations
- Include examples using cross-platform tools such as Azure CLI, PowerShell Core, or REST API calls that work on Linux/macOS.
- Provide sample code for monitoring Batch using Python SDK, which is widely used on Linux/macOS.
- Mention and link to Batch Explorer's cross-platform support (if available) or alternative Linux/macOS-compatible tools.
- Add guidance for integrating Application Insights with non-.NET applications (e.g., Python, Java).
- Ensure that monitoring and log access instructions are not limited to Windows-only technologies.
Batch
Migrate low-priority VMs to spot VMs in Batch
...s/batch/low-priority-vms-retirement-migration-guide.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for automation, but PowerShell (a Windows-centric tool) is given its own dedicated section as an 'alternative automation method.' The CLI examples are cross-platform, but PowerShell is highlighted as a main alternative, and no Linux/macOS shell scripting examples (e.g., Bash) are provided. The order of presentation (CLI first, PowerShell second) is reasonable, but the lack of explicit Linux/macOS scripting parity and the focus on PowerShell may create friction for non-Windows users.
Recommendations
- Add explicit Bash shell scripting examples for Linux/macOS users, demonstrating equivalent automation steps.
- Clarify that Azure CLI commands work cross-platform and are recommended for Linux/macOS users.
- Consider mentioning cross-platform automation tools (e.g., Python SDK, REST API via curl) for completeness.
- If PowerShell is shown, note that PowerShell Core is available on Linux/macOS, or provide links to installation guides.
Batch
Quickstart: Use the Azure portal to create a Batch account and run a job
...e-docs/blob/main/articles/batch/quick-create-portal.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exclusively demonstrates creating a pool of Windows compute nodes and provides only Windows command-line examples (cmd.exe syntax). There is no mention of Linux pools, nor are there any Linux shell (bash/sh) examples for task commands. The documentation refers to Windows-specific tools and patterns, such as 'cmd /c', 'timeout', and the selection of 'microsoftwindowsserver' as the OS, without offering Linux alternatives or guidance.
Recommendations
- Include instructions for creating a pool of Linux compute nodes, such as selecting an Ubuntu or CentOS image.
- Provide Linux shell (bash/sh) command-line examples for tasks, e.g., 'echo $AZ_BATCH; sleep 90'.
- Explicitly mention that both Windows and Linux pools are supported, and link to documentation for Linux pool configuration.
- Present Windows and Linux examples side-by-side or indicate OS-specific steps where relevant.
- Clarify any differences in environment variables or task output between Windows and Linux nodes.
Batch
Quickstart: Use .NET to create a pool and run a job
...zure-docs/blob/main/articles/batch/quick-run-dotnet.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is notably Windows-centric: it creates a pool of Windows Server nodes exclusively, uses Windows command-line tools (cmd /c type), and provides no Linux pool or command-line examples. While .NET is cross-platform and prerequisites mention Linux, all workflow and code samples assume Windows environments, leaving Linux users without guidance for equivalent scenarios.
Recommendations
- Add examples for creating Linux-based Batch pools, including the necessary VirtualMachineConfiguration and ImageReference for common Linux distributions.
- Provide sample task command lines using Linux shell commands (e.g., bash -c 'cat <filename>') alongside the Windows cmd examples.
- Explicitly mention how to adapt the quickstart for Linux/macOS environments, including any differences in node agent SKU, image reference, and command-line syntax.
- Clarify in the prerequisites and throughout the guide that both Windows and Linux pools are supported, and link to documentation for Linux pool configuration.
Batch
Azure Quickstart - Create a Batch account - Azure Resource Manager template
...docs/blob/main/articles/batch/quick-create-template.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page primarily describes deploying an Azure Batch account via the Azure portal, with only a brief mention of alternative methods (Azure PowerShell, Azure CLI, REST API) in a single sentence. The link for further deployment methods points to a page focused on PowerShell, which is Windows-centric. There are no examples or instructions for Linux/macOS users (e.g., Bash, Azure CLI usage), and Windows tools/methods are mentioned before Linux equivalents.
Recommendations
- Add explicit Azure CLI examples for deploying the ARM template, including command-line instructions suitable for Linux/macOS.
- Ensure links to deployment methods include both PowerShell and Azure CLI/Bash instructions, not just PowerShell.
- Present deployment options in a neutral order (e.g., 'Azure CLI, PowerShell, REST API, or portal'), rather than listing Windows-centric tools first.
- Include screenshots or walkthroughs for Azure CLI usage on Linux/macOS where appropriate.
Batch
Mount a virtual file system on a pool
...re-docs/blob/main/articles/batch/virtual-file-mount.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell is used as the primary scripting language for both Windows and Linux examples, rather than Bash for Linux. Windows-specific tools and commands (e.g., 'cmdkey', 'net use', RDP) are described in detail, often before their Linux equivalents. Troubleshooting and manual mounting instructions are more verbose for Windows, and Windows examples are frequently presented first. However, Linux instructions and parity are present throughout, and the supported configurations table clearly indicates Linux capabilities.
Recommendations
- Provide Bash-based examples for Linux users, especially for mounting and troubleshooting, rather than relying solely on PowerShell.
- Present Linux and Windows instructions side-by-side or alternate which OS is shown first to avoid 'Windows-first' ordering.
- Expand troubleshooting sections to include more Linux-specific error messages and solutions.
- Reference Linux-native tools (e.g., 'mount', 'cifs-utils', 'nfs-common') and patterns in more detail, not just PowerShell.
- Clarify when PowerShell is required on Linux, and offer alternative approaches using Bash or native Linux utilities.