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
187 issues found
Showing 151-175 of 187 flagged pages
Container Registry
Store Helm Charts in Azure Container Registry
...es/container-registry/container-registry-helm-repos.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides a generally cross-platform approach, using Helm and Azure CLI commands, which work on Windows, Linux, and macOS. However, there are minor signs of Windows bias: the environment variable is set using the Windows-style 'set' command without a Linux/macOS equivalent, and the order of Kubernetes cluster creation options lists Azure CLI, PowerShell, and Portal, with PowerShell (Windows-specific) mentioned before Portal. No PowerShell-specific commands are given, and most examples use cross-platform tools, but the lack of explicit Linux/macOS shell equivalents for environment variable setting may create friction.
Recommendations
- Provide both Windows ('set') and Linux/macOS ('export') commands when setting environment variables (e.g., ACR_NAME).
- Clarify that Azure CLI commands are cross-platform and can be run on Linux/macOS as well as Windows.
- When listing options for creating AKS clusters, consider mentioning Azure CLI and Portal first, and clarify PowerShell is Windows-specific.
- Review all shell command examples to ensure both Windows and Linux/macOS users are accommodated.
Create Pull Request
Container Registry
Deploy the Connected Registry Arc Extension
...iner-registry/quickstart-connected-registry-arc-cli.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for generating the protected settings JSON file, but the Bash example is presented first. All other command-line examples use Bash syntax or are cross-platform Azure CLI commands. No Windows-specific tools or patterns are favored, and Linux users are not blocked from completing any tasks.
Recommendations
- Maintain parity by continuing to provide both Bash and PowerShell examples where relevant.
- Consider explicitly stating that all Azure CLI commands are cross-platform and can be run on Linux, macOS, and Windows.
- Optionally, provide a note that PowerShell Core is available on Linux/macOS for users who prefer PowerShell.
Container Registry
Store Helm Charts in Azure Container Registry
...es/container-registry/container-registry-helm-repos.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is mostly cross-platform, focusing on Helm and Azure CLI, which are available on Windows, Linux, and macOS. However, there are subtle Windows biases: the environment variable setup uses the Windows 'set' command without showing the Linux/macOS equivalent ('export'), and the order of Kubernetes cluster creation options lists Azure CLI, PowerShell, and Portal, with PowerShell (Windows-specific) mentioned before Portal. No explicit Linux/macOS examples are given for environment variable setup, and there are no PowerShell-specific commands, but the omission of Linux/macOS equivalents creates minor friction.
Recommendations
- Provide both Windows ('set') and Linux/macOS ('export') examples for environment variable setup.
- Clarify that Azure CLI commands are cross-platform and, where relevant, mention Linux/macOS usage.
- When listing cluster creation options, consider listing Azure CLI and Portal first, and clarify PowerShell is Windows-specific.
- Add a note that all CLI commands work on Linux/macOS unless otherwise specified.
Container Registry
Manage Public Content in Private Container Registry
...icles/container-registry/buffer-gate-public-content.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for importing images to Azure Container Registry, but consistently lists Azure PowerShell (a Windows-centric tool) alongside Azure CLI and gives it equal prominence. The PowerShell example is detailed and appears immediately after the CLI example, which may create friction for Linux/macOS users who are less likely to use PowerShell. There are no Linux-specific shell examples (e.g., Bash), and the documentation does not mention Linux-native tools or workflows beyond Azure CLI.
Recommendations
- Prioritize Azure CLI examples, as CLI is cross-platform and preferred by Linux/macOS users.
- Add Bash shell examples for common workflows, especially for importing images and authentication.
- Clarify that Azure PowerShell is optional and primarily for Windows users; consider placing PowerShell examples after CLI and Bash examples.
- Explicitly mention that Azure CLI and Cloud Shell are fully supported on Linux/macOS.
- Consider including a section on using Docker CLI directly for Linux/macOS users, where appropriate.
Container Registry
Deploy the Connected Registry Arc Extension
...iner-registry/quickstart-connected-registry-arc-cli.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for generating the protected settings JSON file, but Bash is presented first. The PowerShell example is included, but it uses Unix-style tools (tr -d '\r'), which may not be native to Windows PowerShell. All subsequent CLI commands are shown in Bash/Azure CLI syntax, and Kubernetes commands are Bash-based. There are no Windows-only tools or patterns, and Linux examples are present throughout. The bias is minor, mainly in the ordering and the PowerShell example's reliance on Unix utilities.
Recommendations
- Ensure the PowerShell example uses native PowerShell methods for string manipulation instead of Unix tools like 'tr'.
- Clarify that Bash and PowerShell examples are equivalent and provide guidance for Windows users if any Bash commands require adaptation.
- Consider alternating the order of Bash and PowerShell tabs or explicitly state that both environments are supported.
- Add a note about using Azure CLI in PowerShell on Windows, including any differences in output formatting or command syntax.
Container Registry
Deploy the Connected Registry Arc Extension
...iner-registry/quickstart-connected-registry-arc-cli.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for generating the protected settings JSON file, but Bash is shown first. The PowerShell example is included, but there is a slight bias in the formatting and explanation: the Bash example is more detailed and uses the canonical file name ('protected-settings-extension.json'), while the PowerShell example uses 'settings.json' and includes a workaround for carriage returns. The rest of the documentation uses Azure CLI and kubectl commands, which are cross-platform and do not show Windows-specific tools or patterns. No Linux examples are missing, and Linux users can complete all tasks.
Recommendations
- Ensure both Bash and PowerShell examples use consistent file naming and structure.
- Add brief notes clarifying that Azure CLI and kubectl commands work on Linux, macOS, and Windows.
- Consider providing a short explanation for PowerShell users about handling carriage returns, or use a more cross-platform approach.
- If possible, provide parity in example detail and output formatting between Bash and PowerShell tabs.
Container Registry
Store Helm Charts in Azure Container Registry
...es/container-registry/container-registry-helm-repos.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page provides command-line examples for Helm and Azure CLI, which are cross-platform tools. However, there is a subtle Windows bias in the use of the 'set' command for environment variable assignment, which is specific to Windows CMD. No explicit Linux/macOS equivalent ('export') is shown, and the Windows-style example appears first. All other commands use syntax compatible with Linux/macOS (bash), but the initial environment variable setup may confuse non-Windows users. No PowerShell-specific or Windows-only tools are used, and the overall workflow is cross-platform.
Recommendations
- Provide both Windows (CMD/PowerShell) and Linux/macOS (bash) syntax for environment variable assignment. For example, show 'set ACR_NAME=...' for Windows and 'export ACR_NAME=...' for Linux/macOS.
- Add a note clarifying which commands are platform-specific and which are universal.
- Where possible, use bash-style syntax for environment variables, as this is more widely compatible across platforms and shells.
- Consider including a short section or table summarizing command differences for Windows, Linux, and macOS users.
Container Registry
Deploy the Connected Registry Arc Extension
...iner-registry/quickstart-connected-registry-arc-cli.md
Low Priority
View Details →
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 shown after Bash. There is no evidence of exclusive use of Windows tools or missing Linux examples; all critical steps (deployment, verification, cleanup) use Azure CLI and kubectl, which are cross-platform. The PowerShell example is present for Windows parity, but Bash is shown first, which is a minor bias toward Linux/macOS users.
Recommendations
- Present Bash and PowerShell examples side-by-side or in a tabbed format to emphasize equal support for both platforms.
- Explicitly state that all Azure CLI and kubectl commands work on Linux, macOS, and Windows.
- Ensure that any platform-specific nuances (e.g., file path differences, shell quoting) are mentioned for both Bash and PowerShell users.
Container Registry
Azure Container Registry Authentication Options Explained
...ontainer-registry/container-registry-authentication.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Minor Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for authentication, but PowerShell (a Windows-centric tool) is consistently presented alongside CLI, and sometimes before or with equal prominence. The table of authentication methods lists PowerShell commands for each method, and PowerShell examples are given their own dedicated sections. However, Linux/macOS users are not blocked from completing any tasks, as Azure CLI and Docker commands are fully documented and cross-platform. There is a minor Windows-first bias in the order and prominence of PowerShell examples, but Linux parity is generally maintained.
Recommendations
- Explicitly state that Azure CLI commands work on Linux/macOS and Windows, and that PowerShell is primarily for Windows users.
- In example sections, present Azure CLI (cross-platform) examples before PowerShell (Windows-centric) ones.
- Add a brief note clarifying that PowerShell examples are for users who prefer or require PowerShell, and that CLI is recommended for cross-platform workflows.
- Consider including bash script examples for common automation scenarios, especially in sections discussing scripting.
- Where environment variables are referenced (e.g., DOCKER_COMMAND), clarify syntax differences between Windows (set) and Linux/macOS (export).
Container Registry
Store Helm Charts in Azure Container Registry
...es/container-registry/container-registry-helm-repos.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation is generally cross-platform and uses standard Helm and Azure CLI commands, which work on Windows, Linux, and macOS. However, there is a minor Windows-first bias in the environment variable setting example, where 'set ACR_NAME=<container-registry-name>' is shown (Windows CMD syntax) before any mention of Linux/macOS alternatives. All other command examples use cross-platform syntax (bash, Azure CLI), and there are no PowerShell-specific or Windows-only tool references.
Recommendations
- Replace or supplement the 'set ACR_NAME=<container-registry-name>' example with the cross-platform 'export ACR_NAME=<container-registry-name>' (bash/zsh/fish) and note the difference for Windows CMD users.
- Add a short note clarifying environment variable syntax differences between Windows CMD, PowerShell, and Linux/macOS shells.
- Ensure all environment variable examples are shown in both Windows and Linux/macOS formats, or use the more common bash syntax first.
Container Registry
Deploy the Connected Registry Arc Extension
...iner-registry/quickstart-connected-registry-arc-cli.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for generating the protected settings JSON file, but Bash is shown first. The PowerShell example is included in a separate tab, ensuring parity. The rest of the instructions use Azure CLI and kubectl, which are cross-platform tools. No Windows-only tools or patterns are present, and Linux/macOS users can follow all steps without friction.
Recommendations
- Continue to provide both Bash and PowerShell examples for cross-platform parity.
- Consider explicitly mentioning that Azure CLI and kubectl commands work on Windows, Linux, and macOS.
- Ensure that any future examples or troubleshooting steps do not assume a Windows environment unless necessary.
Container Registry
Deploy the Connected Registry Arc Extension
...iner-registry/quickstart-connected-registry-arc-cli.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for generating the protected settings JSON file, but Bash is shown first. The PowerShell example is present and uses standard Azure CLI commands, but there is a slight emphasis on Windows/PowerShell by including a dedicated tab for it. All other commands and workflows are cross-platform (Azure CLI, kubectl), and there are no Windows-only tools or patterns. No Linux equivalents are missing, and the overall workflow is platform-agnostic.
Recommendations
- Clarify that both Bash and PowerShell examples are equivalent and suitable for their respective platforms.
- Consider adding a note that Azure CLI commands work on Windows, Linux, and macOS, and that users should select the example matching their shell environment.
- Ensure parity in example complexity and output file naming between Bash and PowerShell (e.g., both use protected-settings-extension.json).
Container Registry
Deploy the Connected Registry Arc Extension
...iner-registry/quickstart-connected-registry-arc-cli.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for generating the protected settings JSON file, but Bash is shown first and PowerShell second. The PowerShell example is present, but there is a slight bias in ordering. All other commands use Azure CLI and kubectl, which are cross-platform and do not favor Windows tools or patterns. No critical steps are Windows-only, and Linux/macOS users can follow all instructions without friction.
Recommendations
- Consider explicitly stating that both Bash and PowerShell examples are provided for cross-platform compatibility.
- Alternate the order of Bash and PowerShell tabs in future documentation to avoid perceived bias.
- Ensure that any OS-specific nuances (e.g., file path formats, shell differences) are noted for both platforms.
Container Registry
Deploy the Connected Registry Arc Extension
...iner-registry/quickstart-connected-registry-arc-cli.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for generating the protected settings JSON file, but the Bash example is presented first. All other command-line instructions use Azure CLI and kubectl, which are cross-platform and do not show Windows-specific bias. No Windows-only tools or patterns are used, and Linux/macOS users are fully supported.
Recommendations
- Maintain the current approach of providing both Bash and PowerShell examples for critical steps.
- Optionally, clarify that Azure CLI and kubectl commands work on Windows, Linux, and macOS.
- If possible, provide a short note that PowerShell Core is available cross-platform, to further reduce perceived bias.
Container Registry
Store Helm Charts in Azure Container Registry
...es/container-registry/container-registry-helm-repos.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides cross-platform instructions for storing Helm charts in Azure Container Registry, primarily using Helm CLI and Azure CLI commands, which are available on Windows, Linux, and macOS. However, there is minor Windows bias in the environment variable setup section, where the 'set' command (Windows syntax) is shown before any Linux/macOS alternative, and no explicit Linux/macOS equivalent ('export') is provided. All other commands and examples are platform-neutral or use Bash syntax, which is common on Linux/macOS and supported in Windows environments via WSL or PowerShell. No PowerShell-specific examples or Windows-only tools are present.
Recommendations
- In the environment variable setup section, add the Linux/macOS equivalent command (e.g., 'export ACR_NAME=<container-registry-name>') alongside the Windows 'set' command.
- Wherever environment variables are referenced, clarify syntax differences between Windows (cmd), PowerShell, and Bash.
- Consider explicitly stating that all CLI commands work on Linux, macOS, and Windows (with Bash/WSL/PowerShell), and link to platform-specific setup guides if available.
Container Registry
Deploy the Connected Registry Arc Extension
...iner-registry/quickstart-connected-registry-arc-cli.md
Low Priority
View Details →
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 to Bash, and there is no explicit Linux/macOS-specific guidance for PowerShell users. In the PowerShell example, a Unix tool (`tr -d '\r'`) is used, which may not work natively in Windows PowerShell without additional tools. All other CLI and kubectl examples are Bash-oriented, but these are generally cross-platform. The documentation does not mention Windows-specific tools or patterns outside of the PowerShell example, and no critical steps are Windows-only.
Recommendations
- Clarify that the Bash example is for Linux/macOS and the PowerShell example is for Windows users.
- In the PowerShell example, replace the use of `tr -d '\r'` with a native PowerShell approach for removing carriage returns, such as using `.Replace('`r','')`.
- Explicitly state which shell/environment each example is intended for, and ensure that PowerShell examples are fully compatible with Windows environments.
- Consider providing a note about cross-platform compatibility for Azure CLI and kubectl commands.
Container Registry
Deploy the Connected Registry Arc Extension
...iner-registry/quickstart-connected-registry-arc-cli.md
Low Priority
View Details →
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 shown second. The rest of the guide uses 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/macOS users can follow all steps without friction.
Recommendations
- Ensure Bash and PowerShell examples are presented with equal prominence, possibly side-by-side or with clear tabs.
- Consider adding a note clarifying that all Azure CLI and kubectl commands work on Linux, macOS, and Windows.
- If possible, provide explicit Linux/macOS verification steps (e.g., checking file contents with 'cat') alongside PowerShell equivalents.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all major steps, but PowerShell is a Windows-centric tool (even though it can run on Linux). The structure consistently presents Azure CLI examples first, followed by PowerShell, which is a minor 'Windows-first' bias. There are no examples or instructions that are Windows-only, and all VM creation and Docker installation steps target Ubuntu Linux. No critical Linux gaps are present.
Recommendations
- Clarify that Azure PowerShell is cross-platform and provide guidance for Linux/macOS users on installing and using PowerShell if they are unfamiliar.
- Consider adding Bash-only or native Linux shell examples for steps that do not require Azure CLI or PowerShell, where appropriate.
- Explicitly state that all instructions are tested and supported on Linux VMs, and highlight any OS-specific caveats if they exist.
- If possible, include a short section or note for macOS users, especially for Docker installation and Azure CLI/PowerShell usage.
Container Registry
Azure Container Registry custom roles
...ainer-registry/container-registry-rbac-custom-roles.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for listing permissions, but PowerShell is mentioned alongside CLI in a way that may suggest parity. However, PowerShell is a Windows-centric tool, and its inclusion may create friction for Linux/macOS users. Additionally, in several places, Azure PowerShell is listed before or alongside Azure CLI, which is cross-platform, but there are no Linux/macOS-specific notes or examples. No Windows-only tools or patterns are exclusively used, and the core instructions are platform-neutral.
Recommendations
- Prioritize Azure CLI examples and references, as CLI is cross-platform and preferred by Linux/macOS users.
- Add explicit notes clarifying that Azure PowerShell is available on Linux/macOS, but CLI is recommended for those platforms.
- Where multiple tool options are listed, present Azure CLI first, followed by PowerShell, to reduce perceived Windows bias.
- Consider including a brief section or note for Linux/macOS users, confirming that all steps can be completed with Azure CLI.
Container Registry
Manage Public Content in Private Container Registry
...icles/container-registry/buffer-gate-public-content.md
Low Priority
View Details →
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 is presented immediately after the CLI example. There is a slight 'windows_first' bias in mentioning Azure PowerShell as a primary tool alongside CLI, which may be less relevant for Linux/macOS users. However, the CLI example is cross-platform and shown first, and no critical steps are Windows-only. No Linux-specific tools or shell examples (e.g., Bash scripts) are provided, but the CLI coverage is sufficient for Linux/macOS users.
Recommendations
- Clarify that Azure CLI is cross-platform and recommended for Linux/macOS users.
- Optionally, add a Bash shell example for common workflows (e.g., scripting image imports).
- Explicitly state that Azure PowerShell is primarily for Windows users, and that Linux/macOS users should use Azure CLI.
- Consider adding a note about Azure Cloud Shell availability for both Bash and PowerShell, and which is recommended for different OS users.
Container Registry
Access Registry Images from ACI
...cles/container-registry/container-registry-auth-aci.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell sample scripts, but references to PowerShell are prominent and placed alongside CLI examples, which may suggest a slight Windows bias. The main example uses Azure CLI, which is cross-platform, but PowerShell is highlighted as an alternative, and the note about 'export MSYS_NO_PATHCONV=1' is relevant for Bash on Windows, not Linux/macOS. There are no explicit Linux/macOS examples or references to platform-specific considerations for those users.
Recommendations
- Add explicit notes or examples for Linux/macOS users, such as confirming Azure CLI commands work natively on those platforms.
- Clarify that Azure CLI is cross-platform and provide troubleshooting tips for Linux/macOS environments if needed.
- Consider including links to sample scripts or documentation specifically for Bash or other common Linux shells.
- If mentioning PowerShell, note its availability on Linux/macOS and provide guidance for those platforms if there are differences.
Container Registry
Quickstart - Create Registry in Portal
...iner-registry/container-registry-get-started-portal.md
Low Priority
View Details →
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 Azure PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and appears immediately after it. There are no Linux-specific command-line examples (e.g., Bash), and PowerShell is not available by default on most Linux/macOS systems. However, Docker installation instructions do link to Linux, Mac, and Windows guides, and the core workflow is cross-platform.
Recommendations
- Clarify that Azure PowerShell is primarily for Windows users, and recommend Azure CLI for Linux/macOS users.
- Consider providing Bash or shell script examples for Linux/macOS users where relevant.
- Explicitly state that Azure CLI commands work on all platforms, while PowerShell is most common on Windows.
- In tabbed instructions, list Azure CLI first and highlight its cross-platform nature.
- Add a note for Linux/macOS users that PowerShell is optional and not required.
Container Registry
Manage OCI Artifacts and Supply Chain Artifacts with ORAS
...ntainer-registry/container-registry-manage-artifact.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Linux/macOS and Windows command examples for key ORAS CLI operations, but consistently lists Linux/macOS instructions first and Windows examples second. Windows examples use Windows CMD syntax (with ^ line continuation and .\oras.exe), while Linux/macOS use Bash. No PowerShell-specific examples are present, and all major workflows are covered for both platforms. There is minor bias in the ordering of examples, with Linux/macOS shown first, but no omission of Windows or Linux instructions.
Recommendations
- Consider alternating the order of platform examples in different sections to avoid perceived bias.
- Explicitly mention that both Linux/macOS and Windows are supported, and clarify which syntax to use for each.
- Add PowerShell examples for Windows users who prefer it over CMD, or clarify that CMD is recommended.
- Ensure all examples are functionally equivalent and tested on both platforms.
Container Registry
Azure Container Registry SKU Features and Limits
...articles/container-registry/container-registry-skus.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for key operations (such as changing SKUs and showing registry usage), but consistently lists PowerShell examples immediately after CLI examples and explicitly mentions PowerShell commands before Linux/macOS alternatives (such as Bash scripts or REST API usage). There are no Linux-specific examples (e.g., Bash, shell scripting), and PowerShell is presented as a primary alternative to the CLI, which may create friction for Linux/macOS users unfamiliar with PowerShell.
Recommendations
- Add explicit Bash/shell script examples for common operations, especially for tasks like changing SKUs and querying usage.
- Present REST API usage examples in a cross-platform way (e.g., using curl) alongside CLI and PowerShell.
- When listing command options, alternate the order or clarify that Azure CLI is cross-platform and PowerShell is Windows-centric.
- Consider adding a note that Azure CLI works natively on Linux/macOS, while PowerShell is primarily used on Windows.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for querying vulnerability assessment results, but PowerShell is given its own tab and is listed before the portal option. There is a slight Windows bias due to the inclusion and prominence of PowerShell, which is primarily a Windows tool, and the ordering of examples (CLI, then PowerShell, then Portal). However, the Azure CLI example is fully cross-platform and no critical functionality is Windows-only.
Recommendations
- Clarify that Azure CLI is cross-platform and suitable for Linux/macOS users.
- Consider listing Azure CLI before PowerShell to emphasize cross-platform support.
- Explicitly mention that PowerShell Core is available on Linux/macOS if relevant.
- Add a note for Linux/macOS users confirming that all functionality is available via Azure CLI.