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 151-156 of 156 flagged pages
Batch
Plan to manage costs for Azure Batch
...-docs/blob/main/articles/batch/plan-to-manage-costs.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page occasionally references Windows-specific resources, such as linking to the Windows pricing page for virtual machines, and lists 'operating system' and 'operating system license' as key cost factors without clarifying Linux options. However, most content is platform-neutral and does not provide examples or instructions that are exclusive to Windows or PowerShell. There are no explicit Linux/macOS examples, but also no Windows-only commands or tools.
Recommendations
- When referencing virtual machine pricing, include both Windows and Linux pricing pages, or clarify that Linux VMs may have different cost structures.
- Explicitly mention Linux as an operating system option when discussing VM selection and licensing costs.
- Provide links to documentation about Linux VM management and cost optimization, alongside Windows resources.
- If examples or screenshots show OS-specific options, ensure Linux is represented.
- Clarify that Azure Batch supports both Windows and Linux workloads, and note any cost differences.
Create Pull Request
Batch
Azure Quickstart - Create a Batch account - Bicep file
...re-docs/blob/main/articles/batch/quick-create-bicep.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment, validation, and cleanup tasks. However, PowerShell examples are given equal prominence to CLI, and PowerShell is a Windows-centric tool. There is no explicit mention of Linux/macOS-specific considerations, nor are there examples using Bash scripting or alternative Linux-native tools. The CLI examples are cross-platform, but PowerShell's inclusion and parity may suggest a slight Windows bias, especially for users unfamiliar with PowerShell on non-Windows systems.
Recommendations
- Clarify that Azure CLI is fully cross-platform and recommended for Linux/macOS users.
- Add notes or links for installing Azure CLI on Linux/macOS.
- Consider providing Bash script examples for automation on Linux/macOS.
- Explicitly mention that PowerShell Core is available on Linux/macOS, if relevant, or clarify its usage.
- List CLI examples first to emphasize cross-platform compatibility.
Batch
Batch security and compliance best practices
...cs/blob/main/articles/batch/security-best-practices.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias. References to Windows-specific tools (such as PowerShell) are present, and Windows OS configuration guidance (TLS/cipher suites) is more detailed than for Linux. Examples for discovering supported images mention PowerShell before Azure CLI, and links for OS-level security settings are Windows-centric. There are no explicit Linux command-line examples or references to Linux-specific security practices, and Windows is often mentioned first when discussing OS support.
Recommendations
- Provide Linux-specific examples and guidance where Windows tools or settings are referenced (e.g., how to list supported images using Bash/Azure CLI).
- Include links to Linux OS security documentation (e.g., TLS/cipher suite configuration for Ubuntu, CentOS, etc.) alongside Windows references.
- Ensure parity in detail for both Windows and Linux OS configuration, especially for security-related sections.
- Alternate the order of OS mentions or explicitly state that guidance applies equally to both platforms.
- Add Linux/macOS command-line examples (e.g., using Azure CLI, Bash scripts) where PowerShell is referenced.
Batch
Quickstart: Create an Azure Batch account using Terraform
...ocs/blob/main/articles/batch/quick-create-terraform.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for verifying results, but the PowerShell example is given equal prominence and detail. The PowerShell section uses Windows-specific syntax and tools, which may not be available or familiar to Linux/macOS users. However, the Azure CLI example is present and shown first, which is cross-platform. No critical steps are Windows-only, but the inclusion of PowerShell may suggest a slight Windows bias.
Recommendations
- Clarify that Azure CLI is cross-platform and recommended for Linux/macOS users.
- Add explicit notes indicating that Azure PowerShell is primarily for Windows, and provide guidance for Linux/macOS users to use Azure CLI.
- Consider listing Azure CLI instructions before PowerShell, and make CLI the default example.
- If possible, include bash-specific notes or troubleshooting tips for Linux/macOS environments.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/account-key-rotation.md
...-docs/blob/main/articles/batch/account-key-rotation.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides instructions for rotating Batch account keys primarily through the Azure portal, without offering any command-line examples. There are no examples using Windows-specific tools (e.g., PowerShell), but there is also a lack of parity for Linux users, as no CLI (Azure CLI, Bash) or cross-platform automation instructions are provided.
Recommendations
- Add Azure CLI examples for key rotation, which are cross-platform and can be used on both Windows and Linux.
- Include Bash script snippets for automating key rotation, demonstrating how Linux users can perform these tasks.
- If PowerShell examples are added in the future, ensure that equivalent Bash/Azure CLI examples are also provided.
- Explicitly mention that the Azure portal is accessible from any OS, but highlight command-line options for automation and scripting.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/private-connectivity.md
...-docs/blob/main/articles/batch/private-connectivity.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation provides only Azure Portal (GUI) instructions for configuring private endpoints with Azure Batch accounts. There are no command-line examples (such as Azure CLI, PowerShell, or Bash scripts) for either Windows or Linux. However, the absence of any CLI examples means Linux users (who often prefer or require CLI-based automation) are not served. There is also no mention of Linux-specific tools or considerations, nor any explicit Windows bias in the form of PowerShell or Windows tool references.
Recommendations
- Add Azure CLI examples for all major steps (creating private endpoints, configuring DNS zones, migrating DNS zones, etc.), as Azure CLI is cross-platform and widely used on Linux.
- Include Bash script snippets for common automation scenarios.
- If PowerShell examples are added, ensure Azure CLI or Bash equivalents are provided alongside.
- Mention any Linux-specific considerations (e.g., editing /etc/hosts, using dig/nslookup on Linux, DNS resolver configuration).
- Clarify that all steps can be performed from Linux, macOS, or Windows environments using Azure CLI.