← Back to Dashboard
109
Pages Scanned
13
Pages Flagged
109
Changed Pages
11.9%
% Pages Flagged

Live Progress

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

Scan Information

Started At: 2026-02-11 00:00:06

Finished At: In Progress

Status: in_progress

Target Repo: Azure Aks

Current Phase: discovery

Files Queued: 109

Files Completed: 109

Problematic Pages

13 issues found
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 is a minor bias in the section 'Verify TLS Bootstrapping is enabled on current agent node pool', where the Windows file path ('C:\k\bootstrap-config') is mentioned after the Linux path. Additionally, in the example output for certificate signing requests, Windows node names (e.g., 'akswinp7000000') are shown, but Linux equivalents are not. All command-line examples use Azure CLI and bash, which are cross-platform, and most instructions are Linux-centric.
Recommendations
  • When showing example output, include both Linux and Windows node names for parity.
  • In the 'Verify TLS Bootstrapping' section, mention Linux file paths first, as AKS is primarily Linux-based.
  • Explicitly state that all commands are applicable to both Linux and Windows node pools unless otherwise noted.
  • Add clarifications or links for Windows users on how to run bash commands (e.g., using WSL or Azure Cloud Shell).
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 covers both Windows/macOS and Linux environments. However, in several sections, Windows/macOS instructions (e.g., 'Launch Docker Desktop') are listed before Linux equivalents, and Linux-specific solutions are sometimes less detailed or presented after Windows steps. There are no PowerShell examples, but Windows tools (Docker Desktop) are mentioned before Linux commands. Azure CLI examples are platform-neutral, but some troubleshooting steps (e.g., Docker permission issues) are more detailed for Linux. Overall, Linux users are supported but not always given equal prominence.
Recommendations
  • Present Linux and Windows/macOS troubleshooting steps in parallel or with equal prominence, rather than listing Windows/macOS first.
  • Add more detailed Linux troubleshooting steps where appropriate (e.g., for Docker Desktop alternatives on Linux).
  • Where possible, clarify which steps apply to all platforms and which are platform-specific.
  • Consider including explicit macOS/Linux/Windows tabs or sections for clarity.
  • Ensure Linux examples are as comprehensive as Windows/macOS 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: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides installation and usage instructions for the agentic CLI for AKS, with a focus on Azure CLI commands. While most steps are cross-platform, there is a subtle Windows bias in the Docker daemon startup instructions: 'macOS/Windows' users are told to launch Docker Desktop, while Linux users are given explicit shell commands. Additionally, the verification step for client mode cleanup uses 'ls ~/.azure/aksAgent.config', which is Unix-specific and may not work on Windows. No PowerShell examples are provided, but Windows users are implicitly assumed to use Docker Desktop, which may not be the only option. The ordering of instructions sometimes puts Windows/macOS first. Overall, the bias is minor and does not prevent Linux/macOS users from completing the tasks.
Recommendations
  • Provide explicit instructions for starting Docker daemon on Windows (e.g., using Windows Services or PowerShell, not just Docker Desktop).
  • Clarify the location of configuration files for Windows users (e.g., mention %USERPROFILE%\.azure\aksAgent.config).
  • Include PowerShell examples for Windows users where shell commands are given for Linux/macOS.
  • Ensure all file path examples are cross-platform or provide alternatives for Windows.
  • Where possible, avoid ordering instructions as 'macOS/Windows' first; consider 'Linux/macOS/Windows' or platform-neutral ordering.
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 (Linux/macOS-friendly) and Azure PowerShell (Windows-centric) examples for troubleshooting, but consistently presents PowerShell examples immediately after CLI and gives them equal prominence. There are no Windows-only tools or patterns, but the PowerShell tab is always present, which may create minor friction for Linux/macOS users. All YAML examples and portal instructions are platform-neutral, and the Azure CLI is featured first, but parity is not perfect.
Recommendations
  • Consider clarifying that Azure PowerShell is primarily for Windows users, and Azure CLI is cross-platform.
  • Add explicit notes or tips for Linux/macOS users, e.g., 'Azure CLI works on Linux, macOS, and Windows.'
  • If possible, provide Bash shell examples for IP retrieval (e.g., using curl or wget) alongside Azure CLI.
  • Review tab order and ensure Azure CLI is always shown first, with PowerShell as an optional alternative.
  • Mention that Cloud Shell supports both Bash and PowerShell, and users can select their preferred environment.
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. However, PowerShell is a Windows-centric tool, and its section appears before the Azure CLI section, which is more native to Linux/macOS environments. There is a minor bias in presenting PowerShell before CLI and giving PowerShell-specific guidance, but Linux/macOS users are not blocked and can use Azure CLI.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is more cross-platform and native for Linux/macOS users.
  • Explicitly mention that Azure CLI is recommended for Linux/macOS users.
  • Add a note clarifying that PowerShell is available cross-platform, but Azure CLI is often preferred on Linux/macOS.
  • Ensure parity in example depth and clarity 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 generally cross-platform, focusing on Azure CLI and Bicep for installation and management, which are available on both Windows and Linux/macOS. However, there is a minor bias in the 'Listing the CRDs in your cluster' section, where only a Windows/PowerShell example (using 'findstr') is provided for filtering CRDs, and no Linux/macOS equivalent (e.g., using 'grep') is shown. Additionally, the PowerShell example is presented without alternatives, which may create friction for non-Windows users.
Recommendations
  • Add Linux/macOS equivalents for command examples, especially for filtering CRDs (e.g., 'kubectl get crds | grep dapr.io').
  • Where possible, present cross-platform commands side-by-side or note the differences.
  • Review other sections for similar single-platform command patterns and provide parity.
  • Consider a short note clarifying that Azure CLI and Bicep are available on all major OS platforms.
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 and often mentioned alongside or after Azure CLI. The Azure CLI is used for all main walkthrough steps, but PowerShell is referenced in the 'Before you begin' section and for subnet listing. There are no Linux/macOS-specific examples, but the CLI commands are cross-platform. Windows tools (PowerShell) are mentioned, and in some cases, Windows/PowerShell is referenced before Linux alternatives. However, the main workflow uses kubectl and Azure CLI, which are cross-platform.
Recommendations
  • Where PowerShell is mentioned, clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Consider providing explicit Bash/Linux shell examples for any Azure CLI commands that use variables or scripting.
  • If referencing PowerShell, always mention the Linux/macOS equivalent (Azure CLI or Bash) first.
  • Remove PowerShell references where not strictly necessary, or add parity for Linux/macOS users.
  • Add a note early in the document stating that Azure CLI is recommended 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: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation primarily uses Azure CLI examples, which are cross-platform, and includes kubectl commands that are standard on Linux/macOS. However, all CLI examples are shown using the Azure CLI, and there is no mention of PowerShell or Windows-specific tools. The order of examples does not favor Windows, but the use of Azure CLI may be perceived as slightly Windows-first, since some users associate CLI usage with Windows environments, though Azure CLI is fully cross-platform. No Linux-specific commands or package manager instructions (e.g., apt, yum, brew) are provided, but none are needed for the described tasks.
Recommendations
  • Explicitly state that Azure CLI and kubectl commands work on Windows, Linux, and macOS.
  • Add a note clarifying that Azure CLI can be installed on Linux/macOS and provide a link to installation instructions for those platforms.
  • Ensure parity by mentioning that all commands are cross-platform and do not require Windows.
  • If possible, provide alternative instructions for users who prefer using Bash scripts or native Linux tools for automation.
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 ⚠ī¸ windows_tools
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 a dedicated section immediately after the Linux section. Windows tools and concepts (like HNS ACLPolicies) are mentioned alongside Linux equivalents (IPTables), and Windows node pool support is discussed in the context of Calico and Azure NPM. However, Linux instructions and examples are generally present and complete, and the page is not Windows-only.
Recommendations
  • Ensure Linux and Windows instructions are equally prominent and parallel in structure.
  • When describing network policy engines, list Linux and Windows support together rather than Windows-specific features first.
  • Where possible, provide Linux and Windows examples side-by-side, especially for cluster creation and network policy application.
  • Clarify when steps are Windows-specific to avoid confusion for Linux users.
  • Consider adding explicit notes or tables summarizing feature parity and limitations for both OSes.
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 instructions for resource cleanup, but lists Azure CLI first. The prerequisites mention both Azure CLI and Azure PowerShell, but do not show any Linux-specific shell or tool examples. All command-line examples use Bash syntax (compatible with Linux/macOS), and there are no PowerShell-specific examples for the main workflow. No Windows-only tools are referenced, and the workflow is cross-platform. However, the presence of Azure PowerShell instructions and its mention in prerequisites may slightly favor Windows users.
Recommendations
  • Clarify that all Bash commands work on Linux/macOS and Windows (with WSL or Git Bash), and explicitly mention cross-platform compatibility.
  • Consider listing Azure CLI as the default/primary method for resource management, with PowerShell as an alternative, and clarify that Azure CLI is cross-platform.
  • Add a note in the prerequisites that Azure CLI is recommended for Linux/macOS users, while Azure PowerShell is primarily for Windows.
  • Ensure parity in examples: if PowerShell is shown for cleanup, consider showing Bash alternatives for all steps, or clarify that Azure CLI is preferred for non-Windows platforms.
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 tasks, but consistently presents Azure CLI (which is cross-platform) before Azure PowerShell (which is Windows-centric). There are no explicit Linux/macOS-specific examples or notes, but the CLI instructions are suitable for Linux/macOS. Bash commands are used for Helm and git operations, which are platform-neutral. No Windows-only tools or patterns are mentioned, and no critical steps are Windows-exclusive.
Recommendations
  • Explicitly state that Azure CLI commands are cross-platform and recommended for Linux/macOS users.
  • Add a note clarifying that Azure PowerShell is primarily for Windows users, while Azure CLI works on all platforms.
  • Consider including a brief section or callout for Linux/macOS users, confirming that all CLI steps are compatible.
  • Ensure that any references to PowerShell do not imply it is required for Linux/macOS users.
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 (user namespaces, AppArmor, seccomp), and explicitly states these are Linux-only. However, in prerequisite sections, Windows tools (Azure PowerShell) are mentioned alongside Azure CLI and Portal, and are listed before Linux equivalents in some places. All technical examples, commands, and walkthroughs are Linux-centric, with no Windows-specific instructions or tools used for the main tasks. No PowerShell-only examples or Windows tools are used for the actual security configuration.
Recommendations
  • In prerequisite lists, mention Azure CLI before Azure PowerShell to prioritize Linux-native tooling.
  • Clarify that Azure PowerShell is optional and not required for Linux users.
  • Consider adding a note that all technical steps are Linux-only and Windows node pools are not supported for these features, to avoid confusion.
  • If possible, provide links to Linux-specific quickstart guides before Windows/PowerShell equivalents.
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 (which is most commonly used on Windows) is given equal prominence to Azure CLI, and PowerShell examples are provided throughout. In some sections, PowerShell is listed before the portal, and the 'devx-track-azurepowershell' custom metadata suggests a PowerShell focus. There are no missing Linux examples, as Azure CLI is fully supported on Linux/macOS and is always included. No Windows-only tools or patterns are mentioned outside of PowerShell.
Recommendations
  • Consider listing Azure CLI examples before Azure PowerShell in each section, as CLI is cross-platform and more commonly used by Linux/macOS users.
  • Explicitly note that Azure CLI commands work on Linux/macOS, and that Azure PowerShell is available on Linux/macOS (if true), to avoid implicit Windows bias.
  • If possible, add a short note or section for users who prefer Bash scripting or other Linux-native tools, clarifying that Azure CLI is the recommended cross-platform approach.
  • Review metadata and page structure to ensure CLI is not deprioritized in favor of PowerShell.
GitHub Create Pull Request