← Back to Dashboard
137
Pages Scanned
14
Pages Flagged
137
Changed Pages
10.2%
% Pages Flagged

Live Progress

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

Scan Information

Started At: 2026-02-26 00:00:09

Finished At: In Progress

Status: in_progress

Target Repo: Azure Aks

Current Phase: discovery

Files Queued: 137

Files Completed: 137

Problematic Pages

14 issues found
Aks Install Dapr Extension for Azure Kubernetes Service (AKS) ...softDocs/azure-aks-docs/blob/main/articles/aks/dapr.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation is generally cross-platform, focusing on Azure CLI and Bicep, which are available on Windows, Linux, and macOS. However, there is a notable bias in the CRD cleanup section, where the only example for listing Dapr CRDs uses Windows-specific PowerShell syntax (`findstr`). No equivalent Linux/macOS example (e.g., using `grep`) is provided. This could cause confusion or friction for non-Windows users.
Recommendations
  • Provide both Windows (findstr) and Linux/macOS (grep) examples when filtering kubectl output, e.g., `kubectl get crds | grep dapr.io`.
  • Explicitly state that Azure CLI and Bicep commands are cross-platform, and link to installation guides for Linux/macOS if not already present.
  • Review for any other subtle Windows-centric assumptions (e.g., environment variable syntax, file paths) and ensure parity.
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 setup, but Windows-specific instructions (such as registering feature flags and creating Windows admin credentials) are presented in detail and immediately after the Linux section. The Windows section is extensive, but Linux parity is maintained throughout. All CLI examples use Azure CLI and Bash, which are cross-platform, but PowerShell is not referenced. Windows-specific tools (HNS ACLPolicy) are mentioned alongside Linux equivalents (IPTables). The ordering sometimes puts Windows instructions before Linux or mixes them, but Linux users can complete all tasks without friction.
Recommendations
  • Ensure Linux and Windows instructions are clearly separated and labeled, so Linux users can easily find relevant sections.
  • Consider presenting Linux instructions first in each section unless the feature is Windows-only.
  • Add explicit notes clarifying which steps are platform-specific.
  • Where possible, provide parity in detail for Linux and Windows steps, especially for advanced scenarios.
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 installation and usage instructions for the Agentic CLI for AKS with clear support for both Windows/macOS and Linux platforms. However, in the Docker daemon startup instructions, Windows/macOS steps (Docker Desktop) are mentioned before Linux-specific commands, which is a minor 'windows_first' bias. All CLI examples and tool references are cross-platform, and Linux-specific commands (systemctl, kubectl) are included where relevant.
Recommendations
  • Present Linux instructions before or alongside Windows/macOS steps in the Docker daemon startup section.
  • Consider explicitly mentioning that all Azure CLI and Docker commands are cross-platform.
  • Add clarifying notes for any platform-specific behaviors (e.g., Docker Desktop vs. Docker Engine) to ensure parity.
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 with both Windows/macOS and Linux instructions. However, in several places, Windows/macOS solutions (e.g., 'Launch Docker Desktop') are listed before Linux solutions, and Windows-specific tooling (Docker Desktop) is mentioned explicitly. Linux instructions are present and generally clear, but Windows/macOS steps are prioritized in ordering and phrasing.
Recommendations
  • Present Linux and Windows/macOS instructions in parallel or in a consistent order (e.g., Linux first, then Windows/macOS, or vice versa, but clearly separated).
  • Explicitly mention that Docker Desktop is a Windows/macOS tool and provide equivalent Linux instructions with equal prominence.
  • Where possible, use neutral language and avoid prioritizing Windows/macOS solutions unless there is a technical reason.
  • Ensure all troubleshooting steps have Linux/macOS parity, and examples are equally detailed.
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 signs of Windows bias. In the section 'Verify TLS Bootstrapping is enabled on current agent node pool', the Windows file path ('C:\k\bootstrap-config') is mentioned immediately after the Linux path, which is appropriate but could be improved by clarifying Linux as the default. There are no PowerShell or Windows-only command examples, and all CLI/script examples use Azure CLI and Bash, which are cross-platform. However, the documentation does not provide explicit instructions for accessing Windows nodes to check certificate files, nor does it clarify how to run Azure CLI commands on Windows (e.g., in PowerShell).
Recommendations
  • Clarify that most AKS clusters use Linux nodes by default and that Linux paths are the primary reference.
  • Add explicit instructions or examples for accessing Windows nodes (e.g., using PowerShell or Azure CLI on Windows) when referencing Windows file paths.
  • When mentioning file paths for both Linux and Windows, consider listing Linux first and providing parity in instructions for both platforms.
  • Add a note about Azure CLI usage on Windows (e.g., that Bash commands can be run in Windows Subsystem for Linux, Git Bash, or PowerShell with minor syntax changes).
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 references Windows tools, but also includes instructions for macOS and Linux. However, PowerShell is presented before Azure CLI, and the PowerShell section is more prominent, which may create a perception of Windows bias. Azure CLI examples (which are cross-platform) are present and functional, but are listed after PowerShell.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is more widely used across Linux/macOS.
  • Ensure that PowerShell instructions clearly highlight cross-platform support and do not assume Windows as the default.
  • Consider adding explicit Bash shell examples where relevant, especially for Linux/macOS users.
  • Clarify that both Azure CLI and PowerShell can be used on all platforms, and recommend Azure CLI for Linux/macOS 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 ⚠ī¸ powershell_heavy
Summary
The documentation provides cross-platform instructions and download links for Windows, macOS, and Linux, and generally avoids Windows-specific tools or patterns. However, there is a minor bias in that keyboard shortcuts and VS Code instructions often mention Windows first (e.g., 'Ctrl+Shift+P on Windows/Linux or Cmd+Shift+P on macOS'), and the VS Code extension workflow is described as the 'recommended' path, which may be more familiar to Windows users. There are no PowerShell-specific examples, but Windows is consistently listed first in download tables and shortcut instructions.
Recommendations
  • Alternate the order of platform mentions (e.g., Linux/macOS/Windows) in tables and instructions to avoid Windows-first bias.
  • Provide explicit examples for Linux/macOS where relevant, such as file paths and environment variable usage.
  • Clarify that the VS Code extension workflow is equally supported on all platforms, and highlight any Linux/macOS-specific considerations (e.g., file permissions, shell usage).
  • Add troubleshooting tips for Linux/macOS users, such as handling executable permissions or common issues with Docker volume mounts.
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 provides both Linux and Windows container examples for volume mounting, but the Linux example is presented first and is more detailed. Windows-specific instructions are included only in a small section. There are no PowerShell-heavy examples, Windows tools, or missing Linux examples. The documentation is generally neutral and covers storage concepts applicable to both Linux and Windows AKS workloads, with a slight preference for Linux-first presentation.
Recommendations
  • Ensure Windows container examples are as detailed as Linux examples, including YAML manifests and explanations.
  • Consider grouping Linux and Windows examples together or explicitly labeling them to improve clarity for both audiences.
  • Where relevant, provide parity in troubleshooting tips or best practices for both Linux and Windows container storage scenarios.
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 consistently mentions Azure PowerShell alongside Azure CLI and portal, and links to PowerShell cmdlets before or equally with CLI commands. There are no Linux/macOS-specific examples or explicit parity guidance. However, all main walkthroughs use kubectl and Azure CLI, which are cross-platform, and no critical steps are Windows-only.
Recommendations
  • When referencing prerequisite cluster creation, mention Azure CLI first (as it is cross-platform), and clarify that Azure PowerShell is Windows-centric.
  • For commands to list subnets, prioritize Azure CLI examples and note that PowerShell is primarily for Windows users.
  • Add explicit notes that Azure CLI and kubectl are fully supported on Linux/macOS, and provide links to installation instructions for those platforms.
  • Consider removing or de-emphasizing PowerShell references unless there is a specific Windows-only audience or requirement.
GitHub Create Pull Request
Aks Azure Kubernetes Service (AKS) Managed Gateway API Installation (preview) ...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 for installation and management, which are cross-platform. However, the examples and instructions do not explicitly mention Linux/macOS compatibility or alternatives, and Azure CLI is often associated with Windows usage. The documentation does not provide PowerShell-specific examples or Windows-only tools, but it also does not highlight Linux/macOS usage or potential differences, and the Azure CLI examples are shown without clarifying their cross-platform nature.
Recommendations
  • Explicitly state that Azure CLI commands work on Windows, Linux, and macOS.
  • Add notes or sections clarifying that all steps are applicable to Linux/macOS users.
  • Include example commands for Bash (Linux/macOS) and, if relevant, PowerShell (Windows), to demonstrate parity.
  • Mention any prerequisites or installation steps for Azure CLI on Linux/macOS, if not already covered elsewhere.
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 available Kubernetes versions), but consistently lists Azure CLI (cross-platform) examples first, followed by Azure PowerShell (Windows-centric) examples. There are no Linux-specific commands or shell examples (e.g., Bash), but the CLI is cross-platform. No Windows-only tools or patterns are mentioned, and the content is not exclusive to Windows. The bias is minor and mostly in the ordering and inclusion of PowerShell examples.
Recommendations
  • Explicitly mention that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Consider adding Bash shell examples for Linux users where relevant (e.g., using curl to install kubectl).
  • Where PowerShell examples are given, clarify their Windows-centric nature and provide parity for Linux/macOS users.
  • Ensure that any references to OS-specific components (e.g., containerd versions for Linux/Windows) are balanced and clear.
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 managing AKS authorized IP ranges, but the PowerShell section is presented immediately after the CLI section and is equally prominent. There are no Linux/macOS-specific examples or explicit mentions of Bash or Linux tools. The Azure CLI example uses 'dig', which is available on Linux/macOS but not by default on Windows, while the PowerShell example is Windows-centric. The rest of the documentation is portal-focused and platform-neutral.
Recommendations
  • Explicitly note that Azure CLI commands are cross-platform and can be run in Bash (Linux/macOS) or Windows Command Prompt/PowerShell.
  • Add a Bash-specific example for retrieving the public IP address (e.g., using 'curl' or 'wget'), since 'dig' may not be installed by default.
  • Clarify that Azure PowerShell is Windows-centric, and recommend Azure CLI for Linux/macOS users.
  • Consider showing Azure CLI examples first, as it is more cross-platform.
  • Add a note about installing 'dig' if not present, or provide alternative commands.
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 (which is cross-platform and preferred on Linux/macOS) first, followed by Azure PowerShell (primarily used on Windows). There are no Windows-specific tools or patterns shown exclusively, and all critical steps are accessible via CLI commands suitable for Linux/macOS. Bash shell commands (git, helm, kubectl) are used for application-level steps, ensuring Linux parity. However, the presence of Azure PowerShell examples throughout may create minor friction for Linux users, as PowerShell is less commonly used outside Windows.
Recommendations
  • Consider clarifying that Azure CLI is the recommended and cross-platform approach for Linux/macOS users.
  • Optionally, add a note at the start of each section indicating Azure PowerShell is primarily for Windows users, while Azure CLI is for all platforms.
  • Ensure that all CLI examples are tested and work on Linux/macOS shells.
  • If possible, provide a Linux/macOS-specific quickstart tab (even if it mirrors Azure CLI) to reinforce parity.
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, but PowerShell examples and terminology are prominent throughout. PowerShell is a Windows-centric tool, and its inclusion alongside Azure CLI may suggest a Windows bias. Additionally, PowerShell instructions are given equal prominence to Azure CLI, which is more cross-platform. There are no explicit Linux/macOS examples or notes about running commands in Bash or zsh locally, and the documentation does not mention Linux-specific patterns or tools. However, Azure CLI is cross-platform and is presented first in most sections.
Recommendations
  • Add explicit notes clarifying that Azure CLI commands work on Linux/macOS as well as Windows.
  • Include Bash/zsh shell examples or mention that Azure CLI commands can be run in native Linux/macOS terminals.
  • Consider reducing the prominence of PowerShell unless there are Windows-specific tasks.
  • Add a brief section or callout for Linux/macOS users, highlighting any differences or confirming parity.
  • Mention that Azure Cloud Shell is available from any OS and supports Bash and PowerShell.
GitHub Create Pull Request