Container Registry
149
Total Pages
127
Linux-Friendly Pages
22
Pages with Bias
14.8%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
183 issues found
Showing 101-125 of 183 flagged pages
Container Registry
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/buffer-gate-public-content.md
...icles/container-registry/buffer-gate-public-content.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for importing images into Azure Container Registry, but it lists Azure PowerShell as a primary tool alongside Azure CLI and portal, which may suggest a Windows-centric approach. The PowerShell example is given equal prominence to the CLI example, and there are no explicit Linux shell (bash) or cross-platform scripting examples. There is no mention of Linux-specific tools or workflows, and PowerShell is traditionally associated with Windows environments, though it is now cross-platform. The documentation does not provide Linux-first or Linux-specific guidance, nor does it mention Linux package managers or shell scripting alternatives.
Recommendations
- Add explicit bash or shell script examples for Linux users, especially for common workflows such as importing images.
- Clarify that Azure CLI is cross-platform and provide usage notes for Linux and macOS environments.
- Mention that PowerShell is available on Linux, but also provide native Linux shell alternatives where appropriate.
- Include references to Linux-native tools or workflows, such as using curl, wget, or podman where relevant.
- Order examples so that cross-platform or Linux-native tools are presented before Windows-centric tools like PowerShell.
- Add a section or note on Linux authentication patterns and registry access, including integration with Linux-based CI/CD systems.
Create Pull Request
Container Registry
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/container-registry-auth-aci.md
...cles/container-registry/container-registry-auth-aci.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page provides both Azure CLI and Azure PowerShell sample script links, but lists Azure PowerShell immediately after Azure CLI, giving it equal prominence. There is no explicit mention or example of Linux-specific tools or shell environments beyond a brief note about setting an environment variable for bash. The documentation does not provide Linux shell script examples inline, and PowerShell (primarily a Windows tool) is featured as a primary alternative to Azure CLI.
Recommendations
- Add explicit Linux/bash script examples inline, not just via external links.
- Mention Linux shell environments (e.g., bash, zsh) and provide guidance for common Linux scenarios.
- If PowerShell is referenced, clarify cross-platform support or provide parity with Linux-native tools.
- List Linux/Unix examples before or alongside Windows/PowerShell examples to avoid implicit prioritization.
- Expand the note about 'export MSYS_NO_PATHCONV=1' to explain its relevance for Linux users, and provide troubleshooting tips for common Linux issues.
Container Registry
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/container-registry-helm-repos.md
...es/container-registry/container-registry-helm-repos.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias in its command examples and environment variable usage. The initial example for setting environment variables uses the Windows 'set' command, with no mention of the Linux/Unix 'export' equivalent. Throughout the page, commands are presented in a generic shell format, but the only explicit environment variable setting is Windows-style. There are no PowerShell-specific examples, but the lack of Linux-specific instructions (such as 'export' for environment variables) may confuse Linux users. No Windows-only tools or patterns are mentioned, but the order of presenting environment variable setup favors Windows.
Recommendations
- Provide both Windows ('set VAR=value') and Linux/macOS ('export VAR=value') examples when setting environment variables.
- Explicitly state which shell is assumed for each command block, or provide separate tabs/sections for Windows CMD, PowerShell, and Bash.
- Ensure parity by including Linux/macOS-specific instructions where relevant, especially for authentication and environment setup.
- Review all command examples to confirm they work as written on both Windows and Linux platforms, or annotate differences.
Container Registry
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/container-registry-rbac-custom-roles.md
...ainer-registry/container-registry-rbac-custom-roles.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation presents both Azure CLI and Azure PowerShell commands for listing permissions, but PowerShell is mentioned alongside CLI in a way that may suggest parity. However, PowerShell is a Windows-centric tool, and there are no explicit Linux shell examples (e.g., Bash, scripting patterns) or notes about cross-platform usage. Additionally, the order of mentioning Azure CLI and PowerShell is inconsistent, sometimes listing PowerShell first in links. There is no explicit bias in tool recommendations, but the lack of Linux-specific examples or clarifications may disadvantage Linux users.
Recommendations
- Clearly indicate that Azure CLI works cross-platform (Windows, Linux, macOS) and is recommended for Linux environments.
- Provide explicit Bash or Linux shell examples where relevant, especially for scripting or automation.
- When listing tools, consistently mention Azure CLI before PowerShell to reflect its cross-platform nature.
- Add notes clarifying that PowerShell Core is available on Linux, or link to installation instructions for Linux users.
- Include troubleshooting or environment setup tips for Linux users, such as file path conventions or authentication differences.
Container Registry
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/container-registry-troubleshoot-access.md
...ner-registry/container-registry-troubleshoot-access.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page does not provide explicit Windows-only examples or tools, but it demonstrates subtle Windows bias by omitting platform-specific troubleshooting steps and examples. For instance, when discussing Docker proxy configuration, it does not mention Linux-specific daemon configuration steps or environment variables. Additionally, while DNS troubleshooting tools like 'dig' and 'nslookup' are mentioned (which are available on both platforms), there are no explicit Linux command-line examples or references to Linux-specific patterns (e.g., systemd configuration for Docker, iptables, or Linux firewall tools). The documentation assumes parity but does not ensure it by providing Linux-centric guidance or examples.
Recommendations
- Add explicit Linux troubleshooting examples, such as configuring Docker proxy settings via systemd drop-in files and environment variables (HTTP_PROXY, HTTPS_PROXY) for Linux.
- Include Linux-specific commands for firewall and network diagnostics (e.g., iptables, ufw, firewalld) alongside any Windows equivalents.
- Provide step-by-step instructions for common Linux distributions (Ubuntu, CentOS, etc.) when discussing Docker daemon restart and proxy configuration.
- Reference Linux log file locations (e.g., /var/log/docker.log) and diagnostic tools (e.g., journalctl) where appropriate.
- Ensure that any mention of network utilities includes installation instructions for Linux (e.g., 'apt install dnsutils' for dig/nslookup).
Container Registry
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/container-registry-tutorial-github-verify-notation-trusted-signing.md
...gistry-tutorial-github-verify-notation-trusted-signing.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Linux (bash) and Windows (PowerShell) examples for all command-line steps, but consistently lists Windows examples after Linux, indicating a 'windows_first' bias in terms of explicit inclusion and ordering. Additionally, Windows-specific tooling (PowerShell, Invoke-WebRequest, New-Item) is used for Windows examples, but no Linux-specific tools beyond curl and bash are mentioned. There is no evidence of missing Linux examples or exclusive use of Windows tools, but the pattern of always providing Windows examples and using PowerShell commands reflects a mild Windows bias.
Recommendations
- Ensure that Linux and Windows examples are presented with equal prominence, possibly by randomizing or alternating the order in which they appear.
- Consider including macOS-specific instructions or notes where relevant, to further improve cross-platform parity.
- Where possible, use platform-agnostic commands or highlight cross-platform tools (e.g., using Python or Node.js scripts for downloads) to minimize reliance on OS-specific shells.
- Explicitly state that all examples are available for both platforms at the start of the section, to reassure users of parity.
- Review for any subtle differences in functionality or prerequisites between platforms and document them clearly.
Container Registry
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/includes/azure-container-registry.md
...ontainer-registry/includes/azure-container-registry.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for querying vulnerability assessment results, but the PowerShell example is given equal prominence to the CLI example, and there is no explicit Linux shell (bash) example or mention of Linux-specific usage patterns. The use of PowerShell (traditionally Windows-centric) and the lack of Linux shell examples may make the documentation feel Windows-biased, especially for users who prefer bash or other Linux shells.
Recommendations
- Add explicit bash/Linux shell examples for running Azure CLI commands, including any necessary environment setup or authentication steps common in Linux environments.
- Clarify that Azure CLI works cross-platform and provide guidance for Linux/macOS users (e.g., installation, authentication).
- If PowerShell is mentioned, also mention alternatives for Linux users (e.g., bash, zsh) and provide equivalent examples.
- Consider reordering examples to present Azure CLI (cross-platform) before PowerShell, or explicitly state platform applicability for each example.
- Include troubleshooting notes or links for common Linux issues (e.g., az CLI installation, permissions).
Container Registry
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/quickstart-client-libraries.md
...cles/container-registry/quickstart-client-libraries.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page demonstrates mild Windows bias in the prerequisites section, where Azure PowerShell and Azure CLI are listed as options for creating a registry, with PowerShell (a Windows-centric tool) mentioned before Azure CLI. The example for creating a registry uses Azure CLI, which is cross-platform, but the ordering of options may suggest a Windows-first approach. The rest of the documentation is focused on cross-platform SDK usage and does not show significant bias in code samples, which are provided for multiple languages and do not rely on Windows-specific tools or patterns.
Recommendations
- List Azure CLI before Azure PowerShell in the prerequisites, as CLI is cross-platform and more widely used on Linux.
- Explicitly mention that Azure CLI is available on Linux/macOS/Windows, while PowerShell is primarily a Windows tool (though it is available cross-platform, many users still associate it with Windows).
- Where possible, provide Linux/macOS-specific notes or instructions for common developer workflows, such as environment variable setup or authentication.
- Ensure that any references to tooling or shell commands are either cross-platform or have Linux/macOS equivalents provided.
- Consider adding a note clarifying that all SDK examples are platform-agnostic and can be run on Linux, macOS, or Windows.
Container Registry
https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/quickstart-connected-registry-arc-cli.md
...iner-registry/quickstart-connected-registry-arc-cli.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for generating the protected settings JSON file, but the PowerShell example is given immediately after Bash and is not clearly marked as Windows-specific. The overall flow does not show a strong bias toward Windows, but the PowerShell example is present and could be interpreted as giving parity to Windows users. There are no exclusive references to Windows tools, and all CLI commands are cross-platform (Azure CLI, kubectl). However, the PowerShell example is included before any mention of Linux-specific shell variants (e.g., zsh, fish), and there is no explicit guidance for Linux users beyond Bash.
Recommendations
- Clearly label the PowerShell example as 'Windows (PowerShell)' and the Bash example as 'Linux/macOS (Bash)' to avoid confusion.
- Provide additional Linux shell variants if relevant (e.g., zsh, fish), or clarify that Bash is the recommended shell for Linux/macOS.
- Ensure that Bash examples are presented first, or in a way that makes it clear they are the default for Linux/macOS users.
- Add a note indicating that all Azure CLI commands are cross-platform and can be run on Windows, Linux, or macOS.
- Consider including a table or section summarizing platform compatibility for all commands and tools used.
Container Registry
Store Helm Charts in Azure Container Registry
...es/container-registry/container-registry-helm-repos.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is generally cross-platform, focusing on Helm and Azure CLI commands, which work on Windows, Linux, and macOS. However, there are subtle Windows-first biases: the environment variable setup uses the Windows 'set' command without showing the equivalent Linux/macOS 'export' command, and the prerequisites mention Azure PowerShell before Azure CLI and portal for AKS creation. No explicit Linux/macOS examples are provided for environment variable setup, which could cause friction for non-Windows users.
Recommendations
- Provide both Windows ('set') and Linux/macOS ('export') examples for environment variable setup.
- When listing prerequisites or creation methods, mention Azure CLI and portal before Azure PowerShell, or clarify that all options are available cross-platform.
- Add a note clarifying that all shown CLI commands work on Linux/macOS unless otherwise stated.
- Review other command snippets to ensure they are not Windows-centric and add Linux/macOS equivalents where needed.
Container Registry
Import Container Images to ACR using Azure APIs
...container-registry/container-registry-import-images.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides examples for both Azure CLI and Azure PowerShell throughout, but consistently lists Azure PowerShell examples immediately after Azure CLI, and references PowerShell in prerequisites and installation instructions. However, Azure CLI is cross-platform and all examples are equally applicable to Linux/macOS users. No Windows-specific tools, commands, or patterns are used, and there are no missing Linux/macOS examples. The only minor bias is the ordering of PowerShell examples after CLI, which may give a slight impression of Windows-first documentation.
Recommendations
- Clarify early that Azure CLI is fully cross-platform and recommended for Linux/macOS users.
- Consider explicitly mentioning that Azure PowerShell is available on Linux/macOS, or link to installation instructions for those platforms.
- If possible, add a brief note in the prerequisites section indicating that all commands shown (CLI and PowerShell) work on Linux, macOS, and Windows, except where noted.
- Optionally, provide a table or section comparing CLI and PowerShell usage across platforms.
Container Registry
Azure Container Registry SKU Features and Limits
...articles/container-registry/container-registry-skus.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for key operations (such as showing usage and changing SKU), but consistently lists PowerShell after CLI and does not provide explicit Linux/macOS shell examples or mention cross-platform parity. There are no examples for Bash scripting, and PowerShell is referenced without clarifying that Azure CLI is the recommended cross-platform tool. This may cause friction for Linux/macOS users, especially those unfamiliar with PowerShell.
Recommendations
- Clearly state that Azure CLI is cross-platform and recommended for Linux/macOS users.
- Provide explicit Bash shell examples where relevant, or clarify that Azure CLI commands work on all platforms.
- When listing both CLI and PowerShell, consider listing CLI first and labeling PowerShell as 'for Windows users' or similar.
- Add a brief section or note about tool parity for different OSes, reassuring Linux/macOS users that all features are available via CLI and REST API.
- Where PowerShell is shown, consider also showing the equivalent Bash/CLI invocation for parity.
Container Registry
Manage Public Content in Private Container Registry
...icles/container-registry/buffer-gate-public-content.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for importing images to Azure Container Registry. However, the PowerShell example is given equal prominence and is presented immediately after the CLI example, which may suggest a Windows-first or PowerShell-heavy bias. There are no explicit Linux/macOS shell examples (e.g., Bash), and no mention of Linux-specific tools or workflows. The CLI example is cross-platform, but the PowerShell example is Windows-centric. The page does not exclusively mention Windows tools, but the parity for Linux/macOS users could be improved by clarifying CLI cross-platform support and adding Bash/Linux shell context.
Recommendations
- Explicitly state that Azure CLI commands are cross-platform and can be used on Linux, macOS, and Windows.
- Add a Bash shell example or clarify that the Azure CLI example works natively in Bash and other Linux/macOS shells.
- Consider mentioning Linux-native tools (such as Docker CLI) where relevant, or provide links to Linux/macOS setup guides for Azure CLI.
- If PowerShell is shown, clarify its availability on Linux/macOS, or note that it is primarily a Windows tool.
Container Registry
Store Helm Charts in Azure Container Registry
...es/container-registry/container-registry-helm-repos.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides command examples for Helm and Azure CLI, which are cross-platform tools. However, the environment variable setting example uses the Windows-style 'set' command without showing the Linux/macOS equivalent ('export'). Additionally, the order of Kubernetes cluster creation options lists Azure CLI, PowerShell, and Portal, with PowerShell (Windows-centric) mentioned before Portal, and no explicit Linux/macOS guidance. Most commands are generic and applicable to all platforms, but minor Windows-first bias is present.
Recommendations
- Add Linux/macOS equivalents for environment variable setting (e.g., 'export ACR_NAME=<container-registry-name>') alongside the Windows 'set' command.
- Clarify that Azure CLI commands are cross-platform and provide any necessary shell-specific instructions (e.g., bash vs. cmd).
- When listing options for creating AKS clusters, consider mentioning Azure CLI and Portal first, and clarify PowerShell is Windows-specific.
- Review all command examples to ensure they work as written on Linux/macOS, and add notes or alternatives where needed.
Container Registry
Import Container Images to ACR using Azure APIs
...container-registry/container-registry-import-images.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides parallel examples for both Azure CLI and Azure PowerShell throughout, with no exclusive focus on Windows tools or patterns. However, Azure PowerShell is a Windows-centric tool, and its inclusion alongside Azure CLI (which is fully cross-platform) may be seen as a mild Windows bias. In some sections, Azure CLI examples are listed before PowerShell, but both are always present. There are no missing Linux/macOS examples, and no use of Windows-only tools or patterns outside of PowerShell.
Recommendations
- Clearly state that both Azure CLI and Azure PowerShell are supported, but Azure CLI is recommended for cross-platform (Linux/macOS/Windows) usage.
- Consider adding a short note at the top explaining that Azure CLI commands work on all platforms, while PowerShell is most common on Windows (though available cross-platform).
- If possible, add Bash or shell script examples for common workflows, or clarify that Azure CLI commands can be run in Bash, Zsh, or other shells.
- Ensure that any references to installing tools include Linux/macOS instructions (the current links do this via the Azure CLI install page).
Container Registry
Azure Container Registry SKU Features and Limits
...articles/container-registry/container-registry-skus.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for key operations (such as changing registry SKU and showing usage), but consistently lists PowerShell examples and references alongside or immediately after CLI examples. There are no Linux/macOS-specific examples or explicit mention of Linux tools, and PowerShell is referenced as a primary alternative to Azure CLI, which may create friction for Linux/macOS users who do not use PowerShell.
Recommendations
- Ensure Azure CLI examples are presented first, as CLI is cross-platform and preferred for Linux/macOS users.
- Clearly indicate that Azure PowerShell is Windows-centric, and suggest Azure CLI for Linux/macOS users.
- Where possible, provide Bash shell examples (using Azure CLI) and clarify that PowerShell examples are optional for Windows users.
- Add explicit notes or sections for Linux/macOS users, highlighting cross-platform tools and workflows.
- Avoid implying parity between Azure CLI and PowerShell unless both are equally supported on all platforms.
Container Registry
Manage Public Content in Private Container Registry
...icles/container-registry/buffer-gate-public-content.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for importing images to Azure Container Registry. However, the PowerShell example is given equal prominence and appears immediately after the CLI example, which may create friction for Linux/macOS users. There is no explicit Linux/macOS example or mention of Bash scripting, and PowerShell is primarily a Windows-centric tool, though it is available cross-platform. The documentation does not reference Linux-specific tools or workflows, and the order of examples could imply Windows/PowerShell parity or priority.
Recommendations
- Explicitly mention that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Provide Bash shell scripting examples or clarify that Azure CLI commands work natively in Bash and other Unix shells.
- Consider placing Azure CLI examples before PowerShell examples, or labeling PowerShell as 'for Windows users' if appropriate.
- Add a note that PowerShell is available cross-platform but is more commonly used on Windows.
- Include links or references to Linux/macOS-specific guidance for Azure Container Registry operations.
Container Registry
Store Helm Charts in Azure Container Registry
...es/container-registry/container-registry-helm-repos.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides command-line examples for Helm and Azure CLI, which are cross-platform tools. However, there is evidence of Windows bias in the use of the 'set' command for environment variables and the lack of explicit Linux/macOS equivalents. The environment variable setup uses 'set', which is Windows-specific, and does not mention 'export' for Linux/macOS. Most other commands are generic and applicable to all platforms, but the initial environment variable example may confuse Linux/macOS users.
Recommendations
- Provide both Windows ('set') and Linux/macOS ('export') commands for setting environment variables.
- Add a note clarifying that Azure CLI and Helm commands are cross-platform and can be run on Windows, Linux, or macOS.
- Where shell commands are shown, specify the shell context (e.g., Bash, PowerShell) or provide alternatives.
- Review all examples for platform-specific syntax and ensure parity.
Container Registry
Azure Container Registry SKU Features and Limits
...articles/container-registry/container-registry-skus.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for key operations (such as changing registry SKU and showing usage), but consistently lists PowerShell examples alongside or after CLI examples without mentioning Linux/macOS shell equivalents (e.g., Bash). There are no explicit Linux/macOS-specific instructions or examples, and PowerShell is referenced without clarifying its cross-platform availability. The documentation does not reference Windows-only tools, but the example pattern may create friction for Linux/macOS users.
Recommendations
- Clarify that Azure CLI commands work on Linux, macOS, and Windows, and are the preferred cross-platform option.
- Explicitly mention Bash or shell environments for Linux/macOS users when referencing Azure CLI.
- Consider providing Bash example blocks for Azure CLI commands, or note that the CLI syntax is identical across platforms.
- When referencing PowerShell, note its cross-platform nature or indicate that it is optional for Windows users.
- List Azure CLI examples first, as it is the most platform-neutral tool.
Container Registry
Azure Container Registry SKU Features and Limits
...articles/container-registry/container-registry-skus.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for key operations (such as changing registry SKU and showing usage), but consistently lists PowerShell examples after CLI and does not provide explicit Linux/macOS shell examples or mention Bash/Zsh. The CLI examples are cross-platform, but the PowerShell examples are Windows-centric. There is no mention of Linux-specific tools or patterns, and no explicit Bash or shell script examples.
Recommendations
- Clarify that Azure CLI commands are cross-platform and can be used on Linux, macOS, and Windows.
- Add explicit Bash/Zsh shell examples where appropriate, especially for Linux/macOS users.
- Mention that Azure PowerShell is available cross-platform, but highlight that CLI is generally preferred for Linux/macOS.
- Consider including links or notes about installing Azure CLI and PowerShell on Linux/macOS.
- Where PowerShell is referenced, add a note for Linux/macOS users about using CLI or PowerShell Core.
Container Registry
Import Container Images to ACR using Azure APIs
...container-registry/container-registry-import-images.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides examples for both Azure CLI and Azure PowerShell throughout, but consistently presents PowerShell examples alongside CLI, and references PowerShell-specific tools and patterns. There is a minor Windows bias in the use of PowerShell, which is more commonly associated with Windows environments, and in the explicit mention of PowerShell installation and usage. However, Azure CLI is cross-platform and all examples are available for it, mitigating the impact for Linux/macOS users. No Linux-specific tools or shell examples (e.g., Bash) are provided, but the CLI examples are sufficient for Linux parity.
Recommendations
- Clarify that Azure CLI is fully supported on Linux/macOS and is the recommended cross-platform option.
- Consider adding brief Bash shell example snippets for common import scenarios, or explicitly state that Azure CLI commands work identically on Linux/macOS.
- Mention that PowerShell Core is available cross-platform, but highlight Azure CLI as the default for Linux/macOS users.
- Add a note in the prerequisites section indicating that Linux/macOS users should use Azure CLI, and provide a link to CLI installation for those platforms.
Container Registry
Manage Public Content in Private Container Registry
...icles/container-registry/buffer-gate-public-content.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for importing images into Azure Container Registry. However, the PowerShell example is given equal prominence to the CLI example, and PowerShell is a Windows-centric tool, which may create friction for Linux/macOS users. Additionally, the order of tools mentioned when creating a registry lists Azure PowerShell before other tools, which subtly prioritizes Windows tooling. No Linux-specific examples or shell scripts are provided, and there is no explicit mention of Linux/macOS workflows or tools.
Recommendations
- Provide Bash or shell script examples for Linux/macOS users alongside Azure CLI and PowerShell examples.
- Clarify that Azure CLI is cross-platform and recommend it as the primary tool for Linux/macOS users.
- When listing tools, mention Azure CLI before PowerShell to avoid subtle Windows-first bias.
- Add explicit statements or links for Linux/macOS users regarding authentication and registry management workflows.
Container Registry
Azure Container Registry Authentication Options Explained
...ontainer-registry/container-registry-authentication.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Minor Windows Tools
Summary
The documentation provides authentication examples for both Azure CLI and Azure PowerShell throughout, but PowerShell is featured equally alongside CLI, which is cross-platform. However, PowerShell examples are given in every section, and the 'Next steps' section lists PowerShell before Linux-native alternatives. There are no explicit Linux/macOS examples (e.g., Bash, shell scripting), and Windows-centric tools (PowerShell) are mentioned as a primary option, even though PowerShell Core is cross-platform. The use of Docker and Azure CLI is platform-neutral, but the documentation does not highlight Linux/macOS usage or shell-specific nuances. The mention of setting DOCKER_COMMAND for Podman is a positive step for Linux parity.
Recommendations
- Add explicit Bash/shell examples for authentication flows, especially for token handling and scripting.
- Clarify that Azure CLI and Docker commands work on Linux/macOS, and provide any OS-specific notes (e.g., file paths, environment variable syntax).
- Balance 'Next steps' by including links to Linux/macOS guides or Bash-based workflows.
- Consider mentioning PowerShell Core's cross-platform nature, or linking to Linux/macOS installation guides.
- Where PowerShell is featured, also show equivalent Bash or shell scripting approaches.
Container Registry
Store Helm Charts in Azure Container Registry
...es/container-registry/container-registry-helm-repos.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is generally cross-platform, as Helm and Azure CLI are available on Windows, Linux, and macOS. However, there are subtle signs of Windows bias: the environment variable example uses the Windows 'set' command instead of the cross-platform 'export', and the prerequisites list Azure PowerShell as an option for creating AKS clusters before mentioning the Azure portal. No explicit Linux/macOS-specific instructions or examples are provided, and the 'set' command may confuse Linux/macOS users. All CLI examples otherwise use cross-platform tools (Helm, Azure CLI), but the ordering and lack of Linux/macOS parity in environment variable examples create minor friction.
Recommendations
- Replace the 'set' command for environment variables with 'export' (or show both, e.g., 'set' for Windows CMD, 'export' for Bash/Linux/macOS).
- Explicitly state that Helm and Azure CLI commands are cross-platform and provide any OS-specific notes where relevant.
- When listing options for creating AKS clusters, mention Azure CLI and Azure portal before Azure PowerShell, or clarify PowerShell is Windows-specific.
- Add a note or section for Linux/macOS users where commands differ (e.g., environment variable syntax).
Container Registry
Manage Public Content in Private Container Registry
...icles/container-registry/buffer-gate-public-content.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for importing images to Azure Container Registry. However, the PowerShell example is presented immediately after the CLI example, and PowerShell is a Windows-centric tool. There are no Linux-specific shell examples (e.g., Bash, shell scripting) or explicit mention of Linux/macOS workflows outside Azure CLI. The CLI example is cross-platform, but the inclusion of PowerShell as a primary alternative may subtly reinforce Windows-centric patterns.
Recommendations
- Clarify that Azure CLI is fully cross-platform and recommended for Linux/macOS users.
- Consider adding a Bash shell example for importing images using Docker CLI (if relevant), or explicitly state that Azure CLI commands work on Linux/macOS.
- Mention that Azure PowerShell is available on Linux/macOS, but is most commonly used on Windows.
- Add a note or section for Linux/macOS users, highlighting any differences or confirming parity.