← Back to Dashboard
151
Pages Scanned
15
Pages Flagged
151
Changed Pages
9.9%
% Pages Flagged

Live Progress

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

Scan Information

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

Finished At: In Progress

Status: in_progress

Target Repo: Azure Aks

Current Phase: discovery

Files Queued: 151

Files Completed: 151

Problematic Pages

14 issues found
Aks Kubernetes on Azure tutorial - Create an Azure Kubernetes Service (AKS) cluster ...ain/articles/aks/tutorial-kubernetes-deploy-cluster.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 examples for Azure CLI, Azure PowerShell, and Azure Developer CLI. However, PowerShell examples are prominent throughout, and PowerShell is a Windows-centric tool. Azure CLI (which is cross-platform) is included, but PowerShell is given equal billing and sometimes appears before CLI in sections. There are no explicit Linux/macOS-specific instructions or examples, and no mention of Linux shell patterns (e.g., Bash scripting, environment variables for Linux, or package managers like apt/yum/brew for installing tools). The install instructions for kubectl rely on Azure CLI/PowerShell commands, omitting native Linux/macOS install methods.
Recommendations
  • Add explicit Linux/macOS install instructions for kubectl (e.g., using curl, apt, brew, or native package managers).
  • Clarify that Azure CLI commands work on Linux/macOS and Windows, and provide Bash shell examples where appropriate.
  • Consider mentioning that PowerShell Core is cross-platform, but most users on Linux/macOS will use Bash or Zsh.
  • Add a section or callout for Linux/macOS users, highlighting any differences or considerations (e.g., SSH key generation, environment variable syntax).
  • When referencing installation of Azure CLI, link to platform-specific instructions (Windows, Linux, macOS).
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: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation provides troubleshooting steps for the Agentic CLI for AKS with both Windows/macOS and Linux instructions. However, in the Docker daemon troubleshooting section, Windows/macOS steps are presented before Linux steps, indicating a minor 'windows_first' bias. All critical tasks include Linux examples, and Linux-specific issues (such as Docker group permissions) are addressed. No PowerShell-only examples or exclusive Windows tools are present.
Recommendations
  • Present Linux instructions before or alongside Windows/macOS instructions, especially for Docker-related troubleshooting, to improve parity.
  • Consider grouping OS-specific steps under clearly labeled subsections or tabs for clarity.
  • Ensure that all examples and solutions are equally detailed for both Linux and Windows/macOS users.
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 after the Linux example. There are no PowerShell-specific commands, Windows tools, or Windows-centric patterns prioritized. The only Windows-specific mention is in the context of mounting volumes in Windows containers, which is appropriate and not excessive. All technical concepts and YAML manifests are generic and applicable to both Linux and Windows AKS node pools. The only minor bias is that Linux examples are shown first, but this is standard practice given Linux is the default for AKS.
Recommendations
  • Ensure parity by always providing both Linux and Windows container examples where relevant, and clarify when a feature or example is OS-specific.
  • Consider explicitly stating in relevant sections that YAML manifests are applicable to both Linux and Windows node pools unless otherwise noted.
  • If possible, provide links to Windows-specific AKS documentation for users seeking more details.
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 ⚠ī¸ powershell_heavy
Summary
The documentation provides both Linux and Windows examples for AKS network policies, but Windows-specific instructions (such as registering feature flags and creating Windows admin credentials) are presented in detail and before Linux equivalents in some sections. The use of Azure CLI and bash is consistent, but Windows-specific steps are more verbose and prominent. However, Linux parity is generally maintained, and all critical tasks are possible on Linux.
Recommendations
  • Ensure Linux and Windows instructions are presented in parallel or grouped by OS, rather than Windows steps being more prominent or detailed.
  • Add explicit notes or sections for Linux/macOS users where Windows-specific steps are described, clarifying which steps are not required for Linux.
  • Where possible, provide Linux-first examples or alternate the order of examples to avoid Windows-first bias.
  • Review the documentation for any unnecessary Windows-specific terminology or tools when Linux equivalents exist.
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 platform-specific instructions for starting Docker, listing both macOS/Windows and Linux steps. However, the Windows/macOS instructions are presented first, and the Linux instructions are secondary. All other examples and instructions are cross-platform (using Azure CLI and Docker), and Linux-specific commands (e.g., systemctl) are included where relevant. No PowerShell-specific commands, Windows-only tools, or missing Linux examples are found.
Recommendations
  • Present Linux instructions alongside Windows/macOS instructions, or in parallel (e.g., in a table or tabbed format) to avoid subtle ordering bias.
  • Explicitly mention that all commands are cross-platform unless otherwise noted.
  • Where possible, clarify that Docker Desktop is available for both Windows and macOS, and that Linux users should use their distribution's package manager.
  • Consider adding links to Linux-specific Docker installation guides for popular distributions (e.g., Ubuntu, CentOS).
GitHub Create Pull Request
Aks Connect your Azure Kubernetes Service (AKS) cluster to AI agents using the Model Context Protocol (MCP) server ...main/articles/aks/aks-model-context-protocol-server.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides cross-platform instructions and download links for Windows, macOS, and Linux. However, in several sections, Windows shortcuts and terminology are mentioned first (e.g., VS Code keybindings), and there are occasional tips for Windows-specific scenarios (such as WSL configuration). While Linux and macOS are included, some examples and troubleshooting steps prioritize Windows or lack explicit Linux-specific guidance (e.g., Docker credential mounting, user IDs, and Azure CLI authentication nuances).
Recommendations
  • Ensure Linux/macOS keyboard shortcuts are presented equally alongside Windows shortcuts, or use neutral phrasing.
  • Add explicit Linux/macOS troubleshooting tips, especially for Docker credential mounting and Azure CLI authentication.
  • Where Windows-specific instructions are given (e.g., WSL), provide equivalent Linux/macOS guidance or clarify differences.
  • Consider alternating the order of platform references to avoid always listing Windows first.
  • Expand on Linux-specific nuances for Docker usage, such as file permissions and user IDs.
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, with most commands and examples using Azure CLI and bash syntax suitable for Linux/macOS. However, there is a minor Windows 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, but no explicit example is provided for accessing the file on Windows. Additionally, some output examples reference Windows node names (e.g., 'akswinp7000000'), but these are not critical and do not hinder Linux users. Overall, Linux parity is strong, but a few minor improvements could be made.
Recommendations
  • Provide explicit Windows command examples where file paths are referenced (e.g., how to access 'C:\k\bootstrap-config' on Windows nodes).
  • Ensure output examples include both Linux and Windows node names or clarify that the examples are representative.
  • When referencing file paths for both Linux and Windows, consider presenting them side-by-side for clarity.
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: Azure portal, Azure PowerShell, and Azure CLI. The PowerShell section is detailed and includes explicit instructions for Windows, macOS, and Linux users, but PowerShell is traditionally Windows-centric and is presented before the CLI. The CLI section is present and offers parity for Linux/macOS users, but PowerShell is given prominence and more explanation. The Azure portal instructions are platform-neutral. No critical steps are Windows-only, but the ordering and emphasis may create friction for Linux/macOS users.
Recommendations
  • Present Azure CLI instructions before PowerShell, as CLI is more cross-platform and preferred by many Linux/macOS users.
  • Explicitly mention that both PowerShell and CLI are cross-platform, but CLI is often the default on Linux/macOS.
  • Ensure that all PowerShell instructions reference Linux/macOS installation equally to Windows, which is already done.
  • Add a note recommending CLI for Linux/macOS users, or clarify tool selection based on OS preference.
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: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation is generally cross-platform and Linux-friendly, but there are several minor signs of Windows bias. Windows-specific instructions and path conventions are mentioned before Linux equivalents in some sections (e.g., mounting Azure Files in Windows containers, path examples). Azure CLI and PowerShell are referenced, but Linux shell examples are more common. Windows-specific tools and conventions are sometimes highlighted, even when Linux is the default or primary platform for AKS.
Recommendations
  • Ensure Linux/macOS examples are presented first, especially in sections where both Windows and Linux are supported.
  • Where Windows-specific instructions are given, provide equivalent Linux/macOS guidance and clarify which applies to which OS.
  • When referencing Azure CLI or PowerShell, clearly indicate which commands are for which platform, and provide parity in examples.
  • Avoid mentioning Windows path conventions before Linux unless the section is specifically about Windows containers.
  • Review output examples and ensure they are representative of both Linux and Windows environments where applicable.
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 mentions Azure PowerShell as a migration tool alongside Azure CLI and Azure Portal, but does not provide PowerShell-specific examples. Azure CLI is used for all command-line examples, which is cross-platform. However, Azure PowerShell is listed before Azure CLI in the migration options, which could suggest a slight Windows-first bias. No PowerShell-only instructions or Windows-specific commands are present, and all YAML and kubectl examples are Linux-oriented.
Recommendations
  • List Azure CLI before Azure PowerShell in migration tool options, as CLI is cross-platform and more commonly used in Linux/macOS environments.
  • Clarify that Azure PowerShell is optional and primarily for Windows users, while Azure CLI is recommended for Linux/macOS.
  • If mentioning Azure PowerShell, provide parity by linking to Linux/macOS installation instructions or note its cross-platform support.
  • Ensure that all example commands are shown in Azure CLI (as currently done), and avoid implying PowerShell is required.
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 consistently mentions Azure PowerShell alongside Azure CLI and portal, sometimes listing PowerShell before Linux-native alternatives. The only explicit command example for subnet listing includes both Azure CLI and PowerShell, but PowerShell is referenced as an equal alternative rather than a secondary option. All actual command examples use Azure CLI and kubectl, which are cross-platform, and no PowerShell-specific commands are required for the main workflow. However, PowerShell is mentioned in the prerequisites and links, which may create minor friction for Linux/macOS users.
Recommendations
  • List Azure CLI as the primary cross-platform option for all examples and prerequisites, with PowerShell as a secondary alternative.
  • Where PowerShell is referenced, clarify that Azure CLI is recommended for Linux/macOS users.
  • Add explicit notes that all Azure CLI and kubectl commands work on Linux/macOS, and that PowerShell is Windows-centric.
  • Consider moving PowerShell references to a separate section or footnote for Windows users.
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 updating AKS authorized IP ranges, but the PowerShell example is given equal prominence and is not clearly marked as Windows-specific. The CLI example (using 'dig') is Linux/macOS-friendly, but the PowerShell example is presented alongside it, which may confuse users on non-Windows platforms. There are no explicit Linux/macOS biases, but Windows tools (PowerShell) are mentioned equally rather than as secondary or optional for Windows users.
Recommendations
  • Clearly label PowerShell examples as 'Windows only' or 'For Windows users'.
  • Present Azure CLI (Linux/macOS cross-platform) examples first, with PowerShell as an optional section for Windows users.
  • Consider adding a note clarifying that Azure CLI works on Windows, Linux, and macOS, while PowerShell is Windows-specific.
  • Ensure all command-line examples are cross-platform unless a Windows-only feature is being discussed.
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 parallel Azure CLI and Azure PowerShell instructions throughout, but PowerShell is featured equally and sometimes before Linux-native alternatives. The prerequisites list Azure PowerShell alongside Azure CLI, and PowerShell cmdlets are given for every major step. However, all CLI instructions are cross-platform, and bash commands are used for Helm, git, and kubectl, which are standard on Linux/macOS. No Windows-only tools or patterns are used, and Linux/macOS users can complete all tasks.
Recommendations
  • Clarify that Azure PowerShell is available on Linux/macOS, reducing the perception of Windows bias.
  • Consider listing Azure CLI examples first, as it is the default and most common cross-platform tool.
  • Explicitly mention that all Azure CLI and PowerShell commands work on Linux/macOS (where applicable).
  • Add a note that Azure Cloud Shell is available in-browser and supports both CLI and PowerShell, regardless of OS.
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 all technical examples, commands, and explanations are Linux-centric. However, in prerequisite sections, Windows tools (Azure PowerShell) are listed alongside Azure CLI and Portal for cluster creation, and PowerShell is mentioned before Linux equivalents in some places. No Windows-specific commands, tools, or examples are given for the main security features, and Linux is clearly the primary platform for the described functionality. There are no missing Linux examples, and Windows is only referenced in limitations or as an unsupported platform.
Recommendations
  • When listing tools for cluster creation, consider mentioning Azure CLI first, as it is cross-platform and more commonly used in Linux environments.
  • Clarify that Azure PowerShell is optional and primarily for Windows users, or provide parity with Bash/CLI examples where relevant.
  • If possible, provide links to Linux-focused quickstart guides before Windows/PowerShell equivalents.
  • Ensure that Linux prerequisites and examples are always prioritized in sections about Linux-only features.
GitHub Create Pull Request