Container Apps
388
Total Pages
343
Linux-Friendly Pages
45
Pages with Bias
11.6%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
101 issues found
Showing 1-25 of 101 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 →
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, and referencing PowerShell before Bash in CLI automation. There is a lack of explicit Linux-focused examples, and Windows tools are mentioned exclusively or before their Linux equivalents. The resources and next steps also emphasize Windows development environments, with no mention of Linux editors or workflows.
Recommendations
- Include explicit Linux examples and workflows, such as using Linux-native editors (e.g., Vim, Emacs, JetBrains IDEs) for container app deployment.
- Provide Bash-first or Bash-only CLI automation examples, and clarify cross-platform compatibility for CLI commands.
- Add resources and tutorials for deploying from Linux environments, including instructions for common Linux distributions.
- Balance references to Visual Studio/VS Code with Linux alternatives, or at least acknowledge their cross-platform nature.
- Mention container tooling and registry workflows commonly used in Linux environments (e.g., Podman, Docker Compose on Linux).
Create Pull Request
Container Apps
Monitor Azure Container Apps metrics
...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 page references both Azure CLI and Azure PowerShell for retrieving metrics, but PowerShell is mentioned explicitly and linked alongside CLI, which is a Windows-centric tool. There are no Linux-specific examples, nor is there mention of Linux-native tools or shell commands. The documentation does not provide parity in examples or instructions for Linux users, and the order of mention (CLI and PowerShell) subtly prioritizes Windows tooling.
Recommendations
- Provide explicit Linux shell examples (e.g., bash commands using Azure CLI) for metric retrieval.
- Mention and link to cross-platform tools first (Azure CLI) before Windows-specific tools (PowerShell).
- Clarify that Azure CLI works on Linux, macOS, and Windows, and provide installation/use instructions for non-Windows platforms.
- Include screenshots or terminal examples from Linux environments.
- If PowerShell is referenced, also mention PowerShell Core's cross-platform support, or clarify the distinction.
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 and workflows, such as Visual Studio and Visual Studio Code, and referencing PowerShell before Bash in the CLI section. There is a lack of explicit Linux-focused examples, tools, or workflows, and Windows tools are mentioned first or exclusively throughout the page.
Recommendations
- Add explicit Linux examples and workflows, such as using VS Code on Linux, Docker commands in Bash, and Linux-native deployment steps.
- Provide parity in tooling recommendations, e.g., mention JetBrains Rider or other cross-platform editors alongside Visual Studio.
- In CLI sections, alternate or balance references to PowerShell and Bash, and provide example commands for both shells.
- Include links to documentation for deploying from Linux environments and using Linux container registries.
- Highlight cross-platform compatibility and note any differences or considerations for Linux users.
Container Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/get-started-existing-container-image.md
...container-apps/get-started-existing-container-image.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides both Bash and PowerShell examples throughout, but the PowerShell examples rely heavily on the Az PowerShell module, which is primarily a Windows/PowerShell-centric tool. In several cases, the PowerShell examples are more verbose and use Windows-specific patterns (e.g., object pipelines, hash tables), and the documentation includes instructions to install PowerShell modules. The Azure CLI (Bash) examples are more concise and cross-platform, but PowerShell is given equal prominence, which may suggest a Windows-centric approach. There is no mention of native Linux tools or shell scripting beyond Bash, and PowerShell is presented as the only alternative to Bash, with no mention of other Unix shells.
Recommendations
- Clarify that PowerShell Core is cross-platform, or explicitly mention that PowerShell examples work on Linux/macOS if PowerShell Core is used.
- Consider adding examples using other common Linux shells (e.g., zsh, sh) or note that Bash examples are compatible with them.
- Where possible, simplify PowerShell examples to reduce Windows-specific patterns and make them more approachable for non-Windows users.
- Add a brief note at the start explaining that Azure CLI is the recommended cross-platform tool, and PowerShell is provided for users who prefer it.
- Ensure that any instructions for installing tools (like Az PowerShell modules) include cross-platform guidance.
- If possible, provide a table or toggle to let users select their preferred environment (Windows, Linux, macOS) and show only relevant examples.
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 focused on Windows and Visual Studio, providing only instructions and screenshots for the Visual Studio GUI on Windows. There are no examples or guidance for deploying to Azure Container Apps from Linux environments, nor are alternative tools (such as VS Code, Azure CLI, or Docker CLI) mentioned. The workflow assumes the user is on Windows with Visual Studio, and does not address Linux users or provide parity in tooling or instructions.
Recommendations
- Add a section describing how to deploy containerized .NET applications to Azure Container Apps using cross-platform tools such as Azure CLI, Docker CLI, or Visual Studio Code.
- Include Linux-specific instructions and command-line examples for creating, building, and deploying the application, ensuring users on Linux or macOS can follow along.
- Mention and link to alternative tools (e.g., VS Code with Docker and Azure extensions) earlier in the documentation, not just Visual Studio.
- Provide parity in screenshots and workflow descriptions for Linux users, or at least clarify that the current instructions are Windows/Visual Studio-specific and link to Linux-friendly guides.
- Ensure that all steps that rely on Visual Studio GUI have equivalent command-line or cross-platform alternatives documented.
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 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 instructions and explanations of object models, while the Azure CLI section is more concise. There is no mention of Linux-specific shells or scripting (e.g., Bash), and PowerShell (a Windows-centric tool) is given equal or greater prominence. No Linux-native tools or patterns (such as Bash scripting or environment variable manipulation in Dockerfiles) are referenced. The tab order also presents PowerShell immediately after Azure CLI, reinforcing parity with Windows tools.
Recommendations
- Add explicit Bash shell examples for Azure CLI commands, showing how to set and export environment variables in a Linux context.
- Include notes or examples for common Linux workflows, such as using environment variables in Dockerfiles or with 'env' files.
- Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows, possibly with a note or section for Linux users.
- Consider adding a 'Bash' or 'Linux shell' tab alongside the existing 'Azure CLI' and 'PowerShell' tabs to demonstrate parity.
- Reduce the level of detail in PowerShell-specific object manipulation unless similar depth is provided for Linux-native workflows.
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 by providing only Windows-based VM creation and validation steps (e.g., using Windows Server images and PowerShell for DNS testing), with no Linux VM or Bash-based examples. The portal and CLI instructions default to Windows Server, and the only shell commands for endpoint validation are in PowerShell. There are no instructions for creating or testing with a Linux VM, nor are there Bash or Linux-native DNS tools (like dig or nslookup in Bash) shown.
Recommendations
- Add parallel instructions for creating a Linux VM (e.g., Ubuntu) in both portal and CLI sections.
- Provide examples for validating DNS and connectivity using Bash (e.g., using nslookup or dig in a Linux shell) inside the Linux VM.
- When listing VM image options, mention Linux images alongside Windows images, or default to a cross-platform-neutral image.
- Where PowerShell is used, also provide equivalent Bash/Linux commands.
- Review the order of presentation to ensure Linux and Windows are given equal prominence, or group instructions by OS.
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
Missing Linux Example
Windows Tools
Summary
The documentation consistently provides PowerShell examples for all supported scenarios, and in some cases, PowerShell is the only scripting language shown alongside Azure CLI and ARM templates. There are no explicit Linux shell (bash) or cross-platform scripting examples outside of Azure CLI, and PowerShell is presented as a primary automation tool. In some cases, features are not supported in PowerShell, but there are no alternative Linux-native instructions or notes for Linux users. The documentation assumes familiarity with Windows-centric tools and patterns, such as PowerShell objects and parameters, without offering parity for Linux shell users.
Recommendations
- Add explicit bash (Linux shell) scripting examples for all scenarios where PowerShell is shown, especially for tasks like setting environment variables, referencing secrets, and mounting volumes.
- Where PowerShell is not supported (e.g., Key Vault references, mounting secrets as a volume), provide alternative instructions or workarounds for Linux users, or clearly state that Azure CLI is the cross-platform alternative.
- Reorder examples to present Azure CLI (which is cross-platform) before PowerShell, or group examples by platform rather than by tool.
- Include notes or callouts for Linux/macOS users, especially where Windows-specific tools or patterns are used.
- Consider adding a section summarizing cross-platform support for each feature, clarifying which tools and platforms are supported.
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 page references both Azure CLI and Azure PowerShell for retrieving metrics, but PowerShell is mentioned explicitly and linked alongside CLI, suggesting parity. However, there are no concrete command examples for either tool, and no Linux-specific tools or patterns (such as Bash scripting, curl, or jq) are mentioned. The documentation does not provide any Linux-oriented guidance or examples, and the mention of PowerShell may imply a Windows-first audience.
Recommendations
- Provide explicit command-line examples for both Azure CLI and Azure PowerShell, showing how to retrieve metrics.
- Include Linux/Bash-specific examples, such as using Azure CLI in Bash, piping output to jq, or integrating with Linux monitoring tools.
- Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
- Avoid mentioning PowerShell before CLI, or present both equally, noting their platform compatibility.
- Add a section or note for Linux users, highlighting any differences or tips for monitoring from Linux environments.
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
Windows Tools
Powershell Heavy
Summary
The documentation shows a moderate Windows bias. In several places, Windows terminology and tools are mentioned first or exclusively (e.g., 'elevated command prompt', 'Docker on Windows', PowerShell examples), and PowerShell is given parity with Bash in extension installation, but Linux-specific shells or tools are not discussed. There is no explicit Linux example for running Docker, and the only shell-specific tabs are Bash and PowerShell, with no mention of Linux-specific troubleshooting environments or commands.
Recommendations
- Add explicit Linux shell examples and instructions where relevant (e.g., mention 'terminal' instead of 'elevated command prompt', and provide Linux-specific Docker run instructions).
- When referencing Docker, include links or notes for both Windows and Linux installation and usage.
- In sections with command tabs, consider adding a generic 'Linux' or 'macOS' tab if there are differences, or clarify that Bash examples work on Linux/macOS.
- Avoid Windows-first language (e.g., say 'open a terminal' instead of 'elevated command prompt') and ensure parity in tool references.
- Mention Linux troubleshooting tools or patterns where appropriate, such as using 'journalctl' for Docker logs or checking permissions.
- Ensure that all PowerShell examples have equivalent Bash/Linux CLI examples, and vice versa.
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 →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides both Bash (Azure CLI) and PowerShell examples for all command-line steps, but PowerShell is given equal prominence throughout, and Windows-specific tools (PowerShell cmdlets) are used extensively. There are no Linux-specific tools or patterns mentioned, and PowerShell examples are present for every operation, reflecting a bias toward Windows environments. Additionally, some resource creation steps (e.g., Log Analytics workspace) are only shown with PowerShell, not Bash, and PowerShell parameter tables are included alongside Bash, reinforcing Windows parity but not Linux-first approaches.
Recommendations
- Ensure all resource creation and configuration steps (e.g., Log Analytics workspace creation) have Bash/Azure CLI equivalents, not just PowerShell.
- Consider providing Linux-specific troubleshooting tips or notes where platform differences may arise.
- If PowerShell is shown, clarify that it is available cross-platform (Windows, macOS, Linux) to reduce the perception of Windows-only bias.
- Add explicit references to Linux environments and tools where relevant, such as mentioning that Bash examples are suitable for Linux and macOS.
- Review the order of examples to ensure Bash/Linux commands are presented first or with equal prominence to PowerShell/Windows commands.
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 more verbose and step-by-step coverage than the Azure CLI section. PowerShell examples are included for every scenario, and the documentation references .NET object models and PowerShell cmdlets, which are Windows-centric. The PowerShell section is given equal prominence as Azure CLI, but the depth and specificity of PowerShell instructions may indicate a slight Windows bias. There are no Linux/macOS-specific examples, nor any mention of platform-specific considerations for non-Windows users.
Recommendations
- Add explicit notes clarifying that Azure CLI works cross-platform (Windows, Linux, macOS) and is recommended for non-Windows users.
- Consider providing bash or shell scripting examples for Linux/macOS users, especially for common automation scenarios.
- Mention that PowerShell Core is available cross-platform, but clarify any differences or limitations when running these commands on Linux/macOS.
- Balance the depth of instructions between Azure CLI and PowerShell, ensuring Linux/macOS users have equally detailed guidance.
- Avoid referencing Windows/.NET object models unless necessary, and provide alternative approaches for non-Windows environments.
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
Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. It highlights Windows-centric tools (Visual Studio, Visual Studio Code) and mentions PowerShell before Bash in the CLI section. Examples and resource links focus on Visual Studio and Visual Studio Code, which are primarily associated with Windows workflows, and do not provide parity with Linux/macOS alternatives (e.g., JetBrains IDEs, Vim, Emacs). There is no explicit mention of Linux/macOS-specific tools or workflows, and Bash is only briefly referenced. No Linux/macOS-specific examples or screenshots are provided.
Recommendations
- Include examples and resource links for Linux/macOS workflows, such as using JetBrains IDEs, Vim, or Emacs.
- Provide Bash-first or Bash-only CLI automation examples, and clarify cross-platform compatibility.
- Add explicit instructions or screenshots for Linux/macOS environments where relevant.
- Balance the order of tool mentions (e.g., 'Bash or PowerShell') and avoid Windows-first phrasing.
- Highlight cross-platform editors and tools in addition to Visual Studio and Visual Studio Code.
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
Windows Tools
Powershell Heavy
Summary
The documentation page demonstrates a notable Windows bias in several areas. When guiding users to create and verify a VM for private endpoint testing, only Windows Server is offered as the VM image, and all connection and DNS verification steps use Windows tools (PowerShell, nslookup) with no mention of Linux alternatives. The examples and instructions for VM creation and testing are Windows-centric, lacking parity for Linux users. Additionally, Windows is presented first and exclusively in critical workflow sections.
Recommendations
- Include instructions and examples for creating a Linux VM (e.g., Ubuntu) in both Azure Portal and CLI sections.
- Provide Linux equivalents for DNS verification (e.g., using 'dig' or 'nslookup' in a Linux shell) and browser access.
- Explicitly mention that either Windows or Linux VMs can be used for testing, and provide side-by-side steps for both.
- Avoid presenting Windows-only tools and workflows; ensure parity by showing Linux commands and patterns.
- Where PowerShell is used, offer Bash or shell alternatives for Linux/macOS users.
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 in the variable assignment example: the Bash example uses 'SET', which is a Windows CMD command, not standard Bash ('export' or variable assignment with '=' is typical in Bash). Additionally, PowerShell examples are present throughout, and the use of 'Invoke-AzOperationalInsightsQuery' is a Windows PowerShell-specific tool, with no mention of Linux/macOS alternatives for querying logs outside of Azure CLI. The Azure Portal instructions are platform-neutral.
Recommendations
- Correct the Bash variable assignment to use standard Bash syntax (e.g., WORKSPACE_ID=<WORKSPACE_ID> or export WORKSPACE_ID=<WORKSPACE_ID>) instead of 'SET', which is a Windows CMD command.
- Clarify that PowerShell examples are for Windows users, and Bash examples are for Linux/macOS users.
- If possible, provide examples using cross-platform tools (e.g., curl, jq) for querying logs, especially for Linux/macOS users.
- Explicitly state platform applicability for each example to reduce ambiguity.
- Consider providing a table or note summarizing command differences between platforms.
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 templates, Azure CLI, and PowerShell. PowerShell is featured as a first-class command-line option, but there are no Linux/macOS-specific shell examples (e.g., Bash, zsh), nor are there any references to Linux-native tools or patterns. PowerShell examples are given equal or greater prominence than CLI, and some features (Key Vault secret references, secret volume mounts) are explicitly unsupported in PowerShell, but this is not balanced by Linux-specific guidance. The CLI examples are cross-platform, but the lack of Linux/macOS shell context or troubleshooting tips creates friction for non-Windows users.
Recommendations
- Add explicit Bash/zsh shell examples for Linux/macOS users, especially for environment variable handling and scripting.
- Clarify that Azure CLI commands are cross-platform and provide troubleshooting notes for common Linux/macOS issues (e.g., quoting, environment variable expansion).
- Where PowerShell is unsupported, offer Linux/macOS alternatives or workarounds.
- Reorder examples so CLI (cross-platform) appears before PowerShell, or group by OS context.
- Explicitly state platform compatibility for each method, especially where features are missing in PowerShell or only available via CLI/ARM.
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 token from the managed identity endpoint, but does not offer an equivalent example for Linux/macOS users (e.g., using curl or wget). This creates a bias toward Windows users, as PowerShell is primarily a Windows tool and its usage is shown exclusively for scripting against the endpoint. The rest of the documentation is generally cross-platform, focusing on Azure CLI, ARM, YAML, and Bicep, which are platform-agnostic.
Recommendations
- Add Linux/macOS shell examples (e.g., using curl or wget) for retrieving tokens from the managed identity endpoint alongside the PowerShell example.
- Explicitly mention that Azure CLI commands work on Windows, Linux, and macOS.
- Where scripting examples are provided, ensure both PowerShell and Bash (or POSIX shell) variants are shown.
- Consider moving PowerShell examples after cross-platform or Linux shell examples, or present them side-by-side.
Container Apps
Tutorial: Build and deploy your app to Azure Container Apps
...main/articles/container-apps/tutorial-code-to-cloud.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides both Bash and PowerShell examples for nearly every command, but PowerShell is featured as a first-class scripting language throughout, with extensive PowerShell-specific instructions and objects. Windows tools (PowerShell, Docker Desktop for Windows) are mentioned explicitly, and PowerShell examples are often more detailed than Bash. There is a slight ordering bias, with PowerShell examples and instructions sometimes appearing before or with more detail than Bash/Linux equivalents. However, Linux and macOS users are not blocked from completing the tutorial, as Bash examples are present for all critical steps.
Recommendations
- Add explicit Linux/macOS instructions where PowerShell-specific steps are given (e.g., for Azure resource creation and management).
- Ensure Bash examples are as detailed as PowerShell ones, including variable usage and output parsing.
- Where Docker Desktop is mentioned, clarify Linux alternatives (e.g., Docker Engine, Podman).
- Consider listing Bash/Linux examples before PowerShell/Windows ones to reduce perceived Windows-first bias.
- Add troubleshooting tips for common Linux/macOS issues (e.g., permissions, environment variables).
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. Visual Studio and Visual Studio Code are featured as primary code editor options, both of which are strongly associated with Windows (though VS Code is cross-platform). The 'Infrastructure as Code' section mentions PowerShell before Bash when discussing automation, and the CLI examples and resources do not clarify or provide explicit Linux/macOS instructions or parity. There is no mention of Linux-native editors (such as Vim, Emacs, or JetBrains IDEs), nor are there examples or resources tailored for Linux/macOS users.
Recommendations
- Add explicit Linux/macOS instructions and examples alongside Windows ones, especially for CLI usage.
- Mention and provide examples for Linux-native editors and workflows (e.g., Vim, Emacs, JetBrains IDEs).
- When listing automation options, alternate or balance the order of PowerShell and Bash, or provide parallel examples.
- Clarify cross-platform compatibility for Visual Studio Code and Azure CLI, and link to installation guides for Linux/macOS.
- Include troubleshooting or tips for Linux/macOS users where workflows may differ.
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 CLI commands, but PowerShell is given equal prominence and, in some sections (notably the 'Deploy front end application'), the PowerShell workflow is much more verbose and detailed than the Bash equivalent. The PowerShell section uses specialized Azure PowerShell cmdlets (e.g., New-AzContainerApp), while the Bash section uses the simpler az CLI. There is a slight Windows-first bias in the depth and complexity of PowerShell instructions, which may make Linux/macOS users feel the documentation is more tailored for Windows environments.
Recommendations
- Ensure parity in detail and explanation between Bash and PowerShell sections. For example, provide more context or troubleshooting for Bash users if complex steps are needed.
- Consider adding a note clarifying that Bash examples are suitable for Linux/macOS and WSL users, and PowerShell is for Windows users.
- Where possible, use az CLI commands for both Bash and PowerShell to reduce platform-specific divergence, unless a PowerShell-only feature is required.
- If advanced PowerShell workflows are shown, provide equivalent Bash scripts or guidance for Linux/macOS users.
- Explicitly mention cross-platform compatibility and test Bash instructions on macOS and Linux.
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 alongside Azure CLI and portal, with PowerShell examples using Windows-specific cmdlets and object models. PowerShell coverage is more verbose and step-by-step than CLI, and PowerShell is a Windows-centric tool. The CLI examples are present and usable cross-platform, but PowerShell is given equal prominence and detail, which may imply a Windows-first approach. No Linux/macOS-specific shell examples (e.g., Bash, scripting) are provided, and PowerShell is not explicitly marked as Windows-only, potentially causing confusion for Linux/macOS users.
Recommendations
- Clarify that PowerShell examples are primarily for Windows users, and note cross-platform availability if relevant.
- Add Bash or shell script examples for Linux/macOS users, especially for tasks involving object manipulation or automation.
- Ensure CLI examples are as detailed as PowerShell, including multi-step scenarios.
- Consider presenting CLI examples before PowerShell, as CLI is cross-platform.
- Explicitly mention tool/platform compatibility in each section.
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, especially in the 'Verify the private endpoint connection' section. Both the Azure Portal and Azure CLI instructions exclusively create and use a Windows Server VM, with no mention of Linux VM alternatives. The connection test is performed using PowerShell and nslookup within a Windows VM, and the VM creation CLI example uses a Windows image. There are no Linux VM examples, nor are Linux command-line tools (e.g., dig, curl) referenced for DNS or connectivity testing.
Recommendations
- Add parallel instructions for creating a Linux VM (e.g., Ubuntu) in both portal and CLI sections.
- Provide Linux command-line examples for DNS resolution (e.g., 'dig <CONTAINER_APP_ENDPOINT>' or 'nslookup') and HTTP connectivity (e.g., 'curl').
- Mention that users can choose either Windows or Linux VMs for testing, and clarify any differences in experience.
- Include screenshots or output samples from Linux tools where appropriate.
- Avoid implying Windows is required for connectivity testing; make Linux parity explicit.
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
Missing Linux Example
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 are subtle signs of Windows bias: the Bash examples use 'SET' (a Windows CMD command) instead of 'export' (the standard for Bash on Linux/macOS), and the PowerShell examples use Windows-specific cmdlets (Invoke-AzOperationalInsightsQuery). There is no explicit mention of Linux/macOS tools or shell environments, and the use of 'SET' in Bash examples may confuse Linux users. No Linux/macOS-specific troubleshooting or parity notes are present.
Recommendations
- Replace 'SET' with 'export' in Bash examples to match standard Linux/macOS usage.
- Add explicit notes clarifying that Bash examples are intended for Linux/macOS and CMD examples for Windows.
- Provide troubleshooting tips or environment notes for Linux/macOS users (e.g., Azure CLI installation, shell compatibility).
- Ensure parity in example order (sometimes show Bash first, sometimes PowerShell) or clarify that both are equally supported.
- Include a brief section on running Azure CLI commands in Linux/macOS terminals.
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 First
Windows Tools
Summary
The documentation provides both Azure CLI (Bash) and Azure PowerShell examples for all command-line instructions, but PowerShell is given equal or greater prominence throughout. Prerequisites and installation steps frequently mention PowerShell and Windows-specific modules (Az.App), sometimes before or alongside Azure CLI. There are no Linux/macOS-specific troubleshooting tips, nor any mention of platform-specific differences. The use of PowerShell and references to Windows tooling may create friction for Linux/macOS users, but CLI parity is maintained.
Recommendations
- Clearly indicate that Azure CLI commands work cross-platform (Linux/macOS/Windows) and are preferred for non-Windows users.
- Move Azure CLI (Bash) examples before PowerShell in all code blocks and instructions, or default to CLI unless PowerShell is required.
- Add notes clarifying that PowerShell examples are intended for Windows users, and that Linux/macOS users should use Bash/CLI.
- Include troubleshooting notes for Linux/macOS environments (e.g., permissions, shell differences, path issues).
- Reduce references to Windows-specific modules unless strictly necessary, and provide alternatives or clarifications for other platforms.
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 templates, Azure CLI, and PowerShell. PowerShell examples are included for most operations, but there are no Linux/macOS-specific shell examples (e.g., Bash, zsh), and PowerShell is Windows-centric. PowerShell is presented as a primary scripting option alongside CLI, but Linux-native scripting (Bash) is not mentioned. In several cases, PowerShell is given equal prominence to CLI, and in some cases, PowerShell functionality is missing (e.g., Key Vault references, secret volume mounts), but this is noted. There is a lack of explicit Linux/macOS parity in scripting examples and tool references.
Recommendations
- Add Bash/zsh shell examples for all CLI commands, showing usage in Linux/macOS environments (e.g., environment variable syntax, quoting).
- Explicitly mention that Azure CLI works cross-platform and provide guidance for Linux/macOS users where syntax or behavior differs.
- Clarify in each section where PowerShell is not supported that Linux/macOS users should use Azure CLI or ARM templates.
- Consider adding a table summarizing feature parity between Azure CLI, PowerShell, ARM templates, and portal, with notes for Linux/macOS users.
- Where PowerShell is shown, add a note that it is primarily for Windows users, and recommend CLI for Linux/macOS.