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 226-250 of 436 flagged pages
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-mpi.md
...tDocs/azure-docs/blob/main/articles/batch/batch-mpi.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias. All code samples, configuration snippets, and walkthroughs use Windows-specific tools (MS-MPI, cmd.exe, .NET/C#), and reference Windows VM images. The installation and execution commands are exclusively for Windows (e.g., MSMpiSetup.exe, cmd /c, mpiexec.exe), and there are no Linux shell or Python examples. Linux and Intel MPI are only mentioned in passing, with no practical guidance or code samples. The code sample and step-by-step instructions require Visual Studio and Windows development tools, with no Linux equivalents or parity.
Recommendations
- Add parallel Linux-focused sections and code samples using Python SDK or Azure CLI, demonstrating how to configure and run multi-instance tasks on Linux pools.
- Provide equivalent shell/bash commands for installing Intel MPI on Linux nodes using StartTask, and show how to run MPI applications with mpirun.
- Include Linux VM pool configuration examples (e.g., Ubuntu images) and show how to set up pools for Linux-based MPI workloads.
- Reference and link to Linux sample repositories more prominently, and provide walkthroughs for building and running MPI applications on Linux.
- Ensure that both Windows and Linux examples are presented side-by-side or in separate clearly marked sections, so users of either platform can follow the documentation equally.
Create Pull Request
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-pool-compute-intensive-sizes.md
...n/articles/batch/batch-pool-compute-intensive-sizes.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Linux and Windows guidance, but there is a notable Windows bias in several areas. Windows examples and tools (such as PowerShell and Remote Desktop) are mentioned explicitly and sometimes before their Linux equivalents. The detailed example for installing Microsoft MPI is only provided for Windows, and the process involves Windows-specific tools. In the pool configuration examples, Windows images and settings are often listed first or in more detail. There is also a reliance on Windows-specific tools (e.g., PowerShell, RDP) in the workflow descriptions.
Recommendations
- Provide Linux-first or parallel Linux and Windows examples in all sections, especially in step-by-step guides.
- Include explicit Linux command-line examples (e.g., using SSH, Bash scripts) where Windows tools like PowerShell or RDP are referenced.
- Add a detailed example for setting up MPI on Linux pools, mirroring the Windows MPI example.
- Ensure that all configuration tables and sample settings are presented in a balanced order (alternating or side-by-side for Linux and Windows).
- Where possible, use cross-platform tools or provide both Windows and Linux command lines/scripts for tasks like driver installation and VM configuration.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-pool-update-properties.md
...ob/main/articles/batch/batch-pool-update-properties.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing only a C# SDK example that uses a Windows VM image (MicrosoftWindowsServer) and node agent (batch.node.windows amd64), with no equivalent example for Linux VM images or Linux node agents. There are no Linux-specific examples, commands, or references to Linux tools or patterns. The documentation implicitly prioritizes Windows by example and omits Linux parity.
Recommendations
- Add parallel examples using Linux VM images (e.g., Ubuntu, CentOS) and the appropriate Linux node agent SKU in the C# SDK example.
- Explicitly mention both Windows and Linux options when discussing VM image configuration, including sample publisher/offer/sku values for popular Linux distributions.
- Provide at least one example that updates a pool to use a Linux image, including the correct nodeAgentSkuId for Linux.
- Where relevant, mention any Linux-specific considerations or differences in pool property updates.
- Ensure that REST/HTTP and SDK examples are balanced between Windows and Linux scenarios.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-rendering-storage-data-movement.md
...rticles/batch/batch-rendering-storage-data-movement.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation exhibits a Windows bias by presenting Windows-specific tools, commands, and patterns before or in greater detail than their Linux equivalents. Examples for file copying and mounting Azure Files are provided only for Windows (using cmdkey, net use, and Windows-style azcopy syntax), while Linux mounting and usage are referenced but not exemplified. The documentation also references Windows tools and workflows (e.g., PowerShell, cmdkey, net use) without providing parallel Linux command-line examples or explicit parity in instructions.
Recommendations
- Provide Linux command-line examples for all file copy and mounting operations, such as using azcopy with Linux syntax, and mounting Azure Files with mount.cifs or SMB utilities.
- Ensure that for every Windows-specific tool or workflow mentioned (e.g., cmdkey, net use), a Linux equivalent (e.g., smbclient, mount -t cifs) is described and exemplified.
- Present Linux and Windows examples side-by-side or in parallel sections, rather than Windows-first or Windows-only.
- Include explicit instructions and code snippets for mounting Azure Files on Linux VMs, not just referencing blobfuse.
- Review the order of presentation to avoid always listing Windows tools and workflows before Linux equivalents.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-sig-images.md
...zure-docs/blob/main/articles/batch/batch-sig-images.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Windows tools and patterns (such as RDP, PowerShell, and Windows-specific instructions) are mentioned before or more prominently than their Linux equivalents. Some examples and instructions are Windows-centric or list Windows first, and there is a lack of parity in providing Linux-specific command-line or tool examples (e.g., no Bash or Linux shell script examples).
Recommendations
- When listing tools or connection methods (e.g., RDP for Windows, SSH for Linux), present both options equally and in parallel, not with Windows first.
- For every PowerShell example or reference, provide an equivalent Bash or Linux shell example where possible.
- When referencing Azure CLI or SDKs, include explicit Linux usage examples (e.g., Bash scripts, Linux shell commands) alongside or before Windows/PowerShell examples.
- In sections describing how to connect to VMs, provide step-by-step instructions for both RDP (Windows) and SSH (Linux), not just a brief mention.
- Ensure that all prerequisites and setup steps are described for both Windows and Linux environments, including any OS-specific considerations.
- Review the order of presentation so that Linux and Windows are given equal prominence, or alternate which is listed first.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-task-dependencies.md
...cs/blob/main/articles/batch/batch-task-dependencies.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation page exhibits a strong Windows bias. All code examples use Windows command-line syntax (cmd.exe /c echo ...), and there are no Linux or cross-platform shell examples. The documentation refers exclusively to Windows tools (cmd.exe), and does not mention Linux shells (bash/sh) or provide equivalent Linux command examples. The structure and examples assume a Windows environment by default, with no guidance for Linux users.
Recommendations
- For every code example using Windows command-line (cmd.exe), provide an equivalent Linux shell (bash/sh) example, e.g., 'bash -c "echo Flowers"'.
- Explicitly mention that Azure Batch supports both Windows and Linux compute nodes, and clarify any differences in task command line syntax.
- Add a section or note explaining how to adapt the examples for Linux pools, including differences in shell invocation and exit code handling if applicable.
- Avoid using Windows tools exclusively in examples; use cross-platform commands where possible (e.g., 'echo' is available on both platforms, but the shell invocation differs).
- Where possible, provide side-by-side or tabbed code samples for Windows and Linux to improve parity and accessibility for all users.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-task-output-file-conventions.md
...n/articles/batch/batch-task-output-file-conventions.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates bias toward Windows environments by exclusively providing .NET (C#) code samples, referencing Visual Studio as the development environment, and mentioning Windows-specific tools and patterns (such as .exe executables and Visual Studio solutions). There are no examples or guidance for Linux users, alternative development environments, or cross-platform .NET usage. The documentation assumes a Windows-centric workflow and does not address Linux or macOS scenarios.
Recommendations
- Provide equivalent code samples and instructions for .NET development on Linux and macOS, including use of cross-platform editors like VS Code and command-line tools like dotnet CLI.
- Mention and demonstrate how to run and build the sample projects using the dotnet CLI, which is available on all major platforms.
- Clarify that the .NET File Conventions library can be used on Linux and macOS, and provide any necessary setup or troubleshooting tips for those environments.
- Avoid references to Windows-specific file extensions (such as .exe) or provide Linux equivalents (such as .dll or cross-platform .NET Core executables).
- Include guidance for uploading application packages and running tasks from Linux/macOS, not just via the Azure portal or Windows tools.
- Explicitly state platform compatibility and provide links to cross-platform .NET documentation.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-task-output-files.md
...cs/blob/main/articles/batch/batch-task-output-files.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation exhibits a strong Windows bias: all code samples use Windows-specific command syntax (cmd.exe), file paths use backslashes by default, and there are no Linux/bash equivalents provided. The only mention of Linux is a note telling users to change backslashes to forward slashes, without any actual Linux example. The code sample and workflow are centered around C#/.NET and Visual Studio, with no mention of cross-platform development tools or languages. The sample project is a Visual Studio solution, further reinforcing the Windows-centric approach.
Recommendations
- Provide equivalent Linux/bash command examples for task commands (e.g., use bash shell syntax in addition to cmd.exe).
- Show file path examples using both Windows (\) and Linux (/) conventions, or use platform-agnostic path joining.
- Include code samples in at least one cross-platform language (e.g., Python) in addition to C#.
- Mention and demonstrate how to use cross-platform development tools (e.g., VS Code, CLI) rather than only Visual Studio.
- Explicitly document any platform-specific considerations (e.g., line endings, shell differences) and provide guidance for both Windows and Linux users.
- Reference and link to Linux-specific Azure Batch documentation or guides, if available.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-upgrade-policy.md
...-docs/blob/main/articles/batch/batch-upgrade-policy.md
High 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 Windows-based pools (e.g., using MicrosoftWindowsServer images and Windows-specific nodeAgentSKUId), referencing Windows-specific configuration properties (such as windowsConfiguration.enableAutomaticUpdates), and omitting any Linux-based pool configuration or examples. There are no Linux image references, node agent SKUs, or Linux-specific configuration guidance, which may mislead users into thinking Auto OS Upgrade is only for Windows pools or make it harder for Linux users to adopt the feature.
Recommendations
- Add parallel examples for Linux-based pools in both REST API and SDK sections, using a popular Linux image (e.g., Ubuntu) and the appropriate nodeAgentSKUId (e.g., batch.node.ubuntu 20.04).
- Include Linux-specific configuration properties and clarify any differences in upgrade behavior or requirements for Linux pools.
- In the requirements section, mention both Windows and Linux configuration properties (e.g., clarify that windowsConfiguration.enableAutomaticUpdates is not relevant for Linux, and note any Linux equivalents if applicable).
- In all code and JSON samples, provide both Windows and Linux variants, or at least alternate between them to ensure parity.
- Explicitly state that Auto OS Upgrade is supported for both Windows and Linux pools (if true), and link to documentation listing supported Linux images.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/create-pool-ephemeral-os-disk.md
...b/main/articles/batch/create-pool-ephemeral-os-disk.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing PowerShell as the only example for programmatically checking VM support for ephemeral OS disks, without mentioning or providing equivalent Linux/CLI commands. Additionally, the only explicit tooling example for querying capabilities is PowerShell, and there is no mention of Bash, Azure CLI, or cross-platform alternatives. While the code samples for SDK usage are platform-neutral (Python and C#), the operational guidance prioritizes Windows tools.
Recommendations
- Add Azure CLI and/or Bash examples for checking VM series support for ephemeral OS disks, alongside or before the PowerShell example.
- Explicitly mention cross-platform tools (e.g., Azure CLI) in the section about programmatically querying VM capabilities.
- Ensure that all operational instructions and examples are provided for both Windows and Linux users, not just PowerShell.
- Consider linking to documentation or guides that show how to perform the same tasks on Linux/macOS environments.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-user-accounts.md
...e-docs/blob/main/articles/batch/batch-user-accounts.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows-first bias in several areas. Windows tools and patterns (such as cmd.exe, Windows Data Protection API, and RDP) are mentioned before or instead of Linux equivalents. Code examples for running tasks often default to Windows command lines (e.g., 'cmd /c echo hello'), and Windows-specific features are described in more detail or earlier than Linux ones. Some Linux-specific details (such as SSH or Linux user configuration) are present but less emphasized, and there are missing Linux command-line examples in several code snippets.
Recommendations
- Provide Linux shell command examples (e.g., 'bash -c "echo hello"') alongside or before Windows 'cmd.exe' examples in all code snippets.
- When referencing Windows tools (e.g., DPAPI, RDP), also mention Linux equivalents (e.g., GnuPG, SSH, or Linux file permissions) and provide links or explanations.
- Ensure that all code samples that show Windows VM configuration or user account creation also include equally detailed Linux examples, not just in .NET but in all supported languages.
- In sections discussing remote access, mention SSH for Linux before or alongside RDP for Windows, and provide parity in guidance and links.
- Review the order of presentation so that Linux and Windows are treated equally, or alternate which OS is presented first in each section.
- Explicitly call out any OS-specific limitations or differences to help users understand cross-platform implications.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-virtual-network.md
...docs/blob/main/articles/batch/batch-virtual-network.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page exhibits subtle Windows bias. While it covers general Azure Batch and networking concepts, it tends to mention Windows-specific tools, ports, and patterns before their Linux equivalents. For example, remote access ports are listed as '3389 (Windows), 22 (Linux)', with Windows (RDP) always preceding Linux (SSH). There is also a lack of explicit Linux CLI or scripting examples (e.g., Bash), and the prerequisites mention Azure PowerShell before Azure CLI. No Linux-specific tooling or command-line examples are provided, and there is no demonstration of Linux-native workflows.
Recommendations
- When listing ports or OS-specific details, alternate the order (e.g., mention Linux/SSH before Windows/RDP in some places) or present them together without preference.
- Provide explicit Linux/Bash command-line examples alongside PowerShell, especially for common tasks like creating virtual networks or subnets.
- Include references to Linux-native tools and workflows (e.g., Bash scripts, Linux CLI usage) in the prerequisites and examples.
- Ensure that all instructions and screenshots are OS-agnostic or provide both Windows and Linux perspectives where relevant.
- Where Azure CLI is mentioned, clarify that it is cross-platform and provide sample commands for both Windows (PowerShell/CMD) and Linux (Bash).
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/nodes-and-pools.md
...azure-docs/blob/main/articles/batch/nodes-and-pools.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation generally covers both Windows and Linux nodes, but there are subtle biases: Windows-specific tools and patterns (e.g., .exe, .cmd, .bat, PowerShell, RDP, Windows Server containers) are mentioned before or more prominently than their Linux equivalents. Some sections (like container support) provide detailed Windows instructions but lack equivalent Linux guidance. There are no Linux-specific command or configuration examples, and Linux tools (e.g., SSH, shell scripts) are referenced less prominently.
Recommendations
- When listing supported script types, mention Linux formats (e.g., shell scripts, Python scripts) before or alongside Windows formats.
- In sections discussing remote access, mention SSH for Linux before or equally with RDP for Windows.
- For container support, provide explicit instructions and examples for both Windows and Linux nodes, including recommended Linux images and setup steps.
- Include Linux-specific examples and references (e.g., mounting disks, using shell scripts in start tasks) wherever Windows examples are given.
- Ensure parity in tool and terminology references (e.g., don't only mention PowerShell or .exe; include bash, sh, and ELF binaries).
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/best-practices.md
.../azure-docs/blob/main/articles/batch/best-practices.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. In several sections, Windows tools (such as PowerShell cmdlets) are mentioned before or more prominently than their Linux equivalents. Some examples and troubleshooting steps are provided only for Windows (e.g., using PowerShell's Get-Disk), while Linux examples are less detailed or appear after Windows. In some cases, only Windows-specific issues (like directory junctions) are discussed, and Linux alternatives are not equally covered. There are also references to .NET SDKs and Windows configuration properties before mentioning cross-platform or Linux options.
Recommendations
- Ensure that all examples and tooling references are provided for both Windows and Linux, and that Linux examples are as detailed as Windows ones.
- When listing tools or APIs (e.g., PowerShell, Azure CLI), mention cross-platform tools (like Azure CLI) first or alongside Windows-specific tools.
- Provide Linux shell command examples (e.g., using lsblk, fdisk, mkfs) wherever PowerShell examples are given, and ensure parity in the level of detail.
- Include troubleshooting tips and best practices for Linux nodes with the same prominence as for Windows nodes.
- Avoid Windows-specific terminology or patterns (such as .NET classes or Windows Services) without also providing Linux equivalents (such as systemd).
- Where Windows-specific issues are discussed (e.g., directory junctions), add corresponding Linux guidance (e.g., symlinks, mount points) for completeness.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/create-pool-public-ip.md
...docs/blob/main/articles/batch/create-pool-public-ip.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing Azure PowerShell as a primary method for creating public IP addresses, and mentioning it before providing any Linux-specific or cross-platform alternatives. While the Azure CLI is mentioned (which is cross-platform), there are no explicit Linux shell or Bash examples, and PowerShell is called out by name. No Linux-specific tools or command-line examples are provided, and the documentation does not clarify parity or differences between Windows and Linux environments for these operations.
Recommendations
- Provide explicit Bash or Linux shell examples for creating public IP addresses using Azure CLI, including sample commands.
- List Azure CLI (which is cross-platform) before Azure PowerShell in the list of methods, or clarify that both are supported equally.
- Clarify that all steps can be performed from Linux, macOS, or Windows, and highlight any OS-specific considerations if they exist.
- Where PowerShell is mentioned, also mention Bash or other Linux-native shells to ensure parity.
- Consider adding a table or section comparing the steps for Windows and Linux users, or explicitly stating that the process is OS-agnostic when using Azure CLI.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/credential-access-key-vault.md
...lob/main/articles/batch/credential-access-key-vault.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. All code examples are exclusively in PowerShell, with no Linux shell or cross-platform alternatives provided. Windows-specific tools and patterns (e.g., PowerShell cmdlets, .msi installers, Windows Management Framework) are referenced throughout, and instructions for certificate creation, service principal setup, and Key Vault access are all tailored to Windows environments. There is no mention of Linux equivalents or guidance for users on Linux-based Batch nodes.
Recommendations
- Provide equivalent Bash/CLI examples for certificate creation (e.g., using OpenSSL) and service principal setup (e.g., using Azure CLI).
- Include instructions for installing necessary Azure libraries on Linux nodes (e.g., Azure CLI, Python SDK).
- Demonstrate how to authenticate to Azure Key Vault from Linux Batch nodes using certificates and managed identities.
- Avoid assuming PowerShell is the default scripting environment; offer cross-platform guidance.
- Reference Linux tools and patterns alongside Windows ones, and ensure both are given equal prominence.
- Add a section or callouts specifically for Linux users, linking to relevant documentation (e.g., 'using Linux compute nodes').
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/monitor-batch.md
...s/azure-docs/blob/main/articles/batch/monitor-batch.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias. While it mentions both Linux and Windows monitoring agents and extensions, Windows tools and .NET libraries are referenced more prominently and with more detailed examples. There are no Linux-specific code samples or references to Linux-native tools or SDKs, and the only application-level monitoring walkthrough is for a .NET (Windows-centric) solution. No PowerShell or CMD examples are present, but the lack of Linux CLI or SDK examples and the focus on Windows/.NET tools indicate a Windows-first approach.
Recommendations
- Add Linux-specific examples for accessing and analyzing Batch logs, such as using Azure CLI, Bash scripts, or Python SDK.
- Provide walkthroughs or code samples for monitoring Batch from Linux environments, not just .NET/Windows.
- Mention and link to cross-platform SDKs (e.g., Python, Java) and show how to use them for monitoring tasks.
- Include references to Linux-native tools (e.g., jq for JSON parsing, Bash scripting) when discussing log file access and analysis.
- Ensure parity in agent/extension documentation by providing equal detail and examples for both Linux and Windows.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/monitor-application-insights.md
...ob/main/articles/batch/monitor-application-insights.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a strong Windows bias. It exclusively references Windows tools and patterns, such as Visual Studio, the Microsoft.ApplicationInsights.WindowsServer NuGet package, and Windows-specific VM images. All code and configuration examples assume a Windows environment, including PowerShell commands and Windows batch commands (cmd /c). There is no mention of Linux equivalents, nor are there any Linux-specific instructions or examples for integrating Application Insights with Azure Batch on Linux compute nodes.
Recommendations
- Provide parallel Linux instructions and examples, including how to install and configure Application Insights on Linux-based Batch nodes.
- Include Linux-friendly package installation commands (e.g., dotnet CLI, apt, yum) and avoid assuming Visual Studio as the only development environment.
- Show how to configure Application Insights for .NET Core/.NET 5+ applications running on Linux, including relevant config file locations and environment variables.
- Demonstrate how to set up Batch pools using Linux VM images, and provide sample pool configuration for both Windows and Linux.
- Replace or supplement PowerShell and cmd examples with Bash or shell script equivalents.
- Clarify any platform-specific limitations or differences in Application Insights support between Windows and Linux.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/quick-create-portal.md
...e-docs/blob/main/articles/batch/quick-create-portal.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively providing instructions and examples for creating and using Windows-based compute nodes (specifically Windows Server 2019) in Azure Batch. The task command line example uses Windows-specific commands (cmd, set, timeout), and there is no mention of Linux pools, Linux VM images, or equivalent Bash command lines. No Linux or cross-platform alternatives are provided at any step.
Recommendations
- Include parallel instructions and screenshots for creating a Linux-based pool (e.g., using Ubuntu or CentOS images) alongside the Windows example.
- Provide Linux-equivalent command line examples for tasks (e.g., using Bash: `bash -c 'env | grep AZ_BATCH; sleep 90'`).
- Explicitly mention that Azure Batch supports both Windows and Linux nodes, and help users choose the appropriate OS for their workloads.
- Where possible, use cross-platform language or clarify when steps are OS-specific.
- Add a section or callout guiding users to Linux-specific documentation or quickstarts if available.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/quick-run-dotnet.md
...zure-docs/blob/main/articles/batch/quick-run-dotnet.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a clear Windows bias. It exclusively uses Windows Server for compute nodes, configures the pool with a Windows image, and provides only Windows command-line examples (e.g., 'cmd /c type'). There are no Linux VM or command-line examples, and the workflow assumes Windows environments for both pool configuration and task execution. Linux equivalents are not mentioned or demonstrated.
Recommendations
- Add parallel Linux examples throughout the documentation, including pool creation with a Linux Marketplace image and corresponding VirtualMachineConfiguration/ImageReference code.
- Show how to specify a Linux command line for tasks (e.g., using '/bin/bash -c cat ...' instead of 'cmd /c type ...').
- Explicitly mention that Azure Batch supports both Windows and Linux pools, and provide guidance on choosing and configuring each.
- Include sample code snippets and configuration for both Windows and Linux scenarios side by side.
- Clarify in the prerequisites and instructions that the quickstart can be completed on both Windows and Linux development environments, and provide any OS-specific notes as needed.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/tutorial-parallel-dotnet.md
...s/blob/main/articles/batch/tutorial-parallel-dotnet.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Powershell Heavy
Summary
The documentation demonstrates a strong Windows bias. It exclusively uses Windows Server VM images for compute pools, references Windows-specific ffmpeg builds and command-line syntax (cmd /c, .exe), and names pools and jobs with 'Win' prefixes. There are no examples or guidance for running the workload on Linux pools, nor are Linux-compatible ffmpeg packages or shell syntax shown. The workflow and code are tailored to Windows environments, with no parity for Linux users.
Recommendations
- Provide parallel Linux examples: Show how to configure a Batch pool with a Linux VM image (e.g., Ubuntu), including the necessary BatchImageReference and node agent SKU values.
- Demonstrate Linux-compatible ffmpeg usage: Reference a Linux build of ffmpeg, and show how to package and use it as an application package.
- Show Linux shell command lines: Include examples using bash/sh syntax (e.g., ./ffmpeg instead of ffmpeg.exe, and without cmd /c).
- Use neutral naming: Avoid pool/job names like 'WinFFmpegPool' and use OS-neutral identifiers.
- Add guidance for cross-platform support: Explain how to adapt the sample for both Windows and Linux, and highlight any differences in configuration or command lines.
- Mention both OS options early: In the prerequisites and pool creation sections, explicitly mention that both Windows and Linux pools are supported and provide links or code for both.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/security-best-practices.md
...cs/blob/main/articles/batch/security-best-practices.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation generally states that Azure Batch supports both Linux and Windows, but there are several subtle biases toward Windows. Windows-specific security configuration (TLS/cipher suites) is discussed in detail, with direct links to Windows Server documentation, while equivalent Linux guidance is missing. The only command-line tool explicitly referenced for querying supported images is PowerShell, with the Azure CLI mentioned only as an afterthought. There are no Linux-specific examples or references to Linux security practices (e.g., SSH hardening, Linux-specific patching guidance), and Windows terminology (RDP, registry settings) is more prominent and explained in greater detail.
Recommendations
- Add Linux-specific security guidance, such as links to official documentation on securing SSH, managing Linux TLS/cipher suites, and patching best practices.
- When referencing command-line tools, provide Azure CLI examples before or alongside PowerShell, and ensure parity in instructions.
- Include explicit Linux examples or notes wherever Windows-specific details are provided (e.g., mention SSH configuration and hardening alongside RDP).
- Balance references to Windows and Linux tools/documentation, ensuring both are equally discoverable and detailed.
- Where OS-specific configuration is discussed (such as TLS/SSL settings), provide equivalent Linux instructions or links to authoritative Linux resources.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/tutorial-run-python-batch-azure-data-factory.md
.../batch/tutorial-run-python-batch-azure-data-factory.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation exhibits a Windows bias by exclusively providing instructions and examples that assume a Windows environment. It specifies the use of Windows-based Batch node images (Dsvm Win 2019), uses Windows command-line syntax (cmd /c), and does not mention or provide alternatives for Linux-based Batch pools or Linux command-line usage. All tooling (Batch Explorer, Storage Explorer) is cross-platform, but the workflow and commands are tailored to Windows, with no guidance for Linux users.
Recommendations
- Include instructions for creating a Batch pool with a Linux image (e.g., Ubuntu) and provide equivalent steps.
- Provide Linux shell command equivalents (e.g., use bash syntax instead of cmd /c) for installing Python packages and running scripts.
- Show how to specify a Linux start task (e.g., /bin/bash -c "pip install ...") and how to run the Python script in a Linux environment.
- Clarify that Batch Explorer and Storage Explorer are cross-platform, and note any differences in usage or UI on Linux.
- Add screenshots or notes for Linux users where UI or workflow may differ.
- Explicitly mention Linux as a supported platform in the prerequisites and throughout the tutorial.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/virtual-file-mount.md
...re-docs/blob/main/articles/batch/virtual-file-mount.md
High 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 interface for both Windows and Linux examples, rather than showing native Linux shell commands. Windows tools and patterns (e.g., 'net use', 'cmdkey') are described in detail, and Windows-specific troubleshooting steps and references are often presented before or more prominently than their Linux equivalents. The documentation also references Windows tools and workflows in several places, sometimes before mentioning Linux alternatives.
Recommendations
- Provide native Linux shell (bash) examples alongside or instead of PowerShell for Linux scenarios, especially for manual mounting and troubleshooting.
- Balance the order of presentation so that Linux and Windows instructions/examples are given equal prominence, or alternate which comes first.
- Include Linux-native troubleshooting commands (e.g., 'mount', 'dmesg', 'journalctl') and log file locations, not just Windows RDP and log file paths.
- Reference Linux-specific documentation and tools (such as mount.cifs, mount.nfs, systemd unit files) where appropriate.
- Clarify when PowerShell is required on Linux, and offer alternatives for users who prefer bash or other shells.
- Ensure that all code snippets and workflows are equally detailed for both platforms, avoiding extra detail or explanation for Windows-only 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
Summary
The documentation page on deploying application packages to Azure Batch compute nodes exhibits a moderate Windows bias. Code examples for deploying and executing application packages are shown only for Windows environments (e.g., using 'cmd /c' and referencing Windows paths), with no equivalent Linux shell examples. The primary code samples use C#/.NET and reference Windows VM images first. Linux-specific instructions are limited to brief notes about environment variable formatting, without showing how to execute installed applications on Linux nodes.
Recommendations
- Provide Linux-specific code examples for deploying and executing application packages, such as using bash or sh in the task command line.
- Show how to reference and run installed applications on Linux nodes, including sample command lines and environment variable usage.
- When presenting code samples, alternate or parallel Windows and Linux examples, or clearly label them as OS-specific.
- Reference Linux VM images in pool creation examples, or provide both Windows and Linux pool configuration samples.