← Back to Dashboard
171
Pages Scanned
18
Pages Flagged
171
Changed Pages
10.5%
% Pages Flagged

Live Progress

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

Scan Information

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

Finished At: In Progress

Status: in_progress

Target Repo: Azure Aks

Current Phase: discovery

Files Queued: 171

Files Completed: 171

Problematic Pages

18 issues found
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 both Linux and Windows/macOS instructions for Docker setup, but in the 'Verify Docker installation and start Docker daemon' section, Windows/macOS instructions are listed before Linux. All CLI examples use Azure CLI, which is cross-platform, and Bash commands are used for verification and cleanup, ensuring Linux parity. No PowerShell-specific or Windows-only tools are referenced, and Linux-specific instructions are present where relevant.
Recommendations
  • Consider listing Linux instructions before Windows/macOS in the Docker daemon startup section, or present all OS instructions in parallel (e.g., in a table or tabs).
  • Explicitly mention that Azure CLI and Docker commands are cross-platform and provide links to installation guides for all supported OSes.
  • Ensure that future examples or troubleshooting sections include Linux/macOS-specific notes if there are OS-specific behaviors.
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 detailed and references Windows tools, but also includes instructions for macOS and Linux. However, PowerShell is presented before Azure CLI, and PowerShell is traditionally associated with Windows, which may create a perception of Windows bias. Azure CLI examples are present and equally functional for Linux/macOS users.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is more cross-platform and commonly used on Linux/macOS.
  • Explicitly mention that Azure PowerShell can be used on Linux and macOS, and link to installation instructions for those platforms.
  • Add brief notes clarifying that both Azure CLI and PowerShell examples are fully cross-platform.
  • Consider adding Bash shell examples for common tasks if relevant.
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. Azure CLI is cross-platform and suitable for Linux/macOS users, while Azure PowerShell is primarily Windows-focused. However, the CLI examples are presented first in each section, ensuring Linux parity. There are no Windows-only tools or patterns mentioned, and Linux users can fully complete the tasks described.
Recommendations
  • Clarify that Azure CLI is cross-platform and recommended for Linux/macOS users.
  • Consider explicitly stating that Azure PowerShell is primarily for Windows users, and that Linux/macOS users should use Azure CLI.
  • Add a brief note in the 'Before you begin' section highlighting the cross-platform nature of Azure CLI.
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 generally provides cross-platform troubleshooting steps, but in the Docker daemon troubleshooting section, instructions for macOS/Windows are listed before Linux, and the Windows solution refers to Docker Desktop (a Windows/macOS-specific tool). However, Linux instructions are present and complete. No PowerShell-specific commands or Windows-only tools are used elsewhere.
Recommendations
  • Present Linux, macOS, and Windows instructions in parallel or in a consistent order (e.g., Linux, macOS, Windows) to avoid implicit prioritization.
  • Explicitly mention that Docker Desktop is for Windows/macOS, and clarify the equivalent for Linux (systemd service).
  • Where possible, provide command-line solutions for all platforms, or link to platform-specific Docker startup guides.
  • If using platform-specific tools (like Docker Desktop), briefly mention alternatives for other OSes.
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 provides both Linux and Windows file paths for verifying TLS Bootstrapping, but the Windows path is mentioned alongside the Linux path rather than exclusively or first. However, in the certificate rotation and verification sections, all command-line examples use Bash, Azure CLI, and kubectl, which are cross-platform but primarily shown in Linux syntax. There are no PowerShell or Windows Command Prompt examples for Windows users, but the documentation does not exclusively mention Windows tools or patterns. The only minor bias is that Linux paths and Bash examples are shown first and exclusively, with Windows-specific file paths mentioned only once.
Recommendations
  • Add explicit PowerShell or Windows Command Prompt examples for certificate expiration checks and Azure CLI commands, especially for Windows users who may not have Bash available.
  • Provide guidance on running Azure CLI and kubectl on Windows, including any prerequisites or differences.
  • Where file paths are shown, clarify if the commands are cross-platform or provide equivalent Windows commands/scripts.
  • Consider showing both Linux and Windows examples side-by-side for critical steps.
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 is featured equally and sometimes referenced first in metadata and tool tracking. There is a slight Windows bias due to the heavy inclusion of PowerShell examples and explicit mention of Azure PowerShell as a primary tool, which is most relevant for Windows users. However, all CLI examples are cross-platform and Linux-compatible, and there are no Windows-only commands or tools. No Linux-specific examples (e.g., Bash scripting, shell environment variables) are provided, but Linux users can complete all tasks using Azure CLI.
Recommendations
  • Clarify that Azure PowerShell is available on Linux/macOS and link to installation instructions for those platforms.
  • Add brief Bash shell scripting examples or notes for setting environment variables (e.g., export vs. set) to improve Linux parity.
  • Explicitly state that all Azure CLI commands are cross-platform and recommend CLI for Linux/macOS users.
  • Consider mentioning that PowerShell Core is cross-platform, if relevant, to reduce perceived Windows bias.
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 provides a comprehensive guide for creating and managing persistent volumes with Azure Files in AKS, primarily using YAML manifests and Azure CLI commands. While the majority of examples and instructions are platform-neutral or Linux-focused, there are occasional signs of Windows bias: Windows path conventions are mentioned before Linux equivalents in some sections, and in the Windows containers section, PowerShell/CMD path examples are given alongside Bash. Azure CLI is used throughout, which is cross-platform, but no explicit Linux shell or macOS-specific guidance is provided for Azure CLI installation or troubleshooting. Overall, the bias is minor and does not prevent Linux/macOS users from completing the tasks.
Recommendations
  • Where Windows path conventions are mentioned, ensure Linux/macOS equivalents are also shown and listed first unless the section is Windows-specific.
  • Clarify that Azure CLI is cross-platform and provide links or notes for Linux/macOS installation and troubleshooting.
  • When providing shell commands, use generic Bash syntax and note any Windows-specific differences only in Windows-focused sections.
  • In sections referencing PowerShell/CMD, ensure Bash/Linux equivalents are equally prominent.
  • Consider adding explicit notes or examples for macOS users where relevant (e.g., file permissions, mount options).
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 option 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 referenced before Azure CLI in the migration options, and there are no Linux-specific notes or examples. The documentation does not provide any Windows-only commands or patterns, but the mention of PowerShell without parity for Linux shell tools (e.g., Bash) is a minor Windows-first bias.
Recommendations
  • Clarify that Azure CLI commands are cross-platform and preferred for Linux/macOS users.
  • If referencing Azure PowerShell, provide equivalent Bash or Linux shell command examples, or explicitly state that Azure CLI is recommended for Linux/macOS.
  • Consider listing Azure CLI before Azure PowerShell in migration options to reinforce Linux parity.
  • Add a note that all CLI examples work on Linux, macOS, and Windows.
GitHub Create Pull Request
Aks Install Dapr Extension for Azure Kubernetes Service (AKS) ...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 cross-platform, focusing on Azure CLI and Bicep for installing Dapr on AKS, which are available on Windows, Linux, and macOS. However, in the section about listing CRDs for cleanup, only a Windows/PowerShell example ('kubectl get crds | findstr dapr.io') is provided, with no Linux/macOS equivalent. Additionally, the use of 'findstr' (a Windows tool) is shown before any mention of Linux alternatives, and no 'grep' example is given.
Recommendations
  • Add a Linux/macOS example for listing CRDs, such as 'kubectl get crds | grep dapr.io'.
  • When showing command-line examples that differ by OS, provide both Windows and Linux/macOS versions side-by-side.
  • Review other sections for similar OS-specific commands and ensure parity.
  • Consider mentioning that Azure CLI and Bicep are cross-platform, reinforcing inclusivity.
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). There are no explicit Windows-only tools or patterns, and all instructions are portal-based or cross-platform. However, the PowerShell section is present, which may be unnecessary for Linux/macOS users, but does not hinder their ability to complete the task. No critical steps are Windows-only.
Recommendations
  • Consider clarifying that Azure PowerShell examples are for Windows users, while Azure CLI is cross-platform.
  • If possible, add a Bash-only example for Linux/macOS users (e.g., using curl for IP retrieval).
  • Ensure that CLI instructions are clearly marked as cross-platform and PowerShell as Windows-specific.
  • Add a note that Azure CLI works on Windows, Linux, and macOS, while PowerShell is primarily for Windows.
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 steps, but consistently mentions Azure PowerShell alongside Azure CLI and portal, sometimes listing PowerShell before Linux-native alternatives. It also references a PowerShell cmdlet (Get-AzVirtualNetworkSubnetConfig) for subnet listing, but does not provide a Linux equivalent (such as Azure CLI) in that context. However, all main examples and workflows use kubectl and Azure CLI, which are cross-platform, and no critical steps are Windows-only.
Recommendations
  • When referencing PowerShell cmdlets (e.g., Get-AzVirtualNetworkSubnetConfig), always provide the Azure CLI equivalent and show it first, as Azure CLI is cross-platform.
  • In prerequisite sections, list Azure CLI before PowerShell to reinforce Linux parity.
  • Consider removing or de-emphasizing PowerShell references unless the feature is Windows-specific.
  • Explicitly note that Azure CLI and kubectl commands work on Linux/macOS/Windows.
  • Add a note clarifying that all main workflows are cross-platform.
GitHub Create Pull Request
Aks Connect to Azure Kubernetes Service (AKS) cluster nodes ...s/azure-aks-docs/blob/main/articles/aks/node-access.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/macOS and Windows node access instructions, but Windows-specific tools (PowerShell, host process containers) are emphasized in dedicated sections. Windows node access methods are described after Linux/macOS, but Windows-specific examples (e.g., PowerShell in host process containers) are prominent and not paralleled with Linux equivalents. The Linux/macOS instructions are clear and complete, but Windows sections rely heavily on Windows tools and patterns.
Recommendations
  • Ensure Linux/macOS and Windows instructions are equally detailed and easy to follow.
  • Where Windows-specific tools (e.g., PowerShell, host process containers) are mentioned, clarify if there are Linux equivalents or explicitly state that these are Windows-only approaches.
  • Consider grouping Linux/macOS and Windows instructions in parallel subsections for easier comparison.
  • Add explicit notes when a method is Windows-only, to avoid confusion for Linux/macOS users.
  • For SSH instructions, provide parity in troubleshooting and advanced access methods for both OS types.
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 presents Azure CLI (cross-platform) examples first, followed by Azure PowerShell (Windows-centric) examples. No Linux-specific commands, tools, or shell patterns are missing, but there is a slight bias in the inclusion of PowerShell examples and terminology, which may be less relevant for Linux/macOS users. However, all critical tasks are covered with cross-platform tools, and Linux-specific OS components are clearly documented.
Recommendations
  • Consider explicitly mentioning that Azure CLI is cross-platform and recommended for Linux/macOS users.
  • Add brief notes clarifying that Azure PowerShell is primarily for Windows users.
  • Where possible, include bash or shell script examples for Linux users, especially for common tasks.
  • Ensure that all CLI instructions are clearly marked as cross-platform.
  • If referencing Azure CLI, highlight its compatibility with Linux/macOS in introductory sections.
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: 2 bias types
Detected Bias Types
⚠ī¸ windows_reference ⚠ī¸ windows_shell_note
Summary
The documentation is generally cross-platform, using Azure CLI and kubectl commands that work on both Linux and Windows. However, there are repeated notes referencing Windows and PowerShell environments when discussing kubectl JSONPath output, despite the examples themselves being bash-oriented and not providing explicit PowerShell or Windows CMD examples. No Linux-specific bias or missing Linux examples are detected, but Windows is mentioned in shell context notes.
Recommendations
  • Add explicit PowerShell and Windows CMD examples if shell differences are significant, or clarify that the provided bash examples work on all platforms with Azure CLI and kubectl installed.
  • Consider adding a brief section or note about shell differences for both Linux/macOS and Windows users, including example commands for each if needed.
  • Ensure that shell notes reference Linux/macOS as well, not just Windows/PowerShell, to maintain parity and inclusivity.
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 steps, but consistently presents Azure CLI (commonly used on Linux/macOS) first and Azure PowerShell (primarily Windows-centric) second. However, there are no explicit Windows-only tools or patterns, and all core steps (kubectl, Helm, git, bash commands) are cross-platform. There is minor bias in the presence of PowerShell examples, but Linux/macOS users are not blocked or significantly inconvenienced.
Recommendations
  • Consider clarifying that Azure PowerShell is primarily for Windows users, and Azure CLI is recommended for Linux/macOS.
  • Explicitly state that all Azure CLI commands work on Linux, macOS, and Windows.
  • Optionally, provide a brief note on how to install Azure CLI and PowerShell on different platforms, linking to platform-specific instructions.
  • Ensure that bash commands (git, helm, kubectl) are shown as cross-platform, and mention any Windows-specific caveats if relevant.
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 examples and references are prominent throughout. PowerShell is a Windows-centric tool, and its inclusion alongside Azure CLI (which is cross-platform) may create a perception of Windows bias. Additionally, PowerShell is mentioned before Linux-native alternatives in several sections, and there are no explicit Bash or Linux shell examples. However, Azure CLI is presented as the primary cross-platform tool, and Cloud Shell (which is Linux-based) is referenced, mitigating the bias.
Recommendations
  • Add explicit Bash/Linux shell examples for Azure CLI commands, showing usage in a typical Linux/macOS terminal.
  • Clarify that Azure CLI commands work identically on Windows, Linux, and macOS, and highlight Bash usage where relevant.
  • Consider reducing PowerShell prominence or move PowerShell examples after Azure CLI examples to reinforce cross-platform parity.
  • Mention that Azure Cloud Shell is Linux-based and suitable for all platforms.
  • Add notes or links for Linux/macOS users about installing Azure CLI and kubectl using native package managers (e.g., apt, brew).
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 policy setup, but Windows-specific instructions (such as registering preview features and creating Windows admin credentials) are given their own section and are detailed before Linux equivalents in some places. The CLI examples are all Bash/Azure CLI, but there are no PowerShell-specific examples, and Linux is not omitted. However, Windows node pool configuration is described in detail, sometimes before Linux, and Windows-specific tools (like HNS ACLPolicy) are mentioned alongside Linux equivalents (iptables).
Recommendations
  • Ensure Linux and Windows instructions are presented in parallel or with clear separation, so Linux users can easily find relevant steps.
  • Where possible, provide Linux-first examples and clarify Windows-specific steps as optional or alternative.
  • Add explicit notes or navigation to help Linux/macOS users skip Windows-only steps.
  • Consider including PowerShell equivalents for Azure CLI commands if Windows users are expected to use PowerShell.
  • Maintain clear labeling for OS-specific instructions to avoid confusion.
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 exclusively uses Azure CLI examples with shell environment variable syntax (e.g., $RESOURCE_GROUP), which is compatible with Bash (Linux/macOS) and PowerShell (Windows). However, there is a subtle bias in that the examples use the $VAR syntax, which is native to PowerShell and Bash, but the documentation does not explicitly clarify cross-platform compatibility or provide Linux/macOS-specific notes. There are no explicit Windows-only tools or patterns, but the order and style may be more familiar to Windows users.
Recommendations
  • Add a note clarifying that all Azure CLI commands are cross-platform and work on Linux, macOS, and Windows.
  • Explicitly mention that the $VAR syntax works in Bash and PowerShell, and provide an example for Linux/macOS users if needed (e.g., export VAR=value).
  • Consider including a Linux/macOS-specific example or note for setting environment variables, or use a more generic syntax.
  • Ensure that browser navigation instructions are platform-neutral (currently they are).
GitHub Create Pull Request