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 151-175 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-11 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 setup, but Windows-specific instructions (such as registering feature flags and creating Windows admin credentials) are presented in a dedicated section immediately after the Linux section. Windows tools and concepts (like HNS ACLPolicies) are mentioned alongside Linux equivalents (IPTables), and Windows node pool support is discussed in the context of Calico and Azure NPM. However, Linux instructions and examples are generally present and complete, and the page is not Windows-only.
Recommendations
  • Ensure Linux and Windows instructions are equally prominent and parallel in structure.
  • When describing network policy engines, list Linux and Windows support together rather than Windows-specific features first.
  • Where possible, provide Linux and Windows examples side-by-side, especially for cluster creation and network policy application.
  • Clarify when steps are Windows-specific to avoid confusion for Linux users.
  • Consider adding explicit notes or tables summarizing feature parity and limitations for both OSes.
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-11 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. The prerequisites mention both Azure CLI and Azure PowerShell, but do not show any Linux-specific shell or tool examples. All command-line examples use Bash syntax (compatible with Linux/macOS), and there are no PowerShell-specific examples for the main workflow. No Windows-only tools are referenced, and the workflow is cross-platform. However, the presence of Azure PowerShell instructions and its mention in prerequisites may slightly favor Windows users.
Recommendations
  • Clarify that all Bash commands work on Linux/macOS and Windows (with WSL or Git Bash), and explicitly mention cross-platform compatibility.
  • Consider listing Azure CLI as the default/primary method for resource management, with PowerShell as an alternative, and clarify that Azure CLI is cross-platform.
  • Add a note in the prerequisites that Azure CLI is recommended for Linux/macOS users, while Azure PowerShell is primarily for Windows.
  • Ensure parity in examples: if PowerShell is shown for cleanup, consider showing Bash alternatives for all steps, or clarify that Azure CLI is preferred for non-Windows platforms.
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-11 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, but consistently presents Azure CLI (which is cross-platform) before Azure PowerShell (which is Windows-centric). There are no explicit Linux/macOS-specific examples or notes, but the CLI instructions are suitable for Linux/macOS. Bash commands are used for Helm and git operations, which are platform-neutral. No Windows-only tools or patterns are mentioned, and no critical steps are Windows-exclusive.
Recommendations
  • Explicitly state that Azure CLI commands are cross-platform and recommended for Linux/macOS users.
  • Add a note clarifying that Azure PowerShell is primarily for Windows users, while Azure CLI works on all platforms.
  • Consider including a brief section or callout for Linux/macOS users, confirming that all CLI steps are compatible.
  • Ensure that any references to PowerShell do not imply it is required for Linux/macOS users.
GitHub Create Pull Request
Aks Secure Container Access to Resources in Azure Kubernetes Service (AKS) ...docs/blob/main/articles/aks/secure-container-access.md
Low Priority View Details →
Scanned: 2026-02-11 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation is focused on Linux security features for AKS containers (user namespaces, AppArmor, seccomp), and explicitly states these are Linux-only. However, in prerequisite sections, Windows tools (Azure PowerShell) are mentioned alongside Azure CLI and Portal, and are listed before Linux equivalents in some places. All technical examples, commands, and walkthroughs are Linux-centric, with no Windows-specific instructions or tools used for the main tasks. No PowerShell-only examples or Windows tools are used for the actual security configuration.
Recommendations
  • In prerequisite lists, mention Azure CLI before Azure PowerShell to prioritize Linux-native tooling.
  • Clarify that Azure PowerShell is optional and not required for Linux users.
  • Consider adding a note that all technical steps are Linux-only and Windows node pools are not supported for these features, to avoid confusion.
  • If possible, provide links to Linux-specific quickstart guides before Windows/PowerShell equivalents.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides parity between Azure CLI, Azure PowerShell, and Azure portal for all AKS upgrade tasks. However, Azure PowerShell (which is most commonly used on Windows) is given equal prominence to Azure CLI, and PowerShell examples are provided throughout. In some sections, PowerShell is listed before the portal, and the 'devx-track-azurepowershell' custom metadata suggests a PowerShell focus. There are no missing Linux examples, as Azure CLI is fully supported on Linux/macOS and is always included. No Windows-only tools or patterns are mentioned outside of PowerShell.
Recommendations
  • Consider listing Azure CLI examples before Azure PowerShell in each section, as CLI is cross-platform and more commonly used by Linux/macOS users.
  • Explicitly note that Azure CLI commands work on Linux/macOS, and that Azure PowerShell is available on Linux/macOS (if true), to avoid implicit Windows bias.
  • If possible, add a short note or section for users who prefer Bash scripting or other Linux-native tools, clarifying that Azure CLI is the recommended cross-platform approach.
  • Review metadata and page structure to ensure CLI is not deprioritized in favor of PowerShell.
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-02-10 00:00
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.
GitHub 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 →
Scanned: 2026-02-10 00:00
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.
GitHub 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 →
Scanned: 2026-02-10 00:00
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.
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-10 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 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).
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-10 00:00
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.
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-10 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 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.
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-10 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 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.
GitHub 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 →
Scanned: 2026-02-10 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 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.
GitHub 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 →
Scanned: 2026-02-10 00:00
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.
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-10 00:00
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.
GitHub 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 →
Scanned: 2026-02-10 00:00
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.
GitHub 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 →
Scanned: 2026-02-10 00:00
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.
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-10 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 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.
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-09 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 consistently lists Azure CLI (cross-platform) first. Azure PowerShell is mentioned as an alternative, but no Windows-specific tools or patterns are prioritized elsewhere. All code and shell examples use Bash syntax, and there are no PowerShell-only or Windows-only instructions. The bias is minor, as Azure CLI is cross-platform and shown first, but PowerShell is included for completeness.
Recommendations
  • Maintain Azure CLI as the primary example, since it is cross-platform.
  • Ensure PowerShell instructions are clearly marked as optional for Windows users.
  • Consider adding explicit notes clarifying that Azure CLI works on Linux/macOS/Windows, and PowerShell is primarily for Windows users.
  • No further Linux parity improvements are needed, as all critical steps are accessible on Linux/macOS.
GitHub 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 →
Scanned: 2026-02-09 00:00
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 with some evidence of Windows bias. In Docker-related troubleshooting, Windows/macOS instructions (Docker Desktop) are listed before Linux instructions, and Linux-specific solutions are sometimes less detailed. Azure CLI examples are platform-neutral, but there are no PowerShell or Linux shell alternatives for Azure commands. The documentation does not provide Linux-specific troubleshooting for Docker Desktop alternatives or mention Linux GUI tools. Overall, the bias is minor and does not prevent Linux/macOS users from completing tasks.
Recommendations
  • Alternate the order of Windows/macOS and Linux instructions to avoid always listing Windows first.
  • Add Linux-specific troubleshooting tips for Docker (e.g., checking Docker daemon status, logs, and common Linux issues).
  • Provide PowerShell and Bash equivalents for Azure CLI commands where relevant.
  • Mention Linux GUI Docker tools (if any) or clarify that Docker Desktop is not available on Linux.
  • Ensure all troubleshooting steps are equally detailed for Linux, macOS, and Windows.
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-09 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 focused on Azure CLI and Bicep, which are available on Windows, Linux, and macOS. However, there is a minor bias in the 'Listing the CRDs in your cluster' section, where a Windows/PowerShell-specific command ('kubectl get crds | findstr dapr.io') is provided, with no Linux/macOS equivalent (such as using 'grep'). Additionally, the use of 'findstr' as the only example may subtly prioritize Windows users.
Recommendations
  • Provide Linux/macOS equivalent commands alongside Windows examples, e.g., 'kubectl get crds | grep dapr.io' for Linux/macOS.
  • When giving command-line examples, consider showing both Windows and Linux/macOS variants, or note that the command works cross-platform.
  • Review all CLI examples for OS-specific syntax and clarify any differences.
  • Explicitly state that Azure CLI and Bicep are cross-platform, and link to installation instructions for all supported OSes.
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-09 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 troubleshooting, but consistently presents Azure CLI (Linux/macOS-friendly) examples first, followed by Azure PowerShell (Windows-centric) examples. There are no Windows-only tools or patterns, and all instructions are accessible via the Azure portal or cross-platform tools. However, the PowerShell section is present, which may be unnecessary for Linux/macOS users, but it is not prioritized over CLI examples.
Recommendations
  • Continue to provide Azure CLI examples first, as they are cross-platform.
  • Consider clarifying that Azure PowerShell is primarily for Windows users, and Azure CLI is recommended for Linux/macOS.
  • If possible, add a short note indicating that Azure CLI works on Windows, Linux, and macOS, while PowerShell is mostly used on Windows.
  • Ensure that all portal instructions and YAML examples are platform-neutral, as currently done.
GitHub 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 →
Scanned: 2026-02-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Minor Windows Tools
Summary
The documentation provides installation and usage instructions for the Agentic CLI for AKS in both client (local) and cluster (in-cluster) modes. While the guide is generally cross-platform and includes Linux-specific instructions (e.g., systemctl for Docker), there are a few instances where Windows/macOS steps or tools are mentioned before Linux equivalents, such as launching Docker Desktop. However, all critical steps and examples are platform-neutral or include Linux instructions, and no PowerShell- or Windows-only tools are used.
Recommendations
  • When listing steps for starting Docker, present Linux, macOS, and Windows instructions in parallel or clarify that all platforms are supported equally.
  • Where Docker Desktop is mentioned, add a note that Linux users should use systemctl or their distribution's service manager.
  • Consider explicitly stating that all commands (az CLI, Docker, kubectl) work on Linux, macOS, and Windows, and link to platform-specific installation guides where relevant.
  • Ensure example commands (e.g., cleanup, verification) include both Linux and Windows/macOS file path conventions if relevant.
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-09 00:00
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. The PowerShell section is prominent and includes detailed instructions, with references to installing/upgrading PowerShell on Windows, macOS, and Linux. However, PowerShell is traditionally a Windows-centric tool, and its section appears before the Azure CLI, which is more universally used across Linux/macOS. The CLI section is present and provides parity, but the ordering and emphasis on PowerShell may create friction for Linux/macOS users.
Recommendations
  • Consider placing Azure CLI instructions before PowerShell, as CLI is more widely used across platforms.
  • Explicitly mention that Azure CLI is recommended for Linux/macOS users.
  • Add a note clarifying that PowerShell is available cross-platform, but Azure CLI is often preferred on Linux/macOS.
  • Ensure that all code blocks and instructions are equally detailed for both PowerShell and CLI.
  • Where possible, avoid referring to PowerShell as the default unless required.
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-09 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 some prerequisite steps, but consistently mentions Azure PowerShell alongside Azure CLI and the Azure portal as ways to create an AKS cluster. Additionally, it references the PowerShell cmdlet Get-AzVirtualNetworkSubnetConfig as an alternative to the Azure CLI command for listing subnets. However, all actual walkthroughs and examples use cross-platform tools (kubectl, Azure CLI), and there are no PowerShell-specific code snippets or Windows-only instructions. The bias is minor and mostly limited to mentioning PowerShell as an option, with Azure CLI (Linux/macOS-friendly) always present.
Recommendations
  • When listing ways to create an AKS cluster, consider mentioning Azure CLI and Azure portal first, then Azure PowerShell, or clarify that Azure PowerShell is primarily for Windows users.
  • For commands to list subnets, prioritize Azure CLI examples and mention PowerShell as an alternative for Windows users.
  • Ensure that all critical steps have Azure CLI examples and avoid PowerShell-only instructions.
  • Consider adding a note that Azure CLI and kubectl are fully cross-platform and recommended for Linux/macOS users.
GitHub Create Pull Request
← Previous Page 7 of 15 Next →