Scan Details - Linux-first Docs for Azure

Aks Access Kubernetes Resources using the Azure Portal ...e-aks-docs/blob/main/articles/aks/kubernetes-portal.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 updating AKS API server authorized IP ranges, but the PowerShell example is presented immediately after the CLI example and is given equal prominence. There are no Linux-specific examples (e.g., Bash or native Linux commands) for retrieving the public IP address, and the PowerShell example is unnecessary for Linux/macOS users. The rest of the documentation is portal-centric and platform-neutral, but the troubleshooting section could create friction for Linux/macOS users.

Recommendations

Add a Bash-only example for retrieving the public IP address (e.g., `curl ifconfig.me` or `curl ipinfo.io/ip`) in the troubleshooting section.
Clarify that Azure PowerShell examples are for Windows users, and Azure CLI is cross-platform.
Consider showing Azure CLI examples first, and PowerShell examples in a separate, clearly marked Windows-only tab.
Explicitly mention that Azure CLI works on Linux/macOS/Windows, while Azure PowerShell is Windows-centric.

Create Pull Request

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

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 1 bias type

Detected Bias Types

⚠️ windows_first

Summary

The documentation provides installation and usage instructions for the Agentic CLI for AKS, supporting both client mode (local Docker) and cluster mode (in-cluster Helm deployment). While the content is generally cross-platform, there is a minor bias in the Docker daemon startup instructions: Windows/macOS instructions (Docker Desktop) are mentioned before Linux instructions (systemctl commands). All CLI examples use Azure CLI, which is cross-platform, and there are no PowerShell-specific commands or Windows-only tools referenced. Linux examples and instructions are present, but not always shown first.

Recommendations

Present Linux instructions alongside or before Windows/macOS instructions for Docker daemon startup.
Explicitly mention that Azure CLI and Docker commands are cross-platform and provide links to Linux/macOS-specific installation guides where relevant.
Consider adding a short section clarifying parity and supported OSes for the Agentic CLI, Docker, and Azure CLI.
Ensure that any troubleshooting or FAQ sections also include Linux/macOS-specific guidance if applicable.

Create Pull Request

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

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 1 bias type

Detected Bias Types

⚠️ windows_first

Summary

The documentation generally provides cross-platform troubleshooting steps, but in the Docker daemon troubleshooting section, instructions for macOS/Windows are listed before Linux, and the Windows/macOS solution is described in more detail (mentioning the system tray/menu bar). Linux instructions are present and accurate, but are listed after Windows/macOS. All other sections use cross-platform or Linux-first tools (kubectl, az CLI), and provide Linux-specific solutions where relevant.

Recommendations

Present Linux, macOS, and Windows instructions in parallel or in a consistent order (e.g., Linux, macOS, Windows) to avoid implicit prioritization.
Ensure that all platforms receive equally detailed instructions (e.g., mention how to start Docker on Linux, macOS, and Windows with similar clarity).
Where possible, use platform-agnostic language or group instructions by platform with clear headings.

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

Detected Bias Types

⚠️ windows_first ⚠️ missing_linux_example

Summary

The documentation is generally cross-platform and AKS-focused, but there is a minor Windows bias in the section 'Verify TLS Bootstrapping is enabled on current agent node pool', where Windows file paths are mentioned before Linux paths and Linux instructions are not always as prominent. However, the majority of examples and commands are Linux-oriented (bash, Azure CLI, kubectl), and Windows-specific tools (PowerShell, CMD) are not used. The bias is minor and does not prevent Linux/macOS users from completing the tasks.

Recommendations

List Linux file paths before Windows file paths in relevant sections.
Provide explicit Linux/macOS instructions/examples where Windows paths or behaviors are mentioned.
Clarify that all CLI and kubectl commands are cross-platform unless otherwise noted.
Add a note confirming parity for Linux/macOS users, especially in sections referencing file paths or node access.

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 detailed and references Windows tools, but also includes instructions for macOS and Linux. However, PowerShell is presented before CLI, and PowerShell is traditionally associated with Windows, which may create a perception of Windows bias. Azure CLI, which is more cross-platform, is included with full examples, but is listed after PowerShell.

Recommendations

Present Azure CLI examples before PowerShell, as CLI is more universally used across Linux/macOS and Windows.
Explicitly note that both Azure PowerShell and Azure CLI are fully supported on Linux and macOS, and provide links to installation instructions for all platforms.
Consider adding a brief note about the cross-platform nature of Azure PowerShell and Azure CLI to reduce perceived Windows bias.
Ensure that any PowerShell instructions reference Linux/macOS usage equally, perhaps with explicit example commands for those platforms.

Create Pull Request

Aks Install Dapr Extension for Azure Kubernetes Service (AKS) ...softDocs/azure-aks-docs/blob/main/articles/aks/dapr.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_tools ⚠️ powershell_heavy ⚠️ missing_linux_example

Summary

The documentation is generally cross-platform, focusing on Azure CLI and Bicep, which are available on Windows, Linux, and macOS. However, in the 'List the CRDs in your cluster' section, only a Windows-specific example is given using 'kubectl get crds | findstr dapr.io', which relies on the Windows 'findstr' command. No Linux/macOS equivalent (such as 'grep') is provided. Additionally, the use of PowerShell syntax for variable assignment (e.g., '$MY_RESOURCE_GROUP') may confuse Linux/macOS users, as Bash uses a different syntax. The rest of the documentation avoids Windows-specific tools and patterns, but these minor examples create friction for non-Windows users.

Recommendations

Provide Linux/macOS equivalents for commands using Windows tools, e.g., 'kubectl get crds | grep dapr.io' alongside the 'findstr' example.
Clarify variable assignment syntax for Bash users, e.g., 'export MY_RESOURCE_GROUP=...' or note that '$MY_RESOURCE_GROUP' is PowerShell syntax.
Where possible, show both Windows and Linux/macOS command examples in troubleshooting and scripting sections.

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 are present and the PowerShell cmdlet is mentioned before its Linux equivalent in the subnet listing section. Azure CLI is used for all main examples, which is cross-platform, but the inclusion and ordering of PowerShell references may create minor friction for Linux/macOS users.

Recommendations

When listing tools for prerequisites or resource queries, mention Azure CLI first as it is cross-platform, and PowerShell second.
Where PowerShell cmdlets are referenced, ensure equivalent Azure CLI commands are also provided and shown first.
Consider clarifying that Azure CLI works on Windows, Linux, and macOS, and that PowerShell is optional for Windows users.
If PowerShell is referenced, provide a brief note for Linux/macOS users that Azure CLI is the recommended tool.

Create Pull Request

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

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 1 bias type

Detected Bias Types

⚠️ windows_first

Summary

The documentation primarily uses Azure CLI commands for installation and management, which are cross-platform. However, Azure CLI examples are presented using the 'azurecli-interactive' code block, which is often associated with Windows/PowerShell environments, and there is no explicit mention of Linux/macOS shell usage or alternative instructions. The verification steps use 'kubectl' and 'jq', which are standard tools on Linux/macOS, but no explicit guidance is given for Linux/macOS users. Overall, the bias is minor and mostly in the ordering and implicit assumptions.

Recommendations

Clarify that Azure CLI commands are cross-platform and can be run on Linux, macOS, and Windows.
Add explicit notes or examples for Linux/macOS users, such as installation instructions for Azure CLI and 'jq'.
Use generic shell code blocks (e.g., 'bash') for Azure CLI commands instead of 'azurecli-interactive', or provide both PowerShell and bash examples if relevant.
Mention that 'kubectl' and 'jq' are available on all platforms and provide links to their installation guides for Linux/macOS.

Create Pull Request

Aks Kubernetes on Azure tutorial - Create an Azure Kubernetes Service (AKS) cluster ...ain/articles/aks/tutorial-kubernetes-deploy-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 parallel instructions for Azure CLI, Azure PowerShell, and Azure Developer CLI. However, Azure PowerShell is featured equally alongside Azure CLI, which is more commonly used on Linux/macOS. PowerShell is primarily a Windows tool, and its inclusion may suggest a Windows-centric approach. Additionally, PowerShell examples are given equal prominence to Azure CLI, rather than being secondary or optional. There are no explicit Linux/macOS-specific examples or notes, and the documentation does not mention Linux shell patterns (e.g., Bash, zsh) or package managers for installing tools. However, all core tasks can be completed using Azure CLI, which is cross-platform, and there are no critical sections that are Windows-only.

Recommendations

Clarify that Azure CLI is the recommended cross-platform tool for Linux/macOS users, and PowerShell is primarily for Windows environments.
Add explicit notes or sections for Linux/macOS users, such as installation instructions for kubectl using native package managers (apt, brew, yum).
Provide Bash/zsh shell command examples where relevant, especially for environment variable usage.
Consider listing Azure CLI instructions before PowerShell, or marking PowerShell as 'Windows only' where appropriate.
Mention that Azure Cloud Shell is available in Bash and PowerShell modes, and clarify which mode is used in examples.

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 full parity between Azure CLI, Azure PowerShell, and Azure portal for all AKS upgrade tasks. However, PowerShell examples are included throughout, which is primarily a Windows-centric tool, and the documentation references Azure PowerShell alongside Azure CLI in nearly every section. In some sections, PowerShell is mentioned before the portal, but Azure CLI (cross-platform) is always presented first. There are no missing Linux/macOS examples, and all CLI commands are cross-platform. No Windows-specific tools or patterns are used, and Linux is referenced in node image upgrade guidance.

Recommendations

Clarify that Azure PowerShell is primarily for Windows users, and Azure CLI is recommended for cross-platform (Linux/macOS/Windows) environments.
Consider adding a note at the top indicating that Azure CLI is the preferred tool for Linux/macOS users.
Ensure that Azure CLI examples are always presented first, as is currently done.
Optionally, provide bash/zsh shell script examples for common tasks to further assist Linux/macOS users.

Create Pull Request

Aks Concepts - Storage in Azure Kubernetes Services (AKS) ...re-aks-docs/blob/main/articles/aks/concepts-storage.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_example_present ⚠️ windows_first

Summary

The documentation is largely platform-neutral and focuses on AKS storage concepts applicable to both Linux and Windows node pools. However, in the 'Persistent volume claims' section, Windows container volume mounting is mentioned after the Linux example, but only briefly. The Windows example is provided, but Linux is implicitly the default throughout. There are no PowerShell or Windows-specific tooling examples, and no critical storage concepts are presented as Windows-only unless explicitly noted (e.g., file system incompatibility).

Recommendations

Ensure parity in example depth: The Windows container volume mount example is brief and lacks context compared to the Linux example. Consider expanding the Windows example to include a full pod manifest, and clarify any Windows-specific requirements or limitations.
Explicitly state Linux/Windows applicability: Where storage classes, volume types, or CSI drivers differ between Linux and Windows, add notes or links to platform-specific documentation.
Balance example ordering: If both Linux and Windows examples are provided, alternate their order or present them side-by-side to avoid implicit platform prioritization.
Add troubleshooting or caveats for Windows: If there are known issues or limitations for Windows containers (e.g., file system support, volume sharing), highlight them with actionable guidance.

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 includes PowerShell (a Windows-centric tool) alongside CLI. The PowerShell examples are given equal prominence, and in some sections, PowerShell is mentioned before Linux-native alternatives. However, all critical steps (including Helm, kubectl, git, and bash commands) are cross-platform, and the Azure CLI is fully supported on Linux/macOS. No Windows-only tools or patterns are used for Kubernetes/Helm operations.

Recommendations

Consider clarifying that Azure PowerShell is primarily for Windows users, while Azure CLI is cross-platform.
Explicitly note that Azure CLI commands work on Linux/macOS and Windows, and that PowerShell is optional.
Where possible, show Azure CLI as the default or primary example, with PowerShell as an alternative for Windows users.
Add a brief section or note about using Azure CLI in Bash or Zsh shells on Linux/macOS.
Ensure that Linux/macOS users are not confused by PowerShell references; link to Azure CLI installation instructions for their platforms.

Create Pull Request

Live Progress

Scan Information

Problematic Pages