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 1-25 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
High Priority View Details →
Scanned: 2026-01-09 19:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides command-line examples for Azure CLI, PowerShell, and REST. However, the PowerShell example is given its own dedicated section, and there is no explicit mention or example of using Bash or Linux shell environments. The CLI example is generic but does not clarify Linux compatibility or provide Bash-specific context. There is a clear PowerShell focus, and the documentation does not address Linux users directly or provide parity in example commands or environment notes.
Recommendations
  • Add explicit Bash/Linux shell examples alongside the Azure CLI example, clarifying that the CLI commands work cross-platform.
  • Include a note that PowerShell examples are primarily for Windows users, and provide equivalent Bash/Linux commands where appropriate.
  • Reorder the examples to present the Azure CLI (cross-platform) first, followed by Bash/Linux, then PowerShell, to avoid implicit Windows-first bias.
  • Mention any OS-specific requirements or differences, if applicable, to help Linux users understand how to adapt the instructions.
  • Consider adding a 'Bash' or 'Linux' tab in the example sections to ensure Linux users see themselves represented.
GitHub Create Pull Request
Container Instances Override entrypoint in container instance ...ntainer-instances/container-instances-start-command.md
High Priority View Details →
Scanned: 2026-01-09 19:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates some Windows bias by referencing Windows tools (PowerShell) and cmd.exe, mentioning PowerShell before Linux equivalents, and providing explicit PowerShell examples while not providing equivalent Bash or Linux shell examples. The 'Default shell' table lists Windows/cmd after Linux shells, but the only non-CLI tool-specific example is for PowerShell. There are no explicit Bash or Linux shell command-line examples for resource creation (e.g., using Bash scripts or Linux-native tools).
Recommendations
  • Add explicit Bash or Linux shell examples for creating container instances, especially for scripting scenarios.
  • Provide Linux-native equivalents for PowerShell examples, such as using Bash with Azure CLI.
  • Where PowerShell cmdlets are mentioned, also mention Bash scripting or Linux automation options.
  • Ensure that Linux tools and patterns are presented with parity to Windows/PowerShell, both in order and in detail.
  • Consider adding a section or table that summarizes both Windows and Linux approaches side by side for common tasks.
GitHub Create Pull Request
Container Instances Set environment variables in container instance ...instances/container-instances-environment-variables.md
High Priority View Details →
Scanned: 2026-01-09 19:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. The Azure PowerShell example is given equal prominence to the Azure CLI, and PowerShell-specific patterns (such as array construction and command syntax) are detailed extensively. Windows Command Prompt quoting is mentioned before Linux/Bash conventions in the CLI section. There is no explicit Linux shell or scripting example (e.g., Bash script), nor are Linux-native tools (like curl, grep, or shell environment variable patterns) referenced. The YAML section does specify osType: Linux, but the main procedural examples focus on Windows-centric tools and patterns.
Recommendations
  • Add explicit Bash shell script examples for setting environment variables and querying container logs, demonstrating Linux-native patterns.
  • Mention Linux/Bash quoting conventions before or alongside Windows Command Prompt conventions in CLI examples.
  • Include references to Linux-native tools or commands (e.g., using curl or grep inside containers) to show environment variable usage.
  • Balance PowerShell and CLI coverage by providing equivalent Linux shell automation examples.
  • Clarify that Azure CLI is cross-platform and provide guidance for both Windows and Linux users where syntax differs.
GitHub Create Pull Request
Container Instances Execute commands in running container instance ...ticles/container-instances/container-instances-exec.md
High Priority View Details →
Scanned: 2026-01-09 19:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Linux and Windows examples for executing commands in running Azure container instances. However, the Windows (cmd.exe) example is given equal prominence to the Linux (bash) example, and there is no mention of Linux-specific tools or troubleshooting patterns beyond Bash. The documentation refers to 'Command Prompt' and Windows-specific output, and does not mention PowerShell or Linux shells beyond Bash. There is a slight bias towards Windows by providing detailed Windows output and terminology, and by not mentioning Linux alternatives (e.g., sh, zsh) or common Linux troubleshooting tools.
Recommendations
  • Add examples using other common Linux shells (e.g., sh, zsh) to show parity with the Windows cmd.exe example.
  • Include Linux-specific troubleshooting patterns or tools (e.g., using top, ps, or tail inside the container) in the examples.
  • When showing example output, provide both Linux and Windows outputs in parallel, or alternate their order to avoid implicit prioritization.
  • Mention that the Azure CLI commands work identically on both Windows and Linux containers, and clarify any differences in shell invocation.
  • Consider referencing PowerShell as a Windows shell alternative to cmd.exe for completeness.
GitHub Create Pull Request
Container Instances Configure custom DNS settings for container group in Azure Container Instances .../container-instances/container-instances-custom-dns.md
High Priority View Details →
Scanned: 2026-01-09 19:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows Image Example Windows First
Summary
The documentation page demonstrates a subtle Windows bias primarily through the use of a Windows-centric container image (mcr.microsoft.com/powershell) as the main example for deploying a container group with custom DNS settings. The example YAML file and subsequent commands focus on deploying a PowerShell container, which is a Microsoft/Windows tool, even though the container is running on Linux. There is no mention or example of using a typical Linux container image (e.g., Ubuntu, Alpine, nginx), and the only container image shown is PowerShell. Additionally, the container group is named 'pwsh-vnet-dns', further reinforcing the Windows/PowerShell focus. While the CLI instructions are Bash-oriented and the OS type is Linux, the choice of container image and naming conventions prioritize Windows tools over Linux equivalents.
Recommendations
  • Provide additional example YAML files using popular Linux container images (e.g., Ubuntu, nginx, Alpine) to demonstrate DNS configuration in a more Linux-native context.
  • Rename example container groups and images to use neutral or Linux-centric names (e.g., 'ubuntu-vnet-dns', 'nginx-vnet-dns') to avoid implicit Windows/PowerShell prioritization.
  • Include a note or section explicitly showing how to configure DNS for a Linux container image, including troubleshooting tips for common Linux distributions.
  • Balance the documentation by offering both PowerShell and Linux shell container examples, or default to a Linux image given the stated Linux OS type and the target audience for container workloads.
GitHub Create Pull Request
Container Instances Create a standby pool for Azure Container Instances ...r-instances/container-instances-standby-pool-create.md
High Priority View Details →
Scanned: 2026-01-09 19: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 all operations, but PowerShell (a Windows-centric tool) is given equal prominence and is mentioned before ARM template and REST options. There are no explicit Linux shell (bash) or native Linux tool examples, and PowerShell is referenced as a primary automation method. The use of PowerShell cmdlets and deployment patterns (e.g., New-AzResourceGroupDeployment) reflects a Windows-oriented approach. No Linux-specific instructions, troubleshooting, or parity notes are present.
Recommendations
  • Add explicit bash/Linux shell examples for all CLI commands, including sample scripts and environment setup notes for Linux users.
  • Clarify that Azure CLI is fully cross-platform and recommend it as the default for Linux/macOS users, while PowerShell is optional.
  • Reorder sections to present CLI (bash) examples before PowerShell, or clearly indicate platform applicability for each example.
  • Include troubleshooting tips or notes for Linux environments, such as file permissions, environment variables, or common issues.
  • Mention and link to Azure Cloud Shell as a cross-platform, browser-based alternative for both Windows and Linux users.
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
High Priority View Details →
Scanned: 2026-01-09 19:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides explicit examples for Azure CLI (cross-platform), PowerShell (Windows-centric), and REST API, but does not include Linux-specific shell examples (e.g., Bash/cURL) or mention Linux tools. The PowerShell example is given its own section, and there is no parity example for Linux shells. The CLI section does not clarify that it is cross-platform, and PowerShell is presented as a primary method, which may suggest a Windows bias.
Recommendations
  • Add a Bash/cURL example for querying the REST API to demonstrate Linux parity.
  • Clarify that Azure CLI commands work on Windows, Linux, and macOS.
  • If PowerShell is included, consider also including a Bash or shell script example.
  • Reorder examples or explicitly state that all platforms are supported equally.
  • Mention common Linux troubleshooting tools or patterns where relevant.
GitHub Create Pull Request
Container Instances Standby pools for Azure Container Instances ...instances/container-instances-standby-pool-overview.md
High Priority View Details →
Scanned: 2026-01-09 19:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by primarily using Azure PowerShell for provider registration and by listing PowerShell examples before CLI equivalents in the availability zones section. There are no explicit Linux shell (bash) examples for provider registration, and the use of Azure Cloud Shell is not clarified as cross-platform. This may hinder Linux users who prefer Azure CLI or bash scripting.
Recommendations
  • Provide Azure CLI (bash) examples alongside or before PowerShell examples for provider registration and other key operations.
  • Clarify that Azure Cloud Shell supports both Bash and PowerShell, and indicate which shell is being used in each example.
  • Ensure that for every PowerShell example, an equivalent Azure CLI (bash) command is provided.
  • Consider listing CLI (bash) examples before PowerShell to avoid implicit Windows-first bias.
  • Explicitly mention Linux compatibility and provide guidance for Linux/macOS users where relevant.
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
High Priority View Details →
Scanned: 2026-01-09 19: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 requesting a container group from a standby pool, but PowerShell (a Windows-centric tool) is given its own dedicated section and example. There is no mention of Linux-specific shell patterns (e.g., bash scripting), nor are Linux-native tools or package managers referenced. The ARM template and REST API examples are platform-neutral, but the command-line examples lean towards Windows by including PowerShell and referencing its cmdlets. The ordering of examples places CLI first, but the presence and detail of PowerShell content suggests a Windows bias.
Recommendations
  • Add explicit bash or shell script examples for Linux users, especially for automation scenarios.
  • Clarify that Azure CLI commands work cross-platform and provide sample usage in bash/zsh (e.g., with environment variables, piping, etc.).
  • If PowerShell is included, consider also including Linux shell equivalents or note PowerShell Core compatibility on Linux.
  • Reference Linux package managers or installation instructions for Azure CLI and PowerShell, if relevant.
  • Ensure that documentation language and examples do not assume a Windows environment by default.
GitHub Create Pull Request
Container Instances Update or delete a standby pool for Azure Container Instances ...nces/container-instances-standby-pool-update-delete.md
High Priority View Details →
Scanned: 2026-01-09 19: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 as CLI, and is mentioned before Linux-native alternatives in some places. There is no explicit mention of Linux shell scripting, nor are there Bash or Linux-specific examples. The ARM template and REST API sections are platform-neutral, but the overall example set leans toward Windows tooling and patterns.
Recommendations
  • Add explicit Bash/Linux shell examples for all CLI commands, demonstrating usage in a Linux terminal.
  • Clarify that Azure CLI is cross-platform and show examples of running CLI commands in Linux environments (e.g., with Bash syntax and environment variables).
  • Consider reordering sections so that CLI (cross-platform) examples appear before PowerShell (Windows-centric) examples.
  • Add notes or links for Linux users, such as installation instructions for Azure CLI on Linux.
  • Avoid assuming PowerShell is the default scripting environment; mention alternatives for Linux and macOS users.
GitHub Create Pull Request
Container Instances Tutorial - Trigger container group by Azure function ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/container-instances/container-instances-tutorial-azure-function-trigger.md
High Priority View Details →
Scanned: 2026-01-09 19:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on PowerShell and Windows-centric tooling. All code examples use PowerShell cmdlets, and the workflow assumes use of Visual Studio Code with the Azure Functions extension, which is most commonly used on Windows. There is no mention of Bash, Azure CLI, or Linux-native scripting alternatives for creating or managing Azure Functions or container groups. The prerequisites and steps reference PowerShell installation and usage exclusively, and do not provide parity for Linux users who may prefer Bash or Azure CLI.
Recommendations
  • Provide equivalent examples using Azure CLI and Bash scripts for all major steps, especially for resource creation, identity assignment, and container group deployment.
  • Explicitly mention and link to Linux setup guides for Azure Functions development, including how to use VS Code and the Azure Functions extension on Linux.
  • Include instructions for installing and using Azure CLI on Linux and macOS, and demonstrate how to perform the same operations without PowerShell.
  • Add notes or sections highlighting cross-platform compatibility, and clarify which steps are OS-agnostic and which may require adaptation for Linux environments.
  • Where PowerShell is used, offer side-by-side Bash/Azure CLI equivalents, especially for commands like New-AzContainerGroup, role assignment, and resource cleanup.
GitHub Create Pull Request
Container Instances Set environment variables in container instance ...instances/container-instances-environment-variables.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
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 PowerShell examples for setting environment variables in container instances, but it demonstrates a Windows bias in several ways. PowerShell (a Windows-centric tool) is given a dedicated section with detailed examples, while Linux/macOS equivalents (such as Bash scripting or shell environment variable patterns) are not covered. In the Azure CLI section, instructions for Windows Command Prompt syntax are mentioned, but there is no equivalent guidance for Linux/macOS shells beyond a brief assumption. The portal instructions are platform-neutral, but overall, Linux-specific patterns and troubleshooting are missing.
Recommendations
  • Add explicit Bash and Linux/macOS shell examples for environment variable syntax and command usage.
  • Provide troubleshooting notes for common Linux/macOS issues (e.g., quoting, shell differences).
  • Include links or references to Linux-native tools and workflows for managing containers and environment variables.
  • Balance PowerShell coverage with equivalent Bash or shell scripting guidance.
  • Ensure that CLI instructions are equally clear for both Windows and Linux/macOS users, including syntax nuances.
GitHub Create Pull Request
Container Instances Enable Managed Identity in a Container Group ...iner-instances/container-instances-managed-identity.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows Section Last Linux First Powershell Example Present 🔧 Windows Tools
Summary
The documentation predominantly provides examples and instructions for Linux-based containers, with Bash and Azure CLI commands throughout. Windows container guidance is relegated to a separate section at the end, with only a brief PowerShell script and curl example. There is no parity in step-by-step walkthroughs for Windows containers, and Windows-specific tooling (PowerShell) is only mentioned in the Windows section. The main flow assumes Linux containers and does not offer equivalent Windows-first or Windows-parallel examples.
Recommendations
  • Add full, step-by-step examples for Windows containers, mirroring the Linux container walkthroughs (resource group creation, identity assignment, key vault access, etc.) using PowerShell and Windows-specific patterns.
  • Present Windows and Linux container instructions in parallel where possible, or clearly indicate which steps differ for each platform.
  • Include notes or tables summarizing differences in managed identity usage between Linux and Windows containers at the start of the article.
  • Provide troubleshooting guidance for common Windows container issues (e.g., lack of metadata server, networking constraints).
GitHub Create Pull Request
Container Instances Create a standby pool for Azure Container Instances ...r-instances/container-instances-standby-pool-create.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
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 operations, but PowerShell is given equal prominence and detail as CLI, and ARM template deployment instructions reference PowerShell cmdlets alongside CLI. PowerShell is a Windows-centric tool, and its inclusion as a primary method (rather than, for example, Bash or shell scripting) reflects a Windows bias. Additionally, deployment instructions for ARM templates mention PowerShell before CLI in some places, and there are no Linux/macOS-specific notes or examples (such as Bash scripts or platform caveats).
Recommendations
  • Add Bash or shell script examples for Linux/macOS users, especially for tasks currently only shown in PowerShell.
  • Clarify that Azure CLI is cross-platform and recommend it as the primary method for non-Windows users.
  • Move CLI examples before PowerShell in each section to emphasize platform neutrality.
  • Include notes or links for Linux/macOS users regarding installation and usage of Azure CLI.
  • If PowerShell is necessary, mention PowerShell Core (pwsh) compatibility on Linux/macOS.
GitHub Create Pull Request
Container Instances Configure role permissions for standby pools in Azure Container Instances ...container-instances-standby-pool-configure-permissions.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently references the Azure portal UI for role assignment and troubleshooting, which is platform-agnostic but most commonly used on Windows. There are no command-line examples (e.g., Azure CLI, Bash, PowerShell) for role assignment or troubleshooting, and the only SDKs mentioned for API calls are 'PowerShell or CLI' with PowerShell listed first. No explicit Linux/macOS instructions or examples are provided, and no Linux-specific tools or patterns are referenced.
Recommendations
  • Add Azure CLI and Bash examples for role assignment and troubleshooting, alongside or before PowerShell examples.
  • Explicitly mention that all steps can be performed on Linux/macOS using Azure CLI or REST API.
  • Provide links to cross-platform command-line documentation for role assignment and troubleshooting.
  • When referencing SDKs, list CLI and REST API before PowerShell, or mention all platforms equally.
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
Medium Priority View Details →
Scanned: 2026-01-14 01:31
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 the health state of a standby pool, but PowerShell is given its own dedicated section alongside CLI and REST. There is no mention of Linux-specific tools or shell patterns, and PowerShell (a Windows-centric tool) is featured equally with CLI, despite CLI being cross-platform. No Linux/macOS shell examples (e.g., curl, jq, Bash) are provided.
Recommendations
  • Add Linux/macOS shell examples using curl to demonstrate REST API usage from Bash.
  • Clarify that Azure CLI commands work identically on Linux/macOS and Windows.
  • Consider adding example output parsing using jq or other common Linux tools.
  • If PowerShell is included, note that PowerShell Core is available cross-platform, or provide Bash alternatives.
GitHub Create Pull Request
Container Instances Standby pools for Azure Container Instances ...instances/container-instances-standby-pool-overview.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page exhibits a moderate Windows bias, primarily through the use of PowerShell for critical resource provider registration and by presenting PowerShell examples before CLI or REST alternatives. The initial prerequisite step for provider registration is shown only with an Azure PowerShell command, which may create friction for Linux/macOS users who typically use Bash/CLI. While later sections do provide Azure CLI and REST examples, the initial focus and lack of Bash/CLI for provider registration suggest a Windows-centric approach.
Recommendations
  • Add Azure CLI (az) and Bash examples for resource provider registration alongside the PowerShell example.
  • Ensure all command-line instructions are provided in both Azure CLI and PowerShell, with CLI examples shown first or side-by-side.
  • Explicitly mention cross-platform compatibility for all tools and commands.
  • Consider adding notes or links for installing Azure CLI and PowerShell on Linux/macOS, if relevant.
GitHub Create Pull Request
Container Instances Update or delete a standby pool for Azure Container Instances ...nces/container-instances-standby-pool-update-delete.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
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 as CLI, and is mentioned before Linux alternatives in some places. There are no explicit Linux/macOS shell examples (e.g., Bash), and PowerShell-specific commands and links are included throughout. ARM template and REST examples are platform-neutral, but the presence and prominence of PowerShell and lack of Linux/macOS-specific guidance indicate a moderate Windows bias.
Recommendations
  • Add explicit Bash shell examples for Linux/macOS users alongside PowerShell, especially for common tasks.
  • Clarify that Azure CLI works cross-platform and provide usage notes for Linux/macOS environments (e.g., installation, shell differences).
  • Reorder examples so that platform-neutral or cross-platform tools (CLI, REST, ARM templates) are shown before PowerShell.
  • Include notes or links for Linux/macOS users on how to install and use Azure CLI and ARM templates.
  • Avoid assuming PowerShell is the default automation tool; mention alternatives for Linux/macOS.
GitHub Create Pull Request
Container Instances Override entrypoint in container instance ...ntainer-instances/container-instances-start-command.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
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 the command-line syntax and examples focus primarily on Azure CLI (cross-platform) and Azure PowerShell (Windows-centric). The PowerShell cmdlet is mentioned before the Azure portal and template methods, and no Linux-specific command-line tool (e.g., Bash scripts, shell commands outside Azure CLI) is shown. The only Windows-specific tool referenced is PowerShell, and there are no Linux/macOS-specific command-line examples or troubleshooting tips. The shell table does mention Linux shells, but the documentation does not provide parity in examples for Linux-native workflows.
Recommendations
  • Add explicit Linux/macOS command-line examples using Bash or shell scripts, especially for local testing or troubleshooting.
  • Provide parity in example sections: if PowerShell is shown, also show equivalent Bash commands for Linux/macOS users.
  • Include troubleshooting or usage notes for Linux/macOS users, such as file path conventions or shell differences.
  • Clarify that Azure CLI is cross-platform and highlight any OS-specific considerations.
  • Reorder examples so that cross-platform or Linux-native methods are presented before Windows-specific ones.
GitHub Create Pull Request
Container Instances Tutorial - Trigger container group by Azure function ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/container-instances/container-instances-tutorial-azure-function-trigger.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation is strongly biased toward Windows and PowerShell. All code examples use PowerShell cmdlets, and the tutorial centers on creating a PowerShell Azure Function. Prerequisites and instructions reference Azure PowerShell and Visual Studio Code, with no mention of Bash, Azure CLI alternatives, or Linux/macOS-specific workflows. Linux users are expected to use PowerShell, which is less common and may not be installed by default. No examples are given for creating the function in other supported languages (e.g., Python, JavaScript), nor for using Bash or Azure CLI to manage resources.
Recommendations
  • Provide equivalent examples using Azure CLI and Bash scripts for resource management steps (e.g., enabling managed identity, assigning roles, creating container groups).
  • Include instructions for creating Azure Functions in other supported languages (e.g., Python, JavaScript) and clarify cross-platform support.
  • Add explicit guidance for Linux/macOS users, including installation and usage of PowerShell Core, or alternatives using native tools.
  • Present CLI/Bash examples alongside PowerShell, or at least link to them.
  • Clarify that PowerShell is cross-platform, but acknowledge that Linux users may prefer CLI/Bash and provide parity.
GitHub Create Pull Request
Container Instances Config Maps for Azure Container Instances .../container-instances/container-instances-config-map.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
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 to CLI, and some advanced object construction is only shown in PowerShell. Additionally, Windows container behavior is described using Windows-specific tools (Invoke-Expression, $Env:ConfigMapURI) without offering Linux equivalents for similar tasks. In the section on how config maps are surfaced in containers, the Windows method is described after the Linux method, but relies solely on Windows-native tooling.
Recommendations
  • Ensure that all PowerShell examples have equivalent Bash or shell script examples for Linux/macOS users, especially for advanced object construction.
  • Where Windows-specific tools (e.g., Invoke-Expression, $Env:ConfigMapURI) are mentioned, provide Linux equivalents or clarify that the method is Windows-only.
  • Consider listing CLI (cross-platform) examples before PowerShell examples to reduce perceived Windows-first bias.
  • Add explicit notes or links for Linux/macOS users on how to perform similar tasks using native tools.
  • Clarify any differences in config map mounting or access between Linux and Windows containers, and provide troubleshooting or workaround guidance for each platform.
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
Medium Priority View Details →
Scanned: 2026-01-14 01:31
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 tab, and no Linux/macOS-specific shell examples (such as Bash or curl) are provided. The PowerShell example is detailed, reinforcing a Windows-centric approach. REST API usage is shown, but only as a generic HTTP request, without Linux-oriented command-line examples (e.g., curl or wget).
Recommendations
  • Add Linux/macOS shell examples using curl or wget for REST API calls.
  • Include Bash scripts or command-line usage for Azure CLI, demonstrating usage in typical Linux environments.
  • Ensure that CLI examples are shown before or alongside PowerShell, and clarify that Azure CLI is cross-platform.
  • Explicitly mention Linux/macOS compatibility and usage patterns where relevant.
GitHub Create Pull Request
Container Instances Big containers on Azure container instances ...ob/main/articles/container-instances/big-containers.md
Medium Priority View Details →
Scanned: 2026-01-14 01:31
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page lists PowerShell as a primary deployment method and mentions it before Linux-friendly tools like Azure CLI and ARM templates. There is no mention of Linux-specific shell examples, nor is there explicit parity in example commands or tooling for Linux/macOS users. The focus on PowerShell and the ordering of tools may create friction for non-Windows users.
Recommendations
  • Provide explicit Linux/macOS shell examples (e.g., Bash) alongside PowerShell.
  • List Azure CLI before PowerShell, as it is cross-platform and preferred by many Linux/macOS users.
  • Clarify that all deployment methods (Azure CLI, ARM templates, PowerShell, Portal) are equally supported on all platforms.
  • Include example commands for both Azure CLI and PowerShell for common tasks.
  • Add a note or section on platform compatibility for each tool.
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
Medium Priority View Details →
Scanned: 2026-01-13 21:56
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides explicit examples for Azure CLI, PowerShell, and REST API, but the PowerShell example is given equal prominence as the CLI, and there is no mention of Linux/macOS-specific shell usage (such as Bash or scripting). The CLI example is generic, but the PowerShell example is Windows-specific, and there are no Linux/macOS shell or scripting examples. The documentation does not clarify cross-platform compatibility for the CLI or REST, nor does it mention Linux tools or patterns.
Recommendations
  • Add explicit Bash or shell examples for Linux/macOS users, demonstrating retrieval and parsing of prediction results.
  • Clarify that the Azure CLI and REST API examples are cross-platform and can be used on Linux/macOS as well as Windows.
  • Consider reordering examples so that CLI (cross-platform) comes before PowerShell (Windows-specific), or add a note about platform compatibility.
  • Include troubleshooting or usage notes for Linux/macOS environments, such as authentication or environment setup.
GitHub Create Pull Request
Container Instances Update or delete a standby pool for Azure Container Instances ...nces/container-instances-standby-pool-update-delete.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
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 coverage. The ARM template section references PowerShell deployment commands before CLI equivalents. There are no Linux/macOS-specific shell examples (e.g., Bash), and PowerShell is featured as a primary method, which may create friction for non-Windows users.
Recommendations
  • Add explicit Bash examples for Linux/macOS users, especially for tasks that use Azure CLI.
  • In ARM template deployment instructions, list Azure CLI commands before PowerShell commands to avoid Windows-first ordering.
  • Clarify that Azure CLI works cross-platform and highlight its use for Linux/macOS users.
  • Consider removing or de-emphasizing PowerShell examples in favor of CLI for parity, or add equivalent Bash scripting examples.
  • Add notes or sections addressing Linux/macOS users, including troubleshooting tips for non-Windows environments.
GitHub Create Pull Request
← Previous Page 1 of 4 Next →