Scan Details - Linux-first Docs for Azure

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

Medium 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 Azure resource management tasks, with PowerShell examples given equal prominence. However, there are no Linux-specific instructions or examples for using native Linux tools or shell environments. The use of PowerShell is highlighted as a primary method alongside Azure CLI, which may create friction for Linux/macOS users who do not use PowerShell.

Recommendations

Clarify that Azure PowerShell examples are intended for Windows users and that Azure CLI is cross-platform.
Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and recommend CLI for non-Windows environments.
Consider listing Azure CLI examples before PowerShell examples, or defaulting to CLI in mainline instructions, with PowerShell as an alternative.
Add notes or links for Linux/macOS users regarding installation and usage of Azure CLI and kubectl in their environments.
Remove or de-emphasize PowerShell examples in sections where CLI is sufficient and more broadly applicable.

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, focusing on Azure CLI and Bicep for installation and management of the Dapr extension on AKS and Arc-enabled Kubernetes clusters. However, there is a minor Windows bias in the troubleshooting section, where the example for listing CRDs uses PowerShell's 'findstr' command with 'kubectl', which is specific to Windows. Additionally, the example is shown without a Linux/macOS equivalent, and the PowerShell example appears first and exclusively.

Recommendations

Provide Linux/macOS equivalents for shell commands, such as using 'grep' instead of 'findstr' (e.g., 'kubectl get crds | grep dapr.io').
Where shell commands are shown, present both Windows (PowerShell) and Linux/macOS (bash/zsh) examples side-by-side or in tabs.
Add a note clarifying that the command syntax may differ between Windows and Linux/macOS environments.
Review other command examples to ensure none are inadvertently Windows-specific.

Create Pull Request

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 instructions for resource cleanup, but lists Azure CLI first. PowerShell is mentioned as an alternative for Azure management, but all operational and application deployment examples use cross-platform tools (kubectl, curl, git). No Windows-only tools or patterns are required, and Linux/macOS users can follow the guide without friction.

Recommendations

Continue listing Azure CLI before PowerShell, as CLI is cross-platform and preferred for Linux/macOS users.
Consider explicitly noting that all kubectl, curl, and git commands work on Linux/macOS and Windows.
If possible, clarify that Azure PowerShell is optional and primarily for users who prefer PowerShell environments.
Ensure any future examples or screenshots do not assume Windows-only environments (e.g., avoid showing Windows terminal exclusively).

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: 3 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example

Summary

The documentation provides installation and usage instructions for the agentic CLI for AKS, with examples and guidance for both client and cluster modes. While the core CLI commands are cross-platform, there is a subtle Windows bias in several areas: Docker startup instructions list macOS/Windows (Docker Desktop) before Linux (systemctl), and verification steps for Docker cleanup reference the Windows/macOS path (~/.azure/aksAgent.config) without clarifying Linux differences. There are no PowerShell-specific examples, but the ordering and phrasing often prioritize Windows/macOS approaches before Linux equivalents. Some verification steps (e.g., checking for Docker Desktop icon) are not relevant for Linux users, and Linux-specific troubleshooting is less detailed.

Recommendations

Present Linux instructions and examples alongside or before Windows/macOS instructions, especially for Docker startup and verification.
Clarify file paths and configuration locations for Linux users (e.g., ~/.azure/aksAgent.config may differ on Linux).
Add troubleshooting notes for common Linux issues (such as permissions, systemd status, or SELinux/AppArmor).
Explicitly state that all az CLI commands work on Linux, macOS, and Windows, and provide any OS-specific caveats.
Where Docker Desktop is referenced, add a note about Linux alternatives (e.g., dockerd, podman compatibility 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

⚠️ windows_first ⚠️ powershell_heavy

Summary

The documentation provides parallel instructions for Azure portal, Azure PowerShell, and Azure CLI. However, the PowerShell section is presented before the CLI section, and there is a notable emphasis on Azure PowerShell, which is a Windows-centric tool (though it is cross-platform). The PowerShell section includes more detailed setup instructions and troubleshooting for different OSes, but the CLI section is more concise. There are no missing Linux examples, and both CLI and PowerShell are supported on Linux/macOS, but the ordering and depth of PowerShell coverage may create a slight perception of Windows bias.

Recommendations

Present Azure CLI instructions before Azure PowerShell, as CLI is more universally used across platforms.
Ensure that setup and troubleshooting instructions for CLI are as detailed as those for PowerShell, including explicit notes for Linux/macOS users.
Clarify in the PowerShell section that Azure PowerShell is cross-platform and provide equal prominence to Linux/macOS installation and usage.
Consider combining or cross-referencing PowerShell and CLI sections where possible to reduce perceived bias.

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: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy

Summary

The documentation generally provides troubleshooting steps for both Windows/macOS and Linux users. However, in the Docker-related troubleshooting section, instructions for starting Docker on Windows/macOS (via Docker Desktop) are presented before Linux commands. Additionally, for permission issues, Windows/macOS users are told to restart Docker Desktop, while Linux users receive more detailed command-line instructions. No PowerShell-specific commands are present, but the pattern of mentioning Windows/macOS solutions before Linux ones is consistent. All Azure CLI and kubectl examples are cross-platform.

Recommendations

Present Linux and Windows/macOS troubleshooting steps in parallel or in a consistent order (e.g., Linux first, then Windows/macOS, or vice versa).
Provide equally detailed instructions for both platforms (e.g., explain how to restart Docker Desktop and how to restart the Docker daemon on Linux).
Explicitly state that all CLI commands work on Linux, macOS, and Windows (with WSL or Azure CLI installed), to reassure non-Windows users.
Consider adding a note about platform differences in Docker installation and management.

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 prerequisite steps, but references to PowerShell (Get-AzVirtualNetworkSubnetConfig) and Azure PowerShell quickstart are given alongside or before Linux equivalents. The main workflow and all code samples use kubectl and Azure CLI, which are cross-platform, but PowerShell is mentioned as a tool for some resource queries. There are no Linux/macOS-specific examples or explicit parity notes.

Recommendations

When listing prerequisite tools, mention Azure CLI as the primary cross-platform tool and clarify that PowerShell is optional for Windows users.
Where PowerShell commands are referenced (e.g., for listing subnets), provide equivalent Azure CLI commands first and clearly indicate cross-platform compatibility.
Consider adding a note that all main steps (kubectl, Azure CLI) work on Linux/macOS and Windows, and provide links to installation guides for each OS.
If mentioning PowerShell, always pair it with the Azure CLI equivalent and avoid implying PowerShell is required for Linux/macOS users.

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 (cross-platform) and Azure PowerShell (Windows-centric) instructions for updating AKS API server authorized IP ranges, but the Azure CLI tab is presented first. No Linux- or macOS-specific instructions are missing, and all critical tasks can be completed using the Azure Portal or Azure CLI. However, the inclusion of Azure PowerShell examples may create a slight Windows bias, especially if users perceive PowerShell as the default or preferred method.

Recommendations

Clarify that Azure CLI is cross-platform and works on Windows, Linux, and macOS, while Azure PowerShell is primarily for Windows users.
Consider adding a note for Linux/macOS users to use Azure CLI, and for Windows users to choose either Azure CLI or PowerShell.
Ensure that Azure CLI examples are always shown first (as is currently the case), and that PowerShell is clearly marked as optional for Windows users.
If possible, add a brief mention that all portal-based actions are OS-agnostic.

Create Pull Request

Aks Secure Pod Traffic with Network Policies in Azure Kubernetes Service (AKS) ...ks-docs/blob/main/articles/aks/use-network-policies.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ windows_tools

Summary

The documentation provides both Linux and Windows examples for AKS network policies, but Windows-specific instructions (such as administrator credential creation and feature flag registration) are presented in detail and before Linux equivalents in some sections. Windows tools and patterns (e.g., HNS ACLPolicy) are described alongside Linux tools (IPTables/BPF), but Windows-specific steps are sometimes more prominent. The main workflow and CLI examples are cross-platform, but the ordering and emphasis can create minor friction for Linux/macOS users.

Recommendations

Present Linux and Windows instructions in parallel or clearly separated sections, with Linux examples shown first where appropriate.
Ensure Linux-specific limitations and steps are as detailed as Windows equivalents.
Clarify which steps are platform-specific and which are universal to avoid confusion.
Add explicit notes or callouts when a section is Windows-only or Linux-only.
Consider grouping platform-specific content under clear headings (e.g., 'Linux instructions', 'Windows instructions').

Create Pull Request

Scan Information

Problematic Pages