Container Registry

149
Total Pages
126
Linux-Friendly Pages
23
Pages with Bias
15.4%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

293 issues found
Showing 126-150 of 293 flagged pages
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
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.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
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.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents 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.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
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).
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both 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.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both 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).
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page 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.
GitHub Create Pull Request
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 →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for 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.
GitHub Create Pull Request
Container Registry Manage Public Content in Private Container Registry ...icles/container-registry/buffer-gate-public-content.md
Low Priority View Details →
Scanned: 2026-03-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for importing images to Azure Container Registry, but the PowerShell example is given equal prominence and appears immediately after the CLI example. There is no explicit Linux/macOS bias, but the inclusion of PowerShell as a primary example may create friction for Linux/macOS users, as PowerShell is less commonly used on those platforms. The page does not provide shell (bash) or Linux-native command examples, nor does it mention Linux tools or patterns for registry management.
Recommendations
  • Add bash shell examples for image import, using Azure CLI, to demonstrate Linux-native workflows.
  • Clarify that Azure CLI commands are cross-platform and preferred for Linux/macOS users.
  • Consider including a note or section for Linux/macOS users, highlighting Azure CLI usage in bash/zsh shells.
  • If PowerShell is included, indicate its cross-platform availability, but prioritize CLI/bash examples for Linux/macOS parity.
GitHub Create Pull Request
Container Registry Push & Pull Container Image using Azure Container Registry ...-registry/container-registry-get-started-docker-cli.md
Low Priority View Details →
Scanned: 2026-03-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for authentication and image removal, with PowerShell examples given equal prominence. However, there is a slight Windows-first bias in listing Azure PowerShell as an option alongside Azure CLI, rather than, for example, Bash scripts or Linux-native tools. All Docker CLI commands are cross-platform, and installation links are provided for macOS, Windows, and Linux. No critical Linux/macOS gaps are present.
Recommendations
  • Clarify that Azure PowerShell is primarily for Windows/PowerShell users, and Azure CLI is cross-platform.
  • Consider listing Azure CLI examples before PowerShell, or explicitly noting that CLI is recommended for Linux/macOS.
  • Optionally, provide Bash script examples for common tasks, or mention that all Docker CLI commands work identically on Linux/macOS.
  • Ensure that any PowerShell-specific instructions are clearly marked as such.
GitHub Create Pull Request
Container Registry Quickstart - Create Registry - Bicep ...ainer-registry/container-registry-get-started-bicep.md
Low Priority View Details →
Scanned: 2026-03-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying the Bicep file, but PowerShell is mentioned alongside CLI in the introductory deployment instructions and has its own example section. The instructions for opening a terminal reference Visual Studio Code (cross-platform), but the PowerShell example may be more familiar to Windows users. No Linux-specific shell (e.g., Bash) or macOS-specific guidance is given, and PowerShell is not as commonly used on Linux/macOS. However, Azure CLI is cross-platform and is shown first.
Recommendations
  • Explicitly mention that Azure CLI commands work on Windows, Linux, and macOS, and recommend CLI for cross-platform users.
  • Add a Bash example or clarify that the CLI example is suitable for Bash/zsh terminals on Linux/macOS.
  • Consider removing or de-emphasizing PowerShell unless there is a specific need for Windows users.
  • Add a note for Linux/macOS users about using their preferred terminal and shell.
GitHub Create Pull Request
Container Registry Store Helm Charts in Azure Container Registry ...es/container-registry/container-registry-helm-repos.md
Low Priority View Details →
Scanned: 2026-03-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides command examples for Helm and Azure CLI, which are cross-platform, but in the 'Set the following environment variables' section, it uses the Windows-style 'set' command without showing the Linux/macOS equivalent ('export'). Additionally, the order of Kubernetes cluster creation options lists Azure CLI first, but includes Azure PowerShell and Portal options, which is acceptable. Overall, the bias is minor and mostly limited to the environment variable example.
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, and macOS.
  • Where shell commands are shown, indicate the shell type or provide alternatives for Bash and PowerShell if syntax differs.
GitHub Create Pull Request
Container Registry Store Helm Charts in Azure Container Registry ...es/container-registry/container-registry-helm-repos.md
Low Priority View Details →
Scanned: 2026-03-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation is largely cross-platform, as Helm and Azure CLI are available on Windows, Linux, and macOS. However, there are minor signs of Windows bias: the environment variable example uses the Windows 'set' command, and the order of Kubernetes cluster creation options lists Azure PowerShell before Linux-friendly alternatives. No Linux/macOS-specific shell examples (e.g., 'export', bash syntax) are provided alongside Windows commands, which may cause friction for non-Windows users.
Recommendations
  • Provide both Windows ('set') and Linux/macOS ('export') environment variable examples when setting variables like ACR_NAME.
  • When listing options for creating AKS clusters, mention Azure CLI (cross-platform) before Azure PowerShell (Windows-centric), or clarify platform compatibility.
  • Add notes or code blocks indicating that Azure CLI and Helm commands are cross-platform, and provide explicit bash/zsh syntax where relevant.
  • Review all code snippets to ensure they work as-is on Linux/macOS, or provide alternative commands where necessary.
GitHub Create Pull Request
Container Registry Manage Public Content in Private Container Registry ...icles/container-registry/buffer-gate-public-content.md
Low Priority View Details →
Scanned: 2026-03-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for importing images to Azure Container Registry, but consistently presents Azure CLI (Linux/macOS-friendly) examples first. However, the PowerShell example is given equal prominence, and there are no Linux-specific shell examples (e.g., Bash scripts) or explicit references to Linux tools. The documentation does not mention Windows-specific tools or patterns outside of PowerShell, nor does it prioritize Windows tools over cross-platform ones. Overall, the bias is minimal and mostly limited to the inclusion of PowerShell as a primary example, without Linux shell equivalents.
Recommendations
  • Add Bash shell script examples for common tasks, such as importing images, to improve parity for Linux/macOS users.
  • Clarify that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
  • Consider including a table or section summarizing tool availability and platform compatibility.
  • Explicitly mention that Azure PowerShell is available on Linux/macOS, or provide links to installation instructions for those platforms.
GitHub Create Pull Request
Container Registry Azure Container Registry Authentication Options Explained ...ontainer-registry/container-registry-authentication.md
Low Priority View Details →
Scanned: 2026-03-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for authentication, but PowerShell (a Windows-centric tool) is consistently presented as a primary or equal method, and is referenced throughout tables and sections. CLI examples are cross-platform, but PowerShell is not, and its prominence may confuse or frustrate Linux/macOS users. Additionally, the documentation refers to 'Connect-AzContainerRegistry' and other PowerShell cmdlets without clarifying their Windows-centric nature. However, Linux/macOS users can complete all tasks using Azure CLI and Docker, and there are some mentions of alternative tools like podman.
Recommendations
  • Clearly indicate that Azure PowerShell examples are primarily for Windows users, and that Azure CLI is recommended for Linux/macOS.
  • Present Azure CLI examples before PowerShell in tables and sections, or group them under OS-specific tabs.
  • Reduce the prominence of PowerShell in general explanations unless the feature is Windows-only.
  • Explicitly state that all tasks can be completed with Azure CLI and Docker (or podman), and provide links to cross-platform installation guides.
  • Consider adding a short section or callout for Linux/macOS users, summarizing the recommended tools and commands.
GitHub Create Pull Request
Container Registry Import Container Images to ACR using Azure APIs ...container-registry/container-registry-import-images.md
Low Priority View Details →
Scanned: 2026-03-09 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides examples for both Azure CLI and Azure PowerShell throughout, but consistently lists PowerShell examples immediately after CLI, and references PowerShell as a primary tool alongside CLI. There are no explicit Windows-only tools or commands, and Azure CLI is cross-platform. However, PowerShell is traditionally associated with Windows, and its inclusion may signal a slight Windows bias, especially since no Bash or Linux-specific shell examples are provided. The documentation does not mention Linux/macOS tools or patterns, nor does it provide Bash or shell script equivalents.
Recommendations
  • Add Bash or shell script examples for common import scenarios, especially since Azure CLI is cross-platform and widely used on Linux/macOS.
  • Clarify that Azure CLI commands can be run on Linux/macOS, and provide guidance for those environments (e.g., installation links, shell usage).
  • Consider referencing Linux/macOS environments explicitly in prerequisites and examples to reinforce parity.
  • If PowerShell is included for completeness, note that it is available cross-platform, but also provide Bash alternatives.
GitHub Create Pull Request
Container Registry Quickstart - Create Registry - Bicep ...ainer-registry/container-registry-get-started-bicep.md
Low Priority View Details →
Scanned: 2026-03-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides deployment instructions for both Azure CLI and PowerShell, but PowerShell is mentioned alongside CLI in the initial deployment section and is given its own example. The instructions for opening a terminal reference Visual Studio Code (cross-platform), but the key combination (ctrl + `) is Windows-centric. PowerShell is included as a primary option, which is more common on Windows, while Bash or Linux-specific instructions are not explicitly highlighted. There are no Linux/macOS-specific examples or explicit mention of Bash terminals, and PowerShell is presented as a first-class option.
Recommendations
  • Add explicit Bash/Linux/macOS terminal instructions alongside PowerShell and Azure CLI.
  • Clarify that Azure CLI commands work on Windows, Linux, and macOS, and provide Bash-specific guidance where relevant.
  • Mention common Linux/macOS terminal key combinations for opening the integrated terminal in Visual Studio Code.
  • Consider showing Azure CLI (Bash) examples first, or at least equally with PowerShell.
  • Add a note that PowerShell is available cross-platform, but Bash is the default shell on Linux/macOS.
GitHub Create Pull Request
Container Registry Push & Pull Container Image using Azure Container Registry ...-registry/container-registry-get-started-docker-cli.md
Low Priority View Details →
Scanned: 2026-03-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell authentication/removal examples, with PowerShell examples given equal prominence. However, PowerShell is a Windows-centric tool, and its inclusion alongside Azure CLI (which is cross-platform) may create a perception of Windows bias. Additionally, keyboard shortcuts for stopping containers ('Ctrl+C') are described generically but may be more familiar to Windows users. The order of listing installation links (macOS, Windows, Linux) and the use of PowerShell tabs may also subtly favor Windows users.
Recommendations
  • Ensure that Linux/macOS users are equally represented by providing Bash or shell script examples where appropriate, especially for automation scenarios.
  • Clarify that Azure CLI is fully cross-platform and recommend it as the default for non-Windows environments.
  • Consider adding explicit Bash examples for authentication and image removal, or note that Azure CLI commands are suitable for Linux/macOS.
  • If PowerShell is included, mention that it is available cross-platform (via PowerShell Core), but clarify its typical usage scenarios.
  • Review the order of installation links and examples to avoid subtle Windows-first ordering.
GitHub Create Pull Request
Container Registry Manage Public Content in Private Container Registry ...icles/container-registry/buffer-gate-public-content.md
Low Priority View Details →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for importing images into Azure Container Registry. However, the Azure CLI example (which is cross-platform and Linux-friendly) is presented first, followed by the Azure PowerShell example. No Windows-specific tools or patterns are mentioned exclusively, and there are no missing Linux/macOS examples. The overall workflow and recommendations are platform-neutral, focusing on Azure services and Docker, which are cross-platform.
Recommendations
  • Maintain the Azure CLI example as the primary example, since it is cross-platform.
  • Consider explicitly mentioning that Azure CLI works on Linux, macOS, and Windows, while Azure PowerShell is most commonly used on Windows.
  • If possible, add a brief note clarifying that all shown workflows are supported on Linux/macOS unless otherwise stated.
  • Ensure parity in future updates by providing Bash or shell script examples if automation is discussed.
  • No changes are strictly required, but clarifying platform support can further improve Linux/macOS user experience.
GitHub Create Pull Request
Container Registry Quickstart - Create Registry - Bicep ...ainer-registry/container-registry-get-started-bicep.md
Low Priority View Details →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying the Bicep file, but PowerShell is mentioned alongside CLI in the instructions and is given its own tab. There is a minor Windows bias in that PowerShell is referenced and the Visual Studio Code terminal shortcut (Ctrl+`) is Windows-centric, but Linux users are not blocked from completing the task. The CLI example is cross-platform and appears first.
Recommendations
  • Clarify that Azure CLI is fully cross-platform and can be used on Linux/macOS.
  • Mention Bash or other Linux/macOS terminals as alternatives to PowerShell and Visual Studio Code terminal.
  • Provide explicit instructions or shortcuts for opening terminals on Linux/macOS.
  • Consider listing Azure CLI instructions before PowerShell in all sections.
  • Add a note that PowerShell Core is available cross-platform, but Bash is the default shell on Linux/macOS.
GitHub Create Pull Request
Container Registry Azure Container Registry Authentication Options Explained ...ontainer-registry/container-registry-authentication.md
Low Priority View Details →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Minor Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for authentication, with PowerShell examples and references present throughout. In several places, PowerShell is mentioned alongside CLI, and in the main authentication options table, PowerShell commands are often listed after CLI but before mentioning Linux-specific alternatives. However, the CLI examples are cross-platform and the documentation does mention using alternative container tools (like podman) and provides bash-style variable assignment, which is Linux-friendly. There are no sections that are Windows-only, and Linux users can complete all tasks described.
Recommendations
  • Continue to present Azure CLI examples first, as these are cross-platform, but consider explicitly stating that Azure CLI commands work on Linux, macOS, and Windows.
  • Where PowerShell is referenced, clarify that Azure PowerShell is available cross-platform, or provide bash/zsh equivalents where relevant.
  • In the authentication options table, consider listing CLI-only or bash-native options before PowerShell, or clearly marking PowerShell as optional for Windows users.
  • Expand the section on alternative container tools to include a brief example for Linux/macOS users using bash/zsh, if any differences exist.
  • Where environment variables are set (e.g., DOCKER_COMMAND), clarify that the syntax shown is bash/zsh and works on Linux/macOS.
GitHub Create Pull Request
Container Registry Push & Pull Container Image using Azure Container Registry ...-registry/container-registry-get-started-docker-cli.md
Low Priority View Details →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell authentication and image removal examples, but PowerShell examples are given equal prominence and are not clearly marked as Windows-only. The PowerShell sections may create friction for Linux/macOS users, as PowerShell is not the default shell on those platforms. Additionally, in the prerequisites, Windows is mentioned before Linux/macOS in the Docker installation links, and PowerShell is listed as a way to create a registry before the Azure CLI.
Recommendations
  • Clearly indicate that Azure PowerShell examples are primarily for Windows users, and recommend Azure CLI for Linux/macOS.
  • Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and more widely used outside Windows.
  • Add explicit notes or tabs clarifying which commands are platform-specific, and provide parity for Linux/macOS users.
  • In prerequisites, list Linux/macOS before Windows or alphabetically to avoid subtle Windows-first bias.
  • Where possible, avoid suggesting PowerShell as a primary method for tasks that can be accomplished with Azure CLI.
GitHub Create Pull Request
Container Registry Store Helm Charts in Azure Container Registry ...es/container-registry/container-registry-helm-repos.md
Low Priority View Details →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
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 Windows biases: the environment variable setup uses the Windows 'set' command without a Linux/macOS equivalent, and the order of Kubernetes cluster creation options lists Azure PowerShell before the Azure portal and Azure CLI. No explicit Linux/macOS examples are provided for environment variable setup, and the 'set' command may confuse non-Windows users.
Recommendations
  • Provide both Windows and Linux/macOS commands for setting environment variables (e.g., 'set' for Windows, 'export' for Linux/macOS).
  • When listing options for creating AKS clusters, mention cross-platform tools (Azure CLI) first, or clarify which options are platform-specific.
  • Add notes or callouts indicating that all CLI commands (Helm, Azure CLI) are cross-platform, and provide links to installation guides for Linux/macOS.
  • Review all example commands to ensure they are either platform-neutral or include both Windows and Linux/macOS variants.
GitHub Create Pull Request
Container Registry Import Container Images to ACR using Azure APIs ...container-registry/container-registry-import-images.md
Low Priority View Details →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides parallel examples for both Azure CLI and Azure PowerShell throughout, but PowerShell is featured equally and sometimes first, which may create friction for Linux/macOS users. There are no explicit Linux/macOS-specific examples or notes, and PowerShell is not a native shell on Linux/macOS, though it is available. No Windows-only tools or patterns are used, and the CLI examples are cross-platform. However, the documentation does not mention Bash or other Linux-native shells, nor does it clarify that Azure CLI is preferred for Linux/macOS users.
Recommendations
  • Explicitly state that Azure CLI is cross-platform and preferred for Linux/macOS users, while PowerShell is optional.
  • Add a note clarifying that PowerShell examples are also usable on Linux/macOS if PowerShell Core is installed, but Azure CLI is more common.
  • Consider showing Azure CLI examples first, as it is the default shell in Azure Cloud Shell and is more widely used on Linux/macOS.
  • Add a brief section or FAQ addressing usage from Linux/macOS environments, confirming parity and any caveats.
GitHub Create Pull Request
Container Registry Azure Container Registry Authentication Options Explained ...ontainer-registry/container-registry-authentication.md
Low Priority View Details →
Scanned: 2026-03-07 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for authentication, but PowerShell is consistently presented as a first-class option alongside CLI, and in some sections, PowerShell is given equal or slightly more prominence than Linux-native workflows. However, Linux/macOS users are not blocked, as all critical flows are covered with Azure CLI and Docker commands, which are cross-platform. There is a minor 'windows_first' bias in the authentication options table, where PowerShell is listed before Docker-native or Linux-native alternatives in some cases.
Recommendations
  • Clearly indicate that Azure PowerShell is optional and primarily for users who prefer it (typically Windows users), while Azure CLI is cross-platform and recommended for Linux/macOS.
  • In tables and code blocks, list Azure CLI (cross-platform) examples before PowerShell to reinforce Linux parity.
  • Add explicit notes that all CLI commands work on Linux/macOS, and clarify that Docker and Podman are supported on all platforms.
  • Where PowerShell is mentioned, consider adding a short note that Bash/CLI is the default for Linux/macOS users.
  • Ensure that all sections referencing PowerShell have equivalent CLI/Bash examples, and vice versa.
GitHub Create Pull Request
← Previous Page 6 of 12 Next →