← Back to Dashboard
124
Pages Scanned
11
Pages Flagged
124
Changed Pages
8.9%
% Pages Flagged

Live Progress

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

Scan Information

Started At: 2026-02-19 00:00:10

Finished At: In Progress

Status: in_progress

Target Repo: Azure Aks

Current Phase: discovery

Files Queued: 124

Files Completed: 124

Problematic Pages

11 issues found
Aks Access Kubernetes Resources using the Azure Portal ...e-aks-docs/blob/main/articles/aks/kubernetes-portal.md
Medium 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 example is given equal prominence and is not clearly marked as Windows-only. The CLI example uses 'dig', which is not available by default on Windows, but no explicit Linux/macOS guidance is provided. The PowerShell example is shown immediately after the CLI example, and neither is prioritized for Linux/macOS users. There are no explicit Linux/macOS instructions or troubleshooting tips, and the documentation does not clarify which commands are platform-specific.
Recommendations
  • Clearly indicate that Azure PowerShell examples are intended for Windows users, and Azure CLI examples are cross-platform.
  • For the Azure CLI example, provide alternative commands for retrieving the public IP address on Windows (e.g., using 'curl' or 'Invoke-RestMethod') and Linux/macOS (e.g., 'curl ifconfig.me').
  • Add a note or tab for Linux/macOS users, specifying which commands are available by default and how to install missing tools (e.g., 'dig').
  • Consider showing Azure CLI examples first, as they are cross-platform, and PowerShell examples only for Windows users.
  • Add troubleshooting tips for Linux/macOS users if certain commands fail due to missing dependencies.
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-focused, but there is a minor bias in the 'Verify TLS Bootstrapping is enabled on current agent node pool' section, where Windows file paths are mentioned alongside Linux paths, but the Windows path is listed second. There are no PowerShell-specific examples, and all command-line instructions use Azure CLI and Bash, which are cross-platform and primarily Linux-oriented. However, there is a lack of explicit Windows command examples (e.g., PowerShell or CMD) for users who may be operating AKS clusters with Windows agent nodes.
Recommendations
  • Add explicit Windows command examples (e.g., PowerShell or CMD) for relevant operations, especially where file paths or certificate checks are mentioned for Windows nodes.
  • Ensure parity in troubleshooting and verification steps for both Linux and Windows node pools, including examples of how to access and verify certificates on Windows nodes.
  • Consider listing Windows and Linux examples side-by-side in sections where both are relevant, rather than only mentioning file paths.
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
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all Azure-related operations, but consistently presents Azure CLI (Linux/macOS-friendly) examples first, followed by Azure PowerShell (Windows-centric) examples. There are no Windows-only tools or commands used, and all shell commands (git, helm, kubectl) are shown in bash syntax, which is cross-platform. However, the presence of Azure PowerShell throughout may suggest a slight Windows bias, but Linux parity is maintained.
Recommendations
  • Continue to present Azure CLI examples first, as this is the most cross-platform approach.
  • Consider clarifying that Azure PowerShell is available on Linux/macOS as well, to avoid the perception that it is Windows-only.
  • Ensure that all bash commands are explicitly noted as compatible with Linux/macOS/Windows (via WSL or Git Bash).
  • Optionally, add a brief note at the start indicating that all steps can be performed on Linux, macOS, or Windows.
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 tasks (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 prioritized, and Linux support is clearly referenced in component tables. No critical tasks are Windows-only, and Linux users can complete all tasks using Azure CLI.
Recommendations
  • Explicitly mention that Azure CLI is cross-platform and recommended for Linux/macOS users.
  • Add a note clarifying that Azure PowerShell is primarily for Windows users.
  • Consider including example commands for Bash or shell scripting where relevant.
  • Where possible, add explicit Linux/macOS instructions or highlight parity.
  • Ensure that any references to Azure CLI or PowerShell are accompanied by a statement about platform compatibility.
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 parity for Linux, macOS, and Windows users in most sections. However, in the Docker daemon startup instructions, Windows/macOS steps (Docker Desktop) are mentioned before Linux steps (systemctl), which is a minor 'windows_first' bias. All CLI examples and tool references are cross-platform, and Linux-specific instructions are present where relevant.
Recommendations
  • Consider listing Linux instructions before or alongside Windows/macOS steps in Docker daemon startup guidance to avoid implicit prioritization.
  • Explicitly mention that all Azure CLI and Docker commands are cross-platform, and provide links to Linux-specific installation guides where possible.
  • Ensure that troubleshooting and cleanup verification steps include Linux, macOS, and Windows variations equally.
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 platform-specific instructions and download links for Windows, macOS, and Linux, and generally covers all major OSes. However, Windows is often mentioned first in lists and keyboard shortcut instructions, and some tips (such as WSL configuration) are Windows-specific. There are no Linux/macOS-specific troubleshooting tips or examples, and Docker instructions reference Windows-specific credential issues without providing equivalent Linux/macOS guidance. Linux is not omitted, but parity in troubleshooting and tips could be improved.
Recommendations
  • Alternate the order of platform mentions (e.g., sometimes list Linux/macOS before Windows).
  • Provide Linux/macOS-specific troubleshooting tips, especially for Docker credential management and VS Code integration.
  • Add explicit Linux/macOS instructions for common issues (e.g., how to check Azure credentials, kubeconfig paths, and permission troubleshooting).
  • Include Linux/macOS-specific keyboard shortcuts and configuration tips alongside Windows/WSL guidance.
  • Ensure that Docker credential instructions are clear for Linux/macOS users, not just Windows.
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: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_missing ⚠ī¸ linux_parity_good
Summary
The documentation provides troubleshooting steps for the Agentic CLI for AKS with clear differentiation between Windows/macOS and Linux environments. Windows/macOS instructions (Docker Desktop) are listed before Linux instructions (systemd), but Linux-specific commands are included and explained. No PowerShell examples are given, and all CLI commands are cross-platform (bash and Azure CLI). There is minor bias in listing Windows/macOS steps first, but Linux users are not blocked or disadvantaged.
Recommendations
  • Consider listing Linux instructions before or alongside Windows/macOS steps to avoid implicit prioritization.
  • Explicitly mention that Azure CLI commands are cross-platform and can be run on Linux, macOS, or Windows.
  • Add PowerShell examples for Windows users if relevant, or clarify that bash/Azure CLI commands are preferred.
  • Where possible, clarify any OS-specific nuances (e.g., Docker group membership is not needed on Windows/macOS).
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. The PowerShell section is prominent and includes detailed instructions, but it does mention installation and usage 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. There are no Linux-specific shell examples (e.g., Bash), and the CLI section is less detailed.
Recommendations
  • Provide Bash shell examples for Linux users alongside PowerShell examples.
  • Move Azure CLI examples before PowerShell, as CLI is more cross-platform and native to Linux/macOS.
  • Clarify that PowerShell instructions are equally applicable on Linux/macOS, or highlight CLI as the preferred method for Linux/macOS users.
  • Add explicit notes or tabs for Linux/macOS workflows, such as using Bash or Zsh.
  • Ensure parity in detail between PowerShell and CLI sections.
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 installing the Dapr extension on AKS and Arc-enabled Kubernetes clusters. However, there is a minor Windows bias in the 'Listing the CRDs in your cluster' section, where the example uses 'kubectl get crds | findstr dapr.io', which is a Windows/PowerShell pattern. No Linux/macOS equivalent (e.g., using 'grep') is provided. Additionally, the use of Azure CLI throughout is platform-neutral, but the CLI examples and instructions are shown first, which may slightly favor Windows users if they are assumed to use CLI more often.
Recommendations
  • Provide Linux/macOS equivalent commands for listing CRDs, such as 'kubectl get crds | grep dapr.io'.
  • Explicitly mention that Azure CLI is cross-platform and link to installation instructions for Linux/macOS.
  • Where shell commands are shown, offer both Windows (findstr) and Linux/macOS (grep) examples side by side.
  • Review other sections for similar shell command patterns and ensure parity.
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 as ways to create an AKS cluster. It also references the PowerShell cmdlet Get-AzVirtualNetworkSubnetConfig as an alternative to the Azure CLI for listing subnets. However, all actual walkthroughs and code examples use cross-platform tools (kubectl, Azure CLI), and there are no PowerShell-specific examples for the main task. The mention of PowerShell is always as an alternative, but it is listed alongside CLI and portal, rather than after Linux/macOS-friendly options.
Recommendations
  • List Azure CLI as the primary recommended tool for Linux/macOS parity, and mention PowerShell as an alternative for Windows users only.
  • Where PowerShell is referenced, clarify that it is for Windows users, and provide equivalent Azure CLI commands first.
  • Consider removing PowerShell references from prerequisite steps unless there is a Windows-specific workflow.
  • Ensure all main task examples use cross-platform tools (kubectl, Azure CLI), as currently done.
GitHub 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 equally alongside Azure CLI, which is more commonly used on Linux/macOS. PowerShell is primarily a Windows-centric tool, and its inclusion may suggest Windows bias. Additionally, PowerShell examples are given equal prominence, and in some sections, PowerShell is mentioned before Azure CLI, which could be perceived as 'windows_first'. No Linux-specific examples, shell patterns, or explicit Linux/macOS guidance are provided, but the Azure CLI instructions are cross-platform.
Recommendations
  • Clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Consider adding explicit Bash shell examples or notes for Linux/macOS users, especially for environment variable usage and SSH key management.
  • Reorder sections to consistently present Azure CLI instructions before PowerShell, as CLI is more universal.
  • Add a brief note explaining that PowerShell is primarily for Windows users, while Azure CLI works on all platforms.
GitHub Create Pull Request