← Back to Dashboard
170
Pages Scanned
16
Pages Flagged
170
Changed Pages
9.4%
% Pages Flagged

Live Progress

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

Scan Information

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

Finished At: In Progress

Status: in_progress

Target Repo: Azure Aks

Current Phase: discovery

Files Queued: 170

Files Completed: 170

Problematic Pages

17 issues found
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 is largely neutral and covers storage concepts for AKS without significant Windows bias. However, in the section on mounting volumes in pods, Windows-specific instructions and YAML examples are presented immediately after Linux examples, which could be interpreted as a minor 'windows_first' bias. There are no PowerShell-heavy examples, Windows tools, or missing Linux examples; the Linux path and mount instructions are provided first and are more prominent.
Recommendations
  • Ensure Linux/macOS instructions are always presented first and clearly separated from Windows-specific guidance.
  • Consider grouping Windows container-specific instructions in a dedicated subsection to avoid mixing OS-specific examples.
  • Explicitly state which examples are for Linux and which are for Windows to avoid confusion.
  • Add clarifying notes to reinforce that most AKS clusters run Linux nodes by default, and Windows-specific instructions are only relevant for Windows node pools.
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 examples for both Azure CLI and Azure PowerShell throughout, but PowerShell is featured equally and sometimes before Linux-native tools. There is no explicit Linux/macOS bias, but the heavy inclusion of PowerShell may create friction for Linux/macOS users. However, all critical operations are covered with Azure CLI (which is cross-platform), and bash commands are used for Helm and kubectl steps.
Recommendations
  • Consider making Azure CLI the default or primary example, as it is cross-platform and more commonly used on Linux/macOS.
  • Clearly indicate that Azure PowerShell is primarily for Windows users, and Azure CLI is recommended for Linux/macOS.
  • Where possible, provide bash shell examples first, and PowerShell examples as an alternative.
  • Add a note clarifying that Azure CLI commands work on Linux, macOS, and Windows, while Azure PowerShell is Windows-centric.
  • Ensure that any PowerShell-specific instructions are accompanied by equivalent bash/CLI instructions.
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 parity for Linux/macOS and Windows users in most areas, but in the Docker daemon startup instructions, Windows/macOS steps are listed before Linux, and the Linux instructions are less detailed. All CLI examples are cross-platform, and Linux-specific commands (e.g., systemctl, kubectl) are included. No critical Windows-only tools or patterns are used.
Recommendations
  • Present Linux instructions for starting Docker daemon before or alongside Windows/macOS steps, with equal detail.
  • Clarify that Docker Desktop is not available on Linux and provide explicit instructions for Linux users (e.g., how to install Docker, how to check Docker service status).
  • Add links to Linux-specific Docker installation guides and troubleshooting tips.
  • Ensure all example commands (e.g., az, kubectl) are confirmed to work on Linux/macOS and Windows.
  • Explicitly mention that all commands are cross-platform unless otherwise noted.
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 largely cross-platform, with most examples using Azure CLI and kubectl commands that work on both Linux and Windows. However, in the section 'Verify TLS Bootstrapping is enabled on current agent node pool', the Windows file path ('C:\k\bootstrap-config') is mentioned after the Linux path, but both are provided. There are no PowerShell-specific examples, and all CLI commands are OS-agnostic. No Windows-only tools or patterns are used. The only minor bias is that Windows is mentioned second in the file path example, and there are no explicit macOS examples (though Linux commands generally apply to macOS).
Recommendations
  • Explicitly state that all Azure CLI and kubectl examples work on Linux, Windows, and macOS.
  • Where file paths are shown, clarify that Linux paths also apply to macOS unless otherwise noted.
  • Consider including a note about macOS parity in relevant sections.
  • If any commands require adaptation for Windows (e.g., path separators), provide those examples as well.
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: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides troubleshooting steps for the agentic CLI for AKS and generally covers both Windows/macOS and Linux environments. However, in Docker-related troubleshooting, Windows/macOS instructions (Docker Desktop) are consistently presented before Linux instructions, and Docker Desktop (a Windows/macOS tool) is referenced as the primary solution for those platforms. Linux solutions are given, but Windows/macOS steps are prioritized in ordering and tool mention.
Recommendations
  • Present Linux and Windows/macOS instructions in parallel or in a neutral order (e.g., Linux first, or both together).
  • Explicitly mention that Docker Desktop is not available on Linux and clarify Linux-specific alternatives.
  • Where possible, provide equivalent troubleshooting steps for all platforms, and avoid implying Windows/macOS as the default.
  • Consider using platform-specific tabs or sections to avoid bias in ordering.
GitHub Create Pull Request
Aks Integrate Azure Container Registry with Azure Kubernetes Service (AKS) ...articles/aks/cluster-container-registry-integration.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 major tasks, but PowerShell (a Windows-centric tool) is given equal prominence throughout. There is no explicit Linux example or mention of Bash scripting, and PowerShell is referenced as a primary tool, which may create friction for Linux/macOS users. However, Azure CLI commands are present and are cross-platform, mitigating most functional bias.
Recommendations
  • Explicitly state that Azure CLI is fully supported on Linux/macOS and is the recommended tool for cross-platform scenarios.
  • Consider mentioning Bash or shell scripting as alternatives for Linux/macOS users, especially in introductory sections.
  • Where PowerShell is referenced, clarify that it is available on Linux/macOS, or provide links to installation instructions for those platforms.
  • If possible, add brief notes or examples for Bash scripting or highlight that Azure CLI commands work natively in Linux/macOS terminals.
  • Ensure that Azure CLI examples are shown first, as it is the most cross-platform tool.
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 prominent, with explicit instructions for Windows, macOS, and Linux users. However, PowerShell is a Windows-centric tool, and its section precedes the Azure CLI, which is more cross-platform. The CLI section is present and offers parity, but PowerShell is given more prominence and detail, and is listed before CLI, which may subtly prioritize Windows users.
Recommendations
  • Consider listing Azure CLI before Azure PowerShell, as CLI is more universally available across platforms.
  • Ensure that CLI examples are as detailed as PowerShell examples, including explanations of each step.
  • Add explicit notes that Azure CLI is recommended for Linux/macOS users, and highlight its cross-platform nature.
  • Where PowerShell is mentioned, clarify its availability and limitations on Linux/macOS, and link to installation instructions for those platforms.
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 alongside Azure CLI and the Azure Portal as options for moving resources, but does not provide Linux-specific guidance or parity for PowerShell usage. Azure CLI is used for all command-line examples, which is cross-platform, but PowerShell is mentioned before CLI in the migration step. There are no PowerShell command examples, and all YAML and kubectl examples are Linux-oriented. The documentation does not provide Linux-specific troubleshooting or highlight Linux-native tools, but overall, the bias is minimal.
Recommendations
  • Clarify that Azure PowerShell is available cross-platform, but provide explicit guidance for Linux/macOS users if PowerShell is required.
  • List Azure CLI before Azure PowerShell when describing migration options, as CLI is more commonly used on Linux/macOS.
  • Add a note that all CLI commands are cross-platform and can be run on Linux, macOS, or Windows.
  • If referencing PowerShell, provide links or examples for installing and using PowerShell on Linux/macOS, or clarify that it's optional.
  • Consider adding troubleshooting tips for Linux/macOS users if there are known issues with Azure CLI or kubectl.
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/resource group queries, but consistently mentions Azure PowerShell alongside Azure CLI and the Azure portal. PowerShell cmdlets are referenced for subnet queries before Linux-native alternatives. However, all core examples and walkthroughs use kubectl and Azure CLI, which are cross-platform. No critical steps are Windows-only, but PowerShell is presented as a peer to CLI, which may create friction for Linux/macOS users.
Recommendations
  • List Azure CLI as the primary cross-platform tool for all prerequisite and resource management steps; mention PowerShell only as an alternative for Windows users.
  • When referencing commands for querying subnets or resources, provide Azure CLI examples first and PowerShell examples in a separate, clearly marked section for Windows users.
  • Clarify that Azure PowerShell is Windows-centric and not required for Linux/macOS users.
  • Ensure all critical workflow steps (manifest creation, kubectl usage, Azure CLI commands) remain cross-platform and avoid PowerShell-only instructions.
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 ⚠ī¸ powershell_heavy
Summary
The documentation is generally cross-platform, focusing on Azure Files usage in AKS with both SMB and NFS protocols. However, there are minor signs of Windows bias: Windows path conventions and PowerShell/CMD syntax are mentioned before Linux equivalents in some places, and Windows-specific instructions are sometimes highlighted first or separately. Most examples and instructions are generic or Linux-oriented, but Windows is occasionally prioritized in explanations or example order.
Recommendations
  • When referencing path conventions, list Linux/macOS examples first or equally alongside Windows (e.g., '/mnt/azure' and 'D:').
  • Where command syntax differs (e.g., PowerShell vs Bash), provide both examples side-by-side, or default to Bash unless the section is Windows-specific.
  • Ensure that any Windows-specific instructions are clearly marked as such, and Linux/macOS alternatives are provided where applicable.
  • Review output examples and ensure they are not exclusively Windows-formatted unless the section is about Windows containers.
  • In sections about mounting volumes or using Azure Files, clarify OS-specific requirements and provide parity in examples.
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 (cross-platform) and Azure PowerShell (Windows-centric) examples for managing AKS authorized IP ranges. However, the PowerShell tab is presented immediately after the CLI, and there is no explicit mention that PowerShell Core is cross-platform, which may lead Linux/macOS users to believe the PowerShell examples are Windows-only. The rest of the documentation is focused on the Azure Portal UI and Azure CLI, which are cross-platform, and does not show a strong Windows bias.
Recommendations
  • Clarify that Azure CLI commands are fully supported on Linux, macOS, and Windows.
  • For PowerShell examples, explicitly mention if Azure PowerShell Core is supported on Linux/macOS, or clarify if the example is Windows-only.
  • Consider listing Azure CLI examples before PowerShell, or defaulting to CLI as the primary cross-platform method.
  • Where possible, add a short note for Linux/macOS users confirming that all shown CLI commands work on their platforms.
GitHub Create Pull Request
Aks Supported Kubernetes Versions in Azure Kubernetes Service (AKS) ...lob/main/articles/aks/supported-kubernetes-versions.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 key operations (such as installing kubectl and listing available Kubernetes versions), but consistently lists Azure PowerShell (a Windows-centric tool) alongside or immediately after Azure CLI. There are no Linux-specific shell examples (e.g., Bash), and the CLI instructions do not reference Linux/macOS explicitly. However, the content itself is not Windows-focused and covers both Linux and Windows node pools and OS components equally.
Recommendations
  • Add explicit Bash/Linux/macOS shell examples for commands where Azure CLI is used, clarifying compatibility and usage on non-Windows platforms.
  • Mention that Azure CLI commands are cross-platform and can be used on Linux/macOS, while Azure PowerShell is primarily for Windows users.
  • Consider listing Azure CLI (cross-platform) examples first, and PowerShell examples second, to reduce perceived Windows bias.
  • Where relevant, add notes or links to Linux/macOS installation instructions for tools like kubectl and Azure CLI.
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 examples for Azure CLI, Azure PowerShell, and Azure Developer CLI, but PowerShell is featured as a first-class option throughout, which may create friction for Linux/macOS users. Azure PowerShell is primarily a Windows-centric tool, and its prominence alongside Azure CLI (which is cross-platform) may suggest a Windows bias. However, all critical tasks are covered with Azure CLI examples, which are suitable for Linux/macOS users. There are no missing Linux examples, and no Windows-only tools are referenced outside PowerShell.
Recommendations
  • Consider making Azure CLI the default or primary example, as it is cross-platform and widely used by Linux/macOS users.
  • Explicitly note that Azure PowerShell is primarily for Windows users, and recommend Azure CLI for Linux/macOS.
  • Add a short section clarifying that all tasks can be completed using Azure CLI on Linux/macOS, and that PowerShell is optional.
  • Ensure that Azure CLI examples are shown first in each section, or highlight their cross-platform compatibility.
GitHub Create Pull Request
Aks Stop and start an Azure Kubernetes Service (AKS) cluster ...-aks-docs/blob/main/articles/aks/start-stop-cluster.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 stopping and starting AKS clusters. However, PowerShell examples are presented alongside CLI examples, and the 'Before you begin' section lists Azure CLI, Azure PowerShell, and Azure Portal as options for cluster creation, with PowerShell mentioned before Portal. There are no Linux-specific examples or explicit mention of Linux/macOS compatibility for Azure CLI commands, but Azure CLI is inherently cross-platform. No Windows-only tools or patterns are used, and all critical operations can be completed with Azure CLI, which works on Linux/macOS.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows.
  • Consider listing Azure CLI examples first in all sections, as it is the most cross-platform tool.
  • Add a note clarifying that Azure PowerShell is primarily for Windows users, while Azure CLI is recommended for Linux/macOS.
  • Ensure parity in example output formats (e.g., JSON for CLI, PowerShell output for PowerShell) and clarify differences.
GitHub Create Pull Request
Aks Upgrade Azure Kubernetes Service (AKS) node images ...-aks-docs/blob/main/articles/aks/upgrade-node-image.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_reference
Summary
The documentation is primarily cross-platform, using Azure CLI and kubectl commands that work on Linux, macOS, and Windows. However, there are repeated notes referencing Windows and PowerShell environments regarding potential differences in shell command syntax, but no actual Windows/PowerShell-specific examples are provided. The documentation does not show Windows tools or patterns exclusively, nor does it prioritize Windows examples.
Recommendations
  • If shell differences are significant, provide explicit PowerShell/Windows CMD examples alongside bash examples.
  • Clarify any shell-specific differences for Linux/macOS users, not just Windows/PowerShell.
  • Consider linking to shell-agnostic guidance or providing a table of equivalent commands for different environments.
GitHub Create Pull Request
Aks Create an OpenID Connect (OIDC) Provider for your Azure Kubernetes Service (AKS) Cluster ...ure-aks-docs/blob/main/articles/aks/use-oidc-issuer.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation uses Azure CLI examples throughout, which are cross-platform, but the shell syntax shown (environment variables, command structure) is Bash-style and not Windows/PowerShell. No Windows-specific tools or patterns are mentioned, and Linux/macOS users can follow all steps as written. However, the page does not provide PowerShell or Windows Command Prompt examples, nor does it mention any platform-specific differences. The Azure CLI is the only tool used, which is available on all major OSes.
Recommendations
  • Explicitly state that Azure CLI commands are cross-platform and supported on Windows, Linux, and macOS.
  • Consider adding a note or section for PowerShell/Windows Command Prompt users, showing equivalent environment variable syntax and command usage.
  • Mention any known platform-specific issues or differences, if applicable.
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 examples and guidance for both Linux and Windows node pools in AKS, but Windows-specific instructions (such as registering preview features, creating Windows admin credentials, and referencing Windows node pool requirements) are presented before or alongside Linux equivalents. Some sections (e.g., cluster creation) show Windows steps in detail, including CLI commands for Windows-specific features, while Linux steps are more concise. However, Linux examples are present and generally complete, and the core network policy concepts are platform-neutral.
Recommendations
  • Ensure Linux and Windows instructions are clearly separated, with Linux steps shown first unless the feature is Windows-only.
  • Add explicit Linux/macOS shell examples where Windows-specific CLI commands are shown (e.g., for credential creation).
  • Clarify which steps are platform-specific and which are universal, possibly with tabbed or split sections for Linux and Windows.
  • Where preview/feature registration is Windows-only, clearly label it as such to avoid confusion.
  • Review the ordering of sections to avoid giving Windows steps prominence unless required by the feature.
GitHub Create Pull Request