Scan Details - Linux-first Docs for Azure

Aks Deploy an application with the Dapr cluster extension for Azure Kubernetes Service (AKS) or Arc-enabled Kubernetes ...ure-aks-docs/blob/main/articles/aks/quickstart-dapr.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 options for resource cleanup, but consistently lists Azure CLI (cross-platform) first. Azure PowerShell is mentioned as an alternative, but no Windows-specific tools or patterns are prioritized elsewhere. All code and shell examples use Bash syntax, and there are no PowerShell-only or Windows-only instructions. The bias is minor, as Azure CLI is cross-platform and shown first, but PowerShell is included for completeness.

Recommendations

Maintain Azure CLI as the primary example, since it is cross-platform.
Ensure PowerShell instructions are clearly marked as optional for Windows users.
Consider adding explicit notes clarifying that Azure CLI works on Linux/macOS/Windows, and PowerShell is primarily for Windows users.
No further Linux parity improvements are needed, as all critical steps are accessible on Linux/macOS.

Create Pull Request

Aks Certificate Rotation in Azure Kubernetes Service (AKS) ...ks-docs/blob/main/articles/aks/certificate-rotation.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 1 bias type

Detected Bias Types

⚠️ windows_first

Summary

The documentation provides both Linux and Windows file paths when verifying TLS Bootstrapping, but lists the Linux path first. All command-line examples use cross-platform tools (Azure CLI, kubectl, openssl, curl) and shell syntax, which are compatible with Linux/macOS. No PowerShell or Windows-specific tooling is used, and no critical steps are Windows-only. There is a minor bias in listing Linux before Windows in the file path section, but this does not disadvantage Linux users.

Recommendations

No changes are necessary for Linux parity, as all steps are fully cross-platform and Linux users are not disadvantaged.
Continue to provide both Linux and Windows paths or examples where relevant.
Optionally, clarify in the prerequisites that the Azure CLI and kubectl commands are supported on Linux, macOS, and Windows.

Create Pull Request

Aks Troubleshoot the Agentic CLI for Azure Kubernetes Service (AKS) ...ob/main/articles/aks/cli-agent-for-aks-troubleshoot.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example

Summary

The documentation provides troubleshooting steps for the agentic CLI for AKS with some evidence of Windows bias. In Docker-related troubleshooting, Windows/macOS instructions (Docker Desktop) are listed before Linux instructions, and Linux-specific solutions are sometimes less detailed. Azure CLI examples are platform-neutral, but there are no PowerShell or Linux shell alternatives for Azure commands. The documentation does not provide Linux-specific troubleshooting for Docker Desktop alternatives or mention Linux GUI tools. Overall, the bias is minor and does not prevent Linux/macOS users from completing tasks.

Recommendations

Alternate the order of Windows/macOS and Linux instructions to avoid always listing Windows first.
Add Linux-specific troubleshooting tips for Docker (e.g., checking Docker daemon status, logs, and common Linux issues).
Provide PowerShell and Bash equivalents for Azure CLI commands where relevant.
Mention Linux GUI Docker tools (if any) or clarify that Docker Desktop is not available on Linux.
Ensure all troubleshooting steps are equally detailed for Linux, macOS, and Windows.

Create Pull Request

Aks Install the Dapr extension for Azure Kubernetes Service (AKS) and Arc-enabled Kubernetes ...softDocs/azure-aks-docs/blob/main/articles/aks/dapr.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation is generally cross-platform and focused on Azure CLI and Bicep, which are available on Windows, Linux, and macOS. However, there is a minor bias in the 'Listing the CRDs in your cluster' section, where a Windows/PowerShell-specific command ('kubectl get crds | findstr dapr.io') is provided, with no Linux/macOS equivalent (such as using 'grep'). Additionally, the use of 'findstr' as the only example may subtly prioritize Windows users.

Recommendations

Provide Linux/macOS equivalent commands alongside Windows examples, e.g., 'kubectl get crds | grep dapr.io' for Linux/macOS.
When giving command-line examples, consider showing both Windows and Linux/macOS variants, or note that the command works cross-platform.
Review all CLI examples for OS-specific syntax and clarify any differences.
Explicitly state that Azure CLI and Bicep are cross-platform, and link to installation instructions for all supported OSes.

Create Pull Request

Aks Access Kubernetes Resources using the Azure Portal ...e-aks-docs/blob/main/articles/aks/kubernetes-portal.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 troubleshooting, but consistently presents Azure CLI (Linux/macOS-friendly) examples first, followed by Azure PowerShell (Windows-centric) examples. There are no Windows-only tools or patterns, and all instructions are accessible via the Azure portal or cross-platform tools. However, the PowerShell section is present, which may be unnecessary for Linux/macOS users, but it is not prioritized over CLI examples.

Recommendations

Continue to provide Azure CLI examples first, as they are cross-platform.
Consider clarifying that Azure PowerShell is primarily for Windows users, and Azure CLI is recommended for Linux/macOS.
If possible, add a short note indicating that Azure CLI works on Windows, Linux, and macOS, while PowerShell is mostly used on Windows.
Ensure that all portal instructions and YAML examples are platform-neutral, as currently done.

Create Pull Request

Aks Install and Use the Agentic CLI for Azure Kubernetes Service (AKS) (Preview) ...cs/blob/main/articles/aks/cli-agent-for-aks-install.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ minor_windows_tools

Summary

The documentation provides installation and usage instructions for the Agentic CLI for AKS in both client (local) and cluster (in-cluster) modes. While the guide is generally cross-platform and includes Linux-specific instructions (e.g., systemctl for Docker), there are a few instances where Windows/macOS steps or tools are mentioned before Linux equivalents, such as launching Docker Desktop. However, all critical steps and examples are platform-neutral or include Linux instructions, and no PowerShell- or Windows-only tools are used.

Recommendations

When listing steps for starting Docker, present Linux, macOS, and Windows instructions in parallel or clarify that all platforms are supported equally.
Where Docker Desktop is mentioned, add a note that Linux users should use systemctl or their distribution's service manager.
Consider explicitly stating that all commands (az CLI, Docker, kubectl) work on Linux, macOS, and Windows, and link to platform-specific installation guides where relevant.
Ensure example commands (e.g., cleanup, verification) include both Linux and Windows/macOS file path conventions if relevant.

Create Pull Request

Aks Configure Azure CNI Networking in Azure Kubernetes Service (AKS) ...aks-docs/blob/main/articles/aks/configure-azure-cni.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation provides examples for Azure portal, Azure PowerShell, and Azure CLI. The PowerShell section is prominent and includes detailed instructions, with references to installing/upgrading PowerShell on Windows, macOS, and Linux. However, PowerShell is traditionally a Windows-centric tool, and its section appears before the Azure CLI, which is more universally used across Linux/macOS. The CLI section is present and provides parity, but the ordering and emphasis on PowerShell may create friction for Linux/macOS users.

Recommendations

Consider placing Azure CLI instructions before PowerShell, as CLI is more widely used across platforms.
Explicitly mention that Azure CLI is recommended for Linux/macOS users.
Add a note clarifying that PowerShell is available cross-platform, but Azure CLI is often preferred on Linux/macOS.
Ensure that all code blocks and instructions are equally detailed for both PowerShell and CLI.
Where possible, avoid referring to PowerShell as the default unless required.

Create Pull Request

Aks Create an internal load balancer ...s/azure-aks-docs/blob/main/articles/aks/internal-lb.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_tools ⚠️ windows_first

Summary

The documentation provides both Azure CLI and PowerShell options for some prerequisite steps, but consistently mentions Azure PowerShell alongside Azure CLI and the Azure portal as ways to create an AKS cluster. Additionally, it references the PowerShell cmdlet Get-AzVirtualNetworkSubnetConfig as an alternative to the Azure CLI command for listing subnets. However, all actual walkthroughs and examples use cross-platform tools (kubectl, Azure CLI), and there are no PowerShell-specific code snippets or Windows-only instructions. The bias is minor and mostly limited to mentioning PowerShell as an option, with Azure CLI (Linux/macOS-friendly) always present.

Recommendations

When listing ways to create an AKS cluster, consider mentioning Azure CLI and Azure portal first, then Azure PowerShell, or clarify that Azure PowerShell is primarily for Windows users.
For commands to list subnets, prioritize Azure CLI examples and mention PowerShell as an alternative for Windows users.
Ensure that all critical steps have Azure CLI examples and avoid PowerShell-only instructions.
Consider adding a note that Azure CLI and kubectl are fully cross-platform and recommended for Linux/macOS users.

Create Pull Request

Aks Kubernetes on Azure tutorial - Upgrade an Azure Kubernetes Service (AKS) cluster ...in/articles/aks/tutorial-kubernetes-upgrade-cluster.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation provides parity between Azure CLI, Azure PowerShell, and Azure portal instructions for all major tasks. However, Azure PowerShell is featured equally alongside Azure CLI, which may create friction for Linux/macOS users since PowerShell is primarily a Windows tool (though it is available cross-platform). Additionally, PowerShell examples are sometimes given before or alongside CLI examples, and the page metadata includes 'devx-track-azurepowershell', suggesting a slight Windows bias. No critical steps are Windows-only, and Linux users can complete all tasks using Azure CLI or portal.

Recommendations

Clearly indicate that Azure PowerShell is optional and that Azure CLI is the recommended cross-platform tool.
Present Azure CLI examples before PowerShell examples in each section to prioritize Linux/macOS parity.
Add a brief note at the start explaining that Azure PowerShell is available cross-platform but is most commonly used on Windows.
Consider removing or minimizing references to PowerShell in page metadata unless necessary.

Create Pull Request

Aks Azure Kubernetes Service (AKS) Managed Gateway API Installation ...aks-docs/blob/main/articles/aks/managed-gateway-api.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example

Summary

The documentation primarily uses Azure CLI commands (az), which are cross-platform, but does not provide explicit Linux/macOS guidance or examples. There is no mention of Windows-specific tools, but the use of Azure CLI and kubectl is shown without clarifying OS-specific installation or usage. No PowerShell or Windows-only commands are present, but the order and phrasing may imply Windows-first bias by not acknowledging Linux/macOS users or their potential needs.

Recommendations

Add explicit notes clarifying that Azure CLI and kubectl commands work on Linux, macOS, and Windows.
Provide links or instructions for installing Azure CLI and kubectl on Linux/macOS.
Mention any OS-specific considerations (such as environment variable syntax differences) where relevant.
Ensure that output examples and command syntax are not Windows-centric (e.g., avoid Windows-style environment variables or file paths).

Create Pull Request

Aks Develop on Azure Kubernetes Service (AKS) with Helm ...ure-aks-docs/blob/main/articles/aks/quickstart-helm.md

Low Priority View Details →

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 for all Azure-related operations, but consistently presents PowerShell examples alongside CLI, and sometimes before Linux-native alternatives. There is no explicit Linux bias, but the presence of PowerShell examples and references may create friction for Linux/macOS users, especially since Azure PowerShell is primarily used on Windows. However, all critical tasks are covered with Azure CLI (cross-platform) and bash commands, ensuring Linux parity.

Recommendations

Consider clarifying that Azure PowerShell is primarily for Windows users and that Azure CLI is recommended for Linux/macOS.
Present Azure CLI examples first in each section, as it is cross-platform and more commonly used on Linux/macOS.
Optionally, add a note that Azure PowerShell can be installed on Linux/macOS, but Azure CLI is generally preferred.
Ensure that any PowerShell-specific instructions do not overshadow or precede CLI/bash instructions.
Review the 'ms.custom' metadata to ensure it does not imply PowerShell is the primary path.

Create Pull Request

Scan Information

Problematic Pages