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 201-225 of 618 flagged pages
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-01 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides Docker daemon startup instructions for macOS/Windows before Linux, and refers to 'Docker Desktop' for macOS/Windows, which is a Windows-centric pattern. However, all critical commands and examples are cross-platform, and Linux-specific instructions are present. No PowerShell-only examples or Windows-only tools are used.
Recommendations
  • Present Linux instructions before or alongside Windows/macOS instructions when describing Docker daemon startup.
  • Clarify that 'Docker Desktop' is not available for Linux, and provide equivalent Linux GUI options (if any) or emphasize command-line usage.
  • Consider grouping OS-specific instructions in parallel lists or tables for parity.
  • Explicitly mention that all az CLI commands are cross-platform and provide links to az CLI installation guides for Linux/macOS/Windows.
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-01 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation provides troubleshooting steps for both Windows/macOS and Linux users, but Windows/macOS solutions (Docker Desktop) are often mentioned before Linux equivalents. Windows-specific tooling (Docker Desktop) is referenced, while Linux solutions use system commands. All critical tasks are covered for Linux, but Windows/macOS instructions are presented first in several sections.
Recommendations
  • Present Linux and Windows/macOS troubleshooting steps in parallel or with equal prominence, rather than listing Windows/macOS first.
  • Explicitly mention that Docker Desktop is not available on Linux, and clarify the Linux-specific alternatives.
  • Where possible, provide command-line solutions for Windows (e.g., PowerShell commands for Docker service management) to match Linux parity.
  • Consider grouping troubleshooting steps by OS, or using tabs for OS-specific instructions to avoid implicit prioritization.
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-01 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation provides parity for both Linux and Windows users, but there are minor signs of Windows bias. In the section 'Verify TLS Bootstrapping is enabled on current agent node pool', Windows file paths are mentioned alongside Linux, but Windows is listed second. The documentation references Azure CLI and kubectl, which are cross-platform tools, and shell commands are shown in Bash syntax, suitable for Linux/macOS. There are no PowerShell-specific examples or Windows-only tools used, and all critical tasks can be completed on Linux/macOS. However, the inclusion of Windows paths and references to Windows nodes (even though not prioritized) shows minor Windows bias.
Recommendations
  • Ensure Linux/macOS examples are shown first, or equally with Windows examples.
  • Explicitly state that all Azure CLI and kubectl commands work on Linux/macOS, and provide any necessary notes for Windows users (e.g., path differences, shell syntax).
  • Where file paths are referenced, clarify OS differences and provide both Linux and Windows paths in parallel.
  • If possible, add example outputs from both Linux and Windows environments for commands that may differ.
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-01 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 prominent and includes detailed instructions for installation and usage, referencing Windows, macOS, and Linux. However, PowerShell is traditionally Windows-centric, and its section appears before the Azure CLI, which is more native to Linux/macOS environments. There is no explicit bias in the examples themselves, as both PowerShell and CLI are covered, but PowerShell is given more detailed treatment and appears first, which may subtly favor Windows users.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is more universally supported across platforms.
  • Ensure that CLI instructions are as detailed as PowerShell instructions, including environment preparation and troubleshooting.
  • Explicitly mention that both PowerShell and CLI are cross-platform, but highlight CLI as the preferred option for Linux/macOS users.
  • Consider adding Bash shell examples where relevant, especially for Linux/macOS users.
GitHub Create Pull Request
Aks Concepts - Storage in Azure Kubernetes Services (AKS) ...re-aks-docs/blob/main/articles/aks/concepts-storage.md
Low Priority View Details →
Scanned: 2026-03-01 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation is generally platform-neutral and covers AKS storage concepts applicable to both Linux and Windows node pools. However, in the section on mounting volumes in pods, the Linux example is presented first, followed by the Windows example. There are no PowerShell-heavy examples, Windows tools, or missing Linux examples. All YAML manifests and storage concepts are generic and applicable to both platforms, with a brief note on Windows-specific mounting syntax.
Recommendations
  • Ensure that Linux and Windows examples are presented with equal prominence, possibly side-by-side or with clear headings.
  • Clarify in the mounting section that both Linux and Windows containers are supported, and provide explicit examples for both where relevant.
  • Add a short note at the start of the mounting section indicating that the syntax differs for Linux and Windows containers, to help users quickly find the relevant information.
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-01 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation is primarily Linux-focused, as AKS clusters default to Linux nodes and most examples use Linux paths and conventions. However, there are minor signs of Windows bias: Windows-specific instructions and path conventions are sometimes mentioned before Linux equivalents, and references to Windows tools (such as PowerShell/CMD path syntax) are included even when Linux is the primary context. Additionally, links to SMB protocol documentation point to Windows-centric resources.
Recommendations
  • When mentioning Windows-specific instructions (e.g., path conventions), place Linux instructions first, as Linux is the default for AKS.
  • Provide parity in examples: if Windows paths or commands are shown, ensure Linux equivalents are equally prominent and vice versa.
  • Where possible, link to cross-platform documentation for SMB/NFS protocols, not just Windows-centric pages.
  • Clarify when a section is Windows-specific, and avoid mixing Windows and Linux instructions unless necessary.
  • Review output examples and ensure they reflect both Linux and Windows environments if relevant.
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-01 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation references Azure PowerShell as a tool for moving resources, alongside Azure CLI and the Azure portal. Azure PowerShell is a Windows-centric tool, and its mention is not accompanied by Linux-specific alternatives (such as Bash scripts or Linux-native tools). However, the primary examples throughout the guide use Azure CLI and kubectl, which are cross-platform. The mention of Azure PowerShell occurs before Azure CLI in the list of migration tools, which may subtly prioritize Windows tooling.
Recommendations
  • Clarify that Azure PowerShell is available cross-platform, or explicitly mention that Azure CLI and Azure portal are recommended for Linux/macOS users.
  • List Azure CLI before Azure PowerShell when describing migration options, as CLI is more universally available.
  • If possible, provide a brief example or link for Linux users on how to install and use Azure CLI and kubectl.
  • Consider adding a note that all CLI and kubectl commands are fully supported on Linux/macOS.
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-01 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 references Azure PowerShell and its cmdlets alongside Azure CLI in several places. The PowerShell example ('Get-AzVirtualNetworkSubnetConfig') is mentioned directly after the Azure CLI command for listing subnets, and the quickstart links list Azure PowerShell before the Azure portal. However, all core examples and walkthroughs use kubectl and Azure CLI, which are cross-platform and Linux-friendly. No critical steps are Windows-only, and Linux users can complete all tasks without friction.
Recommendations
  • When listing tools or commands, mention Azure CLI first, as it is cross-platform, and clarify that Azure PowerShell is optional for Windows users.
  • Provide Linux/macOS-specific notes or examples where relevant (e.g., shell variable syntax differences).
  • Consider removing or de-emphasizing PowerShell references unless necessary for a Windows-specific workflow.
  • Ensure that all prerequisite links and instructions are equally accessible and clear for Linux/macOS users.
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-01 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 the PowerShell example is given equal prominence and detail as the CLI example. Azure PowerShell is primarily used on Windows, and the documentation does not mention Bash or shell alternatives for Linux/macOS users. The CLI example uses a command ('dig') that is not universally available on Windows, but is standard on Linux/macOS, while the PowerShell example is Windows-centric. The rest of the documentation is portal-focused and platform-neutral.
Recommendations
  • Explicitly note that Azure CLI commands can be run in Bash on Linux/macOS and in Cloud Shell for all platforms.
  • Provide Bash shell alternatives for retrieving the public IP address (e.g., 'curl ifconfig.me' or 'curl ipinfo.io/ip') for Linux/macOS users.
  • Clarify that Azure PowerShell is primarily for Windows users, and suggest Azure CLI for cross-platform compatibility.
  • Consider listing Azure CLI (Bash) examples first, as CLI is more widely used across platforms.
GitHub Create Pull Request
Aks Configure LocalDNS in Azure Kubernetes Service (AKS) ...ure-aks-docs/blob/main/articles/aks/localdns-custom.md
Low Priority View Details →
Scanned: 2026-03-01 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation page provides links to AKS cluster creation guides for Azure CLI, PowerShell, and Portal, with PowerShell mentioned alongside CLI and Portal. However, all command examples and instructions use Azure CLI and kubectl, which are cross-platform tools. No Windows-specific tools, patterns, or PowerShell-only examples are present. The documentation explicitly states LocalDNS is only supported on Azure Linux or Ubuntu 22.04+ node pools, and all operational guidance is Linux-centric. The only minor bias is mentioning Azure PowerShell as an option for cluster creation before Linux-specific alternatives, but this does not affect the main LocalDNS configuration workflow.
Recommendations
  • Consider listing Azure CLI and Portal options before PowerShell in the prerequisites section, or clarify that all subsequent instructions are CLI-based and cross-platform.
  • Explicitly state that Azure CLI and kubectl commands work on Windows, Linux, and macOS to reinforce platform parity.
  • If possible, provide a brief note that PowerShell is not required for LocalDNS configuration and that all steps are platform-agnostic.
GitHub Create Pull Request
Aks Develop on Azure Kubernetes Service (AKS) with Helm ...ure-aks-docs/blob/main/articles/aks/quickstart-helm.md
Low Priority View Details →
Scanned: 2026-03-01 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 Azure-related tasks, but consistently presents Azure CLI (which is cross-platform) before Azure PowerShell (which is Windows-centric). There are no explicit Windows-only tools or patterns, and Linux/macOS users can complete all tasks using Azure CLI and bash commands. However, the presence of PowerShell examples and references may create minor friction for Linux/macOS users, as PowerShell is less commonly used on those platforms.
Recommendations
  • Consider clarifying that Azure CLI is recommended for Linux/macOS users, while PowerShell is primarily for Windows users.
  • Optionally, add a note at the top indicating that Azure CLI is cross-platform and preferred for non-Windows environments.
  • Ensure that bash commands and Azure CLI examples are prominent and clearly marked as suitable for Linux/macOS.
  • If possible, provide bash-only quickstart sections for Linux/macOS users to streamline their experience.
GitHub Create Pull Request
Aks Kubernetes on Azure tutorial - Create an Azure Kubernetes Service (AKS) cluster ...ain/articles/aks/tutorial-kubernetes-deploy-cluster.md
Low Priority View Details →
Scanned: 2026-03-01 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides parallel instructions for Azure CLI, Azure PowerShell, and Azure Developer CLI, but PowerShell examples and references are prominent throughout. PowerShell is a Windows-centric tool, and its inclusion alongside Azure CLI (which is cross-platform) may create friction for Linux/macOS users. Additionally, PowerShell instructions are often presented immediately after Azure CLI, which may subtly reinforce Windows as a primary platform. However, Azure CLI is always present and is shown first, and all commands are cross-platform compatible. No critical steps are Windows-only, and Linux/macOS users can complete the tutorial without issue.
Recommendations
  • Consider clarifying that Azure PowerShell is primarily for Windows users, while Azure CLI is cross-platform.
  • Explicitly mention that Azure CLI commands work on Linux/macOS and Windows, and that PowerShell is optional.
  • Add a brief note in the 'Before you begin' section about platform compatibility for each tool.
  • If possible, provide Bash shell examples for Linux/macOS users, especially for environment variable setup and SSH key management.
  • Ensure that Azure CLI is always presented as the default or recommended method for cross-platform parity.
GitHub Create Pull Request
Aks Secure Pod Traffic with Network Policies in Azure Kubernetes Service (AKS) ...ks-docs/blob/main/articles/aks/use-network-policies.md
Low Priority View Details →
Scanned: 2026-03-01 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides examples for both Linux and Windows node pools in AKS, but Windows-specific steps (such as registering preview features and creating Windows admin credentials) are presented in detail and before Linux equivalents. The Windows section is more verbose and includes additional steps, while Linux instructions are concise. All CLI examples use Azure CLI and Bash, which are cross-platform, but there are no PowerShell-specific examples. However, Windows-specific configuration steps are described in depth, potentially creating friction for Linux/macOS users seeking parity.
Recommendations
  • Ensure Linux and Windows instructions are equally detailed and placed in parallel sections.
  • Clearly separate Linux and Windows steps, labeling them for each OS to avoid confusion.
  • Add explicit notes when steps are Windows-only or Linux-only, and provide links to Linux-specific guidance where appropriate.
  • Consider providing PowerShell examples for Windows users and Bash examples for Linux/macOS users, or clarify that Azure CLI commands are cross-platform.
  • Review the order of presentation to avoid Windows-first bias unless the feature is Windows-specific.
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-02-28 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides troubleshooting steps for the Agentic CLI for AKS, with some bias toward Windows/macOS users. In Docker-related troubleshooting, Windows/macOS solutions (Docker Desktop) are listed before Linux solutions, and restarting Docker Desktop is emphasized for permission issues. No PowerShell commands are present, but Azure CLI and kubectl commands are used throughout, which are cross-platform. However, Windows/macOS tools (Docker Desktop) are mentioned first and more prominently than Linux equivalents. Linux-specific steps are present but often secondary.
Recommendations
  • Present Linux and Windows/macOS troubleshooting steps in parallel or with equal prominence, rather than listing Windows/macOS first.
  • Clarify that Docker Desktop is not available on Linux and provide explicit guidance for Linux users (e.g., systemctl commands) before or alongside Windows/macOS instructions.
  • Where possible, add notes about cross-platform command usage and highlight any OS-specific differences.
  • Consider grouping troubleshooting steps by OS or providing a table for quick reference.
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-02-28 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 some prerequisite steps, but Azure CLI is used exclusively for all main examples. However, PowerShell is mentioned first in the 'Before you begin' section, and a PowerShell cmdlet is referenced alongside Azure CLI for subnet listing. There are no Linux/macOS-specific examples or explicit parity guidance, but the main workflow is cross-platform via Azure CLI and kubectl. The bias is minor, mostly in tool mention order and occasional PowerShell references.
Recommendations
  • Mention Azure CLI before PowerShell in prerequisite lists to reflect cross-platform parity.
  • Clarify that Azure CLI and kubectl commands work on Linux, macOS, and Windows.
  • Add explicit notes or links for Linux/macOS users where PowerShell is referenced (e.g., suggest Azure CLI as the primary tool for subnet listing).
  • Consider removing PowerShell references unless a Windows-specific workflow is required.
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-02-28 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides installation and usage instructions for the Agentic CLI for AKS, supporting both client mode (local Docker) and cluster mode (Helm/Kubernetes). In the section on starting the Docker daemon, instructions for macOS/Windows (Docker Desktop) are presented before Linux (systemctl commands). However, all examples and instructions are cross-platform, and Linux-specific guidance is present where relevant. No PowerShell-specific commands, Windows-only tools, or missing Linux examples are found.
Recommendations
  • Present Linux instructions before or alongside Windows/macOS instructions when describing how to start Docker, to avoid subtle ordering bias.
  • Explicitly mention that all commands are compatible with Linux, macOS, and Windows where applicable.
  • Consider adding a short note clarifying that Docker Desktop is not required on Linux, and that Linux users should use their package manager and systemctl.
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-28 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation is generally cross-platform and AKS-focused, but there are minor signs of Windows bias. In the section 'Verify TLS Bootstrapping is enabled on current agent node pool', Windows file paths are mentioned alongside Linux, but Windows is listed second. There are no PowerShell-specific commands or Windows-only tools; all CLI examples use Azure CLI and bash/kubectl, which are cross-platform. However, Azure CLI is more natively available on Linux/macOS, and Windows users may need WSL or install bash. The documentation does not provide PowerShell alternatives or Windows command prompt examples, but it does mention Windows node file paths for completeness.
Recommendations
  • Ensure that Windows and Linux file paths are always presented together, and clarify which commands work natively on Windows (e.g., Azure CLI in PowerShell or Command Prompt).
  • Consider adding PowerShell or Windows Command Prompt equivalents for Azure CLI commands where relevant, or clarify that Azure CLI works in all environments.
  • Explicitly state that all examples are cross-platform unless otherwise noted.
  • For file path references, consider listing Windows and Linux paths in parallel, rather than Linux first.
GitHub Create Pull Request
Aks Concepts - Storage in Azure Kubernetes Services (AKS) ...re-aks-docs/blob/main/articles/aks/concepts-storage.md
Low Priority View Details →
Scanned: 2026-02-28 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides both Linux and Windows container examples for volume mounting, but the Windows example is presented immediately after the Linux example without additional context or parity. There are no PowerShell or Windows-specific CLI examples, nor are Windows tools or patterns mentioned preferentially. The only Windows-specific mention is in the context of mounting volumes in Windows containers, which is appropriate and necessary for completeness.
Recommendations
  • Ensure that Linux/macOS and Windows examples are clearly separated and labeled to avoid confusion.
  • If providing Windows-specific examples, consider also providing equivalent Linux/macOS examples side-by-side for clarity.
  • Add clarifying notes when Windows-specific instructions are given, indicating that Linux/macOS users should refer to the preceding example or section.
  • Review the order of examples to ensure Linux/macOS instructions are not consistently shown after Windows instructions unless contextually appropriate.
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-28 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 prominent and detailed, and PowerShell is historically associated with Windows, though it is now cross-platform. PowerShell instructions and references are given before Azure CLI, and the PowerShell section includes more guidance about Cloud Shell and local installation. However, the CLI section is present and includes Linux/macOS installation links. No critical steps are Windows-only, and Linux/macOS users can complete all tasks.
Recommendations
  • Ensure parity in example detail between PowerShell and CLI sections (e.g., add more CLI guidance about Cloud Shell usage if relevant).
  • Explicitly mention that both PowerShell and CLI are cross-platform and suitable for Linux/macOS users.
  • Consider showing CLI examples before PowerShell, as CLI is more commonly used on Linux/macOS.
  • Add a brief note clarifying that PowerShell is available on Linux/macOS, to avoid confusion.
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-02-28 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation is generally cross-platform and AKS/Linux-focused, but there are minor signs of Windows bias. Windows path conventions and tools are mentioned in a few places, sometimes before Linux equivalents. In the 'Use Azure Files with Windows containers' section, Windows-specific instructions are provided, but Linux/MacOS Bash is also referenced. In some command examples, Windows paths are shown alongside Linux, but Windows is sometimes listed first. Azure CLI is used throughout, which is available cross-platform, but some commands reference Windows-specific path conventions.
Recommendations
  • When mentioning Windows path conventions or tools, ensure Linux/macOS equivalents are given equal prominence and listed first where appropriate.
  • Where commands differ between platforms, provide both Linux/macOS and Windows examples side-by-side, with clear labeling.
  • Review example outputs and instructions to ensure Linux/macOS users are not confused by Windows-centric language or ordering.
  • Consider adding a short section clarifying cross-platform compatibility for Azure CLI and kubectl commands.
  • In sections where Windows is mentioned, clarify if the instructions are Windows-only or if Linux/macOS users should follow different steps.
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-02-28 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation references Azure PowerShell as a migration option alongside Azure CLI and Azure Portal, but does not provide Linux-specific guidance or examples for PowerShell usage. Azure CLI is used for all command-line examples, which is cross-platform, but the mention of Azure PowerShell as a migration tool without clarifying Linux/macOS support or providing parity examples may create confusion. Additionally, the order of tools listed (Portal, PowerShell, CLI) puts Windows-centric tools before CLI, which is more universal.
Recommendations
  • Clarify that Azure PowerShell is available on Linux/macOS and provide installation/use guidance if relevant.
  • Consider listing Azure CLI before Azure PowerShell in tool options, as CLI is more universally supported.
  • If PowerShell is mentioned, provide explicit Linux/macOS usage instructions or note any limitations.
  • Ensure that all example commands use cross-platform tools (Azure CLI, kubectl), as is currently done.
  • Add a brief note that all steps are applicable to Linux/macOS unless otherwise stated.
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-28 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 cluster authorized IP ranges, but consistently presents Azure CLI (Linux/macOS-friendly) examples first. However, PowerShell examples are also included, and no Windows-specific tools or patterns are mentioned exclusively. The rest of the documentation is portal-centric and platform-neutral, with YAML examples targeting Linux node pools. There is no missing Linux example or Windows-only tool bias.
Recommendations
  • Maintain Azure CLI examples as the primary cross-platform option, but clarify that Azure CLI works on Windows, Linux, and macOS.
  • Consider adding a brief note that Azure PowerShell is primarily used on Windows but can also be run on Linux/macOS if needed.
  • Ensure that all CLI instructions are explicitly cross-platform, and avoid implying PowerShell is required for Windows users.
  • If possible, add a Bash example for IP retrieval (e.g., `curl ifconfig.me`) for Linux/macOS users alongside the Azure CLI example.
GitHub Create Pull Request
Aks Develop on Azure Kubernetes Service (AKS) with Helm ...ure-aks-docs/blob/main/articles/aks/quickstart-helm.md
Low Priority View Details →
Scanned: 2026-02-28 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 Azure-related operations, but does not offer Linux-specific shell examples (e.g., Bash scripts for Azure CLI usage) or mention Linux/macOS-specific patterns. Azure PowerShell is featured equally alongside Azure CLI, which is more commonly used on Windows. The ordering of examples sometimes puts Azure CLI first, but PowerShell is always present. There are no Windows-only tools or commands, but the PowerShell parity may create friction for Linux/macOS users unfamiliar with PowerShell.
Recommendations
  • Clarify that Azure CLI commands are cross-platform and can be used on Linux/macOS as well as Windows.
  • Consider adding explicit Bash shell examples for Azure CLI usage, or note that Azure CLI commands can be run in Bash, Zsh, or other Unix shells.
  • De-emphasize Azure PowerShell for general-purpose AKS/Helm workflows unless there is a Windows-specific need.
  • Add notes or guidance for Linux/macOS users about installing Azure CLI and Helm on their platforms.
  • Ensure that any references to Azure Cloud Shell mention its availability from Linux/macOS browsers.
GitHub Create Pull Request
Aks Kubernetes on Azure tutorial - Create an Azure Kubernetes Service (AKS) cluster ...ain/articles/aks/tutorial-kubernetes-deploy-cluster.md
Low Priority View Details →
Scanned: 2026-02-28 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides parallel instructions for Azure CLI, Azure PowerShell, and Azure Developer CLI, but PowerShell is featured prominently and is presented as an equal alternative to Azure CLI. PowerShell is primarily a Windows tool, and its inclusion may signal a Windows-centric approach. However, Azure CLI instructions are present and are suitable for Linux/macOS users. There are no missing Linux examples, and the tools used (Azure CLI, kubectl) are cross-platform. The ordering sometimes places PowerShell before Azure CLI, which could be seen as minor bias.
Recommendations
  • Clearly indicate that Azure PowerShell is primarily for Windows users, and recommend Azure CLI for Linux/macOS.
  • Ensure Azure CLI instructions are always presented first, as it is the most cross-platform tool.
  • Add explicit notes clarifying that all Azure CLI and kubectl commands work on Linux/macOS, and provide links to Linux/macOS installation guides.
  • Consider removing PowerShell instructions from sections where they are not relevant for Linux/macOS users, or move them to a separate section for Windows users.
GitHub Create Pull Request
Aks Secure Pod Traffic with Network Policies in Azure Kubernetes Service (AKS) ...ks-docs/blob/main/articles/aks/use-network-policies.md
Low Priority View Details →
Scanned: 2026-02-28 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Linux and Windows examples for AKS network policy configuration, but Windows-specific instructions (such as registering feature flags and creating Windows admin credentials) are given their own prominent section and are detailed before Linux equivalents in some places. The Windows node pool setup is described in depth, including Azure CLI steps and Windows-specific parameters. However, Linux examples are present and complete, and the main workflow is cross-platform. There is a slight bias toward Windows in the ordering and detail of instructions, but Linux users can complete all tasks without significant friction.
Recommendations
  • Ensure Linux instructions are presented first or equally alongside Windows instructions, especially in sections where both are relevant.
  • Where Windows-specific steps are described, provide clear separation and context so Linux users can easily skip irrelevant steps.
  • Add explicit notes clarifying which steps are platform-specific and which are universal.
  • Consider adding a summary table at the start showing which network policy engines are recommended for each OS, with links to relevant sections.
GitHub Create Pull Request
← Previous Page 9 of 25 Next →