← Back to Dashboard
86
Pages Scanned
8
Pages Flagged
86
Changed Pages
9.3%
% Pages Flagged

Scan Information

Started At: 2026-01-31 00:00:10

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

Status: completed

Target Repo: Azure Aks

Current Phase: discovery

Files Queued: 86

Files Completed: 86

Problematic Pages

8 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 (Linux/macOS-friendly) and Azure PowerShell (Windows-centric) examples for managing AKS authorized IP ranges, but consistently lists Azure PowerShell examples after Azure CLI. The troubleshooting section includes PowerShell commands, which are primarily relevant to Windows users, but does not provide any Windows-only tools or patterns elsewhere. All other instructions are platform-neutral and focus on the Azure portal, which is accessible from any OS.
Recommendations
  • Ensure parity by always providing Azure CLI examples (which run on Linux/macOS/Windows) before PowerShell, as is currently done.
  • Consider explicitly stating that Azure CLI commands work on Linux, macOS, and Windows, while PowerShell commands are primarily for Windows.
  • If possible, add a brief note in troubleshooting that Linux/macOS users should use Azure CLI, while Windows users may use either CLI or PowerShell.
  • Continue to avoid Windows-only tools or patterns unless strictly necessary.
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) alongside Azure CLI and sometimes before Linux-native alternatives. PowerShell examples are present for every major step, and installation/version instructions for PowerShell are given equal prominence to Azure CLI. However, all CLI examples use Azure CLI, which is cross-platform, and there are no Windows-only tools or patterns. No Linux/macOS-specific issues or missing examples are present.
Recommendations
  • Clarify that Azure PowerShell is available cross-platform, but is most familiar to Windows users; consider listing Azure CLI examples first, as it is the default on Linux/macOS.
  • Add a note at the start explaining that Azure CLI is the recommended tool for Linux/macOS users, while PowerShell is more common on Windows.
  • Where possible, highlight the cross-platform nature of both Azure CLI and Azure PowerShell, but avoid implying PowerShell is required for Linux/macOS users.
  • Consider reordering tabs so Azure CLI appears before PowerShell, or defaulting to CLI in code samples.
  • If any step has Linux/macOS-specific caveats (e.g., shell quoting, path separators), mention them explicitly.
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 resource management steps, with PowerShell examples given equal prominence via tabbed sections. However, there is a subtle Windows bias: PowerShell is a Windows-centric tool, and its inclusion may suggest parity, but Linux/macOS users are more likely to use Azure CLI. The documentation does not provide Linux/macOS-specific instructions for installing prerequisites (e.g., Azure CLI, Helm), nor does it mention platform-specific differences or considerations. The ordering of examples is mostly neutral, but PowerShell is presented as an equal alternative, which may be unnecessary for a cross-platform audience.
Recommendations
  • Clarify that Azure CLI is the recommended and cross-platform tool for Linux/macOS users, while PowerShell is primarily for Windows.
  • Add explicit instructions or links for installing Azure CLI and Helm on Linux/macOS, including common package manager commands (e.g., apt, yum, brew).
  • Consider making Azure CLI the default or first example, with PowerShell as an optional tab for Windows users.
  • Add a brief note about platform compatibility for each tool in the prerequisites section.
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: Azure portal, Azure PowerShell, and Azure CLI. The PowerShell section is detailed and references Windows-centric tools and patterns, such as PowerShell cmdlets and installation instructions. The PowerShell tab appears before the CLI tab, and PowerShell is traditionally associated with Windows, though cross-platform support is mentioned. The CLI section is present and provides Linux/macOS parity, but PowerShell is given prominence and more detailed guidance.
Recommendations
  • Present Azure CLI examples before or alongside PowerShell examples, as CLI is more universally supported across platforms.
  • Clarify that PowerShell is cross-platform, but highlight CLI as the recommended approach for Linux/macOS users.
  • Add explicit notes or links for Linux/macOS users, especially in the prerequisites, to guide them toward CLI usage.
  • Ensure parity in example detail and troubleshooting steps for CLI and PowerShell.
  • Consider grouping PowerShell and CLI under a 'Command-line' heading, with equal prominence.
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 the Azure portal when describing how to create an AKS cluster. In the section about listing subnets, both Azure CLI and PowerShell commands are referenced, with CLI shown first. No Linux/macOS-specific examples or tools are missing, but PowerShell is mentioned as an equal alternative throughout, which may create minor friction for Linux/macOS users who do not use PowerShell.
Recommendations
  • Clearly indicate that Azure PowerShell is optional and primarily for Windows users, while Azure CLI is cross-platform.
  • List Azure CLI examples and links before PowerShell alternatives, or group them in a way that does not imply PowerShell is a primary method.
  • Add a note clarifying that all CLI examples work on Linux/macOS, and PowerShell is for Windows users.
  • Where PowerShell is referenced, consider providing a Bash alternative if relevant (though in this context, Azure CLI covers Linux/macOS needs).
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 PowerShell second. The prerequisites mention both Azure CLI and Azure PowerShell, but do not show any bias in installation instructions. All command-line examples for Kubernetes operations use bash/kubectl/curl, which are cross-platform and standard for Linux/macOS. No Windows-only tools, PowerShell-specific patterns, or missing Linux examples are present. The only minor bias is listing Azure CLI before PowerShell and providing PowerShell examples for resource cleanup.
Recommendations
  • Continue listing Azure CLI first, as it is cross-platform, but clarify that both CLI and PowerShell are supported on Windows, Linux, and macOS.
  • Explicitly mention that all kubectl and curl commands work on Linux, macOS, and Windows (with WSL or native tools).
  • Consider adding a note that Azure PowerShell is available on Linux/macOS via PowerShell Core, if relevant to the audience.
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 installation on AKS and Arc-enabled Kubernetes clusters. However, there is a minor Windows bias in the example for listing CRDs, which uses PowerShell's 'findstr' command with 'kubectl', and this example is not accompanied by a Linux/macOS equivalent (e.g., using 'grep'). Additionally, the PowerShell example is presented without clarification or alternatives, which may create minor friction for non-Windows users.
Recommendations
  • Provide Linux/macOS equivalents for shell commands, especially for 'kubectl get crds | findstr dapr.io'. For example, show 'kubectl get crds | grep dapr.io' alongside the PowerShell example.
  • Clarify that Azure CLI commands work on all platforms and, where relevant, mention any OS-specific prerequisites or differences.
  • Consider using more platform-neutral shell syntax in examples, or provide tabs/switches for Windows and Linux/macOS command variants where differences exist.
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 and cluster creation, but Windows-specific instructions (such as registering feature flags and creating administrator credentials) are presented in a dedicated section before Linux equivalents. Windows tooling (e.g., HNS ACLPolicy) is mentioned alongside Linux tools (IPTables/BPF), but not exclusively. The overall structure is balanced, but Windows instructions are sometimes given prominence or detail before Linux equivalents.
Recommendations
  • Ensure Linux and Windows instructions are presented in parallel, with equal prominence and clarity.
  • When listing tools or implementation details, mention Linux and Windows approaches together, or start with Linux if it is the default/recommended platform.
  • If a section is Windows-specific, clearly label it as such and provide a corresponding Linux section if applicable.
  • Consider grouping platform-specific instructions under clear headings to avoid perceived prioritization.
GitHub Create Pull Request