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 51-75 of 618 flagged pages
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) .../blob/main/articles/aks/agentic-cli-for-aks-install.md
Low Priority View Details →
Scanned: 2026-03-10 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides both Linux and Windows/macOS instructions for Docker setup, but in the 'Verify Docker installation and start Docker daemon' section, Windows/macOS instructions are listed before Linux. All CLI examples use Azure CLI, which is cross-platform, and Bash commands are used for verification and cleanup, ensuring Linux parity. No PowerShell-specific or Windows-only tools are referenced, and Linux-specific instructions are present where relevant.
Recommendations
  • Consider listing Linux instructions before Windows/macOS in the Docker daemon startup section, or present all OS instructions in parallel (e.g., in a table or tabs).
  • Explicitly mention that Azure CLI and Docker commands are cross-platform and provide links to installation guides for all supported OSes.
  • Ensure that future examples or troubleshooting sections include Linux/macOS-specific notes if there are OS-specific behaviors.
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-03-10 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. The PowerShell section is detailed and references Windows tools, but also includes instructions for macOS and Linux. However, PowerShell is presented before Azure CLI, and PowerShell is traditionally associated with Windows, which may create a perception of Windows bias. Azure CLI examples are present and equally functional for Linux/macOS users.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is more cross-platform and commonly used on Linux/macOS.
  • Explicitly mention that Azure PowerShell can be used on Linux and macOS, and link to installation instructions for those platforms.
  • Add brief notes clarifying that both Azure CLI and PowerShell examples are fully cross-platform.
  • Consider adding Bash shell examples for common tasks if relevant.
GitHub Create Pull Request
Aks Stop and start an Azure Kubernetes Service (AKS) cluster ...-aks-docs/blob/main/articles/aks/start-stop-cluster.md
Low Priority View Details →
Scanned: 2026-03-10 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for stopping and starting AKS clusters. Azure CLI is cross-platform and suitable for Linux/macOS users, while Azure PowerShell is primarily Windows-focused. However, the CLI examples are presented first in each section, ensuring Linux parity. There are no Windows-only tools or patterns mentioned, and Linux users can fully complete the tasks described.
Recommendations
  • Clarify that Azure CLI is cross-platform and recommended for Linux/macOS users.
  • Consider explicitly stating that Azure PowerShell is primarily for Windows users, and that Linux/macOS users should use Azure CLI.
  • Add a brief note in the 'Before you begin' section highlighting the cross-platform nature of Azure CLI.
GitHub Create Pull Request
Aks Troubleshoot the Agentic CLI for Azure Kubernetes Service (AKS) .../main/articles/aks/agentic-cli-for-aks-troubleshoot.md
Low Priority View Details →
Scanned: 2026-03-10 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation generally provides cross-platform troubleshooting steps, but in the Docker daemon troubleshooting section, instructions for macOS/Windows are listed before Linux, and the Windows solution refers to Docker Desktop (a Windows/macOS-specific tool). However, Linux instructions are present and complete. No PowerShell-specific commands or Windows-only tools are used elsewhere.
Recommendations
  • Present Linux, macOS, and Windows instructions in parallel or in a consistent order (e.g., Linux, macOS, Windows) to avoid implicit prioritization.
  • Explicitly mention that Docker Desktop is for Windows/macOS, and clarify the equivalent for Linux (systemd service).
  • Where possible, provide command-line solutions for all platforms, or link to platform-specific Docker startup guides.
  • If using platform-specific tools (like Docker Desktop), briefly mention alternatives for other OSes.
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-03-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides both Linux and Windows file paths for verifying TLS Bootstrapping, but the Windows path is mentioned alongside the Linux path rather than exclusively or first. However, in the certificate rotation and verification sections, all command-line examples use Bash, Azure CLI, and kubectl, which are cross-platform but primarily shown in Linux syntax. There are no PowerShell or Windows Command Prompt examples for Windows users, but the documentation does not exclusively mention Windows tools or patterns. The only minor bias is that Linux paths and Bash examples are shown first and exclusively, with Windows-specific file paths mentioned only once.
Recommendations
  • Add explicit PowerShell or Windows Command Prompt examples for certificate expiration checks and Azure CLI commands, especially for Windows users who may not have Bash available.
  • Provide guidance on running Azure CLI and kubectl on Windows, including any prerequisites or differences.
  • Where file paths are shown, clarify if the commands are cross-platform or provide equivalent Windows commands/scripts.
  • Consider showing both Linux and Windows examples side-by-side for critical steps.
GitHub Create Pull Request
Aks Integrate Azure Container Registry with Azure Kubernetes Service (AKS) ...articles/aks/cluster-container-registry-integration.md
Low Priority View Details →
Scanned: 2026-03-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all major tasks, but PowerShell is featured equally and sometimes referenced first in metadata and tool tracking. There is a slight Windows bias due to the heavy inclusion of PowerShell examples and explicit mention of Azure PowerShell as a primary tool, which is most relevant for Windows users. However, all CLI examples are cross-platform and Linux-compatible, and there are no Windows-only commands or tools. No Linux-specific examples (e.g., Bash scripting, shell environment variables) are provided, but Linux users can complete all tasks using Azure CLI.
Recommendations
  • Clarify that Azure PowerShell is available on Linux/macOS and link to installation instructions for those platforms.
  • Add brief Bash shell scripting examples or notes for setting environment variables (e.g., export vs. set) to improve Linux parity.
  • Explicitly state that all Azure CLI commands are cross-platform and recommend CLI for Linux/macOS users.
  • Consider mentioning that PowerShell Core is cross-platform, if relevant, to reduce perceived Windows bias.
GitHub Create Pull Request
Aks Create and Manage Persistent Volumes with Azure Files in Azure Kubernetes Service (AKS) ...cs/blob/main/articles/aks/create-volume-azure-files.md
Low Priority View Details →
Scanned: 2026-03-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides a comprehensive guide for creating and managing persistent volumes with Azure Files in AKS, primarily using YAML manifests and Azure CLI commands. While the majority of examples and instructions are platform-neutral or Linux-focused, there are occasional signs of Windows bias: Windows path conventions are mentioned before Linux equivalents in some sections, and in the Windows containers section, PowerShell/CMD path examples are given alongside Bash. Azure CLI is used throughout, which is cross-platform, but no explicit Linux shell or macOS-specific guidance is provided for Azure CLI installation or troubleshooting. Overall, the bias is minor and does not prevent Linux/macOS users from completing the tasks.
Recommendations
  • Where Windows path conventions are mentioned, ensure Linux/macOS equivalents are also shown and listed first unless the section is Windows-specific.
  • Clarify that Azure CLI is cross-platform and provide links or notes for Linux/macOS installation and troubleshooting.
  • When providing shell commands, use generic Bash syntax and note any Windows-specific differences only in Windows-focused sections.
  • In sections referencing PowerShell/CMD, ensure Bash/Linux equivalents are equally prominent.
  • Consider adding explicit notes or examples for macOS users where relevant (e.g., file permissions, mount options).
GitHub Create Pull Request
Aks Move Azure Disk persistent volumes to another AKS cluster in the same or a different subscription .../blob/main/articles/aks/csi-disk-move-subscriptions.md
Low Priority View Details →
Scanned: 2026-03-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation mentions Azure PowerShell as a migration option alongside Azure CLI and Azure Portal, but does not provide PowerShell-specific examples. Azure CLI is used for all command-line examples, which is cross-platform. However, Azure PowerShell is referenced before Azure CLI in the migration options, and there are no Linux-specific notes or examples. The documentation does not provide any Windows-only commands or patterns, but the mention of PowerShell without parity for Linux shell tools (e.g., Bash) is a minor Windows-first bias.
Recommendations
  • Clarify that Azure CLI commands are cross-platform and preferred for Linux/macOS users.
  • If referencing Azure PowerShell, provide equivalent Bash or Linux shell command examples, or explicitly state that Azure CLI is recommended for Linux/macOS.
  • Consider listing Azure CLI before Azure PowerShell in migration options to reinforce Linux parity.
  • Add a note that all CLI examples work on Linux, macOS, and Windows.
GitHub Create Pull Request
Aks Install Dapr Extension for Azure Kubernetes Service (AKS) ...softDocs/azure-aks-docs/blob/main/articles/aks/dapr.md
Low Priority View Details →
Scanned: 2026-03-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation is largely cross-platform, focusing on Azure CLI and Bicep for installing Dapr on AKS, which are available on Windows, Linux, and macOS. However, in the section about listing CRDs for cleanup, only a Windows/PowerShell example ('kubectl get crds | findstr dapr.io') is provided, with no Linux/macOS equivalent. Additionally, the use of 'findstr' (a Windows tool) is shown before any mention of Linux alternatives, and no 'grep' example is given.
Recommendations
  • Add a Linux/macOS example for listing CRDs, such as 'kubectl get crds | grep dapr.io'.
  • When showing command-line examples that differ by OS, provide both Windows and Linux/macOS versions side-by-side.
  • Review other sections for similar OS-specific commands and ensure parity.
  • Consider mentioning that Azure CLI and Bicep are cross-platform, reinforcing inclusivity.
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-03-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for managing AKS authorized IP ranges, but consistently presents Azure CLI (Linux/macOS-friendly) first, followed by Azure PowerShell (Windows-centric). There are no explicit Windows-only tools or patterns, and all instructions are portal-based or cross-platform. However, the PowerShell section is present, which may be unnecessary for Linux/macOS users, but does not hinder their ability to complete the task. No critical steps are Windows-only.
Recommendations
  • Consider clarifying that Azure PowerShell examples are for Windows users, while Azure CLI is cross-platform.
  • If possible, add a Bash-only example for Linux/macOS users (e.g., using curl for IP retrieval).
  • Ensure that CLI instructions are clearly marked as cross-platform and PowerShell as Windows-specific.
  • Add a note that Azure CLI works on Windows, Linux, and macOS, while PowerShell is primarily for Windows.
GitHub Create Pull Request
Aks Create an internal load balancer ...s/azure-aks-docs/blob/main/articles/aks/internal-lb.md
Low Priority View Details →
Scanned: 2026-03-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation provides both Azure CLI and PowerShell options for prerequisite steps, but consistently mentions Azure PowerShell alongside Azure CLI and portal, sometimes listing PowerShell before Linux-native alternatives. It also references a PowerShell cmdlet (Get-AzVirtualNetworkSubnetConfig) for subnet listing, but does not provide a Linux equivalent (such as Azure CLI) in that context. However, all main examples and workflows use kubectl and Azure CLI, which are cross-platform, and no critical steps are Windows-only.
Recommendations
  • When referencing PowerShell cmdlets (e.g., Get-AzVirtualNetworkSubnetConfig), always provide the Azure CLI equivalent and show it first, as Azure CLI is cross-platform.
  • In prerequisite sections, list Azure CLI before PowerShell to reinforce Linux parity.
  • Consider removing or de-emphasizing PowerShell references unless the feature is Windows-specific.
  • Explicitly note that Azure CLI and kubectl commands work on Linux/macOS/Windows.
  • Add a note clarifying that all main workflows are cross-platform.
GitHub Create Pull Request
Aks Connect to Azure Kubernetes Service (AKS) cluster nodes ...s/azure-aks-docs/blob/main/articles/aks/node-access.md
Low Priority View Details →
Scanned: 2026-03-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Linux/macOS and Windows node access instructions, but Windows-specific tools (PowerShell, host process containers) are emphasized in dedicated sections. Windows node access methods are described after Linux/macOS, but Windows-specific examples (e.g., PowerShell in host process containers) are prominent and not paralleled with Linux equivalents. The Linux/macOS instructions are clear and complete, but Windows sections rely heavily on Windows tools and patterns.
Recommendations
  • Ensure Linux/macOS and Windows instructions are equally detailed and easy to follow.
  • Where Windows-specific tools (e.g., PowerShell, host process containers) are mentioned, clarify if there are Linux equivalents or explicitly state that these are Windows-only approaches.
  • Consider grouping Linux/macOS and Windows instructions in parallel subsections for easier comparison.
  • Add explicit notes when a method is Windows-only, to avoid confusion for Linux/macOS users.
  • For SSH instructions, provide parity in troubleshooting and advanced access methods for both OS types.
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-03-10 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 available Kubernetes versions), but consistently presents Azure CLI (cross-platform) examples first, followed by Azure PowerShell (Windows-centric) examples. No Linux-specific commands, tools, or shell patterns are missing, but there is a slight bias in the inclusion of PowerShell examples and terminology, which may be less relevant for Linux/macOS users. However, all critical tasks are covered with cross-platform tools, and Linux-specific OS components are clearly documented.
Recommendations
  • Consider explicitly mentioning that Azure CLI is cross-platform and recommended for Linux/macOS users.
  • Add brief notes clarifying that Azure PowerShell is primarily for Windows users.
  • Where possible, include bash or shell script examples for Linux users, especially for common tasks.
  • Ensure that all CLI instructions are clearly marked as cross-platform.
  • If referencing Azure CLI, highlight its compatibility with Linux/macOS in introductory sections.
GitHub Create Pull Request
← Previous Page 3 of 25 Next →