← Back to Dashboard
109
Pages Scanned
11
Pages Flagged
109
Changed Pages
10.1%
% Pages Flagged

Live Progress

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

Scan Information

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

Finished At: In Progress

Status: in_progress

Target Repo: Azure Aks

Current Phase: discovery

Files Queued: 109

Files Completed: 109

Problematic Pages

11 issues found
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) examples first. However, PowerShell examples are also included, which is good parity. There are no Windows-only tools or patterns, and all examples are cross-platform. The YAML manifests explicitly target Linux node pools, but this is standard for AKS and not Windows-biased. No critical tasks are Windows-only.
Recommendations
  • Maintain the current structure of presenting Azure CLI examples first, as this is inclusive for Linux/macOS users.
  • Continue to provide both Azure CLI and PowerShell examples for administrative tasks.
  • Consider adding a brief note clarifying that Azure CLI commands work on Linux, macOS, and Windows, while PowerShell commands are primarily for Windows users.
  • Ensure screenshots and portal instructions do not reference Windows-specific UI elements or terminology.
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 tasks. However, Azure PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and is sometimes mentioned before or alongside CLI. There are no Linux-specific examples (e.g., Bash scripting, Linux-native tools), but Azure CLI is cross-platform and the examples are not exclusive to Windows. No critical tasks are Windows-only, and Linux/macOS users can complete all steps using Azure CLI or portal.
Recommendations
  • Clarify that Azure CLI is fully cross-platform and recommended for Linux/macOS users.
  • Consider listing Azure CLI examples before PowerShell in each section, or explicitly note CLI as the default for non-Windows environments.
  • Add brief notes or links for Linux/macOS users about installing Azure CLI and using Bash/zsh shells.
  • If possible, provide Bash script snippets for common operations (e.g., looping over node pools).
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: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation primarily uses Azure CLI commands and kubectl, which are cross-platform tools. However, it does not explicitly mention Linux/macOS environments or provide guidance for those platforms. The examples and instructions are generic, but there is a subtle bias in that Windows is implicitly assumed (e.g., no mention of shell differences, environment variable syntax, or installation nuances for Linux/macOS). There are no PowerShell-specific commands or Windows-only tools, but the lack of explicit Linux/macOS guidance may create minor friction.
Recommendations
  • Add a note clarifying that Azure CLI and kubectl commands work on Windows, Linux, and macOS, and provide links to installation instructions for each platform.
  • Include example environment variable syntax for both Windows (e.g., $RESOURCE_GROUP) and Linux/macOS (e.g., export RESOURCE_GROUP=...).
  • Mention any potential differences in command usage or prerequisites for Linux/macOS users, such as package managers or shell requirements.
  • Ensure that all CLI examples are tested and confirmed to work on Linux/macOS terminals.
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_missing ⚠ī¸ minor_windows_tools
Summary
The documentation provides troubleshooting steps for the Agentic CLI for AKS and generally includes both Windows/macOS and Linux guidance. However, in several sections (especially Docker-related issues), Windows/macOS instructions are listed before Linux, and Windows-specific tools (Docker Desktop) are referenced. There are no PowerShell examples, but Windows/macOS users are directed to GUI actions (launch Docker Desktop), while Linux users are given CLI commands. All Azure CLI and kubectl examples are cross-platform. The bias is minor and does not prevent Linux/macOS users from completing tasks.
Recommendations
  • Alternate the order of Windows/macOS and Linux instructions to avoid 'windows_first' bias.
  • Provide explicit Linux/macOS CLI alternatives for Docker Desktop actions (e.g., 'systemctl start docker' for macOS with Homebrew installs).
  • Clarify that Docker Desktop is not available on Linux and provide links to Linux-specific Docker troubleshooting.
  • Consider adding PowerShell examples for Windows users if CLI is preferred, or Bash equivalents for macOS.
  • Ensure parity in troubleshooting steps for all platforms, including edge cases (e.g., Docker on macOS without Docker Desktop).
GitHub Create Pull Request
Aks About the Agentic CLI for Azure Kubernetes Service (AKS) ...s/blob/main/articles/aks/cli-agent-for-aks-overview.md
Low 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 the 'Client mode' section references Docker and Azure CLI credentials without clarifying Linux/macOS compatibility or providing Linux/macOS-specific instructions. There are no explicit Windows-only tools mentioned, but the lack of Linux/macOS examples and prerequisites creates mild friction for non-Windows users.
Recommendations
  • Explicitly state that the Agentic CLI for AKS supports Windows, Linux, and macOS platforms.
  • Provide installation and usage instructions for Linux/macOS, including Docker and Azure CLI setup on those platforms.
  • Mention any platform-specific considerations (e.g., Docker installation differences, Azure CLI authentication nuances) for Linux/macOS users.
  • Add example commands or screenshots for Linux/macOS terminals alongside any Windows examples.
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 parity for both Windows/macOS and Linux users in most sections, especially regarding Docker installation and AKS agent deployment. However, in the 'Verify Docker installation and start Docker daemon' section, instructions for starting Docker are presented as 'macOS/Windows' first, followed by Linux. This is a minor ordering bias, but all necessary Linux instructions are present. No PowerShell-only examples, Windows tools, or missing Linux examples are detected.
Recommendations
  • Present Linux instructions alongside or before Windows/macOS instructions in sections where order may imply priority.
  • Consider grouping OS-specific instructions in a neutral order or explicitly stating that all OSes are equally supported.
  • Continue to ensure all CLI and tool usage examples are cross-platform and avoid Windows-specific tooling unless required.
GitHub Create Pull Request
Aks Deploy an application with the Dapr cluster extension for Azure Kubernetes Service (AKS) or Arc-enabled Kubernetes ...ure-aks-docs/blob/main/articles/aks/quickstart-dapr.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 options for resource cleanup, but consistently lists Azure CLI (cross-platform) before PowerShell. There are no Windows-specific tools or commands used elsewhere, and all example commands (kubectl, curl, git) are cross-platform and compatible with Linux/macOS. The only minor bias is the inclusion of Azure PowerShell as an alternative, which is more common on Windows, but this is balanced by Azure CLI instructions. No critical steps are Windows-only.
Recommendations
  • Continue to list Azure CLI (cross-platform) as the primary option for all tasks.
  • Explicitly mention that all commands (kubectl, curl, git) work on Linux/macOS and Windows.
  • Consider adding brief notes for Linux/macOS users about installing Azure CLI and PowerShell, if relevant.
  • Ensure parity in future updates by avoiding Windows-only tools unless the feature is Windows-specific.
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 more prominent and detailed, and PowerShell is traditionally associated with Windows. The PowerShell prerequisites and instructions are listed before Azure CLI, and the PowerShell section includes extra guidance about installation and usage on Windows, macOS, and Linux, but the CLI section is less emphasized. There are no missing Linux examples, and both PowerShell and CLI commands work on Linux/macOS, but the structure and emphasis favor PowerShell/Windows users.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is more widely used and natively cross-platform.
  • Balance the detail level between PowerShell and CLI sections, ensuring CLI instructions are as thorough as PowerShell.
  • Explicitly mention that both PowerShell and CLI are cross-platform, and highlight CLI as the preferred option for Linux/macOS users.
  • Add a note recommending Azure CLI for Linux/macOS users, or provide links to CLI installation instructions for all platforms.
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 generally cross-platform, focusing on Azure CLI and Bicep for installation and management, which are available on Windows, Linux, and macOS. 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 (e.g., using grep). Additionally, the use of PowerShell-style variables (e.g., $MY_RESOURCE_GROUP) in CLI examples may be confusing for Bash users, though this is minor.
Recommendations
  • Provide Linux/macOS equivalents for commands using Windows-specific tools, e.g., 'kubectl get crds | grep dapr.io' alongside the findstr example.
  • Clarify variable syntax for both Bash and PowerShell users in CLI examples, or use cross-shell compatible syntax.
  • Review all CLI snippets to ensure they work seamlessly on Bash shells, not just PowerShell.
  • Consider showing both Windows and Linux/macOS command examples where shell-specific differences exist.
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 references PowerShell alongside Azure CLI in the 'Before you begin' section and links to PowerShell documentation. The only explicit PowerShell mention is for listing subnets, but no Linux-specific alternatives (e.g., Bash, shell scripting) are given. Azure CLI is used for all command-line examples, which is cross-platform, but PowerShell is mentioned first in some places. No Linux/macOS-specific friction is present, but the PowerShell references may create minor bias.
Recommendations
  • Where PowerShell is mentioned, clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Provide Bash or shell alternatives for listing subnets (e.g., using Azure CLI), rather than referencing PowerShell.
  • Consider listing Azure CLI before PowerShell in prerequisite steps to reinforce Linux parity.
  • Explicitly state that all Azure CLI commands work on Linux/macOS/Windows.
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 includes PowerShell (a Windows-centric tool) alongside CLI. The CLI is cross-platform, but PowerShell is presented equally, which may imply Windows as a primary platform. There are no Linux-specific examples or explicit mentions of Linux/macOS workflows. However, all core commands (Azure CLI, Helm, kubectl, git) are cross-platform, and the bash shell is used for Helm and Kubernetes commands.
Recommendations
  • Clarify that Azure CLI is recommended for Linux/macOS users, and PowerShell is primarily for Windows.
  • Consider showing Azure CLI examples first, or labeling them as the default for cross-platform users.
  • Add a note indicating that PowerShell examples are for Windows users, and CLI examples are for all platforms.
  • Explicitly mention that Helm, kubectl, and git commands work on Linux/macOS and Windows.
  • Optionally, provide Linux/macOS-specific installation instructions for Azure CLI, Helm, and kubectl.
GitHub Create Pull Request