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 51-75 of 183 flagged pages
Container Registry Azure Container Registry Authentication Options Explained ...ontainer-registry/container-registry-authentication.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides authentication instructions for Azure Container Registry using both Azure CLI and Azure PowerShell, but PowerShell examples and references are prominent throughout. PowerShell is a Windows-centric tool, and its usage is presented alongside Azure CLI, which is cross-platform. However, there are no explicit Linux/macOS-specific examples, such as shell scripting or Bash usage. The order of examples often places PowerShell immediately after Azure CLI, and references to PowerShell are frequent. There are no Linux-specific tools or patterns (e.g., Bash, environment variables, shell scripting) highlighted, and the 'Next steps' section links to both CLI and PowerShell guides, but not to Linux/macOS-specific workflows.
Recommendations
  • Add explicit Bash/shell scripting examples for Linux/macOS users, especially for token handling and environment variable usage.
  • Clarify that Azure CLI is cross-platform and provide guidance for installing and using it on Linux/macOS.
  • Include Linux/macOS-specific instructions for Docker installation and configuration, as these differ from Windows.
  • Consider adding a 'Linux/macOS' tab or section for authentication workflows, showing common shell commands and patterns.
  • Balance PowerShell references with Bash or shell equivalents to ensure parity.
GitHub Create Pull Request
Container Registry Azure Container Registry Authentication Options Explained ...ontainer-registry/container-registry-authentication.md
Medium Priority View Details →
Scanned: 2026-02-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides authentication examples for both Azure CLI and Azure PowerShell, but PowerShell examples are given equal prominence throughout, despite PowerShell being primarily a Windows tool. Azure CLI examples are cross-platform, but there are no explicit Linux/macOS shell examples (e.g., Bash), and the CLI examples do not clarify Linux-specific nuances. PowerShell is mentioned in every authentication table row, and the 'Next steps' section links to both CLI and PowerShell guides, but not to Linux/macOS-specific workflows. The documentation does mention using alternative container tools (like podman), but this is a brief section and lacks detailed Linux/macOS guidance.
Recommendations
  • Clarify that Azure CLI commands are cross-platform and provide explicit Bash/zsh examples for Linux/macOS users.
  • Reduce the prominence of PowerShell unless a Windows-specific workflow is required; consider moving PowerShell examples to a separate section or tab.
  • Add Linux/macOS-specific guidance for authentication, including environment variable usage and shell scripting patterns.
  • Include links to Linux/macOS getting started guides in the 'Next steps' section.
  • Expand the 'alternative container tool' section with more detailed podman/skopeo examples and troubleshooting tips for Linux/macOS environments.
GitHub Create Pull Request
Container Registry Azure Container Registry Authentication Options Explained ...ontainer-registry/container-registry-authentication.md
Medium Priority View Details →
Scanned: 2026-02-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for authentication, but PowerShell is given equal prominence to CLI, which is less relevant for Linux/macOS users. In several sections, PowerShell is presented as a primary option alongside CLI, and there are no explicit Linux/macOS-specific examples or notes. The use of PowerShell commands and terminology may create friction for non-Windows users. Additionally, while the CLI is cross-platform, the documentation does not clarify this, nor does it provide shell-specific guidance (e.g., bash, zsh) or address Linux/macOS credential storage nuances.
Recommendations
  • Clearly indicate that Azure CLI commands are cross-platform and preferred for Linux/macOS users.
  • De-emphasize PowerShell by presenting CLI examples first and PowerShell as an alternative, or move PowerShell examples to a separate tab or section labeled 'Windows/PowerShell'.
  • Add explicit Linux/macOS shell examples (e.g., bash, zsh) for environment variable usage and credential management.
  • Include notes or tips about credential storage locations and behaviors on Linux/macOS (e.g., where docker config files are stored).
  • Where relevant, mention that PowerShell Core is available cross-platform, but clarify that most Linux/macOS users will use bash/zsh with Azure CLI.
GitHub Create Pull Request
Container Registry Import Container Images to ACR using Azure APIs ...container-registry/container-registry-import-images.md
Medium Priority View Details →
Scanned: 2026-02-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides examples for both Azure CLI and Azure PowerShell throughout, but there is a notable emphasis on PowerShell, which is primarily a Windows-centric tool. Azure CLI is cross-platform, but PowerShell examples are given equal prominence, and in some cases, PowerShell-specific instructions (such as module installation) are mentioned. There are no Linux/macOS-specific examples or notes about using Azure CLI on those platforms, and PowerShell is presented as a primary alternative, which may create friction for Linux/macOS users.
Recommendations
  • Clearly indicate that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
  • Add brief notes or links about running Azure CLI on Linux/macOS, including installation instructions.
  • Consider demoting PowerShell examples to a secondary position or clarifying their relevance for Windows users.
  • Add troubleshooting tips relevant to Linux/macOS environments (e.g., shell differences, authentication issues).
  • Explicitly state that all Azure CLI commands work on Linux/macOS unless otherwise noted.
GitHub Create Pull Request
Container Registry Azure Container Registry Authentication Options Explained ...ontainer-registry/container-registry-authentication.md
Medium Priority View Details →
Scanned: 2026-02-05 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for authentication, but PowerShell is given equal prominence to CLI, despite being Windows-centric. Most command examples are cross-platform (Azure CLI, Docker), but PowerShell examples are included throughout, and in some cases, CLI and PowerShell are presented as equivalent options. There is no explicit mention of Linux/macOS shell usage (e.g., Bash), and the order of examples often lists PowerShell alongside or immediately after CLI, rather than prioritizing cross-platform tools. There are no Linux-specific authentication patterns or troubleshooting notes, and the 'Next steps' section links to PowerShell and CLI guides, but not to Linux/macOS shell-specific guides.
Recommendations
  • Prioritize Azure CLI and Docker examples, as these are cross-platform, and list them before PowerShell examples.
  • Explicitly mention that Azure CLI and Docker commands work on Linux/macOS, and provide sample Bash syntax where appropriate (e.g., environment variable usage, piping).
  • Add troubleshooting notes or tips for Linux/macOS users, such as file permission issues with Docker config, or differences in environment variable syntax.
  • Consider adding a 'Linux/macOS authentication' section or callout to reassure non-Windows users of parity.
  • Review the 'Next steps' section to include links to Linux/macOS getting started guides, if available.
GitHub Create Pull Request
Container Registry Store Helm Charts in Azure Container Registry ...es/container-registry/container-registry-helm-repos.md
Medium Priority View Details →
Scanned: 2026-02-05 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page provides command-line examples for managing Helm charts in Azure Container Registry, but several commands use Windows-style syntax (e.g., 'set' for environment variables) and do not provide Linux/macOS equivalents. The environment variable setup uses 'set', which is only valid in Windows CMD, while most other commands use Bash syntax. No explicit PowerShell examples are present, and most Azure CLI and Helm commands are cross-platform, but the initial environment variable example may confuse Linux/macOS users.
Recommendations
  • Provide both Windows (CMD/PowerShell) and Linux/macOS (Bash) syntax for environment variable setup. For example, use 'export ACR_NAME=<container-registry-name>' for Bash and 'set ACR_NAME=<container-registry-name>' for CMD.
  • Add a note clarifying which commands are platform-specific and which are cross-platform.
  • Ensure all example commands are shown in both Bash and Windows syntax where differences exist.
  • Consider using Bash syntax as the default, since most cloud-native and Kubernetes users are on Linux/macOS.
GitHub Create Pull Request
Container Registry Store Helm Charts in Azure Container Registry ...es/container-registry/container-registry-helm-repos.md
Medium Priority View Details →
Scanned: 2026-02-03 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides command-line examples for Helm and Azure CLI, which are cross-platform, but some environment variable setting instructions use Windows-style syntax (e.g., 'set ACR_NAME=<container-registry-name>') without showing Linux/macOS equivalents. The order of Kubernetes cluster creation instructions lists Azure CLI, PowerShell, and Portal, with PowerShell (Windows-centric) mentioned before Portal. No explicit Linux/macOS shell examples are provided for environment variables, which may cause confusion for non-Windows users.
Recommendations
  • For all environment variable instructions, provide both Windows (cmd.exe) and Linux/macOS (bash/zsh) syntax, e.g., 'set ACR_NAME=...' and 'export ACR_NAME=...'.
  • When listing options for creating resources (e.g., AKS clusters), consider listing cross-platform tools (Azure CLI, Portal) before Windows-specific tools (PowerShell), or clarify platform applicability.
  • Add a note clarifying that all Azure CLI and Helm commands work on Linux/macOS and Windows, and provide shell-specific guidance where relevant.
  • Where sample commands use shell features (e.g., heredoc, environment variables), clarify syntax differences for Windows and Linux/macOS users.
GitHub Create Pull Request
Container Registry Store Helm Charts in Azure Container Registry ...es/container-registry/container-registry-helm-repos.md
Medium Priority View Details →
Scanned: 2026-02-01 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page provides command-line examples for Helm and Azure CLI, which are cross-platform tools. However, there is a notable Windows bias in the use of the 'set' command for environment variable assignment, which is specific to Windows CMD. There are no Linux/macOS equivalents (e.g., 'export') shown for setting environment variables. All other commands are platform-agnostic, but the initial environment variable setup may confuse or hinder Linux/macOS users.
Recommendations
  • Provide both Windows ('set') and Linux/macOS ('export') examples when setting environment variables.
  • Add a note clarifying which commands are platform-specific and which are cross-platform.
  • Consider showing Linux/macOS examples first or side-by-side, as most Kubernetes/Helm users are on Linux/macOS.
GitHub Create Pull Request
Container Registry Store Helm Charts in Azure Container Registry ...es/container-registry/container-registry-helm-repos.md
Medium Priority View Details →
Scanned: 2026-01-31 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page provides command-line examples for managing Helm charts in Azure Container Registry, but in several places, it defaults to Windows-style commands (e.g., 'set' for environment variables) and does not consistently provide Linux/macOS equivalents. The Azure CLI and Helm commands themselves are cross-platform, but some setup steps and environment variable instructions are Windows-centric, which may cause confusion or friction for Linux/macOS users.
Recommendations
  • For environment variable setup, provide both Windows (e.g., 'set') and Linux/macOS (e.g., 'export') command examples side-by-side.
  • Explicitly state that Azure CLI and Helm commands work on Windows, Linux, and macOS, and clarify any OS-specific differences.
  • Where file operations are shown (e.g., 'rm -rf *'), clarify that these are Unix-style and provide Windows equivalents if relevant.
  • Review all code blocks to ensure parity, especially in authentication and setup sections, so Linux/macOS users are not left to infer the correct commands.
GitHub Create Pull Request
Container Registry Store Helm Charts in Azure Container Registry ...es/container-registry/container-registry-helm-repos.md
Medium Priority View Details →
Scanned: 2026-01-27 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
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 a subtle Windows bias in the use of the set command for environment variables ("set ACR_NAME=<container-registry-name>"), which is specific to Windows CMD. No Linux/macOS equivalent ("export ACR_NAME=<container-registry-name>") is shown. Additionally, the order of Kubernetes cluster creation options lists Azure CLI first, then Azure PowerShell, then Azure portal, but does not mention Linux/macOS shell usage explicitly. Most examples use generic 'console' or 'azurecli' code blocks, which are cross-platform, but the initial environment variable setup could cause friction for Linux/macOS users.
Recommendations
  • Provide both Windows (set) and Linux/macOS (export) examples when setting environment variables.
  • Explicitly mention that Azure CLI and Helm commands work on Linux/macOS, and clarify any platform-specific differences.
  • Use code block annotations (e.g., bash, powershell) to clarify the intended shell for each example.
  • Add a note or table showing equivalent commands for Windows CMD, PowerShell, and Linux/macOS Bash where relevant.
GitHub Create Pull Request
Container Registry Azure Container Registry Authentication Options Explained ...ontainer-registry/container-registry-authentication.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for authentication, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI throughout, and is referenced in nearly every authentication scenario. Examples and instructions for Linux-native workflows (e.g., Bash, shell scripting) are minimal, and PowerShell is presented before or alongside CLI in most cases. There are no explicit Linux/macOS shell script examples for common tasks (e.g., using environment variables, credential management), and the 'Next steps' section only links to Azure CLI and PowerShell guides, omitting Linux-specific or cross-platform container tool guides. The section on alternative container tools (podman) is brief and lacks detailed Linux workflow examples.
Recommendations
  • Add explicit Bash/shell script examples for authentication flows, especially for service principal and token-based logins.
  • Include Linux/macOS-specific instructions for credential management and environment variable usage.
  • Expand the section on alternative container tools (podman) with step-by-step Linux workflow examples, including troubleshooting and best practices.
  • In 'Next steps', link to cross-platform container tool guides (e.g., podman, nerdctl) and Linux/macOS getting started guides.
  • Consider presenting Azure CLI (cross-platform) examples before PowerShell, and clarify that PowerShell is primarily for Windows users.
GitHub Create Pull Request
Container Registry Quickstart - Create Registry - Bicep ...ainer-registry/container-registry-get-started-bicep.md
Medium Priority View Details →
Scanned: 2026-01-14 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 presented as an equal option and is mentioned in the instructions to 'open PowerShell or Azure CLI.' The instructions for opening the integrated Visual Studio Code terminal use the 'ctrl + ` ' shortcut, which is Windows-centric. There are no explicit Linux/macOS examples or notes about platform differences, and PowerShell is not natively available on Linux/macOS by default. The documentation does not mention Bash or shell alternatives, nor does it clarify cross-platform usage for PowerShell.
Recommendations
  • Clarify that Azure CLI commands work on Windows, Linux, and macOS, and recommend it as the default cross-platform option.
  • Add explicit Bash/shell instructions or notes for Linux/macOS users, including how to open the terminal in VS Code on those platforms.
  • Note that PowerShell Core is available on Linux/macOS, but Azure CLI is typically more common for cross-platform scenarios.
  • Present Azure CLI examples first, as it is the most universally available tool.
GitHub Create Pull Request
Container Registry Push & Pull Container Image using Azure Container Registry ...-registry/container-registry-get-started-docker-cli.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for authentication and image removal, but PowerShell examples are given equal prominence despite being Windows-specific. There are no explicit Linux shell (bash) or macOS Terminal examples for Azure authentication or image removal, and Windows-centric tools (PowerShell, Visual Studio Code) are mentioned before Linux alternatives. Minor friction exists for Linux/macOS users who may prefer bash or shell scripting over PowerShell.
Recommendations
  • Add explicit bash/shell examples for Azure authentication and image removal, using Azure CLI and native shell commands.
  • Clarify that PowerShell examples are primarily for Windows users, and provide equivalent steps for Linux/macOS users.
  • Mention Linux/macOS-friendly editors (e.g., VS Code is cross-platform, but alternatives like JetBrains IDEs or command-line workflows could be referenced).
  • Ensure that CLI examples are shown before or alongside PowerShell examples, and label tabs clearly for each platform.
GitHub Create Pull Request
Container Registry Error Reference for Registry Health Checks ...-registry/container-registry-health-error-reference.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation generally describes errors and solutions in a cross-platform manner, referencing CLI tools (Docker, Helm, Notary) that are available on Windows, Linux, and macOS. However, some sections show Windows bias: Windows paths and .exe files are mentioned first or exclusively (e.g., Notary client installation), environment variable instructions use Windows terminology ('system variables'), and Linux/macOS installation paths/examples are less detailed or omitted. There are no explicit Linux/macOS command examples or troubleshooting steps, which may create friction for non-Windows users.
Recommendations
  • Provide Linux/macOS-specific installation instructions and paths alongside Windows examples (e.g., where to place Notary binaries, how to update PATH).
  • Use cross-platform terminology for environment variables (e.g., 'system environment variables' vs. 'PATH variable'), and give examples for both Windows (setx, GUI) and Linux/macOS (export, ~/.bashrc, ~/.zshrc).
  • When referencing executables, clarify platform differences (e.g., notary.exe for Windows, notary for Linux/macOS).
  • Add troubleshooting steps and example commands for Linux/macOS users where relevant.
GitHub Create Pull Request
Container Registry Import Container Images to ACR using Azure APIs ...container-registry/container-registry-import-images.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides examples exclusively for Azure CLI and Azure PowerShell, with no mention of Linux/macOS-specific shell environments or command patterns. PowerShell examples are given equal prominence to CLI, and in some sections, Windows-specific images (e.g., Windows Server Core) are highlighted. There are no bash or Linux-native command examples, nor any discussion of platform-specific considerations for Linux/macOS users.
Recommendations
  • Add explicit bash examples for Linux/macOS users, especially for Azure CLI commands, demonstrating usage in typical Linux shells.
  • Clarify that Azure CLI commands work cross-platform and provide notes or examples for Linux/macOS environments (e.g., using bash, zsh, etc.).
  • When referencing PowerShell, note its availability on Linux/macOS, or provide equivalent bash commands where possible.
  • Avoid highlighting Windows container images unless the scenario is Windows-specific; provide parity by showing Linux container image examples (e.g., Ubuntu, Alpine) alongside Windows ones.
  • Include troubleshooting notes for common Linux/macOS issues (e.g., authentication, environment variables, shell quoting).
GitHub Create Pull Request
Container Registry Store Helm Charts in Azure Container Registry ...es/container-registry/container-registry-helm-repos.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page 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 variable assignment, which is specific to Windows CMD. No equivalent Linux/macOS example (e.g., 'export') is provided. Additionally, the order of Kubernetes cluster creation options lists Azure CLI first, but also mentions Azure PowerShell and Azure Portal, which is acceptable. Most other commands use Bash-style syntax, which is cross-platform, but the initial environment variable example may cause confusion for Linux/macOS users.
Recommendations
  • Provide both Windows and Linux/macOS environment variable assignment examples (e.g., 'set' for Windows CMD, 'export' for Bash).
  • Clarify which commands are platform-specific and offer alternatives where needed.
  • Consider using Bash syntax for environment variables throughout, as Azure CLI and Helm are typically used in Bash on all platforms.
  • Add a note or table summarizing command differences for Windows, Linux, and macOS users.
GitHub Create Pull Request
Container Registry Import Container Images to ACR using Azure APIs ...container-registry/container-registry-import-images.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides examples for both Azure CLI and Azure PowerShell throughout, but PowerShell is a Windows-centric tool and is featured equally alongside CLI. There is a notable Windows bias in the 'Import from Microsoft Container Registry' section, where the only example given is for a Windows Server Core image. There are no explicit Linux/macOS examples (e.g., importing Ubuntu or Alpine images), nor is there mention of Linux-specific patterns or tools. The documentation does not mention platform-specific issues or considerations for Linux/macOS users, and Windows images are highlighted before any Linux equivalents.
Recommendations
  • Add examples importing popular Linux images (e.g., Ubuntu, Alpine, nginx) from public registries and Microsoft Container Registry.
  • Explicitly state that Azure CLI and PowerShell are cross-platform, but clarify installation and usage differences for Linux/macOS users.
  • Include troubleshooting notes or caveats for Linux/macOS environments if any exist.
  • Balance examples by alternating between Windows and Linux image imports, or provide both in each relevant section.
  • Mention that Azure CLI is natively available on Linux/macOS and provide links to installation guides for those platforms.
GitHub Create Pull Request
Container Registry Azure Container Registry Authentication Options Explained ...ontainer-registry/container-registry-authentication.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. Examples and instructions are frequently given for Azure PowerShell and Azure CLI, with PowerShell examples present throughout. Windows-centric tools and patterns (PowerShell, Azure portal UI) are mentioned before or alongside CLI examples, but Linux/macOS-specific workflows are not explicitly covered. While Docker is referenced as the default container tool, Linux alternatives like Podman are only briefly mentioned near the end, and there are no explicit bash or Linux shell examples. There are no direct instructions for Linux/macOS users on installing prerequisites, handling authentication, or troubleshooting common platform-specific issues.
Recommendations
  • Add explicit Linux/macOS shell examples (bash/zsh) for authentication workflows alongside PowerShell.
  • Provide installation and troubleshooting guidance for Azure CLI and Docker/Podman on Linux/macOS.
  • Include Linux/macOS-specific notes for environment setup, such as file paths, permissions, and common errors.
  • Present CLI (cross-platform) examples before PowerShell/Windows-specific ones.
  • Expand the section on alternative container tools to include more details and examples for Podman and other Linux-native tools.
  • Clarify that all authentication methods work on Linux/macOS, and highlight any platform-specific caveats.
GitHub Create Pull Request
Container Registry Quickstart - Create Registry - Bicep ...ainer-registry/container-registry-get-started-bicep.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying the Bicep file, but PowerShell is featured as a primary option and is mentioned before Linux alternatives. The instructions reference opening PowerShell or Azure CLI, but do not explicitly mention Bash or Linux/macOS terminals. There are no Linux-specific examples or guidance for users on non-Windows platforms, and the use of Visual Studio Code is suggested without alternatives for Linux/macOS users.
Recommendations
  • Explicitly mention Bash or Linux/macOS terminal as an option for running Azure CLI commands.
  • Provide Linux/macOS-specific instructions or examples, such as using Bash with Azure CLI.
  • Reorder examples so that Azure CLI (cross-platform) is shown before PowerShell.
  • Clarify that Visual Studio Code is available on Linux/macOS, or suggest alternative editors for those platforms.
  • Add a note or section for Linux/macOS users to ensure parity and inclusivity.
GitHub Create Pull Request
Container Registry Error Reference for Registry Health Checks ...-registry/container-registry-health-error-reference.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation occasionally references Windows-specific tools and paths (e.g., notary.exe, C:\ProgramFiles\Docker\Docker\resources\bin) and mentions adding executables to 'system variables' without clarifying Linux/macOS equivalents. Windows instructions are sometimes given before Linux/macOS, and there are missing explicit examples for Linux/macOS users regarding environment variable configuration and binary placement.
Recommendations
  • For each mention of adding executables to 'system variables', provide explicit Linux/macOS instructions (e.g., updating $PATH in ~/.bashrc or ~/.zshrc).
  • When referencing binary installation paths (e.g., Notary), include typical Linux/macOS locations (such as /usr/local/bin) alongside Windows paths.
  • Ensure that download and installation instructions for tools like Notary are equally detailed for Linux/macOS, not just referencing Windows .exe files and paths.
  • Present cross-platform instructions in parallel, or clarify OS-specific steps, rather than defaulting to Windows-first.
  • Where possible, provide command-line examples for both Windows (PowerShell/CMD) and Linux/macOS (bash/zsh).
GitHub Create Pull Request
Container Registry Customer intent: "As a security analyst, I want to view vulnerability assessment results for container images, so that I can ensure all security issues are identified and resolved in our container registry." ...ontainer-registry/includes/azure-container-registry.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples, but PowerShell is a Windows-centric tool and is presented as a primary tab. There is no explicit mention of Linux/macOS-specific instructions or shell environments, and PowerShell is listed before the portal options. No Linux shell (bash, zsh) or cross-platform scripting alternatives are discussed.
Recommendations
  • Clarify that Azure CLI works natively on Linux/macOS and provide explicit bash/zsh example usage.
  • Add notes or examples for running Azure CLI queries in Linux/macOS terminals, including any OS-specific considerations (e.g., quoting, line breaks).
  • If PowerShell is shown, clarify its cross-platform availability, but avoid implying it is required for Linux/macOS users.
  • Consider listing Azure CLI before PowerShell, as CLI is the most cross-platform tool.
  • Add troubleshooting or environment setup notes for Linux/macOS users if needed.
GitHub Create Pull Request
Container Registry Kubernetes Pull Secret for ACR Authentication ...ntainer-registry/container-registry-auth-kubernetes.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation provides an example for resetting a service principal password using the Azure CLI, which is cross-platform, but does not mention or provide examples for Linux-specific tools or workflows. There are no PowerShell-specific commands, but the lack of Linux-specific context (such as shell differences, credential storage, or alternative authentication patterns) and exclusive mention of Azure CLI (often associated with Windows usage) may suggest a subtle Windows bias. No Linux-first or Linux-only examples are present.
Recommendations
  • Explicitly mention that Azure CLI is cross-platform and provide installation instructions for Linux users.
  • Include Linux-specific notes, such as using bash environment variables for secrets, or referencing Linux credential managers.
  • Add examples or links for using kubectl and Azure CLI on Linux, including any differences in authentication or environment setup.
  • Clarify that all commands work on Linux, macOS, and Windows, and highlight any OS-specific considerations.
GitHub Create Pull Request
Container Registry Store Helm Charts in Azure Container Registry ...es/container-registry/container-registry-helm-repos.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
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 by using Windows-style commands (e.g., 'set' for environment variables) and omitting Linux/macOS equivalents. The environment variable setup uses 'set', which is specific to Windows CMD, without providing the more common 'export' command for Bash on Linux/macOS. No PowerShell-specific commands are present, but the lack of Linux/Bash parity in examples may hinder non-Windows users. The rest of the CLI commands are cross-platform, but the initial environment variable setup is Windows-centric.
Recommendations
  • Provide both Windows (CMD/PowerShell) and Linux/macOS (Bash) command examples for environment variable setup, e.g., 'set' and 'export'.
  • Add a note clarifying which commands are platform-specific and which are cross-platform.
  • Ensure all code snippets are tested and presented for both major platforms, especially for setup steps.
  • Consider using platform-agnostic variable assignment in documentation, or provide tabs/switchers for Windows and Linux/macOS users.
GitHub Create Pull Request
Container Registry Azure Container Registry Entra permissions and role assignments overview ...try/container-registry-rbac-built-in-roles-overview.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page lists Azure CLI, Azure PowerShell, and Azure Portal as the primary tools for performing role assignments, with PowerShell mentioned explicitly and equally alongside CLI and Portal. There are no explicit Linux-specific examples, nor is Bash or Linux terminal usage referenced. The documentation does not provide parity for Linux users in terms of command-line examples or tool recommendations, and PowerShell (primarily a Windows tool, though available on Linux) is given prominence. No Linux-first or Linux-native patterns are discussed.
Recommendations
  • Add explicit Bash/Linux shell examples for role assignment operations using Azure CLI.
  • Clarify that Azure CLI is cross-platform and provide usage examples for Linux/macOS terminals.
  • If PowerShell is mentioned, note its availability on Linux, but avoid implying it is the default or preferred method.
  • Consider including links or references to Linux-specific documentation or troubleshooting guides.
  • Ensure that all example commands are shown in both PowerShell and Bash syntax where relevant.
GitHub Create Pull Request
Container Registry Azure Container Registry custom roles ...ainer-registry/container-registry-rbac-custom-roles.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page presents both Azure CLI and Azure PowerShell examples for listing permissions, but PowerShell (a Windows-centric tool) is mentioned alongside CLI without clarifying cross-platform compatibility. In several places, Azure PowerShell is listed before or equally with Azure CLI, which may subtly prioritize Windows workflows. There are no explicit Linux-specific examples or notes about platform differences, and PowerShell is not clearly marked as Windows-only, potentially leading Linux users to confusion.
Recommendations
  • Clearly indicate which tools are cross-platform (e.g., Azure CLI) and which are Windows-specific (e.g., Azure PowerShell).
  • List Azure CLI examples before PowerShell, as CLI is cross-platform and more widely used on Linux.
  • Add explicit Linux shell examples where relevant, or clarify that Azure CLI commands work on Linux, macOS, and Windows.
  • Include notes or links for installing and using Azure CLI on Linux.
  • Avoid presenting PowerShell as an equal alternative without noting its platform specificity.
GitHub Create Pull Request
← Previous Page 3 of 8 Next →