Container Apps

196
Total Pages
154
Linux-Friendly Pages
42
Pages with Bias
21.4%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

198 issues found
Showing 1-25 of 198 flagged pages
Container Apps Code to cloud options in Azure Container Apps .../main/articles/container-apps/code-to-cloud-options.md
High Priority View Details →
Scanned: 2026-01-11 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 page demonstrates a Windows bias by prioritizing Windows-centric tools and workflows, such as Visual Studio and Visual Studio Code, in both the main content and resource links. There is frequent mention of PowerShell and Windows-first editors, with little to no explicit guidance or examples for Linux users (e.g., using Linux-native editors or shell environments). The CLI section mentions Bash but does not provide Linux-specific instructions or parity in examples. There are no references to Linux package managers, desktop environments, or alternative editors, and the resource links are heavily skewed toward Windows tooling.
Recommendations
  • Include explicit Linux examples and instructions alongside Windows ones, such as using Bash, Linux terminal, and Linux-native editors (e.g., Vim, Emacs, GNOME Builder).
  • Provide resource links for deploying from Linux environments, including step-by-step guides for Ubuntu, Fedora, or other distributions.
  • Mention and demonstrate use of Linux package managers (apt, yum, etc.) for installing Azure CLI and related tools.
  • Balance references to Visual Studio/Visual Studio Code with Linux alternatives, or clarify cross-platform support in those tools.
  • Add examples of deploying from Linux containers and using Linux-based CI/CD pipelines.
  • Ensure PowerShell and Bash examples are presented in parallel, with equal detail and prominence.
GitHub Create Pull Request
Container Apps Manage environment variables on Azure Container Apps .../main/articles/container-apps/environment-variables.md
High Priority View Details →
Scanned: 2026-01-11 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 managing environment variables in Azure Container Apps. However, the PowerShell section is significantly more detailed, with step-by-step instructions, object model explanations, and multiple code samples, while the CLI section is concise and lacks comparable depth. PowerShell (a Windows-centric tool) receives more attention and is presented after CLI, but with much greater detail. There is no mention of Linux-native tools or shell scripting, nor any examples using Bash or other Linux shells, despite Azure CLI being cross-platform. The documentation assumes familiarity with PowerShell object models and cmdlets, which may not be relevant for Linux users.
Recommendations
  • Provide equally detailed examples for Azure CLI, including step-by-step instructions and explanations of parameters and object relationships.
  • Include Linux/Bash shell scripting examples for setting environment variables, especially for automation scenarios.
  • Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and provide sample commands for Bash/zsh.
  • Avoid assuming PowerShell as the default scripting environment; mention alternatives and cross-platform usage.
  • Add a section comparing usage patterns for both Windows (PowerShell) and Linux/macOS (Bash) environments, highlighting any differences or caveats.
GitHub Create Pull Request
Container Apps Quickstart: Deploy an existing container image with the command line ...container-apps/get-started-existing-container-image.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides both Bash and PowerShell examples for all major steps, maintaining some parity. However, PowerShell (a Windows-centric tool) is given equal prominence throughout, and Windows-specific PowerShell modules and patterns (such as Install-Module, New-AzKeyVault, etc.) are described in detail. There is no mention of Linux-native alternatives to PowerShell, nor is there any discussion of using Linux-specific tools or patterns (e.g., shell scripting, environment variable management, or secret management outside Azure CLI). The documentation assumes PowerShell is a primary cross-platform shell, which is a Windows-centric perspective.
Recommendations
  • Clarify that PowerShell is available cross-platform, but Bash is the default shell on most Linux systems.
  • Provide guidance or links for users who may be using other Linux shells (e.g., zsh, fish) or native Linux tools.
  • Consider including notes or examples for Linux-native secret management (e.g., using environment variables, .env files) where appropriate.
  • Explicitly state that PowerShell examples are for users who prefer it, but Bash is more common on Linux.
  • Ensure that Bash examples are listed first, as Bash is the default on Linux, to avoid implicit Windows-first bias.
  • Add troubleshooting tips for common Linux-specific issues (e.g., permissions, environment variable persistence).
GitHub Create Pull Request
Container Apps Azure Container Apps image pull from Azure Container Registry with managed identity ...articles/container-apps/managed-identity-image-pull.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides parity between Azure CLI (Bash) and Azure PowerShell examples throughout, but there is a noticeable Windows bias: PowerShell is always presented as the alternative to Bash, and installation instructions for Azure PowerShell are included in all sections, even when not strictly necessary for Linux users. References to Azure PowerShell and Windows-centric tooling (e.g., Install-Module, New-AzResourceGroup) are frequent and sometimes appear before or alongside CLI instructions. There are no Linux-specific examples (e.g., shell scripts, automation patterns, or troubleshooting notes for Linux environments), and the documentation does not mention Linux-native tools or patterns beyond Bash/CLI.
Recommendations
  • Add explicit notes clarifying that Azure CLI works cross-platform and is the recommended tool for Linux users.
  • Present Bash/Azure CLI examples first in each section, with PowerShell as an alternative, to reduce Windows-first perception.
  • Remove unnecessary PowerShell installation instructions from sections where Bash/CLI is sufficient.
  • Include troubleshooting tips or notes for Linux environments (e.g., file permissions, environment variables, common errors).
  • Reference Linux-native automation patterns (e.g., using shell scripts, cron jobs) where relevant.
  • Clarify that PowerShell Core is available on Linux, but Bash/CLI is more common for Linux users.
  • Ensure that screenshots and UI instructions do not assume Windows conventions (e.g., path separators, UI layout).
GitHub Create Pull Request
Container Apps Create a zone-redundant container app ...main/articles/container-apps/how-to-zone-redundancy.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides step-by-step instructions for creating a zone-redundant container app using the Azure Portal (a web UI, but often associated with Windows users), Azure CLI, and Azure PowerShell. The PowerShell section is extensive and uses Windows-specific tooling. There are no explicit Linux shell examples (e.g., bash scripts), and PowerShell is featured as a primary automation option, which is Windows-centric. The CLI examples use Azure CLI, which is cross-platform, but the lack of Linux-specific shell scripting or notes about Linux environments suggests a subtle Windows bias. The order of presentation (Portal, CLI, PowerShell) also places Windows-centric tools before Linux-native approaches.
Recommendations
  • Add explicit bash shell scripting examples for Linux users alongside Azure CLI commands.
  • Clarify that Azure CLI commands work equally on Linux, macOS, and Windows, and provide any OS-specific notes if needed.
  • Include troubleshooting or environment setup notes for Linux (e.g., installing Azure CLI on Ubuntu).
  • Balance PowerShell examples with bash or zsh equivalents for automation tasks.
  • Consider reordering sections to present cross-platform tools (CLI) before Windows-specific tools (PowerShell).
GitHub Create Pull Request
Container Apps Manage secrets in Azure Container Apps ...cs/blob/main/articles/container-apps/manage-secrets.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias by providing extensive PowerShell examples and support, while lacking equivalent Linux shell or Bash examples. PowerShell is presented as a primary automation tool, with no mention of Linux-specific scripting or workflows. Additionally, certain features (such as Key Vault secret references and secret volume mounts) are explicitly unsupported in PowerShell, but there is no guidance for Linux users on alternative approaches. The documentation does not include any Bash or Linux shell script examples, nor does it address Linux-specific usage patterns.
Recommendations
  • Add Bash/Linux shell script examples alongside PowerShell for all CLI workflows.
  • Explicitly mention Linux support and usage patterns where features are not available in PowerShell.
  • Provide guidance for Linux users on how to accomplish tasks that are unsupported in PowerShell, such as mounting secrets as volumes.
  • Ensure that examples and instructions are not Windows-centric and include cross-platform considerations.
  • Where PowerShell is used, clarify its cross-platform availability or suggest alternatives for Linux environments.
GitHub Create Pull Request
Container Apps Use a private endpoint with an Azure Container Apps environment ...articles/container-apps/how-to-use-private-endpoint.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias in several ways. When guiding users to create a VM for private endpoint testing, only Windows Server is offered as the example image, both in the Azure Portal and Azure CLI instructions. The instructions for verifying DNS resolution use PowerShell commands, with no mention of Linux alternatives (e.g., using dig or nslookup in a Linux shell). There are no examples or guidance for creating or connecting to a Linux VM, nor for using Linux-native tools to test connectivity. The documentation assumes the user is working in a Windows environment for verification and troubleshooting steps.
Recommendations
  • Provide parallel instructions for creating a Linux VM (e.g., Ubuntu) in both Azure Portal and Azure CLI sections.
  • Include Linux shell commands (e.g., 'nslookup', 'dig', 'curl', 'wget') for verifying DNS and connectivity, alongside PowerShell examples.
  • When listing VM images, mention both Windows and popular Linux distributions, allowing users to choose.
  • Clarify that the verification steps can be performed from either Windows or Linux VMs, and provide equivalent commands for each.
  • Ensure troubleshooting links and examples reference both Windows and Linux tools where applicable.
GitHub Create Pull Request
Container Apps Managed identities in Azure Container Apps .../blob/main/articles/container-apps/managed-identity.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page provides a PowerShell example for retrieving tokens from the managed identity endpoint, but does not offer equivalent Linux shell (bash/curl) examples. PowerShell is a Windows-centric tool, and its inclusion without Linux alternatives suggests a bias towards Windows users. Additionally, the use of Azure CLI is cross-platform, but the absence of explicit Linux shell examples (e.g., bash/curl) for direct HTTP requests further reinforces the Windows-first approach in scripting sections.
Recommendations
  • Add Linux shell (bash/curl) examples alongside PowerShell for retrieving tokens from the managed identity endpoint.
  • Explicitly mention that Azure CLI commands work on both Windows and Linux, and provide any necessary platform-specific notes.
  • Ensure that scripting examples (especially for HTTP requests) include both PowerShell and bash/curl variants, with equal prominence.
  • Review other scripting or automation sections for implicit Windows tool assumptions and provide Linux equivalents where appropriate.
GitHub Create Pull Request
Container Apps Monitor Azure Container Apps metrics ...zure-docs/blob/main/articles/container-apps/metrics.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation references Azure PowerShell cmdlets alongside Azure CLI for retrieving metrics, but does not mention or provide examples for Linux-specific tools or workflows. The mention of PowerShell (a Windows-centric tool) and the lack of Linux shell examples or parity in tooling suggests a subtle Windows bias. No Linux-specific instructions, screenshots, or command-line examples are present.
Recommendations
  • Include explicit Linux shell (bash) examples for metric retrieval using Azure CLI.
  • Clarify that Azure CLI works cross-platform and provide sample commands for both Windows (PowerShell) and Linux (bash).
  • Mention Linux-native monitoring tools (e.g., curl, jq, shell scripting) where relevant.
  • Add screenshots or instructions that demonstrate usage from Linux environments.
  • Ensure that references to PowerShell are balanced with Linux shell alternatives, or clarify cross-platform compatibility.
GitHub Create Pull Request
Container Apps Manage revisions in Azure Container Apps .../blob/main/articles/container-apps/revisions-manage.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page provides both Bash (Azure CLI) and PowerShell examples for all revision management tasks in Azure Container Apps. PowerShell examples are given for every command, sometimes using native Azure PowerShell cmdlets, which are primarily Windows-centric. In several cases, PowerShell examples are presented immediately after Bash, and in some cases, PowerShell-specific tools (e.g., Update-AzContainerApp, Get-AzContainerAppRevision) are used, which do not have direct Linux equivalents. There is an implicit Windows bias due to the heavy inclusion of PowerShell and Azure PowerShell cmdlets, which are less commonly used on Linux. The documentation does not mention Linux shell alternatives (e.g., zsh, fish), nor does it clarify that PowerShell can be used cross-platform.
Recommendations
  • Clarify that PowerShell is available cross-platform, but that Azure PowerShell cmdlets are most commonly used in Windows environments.
  • Provide examples using only Azure CLI (which is fully cross-platform) as the primary method, and move PowerShell examples to a dedicated section or appendix.
  • Explicitly mention that Bash examples are applicable to Linux, macOS, and Windows (via WSL or Git Bash), and consider including zsh/fish shell compatibility notes.
  • Where Azure PowerShell cmdlets are used, note that these are primarily for Windows users and recommend Azure CLI for Linux/macOS users.
  • Consider adding a table comparing Azure CLI and Azure PowerShell usage, with platform recommendations.
  • Avoid presenting PowerShell examples immediately after Bash, or at least alternate the order to avoid 'Windows-first' perception.
GitHub Create Pull Request
Container Apps Troubleshooting in Azure Container Apps ...s/blob/main/articles/container-apps/troubleshooting.md
High Priority View Details →
Scanned: 2026-01-11 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 page demonstrates Windows bias by referencing Windows-specific tools and patterns, such as 'elevated command prompt' and Docker on Windows, and by providing PowerShell examples alongside Azure CLI. The instructions often assume use of the Azure portal (which is OS-agnostic but more familiar to Windows users) and mention PowerShell before Bash in some places. There is a lack of explicit Linux shell (e.g., bash) troubleshooting examples, and no mention of Linux-specific considerations for Docker or command-line usage.
Recommendations
  • Include Linux-specific instructions and troubleshooting steps, such as running Docker commands in a Linux terminal and verifying Docker Engine status on Linux.
  • Provide bash examples alongside PowerShell for all command-line operations, and ensure Bash is presented first or equally.
  • Avoid referencing 'elevated command prompt' without also mentioning 'sudo' for Linux users.
  • Add notes or sections for common Linux issues (e.g., permissions, service management) when running containers.
  • Ensure all tool references (e.g., Docker Desktop) mention both Windows and Linux installation guides.
  • Review the order of examples and instructions to avoid Windows-first presentation.
GitHub Create Pull Request
Container Apps Tutorial: Build and deploy your app to Azure Container Apps ...main/articles/container-apps/tutorial-code-to-cloud.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides both Bash and PowerShell examples for all major steps, but PowerShell is treated as a first-class citizen throughout, with full, detailed examples and explanations. PowerShell-specific Azure commands (e.g., New-AzContainerRegistry, New-AzUserAssignedIdentity) are used, which are only available on Windows or require extra effort on Linux. In some cases, PowerShell examples are more verbose and detailed than Bash. Docker Desktop is mentioned as the recommended Docker installation, which is a Windows/Mac-centric tool, even though Linux users typically use native Docker. There is no explicit Linux shell example (e.g., zsh, fish), and Bash is presented generically. PowerShell examples are always present and sometimes precede Bash, reinforcing a Windows-centric workflow.
Recommendations
  • Add explicit Linux-native instructions for Docker installation and usage, referencing the standard Linux Docker Engine installation guides rather than Docker Desktop.
  • Clarify that PowerShell examples are for users who have PowerShell Core installed on Linux/macOS, or provide alternative Bash-only workflows for Linux users.
  • Where PowerShell-specific Azure commands are used, note their platform requirements and provide equivalent Bash/Azure CLI commands for Linux users.
  • Consider reordering examples so Bash/Linux instructions are presented first, or at least equally, to avoid implicit prioritization of Windows/PowerShell.
  • Add troubleshooting notes for Linux users regarding potential issues with PowerShell modules and Azure CLI compatibility.
  • Explicitly mention that all steps are fully supported on Linux, and highlight any platform-specific caveats.
GitHub Create Pull Request
Container Apps Tutorial: Run GitHub Actions runners and Azure Pipelines agents with Azure Container Apps jobs ...articles/container-apps/tutorial-ci-cd-runners-jobs.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Windows Container Recommendation
Summary
The documentation provides both Bash and PowerShell examples for all CLI commands, but PowerShell is given equal prominence throughout, which may indicate a slight Windows bias. Troubleshooting and container image build sections mention Windows-based containers and Mono for .NET Framework, suggesting Windows development patterns. There is also a recommendation to use Windows containers for .NET Framework workloads, which is a Windows-centric solution. However, Linux options (Bash, Mono on Linux, .NET Core) are also described, and most examples default to Linux-compatible workflows. No Linux examples are missing, but Windows-specific advice appears before or alongside Linux alternatives in some places.
Recommendations
  • Make Bash the default or primary example, with PowerShell as a secondary tab, to reflect the prevalence of Linux in container workloads.
  • When recommending solutions for .NET Framework, clarify the tradeoffs between Windows and Linux containers, and provide more guidance for Linux-based builds (e.g., using Mono) before suggesting Windows containers.
  • Explicitly state that all CLI commands work on Linux and macOS, and provide troubleshooting tips for those platforms.
  • Avoid suggesting Windows containers as the primary solution unless absolutely necessary; instead, present Linux solutions first.
  • Add a section or note about running the tutorial entirely on Linux, including any OS-specific caveats or requirements.
GitHub Create Pull Request
Container Apps Integrate a virtual network with an Azure Container Apps environment ...-docs/blob/main/articles/container-apps/vnet-custom.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides both Bash (Azure CLI) and PowerShell examples throughout, but PowerShell (a Windows-centric tool) is given equal prominence and detail as Bash. Many advanced configuration steps, such as creating subnets, delegating, and DNS setup, are shown in PowerShell using Az modules, which are primarily used on Windows. There is no mention of Linux-native tools (e.g., native shell commands, networking utilities) or guidance for Linux users beyond Bash/CLI. PowerShell examples are present for every step, and parameter tables use PowerShell-specific names before CLI equivalents, indicating a subtle Windows-first bias.
Recommendations
  • Clarify that PowerShell examples are for users on Windows or those who have installed PowerShell Core on Linux/macOS.
  • Add explicit notes or guidance for Linux users, such as confirming that all Azure CLI commands work natively on Linux/macOS terminals.
  • Consider providing examples using other Linux-native tools where applicable (e.g., networking validation with ip/ifconfig, DNS checks with dig/nslookup).
  • Ensure parameter tables list Azure CLI/Bash parameters first, or side-by-side with PowerShell equivalents.
  • Add troubleshooting tips for Linux environments, such as handling permissions, environment variables, or common CLI issues.
GitHub Create Pull Request
Container Apps Observability of managed Java components in Azure Container Apps ...ob/main/articles/container-apps/java-component-logs.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both Bash and PowerShell examples for querying logs via Azure CLI, but the variable assignment uses 'SET' in Bash, which is a Windows CMD command, not standard Bash. PowerShell examples are given equal prominence, and there are no explicit Linux-specific instructions or troubleshooting notes. The use of 'SET' in Bash examples may confuse Linux users, and there is a general lack of Linux tool references or patterns.
Recommendations
  • Replace 'SET $WORKSPACE_ID=<WORKSPACE_ID>' with 'export WORKSPACE_ID=<WORKSPACE_ID>' in Bash examples to ensure compatibility with Linux/macOS shells.
  • Add explicit notes or troubleshooting tips for Linux users, such as shell differences and environment variable usage.
  • Consider including examples using native Linux tools (e.g., grep, jq) for log processing, if relevant.
  • Ensure that Bash examples are tested on Linux and macOS environments, not just Windows.
  • Review all CLI instructions to avoid Windows-centric commands or patterns.
GitHub Create Pull Request
Container Apps Tutorial: Build and deploy your app to Azure Container Apps ...main/articles/container-apps/tutorial-code-to-cloud.md
High 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 Bash and PowerShell examples for most commands, but PowerShell is featured heavily and in detail, including advanced Azure PowerShell cmdlets and object construction. Windows-specific tools like Docker Desktop for Windows are mentioned explicitly, and PowerShell examples are often more verbose or detailed than Bash. In some cases, PowerShell cmdlets (e.g., Connect-AzContainerRegistry) are used where Bash relies on cross-platform CLI commands. The documentation also references Windows in Docker installation instructions before Linux, and PowerShell is presented as a first-class option throughout, which may signal a Windows-centric approach.
Recommendations
  • Ensure Bash examples are as detailed as PowerShell, especially for advanced Azure operations (e.g., resource creation, role assignments).
  • Where possible, prefer Azure CLI commands over Azure PowerShell cmdlets, as CLI is more universally available across platforms.
  • When referencing Docker installation, list Linux instructions before or alongside Windows/macOS to avoid perceived prioritization.
  • Add explicit notes or sections for Linux-specific considerations, such as package managers, shell environments, and permissions.
  • Review PowerShell-heavy sections to see if equivalent Bash/CLI workflows can be provided, especially for resource management and role assignments.
  • Consider including troubleshooting tips for Linux users, such as SELinux, firewall, or networking issues that may differ from Windows.
GitHub Create Pull Request
Container Apps Code to cloud options in Azure Container Apps .../main/articles/container-apps/code-to-cloud-options.md
High Priority View Details →
Scanned: 2026-01-10 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 page demonstrates a Windows bias by prioritizing Windows-centric tools and workflows. Visual Studio and Visual Studio Code are highlighted as primary code editors, with deployment examples and resources focused on these tools, which are most commonly used on Windows. The Infrastructure as Code section mentions PowerShell before Bash, and the CLI examples do not provide explicit Linux-specific instructions or parity. There is little to no mention of Linux-native editors (e.g., Vim, Emacs), nor are there examples or resources tailored for Linux users.
Recommendations
  • Add explicit Linux examples for CLI usage, including Bash scripts and terminal commands.
  • Include references to Linux-native editors (e.g., Vim, Emacs, JetBrains IDEs) and how they can be used in the code-to-cloud workflow.
  • Provide deployment instructions and resources for Linux environments, such as using Docker and Azure CLI on Ubuntu or other distributions.
  • Balance the mention of PowerShell and Bash, ensuring Bash is not secondary and is given equal prominence.
  • Add troubleshooting or setup notes for Linux users, such as installing Azure CLI or Docker on Linux.
  • Ensure that all code samples and walkthroughs are cross-platform, with clear indications for both Windows and Linux users.
GitHub Create Pull Request
Container Apps Manage environment variables on Azure Container Apps .../main/articles/container-apps/environment-variables.md
High 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 extensive PowerShell examples and details, including object creation and cmdlet usage, which are specific to Windows environments. PowerShell instructions are given equal prominence to Azure CLI, but the PowerShell section is much more detailed and assumes familiarity with Windows tooling. There is no mention of Linux-specific shell scripting, environment variable management patterns, or alternative tools (e.g., Bash, zsh, or cloud-native YAML manifests). The documentation implicitly favors Windows users by focusing on PowerShell and omitting Linux-centric approaches.
Recommendations
  • Add Linux shell (Bash) examples for managing environment variables, such as using environment variable files or inline shell commands.
  • Include guidance for users working in Linux environments, such as using Azure CLI from Bash or zsh, and how to set environment variables in those shells.
  • Mention cross-platform compatibility of Azure CLI and clarify that PowerShell is optional, not required.
  • Provide parity in example detail: if PowerShell examples include object creation and advanced usage, offer equivalent Bash scripting or YAML manifest examples for Linux users.
  • Reference Linux tools and patterns (e.g., exporting variables, using .env files) alongside Windows/PowerShell approaches.
GitHub Create Pull Request
Container Apps Use a private endpoint with an Azure Container Apps environment ...articles/container-apps/how-to-use-private-endpoint.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias in several areas. When creating a VM to test the private endpoint, only Windows Server is used as the example OS, both in the Azure Portal and Azure CLI instructions. The instructions for verifying DNS resolution and connectivity use PowerShell commands inside the Windows VM, with no mention of Linux alternatives (e.g., using Ubuntu and the dig or nslookup command in Bash). There are no examples or guidance for Linux VM creation or testing, and Windows tools/patterns (PowerShell, Windows Server image) are mentioned exclusively.
Recommendations
  • Add parallel instructions for creating a Linux VM (e.g., Ubuntu) in both Azure Portal and Azure CLI sections.
  • Provide Linux-based commands for DNS resolution and connectivity testing (e.g., using dig or nslookup in Bash).
  • When listing VM image options, mention both Windows and Linux images, or make Linux the default for parity.
  • Where PowerShell is used, offer equivalent Bash commands for Linux users.
  • Explicitly state that the steps apply to both Windows and Linux, and highlight any OS-specific differences.
GitHub Create Pull Request
Container Apps Manage secrets in Azure Container Apps ...cs/blob/main/articles/container-apps/manage-secrets.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell examples for managing secrets in Azure Container Apps, while omitting equivalent Linux shell (bash) examples. PowerShell is featured as a primary method alongside Azure CLI and ARM templates, but there are no bash or Linux-specific command-line examples. Additionally, certain features (such as Key Vault secret references and mounting secrets as volumes) are explicitly noted as unsupported in PowerShell, but there is no guidance for Linux users or alternative approaches. The documentation assumes familiarity with Windows tools and patterns, and does not address Linux workflows or shell scripting.
Recommendations
  • Add bash/Linux shell examples for all CLI operations, especially for secret management and environment variable referencing.
  • Include notes or sections for Linux users, clarifying how to perform equivalent tasks using bash or other common Linux tools.
  • Present CLI examples before PowerShell, or side-by-side, to avoid Windows-first ordering.
  • Explicitly mention cross-platform compatibility for Azure CLI commands and provide troubleshooting tips for Linux environments.
  • Where PowerShell is unsupported, suggest Linux alternatives or provide links to relevant documentation for Linux users.
GitHub Create Pull Request
Container Apps Managed identities in Azure Container Apps .../blob/main/articles/container-apps/managed-identity.md
High 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 a PowerShell example for obtaining tokens from the managed identity endpoint, but does not provide equivalent Linux shell (bash/curl) examples. The use of PowerShell and Windows environment variable syntax is presented before any Linux alternatives, and no Linux-specific command-line patterns (e.g., bash, curl, wget) are shown for this scenario. This may make it harder for Linux users to follow the documentation, especially for tasks like token retrieval from the endpoint.
Recommendations
  • Add Linux shell (bash) examples alongside PowerShell for token retrieval, using curl or wget.
  • Show both Windows (PowerShell) and Linux (bash) environment variable syntax in all relevant code snippets.
  • Explicitly mention that the HTTP GET example can be performed with curl/wget and provide sample commands.
  • Ensure that CLI and scripting examples are platform-neutral or provide both Windows and Linux variants.
  • Review other sections for implicit Windows-first assumptions and add Linux parity where needed.
GitHub Create Pull Request
Container Apps Azure Container Apps image pull from Azure Container Registry with managed identity ...articles/container-apps/managed-identity-image-pull.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. PowerShell examples are provided alongside Bash, but Windows/PowerShell tooling is mentioned first or equally throughout. Prerequisites and instructions frequently reference Azure PowerShell and Windows-centric installation steps. There is no explicit mention of Linux-specific patterns or troubleshooting, and the CLI examples are generic rather than tailored for Linux environments. The documentation assumes parity between Bash and PowerShell, but the prominence of PowerShell and Windows tools may make Linux users feel secondary.
Recommendations
  • Add explicit Linux-focused instructions and troubleshooting steps, especially for common issues encountered on Linux distributions.
  • Where PowerShell is mentioned, clarify that Bash is recommended for Linux and macOS users, and provide links to relevant shell documentation.
  • Include notes about platform differences in environment variable handling, file paths, and permissions.
  • Ensure that Azure CLI examples are tested and presented in a way that is native to Linux (e.g., using export for environment variables, avoiding Windows-specific syntax).
  • Consider adding a dedicated Linux section or pivot, highlighting best practices and common workflows for Linux users.
  • Review installation instructions to ensure they do not assume Windows as the default platform.
GitHub Create Pull Request
Container Apps Monitor Azure Container Apps metrics ...zure-docs/blob/main/articles/container-apps/metrics.md
High Priority View Details →
Scanned: 2026-01-10 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 page exhibits Windows bias by mentioning Azure PowerShell cmdlets alongside Azure CLI as the primary methods for retrieving metric data, with PowerShell referenced before any Linux-specific tools or patterns. There are no Linux shell or Bash examples, nor is there mention of Linux-native monitoring tools or workflows. The documentation assumes familiarity with Windows-centric tools and does not provide parity for Linux users.
Recommendations
  • Include explicit Bash or shell examples for metric retrieval using Azure CLI.
  • Mention Linux-native tools (e.g., curl, jq) for processing metric data from Azure CLI.
  • Ensure that CLI examples are presented before or alongside PowerShell examples, not after.
  • Add guidance for integrating Azure metrics with popular Linux monitoring stacks (e.g., Prometheus, Grafana).
  • Clarify that Azure CLI is cross-platform and provide usage notes for both Windows and Linux environments.
GitHub Create Pull Request
Container Apps Troubleshooting in Azure Container Apps ...s/blob/main/articles/container-apps/troubleshooting.md
High Priority View Details →
Scanned: 2026-01-10 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 demonstrates a Windows bias by referencing Windows-specific tools and patterns, such as 'elevated command prompt' and Docker on Windows, and by providing PowerShell examples alongside Azure CLI. Linux-specific instructions (e.g., running Docker on Linux, using Bash) are either missing or appear after Windows/PowerShell references. The troubleshooting steps and examples frequently assume a Windows environment, with little to no parity for Linux users.
Recommendations
  • Add explicit instructions and examples for Linux environments, such as running Docker commands in a Linux terminal and verifying Docker Engine status on Linux.
  • Present Bash/Azure CLI examples before PowerShell examples, or side-by-side, to avoid Windows-first ordering.
  • Avoid references to 'elevated command prompt' and instead use platform-neutral language like 'terminal' or provide both Windows and Linux equivalents.
  • Include troubleshooting steps and tool references for Linux users (e.g., how to check Docker status on Linux, common Linux errors).
  • Ensure parity in all code samples and instructions, so that both Windows and Linux users can follow along without ambiguity.
GitHub Create Pull Request
Container Apps Manage revisions in Azure Container Apps .../blob/main/articles/container-apps/revisions-manage.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation consistently provides both Bash (Azure CLI) and PowerShell examples for all commands, with PowerShell examples using Windows-centric cmdlets (e.g., Get-AzContainerAppRevision, Update-AzContainerApp). In several cases, PowerShell examples are given even when no direct PowerShell equivalent exists, and the Bash/Azure CLI examples are sometimes presented as secondary or fallback. The use of PowerShell cmdlets and parameters reflects a bias toward Windows tooling and patterns, and the documentation assumes familiarity with Windows/PowerShell environments.
Recommendations
  • Clearly indicate that PowerShell examples are for Windows users and Bash examples are for Linux/macOS users, to avoid confusion.
  • Ensure Bash/Azure CLI examples are presented first, as Azure CLI is cross-platform and more widely used in Linux environments.
  • Where PowerShell examples use Azure CLI commands (e.g., az containerapp revision copy), clarify that these can be run in any shell, not just PowerShell.
  • Add explicit notes or sections for Linux/macOS users, including troubleshooting tips or environment setup instructions.
  • Avoid using Windows-specific cmdlets or patterns unless there is no cross-platform alternative, and always provide a CLI-based example.
  • Consider adding examples for other shells (e.g., zsh, fish) or scripting environments where relevant.
GitHub Create Pull Request
← Previous Page 1 of 8 Next →