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

⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation provides parallel Azure CLI and Azure PowerShell instructions throughout, but does not show explicit Linux/macOS shell examples for Azure CLI usage. Azure PowerShell is featured equally alongside Azure CLI, despite PowerShell being primarily a Windows-centric tool (though available cross-platform). Azure CLI examples are not explicitly shown as Bash or Linux/macOS shell commands, and PowerShell is given equal prominence, which may create friction for Linux/macOS users who typically use Bash and Azure CLI.

Recommendations

Clarify that Azure CLI examples are intended for Bash (Linux/macOS) and Windows Command Prompt users.
Add explicit Bash shell examples for Azure CLI commands, including any relevant environment variable usage or command syntax differences for Linux/macOS.
Consider reducing the prominence of Azure PowerShell unless there are Windows-specific tasks, or move PowerShell instructions to a secondary section or appendix.
Add notes about cross-platform compatibility for Azure CLI and Helm commands, and highlight any OS-specific prerequisites or installation steps.
Ensure that all instructions (especially for Helm, kubectl, git, etc.) are shown in a way that is clear for Linux/macOS users, including references to package managers (apt, yum, brew) for installation.

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, covering both Windows and Linux environments. However, the PowerShell section is notably detailed, with explicit instructions for Windows, macOS, and Linux installation and upgrade, and PowerShell is presented before Azure CLI. This ordering and emphasis may create a perception of Windows/PowerShell bias, though Linux users are not blocked from completing the task.

Recommendations

Present Azure CLI examples before PowerShell, as CLI is more universally used across platforms.
Add explicit notes clarifying that Azure CLI works natively on Linux/macOS and is often preferred for cross-platform scripting.
Balance the detail level between PowerShell and CLI sections, ensuring Linux/macOS users have equally comprehensive guidance.
Consider adding Bash shell examples or highlighting CLI usage in Linux environments.

Create Pull Request

Aks Move Azure Disk persistent volumes to another AKS cluster in the same or a different subscription .../blob/main/articles/aks/csi-disk-move-subscriptions.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_tools ⚠️ windows_first

Summary

The documentation mentions Azure PowerShell as a tool for moving resources, alongside Azure CLI and the Azure portal. Azure CLI is used for all command-line examples, which are cross-platform, but Azure PowerShell is listed before Azure CLI in the section describing migration options. No PowerShell-specific examples are provided, and all YAML and kubectl examples are Linux-oriented. There are no missing Linux examples, but the mention of Azure PowerShell and its placement could create minor friction for Linux/macOS users.

Recommendations

List Azure CLI before Azure PowerShell when describing migration options, as Azure CLI is cross-platform and more widely used in Linux/macOS environments.
Clarify that Azure PowerShell is primarily for Windows users, and recommend Azure CLI for Linux/macOS users.
Optionally, provide a brief note that all command-line examples use Azure CLI, which works on Windows, Linux, and macOS.
Ensure that any future PowerShell examples are accompanied by equivalent Azure CLI examples.

Create Pull Request

Aks Configure LocalDNS in Azure Kubernetes Service (AKS) ...ure-aks-docs/blob/main/articles/aks/localdns-custom.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 1 bias type

Detected Bias Types

⚠️ windows_first

Summary

The documentation provides links for creating an AKS cluster using Azure CLI, Azure PowerShell, and the Azure portal, with PowerShell mentioned alongside CLI and portal. However, all configuration, verification, and troubleshooting examples use cross-platform tools (Azure CLI and kubectl), and the feature itself is explicitly Linux-only (supported only on Azure Linux or Ubuntu 22.04+ node pools). There are no Windows-specific commands, tools, or patterns used in the main instructions. The only minor bias is mentioning PowerShell as an option for cluster creation, but this does not impact Linux/macOS users.

Recommendations

Consider listing Azure CLI and Azure portal first, as they are fully cross-platform, and clarify that Azure PowerShell is primarily for Windows users.
Explicitly state that all configuration and management steps are cross-platform and can be performed from Linux, macOS, or Windows.
If possible, provide a note that Azure PowerShell is not required for Linux users, and that Azure CLI is the recommended tool.

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

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools

Summary

The documentation provides parity for both Linux and Windows node pools in AKS, but there is a slight bias toward Windows in some sections. Windows-specific instructions (such as registering feature flags and creating admin credentials) are given their own section and are detailed before Linux equivalents in some places. The use of Azure CLI is platform-neutral, but Windows-specific tools and patterns (feature flag registration, admin credential setup) are highlighted. Linux examples are present and complete, but Windows instructions are sometimes more verbose and prominent.

Recommendations

Ensure Linux and Windows instructions are presented in parallel sections, with equal prominence and detail.
Where possible, provide Linux-specific notes or examples alongside Windows-specific steps (e.g., admin credential creation).
Avoid presenting Windows-specific steps before Linux unless required by technical order.
Clarify which steps are platform-neutral and which are platform-specific.
Consider adding a summary table or section that clearly delineates Linux vs Windows steps for cluster creation and management.

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 parity for Linux, macOS, and Windows users in most sections, especially regarding Docker and Kubernetes commands. However, in the 'Verify Docker installation and start Docker daemon' section, instructions for starting Docker are presented as 'macOS/Windows' first, followed by Linux. This is a minor ordering bias, but all platforms are covered. No PowerShell-specific commands, Windows-only tools, or missing Linux examples are found.

Recommendations

When listing platform-specific instructions, alternate the order or explicitly state that instructions apply equally to Linux, macOS, and Windows.
Consider grouping instructions by platform or using tabs for clarity.
Ensure that Linux instructions are not consistently listed after Windows/macOS instructions to avoid perceived bias.

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

Detected Bias Types

⚠️ windows_first ⚠️ windows_tools

Summary

The documentation provides troubleshooting steps for the agentic CLI for AKS, with Docker-related solutions often mentioning Windows/macOS tools (Docker Desktop) before Linux equivalents. Windows/macOS instructions are listed first in several sections, and Docker Desktop is referenced as the primary tool for Windows/macOS users, while Linux instructions rely on systemd and command-line utilities. However, Linux-specific guidance is present and generally complete, and most examples are cross-platform.

Recommendations

Alternate the order of platform instructions (e.g., list Linux first in some sections).
Explicitly mention that Docker Desktop is not available on Linux and clarify the Linux workflow.
Provide parity in troubleshooting steps, ensuring Linux/macOS/Windows are equally covered.
Consider grouping platform-specific instructions under clear headings for each OS.
Add notes about platform differences where relevant (e.g., Docker Desktop vs. systemd).

Create Pull Request

Aks Connect your Azure Kubernetes Service (AKS) cluster to AI agents using the Model Context Protocol (MCP) server ...main/articles/aks/aks-model-context-protocol-server.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ missing_linux_example

Summary

The documentation provides a generally cross-platform approach, with explicit download links and instructions for Windows, macOS, and Linux. However, in several sections (especially VS Code instructions), Windows keyboard shortcuts are mentioned first, and Linux-specific troubleshooting or configuration details are less prominent. The Docker section includes Linux-specific user guidance, but overall, Linux examples and tips are less detailed compared to Windows. There are no PowerShell-only examples or Windows-exclusive tools, but Linux users may find minor friction due to the ordering and lack of explicit Linux-focused troubleshooting.

Recommendations

Ensure Linux keyboard shortcuts and configuration steps are given equal prominence to Windows (e.g., list Linux shortcuts first or side-by-side).
Add explicit Linux troubleshooting tips (e.g., common permission issues, file path conventions, user/group mapping for Docker containers).
Include more Linux-specific example commands and configuration scenarios, especially for Docker and manual binary installation.
Consider a dedicated Linux/macOS section for common issues, as is done for Windows/WSL.
Review all download and install instructions to ensure Linux users are not required to infer steps from Windows-centric guidance.

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 ⚠️ windows_tools

Summary

The documentation provides both Linux and Windows file paths when verifying TLS Bootstrapping, but Linux paths are mentioned first. All command examples use cross-platform tools (Azure CLI, kubectl, curl, openssl), and there are no PowerShell or Windows-specific command examples. However, Windows file paths are mentioned in the context of node access, and Azure CLI is used throughout, which is available on both platforms. There is a minor mention of Windows nodes in example output, but no Windows-only tools or patterns are prioritized.

Recommendations

Ensure all file path examples for both Linux and Windows nodes are equally explained and contextualized.
If Windows-specific commands or PowerShell are needed, provide equivalent Linux/bash examples.
Clarify that Azure CLI and kubectl commands are cross-platform and provide links to installation instructions for both Windows and Linux.
If referencing Windows file paths, briefly explain how to access them (e.g., via RDP or Azure Serial Console) for parity with Linux SSH instructions.

Create Pull Request

Aks Create and Manage Persistent Volumes with Azure Files in Azure Kubernetes Service (AKS) ...cs/blob/main/articles/aks/create-volume-azure-files.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ windows_tools

Summary

The documentation is generally cross-platform, focusing on Kubernetes and Azure Files usage for both Linux and Windows containers. However, there are minor signs of Windows bias: Windows path conventions and PowerShell/CMD syntax are mentioned before Linux equivalents in some places, and Windows-specific notes are sometimes presented first. Azure CLI and kubectl are used throughout, which are cross-platform tools, but Windows path examples and references to Windows conventions appear before Linux in some sections.

Recommendations

When providing examples for Windows and Linux/macOS, alternate which platform is shown first or present both together.
Ensure Linux/macOS path conventions and shell syntax are always included alongside Windows examples.
Where Windows-specific notes are given, add equivalent Linux/macOS notes if applicable.
Review output examples to ensure they are not only Windows-centric (e.g., path formats, command syntax).

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

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first

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/PowerShell example is provided (`kubectl get crds | findstr dapr.io`), and no Linux/macOS equivalent (e.g., using `grep`) is shown. Additionally, the use of PowerShell syntax for variable assignment in the Bicep section (`MY_RESOURCE_GROUP=<your-resource-group>`) could be confusing, but it is actually Bash syntax, so this is not a bias. The rest of the documentation uses Azure CLI commands, which are cross-platform, and does not mention Windows tools or patterns exclusively.

Recommendations

Add a Linux/macOS example for listing CRDs, such as `kubectl get crds | grep dapr.io`.
Where possible, show both Windows and Linux/macOS command variants side-by-side, especially for shell commands.
Clarify that Azure CLI and Bicep are cross-platform and can be used on any OS.

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 cluster creation and subnet listing, but references to PowerShell (Get-AzVirtualNetworkSubnetConfig) are given alongside Azure CLI without Linux equivalents. The 'Before you begin' section lists Azure CLI, PowerShell, and Portal, but Azure CLI is mentioned first. All main walkthroughs use kubectl and Azure CLI, which are cross-platform, but PowerShell is referenced as an alternative tool without mentioning Bash or Linux-native scripting. There are no Linux-specific examples or explicit parity notes.

Recommendations

Where PowerShell is referenced, also mention Bash or Linux-native alternatives (e.g., az CLI in Bash, or shell scripting).
Clarify that Azure CLI commands work on Linux/macOS and Windows equally.
Consider providing Linux/macOS-specific guidance or examples where scripting or environment setup is discussed.
If referencing PowerShell, note its availability on Linux/macOS, or provide Bash equivalents.
In prerequisite lists, avoid listing PowerShell before cross-platform tools unless the feature is Windows-only.

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 managing AKS authorized IP ranges, but the PowerShell section is presented immediately after the CLI section and is equally prominent. There are no Linux/macOS-specific examples or explicit mentions of Linux tools or shell patterns (e.g., bash, curl), and the CLI example uses 'dig', which is available on Linux/macOS but not natively on Windows. However, the overall guidance is platform-neutral, focusing on portal-based workflows and Azure CLI/PowerShell, which are cross-platform tools. Minor bias is present in the troubleshooting section where PowerShell is given equal prominence, but no Linux/macOS-specific troubleshooting or shell examples are provided.

Recommendations

Explicitly mention that Azure CLI commands are cross-platform and can be run on Linux, macOS, and Windows.
Add bash-specific or Linux/macOS shell examples for retrieving the public IP address (e.g., using 'curl' or 'wget'), since 'dig' may not be installed by default.
Clarify that Azure PowerShell is available on all platforms, but provide guidance for Linux/macOS users who may prefer bash or zsh.
Consider providing a simple bash command for IP retrieval, such as 'curl ifconfig.me', alongside the 'dig' example.
Ensure troubleshooting steps reference Linux/macOS environments where relevant, especially for network connectivity and IP retrieval.

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 as a primary option alongside Azure CLI, which is more commonly used on Linux/macOS, and PowerShell is typically associated with Windows environments. The examples and instructions for PowerShell are given equal prominence, potentially implying Windows as a first-class platform. There are no explicit Linux/macOS-specific examples or notes, but the Azure CLI instructions are cross-platform and the use of Bash/Cloud Shell is mentioned. No critical steps are Windows-only, and Linux/macOS users can complete the tutorial without friction.

Recommendations

Clarify that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
Add explicit notes or examples for Linux/macOS users, such as using Bash or Zsh shells.
Mention that PowerShell Core is available on Linux/macOS, but Azure PowerShell is most commonly used on Windows.
Consider listing Azure CLI instructions first, as it is the default for cross-platform usage.
Add a brief section or callout for Linux/macOS users, confirming that all steps are supported and providing any shell-specific tips.

Create Pull Request

Live Progress

Scan Information

Problematic Pages