← Back to Dashboard
83
Pages Scanned
9
Pages Flagged
83
Changed Pages
10.8%
% Pages Flagged

Scan Information

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

Finished At: 2026-02-10 18:44:36

Status: completed

Target Repo: Azure Aks

Current Phase: discovery

Files Queued: 83

Files Completed: 83

Problematic Pages

9 issues found
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 is generally cross-platform, with most examples and instructions using Azure CLI and kubectl, which are available on both Windows and Linux/macOS. However, there are minor instances of Windows bias: in the 'Verify TLS Bootstrapping is enabled on current agent node pool' section, the Windows file path is mentioned immediately after the Linux path, and the Windows path uses drive letter notation. Additionally, Azure CLI is presented as the primary tool for cluster management, which is available on all platforms but may be more familiar to Windows users.
Recommendations
  • Ensure Linux and macOS file paths are always presented first, or present both paths simultaneously in a table or side-by-side format.
  • Clarify that Azure CLI and kubectl commands work on Linux, macOS, and Windows, and provide installation links for all platforms.
  • Where file paths differ, explicitly state which OS each path applies to, and consider providing screenshots or example outputs for both environments.
  • If there are any platform-specific caveats (e.g., differences in shell syntax), note them in the relevant sections.
GitHub Create Pull Request
Aks Install the Dapr extension for Azure Kubernetes Service (AKS) and Arc-enabled Kubernetes ...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 generally cross-platform, focusing on Azure CLI and Bicep for Dapr extension management on AKS and Arc-enabled Kubernetes clusters. However, there is a minor Windows bias in the CRD cleanup section, where the example for listing Dapr CRDs uses PowerShell's 'findstr' command with 'kubectl', which is Windows-specific. No Linux/macOS equivalent (e.g., 'grep') is provided, and the example is not marked as Windows-only. Additionally, the PowerShell example appears before any Linux alternative, which is missing.
Recommendations
  • Provide Linux/macOS equivalent commands for CRD listing, such as 'kubectl get crds | grep dapr.io'.
  • Clearly label platform-specific commands (e.g., 'Windows example', 'Linux/macOS example').
  • Ensure that examples for common tasks (like using kubectl) include both Windows and Linux/macOS variants.
  • Consider showing Linux/macOS examples first, or side-by-side, to reinforce cross-platform parity.
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: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ windows_tools
Summary
The documentation provides three main approaches for configuring Azure CNI networking in AKS: Azure portal, Azure PowerShell, and Azure CLI. The PowerShell section is detailed and references Windows-centric tools and patterns, such as Azure PowerShell cmdlets and instructions for installing/upgrading PowerShell on Windows, macOS, and Linux. The PowerShell example is given before the CLI example, and there is a slight emphasis on PowerShell/Windows tooling. However, the CLI instructions are cross-platform and allow Linux/macOS users to complete the task without significant friction.
Recommendations
  • Ensure that Azure CLI examples are given equal prominence and, where possible, presented before or alongside PowerShell examples, as CLI is more universally available across platforms.
  • Clarify that both Azure PowerShell and Azure CLI are supported on Windows, macOS, and Linux, and highlight CLI as the recommended cross-platform approach.
  • Consider adding explicit notes or links for Linux/macOS users to guide them to CLI usage, especially in introductory sections.
  • Avoid language that implies PowerShell is the default or preferred method unless there is a technical reason.
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 and subnet/resource group queries, but consistently mentions Azure PowerShell alongside Azure CLI and lists PowerShell cmdlets as alternatives for tasks like subnet listing. The Azure CLI is used for all procedural examples, but PowerShell is referenced in 'Before you begin' and 'Specify an IP address' sections, and is linked before Linux-native alternatives (e.g., Bash scripting). No Linux/macOS-specific tools or shell examples are provided, and PowerShell is mentioned as an equal alternative to Azure CLI rather than as a Windows-only tool.
Recommendations
  • Clarify that Azure PowerShell is primarily for Windows users and that Azure CLI is cross-platform.
  • List Azure CLI (cross-platform) examples and links before PowerShell alternatives.
  • Where PowerShell is mentioned, also provide Bash or shell scripting equivalents for Linux/macOS users.
  • Explicitly state that all Azure CLI commands work on Linux/macOS/Windows.
  • Consider removing PowerShell references from main instructions unless a Windows-specific workflow is required.
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) instructions in the troubleshooting section. However, the Azure CLI tab is presented first, which is appropriate for Linux/macOS parity. There are no exclusive Windows tools or PowerShell-only instructions, and all critical tasks can be completed using the Azure CLI. The documentation does not provide any Windows-only examples or tools, and the main workflow is through the Azure portal, which is platform-agnostic.
Recommendations
  • Maintain Azure CLI as the first/default example in all code tabs, as it is cross-platform.
  • Ensure that any future additions of scripts or command-line instructions always include Azure CLI (or bash) equivalents when PowerShell is shown.
  • Explicitly mention that Azure CLI works on Linux, macOS, and Windows to reassure non-Windows users.
  • If possible, clarify in the prerequisites that all portal and CLI instructions are cross-platform.
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
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all Azure-related tasks, with PowerShell examples presented alongside CLI examples. However, there is a slight Windows bias in the sense that PowerShell is featured as a primary alternative to Azure CLI, and PowerShell-specific instructions are given equal prominence. The document does not provide explicit Linux/macOS shell alternatives for Azure PowerShell tasks, though the Azure CLI commands are cross-platform. There is minor bias in presenting PowerShell as a first-class option, which may create friction for Linux/macOS users unfamiliar with PowerShell.
Recommendations
  • Clarify that Azure CLI commands are cross-platform and recommended for Linux/macOS users.
  • Add a note indicating that Azure PowerShell is primarily for Windows users, while Azure CLI is supported on all platforms.
  • Consider presenting Azure CLI examples first, as it is the most universally supported tool.
  • Optionally, remove PowerShell examples from the main flow and link to a separate PowerShell-specific guide.
  • Explicitly mention that all bash commands (git, helm, kubectl) work on Linux/macOS and Windows (with WSL or Git Bash).
GitHub Create Pull Request
Aks Deploy an application with the Dapr cluster extension for Azure Kubernetes Service (AKS) or Arc-enabled Kubernetes ...ure-aks-docs/blob/main/articles/aks/quickstart-dapr.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 instructions for resource cleanup, but lists Azure CLI first and Azure PowerShell second. The prerequisites mention both Azure CLI and Azure PowerShell, but do not show any platform-specific bias in the main workflow steps. All example commands for interacting with Kubernetes and the sample apps use cross-platform tools (kubectl, curl, git), and there are no Windows-only tools or patterns. However, the inclusion of PowerShell instructions and the ordering of CLI before PowerShell may indicate a slight Windows-first bias.
Recommendations
  • Continue to provide both Azure CLI and Azure PowerShell instructions for parity.
  • Explicitly state that all main workflow steps (kubectl, curl, git) are cross-platform and work on Linux/macOS/Windows.
  • Consider alternating the order of CLI and PowerShell instructions, or grouping them in tabs labeled by OS (Windows, Linux/macOS) to make parity clearer.
  • Add a note clarifying that Azure CLI is fully supported on Linux/macOS, and that all kubectl/curl/git commands are platform-agnostic.
GitHub Create Pull Request
Aks Kubernetes on Azure tutorial - Upgrade an Azure Kubernetes Service (AKS) cluster ...in/articles/aks/tutorial-kubernetes-upgrade-cluster.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides parallel instructions for Azure CLI, Azure PowerShell, and Azure portal, but consistently lists Azure PowerShell (a Windows-centric tool) as a primary option alongside Azure CLI. In some sections, PowerShell examples are given equal prominence to CLI, and the introductory context mentions Azure PowerShell before Linux alternatives. However, all critical tasks (AKS upgrade, validation, deletion) are fully covered with Azure CLI commands, which work cross-platform, and there are no Windows-only tools or patterns required. No Linux/macOS-specific examples or troubleshooting are provided, but the CLI coverage ensures Linux parity for all operations.
Recommendations
  • List Azure CLI examples before Azure PowerShell in each section to reflect cross-platform usage patterns.
  • Explicitly state that Azure CLI works on Windows, Linux, and macOS, and is recommended for non-Windows users.
  • Add a brief note or link for Linux/macOS users about installing Azure CLI and using it in their environment.
  • Consider removing or de-emphasizing Azure PowerShell examples, or move them to a separate section for Windows users.
  • Add troubleshooting tips or common issues for Linux/macOS environments if relevant.
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 ⚠️ windows_tools
Summary
The documentation provides both Linux and Windows examples for AKS network policy engines, but Windows-specific instructions (such as registering preview features and creating Windows admin credentials) are presented in a dedicated section immediately after the Linux instructions. The documentation references Windows-specific tools (Host Network Service ACLPolicies) and includes Windows node pool configuration steps. However, Linux instructions and examples are present and complete, and the overall flow does not prevent Linux/macOS users from following the guide.
Recommendations
  • Ensure that Linux and Windows instructions are presented with equal prominence, possibly by grouping them under parallel headings (e.g., 'Create an AKS cluster with Azure Network Policy Manager (Linux)' and '(Windows)').
  • Where possible, provide side-by-side examples for both Linux and Windows node pool creation, rather than separating them into sequential sections.
  • Clarify in each section which operating system the instructions apply to, to reduce confusion.
  • Ensure that Linux-specific limitations and features are as thoroughly documented as Windows-specific ones.
  • If Windows-specific tools or patterns are mentioned (e.g., HNS ACLPolicies), briefly note the Linux equivalents (e.g., IPTables/BPF) for parity.
GitHub Create Pull Request