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 326-350 of 436 flagged pages
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 page exclusively provides .NET (C#) code samples and references to Windows-centric development tools and workflows, with no mention of Linux-specific usage, cross-platform considerations, or parity in examples. All code snippets and sample projects are C#/.NET, which is most commonly associated with Windows environments, and there is no guidance for running these workflows on Linux or using Linux-native tools.
Recommendations
- Add explicit instructions or examples for running the Batch Management .NET library on Linux, including any required dependencies or environment setup.
- Include equivalent code samples in other cross-platform languages (e.g., Python, Java) that are commonly used on Linux.
- Mention and demonstrate how to use the .NET CLI and SDK on Linux, including installation and usage steps.
- Clarify that the .NET library and Azure SDKs are cross-platform, and provide troubleshooting tips for Linux users.
- Reference Linux-compatible authentication and credential management workflows, such as using environment variables or managed identities.
- Provide links to Linux-specific documentation or guides for Azure Batch management.
Create Pull Request
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by listing Windows VM sizes and OS families before Linux equivalents, providing detailed information about Windows OS families, and including a dedicated 'windowsConfiguration' section without a corresponding 'linuxConfiguration'. Linux-specific configuration details and examples are missing, and references to Linux are less prominent or absent.
Recommendations
- Add explicit Linux configuration examples, such as a 'linuxConfiguration' section analogous to 'windowsConfiguration', detailing relevant settings (e.g., SSH, update management).
- Present Linux and Windows VM sizes and configuration options in parallel, ensuring equal visibility and detail for both platforms.
- Include Linux OS family/version references and guidance, similar to the Windows OS family table.
- Provide example event bodies and configuration snippets for both Windows and Linux pools.
- Ensure links to Linux documentation are as prominent and detailed as those for Windows.
Batch
Migrate Azure Batch pools to the simplified compute node communication model
...ified-compute-node-communication-model-migration-guide.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates subtle Windows bias by mentioning RDP (a Windows-specific remote access protocol) before SSH (the Linux equivalent) when discussing node connectivity. Additionally, there are no concrete examples or instructions for either platform, but the agent naming example lists the Windows agent ('Microsoft.BatchClusters.Agent.exe') after the generic agent ('Microsoft.BatchClusters.Agent'), which could be interpreted as Windows-centric. There are no explicit PowerShell examples, nor are Windows tools or patterns emphasized, but the lack of Linux-specific examples or instructions contributes to a mild bias.
Recommendations
- Provide explicit examples for both Windows and Linux platforms when discussing connectivity, such as step-by-step instructions for both RDP (Windows) and SSH (Linux).
- When mentioning agents or tools, clarify the usage for both operating systems and avoid listing Windows-specific names first unless alphabetically appropriate.
- Include troubleshooting or migration steps that are specific to Linux environments, such as firewall configuration or package installation.
- Ensure parity in documentation by offering equivalent guidance and examples for Linux users wherever Windows tools or patterns are referenced.
Batch
Migrate low-priority VMs to spot VMs in Batch
...s/batch/low-priority-vms-retirement-migration-guide.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for migrating Batch pools to Spot VMs, but the PowerShell examples are given their own dedicated section ('Option 2'), while Linux-specific shell examples (bash, etc.) are not explicitly mentioned. The CLI examples are cross-platform, but PowerShell (primarily a Windows tool) is highlighted as an alternative automation method, and no Linux-native scripting or tool examples (e.g., bash scripts, cloud-init, etc.) are provided. The documentation refers to PowerShell before mentioning the Azure portal UI, and does not offer parity for Linux users in terms of scripting or troubleshooting examples.
Recommendations
- Add explicit bash shell script examples for common migration and validation tasks, demonstrating usage on Linux and macOS.
- Clarify that Azure CLI commands are cross-platform and provide sample usage in bash/zsh (e.g., with environment variables, piping, jq for JSON parsing).
- Include troubleshooting steps or validation examples using Linux-native tools (e.g., curl for REST API calls, jq for JSON output).
- If PowerShell is mentioned as an automation method, also mention bash scripting or other Linux automation tools for parity.
- Consider reordering sections so that cross-platform or Linux-native methods are presented before or alongside Windows/PowerShell methods.
Batch
Configure node endpoints in Azure Batch pool
...lob/main/articles/batch/pool-endpoint-configuration.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation presents examples for both Windows (RDP) and Linux (SSH) endpoints, but consistently lists Windows/RDP examples before Linux/SSH examples. The introductory text also mentions Windows/RDP before Linux/SSH. There is a slight preference for Windows-first ordering and terminology, but both platforms are covered with equivalent code samples and explanations. No PowerShell-specific examples or exclusive Windows tools are present, but the ordering may subtly reinforce a Windows-centric perspective.
Recommendations
- Alternate the order of examples so that Linux/SSH is sometimes presented before Windows/RDP, or present both together when possible.
- Explicitly state parity between Windows and Linux pools in introductory sections to reinforce equal support.
- Ensure that any referenced tools, commands, or code samples are provided for both platforms where applicable.
- Consider adding a summary table or section that compares configuration steps for both Windows and Linux pools side-by-side.
Batch
Azure Quickstart - Create a Batch account - Bicep file
...re-docs/blob/main/articles/batch/quick-create-bicep.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all deployment, validation, and cleanup steps. However, PowerShell is featured as a first-class option throughout, and its inclusion may indicate a Windows-centric approach, as PowerShell is most commonly used on Windows. There is no explicit mention of Linux-specific tools or shell environments (e.g., Bash), nor are there any Linux-specific notes or examples. The CLI examples are cross-platform, but the documentation does not clarify this or offer guidance for Linux users.
Recommendations
- Add explicit notes clarifying that Azure CLI commands work on Linux, macOS, and Windows.
- Include Bash shell examples or mention that CLI commands can be run in Bash on Linux/macOS.
- Add a section or callout for Linux users, highlighting any differences or prerequisites (e.g., installing Azure CLI on Linux).
- Consider mentioning that PowerShell Core is available cross-platform, but clarify that most Linux users will prefer Bash/CLI.
- Ensure that examples and instructions do not assume a Windows environment by default.
Batch
Create a simplified node communication pool without public IP addresses
...tch/simplified-node-communication-pool-no-public-ip.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation demonstrates mild Windows bias in troubleshooting instructions, where Windows PowerShell commands (Test-NetConnection) are listed first and in more detail, with Linux equivalents (nc) given second. The documentation otherwise maintains good cross-platform parity, mentioning both Azure CLI and PowerShell in prerequisites and providing REST API and ARM template examples that are OS-neutral. No exclusive use of Windows tools or missing Linux examples is present.
Recommendations
- Present troubleshooting commands for Windows and Linux side-by-side, or list Linux first in some cases to balance representation.
- Expand Linux troubleshooting examples with additional context or alternatives (e.g., using curl, telnet, or other common Linux tools).
- Where PowerShell is mentioned, ensure Azure CLI or Bash equivalents are equally detailed and visible.
- Consider including explicit cross-platform notes or sections to reinforce parity and guide users on both Windows and Linux.
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 .NET (C#) code samples and references, which are most commonly used on Windows. There are no examples or guidance for Linux users, such as Bash, CLI, or cross-platform scripting. The documentation does not mention Linux-specific tools or patterns, nor does it provide parity for Linux environments in its examples or workflow descriptions.
Recommendations
- Add equivalent examples using Azure CLI and Bash scripts, which are commonly used on Linux.
- Include notes or sections on how to run .NET code on Linux (e.g., using .NET Core/SDK on Ubuntu).
- Provide guidance or links for Linux users on authentication and environment setup.
- Mention cross-platform compatibility explicitly, and ensure that all steps and code samples are usable on both Windows and Linux.
- Reference Linux tools and patterns (e.g., environment variables, shell scripting) alongside Windows/PowerShell equivalents.
Batch
Migrate low-priority VMs to spot VMs in Batch
...s/batch/low-priority-vms-retirement-migration-guide.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents both Azure CLI and Azure PowerShell examples for migrating Batch pools, but PowerShell (a Windows-centric tool) is given as the only alternative automation method after CLI, with no mention of Bash, Linux shell scripting, or cross-platform SDKs. The PowerShell section is detailed and includes validation steps, while Linux-native automation methods (e.g., Bash scripts, Python SDK) are absent. The ordering places PowerShell before the Azure portal UI method, reinforcing Windows-first patterns.
Recommendations
- Add explicit Bash shell script examples for Azure CLI commands to demonstrate Linux usage (e.g., using environment variables, piping output, jq for JSON parsing).
- Include Python SDK or REST API code snippets for pool migration and validation to provide cross-platform automation alternatives.
- Mention that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows, and provide links to installation guides for non-Windows platforms.
- Reorder automation options so that CLI and Linux-native methods are presented before PowerShell, or group them together as cross-platform solutions.
- Clarify that PowerShell Core is available on Linux/macOS, but provide usage notes or alternatives for users who prefer native Linux tools.
Batch
Move an Azure Batch account to another region
...cs/azure-docs/blob/main/articles/batch/account-move.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively describes moving an Azure Batch account using the Azure portal, with all instructions and screenshots implicitly targeting Windows users. There are no examples or guidance for performing these tasks via CLI tools such as Azure CLI, PowerShell, or Bash, nor are Linux-specific workflows or tools mentioned. The process relies on downloading and unzipping files, which is described in a way that assumes a Windows environment. No parity is provided for Linux users or those preferring command-line automation.
Recommendations
- Add equivalent instructions for exporting and deploying ARM templates using Azure CLI and/or PowerShell, including example commands.
- Include steps for downloading and extracting template files on Linux/macOS, such as using 'curl' or 'wget' and 'unzip'.
- Provide guidance for performing the migration entirely via command line, which is platform-agnostic and beneficial for automation.
- Mention cross-platform tools and workflows explicitly, and avoid assuming use of the Azure portal or Windows file explorer.
- Add notes or links to documentation for Linux/macOS users where workflows differ.
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 generally mentions both Windows and Linux support for the Azure Key Vault VM extension, but Windows is listed first in the FAQ section when linking to platform-specific documentation. There are no concrete code or command examples for either platform, but Linux-specific guidance is less detailed and lacks explicit step-by-step examples, especially for certificate access and installation. The documentation does not provide parity in example depth or order between Windows and Linux.
Recommendations
- Alternate the order of Windows and Linux references to avoid implicit prioritization (e.g., sometimes list Linux first).
- Provide explicit, step-by-step examples for both Windows (PowerShell, CMD) and Linux (Bash, CLI) for common tasks such as installing certificates, accessing certificate stores, and configuring the Key Vault VM extension.
- Include sample scripts or commands for Linux environments, such as how to copy certificates, set file permissions, and access them in Batch tasks.
- Clarify any platform-specific differences in behavior or configuration, and ensure both platforms are equally covered in troubleshooting and FAQs.
- Add links to Linux best practices and troubleshooting guides where appropriate.
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by referencing Windows OS families and configurations first and in detail, while Linux equivalents are only mentioned in passing or as exclusions. There are no explicit Linux configuration examples or details, and the only OS-specific configuration section provided is for Windows ('windowsConfiguration'). The VM size documentation links to both Linux and Windows, but the overall configuration guidance and examples are Windows-centric.
Recommendations
- Add a dedicated section for Linux-specific configuration options, analogous to the 'windowsConfiguration' section.
- Provide example event bodies and configuration snippets for pools using Linux images.
- Include explicit references and links to Linux OS families and versions, similar to the detailed Windows OS family mapping.
- Ensure parity in documentation by describing any Linux-specific behaviors, settings, or caveats for Batch pool creation.
- Where OS-specific configuration is discussed, present Linux and Windows options side-by-side or in parallel sections.
Batch
Migrate Azure Batch pools to the simplified compute node communication model
...ified-compute-node-communication-model-migration-guide.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page references Windows-specific tools and patterns before their Linux equivalents, such as mentioning RDP before SSH in the diagnostics FAQ, and refers to agent binaries with Windows-style naming (.exe) before Linux equivalents. There are no explicit Linux command-line or configuration examples, and no Linux-specific troubleshooting or migration steps are provided.
Recommendations
- Present SSH connectivity before or alongside RDP when discussing node diagnostics to reflect Linux parity.
- Include explicit Linux examples or references in migration steps, such as shell commands or configuration file changes.
- Clarify agent naming for both platforms equally, e.g., 'Microsoft.BatchClusters.Agent (Linux) and Microsoft.BatchClusters.Agent.exe (Windows)'.
- Add troubleshooting or operational notes relevant to Linux environments, such as SELinux, firewall, or package management considerations.
- Ensure that any referenced guides or linked documentation also provide Linux-specific instructions and examples.
Batch
Manage private endpoint connections with Azure Batch accounts
.../articles/batch/manage-private-endpoint-connections.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page presents both Az PowerShell and Azure CLI examples for managing private endpoint connections in Azure Batch accounts. However, the PowerShell examples are listed before the CLI examples, and the PowerShell module is highlighted with a direct link, suggesting a Windows-first approach. There is a slight bias toward Windows users due to the ordering and emphasis on PowerShell, which is predominantly used on Windows systems.
Recommendations
- Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and widely used on Linux and macOS.
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows to encourage non-Windows users.
- Add a note or section highlighting Linux/macOS compatibility and usage patterns.
- Ensure that links and references to tools are balanced between Windows and Linux environments.
Batch
Configure managed identities in Batch pools
...ocs/blob/main/articles/batch/managed-identity-pools.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias, most notably in the section on obtaining managed identity tokens within Batch nodes. The Windows/PowerShell example is presented first, followed by the Linux/Bash example. Additionally, PowerShell is mentioned as a tool for creating managed identities before Linux alternatives (Azure CLI), and the Instance Metadata Service reference links to the Windows VM documentation. However, the page does provide Linux examples and mentions the Azure CLI, so the bias is not exclusive.
Recommendations
- Present Linux/Bash examples before or alongside Windows/PowerShell examples to avoid implicit prioritization.
- Reference both Windows and Linux documentation for the Instance Metadata Service, or use a neutral link.
- Explicitly mention Azure CLI as the primary cross-platform tool for creating managed identities, and provide example commands.
- Ensure parity in all code samples and instructions, offering both Windows and Linux alternatives where applicable.
- Consider adding a table or section comparing steps/tools for both platforms to reinforce cross-platform support.
Batch
Associate Azure Batch accounts with network security perimeter
...blob/main/articles/batch/network-security-perimeter.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides step-by-step instructions for associating Azure Batch accounts with a network security perimeter using the Azure portal, PowerShell, and Azure CLI. PowerShell examples are given in detail and are presented before Azure CLI examples, which may indicate a Windows-first and PowerShell-heavy bias. There are no explicit Linux shell (bash) or cross-platform scripting examples, nor is there mention of Linux-specific tools or patterns. The CLI examples are generic and cross-platform, but PowerShell is highlighted as a primary automation method, which may disadvantage Linux users.
Recommendations
- Add bash shell scripting examples alongside PowerShell for each automation step.
- Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and provide any OS-specific notes if needed.
- Consider presenting Azure CLI examples before PowerShell to emphasize cross-platform parity.
- Mention Linux-native automation options (e.g., bash, scripting with SDKs in Python) where appropriate.
- Clarify that PowerShell examples are for Windows and PowerShell Core users, and provide equivalent bash or shell commands for Linux users.
Batch
Azure Quickstart - Create a Batch account - Bicep file
...re-docs/blob/main/articles/batch/quick-create-bicep.md
Medium 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 steps. However, Azure PowerShell is featured equally alongside Azure CLI, which may introduce a subtle Windows bias since PowerShell is primarily associated with Windows environments. No Linux-specific tools or shell examples (such as Bash scripts) are provided, and PowerShell is presented as a first-class option, potentially prioritizing Windows users. There are no explicit Linux-only examples or mentions of Linux-specific patterns.
Recommendations
- Clarify that Azure CLI commands work natively on Linux, macOS, and Windows, while PowerShell is most common on Windows.
- Add explicit Bash shell examples for Linux users, especially for scripting deployments.
- Include a note or section about using Azure CLI in Bash or zsh environments, with sample commands.
- Consider mentioning cross-platform compatibility for each tool, helping users choose the best option for their OS.
- If PowerShell is shown, clarify how to use PowerShell Core on Linux/macOS, or provide links to installation instructions.
Batch
Azure Quickstart - Create a Batch account - Azure Resource Manager template
...docs/blob/main/articles/batch/quick-create-template.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively describing deployment via the Azure portal and referencing Azure PowerShell as an alternative before mentioning Azure CLI or REST API. No explicit Linux or cross-platform command-line examples are provided, and the deployment instructions focus on GUI-based workflows typical of Windows environments.
Recommendations
- Add explicit Azure CLI examples for template deployment, as CLI is cross-platform and widely used on Linux.
- Include Linux-specific instructions or screenshots where relevant, such as terminal commands for resource validation and cleanup.
- Present deployment alternatives in a neutral order (e.g., 'Azure CLI, PowerShell, REST API, and Portal') rather than listing Windows-centric tools first.
- Provide links to both PowerShell and CLI documentation when referencing alternative deployment methods.
- Clarify that all deployment methods are available on both Windows and Linux, and highlight any platform-specific considerations.
Batch
Configure node endpoints in Azure Batch pool
...lob/main/articles/batch/pool-endpoint-configuration.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation alternates between Windows (RDP) and Linux (SSH) examples, but consistently presents Windows/RDP examples first in each section. Windows terminology (RDP, port 3389, C# code) is introduced before Linux equivalents (SSH, port 22, Python code). There is a slight preference for Windows tools and patterns, as seen in the ordering and language. However, both platforms are covered with equivalent examples and explanations.
Recommendations
- Alternate the order of Windows and Linux examples, or present them side-by-side to avoid implicit prioritization.
- Explicitly mention Linux pools and SSH access first in some sections to balance the narrative.
- Provide parity in code samples (e.g., offer both C# and Python for each scenario, or use a neutral language like REST API or CLI where possible).
- Ensure introductory text does not default to Windows terminology before Linux equivalents.
- Add a table summarizing endpoint configuration for both Windows and Linux pools for quick reference.
Batch
Configure public network access with Azure Batch accounts
...docs/blob/main/articles/batch/public-network-access.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page focuses exclusively on configuring Azure Batch account network access via the Azure Portal UI, without providing any command-line examples. There is no mention of platform-specific tools or scripts (such as PowerShell, Azure CLI, or Bash), but the lack of CLI examples means Linux users are not given parity with Windows users who may be more accustomed to GUI workflows. The absence of Azure CLI or Bash examples constitutes a subtle bias, as Linux administrators often prefer or require command-line instructions.
Recommendations
- Add Azure CLI examples for configuring public network access, including enabling, disabling, and managing IP network rules.
- Include Bash script snippets for automating Batch account network configuration.
- Explicitly mention that all operations can be performed via Azure CLI or REST API, and provide links to relevant documentation.
- Ensure that any future updates include both portal and CLI instructions, presented in parallel.
Batch
Create a simplified node communication pool without public IP addresses
...tch/simplified-node-communication-pool-no-public-ip.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias in troubleshooting examples, specifically in the section for verifying TCP connectivity to the Batch node management endpoint. The Windows PowerShell command (Test-NetConnection) is listed first, followed by the Linux equivalent (nc). Elsewhere, examples and instructions are generally platform-neutral, focusing on REST API, ARM templates, and Azure portal usage, with no exclusive use of Windows tools or omission of Linux equivalents.
Recommendations
- Present Linux and Windows troubleshooting commands side-by-side or alternate which is listed first to avoid implicit prioritization.
- Where possible, provide additional context or examples for Linux users, such as using Bash scripts or other common Linux tools.
- Explicitly state that both Windows and Linux are supported throughout, and link to platform-specific guides for common tasks (e.g., remote connection, DNS troubleshooting).
- Review other sections for subtle platform-specific language or assumptions, and ensure parity in instructions and screenshots.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/quick-create-bicep.md
...re-docs/blob/main/articles/batch/quick-create-bicep.md
Medium 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 is featured equally alongside CLI, and there is no mention of Linux-specific shell environments (e.g., Bash) or guidance for Linux users. The use of PowerShell may implicitly favor Windows users, and the absence of explicit Linux/Bash examples or notes about cross-platform usage suggests a subtle Windows bias.
Recommendations
- Add explicit Bash examples or clarify that Azure CLI commands work in Bash on Linux/macOS.
- Include notes or sections addressing Linux/macOS users, such as installation and usage of Azure CLI in those environments.
- Clarify that PowerShell Core is cross-platform, or provide guidance for using PowerShell on Linux/macOS if PowerShell examples are retained.
- Consider listing Azure CLI (which is cross-platform) before PowerShell in examples to avoid implicit Windows-first ordering.
- Add troubleshooting tips or links for common Linux/macOS issues when using Azure CLI or PowerShell.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/account-move.md
...cs/azure-docs/blob/main/articles/batch/account-move.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation exclusively describes using the Azure portal (a web interface) for exporting and deploying ARM templates, without mentioning command-line alternatives. It references downloading and unzipping files, but does not provide any examples using Azure CLI, PowerShell, or scripting tools. There is no mention of Linux-specific workflows or tools, nor are cross-platform command-line instructions provided. The steps and examples assume a GUI workflow, which is more common on Windows, and do not address Linux users who may prefer CLI or automation.
Recommendations
- Add Azure CLI examples for exporting, modifying, and deploying ARM templates, as Azure CLI is cross-platform and widely used on Linux.
- Include PowerShell examples only alongside Azure CLI, not exclusively or first.
- Provide guidance for performing template modifications and deployments using command-line tools (e.g., jq, sed, az commands) suitable for Linux environments.
- Explicitly mention that all steps can be performed on Linux, macOS, or Windows, and link to platform-specific instructions where relevant.
- Add notes or sections for automating the process via scripts, which is common in Linux-based workflows.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-certificate-migration-guide.md
...in/articles/batch/batch-certificate-migration-guide.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page generally covers both Windows and Linux scenarios, but there is a subtle Windows bias. In the FAQ section, links to Windows documentation are listed before Linux equivalents, and there are no explicit code or command examples for either platform. Linux-specific migration steps (such as handling the removal of $AZ_BATCH_CERTIFICATES_DIR) are mentioned, but practical examples or scripts for Linux users are missing. Windows is referenced first in cross-platform documentation links, and Linux guidance is less detailed.
Recommendations
- Provide explicit, step-by-step examples for both Windows (e.g., PowerShell) and Linux (e.g., Bash) for certificate migration and usage.
- When referencing documentation for both platforms, alternate the order or list Linux first in some cases to balance visibility.
- Include sample scripts or commands for common Linux tasks, such as copying certificates, setting permissions, and accessing Key Vault from Linux pools.
- Clarify any platform-specific differences in the migration process, and ensure Linux users have parity in troubleshooting and best practices guidance.
Batch
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/batch/batch-management-dotnet.md
...cs/blob/main/articles/batch/batch-management-dotnet.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exclusively provides .NET (C#) code samples and references, which are most commonly used in Windows environments. There is no mention of Linux-specific tools, patterns, or equivalent code samples for Linux platforms (e.g., Bash, CLI, Python). The documentation assumes a Windows-centric development workflow, with no guidance for Linux users or cross-platform scenarios.
Recommendations
- Add equivalent code samples using Azure CLI and Bash scripts to demonstrate how to manage Batch accounts and quotas from Linux environments.
- Include Python examples, as Python is widely used cross-platform and is referenced in the 'Next steps' section.
- Explicitly mention that the .NET library can be used on Linux and macOS via .NET Core/6+, and provide setup instructions for those platforms.
- Reference Linux-friendly authentication workflows (e.g., using environment variables for credentials, using az login from CLI).
- Balance the documentation by presenting both Windows and Linux approaches side-by-side, or clearly indicate platform-agnostic steps.