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 326-350 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-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
Aks Supported Kubernetes Versions in Azure Kubernetes Service (AKS) ...lob/main/articles/aks/supported-kubernetes-versions.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 key operations (such as installing kubectl and listing available Kubernetes versions), but consistently presents Azure CLI (cross-platform) examples first, followed by Azure PowerShell (Windows-centric) examples. There are no Linux-specific commands or shell examples (e.g., Bash), but Azure CLI is cross-platform and covers Linux/macOS users. No Windows-only tools or patterns are mentioned outside of PowerShell. No critical tasks are Windows-only, and Linux support is clearly documented in component tables.
Recommendations
  • Explicitly mention that Azure CLI is cross-platform and recommended for Linux/macOS users.
  • Add Bash shell examples for common tasks (e.g., checking Kubernetes version, installing kubectl) to further improve Linux parity.
  • Clarify in relevant sections (e.g., 'Alias minor version', 'Azure portal and CLI versions') that Azure CLI commands work on Linux/macOS.
  • Consider adding a note that Azure PowerShell is primarily for Windows users, while Azure CLI is for all platforms.
GitHub Create Pull Request
Aks Azure Kubernetes Service (AKS) Managed Gateway API Installation (preview) ...aks-docs/blob/main/articles/aks/managed-gateway-api.md
Low Priority View Details →
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 primarily uses Azure CLI commands and kubectl, which are cross-platform, but does not explicitly mention Linux/macOS compatibility or provide Linux/macOS-specific instructions. All examples are shown generically, but there is a subtle bias in not clarifying that these commands work equally well on Linux/macOS. There are no Windows-specific tools or PowerShell examples, but the lack of explicit Linux/macOS guidance may create minor friction for non-Windows users.
Recommendations
  • Add a note clarifying that Azure CLI and kubectl commands are fully supported on Linux and macOS, not just Windows.
  • Include example commands for Linux/macOS where relevant, such as installation instructions for Azure CLI and jq.
  • Mention any OS-specific prerequisites or differences, if applicable (e.g., how to install Azure CLI or jq on Linux/macOS).
  • Ensure links to Azure CLI installation documentation include Linux/macOS options.
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-16 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 API server authorized IP ranges, but consistently presents Azure CLI (Linux/macOS-friendly) examples first. However, PowerShell examples are also included, which may be more relevant to Windows users. No Windows-only tools or patterns are mentioned, and all instructions are portal-based or cross-platform. There are no missing Linux examples, and Linux node selectors are used in the YAML, indicating Linux parity.
Recommendations
  • Maintain Azure CLI examples as the primary cross-platform option.
  • Continue to provide both Azure CLI and PowerShell examples, but clarify that Azure CLI works on Windows, Linux, and macOS.
  • Consider adding brief notes about using Cloud Shell for cross-platform access.
  • Ensure screenshots and portal instructions do not reference Windows-specific UI elements.
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-16 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 mild Windows bias in the section 'Verify TLS Bootstrapping is enabled on current agent node pool', where Windows node paths are mentioned alongside Linux paths, but the Windows path is listed second. There are no PowerShell or Windows-specific command examples, and all CLI/script examples use Bash or Azure CLI, which are cross-platform. However, there are no explicit Linux/macOS instructions for accessing Windows node paths, nor are there Linux/macOS-specific troubleshooting tips. The documentation could improve Linux parity by clarifying access methods for both OS types and ensuring Linux examples are always present and clear.
Recommendations
  • Ensure all file path examples for both Linux and Windows nodes are accompanied by clear instructions for accessing them from Linux/macOS and Windows environments.
  • Add troubleshooting tips or access methods for Linux/macOS users when interacting with Windows node pools, if relevant.
  • Consider listing Linux examples first, as AKS is primarily Linux-based.
  • Explicitly state when a command or path is OS-specific and provide alternatives where possible.
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-16 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 slight preference for Windows/macOS patterns in Docker startup instructions and verification steps. While most commands are cross-platform (Azure CLI, Bash), the instructions for starting Docker daemon mention Windows/macOS (Docker Desktop) before Linux (systemctl), and verification steps for client mode cleanup use Windows-style paths (e.g., ~/.azure/aksAgent.config) without explicit Linux/macOS parity. There are no PowerShell-specific commands, but the ordering and phrasing sometimes prioritize Windows/macOS tools and workflows.
Recommendations
  • Ensure that Linux instructions are given equal prominence and detail as Windows/macOS instructions, especially for Docker startup and verification.
  • Provide explicit Linux/macOS example paths and commands where relevant (e.g., configuration file locations, Docker image cleanup).
  • Consider adding a table or section that summarizes OS-specific steps for Docker installation, startup, and troubleshooting.
  • When mentioning Docker Desktop, clarify that it is not available on Linux and provide Linux alternatives first or equally.
  • Review all example commands and outputs for OS-specific assumptions; add notes or alternatives for Linux/macOS users where needed.
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-16 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 detailed, with instructions for installing/upgrading PowerShell on Windows, macOS, and Linux. However, PowerShell is traditionally associated with Windows, and its section appears before the CLI section. The CLI section uses bash-style syntax, which is more familiar to Linux/macOS users, but is presented after PowerShell. There are no missing Linux examples, and Azure CLI is well-supported.
Recommendations
  • Consider presenting Azure CLI examples before PowerShell, as CLI is more universally used across platforms.
  • Explicitly mention that Azure CLI commands work on Linux/macOS/Windows and highlight its cross-platform nature.
  • Add brief notes clarifying that PowerShell is available on Linux/macOS, but Azure CLI is often preferred for Linux users.
  • Ensure parity in detail and guidance between PowerShell and CLI sections.
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-16 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 Windows/PowerShell tools (e.g., Get-AzVirtualNetworkSubnetConfig) are present. Azure CLI is used for all main examples, which is cross-platform, but PowerShell is mentioned alongside Azure CLI in the 'Before you begin' section and for subnet listing. The PowerShell cmdlet is referenced before its Linux equivalent (Azure CLI) in the subnet listing section. No Linux/macOS-specific friction is present, but Windows tools are referenced and sometimes listed first.
Recommendations
  • When listing prerequisite tools, mention Azure CLI first as it is cross-platform, and clarify that PowerShell is optional for Windows users.
  • For subnet listing, provide Azure CLI as the primary example and mention PowerShell only as an alternative for Windows users.
  • Consider adding explicit notes that all Azure CLI commands work on Linux/macOS, and that PowerShell is only required for Windows environments.
  • Avoid referencing Windows tools (PowerShell) unless necessary, and always provide a Linux/macOS equivalent.
  • Where possible, use Azure CLI for all examples to maximize cross-platform accessibility.
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-16 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation generally provides cross-platform troubleshooting steps for the Agentic CLI for AKS, but in several Docker-related sections, Windows/macOS instructions (Docker Desktop) are listed before Linux equivalents, and there is a heavier emphasis on Docker Desktop (a Windows/macOS tool) compared to Linux-native Docker management. No PowerShell-specific commands are present, but the pattern of mentioning Windows/macOS first and referencing Docker Desktop as the primary tool for those platforms indicates a mild Windows bias. All critical tasks are covered for Linux, so Linux users are not blocked.
Recommendations
  • Alternate the order of platform instructions (sometimes list Linux first) to avoid implicit prioritization of Windows/macOS.
  • Where Docker Desktop is mentioned, clarify that on Linux, Docker is typically managed via systemd and the CLI, and that Docker Desktop is not required.
  • Add explicit notes that all commands are supported on Linux, macOS, and Windows, and clarify any platform-specific differences.
  • If possible, provide Linux/macOS-specific troubleshooting screenshots or examples alongside Windows ones.
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-16 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 (both platform-agnostic). However, in the 'Listing the CRDs in your cluster' section, the example uses 'kubectl get crds | findstr dapr.io', which is a Windows/PowerShell pattern. No equivalent Linux/macOS example (using 'grep') is provided. Additionally, the use of 'findstr' appears before any mention of 'grep', which is absent.
Recommendations
  • Provide both Windows and Linux/macOS examples for commands involving shell utilities. For example, add 'kubectl get crds | grep dapr.io' alongside the 'findstr' example.
  • Clarify that Azure CLI and Bicep commands work on all platforms, and explicitly mention this in the prerequisites.
  • Where shell commands are shown, use platform-neutral language or offer alternatives for both environments.
GitHub Create Pull Request
Aks Azure Kubernetes Service (AKS) Managed Gateway API Installation (preview) ...aks-docs/blob/main/articles/aks/managed-gateway-api.md
Low Priority View Details →
Scanned: 2026-02-16 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 Linux/macOS/Windows. However, the Azure CLI examples are shown using the 'azurecli-interactive' code block, which is sometimes associated with Windows/PowerShell environments, and there is no explicit mention of Linux/macOS compatibility or alternative instructions for those platforms. The order of examples and instructions does not show explicit Linux bias, but Windows users may perceive the CLI examples as more familiar due to the lack of Linux-specific context.
Recommendations
  • Clarify that Azure CLI and kubectl commands are cross-platform and can be run on Linux, macOS, and Windows.
  • Add a short note in the prerequisites or introduction indicating that all CLI instructions are compatible with Bash (Linux/macOS) and PowerShell (Windows).
  • Consider including example commands for Bash and PowerShell if there are any platform-specific differences.
  • Explicitly mention that the Azure CLI can be installed and used on Linux/macOS, with a link to installation instructions for those platforms.
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-16 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The tutorial provides parity between Azure CLI, Azure PowerShell, and Azure portal for all AKS upgrade tasks. However, Azure PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and in some sections, PowerShell examples are shown before CLI. There is no explicit Linux/macOS bias, but the heavy inclusion of PowerShell may create friction for Linux/macOS users, as PowerShell is less commonly used on those platforms. No Windows-only tools or patterns are mentioned, and all commands are cross-platform via Azure CLI or portal.
Recommendations
  • Make Azure CLI the primary or first example in each section, as it is cross-platform and more widely used on Linux/macOS.
  • Clarify that Azure PowerShell is optional and primarily for users already familiar with it.
  • Consider adding a note that Azure CLI is recommended for Linux/macOS users.
  • Ensure that all screenshots and instructions are neutral or show Azure CLI/portal where possible.
GitHub Create Pull Request
← Previous Page 14 of 25 Next →