Container Registry
149
Total Pages
126
Linux-Friendly Pages
23
Pages with Bias
15.4%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
293 issues found
Showing 151-175 of 293 flagged pages
Container Registry
Quickstart - Create Registry - Bicep
...ainer-registry/container-registry-get-started-bicep.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides deployment instructions for both Azure CLI and PowerShell, but the introductory text mentions PowerShell first and references opening PowerShell or Azure CLI. The example for using Visual Studio Code terminal uses a Windows-centric keyboard shortcut (Ctrl + `), and PowerShell is given its own tab alongside CLI. There are no Linux-specific instructions or examples, but the Azure CLI commands are cross-platform. The documentation does not reference Windows-only tools, but the ordering and emphasis slightly favor Windows/PowerShell users.
Recommendations
- Mention Azure CLI first in deployment instructions, as it is cross-platform.
- Clarify that Azure CLI commands work on Windows, Linux, and macOS.
- Add a note about opening terminals on Linux/macOS (e.g., use Ctrl+Shift+` in VS Code on some platforms).
- Consider including Bash shell examples or explicitly stating that Azure CLI commands can be run in Bash or other terminals.
- Balance the order of CLI and PowerShell tabs, or default to CLI.
Create Pull Request
Container Registry
Import Container Images to ACR using Azure APIs
...container-registry/container-registry-import-images.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides parity between Azure CLI and Azure PowerShell throughout, but consistently includes PowerShell examples alongside CLI examples, which may signal a bias toward Windows users. Azure PowerShell is a Windows-centric tool, and its inclusion may be unnecessary for Linux/macOS users, who typically use Azure CLI. Additionally, PowerShell examples are sometimes presented immediately after CLI examples, rather than offering Linux/macOS-specific guidance or alternatives. No Windows-only tools or patterns are referenced, and all commands are cross-platform via Azure CLI.
Recommendations
- Clarify that Azure CLI is fully cross-platform and preferred for Linux/macOS users, while Azure PowerShell is primarily for Windows environments.
- Consider presenting Azure CLI examples first, and PowerShell examples as optional for Windows users.
- Add explicit notes indicating that Azure CLI commands work identically on Linux, macOS, and Windows.
- Remove or de-emphasize PowerShell examples in sections where Azure CLI is sufficient and more universal.
- If possible, provide shell script examples (bash/zsh) for Linux/macOS users, especially for automation scenarios.
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
Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for key operations, but PowerShell is consistently mentioned alongside or immediately after CLI, and no explicit Linux/macOS shell examples (e.g., Bash) are provided. The CLI examples are cross-platform, but the presence of PowerShell (a Windows-centric tool for many users) without explicit mention of Bash or Linux-native tools may create a subtle Windows bias. There are no references to Linux-specific tools or workflows, and the order of examples sometimes puts PowerShell before REST API or other platform-neutral options.
Recommendations
- Clarify that Azure CLI commands work on Linux, macOS, and Windows, and consider explicitly stating this in the documentation.
- Add Bash shell examples where appropriate, or clarify that the CLI examples are intended for cross-platform use.
- When listing programmatic options, consider listing Azure CLI (cross-platform) before PowerShell, and REST API as a platform-neutral alternative.
- If possible, provide short notes or links for Linux/macOS users on installing and using Azure CLI.
Container Registry
Import Container Images to ACR using Azure APIs
...container-registry/container-registry-import-images.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides parity between Azure CLI and Azure PowerShell throughout, with examples for both. However, the PowerShell examples are not inherently Windows-specific, as Azure PowerShell is cross-platform. There are no Windows-only tools or patterns, and Linux/macOS users can use Azure CLI or Azure PowerShell. The only minor bias is that PowerShell examples are sometimes shown immediately after CLI examples, but neither is prioritized or presented as Windows-only.
Recommendations
- Clarify that Azure PowerShell is cross-platform and can be used on Linux/macOS, not just Windows.
- Consider explicitly mentioning that both Azure CLI and Azure PowerShell are available on all major platforms.
- If possible, add brief notes or links about running Azure CLI and PowerShell on Linux/macOS for new users.
Container Registry
Quickstart - Create Registry - Bicep
...ainer-registry/container-registry-get-started-bicep.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides deployment instructions for both Azure CLI and PowerShell, but PowerShell is mentioned alongside CLI in the opening sentence and is given its own example tab. The instructions for opening the terminal reference Visual Studio Code, which is cross-platform, but the key combination (ctrl + `) is Windows-centric. There are no Linux-specific examples or explicit mention of Bash or Linux/macOS terminal environments. The cleanup instructions only reference the Azure portal, which is platform-neutral.
Recommendations
- Explicitly mention that Azure CLI commands can be run in Bash on Linux/macOS, not just in PowerShell.
- Add a Bash example tab for deploying the Bicep file, or clarify that the CLI example works identically on Bash, Zsh, and other shells.
- Adjust terminal instructions to reference macOS/Linux key combinations (e.g., 'Ctrl+`' on Windows, 'Cmd+`' on macOS) or simply say 'open your terminal'.
- Consider mentioning that Visual Studio Code is available on Linux/macOS, or suggest other editors commonly used on those platforms.
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. However, the PowerShell example is given equal prominence to the CLI example, and PowerShell is a Windows-centric tool. The documentation does not explicitly mention Linux-native tools (such as Bash or shell scripting) or provide Linux/macOS-specific guidance. Azure CLI is cross-platform, but PowerShell is presented as an alternative without clarifying its platform limitations. The order of examples (CLI first, then PowerShell) is appropriate, but the lack of explicit Linux/macOS parity or mention of native shell usage is a minor bias.
Recommendations
- Clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Explicitly state that Azure PowerShell is primarily for Windows users, and provide guidance for Linux/macOS users to use Azure CLI.
- Consider adding a brief Bash shell example for Docker image manipulation, if relevant.
- Add a note about Azure Cloud Shell availability for both CLI and PowerShell, and its platform independence.
Container Registry
Push & Pull Container Image using Azure Container Registry
...-registry/container-registry-get-started-docker-cli.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for registry authentication and image removal, but PowerShell examples are given equal prominence and detail as CLI examples. There is a slight 'windows_first' bias: PowerShell is mentioned alongside CLI in prerequisites and throughout, even though PowerShell is primarily used on Windows. However, all Docker commands are cross-platform and the Azure CLI is available on Linux/macOS. No critical steps are Windows-only, and Linux/macOS users can complete all tasks.
Recommendations
- Clarify that Azure PowerShell is primarily for Windows users, and Azure CLI is recommended for Linux/macOS.
- Consider listing Azure CLI examples before PowerShell in each section, or marking PowerShell as 'Windows only'.
- Add explicit notes or tabs for Linux/macOS users where authentication or registry management is discussed, highlighting Azure CLI usage.
- Ensure parity in example detail for Azure CLI and Docker commands, and avoid implying PowerShell is equally relevant for Linux/macOS.
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 generally cross-platform, as Helm and Azure CLI are available on Windows, Linux, and macOS. However, there are minor signs of Windows bias: the environment variable example uses the Windows 'set' command instead of the cross-platform 'export', and the order of Kubernetes cluster creation options lists Azure PowerShell before Linux-friendly alternatives. No PowerShell-specific commands are given, but there is a lack of explicit Linux/macOS examples for environment variables.
Recommendations
- Replace 'set ACR_NAME=<container-registry-name>' with 'export ACR_NAME=<container-registry-name>' or provide both commands for Windows and Linux/macOS.
- When listing options for creating AKS clusters, mention Azure CLI (Linux/macOS-friendly) before Azure PowerShell.
- Add notes clarifying that all Azure CLI and Helm commands are cross-platform, and provide explicit examples for Linux/macOS where relevant.
- Ensure all environment variable instructions are shown for both Windows (set) and Linux/macOS (export).
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
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for key operations such as viewing usage and changing SKUs. However, in several sections, Azure PowerShell is mentioned before REST API or alongside CLI, and PowerShell examples are given equal prominence to CLI. There are no Linux-specific tools or shell examples (e.g., Bash scripting), but the CLI examples are cross-platform. No critical features are Windows-only, and Linux/macOS users can complete all tasks using the CLI or REST API.
Recommendations
- When listing programmatic options, consistently mention Azure CLI before PowerShell, as CLI is cross-platform and PowerShell is Windows-first.
- Consider adding Bash or shell script examples where appropriate, especially for automation scenarios.
- Clarify that Azure CLI commands work on all platforms, while PowerShell is primarily for Windows (though available cross-platform).
- Where possible, provide REST API examples or links for users who may not use CLI or PowerShell.
Container Registry
Quickstart - Create Registry in Portal
...iner-registry/container-registry-get-started-portal.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell options for signing in to the registry, but the PowerShell section is presented equally alongside CLI, and PowerShell is a Windows-centric tool. However, Docker instructions and links are provided for Linux, Mac, and Windows, and all portal steps are platform-neutral. No critical steps are Windows-only, but PowerShell is mentioned as an option for registry login, which may create minor friction for Linux/macOS users who typically use Azure CLI.
Recommendations
- Clearly indicate that Azure CLI is cross-platform and preferred for Linux/macOS users, while PowerShell is primarily for Windows.
- Consider presenting Azure CLI instructions first, as it is the most universally supported tool.
- Add a brief note clarifying that Azure PowerShell is available on Linux/macOS but is less commonly used outside Windows.
- Ensure that all command-line examples and links are equally accessible and relevant for Linux/macOS users.
Container Registry
Quickstart - Create Registry - Bicep
...ainer-registry/container-registry-get-started-bicep.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides deployment instructions for both Azure CLI and PowerShell, but PowerShell is presented as a primary option alongside CLI. The instructions for opening a terminal reference Visual Studio Code and its key combination, which is cross-platform, but PowerShell is featured as a main tab, which may imply Windows bias. There are no Linux-specific examples or explicit mentions of Linux/macOS compatibility, and PowerShell is not natively available on most Linux/macOS systems. However, Azure CLI is cross-platform and shown first.
Recommendations
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
- Clarify that PowerShell examples are intended for Windows users, and suggest Bash or Zsh for Linux/macOS users.
- Add a Bash example or note that Azure CLI can be used in Bash shells on Linux/macOS.
- Consider listing Azure CLI as the default or primary method, with PowerShell as an alternative for Windows users.
Container Registry
Push & Pull Container Image using Azure Container Registry
...-registry/container-registry-get-started-docker-cli.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for authentication and image removal, but PowerShell examples are given equal prominence to CLI examples, and Windows-specific PowerShell tools are mentioned alongside cross-platform alternatives. There is minor Windows bias in the ordering and presence of PowerShell examples, but Linux/macOS users can complete all tasks using the CLI or Docker commands.
Recommendations
- Clearly indicate which commands are cross-platform and which are Windows-only (e.g., PowerShell).
- Consider listing Azure CLI examples before PowerShell examples, as CLI is cross-platform.
- Add explicit notes that Azure PowerShell is Windows-centric, and recommend Azure CLI for Linux/macOS users.
- Ensure that all critical tasks have Azure CLI or Docker CLI examples, and avoid implying PowerShell is required for Linux/macOS users.
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 generally cross-platform, focusing on Helm and Azure CLI, which are available on Windows, Linux, and macOS. However, there are subtle signs of Windows bias: the environment variable setup uses 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 explicit Linux/macOS examples are given for environment variable setup, and the documentation does not clarify cross-platform command differences.
Recommendations
- Provide both Windows ('set') and Linux/macOS ('export') commands for setting environment variables.
- Clarify that Azure CLI and Helm commands are cross-platform and provide any OS-specific notes where relevant.
- When listing options for creating AKS clusters, mention Azure CLI and Portal first, and clarify PowerShell is Windows-specific.
- Add a note or table summarizing command differences for Windows vs. Linux/macOS where applicable.
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 tasks such as showing registry usage and changing the registry SKU. However, PowerShell (a Windows-centric tool) is mentioned alongside CLI in several places, and in some cases, PowerShell examples are given immediately after CLI, which could be interpreted as a mild 'windows_first' bias. There are no Linux/macOS-specific tools or shell examples (e.g., Bash scripts), but the CLI examples are cross-platform. No critical functionality is Windows-only, and Linux/macOS users can complete all tasks using the CLI.
Recommendations
- Clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Consider providing Bash script examples or explicitly stating that all CLI commands work on Linux/macOS.
- If mentioning PowerShell, note that Azure PowerShell is available cross-platform, or link to installation instructions for non-Windows systems.
- Where possible, present CLI examples before PowerShell, or group them under a 'cross-platform' heading.
Container Registry
Import Container Images to ACR using Azure APIs
...container-registry/container-registry-import-images.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 import scenarios, but consistently includes PowerShell examples alongside CLI, and references PowerShell cmdlets and patterns. Azure PowerShell is primarily used on Windows, and its inclusion may signal a Windows bias. Additionally, PowerShell examples are sometimes presented immediately after CLI examples, which can subtly prioritize Windows tools. However, Azure CLI is cross-platform and all examples are available for it, ensuring Linux/macOS parity.
Recommendations
- Clarify that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
- Consider explicitly mentioning that Azure PowerShell is primarily for Windows users, and Azure CLI is recommended for Linux/macOS.
- If possible, show Azure CLI examples first, or highlight them as the default for non-Windows platforms.
- Add a brief section on running Azure CLI on Linux/macOS (e.g., installation link, shell compatibility).
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
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for querying and updating Azure Container Registry SKUs. Azure PowerShell (a Windows-centric tool) is mentioned alongside Azure CLI, but not before it. There are no Linux/macOS-specific tools or shell examples, but Azure CLI is cross-platform and is shown first. No exclusive Windows tools or patterns are used, and no critical steps are Windows-only.
Recommendations
- Ensure that Azure CLI examples are clearly marked as cross-platform (Linux/macOS/Windows).
- Optionally, include Bash or shell script examples for common tasks, especially for Linux/macOS users.
- Clarify that Azure PowerShell is available cross-platform, but that Azure CLI is often preferred on Linux/macOS.
- If possible, add a note that all features and commands shown are available on Linux/macOS unless otherwise stated.
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
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for importing images to Azure Container Registry. The CLI example (which is cross-platform and Linux-friendly) is shown first, followed by PowerShell. There are no Windows-specific tools or patterns mentioned exclusively, and Linux/macOS users are not excluded from any critical workflow. However, PowerShell is referenced as an alternative tool, which may be less relevant for Linux/macOS users.
Recommendations
- Maintain Azure CLI as the primary example, as it is cross-platform.
- Consider clarifying that Azure PowerShell is primarily for Windows users, and that Azure CLI is recommended for Linux/macOS.
- Add a brief note indicating that Azure CLI and Cloud Shell are fully supported on Linux/macOS, and PowerShell is optional.
- If possible, provide bash shell scripting examples for automating imports, to further enhance Linux parity.
Container Registry
Quickstart - Create Registry - Bicep
...ainer-registry/container-registry-get-started-bicep.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying the Bicep file, but PowerShell is mentioned alongside CLI in the introductory text and is given its own example tab. There is a minor bias in mentioning PowerShell and Windows-centric tools (like Visual Studio Code) before Linux equivalents, but Azure CLI is cross-platform and examples are present. No critical steps are Windows-only.
Recommendations
- Explicitly state that Azure CLI commands work on Linux, macOS, and Windows.
- Add a Bash example tab or clarify that the CLI example is suitable for Bash shells on Linux/macOS.
- Mention alternative editors (such as Vim, nano, or VS Code on Linux/macOS) when suggesting how to create the Bicep file.
- When referencing the integrated terminal, note that Linux/macOS users can use their preferred terminal applications.
- Consider listing CLI (cross-platform) examples before PowerShell (Windows-centric) examples.
Container Registry
Push & Pull Container Image using Azure Container Registry
...-registry/container-registry-get-started-docker-cli.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for authentication and image removal, but PowerShell examples are given equal prominence to CLI examples, and PowerShell is mentioned as a recommended method for command-line authentication. There are minor signs of Windows bias, such as mentioning PowerShell alongside CLI throughout, and referencing Windows in the Docker installation prerequisites before Linux/macOS. However, all core Docker commands are cross-platform and shown generically, and Azure CLI is available on all platforms.
Recommendations
- Clarify that Azure PowerShell is primarily for Windows users, while Azure CLI is cross-platform.
- List Linux/macOS before Windows in Docker installation prerequisites to avoid subtle Windows-first ordering.
- Add explicit notes or tabs for Bash/Linux shell usage where Azure CLI is shown, to reinforce cross-platform parity.
- Consider including sample commands for Bash shell (e.g., using environment variables, scripting) for Linux/macOS users.
- Ensure that any references to PowerShell are clearly marked as Windows-specific, and avoid implying it is required for Linux/macOS users.
Container Registry
Quickstart - Create Registry in Portal
...iner-registry/container-registry-get-started-portal.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for signing in to the registry, but does not show any Linux-specific commands or shell examples (e.g., Bash). However, it does mention Docker installation for Mac, Windows, and Linux, and the main workflow uses Docker CLI, which is cross-platform. Azure PowerShell is presented alongside Azure CLI, but PowerShell is more commonly associated with Windows, and no Bash or Linux shell equivalents are given for Azure CLI usage. The order of examples (CLI first, then PowerShell) is neutral, but the lack of explicit Linux shell examples may create minor friction for Linux/macOS users.
Recommendations
- Add explicit Bash/Linux shell examples for Azure CLI commands, clarifying that Azure CLI works on all platforms.
- Mention that Azure CLI commands can be run in Bash, Zsh, or other Linux/macOS shells, not just Windows Command Prompt or PowerShell.
- Consider including a note or tab for Bash usage, especially for commands like az acr login.
- Ensure parity in instructions for signing in and interacting with the registry, so Linux/macOS users see themselves represented.
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 generally uses cross-platform tools (Helm CLI, Azure CLI) and avoids Windows-only commands or tools. However, there are minor signs of Windows bias: the environment variable setup uses the Windows-style 'set' command without showing the Linux/macOS equivalent ('export'), and the order of Kubernetes cluster creation options lists Azure PowerShell before the Azure portal and Azure CLI. No Linux/macOS-specific examples are provided for environment variable setup, and the 'set' command may confuse Linux/macOS users.
Recommendations
- Provide both Windows ('set') and Linux/macOS ('export') examples for environment variable setup.
- When listing options for creating AKS clusters, show Azure CLI first, as it is cross-platform, or clarify that Azure PowerShell is Windows-only.
- Review all command snippets for platform-specific syntax and add Linux/macOS equivalents where needed.
- Explicitly state that all Helm and Azure CLI commands are cross-platform, and note any exceptions.
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 largely cross-platform, focusing on Helm and Azure CLI, which are available on Windows, Linux, and macOS. However, there are subtle signs of Windows bias: the environment variable example uses the Windows-style 'set' command instead of the cross-platform 'export', and the prerequisites list Azure PowerShell as an option before mentioning the Azure portal and Azure CLI. No explicit Linux/macOS-only examples are given, and the initial environment variable setup could confuse Linux/macOS users.
Recommendations
- Replace the 'set' command for environment variables with 'export' or provide both Windows ('set') and Unix ('export') examples.
- Ensure all CLI examples use syntax compatible with Bash/Zsh (e.g., variable assignment, quoting) or provide alternatives for Windows CMD/PowerShell where relevant.
- Clarify that Azure CLI and Helm are cross-platform and provide links or notes for Linux/macOS installation.
- When listing options (e.g., for creating AKS clusters), avoid putting Windows-specific tools (PowerShell) before cross-platform ones (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
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for importing images into Azure Container Registry. The Azure CLI example is presented first, which is cross-platform and suitable for Linux/macOS users. Azure PowerShell, which is Windows-centric, is also included. No Linux-specific tools or shell examples (e.g., Bash scripts, curl, docker CLI) are given, but the Azure CLI is the recommended and primary cross-platform tool. There is a minor bias in listing Azure PowerShell as an equal alternative, but no critical Windows bias is present.
Recommendations
- Clarify that Azure CLI is fully cross-platform and recommended for Linux/macOS users.
- Consider adding a brief Bash shell or Docker CLI example for importing images, if relevant.
- Explicitly state that Azure PowerShell is primarily for Windows users, and that Linux/macOS users should use Azure CLI.
- Add a note that Azure Cloud Shell supports both CLI and PowerShell, but CLI is more universal.
Container Registry
Push & Pull Container Image using Azure Container Registry
...-registry/container-registry-get-started-docker-cli.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell authentication and image removal examples, but PowerShell is given equal prominence to CLI, and Windows-specific PowerShell commands are included throughout. The instructions for stopping containers reference 'Ctrl+C', which is Windows-centric, and PowerShell is mentioned as a recommended method for authentication and image removal, potentially creating friction for Linux/macOS users. However, Docker CLI commands are cross-platform and the page does link to Linux/macOS Docker installation guides.
Recommendations
- Clarify that PowerShell examples are primarily for Windows users and provide Bash or shell equivalents for Linux/macOS where PowerShell is used.
- When referencing keyboard shortcuts, include macOS/Linux equivalents (e.g., 'Ctrl+C or Cmd+C').
- Consider listing Azure CLI (cross-platform) examples before PowerShell, or explicitly state that PowerShell is for Windows environments.
- Add a note that Azure PowerShell is available on Linux/macOS, but Bash/CLI is more common for those platforms.
- Ensure parity by including any Linux/macOS-specific tips or troubleshooting steps, if applicable.
Container Registry
Quickstart - Create Registry - Bicep
...ainer-registry/container-registry-get-started-bicep.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell deployment instructions, but PowerShell is mentioned alongside CLI in the main deployment section and is given its own example. The instructions for opening a terminal reference Visual Studio Code and a Windows-specific keyboard shortcut (ctrl + `), which may not be universal. There are no Linux-specific examples or explicit mentions of Linux/macOS tools, and PowerShell is presented as a primary option, which may create friction for Linux/macOS users.
Recommendations
- Explicitly mention that Azure CLI works cross-platform (Windows, Linux, macOS) and is recommended for Linux/macOS users.
- Provide Linux/macOS-specific instructions for opening a terminal (e.g., Terminal app, bash, zsh) instead of only referencing Visual Studio Code and Windows shortcuts.
- Consider listing Azure CLI instructions before PowerShell, as CLI is more universally available.
- Add a note clarifying that PowerShell examples are for Windows users, and Linux/macOS users should use Azure CLI.
- Include sample commands for bash/zsh where relevant, or clarify that Azure CLI commands are shell-agnostic.