← Back to Dashboard
118
Pages Scanned
10
Pages Flagged
118
Changed Pages
8.5%
% Pages Flagged

Live Progress

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

Scan Information

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

Finished At: In Progress

Status: in_progress

Target Repo: Azure Aks

Current Phase: discovery

Files Queued: 118

Files Completed: 118

Problematic Pages

10 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 are minor signs of Windows bias. In the section 'Verify TLS Bootstrapping is enabled on current agent node pool', the Windows file path is mentioned immediately after the Linux path, but no explicit example is given for how to check on Windows. Additionally, throughout the document, all command-line examples use Azure CLI and bash/kubectl, which are Linux/macOS-friendly, but there are no PowerShell or Windows Command Prompt examples for Windows users. However, the document does not exclusively favor Windows tools or patterns, and Linux parity is mostly maintained.
Recommendations
  • Provide explicit Windows command examples (e.g., PowerShell or Command Prompt) for checking certificate expiration and TLS Bootstrapping, especially when referencing Windows file paths.
  • Clarify any differences in procedure for Windows node pools, if applicable.
  • When mentioning file paths for both Linux and Windows, consider giving a brief example for each platform.
  • Ensure that all steps that reference file paths or commands are clear for both Linux and Windows users.
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 cross-platform instructions for installing and using the Agentic CLI for AKS, but in the Docker daemon startup section, Windows/macOS instructions (Docker Desktop) are mentioned before Linux instructions (systemctl). All other examples and commands are platform-neutral (Azure CLI, Docker, kubectl), and Linux-specific guidance is present where relevant.
Recommendations
  • In the 'Start the Docker daemon' section, present Linux instructions before or alongside Windows/macOS instructions, or clarify that all platforms are equally supported.
  • Consider explicitly stating that all commands (Azure CLI, Docker, kubectl) work on Linux, macOS, and Windows, and provide links to platform-specific installation guides where relevant.
  • If possible, add a brief note that Docker Desktop is not available on Linux, and that Linux users should use systemd/systemctl.
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_missing ⚠ī¸ minor_windows_tools
Summary
The documentation provides troubleshooting steps for the agentic CLI for AKS, with Docker-related issues addressed for macOS/Windows and Linux separately. Windows and macOS instructions are grouped together and presented before Linux in several places. There are no PowerShell-specific examples, but Windows users are directed to use Docker Desktop, a Windows/macOS-specific tool, while Linux users are given command-line instructions. All Azure CLI and Kubernetes commands are cross-platform. No critical troubleshooting steps are Windows-only, and Linux parity is generally maintained.
Recommendations
  • Where possible, provide Linux instructions before or alongside Windows/macOS instructions, rather than after.
  • Explicitly mention that Docker Desktop is not available for Linux and clarify alternatives for Linux users.
  • Consider adding PowerShell examples for Windows users if Bash is not the default shell, or clarify that Bash commands work in Windows Terminal.
  • Ensure that all troubleshooting steps are equally detailed for Linux, macOS, and Windows users.
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 largely platform-agnostic, focusing on Azure CLI and Bicep for managing the Dapr extension on AKS and Arc-enabled Kubernetes clusters. However, there is a minor Windows bias in the CRD deletion section, where the example for listing CRDs uses PowerShell's 'findstr' command with 'kubectl', which is Windows-specific. This command is shown without a Linux/macOS alternative (e.g., using 'grep'). Additionally, the PowerShell example is presented first and exclusively in that context.
Recommendations
  • Provide Linux/macOS equivalents for commands that use Windows-specific tools (e.g., show 'kubectl get crds | grep dapr.io' alongside the PowerShell 'findstr' example).
  • When giving shell command examples, consider presenting both Windows and Linux/macOS versions, or use cross-platform commands where possible.
  • Explicitly state that the command works on Windows and provide alternatives for other platforms to improve accessibility.
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 parallel approaches: Azure portal, Azure PowerShell, and Azure CLI. The PowerShell section is prominent and detailed, with explicit instructions for installation and usage across Windows, macOS, and Linux. However, PowerShell is a Windows-centric tool, and its section appears before the Azure CLI, which is more native to Linux/macOS users. There are no missing Linux examples, as Azure CLI is included and installation links for PowerShell on Linux/macOS are present. The ordering and emphasis on PowerShell may create minor friction for Linux/macOS users.
Recommendations
  • Consider placing the Azure CLI section before the Azure PowerShell section, as CLI is more cross-platform and native to Linux/macOS.
  • Explicitly mention that Azure CLI is recommended for Linux/macOS users.
  • Add a short note clarifying that PowerShell is available cross-platform, but Azure CLI is often preferred on Linux/macOS.
  • Ensure that all code blocks and instructions are equally clear for both CLI and PowerShell users.
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 tasks, but consistently mentions Azure PowerShell alongside Azure CLI and portal as ways to create an AKS cluster. In the section on listing subnets, both Azure CLI and PowerShell are referenced, but PowerShell is mentioned after Azure CLI. No PowerShell-specific examples are shown for core AKS operations, which are all demonstrated with kubectl and Azure CLI. There are no Linux/macOS-specific examples or explicit parity notes, but the overall guidance is cross-platform, with only minor bias toward Windows tools.
Recommendations
  • Clarify that Azure PowerShell is optional and primarily for Windows users; consider listing Azure CLI first in all cases.
  • Add explicit notes that Azure CLI and kubectl commands work on Linux/macOS as well as Windows.
  • Where PowerShell is mentioned, provide equivalent Bash or shell scripting examples for Linux/macOS users.
  • Consider removing PowerShell references from core AKS workflow unless a Windows-specific scenario is being described.
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 examples, which are cross-platform, and includes kubectl commands that work on Linux/macOS/Windows. However, all CLI examples are shown in the Azure CLI interactive block, which may be perceived as Windows-first due to the historical association of Azure CLI with Windows/PowerShell. There are no PowerShell-specific commands or Windows-only tools mentioned, and Linux/macOS users can complete all tasks as described. The order of examples does not explicitly favor Windows, but there is a minor bias in not mentioning Linux/macOS usage or shell compatibility.
Recommendations
  • Explicitly state that Azure CLI and kubectl commands are cross-platform and work on Linux/macOS/Windows.
  • Add a note or section clarifying that all examples are compatible with Bash, Zsh, and other common Linux/macOS shells.
  • Consider including example commands for Bash and PowerShell if there are any syntax differences.
  • Mention that Azure CLI can be installed and used on Linux/macOS, linking to installation instructions.
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 consistently presents Azure CLI (Linux/macOS-friendly) first, followed by Azure PowerShell (Windows-centric). However, there is a slight bias in the troubleshooting section where PowerShell is given equal prominence, and no explicit Linux/macOS shell example (e.g., Bash) is provided for retrieving the public IP address. All other instructions are portal-based and platform-neutral.
Recommendations
  • Add explicit Bash shell examples for Linux/macOS users to retrieve their public IP address (e.g., `curl ifconfig.me`).
  • Clarify that Azure CLI commands work cross-platform and can be run in Bash, Zsh, or other shells.
  • Consider mentioning that Azure PowerShell is primarily for Windows users, while Azure CLI is cross-platform.
  • If possible, provide a table or clear separation of instructions for Windows, Linux, and macOS users.
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 included throughout. There is a minor bias in that PowerShell is featured heavily, and the documentation sometimes lists PowerShell before Linux-native tools or patterns. No critical Linux/macOS friction is present, as Azure CLI is fully supported cross-platform and all tasks can be completed with CLI or portal.
Recommendations
  • Consider listing Azure CLI examples before Azure PowerShell in each section, as CLI is cross-platform and more widely used on Linux/macOS.
  • Explicitly note that Azure CLI is recommended for Linux/macOS users, and PowerShell is primarily for Windows users.
  • Where possible, clarify that Azure PowerShell is available cross-platform, but is most commonly used on Windows.
  • Ensure that all screenshots and output examples are not Windows-specific (e.g., avoid PowerShell console screenshots unless necessary).
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 tasks, but consistently presents Azure CLI (which is cross-platform) before Azure PowerShell (which is Windows-centric). There are no explicit Windows-only tools or commands, and Linux/macOS users are not excluded from any steps. Bash commands are used for Helm and kubectl operations, which are cross-platform. However, the PowerShell examples are unnecessary for Linux/macOS users, and their inclusion may create minor friction or confusion.
Recommendations
  • Clearly indicate that Azure PowerShell is primarily for Windows users, and Azure CLI is recommended for Linux/macOS.
  • Consider grouping Azure CLI and PowerShell examples under separate headings, or use tabs labeled 'Windows' and 'Linux/macOS' to clarify relevance.
  • Add a note at the top of the page stating that Azure CLI is cross-platform and preferred for Linux/macOS.
  • Optionally, provide only Azure CLI examples in the main flow, with PowerShell examples in a separate section for Windows users.
GitHub Create Pull Request