← Back to Dashboard
108
Pages Scanned
12
Pages Flagged
108
Changed Pages
11.1%
% Pages Flagged

Scan Information

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

Finished At: 2026-02-10 18:44:36

Status: completed

Target Repo: Azure Aks

Current Phase: discovery

Files Queued: 108

Files Completed: 108

Problematic Pages

12 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 (Linux/macOS-friendly) and Azure PowerShell (Windows-centric) examples for troubleshooting IP range configuration, but consistently presents PowerShell examples immediately after CLI, and sometimes with more detail. There are no Windows-only tools or patterns, but PowerShell is given equal prominence, which may be unnecessary for cross-platform parity. The rest of the documentation is portal-centric and platform-neutral.
Recommendations
  • Ensure Azure CLI examples are presented first and with equal or greater detail than PowerShell, as CLI is cross-platform.
  • Explicitly note that Azure CLI works on Linux/macOS/Windows, while PowerShell is Windows-centric.
  • Consider providing Bash-native commands for IP retrieval (e.g., `curl ifconfig.me`) as alternatives to `dig`, which may not be installed by default.
  • Clarify that all portal steps are platform-agnostic.
  • If PowerShell is included, ensure it is clearly marked as Windows-specific and not required for Linux/macOS users.
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 examples, which are cross-platform. However, there is a subtle bias in that Azure CLI examples are shown first and exclusively, with no mention of Linux-specific shell patterns or macOS considerations. There are no PowerShell or Windows-only commands, but the documentation assumes the reader is comfortable with Azure CLI and does not provide alternative instructions for Linux-native tools or package managers (e.g., apt, yum, brew) for installing prerequisites. Additionally, there is no explicit mention that all commands work equally on Linux/macOS, which could create uncertainty for non-Windows users.
Recommendations
  • Explicitly state that Azure CLI and kubectl commands are cross-platform and supported on Linux/macOS.
  • Provide links or brief instructions for installing Azure CLI and kubectl on Linux/macOS.
  • Mention any OS-specific considerations (such as environment variable syntax differences or shell requirements) if relevant.
  • Include example commands for updating/installing Azure CLI using Linux package managers (apt, yum, brew) alongside the az extension commands.
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 Azure PowerShell is mentioned alongside Azure CLI in prerequisites and as an alternative for resource deletion. There are no Windows-only tools or commands used elsewhere, and all main deployment steps use cross-platform tools (kubectl, curl, git). However, Azure PowerShell is referenced equally with Azure CLI, which may create minor friction for Linux/macOS users, as PowerShell is less commonly installed or used on those platforms.
Recommendations
  • Make Azure CLI the default and primary example for resource cleanup, with PowerShell as a secondary option.
  • Clarify that Azure PowerShell is optional and primarily for Windows users, while Azure CLI is cross-platform.
  • Consider providing Bash shell examples for common operations if relevant.
  • Ensure that all steps can be completed using Azure CLI and kubectl, without requiring PowerShell.
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 both Linux and Windows file paths for verifying TLS Bootstrapping, but in most sections, examples and commands are generic and platform-neutral (using Azure CLI and kubectl). However, in the 'Verify TLS Bootstrapping is enabled on current agent node pool' section, the Windows path is mentioned alongside the Linux path, but Linux is listed first. There are no PowerShell-specific examples, and all shell commands use bash syntax. No Windows tools or patterns are mentioned exclusively or before Linux equivalents. However, there is a minor bias in that the Windows path is only mentioned in one section, and no explicit Linux-specific troubleshooting or examples are given elsewhere.
Recommendations
  • Ensure that Linux and Windows paths are always provided together when relevant, and clarify any OS-specific steps.
  • Add explicit notes or troubleshooting steps for Linux users where applicable, especially for file access or certificate management.
  • Consider including example outputs for both Linux and Windows environments to improve parity.
  • If there are any OS-specific limitations or behaviors, document them clearly.
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 generally maintains good cross-platform parity, but there are subtle signs of Windows bias. In the Docker daemon startup instructions, macOS/Windows (Docker Desktop) is mentioned before Linux, and no Linux desktop environment is referenced. The verification steps for Docker cleanup use 'ls ~/.azure/aksAgent.config' and 'docker images | grep aks-agent', which are Unix-style commands, but no PowerShell/Windows Command Prompt equivalents are provided. However, the documentation does not provide explicit PowerShell or Windows Command Prompt examples for Azure CLI commands, which are cross-platform. The overall flow and examples are CLI-centric and mostly platform-neutral, but the ordering and some phrasing may create minor friction for Linux users.
Recommendations
  • In Docker daemon startup instructions, mention Linux first or equally, and clarify that Docker Desktop is not available for Linux.
  • Provide PowerShell/Windows Command Prompt equivalents for verification commands (e.g., checking for config files and Docker images) to ensure parity for Windows users.
  • Explicitly state that all Azure CLI commands work on Linux, macOS, and Windows, and link to platform-specific installation guides for Docker and Azure CLI.
  • Where file paths are referenced (e.g., ~/.azure/aksAgent.config), clarify the Windows equivalent (e.g., %USERPROFILE%\.azure\aksAgent.config).
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 detailed and includes instructions for installing/upgrading PowerShell on Windows, macOS, and Linux, but the PowerShell-centric workflow and terminology may be more familiar to Windows users. In the prerequisites, PowerShell is listed before CLI, and PowerShell-specific instructions are more verbose. However, Azure CLI examples are provided and are cross-platform. No critical steps are Windows-only, and Linux/macOS users can complete all tasks.
Recommendations
  • Ensure parity in example detail between Azure PowerShell and Azure CLI sections.
  • Consider listing Azure CLI before PowerShell in prerequisites and configuration sections, as CLI is more universally cross-platform.
  • Add explicit notes highlighting that both Azure PowerShell and Azure CLI are fully supported on Linux and macOS, and link to installation guides for all platforms.
  • Balance the verbosity of PowerShell instructions with CLI instructions to avoid perceived preference.
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 platform-specific guidance for Docker issues. Windows/macOS instructions are often listed before Linux, and Windows-specific tooling (Docker Desktop) is referenced. However, Linux commands are included for most scenarios. There are no PowerShell examples, but Windows/macOS solutions are sometimes prioritized. Azure CLI and kubectl commands are cross-platform, but some troubleshooting steps (e.g., Docker Desktop) are Windows/macOS-centric, and Linux solutions are sometimes less detailed.
Recommendations
  • Present Linux, macOS, and Windows instructions in parallel or in a consistent order (e.g., Linux first, then macOS, then Windows) to avoid implicit prioritization.
  • Expand Linux troubleshooting steps for Docker Desktop alternatives (e.g., mention dockerd or other Linux-specific Docker management tools).
  • Ensure all platform-specific instructions are equally detailed and clear.
  • Where possible, clarify if a solution applies to all platforms or only to Windows/macOS.
  • Add explicit notes for macOS/Linux users when a step is Windows-specific (e.g., Docker Desktop).
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 'Listing the CRDs in your cluster' section, 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 is shown with interactive shell prompts that may be more familiar to Windows users, but the CLI itself is cross-platform.
Recommendations
  • Provide Linux/macOS equivalent for CRD listing, e.g., 'kubectl get crds | grep dapr.io'.
  • When showing shell commands, clarify that Azure CLI works on all platforms and, where relevant, show both Windows and Linux/macOS shell syntax.
  • Review other command examples for platform-specific patterns and add parity where needed.
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 to PowerShell are present alongside Azure CLI in the 'Before you begin' section and for subnet listing. Azure CLI is used for all main walkthrough steps and examples, but PowerShell is mentioned as an alternative tool for some Azure operations. There are no Linux-specific examples or explicit Linux parity notes. The order of tools sometimes puts PowerShell before Azure CLI or at least equally, which may subtly suggest Windows familiarity. However, all critical steps use cross-platform tools (kubectl, Azure CLI), and Linux/macOS users can complete the tasks without friction.
Recommendations
  • Clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Where PowerShell is mentioned, explicitly note that Azure CLI is available and recommended for Linux/macOS.
  • Consider providing Linux/macOS-specific command examples or notes where Azure CLI is used.
  • If referencing PowerShell, always list Azure CLI first and clarify its cross-platform nature.
  • Add a brief note in 'Before you begin' that all main steps use cross-platform tools and are suitable for Linux/macOS.
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 for creating an AKS cluster using Azure CLI, Azure PowerShell, and Azure portal, with PowerShell mentioned alongside CLI and portal. However, all configuration, verification, and troubleshooting examples use cross-platform tools (Azure CLI, kubectl, YAML), and the feature itself is only supported on Azure Linux or Ubuntu node pools. There are no PowerShell-specific commands or Windows-only tools used in the main instructions. The only minor bias is the mention of Azure PowerShell as a cluster creation option, which is listed alongside CLI and portal, but no PowerShell-specific examples are provided.
Recommendations
  • Ensure that Linux/macOS users are aware that Azure CLI and kubectl commands are fully cross-platform.
  • Consider clarifying that Azure PowerShell is primarily for Windows users, and recommend Azure CLI for Linux/macOS.
  • If possible, list Azure CLI as the primary option for cluster creation, with PowerShell as an alternative for Windows users.
  • Add a note that all configuration and verification steps are cross-platform and do not require Windows tools.
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 PowerShell examples alongside CLI, and sometimes references Azure PowerShell in prerequisites and custom metadata. There is no explicit Windows-only content, but PowerShell is a Windows-centric tool, and its inclusion may create friction for Linux/macOS users. However, all critical steps are covered with Azure CLI (cross-platform), and shell/bash commands are used for Helm and kubectl operations.
Recommendations
  • Consider clarifying that Azure PowerShell is primarily for Windows users, and Azure CLI is recommended for Linux/macOS.
  • Present Azure CLI examples first in each section, as it is cross-platform.
  • Add explicit notes or guidance for Linux/macOS users, e.g., 'Azure CLI is recommended for Linux/macOS environments.'
  • Optionally, provide bash/zsh shell script snippets for common tasks, or link to Linux/macOS-specific guides.
  • Remove Azure PowerShell from prerequisites for Linux/macOS users, or clarify its platform relevance.
GitHub Create Pull Request
Aks Secure Pod Traffic with Network Policies in Azure Kubernetes Service (AKS) ...ks-docs/blob/main/articles/aks/use-network-policies.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 Linux and Windows examples for AKS network policy management, but Windows-specific instructions (such as registering feature flags and creating Windows admin credentials) are presented in dedicated sections and sometimes before Linux equivalents. All CLI examples use Azure CLI and Bash, which are cross-platform, but there are no PowerShell-specific examples. The documentation does not show a strong bias, but Windows instructions are prominent and sometimes appear before Linux instructions, creating minor friction for Linux/macOS users.
Recommendations
  • Ensure Linux instructions are presented first in sections where both Linux and Windows are supported.
  • Add explicit notes clarifying which steps are platform-specific and which are cross-platform.
  • Consider providing PowerShell examples for Windows users alongside Bash examples for Linux/macOS users.
  • Clearly separate Windows-only content from Linux content to avoid confusion.
GitHub Create Pull Request