Azure Docs
14605
Total Pages
12420
Linux-Friendly Pages
2185
Pages with Bias
15.0%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
2185 issues found
Showing 801-825 of 2185 flagged pages
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/bastion/configure-host-scaling.md
.../blob/main//articles/bastion/configure-host-scaling.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page focuses exclusively on the Azure portal and references PowerShell as the only command-line alternative, with no mention of Linux-native tools, CLI examples, or cross-platform scripting. This creates a Windows-first impression and omits guidance for Linux users.
Recommendations
- Include Azure CLI examples for configuring host scaling, as Azure CLI is cross-platform and widely used on Linux.
- Mention both PowerShell and Azure CLI as alternatives to the portal, and provide links to both sets of instructions.
- Ensure that any command-line instructions are presented in a way that is accessible to users on both Windows and Linux.
- Add a note clarifying that the Azure portal and Azure CLI are both available on all major operating systems.
Create Pull Request
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/bastion/connect-ip-address.md
...docs/blob/main//articles/bastion/connect-ip-address.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Summary
The documentation page demonstrates a Windows-first bias by prioritizing RDP (a Windows protocol) in both the portal and native client connection examples, listing it before SSH. There are no explicit Linux/Unix-specific examples or screenshots, and the instructions do not mention Linux desktop environments or SSH key management on Linux. The use of Azure CLI is cross-platform, but the lack of Linux-focused context or examples (such as connecting from a Linux terminal or using Linux-native tools) results in missing Linux parity.
Recommendations
- Include explicit Linux/Unix examples, such as connecting from a Linux terminal using SSH and managing SSH keys.
- Provide screenshots or instructions that reference Linux desktop environments or SSH clients (e.g., GNOME Terminal, Konsole, or OpenSSH).
- Balance the order of examples: present SSH (Linux/Unix) before or alongside RDP (Windows) to avoid Windows-first bias.
- Mention Linux-specific considerations, such as file paths for SSH keys, and clarify that the Azure CLI commands work on both Windows and Linux.
- If possible, add troubleshooting tips or notes relevant to common Linux SSH/RDP client issues.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/bastion/work-remotely-support.md
...s/blob/main//articles/bastion/work-remotely-support.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing PowerShell before Azure CLI in the 'Next steps' section, and by not providing any explicit Linux or SSH-based examples or references. The focus on PowerShell and lack of Linux-specific guidance may make the documentation less accessible to Linux administrators.
Recommendations
- Provide explicit Linux/SSH examples or references, especially in sections discussing remote access.
- List Azure CLI before or alongside PowerShell to avoid implying Windows-first workflows.
- Include links or sections for Linux/macOS users, such as how to use Azure Bastion with native SSH clients.
- Ensure that all instructions and examples are cross-platform or clearly indicate platform-specific steps.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/bastion/kerberos-authentication-portal.md
...in//articles/bastion/kerberos-authentication-portal.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 throughout. All examples, templates, and verification steps are centered on Windows VMs, Windows Server, and Windows tools (such as Group Policy Editor and PowerShell). There are no Linux equivalents or guidance for configuring Kerberos authentication with Linux VMs, nor are Linux domain controllers or clients mentioned. The ARM template provisions only Windows images, and all automation scripts use PowerShell. References and links are also exclusively to Windows/Active Directory documentation.
Recommendations
- Add parallel instructions and examples for configuring Kerberos authentication with Linux VMs (e.g., Ubuntu, CentOS) as both clients and domain controllers.
- Provide ARM template options or examples for deploying Linux-based domain controllers (e.g., Samba AD DC) and Linux clients.
- Include verification steps for Kerberos authentication on Linux, such as using kinit, klist, and relevant log files.
- Reference Linux documentation for Kerberos and Active Directory integration (e.g., MIT Kerberos, Samba, SSSD).
- Where PowerShell is used, offer Bash or shell script equivalents for Linux environments.
- Clarify in the prerequisites and throughout the document whether Kerberos authentication via Bastion is supported for Linux VMs, and if so, provide explicit guidance.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/batch/batch-applications-to-pool-nodes.md
...in//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 demonstrates Windows bias by referencing Windows-specific file types and installation patterns (e.g., .exe, .msi) without mentioning Linux equivalents. There are no examples or references to Linux tools, file types, or installation methods. The language and examples assume a Windows environment, omitting guidance for Linux users.
Recommendations
- Include Linux-specific examples alongside Windows ones, such as referencing .sh scripts or Linux package managers (e.g., apt, yum) in start tasks.
- Mention Linux installation patterns (e.g., using chmod, tar, or bash scripts) when discussing application deployment.
- Provide sample command lines for both Windows (cmd, PowerShell) and Linux (bash) in relevant sections.
- Explicitly state that the guidance applies to both Windows and Linux pools, and highlight any differences in approach.
- Reference Linux tools (e.g., scp, rsync, wget) in the 'Additional ways to get data onto nodes' section.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/batch/batch-custom-images.md
...-docs/blob/main//articles/batch/batch-custom-images.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by presenting Windows-specific details and examples before Linux equivalents, particularly in connection instructions (RDP for Windows is mentioned before SSH for Linux). There are no explicit Linux command-line examples (e.g., Bash or CLI), and the only code sample for SDK usage uses a Windows node agent SKU ('batch.node.windows amd64') without a Linux equivalent. Additionally, there are no PowerShell or Bash command examples for creating images or pools, and the REST API and CLI sections are OS-neutral but lack Linux-specific context.
Recommendations
- Provide parallel Linux examples wherever Windows-specific instructions are given (e.g., show SSH before or alongside RDP).
- Include Linux node agent SKU examples in the SDK code samples (e.g., 'batch.node.ubuntu 20.04').
- Add Bash/CLI command examples for common tasks such as creating snapshots, images, and pools, not just REST API or .NET SDK.
- When referencing documentation, link to both Linux and Windows guides equally and in parallel.
- Ensure that all steps and considerations are clearly marked for both Windows and Linux users, especially where procedures differ.
Azure Docs
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 First
Windows Tools
Summary
The documentation page focuses exclusively on .NET and C# examples, references the Azure portal (which is cross-platform but often associated with Windows-centric workflows), and uses terms like 'Windows Azure Service Management API.' There are no Linux-specific instructions, CLI examples, or cross-platform code samples. The only sample project referenced is a C#/.NET application, with no mention of equivalent workflows for Linux users or non-.NET languages. This creates a Windows-first impression and omits guidance for developers working in Linux environments.
Recommendations
- Provide equivalent examples using Azure CLI and/or Azure PowerShell, highlighting cross-platform usage.
- Include sample code in languages commonly used on Linux (e.g., Python, Java, Node.js) for authenticating with Microsoft Entra ID and Batch Management.
- Reference and link to Linux-friendly tools and workflows, such as using the Azure CLI for app registration and permission assignment.
- Clarify that the Azure portal and APIs are accessible from any OS, and explicitly mention Linux compatibility.
- Offer a section or callout for Linux/macOS users, outlining any differences or additional steps required.
- If possible, provide a Docker-based or shell script example for running the sample app on Linux.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/batch/batch-pool-vm-sizes.md
...-docs/blob/main//articles/batch/batch-pool-vm-sizes.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is consistently listed as the first example/tool for querying supported VM sizes and images, and is mentioned in every relevant context. While Azure CLI (cross-platform) is also included, there are no explicit Linux shell (bash) examples or references to Linux-native tools. The documentation refers to 'Windows and Linux' images but does not provide Linux-specific guidance, commands, or troubleshooting tips. The overall pattern is to mention Windows/PowerShell first, with Linux support implied but not highlighted.
Recommendations
- Alternate the order of tool references (e.g., list Azure CLI before PowerShell in some sections, especially since Azure CLI is cross-platform and more common on Linux).
- Add explicit bash shell examples for querying VM sizes and images, demonstrating usage on Linux systems.
- Include Linux-specific notes or troubleshooting tips where relevant (e.g., environment variables, file paths, or image selection nuances).
- Where possible, mention Linux-native tools or scripting approaches (e.g., curl with REST APIs, jq for parsing JSON responses).
- Ensure that any references to PowerShell are balanced with equivalent Linux command-line or scripting options.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/batch/batch-account-create-portal.md
...ob/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 Windows bias primarily in the section on accepting legal terms for marketplace images, where only PowerShell commands (Get-AzMarketplaceTerms, Set-AzMarketplaceTerms) are provided. There are no equivalent Azure CLI or Bash examples, which are more common on Linux systems. Additionally, the 'Other Batch account management options' section lists PowerShell cmdlets before Azure CLI, and the only detailed command-line example is for PowerShell. No Linux-specific tools or workflows are mentioned.
Recommendations
- Provide equivalent Azure CLI commands for accepting marketplace legal terms (e.g., using 'az vm image terms accept'), alongside the PowerShell examples.
- When listing management tools, mention Azure CLI before or alongside PowerShell to avoid implying Windows-first workflows.
- Include Bash or shell script examples where appropriate, especially for steps that can be performed cross-platform.
- Explicitly state that all portal-based steps are OS-agnostic, but provide parity in command-line instructions for both Windows and Linux users.
- Consider adding a note or section for Linux/macOS users, highlighting any differences or additional steps required.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/batch/batch-apis-tools.md
...ure-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 demonstrates a mild Windows bias. PowerShell cmdlets are mentioned first and in more detail than Azure CLI, and the use of Remote Desktop (RDP) for node access is highlighted without mentioning SSH or Linux alternatives. The primary code samples and tutorials are .NET/C#-centric, with Python and JavaScript mentioned later. While Azure CLI and cross-platform tools are referenced, the ordering and emphasis favor Windows-native tools and workflows.
Recommendations
- Present Azure CLI before or alongside PowerShell in the command-line tools section, emphasizing its cross-platform nature.
- When describing node access, mention SSH for Linux nodes alongside RDP for Windows nodes, and provide links to relevant SSH documentation.
- Ensure that code samples and tutorials for Python, Java, and JavaScript are given equal prominence to .NET/C# examples, both in tables and in 'Next steps'.
- Explicitly state when tools (like Batch Explorer) are cross-platform, and avoid defaulting to Windows-centric terminology or workflows.
- Add examples or references for managing Batch resources from Linux/macOS environments, where applicable.
Azure Docs
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 several forms of Windows bias. In multiple sections, Windows-specific tools (such as PowerShell and Windows Services) are mentioned before or more prominently than their Linux equivalents. Some examples are provided only for Windows (e.g., PowerShell cmdlets for disk management), while Linux examples are less detailed or missing. Windows-specific patterns (such as directory junctions, Windows service management, and user/group names) are discussed in depth, sometimes without equivalent Linux guidance. Additionally, links and references to Windows tooling or APIs are often listed before or instead of Linux alternatives.
Recommendations
- Ensure that for every Windows-specific example (e.g., PowerShell commands, Windows Services), an equivalent Linux example (e.g., bash commands, systemd services) is provided and given equal prominence.
- When listing tools or APIs (such as for discovering EOL dates or managing disks), mention Azure CLI and Linux-native tools before or alongside PowerShell, not after.
- Where Windows-specific patterns or pitfalls are discussed (such as directory junctions or user/group names), provide corresponding Linux guidance (e.g., symlinks, Linux user/group management) with equal detail.
- In sections where only Windows examples are given (e.g., disk preparation with PowerShell), add equivalent Linux shell script examples.
- Review the ordering of examples and references to avoid always listing Windows first; alternate or group by platform.
- Explicitly call out platform differences and best practices for both Windows and Linux, especially in areas like service management, file system operations, and user/group handling.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/batch/batch-compute-node-environment-variables.md
...cles/batch/batch-compute-node-environment-variables.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation generally presents Windows tools and patterns before their Linux equivalents, such as listing 'cmd.exe' and Windows command syntax first in examples. Windows-specific details (like drive letters for mounts and environment variable naming conventions) are often described in more detail, while Linux information is sometimes less prominent or missing. Some examples and tables use Windows-style paths or syntax without always providing the Linux equivalent.
Recommendations
- Alternate the order of Windows and Linux examples so that Linux is sometimes presented first.
- Ensure all command-line examples are provided for both Windows (cmd.exe or PowerShell) and Linux (/bin/sh or bash), and that both are equally detailed.
- Where Windows-specific details are given (e.g., drive letters, environment variable naming), provide equally detailed Linux equivalents (e.g., mount points, lowercase/underscore conventions).
- In tables that show example paths or environment variable values, always provide both Windows and Linux formats side by side.
- Avoid using only Windows-style path separators (\) in directory postfix examples; include Linux-style (/) as well.
- Where possible, add PowerShell and bash examples for advanced scripting scenarios.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/batch/batch-container-isolation-task.md
...main//articles/batch/batch-container-isolation-task.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing detailed Windows-specific path mappings and terminology (e.g., D: drive, C: drive) before or instead of Linux equivalents. The table of data paths is Windows-centric, and there are no explicit Linux path examples or Linux-specific code snippets. The documentation refers to Windows patterns and tools (drive letters, Windows directory structure) without providing parallel Linux information.
Recommendations
- Add a table or section that explicitly lists the Linux host and container paths for each Azure Batch data path, similar to the Windows mapping.
- Include Linux-specific examples in both the REST API and SDK/C# code snippets, showing Linux-style paths and usage.
- Present Linux and Windows instructions/examples in parallel, or clearly separate them with tabs or headings, to ensure parity.
- Avoid using Windows-specific terminology (like D: drive) without also providing the Linux equivalent (e.g., /mnt/batch/tasks).
- Clarify any differences in behavior or configuration between Windows and Linux nodes, and provide guidance for both.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/batch/batch-task-dependencies.md
...s/blob/main//articles/batch/batch-task-dependencies.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Windows First
Summary
The documentation exclusively provides Windows-centric examples and command lines (e.g., 'cmd.exe /c echo'), with no mention of Linux shells, tools, or cross-platform patterns. All code snippets use Windows command syntax, and there is no guidance for users running Batch tasks on Linux pools. This may confuse or exclude Linux users and does not demonstrate parity.
Recommendations
- For every example using 'cmd.exe /c echo', provide a Linux equivalent using '/bin/bash -c echo' or similar.
- Explicitly mention that Azure Batch supports both Windows and Linux pools, and clarify any differences in task command lines or behaviors.
- Add a section or callout explaining how to adapt the .NET examples for Linux-based pools, including common shell differences.
- Where possible, use cross-platform commands or highlight how to write platform-agnostic task commands.
- Ensure that references to tools or shell environments (e.g., cmd.exe) are balanced with Linux equivalents (e.g., bash), and avoid assuming Windows as the default.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/batch/batch-ci-cd.md
...cs/azure-docs/blob/main//articles/batch/batch-ci-cd.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates a Windows bias by focusing exclusively on deploying Windows-based Batch nodes, using Windows-specific application packages (Windows 64-bit FFmpeg), and providing ARM template examples that only reference Windows VM images. There are no Linux-based deployment examples, no Linux application package instructions, and the agent pool specification defaults to 'windows-latest' without mentioning Linux alternatives. While a note acknowledges Linux support, no practical guidance or parity is provided for Linux users.
Recommendations
- Provide parallel Linux-based examples throughout the documentation, including ARM templates for Linux pools (e.g., using Ubuntu or CentOS images) and Linux application packages.
- Include instructions for downloading and packaging the Linux version of FFmpeg, and demonstrate how to upload and deploy it to Linux Batch nodes.
- Show how to set up the agent pool using 'ubuntu-latest' or another Linux agent in Azure Pipelines, and discuss any differences in pipeline tasks or scripts.
- Add screenshots and YAML snippets that illustrate Linux-specific configurations where appropriate.
- Explicitly mention and demonstrate the use of cross-platform tools (e.g., Bash scripts) in addition to or instead of PowerShell Core, especially in Azure CLI tasks.
- Ensure that all steps, from repository structure to deployment and testing, have Linux equivalents or clear cross-platform guidance.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/batch/batch-parallel-node-tasks.md
...blob/main//articles/batch/batch-parallel-node-tasks.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-based examples and tools. The only detailed code samples are in C# (.NET), which is most commonly associated with Windows development. The main code example for pool creation uses a Windows Server image, and the referenced GitHub sample is a C# console app. There are no Linux shell or cross-platform scripting examples, and Linux is only mentioned in a REST API JSON snippet, not in a full code sample or workflow. Windows terminology and tools (e.g., MicrosoftWindowsServer, Batch .NET) are used exclusively or before Linux equivalents.
Recommendations
- Add equivalent Linux-based code samples, such as Python SDK examples, especially for pool creation and task submission.
- Include shell script (bash) or CLI examples for common operations, not just .NET/C#.
- Show both Windows and Linux VM image configurations side by side in code samples.
- Reference and link to cross-platform or Linux-specific sample projects (e.g., Python, Node.js) in addition to C#.
- Ensure that documentation language and examples are balanced, mentioning Linux and Windows equally and not prioritizing Windows terminology or tools.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/batch/batch-efficient-list-queries.md
...b/main//articles/batch/batch-efficient-list-queries.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Powershell Heavy
Summary
The documentation page exclusively provides C#/.NET code samples and references, with all examples and sample projects targeting the Batch .NET SDK. There are no Linux-specific or cross-platform CLI (e.g., Azure CLI, Bash) examples, and the only mention of command-line interaction is through C# console applications, which are typically associated with Windows development. REST API references are present, but practical usage examples (e.g., curl, Azure CLI) are missing. This creates a bias toward Windows and .NET developers, making it less accessible for Linux users or those preferring scripting environments.
Recommendations
- Add equivalent examples using the Azure CLI for listing and filtering Batch resources, demonstrating use of --query and --filter parameters.
- Include REST API usage examples with curl or httpie, showing how to construct filter, select, and expand queries from the command line.
- Provide Bash or Python SDK examples for common operations, ensuring parity with the C#/.NET samples.
- Explicitly mention cross-platform tools and patterns early in the document, not just .NET-centric approaches.
- Reference sample projects or scripts that run natively on Linux/macOS, not only C# console applications.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/batch/batch-job-prep-release.md
...cs/blob/main//articles/batch/batch-job-prep-release.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 Windows command-line examples (using 'cmd /c' and Windows environment variable syntax), referencing Windows file paths (with backslashes), and omitting any Linux or cross-platform shell equivalents. There are no examples or guidance for users running Batch tasks on Linux nodes, nor any mention of Bash or POSIX shell syntax. The sample output and code exclusively use Windows conventions.
Recommendations
- Provide parallel Linux/Bash examples for job preparation and release task command lines, using Bash syntax and POSIX environment variables.
- Mention that both Windows and Linux compute nodes are supported, and clarify any differences in environment variables or file paths.
- Update sample code and output to include both Windows and Linux variants, or use cross-platform examples where possible.
- Explicitly state how to write cross-platform scripts for job preparation and release tasks, or link to relevant documentation.
- Avoid using only Windows-specific tools (e.g., 'cmd', 'del') in examples; include Linux equivalents (e.g., 'bash -c', 'rm').
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/batch/batch-mpi.md
...Docs/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 examples and walkthroughs use Windows-specific tools (MS-MPI, cmd.exe, .NET/C#), and the installation and execution instructions are exclusively for Windows environments. Linux and Intel MPI are only mentioned in passing, with no concrete examples or code snippets provided for Linux users. The sample code, setup, and troubleshooting steps are all tailored to Windows, leaving Linux users without practical guidance.
Recommendations
- Add parallel Linux-focused sections with equivalent code samples using Python SDK, Bash shell commands, and Intel MPI.
- Provide explicit Linux pool creation examples, including VM configuration and StartTask for installing Intel MPI.
- Include sample coordination and application commands for Linux (e.g., using mpirun/mpiexec with Intel MPI in Bash).
- Reference and link to Linux-specific sample projects and walkthroughs, not just Windows/MS-MPI ones.
- Ensure that all environment variable usage and file path examples are shown in both Windows and Linux syntax.
- Balance the order of presentation so that Linux and Windows are treated equally, rather than Windows-first.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/batch/batch-pool-compute-intensive-sizes.md
...//articles/batch/batch-pool-compute-intensive-sizes.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation provides both Linux and Windows information, but there is a noticeable Windows bias in several areas. Windows examples and tools (such as PowerShell and Remote Desktop) are mentioned explicitly, and the first detailed example is for Windows. The Linux example is less detailed and lacks command-line specifics. Windows-specific tools and patterns (e.g., PowerShell, RDP, Microsoft MPI) are referenced directly, while Linux equivalents are not always provided or are less prominent.
Recommendations
- Ensure Linux and Windows examples are given equal detail and prominence. For each Windows example, provide a Linux equivalent with step-by-step commands.
- When referencing Windows tools (e.g., PowerShell, RDP), also mention and provide instructions for Linux alternatives (e.g., SSH, Bash scripts, OpenMPI).
- Alternate the order of Linux and Windows examples or present them side-by-side to avoid always listing Windows first.
- Provide explicit Linux command-line examples for tasks such as installing drivers, configuring pools, and deploying images.
- Where possible, use cross-platform tools or highlight them, and clarify when a tool is Windows-only.
- Review the 'Next steps' section to ensure Linux resources are as current and accessible as Windows ones.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/batch/batch-management-dotnet.md
...s/blob/main//articles/batch/batch-management-dotnet.md
High Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Powershell Heavy
Summary
The documentation page exclusively provides C#/.NET code samples and references to Windows-centric tools and workflows, such as the .NET library and Visual Studio-style project structures. There are no Linux-specific instructions, shell (bash) examples, or mentions of cross-platform development environments. The content assumes the user is developing on Windows, with no guidance for Linux users or parity in tooling.
Recommendations
- Include equivalent command-line examples using Azure CLI (az) and Bash scripts, which are cross-platform and commonly used on Linux.
- Mention and provide instructions for setting up the .NET SDK and running the code samples on Linux (e.g., using dotnet CLI on Ubuntu).
- Reference cross-platform editors (such as VS Code) and development environments in addition to Visual Studio.
- Add a section or callout explicitly stating that the .NET library and code samples can be used on Linux and macOS, and provide any necessary prerequisites or troubleshooting tips for those platforms.
- Where possible, provide Python or other language examples that are popular in Linux environments, or link to such resources.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/batch/batch-pool-update-properties.md
...b/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 Windows-based VM image example (using 'MicrosoftWindowsServer' and 'batch.node.windows amd64') in the C# SDK sample, with no equivalent Linux example. The documentation also references Windows-specific node agent SKUs and omits any mention of Linux VM images or node agents. No Linux command-line or configuration examples are provided, and the only detailed code sample is Windows-centric.
Recommendations
- Add parallel examples for updating pools with Linux VM images (e.g., using Ubuntu or CentOS publishers and SKUs) and the corresponding Linux node agent SKU.
- Explicitly mention both Windows and Linux options when discussing VM image configuration, including sample values for each.
- Provide at least one code sample or REST API example that demonstrates updating a pool to use a Linux image.
- Reference Linux tools, patterns, or considerations where relevant, ensuring parity in guidance for both platforms.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/batch/credential-access-key-vault.md
...ob/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-based instructions and code samples, referencing Windows-specific tools (such as .msi installers and Windows Management Framework), and omitting any Linux or cross-platform command-line examples. Steps for certificate creation, service principal setup, Key Vault access, and even installation of required libraries are all described using Windows-centric tools and workflows, with no mention of Linux equivalents or Bash/CLI alternatives.
Recommendations
- Provide equivalent Bash/Azure CLI examples for all PowerShell commands, including certificate creation, service principal setup, and Key Vault access.
- Include instructions for installing necessary libraries (e.g., Azure CLI, Python SDK) on Linux nodes, not just PowerShell on Windows.
- Mention and demonstrate cross-platform tools and workflows where possible, such as using OpenSSL for certificate generation or az CLI for resource management.
- Explicitly state which steps are platform-specific and offer parallel guidance for both Windows and Linux environments.
- Add a section or callouts for Linux users, referencing relevant documentation or scripts for common Linux distributions.
Azure Docs
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 page demonstrates a moderate Windows bias. Windows-specific tools and patterns (such as cmdkey, net use, and Windows-style azcopy syntax) are provided in detail, with explicit command-line examples for Windows (including mounting Azure Files and using azcopy with Windows-style switches). In contrast, Linux equivalents are either missing or only briefly referenced (e.g., blobfuse is mentioned but not shown with mounting commands, and Linux azcopy usage is not exemplified). The order of presentation often places Windows approaches and tools before Linux ones, and there is a lack of parity in example depth and clarity.
Recommendations
- Provide equivalent Linux command-line examples wherever a Windows example is given (e.g., show how to mount Azure Files with mount.cifs or SMB on Linux, and provide azcopy examples using Linux syntax).
- Ensure that Linux tools and workflows (such as blobfuse, mount commands, and Linux shell syntax) are given equal prominence and detail as Windows tools.
- Avoid presenting Windows approaches first by default; alternate or parallelize the presentation of Windows and Linux instructions.
- Include PowerShell and Bash examples side by side where scripting is involved.
- Explicitly mention and link to Linux-specific documentation for mounting and accessing Azure Files and Blob Storage.
- Review for any missing Linux-specific guidance, especially for tasks like credential management and persistent mounts.
Azure Docs
https://github.com/MicrosoftDocs/azure-docs/blob/main//articles/dns/dns-custom-domain.md
...zure-docs/blob/main//articles/dns/dns-custom-domain.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 referencing the 'nslookup' tool for DNS validation, with screenshots and instructions that appear to be from the Windows Command Prompt. There are no examples or mentions of equivalent Linux/macOS tools or command-line environments (such as dig, host, or Linux terminal usage). The instructions and screenshots implicitly assume a Windows environment, and there is no guidance for users on other operating systems.
Recommendations
- Include Linux/macOS equivalents for DNS validation, such as 'dig' and 'host', alongside 'nslookup'.
- Provide example commands for both Windows (cmd/PowerShell) and Linux/macOS terminals when demonstrating DNS lookups.
- Add screenshots or terminal output examples from Linux/macOS environments where appropriate.
- Explicitly state that the steps are cross-platform, or provide a section noting differences for Linux/macOS users.
- Where GUI navigation is described, clarify that the Azure Portal is web-based and platform-agnostic, but for command-line validation, offer parity for all major OSes.