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 26-40 of 40 flagged pages
Container Registry Manage Public Content in Private Container Registry ...icles/container-registry/buffer-gate-public-content.md
Low Priority View Details →
Scanned: 2026-01-12 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, but the PowerShell example is given equal prominence and detail as the CLI example. There is no explicit Linux/macOS bias, but the presence of PowerShell examples (which are primarily used on Windows) and the mention of Azure PowerShell as a main tool may suggest a slight Windows bias. However, the Azure CLI example is cross-platform and shown first, and there are no Windows-only tools or patterns. No Linux-specific examples or tools are missing, but parity could be improved by clarifying cross-platform usage and mentioning Linux/macOS environments explicitly.
Recommendations
  • Explicitly state that Azure CLI is cross-platform and works on Linux/macOS/Windows.
  • Add a note that Azure PowerShell is available on Linux/macOS, but is most commonly used on Windows.
  • Include a brief example of using Azure CLI in a Linux/macOS shell (e.g., bash) to reinforce parity.
  • Ensure that all steps and tools mentioned are clearly marked as cross-platform where applicable.
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
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 🔧 Windows Tools
Summary
The documentation provides parallel examples for both Azure CLI and Azure PowerShell throughout, but PowerShell is a Windows-centric tool and is featured as a first-class option alongside the CLI. The introductory sections mention Azure PowerShell before Azure CLI, and PowerShell is presented as an equal alternative even for Linux scenarios (e.g., installing PowerShell on Ubuntu). There are no examples or guidance for native Linux shell scripting or automation beyond Bash/CLI, and no mention of Linux-specific tools or patterns. However, all resource creation and authentication examples use Ubuntu VMs and Bash commands, and Docker installation instructions are Linux-focused.
Recommendations
  • Make Azure CLI the primary example and reference, as it is cross-platform and native to Linux/macOS.
  • Move Azure PowerShell examples to a secondary section or appendix, clarifying its Windows origins and optional use on Linux.
  • Add native Bash scripting examples for automation tasks, rather than relying on PowerShell for Linux users.
  • Explicitly mention that PowerShell is not required for Linux users unless they prefer it.
  • Highlight Linux-native tools and patterns for authentication and automation where applicable.
GitHub Create Pull Request
Container Registry Quickstart - Create Registry in Portal ...iner-registry/container-registry-get-started-portal.md
Low Priority View Details →
Scanned: 2026-01-12 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 instructions for signing in to the registry, but PowerShell is given equal prominence to CLI, which is a Windows-centric tool. There are no Linux/macOS-specific shell examples (e.g., Bash), and PowerShell is presented as a primary option alongside CLI, potentially creating friction for Linux/macOS users who are less likely to use PowerShell. However, Docker installation links are provided for all platforms, and the main workflow is portal- and Docker-based, which is cross-platform.
Recommendations
  • Clearly indicate that Azure CLI is cross-platform and preferred for Linux/macOS users, while PowerShell is primarily for Windows.
  • Present Azure CLI instructions before PowerShell, or mark CLI as the default/recommended path for non-Windows users.
  • Add explicit Bash shell examples for Linux/macOS users where relevant.
  • Add a note clarifying platform suitability for each tool (e.g., 'Azure PowerShell is recommended for Windows users; Azure CLI is recommended for 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-01-12 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 and image deletion, but PowerShell is presented as a recommended method and receives equal prominence as Azure CLI. There are references to Windows-specific tools (Visual Studio Code with Docker extension) and patterns (Control+C for stopping containers, which is universal but often associated with Windows). However, Linux and macOS users are acknowledged in the prerequisites, and all Docker CLI commands are cross-platform. No Linux-specific commands or package manager examples (e.g., apt, yum) are provided, and PowerShell is mentioned before any Linux shell equivalents. There are no Linux/macOS-specific troubleshooting or usage notes.
Recommendations
  • Add explicit bash or shell examples for authentication and image deletion, especially for Linux/macOS users.
  • Include Linux/macOS-specific notes or troubleshooting tips (e.g., permissions, common issues with Docker on Linux).
  • Balance the prominence of PowerShell by providing equivalent bash commands in tabbed sections.
  • Mention Linux GUI tools (e.g., GNOME Terminal, Docker Desktop for Linux) alongside Visual Studio Code.
  • Clarify that all Docker CLI commands work identically on Linux/macOS, and provide links to Linux/macOS documentation where appropriate.
GitHub Create Pull Request
Container Registry Error Reference for Registry Health Checks ...-registry/container-registry-health-error-reference.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits mild Windows bias in several places. References to 'system variables' and 'system environment variables' are Windows-centric, and the Notary error section describes Windows installation paths and .exe files before mentioning Linux/macOS alternatives. There are no explicit Linux/macOS command examples or environment variable instructions, and Windows terminology appears first or exclusively in some solution steps.
Recommendations
  • Include explicit instructions for adding CLI tools (Docker, Helm, Notary) to the PATH on Linux/macOS (e.g., modifying ~/.bashrc or ~/.zshrc).
  • When mentioning installation paths, provide Linux/macOS equivalents alongside Windows paths.
  • Avoid using Windows-specific terminology like 'system variables' without also mentioning the cross-platform equivalent ('PATH environment variable').
  • Ensure examples and troubleshooting steps are provided for both Windows and Linux/macOS users, ideally with parity in detail and order.
  • Where file extensions are mentioned (.exe), clarify the Linux/macOS binary naming conventions.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias: environment variable setting uses the Windows 'set' command without showing the Linux/macOS equivalent, and the order of Kubernetes cluster creation examples lists Azure CLI (cross-platform) first, but then Azure PowerShell (Windows-only) before Azure Portal. Most commands use Azure CLI or Helm, which are cross-platform, but the initial environment variable setup and lack of explicit Linux/macOS instructions may cause friction for non-Windows users.
Recommendations
  • Provide both Windows and Linux/macOS syntax when setting environment variables (e.g., 'set' for Windows, 'export' for Linux/macOS).
  • Explicitly mention that Azure CLI and Helm commands work on Linux/macOS as well as Windows.
  • Where PowerShell is referenced, clarify that it is Windows-specific and offer Bash alternatives.
  • Consider listing Linux/macOS examples or alternatives alongside or before Windows-specific instructions.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Linux/macOS and Windows examples for key ORAS commands, but Windows examples (using .cmd syntax and .\oras.exe) are consistently shown after Linux/macOS examples. There is a slight bias toward Windows in the authentication section, where Docker Desktop credential store is referenced, and Windows-specific command syntax is included throughout. However, Linux/macOS users are given clear instructions and examples for all major tasks, and Azure CLI commands are cross-platform.
Recommendations
  • Present Linux/macOS and Windows examples side-by-side or in tabs to avoid implicit prioritization.
  • Explicitly mention Linux credential store alternatives when referencing Docker Desktop.
  • Ensure all command examples are provided for both platforms, including any Azure CLI or Docker commands.
  • Add a note clarifying that all CLI commands work on Linux, macOS, and Windows, and highlight any platform-specific caveats.
  • Consider using platform-agnostic command blocks where possible, and only split out platform-specific syntax when necessary.
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-12 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 listing permissions, but PowerShell (a Windows-centric tool) is mentioned alongside CLI rather than as a secondary option. In several places, Azure PowerShell is listed before or equally with Azure CLI, and no Linux/macOS-specific shell examples (e.g., Bash) are given. There is no explicit mention of Linux/macOS compatibility or guidance for users on those platforms, and no examples using native Linux tools.
Recommendations
  • Ensure Azure CLI examples are presented first, as CLI is cross-platform and preferred for Linux/macOS users.
  • Explicitly state that Azure CLI works on Linux/macOS and provide Bash shell usage examples where relevant.
  • Add notes clarifying that Azure PowerShell is available on Linux/macOS, or provide links to installation instructions for non-Windows platforms.
  • Avoid listing PowerShell and CLI together without clarifying platform parity; prioritize CLI for cross-platform documentation.
  • Include troubleshooting or environment setup notes for Linux/macOS users where differences may exist.
GitHub Create Pull Request
Container Registry Azure Container Registry SKU Features and Limits ...articles/container-registry/container-registry-skus.md
Low Priority View Details →
Scanned: 2026-01-12 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 key operations, but PowerShell is mentioned alongside CLI in multiple places and given its own dedicated example section. There is no mention of Linux/macOS-specific tools or shell environments, and examples do not clarify cross-platform usage. The ordering of examples sometimes places PowerShell before or alongside CLI, which may subtly prioritize Windows workflows. No Linux-specific commands (e.g., Bash scripts) or guidance are provided, and there is no explicit assurance that all CLI commands work identically on Linux/macOS.
Recommendations
  • Add explicit Linux/macOS usage notes for Azure CLI commands, confirming cross-platform compatibility.
  • Include Bash shell examples or clarify that CLI commands are intended for Bash/Unix shells as well as PowerShell.
  • If PowerShell is mentioned, also mention Bash or other common Linux shells to balance platform representation.
  • Consider adding a table or section comparing usage across Windows, Linux, and macOS environments.
  • Clarify that Azure CLI is cross-platform and provide installation/use links for Linux/macOS.
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-12 00:00
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 (a Windows-centric tool) is given equal prominence and is listed immediately after CLI. There is no explicit mention of Linux/macOS compatibility for PowerShell commands, nor any Linux/macOS-specific guidance. The CLI example is cross-platform, but the PowerShell tab may cause confusion or friction for non-Windows users.
Recommendations
  • Clarify that Azure CLI is cross-platform and recommended for Linux/macOS users.
  • Add a note indicating that Azure PowerShell is primarily for Windows, with instructions for Linux/macOS users to use CLI.
  • Consider listing CLI examples before PowerShell to emphasize cross-platform support.
  • If PowerShell Core is supported on Linux/macOS, explicitly mention this and provide installation guidance.
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-12 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 the PowerShell example is given equal prominence and is not separated by platform context. There is no explicit mention of Linux/macOS prerequisites or environment setup, and Windows/PowerShell is presented as a first-class option, potentially creating friction for Linux/macOS users. However, all critical tasks can be completed using Bash, and the Azure CLI commands are cross-platform.
Recommendations
  • Clearly indicate which example is for Windows/PowerShell and which is for Linux/macOS/Bash, using platform tabs or headings.
  • Provide explicit guidance for Linux/macOS users in the prerequisites (e.g., mention that Azure CLI and kubectl work on Linux/macOS).
  • List Bash/Linux examples first, as Azure CLI is natively cross-platform.
  • Remove unnecessary PowerShell-specific syntax or provide equivalent Bash commands for all steps.
  • Add troubleshooting notes for common Linux/macOS issues (e.g., file permissions, line endings).
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-12 00:00
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 Windows-centric tools (Azure PowerShell and Azure Portal) are mentioned before the Azure CLI, and the only example provided for registry creation uses Azure CLI (which is cross-platform, but the ordering suggests a Windows-first mindset). There are no PowerShell-heavy examples, and the rest of the documentation is organized by programming language and uses cross-platform tools and environment variables. No critical Linux/macOS gaps are present.
Recommendations
  • List Azure CLI before Azure PowerShell and Portal in the prerequisites section, as CLI is cross-platform and preferred by many Linux/macOS users.
  • Explicitly mention that Azure CLI works on Linux/macOS and provide links to installation instructions for those platforms.
  • Consider providing a Bash shell example for registry creation alongside the CLI command, or clarify that the CLI command works in Bash and other shells.
  • If mentioning Azure PowerShell, also mention Bash or other Linux-native tools for parity.
  • Ensure that all environment variable instructions and code samples are clear for both Windows and Linux/macOS users (e.g., variable naming conventions, export/set commands).
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-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 detail as the CLI example. There is a slight Windows-first bias in mentioning Azure PowerShell as a primary tool alongside Azure CLI, without explicit Linux/macOS shell examples or references to Bash or other Unix-native workflows. The page does not provide Linux-specific commands or highlight cross-platform usage beyond Azure CLI, and PowerShell is not as commonly used on Linux/macOS. However, the CLI example is cross-platform, and no critical steps are Windows-only.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows.
  • Add Bash or shell script examples for common workflows, especially for image import and authentication.
  • Clarify that PowerShell is available on Linux/macOS, or provide alternative shell examples for those platforms.
  • Consider listing Azure CLI examples before PowerShell, as CLI is more universally available.
  • Add notes or links for Linux/macOS users on installing and using Azure CLI.
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-01-10 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 examples are always present and given equal prominence to CLI. There is a subtle Windows bias in that PowerShell is a Windows-native tool, and its inclusion as a primary example may suggest a preference for Windows environments. Additionally, the only explicit OS-specific image import example is for a Windows Server Core image, with no Linux-specific image import example provided. However, the CLI examples are cross-platform and shown first, and there are no exclusive references to Windows-only tools or patterns.
Recommendations
  • Add explicit Linux image import examples (e.g., Ubuntu, Alpine) alongside the Windows Server Core example to demonstrate parity.
  • Clarify that Azure CLI is fully cross-platform and can be used on Linux/macOS/Windows.
  • Consider including Bash shell usage or notes for Linux/macOS users, especially in troubleshooting or authentication sections.
  • If PowerShell is shown, note that PowerShell Core is available cross-platform, but CLI is typically preferred on Linux/macOS.
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-10 00:00
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 a Windows-centric tool and is presented as a primary tab. There is no explicit mention of Linux/macOS-specific instructions, nor is there a Bash or shell script example. The CLI example is cross-platform, but PowerShell's inclusion and prominence may suggest a Windows bias.
Recommendations
  • Clarify that Azure CLI commands work on Windows, Linux, and macOS.
  • Add explicit Bash/shell script examples or notes for Linux/macOS users.
  • Reorder tabs to show Azure CLI first, as it is cross-platform.
  • Add a note that PowerShell Core is available on Linux/macOS, or link to installation instructions.
GitHub Create Pull Request
← Previous Page 2 of 2 Next →