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 51-75 of 101 flagged pages
Container Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/sessions.md
...ure-docs/blob/main/articles/container-apps/sessions.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Hyper-V, a Windows-based virtualization technology, as the foundation for session isolation. There is no mention of Linux-based isolation technologies (such as KVM, gVisor, or Kata Containers) or how sessions are isolated when running on Linux hosts. The documentation links to Windows Server Hyper-V documentation and does not provide Linux equivalents or alternatives, implicitly prioritizing Windows technologies.
Recommendations
- Clarify whether Hyper-V is used for session isolation regardless of the underlying host OS, or if alternative Linux-based isolation technologies are used in Linux environments.
- If Linux-based isolation is supported, mention and briefly describe the relevant technology (e.g., KVM, gVisor, Kata Containers) and provide links to their documentation.
- Avoid linking exclusively to Windows/Hyper-V documentation; provide balanced references to both Windows and Linux isolation technologies where applicable.
- Include a section or note explaining how session isolation works on Linux-based Azure infrastructure, if supported.
- Ensure that examples, descriptions, and technical explanations are platform-agnostic or provide parity between Windows and Linux where possible.
Create Pull Request
Container Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/token-store.md
...-docs/blob/main/articles/container-apps/token-store.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation demonstrates a Windows bias by exclusively referencing the Azure Portal GUI for tasks such as generating a SAS URL and managing secrets, which is typically associated with a Windows-centric workflow. There are no CLI or cross-platform examples for generating the SAS URL or managing secrets, and no mention of Linux tools or command-line alternatives. The only CLI example provided is for the Azure CLI, which is cross-platform, but it appears after several portal-based steps.
Recommendations
- Add Azure CLI and/or Azure PowerShell examples for generating a SAS URL and managing secrets, making it clear these commands work on all platforms.
- Include Linux/macOS-specific instructions or screenshots where appropriate, or clarify that the Azure Portal is accessible from any OS.
- Mention and link to documentation for performing these tasks using the Azure CLI or PowerShell, and consider presenting CLI examples before or alongside portal instructions.
- Explicitly state that all steps can be performed on Linux, macOS, and Windows, and avoid implying a Windows-only workflow.
Container Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/troubleshoot-storage-mount-failures.md
.../container-apps/troubleshoot-storage-mount-failures.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation page exclusively references the Azure Portal's graphical interface for troubleshooting, which is more commonly associated with Windows workflows. There are no examples or instructions for troubleshooting storage mount failures using Linux-native tools, CLI commands (such as Azure CLI), or shell scripting, which are common in Linux environments. No Linux-specific troubleshooting steps or examples are provided.
Recommendations
- Add troubleshooting steps using the Azure CLI (az) for users who prefer command-line interfaces, common in Linux environments.
- Include examples of checking mount points and storage connectivity from within a Linux-based container using shell commands (e.g., ls, mount, df, etc.).
- Provide parity in instructions for both portal (GUI) and CLI-based workflows, ensuring Linux users are equally supported.
- Mention and link to Linux troubleshooting tools and patterns (e.g., viewing logs with tail/cat, checking /etc/fstab, etc.) where relevant.
Container Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/troubleshoot-target-port-settings.md
...es/container-apps/troubleshoot-target-port-settings.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page focuses exclusively on troubleshooting target port settings using the Azure Portal UI, without providing any command-line examples. There is no mention of Linux tools, CLI commands, or cross-platform approaches (such as Azure CLI or Bash). The absence of Linux-specific or cross-platform instructions, and the reliance on a graphical interface (which is more common in Windows-centric workflows), indicates a bias toward Windows users and leaves Linux users without parity.
Recommendations
- Add Azure CLI examples for diagnosing and troubleshooting port settings, including commands that can be run in Bash or any terminal.
- Include Linux-native troubleshooting steps, such as using curl, netstat, or docker commands to verify port exposure and application listening ports.
- Provide PowerShell and Bash script snippets side-by-side where relevant.
- Explicitly mention that the Azure Portal is cross-platform accessible, but supplement with CLI-based instructions for users who prefer or require command-line tools.
Container Apps
Code to cloud options in Azure Container Apps
.../main/articles/container-apps/code-to-cloud-options.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation shows a mild Windows bias by listing Visual Studio (a Windows-first IDE) before Visual Studio Code in the code editor section, and by mentioning PowerShell before Bash when discussing CLI automation. However, Linux/macOS users are not blocked, and alternatives are referenced. No critical sections are Windows-only, and most tools (VS Code, Azure CLI, AZD) are cross-platform.
Recommendations
- When listing code editors, mention Visual Studio Code before Visual Studio, or clarify their cross-platform support.
- When referencing CLI automation, list Bash before PowerShell or mention both equally.
- Add explicit notes or links for Linux/macOS users where relevant, especially in sections referencing PowerShell or Visual Studio.
- Ensure all example commands and scripts are shown for both Bash and PowerShell where automation is discussed.
Container Apps
Deploy the Dapr extension for Azure Functions in Azure Container Apps
...in/articles/container-apps/dapr-functions-extension.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both PowerShell and curl examples for invoking Azure Functions and viewing logs, but PowerShell examples are consistently shown before curl (Linux/macOS) examples. All other instructions use cross-platform Azure CLI commands. There are no missing Linux examples, and no exclusive use of Windows tools.
Recommendations
- Present curl (Linux/macOS) and PowerShell examples in parallel tabs, or alternate the order to avoid consistently prioritizing Windows.
- Explicitly mention that all Azure CLI commands work on Windows, Linux, and macOS.
- Consider adding bash or zsh shell examples if relevant, though curl is sufficient for HTTP requests.
Container Apps
Quickstart: Deploy a Dapr application to Azure Container Apps with an Azure Resource Manager or Bicep file
...iner-apps/microservices-dapr-azure-resource-manager.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Bash (Linux/macOS) and PowerShell (Windows) examples for all Azure CLI and resource management commands. However, PowerShell examples are consistently presented alongside Bash, and in some sections (such as the deployment and log viewing steps), PowerShell is given equal prominence. There is a slight Windows-first bias in the use of PowerShell tabs and the inclusion of Azure PowerShell references in metadata, but Linux/macOS users are not blocked from completing any steps.
Recommendations
- Ensure Bash examples are shown first in all code tabs, as Bash is the default shell for most cross-platform CLI users.
- Add a brief note clarifying that Bash commands work on Linux, macOS, and Windows (with WSL or Git Bash), while PowerShell is primarily for Windows users.
- Review metadata and custom tags (e.g., 'devx-track-azurepowershell') to ensure equal representation of Bash and Azure CLI usage.
- Consider mentioning that Azure CLI is cross-platform and preferred for scripting on Linux/macOS.
Container Apps
Code to cloud options in Azure Container Apps
.../main/articles/container-apps/code-to-cloud-options.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation generally presents a cross-platform approach, but there is a subtle Windows bias in the 'Code editor' section, where Visual Studio (a Windows-first IDE) is mentioned before Visual Studio Code (cross-platform). In the Infrastructure as Code section, PowerShell is mentioned alongside Bash, but PowerShell is listed first, which may imply a Windows-first orientation. However, Linux/macOS users are not blocked from completing any tasks, and Bash is acknowledged. No examples are given that are Windows-only, and Linux equivalents are referenced.
Recommendations
- List Visual Studio Code before Visual Studio in the 'Code editor' section, as VS Code is cross-platform and more relevant to Linux/macOS users.
- In the CLI table, mention Bash before PowerShell to reflect the cross-platform default shell for many users.
- Where possible, clarify that all CLI instructions work on Bash (Linux/macOS) as well as PowerShell (Windows), and provide explicit examples if there are differences.
- Consider adding a brief note in the 'Code editor' section that Visual Studio is only available on Windows, while Visual Studio Code is available on all platforms.
Container Apps
Quickstart: Deploy a Dapr application to Azure Container Apps with an Azure Resource Manager or Bicep file
...iner-apps/microservices-dapr-azure-resource-manager.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Bash (Azure CLI) and PowerShell examples for all deployment, log viewing, and cleanup commands. However, PowerShell examples are given equal prominence to Bash, and in some sections (such as deployment and log viewing), PowerShell examples appear immediately after Bash, which may create a subtle Windows-first impression. There are no Linux-specific tools or patterns mentioned, but the documentation does not omit Linux/macOS instructions and does not rely on Windows-only tools.
Recommendations
- Consider making Bash (Linux/macOS) examples the default or first shown, with PowerShell as an alternative tab.
- Explicitly note that Bash commands work on Linux/macOS and Windows (with WSL or Azure CLI installed), and PowerShell is primarily for Windows users.
- Add a short note clarifying cross-platform compatibility of Azure CLI and Git.
- If possible, include a brief section or callout for Linux/macOS users to confirm parity and ease of use.
Container Apps
Deploy the Dapr extension for Azure Functions in Azure Container Apps
...in/articles/container-apps/dapr-functions-extension.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both PowerShell and curl examples for invoking Azure Functions and viewing logs, but consistently presents PowerShell examples before curl. This ordering subtly prioritizes Windows/PowerShell users, even though curl is available on all platforms. All other setup and deployment steps use Azure CLI, which is cross-platform, and no Windows-only tools or patterns are present.
Recommendations
- Present curl examples before PowerShell, or show curl as the default with PowerShell as an alternative.
- Explicitly mention that curl commands work on Linux, macOS, and Windows (with WSL or Git Bash), while PowerShell is primarily for Windows users.
- Consider using tabbed examples with clear platform labels (e.g., 'Linux/macOS (curl)', 'Windows (PowerShell)').
- Ensure that any future troubleshooting or advanced sections include Linux/macOS-specific guidance if needed.
Container Apps
Create a zone-redundant container app
...main/articles/container-apps/how-to-zone-redundancy.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides examples for Azure Portal, Azure CLI, and Azure PowerShell. While Azure CLI is cross-platform, Azure PowerShell is Windows-centric and is presented as a full example set alongside CLI. In several sections, PowerShell examples are given equal prominence to CLI, and in some cases, PowerShell is shown after CLI but before any mention of Bash or Linux-specific tooling. There are no Linux/macOS-specific shell examples (e.g., Bash scripts), nor is there explicit mention of Linux/macOS usage patterns. However, the CLI examples are sufficient for Linux/macOS users to complete the tasks.
Recommendations
- Add explicit Bash shell examples for Linux/macOS users, especially for environment variable assignment and command chaining.
- Clarify that Azure CLI commands work cross-platform and highlight any OS-specific nuances if applicable.
- Consider moving PowerShell examples to a separate section or clearly label them as Windows-specific.
- Add notes or links for Linux/macOS users on installing and using Azure CLI.
Container Apps
Quickstart: Deploy a Dapr application to Azure Container Apps with an Azure Resource Manager or Bicep file
...iner-apps/microservices-dapr-azure-resource-manager.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Bash and PowerShell examples for all CLI commands, but PowerShell examples are consistently present and sometimes shown before or alongside Bash. This can be interpreted as a mild Windows bias, as PowerShell is primarily a Windows shell (though it is available cross-platform). No Linux-specific tools or workflows are omitted, and Bash examples are always present, ensuring Linux/macOS users can follow along. However, the inclusion of PowerShell in every example and the presence of 'devx-track-azurepowershell' metadata may signal a slight preference for Windows environments.
Recommendations
- Ensure Bash examples are always shown first, as Bash is the default shell for most Linux/macOS users.
- Clarify in the introduction that both Bash and PowerShell are supported, and that Bash is recommended for Linux/macOS.
- Consider adding a note that PowerShell Core is available cross-platform, but Bash is more common on Linux/macOS.
- Review metadata and ensure parity in tracking for Bash and PowerShell usage.
Container Apps
Deploy the Dapr extension for Azure Functions in Azure Container Apps
...in/articles/container-apps/dapr-functions-extension.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both PowerShell and curl examples for invoking Azure Functions and viewing logs, but PowerShell examples are consistently presented before curl. All other instructions use the Azure CLI, which is cross-platform. No exclusive Windows tools or patterns are used, and Linux/macOS users can follow all steps without issue.
Recommendations
- Present curl examples before PowerShell, or present both side-by-side to avoid the perception of Windows-first bias.
- Explicitly mention that Azure CLI commands work on Windows, Linux, and macOS.
- Consider adding bash or zsh shell examples if relevant, though curl is sufficient for HTTP requests.
Container Apps
Code to cloud options in Azure Container Apps
.../main/articles/container-apps/code-to-cloud-options.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page for 'Code to cloud options in Azure Container Apps' demonstrates minor Windows bias. Visual Studio (Windows-only) is mentioned before Visual Studio Code (cross-platform), and deployment examples/resources focus on Visual Studio first. In the Infrastructure as Code section, PowerShell is mentioned alongside Bash, but no Linux/macOS-specific CLI usage or examples are provided. There are no explicit Linux/macOS examples or screenshots, and Windows tooling (Visual Studio, PowerShell) is referenced before or more prominently than Linux equivalents.
Recommendations
- Present Visual Studio Code (cross-platform) examples before or alongside Visual Studio, clarifying platform compatibility.
- Include explicit Bash and Linux/macOS CLI usage examples or screenshots where automation is discussed.
- Add notes or sections highlighting Linux/macOS workflows, such as using Docker CLI, Azure CLI in Bash, or VS Code on Linux/macOS.
- Balance references to PowerShell and Bash, ensuring Linux/macOS users see their preferred shell represented equally.
- Where possible, clarify which tools are Windows-only and which are cross-platform.
Container Apps
Tutorial: Communication between microservices in Azure Container Apps
...es/container-apps/communicate-between-microservices.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for all CLI commands, ensuring cross-platform coverage. However, PowerShell examples are given equal prominence to Bash, and in some cases, PowerShell instructions are more verbose and detailed (e.g., the container app deployment section). There is a slight 'windows_first' bias in the sense that PowerShell is treated as a first-class citizen alongside Bash, which may create friction for Linux/macOS users who typically use Bash. No Windows-only tools or patterns are present, and Linux examples are not missing.
Recommendations
- Keep Bash examples as the primary/default, with PowerShell as an alternative tab, since Bash is more universally available across platforms.
- Where PowerShell instructions are more detailed, provide equivalent Bash instructions (e.g., for complex object creation in container app deployment).
- Clarify in the prerequisites which shell users should choose based on their OS.
- Consider adding a note that Bash examples work on Linux/macOS and Windows (via WSL or Git Bash), while PowerShell is mainly for Windows users.
Container Apps
Deploy an artifact file to Azure Container Apps
...s/blob/main/articles/container-apps/deploy-artifact.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for all command-line steps, but PowerShell (Windows) is always presented as an equal alternative, never as a secondary or follow-up. There is a slight bias in that PowerShell is given equal prominence to Bash, rather than prioritizing Bash (which is native to Linux/macOS and available on Windows via WSL or Git Bash). No Windows-only tools or patterns are used, and Linux/macOS users can complete all tasks without friction. However, the use of PowerShell tabs throughout may subtly reinforce a Windows-centric workflow.
Recommendations
- Consider listing Bash examples first, as Bash is the default shell on Linux/macOS and widely available on Windows.
- Add a note clarifying that Bash commands work on Linux, macOS, and Windows (with WSL or Git Bash), while PowerShell is primarily for Windows users.
- If possible, provide a single Bash example and mention PowerShell only if there are significant differences or Windows-specific steps.
- Explicitly state cross-platform compatibility in the prerequisites section.
Container Apps
Tutorial: Enable Azure Container Apps on Azure Arc-enabled Kubernetes
...in/articles/container-apps/azure-arc-enable-cluster.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI (bash) and PowerShell examples for every step, but PowerShell is always presented as the alternative to Azure CLI, and never Bash for Linux/macOS. The CLI examples use bash syntax, but the tab structure is 'Azure CLI' and 'PowerShell', which may imply a Windows-first mindset. There are no explicit Linux/macOS-only instructions, and PowerShell is given parity with bash, even though PowerShell is primarily a Windows tool (with limited Linux/macOS adoption).
Recommendations
- Rename tabs to 'Bash (Linux/macOS)' and 'PowerShell (Windows)' to clarify OS context.
- Add explicit notes about running Azure CLI commands in Bash on Linux/macOS and in PowerShell on Windows.
- Consider providing a single Bash example first, then PowerShell for Windows users.
- Where relevant, mention Linux/macOS-specific considerations (e.g., file paths, environment variable syntax differences).
- Clarify that PowerShell is optional and that Bash is the default shell for most Linux/macOS users.
Container Apps
Connect to a container console in Azure Container Apps
...blob/main/articles/container-apps/container-console.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Bash and PowerShell examples for all Azure CLI commands, ensuring cross-platform coverage. However, PowerShell examples are given equal prominence to Bash, which may be unnecessary since Bash is the default shell on Linux/macOS and PowerShell is primarily used on Windows. There is a slight 'windows_first' bias in the sense that PowerShell examples are always present, even though Bash is sufficient for Linux/macOS users. No Windows-only tools or patterns are mentioned, and Linux examples are not missing.
Recommendations
- Consider making Bash examples the default and PowerShell examples collapsible or secondary, as Bash is the primary shell for Linux/macOS users.
- Add a note clarifying that Bash commands work on Linux/macOS and Windows (with WSL or Git Bash), while PowerShell is mainly for Windows users.
- If space is a concern, provide Bash examples first and link to PowerShell equivalents for Windows users.
- Explicitly mention cross-platform compatibility of Azure CLI commands.
Container Apps
Azure Container Apps ARM and YAML template specifications
...cles/container-apps/azure-resource-manager-api-spec.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page shows mild Windows bias: Azure PowerShell is mentioned as a primary update method for management tools, and Windows tooling (PowerShell) is referenced before Linux alternatives. However, all code examples use platform-neutral formats (ARM JSON, YAML), and CLI instructions use Azure CLI, which works cross-platform. No critical sections are Windows-only, and Linux/macOS users can follow all instructions without friction.
Recommendations
- When mentioning Azure PowerShell, also explicitly mention Bash or cross-platform shell usage for Azure CLI.
- Clarify that Azure CLI commands work on Linux/macOS and Windows equally.
- If referencing installation or upgrade instructions, provide links or commands for Linux/macOS alongside Windows/PowerShell.
- Avoid listing Windows tools (PowerShell) before cross-platform alternatives unless contextually necessary.
Container Apps
Deploy the Dapr extension for Azure Functions in Azure Container Apps
...in/articles/container-apps/dapr-functions-extension.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both PowerShell and curl examples for API invocation and log retrieval, but consistently lists PowerShell examples first. This ordering subtly prioritizes Windows tooling. However, Linux/macOS users are not blocked, as curl examples are present and all Azure CLI commands are cross-platform.
Recommendations
- Alternate the order of PowerShell and curl examples, or present curl first to better reflect cross-platform usage.
- Explicitly mention that all Azure CLI and curl commands work on Linux/macOS, and provide any necessary notes for environment differences.
- Consider adding bash script examples for more complex workflows, if applicable.
- Clarify that PowerShell examples are also usable on Linux/macOS where PowerShell Core is installed, or link to installation instructions.
Container Apps
Quickstart: Deploy your first container app with containerapp up
...-docs/blob/main/articles/container-apps/get-started.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for the main Azure CLI command, but PowerShell (Windows) is given equal prominence to Bash, and there are no Linux/macOS-specific notes or troubleshooting tips. The order of examples places Bash first, but the presence of a dedicated PowerShell tab and lack of explicit Linux/macOS guidance may create minor friction for non-Windows users.
Recommendations
- Add explicit Linux/macOS troubleshooting notes (e.g., common permission issues, shell differences).
- Clarify that Bash examples apply to Linux/macOS and WSL environments.
- Consider including a note or tab for macOS if there are any platform-specific considerations.
- Ensure that any referenced screenshots or instructions are not Windows-specific.
- If PowerShell is included, mention that it is primarily for Windows users and provide guidance for Linux users who may use Bash or Zsh.
Container Apps
Generate GitHub Actions workflow with Azure CLI in Azure Container Apps
...lob/main/articles/container-apps/github-actions-cli.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for all Azure CLI commands, but PowerShell examples are consistently shown immediately after Bash, and the tab structure gives equal prominence to Windows/PowerShell. There is no explicit mention of Linux/macOS-specific considerations, nor are there any Linux/macOS-only examples or troubleshooting tips. The documentation avoids Windows-only tools, but the PowerShell examples may imply a slight Windows bias, especially for users unfamiliar with PowerShell syntax.
Recommendations
- Add explicit notes clarifying that Bash examples work on Linux/macOS and Windows (with WSL or Git Bash), while PowerShell is primarily for Windows.
- Consider listing Bash examples first, as Bash is the default shell for Linux/macOS and is also available on Windows.
- Include troubleshooting tips for Linux/macOS users (e.g., file permissions, environment variables).
- Mention that Azure CLI works cross-platform and provide links to installation instructions for Linux/macOS.
- If possible, add a generic 'shell' tab or clarify that Bash commands are universal for non-Windows platforms.
Container Apps
Configure the APM Java agent with Init Containers
...apps/java-application-performance-management-config.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for all command-line steps, but PowerShell is always presented alongside Bash, and sometimes shown first in the code tabs. There is no evidence of exclusive use of Windows tools, nor are there missing Linux examples. However, the consistent inclusion of PowerShell commands and the 'tabbed' presentation may subtly prioritize Windows users or create friction for Linux/macOS users who do not use PowerShell.
Recommendations
- Ensure Bash is always presented first in tabbed code blocks, as Bash is the default shell on Linux/macOS.
- Clarify in the prerequisites that Bash examples are intended for Linux/macOS and PowerShell for Windows.
- Consider adding a note that all Azure CLI commands work in Bash on Linux/macOS and in PowerShell on Windows.
- Review whether PowerShell examples are necessary for every step, or if Bash alone suffices for cross-platform parity.
- Explicitly mention that Docker and Azure CLI are cross-platform tools, and provide troubleshooting tips for Linux/macOS users if needed.
Container Apps
Azure Container Apps image pull from Azure Container Registry with managed identity
...articles/container-apps/managed-identity-image-pull.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides both Azure CLI (Bash) and Azure PowerShell examples for all command-line procedures, but PowerShell (Windows) examples are always present and sometimes more detailed. PowerShell is mentioned as a primary tool in prerequisites and installation steps, and links to PowerShell-specific quickstarts are given equal prominence to Azure CLI. In some cases, PowerShell instructions are more verbose or come before Bash instructions. There is no evidence of missing Linux examples, but the documentation assumes PowerShell is a common tool for all users, which may not be true for Linux/macOS users.
Recommendations
- Clearly indicate that PowerShell is primarily for Windows users, and Azure CLI (Bash) is cross-platform.
- Where possible, present Bash/Azure CLI examples before PowerShell examples to reduce perceived Windows primacy.
- Add notes clarifying that PowerShell examples are optional for Linux/macOS users, who should use Bash/Azure CLI.
- Review and streamline PowerShell instructions so they are not more detailed than Bash equivalents unless necessary.
- Consider adding explicit macOS/Linux environment setup notes where relevant.
Container Apps
Monitor Azure Container Apps metrics
...zure-docs/blob/main/articles/container-apps/metrics.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation references both Azure CLI and Azure PowerShell cmdlets for retrieving metrics, but PowerShell is mentioned explicitly and linked alongside the CLI, and no Linux/macOS-specific tools or shell examples are provided. The mention of PowerShell cmdlets and the absence of Bash or Linux-native command examples indicate a mild Windows bias, especially for users unfamiliar with PowerShell or who primarily use Linux/macOS.
Recommendations
- Add explicit Bash/Linux shell examples for metric retrieval using Azure CLI.
- Clarify that Azure CLI is cross-platform and provide usage examples for Linux/macOS terminals.
- If mentioning PowerShell, also mention Bash or other common Linux shells to ensure parity.
- Consider listing Azure CLI before PowerShell, as CLI is more universally available.