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 26-50 of 618 flagged pages
Aks Provision Azure NetApp Files dual-protocol volumes for Azure Kubernetes Service .../main/articles/aks/azure-netapp-files-dual-protocol.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation provides comprehensive instructions for both NFS (Linux) and SMB (Windows) dual-protocol volumes in AKS. However, the SMB example is exclusively Windows-focused, with pod manifests using Windows containers (IIS), nodeSelector for Windows nodes, and Windows shell commands (cmd.exe, dir). There are no SMB pod examples for Linux containers, nor guidance for mounting SMB volumes on Linux nodes, despite SMB being supported on Linux via the CSI driver. The SMB section implicitly prioritizes Windows usage and tools.
Recommendations
  • Add SMB pod manifest examples for Linux containers, demonstrating mounting SMB volumes on Linux nodes.
  • Include Linux shell commands (e.g., bash, ls, df) for verifying SMB mounts in Linux pods, alongside Windows examples.
  • Clarify in the SMB section that SMB volumes can be mounted on both Windows and Linux nodes, and provide parity in instructions.
  • Consider reordering or parallelizing examples so that both Linux and Windows use cases are equally represented for SMB.
GitHub Create Pull Request
Aks Troubleshoot the Agentic CLI for Azure Kubernetes Service (AKS) ...ob/main/articles/aks/cli-agent-for-aks-troubleshoot.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation includes a troubleshooting step for 'ImportError: DLL load failed while importing win32file', which is a Windows-specific error and references reinstalling the Azure CLI client without mentioning Linux/macOS equivalents. There are no Linux/macOS-specific troubleshooting steps or examples, and the guidance does not clarify platform differences for CLI installation or error resolution.
Recommendations
  • Add troubleshooting steps for common Linux/macOS errors (e.g., library issues, permission errors, missing dependencies).
  • Clarify that 'ImportError: DLL load failed while importing win32file' is a Windows-specific error and provide equivalent Linux/macOS error messages and solutions if applicable.
  • Include platform-specific instructions for reinstalling the Azure CLI (e.g., apt, yum, Homebrew commands for Linux/macOS).
  • Explicitly state when a troubleshooting step is only relevant to Windows users.
GitHub Create Pull Request
Aks Deploy an Azure Kubernetes application by using an ARM template .../blob/main/articles/aks/deploy-application-template.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 First Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for accepting marketplace terms, but the PowerShell example is given immediately after the CLI example, and no explicit Linux/macOS shell example is shown. The CLI command is generic, but the PowerShell reference may create a perception of Windows preference. There are no Linux-specific instructions or screenshots, and the workflow assumes familiarity with the Azure portal, which is cross-platform but may be more familiar to Windows users. No Linux tools or shell scripting examples are provided.
Recommendations
  • Clarify that Azure CLI commands work on Windows, Linux, and macOS, and explicitly mention this in the relevant section.
  • Remove or de-emphasize PowerShell examples unless there is a unique Windows-only step.
  • Add a Linux/macOS shell example for downloading and deploying the ARM template, such as using curl, wget, or bash scripting.
  • Include a note or section highlighting cross-platform compatibility and any OS-specific caveats.
  • Ensure screenshots and instructions do not assume a Windows environment (e.g., file paths, shell conventions).
GitHub Create Pull Request
Aks AKS Regulated Cluster for PCI DSS 4.0.1 - Enhanced MFA Implementation ...b/main/articles/aks/pci-enhanced-mfa-implementation.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 First Missing Linux Example
Summary
The documentation provides several implementation examples using PowerShell scripts and references to Azure AD Conditional Access, which are typically managed via the Azure Portal or PowerShell. There are no Linux/macOS-specific CLI or automation examples (e.g., Bash, Azure CLI, REST API) for creating Conditional Access policies or managing MFA, and PowerShell is presented as the only scripting method for policy creation. Additionally, Windows-centric tools and workflows (PowerShell, Azure Portal navigation) are mentioned before any cross-platform alternatives, and Linux-native approaches are not discussed.
Recommendations
  • Add equivalent Bash/Azure CLI examples for creating and managing Conditional Access policies and MFA enforcement.
  • Reference REST API methods for Conditional Access policy management, which are platform-agnostic.
  • Clarify that PowerShell is one option and provide links or examples for Linux/macOS users.
  • Where possible, use Azure CLI for all AKS and Azure AD operations, as it is cross-platform.
  • Explicitly mention that all steps can be performed from Linux/macOS using Azure CLI or REST API, and provide sample commands.
GitHub Create Pull Request
Aks AKS Regulated Cluster for PCI DSS 4.0.1 - Risk Assessment and Code Assets ...-aks-docs/blob/main/articles/aks/pci-ra-code-assets.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 is generally cross-platform and AKS-focused, with most examples and guidance applicable to both Linux and Windows environments. However, there is a notable instance of Windows bias in the Identity and Access Management section, where PowerShell cmdlets are referenced for configuring conditional access policies, without mentioning equivalent CLI or REST API options for Linux/macOS users. Additionally, the PowerShell example is presented first and exclusively, which may create friction for non-Windows users.
Recommendations
  • Include Azure CLI and/or REST API examples alongside PowerShell for configuring conditional access policies, ensuring Linux/macOS users have clear guidance.
  • When referencing management tools or automation, provide cross-platform alternatives or clarify platform requirements.
  • Review other sections for subtle Windows-first patterns and ensure parity in tooling and examples where possible.
GitHub Create Pull Request
Aks AKS Regulated Cluster for PCI DSS 4.0.1 - Security Awareness Training ...b/main/articles/aks/pci-security-awareness-training.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides a PowerShell script as the sole example for automating training completion tracking, without offering equivalent Linux/macOS (e.g., Bash, Python, Azure CLI) alternatives. This may create friction for users who primarily work in Linux environments, as AKS is often managed from Linux/macOS systems. Additionally, the PowerShell example appears before any Linux-friendly tooling is mentioned, suggesting a Windows-first approach in automation guidance.
Recommendations
  • Provide equivalent Bash or Azure CLI examples for tracking training completion and updating Azure AD user properties.
  • Clarify that the PowerShell script is one option and suggest cross-platform alternatives (e.g., Python SDK, REST API, Azure CLI).
  • Ensure automation and scripting examples are presented in a way that is accessible to both Windows and Linux/macOS users.
  • Where possible, use platform-agnostic tools (e.g., Azure CLI, REST API) for examples involving Azure services.
GitHub Create Pull Request
Aks Kubernetes on Azure tutorial - Create an Azure Container Registry and build images ...b/main/articles/aks/tutorial-kubernetes-prepare-acr.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for most steps, but PowerShell is emphasized as an alternative throughout, and is presented in dedicated tabs. The CLI examples use environment variables in a way that is ambiguous for Linux/macOS users (e.g., $ACRNAME), and there are no explicit Linux/macOS shell examples or notes about shell differences. PowerShell is a Windows-centric tool, and its inclusion as a primary alternative may create friction for Linux/macOS users. There are no Linux-specific instructions or examples, and the documentation does not clarify how to set environment variables or run commands in Bash/zsh.
Recommendations
  • Add explicit Bash/zsh examples for Linux/macOS users, especially for environment variable usage (e.g., export ACRNAME=myregistry123).
  • Clarify how environment variables should be set and used in different shells (Windows CMD, PowerShell, Bash/zsh).
  • Consider presenting Azure CLI (cross-platform) examples first, and PowerShell as a secondary option.
  • Add notes or tabs for Linux/macOS users where command syntax or behavior differs.
  • Avoid assuming PowerShell is available or preferred on Linux/macOS.
GitHub Create Pull Request
Aks Control cluster and node access using Conditional Access with AKS-managed Microsoft Entra integration ...b/main/articles/aks/access-control-managed-azure-ad.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias by focusing exclusively on Azure portal workflows and Azure CLI commands, which are cross-platform but often more familiar to Windows users. There are no explicit Linux/macOS-specific instructions or examples, and no mention of Linux-native SSH tools or workflows. The SSH example uses 'az ssh vm', which is Azure-specific and does not discuss standard OpenSSH usage or alternatives for Linux/macOS users. The documentation also references Azure portal navigation and Microsoft Entra ID features, which may be more familiar to Windows-centric administrators.
Recommendations
  • Add explicit Linux/macOS examples for SSH access, such as using OpenSSH with Entra ID integration.
  • Include notes or sections on how to perform equivalent tasks using Linux-native tools and command-line workflows.
  • Clarify that Azure CLI is cross-platform and provide installation instructions for Linux/macOS users.
  • Provide parity in troubleshooting steps or verification methods for Linux/macOS environments.
  • Mention any differences in authentication flows or device compliance checks for non-Windows endpoints.
GitHub Create Pull Request
Aks AKS Production Upgrade Strategies ...main/articles/aks/aks-production-upgrade-strategies.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation page demonstrates a moderate Windows bias. Azure CLI examples dominate, and all traffic management, DNS, and cluster operations use Azure CLI commands, which are most easily run on Windows or via PowerShell. There is no mention of Linux-specific tools, nor are Linux-native command-line alternatives (e.g., bash scripts, Linux DNS utilities) provided. Windows-centric Azure Traffic Manager and DNS update patterns are shown first and exclusively. No PowerShell scripts are present, but the CLI usage and Azure-centric tooling are more familiar to Windows users. Linux users can follow along, but the lack of explicit Linux/macOS guidance or parity examples creates friction.
Recommendations
  • Add explicit notes or examples for Linux/macOS users, including how to install and use Azure CLI on those platforms.
  • Provide bash-native alternatives for DNS switching (e.g., using dig/nsupdate for validation).
  • Include references to Linux-native tools for monitoring and scripting (e.g., systemd timers, cron jobs, shell scripts) alongside Azure CLI.
  • Clarify that Azure CLI is cross-platform and provide links to installation guides for Linux/macOS.
  • Where possible, show both Azure CLI and REST API/cURL equivalents for cluster operations.
  • Add troubleshooting steps that mention Linux-specific issues (e.g., shell quoting, file permissions).
GitHub Create Pull Request
Aks Use Azure Hybrid Benefit ...ks-docs/blob/main/articles/aks/azure-hybrid-benefit.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily focused on Windows workloads and tools. All examples pertain to enabling Azure Hybrid Benefit for Windows Server licenses, and the only admin user shown is a Windows admin. The PowerShell examples reinforce a Windows-centric approach, and there are no Linux-specific examples or mention of Linux workloads. The documentation does not clarify if or how Azure Hybrid Benefit applies to Linux nodes, and the 'Next steps' section exclusively references Windows containers.
Recommendations
  • Clarify early in the documentation that Azure Hybrid Benefit is only applicable to Windows Server workloads, if that is the case. If Linux workloads are supported, provide equivalent examples for Linux nodes.
  • Include a statement or FAQ addressing the applicability (or lack thereof) of Azure Hybrid Benefit to Linux workloads.
  • If possible, provide Linux/macOS shell (bash) equivalents for any Azure CLI commands, and clarify that Azure CLI is cross-platform.
  • Balance the 'Next steps' section by including resources for both Windows and Linux containers on AKS, or explicitly state the Windows focus.
  • Avoid using only Windows admin usernames and passwords in examples; consider using neutral or cross-platform examples.
GitHub Create Pull Request
Aks Provision Azure NetApp Files dual-protocol volumes for Azure Kubernetes Service .../main/articles/aks/azure-netapp-files-dual-protocol.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation provides detailed, step-by-step instructions for both NFS (Linux) and SMB (Windows) volume provisioning in AKS with Azure NetApp Files. However, the SMB section is heavily oriented toward Windows usage: it exclusively demonstrates mounting SMB volumes in Windows pods (using IIS and Windows ServerCore images), uses Windows-specific commands (cmd.exe, dir), and sets nodeSelector for Windows nodes. There are no examples or guidance for mounting SMB volumes in Linux pods, nor any mention of Linux-compatible SMB usage. The SMB CSI driver installation instructions explicitly enable Windows support, and all verification steps for SMB are Windows-centric.
Recommendations
  • Add examples for mounting SMB volumes in Linux pods, including sample YAML manifests and verification steps using Linux containers (e.g., Ubuntu, Alpine).
  • Document any Linux-specific requirements or limitations for SMB volumes in AKS (e.g., supported images, mount options, troubleshooting).
  • Include Linux command-line examples for verifying SMB mounts (e.g., using 'mount', 'df -h', 'ls') alongside Windows commands.
  • Clarify in the SMB section that SMB volumes can be mounted by both Windows and Linux pods, if supported, or explicitly state any platform limitations.
  • Present NFS and SMB instructions in parallel, with equal detail and visibility for both Linux and Windows use cases.
GitHub Create Pull Request
Aks Configure Azure NetApp Files for Azure Kubernetes Service ...-aks-docs/blob/main/articles/aks/azure-netapp-files.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation exhibits mild Windows bias by referencing SMB volumes as only supported on Windows worker nodes and mentioning AD DS integration requirements, which are Windows-centric. All command-line examples use Azure CLI, which is cross-platform, but there are no explicit Linux/macOS-specific instructions or clarifications. The documentation does not provide parity for Linux users regarding SMB volumes, and Windows requirements are mentioned before alternatives or limitations for Linux.
Recommendations
  • Clarify which steps and features are cross-platform and which are Windows-only (e.g., SMB support).
  • Provide explicit guidance or alternatives for Linux/macOS users, especially regarding SMB volumes and AD DS integration.
  • Add Linux/macOS-specific notes or examples where relevant, or link to documentation covering those scenarios.
  • Consider reordering sections so that platform-neutral or Linux-friendly options (NFS, dynamic provisioning) are presented first.
  • Explicitly state limitations for Linux/macOS users up front, and suggest workarounds or alternatives.
GitHub Create Pull Request
Aks Troubleshoot the Agentic CLI for Azure Kubernetes Service (AKS) ...ob/main/articles/aks/cli-agent-for-aks-troubleshoot.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation includes an error ('ImportError: DLL load failed while importing win32file') that is specific to Windows environments, referencing a Windows-only Python module (win32file) and suggesting to reinstall the Azure CLI client without clarifying platform differences or providing Linux/macOS equivalents. No Linux/macOS-specific troubleshooting steps or examples are present, and the guidance does not address how Linux/macOS users should handle similar issues.
Recommendations
  • Add troubleshooting steps for Linux/macOS users, especially for platform-specific errors.
  • Clarify that 'win32file' errors are Windows-specific and provide equivalent Linux/macOS error messages and solutions.
  • Include examples and troubleshooting guidance for common Linux/macOS issues (e.g., permissions, missing dependencies, environment variable setup).
  • Explicitly state platform requirements or differences where relevant.
GitHub Create Pull Request
Aks Integrate Azure Container Registry with Azure Kubernetes Service (AKS) ...articles/aks/cluster-container-registry-integration.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides parallel examples for Azure CLI and Azure PowerShell throughout, but PowerShell is a Windows-centric tool and is listed as a primary method alongside CLI. There are no Linux/macOS-specific shell examples (e.g., Bash), and PowerShell is presented as an equal alternative, which may imply Windows bias. The troubleshooting section only references Azure CLI, but the main workflows consistently offer PowerShell examples. The documentation does not mention Linux-specific tools or patterns, nor does it clarify cross-platform compatibility for PowerShell. Azure CLI is cross-platform, but PowerShell is traditionally associated with Windows, and its inclusion may create friction for Linux/macOS users.
Recommendations
  • Clarify that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
  • Explicitly state that Azure PowerShell is available on Linux/macOS, or provide installation instructions for those platforms.
  • Add Bash shell examples where appropriate, especially for variable assignment and scripting.
  • Consider listing Azure CLI examples before PowerShell to signal cross-platform parity.
  • Mention that all kubectl commands are cross-platform and can be run from any OS with the tool installed.
GitHub Create Pull Request
Aks Concepts - Access and identity in Azure Kubernetes Services (AKS) ...e-aks-docs/blob/main/articles/aks/concepts-identity.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page consistently presents Azure CLI commands (e.g., az login, az aks get-credentials) and workflow steps without specifying platform differences, but implicitly assumes a Windows environment by referencing browser-based authentication and omitting explicit Linux/macOS instructions or examples. There are no PowerShell-specific commands, but the lack of Linux/macOS parity (such as alternative authentication flows, CLI installation, or environment-specific notes) creates friction for non-Windows users.
Recommendations
  • Add explicit instructions or notes for Linux/macOS users, such as how to install Azure CLI, handle browser-based authentication, and manage kubeconfig files.
  • Include example commands and workflows for Linux/macOS environments, especially where file paths, authentication prompts, or CLI usage may differ.
  • Clarify any platform-specific prerequisites or troubleshooting steps, such as handling device authentication on headless Linux servers.
  • Ensure parity in screenshots and UI references (e.g., Azure portal) by noting any differences for non-Windows 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
Medium Priority View Details →
Scanned: 2026-01-13 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 Portal, Azure PowerShell, and Azure CLI, but the PowerShell section is notably detailed and references Windows-centric tools. PowerShell is traditionally a Windows-first tool, and its inclusion as a primary method (with instructions for local installation and usage) can signal a Windows bias, especially since the PowerShell module is referenced before CLI and with more setup detail. The CLI section is present and cross-platform, but PowerShell is given more prominence and explanation. There are no explicit Linux/macOS-only examples or troubleshooting tips, and the PowerShell instructions reference Windows upgrade paths before Linux/macOS.
Recommendations
  • Ensure Azure CLI examples are as detailed as PowerShell examples, since CLI is natively cross-platform.
  • Add troubleshooting or environment setup notes specific to Linux/macOS, especially for PowerShell usage.
  • Consider listing CLI instructions before PowerShell, or clarify that CLI is recommended for Linux/macOS users.
  • Explicitly mention that PowerShell is available cross-platform, but CLI may be more familiar to Linux/macOS users.
  • Provide parity in example depth and setup instructions for both CLI and PowerShell.
GitHub Create Pull Request
Aks Deploy an Azure Kubernetes application by using an ARM template .../blob/main/articles/aks/deploy-application-template.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for accepting marketplace terms, but the PowerShell example is included without a corresponding Linux/macOS shell alternative. The flow assumes use of the Azure portal (web), which is cross-platform, but command-line instructions mention PowerShell specifically and do not show Linux/macOS shell equivalents. The CLI example is shown first, but the PowerShell example may cause confusion for non-Windows users. There is no explicit mention of Linux/macOS compatibility or alternative shell commands.
Recommendations
  • Clarify that Azure CLI commands work on Linux/macOS and Windows equally.
  • Remove or de-emphasize PowerShell examples unless there is a Linux/macOS shell equivalent.
  • Add explicit bash/zsh shell examples for Linux/macOS users where appropriate.
  • Add a note indicating cross-platform compatibility for all CLI commands.
  • If PowerShell is mentioned, clarify its availability on Linux/macOS or provide alternative shell commands.
GitHub Create Pull Request
Aks Deploy to Azure Kubernetes Service with Azure Pipelines ...ure-aks-docs/blob/main/articles/aks/devops-pipeline.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Azure CLI and PowerShell examples for resource creation, but PowerShell is given equal prominence and detail, with explicit instructions for installing Azure PowerShell and registering resource providers. There is no mention of Linux/macOS-specific shell environments, nor are bash or shell script examples provided. The use of PowerShell and references to Windows-centric tools and patterns (such as Install-Module) may create friction for Linux/macOS users, although Azure CLI is cross-platform and included.
Recommendations
  • Ensure Azure CLI examples are presented first, as it is cross-platform and preferred for Linux/macOS users.
  • Add explicit notes or examples for bash/shell environments, including any differences in authentication or environment setup.
  • Clarify that PowerShell examples are optional and primarily for Windows users; suggest alternatives for Linux/macOS.
  • Include troubleshooting tips or links for Linux/macOS users, especially for Cloud Shell usage.
  • Where PowerShell-specific steps are required (e.g., registering resource providers), provide CLI equivalents.
GitHub Create Pull Request
Aks Use Image Integrity to validate signed images before deploying them to your Azure Kubernetes Service (AKS) clusters (Preview) ...ure-aks-docs/blob/main/articles/aks/image-integrity.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Prerequisites and command examples consistently mention Azure CLI and Azure PowerShell, but do not provide explicit Linux/macOS installation or usage guidance. All command-line examples use Azure CLI syntax, which is cross-platform, but PowerShell is referenced as an alternative without equivalent bash or shell examples. There is no mention of Linux-specific considerations, and Windows tools (PowerShell) are listed before Linux alternatives. The documentation does not address potential differences in command usage or environment setup for Linux/macOS users.
Recommendations
  • Explicitly state that Azure CLI is cross-platform and provide installation instructions for Linux/macOS.
  • Add bash/zsh shell examples where PowerShell is mentioned, or clarify that Azure CLI commands work identically on Linux/macOS.
  • Include troubleshooting or environment setup notes for Linux/macOS users (e.g., permissions, package managers).
  • Avoid listing Windows tools (PowerShell) before Linux alternatives unless there is a technical reason.
  • Add a section or note confirming Linux/macOS compatibility and any caveats.
GitHub Create Pull Request
Aks Kubernetes Gateway API Ingress for Istio Service Mesh Add-on for Azure Kubernetes Service (AKS) (preview) ...e-aks-docs/blob/main/articles/aks/istio-gateway-api.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
🔧 Windows Tools
Summary
The documentation page demonstrates a notable bias toward Windows/Azure environments by exclusively using Azure CLI commands (az), which are most commonly installed and supported on Windows and Azure Cloud Shell. There are no PowerShell-specific examples, but the lack of Linux/macOS-specific instructions or parity for Azure CLI installation and usage may create friction for non-Windows users. All shell examples use bash syntax, which is cross-platform, but the Azure CLI focus and lack of alternatives (such as REST API, Terraform, or ARM templates) means Linux/macOS users must install and use Azure CLI to follow the guide.
Recommendations
  • Add a section describing how to install and use Azure CLI on Linux and macOS, including troubleshooting tips for common issues.
  • Provide alternative instructions using Azure Portal, REST API, or Terraform for critical steps involving Azure Key Vault and AKS add-ons.
  • Explicitly state that all CLI commands are compatible with bash on Linux/macOS and provide links to platform-specific installation guides.
  • Where possible, mention that Azure CLI is cross-platform and provide links to official documentation for non-Windows environments.
GitHub Create Pull Request
Aks Quickstart: Deploy an Azure Kubernetes Service (AKS) cluster using the Azure portal ...n/articles/aks/learn/quick-kubernetes-deploy-portal.md
Medium Priority View Details →
Scanned: 2026-01-13 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 connecting to the AKS cluster, but lists PowerShell as a primary tab alongside CLI, and specifically calls out PowerShell usage for local environments before mentioning Azure CLI. There are no explicit Linux-only examples, and the workflow assumes users are either using the Azure Cloud Shell (which is cross-platform) or Windows tools (PowerShell). There are no references to Linux-specific shell environments (e.g., bash) or macOS, and no troubleshooting or alternative instructions for Linux/macOS users. The resource deletion steps are portal-only and do not mention CLI commands, which are often preferred by Linux users.
Recommendations
  • Add explicit bash/Linux/macOS instructions and examples for all steps, especially for connecting to the cluster and managing resources.
  • List Azure CLI (bash) instructions before PowerShell, as CLI is cross-platform and more commonly used on Linux/macOS.
  • Include a section on deleting resources using Azure CLI commands (e.g., az group delete) for parity with portal instructions.
  • Clarify that Cloud Shell is available on all platforms and provide guidance for local Linux/macOS environments.
  • Avoid assuming PowerShell is the default for local environments; mention bash/zsh as alternatives.
GitHub Create Pull Request
Aks Quickstart: Deploy an Azure Kubernetes Service (AKS) cluster using Azure PowerShell ...ticles/aks/learn/quick-kubernetes-deploy-powershell.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on Azure PowerShell, with all core examples and instructions using PowerShell cmdlets. There is no mention of Azure CLI, Bash, or Linux-native workflows for cluster creation, resource management, or credential import. The guidance assumes use of PowerShell either in Azure Cloud Shell or locally, and references Windows-specific patterns (e.g., administrative privileges, PowerShell module installation) without Linux/macOS alternatives. Linux users must adapt the instructions themselves, and may not be aware of equivalent Azure CLI commands.
Recommendations
  • Add parallel Azure CLI/Bash examples for all major steps (resource group creation, AKS cluster creation, credential import, resource deletion).
  • Explicitly mention that Azure Cloud Shell supports Bash as well as PowerShell, and provide links to Bash quickstarts.
  • Include installation instructions for Azure CLI and kubectl on Linux/macOS.
  • Where PowerShell is referenced, offer equivalent CLI commands and note cross-platform compatibility.
  • Reorder or balance examples so that Linux/macOS workflows are presented alongside or before Windows/PowerShell ones.
GitHub Create Pull Request
Aks Connect to Azure Kubernetes Service (AKS) cluster nodes ...s/azure-aks-docs/blob/main/articles/aks/node-access.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides both Linux/macOS and Windows node access methods, but Windows-specific instructions are more complex and rely heavily on PowerShell and Windows-only patterns (e.g., host process containers, Windows Server proxy). Windows node access is described in detail, with multiple workarounds and tools (PowerShell, Azure Bastion, host process containers), while Linux access is straightforward and shown first. There is a notable emphasis on Windows-specific tooling and patterns, and Windows examples (PowerShell, host process containers) are given their own dedicated sections.
Recommendations
  • Provide parity by including Linux/macOS equivalents for host process container access (e.g., privileged containers for troubleshooting Linux nodes).
  • Where possible, show Linux/macOS and Windows examples side-by-side for each major step, rather than separating them into distinct sections.
  • Reduce reliance on Windows-specific tools (e.g., PowerShell) in examples, or provide equivalent Linux commands for similar tasks.
  • Clarify which steps are universal and which are OS-specific, and avoid presenting Windows workarounds as the primary method for node access.
  • Add troubleshooting and advanced access patterns for Linux nodes to match the depth given to Windows nodes.
GitHub Create Pull Request
Aks Use OpenFaaS on Azure Kubernetes Service (AKS) ...Docs/azure-aks-docs/blob/main/articles/aks/openfaas.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page references Windows tools and patterns before Linux equivalents in several places, such as listing Azure PowerShell as a primary method for cluster creation and referencing the Azure portal and Cloud Shell (which defaults to PowerShell for Windows users). There is a lack of explicit Linux/macOS examples for key steps, such as installing MongoDB tools (only 'brew' is mentioned, which is macOS-specific), and no mention of package managers like apt or yum for Linux. The documentation does not provide parity for Linux users in command-line examples or tool installation instructions.
Recommendations
  • Provide Linux-specific installation instructions for MongoDB tools (e.g., using apt, yum, or snap).
  • When listing cluster creation options, mention Linux-friendly tools (Azure CLI) first, and clarify PowerShell is for Windows users.
  • Explicitly state that Azure Cloud Shell supports both Bash and PowerShell, and show examples in Bash where appropriate.
  • Add notes or sections for Linux/macOS users where commands or tools differ.
  • Ensure screenshots and UI references are platform-neutral or include both Windows and Linux variants if differences exist.
GitHub Create Pull Request
Aks Best practices for cluster security ...ticles/aks/operator-best-practices-cluster-security.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for cluster upgrades, but PowerShell (a Windows-centric tool) is given equal prominence and detail as Azure CLI. There is a dedicated section for Windows Server node updates, while Linux node update guidance is present but less detailed in terms of manual operations. No direct Linux shell (bash) or native Linux tool examples (such as kubectl, apt, yum, etc.) are provided for cluster or node management, and Windows-specific tools (PowerShell) are featured as primary options. This may create friction for Linux/macOS users who do not use PowerShell.
Recommendations
  • Add explicit bash/Linux shell examples for common operations, such as checking/upgrading Kubernetes versions and managing node updates.
  • Provide parity in manual node update instructions for Linux nodes, similar to the Windows Server node update section.
  • Clarify that Azure CLI is cross-platform and highlight its usage for Linux/macOS users.
  • Reduce the prominence of PowerShell or clearly indicate its Windows specificity.
  • Include references to native Linux tools (kubectl, apt, yum) where relevant.
GitHub Create Pull Request
← Previous Page 2 of 25 Next →