Scan Details - Linux-first Docs for Azure

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 API server authorized IP ranges, but consistently presents Azure CLI (Linux/macOS-friendly) examples first. However, PowerShell examples are also included, which may be more relevant to Windows users. No Windows-only tools or patterns are mentioned, and all instructions are portal-based or cross-platform. There are no missing Linux examples, and Linux node selectors are used in the YAML, indicating Linux parity.

Recommendations

Maintain Azure CLI examples as the primary cross-platform option.
Continue to provide both Azure CLI and PowerShell examples, but clarify that Azure CLI works on Windows, Linux, and macOS.
Consider adding brief notes about using Cloud Shell for cross-platform access.
Ensure screenshots and portal instructions do not reference Windows-specific UI elements.

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 ⚠️ missing_linux_example

Summary

The documentation is generally cross-platform and AKS is a Linux-first service, but there is mild Windows bias in the section 'Verify TLS Bootstrapping is enabled on current agent node pool', where Windows node paths are mentioned alongside Linux paths, but the Windows path is listed second. There are no PowerShell or Windows-specific command examples, and all CLI/script examples use Bash or Azure CLI, which are cross-platform. However, there are no explicit Linux/macOS instructions for accessing Windows node paths, nor are there Linux/macOS-specific troubleshooting tips. The documentation could improve Linux parity by clarifying access methods for both OS types and ensuring Linux examples are always present and clear.

Recommendations

Ensure all file path examples for both Linux and Windows nodes are accompanied by clear instructions for accessing them from Linux/macOS and Windows environments.
Add troubleshooting tips or access methods for Linux/macOS users when interacting with Windows node pools, if relevant.
Consider listing Linux examples first, as AKS is primarily Linux-based.
Explicitly state when a command or path is OS-specific and provide alternatives where possible.

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: 3 bias types

Detected Bias Types

⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example

Summary

The documentation provides installation and usage instructions for the Agentic CLI for AKS, with a slight preference for Windows/macOS patterns in Docker startup instructions and verification steps. While most commands are cross-platform (Azure CLI, Bash), the instructions for starting Docker daemon mention Windows/macOS (Docker Desktop) before Linux (systemctl), and verification steps for client mode cleanup use Windows-style paths (e.g., ~/.azure/aksAgent.config) without explicit Linux/macOS parity. There are no PowerShell-specific commands, but the ordering and phrasing sometimes prioritize Windows/macOS tools and workflows.

Recommendations

Ensure that Linux instructions are given equal prominence and detail as Windows/macOS instructions, especially for Docker startup and verification.
Provide explicit Linux/macOS example paths and commands where relevant (e.g., configuration file locations, Docker image cleanup).
Consider adding a table or section that summarizes OS-specific steps for Docker installation, startup, and troubleshooting.
When mentioning Docker Desktop, clarify that it is not available on Linux and provide Linux alternatives first or equally.
Review all example commands and outputs for OS-specific assumptions; add notes or alternatives for Linux/macOS users where needed.

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 detailed, with instructions for installing/upgrading PowerShell on Windows, macOS, and Linux. However, PowerShell is traditionally associated with Windows, and its section appears before the CLI section. The CLI section uses bash-style syntax, which is more familiar to Linux/macOS users, but is presented after PowerShell. There are no missing Linux examples, and Azure CLI is well-supported.

Recommendations

Consider presenting Azure CLI examples before PowerShell, as CLI is more universally used across platforms.
Explicitly mention that Azure CLI commands work on Linux/macOS/Windows and highlight its cross-platform nature.
Add brief notes clarifying that PowerShell is available on Linux/macOS, but Azure CLI is often preferred for Linux users.
Ensure parity in detail and guidance between PowerShell and CLI sections.

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 Windows/PowerShell tools (e.g., Get-AzVirtualNetworkSubnetConfig) are present. Azure CLI is used for all main examples, which is cross-platform, but PowerShell is mentioned alongside Azure CLI in the 'Before you begin' section and for subnet listing. The PowerShell cmdlet is referenced before its Linux equivalent (Azure CLI) in the subnet listing section. No Linux/macOS-specific friction is present, but Windows tools are referenced and sometimes listed first.

Recommendations

When listing prerequisite tools, mention Azure CLI first as it is cross-platform, and clarify that PowerShell is optional for Windows users.
For subnet listing, provide Azure CLI as the primary example and mention PowerShell only as an alternative for Windows users.
Consider adding explicit notes that all Azure CLI commands work on Linux/macOS, and that PowerShell is only required for Windows environments.
Avoid referencing Windows tools (PowerShell) unless necessary, and always provide a Linux/macOS equivalent.
Where possible, use Azure CLI for all examples to maximize cross-platform accessibility.

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 ⚠️ windows_tools

Summary

The documentation generally provides cross-platform troubleshooting steps for the Agentic CLI for AKS, but in several Docker-related sections, Windows/macOS instructions (Docker Desktop) are listed before Linux equivalents, and there is a heavier emphasis on Docker Desktop (a Windows/macOS tool) compared to Linux-native Docker management. No PowerShell-specific commands are present, but the pattern of mentioning Windows/macOS first and referencing Docker Desktop as the primary tool for those platforms indicates a mild Windows bias. All critical tasks are covered for Linux, so Linux users are not blocked.

Recommendations

Alternate the order of platform instructions (sometimes list Linux first) to avoid implicit prioritization of Windows/macOS.
Where Docker Desktop is mentioned, clarify that on Linux, Docker is typically managed via systemd and the CLI, and that Docker Desktop is not required.
Add explicit notes that all commands are supported on Linux, macOS, and Windows, and clarify any platform-specific differences.
If possible, provide Linux/macOS-specific troubleshooting screenshots or examples alongside Windows ones.

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 (both platform-agnostic). 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. No equivalent Linux/macOS example (using 'grep') is provided. Additionally, the use of 'findstr' appears before any mention of 'grep', which is absent.

Recommendations

Provide both Windows and Linux/macOS examples for commands involving shell utilities. For example, add 'kubectl get crds | grep dapr.io' alongside the 'findstr' example.
Clarify that Azure CLI and Bicep commands work on all platforms, and explicitly mention this in the prerequisites.
Where shell commands are shown, use platform-neutral language or offer alternatives for both environments.

Create Pull Request

Aks Azure Kubernetes Service (AKS) Managed Gateway API Installation (preview) ...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 Linux/macOS/Windows. However, the Azure CLI examples are shown using the 'azurecli-interactive' code block, which is sometimes associated with Windows/PowerShell environments, and there is no explicit mention of Linux/macOS compatibility or alternative instructions for those platforms. The order of examples and instructions does not show explicit Linux bias, but Windows users may perceive the CLI examples as more familiar due to the lack of Linux-specific context.

Recommendations

Clarify that Azure CLI and kubectl commands are cross-platform and can be run on Linux, macOS, and Windows.
Add a short note in the prerequisites or introduction indicating that all CLI instructions are compatible with Bash (Linux/macOS) and PowerShell (Windows).
Consider including example commands for Bash and PowerShell if there are any platform-specific differences.
Explicitly mention that the Azure CLI can be installed and used on Linux/macOS, with a link to installation instructions for those platforms.

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

⚠️ powershell_heavy ⚠️ windows_first

Summary

The tutorial provides parity between Azure CLI, Azure PowerShell, and Azure portal for all AKS upgrade tasks. However, Azure PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and in some sections, PowerShell examples are shown before CLI. There is no explicit Linux/macOS bias, but the heavy inclusion of PowerShell may create friction for Linux/macOS users, as PowerShell is less commonly used on those platforms. No Windows-only tools or patterns are mentioned, and all commands are cross-platform via Azure CLI or portal.

Recommendations

Make Azure CLI the primary or first example in each section, as it is cross-platform and more widely used on Linux/macOS.
Clarify that Azure PowerShell is optional and primarily for users already familiar with it.
Consider adding a note that Azure CLI is recommended for Linux/macOS users.
Ensure that all screenshots and instructions are neutral or show Azure CLI/portal where possible.

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

⚠️ powershell_heavy ⚠️ windows_first

Summary

The documentation provides both Azure CLI and Azure PowerShell examples throughout, but PowerShell is featured equally alongside CLI, which is more commonly used on Windows. There are no explicit Linux/macOS-specific instructions or examples, and the PowerShell sections may be less relevant for Linux/macOS users. Azure CLI is cross-platform, but the documentation does not clarify this or prioritize CLI examples. The use of PowerShell is not exclusive, but its presence may create confusion or friction for Linux/macOS users.

Recommendations

Explicitly state that Azure CLI is cross-platform and recommended for Linux/macOS users.
Consider presenting Azure CLI examples first, or labeling them as the default for non-Windows platforms.
Add brief notes clarifying that PowerShell examples are primarily for Windows users.
Include a short section or callout for Linux/macOS users, confirming that all steps can be completed with Azure CLI and bash.
Ensure that any shell commands (e.g., git, helm, kubectl) are shown in bash syntax, and clarify compatibility.

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 covers both Linux and Windows scenarios for AKS network policies, but Windows-specific instructions and tools (such as Windows admin credentials setup and feature flag registration) are presented before or alongside Linux equivalents. Windows node pool creation steps are detailed separately and prominently, and Windows-specific limitations and features are discussed in depth. However, Linux examples and instructions are also present and complete, and the page is not Windows-exclusive.

Recommendations

Ensure Linux instructions/examples are presented first in each section unless Windows is the primary focus.
Clearly separate Linux and Windows instructions with headings for easier navigation.
Add explicit notes when a command or step is Windows-only, and provide Linux equivalents where possible.
Consider grouping Windows-specific steps (such as admin credential setup and feature flag registration) in a dedicated section to avoid interleaving with Linux steps.

Create Pull Request

Live Progress

Scan Information

Problematic Pages