Aks

529
Total Pages
422
Linux-Friendly Pages
107
Pages with Bias
20.2%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

301 issues found
Showing 101-125 of 301 flagged pages
Aks Certificate Rotation in Azure Kubernetes Service (AKS) ...ks-docs/blob/main/articles/aks/certificate-rotation.md
Low Priority View Details →
Scanned: 2026-01-13 23:55
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation provides both Linux and Windows file paths when verifying TLS Bootstrapping, but Windows paths are mentioned alongside Linux, and Windows node examples are included in output samples. However, the majority of command-line examples use Bash, Azure CLI, and kubectl, which are cross-platform and default to Linux conventions. There are no PowerShell-specific commands or Windows-only instructions, but Windows nodes are referenced in some output and file path examples.
Recommendations
  • Ensure that every example referencing file paths or node types provides both Linux and Windows equivalents, with equal clarity.
  • Explicitly state which commands are cross-platform and provide PowerShell or Windows Command Prompt alternatives for Azure CLI and kubectl commands where relevant.
  • When showing output samples, include both Linux and Windows node examples, or clarify any differences in output or behavior.
  • Consider alternating the order of Linux and Windows examples, or grouping them together, to avoid implicit prioritization.
GitHub Create Pull Request
Aks Concepts - Storage in Azure Kubernetes Services (AKS) ...re-aks-docs/blob/main/articles/aks/concepts-storage.md
Low Priority View Details →
Scanned: 2026-01-13 23:55
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows Example Present Windows Linux Difference Mentioned
Summary
The documentation is largely platform-neutral, focusing on AKS storage concepts applicable to both Linux and Windows nodes. However, there is a minor Windows bias in the 'Persistent volume claims' section, where a specific example is given for mounting volumes in Windows containers, while the main example is for Linux. Additionally, the documentation notes that persistent volumes cannot be shared between Windows and Linux pods due to filesystem differences, but does not elaborate on Windows-specific limitations or provide equivalent Linux details in that context.
Recommendations
  • Provide parallel Linux and Windows examples for volume mounting, clearly labeling each.
  • Explicitly note any platform-specific limitations or behaviors for both Windows and Linux, not just Windows.
  • Where differences exist (e.g., persistent volumes not shared across OS types), link to further documentation for both Windows and Linux scenarios.
  • Ensure that examples and instructions are presented in a balanced manner, alternating or grouping by OS where relevant.
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-01-13 23:55
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits minor Windows bias by referencing a Windows-specific error ('ImportError: DLL load failed while importing win32file') and suggesting to 'reinstall the Azure CLI client' as a solution, without providing equivalent troubleshooting steps for Linux/macOS users. No PowerShell-heavy or Windows-first example ordering is present, but the lack of Linux/macOS-specific guidance may create friction for non-Windows users encountering similar issues.
Recommendations
  • Add troubleshooting steps for Linux/macOS environments, especially for errors analogous to 'DLL load failed' (e.g., missing shared libraries, permissions issues).
  • Clarify whether the 'reinstall Azure CLI client' step applies to all platforms, and provide platform-specific instructions if needed.
  • Include examples or notes for common Linux/macOS errors that may occur during CLI installation or usage.
  • Explicitly state platform applicability for each troubleshooting step.
GitHub Create Pull Request
Aks Concepts - Access and identity in Azure Kubernetes Services (AKS) ...e-aks-docs/blob/main/articles/aks/concepts-identity.md
Low Priority View Details →
Scanned: 2026-01-13 23:55
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation consistently presents Azure CLI and kubectl workflows, but command-line examples and authentication flows are described generically without explicit OS-specific instructions. However, the only workflow described for accessing AKS clusters is via the Azure CLI ('az login', 'az aks get-credentials'), which is most commonly used on Windows and macOS, but on Linux as well. There is no mention of Linux-specific authentication nuances, nor are alternative Linux-native tools or shell patterns (e.g., bash scripting, environment variables) discussed. The documentation does not provide explicit Linux/macOS command examples or address platform-specific issues (such as browser-based authentication differences, credential storage locations, or CLI installation guidance for Linux). Windows bias is subtle: Windows-centric tools (Azure CLI, browser-based login) are assumed, and no Linux-first or parity guidance is given.
Recommendations
  • Add explicit instructions or examples for Linux and macOS users, including installation steps for Azure CLI and kubectl on those platforms.
  • Discuss platform-specific nuances, such as browser-based authentication differences, credential storage locations (e.g., ~/.kube/config on Linux/macOS), and troubleshooting tips for Linux environments.
  • Provide bash/zsh shell command examples alongside generic CLI instructions.
  • Include links or references to Linux/macOS-specific documentation for Azure CLI and kubectl usage.
  • Clarify that the described workflows are cross-platform, and note any differences in user experience or requirements.
GitHub Create Pull Request
Aks Concepts - IP address planning in Azure Kubernetes Service (AKS) ...n/articles/aks/concepts-network-ip-address-planning.md
Low Priority View Details →
Scanned: 2026-01-13 23:55
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation page does not show explicit Windows bias in terms of examples or tooling (no PowerShell, Windows-only commands, or tools are mentioned). However, when listing methods for configuring maximum pods per node, the Azure CLI is mentioned first, followed by Azure Resource Manager templates and the Azure portal. While Azure CLI is cross-platform, the ordering could be interpreted as a subtle 'windows_first' bias, as it is common for Microsoft documentation to prioritize CLI and portal workflows familiar to Windows users.
Recommendations
  • Explicitly state that Azure CLI is cross-platform and works on Linux/macOS as well as Windows.
  • If relevant, provide examples or notes for Linux/macOS users (e.g., shell syntax differences, installation instructions for Azure CLI on Linux/macOS).
  • Ensure that any future command-line examples include both Bash and PowerShell syntax if there are differences.
  • Consider rotating the order of listed methods or clarifying that all are equally supported on all platforms.
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-01-13 23:55
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, covering both Windows and Linux platforms. However, there is a notable emphasis on Azure PowerShell, which is traditionally more common on Windows, and PowerShell instructions are presented before CLI instructions. The PowerShell section includes detailed instructions and troubleshooting for installing/upgrading PowerShell on Windows, macOS, and Linux, but the overall flow and examples may feel Windows-centric due to the prominence of PowerShell.
Recommendations
  • Ensure Azure CLI examples are presented before or alongside PowerShell examples, as CLI is more universally used across platforms.
  • Add explicit notes or examples for Linux/macOS users, such as shell commands or environment setup tips.
  • Clarify that both Azure CLI and PowerShell are fully supported on Linux/macOS, and link to relevant installation guides.
  • Consider balancing the depth of instructions between PowerShell and CLI sections.
GitHub Create Pull Request
Aks Configure Azure CNI Pod Subnet - Dynamic IP Allocation and enhanced subnet support ...icles/aks/configure-azure-cni-dynamic-ip-allocation.md
Low Priority View Details →
Scanned: 2026-01-13 23:55
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation exclusively uses Azure CLI and Azure Portal workflows, which are cross-platform but heavily oriented toward Azure's ecosystem. There are no references to Windows-specific tools like PowerShell, nor are there explicit Windows-only commands. However, the documentation omits any mention of Linux/macOS-specific nuances, such as shell differences, package managers, or alternative workflows. All command-line examples use Bash syntax, which is more common on Linux/macOS, but Azure CLI is available on all platforms. There is a minor bias in that monitoring instructions reference the Azure Portal (a web interface) and do not mention command-line alternatives that Linux users might prefer.
Recommendations
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows.
  • Provide notes or links for installing Azure CLI on Linux/macOS.
  • Include alternative instructions for monitoring IP subnet usage using command-line tools or kubectl, not just the Azure Portal.
  • Clarify any platform-specific requirements or differences (e.g., SSH key generation, file paths).
GitHub Create Pull Request
Aks Limit access to kubeconfig in Azure Kubernetes Service (AKS) ...cs/blob/main/articles/aks/control-kubeconfig-access.md
Low Priority View Details →
Scanned: 2026-01-13 23:55
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation references Windows-specific tools and patterns before their Linux equivalents, notably by mentioning Azure PowerShell and the Azure portal as alternatives to Azure CLI for cluster creation. However, all command-line examples use Azure CLI and bash-style syntax, which is cross-platform. There are no explicit Windows-only commands or examples, but the initial mention of PowerShell and the Azure portal as primary alternatives may suggest a Windows-first perspective.
Recommendations
  • List Linux/macOS options (Azure CLI) before Windows-specific ones (PowerShell) when suggesting tools for cluster creation.
  • Clarify that all command-line examples are cross-platform and can be run on Linux, macOS, and Windows (with WSL or bash).
  • Provide explicit notes or examples for Linux/macOS users where command syntax or environment may differ (e.g., environment variables, shell differences).
  • Consider adding a section or note about using Azure CLI in PowerShell or Windows Command Prompt, if relevant, to ensure parity.
GitHub Create Pull Request
Aks Customize CoreDNS for Azure Kubernetes Service (AKS) ...zure-aks-docs/blob/main/articles/aks/coredns-custom.md
Low Priority View Details →
Scanned: 2026-01-13 23:55
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page lists Windows-oriented tools (Azure PowerShell) before Linux-friendly options (Azure CLI) when describing how to create an AKS cluster. While the main instructions use cross-platform kubectl commands and YAML, the prerequisites section subtly prioritizes Windows by mentioning Azure PowerShell before Azure CLI, and by linking to a PowerShell-specific quickstart. No Linux-specific examples or troubleshooting are provided, and there is no mention of Linux/macOS shell environments or considerations.
Recommendations
  • List Azure CLI before Azure PowerShell in prerequisites and quickstart links, as CLI is cross-platform and more widely used on Linux/macOS.
  • Explicitly state that all kubectl commands work on Linux, macOS, and Windows, and provide any necessary shell syntax notes if applicable.
  • Add troubleshooting or configuration notes relevant to Linux/macOS environments, such as file permissions or line endings.
  • Include links to Linux/macOS-specific AKS setup guides if available.
GitHub Create Pull Request
Aks Create Node Pools in Azure Kubernetes Service (AKS) ...e-aks-docs/blob/main/articles/aks/create-node-pools.md
Low Priority View Details →
Scanned: 2026-01-13 23:55
Reviewed by: LLM Analysis
Issues: 5 bias types
Detected Bias Types
🔧 Windows Tools Windows Examples Windows Nodepool Sections Windows Late Windows Segregation
Summary
The documentation provides both Linux and Windows node pool instructions for AKS, but Linux is consistently presented first and in greater detail. Windows node pool creation is covered in dedicated sections and tabs, but only after all Linux options are described. There are no PowerShell-specific examples, and all CLI commands use Azure CLI, which is cross-platform. However, Windows node pool instructions are segregated and appear later, which may subtly reinforce a Linux-first workflow. There is no evidence of missing Windows examples or exclusive use of Windows tools, but the ordering and structure reflect a mild bias toward Linux.
Recommendations
  • Present Windows node pool creation options alongside Linux in summary tables or introductory sections, rather than only in dedicated, later sections.
  • Add a brief overview at the start clarifying that both Linux and Windows node pools are supported, and highlight any requirements for each.
  • Where multiple OS options are shown, consider alternating the order or grouping them together to avoid reinforcing a Linux-first perception.
  • Ensure that Windows node pool instructions are as detailed and discoverable as Linux ones, possibly with cross-references.
  • If PowerShell is a common tool for Windows users, consider including PowerShell examples or linking to them.
GitHub Create Pull Request
Aks Azure Key Vault provider for Secrets Store CSI Driver for AKS configuration and troubleshooting options ...rticles/aks/csi-secrets-store-configuration-options.md
Low Priority View Details →
Scanned: 2026-01-13 23:55
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Windows Specific Example
Summary
The documentation is largely cross-platform, focusing on Kubernetes and Azure CLI commands, which work on both Linux and Windows. However, there are minor instances of Windows bias: Windows-specific YAML and commands are mentioned (e.g., deleting AKV provider pods from Windows nodes), and in the migration section, Windows node instructions are given after Linux but are present. No PowerShell or Windows-only CLI examples are present, and most instructions use bash or YAML, which are standard for Linux/macOS. There is a slight tendency to mention Linux first, but Windows is not neglected.
Recommendations
  • Ensure that all Windows-specific instructions are paired with equivalent Linux/macOS instructions and vice versa.
  • Clarify in each example which platforms the commands apply to, especially where Windows-specific YAML or deployment files are referenced.
  • Consider adding explicit notes about cross-platform compatibility for Azure CLI commands.
  • If there are platform-specific troubleshooting steps, provide parity for both Windows and Linux nodes.
  • Where possible, provide PowerShell examples for Windows users alongside bash examples for Linux/macOS.
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-01-13 23:55
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates minor Windows bias primarily in the troubleshooting and CRD cleanup sections. While the main installation and management instructions use Azure CLI and Bicep (both cross-platform), the example for listing Dapr CRDs uses Windows-specific tooling (kubectl piped to findstr), and there are no Linux/macOS equivalents provided. Additionally, the use of Azure CLI is sometimes associated with Windows environments, though it is available cross-platform.
Recommendations
  • Provide Linux/macOS equivalents for commands that use Windows-specific tools, such as replacing 'kubectl get crds | findstr dapr.io' with 'kubectl get crds | grep dapr.io'.
  • Explicitly state that Azure CLI and Bicep are cross-platform and provide installation links or instructions for Linux/macOS users.
  • When showing command-line examples, present both Windows and Linux/macOS variants where output filtering or scripting differs.
  • Avoid using PowerShell or Windows command-line tools exclusively in examples unless necessary, and always offer alternatives.
GitHub Create Pull Request
Aks Schedule and Deploy Batch Jobs with Kueue on Azure Kubernetes Service (AKS) ...blob/main/articles/aks/deploy-batch-jobs-with-kueue.md
Low Priority View Details →
Scanned: 2026-01-13 23:55
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits mild Windows bias in the prerequisites section, where Windows-specific tools (Azure PowerShell) are mentioned alongside Azure CLI and portal, and the PowerShell option is listed before Linux-native alternatives. However, all command-line examples throughout the main guide use bash syntax and standard Kubernetes tools (kubectl, Helm), which are cross-platform and work on Linux, macOS, and Windows (with WSL or native bash). No PowerShell-specific commands or Windows-only tooling are used in the main workflow, and Linux users can follow all steps without modification.
Recommendations
  • List Azure CLI before Azure PowerShell in prerequisites to avoid Windows-first impression.
  • Explicitly mention that all CLI commands work on Linux, macOS, and Windows (with WSL or bash).
  • Provide a brief note or link for Windows users on how to run bash commands (e.g., using WSL, Git Bash, or Azure Cloud Shell).
  • Consider removing or de-emphasizing Azure PowerShell unless there is a compelling reason for its inclusion.
GitHub Create Pull Request
Aks Delete an Azure Kubernetes Service (AKS) cluster ...zure-aks-docs/blob/main/articles/aks/delete-cluster.md
Low Priority View Details →
Scanned: 2026-01-13 23:55
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 deleting an AKS cluster, with PowerShell being a Windows-centric tool. The PowerShell example is given equal prominence to the CLI example, and there is no mention of Linux/macOS-specific shell nuances or alternative Linux-native tools. The Azure CLI example is cross-platform, but the inclusion of PowerShell may suggest a Windows bias, especially since no Bash-specific or Linux/macOS terminal guidance is provided beyond the CLI example.
Recommendations
  • Clarify that Azure CLI commands work on Windows, Linux, and macOS, and explicitly mention Bash or shell usage for Linux/macOS users.
  • If PowerShell is included, consider adding a note about PowerShell Core being available on Linux/macOS, or provide Bash-specific examples for Linux users.
  • Add troubleshooting notes or links for Linux/macOS users regarding environment variable usage and shell differences.
  • Ensure that examples and instructions do not assume a Windows environment unless necessary.
GitHub Create Pull Request
Aks Customer intent: "As a cloud administrator, I want to log in to Azure using the CLI with a workaround, so that I can securely access my subscription and manage resources without issues." ...cs/blob/main/articles/aks/includes/azd/azd-login-ts.md
Low Priority View Details →
Scanned: 2026-01-13 23:55
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows Only Announcement
Summary
The documentation is generally cross-platform, using Azure CLI and curl, which work on Windows, Linux, and macOS. However, there is a notable Windows-only announcement about Azure CLI collecting feedback for the Web Account Manager (WAM) broker, including opt-in instructions that apply only to Windows users. No equivalent Linux/macOS-specific tools or announcements are provided.
Recommendations
  • Add a note clarifying that the WAM broker is Windows-specific and provide information about authentication brokers or best practices for Linux/macOS users, if available.
  • Include any Linux/macOS-specific authentication improvements or feedback channels, if they exist.
  • Ensure parity in announcements and troubleshooting tips for all platforms.
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-01-13 23:55
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates mild Windows bias by referencing Azure PowerShell and Windows-specific tools alongside Azure CLI, and by listing Windows/PowerShell options before Linux equivalents in several places. For example, cluster creation options mention Azure PowerShell before the Azure portal, and PowerShell cmdlets are referenced for subnet listing. However, all actionable examples use Azure CLI and kubectl, which are cross-platform, and there are no critical tasks that are Windows-only.
Recommendations
  • List Linux-friendly tools (Azure CLI, kubectl) before Windows/PowerShell options when presenting alternatives.
  • Where PowerShell cmdlets are mentioned, provide equivalent Azure CLI commands and examples for Linux/macOS users.
  • Clarify that Azure CLI and kubectl are cross-platform and preferred for Linux/macOS.
  • Consider removing or de-emphasizing PowerShell references unless a feature is truly Windows-only.
GitHub Create Pull Request
Aks Enable Federal Information Process Standard (FIPS) for Azure Kubernetes Service (AKS) node pools ...e-aks-docs/blob/main/articles/aks/enable-fips-nodes.md
Low Priority View Details →
Scanned: 2026-01-13 23:55
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows Example Windows First
Summary
The documentation provides both Linux and Windows instructions for enabling FIPS on AKS node pools. However, there is a slight bias toward Windows in the verification steps for Windows node pools, which require use of RDP and the Windows Registry Editor, while Linux verification uses standard CLI commands. Windows-specific tools (RDP, regedit) are mentioned exclusively for Windows, and the Windows verification process is described in more detail than the Linux equivalent. The order of presentation is Linux first, but Windows instructions are given parity.
Recommendations
  • For Windows node pool verification, suggest PowerShell or command-line methods to check FIPS status in addition to regedit, to provide parity with Linux CLI verification.
  • Include explicit mention of how to verify FIPS status on Windows nodes via command line (e.g., querying the registry via PowerShell), not just via GUI tools.
  • Ensure that troubleshooting and verification steps for both OS types use comparable tooling (CLI where possible) and detail.
  • Consider adding a note for macOS users if relevant, or clarifying that AKS node pools do not support macOS.
  • Maintain Linux-first ordering for examples and instructions, as AKS clusters are typically Linux-primary.
GitHub Create Pull Request
Aks Deploy a Java application with Open Liberty/WebSphere Liberty on an Azure Kubernetes Service (AKS) cluster ...lob/main/articles/aks/howto-deploy-java-liberty-app.md
Low Priority View Details →
Scanned: 2026-01-13 23:55
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples throughout, but consistently lists Bash (Linux/macOS) instructions first, followed by PowerShell (Windows). However, the PowerShell examples are comprehensive and not limited to basic commands; they include full environment variable usage and deployment steps. There is no evidence of exclusive use of Windows tools, nor are Windows-specific patterns or tools mentioned before their Linux equivalents. The prerequisites explicitly mention Unix-like OS (Ubuntu, Azure Linux, macOS, WSL) before Windows, and the Azure CLI is used as the primary tool, which is cross-platform. All critical tasks (deployment, build, test, cleanup) are covered for both platforms.
Recommendations
  • Continue listing Bash examples first to reinforce Linux parity.
  • Consider adding a short note at the start clarifying that all steps are equally supported on Linux, macOS, and Windows (via WSL or PowerShell).
  • If possible, provide explicit macOS-specific notes where behavior may differ (e.g., file paths, permissions).
  • Ensure that any troubleshooting or advanced sections also include both Bash and PowerShell examples.
  • Monitor for future additions that might introduce Windows-only tools or patterns.
GitHub Create Pull Request
Aks Plug in CA certificates for Istio-based service mesh add-on on Azure Kubernetes Service ...ure-aks-docs/blob/main/articles/aks/istio-plugin-ca.md
Low Priority View Details →
Scanned: 2026-01-13 23:55
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively uses Azure CLI and kubectl commands, which are cross-platform, but there is a subtle Windows bias in the ordering and assumptions. The 'Verify Azure CLI version' and installation instructions link to the general Azure CLI install page, which presents Windows instructions before Linux/macOS. No explicit Linux/macOS shell differences or considerations are mentioned, and all examples use Bash syntax, which is more common on Linux/macOS but also available on Windows via WSL or Git Bash. There are no PowerShell-specific examples, nor are Windows-only tools referenced, but the documentation does not clarify cross-platform compatibility or provide parity notes for Linux/macOS users.
Recommendations
  • Explicitly state that all CLI commands are cross-platform and provide links to Linux/macOS-specific installation instructions for Azure CLI.
  • Add a note clarifying that Bash syntax is used, and mention alternatives for Windows users (e.g., PowerShell equivalents, or using WSL/Git Bash).
  • Include troubleshooting tips for common platform-specific issues (e.g., file path formats, permissions).
  • Ensure that referenced external documentation (e.g., Azure CLI install) does not prioritize Windows instructions over Linux/macOS.
GitHub Create Pull Request
Aks Enable Istio CNI for Istio-based service mesh add-on for Azure Kubernetes Service ...ocs/azure-aks-docs/blob/main/articles/aks/istio-cni.md
Low Priority View Details →
Scanned: 2026-01-13 23:55
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation relies exclusively on Azure CLI commands for all setup and verification steps. Azure CLI is available cross-platform, but the documentation does not mention or provide parity for Linux-native tools (e.g., shell scripts, direct kubectl usage, or bash alternatives for Azure resource management). The page does not reference PowerShell, but it does use Azure CLI as the only tool for cluster management, which is more commonly associated with Windows environments and may be installed by default there. There is no explicit mention of Linux-specific patterns or tools, and the guidance assumes the use of Azure CLI over alternatives like Terraform, ARM templates, or direct REST API calls, which are often preferred in Linux-centric workflows. The documentation does not provide instructions for installing Azure CLI on Linux/macOS, only a link.
Recommendations
  • Explicitly state that Azure CLI is cross-platform and provide installation instructions for Linux/macOS inline, not just as a link.
  • Add notes or examples for using Azure CLI in bash/zsh environments, including common Linux shell patterns.
  • Mention alternative tools (e.g., Terraform, ARM templates, REST API) for users who may prefer non-Azure CLI workflows.
  • Clarify that all kubectl commands are Linux/macOS compatible and provide troubleshooting tips for common Linux issues (e.g., permissions, path problems).
  • If possible, provide a short section on using the Azure Cloud Shell (which is Linux-based) for users who do not want to install Azure CLI locally.
GitHub Create Pull Request
Aks View Kubelet Logs from AKS Nodes .../azure-aks-docs/blob/main/articles/aks/kubelet-logs.md
Low Priority View Details →
Scanned: 2026-01-13 23:55
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows Example Present
Summary
The documentation primarily focuses on Linux-based AKS nodes, using Linux commands and tools (journalctl, chroot, grep) throughout. Windows node instructions are present, but only as a brief note at the end, mentioning the log location and the 'more' command. There are no PowerShell examples, and Windows tools/patterns are not emphasized or shown first. The Linux workflow is clearly primary, but Windows is not ignored.
Recommendations
  • Provide a dedicated section for Windows node log collection, including step-by-step instructions similar to the Linux workflow.
  • Include PowerShell examples for obtaining credentials and accessing logs on Windows nodes.
  • Clarify prerequisites for Windows node troubleshooting (e.g., remote access setup, permissions).
  • Ensure parity in troubleshooting steps and example outputs for both Linux and Windows nodes.
GitHub Create Pull Request
Aks Install existing applications with Helm in Azure Kubernetes Service (AKS) ...ure-aks-docs/blob/main/articles/aks/kubernetes-helm.md
Low Priority View Details →
Scanned: 2026-01-13 23:55
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation briefly mentions Windows (Azure PowerShell) as a way to create an AKS cluster before Linux (Azure CLI), but all technical examples and commands throughout the page use cross-platform tools (Helm, kubectl, Azure CLI) and shell syntax compatible with Linux/macOS and Windows (via WSL, Git Bash, or PowerShell with appropriate configuration). There are no PowerShell-specific examples, nor exclusive references to Windows tools or patterns.
Recommendations
  • List Azure CLI before Azure PowerShell when suggesting cluster creation methods, as CLI is more universally cross-platform.
  • Explicitly mention that all commands are compatible with Linux/macOS terminals and provide notes for Windows users on using WSL or compatible shells if needed.
  • Add a brief section clarifying shell compatibility for users on different platforms.
GitHub Create Pull Request
Aks Install Kueue on Azure Kubernetes Service (AKS) ...zure-aks-docs/blob/main/articles/aks/kueue-overview.md
Low Priority View Details →
Scanned: 2026-01-13 23:55
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Reference
Summary
The documentation references Windows-specific tools and patterns, such as Azure PowerShell and the Azure portal, before mentioning Linux alternatives. However, all command-line examples use bash syntax, which is cross-platform and compatible with Linux/macOS. There are no exclusive Windows-only commands or examples, but the ordering and tool references show a slight Windows-first bias.
Recommendations
  • List Linux-friendly tools (Azure CLI) before Windows-specific ones (PowerShell, portal) in prerequisites and quickstart links.
  • Explicitly state that all bash commands work on Linux/macOS and provide clarification for Windows users who may need WSL or Git Bash.
  • Add a note or section for macOS/Linux users if any step differs (e.g., Helm or kubectl installation).
  • Where PowerShell is referenced, provide equivalent bash or shell commands if relevant.
GitHub Create Pull Request
Aks Quickstart: Deploy an Azure Kubernetes Service (AKS) cluster using an ARM template ...icles/aks/learn/quick-kubernetes-deploy-rm-template.md
Low Priority View Details →
Scanned: 2026-01-13 23:55
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 key steps (connecting to the cluster, deleting resources), but consistently lists PowerShell as an equal alternative, and sometimes as a separate tab. There is a slight 'Windows first' bias in the ordering and inclusion of PowerShell examples, which are primarily relevant to Windows users. However, Linux/macOS users are not blocked, as Azure CLI and kubectl commands are cross-platform and shown throughout. No critical steps are Windows-only, and Linux tools (ssh-keygen, kubectl) are referenced. The bias is minor and mainly in presentation/order.
Recommendations
  • List Azure CLI examples before PowerShell, as CLI is cross-platform and preferred for Linux/macOS.
  • Explicitly state that Azure CLI commands work on Linux/macOS and Windows, while PowerShell is primarily for Windows.
  • Where PowerShell is shown, clarify its platform relevance.
  • Consider removing PowerShell examples from quickstarts or moving them to a separate section for Windows users.
  • Add a note at the start clarifying that all steps can be completed on Linux/macOS using Azure CLI and kubectl.
GitHub Create Pull Request
Aks Manage local accounts with AKS-managed Microsoft Entra integration ...articles/aks/manage-local-accounts-managed-azure-ad.md
Low Priority View Details →
Scanned: 2026-01-13 23:55
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page primarily uses Azure CLI commands, which are cross-platform, but the only explicit file path example given is a Windows-style path (C:\Users\<username>\.kube\config) in the output section. No Linux/macOS path equivalents are shown, and the output examples use Windows conventions. There are no PowerShell-specific commands, but the documentation implicitly assumes a Windows environment for file paths.
Recommendations
  • Include Linux/macOS file path examples (e.g., ~/.kube/config) alongside Windows paths in output sections.
  • Add a note clarifying that Azure CLI commands work on Windows, Linux, and macOS, and mention any OS-specific differences in output or file locations.
  • Show example outputs for both Windows and Linux/macOS users to ensure parity.
GitHub Create Pull Request
← Previous Page 5 of 13 Next →