← Back to Dashboard
152
Pages Scanned
14
Pages Flagged
152
Changed Pages
9.2%
% Pages Flagged

Live Progress

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

Scan Information

Started At: 2026-03-01 00:00:07

Finished At: In Progress

Status: in_progress

Target Repo: Azure Aks

Current Phase: discovery

Files Queued: 152

Files Completed: 152

Problematic Pages

15 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: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation is generally platform-agnostic and focuses on Azure CLI and Bicep, which are cross-platform tools. However, in the 'List the CRDs in your cluster' section, only a Windows-specific example using 'kubectl get crds | findstr dapr.io' (with PowerShell syntax) is provided. There is no equivalent Linux/macOS example (e.g., using 'grep'), and the use of 'findstr' is a Windows tool, creating friction for non-Windows users.
Recommendations
  • Add a Linux/macOS example for listing CRDs, such as 'kubectl get crds | grep dapr.io'.
  • Mention that 'findstr' is Windows-specific and provide 'grep' as the cross-platform alternative.
  • Review future documentation sections to ensure CLI examples are cross-platform or alternatives are provided.
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 Docker daemon startup instructions for macOS/Windows before Linux, and refers to 'Docker Desktop' for macOS/Windows, which is a Windows-centric pattern. However, all critical commands and examples are cross-platform, and Linux-specific instructions are present. No PowerShell-only examples or Windows-only tools are used.
Recommendations
  • Present Linux instructions before or alongside Windows/macOS instructions when describing Docker daemon startup.
  • Clarify that 'Docker Desktop' is not available for Linux, and provide equivalent Linux GUI options (if any) or emphasize command-line usage.
  • Consider grouping OS-specific instructions in parallel lists or tables for parity.
  • Explicitly mention that all az CLI commands are cross-platform and provide links to az CLI installation guides for Linux/macOS/Windows.
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 both Windows/macOS and Linux users, but Windows/macOS solutions (Docker Desktop) are often mentioned before Linux equivalents. Windows-specific tooling (Docker Desktop) is referenced, while Linux solutions use system commands. All critical tasks are covered for Linux, but Windows/macOS instructions are presented first in several sections.
Recommendations
  • Present Linux and Windows/macOS troubleshooting steps in parallel or with equal prominence, rather than listing Windows/macOS first.
  • Explicitly mention that Docker Desktop is not available on Linux, and clarify the Linux-specific alternatives.
  • Where possible, provide command-line solutions for Windows (e.g., PowerShell commands for Docker service management) to match Linux parity.
  • Consider grouping troubleshooting steps by OS, or using tabs for OS-specific instructions to avoid implicit prioritization.
GitHub Create Pull Request
Aks Use Microsoft Entra ID and Kubernetes RBAC for clusters ...azure-aks-docs/blob/main/articles/aks/azure-ad-rbac.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides command-line examples exclusively using Azure CLI and Bash-style syntax (e.g., variable assignment, read prompts), which are native to Linux/macOS environments but also work in Windows via WSL or Azure Cloud Shell. However, there are no explicit PowerShell or Windows Command Prompt examples, nor are Windows-specific tools or patterns mentioned. The Azure CLI commands are cross-platform, but the documentation assumes Bash shell usage, which may create friction for Windows users who do not use WSL or Cloud Shell.
Recommendations
  • Add explicit notes clarifying that Azure CLI commands can be run in Windows Command Prompt or PowerShell, and provide equivalent syntax for variable assignment and input prompts in those environments.
  • Include PowerShell examples for Azure CLI commands, especially for variable assignment and user input, to ensure Windows parity.
  • Mention that Azure Cloud Shell is available in the Azure portal and supports both Bash and PowerShell, making the examples universally applicable.
  • Consider providing a table or tabs for Bash, PowerShell, and Command Prompt where commands differ.
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 provides parity for both Linux and Windows users, 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. The documentation references Azure CLI and kubectl, which are cross-platform tools, and shell commands are shown in Bash syntax, suitable for Linux/macOS. There are no PowerShell-specific examples or Windows-only tools used, and all critical tasks can be completed on Linux/macOS. However, the inclusion of Windows paths and references to Windows nodes (even though not prioritized) shows minor Windows bias.
Recommendations
  • Ensure Linux/macOS examples are shown first, or equally with Windows examples.
  • Explicitly state that all Azure CLI and kubectl commands work on Linux/macOS, and provide any necessary notes for Windows users (e.g., path differences, shell syntax).
  • Where file paths are referenced, clarify OS differences and provide both Linux and Windows paths in parallel.
  • If possible, add example outputs from both Linux and Windows environments for commands that may differ.
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 includes detailed instructions for installation and usage, referencing Windows, macOS, and Linux. However, PowerShell is traditionally Windows-centric, and its section appears before the Azure CLI, which is more native to Linux/macOS environments. There is no explicit bias in the examples themselves, as both PowerShell and CLI are covered, but PowerShell is given more detailed treatment and appears first, which may subtly favor Windows users.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is more universally supported across platforms.
  • Ensure that CLI instructions are as detailed as PowerShell instructions, including environment preparation and troubleshooting.
  • Explicitly mention that both PowerShell and CLI are cross-platform, but highlight CLI as the preferred option for Linux/macOS users.
  • Consider adding Bash shell examples where relevant, especially for Linux/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 is generally platform-neutral and covers AKS storage concepts applicable to both Linux and Windows node pools. However, in the section on mounting volumes in pods, the Linux example is presented first, followed by the Windows example. There are no PowerShell-heavy examples, Windows tools, or missing Linux examples. All YAML manifests and storage concepts are generic and applicable to both platforms, with a brief note on Windows-specific mounting syntax.
Recommendations
  • Ensure that Linux and Windows examples are presented with equal prominence, possibly side-by-side or with clear headings.
  • Clarify in the mounting section that both Linux and Windows containers are supported, and provide explicit examples for both where relevant.
  • Add a short note at the start of the mounting section indicating that the syntax differs for Linux and Windows containers, to help users quickly find the relevant information.
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 primarily Linux-focused, as AKS clusters default to Linux nodes and most examples use Linux paths and conventions. However, there are minor signs of Windows bias: Windows-specific instructions and path conventions are sometimes mentioned before Linux equivalents, and references to Windows tools (such as PowerShell/CMD path syntax) are included even when Linux is the primary context. Additionally, links to SMB protocol documentation point to Windows-centric resources.
Recommendations
  • When mentioning Windows-specific instructions (e.g., path conventions), place Linux instructions first, as Linux is the default for AKS.
  • Provide parity in examples: if Windows paths or commands are shown, ensure Linux equivalents are equally prominent and vice versa.
  • Where possible, link to cross-platform documentation for SMB/NFS protocols, not just Windows-centric pages.
  • Clarify when a section is Windows-specific, and avoid mixing Windows and Linux instructions unless necessary.
  • Review output examples and ensure they reflect both Linux and Windows environments if relevant.
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 tool for moving resources, alongside Azure CLI and the Azure portal. Azure PowerShell is a Windows-centric tool, and its mention is not accompanied by Linux-specific alternatives (such as Bash scripts or Linux-native tools). However, the primary examples throughout the guide use Azure CLI and kubectl, which are cross-platform. The mention of Azure PowerShell occurs before Azure CLI in the list of migration tools, which may subtly prioritize Windows tooling.
Recommendations
  • Clarify that Azure PowerShell is available cross-platform, or explicitly mention that Azure CLI and Azure portal are recommended for Linux/macOS users.
  • List Azure CLI before Azure PowerShell when describing migration options, as CLI is more universally available.
  • If possible, provide a brief example or link for Linux users on how to install and use Azure CLI and kubectl.
  • Consider adding a note that all CLI and kubectl commands are fully supported on Linux/macOS.
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 Azure PowerShell and its cmdlets alongside Azure CLI in several places. The PowerShell example ('Get-AzVirtualNetworkSubnetConfig') is mentioned directly after the Azure CLI command for listing subnets, and the quickstart links list Azure PowerShell before the Azure portal. However, all core examples and walkthroughs use kubectl and Azure CLI, which are cross-platform and Linux-friendly. No critical steps are Windows-only, and Linux users can complete all tasks without friction.
Recommendations
  • When listing tools or commands, mention Azure CLI first, as it is cross-platform, and clarify that Azure PowerShell is optional for Windows users.
  • Provide Linux/macOS-specific notes or examples where relevant (e.g., shell variable syntax differences).
  • Consider removing or de-emphasizing PowerShell references unless necessary for a Windows-specific workflow.
  • Ensure that all prerequisite links and instructions are equally accessible and clear for Linux/macOS 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 managing AKS authorized IP ranges, but the PowerShell example is given equal prominence and detail as the CLI example. Azure PowerShell is primarily used on Windows, and the documentation does not mention Bash or shell alternatives for Linux/macOS users. The CLI example uses a command ('dig') that is not universally available on Windows, but is standard on Linux/macOS, while the PowerShell example is Windows-centric. The rest of the documentation is portal-focused and platform-neutral.
Recommendations
  • Explicitly note that Azure CLI commands can be run in Bash on Linux/macOS and in Cloud Shell for all platforms.
  • Provide Bash shell alternatives for retrieving the public IP address (e.g., 'curl ifconfig.me' or 'curl ipinfo.io/ip') for Linux/macOS users.
  • Clarify that Azure PowerShell is primarily for Windows users, and suggest Azure CLI for cross-platform compatibility.
  • Consider listing Azure CLI (Bash) examples first, as CLI is more widely used across platforms.
GitHub Create Pull Request
Aks Configure LocalDNS in Azure Kubernetes Service (AKS) ...ure-aks-docs/blob/main/articles/aks/localdns-custom.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation page provides links to AKS cluster creation guides for Azure CLI, PowerShell, and Portal, with PowerShell mentioned alongside CLI and Portal. However, all command examples and instructions use Azure CLI and kubectl, which are cross-platform tools. No Windows-specific tools, patterns, or PowerShell-only examples are present. The documentation explicitly states LocalDNS is only supported on Azure Linux or Ubuntu 22.04+ node pools, and all operational guidance is Linux-centric. The only minor bias is mentioning Azure PowerShell as an option for cluster creation before Linux-specific alternatives, but this does not affect the main LocalDNS configuration workflow.
Recommendations
  • Consider listing Azure CLI and Portal options before PowerShell in the prerequisites section, or clarify that all subsequent instructions are CLI-based and cross-platform.
  • Explicitly state that Azure CLI and kubectl commands work on Windows, Linux, and macOS to reinforce platform parity.
  • If possible, provide a brief note that PowerShell is not required for LocalDNS configuration and that all steps are platform-agnostic.
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 tasks, but consistently presents Azure CLI (which is cross-platform) before Azure PowerShell (which is Windows-centric). There are no explicit Windows-only tools or patterns, and Linux/macOS users can complete all tasks using Azure CLI and bash commands. However, the presence of PowerShell examples and references may create minor friction for Linux/macOS users, as PowerShell is less commonly used on those platforms.
Recommendations
  • Consider clarifying that Azure CLI is recommended for Linux/macOS users, while PowerShell is primarily for Windows users.
  • Optionally, add a note at the top indicating that Azure CLI is cross-platform and preferred for non-Windows environments.
  • Ensure that bash commands and Azure CLI examples are prominent and clearly marked as suitable for Linux/macOS.
  • If possible, provide bash-only quickstart sections for Linux/macOS users to streamline their experience.
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 friction for Linux/macOS users. Additionally, PowerShell instructions are often presented immediately after Azure CLI, which may subtly reinforce Windows as a primary platform. However, Azure CLI is always present and is shown first, and all commands are cross-platform compatible. No critical steps are Windows-only, and Linux/macOS users can complete the tutorial without issue.
Recommendations
  • Consider clarifying that Azure PowerShell is primarily for Windows users, while Azure CLI is cross-platform.
  • Explicitly mention that Azure CLI commands work on Linux/macOS and Windows, and that PowerShell is optional.
  • Add a brief note in the 'Before you begin' section about platform compatibility for each tool.
  • If possible, provide Bash shell examples for Linux/macOS users, especially for environment variable setup and SSH key management.
  • Ensure that Azure CLI is always presented as the default or recommended method for cross-platform parity.
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 examples for both Linux and Windows node pools in AKS, but Windows-specific steps (such as registering preview features and creating Windows admin credentials) are presented in detail and before Linux equivalents. The Windows section is more verbose and includes additional steps, while Linux instructions are concise. All CLI examples use Azure CLI and Bash, which are cross-platform, but there are no PowerShell-specific examples. However, Windows-specific configuration steps are described in depth, potentially creating friction for Linux/macOS users seeking parity.
Recommendations
  • Ensure Linux and Windows instructions are equally detailed and placed in parallel sections.
  • Clearly separate Linux and Windows steps, labeling them for each OS to avoid confusion.
  • Add explicit notes when steps are Windows-only or Linux-only, and provide links to Linux-specific guidance where appropriate.
  • Consider providing PowerShell examples for Windows users and Bash examples for Linux/macOS users, or clarify that Azure CLI commands are cross-platform.
  • Review the order of presentation to avoid Windows-first bias unless the feature is Windows-specific.
GitHub Create Pull Request