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 76-100 of 183 flagged pages
Container Registry Quickstart- Manage Container Registry Content with Azure Client Libraries ...cles/container-registry/quickstart-client-libraries.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
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) and the Azure portal are mentioned before the Azure CLI, and a PowerShell example is given for .NET package installation. However, the main client library usage examples are cross-platform and do not show further Windows bias.
Recommendations
  • List cross-platform tools (Azure CLI) before Windows-specific tools (Azure PowerShell, Azure portal) in the prerequisites section.
  • Provide explicit instructions or examples for Linux/macOS environments where relevant (e.g., package installation commands for .NET using bash).
  • Clarify that Azure CLI is available on all platforms and is recommended for cross-platform usage.
  • Where PowerShell is used for .NET, offer a bash alternative for Linux/macOS users.
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-11 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 the PowerShell example is given equal prominence as the CLI example, and is presented before any mention of Linux-specific tools or shell environments. There are no explicit Linux shell (bash) examples, nor is there any mention of Linux-specific considerations. The presence of a PowerShell tab (which is Windows-centric, though PowerShell Core is cross-platform) without a corresponding bash or Linux shell tab may suggest a subtle Windows bias.
Recommendations
  • Add a dedicated Bash/Linux shell example tab, showing the Azure CLI command in a bash context (e.g., with environment variables, piping, jq usage, etc.).
  • Explicitly mention that the Azure CLI example works on Linux, macOS, and Windows, and provide any Linux-specific notes if needed.
  • If PowerShell is included, clarify whether the example is for Windows PowerShell or cross-platform PowerShell Core.
  • Consider presenting the Azure CLI (which is cross-platform) example first, and PowerShell second, to avoid the impression of Windows-first bias.
  • Where relevant, add troubleshooting or environment setup notes for Linux users.
GitHub Create Pull Request
Container Registry Quickstart: Deploying the Connected Registry Arc Extension ...iner-registry/quickstart-connected-registry-arc-cli.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 provides both Bash and PowerShell examples for generating the protected settings JSON file, but the PowerShell example is given immediately after Bash and is not clearly marked as Windows-specific. There is no explicit prioritization of Windows tools or exclusive use of Windows patterns, but the presence of a PowerShell example may suggest a slight Windows bias, especially since PowerShell is primarily a Windows shell (though available on Linux). All other CLI examples use Azure CLI and kubectl, which are cross-platform, and there are no exclusively Windows tools or instructions. No Linux-specific issues or missing Linux examples are apparent, but the Bash/PowerShell split could be improved for parity and clarity.
Recommendations
  • Clearly label the Bash example as suitable for Linux/macOS and the PowerShell example as suitable for Windows.
  • Consider listing the Bash example first, as Bash is the default shell on most Linux systems.
  • Add a note explaining that PowerShell Core is available on Linux, but most Linux users will prefer Bash.
  • Ensure all steps and commands are tested and work on Linux, and explicitly mention any OS-specific caveats.
  • If possible, provide a single cross-platform example (e.g., using Azure CLI and jq) to reduce confusion.
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-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 listing permissions, but PowerShell (a Windows-centric tool) is mentioned alongside CLI rather than after or as an alternative. In several places, Azure PowerShell is listed before or equally with Azure CLI, and no explicit Linux shell examples (e.g., Bash) or guidance for Linux users is provided. There is a slight preference for Windows tools and patterns, with no mention of Linux-specific considerations or parity.
Recommendations
  • Ensure Azure CLI examples are presented first, as it is cross-platform and preferred for Linux users.
  • Explicitly mention that Azure CLI works on Linux, macOS, and Windows, while Azure PowerShell is primarily Windows-focused.
  • Provide Bash shell usage examples or clarify that CLI commands are suitable for Linux terminals.
  • Add notes or sections highlighting any differences or considerations for Linux users when creating or assigning roles.
  • Avoid listing Azure PowerShell as the default or first option unless contextually appropriate for the majority of users.
GitHub Create Pull Request
Container Registry Cross-Tenant Authentication from AKS to ACR ...es/container-registry/authenticate-aks-cross-tenant.md
Medium Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing the Azure portal (web UI) and Azure CLI for configuration steps, without providing any Linux-specific or cross-platform command-line examples. There are no PowerShell commands, but the lack of Linux shell examples (e.g., Bash scripts, kubectl commands for updating secrets) and the absence of explicit Linux tool references means users on Linux are not directly supported. The instructions implicitly assume a Windows-centric workflow by prioritizing GUI and Azure CLI, which are commonly used on Windows.
Recommendations
  • Add explicit Linux/Bash shell examples for key steps, such as updating AKS service principal credentials and assigning roles.
  • Include kubectl commands for managing image pull secrets, showing how to use the service principal credentials in a Kubernetes-native way.
  • Clarify that Azure CLI is cross-platform, and provide sample commands for both Windows (PowerShell) and Linux (Bash).
  • Mention any OS-specific prerequisites or differences in authentication workflows.
  • Ensure parity by providing step-by-step instructions for both GUI (Azure portal) and CLI workflows, with clear notes for Linux users.
GitHub Create Pull Request
Container Registry Manage Public Content in Private Container Registry ...icles/container-registry/buffer-gate-public-content.md
Medium 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 presents both Azure CLI and Azure PowerShell examples for importing images to Azure Container Registry, but PowerShell is given equal prominence and is described in detail, which may indicate a Windows bias. There are no Linux-specific shell examples (e.g., Bash), nor is there mention of Linux-native tools or workflows. The documentation references Azure Cloud Shell, which is cross-platform, but does not provide explicit Linux command-line examples or mention Linux-specific considerations. The order of presentation (CLI first, then PowerShell) is neutral, but the inclusion of PowerShell as a primary tab and lack of Linux/Bash examples suggests a subtle Windows bias.
Recommendations
  • Add explicit Bash/Linux shell examples for image import and registry management, especially for users working on Linux or macOS.
  • Include references to Linux-native tools and workflows where appropriate (e.g., scripting with Bash, using curl or wget for registry interactions).
  • Clarify that Azure CLI commands are cross-platform and provide usage notes for Linux/macOS environments.
  • Consider adding a 'Linux shell' or 'macOS terminal' tab alongside CLI and PowerShell to demonstrate parity.
  • Mention any Linux-specific authentication or networking considerations when accessing Azure Container Registry.
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-10 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 available on both Windows and Linux, but does not mention or show Linux-specific patterns or alternatives (such as using bash scripting or Linux credential management). There are no PowerShell-specific examples, but the lack of explicit Linux examples or references (e.g., using bash, Linux credential stores, or Linux-specific troubleshooting) may make the documentation feel slightly Windows-centric, especially for users unfamiliar with Azure CLI on Linux.
Recommendations
  • Add explicit notes confirming Azure CLI commands work on Linux, macOS, and Windows.
  • Include example commands using bash scripting for Linux users where appropriate.
  • Mention installation and usage of Azure CLI on Linux, with links to relevant documentation.
  • Provide troubleshooting tips or patterns for Linux environments (e.g., file permissions, environment variables).
  • Ensure parity in references to credential management tools or shell environments (e.g., mention bash/zsh alongside PowerShell if referenced).
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-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 all major steps, but PowerShell is a Windows-centric tool and is presented as an equal alternative to Azure CLI, which is more cross-platform. There are no explicit Windows-only examples, but the prominence of PowerShell may suggest a bias toward Windows users. However, all VM and Docker instructions use Ubuntu (Linux), and Linux-specific commands (apt, ssh) are shown. The documentation does not provide Linux shell alternatives for PowerShell commands, nor does it mention Linux-native tools (e.g., Bash scripts) for Azure resource management. The order of presentation is mostly Azure CLI first, but PowerShell is always present and emphasized.
Recommendations
  • Clarify that PowerShell is available cross-platform, but Azure CLI is generally preferred for Linux users.
  • Add Bash script equivalents for Azure resource management steps, especially for users who may not want to install PowerShell.
  • Consider reducing the prominence of PowerShell in Linux-focused scenarios, or provide guidance on when to use CLI vs. PowerShell.
  • Explicitly mention that all steps can be performed on Linux without requiring Windows tools.
  • If possible, add a section comparing Azure CLI and PowerShell for Linux users, highlighting pros and cons.
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-10 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 environment variable setting (set ACR_NAME=<container-registry-name>) without providing the equivalent Linux/macOS syntax (export ACR_NAME=...), and by listing Azure PowerShell as an option before the Azure portal for creating AKS clusters. All command-line examples use generic 'console' or 'azurecli' blocks, which are mostly cross-platform, but the omission of Linux/macOS-specific instructions for environment variables and authentication may hinder parity.
Recommendations
  • Provide both Windows (set VAR=...) and Linux/macOS (export VAR=...) syntax when instructing users to set environment variables.
  • Explicitly state that all CLI commands are cross-platform and clarify any OS-specific differences.
  • When listing options for creating resources (e.g., AKS clusters), alternate or balance the order between Windows (PowerShell) and Linux/macOS (CLI, portal) tools.
  • Add a note or section highlighting any OS-specific prerequisites or considerations, especially for authentication and scripting.
  • Review all examples to ensure Linux/macOS users are equally supported, especially in sections where Windows conventions are used.
GitHub Create Pull Request
Container Registry Verify Container Images in GitHub Workflows with Notation and Trusted Signing ...gistry-tutorial-github-verify-notation-trusted-signing.md
Medium 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 Linux (bash) and Windows (PowerShell) examples for all CLI commands, but Windows/PowerShell examples are always presented immediately after Linux, and sometimes with more explanation (e.g., directory creation). There is a slight Windows-first bias in the structure and detail of examples, and PowerShell is used as the exclusive Windows shell, with no mention of alternatives like Git Bash or WSL. No Linux example is missing, but Windows tools and patterns (PowerShell, Invoke-WebRequest, New-Item) are consistently highlighted.
Recommendations
  • Alternate the order of Linux and Windows examples, or present them side-by-side to avoid implicit prioritization.
  • Add brief notes about using Git Bash, WSL, or other shells on Windows for parity.
  • Ensure explanations and comments are equally detailed for both platforms.
  • Consider providing a generic cross-platform script example (e.g., using Node.js, Python, or a workflow step) where possible.
  • Explicitly state that all steps are supported on both platforms and clarify any platform-specific caveats.
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-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 the PowerShell example is given equal prominence as the CLI example, which can be interpreted as a Windows bias since PowerShell is primarily a Windows tool (despite cross-platform support). There are no explicit Linux shell (bash) examples or notes about running the CLI on Linux, and the PowerShell example appears before the portal instructions, which may reinforce a Windows-centric workflow.
Recommendations
  • Add explicit bash/Linux shell examples for the Azure CLI, showing usage in a typical Linux terminal.
  • Clarify that the Azure CLI commands work identically on Linux, macOS, and Windows, and provide any OS-specific notes if needed.
  • Consider reordering the examples to present the Azure CLI (which is cross-platform) before PowerShell, or provide a clear note about PowerShell's cross-platform availability.
  • Include a table or section summarizing command usage across different platforms (Windows, Linux, macOS) to reinforce parity.
  • If PowerShell is included, mention PowerShell Core and its availability on Linux/macOS to reduce the perception of Windows-only tooling.
GitHub Create Pull Request
Container Registry Quickstart- Manage Container Registry Content with Azure Client Libraries ...cles/container-registry/quickstart-client-libraries.md
Medium Priority View Details →
Scanned: 2026-01-10 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 Portal and Azure PowerShell) are mentioned before the cross-platform Azure CLI for creating a container registry. The installation example for .NET uses PowerShell syntax, which is Windows-specific, rather than a cross-platform shell. However, the main client library usage examples for all languages are platform-neutral, and Linux tools (Docker CLI) are referenced for pushing images. No explicit Linux examples or Linux-first instructions are present.
Recommendations
  • List Azure CLI as the first option for creating a container registry, as it is cross-platform and widely used on Linux.
  • Provide installation instructions for .NET using both PowerShell and Bash (e.g., 'dotnet add package ...' in Bash), or use a generic command line format.
  • Explicitly mention Linux and macOS compatibility in the prerequisites and installation sections.
  • Include links or references to Linux-specific documentation or troubleshooting guides.
  • Ensure that any tool or command mentioned (e.g., PowerShell) is accompanied by its Linux/macOS equivalent where applicable.
GitHub Create Pull Request
Container Registry Quickstart: Deploying the Connected Registry Arc Extension ...iner-registry/quickstart-connected-registry-arc-cli.md
Medium 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 Bash and PowerShell examples for generating the protected settings JSON file, but the PowerShell example is given equal prominence and is not clearly marked as Windows-specific. The documentation does not exclusively use Windows tools or patterns, but it does present PowerShell as a primary option alongside Bash, which may suggest a slight Windows bias. There are no examples that use Linux-specific tools beyond Bash, and no explicit mention of Linux environments or parity considerations. The Azure CLI commands are cross-platform, but the inclusion of PowerShell examples without clear context may imply Windows-first thinking.
Recommendations
  • Clearly label PowerShell examples as Windows-specific and Bash examples as Linux/macOS-specific.
  • Provide guidance on which example to use based on the user's operating system.
  • Consider including a note at the top of the page clarifying that Azure CLI commands work on Windows, Linux, and macOS, and that Bash examples are intended for Linux/macOS users.
  • If PowerShell is included, ensure that Bash is presented first, or provide a parity check to confirm both environments are equally supported.
  • Add troubleshooting or environment setup notes for Linux users where applicable.
GitHub Create Pull Request
Container Registry https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/container-registry-rbac-custom-roles.md ...ainer-registry/container-registry-rbac-custom-roles.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
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 rather than as a secondary option. In several places, Azure PowerShell is referenced equally with Azure CLI for creating and assigning custom roles, which may suggest a slight Windows bias by not prioritizing cross-platform tools. No explicit Linux-only examples or Linux-specific tools are provided, and PowerShell is traditionally associated with Windows environments.
Recommendations
  • Prioritize Azure CLI examples and instructions, as CLI is natively cross-platform and widely used on Linux and macOS.
  • Clearly indicate that Azure PowerShell is available cross-platform, but note its historical association with Windows to avoid confusion.
  • Add explicit Linux usage notes or examples, such as running Azure CLI commands in Bash or Zsh.
  • If referencing PowerShell, provide context for Linux/macOS users (e.g., how to install and use PowerShell Core on non-Windows systems).
  • Consider including screenshots or terminal outputs from Linux environments to demonstrate parity.
GitHub Create Pull Request
Container Registry https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/authenticate-aks-cross-tenant.md ...es/container-registry/authenticate-aks-cross-tenant.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing the Azure portal (web UI) and omitting command-line examples. There are no examples using cross-platform tools such as Azure CLI, Bash, or PowerShell, nor are there any Linux-specific instructions. The workflow assumes use of the graphical portal, which is more common on Windows, and does not provide parity for users who prefer or require command-line automation, typical in Linux environments.
Recommendations
  • Add Azure CLI command examples for all steps, especially for app registration, service principal creation, and role assignment.
  • Include Bash script snippets for updating AKS credentials and provisioning service principals.
  • Explicitly mention that all steps can be performed from Linux, macOS, or Windows, and provide platform-agnostic instructions.
  • Where the Azure portal is referenced, provide equivalent CLI commands as alternatives.
  • If PowerShell is used, ensure Bash or Azure CLI equivalents are always provided.
GitHub Create Pull Request
Container Registry https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/buffer-gate-public-content.md ...icles/container-registry/buffer-gate-public-content.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
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 into Azure Container Registry, but the PowerShell example is given equal prominence and detail as the CLI example. There are no explicit Linux shell (bash) or native Linux tool examples, nor is there mention of Linux-specific workflows or patterns. The documentation refers to Azure PowerShell as a primary tool, which is more commonly used in Windows environments, and does not offer parity for Linux users beyond the Azure CLI. The order of presentation (CLI first, then PowerShell) is neutral, but the lack of bash or Linux-native examples may disadvantage Linux users.
Recommendations
  • Add explicit bash shell examples for image import using Azure CLI, demonstrating usage in native Linux environments.
  • Clarify that Azure CLI commands can be run directly in Linux/macOS terminals, not just in Azure Cloud Shell.
  • Include references to Linux-native authentication patterns (e.g., using environment variables, .docker/config.json) when discussing Docker Hub authentication.
  • Mention Linux package managers or tools (e.g., apt, yum) for installing Azure CLI and Docker, to assist Linux users.
  • Consider adding a section or tab for 'Linux/Bash' alongside 'Azure CLI' and 'Azure PowerShell' to ensure parity in examples and workflows.
GitHub Create Pull Request
Container Registry https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/container-registry-auth-kubernetes.md ...ntainer-registry/container-registry-auth-kubernetes.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation provides command-line examples using Azure CLI and kubectl, which are cross-platform tools. However, the only credential reset example uses the Azure CLI, which is most commonly installed and used on Windows, and there is no mention of Linux-specific patterns or alternatives (such as using bash scripting, environment variables, or Linux-native credential management). There are no PowerShell-specific commands, but the documentation does not explicitly address Linux usage or provide Linux-centric examples, which may lead to implicit Windows bias.
Recommendations
  • Explicitly mention that Azure CLI and kubectl are cross-platform and provide installation instructions or links for Linux users.
  • Include Linux-specific tips, such as using environment variables to securely handle credentials, or using bash scripting for automation.
  • Add examples of credential management on Linux, such as using keyring or secret management tools.
  • Ensure that references to Azure CLI do not imply Windows-only usage, and clarify that commands work on Linux/macOS as well.
  • Consider adding a note or section for Linux users, highlighting any differences or best practices.
GitHub Create Pull Request
Container Registry https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/container-registry-authentication-managed-identity.md ...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-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides parallel Azure CLI and Azure PowerShell instructions for all steps, but PowerShell is a Windows-centric tool and is presented as an equal alternative throughout. There are no explicit Linux shell examples for Azure resource management (e.g., Bash scripts using REST API or SDKs), and PowerShell installation is described for Ubuntu, which is uncommon for Linux users who typically prefer Bash. The documentation does mention Docker installation for Linux, macOS, and Windows, but all resource management examples are either Azure CLI or PowerShell, with PowerShell given equal prominence despite its Windows origins.
Recommendations
  • Provide Bash script examples for Azure resource management tasks, especially for Linux users who may not use PowerShell.
  • Clarify that Azure CLI is the recommended tool for Linux environments, and mention that PowerShell is optional.
  • Reorder sections so that Azure CLI instructions appear before PowerShell, emphasizing CLI as the default for cross-platform usage.
  • Add explicit notes about the typical usage patterns on Linux (e.g., Bash + Azure CLI) and avoid suggesting PowerShell installation on Linux unless necessary.
  • Where possible, include SDK or REST API examples for advanced users who may prefer direct scripting over CLI/PowerShell.
GitHub Create Pull Request
Container Registry https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/container-registry-troubleshoot-access.md ...ner-registry/container-registry-troubleshoot-access.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page does not provide explicit Windows-only examples or tools, but it exhibits subtle Windows bias by omitting platform-specific troubleshooting steps and examples for Linux. Generic instructions (e.g., configuring Docker behind a proxy, restarting the Docker daemon) do not specify how to perform these actions on Linux, and there are no Linux shell command examples (such as systemctl for restarting Docker). The mention of tools like 'nslookup' (commonly available on both platforms) is paired with 'dig', but there is no explicit parity in example commands or troubleshooting steps for Linux users. The documentation assumes familiarity with Azure CLI and Docker, which are cross-platform, but lacks Linux-specific guidance where platform differences exist.
Recommendations
  • Add explicit Linux command examples for common troubleshooting steps, such as restarting the Docker daemon (e.g., 'sudo systemctl restart docker').
  • Include Linux-specific instructions for configuring Docker behind a proxy, referencing relevant documentation for systemd-based systems.
  • Where network utilities are mentioned, provide example commands for both Windows (e.g., 'nslookup') and Linux (e.g., 'dig', 'host').
  • Clarify any platform-specific differences in Azure CLI usage or environment setup, especially for networking and firewall configuration.
  • Ensure that troubleshooting steps and examples are presented for both Windows and Linux environments, or explicitly state when instructions apply equally to both.
GitHub Create Pull Request
Container Registry https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/container-registry-tutorial-github-verify-notation-trusted-signing.md ...gistry-tutorial-github-verify-notation-trusted-signing.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Linux (bash) and Windows (PowerShell) examples for all relevant CLI commands, but the Windows/PowerShell examples are always presented immediately after the Linux ones, and sometimes with additional context (e.g., directory creation). There is a slight tendency to elaborate more on Windows-specific steps (such as using New-Item in PowerShell), and Windows examples are consistently present, which may suggest a mild Windows bias. However, Linux parity is generally maintained, and no steps are missing for Linux users.
Recommendations
  • Ensure that Linux and Windows examples are equally detailed, especially for tasks like directory creation.
  • Consider alternating the order of examples (sometimes presenting Windows first, sometimes Linux) to avoid implicit prioritization.
  • Add a short note at the beginning clarifying that all steps are equally supported on Linux and Windows, and that users should follow the tab appropriate for their environment.
  • If possible, provide cross-platform commands (e.g., using Python or Node.js scripts) for tasks like downloading files, to further reduce platform-specific bias.
GitHub Create Pull Request
Container Registry https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/includes/azure-container-registry.md ...ontainer-registry/includes/azure-container-registry.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
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 given its own dedicated tab, which can be interpreted as a Windows-centric approach. There is no explicit mention of Linux-specific tools or shell environments, nor are there examples tailored for Bash or Linux users. The Azure CLI example is cross-platform, but the PowerShell example may imply a preference for Windows users. No Linux-specific instructions or troubleshooting are provided.
Recommendations
  • Add explicit Bash/Linux shell examples, showing how to run the Azure CLI command in a typical Linux terminal.
  • Clarify that Azure CLI is fully supported on Linux and macOS, and provide any necessary platform-specific notes (e.g., authentication, environment setup).
  • If PowerShell is mentioned, also mention PowerShell Core (pwsh), which is cross-platform, and clarify usage on Linux/macOS.
  • Consider adding a 'Linux' or 'macOS' tab alongside 'Azure CLI' and 'Azure PowerShell' to reinforce parity.
  • Include troubleshooting or environment setup notes for Linux users if any differences exist.
GitHub Create Pull Request
Container Registry https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/quickstart-client-libraries.md ...cles/container-registry/quickstart-client-libraries.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page demonstrates mild Windows bias in the 'Prerequisites' section, where Azure PowerShell is listed as a primary tool for creating a container registry, alongside the Azure portal and Azure CLI. PowerShell is a Windows-centric tool, and its mention before Linux-native alternatives (such as Bash or shell scripting) may suggest a Windows-first approach. However, the main code samples for all languages use cross-platform tools (Azure CLI, SDKs) and environment variables, and do not rely on Windows-specific patterns or tooling. No PowerShell-heavy examples or missing Linux equivalents are present.
Recommendations
  • In the 'Prerequisites' section, list Azure CLI before Azure PowerShell, as CLI is cross-platform and more commonly used on Linux.
  • Explicitly mention that Azure CLI commands work on both Windows and Linux/macOS, and provide links to installation instructions for multiple platforms.
  • If referencing PowerShell, clarify its cross-platform availability or provide Bash equivalents where appropriate.
  • Ensure that any future examples or instructions do not assume a Windows environment (e.g., avoid referencing Windows-only paths, tools, or environment variables).
GitHub Create Pull Request
Container Registry https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/quickstart-connected-registry-arc-cli.md ...iner-registry/quickstart-connected-registry-arc-cli.md
Medium Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for generating the protected settings JSON file, but the PowerShell example is presented after Bash and uses Unix-style command substitution (suggesting WSL or PowerShell Core on Linux/Mac). There is no exclusive use of Windows tools, nor are Windows-specific patterns or tools mentioned before Linux equivalents. The Azure CLI is used throughout, which is cross-platform, and kubectl commands are shown in Bash. However, the presence of a PowerShell example and its explicit labeling may suggest a slight Windows bias, especially since no explicit Linux-only or MacOS-only instructions are given, and the PowerShell example is not clearly marked as Windows-only.
Recommendations
  • Clarify which shell examples are for which platforms (e.g., label PowerShell as 'Windows PowerShell' and Bash as 'Linux/macOS Bash').
  • Provide explicit instructions for running PowerShell commands on Windows (e.g., using Windows PowerShell vs. PowerShell Core on Linux/macOS).
  • Add a note about running Azure CLI and kubectl on Windows, including any differences in authentication, file paths, or command syntax.
  • Ensure parity by including troubleshooting or setup notes for Linux and macOS users, such as permissions, environment variables, or file system differences.
  • If possible, provide a cross-platform script or highlight any platform-specific caveats for the commands shown.
GitHub Create Pull Request
Container Registry https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/container-registry-rbac-built-in-roles-overview.md ...try/container-registry-rbac-built-in-roles-overview.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page lists Azure PowerShell as a primary method for performing role assignments alongside Azure CLI and Azure portal, but does not mention Linux-specific tools or shell environments (e.g., Bash, scripting with curl, etc.). Azure PowerShell is a Windows-centric tool, and its mention before any Linux equivalents (such as Bash or direct REST API calls) suggests a subtle Windows-first bias. No explicit Linux examples or references to Linux-native tools are provided, and PowerShell is listed as a top-level option for role assignment without clarifying cross-platform parity.
Recommendations
  • Explicitly mention that Azure CLI and Azure PowerShell are cross-platform, but highlight that Bash and shell scripting are common on Linux.
  • Provide example commands for role assignments using Bash (with Azure CLI) and/or REST API calls, demonstrating usage on Linux.
  • Clarify that Azure PowerShell is available on Linux, but most Linux users prefer Azure CLI or Bash scripting.
  • Add links or references to Linux-specific documentation or tutorials for managing Azure Container Registry permissions.
  • Ensure that examples and tool recommendations are balanced, with Linux-native approaches (e.g., Bash, CLI) presented before or alongside Windows/PowerShell options.
GitHub Create Pull Request
Container Registry https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/authenticate-aks-cross-tenant.md ...es/container-registry/authenticate-aks-cross-tenant.md
Medium Priority View Details →
Scanned: 2026-01-08 00:53
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a subtle Windows bias by exclusively referencing the Azure portal (web UI) and Azure CLI, without providing any Linux-specific or cross-platform command-line examples. There are no PowerShell commands, but the lack of explicit Linux shell examples and the use of portal-based instructions may disadvantage Linux users who prefer terminal workflows. Additionally, the documentation does not mention Linux tools or patterns, nor does it provide examples for Linux-based AKS management.
Recommendations
  • Add explicit Linux shell (bash) examples for relevant steps, such as updating AKS service principal credentials and assigning roles.
  • Include Azure CLI commands with notes on cross-platform compatibility (Windows, macOS, Linux).
  • Provide guidance for performing steps via command line on Linux systems, not just via the Azure portal.
  • Clarify that the instructions are applicable to all platforms, and highlight any platform-specific considerations if present.
GitHub Create Pull Request
← Previous Page 4 of 8 Next →