Aks

535
Total Pages
430
Linux-Friendly Pages
105
Pages with Bias
19.6%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

354 issues found
Showing 76-100 of 354 flagged pages
Aks Supported Kubernetes Versions in Azure Kubernetes Service (AKS) ...lob/main/articles/aks/supported-kubernetes-versions.md
Low Priority View Details →
Scanned: 2026-02-17 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. There are no Linux-specific commands or shell examples (e.g., Bash), but Azure CLI is cross-platform and covers Linux/macOS users. No Windows-only tools or patterns are mentioned outside of PowerShell. No critical tasks are Windows-only, and Linux support is clearly documented in component tables.
Recommendations
  • Explicitly mention that Azure CLI is cross-platform and recommended for Linux/macOS users.
  • Add Bash shell examples for common tasks (e.g., checking Kubernetes version, installing kubectl) to further improve Linux parity.
  • Clarify in relevant sections (e.g., 'Alias minor version', 'Azure portal and CLI versions') that Azure CLI commands work on Linux/macOS.
  • Consider adding a note that Azure PowerShell is primarily for Windows users, while Azure CLI is for all platforms.
GitHub Create Pull Request
Aks Azure Kubernetes Service (AKS) Managed Gateway API Installation (preview) ...aks-docs/blob/main/articles/aks/managed-gateway-api.md
Low Priority View Details →
Scanned: 2026-02-17 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation primarily uses Azure CLI commands and kubectl, which are cross-platform, but does not explicitly mention Linux/macOS compatibility or provide Linux/macOS-specific instructions. All examples are shown generically, but there is a subtle bias in not clarifying that these commands work equally well on Linux/macOS. There are no Windows-specific tools or PowerShell examples, but the lack of explicit Linux/macOS guidance may create minor friction for non-Windows users.
Recommendations
  • Add a note clarifying that Azure CLI and kubectl commands are fully supported on Linux and macOS, not just Windows.
  • Include example commands for Linux/macOS where relevant, such as installation instructions for Azure CLI and jq.
  • Mention any OS-specific prerequisites or differences, if applicable (e.g., how to install Azure CLI or jq on Linux/macOS).
  • Ensure links to Azure CLI installation documentation include Linux/macOS options.
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-16 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 API server authorized IP ranges, but consistently presents Azure CLI (Linux/macOS-friendly) examples first. However, PowerShell examples are also included, which may be more relevant to Windows users. No Windows-only tools or patterns are mentioned, and all instructions are portal-based or cross-platform. There are no missing Linux examples, and Linux node selectors are used in the YAML, indicating Linux parity.
Recommendations
  • Maintain Azure CLI examples as the primary cross-platform option.
  • Continue to provide both Azure CLI and PowerShell examples, but clarify that Azure CLI works on Windows, Linux, and macOS.
  • Consider adding brief notes about using Cloud Shell for cross-platform access.
  • Ensure screenshots and portal instructions do not reference Windows-specific UI elements.
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-16 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation is generally cross-platform and AKS is a Linux-first service, but there is mild Windows bias in the section 'Verify TLS Bootstrapping is enabled on current agent node pool', where Windows node paths are mentioned alongside Linux paths, but the Windows path is listed second. There are no PowerShell or Windows-specific command examples, and all CLI/script examples use Bash or Azure CLI, which are cross-platform. However, there are no explicit Linux/macOS instructions for accessing Windows node paths, nor are there Linux/macOS-specific troubleshooting tips. The documentation could improve Linux parity by clarifying access methods for both OS types and ensuring Linux examples are always present and clear.
Recommendations
  • Ensure all file path examples for both Linux and Windows nodes are accompanied by clear instructions for accessing them from Linux/macOS and Windows environments.
  • Add troubleshooting tips or access methods for Linux/macOS users when interacting with Windows node pools, if relevant.
  • Consider listing Linux examples first, as AKS is primarily Linux-based.
  • Explicitly state when a command or path is OS-specific and provide alternatives where possible.
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-16 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides installation and usage instructions for the Agentic CLI for AKS, with a slight preference for Windows/macOS patterns in Docker startup instructions and verification steps. While most commands are cross-platform (Azure CLI, Bash), the instructions for starting Docker daemon mention Windows/macOS (Docker Desktop) before Linux (systemctl), and verification steps for client mode cleanup use Windows-style paths (e.g., ~/.azure/aksAgent.config) without explicit Linux/macOS parity. There are no PowerShell-specific commands, but the ordering and phrasing sometimes prioritize Windows/macOS tools and workflows.
Recommendations
  • Ensure that Linux instructions are given equal prominence and detail as Windows/macOS instructions, especially for Docker startup and verification.
  • Provide explicit Linux/macOS example paths and commands where relevant (e.g., configuration file locations, Docker image cleanup).
  • Consider adding a table or section that summarizes OS-specific steps for Docker installation, startup, and troubleshooting.
  • When mentioning Docker Desktop, clarify that it is not available on Linux and provide Linux alternatives first or equally.
  • Review all example commands and outputs for OS-specific assumptions; add notes or alternatives for Linux/macOS users where needed.
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-16 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 Azure CLI is cross-platform, the PowerShell section is prominent and detailed, with instructions for installing/upgrading PowerShell on Windows, macOS, and Linux. However, PowerShell is traditionally associated with Windows, and its section appears before the CLI section. The CLI section uses bash-style syntax, which is more familiar to Linux/macOS users, but is presented after PowerShell. There are no missing Linux examples, and Azure CLI is well-supported.
Recommendations
  • Consider presenting Azure CLI examples before PowerShell, as CLI is more universally used across platforms.
  • Explicitly mention that Azure CLI commands work on Linux/macOS/Windows and highlight its cross-platform nature.
  • Add brief notes clarifying that PowerShell is available on Linux/macOS, but Azure CLI is often preferred for Linux users.
  • Ensure parity in detail and guidance between PowerShell and CLI sections.
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-16 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 to Windows/PowerShell tools (e.g., Get-AzVirtualNetworkSubnetConfig) are present. Azure CLI is used for all main examples, which is cross-platform, but PowerShell is mentioned alongside Azure CLI in the 'Before you begin' section and for subnet listing. The PowerShell cmdlet is referenced before its Linux equivalent (Azure CLI) in the subnet listing section. No Linux/macOS-specific friction is present, but Windows tools are referenced and sometimes listed first.
Recommendations
  • When listing prerequisite tools, mention Azure CLI first as it is cross-platform, and clarify that PowerShell is optional for Windows users.
  • For subnet listing, provide Azure CLI as the primary example and mention PowerShell only as an alternative for Windows users.
  • Consider adding explicit notes that all Azure CLI commands work on Linux/macOS, and that PowerShell is only required for Windows environments.
  • Avoid referencing Windows tools (PowerShell) unless necessary, and always provide a Linux/macOS equivalent.
  • Where possible, use Azure CLI for all examples to maximize cross-platform accessibility.
GitHub Create Pull Request
Aks Troubleshoot the Agentic CLI for Azure Kubernetes Service (AKS) ...ob/main/articles/aks/cli-agent-for-aks-troubleshoot.md
Low Priority View Details →
Scanned: 2026-02-16 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation generally provides cross-platform troubleshooting steps for the Agentic CLI for AKS, but in several Docker-related sections, Windows/macOS instructions (Docker Desktop) are listed before Linux equivalents, and there is a heavier emphasis on Docker Desktop (a Windows/macOS tool) compared to Linux-native Docker management. No PowerShell-specific commands are present, but the pattern of mentioning Windows/macOS first and referencing Docker Desktop as the primary tool for those platforms indicates a mild Windows bias. All critical tasks are covered for Linux, so Linux users are not blocked.
Recommendations
  • Alternate the order of platform instructions (sometimes list Linux first) to avoid implicit prioritization of Windows/macOS.
  • Where Docker Desktop is mentioned, clarify that on Linux, Docker is typically managed via systemd and the CLI, and that Docker Desktop is not required.
  • Add explicit notes that all commands are supported on Linux, macOS, and Windows, and clarify any platform-specific differences.
  • If possible, provide Linux/macOS-specific troubleshooting screenshots or examples alongside Windows ones.
GitHub Create Pull Request
Aks Install the Dapr extension for Azure Kubernetes Service (AKS) and Arc-enabled Kubernetes ...softDocs/azure-aks-docs/blob/main/articles/aks/dapr.md
Low Priority View Details →
Scanned: 2026-02-16 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation is generally cross-platform, focusing on Azure CLI and Bicep (both platform-agnostic). However, in the 'Listing the CRDs in your cluster' section, the example uses 'kubectl get crds | findstr dapr.io', which is a Windows/PowerShell pattern. No equivalent Linux/macOS example (using 'grep') is provided. Additionally, the use of 'findstr' appears before any mention of 'grep', which is absent.
Recommendations
  • Provide both Windows and Linux/macOS examples for commands involving shell utilities. For example, add 'kubectl get crds | grep dapr.io' alongside the 'findstr' example.
  • Clarify that Azure CLI and Bicep commands work on all platforms, and explicitly mention this in the prerequisites.
  • Where shell commands are shown, use platform-neutral language or offer alternatives for both environments.
GitHub Create Pull Request
Aks Azure Kubernetes Service (AKS) Managed Gateway API Installation (preview) ...aks-docs/blob/main/articles/aks/managed-gateway-api.md
Low Priority View Details →
Scanned: 2026-02-16 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation primarily uses Azure CLI examples, which are cross-platform, and includes kubectl commands that work on Linux/macOS/Windows. However, the Azure CLI examples are shown using the 'azurecli-interactive' code block, which is sometimes associated with Windows/PowerShell environments, and there is no explicit mention of Linux/macOS compatibility or alternative instructions for those platforms. The order of examples and instructions does not show explicit Linux bias, but Windows users may perceive the CLI examples as more familiar due to the lack of Linux-specific context.
Recommendations
  • Clarify that Azure CLI and kubectl commands are cross-platform and can be run on Linux, macOS, and Windows.
  • Add a short note in the prerequisites or introduction indicating that all CLI instructions are compatible with Bash (Linux/macOS) and PowerShell (Windows).
  • Consider including example commands for Bash and PowerShell if there are any platform-specific differences.
  • Explicitly mention that the Azure CLI can be installed and used on Linux/macOS, with a link to installation instructions for those platforms.
GitHub Create Pull Request
Aks Kubernetes on Azure tutorial - Upgrade an Azure Kubernetes Service (AKS) cluster ...in/articles/aks/tutorial-kubernetes-upgrade-cluster.md
Low Priority View Details →
Scanned: 2026-02-16 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The tutorial provides parity between Azure CLI, Azure PowerShell, and Azure portal for all AKS upgrade tasks. However, Azure PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and in some sections, PowerShell examples are shown before CLI. There is no explicit Linux/macOS bias, but the heavy inclusion of PowerShell may create friction for Linux/macOS users, as PowerShell is less commonly used on those platforms. No Windows-only tools or patterns are mentioned, and all commands are cross-platform via Azure CLI or portal.
Recommendations
  • Make Azure CLI the primary or first example in each section, as it is cross-platform and more widely used on Linux/macOS.
  • Clarify that Azure PowerShell is optional and primarily for users already familiar with it.
  • Consider adding a note that Azure CLI is recommended for Linux/macOS users.
  • Ensure that all screenshots and instructions are neutral or show Azure CLI/portal where possible.
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-16 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 throughout, but PowerShell is featured equally alongside CLI, which is more commonly used on Windows. There are no explicit Linux/macOS-specific instructions or examples, and the PowerShell sections may be less relevant for Linux/macOS users. Azure CLI is cross-platform, but the documentation does not clarify this or prioritize CLI examples. The use of PowerShell is not exclusive, but its presence may create confusion or friction for Linux/macOS users.
Recommendations
  • Explicitly state that Azure CLI is cross-platform and recommended for Linux/macOS users.
  • Consider presenting Azure CLI examples first, or labeling them as the default for non-Windows platforms.
  • Add brief notes clarifying that PowerShell examples are primarily for Windows users.
  • Include a short section or callout for Linux/macOS users, confirming that all steps can be completed with Azure CLI and bash.
  • Ensure that any shell commands (e.g., git, helm, kubectl) are shown in bash syntax, and clarify compatibility.
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-16 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation covers both Linux and Windows scenarios for AKS network policies, but Windows-specific instructions and tools (such as Windows admin credentials setup and feature flag registration) are presented before or alongside Linux equivalents. Windows node pool creation steps are detailed separately and prominently, and Windows-specific limitations and features are discussed in depth. However, Linux examples and instructions are also present and complete, and the page is not Windows-exclusive.
Recommendations
  • Ensure Linux instructions/examples are presented first in each section unless Windows is the primary focus.
  • Clearly separate Linux and Windows instructions with headings for easier navigation.
  • Add explicit notes when a command or step is Windows-only, and provide Linux equivalents where possible.
  • Consider grouping Windows-specific steps (such as admin credential setup and feature flag registration) in a dedicated section to avoid interleaving with Linux steps.
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-15 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation is generally cross-platform and AKS is a Linux-first service, but there are minor signs of Windows bias. In the section 'Verify TLS Bootstrapping is enabled on current agent node pool', the Windows file path is mentioned immediately after the Linux path, but no explicit example is given for how to check on Windows. Additionally, throughout the document, all command-line examples use Azure CLI and bash/kubectl, which are Linux/macOS-friendly, but there are no PowerShell or Windows Command Prompt examples for Windows users. However, the document does not exclusively favor Windows tools or patterns, and Linux parity is mostly maintained.
Recommendations
  • Provide explicit Windows command examples (e.g., PowerShell or Command Prompt) for checking certificate expiration and TLS Bootstrapping, especially when referencing Windows file paths.
  • Clarify any differences in procedure for Windows node pools, if applicable.
  • When mentioning file paths for both Linux and Windows, consider giving a brief example for each platform.
  • Ensure that all steps that reference file paths or commands are clear for both Linux and 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-15 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides cross-platform instructions for installing and using the Agentic CLI for AKS, but in the Docker daemon startup section, Windows/macOS instructions (Docker Desktop) are mentioned before Linux instructions (systemctl). All other examples and commands are platform-neutral (Azure CLI, Docker, kubectl), and Linux-specific guidance is present where relevant.
Recommendations
  • In the 'Start the Docker daemon' section, present Linux instructions before or alongside Windows/macOS instructions, or clarify that all platforms are equally supported.
  • Consider explicitly stating that all commands (Azure CLI, Docker, kubectl) work on Linux, macOS, and Windows, and provide links to platform-specific installation guides where relevant.
  • If possible, add a brief note that Docker Desktop is not available on Linux, and that Linux users should use systemd/systemctl.
GitHub Create Pull Request
Aks Troubleshoot the Agentic CLI for Azure Kubernetes Service (AKS) ...ob/main/articles/aks/cli-agent-for-aks-troubleshoot.md
Low Priority View Details →
Scanned: 2026-02-15 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Missing Minor Windows Tools
Summary
The documentation provides troubleshooting steps for the agentic CLI for AKS, with Docker-related issues addressed for macOS/Windows and Linux separately. Windows and macOS instructions are grouped together and presented before Linux in several places. There are no PowerShell-specific examples, but Windows users are directed to use Docker Desktop, a Windows/macOS-specific tool, while Linux users are given command-line instructions. All Azure CLI and Kubernetes commands are cross-platform. No critical troubleshooting steps are Windows-only, and Linux parity is generally maintained.
Recommendations
  • Where possible, provide Linux instructions before or alongside Windows/macOS instructions, rather than after.
  • Explicitly mention that Docker Desktop is not available for Linux and clarify alternatives for Linux users.
  • Consider adding PowerShell examples for Windows users if Bash is not the default shell, or clarify that Bash commands work in Windows Terminal.
  • Ensure that all troubleshooting steps are equally detailed for Linux, macOS, and Windows users.
GitHub Create Pull Request
Aks Install the Dapr extension for Azure Kubernetes Service (AKS) and Arc-enabled Kubernetes ...softDocs/azure-aks-docs/blob/main/articles/aks/dapr.md
Low Priority View Details →
Scanned: 2026-02-15 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation is largely platform-agnostic, focusing on Azure CLI and Bicep for managing the Dapr extension on AKS and Arc-enabled Kubernetes clusters. However, there is a minor Windows bias in the CRD deletion section, where the example for listing CRDs uses PowerShell's 'findstr' command with 'kubectl', which is Windows-specific. This command is shown without a Linux/macOS alternative (e.g., using 'grep'). Additionally, the PowerShell example is presented first and exclusively in that context.
Recommendations
  • Provide Linux/macOS equivalents for commands that use Windows-specific tools (e.g., show 'kubectl get crds | grep dapr.io' alongside the PowerShell 'findstr' example).
  • When giving shell command examples, consider presenting both Windows and Linux/macOS versions, or use cross-platform commands where possible.
  • Explicitly state that the command works on Windows and provide alternatives for other platforms to improve accessibility.
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-15 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides three parallel approaches: Azure portal, Azure PowerShell, and Azure CLI. The PowerShell section is prominent and detailed, with explicit instructions for installation and usage across Windows, macOS, and Linux. However, PowerShell is a Windows-centric tool, and its section appears before the Azure CLI, which is more native to Linux/macOS users. There are no missing Linux examples, as Azure CLI is included and installation links for PowerShell on Linux/macOS are present. The ordering and emphasis on PowerShell may create minor friction for Linux/macOS users.
Recommendations
  • Consider placing the Azure CLI section before the Azure PowerShell section, as CLI is more cross-platform and native to Linux/macOS.
  • Explicitly mention that Azure CLI is recommended for Linux/macOS users.
  • Add a short note clarifying that PowerShell is available cross-platform, but Azure CLI is often preferred on Linux/macOS.
  • Ensure that all code blocks and instructions are equally clear for both CLI and PowerShell users.
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-15 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 tasks, but consistently mentions Azure PowerShell alongside Azure CLI and portal as ways to create an AKS cluster. In the section on listing subnets, both Azure CLI and PowerShell are referenced, but PowerShell is mentioned after Azure CLI. No PowerShell-specific examples are shown for core AKS operations, which are all demonstrated with kubectl and Azure CLI. There are no Linux/macOS-specific examples or explicit parity notes, but the overall guidance is cross-platform, with only minor bias toward Windows tools.
Recommendations
  • Clarify that Azure PowerShell is optional and primarily for Windows users; consider listing Azure CLI first in all cases.
  • Add explicit notes that Azure CLI and kubectl commands work on Linux/macOS as well as Windows.
  • Where PowerShell is mentioned, provide equivalent Bash or shell scripting examples for Linux/macOS users.
  • Consider removing PowerShell references from core AKS workflow unless a Windows-specific scenario is being described.
GitHub Create Pull Request
Aks Azure Kubernetes Service (AKS) Managed Gateway API Installation (preview) ...aks-docs/blob/main/articles/aks/managed-gateway-api.md
Low Priority View Details →
Scanned: 2026-02-15 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation primarily uses Azure CLI examples, which are cross-platform, and includes kubectl commands that work on Linux/macOS/Windows. However, all CLI examples are shown in the Azure CLI interactive block, which may be perceived as Windows-first due to the historical association of Azure CLI with Windows/PowerShell. There are no PowerShell-specific commands or Windows-only tools mentioned, and Linux/macOS users can complete all tasks as described. The order of examples does not explicitly favor Windows, but there is a minor bias in not mentioning Linux/macOS usage or shell compatibility.
Recommendations
  • Explicitly state that Azure CLI and kubectl commands are cross-platform and work on Linux/macOS/Windows.
  • Add a note or section clarifying that all examples are compatible with Bash, Zsh, and other common Linux/macOS shells.
  • Consider including example commands for Bash and PowerShell if there are any syntax differences.
  • Mention that Azure CLI can be installed and used on Linux/macOS, linking to installation instructions.
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-15 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). However, there is a slight bias in the troubleshooting section where PowerShell is given equal prominence, and no explicit Linux/macOS shell example (e.g., Bash) is provided for retrieving the public IP address. All other instructions are portal-based and platform-neutral.
Recommendations
  • Add explicit Bash shell examples for Linux/macOS users to retrieve their public IP address (e.g., `curl ifconfig.me`).
  • Clarify that Azure CLI commands work cross-platform and can be run in Bash, Zsh, or other shells.
  • Consider mentioning that Azure PowerShell is primarily for Windows users, while Azure CLI is cross-platform.
  • If possible, provide a table or clear separation of instructions for Windows, Linux, and macOS users.
GitHub Create Pull Request
Aks Kubernetes on Azure tutorial - Upgrade an Azure Kubernetes Service (AKS) cluster ...in/articles/aks/tutorial-kubernetes-upgrade-cluster.md
Low Priority View Details →
Scanned: 2026-02-15 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides parity between Azure CLI, Azure PowerShell, and Azure portal for all AKS upgrade tasks. However, Azure PowerShell (which is most commonly used on Windows) is given equal prominence to Azure CLI, and PowerShell examples are included throughout. There is a minor bias in that PowerShell is featured heavily, and the documentation sometimes lists PowerShell before Linux-native tools or patterns. No critical Linux/macOS friction is present, as Azure CLI is fully supported cross-platform and all tasks can be completed with CLI or portal.
Recommendations
  • Consider listing Azure CLI examples before Azure PowerShell in each section, as CLI is cross-platform and more widely used on Linux/macOS.
  • Explicitly note that Azure CLI is recommended for Linux/macOS users, and PowerShell is primarily for Windows users.
  • Where possible, clarify that Azure PowerShell is available cross-platform, but is most commonly used on Windows.
  • Ensure that all screenshots and output examples are not Windows-specific (e.g., avoid PowerShell console screenshots unless necessary).
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-15 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 commands, and Linux/macOS users are not excluded from any steps. Bash commands are used for Helm and kubectl operations, which are cross-platform. However, the PowerShell examples are unnecessary for Linux/macOS users, and their inclusion may create minor friction or confusion.
Recommendations
  • Clearly indicate that Azure PowerShell is primarily for Windows users, and Azure CLI is recommended for Linux/macOS.
  • Consider grouping Azure CLI and PowerShell examples under separate headings, or use tabs labeled 'Windows' and 'Linux/macOS' to clarify relevance.
  • Add a note at the top of the page stating that Azure CLI is cross-platform and preferred for Linux/macOS.
  • Optionally, provide only Azure CLI examples in the main flow, with PowerShell examples in 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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation provides both Linux and Windows examples for AKS network policy engines, but Windows-specific instructions (such as administrator credential setup and feature flag registration) are given their own section and are presented immediately after the Linux section. Windows node pool creation steps are detailed, including Azure CLI commands and environment variable setup, while Linux steps are similar but less emphasized. The documentation mentions Windows-specific tools (HNS ACLPolicy) alongside Linux tools (IPTables), but does not prioritize Windows tools over Linux. All CLI examples use Azure CLI and Bash, which are cross-platform, but Bash is shown as the default shell for environment variable setup, which may not be native on Windows.
Recommendations
  • Clarify that Bash commands are cross-platform and provide PowerShell equivalents for Windows users where relevant.
  • Ensure Linux and Windows instructions are equally detailed and presented in parallel, rather than sequentially.
  • Add explicit notes about how Windows users can run Bash commands (e.g., via WSL or Git Bash) or provide alternative PowerShell syntax.
  • Consider a tabbed interface for Linux/Windows steps to improve clarity and parity.
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-14 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 daemon startup, but Windows/macOS instructions are listed first. All CLI examples use cross-platform Azure CLI and Bash commands, and there are no PowerShell or Windows-specific tools mentioned. The documentation is largely platform-neutral, but the ordering of instructions shows a minor Windows bias.
Recommendations
  • List Linux instructions before Windows/macOS, or group all OS instructions together for Docker daemon startup.
  • Explicitly mention that all Azure CLI and Bash commands are cross-platform and provide links to platform-specific installation guides if needed.
  • Ensure parity in troubleshooting and cleanup verification steps by referencing both Linux and Windows/macOS file paths and commands where applicable.
GitHub Create Pull Request
← Previous Page 4 of 15 Next →