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 176-198 of 198 flagged pages
Container Apps Integrate a virtual network with an Azure Container Apps environment ...-docs/blob/main/articles/container-apps/vnet-custom.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Bash (Azure CLI) and PowerShell examples throughout, ensuring Linux parity in command-line instructions. However, PowerShell examples are given equal prominence to Bash, which may reflect a slight Windows bias, especially since PowerShell is primarily a Windows tool (though it is available cross-platform). There are no examples or references to Linux-specific tools, nor are there instructions that are Windows-only. The structure does not prioritize Windows tools over Linux, but the inclusion of PowerShell in every example may create a perception of Windows-centricity.
Recommendations
  • Clarify that PowerShell examples are intended for cross-platform use, or explicitly mention that Bash examples are suitable for Linux/macOS users.
  • Consider adding a note about PowerShell Core availability on Linux/macOS, to avoid confusion.
  • If possible, provide additional context or troubleshooting tips for Linux/macOS users, especially around environment setup and permissions.
  • Ensure that Bash examples are shown first or are clearly marked as the default for Linux/macOS users.
GitHub Create Pull Request
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 →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for every step, but PowerShell is given equal prominence to Bash/Azure CLI, which is more common on Linux/macOS. There are no Linux/macOS-specific instructions or troubleshooting tips, and PowerShell is not natively available on most Linux/macOS systems. The examples do not use Linux-specific shell idioms (e.g., piping, process substitution), and Windows/PowerShell examples are always present and shown alongside Bash, sometimes with Windows-style variable assignment. There is no explicit mention of Linux/macOS tools or patterns, and no guidance for users who do not have PowerShell.
Recommendations
  • Clarify that PowerShell examples are for Windows users and Bash/Azure CLI examples are for Linux/macOS users.
  • Add explicit instructions for Linux/macOS users, such as using Bash or Zsh, and note that PowerShell is not required.
  • Consider showing Bash/Azure CLI examples first, as these are cross-platform and native to Linux/macOS.
  • Add troubleshooting notes for common Linux/macOS issues (e.g., file permissions, base64 flags differences).
  • Remove PowerShell examples or move them to a separate tab labeled 'Windows/PowerShell'.
GitHub Create Pull Request
Container Apps Tutorial: Communication between microservices in Azure Container Apps ...es/container-apps/communicate-between-microservices.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for all CLI commands, but PowerShell examples are consistently shown alongside or immediately after Bash. In some sections, PowerShell instructions are more verbose and detailed, with additional steps and object creation, which may suggest a slight preference or bias toward Windows/PowerShell workflows. However, Linux (Bash) users are not blocked from completing any tasks, and all required commands are present for both platforms.
Recommendations
  • Ensure Bash and PowerShell examples are equally detailed and comprehensive, especially in complex deployment steps.
  • Consider showing Bash examples first, as Bash is the default shell for most Linux and macOS users.
  • Where possible, provide parity in explanations and context for both Bash and PowerShell, so neither platform appears favored.
  • Add a short note at the top clarifying that both Linux/macOS (Bash) and Windows (PowerShell) users are supported equally.
GitHub Create Pull Request
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 →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both PowerShell and curl examples for HTTP requests, but PowerShell examples are consistently shown first in each tabbed section. This ordering subtly prioritizes Windows tooling. However, all critical steps (deployment, verification, log viewing, cleanup) use Azure CLI or curl, which are cross-platform. No steps are Windows-exclusive, and Linux/macOS users can complete the tutorial without friction.
Recommendations
  • Alternate the order of PowerShell and curl examples, or show curl first to better reflect cross-platform usage.
  • Explicitly mention that all CLI commands work on Linux/macOS and Windows.
  • Consider adding bash script examples for automation, or note that PowerShell commands are for Windows users.
  • Add a brief note at the start of the verification/log sections clarifying that curl is recommended for Linux/macOS users.
GitHub Create Pull Request
Container Apps Connect to a container console in Azure Container Apps ...blob/main/articles/container-apps/container-console.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
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 for most Linux/macOS users. The presence of PowerShell examples throughout the page introduces a mild Windows bias, and in some sections, PowerShell examples are listed immediately after Bash, which can subtly reinforce Windows-centric usage patterns.
Recommendations
  • Consider making Bash the primary example, with PowerShell examples available via tabs or expandable sections for Windows users.
  • Add a note clarifying that Bash commands work natively on Linux/macOS and in Windows via WSL or Git Bash, while PowerShell is specific to Windows.
  • If usage patterns differ significantly between platforms, provide platform-specific guidance, but avoid duplicating examples unless necessary.
  • Review whether PowerShell examples are needed for every command, or if a single note about CLI usage in PowerShell suffices.
GitHub Create Pull Request
Container Apps Deploy an artifact file to Azure Container Apps ...s/blob/main/articles/container-apps/deploy-artifact.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for all command-line steps, ensuring cross-platform coverage. However, PowerShell (Windows) examples are always presented second, after Bash, which is the default shell for most Linux/macOS users. There is no evidence of exclusive Windows tools or missing Linux examples, but the presence of PowerShell throughout may signal a slight Windows bias.
Recommendations
  • Consider explicitly mentioning macOS compatibility alongside Linux in Bash sections.
  • Add a note clarifying that Bash instructions apply to both Linux and macOS users.
  • If possible, provide a single unified Bash example when commands are identical, reducing duplication and emphasizing cross-platform parity.
  • Ensure that any troubleshooting or tips sections include Linux/macOS-specific advice if relevant.
GitHub Create Pull Request
Container Apps Configure the APM Java agent with Init Containers ...apps/java-application-performance-management-config.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Bash and PowerShell examples for every command, ensuring that both Linux/macOS and Windows users are supported. However, PowerShell is given equal prominence to Bash throughout, which is uncommon for Linux/macOS users, and may create friction for those unfamiliar with PowerShell. In some sections, PowerShell examples are shown immediately after Bash, rather than Bash-only or Bash-first, which is a subtle form of Windows bias.
Recommendations
  • Consider making Bash the default or primary example, with PowerShell as a secondary tab or footnote, since Bash is the standard shell on Linux/macOS and Azure Cloud Shell.
  • Explicitly note that Bash examples work on Linux/macOS and Azure Cloud Shell, while PowerShell is primarily for Windows users.
  • Add a short section clarifying which shell is recommended for each platform.
  • Where possible, avoid presenting PowerShell as equally standard for Linux/macOS users.
GitHub Create Pull Request
Container Apps Quickstart: Build and deploy your app from your local filesystem to Azure Container Apps ...in/articles/container-apps/quickstart-code-to-cloud.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
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 to Bash, which may reflect a slight Windows bias. There are no Linux-specific tools, patterns, or troubleshooting steps mentioned, and no explicit mention of macOS. However, Bash examples are present throughout, and no critical steps are Windows-only.
Recommendations
  • Explicitly mention that Bash instructions apply to Linux and macOS users.
  • Add a note clarifying that PowerShell examples are for Windows users, while Bash is for Linux/macOS.
  • Consider including troubleshooting tips for common Linux/macOS issues (e.g., permissions, environment variable persistence).
  • Ensure parity in guidance for installing prerequisites (e.g., Azure CLI installation steps for Linux/macOS).
GitHub Create Pull Request
Container Apps Manage revisions in Azure Container Apps .../blob/main/articles/container-apps/revisions-manage.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Bash (Azure CLI) and PowerShell examples for all commands, ensuring cross-platform coverage. However, PowerShell examples are present for every command, and in some cases, PowerShell-specific cmdlets are used (e.g., Update-AzContainerApp), which are only available on Windows or require PowerShell Core on other platforms. Additionally, PowerShell tabs are always present, and in some sections, PowerShell examples use native cmdlets rather than the CLI, which may not be as accessible to Linux/macOS users. The order of tabs is Bash first, then PowerShell, which is good, but the heavy presence of PowerShell may create a perception of Windows bias.
Recommendations
  • Clearly indicate that PowerShell examples using Az cmdlets require PowerShell Core and the Az module, and note their cross-platform compatibility.
  • Where PowerShell examples use Azure CLI commands, clarify that these can be run in any shell, not just PowerShell.
  • Consider adding explicit Linux/macOS notes or examples where PowerShell cmdlets are not available or not cross-platform.
  • If possible, provide Bash-only or POSIX shell examples for all tasks, especially where PowerShell cmdlets are used.
  • Add a brief section at the top explaining the cross-platform nature of Azure CLI and PowerShell, and any limitations.
GitHub Create Pull Request
Container Apps Azure Container Apps image pull from Azure Container Registry with managed identity ...articles/container-apps/managed-identity-image-pull.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides examples for both Azure CLI (Bash) and Azure PowerShell, but PowerShell examples are consistently present and often detailed, reflecting a Windows-centric approach. PowerShell is mentioned as a primary tool for automation and scripting, and installation instructions for PowerShell are given equal or greater prominence compared to Bash/CLI. In some sections, PowerShell examples are shown before Bash, and PowerShell-specific modules and commands are referenced throughout. There is no mention of Linux/macOS-specific shell environments or alternative tools, and no troubleshooting or guidance for non-Windows platforms beyond Bash/CLI.
Recommendations
  • Ensure Bash/Azure CLI examples are always shown first, or alternate order to avoid implicit prioritization.
  • Add explicit notes or troubleshooting for Linux/macOS users, especially regarding PowerShell installation and compatibility.
  • Include references to native Linux/macOS tools or workflows where relevant (e.g., using Bash scripts, zsh, etc.).
  • Clarify that PowerShell is cross-platform, but highlight any platform-specific caveats.
  • Where PowerShell is required, provide guidance for installation on Linux/macOS, and link to official docs for those platforms.
  • Consider including examples using other popular automation tools (e.g., Terraform, Ansible) for parity.
GitHub Create Pull Request
Container Apps Quickstart: Build and deploy from a repository to Azure Container Apps ...in/articles/container-apps/quickstart-repo-to-cloud.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Bash and PowerShell examples for all CLI commands, ensuring parity for Linux/macOS and Windows users. However, PowerShell is given equal prominence as Bash, which may be interpreted as a slight Windows bias, especially since PowerShell is primarily a Windows shell (though available on Linux/macOS). There are no Windows-only tools or patterns, and Linux/macOS users are not blocked from completing any tasks.
Recommendations
  • Clarify that PowerShell examples are for users on Windows, while Bash examples are for Linux/macOS.
  • Consider listing Bash examples first, as Bash is the default shell on most Linux/macOS systems.
  • Add a note that Bash commands work in WSL/Windows Terminal for Windows users who prefer a Linux-like environment.
  • Ensure that any future troubleshooting or advanced sections do not introduce Windows-only tools or instructions.
GitHub Create Pull Request
Container Apps Tutorial: Create an Azure Files volume mount in Azure Container Apps .../articles/container-apps/storage-mounts-azure-files.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for every command, ensuring parity for Linux/macOS and Windows users. However, PowerShell examples are given equal prominence to Bash, and in some cases, Windows-specific patterns (such as PowerShell variable assignment and command continuation) are shown. There is no exclusive use of Windows tools or missing Linux examples, but the dual-tab approach may slightly favor Windows by always including PowerShell, even for tasks that are natively Bash-oriented on Linux/macOS.
Recommendations
  • Consider making Bash the default or first tab in code examples, as Bash is the native shell for Linux/macOS and is also available on Windows via WSL.
  • Clarify in the prerequisites that Bash examples are suitable for Linux/macOS and Windows users with WSL, while PowerShell is for native Windows users.
  • Add a note about using Azure CLI in WSL or Git Bash on Windows for users who prefer Bash.
  • Ensure that any platform-specific nuances (e.g., file redirection, environment variable syntax) are explained for both shells.
GitHub Create Pull Request
Container Apps Troubleshooting in Azure Container Apps ...s/blob/main/articles/container-apps/troubleshooting.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation shows mild Windows bias, primarily in the troubleshooting steps for verifying container image accessibility, where instructions reference running Docker in an 'elevated command prompt' and link to Docker's Windows installation guide. PowerShell examples are provided for updating modules, and references to Azure PowerShell cmdlets are present. While Bash/Azure CLI examples are included, Windows-specific terminology and tools are mentioned first or exclusively in some sections. There are no explicit Linux/macOS troubleshooting steps or references to their environments.
Recommendations
  • Add explicit instructions and links for running Docker commands on Linux/macOS, including references to their installation guides.
  • Replace 'elevated command prompt' with platform-neutral language, such as 'terminal' or specify both Windows and Linux/macOS equivalents.
  • Provide parity in examples: for every PowerShell example, include a Bash or shell equivalent where possible.
  • Mention Linux/macOS environments when discussing prerequisites or troubleshooting steps, especially for Docker and Azure CLI usage.
  • Ensure that links to external tools (like Docker) include both Windows and Linux/macOS installation guides.
GitHub Create Pull Request
Container Apps Tutorial: Scale an Azure Container Apps application .../blob/main/articles/container-apps/tutorial-scaling.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for all Azure CLI commands, but consistently lists Bash first. However, in the 'Send requests' section, the PowerShell example is significantly more complex and uses advanced Windows/PowerShell-specific constructs (RunspacePool, Invoke-WebRequest), while the Bash example uses standard Linux utilities (seq, xargs, curl). No Linux/macOS-specific tools or patterns are omitted, and all tasks can be completed on Linux/macOS using the provided Bash instructions. There is no evidence of exclusive Windows tools or missing Linux examples.
Recommendations
  • Consider providing a simpler PowerShell example for sending concurrent requests, or note that Bash/Linux users can use parallel or other utilities if desired.
  • Explicitly mention that Bash examples work on Linux and macOS, and that PowerShell examples are for Windows users.
  • Add a brief note at the start clarifying cross-platform parity and which shell to use on each OS.
  • Where possible, provide parity in complexity between Bash and PowerShell examples, or explain differences.
  • If relevant, mention alternative Linux tools (e.g., GNU parallel) for advanced concurrency.
GitHub Create Pull Request
Container Apps Tutorial: Run GitHub Actions runners and Azure Pipelines agents with Azure Container Apps jobs ...articles/container-apps/tutorial-ci-cd-runners-jobs.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Bash and PowerShell examples for all CLI commands, ensuring parity for Linux/macOS and Windows users. However, PowerShell examples are always shown alongside Bash, and in some cases, Windows-specific advice (e.g., using Mono or Windows containers for .NET Framework builds) is given before Linux alternatives. The troubleshooting section suggests Windows containers as a solution for .NET Framework, which may reinforce a Windows-centric mindset. There are no sections that are Windows-only, and Linux users can complete all tasks using Bash and Azure CLI.
Recommendations
  • Consider listing Bash examples before PowerShell throughout the documentation to reflect the default shell on Linux/macOS and most CI/CD environments.
  • When suggesting solutions for .NET Framework builds, present Linux/Mono options before Windows containers, and clarify the trade-offs.
  • Explicitly mention that all Azure CLI commands work on Linux/macOS and Windows, and provide links to platform-specific installation guides if needed.
  • Where troubleshooting suggests Windows containers, provide equal detail for Linux/Mono solutions and clarify when Windows containers are strictly required.
  • Add a short note at the beginning confirming full support for Linux/macOS workflows.
GitHub Create Pull Request
Container Apps Integrate a virtual network with an Azure Container Apps environment ...-docs/blob/main/articles/container-apps/vnet-custom.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Bash (Azure CLI) and PowerShell examples for all major steps, ensuring Linux parity in command-line instructions. However, PowerShell examples are given equal prominence throughout, and in some sections (such as resource cleanup), PowerShell is presented immediately after Bash, which may subtly reinforce Windows as a primary platform. There is no evidence of exclusive Windows tools or missing Linux examples, but the consistent inclusion of PowerShell may be unnecessary for Linux/macOS-focused users.
Recommendations
  • Consider making Bash/Azure CLI examples the default or primary example, as Azure CLI is cross-platform and more commonly used on Linux/macOS.
  • Move PowerShell examples to a separate tab or section labeled 'Windows/PowerShell users' to clarify platform relevance.
  • Add a note at the beginning clarifying that Azure CLI commands work on Linux, macOS, and Windows, while PowerShell is primarily for Windows users.
  • Ensure that all instructions and screenshots (if any) are platform-neutral or include Linux/macOS variants where appropriate.
GitHub Create Pull Request
Container Apps Tutorial: Communication between microservices in Azure Container Apps ...es/container-apps/communicate-between-microservices.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
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 and, in some sections (notably the 'Deploy front end application'), the PowerShell workflow is much more verbose and detailed than the Bash equivalent. There is a slight 'Windows-first' bias in the sense that PowerShell is treated as the main alternative to Bash, with no mention of Linux-specific tools or workflows beyond Bash, and PowerShell examples are sometimes more elaborate, potentially making Windows users feel more supported.
Recommendations
  • Ensure that Bash and PowerShell instructions are equally detailed, especially for complex workflows.
  • Consider adding explicit notes about Linux/macOS compatibility, and clarify that Bash instructions work on both Linux and macOS.
  • Where PowerShell examples require additional steps, provide equivalent Bash guidance if relevant.
  • Mention that PowerShell Core is available cross-platform, but clarify that Bash is the default shell for Linux/macOS.
  • If possible, add troubleshooting tips for Linux/macOS users (e.g., permissions, environment variable syntax differences).
GitHub Create Pull Request
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 →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
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 always shown immediately after Bash, and the PowerShell syntax is given equal prominence. There are no Windows-only tools or patterns, but the presence of PowerShell examples may suggest a slight Windows bias, especially since macOS/Linux users would only use Bash.
Recommendations
  • Make it clear that Bash examples are for Linux/macOS and PowerShell for Windows, perhaps with a short note at the top.
  • Consider showing Bash examples first and making them the default, as Azure CLI is cross-platform and Bash is more universal.
  • Optionally, collapse PowerShell examples by default or move them to a separate section for Windows users.
  • Add a brief note about running Azure CLI in Bash on Windows (e.g., via WSL) for parity.
GitHub Create Pull Request
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
Low Priority View Details →
Scanned: 2025-07-13 21:37
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any OS-specific troubleshooting steps or examples, but it also omits any mention of Linux tools, commands, or patterns. While it avoids explicit Windows bias (no Windows/Powershell examples or tools are given), it also fails to address Linux users or provide parity for Linux troubleshooting approaches.
Recommendations
  • Add examples of how to troubleshoot storage mount failures from within a Linux-based container, such as using 'ls', 'mount', or 'df' commands to verify mount points.
  • Include sample error messages or logs that might be seen in Linux environments (e.g., from /var/log or container stdout/stderr).
  • If relevant, mention how to use Linux-native tools (e.g., bash, sh, cat, tail) to inspect mount status or debug issues.
  • Clarify whether the troubleshooting steps apply equally to both Windows and Linux containers, or provide separate guidance if there are differences.
GitHub Create Pull Request
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
Low Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any OS-specific troubleshooting commands, examples, or tools. However, it also omits any mention of Linux-specific tools or command-line instructions, which may be relevant since containers often run on Linux. The absence of both Windows and Linux examples means there is no explicit Windows bias, but the lack of Linux parity (e.g., shell commands, log file locations) is a missed opportunity.
Recommendations
  • Add example troubleshooting steps using common Linux commands (e.g., checking mount points with 'mount' or 'df', inspecting logs with 'cat /var/log/syslog', etc.).
  • Include references to both Linux and Windows environments if relevant, clarifying any OS-specific behaviors or error messages.
  • Provide sample error messages or diagnostic outputs from both Linux-based and Windows-based containers, if supported.
  • Mention where to find logs or diagnostic information inside the container for both Linux and Windows containers.
GitHub Create Pull Request
Container Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/rule-based-routing.md ...lob/main/articles/container-apps/rule-based-routing.md
Low Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation uses Azure CLI examples throughout, which are generally cross-platform. However, there is a subtle Windows bias in the Bicep deployment section: the CLI example for deploying the Bicep file uses PowerShell-style backticks (`) for line continuation, which is specific to Windows/PowerShell. No equivalent Bash (Linux/macOS) example is provided. Additionally, references to 'cmdlets from the Az.App module in PowerShell' are mentioned before CLI commands, and there is no explicit mention of Linux shell usage or examples.
Recommendations
  • For all CLI command examples, provide both Bash (\) and PowerShell (`) line continuation variants, or use single-line commands to avoid platform-specific syntax.
  • When mentioning PowerShell modules or cmdlets, also mention Bash/Azure CLI equivalents, and clarify which environments each applies to.
  • Explicitly state that all Azure CLI commands work on Linux, macOS, and Windows, and provide any necessary notes for cross-platform usage.
  • Where environment variables are set, clarify syntax differences (e.g., $VAR for Bash, $env:VAR for PowerShell) if relevant.
  • Consider adding a 'Platform differences' note or section to highlight any OS-specific considerations.
GitHub Create Pull Request
Container Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/dotnet-overview.md ...s/blob/main/articles/container-apps/dotnet-overview.md
Low Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation page does not show explicit Windows bias in terms of mentioning Windows tools, PowerShell, or Windows-first patterns. However, it lacks Linux-specific examples, commands, or references, and does not address cross-platform development or deployment nuances. The documentation implicitly assumes a platform-agnostic environment but misses opportunities to demonstrate parity by including Linux (or macOS) specific instructions or considerations.
Recommendations
  • Add explicit examples or notes for Linux/macOS users, such as common CLI commands (e.g., docker, az CLI) run from Bash or zsh.
  • Clarify that the instructions and code samples are cross-platform, and mention any platform-specific prerequisites or differences where relevant.
  • Include references to developing and deploying from Linux or macOS environments, not just Visual Studio (which is Windows-centric), such as Visual Studio Code or JetBrains Rider.
  • If any tooling or configuration steps differ between Windows and Linux containers (e.g., file system paths, environment variable syntax), call these out explicitly.
  • Provide links to official .NET and Azure documentation that cover Linux containerization and deployment workflows.
GitHub Create Pull Request
Container Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/waf-app-gateway.md ...s/blob/main/articles/container-apps/waf-app-gateway.md
Low Priority View Details →
Scanned: 2025-07-08 04:23
Reviewed by: Unknown
Issues: 1 bias type
Detected Bias Types
Missing Linux Example
Summary
The documentation exclusively uses Azure Portal (GUI) instructions and does not provide any command-line examples for either Windows (PowerShell/CLI) or Linux (Bash/CLI). However, this omission results in a lack of parity for Linux users, as there are no Bash/Azure CLI examples, which are commonly used on Linux. There is no explicit Windows bias (no PowerShell, Windows tools, or Windows-first ordering), but the absence of CLI examples is a missed opportunity to support Linux workflows.
Recommendations
  • Add Azure CLI (Bash) command-line examples for all major steps (e.g., creating DNS zones, Application Gateway, backend pools, routing rules, and resource cleanup).
  • Where possible, provide both Azure CLI and PowerShell equivalents, but ensure CLI (Bash) examples are present and not secondary.
  • Explicitly mention that all steps can be performed via CLI on Linux, and link to relevant Azure CLI documentation.
  • Consider adding a 'Command-line (CLI)' tab alongside the GUI instructions for each major section.
GitHub Create Pull Request
← Previous Page 8 of 8 Next →