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 26-50 of 198 flagged pages
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Bash and PowerShell examples for all CLI commands, but PowerShell is given equal prominence to Bash, which may indicate a Windows bias. There are several references to Windows-specific concerns (e.g., Mono/.NET Framework, suggesting Windows containers for certain workloads). Troubleshooting and agent setup sections mention Windows containers as alternatives, and PowerShell is always presented as a first-class option, sometimes with more detailed syntax. There are no Linux-only examples, and Windows-specific build concerns (Mono, .NET Framework) are discussed before Linux alternatives. The documentation does not mention Linux-specific tools or patterns, nor does it provide guidance for Linux desktop users (e.g., using native Linux package managers, shell environments, or alternatives to PowerShell).
Recommendations
  • Present Bash examples before PowerShell to reflect the default shell on most CI/CD runners and Linux environments.
  • Add explicit notes or sections for Linux users, such as using native Linux package managers (apt, yum) for prerequisites.
  • When discussing .NET Framework and Mono, clarify that these are Windows-specific concerns and provide Linux-first alternatives (e.g., .NET Core/5+).
  • Include troubleshooting steps for common Linux issues (e.g., permissions, SELinux/AppArmor, systemd integration) alongside Windows-specific troubleshooting.
  • Reference Linux desktop environments and workflows where relevant, such as using GNOME/KDE tools or Linux-native authentication methods.
  • If PowerShell is mentioned, clarify its cross-platform nature and provide guidance for users who prefer Bash or other shells.
  • Avoid suggesting Windows containers as the primary solution for .NET Framework workloads; instead, recommend modern .NET versions that run natively on Linux containers.
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-10 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 (Azure CLI) and PowerShell examples throughout, but PowerShell (Windows-centric) is consistently presented as an equal alternative to Bash, rather than as a secondary option. There is a notable emphasis on PowerShell-specific tooling and patterns, such as the use of New-Az* and Set-Az* cmdlets, which are exclusive to Windows environments. The documentation does not mention Linux-specific tools or patterns (e.g., native Linux networking tools, shell scripting alternatives, or package managers), nor does it clarify that PowerShell examples are primarily for Windows users. Additionally, in some sections, PowerShell examples are given immediately after Bash, reinforcing parity rather than Linux-first guidance.
Recommendations
  • Clearly indicate that PowerShell examples are intended for Windows users, and Bash examples are for Linux/macOS users.
  • Consider presenting Bash (Linux/macOS) examples first, with PowerShell as a secondary option, to reinforce Linux parity.
  • Add notes or guidance for users on Linux who may encounter issues with PowerShell-specific commands or concepts.
  • Where possible, reference Linux-native tools or patterns (e.g., using native networking commands, environment variable handling) in addition to Azure CLI.
  • Ensure that all features and steps are equally achievable on Linux, and call out any Windows-only limitations.
  • Review included files (e.g., container-apps-create-portal-steps.md) for similar bias and update as needed.
GitHub Create Pull Request
Container Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/managed-identity.md .../blob/main/articles/container-apps/managed-identity.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides a PowerShell example for retrieving tokens from the managed identity endpoint, but does not offer equivalent Linux shell (bash/curl) examples. The use of PowerShell and Windows-centric scripting is present, while Linux-native tools and patterns are not mentioned or demonstrated. This may make it less accessible for users working in Linux-based environments, which are common for container workloads.
Recommendations
  • Add Linux shell (bash/curl) examples alongside PowerShell for token retrieval from the managed identity endpoint.
  • Explicitly mention that Azure CLI commands work cross-platform and provide sample commands for both Windows and Linux shells where relevant.
  • Ensure that scripting examples (e.g., for HTTP requests) use both PowerShell and bash/curl to demonstrate parity.
  • Review other sections for implicit Windows-first assumptions and clarify cross-platform compatibility.
  • Consider adding troubleshooting notes for common Linux-specific issues (e.g., environment variable syntax differences).
GitHub Create Pull Request
Container Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/code-to-cloud-options.md .../main/articles/container-apps/code-to-cloud-options.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 a Windows bias by prioritizing Windows-centric tools (Visual Studio, Visual Studio Code) and workflows, mentioning PowerShell before Bash, and lacking explicit Linux-focused examples or tooling. The code editor section exclusively highlights Visual Studio and Visual Studio Code, both strongly associated with Windows environments, and does not mention popular Linux editors or workflows. The infrastructure as code section references PowerShell and Bash together, but PowerShell is listed first, and no Linux-specific CLI usage or examples are provided. There are no references to Linux-native editors (e.g., Vim, Emacs), nor are there examples or guidance for deploying from a Linux environment.
Recommendations
  • Add explicit examples and instructions for deploying from Linux environments, including using Bash and Linux-native tools.
  • Include references to popular Linux editors (e.g., Vim, Emacs, JetBrains IDEs) and workflows for container app deployment.
  • Ensure CLI instructions and automation examples are shown for both PowerShell and Bash, with equal prominence.
  • Provide parity in resource links and tutorials for Linux users, such as guides for setting up Azure CLI and AZD on Linux.
  • Avoid listing Windows tools or workflows before their Linux equivalents; present options in a neutral or parallel manner.
GitHub Create Pull Request
Container Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/environment-variables.md .../main/articles/container-apps/environment-variables.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 managing environment variables in Azure Container Apps. However, the PowerShell section is significantly more detailed, with step-by-step object creation and usage instructions, while the CLI section is comparatively brief. The PowerShell examples rely on Windows-specific cmdlets and object models, and PowerShell is a Windows-centric tool. There are no Linux shell (bash) or scripting examples, nor are there references to Linux-native tools or patterns. PowerShell is presented as a first-class, detailed option, which may disadvantage Linux users or those unfamiliar with PowerShell.
Recommendations
  • Add equivalent bash shell scripting examples for Azure CLI usage, demonstrating environment variable management in a Linux context.
  • Include notes or sections on how to use these commands in Linux environments, such as using bash variables or scripting with az CLI.
  • Balance the level of detail between PowerShell and CLI sections, ensuring Linux users have access to similarly comprehensive guidance.
  • Avoid assuming PowerShell as the default scripting environment; clarify cross-platform support and provide parity in examples.
GitHub Create Pull Request
Container Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/managed-identity-image-pull.md ...articles/container-apps/managed-identity-image-pull.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 mentioned and demonstrated as a first-class option alongside Bash, and some steps (especially in the portal and Bicep sections) reference PowerShell and Windows-centric tooling before or equally with Linux alternatives. The documentation assumes users may be using PowerShell on Windows, and instructions for installing Bicep and Azure PowerShell are given more prominence than Linux-specific guidance. There are no explicit Linux-only examples or references to Linux-native tools (e.g., shell scripting, package managers), and the documentation does not mention WSL or Linux desktop environments. However, Azure CLI (Bash) examples are present, so Linux users are not excluded.
Recommendations
  • Add explicit references to Linux environments and workflows, such as Ubuntu, Fedora, or other distributions, and clarify that Azure CLI commands work natively on Linux.
  • Provide installation instructions for Azure CLI and Bicep using Linux package managers (apt, yum, etc.), not just generic links.
  • Include troubleshooting tips or notes for common Linux-specific issues (e.g., permissions, environment variables, file paths).
  • Mention that PowerShell Core is cross-platform, but clarify that Bash/CLI is the default on Linux.
  • Where PowerShell is referenced, clarify its use on Linux and macOS, or provide separate tabs for Linux and Windows users.
  • Consider adding a Linux-first example or workflow, especially in the portal and Bicep sections, to balance the presentation.
GitHub Create Pull Request
Container Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/metrics.md ...zure-docs/blob/main/articles/container-apps/metrics.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page references Azure PowerShell cmdlets alongside Azure CLI for retrieving metrics, but does not provide any Linux-specific examples or mention Linux tools. The order of mention places PowerShell (a Windows-centric tool) before CLI, and there are no Bash or Linux shell examples, nor any discussion of Linux-native monitoring tools or patterns.
Recommendations
  • Provide explicit Bash or Linux shell examples for metric retrieval using Azure CLI.
  • Mention Linux-native monitoring tools (e.g., curl, jq, or integration with Prometheus/Grafana) where appropriate.
  • Ensure that CLI examples are shown before or alongside PowerShell examples, emphasizing cross-platform parity.
  • Clarify that Azure CLI is cross-platform and provide installation/use instructions for Linux users.
  • Avoid implying PowerShell is the default or primary method, and balance documentation to include Linux workflows.
GitHub Create Pull Request
Container Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/how-to-use-private-endpoint.md ...articles/container-apps/how-to-use-private-endpoint.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a Windows bias in several ways: VM creation examples exclusively use Windows Server images, PowerShell is the only shell shown for connection verification, and there are no Linux VM or shell examples. The portal instructions and CLI commands default to Windows-centric patterns, and Windows tools (PowerShell, Windows Server) are mentioned without Linux equivalents.
Recommendations
  • Add parallel examples for creating and connecting to a Linux VM (e.g., Ubuntu) in both portal and CLI sections.
  • Provide shell commands for connection verification using Bash (e.g., nslookup, dig, curl) on Linux VMs.
  • Mention Linux images as options when creating VMs, and show how to select them in both portal and CLI instructions.
  • Balance PowerShell usage with Bash or other Linux shell examples throughout the documentation.
  • Explicitly state that both Windows and Linux VMs are supported and provide guidance for each.
GitHub Create Pull Request
Container Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/java-component-logs.md ...ob/main/articles/container-apps/java-component-logs.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page displays a Windows bias in several ways: PowerShell examples are provided alongside Bash, but the variable assignment uses 'SET' in Bash, which is a Windows CMD command and not valid in Linux Bash. There is no explicit Linux shell example (e.g., using 'export' or 'WORKSPACE_ID=...'), and the PowerShell examples are given equal prominence to Bash, despite Linux being the more common platform for container workloads. Additionally, Windows-centric patterns (like 'SET') appear before Linux equivalents, and there is no mention of Linux-specific tools or troubleshooting steps.
Recommendations
  • Replace 'SET $WORKSPACE_ID=<WORKSPACE_ID>' in Bash examples with 'export WORKSPACE_ID=<WORKSPACE_ID>' or 'WORKSPACE_ID=<WORKSPACE_ID>' to match Linux Bash syntax.
  • Clearly distinguish between Windows PowerShell, Windows CMD, and Linux Bash examples, and ensure Linux Bash examples use correct syntax.
  • Consider providing Linux-first examples, as container workloads are more commonly run on Linux.
  • Add troubleshooting notes or tips for Linux users, such as permissions or shell compatibility.
  • Review and update all CLI instructions to ensure they work natively on Linux systems.
GitHub Create Pull Request
Container Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/manage-secrets.md ...cs/blob/main/articles/container-apps/manage-secrets.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides examples for Azure Portal, ARM templates, Azure CLI, and PowerShell, but there is a notable emphasis on PowerShell, which is primarily a Windows tool. PowerShell examples are given equal prominence as Azure CLI, and in some cases, PowerShell is the only scripting example provided (e.g., secret definition and referencing). There are no explicit Linux shell (bash) examples, nor is there mention of Linux-specific tooling or patterns. Additionally, certain features (such as Key Vault secret references and secret volume mounts) are explicitly stated as unsupported in PowerShell, but there is no guidance for Linux users or alternatives for those scenarios.
Recommendations
  • Add explicit bash examples alongside Azure CLI commands to demonstrate usage in Linux environments.
  • Clarify that Azure CLI commands are cross-platform and provide sample shell environment variable usage (e.g., export, $VAR) for Linux.
  • Reduce reliance on PowerShell for scripting examples, or provide equivalent bash scripts for each PowerShell example.
  • Mention Linux-specific considerations (such as file permissions when mounting secrets as volumes) where relevant.
  • Where features are unsupported in PowerShell, provide alternative instructions for Linux users (e.g., using Azure CLI or ARM templates).
  • Include a note at the beginning of the documentation clarifying platform support and parity for all examples.
GitHub Create Pull Request
Container Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/microservices-dapr-azure-resource-manager.md ...iner-apps/microservices-dapr-azure-resource-manager.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 CLI commands, but PowerShell is given equal prominence to Bash, which may indicate a slight Windows bias. The use of PowerShell is emphasized throughout, and Windows tooling (PowerShell) is always presented alongside Bash, rather than focusing on cross-platform shell usage. There are no Linux-specific tools or patterns mentioned, and the Azure portal instructions use generic browser-based steps, which are platform-neutral. However, the inclusion of PowerShell in every example and its equal status to Bash may suggest a bias towards Windows users.
Recommendations
  • Consider prioritizing Bash examples, as Bash is available on both Linux and Windows (via WSL or Git Bash), while PowerShell is primarily a Windows tool.
  • Add explicit notes about cross-platform compatibility, e.g., clarify that Bash commands work on Linux, macOS, and Windows (with WSL/Git Bash), while PowerShell is mainly for Windows.
  • Include troubleshooting or environment setup steps for Linux users, such as verifying the Azure CLI installation on Ubuntu or Fedora.
  • If PowerShell is retained, clarify its intended audience (e.g., 'For Windows users, use PowerShell; for Linux/macOS, use Bash').
  • Highlight any differences or considerations for Linux users, such as file permissions or environment variable syntax.
GitHub Create Pull Request
Container Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/tutorial-code-to-cloud.md ...main/articles/container-apps/tutorial-code-to-cloud.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 throughout, including for Azure-specific tasks and Docker usage. Windows tools and patterns (such as PowerShell cmdlets and Docker Desktop for Windows) are mentioned explicitly, sometimes before or with more detail than their Linux equivalents. There is a slight tendency to present Windows/PowerShell options as primary or default, which may make the documentation feel more Windows-centric, especially for users on Linux.
Recommendations
  • Ensure parity by providing Bash examples for all steps, especially where PowerShell-specific cmdlets are used (e.g., resource creation, role assignments).
  • Explicitly mention Linux alternatives for Docker installation and usage, including common Linux distributions and package managers.
  • Where PowerShell is used for Azure resource management, provide equivalent Bash/Azure CLI scripts for Linux users.
  • Avoid language that implies Windows/PowerShell is the default or preferred platform; present Bash and PowerShell options with equal prominence.
  • Add troubleshooting tips or notes for common Linux issues (e.g., permissions, environment variables, Docker daemon setup).
  • Consider including a dedicated Linux section or tab for steps that differ significantly between platforms.
GitHub Create Pull Request
Container Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/tutorial-scaling.md .../blob/main/articles/container-apps/tutorial-scaling.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 all Azure CLI commands, ensuring cross-platform coverage. However, in the 'Send requests' section, the PowerShell example is significantly more complex and detailed than the Bash example, potentially favoring Windows users. The Bash example uses standard Linux utilities (seq, xargs, curl), while the PowerShell example uses advanced PowerShell constructs (RunspacePool, Invoke-WebRequest), which may not be as familiar to Linux users. Additionally, the PowerShell tab is always present, and the instructions sometimes refer to 'command prompt' (a Windows term) when describing how to access PowerShell. There are no explicit Linux-only examples or recommendations, and the Bash examples assume a Unix-like environment but do not mention macOS. No Windows-specific tools are mentioned, but the PowerShell examples are more elaborate and may be perceived as the primary or preferred method for some steps.
Recommendations
  • Provide equivalent Bash examples for advanced scenarios, such as sending concurrent requests, using tools like GNU Parallel or background jobs to match the PowerShell example's concurrency.
  • Clarify that Bash examples work on Linux and macOS, and mention how to install required tools if missing.
  • Avoid referring to 'command prompt' when describing PowerShell usage; use 'PowerShell terminal' or clarify for cross-platform users.
  • Consider adding a note about using WSL (Windows Subsystem for Linux) for Bash commands on Windows.
  • Ensure that both Bash and PowerShell examples are equally detailed and capable, especially for concurrency and automation tasks.
GitHub Create Pull Request
Container Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/troubleshooting.md ...s/blob/main/articles/container-apps/troubleshooting.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 a moderate Windows bias. Windows tools and patterns are referenced before or instead of Linux equivalents, such as mentioning 'elevated command prompt' and Docker on Windows, and providing explicit PowerShell examples. Linux-specific instructions and examples are either missing or only provided as Azure CLI commands, with little mention of Linux environments or shell usage. The troubleshooting steps and examples often assume a Windows context, and PowerShell is given parity with Bash, but not with other Linux shells.
Recommendations
  • Include explicit instructions for Linux users, such as running Docker commands in a Linux terminal and verifying Docker Engine on Linux.
  • When referencing command prompts, mention both Windows Command Prompt/PowerShell and Linux terminal/bash.
  • Provide Linux-specific troubleshooting steps where applicable (e.g., checking Docker installation, permissions, and environment variables on Linux).
  • Ensure examples are not Windows-centric; for instance, avoid phrases like 'elevated command prompt' without also mentioning 'sudo' for Linux.
  • Balance PowerShell and Bash examples, and consider including zsh/fish if relevant.
  • Reference Docker Desktop for both Windows and Linux, or clarify platform-specific instructions.
  • Add notes or callouts for platform differences in networking, file paths, and environment setup.
GitHub Create Pull Request
Container Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/vnet-custom.md ...-docs/blob/main/articles/container-apps/vnet-custom.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides both Bash (Azure CLI) and PowerShell examples for most commands, but PowerShell examples are consistently present and sometimes more detailed, reflecting a Windows-centric approach. PowerShell is given parity with Bash, but the presence of PowerShell throughout, including resource creation, querying, and cleanup, indicates a bias toward Windows users. Additionally, Windows-specific tools (PowerShell cmdlets) are used extensively, and in some cases, PowerShell examples are more verbose or detailed than their Bash equivalents. There is no mention of Linux-specific patterns, troubleshooting, or alternative tools (e.g., native Linux networking commands).
Recommendations
  • Ensure Bash/Azure CLI examples are as detailed as PowerShell examples, especially for complex resource creation steps.
  • Add explicit notes or sections for Linux users, including troubleshooting tips for common Linux issues (e.g., permissions, environment variables).
  • Consider including examples using native Linux tools (such as ip, netplan, or nmcli) where relevant, especially for networking concepts.
  • Review the order of examples to avoid always listing PowerShell first or giving it more prominence.
  • Where possible, provide cross-platform guidance (e.g., how to run Azure CLI on Windows, macOS, and Linux) and clarify that Bash examples work on all platforms with Azure CLI installed.
  • Include a brief comparison table of Bash vs. PowerShell commands for quick reference.
GitHub Create Pull Request
Container Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/code-to-cloud-options.md .../main/articles/container-apps/code-to-cloud-options.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 no mention of Linux-native editors or workflows. The CLI section references PowerShell before Bash, and there are no explicit Linux or macOS examples or resources. The overall structure and resource links favor Windows development environments and tools, with little to no guidance for Linux users.
Recommendations
  • Include examples and workflows using Linux-native editors such as Vim, Emacs, or JetBrains IDEs.
  • Provide explicit Bash and Linux terminal examples alongside or before PowerShell examples.
  • Add resource links and tutorials for deploying from Linux/macOS environments.
  • Mention cross-platform compatibility and provide guidance for users on non-Windows operating systems.
  • Balance references to Windows tools (Visual Studio, PowerShell) with Linux alternatives (VS Code on Linux, Bash, etc.).
GitHub Create Pull Request
Container Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/how-to-use-private-endpoint.md ...articles/container-apps/how-to-use-private-endpoint.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits Windows bias in several ways: VM creation examples exclusively use Windows Server images, and all instructions for connecting to the VM and testing the private endpoint use Windows-specific tools (PowerShell, Windows Server). There are no examples or instructions for creating or using a Linux VM, nor for verifying connectivity using Linux-native tools (e.g., curl, dig, nslookup in bash). The portal instructions and CLI commands default to Windows, with no mention of Linux alternatives.
Recommendations
  • Add parallel instructions and examples for creating a Linux VM (e.g., Ubuntu) in both portal and CLI sections.
  • Provide Linux-native commands for verifying DNS and connectivity (e.g., using bash with nslookup, dig, curl, wget).
  • When listing VM image options, mention both Windows and popular Linux distributions, or show how to select either.
  • Include screenshots or command outputs from Linux environments where appropriate.
  • Explicitly state that the private endpoint can be tested from either Windows or Linux VMs, and provide guidance for both.
GitHub Create Pull Request
Container Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/environment-variables.md .../main/articles/container-apps/environment-variables.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 object creation and usage instructions, while the CLI section is more concise. PowerShell (a Windows-centric tool) is given equal prominence as Azure CLI, and its examples are more verbose and elaborate. There is no mention of Linux-specific tools, shell patterns, or scripting approaches (e.g., Bash, zsh), nor are there examples tailored for Linux users. The documentation assumes familiarity with PowerShell objects and cmdlets, which may be less accessible to Linux users.
Recommendations
  • Add Linux/Bash-specific examples for setting and updating environment variables, such as using Bash scripts or environment variable files.
  • Clarify that Azure CLI is cross-platform and provide shell-specific usage notes (e.g., quoting, escaping) for Bash/zsh.
  • Reduce PowerShell example verbosity or provide equally detailed CLI/Bash examples to ensure parity.
  • Mention that PowerShell is primarily a Windows tool and suggest alternatives for Linux users.
  • Include troubleshooting tips or common patterns for Linux environments, such as exporting environment variables or using .env files.
GitHub Create Pull Request
Container Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/managed-identity.md .../blob/main/articles/container-apps/managed-identity.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides a PowerShell example for retrieving tokens from the managed identity endpoint, but does not offer an equivalent example using Bash, curl, or other common Linux tools. This may disadvantage Linux users, as PowerShell is primarily a Windows tool and not universally available on Linux systems. The lack of Linux-native command-line examples (e.g., using curl or wget) is a notable gap, especially given the prevalence of Linux containers and development environments in cloud-native scenarios.
Recommendations
  • Add Linux-native examples for retrieving tokens, such as using curl or wget in Bash.
  • Ensure that command-line examples are provided for both Windows (PowerShell) and Linux (Bash/curl) environments, especially in sections where direct HTTP requests are shown.
  • Explicitly mention cross-platform compatibility for CLI commands and clarify any OS-specific requirements.
  • Review other sections for implicit Windows-first patterns and ensure parity in tool recommendations and examples.
GitHub Create Pull Request
Container Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/manage-secrets.md ...cs/blob/main/articles/container-apps/manage-secrets.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 bias toward Windows and PowerShell environments. PowerShell examples are provided for most operations, while Linux-specific shell examples (such as Bash) are absent. The CLI examples are generic but do not address Linux-specific considerations (e.g., environment variable syntax, quoting, file permissions). Windows/PowerShell tools and patterns are mentioned or supported exclusively in some cases (e.g., secret Key Vault references and secret volume mounts are not supported in PowerShell, but no Linux shell alternatives are discussed). The ordering of examples often places PowerShell before or alongside CLI, but never includes Linux shell scripting. There is no mention of Linux-specific tools, patterns, or troubleshooting.
Recommendations
  • Add explicit Bash/Linux shell examples alongside Azure CLI and PowerShell, showing environment variable usage, quoting, and file access patterns.
  • Clarify cross-platform differences in CLI usage, such as environment variable expansion, quoting, and file permissions when mounting secrets as volumes.
  • Include troubleshooting or notes for Linux users, such as file system permissions and shell compatibility when accessing secrets.
  • If PowerShell features are unsupported (e.g., secret Key Vault references, volume mounts), provide Linux shell alternatives or workarounds.
  • Reorder examples to present CLI/Bash first, or provide parallel examples for both Windows (PowerShell) and Linux (Bash).
  • Mention Linux tools or patterns (e.g., using cat, grep, chmod) when demonstrating how to access secrets mounted as files.
GitHub Create Pull Request
Container Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/metrics.md ...zure-docs/blob/main/articles/container-apps/metrics.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page references Azure PowerShell cmdlets alongside Azure CLI for retrieving metrics, but does not provide any Linux-specific examples or mention Linux tools. The order of mention places PowerShell (a Windows-centric tool) before any Linux alternatives, and no Bash or Linux shell examples are given. This may create the impression that Windows tools are primary or preferred for monitoring Azure Container Apps metrics.
Recommendations
  • Include explicit Bash/Linux shell examples for retrieving metrics using Azure CLI.
  • Mention that Azure CLI is cross-platform and works natively on Linux, macOS, and Windows.
  • If referencing PowerShell, clarify that PowerShell Core is available on Linux, or provide equivalent Bash commands.
  • Add a section or examples showing how to automate metric retrieval and visualization on Linux systems.
  • Ensure that any tool or command mentioned is accompanied by its cross-platform availability and usage notes.
GitHub Create Pull Request
Container Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/managed-identity-image-pull.md ...articles/container-apps/managed-identity-image-pull.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides parity between Bash (Linux/macOS) and PowerShell (Windows) for most CLI-based instructions, but there is a noticeable Windows bias. PowerShell examples and instructions are given equal or sometimes greater prominence than Bash, and Windows-specific tools (PowerShell, Az.App module) are referenced frequently. In some cases, PowerShell instructions are more detailed (e.g., Log Analytics workspace setup), and prerequisites repeatedly mention installing Azure PowerShell. The documentation does not reference Linux-specific tools or patterns beyond Bash, and Windows-centric terminology (PowerShell, modules) appears before or alongside Bash. There are no explicit Linux-only examples or troubleshooting notes.
Recommendations
  • Ensure Bash instructions are always presented first, especially in mixed Bash/PowerShell tabs.
  • Add explicit Linux troubleshooting notes or references for common issues (e.g., permissions, shell differences).
  • Reference Linux-native tools or patterns where relevant (e.g., systemd, cron for automation, package managers for installation).
  • Clarify that Bash instructions are suitable for Linux/macOS and PowerShell for Windows, to avoid confusion.
  • Where PowerShell modules are required, note equivalent Bash/CLI alternatives and highlight cross-platform compatibility.
  • Consider adding a dedicated Linux section for advanced scenarios or common platform-specific issues.
GitHub Create Pull Request
Container Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/tutorial-code-to-cloud.md ...main/articles/container-apps/tutorial-code-to-cloud.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 given equal or greater prominence throughout, including custom PowerShell cmdlets for Azure operations. There are several places where Windows-specific tools (PowerShell, Docker Desktop for Windows) are mentioned, and PowerShell examples are often more detailed or complex than Bash. The documentation does not provide Linux shell alternatives for PowerShell-specific Azure cmdlets, and Docker Desktop is referenced as the default for local builds, which is more common on Windows/macOS than Linux. There is no explicit mention of Linux-native tools or patterns (e.g., Podman, native Docker engine on Linux, or Linux-specific troubleshooting).
Recommendations
  • For every PowerShell example, ensure there is a Bash (or POSIX shell) equivalent, especially for Azure operations that use custom PowerShell cmdlets (e.g., New-AzContainerApp).
  • Mention and provide instructions for using native Docker engine on Linux, not just Docker Desktop.
  • Where PowerShell-specific Azure cmdlets are used, note that these are Windows-centric and provide Azure CLI alternatives for Linux users.
  • Avoid assuming Docker Desktop is the default on Linux; clarify that Linux users can install Docker engine directly.
  • Add troubleshooting and environment setup notes for Linux users (e.g., permissions, systemd, networking).
  • Consider including a Linux-first section or callout to ensure parity and visibility for Linux workflows.
GitHub Create Pull Request
Container Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/revisions-manage.md .../blob/main/articles/container-apps/revisions-manage.md
High Priority View Details →
Scanned: 2026-01-08 00:53
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 each command, with PowerShell examples using the Az PowerShell module. PowerShell is a Windows-centric shell, and its inclusion throughout the document signals a bias toward Windows users. In several sections, PowerShell examples are presented immediately after Bash, sometimes with more detailed object usage, reinforcing Windows-first patterns. There are no Linux-specific shell examples beyond Bash, and no mention of Linux-native tools or scripting patterns. The documentation does not acknowledge that PowerShell is available cross-platform, nor does it provide parity for other Linux shells (e.g., zsh, fish) or scripting environments.
Recommendations
  • Clarify that PowerShell is available cross-platform, but Bash is the default shell on most Linux distributions.
  • Add notes or examples for other popular Linux shells (e.g., zsh, fish) if relevant, or explicitly state that Bash examples are applicable to most Linux environments.
  • Consider providing examples using native Linux scripting patterns (e.g., using environment variables, piping, jq for JSON parsing) where appropriate.
  • Ensure that Bash examples are as detailed and feature-rich as PowerShell examples, especially where PowerShell uses objects or advanced parameter passing.
  • Add a section explaining the parity between Azure CLI usage on Windows, Linux, and macOS, and clarify any platform-specific caveats.
  • Avoid implying that PowerShell is the primary or preferred automation tool for Azure unless justified by usage statistics.
GitHub Create Pull Request
Container Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/vnet-custom.md ...-docs/blob/main/articles/container-apps/vnet-custom.md
High Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides both Bash (Azure CLI) and PowerShell examples throughout, but PowerShell is given equal prominence and detail, which may indicate a Windows bias. PowerShell is a Windows-centric tool, and its inclusion alongside Bash in every example can be interpreted as catering to Windows users. Additionally, the use of Windows-specific tools (PowerShell cmdlets) and terminology (e.g., `$true/$false` for booleans) reinforces the Windows-first approach. There is no explicit Linux bias or missing Linux examples, but the parity between Bash and PowerShell may unintentionally prioritize Windows users, especially since PowerShell is less commonly used on Linux.
Recommendations
  • Clarify that Bash examples are suitable for both Linux and macOS, and that PowerShell examples are primarily for Windows users.
  • Consider making Bash/Azure CLI the default or first example, with PowerShell as an alternative, to reflect the broader cross-platform usage of Bash.
  • Add explicit notes or guidance for Linux/macOS users, such as environment setup or differences in command syntax/output.
  • Where possible, use generic CLI commands (az) rather than platform-specific scripting (PowerShell), unless a feature is only available in PowerShell.
  • Review terminology and variable usage to ensure cross-platform clarity (e.g., avoid `$true/$false` in CLI examples).
GitHub Create Pull Request
← Previous Page 2 of 8 Next →