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 1-25 of 618 flagged pages
Aks Provision Azure NetApp Files SMB volumes for Azure Kubernetes Service ...-docs/blob/main/articles/aks/azure-netapp-files-smb.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on provisioning SMB volumes for Windows-based AKS workloads. All pod examples use Windows containers (IIS on Windows Server Core), and node selectors are set to Windows. There are no Linux pod/container examples, nor any discussion of mounting SMB volumes from Linux containers. The only usage examples for accessing the SMB share are via Windows tools (cmd.exe, dir). The documentation does not mention Linux compatibility, limitations, or provide Linux-specific guidance for SMB volumes.
Recommendations
  • Add examples for Linux pods mounting SMB volumes, including sample manifests and verification steps using Linux commands (e.g., mount, ls, df).
  • Clarify whether SMB volumes can be mounted by Linux containers in AKS, and document any prerequisites or limitations.
  • Provide parity in troubleshooting and verification steps for both Windows and Linux pods.
  • If SMB volumes are Windows-only, explicitly state this limitation early in the documentation.
  • Include links or references to NFS documentation for Linux workloads, and guidance on choosing between SMB and NFS based on OS.
GitHub Create Pull Request
Aks Enable Group Managed Service Accounts (GMSA) for your Windows Server nodes on your Azure Kubernetes Service (AKS) cluster ...ain/articles/aks/use-group-managed-service-accounts.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows Only Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
This documentation is exclusively focused on enabling Group Managed Service Accounts (GMSA) for Windows Server nodes in AKS. All examples, YAML manifests, and troubleshooting steps are tailored to Windows containers and Windows authentication mechanisms. PowerShell scripts and Windows-specific tools (e.g., IIS, Windows features, Log Monitor) are used throughout, with no mention of Linux equivalents or how Linux nodes might interact with GMSA. There are no Linux container examples, and the guide does not address Linux/macOS users except in general Azure CLI usage.
Recommendations
  • Clearly state at the beginning that GMSA is a Windows-only feature and that the guide is not applicable to Linux nodes.
  • Provide links or references to equivalent Linux authentication mechanisms (e.g., Kerberos integration for Linux containers, if available in AKS).
  • Add a section describing how authentication and service accounts work for Linux nodes in AKS, and how they differ from GMSA.
  • If possible, provide parity documentation for Linux service account management in AKS, or cross-link to such resources.
  • Ensure troubleshooting and verification steps clarify their Windows-only applicability, and suggest alternatives for Linux users where relevant.
GitHub Create Pull Request
Aks Kubernetes on Azure tutorial - Create an Azure Kubernetes Service (AKS) cluster ...ain/articles/aks/tutorial-kubernetes-deploy-cluster.md
Medium Priority View Details →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and Azure Developer CLI, but PowerShell is featured equally alongside CLI and is referenced for installing tools and managing AKS clusters. PowerShell is a Windows-centric tool, and its inclusion may create friction for Linux/macOS users. Additionally, PowerShell installation and usage instructions are presented before any Linux-specific alternatives. There is no explicit Linux/macOS example or mention of Bash or native shell commands for kubectl installation or AKS cluster creation outside of Azure CLI. The documentation assumes Azure CLI and PowerShell are the primary interfaces, potentially overlooking Linux-native workflows.
Recommendations
  • Add explicit Bash/Linux/macOS instructions for installing kubectl (e.g., using curl or package managers like apt, brew, yum).
  • Clarify that Azure CLI commands work on Linux/macOS and Windows, and provide any OS-specific notes if needed.
  • Consider including a Bash example for setting environment variables (e.g., export ACRNAME=...) and SSH key generation.
  • Mention that PowerShell is primarily for Windows users, and suggest alternatives for Linux/macOS users.
  • Ensure that Azure CLI examples are presented first, as it is cross-platform, and clarify its parity across OSes.
GitHub Create Pull Request
Aks Install Dapr Extension for Azure Kubernetes Service (AKS) ...softDocs/azure-aks-docs/blob/main/articles/aks/dapr.md
Medium Priority View Details →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Missing Linux Example 🔧 Windows Tools
Summary
The documentation is generally cross-platform, using Azure CLI and Bicep for all installation and management steps, which are available on Windows, Linux, and macOS. However, in the 'List the CRDs in your cluster' section, the example uses 'kubectl get crds | findstr dapr.io', which relies on the Windows-specific 'findstr' command. There is no equivalent Linux/macOS example (e.g., using 'grep'), and the Windows tool is presented without alternatives.
Recommendations
  • Provide both Windows and Linux/macOS examples for shell commands involving OS-specific tools. For example, show both 'kubectl get crds | findstr dapr.io' (Windows) and 'kubectl get crds | grep dapr.io' (Linux/macOS).
  • When using OS-specific commands, explicitly label them as such and offer alternatives for other platforms.
  • Review all shell command examples to ensure they are either cross-platform or have platform-specific variants.
GitHub Create Pull Request
Aks Kubernetes on Azure tutorial - Create an Azure Kubernetes Service (AKS) cluster ...ain/articles/aks/tutorial-kubernetes-deploy-cluster.md
Medium Priority View Details →
Scanned: 2026-03-07 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The tutorial provides parallel instructions for Azure CLI, Azure PowerShell, and Azure Developer CLI, but PowerShell is featured prominently as a first-class option throughout. PowerShell examples and terminology are used, which may be unfamiliar or less relevant to Linux/macOS users. The documentation sometimes presents PowerShell instructions before Azure CLI, and does not explicitly mention Bash or Linux shell usage outside of Azure Cloud Shell. There are no explicit Linux/macOS-specific examples or guidance, and the install instructions for kubectl focus on Azure CLI/PowerShell commands rather than native package managers (e.g., apt, brew).
Recommendations
  • Add explicit Bash/Linux/macOS shell examples alongside PowerShell, especially for local environments.
  • Include instructions for installing kubectl using native package managers (apt, yum, brew) for Linux/macOS users.
  • Clarify that Azure CLI commands can be run in Bash on Linux/macOS, not just in Azure Cloud Shell.
  • Ensure Azure CLI examples are presented before PowerShell, as CLI is more cross-platform.
  • Add notes or links for Linux/macOS users about prerequisites and environment setup.
GitHub Create Pull Request
Aks Install Dapr Extension for Azure Kubernetes Service (AKS) ...softDocs/azure-aks-docs/blob/main/articles/aks/dapr.md
Medium Priority View Details →
Scanned: 2026-03-06 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is generally cross-platform, using Azure CLI and Bicep for all main instructions, which are available on Windows, Linux, and macOS. However, there is a notable bias in the 'List the CRDs in your cluster' section, where only a Windows-specific example using 'findstr' (a Windows command) is provided for filtering CRDs with kubectl. No Linux/macOS equivalent (e.g., using 'grep') is shown. This could cause confusion or friction for Linux/macOS users.
Recommendations
  • Provide Linux/macOS equivalent commands alongside Windows-specific ones. For example, show both 'kubectl get crds | grep dapr.io' for Linux/macOS and 'kubectl get crds | findstr dapr.io' for Windows.
  • Explicitly state when a command is platform-specific and offer alternatives.
  • Review for any other subtle Windows-first patterns, but the rest of the page appears neutral.
GitHub Create Pull Request
Aks Kubernetes on Azure tutorial - Create an Azure Kubernetes Service (AKS) cluster ...ain/articles/aks/tutorial-kubernetes-deploy-cluster.md
Medium Priority View Details →
Scanned: 2026-03-06 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and Azure Developer CLI. Azure PowerShell is featured equally alongside Azure CLI, which may create friction for Linux/macOS users since PowerShell is primarily a Windows-centric tool. The documentation does not provide Bash-specific or Linux/macOS-native command examples, and PowerShell examples are given equal prominence to Azure CLI, rather than being secondary or optional. However, Azure CLI is cross-platform and is featured first in most sections, mitigating the bias somewhat.
Recommendations
  • Clarify that Azure PowerShell is optional and primarily for Windows users; recommend Azure CLI for Linux/macOS users.
  • Add explicit Bash shell examples for Azure CLI commands, especially for environment variable usage (e.g., export ACRNAME=myacr).
  • Mention that Azure CLI is the preferred tool for Linux/macOS users and that PowerShell is optional.
  • Consider providing a table or section summarizing tool parity and OS compatibility.
  • Add notes about how to install and use Azure CLI and kubectl on Linux/macOS, including links to relevant installation guides.
GitHub Create Pull Request
Aks Kubernetes on Azure tutorial - Create an Azure Kubernetes Service (AKS) cluster ...ain/articles/aks/tutorial-kubernetes-deploy-cluster.md
Medium Priority View Details →
Scanned: 2026-03-05 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, but PowerShell examples and terminology are prominent throughout. PowerShell is a Windows-centric tool, and its inclusion as a primary option may create friction for Linux/macOS users. Additionally, PowerShell instructions are often given equal prominence to Azure CLI, rather than Azure CLI being presented as the default cross-platform method. There are no explicit Linux/macOS-specific examples or notes, and the documentation does not clarify that PowerShell is not natively available on most Linux/macOS systems.
Recommendations
  • Clearly indicate that Azure CLI is the default, cross-platform method and recommend it for Linux/macOS users.
  • Add explicit notes or sections for Linux/macOS users, clarifying that PowerShell is optional and not required.
  • Consider presenting Azure CLI instructions first, followed by PowerShell as an alternative for Windows users.
  • Include links or brief instructions for installing Azure CLI and kubectl on Linux/macOS.
  • Where possible, avoid PowerShell-specific terminology in general guidance, or clarify its platform limitations.
GitHub Create Pull Request
Aks Develop on Azure Kubernetes Service (AKS) with Helm ...ure-aks-docs/blob/main/articles/aks/quickstart-helm.md
Medium Priority View Details →
Scanned: 2026-03-02 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides parallel Azure CLI and Azure PowerShell instructions throughout, but does not show explicit Linux/macOS shell examples for Azure CLI usage. Azure PowerShell is featured equally alongside Azure CLI, despite PowerShell being primarily a Windows-centric tool (though available cross-platform). Azure CLI examples are not explicitly shown as Bash or Linux/macOS shell commands, and PowerShell is given equal prominence, which may create friction for Linux/macOS users who typically use Bash and Azure CLI.
Recommendations
  • Clarify that Azure CLI examples are intended for Bash (Linux/macOS) and Windows Command Prompt users.
  • Add explicit Bash shell examples for Azure CLI commands, including any relevant environment variable usage or command syntax differences for Linux/macOS.
  • Consider reducing the prominence of Azure PowerShell unless there are Windows-specific tasks, or move PowerShell instructions to a secondary section or appendix.
  • Add notes about cross-platform compatibility for Azure CLI and Helm commands, and highlight any OS-specific prerequisites or installation steps.
  • Ensure that all instructions (especially for Helm, kubectl, git, etc.) are shown in a way that is clear for Linux/macOS users, including references to package managers (apt, yum, brew) for installation.
GitHub Create Pull Request
Aks Install Dapr Extension for Azure Kubernetes Service (AKS) ...softDocs/azure-aks-docs/blob/main/articles/aks/dapr.md
Medium Priority View Details →
Scanned: 2026-03-01 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 and focuses on Azure CLI and Bicep, which are cross-platform tools. However, in the 'List the CRDs in your cluster' section, only a Windows-specific example using 'kubectl get crds | findstr dapr.io' (with PowerShell syntax) is provided. There is no equivalent Linux/macOS example (e.g., using 'grep'), and the use of 'findstr' is a Windows tool, creating friction for non-Windows users.
Recommendations
  • Add a Linux/macOS example for listing CRDs, such as 'kubectl get crds | grep dapr.io'.
  • Mention that 'findstr' is Windows-specific and provide 'grep' as the cross-platform alternative.
  • Review future documentation sections to ensure CLI examples are cross-platform or alternatives are provided.
GitHub Create Pull Request
Aks Install Dapr Extension for Azure Kubernetes Service (AKS) ...softDocs/azure-aks-docs/blob/main/articles/aks/dapr.md
Medium Priority View Details →
Scanned: 2026-02-28 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, which are supported on Windows, Linux, and macOS. However, the only example for listing Dapr CRDs uses a Windows-specific pattern ('kubectl get crds | findstr dapr.io'), and the use of PowerShell-style piping ('| findstr') is shown without a Linux/macOS equivalent (e.g., 'grep'). Additionally, this Windows example appears before any mention of Linux alternatives, which may cause friction for non-Windows users.
Recommendations
  • Provide both Windows and Linux/macOS examples for commands involving shell utilities, such as listing CRDs (e.g., 'kubectl get crds | grep dapr.io' for Linux/macOS).
  • Explicitly state that Azure CLI and Bicep commands are cross-platform and supported on Windows, Linux, and macOS.
  • Where shell commands are given, use tabs or callouts to distinguish between Windows and Linux/macOS usage.
  • Review for other places where Windows-specific syntax or tools (like 'findstr') are used and add Linux/macOS equivalents.
GitHub Create Pull Request
Aks Kubernetes on Azure tutorial - Create an Azure Kubernetes Service (AKS) cluster ...ain/articles/aks/tutorial-kubernetes-deploy-cluster.md
Medium Priority View Details →
Scanned: 2026-02-27 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides parallel examples for Azure CLI, Azure PowerShell, and Azure Developer CLI. However, PowerShell examples are prominent throughout, and PowerShell is a Windows-centric tool. Azure CLI (which is cross-platform) is included, but PowerShell is given equal billing and sometimes appears before CLI in sections. There are no explicit Linux/macOS-specific instructions or examples, and no mention of Linux shell patterns (e.g., Bash scripting, environment variables for Linux, or package managers like apt/yum/brew for installing tools). The install instructions for kubectl rely on Azure CLI/PowerShell commands, omitting native Linux/macOS install methods.
Recommendations
  • Add explicit Linux/macOS install instructions for kubectl (e.g., using curl, apt, brew, or native package managers).
  • Clarify that Azure CLI commands work on Linux/macOS and Windows, and provide Bash shell examples where appropriate.
  • Consider mentioning that PowerShell Core is cross-platform, but most users on Linux/macOS will use Bash or Zsh.
  • Add a section or callout for Linux/macOS users, highlighting any differences or considerations (e.g., SSH key generation, environment variable syntax).
  • When referencing installation of Azure CLI, link to platform-specific instructions (Windows, Linux, macOS).
GitHub Create Pull Request
Aks Install Dapr Extension for Azure Kubernetes Service (AKS) ...softDocs/azure-aks-docs/blob/main/articles/aks/dapr.md
Medium Priority View Details →
Scanned: 2026-02-26 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is generally cross-platform, focusing on Azure CLI and Bicep, which are available on Windows, Linux, and macOS. However, there is a notable bias in the CRD cleanup section, where the only example for listing Dapr CRDs uses Windows-specific PowerShell syntax (`findstr`). No equivalent Linux/macOS example (e.g., using `grep`) is provided. This could cause confusion or friction for non-Windows users.
Recommendations
  • Provide both Windows (findstr) and Linux/macOS (grep) examples when filtering kubectl output, e.g., `kubectl get crds | grep dapr.io`.
  • Explicitly state that Azure CLI and Bicep commands are cross-platform, and link to installation guides for Linux/macOS if not already present.
  • Review for any other subtle Windows-centric assumptions (e.g., environment variable syntax, file paths) and ensure parity.
GitHub Create Pull Request
Aks Access Kubernetes Resources using the Azure Portal ...e-aks-docs/blob/main/articles/aks/kubernetes-portal.md
Medium Priority View Details →
Scanned: 2026-02-22 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 the PowerShell example is presented immediately after the CLI example and is given equal prominence. There are no Linux-specific examples (e.g., Bash or native Linux commands) for retrieving the public IP address, and the PowerShell example is unnecessary for Linux/macOS users. The rest of the documentation is portal-centric and platform-neutral, but the troubleshooting section could create friction for Linux/macOS users.
Recommendations
  • Add a Bash-only example for retrieving the public IP address (e.g., `curl ifconfig.me` or `curl ipinfo.io/ip`) in the troubleshooting section.
  • Clarify that Azure PowerShell examples are for Windows users, and Azure CLI is cross-platform.
  • Consider showing Azure CLI examples first, and PowerShell examples in a separate, clearly marked Windows-only tab.
  • Explicitly mention that Azure CLI works on Linux/macOS/Windows, while Azure PowerShell is Windows-centric.
GitHub Create Pull Request
Aks About the Agentic CLI for Azure Kubernetes Service (AKS) ...blob/main/articles/aks/agentic-cli-for-aks-overview.md
Medium Priority View Details →
Scanned: 2026-02-21 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation for the Agentic CLI for AKS does not explicitly mention Windows, but it refers to 'local machine' usage and prerequisites such as Docker and Azure CLI without clarifying Linux/macOS compatibility or providing Linux/macOS-specific instructions. There are no examples or guidance for Linux/macOS users, and the phrasing may imply a Windows-centric perspective by default.
Recommendations
  • Explicitly state that the Agentic CLI for AKS supports Windows, Linux, and macOS platforms.
  • Provide installation and usage instructions for Linux/macOS, including any differences in Docker or Azure CLI setup.
  • Add troubleshooting tips for Linux/macOS environments (e.g., common issues with Docker on Linux, Azure CLI authentication differences).
  • Include example commands or screenshots from Linux/macOS terminals alongside Windows examples if applicable.
GitHub Create Pull Request
Aks Kubernetes on Azure tutorial - Create an Azure Kubernetes Service (AKS) cluster ...ain/articles/aks/tutorial-kubernetes-deploy-cluster.md
Medium Priority View Details →
Scanned: 2026-02-21 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides parallel examples for Azure CLI, Azure PowerShell, and Azure Developer CLI, but PowerShell is featured prominently, and the use of PowerShell cmdlets (e.g., Install-AzAksCliTool, New-AzAksCluster, Import-AzAksCredential) may implicitly favor Windows users. Azure CLI examples are present, but PowerShell is given equal weight, which is uncommon for Linux/macOS users. There are no explicit Linux/macOS examples (e.g., Bash shell, native package installation for kubectl), and PowerShell is mentioned before Linux-native tools in several places.
Recommendations
  • Add explicit Bash/Linux/macOS instructions for installing kubectl (e.g., using curl or package managers like apt, brew, yum).
  • Clarify that Azure CLI commands work on Linux/macOS and Windows equally, and provide Bash shell examples where relevant.
  • De-emphasize PowerShell for cross-platform tasks, or clearly mark PowerShell sections as Windows-specific.
  • Include troubleshooting tips for Linux/macOS users (e.g., SSH key generation, environment variable setup).
  • Consider adding a section on using kubectl and Azure CLI in native Linux/macOS environments outside Cloud Shell.
GitHub Create Pull Request
Aks Install Dapr Extension for Azure Kubernetes Service (AKS) ...softDocs/azure-aks-docs/blob/main/articles/aks/dapr.md
Medium Priority View Details →
Scanned: 2026-02-20 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 cross-platform, focusing on Azure CLI and Bicep, which are available on Windows, Linux, and macOS. However, there is a notable instance where a Windows-specific command (`findstr`) is used with `kubectl` to filter CRDs, and this is presented without a Linux/macOS equivalent. Additionally, the use of PowerShell-style variable assignment (`$MY_RESOURCE_GROUP`) in CLI examples may be confusing for Bash users. No explicit Linux or macOS examples are provided for these cases.
Recommendations
  • For the `kubectl get crds | findstr dapr.io` example, provide a cross-platform alternative, such as `kubectl get crds | grep dapr.io` for Linux/macOS.
  • When showing variable assignment for Azure CLI commands, include both PowerShell (`$VAR=...`) and Bash (`VAR=...`) syntax, or clarify which shell is being used.
  • Review all CLI examples to ensure they are shell-agnostic or provide alternatives for both Windows and Linux/macOS users.
  • Consider adding a short note at the start of the CLI sections indicating that the Azure CLI and Bicep commands work on all major platforms, and point to shell-specific guidance if needed.
GitHub Create Pull Request
Aks Kubernetes on Azure tutorial - Create an Azure Kubernetes Service (AKS) cluster ...ain/articles/aks/tutorial-kubernetes-deploy-cluster.md
Medium Priority View Details →
Scanned: 2026-02-20 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The tutorial provides parallel instructions for Azure CLI, Azure PowerShell, and Azure Developer CLI, but PowerShell examples and terminology are prominent throughout. PowerShell is a Windows-centric tool, and its inclusion alongside Azure CLI may signal a Windows bias. Additionally, PowerShell sections are consistently presented before Azure Developer CLI, and sometimes Azure CLI instructions reference Bash/Cloud Shell but do not explicitly mention Linux/macOS environments or alternatives. There are no explicit Linux/macOS examples or shell-specific guidance for those platforms.
Recommendations
  • Add explicit guidance for Linux/macOS users, such as referencing Bash or Zsh environments and confirming compatibility of Azure CLI commands.
  • Clarify that Azure CLI commands work on Windows, Linux, and macOS, and provide links to platform-specific installation instructions.
  • Consider including example commands for Bash (Linux/macOS) where appropriate, especially for environment variable usage and SSH key management.
  • Balance PowerShell and Azure CLI coverage by mentioning that PowerShell is primarily for Windows users, while Azure CLI is cross-platform.
  • Where possible, provide parity in examples for Linux/macOS users, such as using native shell commands for tasks like SSH key generation.
GitHub Create Pull Request
Aks Access Kubernetes Resources using the Azure Portal ...e-aks-docs/blob/main/articles/aks/kubernetes-portal.md
Medium Priority View Details →
Scanned: 2026-02-19 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for managing AKS authorized IP ranges, but the PowerShell example is given equal prominence and is not clearly marked as Windows-only. The CLI example uses 'dig', which is not available by default on Windows, but no explicit Linux/macOS guidance is provided. The PowerShell example is shown immediately after the CLI example, and neither is prioritized for Linux/macOS users. There are no explicit Linux/macOS instructions or troubleshooting tips, and the documentation does not clarify which commands are platform-specific.
Recommendations
  • Clearly indicate that Azure PowerShell examples are intended for Windows users, and Azure CLI examples are cross-platform.
  • For the Azure CLI example, provide alternative commands for retrieving the public IP address on Windows (e.g., using 'curl' or 'Invoke-RestMethod') and Linux/macOS (e.g., 'curl ifconfig.me').
  • Add a note or tab for Linux/macOS users, specifying which commands are available by default and how to install missing tools (e.g., 'dig').
  • Consider showing Azure CLI examples first, as they are cross-platform, and PowerShell examples only for Windows users.
  • Add troubleshooting tips for Linux/macOS users if certain commands fail due to missing dependencies.
GitHub Create Pull Request
Aks About the Agentic CLI for Azure Kubernetes Service (AKS) ...s/blob/main/articles/aks/cli-agent-for-aks-overview.md
Medium Priority View Details →
Scanned: 2026-02-18 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation describes the Agentic CLI for AKS in a platform-neutral manner but subtly exhibits Windows bias by referencing 'local Azure CLI credentials' and 'Docker' without clarifying Linux/macOS support. There are no explicit Linux/macOS examples or instructions, and prerequisites are listed generically (e.g., 'Docker'), which may imply Windows as the default environment. The absence of Linux/macOS-specific guidance or troubleshooting creates friction for non-Windows users.
Recommendations
  • Explicitly state that the Agentic CLI for AKS supports Windows, Linux, and macOS platforms.
  • Provide installation and usage examples for Linux and macOS, including any platform-specific prerequisites or troubleshooting tips.
  • Clarify that Docker and Azure CLI are cross-platform tools, and link to their Linux/macOS installation guides.
  • Add a section or table highlighting any differences or considerations 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
Medium Priority View Details →
Scanned: 2026-02-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides parallel Azure CLI and Azure PowerShell instructions for all Azure-related steps, but PowerShell is featured equally alongside CLI. There are no Windows-only tools or patterns, but PowerShell is a Windows-centric tool and is presented as a primary option. The document does not provide Linux-specific shell examples (e.g., Bash for Azure CLI) or highlight Linux/macOS parity. Azure CLI is cross-platform, but PowerShell is not as widely used on Linux/macOS. The ordering of examples is neutral, but the presence of PowerShell throughout may create friction for Linux/macOS users.
Recommendations
  • Clarify that Azure CLI is the recommended cross-platform tool for Linux/macOS users.
  • Consider adding explicit Bash shell examples for Azure CLI commands to reinforce Linux/macOS parity.
  • Mention that Azure PowerShell is primarily for Windows users, and provide guidance for Linux/macOS users to use Azure CLI.
  • Add notes or callouts where PowerShell is used, indicating alternative approaches for Linux/macOS users.
  • Ensure that all steps can be completed using Azure CLI alone, and highlight this in the prerequisites.
GitHub Create Pull Request
Aks Kubernetes on Azure tutorial - Upgrade an Azure Kubernetes Service (AKS) cluster ...in/articles/aks/tutorial-kubernetes-upgrade-cluster.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides parallel examples for Azure CLI, Azure PowerShell, and Azure portal for all major tasks. However, Azure PowerShell is featured equally alongside Azure CLI, which is more cross-platform, and PowerShell is primarily a Windows-centric tool (though available on Linux/macOS). In some sections, PowerShell examples are given before Azure CLI, and PowerShell-specific installation instructions are included. There are no Linux-specific shell examples (e.g., Bash), nor explicit mention of Linux/macOS command-line environments. The documentation does not use Windows-only tools, but the prominence of PowerShell may create friction for Linux/macOS users.
Recommendations
  • Clearly indicate that Azure CLI is recommended for Linux/macOS users, and that PowerShell is optional.
  • Add brief notes clarifying that Azure CLI commands work on all platforms, while PowerShell is more common on Windows.
  • Consider including Bash shell examples or notes for Linux/macOS users, especially for common tasks.
  • Reorder examples to show Azure CLI first, followed by PowerShell, to reduce Windows-first bias.
  • Add a short section or callout for Linux/macOS users, linking to Azure CLI installation and usage guidance.
GitHub Create Pull Request
Aks Develop on Azure Kubernetes Service (AKS) with Helm ...ure-aks-docs/blob/main/articles/aks/quickstart-helm.md
Medium Priority View Details →
Scanned: 2026-02-05 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 tasks, with PowerShell examples given equal prominence. However, there are no Linux-specific instructions or examples for using native Linux tools or shell environments. The use of PowerShell is highlighted as a primary method alongside Azure CLI, which may create friction for Linux/macOS users who do not use PowerShell.
Recommendations
  • Clarify that Azure PowerShell examples are intended for Windows users and that Azure CLI is cross-platform.
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and recommend CLI for non-Windows environments.
  • Consider listing Azure CLI examples before PowerShell examples, or defaulting to CLI in mainline instructions, with PowerShell as an alternative.
  • Add notes or links for Linux/macOS users regarding installation and usage of Azure CLI and kubectl in their environments.
  • Remove or de-emphasize PowerShell examples in sections where CLI is sufficient and more broadly applicable.
GitHub Create Pull Request
Aks Upgrade the Azure Kubernetes Service (AKS) cluster control plane ...cs/blob/main/articles/aks/upgrade-aks-control-plane.md
Medium Priority View Details →
Scanned: 2026-01-14 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 upgrade operations, with Azure PowerShell (a Windows-centric tool) given equal prominence and detail as Azure CLI. In some sections, PowerShell examples are presented before or alongside CLI examples, and there is explicit mention of installing/upgrading Azure PowerShell. However, there are no Linux-specific shell examples (e.g., bash, zsh), and the documentation does not mention Linux/macOS compatibility for Azure CLI commands, nor does it clarify that PowerShell Core is cross-platform. The bias is moderate, as Linux/macOS users can complete all tasks using Azure CLI, but the equal focus on PowerShell may create friction or confusion for non-Windows users.
Recommendations
  • Clarify that Azure CLI is fully supported on Linux and macOS, and recommend it as the primary tool for cross-platform scenarios.
  • Note that Azure PowerShell is available cross-platform via PowerShell Core, but is most commonly used on Windows.
  • Consider presenting Azure CLI examples first, as it is the default for Linux/macOS users.
  • Add a brief note for Linux/macOS users about installing Azure CLI and running commands in bash/zsh.
  • Remove unnecessary emphasis on PowerShell unless there are Windows-specific steps.
GitHub Create Pull Request
Aks API Server Authorized IP Ranges in Azure Kubernetes Service (AKS) ...b/main/articles/aks/api-server-authorized-ip-ranges.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides both Azure CLI (cross-platform) and Azure PowerShell (Windows-centric) instructions for all major tasks, but PowerShell examples and Windows-specific tooling are given equal or greater prominence. In the 'Find your IP address' section, Windows-specific methods (PowerShell command and Microsoft support link) are mentioned, while Linux/macOS alternatives are less visible or not explicitly described. The use of PowerShell and references to Windows tools may create friction for Linux/macOS users, though CLI examples are present throughout.
Recommendations
  • For every PowerShell example, ensure a Linux/macOS shell equivalent is provided (e.g., bash, curl, dig).
  • In the 'Find your IP address' section, add explicit Linux/macOS commands (e.g., curl ifconfig.me, dig, or ip addr) and mention them before or alongside Windows methods.
  • Clarify that Azure CLI commands work on all platforms and highlight platform-agnostic approaches.
  • Review all sections for implicit Windows-first assumptions and rephrase to be platform-neutral where possible.
GitHub Create Pull Request
← Previous Page 1 of 25 Next →