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 51-75 of 301 flagged pages
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-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides parallel examples for Azure CLI and Azure PowerShell, but PowerShell is a Windows-centric tool and is presented as an equal alternative to the cross-platform Azure CLI. There are no explicit Linux/macOS shell examples (e.g., Bash), and PowerShell is featured in tabs throughout, which may suggest Windows as a primary platform. Additionally, environment variable usage is shown in PowerShell syntax, which differs from Bash/Linux conventions. No Linux-specific tools or patterns are mentioned, and the CLI examples do not clarify Linux/macOS usage (e.g., export vs. set for environment variables).
Recommendations
  • Add explicit Bash/Linux/macOS shell examples for all CLI commands, especially for environment variable usage (e.g., 'export ACRNAME=...').
  • Clarify that Azure CLI is cross-platform and provide guidance for Linux/macOS users where syntax differs.
  • Reorder tabs to show Azure CLI (Bash) first, or provide a dedicated Linux/macOS section.
  • Avoid presenting PowerShell as the default or primary scripting environment unless necessary.
  • Include notes or callouts for platform-specific differences, especially for environment variable handling and file paths.
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-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides parallel instructions for Azure CLI, Azure PowerShell, and Azure Developer CLI, but PowerShell is given equal prominence as Azure CLI, and PowerShell-specific commands are presented throughout. PowerShell is a Windows-centric tool, and its inclusion as a primary method may signal a Windows bias. Additionally, installation instructions for kubectl and AKS cluster creation include PowerShell-specific cmdlets and examples, which are not relevant for Linux/macOS users. The ordering of sections sometimes places PowerShell before or alongside CLI, rather than focusing on cross-platform CLI tools first.
Recommendations
  • Clearly indicate that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Add explicit Bash/Linux/macOS instructions and examples where relevant, especially for kubectl installation (e.g., using curl or package managers).
  • De-emphasize PowerShell as a primary method, or clarify its Windows-centric nature.
  • Provide a table or summary at the start indicating which tools are cross-platform and which are Windows-only.
  • Ensure that CLI examples appear before PowerShell examples, or group Windows-specific instructions in a separate section.
  • Include links or notes for Linux/macOS users on alternative installation and usage patterns.
GitHub Create Pull Request
Aks Use system node pools in Azure Kubernetes Service (AKS) ...re-aks-docs/blob/main/articles/aks/use-system-pools.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides examples exclusively using Azure CLI and Azure PowerShell, with no Linux/macOS-specific shell examples or guidance. While Azure CLI is cross-platform, the PowerShell examples are Windows-centric and are presented alongside CLI examples in every section. There are no bash or shell script examples, nor is there mention of Linux-native tools or workflows. Additionally, PowerShell is listed as a primary tool, which may create friction for Linux/macOS users unfamiliar with it.
Recommendations
  • Clarify that Azure CLI commands work natively on Linux/macOS and provide explicit bash/shell examples where appropriate.
  • De-emphasize PowerShell as a primary workflow for cross-platform documentation, or provide bash equivalents for all PowerShell commands.
  • Add notes or sections for Linux/macOS users, such as installation instructions for Azure CLI on those platforms.
  • Where PowerShell is used for complex object manipulation, provide equivalent bash/jq or Python examples.
  • Explicitly state that all operations can be performed from Linux/macOS terminals using Azure CLI.
GitHub Create Pull Request
Aks Use Virtual Machines node pools in Azure Kubernetes Services (AKS) .../blob/main/articles/aks/virtual-machines-node-pools.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits moderate Windows bias. While the main AKS node pool creation and management examples use Azure CLI (cross-platform), the section on creating Windows-enabled clusters and node pools focuses on Windows-specific requirements (username, password complexity) and does not provide parity for Linux node pool creation steps. Windows terminology and requirements are presented first and in detail, while Linux-specific instructions are minimal or absent. No PowerShell is used, but Windows administrative patterns (username/password prompts, password complexity) are emphasized. There are no explicit Linux examples for creating Linux node pools, nor is there guidance for Linux-specific configuration or troubleshooting.
Recommendations
  • Add explicit Linux node pool creation examples and instructions, including any Linux-specific configuration or requirements.
  • Balance the documentation by presenting Linux and Windows node pool creation steps side-by-side or in parallel sections.
  • Clarify which steps are OS-agnostic and which are Windows-specific, to avoid confusion for Linux/macOS users.
  • Include troubleshooting or notes relevant to Linux node pools, such as SSH key management or Linux VM specifics.
  • Avoid presenting Windows requirements (username/password) before Linux equivalents unless contextually necessary.
GitHub Create Pull Request
Aks Migrate Azure Kubernetes Service (AKS) Pods to Microsoft Entra Workload ID ...les/aks/workload-identity-migrate-from-pod-identity.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Missing Windows Example Linux Only Feature Windows Exclusion
Summary
The documentation exhibits a Linux bias in the migration sidecar approach, which is explicitly stated as 'Linux containers only' and excludes Windows containers. No Windows-specific examples, tools, or PowerShell commands are provided; all CLI and Kubernetes examples are platform-neutral or Linux-oriented. Windows users are told to rewrite their applications for SDK parity, but no Windows container migration workaround or example is offered.
Recommendations
  • Provide explicit guidance or examples for Windows container users, especially for scenarios where the migration sidecar is unavailable.
  • Clarify migration steps for Windows containers, including any limitations or alternative approaches.
  • If possible, develop and document a migration sidecar or proxy solution for Windows containers, or explain technical barriers.
  • Include PowerShell examples for Azure CLI commands where appropriate to improve parity for Windows administrators.
  • Clearly indicate which steps are platform-agnostic and which require Linux, to help users plan accordingly.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation provides both NFS (Linux) and SMB (Windows) examples for provisioning Azure NetApp Files dual-protocol volumes in AKS. However, the SMB section is heavily oriented toward Windows: it exclusively demonstrates mounting SMB volumes on Windows nodes using Windows containers (IIS), Windows-specific nodeSelector, and Windows shell commands (cmd.exe, dir). There are no examples for mounting SMB volumes on Linux pods, nor any mention of Linux SMB client usage or Linux container images. The SMB CSI driver installation instructions also highlight enabling Windows support, with no Linux parity guidance. The NFS section is Linux-focused, but the SMB section is Windows-only.
Recommendations
  • Add examples for mounting SMB volumes on Linux worker nodes and Linux containers (e.g., using Ubuntu or Alpine images).
  • Include instructions for using the SMB CSI driver with Linux nodes, clarifying any differences in configuration or usage.
  • Provide Linux shell commands (e.g., ls, df) for verifying SMB mounts inside Linux pods.
  • Clarify that SMB volumes can be used by both Windows and Linux pods, and describe any limitations or requirements.
  • Present NFS and SMB examples in parallel, showing both Windows and Linux usage for each protocol where possible.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation exhibits a moderate Windows bias. While the Azure CLI is used for all command-line examples (which is cross-platform), there is a notable focus on SMB volumes being supported only on Windows worker nodes, and Active Directory integration is discussed primarily in a Windows context. There are no explicit Linux/macOS-specific instructions or examples, and the documentation does not clarify Linux/macOS support for SMB scenarios. Additionally, the prerequisites and instructions do not mention Linux-specific considerations, and Windows-specific limitations are described before Linux alternatives.
Recommendations
  • Add explicit Linux/macOS instructions or notes, especially regarding SMB support and limitations.
  • Clarify which steps and features are cross-platform and which are Windows-only.
  • Provide parity in examples for Linux/macOS environments, such as mentioning NFS as the preferred protocol for non-Windows nodes.
  • Include troubleshooting or alternative guidance for Linux/macOS users where Windows-only features (like SMB on Windows worker nodes) are mentioned.
  • Consider reordering sections so that cross-platform or Linux-first options (NFS, Trident usage) are described before Windows-only features.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page provides parallel examples for Azure CLI and Azure PowerShell throughout, but PowerShell is a Windows-centric tool and is highlighted as a primary method alongside Azure CLI. There are no Linux/macOS-specific shell examples (e.g., Bash), nor are platform differences discussed. The use of PowerShell and its cmdlets may create friction for Linux/macOS users, as PowerShell is not natively installed on those platforms. Additionally, PowerShell examples are presented with equal prominence to CLI, and troubleshooting steps reference CLI only, with no Linux/macOS-specific guidance.
Recommendations
  • Clarify that Azure CLI is cross-platform and recommend it as the default for Linux/macOS users.
  • Add explicit Bash shell examples and usage notes for Linux/macOS environments where appropriate.
  • Note that PowerShell is available for Linux/macOS but may require installation, and provide installation instructions or links.
  • Ensure troubleshooting and validation steps include platform-agnostic or Linux/macOS-specific guidance.
  • Consider reordering examples to present Azure CLI (cross-platform) before PowerShell (Windows-centric) in each section.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation contains a Windows-specific error ('ImportError: DLL load failed while importing win32file') and recommends reinstalling the Azure CLI client without clarifying platform-specific steps. There are no explicit Linux/macOS troubleshooting examples or references to Linux-specific errors, despite the CLI being cross-platform.
Recommendations
  • Add troubleshooting steps for common Linux/macOS-specific errors (e.g., library or permission issues).
  • Clarify whether the 'ImportError: DLL load failed while importing win32file' is exclusive to Windows and provide equivalent Linux/macOS error messages and solutions.
  • Include platform-specific instructions for reinstalling the Azure CLI (e.g., apt, yum, brew commands for Linux/macOS).
  • Ensure that examples and error messages cover both Windows and Linux/macOS environments.
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-12 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 accepting terms, but PowerShell (a Windows-centric tool) is mentioned and shown alongside CLI, with no explicit mention of Linux/macOS shell alternatives. The instructions for downloading and saving the ARM template refer generically to 'your computer' and do not clarify cross-platform steps. There is no explicit Linux/macOS example or guidance, and PowerShell is referenced without noting its limited availability on non-Windows platforms.
Recommendations
  • Explicitly state that Azure CLI works on Linux/macOS and provide shell-specific examples (e.g., bash/zsh).
  • Clarify that PowerShell examples are optional and provide parity for Linux/macOS users.
  • Add notes or links for installing and using Azure CLI on Linux/macOS.
  • Ensure screenshots and instructions do not assume Windows-only environments.
  • Mention file path conventions for both Windows and Linux/macOS when saving the ARM template.
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-12 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 and Azure Key Vault for secret management. There are no references to Linux-specific tools, nor are alternative approaches for non-Azure or non-Windows environments provided. All examples for certificate creation, secret management, and add-on enablement use Azure CLI and Azure Key Vault, which are most commonly used in Windows-centric or Azure cloud environments.
Recommendations
  • Provide alternative instructions for secret management using Kubernetes-native Secrets, which are platform-agnostic and do not require Azure Key Vault.
  • Include examples for certificate creation and management using Linux-native tools and workflows, such as using kubectl to create TLS secrets directly.
  • Add notes or sections for users running AKS clusters on Linux/macOS, clarifying that Azure CLI is cross-platform but that Azure Key Vault is not required for all scenarios.
  • Offer guidance for users who wish to use other cloud providers or on-premises clusters, such as using HashiCorp Vault or other secret stores.
  • Clarify that the Azure CLI is available for Linux/macOS, but provide links or instructions for installation on those platforms.
GitHub Create Pull Request
Aks Azure Kubernetes Service (AKS) Managed Gateway API Installation ...aks-docs/blob/main/articles/aks/managed-gateway-api.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation relies exclusively on Azure CLI commands, which are cross-platform but are often associated with Windows environments. There is no mention of Linux-specific tools or package managers (e.g., apt, yum, Homebrew), nor are there instructions for installing prerequisites (like Azure CLI itself) on Linux/macOS. All command-line examples use Azure CLI and bash, but the installation and environment setup steps assume familiarity with Windows-centric workflows. No PowerShell-specific commands are present, but the lack of Linux/macOS installation guidance and the absence of alternative tooling (such as kubectl-only workflows) create friction for non-Windows users.
Recommendations
  • Add explicit instructions for installing Azure CLI on Linux and macOS, including links to official guides.
  • Include notes or examples for using Azure CLI in bash/zsh on Linux/macOS, and clarify cross-platform compatibility.
  • Mention alternative methods for managing AKS clusters, such as using kubectl directly where possible.
  • Ensure that all prerequisite steps are platform-agnostic, or provide platform-specific guidance as needed.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation provides both Linux/macOS and Windows guidance, but Windows-specific tools (PowerShell, host process containers) and workarounds are described in detail, sometimes before or more prominently than Linux equivalents. Windows node access requires more complex steps and relies heavily on PowerShell and Windows-specific Kubernetes features, while Linux access is more straightforward. Some sections (like host process containers) are Windows-only and use PowerShell as the default shell.
Recommendations
  • Provide equivalent Linux/macOS examples for all major steps, especially where Windows-specific tools (e.g., PowerShell, host process containers) are used.
  • Ensure Linux/macOS instructions are presented first or in parallel with Windows instructions, rather than Windows-first in some sections.
  • Where possible, clarify which steps are OS-specific and offer parity in troubleshooting and maintenance workflows.
  • Add more troubleshooting and advanced access examples for Linux nodes to match the depth given for Windows nodes.
  • Explicitly note limitations or differences for each OS at the start of each section.
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-12 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 to CLI, and Windows Server node update instructions are included as a separate section. There are no explicit Linux shell examples (e.g., bash), and Windows tools/patterns (PowerShell) are mentioned before or alongside CLI, which is cross-platform. The documentation does mention Linux node update processes, but does not provide command-line examples for Linux users, focusing instead on automated processes. There is a slight bias towards Windows tools and patterns, and Linux users may need to infer or adapt instructions.
Recommendations
  • Provide explicit bash or Linux shell examples for common operations, especially for cluster upgrades and node management.
  • Clarify that Azure CLI is cross-platform and recommend it as the primary tool for Linux/macOS users.
  • Add parity in example sections: for every PowerShell example, provide a bash/Linux shell equivalent.
  • Include troubleshooting or manual update instructions for Linux nodes, not just automated processes.
  • Reorder examples to show CLI (cross-platform) first, followed by PowerShell (Windows-centric).
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-12 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-specific tools and patterns in several places, such as listing Azure PowerShell and Azure portal as cluster creation options before mentioning the Azure CLI. 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 Linux package managers (apt, yum). The use of Azure Cloud Shell is platform-neutral, but some commands (e.g., password generation) assume Bash, which is more common on Linux/macOS but not universal on Windows. There are no PowerShell-specific commands, but the ordering and lack of Linux-specific installation instructions create friction for non-Windows users.
Recommendations
  • Provide Linux-specific installation instructions for tools like MongoDB (e.g., apt, yum, zypper).
  • When listing options for cluster creation, mention Azure CLI first, as it is cross-platform, and clarify which tools are available on which OS.
  • Explicitly state that Bash commands (e.g., password generation) may not work in Windows CMD/PowerShell and provide alternatives.
  • Add notes or sections for macOS and Linux users where steps differ (e.g., file creation, environment variable syntax).
  • Ensure screenshots and UI references are not Windows-centric.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. While most implementation steps use Azure CLI (which is cross-platform), the only explicit code example for creating Conditional Access policies is given in PowerShell, with no Linux/macOS equivalent. The guidance and tooling references (Azure AD, Conditional Access, Azure Monitor) are heavily oriented toward Microsoft/Azure ecosystems, which are most familiar to Windows users. There are no Linux-specific examples or alternative approaches for non-Windows environments, and the PowerShell example may create friction for Linux/macOS users.
Recommendations
  • Provide equivalent Bash or Azure CLI examples for all PowerShell scripts, especially for Conditional Access policy creation.
  • Clarify which tools and commands are cross-platform, and offer guidance for Linux/macOS users where Azure CLI or REST API alternatives exist.
  • Explicitly state that Azure CLI commands can be run on Linux/macOS, and link to installation guides for those platforms.
  • Where possible, avoid using Windows-centric scripting languages (PowerShell) as the sole example, or provide parity with Bash/CLI.
  • Add notes or sections for Linux/macOS users, especially for administrative tasks that may differ from Windows environments.
GitHub Create Pull Request
Aks AKS Regulated Cluster for PCI DSS 4.0.1 - Security Policies ...cs/azure-aks-docs/blob/main/articles/aks/pci-policy.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates a bias towards Microsoft and Windows-centric tools and services. All examples and recommendations reference Microsoft products (Purview Compliance Manager, Defender for Cloud, Azure Advisor, Entra, Defender for Endpoint) without mentioning or providing Linux-native or open-source alternatives. There are no examples or guidance for Linux/macOS users or for those using non-Microsoft environments. The documentation assumes the use of Azure and Microsoft security tooling, which may not be available or preferred in Linux-first or multi-cloud environments.
Recommendations
  • Include examples and recommendations for Linux-native and open-source security tools (e.g., OpenSCAP, osquery, Falco, auditd) for device discovery, inventory management, and compliance assessment.
  • Reference Kubernetes-native solutions and cross-platform cloud IAM/logging tools (e.g., Kubernetes RBAC audit logs, AWS IAM, Google Cloud IAM) alongside Microsoft Entra.
  • Provide guidance for users operating AKS clusters from Linux/macOS environments, including CLI commands and integration patterns.
  • List open standards and vendor-neutral resources before or alongside Microsoft-specific ones.
  • Add explicit instructions or links for users who do not use Microsoft Defender or Entra, including how to achieve similar compliance outcomes with other tools.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page provides implementation examples for tracking training completion using PowerShell scripts and Azure AD integration, which are Windows-centric tools. No equivalent Linux/bash examples are provided for these critical automation tasks, and the scripting guidance assumes familiarity with PowerShell and Windows-based Azure tooling. Other sections use YAML, KQL, and Azure CLI, which are cross-platform, but the only explicit code sample for training tracking is PowerShell, creating friction for Linux/macOS users.
Recommendations
  • Provide equivalent bash or Python script examples for tracking training completion, using Azure CLI and REST APIs, suitable for Linux/macOS environments.
  • Explicitly mention cross-platform alternatives to PowerShell, such as Azure CLI, for automation tasks.
  • Ensure all critical implementation steps include both Windows and Linux/macOS compatible instructions or scripts.
  • Add notes clarifying which tools/scripts are cross-platform and which are Windows-specific.
GitHub Create Pull Request
Aks Stop and start an Azure Kubernetes Service (AKS) cluster ...-aks-docs/blob/main/articles/aks/start-stop-cluster.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for stopping and starting AKS clusters. However, Azure PowerShell examples are given equal prominence to Azure CLI, and PowerShell is a Windows-centric tool. In the 'Before you begin' section, Azure PowerShell is mentioned before the Azure portal, and is listed alongside Azure CLI as a way to create clusters, which may suggest Windows-first thinking. There are no Linux-specific examples or notes, and no mention of Bash, shell scripting, or Linux/macOS nuances. The CLI instructions are cross-platform, but the inclusion and equal emphasis on PowerShell may create friction for Linux/macOS users.
Recommendations
  • Clearly state that Azure CLI works on Windows, Linux, and macOS, and is the recommended cross-platform tool.
  • Move Azure CLI instructions before PowerShell in all sections to reinforce cross-platform parity.
  • Add a note clarifying that Azure PowerShell is primarily for Windows users, and that Linux/macOS users should use Azure CLI.
  • Consider removing PowerShell examples from the main flow, or placing them in a separate tab or appendix for Windows users.
  • Add explicit Bash/shell examples where relevant, or clarify that the CLI commands work in Bash, zsh, etc.
GitHub Create Pull Request
Aks Kubernetes on Azure tutorial - Deploy an application to Azure Kubernetes Service (AKS) ...articles/aks/tutorial-kubernetes-deploy-application.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides parallel instructions for Azure CLI, Azure PowerShell, and Azure Developer CLI, but PowerShell is featured as a primary option alongside CLI, and no explicit Linux/macOS shell examples (e.g., bash, zsh) are given. The PowerShell instructions and references may create friction for Linux/macOS users, as PowerShell is not the default shell on those platforms. The document does not mention or show Linux-specific patterns or tools, nor does it clarify that Azure CLI commands work natively on Linux/macOS. The order of examples sometimes puts PowerShell before CLI, and there is no explicit guidance for Linux users.
Recommendations
  • Add explicit bash/zsh examples for Linux/macOS users, especially for steps involving file editing and environment variables.
  • Clarify that Azure CLI commands work natively on Linux/macOS and provide installation links for those platforms.
  • Reorder example tabs to put Azure CLI (cross-platform) first, followed by PowerShell (Windows-centric), and then Azure Developer CLI.
  • Mention that PowerShell is optional and not required for Linux/macOS users.
  • Include notes or callouts for Linux/macOS users where file paths, editors, or shell commands may differ.
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-01-12 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 as a primary method alongside CLI, and several installation and usage instructions reference PowerShell-specific cmdlets. There is an implicit bias towards Windows environments, as PowerShell is a Windows-centric tool, and its usage is presented on equal footing with the cross-platform Azure CLI. Linux/macOS users may find the PowerShell sections irrelevant or confusing, and there are no explicit Linux/macOS shell examples (e.g., Bash, zsh) or references to platform-specific nuances. The ordering of examples sometimes places PowerShell before CLI, and installation instructions for kubectl focus on Azure CLI and PowerShell, omitting native package manager options for Linux/macOS.
Recommendations
  • Add explicit Bash/zsh examples for Linux/macOS users, especially for kubectl installation (e.g., using apt, yum, brew).
  • Clarify that PowerShell examples are primarily for Windows users, and highlight Azure CLI as the cross-platform method.
  • Include platform-specific notes about differences in environment variables, file paths, and prerequisites for Linux/macOS.
  • Ensure Azure CLI examples are presented first, as it is the most universally applicable tool.
  • Add a section or callout for Linux/macOS users describing native installation and usage patterns.
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-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The tutorial provides parallel instructions for Azure CLI and Azure PowerShell, but PowerShell is a Windows-centric tool and is presented as an equal alternative to Azure CLI. There are no Linux/macOS-specific shell examples (e.g., Bash), and PowerShell examples are given for all steps except image building, which is only available via Azure CLI. The documentation does not mention Linux-specific patterns or tools, nor does it clarify that Azure CLI is cross-platform while PowerShell is primarily used on Windows. The structure may imply Windows-first workflows and could create friction for Linux/macOS users.
Recommendations
  • Clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Add explicit Bash shell examples for environment variable usage (e.g., export ACRNAME=myregistry$RANDOM) and command invocation.
  • Note that PowerShell is primarily for Windows users and provide guidance for Linux/macOS users to use Azure CLI.
  • Reorder sections to present Azure CLI (Linux/macOS-friendly) before PowerShell.
  • Add a table or callout comparing usage on Windows vs. Linux/macOS.
  • Where PowerShell is not available (e.g., image build), explicitly state that Linux/macOS users should use Azure CLI.
GitHub Create Pull Request
Aks Use system node pools in Azure Kubernetes Service (AKS) ...re-aks-docs/blob/main/articles/aks/use-system-pools.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides examples for Azure CLI and Azure PowerShell, but does not offer any Linux/macOS-specific shell commands or workflows. While Azure CLI is cross-platform, the PowerShell examples are Windows-centric and are presented alongside CLI examples in every section. There are no bash-specific instructions, nor are Linux-native tools or patterns (e.g., bash scripting, environment variables, package managers) mentioned. The documentation also references PowerShell installation and usage before mentioning Linux or macOS alternatives, and does not clarify that Azure CLI commands are equally applicable on Linux/macOS.
Recommendations
  • Clarify that Azure CLI commands work identically on Linux, macOS, and Windows.
  • Add bash/zsh shell examples for common operations, especially for scripting or automation tasks.
  • Include installation instructions for Azure CLI and kubectl on Linux/macOS, not just Windows/PowerShell.
  • Reduce the prominence of PowerShell by moving CLI examples first, and making PowerShell examples optional or secondary.
  • Explicitly mention Linux/macOS compatibility in prerequisites and command sections.
  • Where PowerShell is used for object manipulation, provide equivalent bash/jq or Python examples for Linux users.
GitHub Create Pull Request
Aks Use Virtual Machines node pools in Azure Kubernetes Services (AKS) .../blob/main/articles/aks/virtual-machines-node-pools.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation displays a moderate Windows bias. Windows-specific concepts (Windows admin username/password, Windows Server password complexity) are discussed in detail, and Windows node pool creation is given a dedicated section. The examples for cluster creation and node pool management use Azure CLI, which is cross-platform, but Windows-specific instructions (e.g., password requirements) are emphasized. There is no explicit Linux example for node pool creation, and the Windows workflow is described before any Linux-specific guidance. The documentation assumes familiarity with Windows tools and patterns, such as password complexity rules, without providing Linux equivalents or parity.
Recommendations
  • Add explicit Linux node pool creation examples, including any Linux-specific configuration steps.
  • Clarify that Azure CLI commands work on Linux/macOS, and provide any necessary shell syntax differences.
  • Balance the Windows node pool section with a parallel Linux node pool section, highlighting differences and similarities.
  • If password complexity or admin credential requirements exist for Linux, document them as well.
  • Ensure that examples and instructions for both OS types are presented with equal prominence.
GitHub Create Pull Request
Aks Migrate Azure Kubernetes Service (AKS) Pods to Microsoft Entra Workload ID ...les/aks/workload-identity-migrate-from-pod-identity.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Linux Only Example Windows Missing Example Explicit Linux Limitation
Summary
The documentation provides detailed migration instructions for AKS pods to Microsoft Entra Workload ID, including a migration sidecar approach that is explicitly limited to Linux containers. There are no examples, instructions, or guidance for Windows containers except to note that the sidecar approach does not support them. The rewrite approach mentions Windows container support but does not provide any Windows-specific examples or troubleshooting. All CLI and Kubernetes commands are platform-agnostic, but the only migration workaround for older SDKs is unavailable for Windows users.
Recommendations
  • Provide Windows container migration examples, especially for scenarios where the migration sidecar is not available.
  • Include troubleshooting or guidance for Windows container users who cannot use the sidecar approach.
  • Explicitly state alternative migration paths for Windows containers when using older SDKs.
  • Add a table or section comparing Linux and Windows container support for each migration path.
  • If possible, develop and document a migration workaround for Windows containers using older SDKs.
GitHub Create Pull Request
← Previous Page 3 of 13 Next →