Container Instances

178
Total Pages
155
Linux-Friendly Pages
23
Pages with Bias
12.9%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

97 issues found
Showing 76-97 of 97 flagged pages
Container Instances Get prediction results for standby pools for Azure Container Instances (Preview) ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/container-instances/container-instances-standby-pool-prediction-results.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for retrieving prediction results, but PowerShell is featured as a primary method alongside CLI and REST. PowerShell is a Windows-centric tool, and its inclusion as a top-level example (with a dedicated tab) reflects a Windows bias. There are no Linux/macOS-specific shell examples (e.g., Bash scripts, curl commands), and PowerShell is listed before REST, which is platform-neutral. However, the Azure CLI example is cross-platform, mitigating the bias somewhat.
Recommendations
  • Add explicit Bash/curl examples for Linux/macOS users under a separate tab or within the REST section.
  • Clarify that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
  • Consider listing CLI and REST examples before PowerShell, or at least clarify PowerShell's platform limitations.
  • If PowerShell is mentioned, note that PowerShell Core is available on Linux/macOS, but provide native shell examples for those platforms.
GitHub Create Pull Request
Container Instances Troubleshoot common issues ...ainer-instances/container-instances-troubleshooting.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation provides both Linux and Windows examples for container deployment and troubleshooting, but Windows-specific considerations (such as image support, networking delays, and cached images) are often mentioned before or in more detail than Linux equivalents. Windows-specific tools and patterns (e.g., PowerShell, Windows image tags, Windows networking delays) are described, while Linux details are sometimes less emphasized. In some cases, instructions for shell commands note Bash as the default, but only briefly mention the need to adjust for PowerShell/Command Prompt, without providing explicit Linux/macOS alternatives.
Recommendations
  • Ensure Linux/macOS examples are presented with equal detail and prominence as Windows examples.
  • When mentioning shell commands, provide explicit Bash and PowerShell/Command Prompt syntax side-by-side.
  • Expand troubleshooting sections to cover Linux/macOS-specific issues (e.g., SELinux/AppArmor, common Linux container errors).
  • Balance the order of presentation so that Linux and Windows considerations are alternated or grouped, rather than Windows-first.
  • Provide links to Linux/macOS documentation and tools where relevant.
GitHub Create Pull Request
Container Instances Understand the health state of your standby pool for Azure Container Instances ...ances/container-instances-standby-pool-health-state.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides command-line examples for Azure CLI, PowerShell, and REST API. The PowerShell example is given equal prominence to the CLI, and there is no mention of Linux/macOS-specific tools or shell environments (e.g., Bash). The CLI example is cross-platform, but PowerShell is a Windows-centric tool, and its inclusion without a Bash or shell script example suggests a mild Windows bias. The ordering of examples (CLI first, then PowerShell) is neutral, but the lack of explicit Linux/macOS shell examples or notes about cross-platform usage is a subtle bias.
Recommendations
  • Add explicit Bash or shell script examples for Linux/macOS users, especially for REST API calls (e.g., using curl).
  • Clarify that Azure CLI is cross-platform and can be used on Linux/macOS.
  • Note that PowerShell Core is available on Linux/macOS, or provide guidance for those platforms.
  • Include troubleshooting or environment setup notes for Linux/macOS users if any differences exist.
GitHub Create Pull Request
Container Instances Override entrypoint in container instance ...ntainer-instances/container-instances-start-command.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides both Linux and Windows shell examples in the shell table, but there is a notable emphasis on Azure PowerShell (Windows-centric) as a primary tool alongside Azure CLI. Windows tools and conventions (cmd, PowerShell) are mentioned explicitly and sometimes before Linux equivalents. However, Linux shell usage is demonstrated in examples, and the Azure CLI (cross-platform) is used for all step-by-step instructions. There are no exclusive Windows-only instructions, but the presence of PowerShell and Windows shell references may create mild friction for Linux/macOS users.
Recommendations
  • Add explicit Linux/macOS PowerShell alternatives or clarify that Azure CLI is cross-platform and preferred for non-Windows users.
  • Reorder shell table to list Linux shells first (e.g., Ubuntu, Alpine) before Windows (cmd) to reduce Windows-first perception.
  • Provide a Linux/macOS-specific example for Resource Manager templates or YAML files, showing command-line overrides in a native editor or workflow.
  • Clarify that PowerShell is optional and not required for Linux/macOS users.
  • Add a note that Azure CLI commands work identically on Linux, macOS, and Windows.
GitHub Create Pull Request
Container Instances Update or delete a standby pool for Azure Container Instances ...nces/container-instances-standby-pool-update-delete.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides both Azure CLI and PowerShell examples for updating and deleting standby pools, but PowerShell (a Windows-centric tool) is given equal prominence and detailed usage. The ARM template section mentions deployment via both az CLI and New-AzResourceGroupDeployment (PowerShell), but does not clarify Linux/macOS deployment patterns. There is no explicit Linux/macOS bias, but the presence and parity of PowerShell examples, and references to Windows tools, may create friction for non-Windows users.
Recommendations
  • Clarify that Azure CLI commands work cross-platform (Windows, Linux, macOS) and recommend CLI for Linux/macOS users.
  • Add explicit notes or examples for Linux/macOS users, such as shell syntax (bash/zsh) for CLI commands.
  • Deprioritize PowerShell examples or move them after CLI examples, as CLI is more universal.
  • For ARM template deployment, provide Linux/macOS deployment commands (e.g., az deployment group create) before PowerShell equivalents.
  • Consider adding a section on platform compatibility for each tool.
GitHub Create Pull Request
Container Instances Configure custom DNS settings for container group in Azure Container Instances .../container-instances/container-instances-custom-dns.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy
Summary
The documentation page is generally Linux/Bash-centric, with all CLI examples formatted for Bash and explicit notes about Linux container support. However, there is a notable Windows bias in the choice of container image: the YAML example uses the 'mcr.microsoft.com/powershell:latest' image, which is a Microsoft-maintained PowerShell image. This may suggest a Windows-centric workflow, even though the container is deployed with 'osType: Linux'. There are no PowerShell or Windows command prompt examples, but the use of PowerShell as the container workload could be confusing or less relevant for Linux-focused users.
Recommendations
  • Provide alternative YAML examples using more common Linux images (e.g., Ubuntu, Alpine, nginx) to demonstrate DNS configuration in a typical Linux container.
  • Clarify that the PowerShell image is cross-platform and runs on Linux, or explicitly mention its suitability for Linux containers.
  • Add a note or example for users who may want to use a native Linux shell (e.g., bash, sh) as the container entrypoint.
  • Ensure that the documentation does not imply that PowerShell is required for Linux container scenarios.
GitHub Create Pull Request
Container Instances Encrypt deployment data ...ontainer-instances/container-instances-encrypt-data.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias. While most command-line examples use Azure CLI (which is cross-platform), instructions for creating and managing Azure Key Vault resources explicitly mention Azure PowerShell and Azure Portal before Azure CLI, and some critical configuration steps (like enabling Soft Delete and Do Not Purge) are described as being performed via PowerShell or CLI, with PowerShell mentioned first. There are no Linux-specific examples, nor is Bash scripting shown, and screenshots and UI instructions are based on the Azure Portal, which is platform-agnostic but often associated with Windows workflows. No steps are strictly Windows-only, but the ordering and tool references may subtly favor Windows users.
Recommendations
  • List Azure CLI before Azure PowerShell when describing resource creation and configuration steps, as CLI is more universally available across platforms.
  • Provide explicit Bash/Linux shell examples for variable assignment and scripting, especially where CLI commands are shown.
  • Clarify that all CLI and PowerShell commands work on Linux, macOS, and Windows, and link to platform-specific setup guides.
  • Add notes or examples for Linux/macOS users where file upload or editing is mentioned (e.g., using SCP, SFTP, or VS Code Remote for Cloud Shell).
  • Avoid mentioning PowerShell first unless there is a technical reason; strive for parity in tool recommendations.
GitHub Create Pull Request
Container Instances Execute commands in running container instance ...ticles/container-instances/container-instances-exec.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation provides both Linux (Bash) and Windows (Command Prompt) examples for executing commands in running Azure container instances. However, the Windows example is given equal prominence and detail, including a full output listing, and Windows-specific terminology (cmd.exe, Command Prompt) is used. There is no mention of PowerShell, but the documentation does reference Windows tools and patterns. The examples are balanced, but Windows terminology and examples are presented with similar emphasis as Linux, rather than Linux-first, which is more typical for container documentation.
Recommendations
  • Present Linux examples first, as containers are most commonly Linux-based.
  • Add explicit macOS notes if there are platform-specific behaviors.
  • Clarify that az container exec works identically across platforms, and highlight any differences.
  • Provide more Linux troubleshooting examples or shell usage tips.
  • Reduce Windows-specific terminology unless necessary for the task.
GitHub Create Pull Request
Container Instances Set environment variables in container instance ...instances/container-instances-environment-variables.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for setting environment variables in Azure Container Instances, but it demonstrates a mild Windows bias. PowerShell (a Windows-centric tool) is given a dedicated section, and the CLI examples include explicit instructions for Windows Command Prompt users before Linux/Bash users. There is no explicit Linux shell example for PowerShell, nor are macOS-specific considerations mentioned. The YAML section does use Linux containers and Bash, but overall, Windows tools and patterns are presented first or exclusively in some cases.
Recommendations
  • Provide Linux/macOS-specific instructions and examples where relevant, especially for shell quoting and environment variable syntax.
  • Reorder examples so that cross-platform tools (Azure CLI, YAML) are presented before Windows-specific tools (PowerShell).
  • Add explicit notes or examples for macOS users, especially regarding shell differences.
  • Clarify that PowerShell Core is available on Linux/macOS, and provide corresponding examples if relevant.
  • Ensure that all instructions referencing shell syntax (quotes, environment variable expansion) include both Windows and Linux/macOS variants.
GitHub Create Pull Request
Container Instances Azure Resource Manager template samples .../container-instances/container-instances-samples-rm.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page displays minor Windows bias. In the sample templates table, the only application-specific Windows container example (MS NAV with SQL Server and IIS) is highlighted, while Linux examples are mostly generic. In the deployment section, Azure PowerShell is listed as a primary deployment option alongside Azure CLI, but no explicit Linux/macOS-specific tools or instructions are provided. Windows tools (PowerShell, IIS, SQL Server) are mentioned, but Linux equivalents are not. However, Linux container samples are present and Azure CLI is cross-platform.
Recommendations
  • Add Linux/macOS-specific deployment instructions or examples, such as Bash scripts or references to Linux-native tools.
  • Balance application samples by including a Linux-specific application example (e.g., LAMP stack) to match the Windows MS NAV sample.
  • Clarify that Azure CLI is cross-platform and highlight its use for Linux/macOS users.
  • List deployment options in a neutral order (e.g., CLI first, then PowerShell) or group by platform.
GitHub Create Pull Request
Container Instances Get standby pool for Azure Container Instances details ...tances/container-instances-standby-pool-get-details.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides examples for Azure CLI, PowerShell, and REST API. However, PowerShell is highlighted as a primary method alongside CLI, which can be seen as Windows-centric since PowerShell is most commonly used on Windows. There is no mention of Linux/macOS shell alternatives (e.g., Bash scripts), and PowerShell is presented before REST, reinforcing a Windows-first approach. All examples are generic, but the inclusion and emphasis on PowerShell may create friction for Linux/macOS users who do not use PowerShell.
Recommendations
  • Add Bash shell examples for Linux/macOS users, especially for common tasks shown in PowerShell.
  • Clarify that Azure CLI works cross-platform and is recommended for Linux/macOS.
  • Consider reordering tabs to show CLI first, then Bash, then PowerShell, then REST.
  • Explicitly mention platform compatibility for each example.
GitHub Create Pull Request
Container Instances Understand the health state of your standby pool for Azure Container Instances ...ances/container-instances-standby-pool-health-state.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for retrieving the health state of a standby pool, but the PowerShell example is given equal prominence to the CLI example, despite PowerShell being primarily a Windows tool. There is no mention of Linux/macOS-specific shell usage (e.g., Bash), nor are there any Linux/macOS-specific troubleshooting or usage notes. The CLI example is cross-platform, but the documentation does not clarify this, and the PowerShell example may suggest a Windows-centric workflow.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux/macOS as well as Windows.
  • Add Bash or shell script examples for Linux/macOS users, especially for parsing or processing output.
  • Clarify that PowerShell is available cross-platform, but note its prevalence on Windows.
  • Include troubleshooting or usage notes relevant to Linux/macOS environments (e.g., authentication, environment setup).
  • Consider listing CLI examples first, as they are more universally applicable.
GitHub Create Pull Request
Container Instances Get prediction results for standby pools for Azure Container Instances (Preview) ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/container-instances/container-instances-standby-pool-prediction-results.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for retrieving prediction results, but PowerShell (a Windows-centric tool) is given its own dedicated example section, and is listed immediately after CLI. There are no Linux/macOS-specific shell examples (e.g., Bash, curl), nor are there explicit instructions for Linux users. The CLI example is cross-platform, but PowerShell's prominence and lack of Linux-specific guidance indicate a mild Windows bias.
Recommendations
  • Add explicit Bash/curl examples for REST API calls to demonstrate Linux/macOS usage.
  • Clarify that Azure CLI works on Linux/macOS and provide installation/use links for those platforms.
  • Consider listing CLI examples before PowerShell, or grouping them together as 'cross-platform' and 'Windows-specific' sections.
  • Mention that PowerShell Core is available on Linux/macOS if relevant, or clarify platform support.
GitHub Create Pull Request
Container Instances Request a container from a Standby pool for Azure Container Instances ...https://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/container-instances/container-instances-standby-pool-request-container.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for requesting a container from a standby pool, but PowerShell (a Windows-centric tool) is given equal prominence as CLI, and is presented before ARM template and REST examples. There are no Linux-specific shell examples (e.g., Bash), nor is there mention of Linux/macOS tooling or usage patterns. The CLI example is cross-platform, but the presence and prominence of PowerShell may create friction for Linux/macOS users.
Recommendations
  • Clarify that Azure CLI commands work on Linux/macOS and Windows, and consider providing explicit Bash examples or notes for Linux/macOS users.
  • De-emphasize PowerShell as a primary method, or move it after CLI and ARM/REST examples.
  • Add a note that PowerShell is primarily for Windows, and suggest alternatives for Linux/macOS users.
  • Where possible, provide Linux/macOS shell usage patterns (e.g., Bash scripts) alongside PowerShell.
GitHub Create Pull Request
Container Instances Override entrypoint in container instance ...ntainer-instances/container-instances-start-command.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides both Linux and Windows shell examples, but Windows-specific tools (PowerShell cmdlet) are mentioned explicitly and given equal prominence to cross-platform tools (Azure CLI). The PowerShell example is listed before the Azure portal and template methods, and the documentation references Windows shell ('cmd') alongside Linux shells. However, the main worked example uses Azure CLI, which is cross-platform, and all command-line examples use Linux syntax. There is no critical omission of Linux/macOS instructions, but Windows tools are given notable visibility.
Recommendations
  • Add explicit Linux/macOS command-line examples where PowerShell is mentioned, such as Bash scripts or shell commands.
  • Reorder examples to show cross-platform (CLI, portal, template) methods before Windows-specific tools.
  • Clarify that Azure CLI is available on Windows, Linux, and macOS.
  • Where PowerShell is referenced, add a note or link to equivalent Bash usage for Linux/macOS users.
  • Consider adding a section on using Bash or other Linux-native scripting for container management.
GitHub Create Pull Request
Container Instances Troubleshoot common issues ...ainer-instances/container-instances-troubleshooting.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation provides both Linux and Windows examples for container deployment and troubleshooting, but Windows-specific considerations and tools (such as PowerShell, Windows image support, and Windows networking delays) are often mentioned before or in greater detail than their Linux equivalents. Some instructions explicitly mention Bash as the default shell, with only a brief note that PowerShell/Command Prompt require adjustment, but do not provide direct Linux/macOS alternatives for all steps. Windows-specific troubleshooting (e.g., network readiness delays, image support) is given dedicated sections, while Linux issues are covered more generally.
Recommendations
  • Ensure Linux/macOS examples are presented with equal prominence and detail as Windows examples.
  • Provide explicit command-line examples for both Bash (Linux/macOS) and PowerShell/Command Prompt (Windows) where variable assignment or shell-specific syntax is required.
  • Balance troubleshooting sections so that Linux-specific issues (such as common exit codes, networking quirks, or image compatibility) are covered with similar depth as Windows sections.
  • Where Windows tools or patterns are mentioned (e.g., ping -t for keeping containers alive), offer direct Linux equivalents (e.g., tail -f /dev/null) and explain their usage.
  • Add a summary table or section that clearly distinguishes platform-specific behaviors and recommendations.
GitHub Create Pull Request
Container Instances Big containers on Azure container instances ...ob/main/articles/container-instances/big-containers.md
Low Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation lists PowerShell as a deployment option before Linux-friendly tools (Azure CLI), and does not provide any concrete examples or command snippets for either platform. The mention of PowerShell without equivalent emphasis on Bash or Linux shell usage suggests a subtle Windows-first bias. There are no explicit Linux/macOS examples, nor any mention of platform-specific considerations for deploying Big Containers.
Recommendations
  • Provide explicit deployment examples using both Azure CLI (Bash) and PowerShell, with equal prominence.
  • List Azure CLI (cross-platform) before PowerShell when enumerating deployment options.
  • Add a section on platform-specific prerequisites or tips for Linux/macOS users.
  • Ensure that all instructions and tooling references are cross-platform, or provide alternatives where necessary.
GitHub Create Pull Request
Container Instances Config Maps for Azure Container Instances .../container-instances/container-instances-config-map.md
Low Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for all major workflows, but PowerShell (a Windows-centric tool) is given equal prominence as CLI, and some ARM template and REST examples reference PowerShell deployment commands. The section on accessing config maps in containers gives a Linux example (mount path) and a Windows example (PowerShell command), but the Windows method is less clear and relies on Windows tooling. There is no explicit Linux shell example for accessing config map values inside the container, and PowerShell is mentioned before Linux shell alternatives in several places.
Recommendations
  • Add explicit Linux shell examples for accessing config map values inside containers (e.g., using 'cat' or 'ls' on the mount path).
  • Clarify the Windows container config map access method, and provide a more concrete example (e.g., using 'type' or other Windows shell commands, not just PowerShell).
  • Consider listing CLI (cross-platform) examples before PowerShell in each tab group to reduce Windows-first perception.
  • Where ARM template and REST examples mention deployment tools, highlight cross-platform options (e.g., Azure CLI, Bicep) before PowerShell.
  • Add notes about which commands are cross-platform and which are Windows-only, especially for PowerShell scripts.
GitHub Create Pull Request
Container Instances Create a standby pool for Azure Container Instances ...r-instances/container-instances-standby-pool-create.md
Low Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for all major steps, but PowerShell is given equal prominence as CLI, and is referenced throughout. PowerShell is a Windows-centric tool, and its inclusion as a primary method (alongside CLI) can indicate a Windows bias, especially since PowerShell is still more commonly used on Windows. Additionally, deployment instructions for ARM templates mention PowerShell (New-AzResourceGroupDeployment) before CLI in some places, and PowerShell modules are referenced directly. There are no explicit Linux/macOS-only examples or notes, and no mention of Bash scripting or Linux-native tools. However, the Azure CLI examples are cross-platform and shown first in each tab set, which helps mitigate bias.
Recommendations
  • Clarify that Azure CLI is fully cross-platform and recommend it as the default for Linux/macOS users.
  • Add explicit notes or callouts for Linux/macOS users, such as installation instructions for Azure CLI on those platforms.
  • Include Bash script examples or usage patterns where appropriate.
  • De-emphasize PowerShell as a primary method, or clarify its cross-platform availability (PowerShell Core), but note that CLI is more common on Linux/macOS.
  • Ensure that all deployment instructions (e.g., for ARM templates) show CLI commands before PowerShell, or provide parity in ordering.
GitHub Create Pull Request
Container Instances Understand the health state of your standby pool for Azure Container Instances ...ances/container-instances-standby-pool-health-state.md
Low Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for retrieving the health state of the standby pool, but the PowerShell example is given equal prominence to the CLI example. PowerShell is a Windows-centric tool, and there is no mention of Linux/macOS-specific shell usage (e.g., Bash) or guidance for non-Windows environments. The CLI example is cross-platform, but the documentation does not clarify this or encourage its use for Linux/macOS users. No Linux-specific tools or patterns are mentioned.
Recommendations
  • Explicitly state that Azure CLI is cross-platform and recommended for Linux/macOS users.
  • Add Bash shell usage examples for Linux/macOS users, if applicable.
  • Clarify that PowerShell is primarily for Windows users, or mention PowerShell Core compatibility with Linux/macOS if relevant.
  • Consider listing CLI examples before PowerShell to reduce perceived Windows-first bias.
  • Add a note or section on using these commands in Linux/macOS environments.
GitHub Create Pull Request
Container Instances Get prediction results for standby pools for Azure Container Instances (Preview) ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/container-instances/container-instances-standby-pool-prediction-results.md
Low Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Azure CLI and PowerShell examples for retrieving prediction results, but PowerShell is given a dedicated tab and example, which is a Windows-centric tool. The CLI example is cross-platform, but PowerShell is presented before REST and with equal prominence, suggesting a Windows-first approach. There are no Linux/macOS-specific instructions or examples, and no mention of Bash scripting or native Linux tools.
Recommendations
  • Add explicit Bash or shell script examples for Linux/macOS users, especially for parsing or processing results.
  • Clarify that Azure CLI works on Windows, Linux, and macOS, and consider showing Bash usage (e.g., with jq for JSON parsing).
  • If PowerShell is included, also mention PowerShell Core compatibility on Linux/macOS, or provide equivalent Linux-native instructions.
  • Consider listing CLI examples before PowerShell, as CLI is cross-platform.
GitHub Create Pull Request
Container Instances Override entrypoint in container instance ...ntainer-instances/container-instances-start-command.md
Low Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides both Linux and Windows shell examples in the shell table, but in the command line syntax section, Azure PowerShell is mentioned as a primary method alongside Azure CLI, and the PowerShell cmdlet is given a dedicated example before the portal and template methods. There is a slight emphasis on Windows tools (PowerShell, 'cmd') and the PowerShell cmdlet is referenced directly, while Linux-specific tools (e.g., bash scripting, shell utilities) are not highlighted as much. However, the main CLI examples use bash syntax and Linux-style commands, and there are no critical omissions for Linux/macOS users.
Recommendations
  • Add explicit Linux/macOS shell examples alongside PowerShell, such as using bash/zsh in terminal.
  • Mention Linux-native tools or scripting patterns where relevant, such as using shell scripts for entrypoint overrides.
  • Ensure that PowerShell and Windows-specific instructions are not presented before Linux equivalents, or present them in parallel.
  • Clarify that Azure CLI works cross-platform and provide example commands for both Windows (cmd/PowerShell) and Linux/macOS (bash/zsh) environments.
GitHub Create Pull Request
← Previous Page 4 of 4 Next →