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 126-150 of 198 flagged pages
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 →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for all Azure CLI commands, ensuring parity in basic usage. However, in the 'Send requests' section, the PowerShell example is significantly more complex than the Bash equivalent, relying on advanced Windows/PowerShell constructs (runspaces, Invoke-WebRequest) that have no direct Linux/Bash counterpart. Additionally, instructions for opening a new shell are phrased as 'Open a new bash shell' for Bash and 'Open a new command prompt and enter PowerShell' for Windows, subtly prioritizing Windows terminology. The Bash examples use standard Linux utilities (seq, xargs, curl), but the PowerShell example is much longer and more involved, which may suggest a bias toward Windows users by providing more detailed guidance for PowerShell. No Linux-specific tools or patterns are mentioned first or exclusively, but the PowerShell examples are always present and sometimes more elaborate.
Recommendations
- Ensure that Bash and PowerShell examples are equally detailed and provide similar levels of explanation.
- Consider adding a brief explanation for how to run the Bash commands on Windows (e.g., via WSL or Git Bash), to help Windows users who prefer Bash.
- For the 'Send requests' section, provide a simpler PowerShell example if possible, or explain why the PowerShell approach is more complex.
- Avoid phrasing that assumes Windows as the default (e.g., 'Open a new command prompt'), and use more neutral language such as 'Open a new shell'.
- If possible, add troubleshooting notes for both Bash and PowerShell environments, not just one.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI (Bash) and PowerShell examples for all commands, but does not include explicit Linux shell (e.g., Bash) examples outside of the Azure CLI tab. PowerShell is given equal prominence to Azure CLI, which is more commonly used on Windows. There are no Linux-specific instructions, troubleshooting, or environment notes, and PowerShell is not natively available on most Linux distributions. The structure (CLI first, then PowerShell) is better than Windows-first, but the parity is not complete for Linux users.
Recommendations
- Clarify in the prerequisites or setup sections that Azure CLI commands are intended for Bash or compatible Linux shells, and provide explicit Bash examples where environment variable syntax or command usage differs from PowerShell.
- Remove or de-emphasize PowerShell examples unless there is a specific Windows-only step, or add a dedicated Bash/Linux tab for clarity.
- Add troubleshooting notes or environment setup tips for Linux users, such as installing required tools (e.g., base64 with -w0 flag, which differs on macOS), and note any differences in command output or file paths (e.g., ~/.kube/config).
- Where environment variables are set, ensure the Bash syntax is always shown and explained, as PowerShell variable assignment is not portable to Linux.
- If PowerShell is to be retained, clarify that it is cross-platform but less common on Linux, and provide guidance for users who may not have it installed.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Bash and PowerShell examples for all Azure CLI and Docker commands, ensuring cross-platform coverage. However, in several key sections, the PowerShell workflow is more verbose and detailed, especially for deploying the frontend application, where the PowerShell path uses multiple custom objects and cmdlets, while the Bash path uses a single CLI command. Additionally, in the deployment section, the Bash example is presented first, followed by the PowerShell example, which may subtly prioritize Bash/Linux users, but the PowerShell path is more elaborate and may imply a Windows-centric workflow.
Recommendations
- Ensure that both Bash and PowerShell examples are equally detailed and cover the same workflow steps, especially for complex operations like deploying container apps.
- Where possible, provide simplified PowerShell examples that match the simplicity of the Bash/CLI approach, or explain why the PowerShell workflow is more complex.
- Consider explicitly mentioning that both Bash and PowerShell can be used on Windows, macOS, and Linux, to avoid the perception that PowerShell is only for Windows users.
- If advanced PowerShell workflows are included, consider providing advanced Bash equivalents (e.g., using jq for JSON parsing) to maintain parity.
- Review the ordering of examples to ensure neither platform is consistently prioritized over the other.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both PowerShell and curl examples for invoking Azure Functions and viewing logs, but consistently lists PowerShell examples before curl. This ordering implicitly prioritizes Windows users. There are no Linux- or bash-specific instructions or notes, and PowerShell is not as commonly used on Linux. However, all Azure CLI commands are cross-platform, and curl is included, so Linux users are not blocked, but the presentation order and example emphasis show a subtle Windows bias.
Recommendations
- Present curl (bash/Linux) examples before PowerShell examples, or at least alternate the order in different sections.
- Explicitly mention that all Azure CLI and curl commands work on Linux, macOS, and Windows.
- Consider adding bash script examples or notes for Linux users where appropriate.
- If PowerShell is shown, clarify that it is available cross-platform, or provide equivalent bash one-liners for Linux/macOS users.
- Add a short section in prerequisites or introduction noting that all steps are cross-platform unless otherwise specified.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page exclusively uses the Azure Portal (web UI) for all instructions and does not provide any command-line examples (such as Azure CLI or PowerShell). While this avoids explicit Windows-only tools, the lack of CLI examples means Linux users (who often prefer or require CLI workflows) are not served. Additionally, when exceptions are mentioned, the workaround references 'Azure CLI' but does not provide actual CLI steps, and the linked documentation defaults to the Azure Portal, which is more familiar to Windows users.
Recommendations
- Add Azure CLI examples for all major steps, including enabling managed identity, assigning roles, and importing certificates, to ensure parity for Linux and cross-platform users.
- Where exceptions require CLI usage, provide explicit CLI commands and not just references.
- When linking to further documentation, ensure that both Portal and CLI tabs/examples are present and clearly indicated.
- Consider including a section that summarizes both Portal and CLI workflows, allowing users to choose their preferred method.
Container Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/sessions.md
...ure-docs/blob/main/articles/container-apps/sessions.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Hyper-V (a Windows-specific virtualization technology) as the foundation for session isolation, without mentioning or acknowledging Linux-based alternatives or underlying technologies. There are no Linux-specific tools, patterns, or examples provided, and the documentation implicitly assumes a Windows-centric approach to sandboxing and isolation.
Recommendations
- Acknowledge that Hyper-V is a Windows technology and clarify whether Linux-based container hosts use different isolation mechanisms (such as gVisor, Kata Containers, or other Linux container isolation technologies).
- If Azure Container Apps uses different underlying technologies for Linux-based environments, document these explicitly to provide transparency and parity.
- Include references or links to documentation about container isolation on Linux, and explain how session isolation is achieved on non-Windows hosts.
- Avoid assuming Hyper-V is universally applicable; clarify platform-specific details where relevant.
- If possible, provide examples or explanations relevant to both Windows and Linux users, or note any differences in behavior or implementation.
Container Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/vnet-custom.md
...-docs/blob/main/articles/container-apps/vnet-custom.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Bash (Azure CLI) and PowerShell examples throughout, but PowerShell is given equal or greater prominence, and all scripting alternatives are either Bash or PowerShell. There is a strong focus on PowerShell, which is primarily a Windows tool, and no explicit mention or examples for native Linux shell environments beyond Bash. In some sections, PowerShell examples are presented before or alongside Bash, which can be perceived as a Windows-first approach. No Linux-specific tools or patterns (such as native Linux networking tools or automation approaches) are mentioned.
Recommendations
- Ensure Bash (Azure CLI) examples are always presented before PowerShell, as Bash is more universally available across platforms.
- Clarify that Bash examples are suitable for Linux and macOS users, and PowerShell is primarily for Windows users (unless using PowerShell Core on Linux).
- Consider including explicit Linux shell environment notes or troubleshooting tips for common Linux distributions.
- If possible, add a short section or callout for Linux users, confirming that all Azure CLI commands work natively on Linux and macOS.
- Avoid assuming PowerShell is the default scripting environment; make it clear that it is an alternative for those who prefer it.
Container Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/microservices-dapr-pubsub.md
...n/articles/container-apps/microservices-dapr-pubsub.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation generally provides cross-platform instructions, but there is a subtle Windows bias in the Python section where Windows command examples are presented before Linux ones, and in some places, Linux-specific instructions are less prominent or missing. There are no PowerShell-heavy examples or exclusive use of Windows tools, but the ordering and occasional lack of explicit Linux parity can create a perception of Windows-first orientation.
Recommendations
- Present Linux and Windows examples side-by-side or in a consistent order (e.g., Linux first, then Windows, or vice versa, but be consistent across all language pivots).
- Where platform-specific commands are needed, ensure both Windows and Linux/macOS variants are always shown, not just for Python but for all languages.
- Consider using platform-agnostic commands (e.g., 'python3' instead of 'python' where possible) or provide a note explaining differences.
- Explicitly mention that all CLI commands (e.g., Dapr, azd, git) work on both Windows and Linux/macOS, and link to cross-platform installation guides.
- Audit other language pivots (Node.js, C#) to ensure that if there are any platform-specific nuances, they are equally documented for both Windows and Linux.
Container Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/managed-identity-image-pull.md
...articles/container-apps/managed-identity-image-pull.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI (Bash) and Azure PowerShell examples throughout, but there is a consistent pattern of presenting PowerShell (a Windows-centric tool) alongside or even before Bash/CLI in many sections. The prerequisites and setup instructions often mention PowerShell explicitly and sometimes in more detail than Bash, and the inclusion of PowerShell tabs and instructions may suggest a slight Windows bias. However, Linux users are not excluded, as Bash/CLI examples are present for all major steps. There are no exclusive Windows-only tools or missing Linux examples, but the parity in depth and order could be improved.
Recommendations
- Ensure that Bash/Azure CLI examples are always presented first, as CLI is cross-platform and more common for Linux users.
- Where possible, provide additional context or troubleshooting tips specifically for Linux environments (e.g., file permissions, environment variable syntax differences).
- Avoid giving more detailed or advanced PowerShell examples than Bash/CLI unless there is a technical reason.
- Explicitly state that all CLI examples work on Linux, macOS, and Windows, and clarify any OS-specific requirements.
- Consider adding a short section or note for Linux users highlighting any differences or best practices.
Container Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/microservices-dapr-pubsub.md
...n/articles/container-apps/microservices-dapr-pubsub.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation generally maintains good cross-platform parity, especially in the Python section, where both Windows and Linux commands are provided side-by-side. However, there is a subtle 'windows_first' bias in the ordering of examples (Windows commands are listed before Linux), and the documentation consistently references Windows-centric tools such as Docker Desktop, which is less common on Linux. There are no PowerShell-only examples, and Linux instructions are present where relevant.
Recommendations
- When presenting platform-specific commands, alternate the order (e.g., show Linux first in some sections) or present both together in a neutral way.
- Where Docker Desktop is mentioned as a prerequisite, clarify that Linux users can use the standard Docker Engine and provide a link to Linux installation instructions.
- Review other tool references (such as Azure CLI) to ensure Linux compatibility is explicitly stated or linked.
- Continue providing both Windows and Linux command examples, and consider adding macOS instructions where applicable.
- If possible, use platform-agnostic command blocks or tabs to avoid implying a default platform.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page predominantly features .NET/ASP.NET Core and Orleans samples, which are technologies most commonly associated with Windows development. The majority of the listed samples focus on Microsoft-centric stacks, with only a few Java and Drupal examples representing more cross-platform or Linux-native technologies. There are no explicit Linux or Linux tool-specific examples, and the ordering and selection of samples suggest a Windows/.NET-first perspective.
Recommendations
- Add more samples featuring Linux-native technologies (e.g., Node.js, Python, Go, PHP) deployed to Azure Container Apps.
- Include examples that use Linux command-line tools and scripting (e.g., Bash, shell scripts) for deployment and management.
- Ensure parity in documentation by providing equivalent walkthroughs for both Windows/.NET and Linux/open-source stacks.
- Highlight cross-platform deployment strategies and tools, not just those familiar to Windows users.
- Consider reordering the sample list to alternate between Windows-centric and Linux-centric technologies, or group by language/platform.
Container Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/authentication-github.md
.../main/articles/container-apps/authentication-github.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation page provides instructions primarily through the Azure Portal UI and does not include any command-line examples. There are no references to Windows-specific tools or PowerShell, but there is also a lack of parity for Linux users: no CLI (Azure CLI, Bash) examples are provided, which are commonly used on Linux and cross-platform environments. The absence of CLI instructions may implicitly favor Windows users, who are more likely to use the portal, and does not address the needs of Linux or automation-focused users.
Recommendations
- Add Azure CLI examples for all configuration steps, including registering the GitHub app and configuring authentication providers.
- Include Bash script snippets for secret management and app configuration.
- Explicitly mention that all steps can be performed via CLI on Linux, macOS, or Windows, and provide links to relevant CLI documentation.
- Ensure that any future troubleshooting or advanced configuration sections include both portal and CLI/Bash instructions.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI (Bash) and PowerShell examples for all steps, but does not include any Linux-specific shell examples (such as plain Bash or zsh), nor does it mention Linux tooling or patterns. PowerShell is given equal prominence to Azure CLI, which is more common on Windows, and the PowerShell examples use Windows-style variable syntax. In some cases, PowerShell examples are shown before or alongside CLI, but there is no explicit Linux-first approach. There are no examples or notes for Linux-specific environments, nor any mention of WSL or native Linux shells.
Recommendations
- Add explicit Bash (Linux/macOS) examples where relevant, especially for environment variable syntax and command usage.
- Clarify that Azure CLI examples are intended for Bash/zsh shells on Linux/macOS, and PowerShell examples are for Windows users.
- Consider providing a Linux/macOS tab (with Bash syntax) in addition to Azure CLI and PowerShell, or clarify that the Azure CLI tab uses Bash.
- Include notes on any differences in command output or file paths (e.g., kubeconfig location) between Windows and Linux.
- Where PowerShell is used, ensure it is not presented as the default or primary method unless justified by audience data.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for all command-line steps, but in several key sections, the PowerShell (Windows) workflow is more detailed and prominent. For example, the deployment of the frontend app is described with a simple Bash command, but the PowerShell section includes extensive object creation and scripting, which may suggest a Windows-centric workflow. Additionally, in some places, PowerShell examples or explanations are given after Bash, but with more detail, indicating a possible subtle 'windows_first' or 'windows_heavy' bias.
Recommendations
- Ensure parity in explanation depth and workflow between Bash and PowerShell sections. If the PowerShell workflow requires more steps, consider providing equivalent Bash scripting for advanced scenarios.
- Where possible, avoid making the PowerShell workflow appear as the 'default' or more complete path. If additional steps are needed for PowerShell, clarify why and provide Bash equivalents.
- Consider including a short explanation at the start that both Bash (Linux/macOS) and PowerShell (Windows) are equally supported, and that users should follow the tab that matches their environment.
- If advanced object-based scripting is shown for PowerShell, provide a Bash script or reference for users who want to automate similar steps on Linux.
- Review the order and prominence of examples to ensure neither platform is implicitly prioritized.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both PowerShell and curl examples for invoking HTTP endpoints and viewing logs, but PowerShell examples are consistently presented first. There are no Linux-specific shell or tool examples beyond curl, and the use of PowerShell may suggest a Windows-centric workflow. However, the main deployment and setup steps use Azure CLI, which is cross-platform.
Recommendations
- Alternate the order of PowerShell and curl examples, or present curl (Linux/macOS) examples first to avoid implicit Windows prioritization.
- Explicitly mention that curl commands are suitable for Linux/macOS users and PowerShell for Windows users.
- Consider adding bash script examples or referencing Linux-native tools where appropriate.
- Clarify in the prerequisites or relevant sections that all steps are cross-platform unless otherwise noted.
- If PowerShell-specific features are used, provide equivalent bash or shell script alternatives.
Container Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/sessions.md
...ure-docs/blob/main/articles/container-apps/sessions.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page exhibits a Windows bias by exclusively referencing Hyper-V, a Windows-specific virtualization technology, as the foundation for session isolation. There is no mention of Linux-based isolation technologies (such as KVM, gVisor, or Kata Containers), nor is there any discussion of how sessions operate or are isolated on non-Windows platforms. The documentation also links to Windows Server Hyper-V documentation, reinforcing the Windows-centric perspective.
Recommendations
- Include information on whether Linux-based isolation technologies (e.g., KVM, gVisor, Kata Containers) are used or supported for session isolation, especially since Azure Container Apps can run Linux containers.
- Provide links to documentation for Linux-based sandboxing or isolation technologies if applicable.
- Clarify if Hyper-V is used for all session types regardless of the underlying OS, or if different technologies are used for Linux containers.
- Ensure that any platform-specific details (such as isolation mechanisms) are presented in a cross-platform manner, or clearly state any platform limitations or differences.
- If only Hyper-V is supported, explicitly state this and provide guidance for Linux users regarding compatibility or alternatives.
Container Apps
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/container-apps/troubleshoot-container-create-failures.md
...ntainer-apps/troubleshoot-container-create-failures.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation does not provide any command-line troubleshooting examples, but all diagnostic instructions are given in the context of the Azure Portal UI, which is platform-agnostic. However, there is a notable absence of CLI-based troubleshooting steps (such as using Azure CLI, Bash, or PowerShell), and no mention of Linux-native tools or workflows. This omission may disadvantage Linux users who typically rely on command-line tools for container diagnostics. The documentation also does not mention Windows-specific tools, but the lack of Linux examples still constitutes a subtle bias.
Recommendations
- Add troubleshooting steps using Azure CLI commands that can be run from Bash or PowerShell, ensuring parity for both Linux and Windows users.
- Include examples of how to access container logs and exit codes using cross-platform tools (e.g., az containerapp revision list, az containerapp logs).
- Mention Linux-native diagnostic tools (such as journalctl, docker logs, or kubectl logs if relevant) where appropriate.
- Explicitly state that the Azure Portal steps are platform-independent, and provide alternative CLI-based instructions for users who prefer command-line interfaces.
Container Apps
Quickstart: Deploy a Dapr application to Azure Container Apps with an Azure Resource Manager or Bicep file
...iner-apps/microservices-dapr-azure-resource-manager.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Bash (Linux/macOS) and PowerShell (Windows) examples for all CLI commands, ensuring cross-platform usability. However, PowerShell examples are consistently included and sometimes shown before or alongside Bash, which may create a slight perception of Windows-first bias. There are no missing Linux/macOS examples, and all tooling (Azure CLI, Git) is cross-platform. No Windows-specific tools or patterns are mentioned.
Recommendations
- Ensure Bash examples are shown first when presenting command tabs, as Bash is the default shell for most Linux/macOS users.
- Explicitly state that all commands work on Linux/macOS unless otherwise noted.
- Consider adding a brief note at the start clarifying parity and platform support for Azure CLI and Git.
- If possible, minimize the prominence of PowerShell unless a Windows-only step is required.
Container Apps
Deploy the Dapr extension for Azure Functions in Azure Container Apps
...in/articles/container-apps/dapr-functions-extension.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both PowerShell and curl examples for invoking Azure Functions and viewing logs, but PowerShell examples are consistently presented first. This ordering may subtly signal a preference for Windows tooling. However, Linux/macOS users are not blocked, as curl examples are present and all Azure CLI commands are cross-platform.
Recommendations
- Alternate the order of PowerShell and curl examples, or present curl first to better reflect cross-platform usage.
- Explicitly mention that all CLI and curl commands work on Linux/macOS, and clarify that PowerShell is optional.
- Consider adding Bash script examples for common automation tasks, if relevant.
- Where possible, use generic shell commands (curl, Azure CLI) as the primary example, with PowerShell as an additional tab.
Container Apps
Code to cloud options in Azure Container Apps
.../main/articles/container-apps/code-to-cloud-options.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page presents deployment options for Azure Container Apps in a generally cross-platform manner, but there are subtle signs of Windows bias. Visual Studio is mentioned before Visual Studio Code, and PowerShell is referenced alongside Bash for CLI automation, with no explicit Linux/macOS command examples. There are no Linux-specific editor or tool recommendations, and the resources and examples lean toward Microsoft-centric tooling, which is more familiar to Windows users.
Recommendations
- Provide explicit Bash and Linux/macOS command examples alongside PowerShell, especially in CLI sections.
- Include references to popular Linux/macOS code editors (e.g., JetBrains Rider, Vim, etc.) or clarify that Visual Studio Code is cross-platform.
- Ensure that examples and resource links are balanced between Windows and Linux/macOS environments.
- Consider listing Visual Studio Code before Visual Studio to reflect its cross-platform nature.
- Add notes or links for Linux/macOS users about prerequisites or environment setup where relevant.
Container Apps
Create a zone-redundant container app
...main/articles/container-apps/how-to-zone-redundancy.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides step-by-step instructions for creating a zone-redundant container app using the Azure Portal, Azure CLI, and Azure PowerShell. The Azure PowerShell section is included alongside Azure CLI, and examples for both are provided. However, the PowerShell instructions are shown in full detail, and the tab order places Azure PowerShell immediately after Azure CLI, which may suggest a slight Windows-first orientation. There are no Linux-specific tools or shell examples (e.g., Bash scripting), but the Azure CLI instructions are fully cross-platform and suitable for Linux/macOS users. No critical steps are Windows-only, and Linux users can complete all tasks using the CLI.
Recommendations
- Clarify that Azure CLI commands work on Windows, Linux, and macOS.
- Consider mentioning Bash or shell scripting for Linux/macOS users where environment variables are set (e.g., using export instead of PowerShell syntax).
- Ensure tab order does not imply Windows preference (e.g., list CLI before PowerShell, or clarify cross-platform support).
- Add a note that PowerShell Core is available on Linux/macOS if users prefer PowerShell.
Container Apps
Troubleshooting in Azure Container Apps
...s/blob/main/articles/container-apps/troubleshooting.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Summary
The documentation is generally cross-platform, focusing on Azure CLI and portal workflows. However, there are some subtle Windows biases: references to 'elevated command prompt' and 'Docker on Windows' appear before Linux/macOS equivalents, and PowerShell examples are provided alongside Bash, but not Linux shell alternatives for PowerShell-specific tasks. The troubleshooting steps and examples are mostly platform-agnostic, but Windows terminology and tools are mentioned first or exclusively in a few places.
Recommendations
- When mentioning Docker usage, include references to Linux/macOS installation and usage guides alongside Windows.
- Replace 'elevated command prompt' with 'terminal with appropriate permissions' or specify both Windows and Linux/macOS equivalents.
- For PowerShell examples, clarify that Bash/CLI commands are suitable for Linux/macOS users, and provide Linux/macOS alternatives for any PowerShell-specific tasks.
- Ensure that any references to platform-specific tools (like 'Docker on Windows') are balanced with links or notes for Linux/macOS users.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Bash (Azure CLI) and PowerShell examples for all major steps, ensuring cross-platform coverage. However, PowerShell examples are given equal prominence to Bash, and in some cases, PowerShell-specific patterns (e.g., use of hashtables, cmdlets) may be more familiar to Windows users. The presence of PowerShell tabs and examples throughout, and the use of PowerShell for resource management, reflects a moderate Windows bias, but Linux/macOS users can fully complete all tasks using Bash/Azure CLI commands. No critical steps are Windows-only, and Linux parity is generally good.
Recommendations
- Consider listing Bash/Azure CLI examples before PowerShell examples, as Bash is the default shell on Linux/macOS and Azure CLI is cross-platform.
- Add a brief note clarifying that Bash/Azure CLI commands work on Linux, macOS, and Windows (with WSL or native Bash), while PowerShell examples are primarily for Windows users.
- Where possible, simplify PowerShell examples to avoid advanced Windows-centric patterns unless necessary.
- Ensure that any referenced tooling or prerequisites (e.g., Azure CLI installation) include Linux/macOS instructions or links.
Container Apps
Code to cloud options in Azure Container Apps
.../main/articles/container-apps/code-to-cloud-options.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page presents deployment options for Azure Container Apps but demonstrates subtle Windows bias. Visual Studio is mentioned before Visual Studio Code, and PowerShell is referenced alongside Bash in CLI automation, but no Linux/macOS-specific editors or workflows are highlighted. There are no explicit Linux/macOS examples or tool recommendations, and Windows-oriented tools (Visual Studio, PowerShell) are referenced first or exclusively.
Recommendations
- Include explicit examples and guidance for Linux/macOS users, such as using VS Code on Linux, JetBrains IDEs, or other cross-platform editors.
- Provide Bash-only automation examples, or clarify parity between PowerShell and Bash for CLI tasks.
- Mention Linux/macOS prerequisites and workflows where relevant, such as Docker installation or CLI usage on those platforms.
- Balance the order of tool presentation (e.g., mention VS Code before Visual Studio, or together) to avoid Windows-first perception.
Container Apps
Deploy the Dapr extension for Azure Functions in Azure Container Apps
...in/articles/container-apps/dapr-functions-extension.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both PowerShell and curl examples for invoking Azure Functions and viewing logs, but PowerShell examples are consistently shown first. This ordering may subtly signal a Windows-first approach, and the explicit use of PowerShell tabs could be interpreted as a slight bias toward Windows users. However, curl examples are present and fully functional for Linux/macOS users. All core deployment and setup instructions use Azure CLI, which is cross-platform.
Recommendations
- Alternate the order of PowerShell and curl examples, or show curl first to better represent Linux/macOS users.
- Explicitly state that curl commands work on Linux/macOS and that PowerShell is for Windows users.
- Consider adding bash script examples for multi-step processes, if applicable.
- Ensure screenshots and portal instructions do not assume Windows-only environments.