← Back to Dashboard
128
Pages Scanned
13
Pages Flagged
128
Changed Pages
10.2%
% Pages Flagged

Live Progress

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

Scan Information

Started At: 2026-02-23 00:00:32

Finished At: In Progress

Status: in_progress

Target Repo: Azure Aks

Current Phase: discovery

Files Queued: 128

Files Completed: 128

Problematic Pages

13 issues found
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 troubleshooting, but consistently presents Azure CLI (cross-platform) first and then Azure PowerShell (Windows-centric). There are no explicit Windows-only tools or patterns, and all examples are generally applicable to Linux and macOS users. However, the inclusion of PowerShell examples may create minor friction for Linux/macOS users, as PowerShell is less commonly used on those platforms.
Recommendations
  • Clearly indicate that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Add explicit notes or tabs for Bash (where relevant) to reinforce Linux parity.
  • Consider referencing PowerShell as 'for Windows users' or noting its cross-platform availability.
  • Ensure troubleshooting steps do not assume PowerShell is available on Linux/macOS.
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 (local/Docker) and cluster (Helm/Kubernetes) modes. While the guide is generally cross-platform, there is a minor bias in the Docker daemon startup instructions: Windows/macOS (Docker Desktop) are mentioned before Linux (systemctl commands). All CLI examples use Azure CLI, which is cross-platform, and Linux-specific commands (e.g., kubectl, bash) are included. No critical Windows-only tools or PowerShell examples are present.
Recommendations
  • In the Docker daemon startup section, present Linux instructions before or alongside Windows/macOS instructions, or clarify that all OSes are equally supported.
  • Explicitly mention that Docker Desktop is available for both Windows and macOS, and that Linux users should use system services.
  • Ensure that any troubleshooting or FAQ sections also provide parity for Linux/macOS users if OS-specific issues are discussed.
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 (Docker Desktop) are listed before Linux, which is a minor 'windows_first' bias. All other examples and solutions include Linux commands and do not rely on Windows-specific tools or PowerShell.
Recommendations
  • Present Linux, macOS, and Windows instructions in parallel or in a consistent order (e.g., Linux, macOS, Windows) to avoid the perception of prioritizing Windows.
  • Where possible, clarify when steps are identical across platforms, and only separate out platform-specific instructions as needed.
  • Consider adding explicit Linux/macOS/Windows tabs or callouts for clarity if instructions differ.
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 is generally cross-platform and focuses on AKS storage concepts applicable to both Linux and Windows node pools. However, in the section on mounting volumes in pods, the Linux example is shown first, followed by a Windows-specific example. There are no PowerShell-heavy examples, Windows tools, or missing Linux examples. The only minor bias is that Windows mounting syntax is shown after the Linux example, which is a common and reasonable pattern.
Recommendations
  • Ensure that Windows and Linux examples are equally represented and clearly labeled.
  • Consider adding explicit notes when features or syntax differ between Linux and Windows containers.
  • If possible, provide side-by-side examples for mounting volumes in both Linux and Windows pods for clarity.
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 and AKS is a Linux-first service, but 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 immediately after the Linux path, and no further Windows-specific commands or examples are provided elsewhere. All command-line examples use Azure CLI and bash/kubectl, which are standard for Linux/macOS and Windows (via WSL or Azure Cloud Shell). There are no PowerShell-specific examples or Windows-only tools used. However, the documentation could improve parity by clarifying Windows node pool differences and providing more explicit Linux/Windows distinctions where relevant.
Recommendations
  • In the 'Verify TLS Bootstrapping is enabled' section, clarify that most AKS clusters use Linux nodes by default, and Windows node pools are optional.
  • Provide explicit instructions or links for accessing Windows node pools (e.g., using PowerShell or Windows-native tools) if relevant.
  • Where file paths differ, consider providing both Linux and Windows examples equally, or note which is more common.
  • Add a brief note about Azure CLI and kubectl usage on Windows (e.g., via WSL, PowerShell, or Azure Cloud Shell) to help Windows users.
  • Ensure that any Windows-specific instructions are clearly marked as such and do not precede Linux instructions unless the topic is Windows-specific.
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. While Azure CLI is cross-platform, the PowerShell section is prominent and detailed, and PowerShell is traditionally associated with Windows. The PowerShell prerequisites and instructions are listed before Azure CLI, and PowerShell-specific guidance is more extensive. However, Azure CLI examples are present and fully functional for Linux/macOS users. There are no Windows-only tools or missing Linux examples, but the ordering and emphasis slightly favor Windows/PowerShell.
Recommendations
  • Consider listing Azure CLI instructions before PowerShell, as CLI is more widely used across platforms.
  • Clarify that both Azure PowerShell and Azure CLI are fully supported on Linux/macOS, and highlight this in the prerequisites.
  • Balance the depth of instructions between PowerShell and CLI sections to avoid perceived preference.
  • Explicitly mention that Azure Cloud Shell supports Bash (for CLI) as well as PowerShell, and that both are available to all users.
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
⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation is generally cross-platform, focusing on Azure CLI and Bicep for installing Dapr on AKS, which are available on Windows, Linux, and macOS. However, in the 'List the CRDs in your cluster' section, the example uses 'kubectl get crds | findstr dapr.io', which is a Windows-specific command (findstr). No equivalent Linux/macOS example (e.g., using 'grep') is provided. This is a minor bias, as most of the workflow is platform-agnostic, but the CRD listing step could create friction for Linux/macOS users.
Recommendations
  • Provide both Windows and Linux/macOS examples for listing CRDs, e.g., 'kubectl get crds | grep dapr.io' for Linux/macOS.
  • Review other command examples to ensure they are platform-agnostic or offer alternatives for different OS environments.
  • Explicitly state that Azure CLI and Bicep are supported on all major platforms to reassure non-Windows 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 prerequisite steps, but references to PowerShell (a Windows-centric tool) are present alongside Azure CLI. Azure CLI is cross-platform, but PowerShell is typically Windows-first. The PowerShell cmdlet for listing subnets is mentioned after the Azure CLI command, so Linux parity is mostly maintained. However, the 'Before you begin' section and subnet listing instructions include PowerShell references, which may create minor friction for Linux/macOS users.
Recommendations
  • Clearly indicate that Azure CLI is the recommended, cross-platform tool for all steps.
  • Move PowerShell references to a dedicated section or appendix for Windows users, rather than mixing them with main instructions.
  • Where PowerShell is mentioned, provide equivalent Bash/Linux commands (if any) or clarify that Azure CLI covers all required functionality.
  • Consider removing PowerShell references from the main flow unless a Windows-only 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 for installation and management, which are cross-platform. However, the examples are labeled as 'azurecli-interactive', and there is no explicit mention of PowerShell or Windows-specific tools. The verification steps use 'kubectl' and 'jq', which are standard Linux/macOS tools, and the commands are shown in Bash syntax. There is a minor bias in that Azure CLI examples are shown first and exclusively, with no mention of alternative methods (such as using Azure Cloud Shell, Bash, or PowerShell), but this does not significantly impact Linux/macOS users.
Recommendations
  • Clarify that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
  • Add a note or link to instructions for installing Azure CLI and kubectl on Linux/macOS.
  • Optionally provide PowerShell equivalents if relevant, but ensure Bash/Linux examples are equally represented.
  • Mention that Azure Cloud Shell can be used from any OS for these commands.
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 (a Windows-centric tool) is given equal prominence to Azure CLI. In some sections, PowerShell examples are shown before or alongside CLI, which may create friction for Linux/macOS users. However, all critical tasks can be completed with Azure CLI, and bash commands are used for Helm and kubectl, ensuring Linux parity.
Recommendations
  • Consider making Azure CLI the primary/default example, as it is cross-platform, and move PowerShell instructions to secondary tabs or sections.
  • Explicitly state that Azure CLI is recommended for Linux/macOS users, and PowerShell is for Windows users.
  • Ensure that all bash commands (helm, kubectl, git) are clearly marked as cross-platform and do not reference Windows-specific shell behaviors.
  • Add a brief note clarifying that PowerShell is not required for Linux/macOS users.
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 tasks (such as installing/updating kubectl and listing available Kubernetes versions), but consistently presents Azure CLI (Linux/macOS-friendly) examples first. There are no Windows-only tools or patterns, and Linux-specific information is included where relevant (e.g., OS components, Azure Linux retirement). However, there are no explicit bash or Linux shell examples, and PowerShell is always presented as an alternative, not exclusively. No critical tasks are Windows-only, and Linux parity is maintained.
Recommendations
  • Consider adding explicit bash or Linux shell examples for commands where Azure CLI is used, to reinforce Linux/macOS parity.
  • Clarify that Azure CLI commands work cross-platform (Windows, Linux, macOS) and are recommended for Linux/macOS users.
  • Add a brief note that Azure PowerShell is primarily for Windows users, while Azure CLI is cross-platform.
  • If possible, provide links to Linux/macOS installation instructions for Azure CLI and kubectl.
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 parity for both Linux and Windows node pools in AKS, but there is a slight bias toward Windows in some sections. Windows-specific steps (such as registering preview features and creating Windows admin credentials) are presented in detail and sometimes before Linux equivalents. However, Linux examples and instructions are present and comprehensive. All CLI examples use Bash/Azure CLI, not PowerShell, and Linux is referenced throughout, but Windows-specific tooling and steps are highlighted in dedicated sections.
Recommendations
  • Ensure Linux and Windows instructions are presented with equal prominence and clarity.
  • Where possible, group Linux and Windows steps side-by-side for easier comparison.
  • Clarify when steps are Windows-only and provide Linux equivalents or explicitly state when not applicable.
  • Maintain consistent ordering (e.g., Linux first, Windows second, or vice versa) throughout the document.
  • Add explicit notes when a feature or step is not available for Linux or Windows, to avoid confusion.
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 are prominent and given equal weight to Azure CLI. PowerShell is primarily a Windows 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 some sections, and there are no explicit Bash/Linux shell examples outside of Azure CLI. However, Azure CLI is presented as the main cross-platform tool, and the tutorial does not rely on Windows-only features.
Recommendations
  • Clarify that Azure CLI commands are fully supported on Linux/macOS and recommend it as the primary cross-platform option.
  • Add explicit Bash shell examples for common tasks (e.g., setting environment variables, running Azure CLI commands) to reinforce Linux parity.
  • Consider moving Azure CLI examples before PowerShell in each section to emphasize cross-platform support.
  • Mention that PowerShell Core is available on Linux/macOS, but highlight Azure CLI as the default for non-Windows users.
  • Add a note in the 'Before you begin' section indicating that Azure CLI is recommended for Linux/macOS users.
GitHub Create Pull Request