← Back to Dashboard
94
Pages Scanned
10
Pages Flagged
94
Changed Pages
10.6%
% Pages Flagged

Scan Information

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

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

Status: completed

Target Repo: Azure Aks

Current Phase: discovery

Files Queued: 94

Files Completed: 94

Problematic Pages

10 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: 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 examples and guidance for both client and cluster modes. While the CLI itself is cross-platform and most instructions are generic, there are subtle signs of Windows bias: in the Docker startup instructions, macOS/Windows steps (Docker Desktop) are described before Linux (systemctl), and Linux users are given less detail. There are no PowerShell-specific commands, but the ordering and phrasing favor Windows/macOS users. Some verification steps (e.g., checking config file location) assume a default home directory structure typical of Windows/macOS. Linux-specific troubleshooting or alternative commands (e.g., service management, file locations) are not always included.
Recommendations
  • Present Linux instructions alongside or before Windows/macOS steps, especially for Docker startup and verification.
  • Include explicit Linux command-line examples for all steps, such as checking config file locations and cleaning up Docker images.
  • Clarify differences in file paths and environment setup for Linux users.
  • Add troubleshooting tips for common Linux issues (e.g., permissions, systemd status).
  • Ensure parity in detail and clarity for Linux/macOS instructions compared to Windows.
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 guidance, but in several troubleshooting steps, Windows and macOS instructions (e.g., 'Launch Docker Desktop') are listed before Linux equivalents. The documentation refers to 'Docker Desktop' as the solution for Windows/macOS, which is a Windows/macOS-specific tool, while Linux users are given systemd-based instructions. In some cases, Windows and macOS are grouped together, and Linux is addressed separately, with Windows instructions appearing first. All command-line examples are cross-platform (bash, Azure CLI, kubectl), and there are no PowerShell-specific commands or Windows-only command syntax.
Recommendations
  • Alternate the order of platform instructions, or present all platforms in parallel (e.g., with tabs for Windows, macOS, Linux) to avoid consistently listing Windows/macOS first.
  • Explicitly mention Linux GUI options for Docker if available, or clarify that Docker Desktop is not available on Linux.
  • Where possible, provide parity in troubleshooting steps (e.g., if a GUI tool is mentioned for Windows/macOS, suggest equivalent Linux tools or clarify their absence).
  • Consider using headings or callouts for each OS to make parity clear.
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 three main approaches for configuring Azure CNI networking in AKS: Azure portal, Azure PowerShell, and Azure CLI. The PowerShell section is detailed and references Windows-centric tooling, but it does mention installation and usage on macOS and Linux. The PowerShell example appears before the CLI example, which is more cross-platform. There are no explicit Linux/macOS examples or screenshots, and PowerShell is generally perceived as a Windows-first tool, despite its cross-platform support.
Recommendations
  • Add explicit Linux/macOS command-line examples or notes, especially for Azure CLI usage.
  • Clarify that Azure PowerShell can be used on Linux/macOS and provide more parity in instructions (e.g., shell commands for Linux/macOS environments).
  • Consider presenting Azure CLI examples before PowerShell, as CLI is more universally available and preferred on Linux/macOS.
  • Include troubleshooting or environment setup notes for Linux/macOS users, such as SSH key generation and shell differences.
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 is generally cross-platform and focuses on Kubernetes and Azure CLI, which are available on Linux, macOS, and Windows. However, there are minor instances of Windows bias: (1) PowerShell is mentioned as an option for creating an AKS cluster and for listing subnets, and (2) Windows/PowerShell tools are referenced before or alongside Azure CLI equivalents, rather than after or in parity with Linux/macOS tools.
Recommendations
  • When listing options for creating AKS clusters or managing resources, present Azure CLI (cross-platform) first, then PowerShell (Windows-centric) as an alternative.
  • Where PowerShell commands are referenced (e.g., for listing subnets), ensure that Azure CLI equivalents are shown first and clearly marked as cross-platform.
  • Consider adding explicit notes that Azure CLI works on Linux/macOS/Windows, and PowerShell is primarily for Windows users.
  • If PowerShell is mentioned, provide equivalent Bash or shell commands for Linux/macOS users, or clarify that PowerShell Core is available cross-platform if relevant.
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 focused on Azure CLI and Bicep, which are available on Windows, Linux, and macOS. However, there is a minor Windows bias in the example for listing Dapr CRDs, where the command uses 'findstr' (a Windows-only tool) with kubectl, and this is the only example given for filtering CRDs. Additionally, the use of PowerShell syntax (e.g., environment variable assignment with $MY_RESOURCE_GROUP) appears before any mention of Linux/macOS alternatives, which may cause friction for non-Windows users.
Recommendations
  • Provide Linux/macOS equivalent commands for filtering CRDs, such as 'kubectl get crds | grep dapr.io'.
  • When showing environment variable assignment, include both PowerShell (Windows) and Bash (Linux/macOS) syntax, or use tabs to separate them.
  • Explicitly state that Azure CLI and Bicep are cross-platform, and provide links or notes for installing them on Linux/macOS.
  • Review all command examples to ensure they are not Windows-specific unless necessary.
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) instructions for managing AKS cluster authorized IP ranges. However, PowerShell examples are presented immediately after CLI examples and with equal prominence, which may subtly reinforce Windows tooling. The documentation does not provide any Windows-only examples, nor does it omit Linux/macOS equivalents, but the inclusion and ordering of PowerShell instructions could be seen as a minor Windows-first bias.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, while PowerShell is primarily for Windows users.
  • Consider listing Azure CLI instructions first and clarifying its cross-platform nature.
  • Add a note that PowerShell is optional and mainly for users on Windows, while CLI is recommended for Linux/macOS.
  • Ensure screenshots and UI references do not assume a Windows environment (e.g., avoid showing Windows-specific browser or OS elements).
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 mentions Azure CLI, Azure PowerShell, and Azure Portal as options for creating AKS clusters, listing Azure PowerShell before Linux-native alternatives. However, all configuration, verification, and troubleshooting examples use Azure CLI and kubectl, which are cross-platform tools. No PowerShell-specific commands or Windows-only tools are used in the main workflow. There are no examples or instructions that are exclusive to Windows, nor are Linux/macOS users disadvantaged in following the guide.
Recommendations
  • List Azure CLI before Azure PowerShell when presenting options for cluster creation, as CLI is cross-platform and preferred by Linux/macOS users.
  • Explicitly state that all shown commands (Azure CLI, kubectl) work on Linux, macOS, and Windows.
  • Consider providing a brief note that PowerShell is primarily for Windows users, and recommend Azure CLI for Linux/macOS users.
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 parallel examples for both Azure CLI and Azure PowerShell throughout, but consistently lists Azure PowerShell (a Windows-centric tool) as an equal alternative to Azure CLI, and sometimes before Linux-native workflows. There are no explicit Linux/macOS-specific instructions or troubleshooting tips, and PowerShell is presented as a first-class option, which may create friction for Linux/macOS users unfamiliar with PowerShell.
Recommendations
  • Clearly indicate that Azure CLI is cross-platform and preferred for Linux/macOS users, while Azure PowerShell is primarily for Windows.
  • Add notes or callouts specifying that PowerShell examples are intended for Windows users, and that CLI examples are recommended for Linux/macOS.
  • Consider listing Azure CLI examples before PowerShell examples, or defaulting to CLI in mainline instructions, with PowerShell as an alternative.
  • Include troubleshooting tips or links for Linux/macOS users (e.g., common issues with Azure CLI installation, SSH key generation, etc.).
  • Explicitly mention that Azure Cloud Shell is available cross-platform and can be used from any OS.
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 presents both Azure CLI and Azure PowerShell as options for resource management, but PowerShell is mentioned alongside CLI in prerequisites and is given its own example in the clean-up section. The ordering of examples and references sometimes places Windows/PowerShell tools before Linux-native equivalents, which may subtly suggest a Windows-first approach. However, all critical steps (deployment, configuration, verification) use cross-platform tools (kubectl, curl, git), and no steps are Windows-only.
Recommendations
  • List Azure CLI before Azure PowerShell in prerequisites and example tabs, as CLI is cross-platform and preferred for Linux/macOS users.
  • Explicitly state that all kubectl and curl commands work on Linux/macOS, and provide any necessary notes for platform differences if applicable.
  • Consider adding a note clarifying that Azure PowerShell is optional and primarily for Windows users, while Azure CLI is recommended for Linux/macOS.
  • Ensure that example tabs for resource deletion (and other management tasks) default to Azure CLI, with PowerShell as a secondary option.
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
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all major steps, with Azure CLI (cross-platform) examples consistently shown first. Azure PowerShell (Windows-centric) is given equal prominence, but there are no Linux/macOS-specific shell examples (e.g., Bash scripts) beyond the CLI. There is no evidence of exclusive use of Windows tools or missing Linux examples, as Azure CLI is fully supported on Linux/macOS. The documentation avoids Windows-only tools and does not mention Windows patterns before Linux equivalents.
Recommendations
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows, and that PowerShell examples are primarily for Windows users.
  • Consider adding brief notes or links for Linux/macOS users about installing Azure CLI and using Bash/zsh, especially in the 'Before you begin' section.
  • If relevant, provide example shell scripts for common Linux/macOS workflows (e.g., using Bash for automation).
  • Explicitly state that Azure PowerShell is optional and not required for Linux/macOS users.
GitHub Create Pull Request