← Back to Dashboard
152
Pages Scanned
13
Pages Flagged
152
Changed Pages
8.6%
% Pages Flagged

Live Progress

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

Scan Information

Started At: 2026-02-28 00:00:40

Finished At: In Progress

Status: in_progress

Target Repo: Azure Aks

Current Phase: discovery

Files Queued: 152

Files Completed: 152

Problematic Pages

13 issues found
Aks Install Dapr Extension for Azure Kubernetes Service (AKS) ...softDocs/azure-aks-docs/blob/main/articles/aks/dapr.md
Medium 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, which are supported on Windows, Linux, and macOS. However, the only example for listing Dapr CRDs uses a Windows-specific pattern ('kubectl get crds | findstr dapr.io'), and the use of PowerShell-style piping ('| findstr') is shown without a Linux/macOS equivalent (e.g., 'grep'). Additionally, this Windows example appears before any mention of Linux alternatives, which may cause friction for non-Windows users.
Recommendations
  • Provide both Windows and Linux/macOS examples for commands involving shell utilities, such as listing CRDs (e.g., 'kubectl get crds | grep dapr.io' for Linux/macOS).
  • Explicitly state that Azure CLI and Bicep commands are cross-platform and supported on Windows, Linux, and macOS.
  • Where shell commands are given, use tabs or callouts to distinguish between Windows and Linux/macOS usage.
  • Review for other places where Windows-specific syntax or tools (like 'findstr') are used and add Linux/macOS equivalents.
GitHub Create Pull Request
Aks Troubleshoot the Agentic CLI for Azure Kubernetes Service (AKS) .../main/articles/aks/agentic-cli-for-aks-troubleshoot.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation provides troubleshooting steps for the Agentic CLI for AKS, with some bias toward Windows/macOS users. In Docker-related troubleshooting, Windows/macOS solutions (Docker Desktop) are listed before Linux solutions, and restarting Docker Desktop is emphasized for permission issues. No PowerShell commands are present, but Azure CLI and kubectl commands are used throughout, which are cross-platform. However, Windows/macOS tools (Docker Desktop) are mentioned first and more prominently than Linux equivalents. Linux-specific steps are present but often secondary.
Recommendations
  • Present Linux and Windows/macOS troubleshooting steps in parallel or with equal prominence, rather than listing Windows/macOS first.
  • Clarify that Docker Desktop is not available on Linux and provide explicit guidance for Linux users (e.g., systemctl commands) before or alongside Windows/macOS instructions.
  • Where possible, add notes about cross-platform command usage and highlight any OS-specific differences.
  • Consider grouping troubleshooting steps by OS or providing a table for quick reference.
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 Azure CLI is used exclusively for all main examples. However, PowerShell is mentioned first in the 'Before you begin' section, and a PowerShell cmdlet is referenced alongside Azure CLI for subnet listing. There are no Linux/macOS-specific examples or explicit parity guidance, but the main workflow is cross-platform via Azure CLI and kubectl. The bias is minor, mostly in tool mention order and occasional PowerShell references.
Recommendations
  • Mention Azure CLI before PowerShell in prerequisite lists to reflect cross-platform parity.
  • Clarify that Azure CLI and kubectl commands work on Linux, macOS, and Windows.
  • Add explicit notes or links for Linux/macOS users where PowerShell is referenced (e.g., suggest Azure CLI as the primary tool for subnet listing).
  • Consider removing PowerShell references unless a Windows-specific workflow is required.
GitHub Create Pull Request
Aks Install and Use the Agentic CLI for Azure Kubernetes Service (AKS) (Preview) .../blob/main/articles/aks/agentic-cli-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 installation and usage instructions for the Agentic CLI for AKS, supporting both client mode (local Docker) and cluster mode (Helm/Kubernetes). In the section on starting the Docker daemon, instructions for macOS/Windows (Docker Desktop) are presented before Linux (systemctl commands). However, all examples and instructions are cross-platform, and Linux-specific guidance is present where relevant. No PowerShell-specific commands, Windows-only tools, or missing Linux examples are found.
Recommendations
  • Present Linux instructions before or alongside Windows/macOS instructions when describing how to start Docker, to avoid subtle ordering bias.
  • Explicitly mention that all commands are compatible with Linux, macOS, and Windows where applicable.
  • Consider adding a short note clarifying that Docker Desktop is not required on Linux, and that Linux users should use their package manager and systemctl.
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 ⚠ī¸ windows_tools
Summary
The documentation is generally cross-platform and AKS-focused, but there are minor signs of Windows bias. In the section 'Verify TLS Bootstrapping is enabled on current agent node pool', Windows file paths are mentioned alongside Linux, but Windows is listed second. There are no PowerShell-specific commands or Windows-only tools; all CLI examples use Azure CLI and bash/kubectl, which are cross-platform. However, Azure CLI is more natively available on Linux/macOS, and Windows users may need WSL or install bash. The documentation does not provide PowerShell alternatives or Windows command prompt examples, but it does mention Windows node file paths for completeness.
Recommendations
  • Ensure that Windows and Linux file paths are always presented together, and clarify which commands work natively on Windows (e.g., Azure CLI in PowerShell or Command Prompt).
  • Consider adding PowerShell or Windows Command Prompt equivalents for Azure CLI commands where relevant, or clarify that Azure CLI works in all environments.
  • Explicitly state that all examples are cross-platform unless otherwise noted.
  • For file path references, consider listing Windows and Linux paths in parallel, rather than Linux first.
GitHub Create Pull Request
Aks Concepts - Storage in Azure Kubernetes Services (AKS) ...re-aks-docs/blob/main/articles/aks/concepts-storage.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 container examples for volume mounting, but the Windows example is presented immediately after the Linux example without additional context or parity. There are no PowerShell or Windows-specific CLI examples, nor are Windows tools or patterns mentioned preferentially. The only Windows-specific mention is in the context of mounting volumes in Windows containers, which is appropriate and necessary for completeness.
Recommendations
  • Ensure that Linux/macOS and Windows examples are clearly separated and labeled to avoid confusion.
  • If providing Windows-specific examples, consider also providing equivalent Linux/macOS examples side-by-side for clarity.
  • Add clarifying notes when Windows-specific instructions are given, indicating that Linux/macOS users should refer to the preceding example or section.
  • Review the order of examples to ensure Linux/macOS instructions are not consistently shown after Windows instructions unless contextually appropriate.
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 prominent and detailed, and PowerShell is historically associated with Windows, though it is now cross-platform. PowerShell instructions and references are given before Azure CLI, and the PowerShell section includes more guidance about Cloud Shell and local installation. However, the CLI section is present and includes Linux/macOS installation links. No critical steps are Windows-only, and Linux/macOS users can complete all tasks.
Recommendations
  • Ensure parity in example detail between PowerShell and CLI sections (e.g., add more CLI guidance about Cloud Shell usage if relevant).
  • Explicitly mention that both PowerShell and CLI are cross-platform and suitable for Linux/macOS users.
  • Consider showing CLI examples before PowerShell, as CLI is more commonly used on Linux/macOS.
  • Add a brief note clarifying that PowerShell is available on Linux/macOS, to avoid confusion.
GitHub Create Pull Request
Aks Create and Manage Persistent Volumes with Azure Files in Azure Kubernetes Service (AKS) ...cs/blob/main/articles/aks/create-volume-azure-files.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation is generally cross-platform and AKS/Linux-focused, but there are minor signs of Windows bias. Windows path conventions and tools are mentioned in a few places, sometimes before Linux equivalents. In the 'Use Azure Files with Windows containers' section, Windows-specific instructions are provided, but Linux/MacOS Bash is also referenced. In some command examples, Windows paths are shown alongside Linux, but Windows is sometimes listed first. Azure CLI is used throughout, which is available cross-platform, but some commands reference Windows-specific path conventions.
Recommendations
  • When mentioning Windows path conventions or tools, ensure Linux/macOS equivalents are given equal prominence and listed first where appropriate.
  • Where commands differ between platforms, provide both Linux/macOS and Windows examples side-by-side, with clear labeling.
  • Review example outputs and instructions to ensure Linux/macOS users are not confused by Windows-centric language or ordering.
  • Consider adding a short section clarifying cross-platform compatibility for Azure CLI and kubectl commands.
  • In sections where Windows is mentioned, clarify if the instructions are Windows-only or if Linux/macOS users should follow different steps.
GitHub Create Pull Request
Aks Move Azure Disk persistent volumes to another AKS cluster in the same or a different subscription .../blob/main/articles/aks/csi-disk-move-subscriptions.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation references Azure PowerShell as a migration option alongside Azure CLI and Azure Portal, but does not provide Linux-specific guidance or examples for PowerShell usage. Azure CLI is used for all command-line examples, which is cross-platform, but the mention of Azure PowerShell as a migration tool without clarifying Linux/macOS support or providing parity examples may create confusion. Additionally, the order of tools listed (Portal, PowerShell, CLI) puts Windows-centric tools before CLI, which is more universal.
Recommendations
  • Clarify that Azure PowerShell is available on Linux/macOS and provide installation/use guidance if relevant.
  • Consider listing Azure CLI before Azure PowerShell in tool options, as CLI is more universally supported.
  • If PowerShell is mentioned, provide explicit Linux/macOS usage instructions or note any limitations.
  • Ensure that all example commands use cross-platform tools (Azure CLI, kubectl), as is currently done.
  • Add a brief note that all steps are applicable to Linux/macOS unless otherwise stated.
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 cluster authorized IP ranges, but consistently presents Azure CLI (Linux/macOS-friendly) examples first. However, PowerShell examples are also included, and no Windows-specific tools or patterns are mentioned exclusively. The rest of the documentation is portal-centric and platform-neutral, with YAML examples targeting Linux node pools. There is no missing Linux example or Windows-only tool bias.
Recommendations
  • Maintain Azure CLI examples as the primary cross-platform option, but clarify that Azure CLI works on Windows, Linux, and macOS.
  • Consider adding a brief note that Azure PowerShell is primarily used on Windows but can also be run on Linux/macOS if needed.
  • Ensure that all CLI instructions are explicitly cross-platform, and avoid implying PowerShell is required for Windows users.
  • If possible, add a Bash example for IP retrieval (e.g., `curl ifconfig.me`) for Linux/macOS users alongside the Azure CLI example.
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 does not offer Linux-specific shell examples (e.g., Bash scripts for Azure CLI usage) or mention Linux/macOS-specific patterns. Azure PowerShell is featured equally alongside Azure CLI, which is more commonly used on Windows. The ordering of examples sometimes puts Azure CLI first, but PowerShell is always present. There are no Windows-only tools or commands, but the PowerShell parity may create friction for Linux/macOS users unfamiliar with PowerShell.
Recommendations
  • Clarify that Azure CLI commands are cross-platform and can be used on Linux/macOS as well as Windows.
  • Consider adding explicit Bash shell examples for Azure CLI usage, or note that Azure CLI commands can be run in Bash, Zsh, or other Unix shells.
  • De-emphasize Azure PowerShell for general-purpose AKS/Helm workflows unless there is a Windows-specific need.
  • Add notes or guidance for Linux/macOS users about installing Azure CLI and Helm on their platforms.
  • Ensure that any references to Azure Cloud Shell mention its availability from Linux/macOS browsers.
GitHub Create Pull Request
Aks Kubernetes on Azure tutorial - Create an Azure Kubernetes Service (AKS) cluster ...ain/articles/aks/tutorial-kubernetes-deploy-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 parallel instructions for Azure CLI, Azure PowerShell, and Azure Developer CLI, but PowerShell is featured prominently and is presented as an equal alternative to Azure CLI. PowerShell is primarily a Windows tool, and its inclusion may signal a Windows-centric approach. However, Azure CLI instructions are present and are suitable for Linux/macOS users. There are no missing Linux examples, and the tools used (Azure CLI, kubectl) are cross-platform. The ordering sometimes places PowerShell before Azure CLI, which could be seen as minor bias.
Recommendations
  • Clearly indicate that Azure PowerShell is primarily for Windows users, and recommend Azure CLI for Linux/macOS.
  • Ensure Azure CLI instructions are always presented first, as it is the most cross-platform tool.
  • Add explicit notes clarifying that all Azure CLI and kubectl commands work on Linux/macOS, and provide links to Linux/macOS installation guides.
  • Consider removing PowerShell instructions from sections where they are not relevant for Linux/macOS users, or move them to a separate section for Windows users.
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: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation provides both Linux and Windows examples for AKS network policy configuration, but Windows-specific instructions (such as registering feature flags and creating Windows admin credentials) are given their own prominent section and are detailed before Linux equivalents in some places. The Windows node pool setup is described in depth, including Azure CLI steps and Windows-specific parameters. However, Linux examples are present and complete, and the main workflow is cross-platform. There is a slight bias toward Windows in the ordering and detail of instructions, but Linux users can complete all tasks without significant friction.
Recommendations
  • Ensure Linux instructions are presented first or equally alongside Windows instructions, especially in sections where both are relevant.
  • Where Windows-specific steps are described, provide clear separation and context so Linux users can easily skip irrelevant steps.
  • Add explicit notes clarifying which steps are platform-specific and which are universal.
  • Consider adding a summary table at the start showing which network policy engines are recommended for each OS, with links to relevant sections.
GitHub Create Pull Request