← Back to Dashboard
118
Pages Scanned
11
Pages Flagged
118
Changed Pages
9.3%
% Pages Flagged

Live Progress

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

Scan Information

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

Finished At: In Progress

Status: in_progress

Target Repo: Azure Aks

Current Phase: discovery

Files Queued: 118

Files Completed: 118

Problematic Pages

11 issues found
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 Linux, macOS, and Windows users throughout, but in the Docker daemon startup instructions, Windows/macOS are mentioned before Linux. All CLI examples use cross-platform Azure CLI and Bash commands, and Linux-specific instructions are present where relevant. No PowerShell or Windows-only tools are used.
Recommendations
  • In the Docker daemon startup section, consider listing Linux instructions before or alongside Windows/macOS for improved parity.
  • Explicitly state that all Azure CLI and Bash commands are cross-platform and supported on Linux, macOS, and Windows.
  • Ensure that any troubleshooting or advanced configuration sections reference Linux and macOS paths and conventions where applicable.
GitHub Create Pull Request
Aks Secure Container Access to Resources in Azure Kubernetes Service (AKS) ...docs/blob/main/articles/aks/secure-container-access.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation is focused on Linux security features for AKS containers and does not exhibit Windows bias in examples or tooling. However, in several prerequisite sections, the Azure PowerShell option is mentioned before Linux-centric alternatives (Azure CLI), which is a minor 'windows_first' bias. All technical content, examples, and instructions are Linux-focused and relevant for Linux node pools only.
Recommendations
  • In prerequisite lists, mention Azure CLI before Azure PowerShell to prioritize Linux-friendly tooling.
  • Where possible, clarify that Azure PowerShell is optional and primarily for Windows users, while Azure CLI is cross-platform.
  • Consider adding explicit notes that all examples are Linux-only and not applicable to Windows node pools, to avoid confusion.
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, focusing on Azure CLI and kubectl commands, which are available on both Windows and Linux. However, in the section 'Verify TLS Bootstrapping is enabled on current agent node pool', the Windows file path ('C:\k\bootstrap-config') is mentioned after the Linux path, but both are provided. There are no PowerShell-specific examples, and all command-line instructions use bash or Azure CLI. No Windows-only tools or patterns are used, and Linux parity is mostly maintained. The only minor bias is that Windows is mentioned second in the file path example, and there are no explicit macOS references.
Recommendations
  • Explicitly mention that all Azure CLI and kubectl commands work on Linux, macOS, and Windows.
  • Add a note clarifying that macOS users can use the Linux instructions.
  • Ensure parity in file path examples by consistently listing Linux, macOS, and Windows paths together.
  • Consider adding a brief section or note about using Azure CLI and kubectl on macOS, if relevant.
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). No Windows-only tools or patterns are prioritized, and all examples are cross-platform. However, the PowerShell section is present, which could be considered minor Windows bias, but Linux parity is maintained throughout. No critical tasks are Windows-only, and Linux/macOS users can complete all steps.
Recommendations
  • Continue to provide Azure CLI examples first, as this is the most cross-platform approach.
  • Consider explicitly stating that Azure CLI works on Windows, Linux, and macOS, and that PowerShell is primarily for Windows users.
  • If possible, add a Bash-only example for retrieving the public IP address (e.g., using curl or wget), to further improve Linux parity.
  • Ensure screenshots and portal instructions do not reference Windows-specific UI elements or terminology.
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: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation generally provides cross-platform troubleshooting steps, but in several places, Windows (and macOS) instructions are listed before Linux equivalents, and 'Docker Desktop' (a Windows/macOS tool) is referenced before Linux-specific commands. Linux instructions are present, but the ordering and emphasis may subtly favor Windows/macOS users.
Recommendations
  • Present Linux, macOS, and Windows instructions in parallel or in a consistent order (e.g., Linux, macOS, then Windows) to avoid implicit prioritization.
  • When referencing Docker, clarify that 'Docker Desktop' is for Windows/macOS and provide equal prominence to Linux service management commands.
  • Where possible, use platform-agnostic language or group instructions by OS with clear headings.
  • Ensure all examples (e.g., for Docker, Azure CLI) are validated to work on Linux, and explicitly state any platform-specific caveats.
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 Azure CLI is cross-platform, the PowerShell section is prominent and includes detailed instructions, including module installation and upgrade steps for Windows, macOS, and Linux. The PowerShell instructions are slightly more detailed and appear before the Azure CLI section. However, Azure CLI examples are present and clearly labeled, ensuring Linux/macOS users can complete the task. There is a minor bias in the ordering and emphasis on PowerShell, but Linux parity is largely maintained.
Recommendations
  • Consider presenting Azure CLI examples before PowerShell, as CLI is more universally supported across platforms.
  • Ensure that CLI instructions are as detailed as PowerShell instructions, including environment preparation and troubleshooting steps.
  • Explicitly note that Azure CLI is recommended for Linux/macOS users, and PowerShell is optional.
  • Add a brief section clarifying that both PowerShell and CLI are fully supported on Linux/macOS, with links to installation guides.
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 platform-neutral, focusing on Azure CLI and Bicep for Dapr extension installation on AKS and Arc-enabled Kubernetes. However, there is a minor Windows bias in the CRD listing example, which uses 'kubectl get crds | findstr dapr.io' (a Windows/PowerShell pattern) instead of a cross-platform or Linux-first approach. Additionally, the use of Azure CLI throughout is platform-neutral, but the example for listing CRDs could create friction for Linux/macOS users.
Recommendations
  • Replace 'kubectl get crds | findstr dapr.io' with 'kubectl get crds | grep dapr.io', or provide both examples for Windows and Linux/macOS.
  • Where possible, ensure all shell examples are cross-platform or explicitly note OS-specific commands.
  • Review other command snippets for any implicit Windows assumptions and clarify as 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 some prerequisite steps, but consistently mentions Azure PowerShell alongside Azure CLI and the Azure portal as ways to create an AKS cluster. Additionally, PowerShell is referenced as a tool for querying subnets, and its cmdlet is linked before or alongside the Azure CLI equivalent. However, all actual operational examples (manifest creation, kubectl commands, Azure CLI commands) are cross-platform and do not use Windows-specific syntax or tools. There are no PowerShell-only critical steps, and Linux/macOS users can complete all tasks using Azure CLI and kubectl.
Recommendations
  • When listing ways to create an AKS cluster, mention Azure CLI first, as it is cross-platform, and clarify that Azure PowerShell is Windows-centric.
  • When referencing commands to query subnets, list Azure CLI as the primary example and PowerShell as an alternative for Windows users.
  • Consider adding a note that Azure CLI is recommended for Linux/macOS users, while PowerShell is primarily for Windows environments.
  • Ensure that all critical steps have Azure CLI equivalents and that PowerShell is not presented as the default or only option.
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 presents Azure CLI (cross-platform) examples first and Azure PowerShell (Windows-centric) examples second. There are no explicit Windows-only tools or patterns, and Linux/macOS users are not blocked from completing any tasks. Bash commands (git, helm, kubectl) are used for Kubernetes-native steps, which are cross-platform. However, the presence of Azure PowerShell throughout, and its parity with Azure CLI, may create mild friction for Linux/macOS users who may not use PowerShell.
Recommendations
  • Clarify that Azure PowerShell is available cross-platform (via PowerShell Core), but Azure CLI is generally preferred for Linux/macOS users.
  • Consider adding a note or section highlighting that Azure CLI is the recommended tool for Linux/macOS, and PowerShell is optional.
  • Ensure that all bash commands are clearly marked as cross-platform, and avoid implying PowerShell is required for non-Windows users.
  • Optionally, provide explicit bash-only workflows for users who do not wish to use PowerShell.
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 operations (such as installing kubectl and listing available Kubernetes versions), but consistently presents 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 Azure CLI is cross-platform and covers Linux/macOS users. No Windows-only tools or patterns are mentioned outside of PowerShell. No critical tasks are Windows-only, and Linux support is clearly documented in component tables.
Recommendations
  • Explicitly mention that Azure CLI is cross-platform and recommended for Linux/macOS users.
  • Add Bash shell examples for common tasks (e.g., checking Kubernetes version, installing kubectl) to further improve Linux parity.
  • Clarify in relevant sections (e.g., 'Alias minor version', 'Azure portal and CLI versions') that Azure CLI commands work on Linux/macOS.
  • Consider adding a note that Azure PowerShell is primarily for Windows users, while Azure CLI is for all platforms.
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: 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, but does not explicitly mention Linux/macOS compatibility or provide Linux/macOS-specific instructions. All examples are shown generically, but there is a subtle bias in not clarifying that these commands work equally well on Linux/macOS. There are no Windows-specific tools or PowerShell examples, but the lack of explicit Linux/macOS guidance may create minor friction for non-Windows users.
Recommendations
  • Add a note clarifying that Azure CLI and kubectl commands are fully supported on Linux and macOS, not just Windows.
  • Include example commands for Linux/macOS where relevant, such as installation instructions for Azure CLI and jq.
  • Mention any OS-specific prerequisites or differences, if applicable (e.g., how to install Azure CLI or jq on Linux/macOS).
  • Ensure links to Azure CLI installation documentation include Linux/macOS options.
GitHub Create Pull Request