← Back to Dashboard
115
Pages Scanned
12
Pages Flagged
115
Changed Pages
10.4%
% Pages Flagged

Live Progress

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

Scan Information

Started At: 2026-02-14 00:00:30

Finished At: In Progress

Status: in_progress

Target Repo: Azure Aks

Current Phase: discovery

Files Queued: 115

Files Completed: 115

Problematic Pages

12 issues found
Aks Develop on Azure Kubernetes Service (AKS) with Helm ...ure-aks-docs/blob/main/articles/aks/quickstart-helm.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides parallel Azure CLI and Azure PowerShell instructions for all Azure-related steps, but PowerShell is featured equally alongside CLI. There are no Windows-only tools or patterns, but PowerShell is a Windows-centric tool and is presented as a primary option. The document does not provide Linux-specific shell examples (e.g., Bash for Azure CLI) or highlight Linux/macOS parity. Azure CLI is cross-platform, but PowerShell is not as widely used on Linux/macOS. The ordering of examples is neutral, but the presence of PowerShell throughout may create friction for Linux/macOS users.
Recommendations
  • Clarify that Azure CLI is the recommended cross-platform tool for Linux/macOS users.
  • Consider adding explicit Bash shell examples for Azure CLI commands to reinforce Linux/macOS parity.
  • Mention that Azure PowerShell is primarily for Windows users, and provide guidance for Linux/macOS users to use Azure CLI.
  • Add notes or callouts where PowerShell is used, indicating alternative approaches for Linux/macOS users.
  • Ensure that all steps can be completed using Azure CLI alone, and highlight this in the prerequisites.
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 engines, but Windows-specific instructions (such as administrator credential setup and feature flag registration) are given their own section and are presented immediately after the Linux section. Windows node pool creation steps are detailed, including Azure CLI commands and environment variable setup, while Linux steps are similar but less emphasized. The documentation mentions Windows-specific tools (HNS ACLPolicy) alongside Linux tools (IPTables), but does not prioritize Windows tools over Linux. All CLI examples use Azure CLI and Bash, which are cross-platform, but Bash is shown as the default shell for environment variable setup, which may not be native on Windows.
Recommendations
  • Clarify that Bash commands are cross-platform and provide PowerShell equivalents for Windows users where relevant.
  • Ensure Linux and Windows instructions are equally detailed and presented in parallel, rather than sequentially.
  • Add explicit notes about how Windows users can run Bash commands (e.g., via WSL or Git Bash) or provide alternative PowerShell syntax.
  • Consider a tabbed interface for Linux/Windows steps to improve clarity and parity.
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 both Linux and Windows/macOS instructions for Docker daemon startup, but Windows/macOS instructions are listed first. All CLI examples use cross-platform Azure CLI and Bash commands, and there are no PowerShell or Windows-specific tools mentioned. The documentation is largely platform-neutral, but the ordering of instructions shows a minor Windows bias.
Recommendations
  • List Linux instructions before Windows/macOS, or group all OS instructions together for Docker daemon startup.
  • Explicitly mention that all Azure CLI and Bash commands are cross-platform and provide links to platform-specific installation guides if needed.
  • Ensure parity in troubleshooting and cleanup verification steps by referencing both Linux and Windows/macOS file paths and commands where applicable.
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 instances of Windows bias. In the 'Verify TLS Bootstrapping is enabled on current agent node pool' section, the Windows file path is listed after the Linux path, but no command-line example is provided for Windows users (e.g., how to check the file exists). All command examples use Bash or Azure CLI, which are cross-platform, but there are no PowerShell or Windows CMD examples for Windows users. The documentation does not mention Windows tools or patterns exclusively, nor does it prioritize Windows-specific instructions over Linux ones.
Recommendations
  • Add explicit Windows command-line examples (e.g., PowerShell or CMD) for checking file existence at 'C:\k\bootstrap-config'.
  • Clarify that Azure CLI and kubectl commands work on Windows, and provide any necessary Windows-specific flags or considerations.
  • Consider including a note or example for Windows users on how to decode base64 or use openssl if not installed.
  • Ensure parity in troubleshooting steps for both Linux and Windows nodes where applicable.
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 parallel instructions for Azure portal, Azure PowerShell, and Azure CLI. However, the PowerShell section is notably detailed, with explicit instructions for installation and version checks, and is presented before the CLI section. The PowerShell instructions reference Windows tools and patterns, but do include links for macOS and Linux installation. The CLI section is less detailed and does not mention OS-specific considerations. There are no missing Linux examples, but the prominence and detail of PowerShell instructions may create a perception of Windows bias.
Recommendations
  • Expand Azure CLI instructions to include OS-specific installation and troubleshooting links for Linux/macOS, similar to the PowerShell section.
  • Ensure that CLI examples are as detailed as PowerShell examples, including version checks and environment preparation.
  • Consider presenting CLI instructions before PowerShell, or at least in parallel, to avoid 'windows_first' bias.
  • Add explicit notes that both PowerShell and CLI are fully cross-platform, and highlight Linux/macOS parity where relevant.
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 Azure PowerShell and its cmdlets alongside Azure CLI. In the 'Before you begin' section, Azure PowerShell is mentioned as an option for creating an AKS cluster before Azure CLI and the Azure portal. Additionally, the PowerShell cmdlet 'Get-AzVirtualNetworkSubnetConfig' is referenced for listing subnets, but no Linux/macOS equivalent (such as Azure CLI or Bash) is shown alongside it. All main procedural examples use kubectl and Azure CLI, which are cross-platform, but the inclusion and ordering of PowerShell references may create minor friction for Linux/macOS users.
Recommendations
  • When listing options for creating AKS clusters, mention Azure CLI first, as it is cross-platform, followed by Azure PowerShell for Windows users.
  • For listing subnets, provide only Azure CLI examples or clearly indicate that PowerShell is Windows-specific and Azure CLI is recommended for Linux/macOS.
  • If PowerShell is referenced, always provide an Azure CLI equivalent and note platform differences.
  • Consider grouping Windows-specific tools in a separate section or appendix, rather than mixing them with cross-platform options.
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, but in several places, Windows/macOS solutions (e.g., 'Launch Docker Desktop') are mentioned before Linux equivalents. Some instructions for Docker issues are Windows/macOS-centric, and Linux-specific solutions are sometimes secondary. There are no PowerShell-specific commands, but Windows Desktop patterns are referenced. All Azure CLI and kubectl examples are cross-platform, but the ordering and phrasing show a mild Windows bias.
Recommendations
  • Present Linux, macOS, and Windows solutions in parallel or grouped by OS, rather than listing Windows/macOS first.
  • Clarify that Docker Desktop is not available on Linux and provide explicit Linux alternatives (e.g., systemd commands) before or alongside Windows/macOS instructions.
  • Where possible, add notes for Linux-specific troubleshooting steps (e.g., checking Docker group membership, restarting Docker service).
  • Ensure that examples and solutions are equally detailed for all platforms.
  • Avoid phrases like 'On macOS/Windows' unless truly identical; separate instructions for each OS where they differ.
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 and focuses on Azure CLI and Bicep, both of which are available on Windows, Linux, and macOS. However, there is a minor Windows bias in the 'Listing the CRDs in your cluster' section, where the example uses 'kubectl get crds | findstr dapr.io', which relies on the Windows 'findstr' command. No equivalent Linux/macOS example (e.g., using 'grep') is provided, and the PowerShell/Windows syntax is shown first and exclusively in this context.
Recommendations
  • Provide Linux/macOS equivalent commands alongside Windows examples, such as 'kubectl get crds | grep dapr.io'.
  • When showing shell commands, clarify which OS they apply to or use cross-platform syntax where possible.
  • Consider listing both Windows and Linux/macOS command variants in troubleshooting or operational sections.
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: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for managing AKS authorized IP ranges. However, the PowerShell section is presented immediately after the Azure CLI section, and both are given equal prominence. No Linux-specific tools or commands (such as bash or Linux-native utilities) are mentioned, but the Azure CLI example uses 'dig', which is available on Linux/macOS by default. There are no Windows-only tools or patterns, and the documentation is generally neutral and portal-focused. The PowerShell example is not prioritized over the CLI, and Linux users can complete all tasks using the Azure CLI instructions.
Recommendations
  • Explicitly note that Azure CLI commands are cross-platform and suitable for Linux/macOS users.
  • Consider adding a brief note or section clarifying that PowerShell examples are primarily for Windows users, while Azure CLI is recommended for Linux/macOS.
  • If possible, add a bash-only example for retrieving the public IP address (e.g., using 'curl' or 'wget') for Linux/macOS users who may not have 'dig' installed.
  • Ensure that any future troubleshooting steps or examples do not default to Windows tools unless necessary.
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 to AKS cluster creation guides for Azure CLI, Azure PowerShell, and Azure Portal, listing PowerShell before Portal. However, all configuration, verification, and troubleshooting steps use cross-platform tools (Azure CLI, kubectl, YAML), and the feature itself is only supported on Azure Linux or Ubuntu node pools. No Windows-specific tools, patterns, or examples are given, and Linux parity is strong throughout.
Recommendations
  • Consider listing Azure CLI and Portal before PowerShell in the prerequisites to reinforce Linux/macOS parity.
  • Explicitly note that all commands are cross-platform and can be run from Linux, macOS, or Windows environments.
  • Optionally, provide a brief note that PowerShell is primarily for Windows users, while Azure CLI is recommended for all platforms.
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 PowerShell examples are included throughout. Azure CLI is cross-platform, but PowerShell is primarily used on Windows, and its inclusion may create friction for Linux/macOS users. In some sections, PowerShell is listed before Azure portal, but not before Azure CLI. No Windows-specific tools or patterns are mentioned, and Linux/macOS users can complete all tasks using Azure CLI or portal. There are no missing Linux examples, and the documentation does not favor Windows tools exclusively.
Recommendations
  • Clarify that Azure CLI is fully cross-platform and recommended for Linux/macOS users.
  • Consider moving Azure PowerShell examples after Azure CLI and Azure portal, or explicitly note PowerShell is primarily for Windows users.
  • Add a brief note at the start indicating Azure CLI is the preferred tool for non-Windows environments.
  • Ensure all references to PowerShell are accompanied by Azure CLI equivalents (already done here).
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 page is focused on Linux security features for AKS containers, with all technical examples, commands, and walkthroughs targeting Linux environments. However, in several prerequisite sections, Windows tools (Azure PowerShell) are mentioned alongside Azure CLI and Portal, and are listed before Linux equivalents. No PowerShell-specific examples or Windows-only tools are used, and all technical steps are Linux-centric. There are no missing Linux examples, nor are Windows tools used exclusively.
Recommendations
  • In prerequisite lists, consider listing Azure CLI (cross-platform) before Azure PowerShell, or clarifying that PowerShell is primarily for Windows users.
  • Where possible, provide parity in introductory guidance for Linux/macOS users (e.g., highlight Azure CLI as the default for cross-platform scenarios).
  • Explicitly state that all technical steps and examples are Linux-only, and clarify that Windows node pools are not supported for these features.
GitHub Create Pull Request