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 26-50 of 156 flagged pages
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
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a strong Windows bias. All code samples are in C# and reference the .NET File Conventions library, with no mention of Linux, cross-platform, or non-Windows development environments. The instructions and code samples assume use of Visual Studio (a Windows-centric IDE), and there are no examples or guidance for using the library or conventions from Linux environments, with other languages, or via command-line tools. References to the Azure Storage client library are specific to .NET, and there is no mention of Linux-compatible alternatives or how to implement the conventions in Linux-based Batch pools.
Recommendations
- Add explicit guidance and code samples for using the File Conventions standard from Linux environments, such as with .NET Core on Linux, or with other languages (e.g., Python, Java).
- Include instructions for setting up and running the sample project on Linux (e.g., using VS Code, JetBrains Rider, or command-line .NET SDK), not just Visual Studio.
- Mention and provide examples for using Azure CLI, Azure Storage Explorer (which is cross-platform), or REST APIs to interact with persisted output files.
- Clarify that the File Conventions standard can be implemented in any language/environment, and link to or provide sample implementations for Linux users.
- Add a section or callout explicitly addressing Linux Batch pool scenarios and any platform-specific considerations.
Create Pull Request
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-task-output.md
...ure-docs/blob/main/articles/batch/batch-task-output.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page exhibits Windows bias by providing examples and instructions that reference Windows-specific patterns (such as .exe files and Windows command syntax) without offering equivalent Linux examples. The only explicit example of running a custom file movement solution uses Windows executables, and there is no mention of Linux shell scripts or tools. The page also references .NET and C# libraries first, with no mention of cross-platform alternatives or parity for Linux users.
Recommendations
- Provide equivalent Linux examples alongside Windows examples, such as using shell scripts (.sh) and Linux command syntax.
- Mention Linux tools (e.g., Bash, rsync, curl) for custom file movement solutions.
- Clarify that the Batch File Conventions library is only for .NET, and suggest cross-platform approaches or libraries for other languages and platforms.
- Include sample commands for both Windows and Linux nodes when describing how to invoke custom scripts or executables.
- Add a sample project or code snippets for Linux environments in the 'Next step' section.
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
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. All code examples are in C# and use Windows-style commands (e.g., 'cmd /v:ON /c'), with no Linux shell equivalents provided. File paths use backslashes by default, with only a brief note for Linux users to change slashes. The only sample project is a Visual Studio solution for .NET, and all tooling references (e.g., NuGet, Visual Studio) are Windows-centric. There are no Linux or cross-platform code samples, nor are there instructions for using Linux tools or SDKs. The documentation also refers to Windows tools and patterns first and exclusively.
Recommendations
- Provide equivalent Linux shell (bash) command examples for task commands, alongside the Windows 'cmd' examples.
- Include code samples in additional languages commonly used on Linux (e.g., Python, Java), and demonstrate use of the Azure SDK for these languages.
- Show file path examples using both Windows (backslash) and Linux (forward slash) conventions, not just a note.
- Offer instructions for using cross-platform editors (e.g., VS Code) and package managers (e.g., pip for Python, Maven for Java) in addition to Visual Studio and NuGet.
- Add a Linux-based sample project or instructions for running the sample on Linux, including any required setup.
- Explicitly mention and demonstrate how to use the Batch service API from Linux environments, not just Windows.
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
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates several forms of Windows bias. Windows tools and patterns (e.g., RDP, DPAPI, 'cmd.exe', 'cmd /c') are mentioned before or instead of Linux equivalents. In code examples, Windows-specific commands are used (such as 'cmd.exe /c echo') without providing Linux shell equivalents (like '/bin/bash -c'). The .NET example for named user accounts is split into Windows and Linux, but only the Windows example includes a full command line for running a task under a named user account. Linux-specific instructions are less prominent, and Linux command examples are missing in several places. Additionally, Windows tools (e.g., DPAPI) are referenced without mentioning Linux alternatives.
Recommendations
- For every example using Windows-specific commands (e.g., 'cmd.exe /c echo'), provide a Linux equivalent (e.g., '/bin/bash -c "echo hello"').
- When referencing Windows tools like DPAPI, mention Linux alternatives for secret management (e.g., GnuPG, file permissions, or other Linux-native approaches).
- Ensure that Linux and Windows instructions/examples are presented with equal prominence and in parallel where possible, rather than Windows first.
- Add explicit Linux code examples for running tasks under named user accounts, including command lines using bash/sh.
- In introductory sections, mention SSH and Linux access patterns before or alongside RDP and Windows.
- Review all code snippets and update them to include both Windows and Linux command-line examples where applicable.
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 Tools
Windows First
Summary
The documentation page demonstrates Windows bias by referencing PowerShell as the primary method for programmatically querying VM capabilities (specifically 'EphemeralOSDiskSupported'), without providing equivalent Linux or cross-platform CLI examples. The mention of PowerShell cmdlets and the lack of Azure CLI, Bash, or other Linux-native tooling examples suggest a preference for Windows tools and patterns. Additionally, Windows-specific tools are mentioned before any Linux alternatives, which are absent.
Recommendations
- Add Azure CLI and Bash examples for querying VM capabilities, such as checking 'EphemeralOSDiskSupported', alongside the PowerShell example.
- Explicitly mention cross-platform tools (e.g., Azure CLI) and provide usage instructions for both Windows and Linux environments.
- Ensure that code and command-line examples are balanced between Windows and Linux, or presented in a platform-neutral way.
- Reference Linux documentation and tools where appropriate, and avoid assuming PowerShell as the default scripting environment.
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 Tools
Missing Linux Example
Windows First
Summary
The documentation page demonstrates a strong Windows bias. All code examples are provided exclusively in PowerShell, with no equivalent Bash or Linux shell commands. Windows-specific tools and patterns (such as PowerShell cmdlets, .msi installers, and references to Windows Management Framework) are used throughout, and there is no mention of how to perform these tasks on Linux Batch nodes. The documentation assumes a Windows environment by default, and Linux alternatives are not discussed or linked.
Recommendations
- Provide equivalent Bash or Azure CLI examples for all major steps, including certificate creation, service principal setup, and Key Vault access.
- Mention and demonstrate how to install necessary tools (e.g., Azure CLI) on Linux Batch nodes, rather than only referencing PowerShell and .msi installers.
- Explicitly state support for both Windows and Linux Batch nodes, and provide parallel instructions or callouts for Linux users.
- Reference Linux tools (e.g., openssl for certificate generation) and show how to authenticate and access Key Vault from Linux scripts.
- Reorder sections or provide tabs so that Linux and Windows instructions are presented with equal prominence.
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 exhibits a mild Windows bias. In several places, Windows tools and patterns (e.g., 'cmd.exe', 'robocopy', 'setup.exe', MSI installers) are mentioned first or exclusively, with Linux equivalents only briefly referenced or omitted. The command-line examples place Windows syntax before Linux, and Windows-specific tools are suggested without Linux alternatives. There are no PowerShell-specific examples, but the overall pattern favors Windows terminology and tools.
Recommendations
- When providing command-line examples, alternate the order or present Linux examples first in some cases.
- Where Windows tools like 'robocopy', 'setup.exe', or MSI are mentioned, also mention common Linux equivalents (e.g., 'cp', 'rsync', '.sh' scripts, '.deb' or '.rpm' packages).
- Explicitly state that both Windows and Linux nodes are supported, and provide parallel examples for both platforms where possible.
- If referencing Windows environment variable syntax, also provide the Linux syntax in equal prominence.
- Where application packaging is discussed, mention Linux-native packaging and installation methods alongside Windows ones.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/low-priority-vms-retirement-migration-guide.md
...s/batch/low-priority-vms-retirement-migration-guide.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides both Azure CLI (cross-platform) and Azure PowerShell (Windows-centric) examples for automating migration to Spot VMs. However, PowerShell is called out as the only alternative to CLI for automation, and is presented before the Azure portal (UI) method. There are no explicit Linux shell or Bash-specific examples, and PowerShell is highlighted as a primary automation method, which may bias towards Windows users. Additionally, the PowerShell section uses Windows-style command syntax and context variables, with no mention of Linux equivalents or cross-platform PowerShell usage.
Recommendations
- Add Bash shell script examples for common migration tasks, especially for validation and automation, to provide parity with PowerShell.
- Clarify that Azure CLI is fully cross-platform and can be used on Windows, Linux, and macOS, and consider listing it as the primary automation method.
- If PowerShell is included, specify that Azure PowerShell can also be run on Linux/macOS (with PowerShell Core), or provide explicit Bash alternatives.
- Where possible, avoid presenting Windows-centric tools (like PowerShell) before platform-agnostic or Linux-native tools.
- Add troubleshooting and validation examples using Bash/CLI pipelines (e.g., using jq or grep with az batch pool show) to help Linux users.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/manage-private-endpoint-connections.md
.../articles/batch/manage-private-endpoint-connections.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation demonstrates a Windows bias by presenting PowerShell examples before Azure CLI, referencing the Az PowerShell module prominently, and using PowerShell-specific syntax. The Azure portal instructions are also more familiar to Windows users. While Azure CLI examples are provided, they appear after the PowerShell section, and there is no explicit mention of Linux or Bash environments.
Recommendations
- Present Azure CLI (cross-platform) examples before PowerShell to emphasize platform neutrality.
- Explicitly mention that Azure CLI commands can be run on Linux, macOS, and Windows, and provide Bash syntax where appropriate.
- Add a note clarifying that PowerShell examples are primarily for Windows users, while Azure CLI is recommended for cross-platform usage.
- If possible, include screenshots or terminal output from Linux environments to reinforce parity.
- Review and balance the prominence of Windows-specific tools and terminology throughout the documentation.
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 exhibits a strong Windows bias. Windows-specific tools (Visual Studio, WindowsServer VM images, cmd.exe) are mentioned exclusively or before any Linux equivalents. The only package installation example is given in PowerShell, and there are no Linux or cross-platform alternatives provided for key steps such as environment setup, package installation, or VM configuration. The documentation does not address how to use Application Insights with Azure Batch on Linux pools, nor does it provide Linux shell commands or mention .NET Core cross-platform compatibility.
Recommendations
- Add Linux-based prerequisites, such as instructions for installing .NET SDK on Ubuntu or other distributions.
- Provide equivalent Linux shell (bash) commands for NuGet package installation (e.g., 'dotnet add package').
- Include examples and configuration steps for deploying Application Insights on Azure Batch pools running Linux VMs (e.g., Ubuntu images).
- Mention and demonstrate how to run the sample code on .NET Core/.NET 6+ for cross-platform compatibility.
- Show how to use Linux-native tools and commands for staging files and running tasks (e.g., using bash scripts instead of cmd.exe).
- Clarify which features or libraries are Windows-only (e.g., Microsoft.ApplicationInsights.WindowsServer) and suggest alternatives or limitations for Linux.
- Add screenshots or walkthroughs for monitoring Linux-based compute nodes in the Azure portal.
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
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation shows a mild Windows bias. Windows tools and patterns (such as .exe, .cmd, .bat, and PowerShell scripts) are mentioned first and in more detail than Linux equivalents. Container support examples focus on Windows Server images, and Docker on Linux is only briefly referenced. There are no explicit Linux shell or scripting examples, and Windows remote access (RDP) is mentioned before Linux (SSH). References to Windows-specific tools and patterns are more prominent, and Linux alternatives are less detailed or omitted.
Recommendations
- Provide Linux shell script examples (e.g., .sh, bash) alongside or before Windows script examples.
- When discussing remote access, mention SSH for Linux nodes before or equally with RDP for Windows nodes.
- In container support sections, include explicit examples and instructions for using Docker on Linux nodes, not just Windows.
- Ensure that Linux tools and patterns (such as mounting disks, using bash scripts, etc.) are described with the same level of detail as Windows equivalents.
- Add links to Linux-specific documentation (e.g., 'Provision Linux compute nodes in Azure Batch pools') in relevant sections, not just as a reference.
- Review all sections to ensure Linux and Windows parity in examples, tool mentions, and ordering.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/pool-endpoint-configuration.md
...lob/main/articles/batch/pool-endpoint-configuration.md
High Priority
View Details →
Detected Bias Types
Windows First
Paired Examples
No Cli Examples
No Linux Tools
Summary
The documentation presents both Windows (RDP) and Linux (SSH) scenarios in parallel, with each example given for both platforms. However, Windows/RDP examples are consistently presented before Linux/SSH examples, and all code samples use high-level SDKs (C# for Windows, Python for Linux) rather than platform-native tools or CLI commands. There are no examples using Powershell, but also no Linux shell or CLI (e.g., Bash, az CLI) examples. The documentation does not mention or recommend platform-specific tools for either OS, but the ordering and language may subtly prioritize Windows.
Recommendations
- Alternate the order of Windows and Linux examples, or present them side-by-side to avoid implicit prioritization.
- Add examples using platform-native tools: Powershell for Windows, Bash or az CLI for Linux.
- Include explicit instructions or code samples for configuring endpoints using CLI commands on both platforms.
- Mention platform-specific considerations or troubleshooting steps for both Windows and Linux environments.
- Ensure that terminology and guidance is equally detailed for both OS types, and avoid language that assumes Windows as the default.
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 exclusively demonstrates creating a pool of Windows compute nodes and provides only Windows-specific command-line examples (e.g., using 'cmd', 'set', 'timeout'). There is no mention of Linux-based pools or equivalent Linux shell commands, and the steps for creating pools and tasks are tailored solely to Windows environments.
Recommendations
- Include instructions and screenshots for creating a pool of Linux compute nodes (e.g., using Ubuntu or CentOS images).
- Provide parallel Linux shell command examples for tasks (e.g., using 'bash -c "env; sleep 90"' instead of 'cmd /c "set AZ_BATCH & timeout /t 90 > NUL"').
- Explicitly mention that Azure Batch supports both Windows and Linux pools, and highlight any differences or considerations.
- Where possible, present both Windows and Linux examples side-by-side, or allow the user to select their preferred OS context.
- Update the narrative to avoid assuming Windows as the default, and ensure Linux users are equally supported throughout the quickstart.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/quick-create-template.md
...docs/blob/main/articles/batch/quick-create-template.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation demonstrates a Windows bias by primarily featuring the Azure Portal (a GUI tool most familiar to Windows users) and referencing Azure PowerShell as the first alternative deployment method. There are no explicit Linux or cross-platform CLI examples, and the only command-line tool mentioned by name is PowerShell. The Azure CLI is mentioned, but only after PowerShell and without any example. There are no Linux shell (bash) or cross-platform scripting examples, nor is there guidance for Linux users.
Recommendations
- Add explicit Azure CLI (az) command examples for deploying the ARM template, with step-by-step instructions.
- Present Azure CLI examples before or alongside PowerShell to emphasize cross-platform parity.
- Include bash shell scripting examples for Linux users.
- Mention and link to Linux-friendly tools (such as Cloud Shell, which is available in the browser and supports both bash and PowerShell).
- Clarify that all deployment methods (Portal, PowerShell, CLI, REST) are cross-platform, and provide links or instructions for each.
- Avoid listing PowerShell before CLI unless there is a technical reason; alternate or randomize order to avoid perceived bias.
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
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation page generally aims for OS neutrality, but there are subtle signs of Windows bias. Windows-specific tools (e.g., PowerShell) are mentioned before or instead of Linux equivalents for certain operations, such as discovering supported images. The section on TLS configuration provides detailed guidance and links for Windows but omits equivalent Linux guidance. There are no Linux-specific examples or references to Linux-native tools (e.g., Bash, Linux configuration files), and where remote access is discussed, RDP (Windows) is mentioned before SSH (Linux).
Recommendations
- When referencing tools for discovering supported images, include Linux-native options (e.g., Azure CLI with Bash) alongside or before PowerShell.
- Provide equivalent guidance and links for configuring SSL/TLS on Linux, not just Windows.
- Where remote access is discussed, mention SSH (for Linux) before or alongside RDP (for Windows), and provide links to relevant Linux documentation.
- Add Linux-specific examples or callouts where OS-level configuration is required, such as patching, security hardening, or disk encryption.
- Review the order of OS mentions to ensure Linux is not consistently secondary to Windows.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/simplified-node-communication-pool-no-public-ip.md
...tch/simplified-node-communication-pool-no-public-ip.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias in troubleshooting sections by presenting Windows (PowerShell) commands before Linux equivalents, and by providing more detailed Windows command examples. In the 'Troubleshooting' section, the Windows PowerShell command (Test-NetConnection) is listed first, with the Linux command (nc) given second and without explanation. There are no Bash or Linux CLI examples for other operations (e.g., ARM deployment, REST API usage), and the portal instructions do not mention cross-platform CLI tools (e.g., Azure CLI) as a primary method.
Recommendations
- Present Linux and Windows command examples side-by-side, or alternate which platform is shown first to avoid implicit prioritization.
- Provide equivalent Bash/Linux CLI commands (e.g., curl for REST API, az CLI for resource management) in all relevant sections, not just PowerShell.
- Expand troubleshooting steps to include Linux-native tools (e.g., dig for DNS, traceroute, etc.) with explanations.
- Instruct users on using Azure CLI and Bash for pool creation and management, not just the Azure portal or ARM templates.
- Ensure that all code snippets and screenshots are platform-agnostic or provide variants for both Windows and Linux environments.
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
Summary
The documentation page exhibits a Windows bias by exclusively using Windows Server VM images for compute pools, referencing Windows-specific ffmpeg builds, and providing only Windows command-line examples (cmd /c, ffmpeg.exe). There are no Linux pool configuration examples, nor any Linux-compatible ffmpeg usage or shell commands. The tutorial does not mention how to adapt the workflow for Linux compute nodes, despite Azure Batch supporting both Windows and Linux environments.
Recommendations
- Add explicit instructions and code samples for creating Linux-based pools, including the appropriate BatchImageReference and node agent SKU for Ubuntu or other supported Linux distributions.
- Provide Linux-compatible ffmpeg application package references and download links (e.g., static Linux builds from ffmpeg.org).
- Include example task command lines using Linux shell syntax (e.g., bash, ./ffmpeg -i ...) alongside the Windows cmd examples.
- Clarify any differences in application package deployment or resource file handling between Windows and Linux nodes.
- Update screenshots and walkthroughs to show both Windows and Linux pool/job/task creation and monitoring where applicable.
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 predominantly features Windows-centric examples and patterns. All code samples use C# and reference Windows VM images, with command lines using Windows syntax (cmd /c, backslashes). While Linux is mentioned in environment variable formatting and application ID restrictions, there are no Linux-specific code samples, shell command examples, or explicit guidance for deploying to Linux nodes. The documentation implicitly assumes Windows as the default platform, which may create friction for Linux/macOS users.
Recommendations
- Add Linux-specific code samples, such as using Linux VM images in pool creation and shell command lines (e.g., bash syntax, forward slashes).
- Include examples of referencing application packages in Linux tasks, showing environment variable usage in bash scripts.
- Clarify any platform-specific differences in deployment, troubleshooting, and file paths.
- Present Windows and Linux examples side-by-side where applicable, or clearly indicate platform-specific instructions.
- Reference cross-platform tools and APIs, not only .NET/C#.
Batch
Migrate Batch account certificates to Azure Key Vault
...in/articles/batch/batch-certificate-migration-guide.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation mentions both Windows and Linux support for the Azure Key Vault VM extension, but provides links to separate documentation for each without giving direct examples or guidance for either platform. Windows is mentioned first in the FAQ section, and there are no concrete Linux command examples or step-by-step instructions for Linux users. Some Linux-specific details are discussed (e.g., certificateStoreLocation, file permissions), but practical examples are missing.
Recommendations
- Provide explicit Linux and Windows example workflows for migrating certificates, including sample commands and configuration snippets.
- Ensure Linux examples are presented alongside or before Windows examples, especially in sections discussing certificate access and installation.
- Include troubleshooting tips specific to Linux environments (e.g., SELinux, file permissions, common errors).
- Add a table or side-by-side comparison of steps for both platforms to highlight parity.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates Windows bias by providing only Windows-centric examples (C# SDK with a Windows VM image), referencing Windows-specific VM images and node agent SKUs, and omitting Linux/macOS equivalents. No Linux VM image update example or cross-platform SDK usage is shown, and the example code uses Windows-specific identifiers and patterns.
Recommendations
- Add example code for updating a pool with a Linux VM image (e.g., Ubuntu or CentOS) and corresponding node agent SKU.
- Include cross-platform SDK usage examples (e.g., Python, CLI, or REST calls that are OS-agnostic).
- Present examples for both Windows and Linux in parallel, or alternate which OS is shown first.
- Explicitly mention Linux/macOS compatibility and provide guidance for those platforms where relevant.
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 more detailed and explicit examples for Windows, including command-line usage and mounting instructions, while Linux equivalents are either less detailed or missing. Windows tools and patterns (cmdkey, net use, mapped drives) are described in depth, with Linux mounting and usage covered only briefly. The azcopy example uses Windows-style syntax, and Linux-specific mounting (e.g., with Azure Files) is not shown. This creates friction for Linux/macOS users who may need to infer or seek out additional steps.
Recommendations
- Add explicit Linux/macOS examples for mounting Azure Files shares (e.g., using mount.cifs or SMB mounting commands).
- Provide azcopy usage examples with Linux/macOS syntax and flags.
- Include parity in step-by-step instructions for both Windows and Linux/macOS, especially for mounting and accessing file shares.
- Reference Linux tools and patterns (e.g., shell commands, fstab configuration) alongside Windows tools.
- Ensure all major workflows (copying, mounting, accessing files) have both Windows and Linux/macOS examples.
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits moderate Windows bias. Windows-specific tools (PowerShell) and patterns are mentioned before or more prominently than their Linux equivalents. Examples for disk preparation and management are more detailed for Windows (with PowerShell commands), while Linux guidance is less explicit and lacks equivalent shell script examples. Some sections, such as directory junctions and service management, focus on Windows-specific issues or features, with Linux alternatives mentioned second or not at all.
Recommendations
- Provide Linux shell script examples (e.g., using fdisk, mkfs, mount) for disk preparation, similar to the PowerShell example for Windows.
- Ensure that Linux tools and patterns (e.g., systemd for service management, symlinks vs. hard-links) are described with equal detail and prominence as Windows equivalents.
- Present both Windows and Linux instructions/examples side-by-side, rather than listing Windows first.
- Include references to Linux-specific troubleshooting and management tools where appropriate.
- Review sections for implicit Windows-first language and rephrase to treat platforms equally.
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 examples and references Windows-centric development patterns (e.g., .NET, Visual Studio, Console.WriteLine). There are no Linux/macOS-specific instructions, nor are there cross-platform considerations or alternative code samples for Linux users. The documentation assumes familiarity with Windows tooling and does not mention Linux development environments, shell equivalents, or platform-specific caveats.
Recommendations
- Add explicit notes clarifying that the .NET library and code samples are cross-platform and can run on Linux/macOS with .NET Core/.NET 6+.
- Provide example commands for installing .NET SDK on Linux/macOS.
- Include sample code snippets showing execution on Linux (e.g., using bash, terminal output, or VS Code on Linux).
- Mention any platform-specific requirements or differences (e.g., authentication, environment variables, file paths).
- Link to documentation or guides for setting up .NET development environments on Linux/macOS.
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 page demonstrates a notable Windows bias: all code samples and walkthroughs use the .NET library and C#, which are traditionally Windows-centric. The referenced sample project (AccountManagement) is C#/.NET only, with no mention of Linux/macOS usage or alternatives. Azure portal instructions use Windows terminology (e.g., 'Windows Azure Service Management API'), and there are no examples or guidance for Linux or cross-platform authentication flows, such as using Python, Java, or CLI tools. The documentation does not address how to run the sample or perform authentication from Linux/macOS environments.
Recommendations
- Add equivalent sample projects and code snippets for Linux-friendly languages (e.g., Python, Java, Node.js) using MSAL.
- Include instructions for authenticating with Microsoft Entra ID using Azure CLI or REST API, which are cross-platform.
- Clarify that the .NET library and C# samples can be run on Linux/macOS via .NET Core, and provide setup instructions.
- Provide explicit steps for Linux/macOS users, including environment setup and any platform-specific caveats.
- Avoid using 'Windows Azure Service Management API' terminology exclusively; clarify cross-platform applicability.
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 Tools
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias, particularly in the 'Accept legal terms' section, where only PowerShell commands are provided for accepting marketplace terms. No equivalent Azure CLI or Bash examples are given, which may hinder Linux/macOS users. Additionally, references to 'Batch PowerShell cmdlets' are listed before Azure CLI in the 'Other Batch account management options' section, and the documentation generally assumes portal or PowerShell usage, which are more common on Windows.
Recommendations
- Provide Azure CLI equivalents for all PowerShell commands, especially for accepting marketplace terms (e.g., az vm image terms accept).
- Explicitly mention that all portal steps are OS-agnostic and clarify when command-line alternatives are available.
- In 'Other Batch account management options', list Azure CLI before PowerShell or present both equally.
- Add Bash or shell script examples where relevant, or link to cross-platform instructions.
- Include a note for Linux/macOS users on how to perform key steps without PowerShell.