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 101-125 of 436 flagged pages
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several ways: Windows tools and patterns (such as RDP and DPAPI) are mentioned before or instead of Linux equivalents; code examples and explanations often use Windows-centric commands (e.g., 'cmd /c echo hello') and VM images; and some scenarios (like secret sharing) reference Windows-specific APIs without Linux alternatives. While Linux is addressed in some sections, Windows examples and terminology are generally presented first or exclusively, and Linux-specific guidance is less detailed.
Recommendations
- Provide Linux-first or parallel examples for all code snippets, including command lines (e.g., use 'bash -c "echo hello"' alongside 'cmd /c echo hello').
- Mention Linux tools and patterns (e.g., SSH, Linux file permissions, GPG for secrets) wherever Windows tools like DPAPI or RDP are referenced, and explain their usage.
- Ensure that introductory and scenario explanations do not default to Windows terminology; present both Windows and Linux options equally.
- Expand Linux-specific guidance, such as how to share secrets or configure user accounts using Linux-native methods.
- Add explicit Linux examples in sections where only Windows is shown (e.g., running tasks under named user accounts with elevated access).
Create Pull Request
Batch
Provision a pool in a virtual network
...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 demonstrates subtle Windows bias. While it mentions both Windows and Linux in some contexts (e.g., remote access ports), it tends to list Windows options first (e.g., port 3389 for Windows before 22 for Linux), and does not provide explicit Linux-specific instructions or examples. The prerequisites and creation steps reference Azure PowerShell and the Azure portal, but do not provide command-line examples for Linux users (e.g., Bash or Azure CLI usage). There is no mention of Linux tools or workflows, and the documentation lacks parity in examples for Linux environments.
Recommendations
- Provide explicit Azure CLI (bash) examples for pool and virtual network creation alongside PowerShell and portal instructions.
- List Linux options (e.g., SSH port 22) before or alongside Windows options (e.g., RDP port 3389) to avoid 'Windows first' ordering.
- Include Linux-specific guidance for remote access, troubleshooting, and file mounting (e.g., NFS, SSHFS).
- Reference Linux-native tools and workflows where appropriate, such as using cloud-init or bash scripts for pool configuration.
- Ensure that all examples and screenshots are platform-neutral or provide both Windows and Linux variants.
Batch
Use ephemeral OS disk nodes for Azure Batch pools
...b/main/articles/batch/create-pool-ephemeral-os-disk.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates Windows bias by referencing PowerShell as the primary method for programmatically querying VM capabilities, without mentioning Linux alternatives such as Azure CLI or Bash. The only tool-specific example for checking ephemeral OS disk support is PowerShell, and Windows-centric tools are mentioned before any cross-platform or Linux-native equivalents. There are no explicit Linux command examples or guidance for non-Windows users.
Recommendations
- Add Azure CLI and Bash examples for querying VM capabilities, alongside the PowerShell example.
- Explicitly mention cross-platform tools and provide parity in instructions for both Windows and Linux environments.
- Ensure that any code or command-line examples are available for both Windows and Linux users, and avoid referencing Windows tools exclusively or first.
- Include a note or section highlighting how Linux users can perform equivalent operations, such as using Azure CLI or REST API.
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides both Linux and Windows examples for creating pools with extensions, but there is a noticeable bias towards Windows in several areas. The list of supported extensions includes more Windows-specific extensions (such as Antimalware, Diagnostics, DSC, and multiple GPU drivers for Windows), while Linux equivalents are fewer or missing. Windows tools and concepts (like certificateStoreLocation: LocalMachine, keyExportable, and references to Windows-specific extensions) are mentioned explicitly, and some troubleshooting and extension documentation links prioritize Windows. There is also a lack of parity in example depth and troubleshooting guidance for Linux compared to Windows.
Recommendations
- Expand the list of supported extensions to include more Linux equivalents where possible, or clarify parity gaps.
- Provide troubleshooting steps and log locations for Linux extensions, similar to those given for Windows.
- Ensure that Linux examples are as detailed as Windows examples, especially for advanced configuration options.
- Mention Linux tools and patterns (such as systemd, journald, or Linux certificate stores) where relevant, and provide guidance for their use.
- When listing extensions, alternate between Windows and Linux or group them by OS to avoid implicit prioritization.
- Add explicit notes about any functionality that is only available on Windows, and suggest Linux alternatives or workarounds.
Batch
Provision a pool with Auto OS Upgrade
...-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 OS images and configurations, such as using 'MicrosoftWindowsServer' and 'batch.node.windows amd64' in both REST API and C# SDK examples. There are no equivalent examples or guidance for Linux OS images, agent SKUs, or Linux-specific configuration properties. Windows-specific properties (e.g., 'enableAutomaticUpdates') and tools (Windows Update) are discussed without mentioning Linux alternatives. The documentation does not show how to provision a pool with Auto OS Upgrade for Linux nodes, nor does it mention Linux agent SKUs or image references.
Recommendations
- Add parallel examples for Linux pools, including REST API and SDK code snippets using Linux image references (e.g., Ubuntu, CentOS) and the appropriate nodeAgentSKUId (e.g., 'batch.node.ubuntu 20.04').
- Include Linux-specific configuration properties and explain how automatic OS upgrades work for Linux nodes, including any differences in upgrade mechanisms compared to Windows.
- Mention Linux equivalents to Windows-specific tools and properties, such as how patching and upgrades are handled for Linux VMs.
- Ensure that all sections referencing Windows images, agent SKUs, or configuration properties also provide Linux alternatives or explicitly state their applicability.
- Review the FAQ and requirements sections to include Linux-specific considerations and guidance.
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-specific tools (PowerShell) and patterns are mentioned first or exclusively in several places, such as disk preparation and troubleshooting. PowerShell is presented as the default for certain operations, and Windows-specific advice (directory junctions, Windows Services) is given more detail or appears before Linux equivalents. Linux examples are sometimes present but less detailed or appear after Windows ones.
Recommendations
- Ensure Linux and Windows examples are provided side-by-side for all operational procedures (e.g., disk preparation, troubleshooting).
- Present CLI and Linux-native tools (e.g., bash, lsblk, systemd) before or alongside PowerShell, not after.
- Expand Linux-specific guidance to match the detail given for Windows (e.g., troubleshooting, service management, file cleanup).
- Avoid presenting Windows tools or patterns as the default; use neutral language and order.
- Where PowerShell is referenced, also provide equivalent Azure CLI or bash script examples.
- Add explicit Linux troubleshooting steps and common issues, matching the coverage for Windows.
- Review all sections for parity in recommendations, examples, and terminology for both platforms.
Batch
Create a Batch pool with specified public IP addresses
...docs/blob/main/articles/batch/create-pool-public-ip.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Summary
The documentation page demonstrates Windows bias by listing Azure PowerShell as a method for creating public IP addresses alongside the Azure portal and Azure CLI, with PowerShell mentioned explicitly and equally. There is no mention of Linux-specific tools (such as Bash scripts or native Linux utilities), and the examples do not provide parity for Linux users. The order of methods does not prioritize Linux-first workflows, and the inclusion of PowerShell may imply a Windows-centric approach.
Recommendations
- Add explicit Linux/Bash examples for creating public IP addresses, such as using Bash scripts with Azure CLI.
- Clarify that Azure CLI is cross-platform and provide sample commands for both Windows (PowerShell) and Linux (Bash) environments.
- Reorder the list of creation methods to mention Azure CLI before PowerShell, highlighting CLI as the recommended cross-platform solution.
- Include notes or links for Linux users on installing and using Azure CLI, and avoid implying PowerShell is required.
- Where possible, provide side-by-side examples for both PowerShell and Bash/CLI usage.
Batch
Monitor Batch with Azure Application Insights
...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. Prerequisites and setup instructions focus exclusively on Windows tooling (Visual Studio, WindowsServer VM images, WindowsServer NuGet packages), and all code samples and configuration steps assume a Windows environment. The only example for installing dependencies uses PowerShell, and the VM configuration is for Windows only. There are no Linux equivalents or instructions, nor any mention of cross-platform compatibility or alternative Linux workflows.
Recommendations
- Add Linux-specific instructions for setting up Application Insights in Azure Batch, including supported Linux VM images and configuration.
- Provide examples for installing dependencies using Linux tools (e.g., dotnet CLI, apt, yum) alongside PowerShell.
- Include code samples and configuration steps that work on both Windows and Linux compute nodes, or clearly indicate platform-specific differences.
- Mention and link to cross-platform .NET development environments (e.g., VS Code, JetBrains Rider) in prerequisites.
- Clarify whether the Microsoft.ApplicationInsights.WindowsServer package is required for Linux, and if not, provide guidance for Linux users.
- Describe how to run background telemetry processes on Linux nodes (e.g., using bash scripts or systemd instead of cmd.exe).
Batch
Use certificates and securely access Azure Key Vault with Batch
...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 by exclusively providing PowerShell commands and workflows, referencing Windows-specific tools (such as .msi installers and Windows Management Framework), and omitting any Linux or cross-platform command-line examples. There is no mention of how to perform equivalent tasks on Linux Batch nodes, nor are Bash, Azure CLI, or other cross-platform tools referenced. The structure and language assume a Windows environment as the default.
Recommendations
- Provide equivalent Bash or Azure CLI examples for all PowerShell commands, especially for certificate creation, service principal management, and Key Vault access.
- Explicitly mention Linux support and provide guidance for Linux Batch nodes, including how to install necessary libraries and authenticate using certificates.
- Reference cross-platform tools (such as Azure CLI and OpenSSL) alongside or before Windows-specific tools.
- Include installation instructions for Azure CLI and relevant Python/SDK libraries on Linux nodes.
- Add a section or callouts that highlight any differences or additional steps required for Linux environments.
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by referencing Windows-centric tools and libraries (such as Batch Explorer and the Batch .NET library) without mentioning Linux equivalents or alternatives. All code and tool examples are either platform-neutral or Windows-focused, with no explicit Linux or cross-platform command-line examples (e.g., Bash, CLI, or Python). There is no mention of Linux-specific monitoring patterns, and the Application Insights integration walkthrough is only for .NET (Windows-first).
Recommendations
- Include examples using Azure CLI and Bash scripts for accessing diagnostic logs and metrics, alongside or before any PowerShell/.NET examples.
- Mention and provide guidance for Linux-compatible tools and SDKs (e.g., Python SDK, REST API usage from Bash, or cross-platform monitoring agents).
- Add sample code and walkthroughs for monitoring Batch from Linux environments, such as using Python, curl, jq, or other common Linux utilities.
- Provide parity in Application Insights integration examples by including a walkthrough for a Batch application written in Python or Node.js, running on Linux.
- Explicitly state the cross-platform compatibility of Batch Explorer and other tools, or suggest alternatives if they are Windows-only.
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a mild Windows bias. Windows-specific executable/script types (e.g., .exe, .cmd, .bat, PowerShell) are listed before Linux equivalents, and Windows tooling (RDP, Windows Server 2016 Datacenter with Containers) is mentioned explicitly and sometimes before Linux options. Container support examples focus on Windows images first, with Linux options implied but not detailed. There are no explicit Linux shell or tool examples, and the documentation references Windows patterns and tools more frequently.
Recommendations
- List Linux script types (e.g., shell, Python) before or alongside Windows types when discussing supported executables.
- Provide explicit Linux examples and tooling (e.g., SSH, Linux VM images) in parallel to Windows examples.
- When discussing container support, include examples and instructions for Linux-based container pools (e.g., Ubuntu with Docker) alongside Windows Server options.
- Mention Linux remote access (SSH) before or alongside Windows (RDP) when describing node access.
- Ensure that references to OS-specific features, images, or tools are balanced and not Windows-first.
- Add links to Linux-specific documentation (e.g., provisioning Linux nodes, troubleshooting on Linux) where appropriate.
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
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by exclusively using Windows compute nodes (Windows Server 2019) in the pool creation steps, providing only Windows command line examples (cmd /c), and referencing Windows-specific tools (cmd, timeout). There is no mention of Linux node options, nor are any Linux shell command examples provided for tasks.
Recommendations
- Include instructions and screenshots for creating a pool with Linux compute nodes (e.g., Ubuntu or CentOS).
- Provide equivalent Linux shell command examples (e.g., bash commands) for task creation.
- Mention both Windows and Linux options when describing OS selection for pools.
- Clarify that Azure Batch supports both Windows and Linux nodes, and link to documentation for each.
- Ensure parity in examples and screenshots for both platforms throughout the quickstart.
Batch
Tutorial: Run a parallel workload using the .NET API
...s/blob/main/articles/batch/tutorial-parallel-dotnet.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a significant Windows bias. It exclusively uses Windows VM images for compute pools, references only the Windows build of ffmpeg, and provides command-line examples using Windows syntax (cmd /c, .exe). There are no Linux VM pool configuration examples, nor any Linux-compatible ffmpeg usage or shell command lines. The tutorial does not mention how to adapt the workflow for Linux pools or provide parity for Linux users.
Recommendations
- Add examples for creating Batch pools with Linux VM images, including the necessary configuration (e.g., Ubuntu or other supported Linux distros).
- Provide instructions and sample code for using the Linux build of ffmpeg, including download sources and application package setup.
- Include Linux shell command-line examples (e.g., bash syntax for running ffmpeg) alongside Windows examples.
- Clarify any differences in environment variables, file paths, and execution patterns between Windows and Linux compute nodes.
- Explicitly state cross-platform support and provide guidance for users who wish to run workloads on Linux pools.
Batch
Quickstart: Use .NET to create a pool and run a job
...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 page exhibits a Windows bias by exclusively using Windows Server images for compute nodes, Windows command-line tools (e.g., 'cmd /c type'), and Windows-centric terminology throughout. There are no examples or instructions for using Linux-based pools, nor any Linux shell command equivalents. The documentation assumes Windows as the default environment for both the Batch pool and task execution, and does not provide parity for Linux users.
Recommendations
- Add explicit examples for creating Batch pools with Linux VM images (e.g., Ubuntu, CentOS), including the necessary changes to the VirtualMachineConfiguration and ImageReference.
- Provide Linux shell command equivalents for task execution (e.g., use 'cat' instead of 'type'), and show how to specify these in the CommandLine property.
- Include instructions for running the sample app on Linux, such as using VS Code or the dotnet CLI on Linux, and clarify any platform-specific steps.
- Mention the wide range of supported Linux Marketplace images earlier in the documentation, and provide guidance on selecting and configuring them.
- Ensure that both Windows and Linux options are presented in parallel throughout the documentation, rather than defaulting to Windows.
Batch
Batch security and compliance best practices
...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 page demonstrates several subtle Windows biases. Windows-specific tools and documentation (e.g., PowerShell, Windows registry settings for TLS) are referenced before or more prominently than their Linux equivalents. Examples for discovering supported images reference PowerShell first, and Windows-specific security configuration guidance is detailed, while Linux equivalents are not. There is a lack of Linux-specific examples or links for tasks such as cipher suite management, and the documentation for OS-level security settings is focused on Windows. Overall, Linux is acknowledged as supported, but practical guidance and tooling references are skewed toward Windows.
Recommendations
- Provide Linux-specific examples and links alongside Windows ones, such as using Azure CLI or REST API for supported images.
- Include guidance or references for managing SSL/TLS and cipher suites on Linux distributions, not just Windows registry settings.
- Balance the order of tool references (e.g., mention Azure CLI before or alongside PowerShell).
- Add explicit Linux security best practices, such as recommended patching methods, configuration files, and OS hardening steps.
- Ensure that all remote access, encryption, and compliance sections include Linux-specific instructions or considerations.
Batch
Mount a virtual file system on a pool
...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 exhibits a moderate Windows bias. PowerShell is used as the primary scripting language for both Windows and Linux examples, rather than Bash for Linux. Windows tools and patterns (e.g., 'cmdkey', 'net use', RDP) are described in detail and often before their Linux equivalents. Troubleshooting and manual mounting instructions are more verbose for Windows, and Windows terminology (drive letters, RDP, 'net use') is prominent throughout. Linux-specific tools and commands (e.g., Bash, mount, package installation) are mentioned but not as thoroughly explained or exemplified.
Recommendations
- Provide Bash-based examples for Linux, especially for manual mounting and troubleshooting, rather than using PowerShell for Linux nodes.
- Ensure Linux instructions (e.g., mounting via 'mount' command, package installation with apt/yum) are as detailed as Windows instructions.
- Present Linux and Windows instructions in parallel, giving equal prominence and depth to both platforms.
- Include troubleshooting steps and error message examples that are specific to Linux tools and workflows.
- Reference Linux documentation and community resources as frequently as Windows ones.
- Clarify when PowerShell is required or optional for Linux, and offer native alternatives where possible.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-apis-tools.md
...zure-docs/blob/main/articles/batch/batch-apis-tools.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page shows moderate Windows bias. PowerShell cmdlets are listed first in the command-line tools section, and Remote Desktop (RDP) is mentioned as the example for connecting to compute nodes, which is a Windows-centric pattern. There is a lack of Linux-specific examples or references to SSH for node access, and the code samples and tutorials prioritize .NET/C# (commonly associated with Windows) before Python or JavaScript. While Azure CLI and cross-platform tools are mentioned, Windows tools and patterns are more prominent and appear first.
Recommendations
- Include SSH-based examples and instructions for connecting to Linux compute nodes, alongside or before RDP references.
- Present Azure CLI as the primary cross-platform command-line tool, listing it before PowerShell cmdlets.
- Add explicit Linux/macOS usage notes or examples for command-line tools and application development workflows.
- Ensure code samples and tutorials highlight Python, JavaScript, or Java options equally or before .NET/C# to avoid Windows-first perception.
- Clarify cross-platform compatibility for all tools, especially where installation or usage may differ on Linux/macOS.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-ci-cd.md
...ocs/azure-docs/blob/main/articles/batch/batch-ci-cd.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page exhibits several forms of Windows bias. The example solution is explicitly built for Windows-based Batch nodes, with ARM templates specifying Windows Server images and node agent SKUs for Windows. The application package instructions only reference the Windows version of FFmpeg, and there are no Linux equivalents or examples provided. The pipeline agent specification is set to 'windows-latest', and Azure CLI tasks are configured to use PowerShell Core, which is more common on Windows. There is no mention of Linux-based pools, Linux agent specifications, or Linux application packaging, despite a brief note that Azure Batch supports Linux.
Recommendations
- Provide parallel examples for deploying Linux-based Batch pools, including ARM templates with Linux VM images and node agent SKUs.
- Include instructions for downloading and packaging the Linux version of FFmpeg, and demonstrate how to deploy it to Linux nodes.
- Show how to set the pipeline agent specification to 'ubuntu-latest' or other Linux agents, and provide YAML and task examples for Linux environments.
- Offer Azure CLI task examples using Bash scripts, not just PowerShell Core.
- Add a section or callouts highlighting differences and considerations when deploying to Linux versus Windows nodes.
- Ensure screenshots and repository structures reflect both Windows and Linux scenarios where relevant.
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 demonstrates a moderate Windows bias. Windows-specific terminology (e.g., RDP, port 3389) is mentioned before Linux equivalents (SSH, port 22) in several places. The prerequisites and instructions reference Azure PowerShell before Azure CLI, and there are no explicit Linux-focused examples or screenshots. The documentation does not provide parity in step-by-step instructions or tooling for Linux users, and references to remote access default to Windows (RDP) before Linux (SSH).
Recommendations
- Present Linux and Windows options side-by-side, or alternate which is mentioned first (e.g., 'SSH (Linux, port 22) or RDP (Windows, port 3389)').
- Include explicit examples using Azure CLI commands for Linux users, not just Azure PowerShell.
- Add screenshots or instructions showing the experience on Linux systems (e.g., using SSH for remote access).
- Where tools are listed (Azure portal, PowerShell, CLI), avoid listing PowerShell first or exclusively; clarify cross-platform availability.
- Ensure that references to remote access, networking, and security rules mention Linux and Windows equally, and provide configuration examples for both.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/jobs-and-tasks.md
.../azure-docs/blob/main/articles/batch/jobs-and-tasks.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias. Windows tools and patterns (e.g., 'cmd.exe', 'robocopy', 'setup.exe', MSI installers, %VARIABLE_NAME% syntax) are mentioned first or exclusively in several places, with Linux equivalents provided only as secondary notes or not at all. Examples and tool references (such as 'robocopy' and MSI) are Windows-centric, and there is little mention of Linux-specific tools or workflows. There are no PowerShell examples, but the overall pattern prioritizes Windows approaches.
Recommendations
- Provide Linux-first or side-by-side examples for command lines, such as showing '/bin/sh' and '$VARIABLE_NAME' before or alongside 'cmd.exe' and '%VARIABLE_NAME%'.
- Include Linux-native tools (e.g., 'cp', 'tar', 'unzip') in start task examples, not just 'robocopy' and MSI installers.
- Mention Linux package installation methods (e.g., 'apt-get', 'yum') when discussing application deployment in start tasks.
- Ensure references to environment variable syntax use both Windows and Linux formats equally.
- Add explicit Linux workflow examples and troubleshooting notes where only Windows tools or patterns are currently described.
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 provided exclusively in PowerShell, with no mention of Bash, Linux CLI, or cross-platform alternatives. Windows-specific tools and patterns (e.g., WMF, .msi installers, PowerShell cmdlets) are referenced throughout, and instructions for certificate creation, service principal setup, and Key Vault access are all Windows-centric. There is no guidance for performing these tasks on Linux nodes, nor are Linux tools or workflows mentioned.
Recommendations
- Add equivalent Bash or Azure CLI examples for certificate creation, service principal setup, and Key Vault access.
- Include instructions for installing necessary libraries and tools on Linux Batch nodes (e.g., using apt/yum for Azure CLI or PowerShell Core).
- Reference cross-platform methods for authentication and certificate management, such as using OpenSSL for certificate generation.
- Reorder examples or sections to present both Windows and Linux approaches equally, or clarify platform-specific steps.
- Explicitly mention Linux support and link to relevant documentation for Linux Batch node configuration and Key Vault access.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-account-create-portal.md
...lob/main/articles/batch/batch-account-create-portal.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a bias towards Windows by providing only PowerShell examples for required command-line operations (such as accepting Marketplace terms), without offering equivalent Azure CLI or Bash commands. The documentation references PowerShell cmdlets as a primary tool and does not provide Linux-native command-line alternatives, which may hinder Linux users or those preferring cross-platform tools.
Recommendations
- For every PowerShell example, provide an equivalent Azure CLI (az) command example, especially for critical steps like accepting Marketplace terms.
- When listing management tools, mention Azure CLI before or alongside PowerShell, and provide links to both sets of documentation.
- Explicitly state that all steps can be performed from any OS via the Azure portal and Azure CLI, not just from Windows/PowerShell.
- Add Bash or shell script examples where appropriate to ensure Linux users have clear, native instructions.
- Review all command-line instructions and ensure parity between Windows and Linux environments.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-applications-to-pool-nodes.md
...ain/articles/batch/batch-applications-to-pool-nodes.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page exhibits Windows bias by referencing Windows-specific tools and patterns (such as .exe and .msi installers) without mentioning Linux equivalents. There are no examples or guidance for Linux application packaging or installation methods, and Windows terminology appears first or exclusively in relevant sections.
Recommendations
- Include examples for Linux application deployment, such as using .sh scripts, tarballs, or package managers (apt, yum).
- Mention Linux equivalents when referencing Windows installers (e.g., .msi), such as .deb, .rpm, or source builds.
- Provide sample start task commands for both Windows (PowerShell, .exe) and Linux (bash, shell scripts).
- Clarify that Azure Batch supports both Windows and Linux nodes, and highlight any platform-specific considerations.
- Add links to documentation on Linux node configuration and data transfer best practices.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-aad-auth-management.md
.../blob/main/articles/batch/batch-aad-auth-management.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation page demonstrates a bias toward Windows environments and tooling. All code samples and walkthroughs are based on the .NET library and a C# sample application, which are traditionally Windows-centric. The documentation references the 'Windows Azure Service Management API' and does not provide equivalent Linux or cross-platform examples, nor does it mention Linux-specific tools or workflows. The instructions and screenshots are tailored to the Azure portal, which is platform-agnostic, but the overall context and examples assume a Windows development environment.
Recommendations
- Include equivalent examples using cross-platform languages and SDKs (e.g., Python, Java, or Node.js) that are commonly used on Linux.
- Provide instructions and code samples for authenticating Batch Management solutions from Linux environments, possibly using Azure CLI, Bash scripts, or REST API calls.
- Reference Linux-friendly tools and workflows, such as Azure CLI or PowerShell Core (which is cross-platform), and clarify that the authentication process is not limited to Windows.
- Add a section or callout explicitly stating that the authentication process and APIs are platform-independent, and provide links to Linux and macOS setup guides.
- Where possible, avoid using 'Windows Azure' terminology in favor of 'Azure' to reinforce cross-platform applicability.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-application-packages.md
...blob/main/articles/batch/batch-application-packages.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page demonstrates a Windows bias in several ways. Code examples for deploying and running application packages on Azure Batch are exclusively in C# and use Windows-centric command lines (e.g., 'cmd /c', Windows environment variable formats, Windows image references). There are no Linux shell or Bash examples, and Windows node configuration is shown before Linux equivalents. Windows-specific tools and patterns (such as referencing 'cmd /c' and Windows image references) are used without Linux alternatives. Linux-specific details are only mentioned in passing, mostly in environment variable formatting, and not in code or deployment examples.
Recommendations
- Provide equivalent Linux/Bash code examples alongside Windows examples, especially for task command lines and environment variable usage.
- Show how to configure pools with Linux VM images, including sample imageReference for popular Linux distributions.
- Include Linux-specific instructions for referencing and executing installed application packages (e.g., using Bash, environment variable syntax, and file paths).
- Ensure that examples and explanations are presented in parallel for both Windows and Linux, rather than focusing on Windows first.
- Mention Linux tools and patterns (such as shell scripts) where Windows tools (like cmd.exe) are referenced.
- Add a section or table summarizing differences and best practices for both Windows and Linux compute nodes.