Scan Details - Linux-first Docs for Azure

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 both Windows/macOS and Linux instructions. However, in several sections, Windows/macOS solutions (e.g., launching Docker Desktop) are mentioned before Linux equivalents, and Windows-specific tools like Docker Desktop are referenced. Linux instructions are present and generally complete, but Windows/macOS steps are often listed first, which may create minor friction for Linux users.

Recommendations

Present Linux instructions before or alongside Windows/macOS steps, especially in Docker troubleshooting sections.
Explicitly mention parity between platforms where applicable (e.g., clarify that Docker Desktop is not available on Linux and provide alternative Linux-specific troubleshooting tips).
Ensure that all CLI examples (az, kubectl) are platform-neutral and clarify any OS-specific prerequisites.
Consider grouping troubleshooting steps by OS, or using tabs to allow users to select their platform.

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: 1 bias type

Detected Bias Types

⚠️ windows_first

Summary

The documentation is generally neutral and covers storage concepts for AKS without favoring Windows-specific tools or patterns. However, in the section on mounting volumes in pods, Windows container examples are presented immediately after Linux-style examples, with a brief note on specifying drive letters and paths for Windows. There are no PowerShell-heavy examples, Windows tools, or missing Linux examples. The only minor bias is that Windows mounting syntax is shown directly after the Linux example, but this is not significant.

Recommendations

Ensure that Linux/macOS examples are always presented first unless the section is explicitly Windows-specific.
Consider clarifying in the mounting section that the Linux-style path is the default for most AKS clusters, and Windows mounting is only relevant for Windows node pools.
Add a brief note or link to documentation about Linux/macOS volume mounting for completeness, if not already present.

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 is a Linux-first service, but there is minor evidence of Windows bias. In the section 'Verify TLS Bootstrapping is enabled on current agent node pool', the Windows file path is mentioned alongside the Linux path, but the Linux path is listed first. However, in the example output for certificate signing requests (CSRs), Windows node names (e.g., 'akswinp7000000') are used, but there is no explicit Linux node example. All command-line examples use Azure CLI and bash, which are cross-platform, but the documentation does not provide PowerShell or Windows-specific CLI examples, nor does it mention Windows tools preferentially.

Recommendations

Add explicit Linux node examples in output sections, especially where Windows node names are shown.
Ensure that when referencing file paths or node names, both Linux and Windows examples are provided for parity.
Consider adding notes or examples for Windows users where relevant, such as PowerShell equivalents for Azure CLI commands, if applicable.

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 in some places before Linux equivalents, and Azure CLI examples (which are cross-platform but often associated with Windows environments) are used exclusively for Azure resource creation. The documentation does not provide explicit Linux shell alternatives for Azure resource setup, but all Kubernetes examples and mount options are Linux-centric by default, with Windows-specific notes added where relevant.

Recommendations

Where Windows path conventions are mentioned, ensure Linux path conventions are equally prominent and shown first if the majority of AKS users are on Linux.
For Azure resource creation, clarify that Azure CLI is cross-platform and works on Linux/macOS as well as Windows.
When showing commands that differ between platforms (e.g., file paths, kubectl exec syntax), provide both Linux and Windows variants side by side.
Consider adding a brief section or note about using Azure CLI on Linux/macOS, including installation links.
Review the order of examples and notes to ensure Linux is not consistently secondary to Windows.

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. While the PowerShell section is prominent and detailed, it does include instructions for installing/upgrading PowerShell on macOS and Linux. However, PowerShell is a Windows-centric tool, and its section appears before the Azure CLI, which is more native to Linux/macOS users. 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 examples before PowerShell examples, as CLI is more universal across platforms.
Explicitly note that Azure CLI is recommended for Linux/macOS users, while PowerShell is an option for those who prefer it.
Ensure that all PowerShell instructions referencing local installation or usage clearly indicate cross-platform support.
Add brief notes or links about running Azure CLI in Cloud Shell for Linux/macOS users.

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 references Azure PowerShell as a tool for moving resources, alongside Azure CLI and Azure Portal. Azure PowerShell is a Windows-centric tool, and its mention is placed before Azure CLI in the list of migration options. However, all command-line examples provided use Azure CLI and Bash, which are cross-platform and Linux-friendly. No PowerShell-specific commands or Windows-only instructions are present.

Recommendations

List Azure CLI before Azure PowerShell in migration tool options, as Azure CLI is more universally supported across platforms.
Clarify that Azure PowerShell is available on Linux/macOS as well, or link to cross-platform installation instructions.
Consider removing Azure PowerShell from the main flow unless a PowerShell-specific example is provided, or add equivalent Linux/macOS instructions if PowerShell is used.
Explicitly state that all provided CLI examples work on Linux, macOS, and Windows.

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

⚠️ missing_linux_example ⚠️ windows_tools

Summary

The documentation is generally cross-platform, using Azure CLI and Bicep (both cross-platform tools) for all installation and management steps. However, in the 'List the CRDs in your cluster' section, the example uses 'kubectl get crds | findstr dapr.io', which relies on the Windows-specific 'findstr' command. No Linux/macOS equivalent (e.g., using 'grep') is provided. This is a minor bias, as most of the guide is platform-agnostic, but this step could cause confusion or friction for Linux/macOS users.

Recommendations

Provide both Windows and Linux/macOS examples for shell commands involving OS-specific utilities. For example, add 'kubectl get crds | grep dapr.io' alongside the existing 'findstr' example.
Where possible, prefer cross-platform commands or explicitly note platform differences.
Review for other minor shell command examples that may assume a Windows environment and ensure parity.

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-specific alternatives. Azure PowerShell is mentioned as a tool for cluster creation before the Azure portal, and PowerShell cmdlets are referenced for subnet listing. However, all actual walkthroughs and examples use kubectl and Azure CLI, which are cross-platform. No critical steps are Windows-only, but minor bias exists in tool mentions.

Recommendations

Clarify that Azure PowerShell is Windows-centric and recommend Azure CLI as the primary cross-platform tool.
List Azure CLI before Azure PowerShell in prerequisite sections.
Where PowerShell cmdlets are mentioned, provide equivalent Azure CLI commands or note that Azure CLI is preferred for Linux/macOS users.
Explicitly state that all kubectl and Azure CLI commands work on Linux/macOS/Windows.
Consider removing PowerShell references from sections not requiring Windows-specific functionality.

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 API server authorized IP ranges, but the PowerShell section is given equal prominence and appears directly after the CLI example. There are no Linux/macOS-specific examples or explicit mentions of Linux tools (e.g., bash, curl) for retrieving the public IP address. The CLI example uses 'dig', which is available on Linux/macOS but not by default on Windows, while the PowerShell example is Windows-specific. However, the overall workflow is portal-centric and platform-agnostic, and the YAML deployment targets Linux node pools.

Recommendations

Add a bash/curl example for retrieving the public IP address for Linux/macOS users (e.g., `curl ifconfig.me` or `curl ipinfo.io/ip`).
Clarify that Azure CLI commands can be run on any OS, and that 'dig' may need to be installed on Windows.
Consider mentioning that Cloud Shell is platform-agnostic and available from the portal for all users.
Explicitly state that both Azure CLI and PowerShell are cross-platform, but PowerShell is most commonly used on Windows.

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 both Linux and Windows examples for AKS network policy setup, but Windows-specific instructions (such as registering preview features and creating Windows 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 there are Windows-specific steps and terminology (e.g., HNS ACLPolicies) discussed before Linux equivalents. However, Linux parity is generally maintained, and most examples are cross-platform.

Recommendations

Ensure Linux and Windows instructions are presented in parallel, with clear separation and equal prominence.
When discussing tools or concepts (e.g., IPTables vs. HNS ACLPolicies), provide Linux explanations first or side-by-side.
Where possible, clarify which steps are platform-neutral and which are platform-specific.
Add explicit notes or callouts to help Linux/macOS users skip Windows-only steps.
Consider adding a table or section summarizing differences and steps for each OS, rather than interleaving them.

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 parallel Azure CLI and Azure PowerShell instructions throughout, but PowerShell is featured equally and sometimes referenced first. There is no explicit Windows bias in the examples themselves, as Azure CLI is cross-platform and bash commands are used for Helm and kubectl. However, the presence of Azure PowerShell instructions may create friction for Linux/macOS users, as PowerShell is less commonly used on those platforms. There are no missing Linux examples, and Windows-specific tools or patterns are not mentioned exclusively.

Recommendations

Clarify that Azure CLI is recommended for Linux/macOS users, and PowerShell is optional or primarily for Windows users.
Consider presenting Azure CLI instructions before PowerShell instructions, as CLI is more universally supported.
Add a note indicating that Azure PowerShell is available cross-platform, but CLI is the default for Linux/macOS.
Ensure that bash commands (helm, kubectl, git) are shown as the primary workflow for Linux/macOS users.
Optionally, provide a table or section summarizing which tools are best suited for each OS.

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 examples for Azure CLI, Azure PowerShell, and Azure Developer CLI throughout, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI. There are no explicit Linux/macOS examples (e.g., Bash shell, native package managers), and PowerShell is presented as a primary option, which may create friction for Linux/macOS users. However, Azure CLI is cross-platform and is shown first in most sections, mitigating the bias. No critical steps are Windows-only, and Linux/macOS users can complete the tutorial using Azure CLI.

Recommendations

Clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
Add explicit Bash shell examples or mention native installation methods for kubectl on Linux/macOS (e.g., apt, yum, Homebrew).
De-emphasize PowerShell for non-Windows users, or add notes indicating PowerShell is primarily for Windows.
Consider adding a section or callout for Linux/macOS users to highlight relevant tools and commands.

Create Pull Request

Live Progress

Scan Information

Problematic Pages