Aks

535
Total Pages
430
Linux-Friendly Pages
105
Pages with Bias
19.6%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

354 issues found
Showing 51-75 of 354 flagged pages
Aks Connect your Azure Kubernetes Service (AKS) cluster to AI agents using the Model Context Protocol (MCP) server ...main/articles/aks/aks-model-context-protocol-server.md
Low Priority View Details →
Scanned: 2026-02-19 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides platform-specific instructions and download links for Windows, macOS, and Linux, and generally covers all major OSes. However, Windows is often mentioned first in lists and keyboard shortcut instructions, and some tips (such as WSL configuration) are Windows-specific. There are no Linux/macOS-specific troubleshooting tips or examples, and Docker instructions reference Windows-specific credential issues without providing equivalent Linux/macOS guidance. Linux is not omitted, but parity in troubleshooting and tips could be improved.
Recommendations
  • Alternate the order of platform mentions (e.g., sometimes list Linux/macOS before Windows).
  • Provide Linux/macOS-specific troubleshooting tips, especially for Docker credential management and VS Code integration.
  • Add explicit Linux/macOS instructions for common issues (e.g., how to check Azure credentials, kubeconfig paths, and permission troubleshooting).
  • Include Linux/macOS-specific keyboard shortcuts and configuration tips alongside Windows/WSL guidance.
  • Ensure that Docker credential instructions are clear for Linux/macOS users, not just Windows.
GitHub Create Pull Request
Aks Troubleshoot the Agentic CLI for Azure Kubernetes Service (AKS) .../main/articles/aks/agentic-cli-for-aks-troubleshoot.md
Low Priority View Details →
Scanned: 2026-02-19 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Missing Linux Parity Good
Summary
The documentation provides troubleshooting steps for the Agentic CLI for AKS with clear differentiation between Windows/macOS and Linux environments. Windows/macOS instructions (Docker Desktop) are listed before Linux instructions (systemd), but Linux-specific commands are included and explained. No PowerShell examples are given, and all CLI commands are cross-platform (bash and Azure CLI). There is minor bias in listing Windows/macOS steps first, but Linux users are not blocked or disadvantaged.
Recommendations
  • Consider listing Linux instructions before or alongside Windows/macOS steps to avoid implicit prioritization.
  • Explicitly mention that Azure CLI commands are cross-platform and can be run on Linux, macOS, or Windows.
  • Add PowerShell examples for Windows users if relevant, or clarify that bash/Azure CLI commands are preferred.
  • Where possible, clarify any OS-specific nuances (e.g., Docker group membership is not needed on Windows/macOS).
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-19 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, but it does mention installation and usage on macOS and Linux. However, PowerShell is a Windows-centric tool, and its section appears before the Azure CLI, which is more native to Linux/macOS. There are no Linux-specific shell examples (e.g., Bash), and the CLI section is less detailed.
Recommendations
  • Provide Bash shell examples for Linux users alongside PowerShell examples.
  • Move Azure CLI examples before PowerShell, as CLI is more cross-platform and native to Linux/macOS.
  • Clarify that PowerShell instructions are equally applicable on Linux/macOS, or highlight CLI as the preferred method for Linux/macOS users.
  • Add explicit notes or tabs for Linux/macOS workflows, such as using Bash or Zsh.
  • Ensure parity in detail between PowerShell and CLI sections.
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-19 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 installing the Dapr extension on AKS and Arc-enabled Kubernetes clusters. However, there is a minor Windows bias in the 'Listing the CRDs in your cluster' section, where the example uses 'kubectl get crds | findstr dapr.io', which is a Windows/PowerShell pattern. No Linux/macOS equivalent (e.g., using 'grep') is provided. Additionally, the use of Azure CLI throughout is platform-neutral, but the CLI examples and instructions are shown first, which may slightly favor Windows users if they are assumed to use CLI more often.
Recommendations
  • Provide Linux/macOS equivalent commands for listing CRDs, such as 'kubectl get crds | grep dapr.io'.
  • Explicitly mention that Azure CLI is cross-platform and link to installation instructions for Linux/macOS.
  • Where shell commands are shown, offer both Windows (findstr) and Linux/macOS (grep) examples side by side.
  • Review other sections for similar shell command patterns and ensure parity.
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-19 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 as ways to create an AKS cluster. It also references the PowerShell cmdlet Get-AzVirtualNetworkSubnetConfig as an alternative to the Azure CLI for listing subnets. However, all actual walkthroughs and code examples use cross-platform tools (kubectl, Azure CLI), and there are no PowerShell-specific examples for the main task. The mention of PowerShell is always as an alternative, but it is listed alongside CLI and portal, rather than after Linux/macOS-friendly options.
Recommendations
  • List Azure CLI as the primary recommended tool for Linux/macOS parity, and mention PowerShell as an alternative for Windows users only.
  • Where PowerShell is referenced, clarify that it is for Windows users, and provide equivalent Azure CLI commands first.
  • Consider removing PowerShell references from prerequisite steps unless there is a Windows-specific workflow.
  • Ensure all main task examples use cross-platform tools (kubectl, Azure CLI), as currently done.
GitHub Create Pull Request
Aks Kubernetes on Azure tutorial - Create an Azure Kubernetes Service (AKS) cluster ...ain/articles/aks/tutorial-kubernetes-deploy-cluster.md
Low Priority View Details →
Scanned: 2026-02-19 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides parallel instructions for Azure CLI, Azure PowerShell, and Azure Developer CLI. However, Azure PowerShell is featured equally alongside Azure CLI, which is more commonly used on Linux/macOS. PowerShell is primarily a Windows-centric tool, and its inclusion may suggest Windows bias. Additionally, PowerShell examples are given equal prominence, and in some sections, PowerShell is mentioned before Azure CLI, which could be perceived as 'windows_first'. No Linux-specific examples, shell patterns, or explicit Linux/macOS guidance are provided, but the Azure CLI instructions are cross-platform.
Recommendations
  • Clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Consider adding explicit Bash shell examples or notes for Linux/macOS users, especially for environment variable usage and SSH key management.
  • Reorder sections to consistently present Azure CLI instructions before PowerShell, as CLI is more universal.
  • Add a brief note explaining that PowerShell is primarily for Windows users, while Azure CLI works on all platforms.
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-18 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides both Windows/macOS and Linux instructions for Docker daemon startup, but presents Windows/macOS steps first. All CLI examples use Azure CLI, which is cross-platform, and shell commands are shown in Bash, suitable for Linux/macOS. No PowerShell or Windows-specific tools are referenced, and Linux parity is generally maintained.
Recommendations
  • Present Linux instructions before Windows/macOS in Docker daemon startup steps, or group them equally.
  • Explicitly mention that all Azure CLI commands work on Linux, macOS, and Windows.
  • Consider adding a note that Bash commands are applicable to Linux/macOS, and Windows users may use WSL or Docker Desktop terminal.
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-18 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 PowerShell examples are presented immediately after CLI and are given equal prominence. There is no explicit Linux/macOS bias, but the PowerShell section may be unnecessary for Linux/macOS users. The rest of the documentation is portal-centric and platform-agnostic, with all YAML examples targeting Linux node pools. No Windows-specific tools or patterns are mentioned outside the PowerShell section.
Recommendations
  • Clearly indicate that Azure PowerShell examples are for Windows users, and Azure CLI examples are cross-platform.
  • Consider presenting Azure CLI examples first, and PowerShell examples in a separate, clearly labeled section for Windows users.
  • Add a note clarifying that Azure CLI commands work on Linux, macOS, and Windows, while PowerShell is Windows-centric.
  • If possible, provide Bash alternatives for retrieving the public IP address, or clarify that the CLI example works on Linux/macOS.
GitHub Create Pull Request
Aks Supported Kubernetes Versions in Azure Kubernetes Service (AKS) ...lob/main/articles/aks/supported-kubernetes-versions.md
Low Priority View Details →
Scanned: 2026-02-18 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 key operations (such as installing kubectl and listing AKS versions), but consistently presents Azure CLI (cross-platform) examples first, followed by Azure PowerShell (Windows-centric) examples. No Linux-specific commands or tools are mentioned, but Azure CLI is inherently cross-platform. There are no Windows-only tools or patterns, and Linux is referenced equally in component tables. No critical tasks are Windows-only.
Recommendations
  • Explicitly mention that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Consider adding a brief note or example for Linux/macOS users (e.g., installation of Azure CLI or kubectl via package managers like apt, brew, or curl).
  • Where PowerShell is referenced, clarify its Windows focus and suggest Azure CLI for Linux/macOS.
  • Add links or references to Linux/macOS installation guides for Azure CLI and kubectl.
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-18 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 notably detailed and references Windows tools and patterns (such as PowerShell cmdlets and Cloud Shell), and is presented before the Azure CLI section. The PowerShell section includes explicit instructions for Windows, macOS, and Linux installation, but the CLI section is less prominent. There is a slight bias toward Windows/PowerShell usage, but Linux/macOS users can complete all tasks using Azure CLI or PowerShell.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is more universally used across platforms.
  • Expand Azure CLI instructions to match the detail provided in the PowerShell section, including environment setup and prerequisites for Linux/macOS.
  • Explicitly mention that both PowerShell and CLI are fully supported on Linux/macOS, and provide links to installation guides for each platform.
  • Consider adding Bash shell examples or highlighting CLI usage in Linux/macOS contexts.
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-18 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides a single example of a Windows file path for verifying TLS Bootstrapping ('C:\k\bootstrap-config'), while the Linux equivalent is also mentioned but not shown first. All other examples and commands are either cross-platform (Azure CLI, kubectl, bash, curl) or explicitly reference Linux file paths. There are no PowerShell-specific commands, Windows tools, or Windows-only patterns used. The Windows path is mentioned after the Linux path, but no Linux-specific troubleshooting or parity notes are provided.
Recommendations
  • Ensure Linux and Windows examples are presented with equal prominence, ideally side-by-side or with clear parity.
  • Add explicit notes or troubleshooting steps for Linux users where file paths or behaviors may differ.
  • Where file paths are given, clarify any differences in permissions, access, or tooling between Linux and Windows nodes.
  • Consider adding a brief section on accessing Linux agent nodes for certificate checks, as is done for Windows nodes.
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-18 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. Windows/macOS instructions are often mentioned before Linux, and Docker Desktop (a Windows/macOS tool) is referenced, but Linux-specific commands are also provided. Azure CLI and kubectl commands are platform-neutral, but there are no PowerShell-specific examples. However, some solutions (e.g., Docker Desktop restart) are Windows/macOS-centric, and Linux instructions are sometimes secondary. There are minor instances where Linux examples could be more prominent or detailed.
Recommendations
  • Present Linux instructions before or alongside Windows/macOS instructions, especially for Docker troubleshooting.
  • Clarify that Docker Desktop is not available on Linux and provide alternative Linux troubleshooting steps (e.g., checking systemd status, logs).
  • Ensure all troubleshooting steps have parity for Linux, including error messages and solutions.
  • Add explicit notes when steps differ between platforms, and avoid assuming Docker Desktop for Linux users.
  • Consider including macOS-specific commands where relevant, rather than grouping macOS and Windows together.
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-18 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 cluster creation and subnet listing, but consistently mentions Azure PowerShell alongside Azure CLI and portal, and references PowerShell cmdlets before or equally with CLI commands. There are no Linux/macOS-specific examples or notes, and the PowerShell tool is presented as a primary option for resource management, which may create friction for Linux/macOS users.
Recommendations
  • List Azure CLI examples and commands before PowerShell, as Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Clearly indicate that Azure PowerShell is Windows-centric and suggest Azure CLI as the default for cross-platform usage.
  • Where PowerShell cmdlets are referenced (e.g., Get-AzVirtualNetworkSubnetConfig), provide equivalent Azure CLI commands first and clarify their parity.
  • Consider removing or relegating PowerShell references to a separate section or note for Windows users.
  • Add explicit notes that all Azure CLI commands are supported on Linux/macOS, and highlight any differences if present.
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-18 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 tasks, but consistently presents PowerShell as a first-class option alongside CLI. There are no explicit Linux/macOS-specific examples or notes, and PowerShell is featured equally throughout. However, the core workflow uses cross-platform tools (Azure CLI, Helm, kubectl, git), and bash commands are used for Helm and Kubernetes steps. The bias is minor, mainly in the parity of PowerShell and CLI, and the lack of explicit Linux/macOS guidance.
Recommendations
  • Clarify that Azure PowerShell is primarily for Windows users, and Azure CLI is cross-platform (Windows, Linux, macOS).
  • Add notes or guidance for Linux/macOS users, such as installation instructions for Azure CLI, Helm, and kubectl on those platforms.
  • Consider showing Azure CLI examples first, as CLI is the default and recommended tool for cross-platform usage.
  • Explicitly mention that PowerShell examples are for Windows users, and that Linux/macOS users should use Azure CLI.
  • Add troubleshooting tips for Linux/macOS users (e.g., file path differences, shell environment setup).
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-18 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation is generally platform-agnostic, focusing on Azure CLI and Bicep for Dapr extension installation on AKS and Arc-enabled Kubernetes. 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 (such as grep). This is a minor Windows bias, as Linux/macOS users would need to adapt the command themselves.
Recommendations
  • Provide both Windows (findstr) and Linux/macOS (grep) examples for commands involving output filtering, e.g., 'kubectl get crds | grep dapr.io'.
  • Where possible, avoid using platform-specific tools in documentation, or clearly indicate alternatives for other platforms.
  • Consider adding a note or a table showing command variants for different operating systems.
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-18 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides links to Windows (Azure PowerShell) and Linux (Azure CLI) methods for AKS cluster creation, but the PowerShell link is listed before the Azure portal link, and Azure CLI is listed first. All command examples use Azure CLI and kubectl, which are cross-platform and not Windows-specific. No PowerShell or Windows-only tools are used in examples. The documentation explicitly states LocalDNS is only supported on Azure Linux or Ubuntu node pools, and there are no Windows-specific instructions or tools. The minor bias is limited to the order of quickstart links, where PowerShell is mentioned before the portal.
Recommendations
  • List Linux and cross-platform tools (Azure CLI, kubectl) before Windows-specific tools in prerequisite links.
  • Consider grouping quickstart links by platform or clarifying that Azure CLI and Azure PowerShell are both cross-platform.
  • Ensure parity in example commands for both Azure CLI and PowerShell if relevant, but in this case Azure CLI is sufficient since LocalDNS is Linux-only.
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-17 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides parity for Linux, macOS, and Windows users throughout, but in the Docker daemon startup instructions, Windows/macOS are mentioned before Linux. All CLI examples use cross-platform Azure CLI and Bash commands, and Linux-specific instructions are present where relevant. No PowerShell or Windows-only tools are used.
Recommendations
  • In the Docker daemon startup section, consider listing Linux instructions before or alongside Windows/macOS for improved parity.
  • Explicitly state that all Azure CLI and Bash commands are cross-platform and supported on Linux, macOS, and Windows.
  • Ensure that any troubleshooting or advanced configuration sections reference Linux and macOS paths and conventions where applicable.
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-17 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 and does not exhibit Windows bias in examples or tooling. However, in several prerequisite sections, the Azure PowerShell option is mentioned before Linux-centric alternatives (Azure CLI), which is a minor 'windows_first' bias. All technical content, examples, and instructions are Linux-focused and relevant for Linux node pools only.
Recommendations
  • In prerequisite lists, mention Azure CLI before Azure PowerShell to prioritize Linux-friendly tooling.
  • Where possible, clarify that Azure PowerShell is optional and primarily for Windows users, while Azure CLI is cross-platform.
  • Consider adding explicit notes that all examples are Linux-only and not applicable to Windows node pools, to avoid confusion.
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-17 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, focusing on Azure CLI and kubectl commands, which are available on both Windows and Linux. However, in the section 'Verify TLS Bootstrapping is enabled on current agent node pool', the Windows file path ('C:\k\bootstrap-config') is mentioned after the Linux path, but both are provided. There are no PowerShell-specific examples, and all command-line instructions use bash or Azure CLI. No Windows-only tools or patterns are used, and Linux parity is mostly maintained. The only minor bias is that Windows is mentioned second in the file path example, and there are no explicit macOS references.
Recommendations
  • Explicitly mention that all Azure CLI and kubectl commands work on Linux, macOS, and Windows.
  • Add a note clarifying that macOS users can use the Linux instructions.
  • Ensure parity in file path examples by consistently listing Linux, macOS, and Windows paths together.
  • Consider adding a brief section or note about using Azure CLI and kubectl on macOS, if relevant.
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-17 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) first, followed by Azure PowerShell (Windows-centric). No Windows-only tools or patterns are prioritized, and all examples are cross-platform. However, the PowerShell section is present, which could be considered minor Windows bias, but Linux parity is maintained throughout. No critical tasks are Windows-only, and Linux/macOS users can complete all steps.
Recommendations
  • Continue to provide Azure CLI examples first, as this is the most cross-platform approach.
  • Consider explicitly stating that Azure CLI works on Windows, Linux, and macOS, and that PowerShell is primarily for Windows users.
  • If possible, add a Bash-only example for retrieving the public IP address (e.g., using curl or wget), to further improve Linux parity.
  • Ensure screenshots and portal instructions do not reference Windows-specific UI elements or terminology.
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-17 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation generally provides cross-platform troubleshooting steps, but in several places, Windows (and macOS) instructions are listed before Linux equivalents, and 'Docker Desktop' (a Windows/macOS tool) is referenced before Linux-specific commands. Linux instructions are present, but the ordering and emphasis may subtly favor Windows/macOS users.
Recommendations
  • Present Linux, macOS, and Windows instructions in parallel or in a consistent order (e.g., Linux, macOS, then Windows) to avoid implicit prioritization.
  • When referencing Docker, clarify that 'Docker Desktop' is for Windows/macOS and provide equal prominence to Linux service management commands.
  • Where possible, use platform-agnostic language or group instructions by OS with clear headings.
  • Ensure all examples (e.g., for Docker, Azure CLI) are validated to work on Linux, and explicitly state any platform-specific caveats.
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-17 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, including module installation and upgrade steps for Windows, macOS, and Linux. The PowerShell instructions are slightly more detailed and appear before the Azure CLI section. However, Azure CLI examples are present and clearly labeled, ensuring Linux/macOS users can complete the task. There is a minor bias in the ordering and emphasis on PowerShell, but Linux parity is largely maintained.
Recommendations
  • Consider presenting Azure CLI examples before PowerShell, as CLI is more universally supported across platforms.
  • Ensure that CLI instructions are as detailed as PowerShell instructions, including environment preparation and troubleshooting steps.
  • Explicitly note that Azure CLI is recommended for Linux/macOS users, and PowerShell is optional.
  • Add a brief section clarifying that both PowerShell and CLI are fully supported on Linux/macOS, with links to installation guides.
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-17 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation is generally platform-neutral, focusing on Azure CLI and Bicep for Dapr extension installation on AKS and Arc-enabled Kubernetes. However, there is a minor Windows bias in the CRD listing example, which uses 'kubectl get crds | findstr dapr.io' (a Windows/PowerShell pattern) instead of a cross-platform or Linux-first approach. Additionally, the use of Azure CLI throughout is platform-neutral, but the example for listing CRDs could create friction for Linux/macOS users.
Recommendations
  • Replace 'kubectl get crds | findstr dapr.io' with 'kubectl get crds | grep dapr.io', or provide both examples for Windows and Linux/macOS.
  • Where possible, ensure all shell examples are cross-platform or explicitly note OS-specific commands.
  • Review other command snippets for any implicit Windows assumptions and clarify as 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-17 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, PowerShell is referenced as a tool for querying subnets, and its cmdlet is linked before or alongside the Azure CLI equivalent. However, all actual operational examples (manifest creation, kubectl commands, Azure CLI commands) are cross-platform and do not use Windows-specific syntax or tools. There are no PowerShell-only critical steps, and Linux/macOS users can complete all tasks using Azure CLI and kubectl.
Recommendations
  • When listing ways to create an AKS cluster, mention Azure CLI first, as it is cross-platform, and clarify that Azure PowerShell is Windows-centric.
  • When referencing commands to query subnets, list Azure CLI as the primary example and PowerShell as an alternative for Windows users.
  • Consider adding a note that Azure CLI is recommended for Linux/macOS users, while PowerShell is primarily for Windows environments.
  • Ensure that all critical steps have Azure CLI equivalents and that PowerShell is not presented as the default or only option.
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-17 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 (cross-platform) examples first and Azure PowerShell (Windows-centric) examples second. There are no explicit Windows-only tools or patterns, and Linux/macOS users are not blocked from completing any tasks. Bash commands (git, helm, kubectl) are used for Kubernetes-native steps, which are cross-platform. However, the presence of Azure PowerShell throughout, and its parity with Azure CLI, may create mild friction for Linux/macOS users who may not use PowerShell.
Recommendations
  • Clarify that Azure PowerShell is available cross-platform (via PowerShell Core), but Azure CLI is generally preferred for Linux/macOS users.
  • Consider adding a note or section highlighting that Azure CLI is the recommended tool for Linux/macOS, and PowerShell is optional.
  • Ensure that all bash commands are clearly marked as cross-platform, and avoid implying PowerShell is required for non-Windows users.
  • Optionally, provide explicit bash-only workflows for users who do not wish to use PowerShell.
GitHub Create Pull Request
← Previous Page 3 of 15 Next →