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 251-275 of 618 flagged pages
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-26 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 all Azure-related operations, but consistently presents Azure CLI (which is cross-platform and preferred on Linux/macOS) first, followed by Azure PowerShell (primarily used on Windows). There are no Windows-specific tools or patterns shown exclusively, and all critical steps are accessible via CLI commands suitable for Linux/macOS. Bash shell commands (git, helm, kubectl) are used for application-level steps, ensuring Linux parity. However, the presence of Azure PowerShell examples throughout may create minor friction for Linux users, as PowerShell is less commonly used outside Windows.
Recommendations
  • Consider clarifying that Azure CLI is the recommended and cross-platform approach for Linux/macOS users.
  • Optionally, add a note at the start of each section indicating Azure PowerShell is primarily for Windows users, while Azure CLI is for all platforms.
  • Ensure that all CLI examples are tested and work on Linux/macOS shells.
  • If possible, provide a Linux/macOS-specific quickstart tab (even if it mirrors Azure CLI) to reinforce parity.
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-26 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 terminology are prominent throughout. PowerShell is a Windows-centric tool, and its inclusion alongside Azure CLI may suggest a Windows bias. Additionally, PowerShell instructions are given equal prominence to Azure CLI, which is more cross-platform. There are no explicit Linux/macOS examples or notes about running commands in Bash or zsh locally, and the documentation does not mention Linux-specific patterns or tools. However, Azure CLI is cross-platform and is presented first in most sections.
Recommendations
  • Add explicit notes clarifying that Azure CLI commands work on Linux/macOS as well as Windows.
  • Include Bash/zsh shell examples or mention that Azure CLI commands can be run in native Linux/macOS terminals.
  • Consider reducing the prominence of PowerShell unless there are Windows-specific tasks.
  • Add a brief section or callout for Linux/macOS users, highlighting any differences or confirming parity.
  • Mention that Azure Cloud Shell is available from any OS and supports Bash and PowerShell.
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-25 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 and includes examples for Docker issues on macOS/Windows and Linux. Windows/macOS instructions (e.g., 'Launch Docker Desktop') are consistently mentioned before Linux equivalents, and Windows tools (Docker Desktop) are referenced without mentioning Linux alternatives (such as dockerd or system tray indicators). Azure CLI examples are cross-platform, but there are no PowerShell-specific commands. The bias is mostly in the ordering and tool references, with Linux instructions present but secondary.
Recommendations
  • Present Linux instructions before or alongside Windows/macOS steps, rather than after.
  • Mention Linux-native Docker tools (e.g., dockerd, systemctl) as alternatives to Docker Desktop.
  • Clarify that Docker Desktop is not available on Linux and suggest equivalent Linux solutions.
  • Ensure troubleshooting steps are equally detailed for Linux users (e.g., restarting Docker service, checking logs).
  • Add explicit notes about cross-platform compatibility for Azure CLI commands.
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-25 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation is generally platform-neutral and covers storage concepts for AKS without favoring Windows-specific tools or patterns. However, in the section about mounting volumes in pods, Windows container examples are provided immediately after Linux examples, but Linux is not explicitly named. The Windows example is clearly labeled, but there are no PowerShell or Windows-only tools referenced, and no critical steps are Windows-only. The overall structure and examples are Kubernetes-standard and applicable to both Linux and Windows node pools.
Recommendations
  • Explicitly label Linux examples where appropriate to clarify platform context.
  • Where Windows-specific YAML is shown, ensure Linux equivalents are also clearly presented and labeled.
  • Add a brief note clarifying that most AKS clusters run Linux nodes by default, and that Windows node pools require explicit configuration.
  • Consider adding a table or section summarizing any differences in storage support or volume mounting between Linux and Windows node pools.
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-25 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 PowerShell appear alongside Azure CLI and are linked in the 'Before you begin' section. The only explicit PowerShell mention is for querying subnets, while all actual command examples use Azure CLI or kubectl (which are cross-platform). Azure CLI is shown first and used throughout, but PowerShell is mentioned as an alternative. There are no Linux/macOS-specific examples or explicit parity notes. The bias is minor and does not prevent Linux/macOS users from completing the task.
Recommendations
  • Clarify that Azure CLI and kubectl are fully cross-platform and preferred for Linux/macOS users.
  • Where PowerShell is mentioned, add equivalent Azure CLI commands and note their cross-platform compatibility.
  • Consider removing PowerShell references from main steps unless a Windows-only scenario is being described.
  • Add a note in the 'Before you begin' section highlighting that all steps can be completed on Linux/macOS using Azure CLI and kubectl.
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-25 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation primarily uses Azure CLI commands and kubectl examples, which are cross-platform. However, the Azure CLI examples are shown using the 'azurecli-interactive' code block, which is often associated with Windows environments, and there is no explicit mention of Linux/macOS compatibility or alternative shell usage. The order of examples and instructions does not favor Windows tools (e.g., PowerShell) over Linux tools, but the documentation does not clarify that all commands work equally well on Linux/macOS, nor does it provide explicit Linux/macOS shell instructions or troubleshooting tips.
Recommendations
  • Explicitly state that Azure CLI and kubectl commands are cross-platform and can be run on Linux, macOS, and Windows.
  • Add notes or sections for Linux/macOS users, such as installation prerequisites for Azure CLI and jq on those platforms.
  • Consider including example commands using bash/zsh syntax where relevant (e.g., for environment variables or piping).
  • Mention any OS-specific caveats, if applicable, for Azure CLI or kubectl usage.
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-25 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 consistently includes PowerShell examples alongside CLI, which is primarily used on Windows. Azure CLI is cross-platform, but PowerShell is Windows-centric (though available on Linux/macOS). The structure presents both options equally, but PowerShell is not as commonly used on Linux/macOS. There are no Linux-specific examples or explicit mentions of Linux tools/patterns. Bash commands are used for Helm and git, but Azure operations are only shown via CLI and PowerShell.
Recommendations
  • Clarify that Azure CLI is the recommended cross-platform tool for Linux/macOS users.
  • Consider presenting Azure CLI examples first, or exclusively, unless PowerShell is required for a specific scenario.
  • Add explicit notes or sections for Linux/macOS users, highlighting that Azure CLI and Bash commands are fully supported.
  • Remove or de-emphasize PowerShell examples unless targeting Windows users specifically.
  • Add troubleshooting or environment notes for Linux/macOS users (e.g., installing Azure CLI, Helm, kubectl on Linux).
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-25 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 (a Windows-centric tool) is given equal prominence to Azure CLI, and is sometimes listed before CLI in explanations. There are no Linux-specific shell examples (e.g., Bash), but Azure CLI is cross-platform and is the primary tool for Linux/macOS users. No Windows-only tools or patterns are used, and all features are available to Linux/macOS users.
Recommendations
  • Clarify that Azure PowerShell is primarily for Windows users, while Azure CLI is cross-platform and recommended for Linux/macOS.
  • Consider listing Azure CLI examples before Azure PowerShell in each section, as CLI is more widely used across platforms.
  • Add a brief note in the 'Before you begin' section highlighting that Azure CLI is available on Linux/macOS and is the preferred tool for non-Windows environments.
  • Optionally, provide Bash shell script snippets for common tasks to further improve Linux parity.
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-25 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides parity for Linux, macOS, and Windows users throughout, but in the Docker daemon startup instructions, Windows/macOS steps are listed before Linux steps. All CLI examples use cross-platform Azure CLI and Bash commands, and Linux-specific instructions (e.g., using systemctl to start Docker) are included. No PowerShell or Windows-only tools are referenced, and Linux examples are present wherever relevant.
Recommendations
  • Consider listing Linux startup instructions before Windows/macOS, or clarify that all operating systems are equally supported.
  • Explicitly mention that all commands are cross-platform and provide links to OS-specific installation guides where relevant.
  • Ensure that troubleshooting and cleanup instructions reference Linux/macOS paths and tools equally alongside Windows equivalents.
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-25 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation is largely cross-platform, focusing on Azure CLI and kubectl commands, which are available on both Windows and Linux. However, there is a minor bias in the section 'Verify TLS Bootstrapping is enabled on current agent node pool', where the Windows file path ('C:\k\bootstrap-config') is mentioned after the Linux path, but no further Windows-specific examples or instructions are provided. Additionally, some commands reference Linux file paths and tools (e.g., openssl, grep), but do not explicitly provide Windows equivalents or clarify how Windows users can perform these tasks, potentially creating friction for Windows users.
Recommendations
  • For commands that use Linux-specific tools (e.g., openssl, grep, base64), provide Windows equivalents or clarify if these commands can be run in Windows Subsystem for Linux (WSL) or PowerShell.
  • In sections referencing file paths, ensure both Linux and Windows paths are equally described, and provide instructions for accessing these files on Windows nodes.
  • Where possible, provide PowerShell or Windows-native command examples alongside bash examples.
  • Add notes or links to guidance for Windows users on installing required tools or using WSL if 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-25 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. PowerShell is featured prominently, and its prerequisites and usage instructions are detailed more extensively than the Azure CLI. PowerShell instructions reference Windows tools and patterns, but also include links for macOS and Linux installation. The PowerShell section appears before the CLI section, and PowerShell is generally associated with Windows, though cross-platform support is acknowledged. There are no missing Linux examples, as Azure CLI is included and is cross-platform.
Recommendations
  • Ensure Azure CLI instructions are equally prominent and detailed as PowerShell, including troubleshooting and environment setup.
  • Consider listing Azure CLI before PowerShell, as CLI is more widely used on Linux/macOS.
  • Explicitly mention that both PowerShell and CLI are cross-platform, and highlight Linux/macOS usage where relevant.
  • Add notes or links for Linux/macOS users about using Azure Cloud Shell or installing Azure CLI/PowerShell, if not already present.
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-25 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 updating AKS API server authorized IP ranges, but consistently presents Azure CLI (Linux/macOS-friendly) examples first, followed by Azure PowerShell (Windows-centric) examples. There is no evidence of exclusive Windows tools, missing Linux examples, or Windows-only patterns. All tasks can be completed from Linux/macOS, and the portal-based workflow is platform-agnostic.
Recommendations
  • Maintain parity by continuing to provide Azure CLI examples alongside Azure PowerShell.
  • Consider explicitly stating that Azure CLI commands work on Linux, macOS, and Windows, while PowerShell is primarily for Windows users.
  • If possible, add Bash or shell script examples for common troubleshooting steps, especially for Linux/macOS users.
  • Ensure that screenshots and portal instructions do not reference Windows-specific UI elements or terminology.
GitHub Create Pull Request
Aks Secure Container Access to Resources in Azure Kubernetes Service (AKS) ...docs/blob/main/articles/aks/secure-container-access.md
Low Priority View Details →
Scanned: 2026-02-25 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation is focused on Linux security features for AKS, and all technical examples, commands, and walkthroughs are Linux-centric. However, in prerequisite sections, Windows tools (Azure PowerShell) are mentioned alongside Azure CLI and Portal, and are always listed before Linux equivalents. No PowerShell-specific examples or Windows tools are used in the technical steps, and the content clearly states Linux-only applicability. There are no missing Linux examples, and no Windows tools or patterns are used in critical steps.
Recommendations
  • List Azure CLI before Azure PowerShell in prerequisites to prioritize Linux-native tooling.
  • Explicitly note that Azure PowerShell is cross-platform, but CLI is preferred for Linux/macOS users.
  • Consider providing a short note for Linux/macOS users about using Azure CLI and SSH, and clarify that PowerShell is optional.
  • Ensure that any future examples or walkthroughs do not default to Windows tools or patterns unless necessary.
GitHub Create Pull Request
Aks Supported Kubernetes Versions in Azure Kubernetes Service (AKS) ...lob/main/articles/aks/supported-kubernetes-versions.md
Low Priority View Details →
Scanned: 2026-02-25 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation provides examples for Azure CLI and Azure PowerShell, but does not include Linux-native shell examples (e.g., Bash) or mention Linux-specific tools. Windows tools (PowerShell) are mentioned alongside Azure CLI, and in some cases, Windows-specific add-ons and OS components are listed before Linux equivalents. However, the overall content is not heavily Windows-biased and covers both Linux and Windows node pools/components where relevant.
Recommendations
  • Add Bash/Linux shell examples for commands where Azure CLI is used, to demonstrate parity for Linux/macOS users.
  • Clarify that Azure CLI commands are cross-platform and can be run on Linux/macOS, not just Windows.
  • When listing OS components or add-ons, ensure Linux and Windows are presented in a neutral order or grouped by platform.
  • Consider including explicit notes or links for Linux/macOS users regarding installation and usage of Azure CLI and kubectl.
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-25 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides parallel examples for Azure CLI, Azure PowerShell, and Azure Developer CLI, but PowerShell is featured equally alongside CLI and is referenced throughout. There is a mild Windows bias in the sense that PowerShell is a Windows-centric tool, and its inclusion may suggest Windows as a primary platform. However, Azure CLI and kubectl (both cross-platform) are also featured, and Bash/Cloud Shell is mentioned. No critical Linux/macOS omissions are present, but PowerShell is presented as a first-class option, which may create minor friction for Linux/macOS users.
Recommendations
  • Clarify that Azure PowerShell is available cross-platform, but is most commonly used on Windows.
  • Explicitly mention that Azure CLI and kubectl are fully supported on Linux/macOS and provide links to Linux/macOS installation guides.
  • Consider showing Azure CLI examples first, as it is the most platform-neutral and widely used tool.
  • Add a brief note for Linux/macOS users about using Bash or zsh for Azure CLI and kubectl commands.
  • Where PowerShell is referenced, note that Linux/macOS users can use PowerShell Core if desired, but Azure CLI is recommended for native shell environments.
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-23 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for troubleshooting, but consistently presents Azure CLI (cross-platform) first and then Azure PowerShell (Windows-centric). There are no explicit Windows-only tools or patterns, and all examples are generally applicable to Linux and macOS users. However, the inclusion of PowerShell examples may create minor friction for Linux/macOS users, as PowerShell is less commonly used on those platforms.
Recommendations
  • Clearly indicate that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Add explicit notes or tabs for Bash (where relevant) to reinforce Linux parity.
  • Consider referencing PowerShell as 'for Windows users' or noting its cross-platform availability.
  • Ensure troubleshooting steps do not assume PowerShell is available on Linux/macOS.
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-23 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 (local/Docker) and cluster (Helm/Kubernetes) modes. While the guide is generally cross-platform, there is a minor bias in the Docker daemon startup instructions: Windows/macOS (Docker Desktop) are mentioned before Linux (systemctl commands). All CLI examples use Azure CLI, which is cross-platform, and Linux-specific commands (e.g., kubectl, bash) are included. No critical Windows-only tools or PowerShell examples are present.
Recommendations
  • In the Docker daemon startup section, present Linux instructions before or alongside Windows/macOS instructions, or clarify that all OSes are equally supported.
  • Explicitly mention that Docker Desktop is available for both Windows and macOS, and that Linux users should use system services.
  • Ensure that any troubleshooting or FAQ sections also provide parity for Linux/macOS users if OS-specific issues are discussed.
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-23 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 (Docker Desktop) are listed before Linux, which is a minor 'windows_first' bias. All other examples and solutions include Linux commands and do not rely on Windows-specific tools or PowerShell.
Recommendations
  • Present Linux, macOS, and Windows instructions in parallel or in a consistent order (e.g., Linux, macOS, Windows) to avoid the perception of prioritizing Windows.
  • Where possible, clarify when steps are identical across platforms, and only separate out platform-specific instructions as needed.
  • Consider adding explicit Linux/macOS/Windows tabs or callouts for clarity if instructions differ.
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-23 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation is generally cross-platform and focuses on AKS storage concepts applicable to both Linux and Windows node pools. However, in the section on mounting volumes in pods, the Linux example is shown first, followed by a Windows-specific example. There are no PowerShell-heavy examples, Windows tools, or missing Linux examples. The only minor bias is that Windows mounting syntax is shown after the Linux example, which is a common and reasonable pattern.
Recommendations
  • Ensure that Windows and Linux examples are equally represented and clearly labeled.
  • Consider adding explicit notes when features or syntax differ between Linux and Windows containers.
  • If possible, provide side-by-side examples for mounting volumes in both Linux and Windows pods for clarity.
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-23 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 a minor Windows bias in the section 'Verify TLS Bootstrapping is enabled on current agent node pool', where the Windows file path ('C:\k\bootstrap-config') is mentioned immediately after the Linux path, and no further Windows-specific commands or examples are provided elsewhere. All command-line examples use Azure CLI and bash/kubectl, which are standard for Linux/macOS and Windows (via WSL or Azure Cloud Shell). There are no PowerShell-specific examples or Windows-only tools used. However, the documentation could improve parity by clarifying Windows node pool differences and providing more explicit Linux/Windows distinctions where relevant.
Recommendations
  • In the 'Verify TLS Bootstrapping is enabled' section, clarify that most AKS clusters use Linux nodes by default, and Windows node pools are optional.
  • Provide explicit instructions or links for accessing Windows node pools (e.g., using PowerShell or Windows-native tools) if relevant.
  • Where file paths differ, consider providing both Linux and Windows examples equally, or note which is more common.
  • Add a brief note about Azure CLI and kubectl usage on Windows (e.g., via WSL, PowerShell, or Azure Cloud Shell) to help Windows users.
  • Ensure that any Windows-specific instructions are clearly marked as such and do not precede Linux instructions unless the topic is Windows-specific.
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-23 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, and PowerShell is traditionally associated with Windows. The PowerShell prerequisites and instructions are listed before Azure CLI, and PowerShell-specific guidance is more extensive. However, Azure CLI examples are present and fully functional for Linux/macOS users. There are no Windows-only tools or missing Linux examples, but the ordering and emphasis slightly favor Windows/PowerShell.
Recommendations
  • Consider listing Azure CLI instructions before PowerShell, as CLI is more widely used across platforms.
  • Clarify that both Azure PowerShell and Azure CLI are fully supported on Linux/macOS, and highlight this in the prerequisites.
  • Balance the depth of instructions between PowerShell and CLI sections to avoid perceived preference.
  • Explicitly mention that Azure Cloud Shell supports Bash (for CLI) as well as PowerShell, and that both are available to all users.
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-02-23 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation is generally cross-platform, focusing on Azure CLI and Bicep for installing Dapr on AKS, which are available on Windows, Linux, and macOS. However, in the 'List the CRDs in your cluster' section, the example uses 'kubectl get crds | findstr dapr.io', which is a Windows-specific command (findstr). No equivalent Linux/macOS example (e.g., using 'grep') is provided. This is a minor bias, as most of the workflow is platform-agnostic, but the CRD listing step could create friction for Linux/macOS users.
Recommendations
  • Provide both Windows and Linux/macOS examples for listing CRDs, e.g., 'kubectl get crds | grep dapr.io' for Linux/macOS.
  • Review other command examples to ensure they are platform-agnostic or offer alternatives for different OS environments.
  • Explicitly state that Azure CLI and Bicep are supported on all major platforms to reassure non-Windows 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-23 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 PowerShell (a Windows-centric tool) are present alongside Azure CLI. Azure CLI is cross-platform, but PowerShell is typically Windows-first. The PowerShell cmdlet for listing subnets is mentioned after the Azure CLI command, so Linux parity is mostly maintained. However, the 'Before you begin' section and subnet listing instructions include PowerShell references, which may create minor friction for Linux/macOS users.
Recommendations
  • Clearly indicate that Azure CLI is the recommended, cross-platform tool for all steps.
  • Move PowerShell references to a dedicated section or appendix for Windows users, rather than mixing them with main instructions.
  • Where PowerShell is mentioned, provide equivalent Bash/Linux commands (if any) or clarify that Azure CLI covers all required functionality.
  • Consider removing PowerShell references from the main flow unless a Windows-only 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-23 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation primarily uses Azure CLI examples for installation and management, which are cross-platform. However, the examples are labeled as 'azurecli-interactive', and there is no explicit mention of PowerShell or Windows-specific tools. The verification steps use 'kubectl' and 'jq', which are standard Linux/macOS tools, and the commands are shown in Bash syntax. There is a minor bias in that Azure CLI examples are shown first and exclusively, with no mention of alternative methods (such as using Azure Cloud Shell, Bash, or PowerShell), but this does not significantly impact Linux/macOS users.
Recommendations
  • Clarify that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS.
  • Add a note or link to instructions for installing Azure CLI and kubectl on Linux/macOS.
  • Optionally provide PowerShell equivalents if relevant, but ensure Bash/Linux examples are equally represented.
  • Mention that Azure Cloud Shell can be used from any OS for these commands.
GitHub Create Pull Request
← Previous Page 11 of 25 Next →