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 51-75 of 198 flagged pages
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits Windows bias in several ways: Windows tools and terminology (elevated command prompt, Docker on Windows) are mentioned explicitly, and PowerShell examples are provided alongside Bash, but no Linux-specific troubleshooting advice or references are given. The order of presentation and language often assumes Windows as the default environment, with Linux alternatives missing or relegated to secondary status.
Recommendations
- Add explicit Linux troubleshooting steps and references (e.g., mention running Docker commands in Linux terminals, provide links to Docker on Linux installation).
- When referencing command prompts, clarify instructions for both Windows (Command Prompt/PowerShell) and Linux (Terminal/Bash).
- Ensure that examples and tool references (such as Docker) include Linux-specific notes, such as permissions, common issues, and links to Linux documentation.
- Present Bash and PowerShell examples in parallel, and avoid giving precedence to Windows tools or terminology.
- Review all steps for Azure CLI and ensure parity in instructions for both Windows and Linux environments, including environment-specific caveats.
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 →
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 (Visual Studio, Visual Studio Code) and workflows, mentioning PowerShell before Bash, and focusing on Windows development environments. There is a lack of explicit Linux or cross-platform examples, and the documentation does not provide parity for Linux users in terms of tooling or workflow guidance.
Recommendations
- Include explicit Linux and macOS examples and workflows alongside Windows ones, especially in sections discussing code editors and CLI usage.
- When mentioning scripting or automation, present Bash and PowerShell examples side by side, or clarify that both are supported.
- Highlight cross-platform tools (e.g., Docker CLI, VS Code) and provide guidance for users on Linux and macOS.
- Add references to popular Linux editors (e.g., Vim, Emacs, JetBrains IDEs) or at least acknowledge their use.
- Ensure that all resource links and tutorials are accessible and relevant for Linux users, not just Windows/Visual Studio users.
- Avoid listing Windows tools or patterns first unless there is a clear reason; alternate the order or group by platform.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides both Bash and PowerShell examples for querying logs, but the Bash examples use the non-standard 'SET' command for variable assignment, which is a Windows CMD syntax, not valid in Bash or Linux shells. This may confuse Linux users. Additionally, PowerShell examples are always present, and sometimes appear before or alongside Bash, indicating a slight Windows-first approach. There are no Linux-specific instructions or troubleshooting tips, and the CLI examples do not use standard Linux shell conventions.
Recommendations
- Replace 'SET $WORKSPACE_ID=<WORKSPACE_ID>' in Bash examples with the correct Bash syntax: 'WORKSPACE_ID=<WORKSPACE_ID>'.
- Ensure Bash/Linux examples use standard shell conventions and are tested in a Linux environment.
- Consider placing Bash/Linux examples before PowerShell to reflect the prevalence of Linux in containerized/cloud environments.
- Add Linux-specific notes or troubleshooting tips where relevant.
- Clarify which examples are for Windows CMD, PowerShell, or Bash, and avoid cross-polluting syntax.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation shows a moderate Windows bias. Portal-based troubleshooting steps are described in a way that assumes familiarity with the Azure Portal UI, which is platform-agnostic but often more familiar to Windows users. In the 'Verify accessibility of container image' section, the only explicit OS-specific note is for Docker on Windows, with no mention of Linux or macOS Docker usage. In the 'Verify latest version of Azure Container Apps extension is installed' section, both Bash (Azure CLI) and PowerShell examples are provided, but PowerShell is given a dedicated tab and more detailed instructions, including module installation and update commands. There are no Linux-specific troubleshooting tools, commands, or notes, and no mention of running commands in a Linux shell or terminal. The only command-line example that could be OS-specific (docker run) is shown in a generic way, but the supporting text references 'elevated command prompt' and Docker on Windows, with no equivalent Linux/macOS instructions.
Recommendations
- When referencing Docker, include instructions or notes for both Windows and Linux/macOS users (e.g., mention 'open a terminal or command prompt' and provide links to Docker installation for all platforms).
- Where 'elevated command prompt' is mentioned, add Linux/macOS equivalents (e.g., 'use sudo if necessary').
- In sections with PowerShell examples, ensure Bash/Azure CLI examples are equally prominent and detailed.
- If referencing OS-specific issues (like Docker Desktop on Windows), add parallel notes for Linux/macOS (e.g., checking Docker daemon status on Linux).
- Consider including troubleshooting steps or examples that are specific to Linux environments, such as checking system logs or network configuration using Linux tools.
- Review the ordering of examples and avoid always listing Windows/PowerShell first; alternate or present Bash/Azure CLI first where appropriate.
Container Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/java-containers-intro.md
.../main/articles/container-apps/java-containers-intro.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by recommending Docker Desktop (which is primarily for Windows and macOS) as the default Docker installation method, and by not mentioning Linux installation or tools explicitly. Visual Studio Code is presented as the primary editor, with no mention of Linux-native editors or workflows. There are no Linux-specific installation instructions or troubleshooting steps, and the document assumes the reader is using tools and patterns most common on Windows or macOS. No Linux package manager commands or Linux-specific Docker installation guidance is provided.
Recommendations
- Add explicit instructions for installing Docker Engine on Linux distributions (e.g., Ubuntu, Fedora), including package manager commands.
- Mention Linux-native editors (such as Vim, Emacs, or JetBrains IDEs) as alternatives to Visual Studio Code, or clarify that VS Code is cross-platform.
- Include verification steps and troubleshooting commands that are relevant to Linux environments (e.g., using systemctl to check Docker service status).
- When referencing Docker Desktop, clarify that on Linux, Docker Engine is installed directly and Docker Compose may need to be installed separately.
- Provide example shell commands that work on Linux (e.g., using sudo where appropriate, or noting differences in file paths and permissions).
- Ensure that all tool recommendations and workflows are presented in a cross-platform manner, or provide parallel instructions for Linux users.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a bias toward Windows and PowerShell by consistently providing PowerShell examples alongside Azure CLI, ARM, and portal instructions, even when PowerShell support is incomplete or missing for certain features (e.g., Key Vault references, secret volume mounts). There is no mention or example of Linux-specific tools, shell scripting, or cross-platform command-line usage (e.g., Bash), and PowerShell is presented as a primary automation method. The documentation does not address or acknowledge Linux shell environments, nor does it provide parity for Linux users in terms of scripting or automation guidance.
Recommendations
- Add explicit Bash/Linux shell examples for all CLI instructions, demonstrating usage in a typical Linux terminal environment.
- Clarify that Azure CLI commands are cross-platform and can be run in Bash, PowerShell, or other shells, and provide sample commands for both Bash and PowerShell where relevant.
- When PowerShell support is missing for a feature (e.g., Key Vault references, secret volume mounts), provide alternative Linux scripting or CLI-based workflows.
- Avoid presenting PowerShell as the default or primary scripting language; instead, offer both PowerShell and Bash examples, or clearly indicate when an example is Windows-specific.
- Include notes or sections addressing Linux/macOS users, such as environment variable syntax differences, file path conventions, and shell scripting best practices.
- Where possible, provide downloadable sample scripts for both PowerShell and Bash to ensure parity and accessibility for users on all platforms.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation references both Azure CLI and Azure PowerShell for retrieving metrics, but PowerShell is mentioned alongside CLI without providing any Linux-specific examples or guidance. There are no Linux shell (bash) or cross-platform command-line examples, and the only explicit command-line tooling mentioned is PowerShell, which is Windows-centric. This may make Linux users feel secondary or unsupported.
Recommendations
- Provide explicit bash/Linux shell examples for retrieving metrics using Azure CLI, demonstrating parity with PowerShell.
- When referencing command-line tools, list Azure CLI (which is cross-platform) before PowerShell, and clarify that PowerShell is optional or for Windows users.
- Include notes or sections highlighting that all Azure CLI commands work on Linux, macOS, and Windows.
- Avoid implying PowerShell is the default or primary method unless there is a clear technical reason.
- Add screenshots or terminal snippets from Linux environments where relevant.
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 →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation includes a dedicated PowerShell example for retrieving tokens from the managed identity endpoint, but does not provide equivalent Linux shell (bash/curl) examples. The PowerShell example uses Windows-specific tools (Invoke-RestMethod, PowerShell environment variable syntax), and there is no mention of Linux or cross-platform command-line alternatives. This may make it less accessible for Linux users or those working in non-Windows environments.
Recommendations
- For every PowerShell example, provide an equivalent bash/curl example for Linux/macOS users.
- Explicitly mention that Azure CLI and HTTP GET examples are cross-platform, and clarify any OS-specific considerations.
- Avoid using only Windows-specific tools (like PowerShell) in code samples; always provide parity with common Linux tools.
- Where environment variables are referenced, show both Windows (e.g., $env:VAR) and Linux (e.g., $VAR) syntax.
- Consider adding a section or tab for 'Bash' or 'Linux shell' alongside 'PowerShell' in code sample tabsets.
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 →
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 (Visual Studio, Visual Studio Code) and workflows, referencing PowerShell before Bash, and omitting explicit Linux or cross-platform examples. The focus on Visual Studio (a Windows-first IDE) and lack of Linux-specific guidance or screenshots further reinforce this bias. While Azure CLI and AZD are cross-platform, the documentation does not provide parity in Linux-specific instructions or highlight Linux-native development environments.
Recommendations
- Include explicit Linux examples and workflows, such as using VS Code on Linux, or developing/deploying from a Linux terminal.
- Provide Bash-first or Bash-equal examples alongside PowerShell, especially in CLI automation contexts.
- Mention Linux-native editors (e.g., Vim, Emacs, JetBrains IDEs) as alternatives to Visual Studio.
- Add screenshots or walkthroughs from Linux environments where possible.
- Clarify that Azure CLI and AZD are cross-platform, and provide installation or usage notes for Linux users.
- Balance the order of tool presentation (e.g., mention Bash before or alongside PowerShell).
Container Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/deploy-visual-studio.md
...b/main/articles/container-apps/deploy-visual-studio.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily oriented towards Windows users by focusing exclusively on Visual Studio, a Windows-centric IDE, for all steps including project creation, deployment, and resource management. There are no examples or instructions for performing these tasks using cross-platform tools or on Linux/macOS. The workflow assumes the use of Visual Studio GUI and does not mention alternatives such as the Azure CLI, Docker CLI, or VS Code, which are more commonly used on Linux. While the Docker container is set to Linux, the development and deployment process is entirely Windows/Visual Studio-centric.
Recommendations
- Add parallel instructions for deploying to Azure Container Apps using cross-platform tools such as the Azure CLI, Docker CLI, and VS Code.
- Provide command-line examples for project creation, Docker image building, and deployment that work on Linux and macOS.
- Include a section or links for Linux/macOS users who may not have access to Visual Studio, outlining equivalent workflows.
- Mention and demonstrate how to use GitHub Actions or Azure DevOps pipelines for CI/CD from non-Windows environments.
- Clarify in the prerequisites that the tutorial is Visual Studio-specific and provide references to cross-platform alternatives.
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 →
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, but the PowerShell section is significantly more detailed and complex, reflecting a Windows-centric approach. PowerShell (a Windows-native tool) is given equal prominence to Azure CLI, and the PowerShell workflow is described in much greater depth, including object creation and manipulation, which may be unfamiliar or irrelevant to Linux/macOS users. There is no mention of Linux-specific tools, shell scripting, or considerations for non-Windows environments, and the documentation does not clarify that Azure CLI is cross-platform while PowerShell examples are primarily for Windows users.
Recommendations
- Clarify that Azure CLI is cross-platform and suitable for Linux/macOS/Windows, while PowerShell is primarily for Windows users (or for those who have installed PowerShell Core on other platforms).
- Provide Bash shell scripting examples alongside PowerShell, especially for common automation scenarios, to ensure Linux users have parity.
- Reduce the depth and complexity of the PowerShell section unless there is a specific Windows-only feature being demonstrated. Instead, focus on Azure CLI as the primary, platform-neutral interface.
- Explicitly state in each section which platforms the instructions are intended for, and recommend Azure CLI for Linux/macOS users.
- If PowerShell is included, also mention PowerShell Core and its cross-platform capabilities, but do not assume all users have it installed.
- Consider adding a table or quick-start guide comparing Azure CLI and PowerShell usage for common tasks, with notes on platform compatibility.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a Windows bias in several ways: When creating a VM for testing, the only OS option shown is Windows Server 2022, and the CLI example uses the Win2022Datacenter image. The instructions for verifying connectivity exclusively use PowerShell commands inside the Windows VM, with no mention of Linux alternatives (e.g., using nslookup or dig on a Linux VM). There are no examples or guidance for deploying or testing with a Linux VM, nor are Linux command-line tools or shell examples provided for the verification steps. The portal instructions also default to Windows images and workflows.
Recommendations
- Provide parallel instructions for creating a Linux VM (e.g., Ubuntu) in both portal and CLI sections, including appropriate image references (e.g., UbuntuLTS).
- Include Linux command-line examples for verifying DNS resolution and connectivity (e.g., using nslookup or dig in bash).
- When presenting a list of OS options or tools, avoid defaulting to Windows first; present both Windows and Linux options, or alternate their order.
- Instruct users on how to run equivalent commands in both PowerShell (Windows) and bash (Linux), especially for common tasks like DNS lookups.
- Clarify that the private endpoint functionality is OS-agnostic and works with both Windows and Linux VMs.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides both Bash and PowerShell examples for querying logs, but there are several signs of Windows bias: PowerShell examples are always present and sometimes appear before Bash, the Bash examples use 'SET' (a Windows command) instead of 'export' for environment variables, and there is no mention of Linux-specific tools or patterns. Additionally, there are no explicit Linux/macOS instructions or troubleshooting tips, and the CLI sections do not clarify cross-platform differences.
Recommendations
- Replace 'SET' with 'export' in Bash examples to align with standard Linux/macOS shell usage.
- Ensure Bash (Linux/macOS) examples are listed before PowerShell (Windows) examples to avoid Windows-first bias.
- Add explicit notes or troubleshooting tips for Linux/macOS users where command syntax or behavior may differ.
- Include references to Linux/macOS terminal environments and tools where appropriate.
- Audit all CLI examples for platform-appropriate syntax and clarify any differences in environment variable usage or command output.
Container Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/java-containers-intro.md
.../main/articles/container-apps/java-containers-intro.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias by recommending Docker Desktop (which is primarily for Windows and macOS) as the default Docker installation method, and by not mentioning native Linux Docker installation or Linux-specific development workflows. Visual Studio Code is presented as the primary editor, with no mention of alternative editors or command-line workflows common on Linux. There are no Linux-specific troubleshooting or setup instructions, and the documentation omits guidance for users developing on native Linux environments.
Recommendations
- Include instructions for installing Docker Engine natively on Linux distributions (e.g., Ubuntu, Fedora), not just Docker Desktop.
- Mention alternative editors and workflows commonly used on Linux, such as JetBrains IDEs, Eclipse, or command-line tools.
- Provide Linux-specific troubleshooting tips (e.g., using systemd to manage Docker, checking permissions for the docker group).
- When listing tools, avoid phrasing that implies Docker Desktop is required for all platforms; clarify that Linux users should install Docker Engine.
- Add explicit Linux shell command examples where relevant (e.g., using apt or yum for installation, using systemctl to manage Docker).
- Ensure parity in examples and instructions for both Windows and Linux environments, especially in setup and debugging sections.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Portal-based troubleshooting steps are described using generic UI instructions, but when command-line examples are given, PowerShell and Windows-specific tools are often mentioned or prioritized. For example, the section on verifying container image accessibility refers to running Docker in an 'elevated command prompt' and specifically calls out 'Docker on Windows', without mentioning Linux or macOS equivalents. When discussing Azure CLI and PowerShell, the PowerShell module is given its own tab and update instructions, but there is no equivalent for Linux shell environments beyond a single Bash example. There are no explicit Linux/macOS troubleshooting notes or examples, and Windows terminology (e.g., 'elevated command prompt') is used exclusively.
Recommendations
- Wherever 'elevated command prompt' or 'Docker on Windows' is mentioned, add equivalent instructions for Linux (e.g., 'open a terminal and run with sudo if needed') and macOS.
- When referencing Docker, clarify that the command works on all platforms and provide links to Docker installation instructions for Linux and macOS, not just Windows.
- For Azure CLI and PowerShell instructions, ensure parity by providing Bash/zsh examples and update instructions for Linux/macOS environments, not just PowerShell.
- Avoid Windows-specific terminology (like 'elevated command prompt') or always pair it with cross-platform equivalents.
- Explicitly state that all CLI commands are cross-platform unless otherwise noted, and provide troubleshooting notes for common Linux/macOS issues where relevant.
Container Apps
Code to cloud options in Azure Container Apps
.../main/articles/container-apps/code-to-cloud-options.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a moderate 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. Windows tools are mentioned first, and PowerShell is referenced before Bash in the CLI section. There is a lack of explicit Linux/macOS examples or parity in tooling recommendations, which may create friction for non-Windows users.
Recommendations
- Include explicit examples and workflows for Linux/macOS users, such as using VS Code on Linux, or alternative editors.
- Provide Bash-first or Bash-equal automation examples alongside PowerShell in CLI sections.
- Mention cross-platform alternatives to Visual Studio, or clarify when Visual Studio Code is suitable for Linux/macOS.
- Add resource links and tutorials for deploying from Linux/macOS environments.
- Ensure that references to local development and deployment do not assume a Windows environment.
Container Apps
Observability of managed Java components in Azure Container Apps
...ob/main/articles/container-apps/java-component-logs.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for querying logs via Azure CLI, but PowerShell examples are consistently shown after Bash. However, there is a subtle Windows bias: the Bash examples use 'SET' (a Windows command) instead of 'export' for environment variables, which is not standard on Linux/macOS. Additionally, PowerShell examples are present throughout, which is helpful for Windows users but may suggest a slight prioritization of Windows tooling.
Recommendations
- Replace 'SET' with 'export' in Bash examples to ensure compatibility with Linux/macOS shells.
- Clarify which commands are for Windows CMD, PowerShell, or Bash, and provide accurate examples for each.
- Consider providing Linux/macOS-specific notes or troubleshooting tips where differences may arise.
- Ensure that examples for Linux/macOS are tested and clearly labeled.
Container Apps
Tutorial: Enable Azure Container Apps on Azure Arc-enabled Kubernetes
...in/articles/container-apps/azure-arc-enable-cluster.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides both Azure CLI (bash) and PowerShell examples for every step, but PowerShell is given equal prominence as Azure CLI, which is atypical for Linux/macOS users. There are no explicit Linux/macOS-specific instructions, and PowerShell is not natively available on most Linux/macOS systems. Some environment variable handling and command syntax (e.g., use of `$VAR` vs. `$VAR=...`) may be confusing for non-Windows users. There are no examples for Linux-specific shell environments beyond bash, nor any mention of macOS.
Recommendations
- Clearly state that Azure CLI examples are intended for bash on Linux/macOS and Windows, while PowerShell is primarily for Windows users.
- List Azure CLI (bash) examples first, as this is the default on Linux/macOS.
- Remove or de-emphasize PowerShell examples unless there is a specific Windows-only step.
- Add explicit notes or sections for Linux/macOS users, including any OS-specific prerequisites or troubleshooting steps.
- Ensure environment variable usage and command syntax are correct and clear for bash users (e.g., avoid mixing PowerShell variable assignment in bash sections).
- Mention that PowerShell Core is available on Linux/macOS if PowerShell examples are retained, but clarify that bash is preferred.
Container Apps
Tutorial: Communication between microservices in Azure Container Apps
...es/container-apps/communicate-between-microservices.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for all commands, but PowerShell is given equal prominence and, in some sections (notably the 'Deploy front end application'), PowerShell instructions are much more detailed and complex than the Bash equivalents. There is a slight Windows-first bias in the depth and explanation of PowerShell workflows, which may make Linux/macOS users feel underserved, especially when advanced configuration is required.
Recommendations
- Ensure Bash and PowerShell examples are equally detailed, especially for complex deployment steps.
- Provide advanced Bash (Linux/macOS) workflows for multi-step deployments, not just single-line az CLI commands.
- Consider adding a note clarifying that Bash examples are suitable for Linux/macOS and WSL users, and PowerShell for Windows.
- Where PowerShell uses custom objects and templates, provide equivalent Bash/az CLI scripting (e.g., using JSON files or environment variables).
- Review the order and prominence of examples to avoid implicit prioritization of Windows/PowerShell.
Container Apps
Use a private endpoint with an Azure Container Apps environment
...articles/container-apps/how-to-use-private-endpoint.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a notable Windows bias in several areas. VM creation examples exclusively use Windows Server images, and connection verification is performed using PowerShell commands within a Windows VM. There are no Linux VM creation examples, nor are there instructions for verifying connectivity using Linux tools (e.g., nslookup, dig, curl). Windows tools and workflows are mentioned exclusively, and Windows is presented as the default/first option for critical steps.
Recommendations
- Provide parallel Linux VM creation instructions (e.g., using Ubuntu or other common distributions) alongside Windows examples.
- Include Linux command-line equivalents for connection verification (e.g., nslookup, dig, curl, wget) and browser access.
- Explicitly mention that either Windows or Linux VMs can be used for testing, and clarify any OS-specific requirements.
- Avoid presenting Windows as the default or only option; offer both platforms equally in examples and screenshots.
Container Apps
Manage environment variables on Azure Container Apps
.../main/articles/container-apps/environment-variables.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides detailed PowerShell instructions and references to Windows-specific cmdlets and object models, with extensive step-by-step examples. While Azure CLI examples are present (which are cross-platform), the PowerShell sections are more verbose and detailed, and the documentation references Windows-centric tooling (PowerShell, .NET object models) without equivalent coverage for Linux/macOS shell scripting or automation. PowerShell is presented as a first-class option alongside CLI and Portal, but there is no mention of Bash, shell scripting, or Linux-native patterns. The order of sections sometimes puts PowerShell before Linux-native alternatives.
Recommendations
- Add Bash or shell scripting examples for Linux/macOS users, especially for tasks involving environment variable manipulation.
- Provide parity in detail for CLI instructions, matching the step-by-step guidance given for PowerShell.
- Explicitly mention that Azure CLI commands work on Linux/macOS and provide troubleshooting tips for those platforms.
- Consider adding a 'Linux/macOS' tab or section for users who do not use PowerShell.
- Avoid referencing .NET object models and PowerShell-specific constructs unless cross-platform alternatives are also described.
Container Apps
Azure Container Apps image pull from Azure Container Registry with managed identity
...articles/container-apps/managed-identity-image-pull.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides both Bash/Azure CLI and PowerShell examples for all command-line scenarios, but PowerShell is given equal or greater prominence, with detailed PowerShell code blocks and prerequisites. There are multiple references to installing and using Azure PowerShell, and some steps (e.g., Bicep installation) require manual steps for PowerShell users. The use of PowerShell and references to the Az.App module, as well as the explicit mention of Windows-centric tooling, indicate a bias toward Windows environments. In some sections, PowerShell examples are shown before or with equal weight to Bash, rather than Bash/Linux-first. No critical steps are Windows-only, but the documentation assumes familiarity with PowerShell and Windows tools.
Recommendations
- Make Bash/Azure CLI examples the default or primary example, with PowerShell as an alternative for Windows users.
- Clearly indicate which steps are platform-agnostic and which require Windows/PowerShell, and provide Linux/macOS alternatives where needed.
- Reduce the prominence of PowerShell in prerequisites and instructions, or move PowerShell-specific instructions to a dedicated section for Windows users.
- Where manual installation steps are required for PowerShell/Bicep, provide equivalent streamlined instructions for Linux/macOS users.
- Add explicit notes about cross-platform compatibility and clarify that Azure CLI works natively on Linux/macOS.
Container Apps
Monitor Azure Container Apps metrics
...zure-docs/blob/main/articles/container-apps/metrics.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation references both Azure CLI and Azure PowerShell cmdlets for retrieving metrics, but PowerShell is mentioned alongside CLI in a way that may suggest parity. However, there are no explicit Linux/macOS examples, and PowerShell is a Windows-centric tool. The documentation does not provide command-line examples for either platform, but the only tool mentioned with platform bias is PowerShell, which is primarily used on Windows. There is no mention of Bash, shell scripting, or Linux-specific patterns, and no screenshots or instructions tailored for Linux/macOS users.
Recommendations
- Add explicit Linux/macOS examples using Azure CLI commands, including sample metric retrieval commands.
- Clarify that Azure CLI is cross-platform and provide instructions for installing and using it on Linux/macOS.
- If PowerShell is mentioned, also mention Bash or shell scripting alternatives for Linux/macOS users.
- Include screenshots or terminal output examples from Linux/macOS environments.
- Reorder tool mentions to list Azure CLI first, as it is cross-platform.
Container Apps
Manage secrets in Azure Container Apps
...cs/blob/main/articles/container-apps/manage-secrets.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides examples for Azure Portal, ARM template, Azure CLI, and PowerShell. PowerShell is featured as a primary scripting example, but there are no Linux/macOS-specific shell examples (e.g., Bash, zsh). PowerShell is used for tasks that are not supported in PowerShell (e.g., Key Vault references, secret volume mounts), but no alternative Linux/macOS scripting guidance is provided. The ordering of examples often places PowerShell before CLI, and there is no mention of Linux-specific tools or patterns.
Recommendations
- Add Bash/zsh shell script examples for Linux/macOS users alongside PowerShell examples.
- Clearly indicate when features are not supported in PowerShell and provide CLI or ARM template alternatives for Linux/macOS users.
- Reorder examples to present cross-platform CLI (Azure CLI, ARM template) before PowerShell.
- Explicitly state that PowerShell examples are for Windows and provide parity for Linux/macOS where possible.
- Mention that Azure CLI is cross-platform and recommend it for Linux/macOS users.
Container Apps
Managed identities in Azure Container Apps
.../blob/main/articles/container-apps/managed-identity.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Summary
The documentation provides a PowerShell example for retrieving a managed identity token, but does not offer equivalent Linux/macOS shell examples (e.g., curl, wget, or bash). This creates a bias toward Windows users by assuming PowerShell as the default scripting environment for command-line token retrieval. No Linux-specific tools or shell patterns are mentioned in this section, and PowerShell is presented as the only script-based example for this task.
Recommendations
- Add equivalent Linux/macOS shell examples using curl or wget for token retrieval from the managed identity endpoint.
- Explicitly mention that the HTTP GET example can be performed with standard tools available on Linux/macOS, and provide sample bash/curl commands.
- Clarify that PowerShell is just one option, and provide parity for users on non-Windows platforms.
- Consider adding a note or a tab for 'Bash' or 'Linux/macOS' in the code example sections where PowerShell is used.