Scan Details - Linux-first Docs for Azure

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 configuration instructions for Azure CNI networking in AKS using three methods: Azure portal, Azure PowerShell, and Azure CLI. The PowerShell section is prominent and includes detailed instructions for installing/upgrading Azure PowerShell on Windows, macOS, and Linux. However, PowerShell is a Windows-centric tool, and its inclusion as a primary method may signal a Windows bias. Additionally, the PowerShell instructions and references appear before the Azure CLI examples, which are more universally applicable across platforms. No Linux-specific tools or shell examples (e.g., Bash) are provided, and the CLI instructions are listed last.

Recommendations

Present Azure CLI instructions before PowerShell, as CLI is cross-platform and preferred by many Linux/macOS users.
Add explicit Bash shell examples or notes for Linux/macOS users where relevant.
Clarify that PowerShell is available on Linux/macOS, but Azure CLI is often the default/preferred tool for those platforms.
Consider adding a table or section comparing the three approaches, highlighting platform compatibility.

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 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 PowerShell's 'findstr' command with kubectl, which is specific to Windows. No Linux/macOS equivalent (e.g., grep) is provided, and the example is shown without alternatives.

Recommendations

Provide Linux/macOS equivalents for shell commands, especially where Windows-specific tools like 'findstr' are used. For example, add a 'kubectl get crds | grep dapr.io' example alongside the PowerShell version.
Where possible, clarify that Azure CLI and Bicep commands work on all major platforms, and link to installation instructions for Linux/macOS as well as Windows.
Consider using platform-agnostic commands or explicitly showing both Windows and Linux/macOS variants when shell commands are involved.

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 (Linux/macOS-friendly) and Azure PowerShell (Windows-centric) examples for managing AKS authorized IP ranges. However, PowerShell examples are presented alongside CLI examples, and PowerShell is given a dedicated section. The CLI example is shown first, but the PowerShell section is equally prominent. There are no Windows-only tools or patterns, and all instructions are accessible from any OS. The overall workflow is portal-based and cross-platform, with no missing Linux/macOS examples.

Recommendations

Clarify that Azure CLI commands work on Windows, Linux, and macOS, while Azure PowerShell is primarily for Windows users.
Consider grouping CLI and PowerShell examples under a 'Choose your platform' heading to reinforce parity.
Explicitly mention that Cloud Shell supports both Bash (CLI) and PowerShell, and is available in the portal for all platforms.
If possible, add a note that Linux/macOS users should use Azure CLI, while Windows users may use either CLI or PowerShell.

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 to PowerShell and Windows tooling (e.g., Get-AzVirtualNetworkSubnetConfig) are present before or alongside Linux-friendly alternatives. Azure CLI is used for all actual walkthrough commands, which are cross-platform, but PowerShell is mentioned as an equivalent option for some resource queries. There are no Linux/macOS-specific examples or explicit parity notes.

Recommendations

When listing prerequisite tooling, mention Azure CLI first, as it is cross-platform, and clarify that PowerShell is an alternative for Windows users.
For resource queries, provide Azure CLI commands as the primary example, and mention PowerShell only as an alternative for Windows users.
Add a note clarifying that all kubectl and Azure CLI commands work on Linux, macOS, and Windows.
Consider removing or relegating PowerShell references to a 'Windows alternative' section, ensuring Linux/macOS users are not confused or feel excluded.

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 as options, but do not show any Linux/macOS-specific instructions or highlight cross-platform differences. All command-line examples use Bash syntax (compatible with Linux/macOS and Windows via WSL or Git Bash), and no Windows-specific tools or patterns are prioritized. However, the presence of Azure PowerShell instructions and references could be seen as a mild Windows-first bias, especially since PowerShell is more commonly used on Windows.

Recommendations

Explicitly state that all Bash commands work on Linux, macOS, and Windows (with WSL or Git Bash).
Clarify that Azure CLI is cross-platform and provide installation instructions for Linux/macOS users.
Consider listing Azure CLI as the primary method, with PowerShell as an alternative, and note platform compatibility.
Add a note for Linux/macOS users regarding any differences in Azure CLI or kubectl usage, if applicable.

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 CLI examples shown first. There is no explicit Windows-only content, but PowerShell is featured equally alongside CLI, which is more cross-platform. No Linux-specific tools or patterns are missing, but the presence of PowerShell examples may create minor friction for Linux/macOS users who are unlikely to use PowerShell. All critical steps (AKS, ACR, Helm, kubectl) are covered with CLI commands, which work on Linux/macOS.

Recommendations

Clearly indicate that Azure PowerShell is optional and primarily for Windows users.
Consider moving PowerShell examples to a separate section or appendix, or marking them as 'Windows only'.
Add a note that Azure CLI is recommended for Linux/macOS users.
Ensure that CLI examples are always shown first (which is currently the case).
Optionally, provide bash script snippets for multi-step processes to further help Linux users.

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 examples for Azure CLI, Azure PowerShell, and Azure portal throughout, but consistently lists Azure PowerShell (a Windows-centric tool) as a primary option alongside Azure CLI. In some sections, PowerShell examples and instructions appear before or with equal prominence to CLI, which is more cross-platform. There are no Linux-specific shell examples (e.g., Bash, zsh), but Azure CLI commands are inherently cross-platform. No Windows-only tools or patterns are used, and the content is not about a Windows-specific AKS feature.

Recommendations

Make it clear that Azure CLI is cross-platform and preferred for Linux/macOS users.
Consider listing Azure CLI examples before PowerShell in each section to reinforce Linux parity.
Add brief notes or callouts clarifying that PowerShell is primarily for Windows users, while CLI works on all platforms.
Optionally, include Bash/zsh shell script examples for common tasks to further support Linux/macOS users.

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 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.

Create Pull Request

Scan Information

Problematic Pages