Container Registry

293
Total Pages
277
Linux-Friendly Pages
16
Pages with Bias
5.5%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

40 issues found
Showing 1-25 of 40 flagged pages
Container Registry Store Helm Charts in Azure Container Registry ...es/container-registry/container-registry-helm-repos.md
Medium Priority View Details →
Scanned: 2026-02-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 several places (e.g., setting environment variables), Windows-style commands (e.g., 'set ACR_NAME=<container-registry-name>') are shown without Linux/macOS equivalents. Additionally, the order of presenting options for creating AKS clusters lists Azure CLI, PowerShell, and Portal, with PowerShell (Windows-centric) mentioned before Portal. There are no explicit Linux/macOS-specific instructions or examples for setting environment variables or other OS-dependent steps.
Recommendations
  • Provide both Windows (cmd/PowerShell) and Linux/macOS (bash/zsh) command examples for setting environment variables, e.g., use 'export ACR_NAME=<container-registry-name>' for bash/zsh.
  • Clarify that Azure CLI commands are cross-platform and can be run on Linux/macOS terminals.
  • When listing options for creating AKS clusters, consider mentioning Azure CLI and Portal first, or explicitly note PowerShell is Windows-specific.
  • Add notes or callouts for any OS-specific differences, especially for shell commands.
  • Ensure all code blocks that are OS-dependent (e.g., environment variable setting) have both Windows and Linux/macOS variants.
GitHub Create Pull Request
Container Registry Managed Identity Authentication for ACR ...https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/container-registry-authentication-managed-identity.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides parallel examples for Azure CLI and Azure PowerShell throughout, but PowerShell is emphasized as an equal alternative to CLI, which is a Windows-centric tool, even though all VM and Docker instructions are for Ubuntu/Linux. There are no explicit Windows-only tools or examples, but PowerShell is presented as a primary automation method alongside CLI, which may create friction for Linux/macOS users who rarely use PowerShell. In some sections, PowerShell instructions appear before CLI, and the initial tooling requirements mention PowerShell before Linux alternatives.
Recommendations
  • Clarify that PowerShell is cross-platform, but note that Azure CLI is more commonly used on Linux/macOS.
  • Provide Bash scripting examples for automation on Linux/macOS, not just PowerShell.
  • Consider moving Azure CLI instructions before PowerShell in all sections, or default to CLI for Linux scenarios.
  • Explicitly state that PowerShell is optional for Linux users and that Bash/CLI is the native approach.
  • Add a note or section for Windows VM scenarios if PowerShell is to be emphasized, or otherwise reduce PowerShell prominence for Linux-focused guides.
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 06:17
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. Windows-centric tools (Azure PowerShell) and patterns are presented alongside Azure CLI, but Linux/macOS equivalents are not always given equal prominence. PowerShell examples are provided in dedicated sections, while Linux-native shell examples are limited. The use of Docker is assumed as the default, with only a brief mention of Podman for Linux users. There are no explicit bash or shell script examples for Linux/macOS users, and instructions for setting environment variables or troubleshooting are not tailored for non-Windows platforms.
Recommendations
  • Provide Linux/macOS-specific examples, such as bash shell commands, especially for authentication flows.
  • Include troubleshooting steps and environment variable instructions for Linux/macOS (e.g., export DOCKER_COMMAND=podman).
  • Present Azure CLI (cross-platform) examples before PowerShell, and clarify platform applicability.
  • Expand on alternative container tools (Podman, Buildah) with concrete examples and guidance for Linux users.
  • Add a section or notes explicitly addressing Linux/macOS workflows and common issues.
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-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. While the Docker CLI examples are cross-platform, authentication and registry management instructions are presented with Azure PowerShell and Azure CLI tabs, with PowerShell (a Windows-centric tool) featured prominently. Visual Studio Code (often used on Windows) is recommended for login, and Windows-specific shortcuts (Control+C) are mentioned for stopping containers. The order of presentation and tool recommendations favor Windows users, and Linux/macOS-specific nuances or alternatives are not discussed.
Recommendations
  • Add explicit Linux/macOS command-line examples where platform-specific nuances exist (e.g., stopping containers, file paths, environment variables).
  • Include Bash or shell script examples for authentication and registry management alongside PowerShell and Azure CLI.
  • Clarify that Visual Studio Code and Docker CLI instructions apply equally to Linux/macOS, and mention alternative editors or tools popular on those platforms.
  • When mentioning keyboard shortcuts (e.g., Control+C), note any differences for macOS (e.g., Command+C) or Linux terminal conventions.
  • Ensure parity in tool recommendations, such as suggesting Linux-native tools or scripts for automation.
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 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation presents both Azure CLI and PowerShell deployment instructions, but PowerShell is given a dedicated tab and is mentioned alongside CLI as a primary option. There is no mention of Bash, Linux, or macOS-specific instructions, nor are there examples for Linux shell environments. The use of Visual Studio Code is platform-neutral, but the terminal instructions and examples lean towards Windows users. The cleanup section only references the Azure portal, omitting CLI or shell-based deletion commands that would be useful for Linux/macOS users.
Recommendations
  • Add explicit Bash/Linux/macOS shell examples for deploying the Bicep file using Azure CLI.
  • Include instructions for deleting resources via Azure CLI in addition to the portal method.
  • Reorder examples to present Azure CLI (cross-platform) before PowerShell, or clarify that CLI works on all platforms.
  • Add notes or sections highlighting Linux/macOS compatibility and usage patterns.
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 06:17
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 suggests adding executables to 'system variables' or 'system environment variables' without clarifying Linux/macOS equivalents. Windows instructions are sometimes given first or exclusively, while Linux/macOS details are less explicit or only mentioned secondarily. There are no concrete Linux/macOS command examples or environment setup instructions.
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 file paths (such as for Notary), include Linux/macOS locations (e.g., /usr/local/bin or /usr/bin) alongside Windows paths.
  • Provide Linux/macOS-specific installation and troubleshooting steps where relevant, not just generic advice.
  • Ensure examples and instructions are presented in a cross-platform manner, or alternate between Windows and Linux/macOS examples.
  • Clarify terminology such as 'system variables' to include platform-specific equivalents.
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 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation consistently provides both Azure CLI and Azure PowerShell examples for all operations, but PowerShell is a Windows-centric tool and is referenced equally alongside CLI. There is a notable Windows bias in the 'Import from Microsoft Container Registry' section, where only a Windows Server Core image is shown as an example, with no Linux image import example from MCR. Additionally, PowerShell is presented as a primary automation tool, which is more native to Windows environments. There are no explicit Linux/macOS shell examples (e.g., bash), and no mention of Linux-specific patterns or troubleshooting.
Recommendations
  • Add Linux image import examples from Microsoft Container Registry (e.g., Ubuntu, Alpine) to balance the Windows-only example.
  • Clarify that both Azure CLI and PowerShell are cross-platform, but highlight that CLI is more commonly used on Linux/macOS.
  • Include troubleshooting tips or notes relevant to Linux/macOS environments (e.g., file permissions, shell differences).
  • Consider adding bash shell script examples for automation, especially for Linux/macOS users.
  • Explicitly mention that all commands work on Linux/macOS and provide links to platform-specific installation guides.
GitHub Create Pull Request
Container Registry Quickstart - Create Registry in Portal ...iner-registry/container-registry-get-started-portal.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
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 instructions for signing in to the registry, but PowerShell is featured equally and prominently, despite being primarily a Windows tool. The CLI and PowerShell tabs are presented together, but there is no explicit Bash/Linux shell example, and PowerShell is not natively available on most Linux/macOS systems. Additionally, the order of presentation sometimes puts Windows-centric tools (PowerShell) on equal footing with cross-platform tools (CLI), which may confuse Linux/macOS users.
Recommendations
  • Clearly indicate that Azure PowerShell is primarily for Windows users, and recommend Azure CLI for Linux/macOS.
  • Provide explicit Bash or shell examples for Linux/macOS users when demonstrating CLI usage.
  • Present Azure CLI examples first, as it is cross-platform, and move PowerShell examples to a separate section or as an alternative for Windows users.
  • Add a note clarifying platform compatibility for each tool (CLI, PowerShell).
  • Where possible, include screenshots or instructions for Linux/macOS users (e.g., terminal usage, package installation).
GitHub Create Pull Request
Container Registry Azure Container Registry SKU Features and Limits ...articles/container-registry/container-registry-skus.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
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 key operations, but PowerShell (a Windows-centric tool) is consistently mentioned alongside or immediately after CLI, and sometimes with more detail. There are no explicit Linux/macOS shell examples (e.g., Bash), nor is there mention of Linux-specific tools or patterns. The CLI examples are cross-platform, but the presence of PowerShell and lack of Linux shell parity may create friction for non-Windows users.
Recommendations
  • Add explicit Bash or shell script examples for Linux/macOS users where CLI is shown.
  • Clarify that Azure CLI commands work on Linux/macOS and Windows equally.
  • Consider mentioning Linux-native tools (e.g., curl for REST API calls) where appropriate.
  • Avoid listing PowerShell examples before CLI, or provide parity for Linux/macOS users.
  • Include a note about cross-platform support for all shown tools.
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-12 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 provided for Azure PowerShell and Azure CLI, with PowerShell examples given equal prominence to CLI. Windows-specific tools and patterns (PowerShell cmdlets, references to Connect-AzAccount, etc.) are mentioned throughout, often before or alongside cross-platform CLI commands. Linux/macOS users are referenced mainly in the context of Docker and Podman, but there are few explicit Linux/macOS shell examples (e.g., bash, zsh), and PowerShell is not available natively on most Linux/macOS systems. The page does mention Podman for RHEL, but only as an alternative to Docker and with minimal guidance. There are no examples using native Linux authentication tools or workflows outside of Docker/Podman. The 'Next steps' section also lists PowerShell as a primary path.
Recommendations
  • Add explicit bash/zsh shell examples for Linux/macOS users, especially for authentication and scripting scenarios.
  • Provide guidance for Linux/macOS users on installing and using Azure CLI, and clarify that PowerShell is optional and not required for most workflows.
  • Reorder examples so that cross-platform CLI (az) and Docker/Podman commands are shown before PowerShell, or provide tabs for 'Windows', 'Linux/macOS', and 'Cloud Shell' usage.
  • Include troubleshooting tips specific to Linux/macOS environments (e.g., Docker daemon issues, permissions, environment variables).
  • Expand on Podman usage for Linux, including authentication flows and registry access, not just as a Docker replacement.
  • Clarify which commands are cross-platform and which are Windows/PowerShell-specific.
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-12 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 given its own tab. There is no mention of Bash or Linux-specific shell usage, nor are there any Linux/macOS-specific instructions or screenshots. The use of Visual Studio Code is suggested, but no alternatives for Linux users are discussed. The cleanup instructions focus on the Azure portal, with no CLI/Bash examples for resource deletion.
Recommendations
  • Add explicit Bash/Linux shell examples for deploying the Bicep file using Azure CLI.
  • Include instructions or screenshots relevant to Linux/macOS environments, such as using the terminal or alternative editors.
  • Provide parity in cleanup instructions by showing how to delete resources using Azure CLI/Bash.
  • Avoid presenting PowerShell as the default or primary option; ensure CLI/Bash instructions are equally prominent.
  • Mention cross-platform tools and workflows where appropriate.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides examples exclusively for Azure CLI and Azure PowerShell, with no explicit Linux/macOS shell examples or instructions. While Azure CLI is cross-platform, PowerShell is traditionally associated with Windows, and its usage is emphasized throughout. There are no Linux-specific tools, shell commands, or platform notes, and Windows-centric images (e.g., Windows Server Core) are highlighted without Linux equivalents. The ordering of examples sometimes places PowerShell first or equally, which may subtly prioritize Windows users.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux/macOS and provide example shell environments (e.g., bash, zsh) for clarity.
  • Add Linux/macOS-specific notes or troubleshooting tips where platform differences may affect usage (e.g., authentication, file paths, environment variables).
  • Include Linux container image examples (e.g., Ubuntu, Alpine) alongside Windows images to demonstrate parity.
  • Clarify that PowerShell Core is available cross-platform, or de-emphasize PowerShell in favor of CLI for platform-neutral documentation.
  • Where possible, add sample commands using native Linux tools (e.g., curl, wget) for related tasks, or link to such resources.
GitHub Create Pull Request
Container Registry Azure Container Registry Authentication Options Explained ...ontainer-registry/container-registry-authentication.md
Low Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Minor Missing Linux Example
Summary
The documentation provides authentication instructions for Azure Container Registry using both Azure CLI and Azure PowerShell, with PowerShell examples and references featured throughout. While Azure CLI is cross-platform, PowerShell is primarily associated with Windows, and its examples may not be relevant for Linux/macOS users. The CLI and PowerShell examples are presented in parallel, but PowerShell is mentioned in tables and sections alongside CLI, potentially implying parity. There are no explicit Linux/macOS-specific examples (e.g., shell scripting, environment variable usage in Bash), and the 'Next steps' section links to PowerShell and CLI guides, but not to Linux/macOS-specific workflows. The documentation does mention alternative container tools like podman, which is a positive step for Linux parity.
Recommendations
  • Add explicit Bash/Linux/macOS shell examples for authentication flows, especially for scripting scenarios.
  • Clarify that Azure CLI is fully cross-platform and recommend it as the default for Linux/macOS users.
  • Consider adding a 'Linux/macOS authentication workflow' section or linking to relevant guides.
  • Reduce prominence of PowerShell in tables and summaries unless it is equally relevant for Linux/macOS users.
  • Expand 'Next steps' to include Linux/macOS-specific getting started guides.
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-02-10 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 does not show any Linux/macOS-specific commands, tools, or shell patterns. Azure PowerShell is featured equally alongside Azure CLI, which is cross-platform, but PowerShell is historically associated with Windows and its inclusion may suggest Windows bias. In some sections, PowerShell examples are presented immediately after CLI, and the documentation references PowerShell module installation, which is more common on Windows. No Linux/macOS-specific shell (bash/zsh) or OS-specific guidance is provided, and there are no explicit Linux-first examples.
Recommendations
  • Clarify that both Azure CLI and Azure PowerShell are cross-platform and can be used on Linux/macOS as well as Windows.
  • Add explicit bash/zsh shell examples or notes for Linux/macOS users, especially for command-line usage.
  • Mention that Azure CLI is available natively on Linux/macOS and provide installation links for those platforms.
  • Consider including troubleshooting or environment setup notes for Linux/macOS users (e.g., authentication, file paths, environment variables).
  • If PowerShell is recommended, highlight its cross-platform availability and provide installation instructions for Linux/macOS.
GitHub Create Pull Request
Container Registry Deploy the Connected Registry Arc Extension ...iner-registry/quickstart-connected-registry-arc-cli.md
Low Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Bash and PowerShell examples for generating the protected settings JSON file, but Bash is presented first and is more concise. The PowerShell example is included, but it uses Unix-style commands (e.g., tr -d '\r') and does not leverage native Windows/PowerShell idioms. All other steps use Azure CLI and kubectl commands, which are cross-platform and do not exhibit Windows-specific bias. No Windows-only tools or patterns are mentioned, and Linux parity is generally maintained.
Recommendations
  • Clarify that both Bash and PowerShell examples are supported on Windows, Linux, and macOS, and indicate which environments each example is intended for.
  • Provide a native PowerShell example that does not rely on Unix utilities (e.g., 'tr'), using PowerShell's own string manipulation features.
  • Consider adding a note about running Azure CLI and kubectl commands on Linux/macOS and Windows, including any minor differences (such as file path separators or shell syntax).
GitHub Create Pull Request
Container Registry Deploy the Connected Registry Arc Extension ...iner-registry/quickstart-connected-registry-arc-cli.md
Low Priority View Details →
Scanned: 2026-01-25 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for generating the protected settings JSON file, but the Bash example is shown first. The PowerShell example is included, but it is not strictly Windows-specific (PowerShell Core is cross-platform). All other commands use Azure CLI and kubectl, which are cross-platform tools. No Windows-only tools or patterns are used, and Linux users can follow the guide without friction.
Recommendations
  • Clarify that the PowerShell example works on both Windows PowerShell and PowerShell Core (which is available on Linux/macOS).
  • Consider labeling the PowerShell tab as 'PowerShell (Windows/macOS/Linux)' to avoid implying it's Windows-only.
  • Ensure any future examples that use OS-specific shell features are mirrored for both Bash and PowerShell, and clarify platform compatibility.
  • If possible, add a note that Bash is available on Windows via WSL or Git Bash, and PowerShell is available on Linux/macOS.
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-01-13 06:17
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, but the PowerShell example is given equal prominence and detail, despite PowerShell being primarily a Windows tool. There are no explicit Linux/macOS shell examples (e.g., Bash), and the mention of Azure PowerShell may imply a Windows-centric workflow. However, the Azure CLI example is cross-platform and shown first, mitigating some bias.
Recommendations
  • Clarify that Azure CLI is fully cross-platform and recommend it for Linux/macOS users.
  • Add explicit Bash or shell script examples for Linux/macOS users where relevant.
  • Note that Azure PowerShell is available on Linux/macOS, but CLI is generally preferred for those platforms.
  • Ensure that instructions and examples do not imply PowerShell is required for non-Windows environments.
GitHub Create Pull Request
Container Registry Access Registry Images from ACI ...cles/container-registry/container-registry-auth-aci.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides Azure CLI examples (cross-platform) but references Azure PowerShell scripts as an alternative, which are primarily Windows-centric. The mention of setting 'export MSYS_NO_PATHCONV=1' is a workaround for bash on Windows, but there are no explicit Linux/macOS-specific instructions or troubleshooting notes. The sample scripts section lists Azure PowerShell before clarifying Linux/CLI parity, and does not link to bash/zsh-specific samples or address Linux/macOS users directly.
Recommendations
  • Add explicit Linux/macOS instructions or troubleshooting notes, such as shell environment differences and credential storage best practices.
  • Provide links to bash/zsh sample scripts or clarify that Azure CLI commands work natively on Linux/macOS.
  • Reorder sample script references to list Azure CLI (cross-platform) before Azure PowerShell (Windows-centric), and clarify platform applicability.
  • Include a note that Azure PowerShell is primarily for Windows, and suggest alternatives for Linux/macOS users.
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-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates minor Windows bias by using Windows-style environment variable setting (set ACR_NAME=...) in the initial setup example, without providing the equivalent Linux/macOS syntax (export ACR_NAME=...). All other command examples use cross-platform tools (Helm, Azure CLI) and shell syntax that is compatible with both Windows (via WSL, Git Bash, etc.) and Linux/macOS. No PowerShell-specific commands or Windows-only tools are present, and Linux/macOS users can complete all tasks with minor adjustments.
Recommendations
  • Provide both Windows (set) and Linux/macOS (export) syntax for environment variable setup.
  • Explicitly note that all CLI examples are intended to be run in a Bash-like shell, and provide guidance for Windows users (e.g., use WSL, Git Bash, or PowerShell equivalents).
  • Where commands differ between platforms, offer side-by-side examples or a platform selector.
  • Review for any other subtle platform-specific assumptions (e.g., file paths, shell features) and clarify as needed.
GitHub Create Pull Request
Container Registry Manage OCI Artifacts and Supply Chain Artifacts with ORAS ...ntainer-registry/container-registry-manage-artifact.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Linux/macOS and Windows examples for key ORAS CLI commands, but Windows examples are consistently presented after Linux/macOS examples. Windows-specific command syntax (using .\oras.exe and ^ for line continuation) is included, but there are no PowerShell-only or Windows-exclusive steps. All workflows are achievable on Linux/macOS, and the majority of examples use Bash syntax. There is minor bias in the ordering and explicit inclusion of Windows command blocks, but Linux parity is generally maintained.
Recommendations
  • Present Linux/macOS and Windows examples side-by-side or in tabs to avoid perceived prioritization.
  • Ensure all instructions referencing environment variables or command syntax clarify cross-platform differences (e.g., path separators, quoting).
  • Consider adding explicit macOS notes if there are any unique considerations.
  • If possible, minimize duplication by using platform-agnostic commands where feasible.
GitHub Create Pull Request
Container Registry Azure Container Registry custom roles ...ainer-registry/container-registry-rbac-custom-roles.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
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 examples for listing permissions, but PowerShell (a Windows-centric tool) is featured alongside CLI rather than after or as an alternative. References to Azure PowerShell are frequent and given equal prominence to Azure CLI, with no explicit mention of Linux/macOS shell environments or their nuances. There are no Linux-specific examples or guidance, and PowerShell is referenced before Linux-native alternatives in some sections.
Recommendations
  • Explicitly state that Azure CLI works cross-platform (Windows, Linux, macOS) and is recommended for Linux/macOS users.
  • Present Azure CLI examples first, as it is the most platform-neutral tool.
  • Add notes or examples for Linux/macOS users, such as shell syntax or installation instructions for Azure CLI.
  • Clarify that Azure PowerShell is primarily for Windows users, and provide links to Bash or other Linux-native scripting guides where relevant.
  • Avoid implying parity between PowerShell and CLI unless both are equally supported on all platforms.
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
Low Priority View Details →
Scanned: 2026-01-13 06:17
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, but PowerShell is featured as a primary tab, which may indicate a Windows-first approach. There is no explicit mention of Linux/macOS compatibility for PowerShell, nor are there any Linux-specific instructions or examples. The CLI example is cross-platform, but PowerShell is typically associated with Windows, and its inclusion without clarification can create friction for non-Windows users.
Recommendations
  • Clarify that Azure CLI works on Linux, macOS, and Windows, and recommend it as the preferred cross-platform method.
  • Add a note specifying that Azure PowerShell is available on Linux and macOS via PowerShell Core, or link to installation instructions for non-Windows platforms.
  • Consider listing Azure CLI before PowerShell to emphasize cross-platform support.
  • Explicitly mention Linux/macOS compatibility in the introduction or relevant sections.
GitHub Create Pull Request
Container Registry Quickstart: Deploying the Connected Registry Arc Extension ...iner-registry/quickstart-connected-registry-arc-cli.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Bash and PowerShell examples for generating the protected settings JSON file, but the PowerShell example is given equal prominence and is not separated into a dedicated Windows section. There is no explicit mention of Linux/macOS-specific tools or troubleshooting, and the PowerShell example uses Windows-specific syntax (echo, tr -d '\r') that may not work on Linux/macOS. However, the majority of CLI commands are cross-platform and use Azure CLI and kubectl, which are available on all major platforms.
Recommendations
  • Clearly label Bash examples as suitable for Linux/macOS and PowerShell examples as suitable for Windows, possibly using tabbed sections with platform icons.
  • Provide troubleshooting notes for common issues encountered on Linux/macOS (e.g., file permissions, line endings, shell differences).
  • Ensure all examples using PowerShell syntax are explicitly marked as Windows-only and provide equivalent Bash commands for Linux/macOS.
  • Add a note about installing Azure CLI and kubectl on Linux/macOS, with links to platform-specific installation guides.
  • Review all command snippets for Windows-specific assumptions (such as line endings or file paths) and clarify where differences may occur.
GitHub Create Pull Request
Container Registry Quickstart- Manage Container Registry Content with Azure Client Libraries ...cles/container-registry/quickstart-client-libraries.md
Low Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page shows mild Windows bias in the 'Prerequisites' section, where Windows-specific tools (Azure PowerShell) are mentioned before Linux-friendly alternatives (Azure CLI), and the only example for creating a registry uses Azure CLI, which is cross-platform but often associated with Windows. There are no PowerShell-heavy sections, and all code samples for client libraries are provided for multiple languages and are platform-neutral. No critical Linux/macOS parity issues are present.
Recommendations
  • List Azure CLI before Azure PowerShell in the prerequisites, as CLI is more universally available across platforms.
  • Explicitly mention that Azure CLI and Docker CLI are cross-platform and provide links to installation instructions for Linux/macOS.
  • Consider adding a note that Azure PowerShell is primarily for Windows and provide equivalent Bash or shell commands for Linux/macOS users where relevant.
  • Ensure that any future examples or instructions involving command-line tools include both Windows and Linux/macOS variants if there are differences.
GitHub Create Pull Request
Container Registry Access Registry Images from ACI ...cles/container-registry/container-registry-auth-aci.md
Low Priority View Details →
Scanned: 2026-01-12 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 script links, but the main example uses Azure CLI, which is cross-platform. However, the mention of Azure PowerShell and the explicit linking to PowerShell samples introduces a Windows bias. The note about 'export MSYS_NO_PATHCONV=1' is relevant for bash on Windows, but does not clarify Linux/macOS usage. There is no explicit Linux/macOS example or guidance, and the documentation does not mention platform-specific differences or provide parity for Linux users beyond the CLI example.
Recommendations
  • Add explicit Linux/macOS usage notes, including any environment variables or differences in command execution.
  • Provide sample scripts or links for bash/zsh on Linux/macOS, not just Azure CLI and PowerShell.
  • Clarify that Azure CLI is cross-platform and provide examples of running it on Linux/macOS.
  • If mentioning PowerShell, also mention bash/zsh or other common Linux shells to ensure parity.
GitHub Create Pull Request
← Previous Page 1 of 2 Next →