← Back to Dashboard
125
Pages Scanned
11
Pages Flagged
125
Changed Pages
8.8%
% Pages Flagged

Live Progress

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

Scan Information

Started At: 2026-02-20 00:00:07

Finished At: In Progress

Status: in_progress

Target Repo: Azure Aks

Current Phase: discovery

Files Queued: 125

Files Completed: 125

Problematic Pages

11 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 cross-platform, focusing on Azure CLI and Bicep, which are available on Windows, Linux, and macOS. However, there is a notable instance where a Windows-specific command (`findstr`) is used with `kubectl` to filter CRDs, and this is presented without a Linux/macOS equivalent. Additionally, the use of PowerShell-style variable assignment (`$MY_RESOURCE_GROUP`) in CLI examples may be confusing for Bash users. No explicit Linux or macOS examples are provided for these cases.
Recommendations
  • For the `kubectl get crds | findstr dapr.io` example, provide a cross-platform alternative, such as `kubectl get crds | grep dapr.io` for Linux/macOS.
  • When showing variable assignment for Azure CLI commands, include both PowerShell (`$VAR=...`) and Bash (`VAR=...`) syntax, or clarify which shell is being used.
  • Review all CLI examples to ensure they are shell-agnostic or provide alternatives for both Windows and Linux/macOS users.
  • Consider adding a short note at the start of the CLI sections indicating that the Azure CLI and Bicep commands work on all major platforms, and point to shell-specific guidance if needed.
GitHub Create Pull Request
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 tutorial provides parallel instructions for Azure CLI, Azure PowerShell, and Azure Developer CLI, but PowerShell examples and terminology are prominent throughout. PowerShell is a Windows-centric tool, and its inclusion alongside Azure CLI may signal a Windows bias. Additionally, PowerShell sections are consistently presented before Azure Developer CLI, and sometimes Azure CLI instructions reference Bash/Cloud Shell but do not explicitly mention Linux/macOS environments or alternatives. There are no explicit Linux/macOS examples or shell-specific guidance for those platforms.
Recommendations
  • Add explicit guidance for Linux/macOS users, such as referencing Bash or Zsh environments and confirming compatibility of Azure CLI commands.
  • Clarify that Azure CLI commands work on Windows, Linux, and macOS, and provide links to platform-specific installation instructions.
  • Consider including example commands for Bash (Linux/macOS) where appropriate, especially for environment variable usage and SSH key management.
  • Balance PowerShell and Azure CLI coverage by mentioning that PowerShell is primarily for Windows users, while Azure CLI is cross-platform.
  • Where possible, provide parity in examples for Linux/macOS users, such as using native shell commands for tasks like SSH key generation.
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 detailed, with installation/upgrade instructions for Windows, macOS, and Linux. However, PowerShell is a Windows-centric tool, and its section appears before the Azure CLI, which is more native to Linux/macOS users. The CLI section is present and functional, but the ordering and emphasis on PowerShell may create friction for Linux/macOS users.
Recommendations
  • Present Azure CLI examples before Azure PowerShell, as CLI is more cross-platform and native for Linux/macOS users.
  • Explicitly mention that both Azure CLI and PowerShell are fully supported on Linux/macOS, and link to installation instructions for both.
  • Consider adding Bash shell examples where relevant, or clarify that Azure CLI commands work in Bash, Zsh, etc.
  • Balance the detail level between PowerShell and CLI sections to avoid implying PowerShell is preferred.
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 cluster authorized IP ranges, but consistently presents Azure CLI (Linux/macOS-friendly) examples first. However, the PowerShell section is equally detailed and not prioritized over Linux tools. No Windows-specific tools, patterns, or PowerShell-only instructions are present elsewhere. The documentation is largely platform-neutral, focusing on portal-based workflows and Azure CLI, with PowerShell as an alternative.
Recommendations
  • Maintain Azure CLI examples as the primary cross-platform option, as currently done.
  • Consider explicitly stating that Azure CLI works on Windows, Linux, and macOS, and that PowerShell is an alternative for Windows users.
  • If possible, add a note clarifying that all portal and Azure CLI instructions are OS-agnostic.
  • Ensure that any future troubleshooting or command-line sections continue to offer both CLI and PowerShell options, with CLI shown first.
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 Windows-specific guidance appears after the Linux example. There are no PowerShell-heavy examples, Windows tools, or missing Linux examples. The only evidence of bias is that Windows container mounting instructions are presented after Linux, which is a minor ordering preference.
Recommendations
  • Consider presenting Linux and Windows container volume mounting examples side-by-side or with equal prominence.
  • Explicitly clarify when instructions apply to Linux, Windows, or both, to improve clarity for cross-platform users.
  • Ensure all YAML and CLI examples are provided for both Linux and Windows scenarios where relevant.
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 both Windows/macOS and Linux instructions for Docker daemon startup, but lists Windows/macOS instructions before Linux. All CLI examples use cross-platform Azure CLI and Bash commands, and there are no PowerShell-specific or Windows-only tools mentioned. The documentation is generally neutral, but the ordering of instructions for Docker startup shows a minor 'windows_first' bias.
Recommendations
  • Present Linux instructions before or alongside Windows/macOS instructions, especially for Docker daemon startup.
  • Explicitly state that all CLI examples work on Linux, macOS, and Windows.
  • Where possible, use OS-neutral language and avoid implying Windows/macOS as the default environment.
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 examples and instructions for both Linux and Windows environments, but in some sections, Windows paths are mentioned alongside Linux paths (e.g., in the TLS Bootstrapping section), and Windows nodes are referenced in example output. However, the majority of commands and examples are cross-platform (Azure CLI, kubectl, openssl, curl), and Linux paths are generally shown first. There is minor bias in mentioning Windows paths and node names in output examples, but no critical Windows-only instructions or tools are used.
Recommendations
  • Ensure Linux and Windows examples are presented with equal prominence, ideally listing Linux instructions first if Linux is the default AKS node type.
  • Where output examples reference Windows node names (e.g., 'akswinp7000000'), add Linux node name examples for parity.
  • Clarify that Azure CLI and kubectl commands are cross-platform and provide any OS-specific caveats if needed.
  • For file paths, always show both Linux and Windows variants together, and note which applies to which node type.
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: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_missing ⚠ī¸ windows_tools
Summary
The documentation provides troubleshooting steps for the Agentic CLI for AKS and covers both Windows/macOS and Linux environments. However, there is a mild bias: Windows/macOS solutions (e.g., 'Launch Docker Desktop') are listed before Linux solutions, and Windows tooling (Docker Desktop) is mentioned without referencing Linux alternatives (such as dockerd or systemd management). There are no PowerShell examples, but Windows users are expected to use Docker Desktop, which is a Windows/macOS-specific tool. All CLI commands are cross-platform, and Linux-specific commands are included, so Linux users can complete all tasks.
Recommendations
  • Present Linux and Windows/macOS troubleshooting steps in parallel or with equal prominence.
  • Mention Linux-native Docker management tools (dockerd, systemctl) alongside Docker Desktop.
  • Add explicit notes about differences in Docker installation and management between platforms.
  • Consider including Linux-first examples where appropriate, or alternate the order.
  • Clarify that Docker Desktop is not available on Linux and provide links to Linux Docker installation guides.
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 some prerequisite steps, but the PowerShell tool is mentioned alongside Azure CLI and portal as a way to create an AKS cluster. Additionally, the PowerShell cmdlet 'Get-AzVirtualNetworkSubnetConfig' is referenced for listing subnets, but no Linux/macOS equivalent (such as Azure CLI or Bash) is shown in that context. Azure CLI is used for most examples, which is cross-platform, but PowerShell is referenced without clear parity for Linux users in those sections.
Recommendations
  • When listing ways to create an AKS cluster, mention Azure CLI and portal first, and clarify that PowerShell is primarily for Windows users.
  • For subnet listing, provide Azure CLI examples before or alongside PowerShell, and clarify that Azure CLI works on Linux/macOS.
  • Where PowerShell is referenced, always provide the Azure CLI equivalent and note its cross-platform compatibility.
  • Consider removing PowerShell-only references unless the feature is Windows-specific, or add a note about platform compatibility.
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 examples for all Azure-related tasks, but consistently includes Azure PowerShell (a Windows-centric tool) as a primary option alongside Azure CLI. Azure PowerShell examples are given equal prominence, and in some sections, PowerShell is mentioned before Linux-native alternatives. However, all core Kubernetes and Helm commands use cross-platform bash examples, and there are no Windows-only tools or patterns used for the main Helm/AKS workflow.
Recommendations
  • Consider clarifying that Azure PowerShell is primarily for Windows users, and Azure CLI is cross-platform (Linux, macOS, Windows).
  • Where possible, show Azure CLI examples first, as it is the default for Linux/macOS users.
  • Add brief notes indicating that Azure PowerShell is not available natively on most Linux distributions, and recommend Azure CLI for Linux/macOS users.
  • Ensure that bash commands and Helm/Kubectl instructions are always shown as the default, with PowerShell as an optional alternative for Windows 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 ⚠ī¸ windows_tools
Summary
The documentation provides examples for Azure CLI and Azure PowerShell, with PowerShell (a Windows-centric tool) given equal prominence to Azure CLI. In some sections, Windows-specific tools and OS versions are mentioned alongside Linux equivalents, but there is no clear bias toward Windows-only tools or patterns. No Linux/macOS-specific CLI examples (such as Bash or shell scripting) are provided, but Azure CLI is cross-platform. Windows and Linux OS components are listed together in breaking changes tables, and Windows is not prioritized over Linux in descriptions.
Recommendations
  • Add explicit Bash or shell examples for Linux/macOS users where Azure CLI is used, clarifying cross-platform compatibility.
  • Consider mentioning that Azure CLI works on Linux/macOS and Windows, and provide links to installation instructions for all platforms.
  • If referencing PowerShell, clarify its availability on Linux/macOS and link to cross-platform installation guides.
  • Ensure that any OS-specific instructions or examples are grouped or labeled by platform, so Linux/macOS users can easily find relevant information.
GitHub Create Pull Request