Scan Details - Linux-first Docs for Azure

Aks Kubernetes on Azure tutorial - Upgrade an Azure Kubernetes Service (AKS) cluster ...in/articles/aks/tutorial-kubernetes-upgrade-cluster.md

Medium Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation provides parallel examples for Azure CLI, Azure PowerShell, and Azure portal for all major tasks. However, Azure PowerShell is featured equally alongside Azure CLI, which is more cross-platform, and PowerShell is primarily a Windows-centric tool (though available on Linux/macOS). In some sections, PowerShell examples are given before Azure CLI, and PowerShell-specific installation instructions are included. There are no Linux-specific shell examples (e.g., Bash), nor explicit mention of Linux/macOS command-line environments. The documentation does not use Windows-only tools, but the prominence of PowerShell may create friction for Linux/macOS users.

Recommendations

Clearly indicate that Azure CLI is recommended for Linux/macOS users, and that PowerShell is optional.
Add brief notes clarifying that Azure CLI commands work on all platforms, while PowerShell is more common on Windows.
Consider including Bash shell examples or notes for Linux/macOS users, especially for common tasks.
Reorder examples to show Azure CLI first, followed by PowerShell, to reduce Windows-first bias.
Add a short section or callout for Linux/macOS users, linking to Azure CLI installation and usage guidance.

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 there is a minor bias in mentioning Windows file paths alongside Linux paths (sometimes Windows first), and referencing Windows-specific tools (e.g., C:\k\bootstrap-config) without always providing equivalent Linux instructions first. However, most commands and examples are cross-platform (Azure CLI, kubectl, bash/curl/openssl), and Linux paths are generally included. No critical steps are Windows-only.

Recommendations

Ensure Linux examples and file paths are always presented before Windows equivalents, as Linux is the default for AKS.
Where Windows paths are mentioned, explicitly clarify Linux paths and context first.
If showing file paths or commands for both OSes, use side-by-side tables or clear separation to avoid confusion.
Review for any subtle ordering bias and adjust to prioritize Linux, as AKS clusters are predominantly Linux-based.

Create Pull Request

Aks Install and Use the Agentic CLI for Azure Kubernetes Service (AKS) (Preview) ...cs/blob/main/articles/aks/cli-agent-for-aks-install.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 2 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy

Summary

The documentation is generally cross-platform and AKS-focused, but there are subtle signs of Windows bias. In several sections, Windows/macOS instructions (e.g., starting Docker Desktop) are mentioned before Linux equivalents. The Docker daemon startup instructions list Windows/macOS first, then Linux. All CLI examples use Azure CLI, which is cross-platform, but there are no PowerShell-specific examples or Windows-only tools. However, the documentation does not provide explicit Linux/macOS parity in some instructions (e.g., launching Docker Desktop vs. starting Docker daemon on Linux).

Recommendations

Present Linux instructions before or alongside Windows/macOS instructions, especially in sections about starting Docker.
Add explicit notes or links for Linux users where only Windows/macOS instructions are given (e.g., how to launch Docker on Linux desktops).
Ensure parity in troubleshooting and cleanup instructions, such as verifying Docker images or configuration files, by providing Linux-specific commands where appropriate.
Consider adding a table or section summarizing OS-specific steps for Docker installation and startup.

Create Pull Request

Aks Troubleshoot the Agentic CLI for Azure Kubernetes Service (AKS) ...ob/main/articles/aks/cli-agent-for-aks-troubleshoot.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 3 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example

Summary

The documentation provides troubleshooting steps for the Agentic CLI for AKS and includes examples for Docker issues on macOS/Windows and Linux. However, Windows/macOS solutions are often listed before Linux, and some steps (such as restarting Docker Desktop) are Windows/macOS-centric without equivalent Linux guidance. There are no PowerShell-specific commands, but Windows tools (Docker Desktop) are referenced. Azure CLI and kubectl commands are cross-platform, but minor bias exists in ordering and completeness of Linux instructions.

Recommendations

Present Linux solutions before or alongside Windows/macOS solutions for parity.
Clarify that Docker Desktop is not available on Linux and provide equivalent Linux troubleshooting steps (e.g., systemctl restart docker, checking service status).
Where Windows/macOS instructions reference GUI actions (like launching Docker Desktop), provide Linux command-line alternatives.
Ensure all troubleshooting steps are equally detailed for Linux, including guidance for common Linux-specific issues (e.g., SELinux/AppArmor, systemd status checks).
Explicitly mention that Azure CLI and kubectl commands are cross-platform, and provide any OS-specific caveats if needed.

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 are present alongside Azure CLI in the 'Before you begin' section. The PowerShell cmdlet (Get-AzVirtualNetworkSubnetConfig) is mentioned as an alternative to Azure CLI for listing subnets, but no Linux-specific guidance or parity for PowerShell is provided. Azure CLI is used for all command-line examples, which is cross-platform, but PowerShell is referenced before Linux shell alternatives in some places.

Recommendations

Clarify that Azure PowerShell is optional and primarily for Windows users; consider mentioning Bash or other Linux-native tools where relevant.
Where PowerShell is referenced, ensure Linux/macOS users are guided to use Azure CLI or provide equivalent Bash commands.
If PowerShell is mentioned, add a note that Azure CLI is fully supported and preferred for cross-platform use.
Review the order of tool mentions in the 'Before you begin' section: list Azure CLI (cross-platform) before PowerShell (Windows-centric).

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. While Azure CLI is cross-platform, the PowerShell section is prominent and includes detailed instructions for installation and usage, with Windows mentioned first in upgrade instructions. The PowerShell section is more elaborate than the CLI section, potentially favoring Windows users. However, CLI instructions are present and usable for Linux/macOS users.

Recommendations

Ensure Azure CLI instructions are as detailed as PowerShell instructions, including environment setup and troubleshooting.
When mentioning installation or upgrade instructions for PowerShell, list Linux/macOS before Windows or equally.
Highlight Azure CLI as the recommended cross-platform tool for Linux/macOS users.
Add explicit notes clarifying that both Azure CLI and PowerShell are fully supported on Linux/macOS.

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 installation and management, which are available on Windows, Linux, and macOS. However, in the 'Listing the CRDs in your cluster' section, the example uses 'kubectl get crds | findstr dapr.io', which is a Windows/PowerShell pattern. The use of 'findstr' is Windows-specific, and no Linux/macOS equivalent (such as 'grep') is provided. Additionally, this Windows example appears before any alternative, creating minor friction for Linux/macOS users.

Recommendations

Provide both Windows and Linux/macOS command examples for shell operations, e.g., show 'kubectl get crds | grep dapr.io' alongside the 'findstr' example.
Where possible, use cross-platform commands or note OS-specific differences.
Review other shell command examples to ensure parity for all platforms.

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 authorized IP ranges, but the PowerShell section is presented immediately after the CLI section and is equally prominent. There are no Linux/macOS-specific examples (e.g., Bash or zsh), and the CLI example uses 'dig', which is available on Linux/macOS but not natively on Windows. However, the documentation does not exclusively favor Windows tools or patterns, and the Azure portal workflow is inherently cross-platform. The severity of bias is low, as Linux/macOS users can follow the Azure CLI instructions without friction, but the PowerShell section may be unnecessary for non-Windows users.

Recommendations

Clarify that Azure PowerShell examples are for Windows users, and Azure CLI is cross-platform.
Consider adding a note that Azure CLI commands work on Linux, macOS, and Windows (with WSL or Git Bash).
Optionally, provide Bash/zsh shell examples for retrieving the public IP address (e.g., using 'curl' or 'wget') for Linux/macOS users.
Make it clear which commands are platform-specific to avoid confusion.

Create Pull Request

Aks Use a Service Principal with Azure Kubernetes Service (AKS) ...blob/main/articles/aks/kubernetes-service-principal.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 key tasks, using a 'zone pivot' pattern. However, PowerShell examples are included throughout, which are primarily relevant for Windows users. Azure CLI is cross-platform, but PowerShell is Windows-centric (though available on Linux/macOS, it's less commonly used there). In some sections, PowerShell examples are given equal prominence to CLI, and terminology like 'PSCredential' is Windows-specific. There are no Linux/macOS-specific shell examples (e.g., Bash), and no explicit mention of Linux/macOS workflows or tools.

Recommendations

Clarify that Azure CLI commands are fully cross-platform and preferred for Linux/macOS users.
Consider adding Bash shell scripting examples for environment variable handling, especially in sections where PowerShell scripting is shown.
Where PowerShell-specific terminology is used (e.g., PSCredential), note its relevance to Windows and provide cross-platform alternatives.
Add a brief note at the start indicating that Azure CLI is recommended for Linux/macOS users, and PowerShell is primarily for Windows users.
Ensure that any file path references (e.g., /etc/kubernetes/azure.json) are explained for both Linux and Windows node pools if relevant.

Create Pull Request

Aks Azure Kubernetes Service (AKS) Managed Gateway API Installation ...aks-docs/blob/main/articles/aks/managed-gateway-api.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 1 bias type

Detected Bias Types

⚠️ windows_first

Summary

The documentation primarily uses Azure CLI examples, which are cross-platform, and includes kubectl commands that work on all OSes. However, there is a minor bias in that Azure CLI examples are shown using the 'azurecli-interactive' code block, which sometimes defaults to Windows-style terminals in Azure docs, and there is no explicit mention or example for Linux/macOS users (e.g., Bash shell, package installation, or alternative CLI usage). No PowerShell or Windows-specific tools are used, and all commands are compatible with Linux/macOS. The bias is minimal and does not prevent Linux/macOS users from completing the task.

Recommendations

Clarify that Azure CLI and kubectl commands are cross-platform and can be run on Linux, macOS, and Windows.
Add a note or section for Linux/macOS users, mentioning any prerequisites (such as installing Azure CLI or jq) and shell compatibility.
Ensure code blocks are labeled generically (e.g., 'bash' or 'shell') rather than 'azurecli-interactive' if possible, to avoid confusion.
Explicitly mention that all steps are OS-agnostic unless there are exceptions.

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 presents both Azure CLI and Azure PowerShell options for resource cleanup, but lists Azure CLI first and provides explicit PowerShell instructions. The prerequisites mention both Azure CLI and Azure PowerShell, but all operational examples (deployment, verification, interaction) use cross-platform tools (kubectl, curl, git) and do not rely on Windows-specific tooling. No Linux/macOS examples are missing, and no Windows-only tools are required for the main workflow.

Recommendations

Continue listing Azure CLI first, as it is cross-platform, but clarify that PowerShell is optional and primarily for Windows users.
Consider explicitly noting that all main steps (kubectl, curl, git) work on Linux/macOS and Windows.
If possible, add a short note in the prerequisites that Azure CLI is recommended for Linux/macOS users, while PowerShell is for Windows.
Ensure parity in cleanup instructions by providing Bash script examples for resource deletion, if relevant.

Create Pull Request

Aks Configure LocalDNS in Azure Kubernetes Service (AKS) ...ure-aks-docs/blob/main/articles/aks/localdns-custom.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 1 bias type

Detected Bias Types

⚠️ windows_first

Summary

The documentation provides links for creating an AKS cluster using Azure CLI, Azure PowerShell, and the Azure portal, listing Azure PowerShell before Linux-native alternatives. However, all configuration, verification, and operational examples use cross-platform tools (Azure CLI, kubectl, YAML) and explicitly state LocalDNS is only supported on Azure Linux or Ubuntu node pools. No Windows-specific commands, tools, or patterns are used in the main instructions.

Recommendations

List Azure CLI (Linux/macOS-friendly) before Azure PowerShell in prerequisite links to reinforce Linux parity.
Explicitly mention that all operational steps are cross-platform and can be run from Linux, macOS, or Windows.
Consider adding a note clarifying that Azure PowerShell is optional and not required for Linux/macOS users.

Create Pull Request

Aks Use GPUs on Azure Kubernetes Service (AKS) ...zure-aks-docs/blob/main/articles/aks/use-nvidia-gpu.md

Low Priority View Details →

Reviewed by: LLM Analysis

Issues: 1 bias type

Detected Bias Types

⚠️ windows_first

Summary

The documentation is focused on GPU usage in AKS Linux node pools, but in the 'Before you begin' section, Windows tooling (Azure PowerShell) and the Azure portal are mentioned alongside the Azure CLI as ways to create a cluster, with PowerShell listed before the portal. However, all actual examples and instructions are Linux-centric, using Azure CLI and kubectl, and there are no PowerShell or Windows-specific commands or tools used for the main workflow.

Recommendations

In the 'Before you begin' section, list Linux-friendly tools (Azure CLI, portal) before Windows-specific tools (PowerShell), or clarify that PowerShell is primarily for Windows users.
Consider adding a note that all subsequent examples assume a Linux environment and Azure CLI usage.
If PowerShell is mentioned, provide parity by linking to Linux shell equivalents or clarify its scope.

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 steps, but consistently presents Azure CLI (cross-platform) examples first, followed by Azure PowerShell (Windows-centric) examples. There are no explicit Windows-only tools or patterns, and all critical steps are achievable via CLI or Bash commands. The Helm and kubectl commands are shown in Bash, which is cross-platform. No Linux-specific examples are missing, but PowerShell is featured equally alongside CLI, which may create minor friction for Linux/macOS users.

Recommendations

Consider clarifying that Azure PowerShell is primarily for Windows users, and Azure CLI is recommended for Linux/macOS.
Add explicit notes or guidance for Linux/macOS users, such as confirming that all Azure CLI and Bash commands work natively.
Optionally, provide a brief section on using Bash or Zsh shells for Linux/macOS users, or link to Azure CLI installation instructions for those platforms.
Ensure that any future examples or troubleshooting steps do not assume PowerShell as the default shell.

Create Pull Request

Scan Information

Problematic Pages