← Back to Dashboard
126
Pages Scanned
13
Pages Flagged
126
Changed Pages
10.3%
% Pages Flagged

Live Progress

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

Scan Information

Started At: 2026-02-21 00:00:11

Finished At: In Progress

Status: in_progress

Target Repo: Azure Aks

Current Phase: discovery

Files Queued: 126

Files Completed: 126

Problematic Pages

13 issues found
Aks About the Agentic CLI for Azure Kubernetes Service (AKS) ...blob/main/articles/aks/agentic-cli-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 for the Agentic CLI for AKS does not explicitly mention Windows, but it refers to 'local machine' usage and prerequisites such as Docker and Azure CLI without clarifying Linux/macOS compatibility or providing Linux/macOS-specific instructions. There are no examples or guidance for Linux/macOS users, and the phrasing may imply a Windows-centric perspective by default.
Recommendations
  • Explicitly state that the Agentic CLI for AKS supports Windows, Linux, and macOS platforms.
  • Provide installation and usage instructions for Linux/macOS, including any differences in Docker or Azure CLI setup.
  • Add troubleshooting tips for Linux/macOS environments (e.g., common issues with Docker on Linux, Azure CLI authentication differences).
  • Include example commands or screenshots from Linux/macOS terminals alongside Windows examples if applicable.
GitHub Create Pull Request
Aks Kubernetes on Azure tutorial - Create an Azure Kubernetes Service (AKS) cluster ...ain/articles/aks/tutorial-kubernetes-deploy-cluster.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 examples for Azure CLI, Azure PowerShell, and Azure Developer CLI, but PowerShell is featured prominently, and the use of PowerShell cmdlets (e.g., Install-AzAksCliTool, New-AzAksCluster, Import-AzAksCredential) may implicitly favor Windows users. Azure CLI examples are present, but PowerShell is given equal weight, which is uncommon for Linux/macOS users. There are no explicit Linux/macOS examples (e.g., Bash shell, native package installation for kubectl), and PowerShell is mentioned before Linux-native tools in several places.
Recommendations
  • Add explicit Bash/Linux/macOS instructions for installing kubectl (e.g., using curl or package managers like apt, brew, yum).
  • Clarify that Azure CLI commands work on Linux/macOS and Windows equally, and provide Bash shell examples where relevant.
  • De-emphasize PowerShell for cross-platform tasks, or clearly mark PowerShell sections as Windows-specific.
  • Include troubleshooting tips for Linux/macOS users (e.g., SSH key generation, environment variable setup).
  • Consider adding a section on using kubectl and Azure CLI in native Linux/macOS environments outside Cloud Shell.
GitHub 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 and covers both Windows/macOS and Linux environments. However, in several sections (especially Docker-related issues), Windows/macOS solutions are listed before Linux solutions, and Windows tools (Docker Desktop) are mentioned explicitly. Linux solutions are present and explained, but Windows/macOS are prioritized in ordering and tool references.
Recommendations
  • Present Linux and Windows/macOS solutions in parallel or in a neutral order (e.g., Linux first, or alphabetical).
  • Explicitly mention Linux alternatives for Docker Desktop (such as dockerd/systemctl) where appropriate.
  • Ensure that all troubleshooting steps for Azure CLI, kubectl, and Docker are equally detailed for Linux, macOS, and Windows.
  • Where possible, use generic language (e.g., 'Start Docker daemon') and then provide OS-specific instructions.
  • Consider adding a summary table or section outlining OS-specific troubleshooting steps for quick reference.
GitHub 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 cross-platform instructions for installing and using the Agentic CLI for AKS, including both Linux and Windows/macOS examples. However, in the section about starting the Docker daemon, instructions for macOS/Windows (using Docker Desktop) are presented before Linux (using systemctl), which is a minor 'windows_first' bias. All other examples, commands, and tool references are platform-neutral or include Linux-specific guidance where appropriate.
Recommendations
  • Present Linux instructions before or alongside Windows/macOS instructions when describing how to start Docker, to avoid implicit prioritization.
  • Explicitly mention that Docker Desktop is not available for Linux and clarify the distinction between Linux and Windows/macOS approaches.
  • Ensure parity in troubleshooting and cleanup instructions by verifying that all steps are equally applicable to Linux, macOS, and Windows users.
GitHub 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 cross-platform instructions and download links for Windows, macOS, and Linux, and generally avoids Windows-specific tools or patterns. However, in several places, keyboard shortcuts and UI instructions list Windows first (e.g., 'Ctrl+Shift+P on Windows/Linux or Cmd+Shift+P on macOS'), and troubleshooting tips reference Windows (e.g., WSL configuration) before Linux. There are no explicit Linux-specific troubleshooting examples or tips, and some Docker credential instructions mention Windows limitations but do not provide equivalent Linux guidance. Overall, Linux parity is good, but minor bias exists in ordering and lack of Linux-specific troubleshooting.
Recommendations
  • Alternate keyboard shortcut ordering (e.g., list macOS first sometimes, or use 'on Windows/Linux' and 'on macOS' equally).
  • Add Linux-specific troubleshooting tips, especially for Docker credential mounting and Azure authentication.
  • Provide explicit examples for Linux users where Windows-specific instructions are given (e.g., WSL tips could be matched with Linux container tips).
  • Ensure parity in troubleshooting and common issues sections by including Linux/macOS scenarios.
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 AKS is a Linux-first service, but there are minor instances of Windows bias. In the 'Verify TLS Bootstrapping is enabled on current agent node pool' section, Windows file paths are mentioned alongside Linux, but Windows is listed second. However, in certificate rotation verification examples, output includes Windows node names (e.g., 'akswinp7000000'), which may confuse Linux users. There are no PowerShell-specific commands or Windows-only tools used, and all CLI examples are cross-platform. No critical steps are Windows-only.
Recommendations
  • Ensure Linux examples and file paths are always listed first, as AKS is primarily Linux-based.
  • Clarify that output examples containing Windows node names are applicable to both Linux and Windows node pools, or provide separate examples for each.
  • Add explicit notes or examples for Linux/macOS users where Windows-specific paths or node names are shown.
  • Where possible, provide parallel examples for both Linux and Windows node pools, especially in output sections.
GitHub 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 cross-platform and focuses on AKS storage concepts relevant to both Linux and Windows node pools. However, in the section on mounting volumes in pods, the Linux example is presented first, followed by a Windows-specific example. There are no PowerShell-heavy examples, Windows tools, or missing Linux examples. The only evidence of bias is the ordering of examples, with Linux shown first and Windows second.
Recommendations
  • Ensure that both Linux and Windows examples are presented with equal prominence, possibly by grouping them under clear subheadings (e.g., 'Mounting volumes in Linux containers' and 'Mounting volumes in Windows containers').
  • Clarify that the majority of examples are Linux-centric by default, and provide links to Windows-specific documentation for users running Windows node pools.
  • If possible, provide parity in YAML manifest examples for both Linux and Windows containers throughout the documentation, not just in the volume mount section.
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, covering all major platforms. However, the PowerShell section is more detailed, with explicit instructions for installation and version checks, and is presented before the CLI section. The PowerShell instructions reference Windows tools and patterns more prominently, but also include links for macOS and Linux installation. The CLI section is less detailed and appears after PowerShell, which may subtly prioritize Windows users.
Recommendations
  • Ensure parity in detail between Azure PowerShell and Azure CLI sections, including environment preparation, version checks, and troubleshooting.
  • Consider presenting Azure CLI examples before PowerShell, as CLI is cross-platform and widely used.
  • Explicitly mention that both PowerShell and CLI are available on Windows, macOS, and Linux, and provide equal guidance for each.
  • Add troubleshooting or environment setup notes for CLI users on Linux/macOS, similar to PowerShell.
  • Where possible, avoid referencing Windows-specific tools or patterns unless necessary, and ensure Linux/macOS equivalents are equally visible.
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 references Azure PowerShell alongside Azure CLI in the 'Before you begin' section and links to PowerShell-specific commands before Linux equivalents. The PowerShell cmdlet (Get-AzVirtualNetworkSubnetConfig) is mentioned as an option for listing subnets, but no Linux/macOS equivalent is provided (such as Azure CLI or REST API). However, all core examples for load balancer creation, service deployment, and management use kubectl and Azure CLI, which are cross-platform. There are no PowerShell-only critical steps, and Linux/macOS users can complete all tasks.
Recommendations
  • When referencing Azure PowerShell, always mention Azure CLI first and clarify that Azure CLI is cross-platform.
  • For subnet listing, provide Azure CLI examples before PowerShell, and explicitly note that Azure CLI works on Linux/macOS.
  • Where PowerShell is mentioned, add a note that Azure CLI is recommended for non-Windows users.
  • Consider removing PowerShell links from the main flow or placing them in a separate 'Windows alternative' section.
  • Ensure all critical steps have Azure CLI examples and avoid PowerShell-only instructions.
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) first, followed by Azure PowerShell (Windows-centric). However, the PowerShell section is equally detailed and not prioritized over CLI. No Windows-only tools or patterns are mentioned, and all examples are cross-platform. There are no missing Linux/macOS examples, and the YAML deployment targets Linux node pools. The bias is minor, limited to the ordering of examples and the inclusion of PowerShell.
Recommendations
  • Continue to provide Azure CLI examples first, as CLI is cross-platform.
  • Ensure that all PowerShell commands are accompanied by Azure CLI equivalents.
  • Consider clarifying that Azure CLI works on Windows, Linux, and macOS, while PowerShell is primarily for Windows users.
  • If possible, add a Bash-only example for IP address retrieval for Linux/macOS users (e.g., using curl or wget), though 'dig' is already used.
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 PowerShell is featured equally alongside CLI, which is more common on Windows. The structure consistently presents Azure CLI examples first, followed by PowerShell, potentially favoring Windows users. However, all critical steps are covered with cross-platform tools (Azure CLI, Helm, kubectl, git), and Linux/macOS users can follow the CLI instructions without issue. No Windows-only tools or patterns are used, and Linux parity is maintained throughout.
Recommendations
  • Consider clarifying that Azure CLI is fully cross-platform and recommended for Linux/macOS users.
  • Explicitly state that PowerShell examples are primarily for Windows users, while Azure CLI works on all platforms.
  • Add a note at the top indicating that Linux/macOS users should use Azure CLI and ignore PowerShell sections.
  • Ensure that any future examples or troubleshooting steps do not assume PowerShell as the default shell.
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 command examples for both Azure CLI and Azure PowerShell, but consistently lists Azure PowerShell (a Windows-centric tool) examples immediately after Azure CLI, and references PowerShell-specific commands (e.g., Install-AzAksKubectl, Get-AzAksVersion) without Linux/macOS equivalents. There are no bash or shell script examples, and no explicit mention of Linux/macOS-specific tools or workflows. However, Azure CLI is cross-platform and is shown first in all cases, mitigating the impact. No critical tasks are Windows-only.
Recommendations
  • Explicitly state that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Add bash/shell script examples where relevant, especially for common tasks like checking Kubernetes versions or installing kubectl.
  • Clarify that Azure PowerShell is primarily for Windows users, and provide parity with Linux/macOS instructions when referencing PowerShell.
  • Consider including links or references to Linux/macOS-specific documentation or tools (e.g., Homebrew for kubectl installation).
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 parity between Azure CLI, Azure PowerShell, and Azure portal for all AKS upgrade operations. However, Azure PowerShell examples are included throughout, which is primarily a Windows tool, and in some sections, PowerShell is listed before Azure CLI. There are no Linux-specific shell examples (e.g., Bash), but Azure CLI is cross-platform and is presented as the main tool. No Windows-only tools or patterns are used, and Linux users can complete all tasks using Azure CLI or portal.
Recommendations
  • Ensure Azure CLI examples are always presented first, as it is cross-platform and preferred for Linux/macOS users.
  • Clarify that Azure PowerShell is primarily for Windows users, and recommend Azure CLI for Linux/macOS.
  • Consider adding Bash shell examples for common tasks (e.g., scripting upgrades, validating output) to further improve Linux parity.
  • Explicitly state that Azure CLI works on Linux/macOS/Windows, while Azure PowerShell is Windows-centric.
  • Add a note for Linux/macOS users that Azure CLI is the recommended tool for command-line operations.
GitHub Create Pull Request