← Back to Dashboard
112
Pages Scanned
11
Pages Flagged
112
Changed Pages
9.8%
% Pages Flagged

Live Progress

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

Scan Information

Started At: 2026-02-13 00:00:08

Finished At: In Progress

Status: in_progress

Target Repo: Azure Aks

Current Phase: discovery

Files Queued: 112

Files Completed: 112

Problematic Pages

11 issues found
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 three main approaches: Azure portal, Azure PowerShell, and Azure CLI. Azure PowerShell is featured prominently, with detailed instructions and prerequisites, including references to Windows, macOS, and Linux installation. However, PowerShell is a Windows-centric tool, and its section appears before the Azure CLI, which is more cross-platform and native to Linux/macOS. The PowerShell section is more verbose and detailed compared to the CLI section. There are no missing Linux examples, as Azure CLI is included, but the ordering and emphasis favor Windows/PowerShell.
Recommendations
  • Present Azure CLI instructions before Azure PowerShell, as CLI is more universally supported across platforms.
  • Ensure parity in detail between PowerShell and CLI sections; expand CLI instructions if needed.
  • Explicitly mention that Azure CLI is recommended for Linux/macOS users.
  • Consider adding a note clarifying that PowerShell is available on Linux/macOS, but Azure CLI is the default for those platforms.
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 AKS cluster creation guides for Azure CLI, PowerShell, and Portal, with PowerShell (a Windows-centric tool) mentioned alongside CLI and Portal. However, all actual configuration, verification, and troubleshooting examples use Azure CLI and kubectl, which are cross-platform tools. There are no PowerShell-specific commands or Windows-only tools used in the main instructions. The documentation explicitly states LocalDNS is only supported on Azure Linux or Ubuntu node pools, not Windows, and does not present Windows-specific patterns or tools.
Recommendations
  • When referencing AKS creation guides, list Azure CLI and Portal before PowerShell, or clarify PowerShell is Windows-specific.
  • Consider adding a note that Azure CLI and kubectl are fully supported on Linux/macOS, and that PowerShell is optional for Windows users.
  • Ensure all example commands are cross-platform (which they currently are).
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: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation provides troubleshooting steps for the agentic CLI for AKS and generally includes both Windows/macOS and Linux instructions. However, in the Docker daemon troubleshooting section, Windows/macOS steps are listed before Linux steps, which is a minor 'windows_first' bias. All other examples and solutions are cross-platform or Linux-first, and Linux-specific issues (such as Docker permissions) are addressed directly.
Recommendations
  • Present Linux and Windows/macOS instructions in parallel or in the same order throughout the documentation.
  • Consider using tabs or clear section headers to distinguish platform-specific instructions, ensuring equal visibility.
  • Review other sections for ordering and ensure Linux instructions are not consistently placed after Windows/macOS instructions.
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 is generally cross-platform and Linux-centric, but there are minor instances of Windows bias. In the 'Verify TLS Bootstrapping is enabled on current agent node pool' section, the Windows file path ('C:\k\bootstrap-config') is mentioned after the Linux path, which is good, but no Windows-specific command examples are provided. Most examples use bash, Azure CLI, and kubectl, which are standard for Linux/macOS. However, there are no PowerShell or Windows command-line examples for Windows users, and the documentation assumes Linux as the default for node access and certificate checks.
Recommendations
  • Add Windows-specific command examples (e.g., PowerShell or Command Prompt) for checking certificate expiration and accessing node files.
  • Clarify in sections where file paths differ between Linux and Windows, and provide explicit instructions for Windows users.
  • Ensure parity by including Windows node pool scenarios where relevant, or explicitly state if steps are Linux-only.
  • Consider adding a note about using Azure CLI and kubectl on Windows, including any prerequisites or differences.
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: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation page provides installation and usage instructions for the Agentic CLI for AKS, with a focus on Azure CLI commands. While most examples are cross-platform (Azure CLI and bash), there is a subtle Windows bias in the ordering and presentation of Docker daemon startup instructions: Windows/macOS (Docker Desktop) are mentioned before Linux (systemctl), and Linux instructions are less detailed. Additionally, some verification steps (e.g., checking config file removal) use bash commands without explicit Windows equivalents, and there are no PowerShell examples for Windows users. However, the overall impact is minor, as the Azure CLI and Docker are cross-platform, and Linux/macOS users can follow the instructions with minimal friction.
Recommendations
  • Present Linux instructions for Docker daemon startup before or alongside Windows/macOS instructions, and provide more detail for Linux users.
  • Include PowerShell equivalents for bash commands where relevant (e.g., checking file removal, listing Docker images) to improve parity for Windows users.
  • Explicitly mention that Azure CLI commands are cross-platform and provide links to platform-specific installation guides.
  • Add troubleshooting notes for common Linux/macOS issues (e.g., Docker daemon permissions, systemctl failures).
GitHub Create Pull Request
Aks Azure Kubernetes Service (AKS) Managed Gateway API Installation ...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 and kubectl examples, which are cross-platform. However, all CLI examples are shown using Azure CLI (az), which is available on Windows, Linux, and macOS, but the documentation does not mention Linux/macOS-specific considerations or alternative commands. There is a minor bias in that Windows is implicitly assumed as the default environment, as no Linux/macOS shell-specific notes or troubleshooting are provided.
Recommendations
  • Explicitly state that Azure CLI and kubectl commands work on Windows, Linux, and macOS.
  • Add notes about installing Azure CLI and kubectl on Linux/macOS, including links to official installation guides.
  • Mention any potential differences in environment variables, shell syntax, or command output between platforms.
  • If relevant, provide troubleshooting tips for Linux/macOS users (e.g., permissions, PATH issues).
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: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation is largely cross-platform, focusing on Azure CLI and Bicep for Dapr extension management on AKS and Arc-enabled Kubernetes. However, there is a minor Windows bias in the CRD deletion section, where the example for listing CRDs uses PowerShell's 'findstr' command with 'kubectl', which is Windows-specific. Additionally, this example is given without a Linux/macOS equivalent, and the PowerShell usage appears before any mention of Linux tools.
Recommendations
  • Provide Linux/macOS equivalents for the CRD listing command, such as 'kubectl get crds | grep dapr.io'.
  • When giving shell command examples, show both Windows (PowerShell) and Linux/macOS (bash) versions side-by-side or indicate which platforms they apply to.
  • Consider using platform-neutral commands or note platform-specific differences where relevant.
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 steps, but consistently mentions Azure PowerShell alongside Azure CLI and portal, and links to PowerShell-specific resources. In the section about listing subnets, both Azure CLI and PowerShell are referenced, but PowerShell is mentioned second. There are no PowerShell-specific examples in the main workflow, and all command-line examples use Azure CLI or kubectl, which are cross-platform. However, the presence of PowerShell links and references may create minor friction for Linux/macOS users.
Recommendations
  • Where PowerShell is referenced, ensure equivalent Bash or cross-platform CLI options are always provided and shown first.
  • Clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Consider removing PowerShell references from main instructions unless a feature is PowerShell-only.
  • Add explicit notes or links for Linux/macOS users where PowerShell is mentioned, pointing to Azure CLI alternatives.
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 updating AKS API server authorized IP ranges, but consistently presents Azure CLI (Linux/macOS-friendly) instructions first, followed by Azure PowerShell (Windows-centric) instructions. No Windows-specific tools or patterns are mentioned exclusively, and all examples are cross-platform. However, the PowerShell section is present, which may be unnecessary for Linux/macOS users, but parity is maintained. There are no missing Linux examples, and the YAML deployment targets Linux node pools.
Recommendations
  • Clarify that Azure CLI commands are cross-platform and preferred for Linux/macOS users.
  • Consider explicitly stating that Azure PowerShell is primarily for Windows users.
  • Add a brief note indicating that Azure CLI works on Windows, Linux, and macOS, while PowerShell is mainly Windows-focused.
  • Ensure that any screenshots or UI instructions do not reference Windows-specific behaviors.
  • If possible, provide Bash-only examples for Linux users, or highlight that Cloud Shell supports Bash and PowerShell.
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 operations, but consistently presents Azure CLI (which is cross-platform) before Azure PowerShell (which is Windows-centric). There are no Windows-only tools or commands, and all critical steps are achievable with Azure CLI, which works on Linux/macOS. Bash commands are used for Helm and kubectl, and no Windows-specific patterns or tools are mentioned. However, the presence of Azure PowerShell throughout and its parity with Azure CLI may create a slight perception of Windows bias.
Recommendations
  • Consider clarifying that Azure PowerShell is primarily for Windows users and Azure CLI is cross-platform.
  • Optionally, add a note at the start of the PowerShell sections indicating that Linux/macOS users should use Azure CLI.
  • Ensure that bash commands and cross-platform tools (Helm, kubectl) are always shown and not replaced by Windows-specific alternatives.
  • If possible, add explicit Linux/macOS instructions for installing Azure CLI, Helm, and kubectl (linking to their install docs).
GitHub 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, Azure PowerShell (which is Windows-centric) is given equal prominence to Azure CLI, and is sometimes mentioned before Linux-native tools. There are no missing Linux examples, but the presence of PowerShell examples and references may create minor friction for Linux/macOS users, as PowerShell is less commonly used on those platforms.
Recommendations
  • Consider listing Azure CLI examples first in each section, as it is the most cross-platform and widely used tool.
  • Explicitly note that Azure PowerShell is available on Linux/macOS, but Azure CLI is recommended for those platforms.
  • Add brief guidance for Linux/macOS users, clarifying that Azure CLI is the preferred tool and that all examples are fully supported on those platforms.
  • If possible, reduce the prominence of PowerShell in cross-platform tutorials, or move PowerShell examples to a secondary position.
GitHub Create Pull Request