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 101-125 of 198 flagged pages
Container Apps Tutorial: Communication between microservices in Azure Container Apps ...es/container-apps/communicate-between-microservices.md
Medium Priority View Details →
Scanned: 2026-01-10 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 command-line steps, ensuring parity between Linux and Windows users. However, PowerShell examples are often more verbose and detailed, especially in the deployment section, where the PowerShell workflow uses multiple custom objects and steps, while the Bash workflow is a single command. In some sections, PowerShell instructions are presented after Bash, but the PowerShell content is more extensive, which may give the impression of a Windows bias in terms of depth and guidance.
Recommendations
  • Ensure Bash and PowerShell examples are equally detailed, especially for complex workflows like container app deployment.
  • Where possible, simplify PowerShell examples to match the Bash workflow, or provide expanded Bash examples for parity.
  • Consider adding explicit notes about cross-platform compatibility and clarify that Bash commands work on Linux, macOS, and Windows (via WSL or Git Bash).
  • If advanced PowerShell usage is shown, provide equivalent advanced Bash scripting for users who need more control.
  • Review the order and prominence of examples to avoid giving the impression that Windows/PowerShell is the preferred or default platform.
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
Medium Priority View Details →
Scanned: 2026-01-10 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 API invocation and log retrieval, but consistently lists PowerShell examples before curl, which may subtly prioritize Windows users. There is no explicit mention of Linux-specific tools or workflows, and PowerShell is featured as a primary tab, suggesting a Windows-first approach. However, Azure CLI and curl commands are cross-platform, and no Windows-only tools are required.
Recommendations
  • Alternate the order of PowerShell and curl examples, or list curl first to better reflect Linux usage patterns.
  • Explicitly state that all CLI and curl commands work on Linux, macOS, and Windows.
  • Add bash script examples for common tasks, such as resource cleanup, to further support Linux users.
  • Mention Linux-specific considerations or troubleshooting tips where relevant.
  • Clarify that PowerShell examples are optional and provide equivalent bash/curl commands for every step.
GitHub Create Pull Request
Container Apps Quickstart: Deploy an existing container image with the command line ...container-apps/get-started-existing-container-image.md
Medium Priority View Details →
Scanned: 2026-01-10 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 major steps, which is positive for cross-platform parity. However, PowerShell examples are given equal prominence to Bash, and in some cases, PowerShell-specific instructions (such as installing the Az.KeyVault module) are included, while Linux-specific nuances (such as shell environment differences or package installation) are not mentioned. The documentation assumes familiarity with PowerShell and Windows tooling, and does not address Linux-specific patterns or troubleshooting. The order of presentation sometimes places PowerShell before or alongside Bash, rather than Bash (Linux/macOS) first, which is more typical for cross-platform cloud documentation.
Recommendations
  • Present Bash (Linux/macOS) examples before PowerShell (Windows) examples to reflect the majority of cloud-native developer environments.
  • Include Linux-specific notes where PowerShell-specific instructions are given (e.g., mention package managers or shell differences for Bash users).
  • Add troubleshooting tips for Bash/Linux environments, such as permissions, environment variable persistence, or common CLI issues.
  • Clarify that PowerShell examples are primarily for Windows users, and Bash for Linux/macOS, to guide users to the most relevant instructions.
  • Review included modules and steps for parity—if PowerShell requires a module install, note any equivalent Bash prerequisites (e.g., Azure CLI extensions).
GitHub Create Pull Request
Container Apps Configure the APM Java agent with Init Containers ...apps/java-application-performance-management-config.md
Medium Priority View Details →
Scanned: 2026-01-10 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, but consistently lists Bash first, followed by PowerShell. There is no evidence of exclusive use of Windows tools or patterns, nor are Windows-specific tools mentioned before Linux equivalents. However, the presence of PowerShell examples throughout the document indicates a bias toward Windows users, as Linux users would typically use Bash. No Linux-specific tools or instructions are missing, and the Dockerfile and shell scripts are written in a Linux-compatible way.
Recommendations
  • Consider clarifying that PowerShell examples are for Windows users and Bash for Linux/macOS users, to help readers choose the appropriate instructions.
  • Add a note explaining that Bash commands work natively on Linux/macOS and in Windows environments with WSL or Git Bash.
  • If possible, provide guidance for users running Azure CLI in native Windows Command Prompt (cmd.exe), or clarify that PowerShell is the recommended shell for Windows.
  • Ensure that any platform-specific nuances (such as file path formats or environment variable syntax) are explicitly called out.
  • Continue to provide parity between Bash and PowerShell examples, but consider adding a short section on cross-platform shell usage for Azure CLI.
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
Medium Priority View Details →
Scanned: 2026-01-10 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 environment variable setup, deployment, and cleanup, but consistently lists Bash first and PowerShell second. There is no evidence of exclusive use of Windows tools or missing Linux examples; both platforms are covered equally in command-line instructions. However, the presence of PowerShell examples throughout, and the explicit mention of PowerShell as a tab, may signal a slight Windows bias, especially since PowerShell is primarily a Windows shell (though available on Linux). There are no Windows-only tools or patterns, and Linux users are not excluded from any steps.
Recommendations
  • Clarify that PowerShell examples are also valid for PowerShell Core on Linux, to avoid implying Windows exclusivity.
  • Consider adding a note about shell compatibility for each tab, e.g., 'Bash (Linux/macOS/WSL)' and 'PowerShell (Windows/PowerShell Core on Linux/macOS)'.
  • Ensure that any troubleshooting or tips sections mention platform-specific issues for both Windows and Linux users.
  • If possible, include a brief mention of WSL for Windows users who prefer a Linux-like environment.
GitHub Create Pull Request
Container Apps Tutorial: Scale an Azure Container Apps application .../blob/main/articles/container-apps/tutorial-scaling.md
Medium Priority View Details →
Scanned: 2026-01-10 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, ensuring parity for Windows and Linux users in most sections. However, in the 'Send requests' section, the PowerShell example is significantly more complex and uses advanced Windows-specific constructs (RunspacePool, PowerShell objects), while the Bash example uses standard Linux utilities (seq, xargs, curl). Additionally, instructions for opening a shell are phrased as 'Open a new bash shell' for Bash and 'Open a new command prompt and enter PowerShell' for PowerShell, subtly prioritizing Windows terminology. The PowerShell examples are always presented immediately after Bash, but never omitted, which can be interpreted as a mild 'windows_first' bias, especially given the complexity and length of the PowerShell examples compared to their Bash counterparts.
Recommendations
  • Provide a simpler PowerShell example using basic loops and Invoke-WebRequest, if possible, to match the simplicity of the Bash example.
  • Explicitly mention that Bash commands work in Linux, macOS, and Windows (via WSL or Git Bash), to clarify cross-platform applicability.
  • Consider including a note about using Windows Subsystem for Linux (WSL) or Git Bash on Windows for users who prefer Bash commands.
  • Ensure that instructions for opening shells are platform-neutral (e.g., 'Open a new terminal window' instead of 'command prompt').
  • Where possible, offer parity in command complexity and explanation between Bash and PowerShell examples.
GitHub Create Pull Request
Container Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/azure-resource-manager-api-spec.md ...cles/container-apps/azure-resource-manager-api-spec.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page demonstrates mild Windows bias by mentioning Azure PowerShell (a Windows-centric tool) alongside Azure CLI, and by providing instructions and links for updating Azure PowerShell before mentioning SDKs for other languages. There are no explicit PowerShell command examples, but the reference to PowerShell and the order of presentation (CLI and PowerShell before SDKs) reflect a subtle Windows-first orientation. All code examples are platform-neutral (ARM, YAML, JSON), and there are no missing Linux-specific examples or exclusive use of Windows tools.
Recommendations
  • Add explicit mention that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Provide update instructions for Azure CLI and Azure PowerShell in parallel, clarifying platform applicability.
  • Include links or notes for Bash shell usage and Linux-specific considerations where relevant.
  • Ensure that any future command-line examples include both PowerShell and Bash syntax when appropriate.
  • Consider listing SDKs and tools in alphabetical order or by platform neutrality to avoid implicit prioritization.
GitHub Create Pull Request
Container Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/communicate-between-microservices.md ...es/container-apps/communicate-between-microservices.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
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, maintaining parity in command-line instructions. However, the PowerShell examples are often more verbose and detailed, especially in the 'Deploy front end application' section, where the PowerShell workflow is described with multiple custom objects and steps, while Bash uses a single CLI command. Additionally, PowerShell examples are given equal prominence to Bash, which may reflect a slight Windows bias, as PowerShell is primarily a Windows tool (though available on Linux). There are no Linux-specific tools or patterns mentioned, and no Linux-only examples. The documentation avoids exclusive use of Windows tools but does present PowerShell workflows that are more complex and detailed than their Bash counterparts.
Recommendations
  • Provide equivalent Bash examples for complex deployment workflows, such as using ARM templates or az CLI with JSON input, to match the detail given in PowerShell.
  • Add notes clarifying that PowerShell is available cross-platform, but Bash is the default shell on most Linux systems.
  • Consider including Linux-specific troubleshooting tips or environment setup instructions, especially for Docker and Azure CLI usage.
  • Ensure that Bash examples are as detailed as PowerShell ones, especially for advanced scenarios, to avoid implying that PowerShell is the preferred or more capable option.
GitHub Create Pull Request
Container Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/azure-arc-enable-cluster.md ...in/articles/container-apps/azure-arc-enable-cluster.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
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 featured as a first-class option throughout, which is primarily a Windows shell. There are no explicit Linux shell examples (e.g., bash scripts), and PowerShell is presented alongside Azure CLI in all code tabs, despite Azure CLI being cross-platform and PowerShell being Windows-centric for most users. Additionally, some environment variable handling and command syntax (e.g., use of $VAR vs. $VAR=) may be confusing for Linux users, and there is no mention of Linux-specific patterns or troubleshooting.
Recommendations
  • Remove PowerShell examples or move them to a separate section, making Azure CLI/bash the default and primary example.
  • Explicitly mention that Azure CLI commands are cross-platform and provide bash-specific syntax for environment variables and scripting.
  • Add troubleshooting notes for Linux users, such as handling file permissions, differences in base64 encoding flags (e.g., -w0 vs. --wrap=0), and shell compatibility.
  • Include a note clarifying that PowerShell examples are intended for Windows users, and recommend bash for Linux/macOS.
  • Where environment variables are set, use export statements for bash and clarify differences with PowerShell.
  • Ensure that any references to tools or patterns (e.g., load balancer setup, file paths) include Linux equivalents or considerations.
GitHub Create Pull Request
Container Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/dapr-functions-extension.md ...in/articles/container-apps/dapr-functions-extension.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
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 API invocation and log retrieval, but consistently lists PowerShell examples first and uses PowerShell-specific syntax. There is no explicit mention of Linux or bash usage, and the structure may implicitly prioritize Windows users by defaulting to PowerShell tabs before curl. No Linux-specific tools or troubleshooting steps are provided.
Recommendations
  • Alternate the order of PowerShell and curl examples, or default to curl/bash first to better support Linux users.
  • Explicitly mention that curl commands work on Linux, macOS, and Windows (with WSL or Git Bash), and clarify PowerShell is for Windows.
  • Add bash-specific examples or troubleshooting notes for common Linux environments.
  • Where possible, use platform-neutral commands (e.g., curl, az CLI) as the primary example, and offer PowerShell as an alternative.
  • Include a note in the prerequisites section about supported platforms and shell environments.
GitHub Create Pull Request
Container Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/get-started.md ...-docs/blob/main/articles/container-apps/get-started.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
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 the Azure CLI command, but PowerShell is given equal prominence to Bash, which is not typical for cross-platform parity. There is no explicit Linux example or mention of Linux-specific considerations, and the PowerShell example may be interpreted as Windows-centric. The documentation does not mention Linux tools or patterns, nor does it provide troubleshooting or environment setup guidance for Linux users.
Recommendations
  • Clearly indicate that Bash examples are intended for Linux/macOS and PowerShell for Windows, to help users choose the appropriate tab.
  • Add explicit Linux/macOS instructions or troubleshooting notes, such as verifying Azure CLI installation on Linux, or handling permissions.
  • Consider making Bash the default or first tab, as Bash is the standard shell on Linux/macOS and is also available on Windows via WSL.
  • Include a note about running Azure CLI commands in WSL or native Linux environments.
  • Provide parity in troubleshooting tips for Linux users, such as common issues with package managers or environment variables.
GitHub Create Pull Request
Container Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/java-application-performance-management-config.md ...apps/java-application-performance-management-config.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
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 command-line steps, but PowerShell is featured as a first-class option throughout, which may reflect a Windows-centric approach. There is no evidence of exclusive use of Windows tools or missing Linux examples, but the presence of PowerShell tabs and examples in every step suggests a bias toward Windows users. No Windows-only tools or patterns are mentioned, and all instructions are compatible with Linux environments.
Recommendations
  • Consider making Bash the default or first example in each code block, as Bash is the native shell for Linux and most containers.
  • Add a note clarifying that Bash examples are suitable for Linux/macOS and most container environments, while PowerShell is primarily for Windows users.
  • Review whether PowerShell examples are necessary for every step, or if a single section explaining PowerShell usage would suffice.
  • Ensure that any references to file paths, environment variables, or shell scripting do not assume Windows conventions.
  • Explicitly mention Linux compatibility in the prerequisites and setup sections to reassure non-Windows users.
GitHub Create Pull Request
Container Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/log-streaming.md ...ocs/blob/main/articles/container-apps/log-streaming.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
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 presented immediately after Bash, and the use of PowerShell is emphasized as the only Windows shell option. There is no mention of Linux-specific tools, patterns, or alternative shells (e.g., zsh, fish), nor is there guidance for Linux users beyond Bash. The documentation also uses Windows-style line continuation in PowerShell examples, which may reinforce a Windows-centric approach.
Recommendations
  • Explicitly mention that Bash examples are suitable for Linux/macOS users and that PowerShell examples are for Windows users.
  • Consider adding a note or section for Linux users, highlighting any differences or tips for running Azure CLI commands on Linux (e.g., shell compatibility, line continuation).
  • Include alternative shell examples or guidance (e.g., zsh, fish) for Linux users, if relevant.
  • Ensure that Bash examples are clearly marked as the default for cross-platform usage, and clarify that PowerShell is primarily for Windows environments.
  • Add troubleshooting tips for common Linux issues (e.g., permissions, environment variables) when using Azure CLI.
GitHub Create Pull Request
Container Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/revisions-manage.md .../blob/main/articles/container-apps/revisions-manage.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
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 every command, ensuring that both Linux and Windows users are supported. However, PowerShell examples are consistently present, and in some cases, PowerShell-specific Azure modules (e.g., Update-AzContainerApp, Enable-AzContainerAppRevision) are used, which are primarily Windows-centric. Additionally, PowerShell examples are given equal prominence as Bash, sometimes with more detailed parameterization, indicating a slight Windows bias. There are no Linux-specific tools or patterns (e.g., shell scripting, piping, jq usage) shown, and PowerShell is featured as a first-class citizen throughout.
Recommendations
  • Add Linux-specific examples or tips, such as using jq for JSON parsing, or shell scripting for automation.
  • Include notes about cross-platform compatibility of Azure CLI and PowerShell, clarifying that PowerShell Core can run on Linux and macOS.
  • Consider providing examples in other popular shells (e.g., zsh, fish) or scripting languages used on Linux.
  • Where PowerShell modules are used, clarify if they are available cross-platform or provide alternative CLI-only workflows.
  • Explicitly mention that Bash examples are suitable for Linux/macOS and that PowerShell examples are for Windows or PowerShell Core users.
GitHub Create Pull Request
Container Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/communicate-between-microservices.md ...es/container-apps/communicate-between-microservices.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
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 in command-line instructions. However, PowerShell is featured as the only Windows shell, and its examples are often more verbose and detailed, especially in the deployment section. The PowerShell workflow is described with additional object creation steps, which may suggest a Windows-centric approach. There are no Linux-specific tools or patterns mentioned, and Bash is used generically for Unix-like systems without explicit reference to Linux distributions or their unique considerations.
Recommendations
  • Add explicit references to Linux environments (e.g., Ubuntu, CentOS) where relevant, especially in setup or troubleshooting sections.
  • Include examples or notes for other Windows shells (e.g., Command Prompt) or clarify that PowerShell is recommended for Windows users.
  • Provide troubleshooting tips or environment-specific notes for common Linux distributions to improve parity.
  • Ensure that Bash examples are tested and compatible with popular Linux shells (e.g., zsh, dash) and mention any differences if applicable.
  • Consider adding a table or section that summarizes differences or considerations between Windows and Linux environments for Azure CLI usage.
GitHub Create Pull Request
Container Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/dapr-functions-extension.md ...in/articles/container-apps/dapr-functions-extension.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents command-line examples in both PowerShell and curl, but PowerShell examples are consistently listed first in each tabbed section. This ordering subtly prioritizes Windows users. The use of PowerShell as a primary example may be less familiar or accessible to Linux users, who typically use bash and curl. However, the presence of curl examples does provide Linux parity for the main API invocation and log retrieval steps. No exclusive Windows tools or missing Linux examples are present, and Azure CLI commands are cross-platform.
Recommendations
  • Alternate the order of PowerShell and curl examples, or present curl first to better serve Linux/macOS users.
  • Explicitly state that all Azure CLI and curl commands work on Linux, macOS, and Windows, to reinforce cross-platform compatibility.
  • Consider adding bash script examples for multi-step processes, or note how Linux users can adapt PowerShell commands if needed.
  • Avoid implying PowerShell is the default or preferred shell for all users; clarify that users can choose their preferred shell.
GitHub Create Pull Request
Container Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/get-started.md ...-docs/blob/main/articles/container-apps/get-started.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
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 the main Azure CLI command, but PowerShell is given equal prominence to Bash, which may reflect a Windows-centric approach. There is no mention of Linux-specific tools, patterns, or troubleshooting, and the structure does not prioritize Linux or cross-platform considerations. The cleanup command is shown only in Azure CLI syntax, which is cross-platform, but the overall example set leans toward Windows by including PowerShell as a primary tab.
Recommendations
  • Ensure Bash examples are presented first, as Bash is the default shell on most Linux and macOS systems.
  • Include explicit Linux/macOS verification steps or troubleshooting tips, such as checking for CLI installation via package managers (apt, yum, brew).
  • Add a note clarifying that Azure CLI commands work identically on Linux, macOS, and Windows, and provide links to platform-specific installation guides.
  • Consider including a Linux terminal screenshot or reference to reinforce cross-platform parity.
  • If PowerShell is included, also mention that PowerShell Core is available on Linux/macOS, or clarify when to use Bash vs. PowerShell.
GitHub Create Pull Request
Container Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/azure-resource-manager-api-spec.md ...cles/container-apps/azure-resource-manager-api-spec.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page shows mild Windows bias: Azure PowerShell is mentioned as a primary management tool alongside Azure CLI, and instructions for updating Azure PowerShell are provided, while no equivalent instructions for Linux-native tools (e.g., Bash, shell scripts) or alternative Linux package managers are given. The SDK list is cross-platform, but PowerShell is referenced before any Linux-specific alternatives, and no Linux-specific CLI nuances or examples are discussed. There are no explicit PowerShell command examples, but the mention of PowerShell and lack of Linux-specific details suggest a subtle preference for Windows tooling.
Recommendations
  • Include explicit instructions for updating Azure CLI on Linux (e.g., apt, yum, zypper) and mention cross-platform compatibility.
  • Add notes or examples for using Azure CLI in Linux shells (bash, zsh), including environment setup and common patterns.
  • If mentioning Azure PowerShell, also mention Linux-native scripting alternatives and clarify that Azure CLI is fully supported on Linux.
  • Ensure parity in troubleshooting or installation guidance for both Windows and Linux users.
  • Consider adding a section highlighting differences or considerations for Linux users when working with ARM and YAML templates.
GitHub Create Pull Request
Container Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/azure-arc-enable-cluster.md ...in/articles/container-apps/azure-arc-enable-cluster.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation consistently provides both Azure CLI (bash) and PowerShell examples for all commands, but PowerShell is given equal prominence to bash, which is unusual since PowerShell is primarily a Windows shell. There are no Linux-specific shell examples (e.g., zsh, fish), and no mention of Linux-specific tools or patterns. The use of PowerShell tabs throughout may signal a Windows-centric approach, and the documentation does not clarify that the Azure CLI commands are cross-platform or provide guidance for Linux users beyond bash. There is no explicit Windows-only tooling, but the parity between bash and PowerShell may unintentionally prioritize Windows users.
Recommendations
  • Clarify that Azure CLI commands work on both Linux and macOS, not just Windows.
  • Consider providing examples for other popular Linux shells (e.g., zsh) or note that bash commands apply to most Unix-like environments.
  • Add a brief section or note for Linux/macOS users, highlighting any differences in environment variable syntax or prerequisites.
  • Reduce the prominence of PowerShell unless there are truly Windows-specific steps; otherwise, focus on bash as the default cross-platform shell.
  • If PowerShell is retained, clarify that PowerShell Core is available on Linux and macOS, and provide guidance for installation if relevant.
GitHub Create Pull Request
Container Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/java-component-logs.md ...ob/main/articles/container-apps/java-component-logs.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
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 querying logs via Azure CLI, but PowerShell is consistently presented alongside or immediately after Bash, and variable assignment uses 'SET' (which is not standard Bash but is a Windows CMD convention). There is a subtle prioritization of Windows tooling and patterns, such as using 'SET' for Bash and PowerShell variable assignment, which may confuse Linux users. No Linux-specific tools or troubleshooting steps are mentioned, and the CLI examples do not use native Bash conventions (e.g., 'export' for environment variables).
Recommendations
  • Replace 'SET' with 'export' for Bash variable assignment to match Linux conventions.
  • Ensure Bash examples use standard Linux shell syntax and tools.
  • Consider providing Linux-first examples or explicitly noting differences between Windows and Linux shells.
  • Add troubleshooting notes for common Linux shell issues (e.g., quoting, environment variables).
  • Review the order of examples to avoid implicit prioritization of Windows/PowerShell.
GitHub Create Pull Request
Container Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/log-streaming.md ...ocs/blob/main/articles/container-apps/log-streaming.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation consistently provides both Bash and PowerShell examples for Azure CLI commands, but PowerShell examples are always presented immediately after Bash, giving Windows users equal prominence. There are no Linux-specific tools or patterns mentioned, and stopping the live stream references both Ctrl-C (Linux/Windows) and Cmd-C (macOS), but does not mention Linux-specific nuances. The documentation does not provide any Linux-only examples or highlight Linux workflows, and PowerShell (a Windows-centric shell) is given parity with Bash, which may not reflect the actual usage patterns of Azure CLI users (who are predominantly on Bash in Linux/macOS environments).
Recommendations
  • Consider providing Bash examples first and PowerShell examples second, or clarify that Bash is the default for cross-platform use.
  • Add notes explaining that Bash is the default shell for Linux/macOS users, and PowerShell is primarily for Windows users.
  • Include explicit references to Linux environments and workflows, such as using tail, grep, or other native Linux tools for log processing.
  • Mention that Azure CLI works natively in Bash on Linux/macOS, and provide troubleshooting tips for common Linux shell issues.
  • If possible, include a section on viewing logs using Linux-native tools or integrating with Linux-based monitoring solutions.
GitHub Create Pull Request
Container Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/github-actions-cli.md ...lob/main/articles/container-apps/github-actions-cli.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
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 commands, but PowerShell examples are given equal prominence and appear immediately after Bash, which can signal a Windows-centric approach. There is no explicit mention of Linux-specific considerations, nor are Linux tools or shell patterns highlighted. The documentation does not mention WSL, native Linux environments, or differences in authentication or file paths that may affect Linux users.
Recommendations
  • Explicitly mention that Bash examples are suitable for Linux and macOS users, and clarify any platform-specific differences.
  • Add notes about running Azure CLI in native Linux environments, including any prerequisites or common issues.
  • If there are differences in authentication or file paths between Windows and Linux, document them.
  • Consider listing Bash (Linux/macOS) examples before PowerShell (Windows) to reinforce cross-platform parity.
  • Include troubleshooting tips for Linux users, such as permissions or environment setup.
GitHub Create Pull Request
Container Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/java-application-performance-management-config.md ...apps/java-application-performance-management-config.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
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 parity between Linux and Windows users. However, PowerShell is featured as the only Windows shell, and its examples are always presented alongside Bash, sometimes even before Bash in the tab order. There are no examples for native Windows CMD, and no explicit mention of Linux-specific tools or troubleshooting. The Dockerfile and shell scripts use Linux conventions, but the overall pattern is to treat Bash and PowerShell as equally primary, which can be seen as a mild Windows bias due to PowerShell's prominence.
Recommendations
  • Add explicit notes clarifying that Bash examples are for Linux/macOS and PowerShell for Windows, to help users choose the right instructions.
  • Consider including Windows CMD examples for basic Azure CLI usage, or at least mention that PowerShell is the recommended shell for Windows.
  • Add troubleshooting tips or notes for common Linux-specific issues (e.g., file permissions, shell compatibility) to improve Linux parity.
  • Ensure that Bash examples are presented first, or clarify the intended audience for each shell to avoid implicit prioritization.
  • Reference Linux distributions (e.g., Ubuntu, CentOS) when discussing prerequisites or environment setup, not just generic 'Docker'.
GitHub Create Pull Request
Container Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/microservices-dapr-azure-resource-manager.md ...iner-apps/microservices-dapr-azure-resource-manager.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
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 major commands, ensuring cross-platform coverage. However, PowerShell examples are present throughout, and in some sections (such as log viewing and resource cleanup), PowerShell is listed alongside Bash, which may slightly favor Windows users. There are no Linux-specific tools or patterns mentioned, and the Azure portal instructions are platform-neutral. No explicit Linux examples (e.g., zsh, fish, or Linux-specific troubleshooting) are provided, and PowerShell is featured as a first-class option, which can be interpreted as a mild Windows bias.
Recommendations
  • Clarify that Bash examples are suitable for Linux/macOS and PowerShell for Windows, to help users choose the right instructions.
  • Consider adding troubleshooting notes or tips for common Linux/macOS issues (e.g., permissions, environment variables).
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide links to platform-specific installation guides.
  • If possible, include examples for other popular shells (e.g., zsh) or note any differences for Linux users.
  • Review the order of examples to ensure Bash (Linux/macOS) is not consistently listed after PowerShell, or alternate the order to avoid perceived priority.
GitHub Create Pull Request
Container Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/storage-mounts-azure-files.md .../articles/container-apps/storage-mounts-azure-files.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
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, but PowerShell is given equal prominence and detail as Bash, which can be interpreted as a Windows bias. There are no Linux-specific tools, patterns, or troubleshooting steps mentioned, and the use of PowerShell throughout may suggest a preference for Windows environments. However, the Azure CLI is cross-platform, and the examples themselves are not exclusive to Windows. The documentation does not mention Linux-specific file system considerations, nor does it provide troubleshooting tips for common Linux issues (e.g., SMB mount issues on Linux).
Recommendations
  • Add Linux-specific troubleshooting steps, especially for SMB mounts (e.g., required packages, SELinux/AppArmor considerations).
  • Include notes about differences in environment variable handling between Bash and PowerShell, and how this may affect scripts.
  • Provide explicit instructions or examples for Linux users where relevant (e.g., using 'mount' commands directly, or verifying SMB connectivity from a Linux shell).
  • Consider including a section or appendix on using the Azure CLI from WSL or native Linux environments.
  • Mention any OS-specific limitations or behaviors for Azure Files mounts in container apps.
GitHub Create Pull Request
← Previous Page 5 of 8 Next →