← Back to Dashboard
119
Pages Scanned
11
Pages Flagged
119
Changed Pages
9.2%
% Pages Flagged

Live Progress

🔴 Connecting...
100%
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:06 Scan started

Scan Information

Started At: 2026-02-18 00:00:06

Finished At: In Progress

Status: in_progress

Target Repo: Azure Aks

Current Phase: discovery

Files Queued: 119

Files Completed: 119

Problematic Pages

11 issues found
Aks About the Agentic CLI for Azure Kubernetes Service (AKS) ...s/blob/main/articles/aks/cli-agent-for-aks-overview.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation describes the Agentic CLI for AKS in a platform-neutral manner but subtly exhibits Windows bias by referencing 'local Azure CLI credentials' and 'Docker' without clarifying Linux/macOS support. There are no explicit Linux/macOS examples or instructions, and prerequisites are listed generically (e.g., 'Docker'), which may imply Windows as the default environment. The absence of Linux/macOS-specific guidance or troubleshooting creates friction for non-Windows users.
Recommendations
  • Explicitly state that the Agentic CLI for AKS supports Windows, Linux, and macOS platforms.
  • Provide installation and usage examples for Linux and macOS, including any platform-specific prerequisites or troubleshooting tips.
  • Clarify that Docker and Azure CLI are cross-platform tools, and link to their Linux/macOS installation guides.
  • Add a section or table highlighting any differences or considerations for Linux/macOS users.
GitHub 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: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation provides both Windows/macOS and Linux instructions for Docker daemon startup, but presents Windows/macOS steps first. All CLI examples use Azure CLI, which is cross-platform, and shell commands are shown in Bash, suitable for Linux/macOS. No PowerShell or Windows-specific tools are referenced, and Linux parity is generally maintained.
Recommendations
  • Present Linux instructions before Windows/macOS in Docker daemon startup steps, or group them equally.
  • Explicitly mention that all Azure CLI commands work on Linux, macOS, and Windows.
  • Consider adding a note that Bash commands are applicable to Linux/macOS, and Windows users may use WSL or Docker Desktop terminal.
GitHub 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 PowerShell examples are presented immediately after CLI and are given equal prominence. There is no explicit Linux/macOS bias, but the PowerShell section may be unnecessary for Linux/macOS users. The rest of the documentation is portal-centric and platform-agnostic, with all YAML examples targeting Linux node pools. No Windows-specific tools or patterns are mentioned outside the PowerShell section.
Recommendations
  • Clearly indicate that Azure PowerShell examples are for Windows users, and Azure CLI examples are cross-platform.
  • Consider presenting Azure CLI examples first, and PowerShell examples in a separate, clearly labeled section for Windows users.
  • Add a note clarifying that Azure CLI commands work on Linux, macOS, and Windows, while PowerShell is Windows-centric.
  • If possible, provide Bash alternatives for retrieving the public IP address, or clarify that the CLI example works on Linux/macOS.
GitHub Create Pull Request
Aks Supported Kubernetes Versions in Azure Kubernetes Service (AKS) ...lob/main/articles/aks/supported-kubernetes-versions.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 key operations (such as installing kubectl and listing AKS versions), but consistently presents Azure CLI (cross-platform) examples first, followed by Azure PowerShell (Windows-centric) examples. No Linux-specific commands or tools are mentioned, but Azure CLI is inherently cross-platform. There are no Windows-only tools or patterns, and Linux is referenced equally in component tables. No critical tasks are Windows-only.
Recommendations
  • Explicitly mention that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Consider adding a brief note or example for Linux/macOS users (e.g., installation of Azure CLI or kubectl via package managers like apt, brew, or curl).
  • Where PowerShell is referenced, clarify its Windows focus and suggest Azure CLI for Linux/macOS.
  • Add links or references to Linux/macOS installation guides for Azure CLI and kubectl.
GitHub 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 both PowerShell and CLI are cross-platform, the PowerShell section is notably detailed and references Windows tools and patterns (such as PowerShell cmdlets and Cloud Shell), and is presented before the Azure CLI section. The PowerShell section includes explicit instructions for Windows, macOS, and Linux installation, but the CLI section is less prominent. There is a slight bias toward Windows/PowerShell usage, but Linux/macOS users can complete all tasks using Azure CLI or PowerShell.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is more universally used across platforms.
  • Expand Azure CLI instructions to match the detail provided in the PowerShell section, including environment setup and prerequisites for Linux/macOS.
  • Explicitly mention that both PowerShell and CLI are fully supported on Linux/macOS, and provide links to installation guides for each platform.
  • Consider adding Bash shell examples or highlighting CLI usage in Linux/macOS contexts.
GitHub 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 provides a single example of a Windows file path for verifying TLS Bootstrapping ('C:\k\bootstrap-config'), while the Linux equivalent is also mentioned but not shown first. All other examples and commands are either cross-platform (Azure CLI, kubectl, bash, curl) or explicitly reference Linux file paths. There are no PowerShell-specific commands, Windows tools, or Windows-only patterns used. The Windows path is mentioned after the Linux path, but no Linux-specific troubleshooting or parity notes are provided.
Recommendations
  • Ensure Linux and Windows examples are presented with equal prominence, ideally side-by-side or with clear parity.
  • Add explicit notes or troubleshooting steps for Linux users where file paths or behaviors may differ.
  • Where file paths are given, clarify any differences in permissions, access, or tooling between Linux and Windows nodes.
  • Consider adding a brief section on accessing Linux agent nodes for certificate checks, as is done for Windows nodes.
GitHub 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 and includes examples for Docker issues on macOS/Windows and Linux. Windows/macOS instructions are often mentioned before Linux, and Docker Desktop (a Windows/macOS tool) is referenced, but Linux-specific commands are also provided. Azure CLI and kubectl commands are platform-neutral, but there are no PowerShell-specific examples. However, some solutions (e.g., Docker Desktop restart) are Windows/macOS-centric, and Linux instructions are sometimes secondary. There are minor instances where Linux examples could be more prominent or detailed.
Recommendations
  • Present Linux instructions before or alongside Windows/macOS instructions, especially for Docker troubleshooting.
  • Clarify that Docker Desktop is not available on Linux and provide alternative Linux troubleshooting steps (e.g., checking systemd status, logs).
  • Ensure all troubleshooting steps have parity for Linux, including error messages and solutions.
  • Add explicit notes when steps differ between platforms, and avoid assuming Docker Desktop for Linux users.
  • Consider including macOS-specific commands where relevant, rather than grouping macOS and Windows together.
GitHub 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 consistently mentions Azure PowerShell alongside Azure CLI and portal, and references PowerShell cmdlets before or equally with CLI commands. There are no Linux/macOS-specific examples or notes, and the PowerShell tool is presented as a primary option for resource management, which may create friction for Linux/macOS users.
Recommendations
  • List Azure CLI examples and commands before PowerShell, as Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Clearly indicate that Azure PowerShell is Windows-centric and suggest Azure CLI as the default for cross-platform usage.
  • Where PowerShell cmdlets are referenced (e.g., Get-AzVirtualNetworkSubnetConfig), provide equivalent Azure CLI commands first and clarify their parity.
  • Consider removing or relegating PowerShell references to a separate section or note for Windows users.
  • Add explicit notes that all Azure CLI commands are supported on Linux/macOS, and highlight any differences if present.
GitHub 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 tasks, but consistently presents PowerShell as a first-class option alongside CLI. There are no explicit Linux/macOS-specific examples or notes, and PowerShell is featured equally throughout. However, the core workflow uses cross-platform tools (Azure CLI, Helm, kubectl, git), and bash commands are used for Helm and Kubernetes steps. The bias is minor, mainly in the parity of PowerShell and CLI, and the lack of explicit Linux/macOS guidance.
Recommendations
  • Clarify that Azure PowerShell is primarily for Windows users, and Azure CLI is cross-platform (Windows, Linux, macOS).
  • Add notes or guidance for Linux/macOS users, such as installation instructions for Azure CLI, Helm, and kubectl on those platforms.
  • Consider showing Azure CLI examples first, as CLI is the default and recommended tool for cross-platform usage.
  • Explicitly mention that PowerShell examples are for Windows users, and that Linux/macOS users should use Azure CLI.
  • Add troubleshooting tips for Linux/macOS users (e.g., file path differences, shell environment setup).
GitHub 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: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation is generally platform-agnostic, focusing on Azure CLI and Bicep for Dapr extension installation on AKS and Arc-enabled Kubernetes. However, in the section 'Listing the CRDs in your cluster', the example uses 'kubectl get crds | findstr dapr.io', which is a Windows/PowerShell command (findstr) and does not provide a Linux/macOS equivalent (such as grep). This is a minor Windows bias, as Linux/macOS users would need to adapt the command themselves.
Recommendations
  • Provide both Windows (findstr) and Linux/macOS (grep) examples for commands involving output filtering, e.g., 'kubectl get crds | grep dapr.io'.
  • Where possible, avoid using platform-specific tools in documentation, or clearly indicate alternatives for other platforms.
  • Consider adding a note or a table showing command variants for different operating systems.
GitHub 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 to Windows (Azure PowerShell) and Linux (Azure CLI) methods for AKS cluster creation, but the PowerShell link is listed before the Azure portal link, and Azure CLI is listed first. All command examples use Azure CLI and kubectl, which are cross-platform and not Windows-specific. No PowerShell or Windows-only tools are used in examples. The documentation explicitly states LocalDNS is only supported on Azure Linux or Ubuntu node pools, and there are no Windows-specific instructions or tools. The minor bias is limited to the order of quickstart links, where PowerShell is mentioned before the portal.
Recommendations
  • List Linux and cross-platform tools (Azure CLI, kubectl) before Windows-specific tools in prerequisite links.
  • Consider grouping quickstart links by platform or clarifying that Azure CLI and Azure PowerShell are both cross-platform.
  • Ensure parity in example commands for both Azure CLI and PowerShell if relevant, but in this case Azure CLI is sufficient since LocalDNS is Linux-only.
GitHub Create Pull Request