Aks

529
Total Pages
427
Linux-Friendly Pages
102
Pages with Bias
19.3%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

343 issues found
Showing 26-50 of 343 flagged pages
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
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-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 demonstrates a moderate Windows bias. PowerShell is used for scripting Conditional Access policies, and Azure AD/Entra tools (which are more Windows-centric) are referenced throughout. No Linux/macOS-specific CLI or scripting examples are provided, and the only explicit script example for policy creation is in PowerShell. Azure CLI is used for AKS operations, which is cross-platform, but the lack of Bash or Linux-native scripting for policy management and the absence of Linux/macOS-specific access patterns or troubleshooting guidance create friction for non-Windows users.
Recommendations
  • Provide Bash or cross-platform shell examples for Conditional Access policy creation and management, not just PowerShell.
  • Explicitly mention that Azure CLI commands work on Linux/macOS and provide any OS-specific caveats.
  • Include guidance or links for Linux/macOS users on managing Azure AD/Entra policies (e.g., via REST API, Azure CLI, or portal).
  • Add troubleshooting notes or access patterns for Linux/macOS users, especially for MFA and AKS access.
  • Ensure that scripting and automation examples are provided in both PowerShell and Bash where possible.
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-13 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 Windows bias by exclusively referencing Microsoft-centric tools and services (e.g., Microsoft Purview Compliance Manager, Defender for Cloud, Defender for Endpoint, Entra logs) for compliance and security management. There are no examples or mentions of Linux-native or open-source alternatives for device discovery, IAM, or inventory management. The guidance assumes users are operating primarily in a Microsoft/Azure ecosystem, which may not be representative of all AKS users, especially those running Linux-based workloads or using non-Microsoft tools.
Recommendations
  • Include examples or references to Linux-native/open-source tools for device discovery (e.g., osquery, OpenSCAP), IAM logging (e.g., auditd, Linux system logs), and inventory management.
  • Mention cross-platform or cloud-agnostic solutions alongside Microsoft tools to provide parity for non-Windows environments.
  • Add guidance for integrating AKS with non-Microsoft security and compliance solutions commonly used in Linux environments.
  • Where possible, provide links or documentation for equivalent Linux/macOS workflows.
GitHub Create Pull Request
Aks AKS Regulated Cluster for PCI DSS 4.0.1 - Network Security ...s/azure-aks-docs/blob/main/articles/aks/pci-network.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 notable Windows/Azure bias by exclusively referencing Azure-native tools and patterns (e.g., Azure Firewall, NSGs, Application Gateway, Azure Bastion, Azure CLI, Bicep, ARM templates) for network security and infrastructure management. There are no Linux-specific or cross-platform CLI examples, nor are open-source alternatives (other than Kubernetes-native resources) discussed. The documentation assumes the use of Azure services and Windows-centric management workflows, with no mention of Linux-native tools (e.g., iptables, nftables, firewalld) or Linux command-line examples for network configuration, monitoring, or firewall management.
Recommendations
  • Provide Linux-native examples for network security tasks, such as configuring firewalls with iptables/nftables or using Linux CLI tools to view network topology.
  • Include cross-platform CLI examples (e.g., kubectl, Terraform, Ansible) for infrastructure as code and cluster management, not just Azure-specific tools.
  • Reference open-source or Linux-native alternatives to Azure services where possible (e.g., alternatives to Azure Firewall, Bastion, Application Gateway).
  • Explicitly state which instructions are platform-agnostic and which are Azure/Windows-specific.
  • Add guidance for users deploying AKS clusters from Linux/macOS environments, including SSH, VPN, and firewall configuration steps.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides a PowerShell script for tracking training completion and references Azure AD integration, which are Windows-centric tools and patterns. There are no equivalent Linux/bash examples for tracking training completion, nor is there mention of cross-platform alternatives for the script. The use of PowerShell and Azure AD as the sole example for automation and integration creates friction for Linux/macOS users who may prefer or require bash, Python, or other non-Windows tooling.
Recommendations
  • Provide equivalent bash or Python script examples for tracking training completion and integrating with Azure services.
  • Explicitly mention cross-platform alternatives to PowerShell, such as Azure CLI or REST API usage from Linux/macOS.
  • Clarify that Azure AD integration and automation can be performed from Linux/macOS environments, and provide links or examples.
  • Ensure that all automation and scripting guidance includes both Windows and Linux/macOS options, or is platform-neutral where possible.
GitHub Create Pull Request
Aks Control cluster and node access using Privileged Identity Management (PIM) with AKS-managed Microsoft Entra integration ...ob/main/articles/aks/privileged-identity-management.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation demonstrates a moderate Windows bias. While most CLI examples use the cross-platform Azure CLI and bash syntax, several critical steps (such as token revocation) reference Windows-only tools (PowerShell cmdlets). The SSH workflow relies on Azure CLI extensions, which are cross-platform, but there is no explicit mention of Linux/macOS-specific nuances or alternative commands. Portal navigation instructions use generic UI terms, but do not clarify platform differences. The PowerShell cmdlet for token revocation is referenced without a Linux/macOS equivalent, and Windows tools are mentioned before alternatives.
Recommendations
  • Provide Linux/macOS equivalents for PowerShell-only commands, such as token revocation (e.g., using Microsoft Graph API or REST calls).
  • Explicitly state that Azure CLI and kubectl commands work on Linux/macOS and provide any necessary installation or usage notes for those platforms.
  • Add notes or examples for Linux/macOS users where authentication flows or SSH may differ (e.g., SSH agent configuration, credential storage).
  • Where PowerShell cmdlets are referenced, include REST API or CLI alternatives for non-Windows users.
  • Clarify that Azure Portal steps are platform-agnostic, but mention browser compatibility if relevant.
GitHub Create Pull Request
Aks RDP to AKS Windows Server nodes ...osoftDocs/azure-aks-docs/blob/main/articles/aks/rdp.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation is heavily focused on Windows environments, both in terms of the operating system being managed (Windows Server nodes) and the tools used to interact with Azure (Azure CLI and Azure PowerShell). All examples for creating VMs, managing credentials, and connecting to nodes are provided using Windows-centric tools and workflows. There are no Linux/macOS-specific instructions or examples for connecting via RDP, and the only RDP client mentioned is Microsoft Remote Desktop. The workflow assumes the user is comfortable with Windows command-line tools and RDP, with no mention of alternatives or parity for Linux/macOS users.
Recommendations
  • Provide explicit instructions and examples for Linux/macOS users, including how to use RDP clients available on those platforms (e.g., Remmina, FreeRDP, rdesktop).
  • Include bash shell examples where possible, and clarify that Azure CLI commands can be run from any OS.
  • Mention and link to cross-platform RDP clients, not just Microsoft Remote Desktop.
  • Clarify that Azure CLI and kubectl are cross-platform tools and provide installation instructions for Linux/macOS.
  • If any steps require Windows-only tools (such as PowerShell scripts), offer equivalent bash or shell commands, or note any limitations for non-Windows users.
  • Add a section or callout for Linux/macOS users summarizing any differences or additional steps required.
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-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 parallel instructions for Azure CLI, Azure PowerShell, and Azure Developer CLI, but the PowerShell section introduces a Windows-centric toolset without offering Linux shell equivalents (e.g., Bash scripting for querying ACR). Additionally, PowerShell is presented as a primary tab alongside CLI, which may imply parity, but Linux/macOS users are left without explicit guidance for common shell environments. There are no explicit Linux/macOS-specific instructions or troubleshooting, and PowerShell is given equal prominence to the cross-platform CLI.
Recommendations
  • Add a Bash (Linux/macOS) example for querying the ACR login server, e.g., using 'az acr list' with jq or similar tools.
  • Clarify that Azure CLI commands are cross-platform and can be run in Bash, zsh, or other Unix shells.
  • Consider reordering tabs to present Azure CLI (cross-platform) first, followed by Bash (Linux/macOS), then PowerShell (Windows), to reflect the broader user base.
  • Include troubleshooting or notes for Linux/macOS users where file paths, permissions, or environment differences may arise.
  • Explicitly mention that PowerShell Core is available on Linux/macOS if PowerShell is to be included, or clarify its intended audience.
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 00:00
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 featured heavily throughout, with dedicated sections and commands. PowerShell is a Windows-centric tool, and its inclusion as a primary method may suggest a Windows bias. Additionally, installation instructions for kubectl and AKS cluster creation are given for PowerShell before any mention of Linux-native alternatives (e.g., Bash, native package managers). There is no explicit mention of Linux/macOS-specific installation methods for kubectl (such as using apt, yum, or Homebrew), nor are there examples using Bash scripts or Linux shell commands outside of Azure CLI. The documentation assumes familiarity with PowerShell and Windows patterns, which may create friction for Linux/macOS users.
Recommendations
  • Add explicit instructions for installing kubectl on Linux/macOS using native package managers (e.g., apt, yum, Homebrew).
  • Include Bash shell examples for AKS cluster creation and credential management, especially for users working outside Azure Cloud Shell.
  • Clarify that Azure CLI commands work cross-platform and highlight any OS-specific considerations.
  • Reorder sections so that cross-platform tools (Azure CLI, Bash) are presented before Windows-specific tools (PowerShell).
  • Add notes or links for Linux/macOS users about alternative 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-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 parallel examples for Azure CLI and Azure PowerShell, but PowerShell is a Windows-centric tool and is featured throughout. There is no explicit mention of Linux/macOS shell environments (e.g., Bash), nor are there examples tailored to those platforms. The use of environment variables (e.g., $ACRNAME) is shown in PowerShell syntax, which differs from Bash conventions. The tutorial does not clarify cross-platform differences or provide Linux/macOS-specific guidance, which may cause friction for non-Windows users.
Recommendations
  • Add explicit Bash examples for environment variable usage and command syntax, especially for setting variables (e.g., export ACRNAME=myregistry$RANDOM).
  • Clarify that Azure CLI commands work on Linux/macOS and provide any necessary platform-specific notes.
  • Reorder sections to present Azure CLI (cross-platform) before PowerShell (Windows-centric), or clarify that CLI is recommended for Linux/macOS.
  • Include a note about differences in environment variable syntax between PowerShell and Bash.
  • Consider removing or de-emphasizing PowerShell unless there is unique functionality not available in 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-13 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-specific shell examples (e.g., Bash) or macOS-specific guidance. The introductory 'Before you begin' section lists Azure CLI first, but then gives equal coverage to Azure PowerShell, which is primarily a Windows-centric tool. Throughout the page, every operation is shown with both Azure CLI and Azure PowerShell, but there are no examples using Bash scripts, Linux-native tools, or macOS-specific instructions. There is also no mention of Linux package managers for installing the CLI, nor any troubleshooting tips for non-Windows environments. The documentation assumes parity between CLI and PowerShell, but PowerShell is not the default shell for most Linux/macOS users.
Recommendations
  • Add explicit Bash shell examples for all CLI commands, showing usage in a Linux/macOS terminal.
  • Include installation instructions for Azure CLI using Linux package managers (apt, yum, etc.) and macOS (Homebrew).
  • Clarify that Azure CLI commands work natively in Bash/zsh/fish and are cross-platform, while PowerShell is optional for Linux/macOS.
  • Add troubleshooting notes for common Linux/macOS issues (e.g., permissions, path, SSH key generation differences).
  • Consider reordering examples to show Azure CLI (Bash) first, then PowerShell, to reflect the cross-platform nature of AKS.
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 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation demonstrates a moderate Windows bias, especially in sections related to creating Windows node pools. Windows-specific administrative steps (username/password creation, password complexity requirements) are described in detail, and Windows node pool creation is covered with dedicated examples. However, the main workflow uses Azure CLI, which is cross-platform, and Linux is referenced as the default system pool in Windows cluster creation. No Linux-specific examples or parity notes are provided, and Windows administrative patterns (e.g., password complexity) are emphasized without Linux equivalents.
Recommendations
  • Add explicit Linux node pool creation examples, especially in sections where Windows node pool creation is detailed.
  • Include notes or links to Linux password/SSH key management for parity with Windows admin credential steps.
  • When discussing Windows-specific requirements (e.g., password complexity), clarify that these steps are only relevant for Windows node pools and provide Linux alternatives or state that Linux pools do not require these steps.
  • Ensure that examples and workflows for both Windows and Linux node pools are presented side-by-side or in parallel sections.
  • Mention that Azure CLI commands work on Linux/macOS and Windows, and provide any OS-specific caveats if relevant.
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 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Missing Windows Example Linux Only Feature Windows Support Not Emphasized
Summary
The documentation is generally cross-platform, but the migration sidecar approach is explicitly limited to Linux containers, with no equivalent solution or example for Windows containers. There are no PowerShell or Windows-specific CLI examples; all command-line instructions use Azure CLI and bash syntax, which are cross-platform but shown in a Linux-centric way. The rewrite approach notes that it supports both Linux and Windows containers, but does not provide any Windows-specific guidance or examples.
Recommendations
  • Provide explicit instructions or examples for migrating Windows containers, especially for users who cannot immediately upgrade their SDKs.
  • Include PowerShell or Windows Command Prompt equivalents for Azure CLI and bash commands where relevant.
  • Clarify any limitations or differences for Windows container users in each migration path, and link to additional resources if available.
  • If no migration sidecar exists for Windows, state this clearly and suggest alternative strategies for Windows users.
GitHub Create Pull Request
Aks Install and Use the Agentic CLI for Azure Kubernetes Service (AKS) (Preview) ...cs/blob/main/articles/aks/cli-agent-for-aks-install.md
Low Priority View Details →
Scanned: 2026-02-18 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides both Windows/macOS and Linux instructions for Docker daemon startup, but presents Windows/macOS steps first. All CLI examples use Azure CLI, which is cross-platform, and shell commands are shown in Bash, suitable for Linux/macOS. No PowerShell or Windows-specific tools are referenced, and Linux parity is generally maintained.
Recommendations
  • Present Linux instructions before Windows/macOS in Docker daemon startup steps, or group them equally.
  • Explicitly mention that all Azure CLI commands work on Linux, macOS, and Windows.
  • Consider adding a note that Bash commands are applicable to Linux/macOS, and Windows users may use WSL or Docker Desktop terminal.
GitHub Create Pull Request
Aks Access Kubernetes Resources using the Azure Portal ...e-aks-docs/blob/main/articles/aks/kubernetes-portal.md
Low Priority View Details →
Scanned: 2026-02-18 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 troubleshooting, but PowerShell examples are presented immediately after CLI and are given equal prominence. There is no explicit Linux/macOS bias, but the PowerShell section may be unnecessary for Linux/macOS users. The rest of the documentation is portal-centric and platform-agnostic, with all YAML examples targeting Linux node pools. No Windows-specific tools or patterns are mentioned outside the PowerShell section.
Recommendations
  • Clearly indicate that Azure PowerShell examples are for Windows users, and Azure CLI examples are cross-platform.
  • Consider presenting Azure CLI examples first, and PowerShell examples in a separate, clearly labeled section for Windows users.
  • Add a note clarifying that Azure CLI commands work on Linux, macOS, and Windows, while PowerShell is Windows-centric.
  • If possible, provide Bash alternatives for retrieving the public IP address, or clarify that the CLI example works on Linux/macOS.
GitHub Create Pull Request
Aks Supported Kubernetes Versions in Azure Kubernetes Service (AKS) ...lob/main/articles/aks/supported-kubernetes-versions.md
Low Priority View Details →
Scanned: 2026-02-18 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 key operations (such as installing kubectl and listing AKS versions), but consistently presents Azure CLI (cross-platform) examples first, followed by Azure PowerShell (Windows-centric) examples. No Linux-specific commands or tools are mentioned, but Azure CLI is inherently cross-platform. There are no Windows-only tools or patterns, and Linux is referenced equally in component tables. No critical tasks are Windows-only.
Recommendations
  • Explicitly mention that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Consider adding a brief note or example for Linux/macOS users (e.g., installation of Azure CLI or kubectl via package managers like apt, brew, or curl).
  • Where PowerShell is referenced, clarify its Windows focus and suggest Azure CLI for Linux/macOS.
  • Add links or references to Linux/macOS installation guides for Azure CLI and kubectl.
GitHub Create Pull Request
Aks Configure Azure CNI Networking in Azure Kubernetes Service (AKS) ...aks-docs/blob/main/articles/aks/configure-azure-cni.md
Low Priority View Details →
Scanned: 2026-02-18 00:00
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. While both PowerShell and CLI are cross-platform, the PowerShell section is notably detailed and references Windows tools and patterns (such as PowerShell cmdlets and Cloud Shell), and is presented before the Azure CLI section. The PowerShell section includes explicit instructions for Windows, macOS, and Linux installation, but the CLI section is less prominent. There is a slight bias toward Windows/PowerShell usage, but Linux/macOS users can complete all tasks using Azure CLI or PowerShell.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is more universally used across platforms.
  • Expand Azure CLI instructions to match the detail provided in the PowerShell section, including environment setup and prerequisites for Linux/macOS.
  • Explicitly mention that both PowerShell and CLI are fully supported on Linux/macOS, and provide links to installation guides for each platform.
  • Consider adding Bash shell examples or highlighting CLI usage in Linux/macOS contexts.
GitHub Create Pull Request
Aks Certificate Rotation in Azure Kubernetes Service (AKS) ...ks-docs/blob/main/articles/aks/certificate-rotation.md
Low Priority View Details →
Scanned: 2026-02-18 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides a single example of a Windows file path for verifying TLS Bootstrapping ('C:\k\bootstrap-config'), while the Linux equivalent is also mentioned but not shown first. All other examples and commands are either cross-platform (Azure CLI, kubectl, bash, curl) or explicitly reference Linux file paths. There are no PowerShell-specific commands, Windows tools, or Windows-only patterns used. The Windows path is mentioned after the Linux path, but no Linux-specific troubleshooting or parity notes are provided.
Recommendations
  • Ensure Linux and Windows examples are presented with equal prominence, ideally side-by-side or with clear parity.
  • Add explicit notes or troubleshooting steps for Linux users where file paths or behaviors may differ.
  • Where file paths are given, clarify any differences in permissions, access, or tooling between Linux and Windows nodes.
  • Consider adding a brief section on accessing Linux agent nodes for certificate checks, as is done for Windows nodes.
GitHub Create Pull Request
← Previous Page 2 of 14 Next →