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 26-50 of 101 flagged pages
Container Apps Managed identities in Azure Container Apps .../blob/main/articles/container-apps/managed-identity.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation includes a dedicated PowerShell example for obtaining tokens, but does not provide equivalent Linux/macOS shell examples (e.g., Bash/curl). The PowerShell script uses Windows-specific environment variable syntax and tools (Invoke-RestMethod), and is presented before the generic HTTP example. There are no Linux/macOS CLI or shell script examples for token retrieval, which may create friction for non-Windows users.
Recommendations
  • Add Bash/curl examples for token retrieval alongside the PowerShell example.
  • Use cross-platform environment variable syntax in examples, or clarify differences between Windows and Linux/macOS.
  • Present generic HTTP/curl examples before or alongside PowerShell to avoid Windows-first bias.
  • Explicitly mention that Azure CLI commands work on Linux/macOS and Windows, and provide any necessary platform-specific notes.
GitHub Create Pull Request
Container Apps Tutorial: Build and deploy your app to Azure Container Apps ...main/articles/container-apps/tutorial-code-to-cloud.md
Medium Priority View Details →
Scanned: 2026-01-11 06:20
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides both Bash and PowerShell examples throughout, but PowerShell coverage is extensive and often includes Windows-specific cmdlets (e.g., New-AzContainerRegistry, Remove-AzResourceGroup) that are only available on Windows or require Windows PowerShell. In some sections, PowerShell instructions are more detailed than Bash, and Windows tools (Docker Desktop for Windows, PowerShell cmdlets) are mentioned explicitly. Bash examples are present, but PowerShell is given equal or greater prominence, which may create friction for Linux/macOS users.
Recommendations
  • Ensure Bash examples are always shown first, as Bash is the default shell on Linux/macOS.
  • Clarify that PowerShell cmdlets require Windows or PowerShell Core, and provide Bash/Azure CLI equivalents wherever possible.
  • For Docker installation, mention Linux-native Docker installation methods before Docker Desktop for Windows.
  • Where PowerShell instructions are more detailed, ensure Bash/Azure CLI instructions are equally comprehensive.
  • Add explicit notes when a command or tool is Windows-only, and suggest Linux/macOS alternatives.
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, maintaining parity in command-line instructions. However, in the 'Send requests' section, the PowerShell example is significantly more complex and Windows-specific, while the Bash example uses standard Linux utilities. The PowerShell example is presented with equal prominence, but the explanations and referenced tools (e.g., PowerShell runspaces) are Windows-centric and may not be familiar to Linux users. Additionally, the instructions for opening a shell refer to 'bash shell' for Bash and 'command prompt and enter PowerShell' for PowerShell, subtly prioritizing Windows terminology. There is no explicit mention of Linux alternatives for the PowerShell-specific patterns, nor is there guidance for macOS users.
Recommendations
  • Add explicit instructions for macOS users, clarifying that Bash commands work on macOS and most Linux distributions.
  • In the 'Send requests' section, provide a brief explanation that Bash commands are native to Linux/macOS, while PowerShell commands are for Windows users.
  • Consider mentioning cross-platform shells such as PowerShell Core, which runs on Linux and macOS, and clarify any differences in command syntax or behavior.
  • Where PowerShell examples use advanced Windows-specific constructs (e.g., runspaces), offer alternative Bash or Linux-native approaches for concurrency, or reference tools like GNU Parallel.
  • Review terminology to avoid subtle Windows bias (e.g., use 'terminal' or 'shell' instead of 'command prompt' when referring to opening a shell).
GitHub Create Pull Request
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 cross-platform coverage. However, PowerShell examples are given equal prominence to Bash, and in some sections (such as the 'Deploy front end application'), the PowerShell workflow is significantly more verbose and detailed, which may implicitly favor Windows users by offering more guidance and explanation for PowerShell. There is no explicit mention of Linux-specific tools, patterns, or troubleshooting, and no examples for native Linux shells other than Bash. Windows/PowerShell is treated as a first-class citizen throughout, with detailed object-oriented scripting, while Bash examples are more concise.
Recommendations
  • Ensure that Bash and PowerShell examples are equally detailed, so Linux users receive the same level of guidance as Windows users.
  • Add troubleshooting notes or tips specific to Linux environments, such as permissions, environment variable handling, or common issues with Docker and Azure CLI on Linux.
  • Consider including examples for other popular Linux shells (e.g., zsh, fish) or note that Bash examples are applicable to most POSIX shells.
  • Where PowerShell-specific objects and workflows are explained, provide equivalent explanations for Bash workflows (e.g., how environment variables are set and used, how to handle output parsing).
  • Explicitly state that all steps are cross-platform and highlight any platform-specific caveats or differences.
GitHub Create Pull Request
Container Apps Deploy an artifact file to Azure Container Apps ...s/blob/main/articles/container-apps/deploy-artifact.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 commands, ensuring cross-platform coverage. However, PowerShell is given equal prominence to Bash, which may reflect a slight Windows bias, as Linux users are more likely to use Bash. Additionally, in the 'Run the project locally' section, the example uses a Windows-style path separator (target\containerapps-albumapi-java-0.0.1-SNAPSHOT.jar) in both Bash and PowerShell tabs, which may confuse Linux users. No Linux-specific tools or patterns are mentioned, and Windows tools are not exclusively referenced.
Recommendations
  • Ensure that Bash examples use Linux-style path separators (forward slashes) to avoid confusion.
  • Consider listing Bash examples before PowerShell, as Bash is more common in cross-platform and cloud-native scenarios.
  • Add a note clarifying that PowerShell examples are intended for Windows users, and Bash for Linux/macOS.
  • Where relevant, mention Linux/macOS-specific troubleshooting tips or environment setup steps.
  • Review all code snippets for platform-specific assumptions (such as file paths) and adjust as needed for true cross-platform parity.
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 PowerShell is consistently presented first, suggesting a Windows-first approach. There is no explicit mention of Linux-specific tools or shell environments, and the examples do not address potential differences in command syntax or environment setup between Windows and Linux. The Azure CLI is used throughout, which is cross-platform, but the ordering and prominence of PowerShell may signal a subtle bias toward Windows users.
Recommendations
  • Alternate the order of PowerShell and curl examples, or present curl first to better reflect Linux usage patterns.
  • Explicitly mention that Azure CLI and curl commands work on Linux, macOS, and Windows, and provide any necessary notes about environment-specific differences.
  • Include example terminal prompts or screenshots from Linux environments alongside Windows examples.
  • Add a brief section or note confirming cross-platform compatibility and pointing to further resources for Linux/macOS users.
  • Consider including bash or zsh shell examples for common tasks, especially for scripting or automation.
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
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 commands, but PowerShell (Windows) examples are always presented immediately after Bash, suggesting a slight Windows-first ordering. The presence of PowerShell examples throughout indicates a moderate bias toward Windows users, as Linux users typically use Bash. No Linux-specific tools or patterns are missing, but the parity in example presentation could be improved.
Recommendations
  • Consider presenting Bash examples before PowerShell, or alternating which comes first to avoid implicit prioritization.
  • Explicitly mention that Bash examples are suitable for Linux/macOS and PowerShell for Windows, to guide users.
  • Add a short section clarifying cross-platform compatibility of Azure CLI commands, reassuring Linux users.
  • If relevant, include troubleshooting notes for common Linux-specific issues (e.g., permissions, environment variables).
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 command-line steps, ensuring parity between Linux and Windows users. However, PowerShell is featured as a first-class citizen throughout, which is a Windows-centric shell. There is no explicit mention of Linux-specific tools or troubleshooting, and PowerShell examples are given equal prominence to Bash, which may subtly reinforce Windows usage in cross-platform scenarios.
Recommendations
  • Clarify that Bash examples are intended for Linux/macOS and PowerShell for Windows, to help users choose the right instructions.
  • Add troubleshooting notes for common Linux-specific issues (e.g., file permissions, shell differences).
  • Include explicit references to Linux distributions (Ubuntu, CentOS, etc.) where relevant, especially for Docker and shell script usage.
  • Consider providing examples using native Linux tools (e.g., sed, grep) for configuration editing, or mention alternatives to PowerShell for Linux users.
  • Add a note that PowerShell Core is cross-platform, but most Windows users will use Windows PowerShell, and Linux/macOS users will likely use Bash.
GitHub Create Pull Request
Container Apps Observability of managed Java components in Azure Container Apps ...ob/main/articles/container-apps/java-component-logs.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 querying logs via Azure CLI, but in each case, the PowerShell example is presented immediately after Bash, and variable assignment uses 'SET' (which is a Windows command, not standard Bash). There is a subtle preference for Windows tooling and patterns, such as the use of PowerShell and 'SET' for Bash, which may confuse Linux users. No Linux-specific tools or patterns (e.g., export, shell scripting, grep) are mentioned, and the Bash examples use syntax that is not idiomatic for Linux environments.
Recommendations
  • Replace 'SET' with 'export' for Bash variable assignment to match Linux conventions.
  • Ensure Bash examples use idiomatic Linux shell syntax and commands.
  • Consider presenting Bash (Linux) examples before PowerShell (Windows) to avoid implicit Windows-first bias.
  • Add notes clarifying differences between Bash on Linux/macOS and PowerShell on Windows, especially for variable assignment and command usage.
  • Include troubleshooting tips or alternative commands for common Linux shells (e.g., zsh, sh) if relevant.
GitHub Create Pull Request
Container Apps View log streams in Azure Container Apps ...ocs/blob/main/articles/container-apps/log-streaming.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 Azure CLI commands, ensuring coverage for both Linux/macOS and Windows users. However, PowerShell examples are given equal prominence to Bash, which may be unnecessary given that Azure CLI is cross-platform and Bash is the default shell for most Linux/macOS environments. The use of PowerShell examples throughout the page, rather than focusing primarily on Bash (with a note for Windows users), reflects a mild Windows bias. Additionally, instructions for stopping the log stream mention both Ctrl-C and Cmd-C, but do not reference Linux-specific shortcuts or considerations.
Recommendations
  • Make Bash the default or primary example, with PowerShell examples available via tabs or expandable sections for Windows users.
  • Clarify that Bash commands work on Linux/macOS and Windows (with WSL or Git Bash), and that PowerShell is primarily for native Windows environments.
  • Add notes or guidance for Linux users regarding shell compatibility, especially if any command syntax differs.
  • Ensure that instructions for stopping log streams mention Linux-specific shortcuts (e.g., Ctrl-C) and clarify any differences for macOS/Windows.
  • Consider reducing the prominence of PowerShell examples unless there are Windows-specific behaviors or requirements.
GitHub Create Pull Request
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
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, ensuring cross-platform coverage. However, PowerShell examples are included for every step, which may indicate a slight bias towards Windows users. Additionally, in some sections (such as log viewing and resource cleanup), PowerShell examples are presented immediately after Bash, potentially giving Windows tools parity or priority. There are no Linux-specific tools or patterns mentioned, but Bash examples are present throughout, so Linux users are not excluded.
Recommendations
  • Explicitly state that Bash examples are suitable for Linux/macOS and PowerShell for Windows, to clarify platform relevance.
  • Consider including a note about running Bash commands in Windows environments (e.g., via WSL or Git Bash) for users who may not use PowerShell.
  • Add troubleshooting or environment setup tips for Linux/macOS users, such as common issues with Azure CLI or permissions.
  • Ensure that any referenced scripts or templates work identically on Linux/macOS and Windows, and mention any platform-specific caveats.
  • If possible, provide a summary table mapping commands to platforms (Windows/PowerShell, Linux/Bash, macOS/Bash) for quick reference.
GitHub Create Pull Request
Container Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/authentication-entra.md ...b/main/articles/container-apps/authentication-entra.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation exclusively uses the Azure Portal (a web UI) for all configuration steps and does not provide any command-line examples. There are no references to Windows-specific tools like PowerShell or CMD, but there is also a lack of parity for Linux users, as no CLI (e.g., Azure CLI, Bash) instructions are provided. This can disadvantage users who prefer or require command-line automation, which is common in Linux environments.
Recommendations
  • Add Azure CLI examples for all major configuration steps, such as app registration, setting authentication providers, and managing secrets.
  • Explicitly mention that all steps can be performed via the Azure CLI or ARM templates, and link to relevant documentation.
  • Where possible, provide Bash shell command examples alongside portal instructions to support Linux users and automation scenarios.
  • Include a section summarizing cross-platform options for performing the tasks described, highlighting both portal and CLI approaches.
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: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Bash and PowerShell examples for every command, ensuring cross-platform coverage. However, PowerShell (and thus Windows) examples are consistently present and, in some sections (notably the 'Deploy front end application'), the PowerShell instructions are more verbose and detailed than the Bash equivalents. The PowerShell workflow uses more Azure PowerShell-specific cmdlets and objects, which are primarily relevant to Windows users. Bash examples are generally simpler and use Azure CLI directly, but the PowerShell sections may give the impression of Windows primacy due to their length and detail.
Recommendations
  • Ensure Bash and PowerShell instructions are equally detailed, especially in complex deployment steps.
  • Add explicit notes clarifying that Bash instructions are suitable for Linux and macOS users, and PowerShell for Windows users.
  • Where possible, provide parity in workflow complexity between Bash and PowerShell, so Linux users do not feel their instructions are less complete.
  • Consider including a table or section summarizing cross-platform command equivalence for quick reference.
  • Avoid using advanced PowerShell-specific patterns (like custom object creation) unless a Bash/Linux equivalent is also provided or explained.
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: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both PowerShell and curl examples for key API interactions and log queries, but consistently lists PowerShell examples before curl. This ordering implicitly prioritizes Windows tooling and patterns, even though the Azure CLI and curl are cross-platform. No Linux-specific tools or shell examples (e.g., bash scripts) are provided, and PowerShell is given equal or greater prominence than curl, which may be less familiar to Linux users.
Recommendations
  • Present curl (Linux/macOS) examples before PowerShell examples, or side-by-side, to avoid implicit prioritization.
  • Explicitly note that all CLI and curl commands work on Linux, macOS, and Windows, and clarify any platform-specific differences.
  • Add bash script examples or references for common tasks, especially for log queries and API calls.
  • Avoid using PowerShell-specific syntax (e.g., @{} for headers) without explanation or Linux equivalents.
  • Include a note in the prerequisites or introduction about cross-platform compatibility and tool availability.
GitHub Create Pull Request
Container Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/deploy-visual-studio-code.md ...n/articles/container-apps/deploy-visual-studio-code.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation demonstrates a bias towards Windows by only providing instructions and examples using Visual Studio Code's GUI and command palette, which are presented in a way that closely aligns with Windows workflows. There are no examples or instructions for deploying via Linux-native tools, CLI, or terminal commands, nor is there mention of Linux-specific considerations or parity. The documentation implicitly assumes a Windows or at least a GUI-centric environment.
Recommendations
  • Include equivalent instructions for deploying to Azure Container Apps using the Azure CLI or Bash terminal, which are common on Linux.
  • Explicitly mention that Visual Studio Code and its extensions are available on Linux and macOS, and note any platform-specific differences if they exist.
  • Provide examples or links for performing the same deployment steps using Linux-native tools (e.g., Azure CLI, Docker CLI) outside of Visual Studio Code.
  • Add a section or callout for Linux users, highlighting any differences or additional steps required.
  • Ensure that screenshots and keyboard shortcuts are not Windows-specific (e.g., avoid only referencing <kbd>F1</kbd> if it behaves differently on Linux/macOS).
GitHub Create Pull Request
Container Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/deploy-artifact.md ...s/blob/main/articles/container-apps/deploy-artifact.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for all commands, ensuring cross-platform coverage. However, PowerShell (Windows) examples are always presented immediately after Bash, and the use of PowerShell tabs throughout may subtly reinforce Windows as a primary platform. There are no Linux-specific tools or troubleshooting steps, and no mention of Linux distributions or shell alternatives beyond Bash. The file path in the 'Run the project locally' section uses backslashes (Windows style), which may confuse Linux users.
Recommendations
  • Explicitly mention Linux and macOS compatibility in the prerequisites and throughout the guide.
  • Include troubleshooting tips for common Linux/macOS issues (e.g., permissions, package installation).
  • Use forward slashes in file paths for Bash examples to match Linux/macOS conventions.
  • Consider presenting Bash (Linux/macOS) examples before PowerShell (Windows), or clarify that Bash is suitable for both Linux and macOS.
  • Add notes about differences in environment variable syntax between shells/platforms.
  • If possible, include a section or tab for macOS-specific instructions, especially for Java and Maven installation.
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
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by referencing Visual Studio as the first deployment tutorial and omitting explicit Linux-oriented tooling or examples. There are no PowerShell commands or Windows-specific tools mentioned directly, but the lack of Linux CLI examples and the prioritization of Visual Studio (a primarily Windows IDE) in deployment guidance suggest a Windows-first perspective. There is no mention of Linux-native workflows, such as using VS Code, Bash, or Docker CLI commands on Linux, nor are there examples tailored to Linux environments.
Recommendations
  • Add explicit Linux deployment examples, such as using Azure CLI or Docker CLI from a Bash shell.
  • Include guidance for deploying from VS Code or other cross-platform editors, not just Visual Studio.
  • Provide sample commands and configuration steps for both Windows and Linux environments.
  • Clarify that all steps can be performed on Linux, and highlight any platform-specific considerations.
  • Balance tutorial links so that Linux-first or cross-platform options appear alongside or before Windows-centric ones.
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: 2025-12-29 18:00
Reviewed by: Unknown
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 listed second and uses Windows-centric variable assignment syntax. The use of 'SET' for Bash variable assignment is incorrect and more typical of Windows CMD, suggesting a Windows-first approach. There is no mention of Linux-specific tools or troubleshooting, and the CLI examples do not use native Linux conventions (e.g., 'export' for environment variables).
Recommendations
  • Use correct Bash syntax for variable assignment (e.g., 'export WORKSPACE_ID=<WORKSPACE_ID>') instead of 'SET', which is a Windows CMD command.
  • Provide Linux-specific troubleshooting steps or notes where relevant.
  • Ensure Bash examples use idiomatic Linux shell commands and are listed first if targeting cross-platform users.
  • Consider including examples using other popular Linux shells (e.g., zsh) if relevant.
  • Explicitly state cross-platform compatibility and highlight any OS-specific differences in CLI usage.
GitHub Create Pull Request
Container Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/key-vault-certificates-manage.md ...ticles/container-apps/key-vault-certificates-manage.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively uses the Azure portal UI for all steps, which is primarily accessed via web browsers on Windows, and does not provide any command-line examples (such as Azure CLI, Bash, or PowerShell). There are no Linux-specific instructions, nor are cross-platform CLI patterns shown. The only mention of command-line tooling is a brief reference to Azure CLI for App Service certificates, but no example is given. This results in a Windows-first and GUI-centric bias, with missing parity for Linux or CLI users.
Recommendations
  • Add Azure CLI and/or PowerShell command examples for all major steps, including enabling managed identity, assigning roles, and importing certificates.
  • Explicitly mention that all steps can be performed on Linux, macOS, and Windows using CLI tools.
  • Provide Bash shell examples for Linux users.
  • Include links to cross-platform CLI documentation where relevant.
  • Clarify any platform-specific limitations, if present, for portal or CLI usage.
GitHub Create Pull Request
Container Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/migrate-functions.md ...blob/main/articles/container-apps/migrate-functions.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exhibits Windows bias primarily in the prerequisites section, where the Azure CLI installation link points to the Windows-specific instructions and no Linux or cross-platform alternatives are mentioned. No explicit Linux or macOS examples or instructions are provided, and no platform-specific differences are discussed. All command-line examples use Azure CLI, which is cross-platform, but the lack of Linux parity in installation guidance may hinder non-Windows users.
Recommendations
  • Update the Azure CLI installation link to point to the cross-platform installation page or provide links for Windows, Linux, and macOS.
  • Explicitly state that all Azure CLI commands work on Windows, Linux, and macOS.
  • If there are any platform-specific considerations (e.g., environment variable syntax, file paths), mention them or provide examples.
  • Consider adding a note or section for Linux/macOS users to ensure parity and inclusivity.
GitHub Create Pull Request
Container Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/quota-requests.md ...cs/blob/main/articles/container-apps/quota-requests.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation exclusively describes quota requests using the Azure Portal (a web-based GUI) and does not mention or provide examples for command-line tools such as Azure CLI or Azure PowerShell. This approach implicitly favors users accustomed to GUI workflows, which are more common in Windows environments, and omits parity for Linux users who may prefer or require CLI-based instructions.
Recommendations
  • Add equivalent instructions for requesting quota changes using the Azure CLI, which is cross-platform and widely used on Linux.
  • If PowerShell examples are relevant, ensure Azure CLI examples are provided first or alongside them.
  • Explicitly state that the Azure Portal is web-based and accessible from any OS, but also provide links or steps for CLI-based workflows.
  • Include screenshots or code snippets demonstrating quota requests via CLI commands to support Linux and automation-focused users.
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: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Bash (Azure CLI) and PowerShell examples for each command, with Bash examples first. However, the PowerShell examples use Azure PowerShell cmdlets (e.g., Get-AzContainerAppRevision, Update-AzContainerApp), which are Windows-centric and less commonly used on Linux. In some cases, PowerShell examples simply call the Azure CLI, but the documentation still presents PowerShell as a primary workflow. There are no Linux-specific shell examples (e.g., zsh, fish), and no mention of native Linux tools or scripting patterns. The documentation assumes parity between Bash and PowerShell, but the heavy use of PowerShell cmdlets and the presence of PowerShell tabs throughout indicates a Windows bias.
Recommendations
  • Clarify that Azure PowerShell cmdlets are primarily supported on Windows, and that Bash/CLI examples are cross-platform.
  • Consider providing additional Linux-native shell examples (e.g., zsh, fish) or scripting patterns where relevant.
  • Where PowerShell examples simply invoke the Azure CLI, note that these commands are identical to Bash and can be run in any shell.
  • Add a short section explaining the cross-platform availability of Azure CLI and PowerShell, and recommend Azure CLI for Linux/macOS users.
  • If possible, provide examples using only the Azure CLI for maximum cross-platform compatibility, and move PowerShell examples to a secondary position or appendix.
GitHub Create Pull Request
Container Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/samples.md ...zure-docs/blob/main/articles/container-apps/samples.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page lists Azure Container Apps samples, with a strong emphasis on .NET/ASP.NET Core, Orleans, and Blazor Server applications, which are traditionally associated with Windows development. These samples are presented first and in greater number compared to Linux-native or open-source technology samples (e.g., Drupal, Java, Node.js). There is no explicit mention of Linux-specific tools, deployment patterns, or examples, nor are there references to Linux shell commands or containerization workflows common in Linux environments. The ordering and selection of samples suggest a Windows/.NET-first bias, and the lack of Linux-specific guidance or parity in examples further reinforces this.
Recommendations
  • Add more samples featuring Linux-native technologies (e.g., Python, Go, Ruby, PHP beyond Drupal) and deployment scenarios.
  • Include explicit Linux shell (bash) deployment instructions or scripts alongside any PowerShell or Windows-centric guidance.
  • Balance the ordering of samples so that Linux/open-source technologies are presented alongside .NET/Windows samples, not after them.
  • Highlight containerization workflows common in Linux environments, such as Docker Compose, Kubernetes YAML, or CLI commands.
  • Provide guidance on using Azure CLI from Linux terminals, and reference Linux-based development environments in sample documentation.
GitHub Create Pull Request
Container Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/tutorial-scaling.md .../blob/main/articles/container-apps/tutorial-scaling.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
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 cross-platform parity for core tasks. However, in the 'Send requests' section, the Bash example uses standard Linux utilities (seq, xargs, curl), while the PowerShell example uses advanced PowerShell constructs (runspaces, Invoke-WebRequest), which are more complex and less familiar to Linux users. Additionally, the PowerShell examples are always presented after Bash, but the explanations and links for Bash commands are more detailed, with Linux man page links, while the PowerShell section only links to a Microsoft blog. There is a slight bias towards Windows/PowerShell in the complexity and depth of the PowerShell examples, but overall, Linux is well represented.
Recommendations
  • Ensure that the explanations and documentation links for PowerShell commands are as detailed as those for Bash (e.g., link to official PowerShell documentation for each cmdlet used).
  • Consider providing simpler PowerShell alternatives for sending concurrent requests, or note that the Bash example can be run in WSL on Windows for parity.
  • Explicitly mention that all Azure CLI commands work identically on Linux, macOS, and Windows, and that Bash examples can be run in WSL or Git Bash on Windows.
  • Add a short section at the start clarifying that both Bash and PowerShell are supported, and users can choose their preferred shell.
  • Where possible, provide a cross-platform (Python or Node.js) script for sending concurrent requests, to avoid shell-specific complexity.
GitHub Create Pull Request
Container Apps https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/service-connector.md ...blob/main/articles/container-apps/service-connector.md
Medium Priority View Details →
Scanned: 2025-12-29 18:00
Reviewed by: Unknown
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation provides instructions using the Azure Portal and Azure CLI, which are both cross-platform tools. However, there is a subtle Windows bias: the CLI examples do not mention Linux or macOS shells, nor do they provide any Bash-specific guidance or troubleshooting. There are no references to Linux-specific tools, nor are there any screenshots or examples that show Linux environments. The documentation does not mention or address potential differences in CLI usage or authentication flows on Linux/macOS versus Windows. Additionally, the CLI instructions assume the user is familiar with the Azure CLI, which is available on all platforms, but there is no explicit mention of Linux or macOS, and the browser-based authentication flow is described in a way that may be more familiar to Windows users.
Recommendations
  • Explicitly state that the Azure CLI commands work on Windows, Linux, and macOS, and provide any platform-specific notes if relevant.
  • Include Bash shell examples or troubleshooting tips for Linux/macOS users (e.g., handling environment variables, file paths, or authentication issues).
  • Add screenshots or terminal examples from a Linux shell to visually reinforce cross-platform support.
  • Mention installation instructions or prerequisites for the Azure CLI on Linux/macOS, or link to relevant documentation.
  • If there are any differences in authentication flows or required dependencies on Linux/macOS, call them out in the documentation.
GitHub Create Pull Request
← Previous Page 2 of 5 Next →