Container Instances

The documentation page for 'Standby pools for Azure Container Instances' shows a moderate Windows bias. The provider registration step exclusively uses Azure PowerShell, with no Azure CLI or REST example. In the 'Availability zones' section, PowerShell is presented before CLI and REST, and both CLI and PowerShell examples are given, but the initial registration step is PowerShell-only. There are no Linux-specific tools or patterns mentioned, but the ordering and example selection favor Windows/PowerShell users.

• Add Azure CLI and REST examples for provider registration, not just PowerShell.
• Ensure CLI examples are presented before or alongside PowerShell examples in all sections.
• Explicitly mention that all commands (PowerShell, CLI, REST) can be run from Linux/macOS environments, and provide guidance for non-Windows users where relevant.
• Consider including bash script snippets or notes for Linux users where appropriate.

The documentation provides both Azure CLI and Azure PowerShell examples for all deployment, management, and cleanup steps. However, PowerShell examples are given equal prominence and are presented immediately alongside CLI examples, which may create a slight Windows-first impression. There are no Linux/macOS-specific shell examples (e.g., Bash), but the use of Azure CLI is cross-platform and sufficient for non-Windows users. No Windows-only tools or patterns are mentioned, and the documentation does not omit Linux/macOS equivalents.

• Clarify that Azure CLI commands work on Windows, Linux, and macOS, and recommend CLI for cross-platform usage.
• Consider listing Azure CLI examples first, as CLI is the default for cross-platform scenarios.
• Optionally, add a note that PowerShell examples are primarily for Windows users, while CLI is recommended for Linux/macOS.
• Ensure that screenshots or UI references (if any) do not assume Windows environments.

The documentation provides both Azure CLI and PowerShell examples for retrieving prediction results, but PowerShell is given a dedicated tab and example, which is primarily a Windows tool. The PowerShell example appears before the REST API example, and there is no mention of Linux/macOS-specific shell usage (e.g., Bash), nor any explicit Linux/macOS instructions. However, the Azure CLI example is cross-platform and shown first, mitigating the bias somewhat.

• Clarify that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
• Consider adding a Bash shell example or explicitly stating that the CLI commands work on Linux/macOS.
• If PowerShell is shown, note that PowerShell Core is available on Linux/macOS, or provide equivalent Bash examples.
• Ensure that examples and instructions do not imply PowerShell is required unless there is a Windows-only feature.

The documentation provides examples for Azure CLI, PowerShell, and REST API. PowerShell is given a dedicated example tab, and is listed before REST API. While Azure CLI is cross-platform, PowerShell is primarily associated with Windows, and no Linux/macOS-specific shell examples (such as Bash/cURL for REST) are provided. The ordering of examples (CLI, then PowerShell, then REST) may subtly prioritize Windows users, and the lack of explicit Linux/macOS shell examples creates minor friction for non-Windows users.

• Add a Bash/cURL example for querying the REST API, demonstrating how Linux/macOS users can retrieve the health state.
• Clarify that Azure CLI is cross-platform and works on Linux/macOS as well as Windows.
• Consider listing REST API and CLI examples before PowerShell, or grouping all examples equally to avoid implicit prioritization.
• Explicitly mention that PowerShell Core is available on Linux/macOS if relevant.