Aks

535
Total Pages
430
Linux-Friendly Pages
105
Pages with Bias
19.6%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

365 issues found
Showing 226-250 of 365 flagged pages
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 →
Scanned: 2026-02-02 00:00
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 detail and before Linux equivalents in some sections. Windows tools and concepts (e.g., HNS ACLPolicy) are described alongside Linux (IPTables), but Windows-specific steps are more prominent, especially in the cluster creation walkthroughs. All CLI examples use Azure CLI and Bash, which are cross-platform, but there is a slight tendency to present Windows node pool configuration steps first or with more detail.
Recommendations
  • Ensure Linux and Windows instructions are presented in parallel, with equal detail and clarity.
  • Where possible, group Linux and Windows steps together and clearly label them for each platform.
  • Provide explicit notes when steps differ between Linux and Windows, and avoid presenting Windows-specific steps before Linux unless contextually necessary.
  • Consider adding a summary table or section that clarifies which steps apply to which OS, and ensure Linux parity in all example walkthroughs.
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 →
Scanned: 2026-02-01 00:00
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 tools and patterns (e.g., PowerShell cmdlets, local installation instructions), and PowerShell is traditionally a Windows-centric tool, though it is cross-platform now. The PowerShell instructions and references (such as module installation/upgrades) mention Windows first, and the overall structure places PowerShell before CLI, which is more native to Linux/macOS users. However, the CLI instructions are present and complete, and PowerShell cross-platform support is acknowledged.
Recommendations
  • Make clear that Azure PowerShell is available on Linux/macOS and provide equal emphasis on installation/upgrade instructions for all platforms.
  • Consider listing Azure CLI instructions before PowerShell, as CLI is more commonly used on Linux/macOS.
  • Explicitly mention that all steps can be performed on Linux/macOS and provide links to platform-specific instructions where relevant.
  • Ensure that examples and instructions do not assume a Windows environment (e.g., file paths, shell usage).
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 →
Scanned: 2026-02-01 00:00
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 (e.g., listing subnets), but consistently mentions Azure PowerShell alongside Azure CLI and the Azure portal when introducing AKS cluster creation. PowerShell is referenced as an equivalent tool to Azure CLI for some tasks, but Linux/macOS users are not given Bash or shell script examples, and PowerShell is listed before Linux-native alternatives in some places.
Recommendations
  • When listing options for cluster creation, mention Azure CLI and Azure portal first, and clarify that Azure PowerShell is primarily for Windows users.
  • For commands where both Azure CLI and PowerShell are referenced (e.g., listing subnets), provide explicit Bash/shell examples for Linux/macOS users.
  • Add a note clarifying that Azure CLI is cross-platform and preferred for Linux/macOS, while PowerShell is mainly for Windows.
  • Where possible, avoid listing PowerShell before CLI or portal unless the task is Windows-specific.
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 →
Scanned: 2026-02-01 00:00
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) instructions for critical tasks such as updating authorized IP ranges and retrieving kubeconfig credentials. However, the PowerShell instructions are presented immediately after the CLI instructions and are given equal prominence, which may subtly reinforce a Windows-first mindset. No explicit Windows-only tools or patterns are used, and Linux examples are present where relevant. The overall workflow is platform-neutral, as the Azure portal and Azure CLI are cross-platform.
Recommendations
  • Consider explicitly stating that Azure CLI commands work on Linux, macOS, and Windows, while Azure PowerShell is primarily for Windows users.
  • Where possible, present CLI instructions before PowerShell, or clarify platform applicability in section headings (e.g., 'For Linux/macOS: Azure CLI', 'For Windows: Azure PowerShell').
  • Add a brief note at the start of the troubleshooting section indicating that both CLI and PowerShell options are provided for user convenience, and users should choose the tool appropriate for their OS.
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 →
Scanned: 2026-02-01 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation is generally cross-platform and focuses on Azure CLI and Bicep, which are available on Windows, Linux, and macOS. However, there is a minor Windows bias in the 'Listing the CRDs in your cluster' section, where the example uses 'kubectl get crds | findstr dapr.io', a Windows/PowerShell-specific pattern. The use of 'findstr' is not portable to Linux/macOS, where 'grep' would be standard. This example is also presented without an equivalent Linux/macOS command. Additionally, the use of PowerShell-style variable assignment (e.g., $MY_RESOURCE_GROUP) in CLI examples may be more familiar to Windows users, though it is generally supported in Bash as well.
Recommendations
  • Provide both Windows and Linux/macOS command examples for filtering CRDs (e.g., 'kubectl get crds | grep dapr.io' for Linux/macOS).
  • Explicitly mention that Azure CLI and Bicep are cross-platform and provide links or notes for installation on Linux/macOS.
  • Where variable assignment is shown, clarify syntax differences between Bash and PowerShell if relevant.
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 →
Scanned: 2026-02-01 00:00
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 operations, with PowerShell examples presented in parallel tabs. However, there is a slight Windows bias: PowerShell is a Windows-centric tool, and its inclusion alongside CLI in every section may suggest Windows as a first-class environment. The Azure CLI examples are cross-platform, but PowerShell is not natively available on Linux/macOS (though PowerShell Core exists). No Linux-specific tools or shell patterns are highlighted, and the documentation does not mention OS-specific considerations for running PowerShell or CLI. The order of tabs sometimes places PowerShell before CLI, and PowerShell is referenced in the prerequisites without clarifying cross-platform support.
Recommendations
  • Clarify in the prerequisites that Azure CLI is cross-platform (Windows, Linux, macOS), while Azure PowerShell is primarily for Windows but can be installed on other platforms via PowerShell Core.
  • Consider making Azure CLI the default or first example, as it is the most universally supported tool for cross-platform scenarios.
  • Add a note or section for Linux/macOS users about installing PowerShell Core if they wish to use PowerShell examples.
  • Explicitly state that all CLI commands work on Linux/macOS and Windows, and provide troubleshooting tips for non-Windows environments if needed.
  • If possible, add bash script examples for common workflows to further improve Linux parity.
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 →
Scanned: 2026-02-01 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and Azure portal for all major steps. However, Azure PowerShell (a Windows-centric tool) is presented as a first-class option alongside Azure CLI, and in some places, PowerShell examples are shown before or with equal prominence to CLI. There is a slight Windows-first bias in the inclusion and prominence of PowerShell, but Linux/macOS users can fully complete all tasks using Azure CLI, which is cross-platform. No critical steps are Windows-only, and Linux parity is generally good.
Recommendations
  • Clearly indicate that Azure CLI is cross-platform and suitable for Linux/macOS users, while Azure PowerShell is primarily for Windows.
  • Present Azure CLI examples before Azure PowerShell examples, or explicitly note that CLI is recommended for Linux/macOS.
  • Add a brief note at the start clarifying tool/platform compatibility for new users.
  • Consider de-emphasizing PowerShell in favor of CLI in cross-platform documentation unless there is a specific PowerShell-only feature.
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 →
Scanned: 2026-02-01 00:00
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 options 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 Linux-specific alternatives or examples for PowerShell commands. All code and workflow examples use cross-platform tools (kubectl, curl, git), and there are no Windows-only tools or patterns. No Linux-specific friction is present, but PowerShell is mentioned as an equal alternative to Azure CLI, which may be less relevant for Linux/macOS users.
Recommendations
  • Make it clear that Azure PowerShell is optional and primarily relevant for Windows users.
  • Explicitly state that Azure CLI is cross-platform and recommended for Linux/macOS users.
  • Consider adding a note that PowerShell is available on Linux/macOS, but CLI is more common.
  • Ensure that any future examples or instructions using PowerShell are accompanied by CLI equivalents, with CLI shown first.
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 →
Scanned: 2026-02-01 00:00
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 administrator credential setup and feature flag registration) are presented in detail and sometimes before Linux equivalents. Windows node pool creation steps are given their own section, with additional Azure CLI commands and preview feature registration, while Linux instructions are more streamlined. The documentation references Windows-specific tools (HNS ACLPolicy) and includes Windows node pool credential setup, but does not omit Linux examples or make Linux tasks impossible to complete.
Recommendations
  • Ensure Linux and Windows instructions are presented with equal prominence and clarity, possibly by grouping OS-specific steps together and explicitly labeling them.
  • Where possible, provide parallel step-by-step instructions for both Linux and Windows, rather than giving Windows steps more detail or prominence.
  • Avoid presenting Windows-specific steps before Linux equivalents unless required by feature availability.
  • Clarify which steps are OS-specific and which are universal, to reduce confusion 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 →
Scanned: 2026-01-31 00:00
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 →
Scanned: 2026-01-31 00:00
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 →
Scanned: 2026-01-31 00:00
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 →
Scanned: 2026-01-31 00:00
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 →
Scanned: 2026-01-31 00:00
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 →
Scanned: 2026-01-31 00:00
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 →
Scanned: 2026-01-31 00:00
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 →
Scanned: 2026-01-31 00:00
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
Aks Certificate Rotation in Azure Kubernetes Service (AKS) ...ks-docs/blob/main/articles/aks/certificate-rotation.md
Low Priority View Details →
Scanned: 2026-01-30 00:00
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 →
Scanned: 2026-01-30 00:00
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 →
Scanned: 2026-01-30 00:00
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 →
Scanned: 2026-01-30 00:00
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 →
Scanned: 2026-01-30 00:00
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 →
Scanned: 2026-01-30 00:00
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 →
Scanned: 2026-01-30 00:00
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 →
Scanned: 2026-01-30 00:00
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
← Previous Page 10 of 15 Next →