Aks

540
Total Pages
431
Linux-Friendly Pages
109
Pages with Bias
20.2%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

618 issues found
Showing 376-400 of 618 flagged pages
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-13 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides troubleshooting steps for the agentic CLI for AKS and generally includes both Windows/macOS and Linux instructions. However, in the Docker daemon troubleshooting section, Windows/macOS steps are listed before Linux steps, which is a minor 'windows_first' bias. All other examples and solutions are cross-platform or Linux-first, and Linux-specific issues (such as Docker permissions) are addressed directly.
Recommendations
  • Present Linux and Windows/macOS instructions in parallel or in the same order throughout the documentation.
  • Consider using tabs or clear section headers to distinguish platform-specific instructions, ensuring equal visibility.
  • Review other sections for ordering and ensure Linux instructions are not consistently placed after Windows/macOS instructions.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation is generally cross-platform and Linux-centric, but there are minor instances of Windows bias. In the 'Verify TLS Bootstrapping is enabled on current agent node pool' section, the Windows file path ('C:\k\bootstrap-config') is mentioned after the Linux path, which is good, but no Windows-specific command examples are provided. Most examples use bash, Azure CLI, and kubectl, which are standard for Linux/macOS. However, there are no PowerShell or Windows command-line examples for Windows users, and the documentation assumes Linux as the default for node access and certificate checks.
Recommendations
  • Add Windows-specific command examples (e.g., PowerShell or Command Prompt) for checking certificate expiration and accessing node files.
  • Clarify in sections where file paths differ between Linux and Windows, and provide explicit instructions for Windows users.
  • Ensure parity by including Windows node pool scenarios where relevant, or explicitly state if steps are Linux-only.
  • Consider adding a note about using Azure CLI and kubectl on Windows, including any prerequisites or differences.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page provides installation and usage instructions for the Agentic CLI for AKS, with a focus on Azure CLI commands. While most examples are cross-platform (Azure CLI and bash), there is a subtle Windows bias in the ordering and presentation of Docker daemon startup instructions: Windows/macOS (Docker Desktop) are mentioned before Linux (systemctl), and Linux instructions are less detailed. Additionally, some verification steps (e.g., checking config file removal) use bash commands without explicit Windows equivalents, and there are no PowerShell examples for Windows users. However, the overall impact is minor, as the Azure CLI and Docker are cross-platform, and Linux/macOS users can follow the instructions with minimal friction.
Recommendations
  • Present Linux instructions for Docker daemon startup before or alongside Windows/macOS instructions, and provide more detail for Linux users.
  • Include PowerShell equivalents for bash commands where relevant (e.g., checking file removal, listing Docker images) to improve parity for Windows users.
  • Explicitly mention that Azure CLI commands are cross-platform and provide links to platform-specific installation guides.
  • Add troubleshooting notes for common Linux/macOS issues (e.g., Docker daemon permissions, systemctl failures).
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-13 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation primarily uses Azure CLI commands and kubectl examples, which are cross-platform. However, all CLI examples are shown using Azure CLI (az), which is available on Windows, Linux, and macOS, but the documentation does not mention Linux/macOS-specific considerations or alternative commands. There is a minor bias in that Windows is implicitly assumed as the default environment, as no Linux/macOS shell-specific notes or troubleshooting are provided.
Recommendations
  • Explicitly state that Azure CLI and kubectl commands work on Windows, Linux, and macOS.
  • Add notes about installing Azure CLI and kubectl on Linux/macOS, including links to official installation guides.
  • Mention any potential differences in environment variables, shell syntax, or command output between platforms.
  • If relevant, provide troubleshooting tips for Linux/macOS users (e.g., permissions, PATH issues).
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-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation is largely cross-platform, focusing on Azure CLI and Bicep for Dapr extension management on AKS and Arc-enabled Kubernetes. However, there is a minor Windows bias in the CRD deletion section, where the example for listing CRDs uses PowerShell's 'findstr' command with 'kubectl', which is Windows-specific. Additionally, this example is given without a Linux/macOS equivalent, and the PowerShell usage appears before any mention of Linux tools.
Recommendations
  • Provide Linux/macOS equivalents for the CRD listing command, such as 'kubectl get crds | grep dapr.io'.
  • When giving shell command examples, show both Windows (PowerShell) and Linux/macOS (bash) versions side-by-side or indicate which platforms they apply to.
  • Consider using platform-neutral commands or note platform-specific differences where relevant.
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-13 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 portal, and links to PowerShell-specific resources. In the section about listing subnets, both Azure CLI and PowerShell are referenced, but PowerShell is mentioned second. There are no PowerShell-specific examples in the main workflow, and all command-line examples use Azure CLI or kubectl, which are cross-platform. However, the presence of PowerShell links and references may create minor friction for Linux/macOS users.
Recommendations
  • Where PowerShell is referenced, ensure equivalent Bash or cross-platform CLI options are always provided and shown first.
  • Clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Consider removing PowerShell references from main instructions unless a feature is PowerShell-only.
  • Add explicit notes or links for Linux/macOS users where PowerShell is mentioned, pointing to Azure CLI alternatives.
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-13 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 updating AKS API server authorized IP ranges, but consistently presents Azure CLI (Linux/macOS-friendly) instructions first, followed by Azure PowerShell (Windows-centric) instructions. No Windows-specific tools or patterns are mentioned exclusively, and all examples are cross-platform. However, the PowerShell section is present, which may be unnecessary for Linux/macOS users, but parity is maintained. There are no missing Linux examples, and the YAML deployment targets Linux node pools.
Recommendations
  • Clarify that Azure CLI commands are cross-platform and preferred for Linux/macOS users.
  • Consider explicitly stating that Azure PowerShell is primarily for Windows users.
  • Add a brief note indicating that Azure CLI works on Windows, Linux, and macOS, while PowerShell is mainly Windows-focused.
  • Ensure that any screenshots or UI instructions do not reference Windows-specific behaviors.
  • If possible, provide Bash-only examples for Linux users, or highlight that Cloud Shell supports Bash and PowerShell.
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-13 00:00
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 for all Azure-related operations, but consistently presents Azure CLI (which is cross-platform) before Azure PowerShell (which is Windows-centric). There are no Windows-only tools or commands, and all critical steps are achievable with Azure CLI, which works on Linux/macOS. Bash commands are used for Helm and kubectl, and no Windows-specific patterns or tools are mentioned. However, the presence of Azure PowerShell throughout and its parity with Azure CLI may create a slight perception of Windows bias.
Recommendations
  • Consider clarifying that Azure PowerShell is primarily for Windows users and Azure CLI is cross-platform.
  • Optionally, add a note at the start of the PowerShell sections indicating that Linux/macOS users should use Azure CLI.
  • Ensure that bash commands and cross-platform tools (Helm, kubectl) are always shown and not replaced by Windows-specific alternatives.
  • If possible, add explicit Linux/macOS instructions for installing Azure CLI, Helm, and kubectl (linking to their install docs).
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-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides full parity between Azure CLI, Azure PowerShell, and Azure portal for all AKS upgrade tasks. However, Azure PowerShell (which is Windows-centric) is given equal prominence to Azure CLI, and is sometimes mentioned before Linux-native tools. There are no missing Linux examples, but the presence of PowerShell examples and references may create minor friction for Linux/macOS users, as PowerShell is less commonly used on those platforms.
Recommendations
  • Consider listing Azure CLI examples first in each section, as it is the most cross-platform and widely used tool.
  • Explicitly note that Azure PowerShell is available on Linux/macOS, but Azure CLI is recommended for those platforms.
  • Add brief guidance for Linux/macOS users, clarifying that Azure CLI is the preferred tool and that all examples are fully supported on those platforms.
  • If possible, reduce the prominence of PowerShell in cross-platform tutorials, or move PowerShell examples to a secondary position.
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-12 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 updating AKS API server authorized IP ranges, but consistently presents Azure CLI (Linux/macOS-friendly) examples first. However, PowerShell examples are also included, which is good parity. There are no Windows-only tools or patterns, and all examples are cross-platform. The YAML manifests explicitly target Linux node pools, but this is standard for AKS and not Windows-biased. No critical tasks are Windows-only.
Recommendations
  • Maintain the current structure of presenting Azure CLI examples first, as this is inclusive for Linux/macOS users.
  • Continue to provide both Azure CLI and PowerShell examples for administrative tasks.
  • Consider adding a brief note clarifying that Azure CLI commands work on Linux, macOS, and Windows, while PowerShell commands are primarily for Windows users.
  • Ensure screenshots and portal instructions do not reference Windows-specific UI elements or terminology.
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-12 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 (a Windows-centric tool) is given equal prominence to Azure CLI, and is sometimes mentioned before or alongside CLI. There are no Linux-specific examples (e.g., Bash scripting, Linux-native tools), but Azure CLI is cross-platform and the examples are not exclusive to Windows. No critical tasks are Windows-only, and Linux/macOS users can complete all steps using Azure CLI or portal.
Recommendations
  • Clarify that Azure CLI is fully cross-platform and recommended for Linux/macOS users.
  • Consider listing Azure CLI examples before PowerShell in each section, or explicitly note CLI as the default for non-Windows environments.
  • Add brief notes or links for Linux/macOS users about installing Azure CLI and using Bash/zsh shells.
  • If possible, provide Bash script snippets for common operations (e.g., looping over node pools).
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation primarily uses Azure CLI commands and kubectl, which are cross-platform tools. However, it does not explicitly mention Linux/macOS environments or provide guidance for those platforms. The examples and instructions are generic, but there is a subtle bias in that Windows is implicitly assumed (e.g., no mention of shell differences, environment variable syntax, or installation nuances for Linux/macOS). There are no PowerShell-specific commands or Windows-only tools, but the lack of explicit Linux/macOS guidance may create minor friction.
Recommendations
  • Add a note clarifying that Azure CLI and kubectl commands work on Windows, Linux, and macOS, and provide links to installation instructions for each platform.
  • Include example environment variable syntax for both Windows (e.g., $RESOURCE_GROUP) and Linux/macOS (e.g., export RESOURCE_GROUP=...).
  • Mention any potential differences in command usage or prerequisites for Linux/macOS users, such as package managers or shell requirements.
  • Ensure that all CLI examples are tested and confirmed to work on Linux/macOS terminals.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Missing Minor Windows Tools
Summary
The documentation provides troubleshooting steps for the Agentic CLI for AKS and generally includes both Windows/macOS and Linux guidance. However, in several sections (especially Docker-related issues), Windows/macOS instructions are listed before Linux, and Windows-specific tools (Docker Desktop) are referenced. There are no PowerShell examples, but Windows/macOS users are directed to GUI actions (launch Docker Desktop), while Linux users are given CLI commands. All Azure CLI and kubectl examples are cross-platform. 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 'windows_first' bias.
  • Provide explicit Linux/macOS CLI alternatives for Docker Desktop actions (e.g., 'systemctl start docker' for macOS with Homebrew installs).
  • Clarify that Docker Desktop is not available on Linux and provide links to Linux-specific Docker troubleshooting.
  • Consider adding PowerShell examples for Windows users if CLI is preferred, or Bash equivalents for macOS.
  • Ensure parity in troubleshooting steps for all platforms, including edge cases (e.g., Docker on macOS without Docker Desktop).
GitHub Create Pull Request
Aks About the Agentic CLI for Azure Kubernetes Service (AKS) ...s/blob/main/articles/aks/cli-agent-for-aks-overview.md
Low Priority View Details →
Scanned: 2026-02-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation describes the Agentic CLI for AKS in a platform-neutral manner, but the 'Client mode' section references Docker and Azure CLI credentials without clarifying Linux/macOS compatibility or providing Linux/macOS-specific instructions. There are no explicit Windows-only tools mentioned, but the lack of Linux/macOS examples and prerequisites creates mild friction for non-Windows users.
Recommendations
  • Explicitly state that the Agentic CLI for AKS supports Windows, Linux, and macOS platforms.
  • Provide installation and usage instructions for Linux/macOS, including Docker and Azure CLI setup on those platforms.
  • Mention any platform-specific considerations (e.g., Docker installation differences, Azure CLI authentication nuances) for Linux/macOS users.
  • Add example commands or screenshots for Linux/macOS terminals alongside any Windows examples.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides parity for both Windows/macOS and Linux users in most sections, especially regarding Docker installation and AKS agent deployment. However, in the 'Verify Docker installation and start Docker daemon' section, instructions for starting Docker are presented as 'macOS/Windows' first, followed by Linux. This is a minor ordering bias, but all necessary Linux instructions are present. No PowerShell-only examples, Windows tools, or missing Linux examples are detected.
Recommendations
  • Present Linux instructions alongside or before Windows/macOS instructions in sections where order may imply priority.
  • Consider grouping OS-specific instructions in a neutral order or explicitly stating that all OSes are equally supported.
  • Continue to ensure all CLI and tool usage examples are cross-platform and avoid Windows-specific tooling unless required.
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-12 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) before PowerShell. There are no Windows-specific tools or commands used elsewhere, and all example commands (kubectl, curl, git) are cross-platform and compatible with Linux/macOS. The only minor bias is the inclusion of Azure PowerShell as an alternative, which is more common on Windows, but this is balanced by Azure CLI instructions. No critical steps are Windows-only.
Recommendations
  • Continue to list Azure CLI (cross-platform) as the primary option for all tasks.
  • Explicitly mention that all commands (kubectl, curl, git) work on Linux/macOS and Windows.
  • Consider adding brief notes for Linux/macOS users about installing Azure CLI and PowerShell, if relevant.
  • Ensure parity in future updates by avoiding Windows-only tools unless the feature is Windows-specific.
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-12 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 both PowerShell and CLI are cross-platform, the PowerShell section is more prominent and detailed, and PowerShell is traditionally associated with Windows. The PowerShell prerequisites and instructions are listed before Azure CLI, and the PowerShell section includes extra guidance about installation and usage on Windows, macOS, and Linux, but the CLI section is less emphasized. There are no missing Linux examples, and both PowerShell and CLI commands work on Linux/macOS, but the structure and emphasis favor PowerShell/Windows users.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is more widely used and natively cross-platform.
  • Balance the detail level between PowerShell and CLI sections, ensuring CLI instructions are as thorough as PowerShell.
  • Explicitly mention that both PowerShell and CLI are cross-platform, and highlight CLI as the preferred option for Linux/macOS users.
  • Add a note recommending Azure CLI for Linux/macOS users, or provide links to CLI installation instructions for all platforms.
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-12 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 section 'Listing the CRDs in your cluster', the example uses 'kubectl get crds | findstr dapr.io', which is a Windows/PowerShell command (findstr) and does not provide a Linux/macOS equivalent (e.g., using grep). Additionally, the use of PowerShell-style variables (e.g., $MY_RESOURCE_GROUP) in CLI examples may be confusing for Bash users, though this is minor.
Recommendations
  • Provide Linux/macOS equivalents for commands using Windows-specific tools, e.g., 'kubectl get crds | grep dapr.io' alongside the findstr example.
  • Clarify variable syntax for both Bash and PowerShell users in CLI examples, or use cross-shell compatible syntax.
  • Review all CLI snippets to ensure they work seamlessly on Bash shells, not just PowerShell.
  • Consider showing both Windows and Linux/macOS command examples where shell-specific differences exist.
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-12 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 PowerShell alongside Azure CLI in the 'Before you begin' section and links to PowerShell documentation. The only explicit PowerShell mention is for listing subnets, but no Linux-specific alternatives (e.g., Bash, shell scripting) are given. Azure CLI is used for all command-line examples, which is cross-platform, but PowerShell is mentioned first in some places. No Linux/macOS-specific friction is present, but the PowerShell references may create minor bias.
Recommendations
  • Where PowerShell is mentioned, clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Provide Bash or shell alternatives for listing subnets (e.g., using Azure CLI), rather than referencing PowerShell.
  • Consider listing Azure CLI before PowerShell in prerequisite steps to reinforce Linux parity.
  • Explicitly state that all Azure CLI commands work on Linux/macOS/Windows.
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-12 00:00
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 for all Azure-related operations, but consistently includes PowerShell (a Windows-centric tool) alongside CLI. The CLI is cross-platform, but PowerShell is presented equally, which may imply Windows as a primary platform. There are no Linux-specific examples or explicit mentions of Linux/macOS workflows. However, all core commands (Azure CLI, Helm, kubectl, git) are cross-platform, and the bash shell is used for Helm and Kubernetes commands.
Recommendations
  • Clarify that Azure CLI is recommended for Linux/macOS users, and PowerShell is primarily for Windows.
  • Consider showing Azure CLI examples first, or labeling them as the default for cross-platform users.
  • Add a note indicating that PowerShell examples are for Windows users, and CLI examples are for all platforms.
  • Explicitly mention that Helm, kubectl, and git commands work on Linux/macOS and Windows.
  • Optionally, provide Linux/macOS-specific installation instructions for Azure CLI, Helm, and kubectl.
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-11 00:00
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 a minor bias in the section 'Verify TLS Bootstrapping is enabled on current agent node pool', where the Windows file path ('C:\k\bootstrap-config') is mentioned after the Linux path. Additionally, in the example output for certificate signing requests, Windows node names (e.g., 'akswinp7000000') are shown, but Linux equivalents are not. All command-line examples use Azure CLI and bash, which are cross-platform, and most instructions are Linux-centric.
Recommendations
  • When showing example output, include both Linux and Windows node names for parity.
  • In the 'Verify TLS Bootstrapping' section, mention Linux file paths first, as AKS is primarily Linux-based.
  • Explicitly state that all commands are applicable to both Linux and Windows node pools unless otherwise noted.
  • Add clarifications or links for Windows users on how to run bash commands (e.g., using WSL or Azure Cloud Shell).
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-11 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 covers both Windows/macOS and Linux environments. However, in several sections, Windows/macOS instructions (e.g., 'Launch Docker Desktop') are listed before Linux equivalents, and Linux-specific solutions are sometimes less detailed or presented after Windows steps. There are no PowerShell examples, but Windows tools (Docker Desktop) are mentioned before Linux commands. Azure CLI examples are platform-neutral, but some troubleshooting steps (e.g., Docker permission issues) are more detailed for Linux. Overall, Linux users are supported but not always given equal prominence.
Recommendations
  • Present Linux and Windows/macOS troubleshooting steps in parallel or with equal prominence, rather than listing Windows/macOS first.
  • Add more detailed Linux troubleshooting steps where appropriate (e.g., for Docker Desktop alternatives on Linux).
  • Where possible, clarify which steps apply to all platforms and which are platform-specific.
  • Consider including explicit macOS/Linux/Windows tabs or sections for clarity.
  • Ensure Linux examples are as comprehensive as Windows/macOS examples.
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-11 00:00
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 focus on Azure CLI commands. While most steps are cross-platform, there is a subtle Windows bias in the Docker daemon startup instructions: 'macOS/Windows' users are told to launch Docker Desktop, while Linux users are given explicit shell commands. Additionally, the verification step for client mode cleanup uses 'ls ~/.azure/aksAgent.config', which is Unix-specific and may not work on Windows. No PowerShell examples are provided, but Windows users are implicitly assumed to use Docker Desktop, which may not be the only option. The ordering of instructions sometimes puts Windows/macOS first. Overall, the bias is minor and does not prevent Linux/macOS users from completing the tasks.
Recommendations
  • Provide explicit instructions for starting Docker daemon on Windows (e.g., using Windows Services or PowerShell, not just Docker Desktop).
  • Clarify the location of configuration files for Windows users (e.g., mention %USERPROFILE%\.azure\aksAgent.config).
  • Include PowerShell examples for Windows users where shell commands are given for Linux/macOS.
  • Ensure all file path examples are cross-platform or provide alternatives for Windows.
  • Where possible, avoid ordering instructions as 'macOS/Windows' first; consider 'Linux/macOS/Windows' or platform-neutral ordering.
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-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 (Linux/macOS-friendly) and Azure PowerShell (Windows-centric) examples for troubleshooting, but consistently presents PowerShell examples immediately after CLI and gives them equal prominence. There are no Windows-only tools or patterns, but the PowerShell tab is always present, which may create minor friction for Linux/macOS users. All YAML examples and portal instructions are platform-neutral, and the Azure CLI is featured first, but parity is not perfect.
Recommendations
  • Consider clarifying that Azure PowerShell is primarily for Windows users, and Azure CLI is cross-platform.
  • Add explicit notes or tips for Linux/macOS users, e.g., 'Azure CLI works on Linux, macOS, and Windows.'
  • If possible, provide Bash shell examples for IP retrieval (e.g., using curl or wget) alongside Azure CLI.
  • Review tab order and ensure Azure CLI is always shown first, with PowerShell as an optional alternative.
  • Mention that Cloud Shell supports both Bash and PowerShell, and users can select their preferred environment.
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-11 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 detailed and includes instructions for installing/upgrading PowerShell on Windows, macOS, and Linux. However, PowerShell is a Windows-centric tool, and its section appears before the Azure CLI section, which is more native to Linux/macOS environments. There is a minor bias in presenting PowerShell before CLI and giving PowerShell-specific guidance, but Linux/macOS users are not blocked and can use Azure CLI.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is more cross-platform and native for Linux/macOS users.
  • 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 parity in example depth and clarity between PowerShell and CLI sections.
GitHub Create Pull Request
← Previous Page 16 of 25 Next →