Aks

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

Bias Trend Over Time

Pages with Bias Issues

365 issues found
Showing 201-225 of 365 flagged pages
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-04 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 Portal, Azure PowerShell, and Azure CLI, ensuring both Windows and cross-platform (Linux/macOS) users are supported. However, the PowerShell section is more prominent and detailed, with explicit instructions for installing/upgrading Azure PowerShell on Windows, macOS, and Linux. The PowerShell tab appears before the CLI tab, and the PowerShell workflow is described in greater depth, which may subtly prioritize Windows-centric tooling and patterns.
Recommendations
  • Ensure that Azure CLI instructions are as detailed as the PowerShell instructions, including guidance for installation and environment setup on all platforms.
  • Consider placing the Azure CLI tab before or alongside the PowerShell tab, as the CLI is the primary cross-platform tool for Azure.
  • In the prerequisites, provide equal emphasis on both Azure CLI and PowerShell, and clarify that both are fully supported on Windows, Linux, and macOS.
  • Where PowerShell installation/upgrade links are provided for all OSes, do the same for Azure CLI.
  • Review the order and depth of examples to avoid the impression that PowerShell is the preferred or default approach.
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-04 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation generally maintains cross-platform parity, but there are minor signs of Windows bias. In the Docker daemon startup instructions, macOS/Windows (Docker Desktop) is mentioned before Linux, and Linux users are given explicit shell commands while Windows/macOS users are told to launch Docker Desktop. The verification steps for cleanup and Docker images use bash commands, which are not directly applicable to Windows users unless they use WSL or Git Bash. There are no PowerShell-specific examples, but the ordering and phrasing sometimes prioritize Windows/macOS over Linux. No critical functionality is locked to Windows, and Linux users can complete all tasks.
Recommendations
  • Explicitly mention that Docker Desktop is available for both Windows and macOS, and clarify Linux alternatives.
  • Provide PowerShell equivalents for bash commands where relevant, or clarify that bash commands are for Linux/macOS and suggest alternatives for Windows users (e.g., using WSL, PowerShell, or Docker Desktop UI).
  • When listing OS-specific instructions, alternate the order or present them in parallel to avoid implicit prioritization.
  • Add a note about using WSL or Git Bash for Windows users who want to run bash commands.
  • Ensure all verification and cleanup steps are clearly described for both Linux and Windows environments.
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-04 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation generally provides troubleshooting steps for both Windows/macOS and Linux users, especially in Docker-related sections. However, in several places, instructions for Windows/macOS (specifically Docker Desktop) are listed before Linux equivalents, and there is a slight tendency to mention Windows/macOS solutions first. There are no PowerShell-specific commands, but the pattern of listing Windows/macOS before Linux may subtly reinforce a Windows-first approach.
Recommendations
  • Present Linux and Windows/macOS instructions in parallel or in a neutral order (e.g., Linux first, alphabetical, or grouped together).
  • Explicitly mention that commands are cross-platform where applicable.
  • Where possible, provide platform-agnostic troubleshooting steps before platform-specific ones.
  • Ensure parity in troubleshooting details for both Linux and Windows/macOS users.
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-04 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation is generally cross-platform and focuses on Azure CLI and Bicep, both of which are available on Windows, Linux, and macOS. However, there is a minor Windows bias in the section 'Listing the CRDs in your cluster', where the example uses PowerShell's 'findstr' command with 'kubectl', which is specific to Windows. No Linux/macOS equivalent (e.g., 'grep') is provided, and the example is not presented in a cross-platform way. Additionally, the PowerShell example appears before any mention of Linux alternatives.
Recommendations
  • Provide both Windows (findstr) and Linux/macOS (grep) examples for commands that involve text filtering, e.g., 'kubectl get crds | grep dapr.io'.
  • Explicitly state that Azure CLI and Bicep commands work on Windows, Linux, and macOS, and link to installation instructions for each platform.
  • Where shell commands are shown, use cross-platform syntax or provide tabs/examples for each OS when differences exist.
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-04 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides both Azure CLI (cross-platform) and Azure PowerShell (primarily Windows-focused) instructions for managing AKS authorized IP ranges. However, the Azure CLI tab is presented first, and all command-line examples are cross-platform. There are no exclusive Windows tools or PowerShell-only instructions, and no missing Linux/macOS examples. The rest of the documentation is focused on the Azure portal, which is web-based and OS-agnostic.
Recommendations
  • No significant improvements needed; Azure CLI is already presented first and is cross-platform.
  • Ensure that any future command-line examples continue to provide Azure CLI (or Bash) instructions before or alongside PowerShell.
  • If possible, clarify in the PowerShell tab that Azure PowerShell is available cross-platform (on macOS/Linux via PowerShell Core), to avoid the perception that it's Windows-only.
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-04 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for resource cleanup, but lists Azure CLI first. Azure PowerShell is mentioned as an alternative throughout, but no Linux-specific shell or tooling is highlighted. All command-line examples use cross-platform tools (kubectl, curl, git), and there are no Windows-only commands or tools. However, Azure PowerShell is a Windows-first tool, and its inclusion without mentioning Linux shell alternatives (e.g., Bash scripts) may create minor friction for Linux/macOS users.
Recommendations
  • Explicitly state that all CLI examples (kubectl, curl, git) work on Linux, macOS, and Windows.
  • Clarify that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
  • Consider adding a note that Azure PowerShell is available on Linux/macOS, or link to installation instructions for those platforms.
  • If possible, provide Bash script examples for resource cleanup alongside Azure CLI 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-04 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all Azure resource management steps, with clear tabbed separation. However, Azure PowerShell is a Windows-centric tool, and its inclusion alongside Azure CLI in every section may create a perception of Windows bias, especially since PowerShell is less commonly used on Linux/macOS for Azure tasks. The CLI (cross-platform) examples are always present and shown first, but PowerShell is given equal prominence throughout.
Recommendations
  • Clarify that Azure CLI is cross-platform and recommended for Linux/macOS users, while PowerShell is primarily for Windows.
  • Consider moving PowerShell examples to a separate section or appendix, or labeling them as 'Windows/PowerShell' to reduce confusion for non-Windows users.
  • Add a brief note in the prerequisites or introduction specifying which tool is best for which OS.
  • Ensure all CLI commands are tested and work on Linux/macOS shells (bash/zsh), and highlight any OS-specific caveats.
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-04 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure portal for all major operations. However, Azure PowerShell examples are given equal prominence to Azure CLI, and in some sections, PowerShell is listed before portal instructions. There is a slight 'windows_first' bias in that PowerShell is a Windows-centric tool, and its inclusion alongside CLI may suggest a preference for Windows environments. However, all CLI commands are cross-platform, and no steps require Windows-only tools or patterns. No Linux/macOS users are blocked from completing the tutorial, but the presence and prominence of PowerShell may create minor friction for non-Windows users.
Recommendations
  • Clarify that Azure CLI is fully cross-platform and recommend it as the default for Linux/macOS users.
  • Consider listing Azure CLI instructions before PowerShell in all sections.
  • Add a brief note at the start explaining that PowerShell examples are primarily for Windows users, while CLI is suitable for all platforms.
  • Ensure that any references to installing Azure PowerShell include a note about its availability on Linux/macOS (if relevant), or direct Linux/macOS users to CLI.
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-03 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 examples and guidance for both client and cluster modes. While the CLI itself is cross-platform and most instructions are generic, there are subtle signs of Windows bias: in the Docker startup instructions, macOS/Windows steps (Docker Desktop) are described before Linux (systemctl), and Linux users are given less detail. There are no PowerShell-specific commands, but the ordering and phrasing favor Windows/macOS users. Some verification steps (e.g., checking config file location) assume a default home directory structure typical of Windows/macOS. Linux-specific troubleshooting or alternative commands (e.g., service management, file locations) are not always included.
Recommendations
  • Present Linux instructions alongside or before Windows/macOS steps, especially for Docker startup and verification.
  • Include explicit Linux command-line examples for all steps, such as checking config file locations and cleaning up Docker images.
  • Clarify differences in file paths and environment setup for Linux users.
  • Add troubleshooting tips for common Linux issues (e.g., permissions, systemd status).
  • Ensure parity in detail and clarity for Linux/macOS instructions compared to Windows.
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-03 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation generally provides cross-platform guidance, but in several troubleshooting steps, Windows and macOS instructions (e.g., 'Launch Docker Desktop') are listed before Linux equivalents. The documentation refers to 'Docker Desktop' as the solution for Windows/macOS, which is a Windows/macOS-specific tool, while Linux users are given systemd-based instructions. In some cases, Windows and macOS are grouped together, and Linux is addressed separately, with Windows instructions appearing first. All command-line examples are cross-platform (bash, Azure CLI, kubectl), and there are no PowerShell-specific commands or Windows-only command syntax.
Recommendations
  • Alternate the order of platform instructions, or present all platforms in parallel (e.g., with tabs for Windows, macOS, Linux) to avoid consistently listing Windows/macOS first.
  • Explicitly mention Linux GUI options for Docker if available, or clarify that Docker Desktop is not available on Linux.
  • Where possible, provide parity in troubleshooting steps (e.g., if a GUI tool is mentioned for Windows/macOS, suggest equivalent Linux tools or clarify their absence).
  • Consider using headings or callouts for each OS to make parity clear.
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-03 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides three main approaches for configuring Azure CNI networking in AKS: Azure portal, Azure PowerShell, and Azure CLI. The PowerShell section is detailed and references Windows-centric tooling, but it does mention installation and usage on macOS and Linux. The PowerShell example appears before the CLI example, which is more cross-platform. There are no explicit Linux/macOS examples or screenshots, and PowerShell is generally perceived as a Windows-first tool, despite its cross-platform support.
Recommendations
  • Add explicit Linux/macOS command-line examples or notes, especially for Azure CLI usage.
  • Clarify that Azure PowerShell can be used on Linux/macOS and provide more parity in instructions (e.g., shell commands for Linux/macOS environments).
  • Consider presenting Azure CLI examples before PowerShell, as CLI is more universally available and preferred on Linux/macOS.
  • Include troubleshooting or environment setup notes for Linux/macOS users, such as SSH key generation and shell differences.
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-03 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation is generally cross-platform and focuses on Kubernetes and Azure CLI, which are available on Linux, macOS, and Windows. However, there are minor instances of Windows bias: (1) PowerShell is mentioned as an option for creating an AKS cluster and for listing subnets, and (2) Windows/PowerShell tools are referenced before or alongside Azure CLI equivalents, rather than after or in parity with Linux/macOS tools.
Recommendations
  • When listing options for creating AKS clusters or managing resources, present Azure CLI (cross-platform) first, then PowerShell (Windows-centric) as an alternative.
  • Where PowerShell commands are referenced (e.g., for listing subnets), ensure that Azure CLI equivalents are shown first and clearly marked as cross-platform.
  • Consider adding explicit notes that Azure CLI works on Linux/macOS/Windows, and PowerShell is primarily for Windows users.
  • If PowerShell is mentioned, provide equivalent Bash or shell commands for Linux/macOS users, or clarify that PowerShell Core is available cross-platform if relevant.
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-03 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation is generally cross-platform and focused on Azure CLI and Bicep, which are available on Windows, Linux, and macOS. However, there is a minor Windows bias in the example for listing Dapr CRDs, where the command uses 'findstr' (a Windows-only tool) with kubectl, and this is the only example given for filtering CRDs. Additionally, the use of PowerShell syntax (e.g., environment variable assignment with $MY_RESOURCE_GROUP) appears before any mention of Linux/macOS alternatives, which may cause friction for non-Windows users.
Recommendations
  • Provide Linux/macOS equivalent commands for filtering CRDs, such as 'kubectl get crds | grep dapr.io'.
  • When showing environment variable assignment, include both PowerShell (Windows) and Bash (Linux/macOS) syntax, or use tabs to separate them.
  • Explicitly state that Azure CLI and Bicep are cross-platform, and provide links or notes for installing them on Linux/macOS.
  • Review all command examples to ensure they are not Windows-specific unless necessary.
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-03 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) instructions for managing AKS cluster authorized IP ranges. However, PowerShell examples are presented immediately after CLI examples and with equal prominence, which may subtly reinforce Windows tooling. The documentation does not provide any Windows-only examples, nor does it omit Linux/macOS equivalents, but the inclusion and ordering of PowerShell instructions could be seen as a minor Windows-first bias.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, while PowerShell is primarily for Windows users.
  • Consider listing Azure CLI instructions first and clarifying its cross-platform nature.
  • Add a note that PowerShell is optional and mainly for users on Windows, while CLI is recommended for Linux/macOS.
  • Ensure screenshots and UI references do not assume a Windows environment (e.g., avoid showing Windows-specific browser or OS elements).
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-03 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation mentions Azure CLI, Azure PowerShell, and Azure Portal as options for creating AKS clusters, listing Azure PowerShell before Linux-native alternatives. However, all configuration, verification, and troubleshooting examples use Azure CLI and kubectl, which are cross-platform tools. No PowerShell-specific commands or Windows-only tools are used in the main workflow. There are no examples or instructions that are exclusive to Windows, nor are Linux/macOS users disadvantaged in following the guide.
Recommendations
  • List Azure CLI before Azure PowerShell when presenting options for cluster creation, as CLI is cross-platform and preferred by Linux/macOS users.
  • Explicitly state that all shown commands (Azure CLI, kubectl) work on Linux, macOS, and Windows.
  • Consider providing a brief note that PowerShell is primarily for Windows users, and recommend Azure CLI for Linux/macOS users.
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-03 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides parallel examples for both Azure CLI and Azure PowerShell throughout, but consistently lists Azure PowerShell (a Windows-centric tool) as an equal alternative to Azure CLI, and sometimes before Linux-native workflows. There are no explicit Linux/macOS-specific instructions or troubleshooting tips, and PowerShell is presented as a first-class option, which may create friction for Linux/macOS users unfamiliar with PowerShell.
Recommendations
  • Clearly indicate that Azure CLI is cross-platform and preferred for Linux/macOS users, while Azure PowerShell is primarily for Windows.
  • Add notes or callouts specifying that PowerShell examples are intended for Windows users, and that CLI examples are recommended for Linux/macOS.
  • Consider listing Azure CLI examples before PowerShell examples, or defaulting to CLI in mainline instructions, with PowerShell as an alternative.
  • Include troubleshooting tips or links for Linux/macOS users (e.g., common issues with Azure CLI installation, SSH key generation, etc.).
  • Explicitly mention that Azure Cloud Shell is available cross-platform and can be used from any OS.
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-03 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents both Azure CLI and Azure PowerShell as options for resource management, but PowerShell is mentioned alongside CLI in prerequisites and is given its own example in the clean-up section. The ordering of examples and references sometimes places Windows/PowerShell tools before Linux-native equivalents, which may subtly suggest a Windows-first approach. However, all critical steps (deployment, configuration, verification) use cross-platform tools (kubectl, curl, git), and no steps are Windows-only.
Recommendations
  • List Azure CLI before Azure PowerShell in prerequisites and example tabs, as CLI is cross-platform and preferred for Linux/macOS users.
  • Explicitly state that all kubectl and curl commands work on Linux/macOS, and provide any necessary notes for platform differences if applicable.
  • Consider adding a note clarifying that Azure PowerShell is optional and primarily for Windows users, while Azure CLI is recommended for Linux/macOS.
  • Ensure that example tabs for resource deletion (and other management tasks) default to Azure CLI, with PowerShell as a secondary option.
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-03 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all major steps, with Azure CLI (cross-platform) examples consistently shown first. Azure PowerShell (Windows-centric) is given equal prominence, but there are no Linux/macOS-specific shell examples (e.g., Bash scripts) beyond the CLI. There is no evidence of exclusive use of Windows tools or missing Linux examples, as Azure CLI is fully supported on Linux/macOS. The documentation avoids Windows-only tools and does not mention Windows patterns before Linux equivalents.
Recommendations
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows, and that PowerShell examples are primarily for Windows users.
  • Consider adding brief notes or links for Linux/macOS users about installing Azure CLI and using Bash/zsh, especially in the 'Before you begin' section.
  • If relevant, provide example shell scripts for common Linux/macOS workflows (e.g., using Bash for automation).
  • Explicitly state that Azure PowerShell is optional and not required for Linux/macOS users.
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-02 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides configuration instructions for Azure CNI networking in AKS using three methods: Azure portal, Azure PowerShell, and Azure CLI. The PowerShell section is prominent and includes detailed instructions for installing/upgrading Azure PowerShell on Windows, macOS, and Linux. However, PowerShell is a Windows-centric tool, and its inclusion as a primary method may signal a Windows bias. Additionally, the PowerShell instructions and references appear before the Azure CLI examples, which are more universally applicable across platforms. No Linux-specific tools or shell examples (e.g., Bash) are provided, and the CLI instructions are listed last.
Recommendations
  • Present Azure CLI instructions before PowerShell, as CLI is cross-platform and preferred by many Linux/macOS users.
  • Add explicit Bash shell examples or notes for Linux/macOS users where relevant.
  • Clarify that PowerShell is available on Linux/macOS, but Azure CLI is often the default/preferred tool for those platforms.
  • Consider adding a table or section comparing the three approaches, highlighting platform compatibility.
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-02 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation is generally cross-platform and focuses on Azure CLI and Bicep, which are available on Windows, Linux, and macOS. However, there is a minor Windows bias in the 'Listing the CRDs in your cluster' section, where the example uses PowerShell's 'findstr' command with kubectl, which is specific to Windows. No Linux/macOS equivalent (e.g., grep) is provided, and the example is shown without alternatives.
Recommendations
  • Provide Linux/macOS equivalents for shell commands, especially where Windows-specific tools like 'findstr' are used. For example, add a 'kubectl get crds | grep dapr.io' example alongside the PowerShell version.
  • Where possible, clarify that Azure CLI and Bicep commands work on all major platforms, and link to installation instructions for Linux/macOS as well as Windows.
  • Consider using platform-agnostic commands or explicitly showing both Windows and Linux/macOS variants when shell commands are involved.
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-02 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 managing AKS authorized IP ranges. However, PowerShell examples are presented alongside CLI examples, and PowerShell is given a dedicated section. The CLI example is shown first, but the PowerShell section is equally prominent. There are no Windows-only tools or patterns, and all instructions are accessible from any OS. The overall workflow is portal-based and cross-platform, with no missing Linux/macOS examples.
Recommendations
  • Clarify that Azure CLI commands work on Windows, Linux, and macOS, while Azure PowerShell is primarily for Windows users.
  • Consider grouping CLI and PowerShell examples under a 'Choose your platform' heading to reinforce parity.
  • Explicitly mention that Cloud Shell supports both Bash (CLI) and PowerShell, and is available in the portal for all platforms.
  • If possible, add a note that Linux/macOS users should use Azure CLI, while Windows users may use either CLI or PowerShell.
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-02 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation provides both Azure CLI and PowerShell options for prerequisite steps, but references to PowerShell and Windows tooling (e.g., Get-AzVirtualNetworkSubnetConfig) are present before or alongside Linux-friendly alternatives. Azure CLI is used for all actual walkthrough commands, which are cross-platform, but PowerShell is mentioned as an equivalent option for some resource queries. There are no Linux/macOS-specific examples or explicit parity notes.
Recommendations
  • When listing prerequisite tooling, mention Azure CLI first, as it is cross-platform, and clarify that PowerShell is an alternative for Windows users.
  • For resource queries, provide Azure CLI commands as the primary example, and mention PowerShell only as an alternative for Windows users.
  • Add a note clarifying that all kubectl and Azure CLI commands work on Linux, macOS, and Windows.
  • Consider removing or relegating PowerShell references to a 'Windows alternative' section, ensuring Linux/macOS users are not confused or feel excluded.
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-02 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for resource cleanup, but lists Azure CLI first and PowerShell second. The prerequisites mention both Azure CLI and Azure PowerShell as options, but do not show any Linux/macOS-specific instructions or highlight cross-platform differences. All command-line examples use Bash syntax (compatible with Linux/macOS and Windows via WSL or Git Bash), and no Windows-specific tools or patterns are prioritized. However, the presence of Azure PowerShell instructions and references could be seen as a mild Windows-first bias, especially since PowerShell is more commonly used on Windows.
Recommendations
  • Explicitly state that all Bash commands work on Linux, macOS, and Windows (with WSL or Git Bash).
  • Clarify that Azure CLI is cross-platform and provide installation instructions for Linux/macOS users.
  • Consider listing Azure CLI as the primary method, with PowerShell as an alternative, and note platform compatibility.
  • Add a note for Linux/macOS users regarding any differences in Azure CLI or kubectl usage, if applicable.
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-02 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all Azure resource management steps, with CLI examples shown first. There is no explicit Windows-only content, but PowerShell is featured equally alongside CLI, which is more cross-platform. No Linux-specific tools or patterns are missing, but the presence of PowerShell examples may create minor friction for Linux/macOS users who are unlikely to use PowerShell. All critical steps (AKS, ACR, Helm, kubectl) are covered with CLI commands, which work on Linux/macOS.
Recommendations
  • Clearly indicate that Azure PowerShell is optional and primarily for Windows users.
  • Consider moving PowerShell examples to a separate section or appendix, or marking them as 'Windows only'.
  • Add a note that Azure CLI is recommended for Linux/macOS users.
  • Ensure that CLI examples are always shown first (which is currently the case).
  • Optionally, provide bash script snippets for multi-step processes to further help Linux users.
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-02 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides parallel examples for Azure CLI, Azure PowerShell, and Azure portal throughout, but consistently lists Azure PowerShell (a Windows-centric tool) as a primary option alongside Azure CLI. In some sections, PowerShell examples and instructions appear before or with equal prominence to CLI, which is more cross-platform. There are no Linux-specific shell examples (e.g., Bash, zsh), but Azure CLI commands are inherently cross-platform. No Windows-only tools or patterns are used, and the content is not about a Windows-specific AKS feature.
Recommendations
  • Make it clear that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Consider listing Azure CLI examples before PowerShell in each section to reinforce Linux parity.
  • Add brief notes or callouts clarifying that PowerShell is primarily for Windows users, while CLI works on all platforms.
  • Optionally, include Bash/zsh shell script examples for common tasks to further support Linux/macOS users.
GitHub Create Pull Request
← Previous Page 9 of 15 Next →