Scan Details - Linux-first Docs for Azure

Virtual Machines Instantly access managed disk snapshots ...les/virtual-machines/disks-instant-access-snapshots.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example

Summary

The documentation provides both Azure CLI (bash-style) and Azure PowerShell examples for creating instant access snapshots, but does not include explicit Linux/macOS shell examples (e.g., bash, zsh) or mention Linux-specific considerations. PowerShell examples are given equal prominence, and there is no discussion of Linux tools or patterns. The CLI examples use bash syntax, which is compatible with Linux/macOS, but this is not clarified. No Linux-specific troubleshooting or alternative workflows are described.

Recommendations

Explicitly state that Azure CLI examples are compatible with Linux/macOS shells and provide sample commands using bash/zsh syntax.
Add a section or tab labeled 'Linux/macOS Shell' to clarify usage on non-Windows platforms.
Include troubleshooting tips or notes for Linux users (e.g., installation of Azure CLI, environment variables, file permissions).
Ensure that PowerShell is not presented as the default or primary method, and clarify cross-platform parity.
Mention any OS-specific caveats if they exist (e.g., differences in authentication, file paths, or environment setup).

Create Pull Request

Container Instances Get prediction results for standby pools for Azure Container Instances (Preview) ...ttps://github.com/MicrosoftDocs/azure-compute-docs/blob/main/articles/container-instances/container-instances-standby-pool-prediction-results.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example

Summary

The documentation provides explicit examples for Azure CLI, PowerShell, and REST API, but the PowerShell example is given equal prominence as the CLI, and there is no mention of Linux/macOS-specific shell usage (such as Bash or scripting). The CLI example is generic, but the PowerShell example is Windows-specific, and there are no Linux/macOS shell or scripting examples. The documentation does not clarify cross-platform compatibility for the CLI or REST, nor does it mention Linux tools or patterns.

Recommendations

Add explicit Bash or shell examples for Linux/macOS users, demonstrating retrieval and parsing of prediction results.
Clarify that the Azure CLI and REST API examples are cross-platform and can be used on Linux/macOS as well as Windows.
Consider reordering examples so that CLI (cross-platform) comes before PowerShell (Windows-specific), or add a note about platform compatibility.
Include troubleshooting or usage notes for Linux/macOS environments, such as authentication or environment setup.

Create Pull Request

Virtual Machines Ebdsv6 size series ...rtual-machines/sizes/memory-optimized/ebdsv6-series.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_tools ⚠️ windows_first

Summary

The documentation page is largely platform-neutral, focusing on VM specifications and features. However, there is mild Windows bias in the 'Feature support' section, where nested virtualization is linked only to a Windows/Hyper-V guide, and in the 'Network' section, where bandwidth testing references NTTTCP—a Windows-centric tool—without mentioning Linux alternatives. Windows and Windows tools are mentioned before or instead of Linux equivalents in these cases.

Recommendations

Include links or references to Linux/KVM nested virtualization documentation alongside the Windows/Hyper-V guide.
Mention Linux-compatible bandwidth testing tools (e.g., iperf, netperf) in the networking section and provide relevant links.
Where features are supported or unsupported for both Windows and Linux, list both platforms together or in alphabetical order to avoid perceived prioritization.
Ensure that examples and tooling references are provided for both Windows and Linux where applicable.

Create Pull Request

Container Instances Big containers on Azure container instances ...ob/main/articles/container-instances/big-containers.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example

Summary

The documentation mentions PowerShell as a deployment option alongside Azure CLI, ARM templates, and the portal, but does not provide explicit Linux/macOS examples or mention Bash or shell scripting. The ordering of deployment tools lists PowerShell before Linux-native options, and there is no discussion of Linux-specific workflows or considerations. This creates a subtle Windows-first bias and may leave Linux/macOS users unsure about parity or best practices.

Recommendations

Explicitly mention Bash/shell scripting as a supported deployment method.
Provide example commands for both PowerShell and Bash/Azure CLI, showing parity.
Reorder deployment tool lists to alternate or start with cross-platform tools (e.g., Azure CLI, then PowerShell).
Add a note clarifying that all deployment methods are supported on Linux/macOS and Windows.
Include links to Linux/macOS-specific documentation or troubleshooting guides if relevant.

Create Pull Request

Container Instances Quickstart - create a container instance - Bicep ...iner-instances/container-instances-quickstart-bicep.md

Low Priority View Details →

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 commands, but consistently lists PowerShell (a Windows-centric tool) as the only alternative to CLI, without mentioning Bash or native Linux/macOS shell scripting. The tab order and headings always present CLI first, but the only non-CLI alternative is PowerShell, which may give the impression that Windows tools are the primary or only supported alternative to CLI. There are no explicit Linux/macOS-specific instructions or troubleshooting notes.

Recommendations

Clarify that Azure CLI is fully cross-platform and recommend it as the preferred tool for Linux/macOS users.
Explicitly mention that PowerShell Core is available on Linux/macOS if PowerShell examples are to be retained.
Consider adding Bash script examples or notes for Linux/macOS users where appropriate.
Add a short section in prerequisites or introduction clarifying tool parity and platform support.
If possible, provide links to documentation on installing Azure CLI and PowerShell on all platforms.

Create Pull Request

Container Instances Understand the health state of your standby pool for Azure Container Instances ...ances/container-instances-standby-pool-health-state.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy

Summary

The documentation provides examples for Azure CLI, PowerShell, and REST API. PowerShell is given its own dedicated example tab, which is a Windows-centric tool, and is listed before REST API. There is no mention of Linux/macOS-specific tools or shell commands (e.g., Bash, curl, jq), nor is there guidance for Linux users beyond the CLI and REST API. The CLI example is cross-platform, but the PowerShell example and its prominence suggest a mild Windows bias.

Recommendations

Add explicit Bash/shell examples using curl for REST API calls and jq for parsing output.
Clarify that Azure CLI works on Linux/macOS and provide example commands for those environments (e.g., piping output to jq).
Consider reordering tabs so that cross-platform tools (CLI, REST) appear before Windows-specific tools (PowerShell).
Mention that PowerShell Core is available on Linux/macOS if relevant, or clarify if the example is Windows-only.

Create Pull Request

Container Instances Standby pools for Azure Container Instances ...instances/container-instances-standby-pool-overview.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy

Summary

The documentation page demonstrates mild Windows bias by presenting PowerShell commands first for critical resource provider registration and by including both PowerShell and Azure CLI examples for pool creation, but listing PowerShell before CLI. There are no Linux-specific shell examples (e.g., Bash), and the use of 'Azure Cloud Shell' is ambiguous but typically defaults to PowerShell in documentation. However, Azure CLI examples are present, and all JSON/REST examples are platform-neutral.

Recommendations

Present Azure CLI (Bash) examples before PowerShell, as CLI is cross-platform and more common for Linux/macOS users.
Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and provide both command variants for provider registration.
Add a Bash shell example for provider registration (e.g., using 'az provider register').
Ensure parity in all code samples by including both CLI and PowerShell tabs where relevant.
Clarify any platform-specific behaviors or requirements, especially for Linux/macOS users.

Create Pull Request

Scan Information

Problematic Pages