Aks

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

Bias Trend Over Time

Pages with Bias Issues

365 issues found
Showing 326-350 of 365 flagged pages
Aks Schedule and Deploy Batch Jobs with Kueue on Azure Kubernetes Service (AKS) ...blob/main/articles/aks/deploy-batch-jobs-with-kueue.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a mild Windows bias in the prerequisites section, where Windows-centric tools (Azure CLI, Azure PowerShell, Azure portal) are listed for AKS cluster creation, with PowerShell mentioned before Linux-native alternatives. However, all operational examples (kubectl, Helm, YAML manifests) are cross-platform and shell-agnostic, using Bash syntax compatible with Linux/macOS. No critical steps are Windows-only, and Linux/macOS users can follow the guide without significant friction.
Recommendations
  • Explicitly mention Linux/macOS compatibility in the prerequisites and examples.
  • List Linux-native tools (Azure CLI, Bash) before or alongside PowerShell and Windows-specific options.
  • Provide example commands for AKS cluster creation using Bash/Azure CLI on Linux/macOS, not just PowerShell.
  • Clarify that all kubectl and Helm commands work on Linux, macOS, and Windows.
  • Add a note or section for Linux/macOS users, highlighting any differences or confirming parity.
GitHub Create Pull Request
Aks Understand platform differences for the web application workload ...-aks-docs/blob/main/articles/aks/eks-web-understand.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates mild Windows bias by listing PowerShell as a native CLI option for AKS, referencing Azure CLI and Azure Developer CLI (which are cross-platform but often associated with Windows), and including PowerShell links in the deployment options. While Linux/macOS users can use Azure CLI and other tools, the explicit mention and linking of PowerShell as a primary deployment method suggests a Windows-centric perspective. Additionally, Azure CLI is described as 'streamlined,' but no mention is made of Linux-specific patterns or shell usage. Examples and instructions do not explicitly show Linux/macOS parity, and Windows tools are listed before Linux alternatives in some cases.
Recommendations
  • Explicitly state that Azure CLI and Azure Developer CLI are cross-platform and provide example commands for Linux/macOS shells (e.g., Bash, zsh).
  • Add Linux/macOS-specific deployment examples or notes, especially where PowerShell is mentioned.
  • Clarify that PowerShell is optional and provide parity for Bash or other common Linux shells.
  • Ensure that CLI instructions and links do not prioritize Windows tools over cross-platform alternatives.
  • Consider adding a section or note about platform compatibility for all listed tools.
GitHub Create Pull Request
Aks Customer intent: "As a cloud administrator, I want to log in to Azure using the CLI with a workaround, so that I can securely access my subscription and manage resources without issues." ...cs/blob/main/articles/aks/includes/azd/azd-login-ts.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows Only Announcement
Summary
The documentation is generally cross-platform, using Azure CLI and curl, which work on Windows, Linux, and macOS. However, there is a notable Windows bias in the announcement section, which discusses the Windows-only Web Account Manager (WAM) broker and provides instructions relevant only to Windows users, without mentioning Linux/macOS equivalents or alternatives.
Recommendations
  • Add a note clarifying that the WAM broker is Windows-only and explain what Linux/macOS users should expect or do instead.
  • If there are Linux/macOS-specific authentication improvements or alternatives, mention them.
  • Ensure parity in announcements and configuration guidance for all platforms, or explicitly state when a feature is platform-specific.
GitHub Create Pull Request
Aks Deploy a Java application with Open Liberty/WebSphere Liberty on an Azure Kubernetes Service (AKS) cluster ...lob/main/articles/aks/howto-deploy-java-liberty-app.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for all command-line steps, ensuring Linux and macOS users are supported. However, PowerShell examples are shown for every step, and in some cases, Windows-specific patterns (e.g., use of $Env: variables, Windows Subsystem for Linux in prerequisites) are mentioned. The ordering of examples sometimes puts Bash first, but PowerShell is always present and detailed, which may create a perception of Windows-first or PowerShell-heavy bias. No critical steps are Windows-only, and Linux/macOS users can complete all tasks without friction.
Recommendations
  • Continue to provide Bash examples first, as Bash is the default shell for most Linux/macOS users.
  • Clarify in the prerequisites that Bash examples apply to native Linux/macOS terminals and Windows Subsystem for Linux (WSL), while PowerShell examples are for Windows users.
  • Consider adding a note or table at the top explaining which shell to use based on OS.
  • Ensure parity in troubleshooting and advanced sections, referencing Linux-native tools where relevant.
  • If possible, add explicit macOS notes where there are differences (e.g., file paths, permissions).
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-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation references both Azure CLI and Azure PowerShell for cluster creation and subnet listing, but consistently mentions PowerShell as an alternative and provides direct links to PowerShell commands. The only non-CLI command example given is for PowerShell (`Get-AzVirtualNetworkSubnetConfig`), and PowerShell is mentioned before Linux-native tools in some places. There are no Linux/macOS-specific examples or mentions of Bash scripting, nor any parity for PowerShell commands with Bash equivalents. However, the main workflow uses Azure CLI and kubectl, which are cross-platform.
Recommendations
  • Provide Bash or shell script equivalents for all PowerShell commands, especially for subnet listing and resource management.
  • When listing options for cluster creation or resource management, mention CLI and Bash alternatives before or alongside PowerShell.
  • Clarify that Azure CLI and kubectl are cross-platform and provide explicit instructions for Linux/macOS users where relevant.
  • Add notes or links to Linux/macOS installation and usage guides for Azure CLI and kubectl.
  • Remove unnecessary PowerShell bias in links and examples, or balance them with Linux/macOS alternatives.
GitHub Create Pull Request
Aks Plug in CA certificates for Istio-based service mesh add-on on Azure Kubernetes Service ...ure-aks-docs/blob/main/articles/aks/istio-plugin-ca.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively provides command-line examples using Azure CLI and kubectl, which are cross-platform tools, but it lacks explicit mention of Linux/macOS environments or any platform-specific considerations. There is no evidence of Windows-only commands (e.g., PowerShell), but the documentation does not clarify that all commands work equally on Linux/macOS, nor does it provide any Linux/macOS-specific troubleshooting or notes. The order of presentation and implicit assumptions may lead Linux/macOS users to wonder if there are platform-specific steps or issues.
Recommendations
  • Explicitly state that all CLI commands are cross-platform and provide links or notes about installing Azure CLI and kubectl on Linux/macOS.
  • Add troubleshooting notes or caveats for Linux/macOS users where relevant (e.g., file permissions, shell differences).
  • Include a short section or note confirming that no steps are Windows-specific and that the process is identical on Linux/macOS.
  • If any step has platform-specific nuances (such as file path formats), clarify them.
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-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI (Linux/macOS friendly) and Azure PowerShell (Windows-centric) instructions for managing AKS API server authorized IP ranges. However, the PowerShell example is given equal prominence and is presented immediately after the CLI example, which may suggest parity but also reinforces Windows tooling. There are no explicit Linux/macOS-only examples, nor are there any sections that require Windows-specific tools to complete the workflow. The rest of the documentation is platform-neutral, focusing on the Azure portal and Kubernetes YAML, which are cross-platform.
Recommendations
  • Clearly indicate that Azure CLI works on Linux, macOS, and Windows, while Azure PowerShell is primarily for Windows users.
  • Consider listing Azure CLI instructions first and labeling them as the recommended cross-platform approach.
  • Add a note clarifying that all portal-based steps are platform-agnostic.
  • If possible, provide bash/zsh examples for common troubleshooting tasks, especially where PowerShell syntax is shown.
  • Explicitly mention that the Azure CLI can be used in Cloud Shell (browser-based, cross-platform) for all users.
GitHub Create Pull Request
Aks View Kubelet Logs from AKS Nodes .../azure-aks-docs/blob/main/articles/aks/kubelet-logs.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows Example Present
Summary
The documentation provides Linux-focused instructions for viewing kubelet logs on AKS nodes, primarily using journalctl and bash commands. Windows node instructions are present, but only as a brief note at the end, specifying the log location and the use of the 'more' command. There is no evidence of Windows-first ordering, Powershell-heavy examples, or missing Linux examples; the main flow is Linux-centric, with Windows covered as an aside.
Recommendations
  • Expand the Windows section to include more detailed steps, such as how to SSH or RDP into Windows nodes, and how to locate and interpret kubelet logs.
  • Provide parity in troubleshooting steps for Windows nodes, including PowerShell commands where appropriate.
  • Consider grouping Linux and Windows instructions into clearly labeled subsections for easier navigation.
  • Add a note at the beginning clarifying which instructions apply to Linux nodes and which to Windows nodes.
GitHub Create Pull Request
Aks Install existing applications with Helm in Azure Kubernetes Service (AKS) ...ure-aks-docs/blob/main/articles/aks/kubernetes-helm.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation generally provides cross-platform, shell-agnostic instructions for using Helm with AKS, focusing on standard CLI commands. However, in the 'Before you begin' section, when referencing how to create an AKS cluster, the documentation lists 'Azure CLI', 'Azure PowerShell', and 'Azure portal' in that order, with PowerShell (a Windows-centric tool) mentioned before the portal and without explicit mention of Linux-native tools or workflows. No PowerShell-specific commands or Windows-only tools are used in the main Helm workflow examples, and all command-line examples use bash-style syntax.
Recommendations
  • When listing options for creating an AKS cluster, ensure Linux-native tools (Azure CLI) are always listed first, and clarify that Azure CLI is fully cross-platform.
  • Consider explicitly mentioning that all command-line examples are intended to work on Linux, macOS, and Windows (with WSL or Azure CLI installed), to reassure non-Windows users.
  • If referencing PowerShell, provide equivalent Bash or shell commands where appropriate, or clarify when a step is platform-agnostic.
  • Add a note that Azure CLI is available on all major platforms and is the recommended tool for Linux/macOS users.
GitHub Create Pull Request
Aks Quickstart: Deploy an Azure Kubernetes Service (AKS) cluster with Flatcar Container Linux for AKS (preview) using an ARM template ...rticles/aks/learn/quick-flatcar-deploy-arm-template.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for connecting to the AKS cluster and deleting resources, but PowerShell instructions are presented as a primary alternative to Azure CLI, with no mention of Linux/macOS-specific shell environments or tools. The SSH key creation section does mention both 'az sshkey create' and 'ssh-keygen', but overall, Windows-centric tools (PowerShell) are given parity with CLI, and there is no explicit guidance for Linux/macOS users regarding their native environments. The documentation does not reference Windows-only tools, but the structure and example ordering may create friction for Linux/macOS users.
Recommendations
  • Explicitly mention Linux/macOS environments and provide guidance for using Bash or Zsh shells, including any OS-specific considerations for Azure CLI.
  • Clarify that Azure CLI commands work on Linux/macOS and Windows, and provide troubleshooting tips for common issues on non-Windows platforms.
  • Reorder examples to present Azure CLI (cross-platform) instructions first, and clearly label PowerShell as a Windows-specific alternative.
  • Add notes or sections for Linux/macOS users, such as how to install Azure CLI and kubectl on those platforms.
  • Avoid implying parity between PowerShell and Bash unless both are equally supported and documented.
GitHub Create Pull Request
Aks Install Kueue on Azure Kubernetes Service (AKS) ...zure-aks-docs/blob/main/articles/aks/kueue-overview.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Mention
Summary
The documentation page primarily provides Bash-based examples for installing and managing Kueue on AKS, which are cross-platform and suitable for both Linux and Windows (with WSL or Git Bash). However, in the prerequisites section, Windows-centric tools and patterns are mentioned first: the Azure CLI, Azure PowerShell, and Azure Portal are listed as options to create an AKS cluster, with PowerShell explicitly referenced and linked. There are no explicit Linux-only or Windows-only command examples, but the ordering and inclusion of PowerShell as a primary option may signal a Windows-first bias.
Recommendations
  • List Linux-native tools (e.g., Bash, Azure CLI on Linux) before or alongside Windows tools in the prerequisites.
  • Provide explicit instructions or links for creating AKS clusters on Linux/macOS (e.g., using Azure CLI in a Linux terminal).
  • Clarify that all shown Bash commands work on Linux, macOS, and Windows (with WSL or compatible shell).
  • If mentioning PowerShell, also mention Linux equivalents or alternatives (e.g., Bash scripts for cluster creation).
GitHub Create Pull Request
Aks Quickstart: Deploy an Azure Kubernetes Service (AKS) cluster using Bicep ...in/articles/aks/learn/quick-kubernetes-deploy-bicep.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for all major steps, but PowerShell (a Windows-centric tool) is given equal prominence as Azure CLI. There are no Linux-specific examples or explicit mentions of Linux/macOS terminal usage, and PowerShell is presented as a primary option throughout. The SSH key generation step does mention 'ssh-keygen', which is cross-platform, but otherwise, the documentation does not address Linux/macOS users directly or provide tailored guidance for those platforms.
Recommendations
  • Clarify that Azure CLI commands work on Linux, macOS, and Windows, and recommend CLI for cross-platform parity.
  • Add explicit instructions or notes for Linux/macOS users, such as installing Azure CLI and kubectl on those platforms.
  • De-emphasize PowerShell as a primary option, or present Azure CLI examples first, as CLI is natively cross-platform.
  • Include troubleshooting notes for common Linux/macOS issues (e.g., file permissions, environment variables).
  • Add a section or tab for Bash shell usage, especially for steps like uploading files to Cloud Shell.
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-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation references Windows-centric tools and patterns before Linux equivalents, notably in the prerequisites section where Azure PowerShell and Azure CLI are both mentioned, but PowerShell is listed before Linux-friendly CLI. However, all command examples use Azure CLI and kubectl, which are cross-platform. There are no exclusive Windows-only examples, but the ordering and mention of PowerShell may subtly signal a Windows-first approach.
Recommendations
  • List Azure CLI before Azure PowerShell in prerequisites and quickstart links, as CLI is more widely used across platforms.
  • Explicitly mention that Azure CLI and kubectl are cross-platform and provide installation links for Linux/macOS.
  • Add a note clarifying that all command-line examples work on Linux, macOS, and Windows.
  • Consider removing or de-emphasizing PowerShell references unless a specific Windows-only workflow is required.
GitHub Create Pull Request
Aks Azure Kubernetes Service (AKS) Managed Gateway API Installation ...aks-docs/blob/main/articles/aks/managed-gateway-api.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation relies exclusively on Azure CLI (az) commands for installation, management, and uninstallation of the Managed Gateway API CRDs. While Azure CLI is cross-platform, there is no mention of Linux-specific package managers, shell environments, or alternative installation methods. There are no PowerShell-specific examples, but the documentation does not address Linux/macOS nuances or provide parity for users who may prefer native Linux tools or scripts. The examples and instructions are generic, but the focus on Azure CLI (commonly associated with Windows environments) and lack of explicit Linux/macOS guidance creates a subtle bias.
Recommendations
  • Explicitly state that Azure CLI is cross-platform and provide installation instructions for Linux/macOS users.
  • Include notes or examples for common Linux shell environments (e.g., bash, zsh) where relevant.
  • Mention alternative methods for managing AKS clusters (such as using the Azure portal, REST API, or Terraform) if applicable.
  • Clarify that all commands work on Linux/macOS, and highlight any OS-specific caveats if present.
  • Provide troubleshooting tips for Linux/macOS users (e.g., permissions, environment variables).
GitHub Create Pull Request
Aks Node resource reservations in Azure Kubernetes Service (AKS) ...s/blob/main/articles/aks/node-resource-reservations.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows Only Note
Summary
The documentation is largely platform-neutral, but there is a specific note about AKS reserving extra memory for system processes on Windows nodes. No equivalent details or examples are provided for Linux nodes, and the Windows-specific reservation is mentioned without parity or comparative information for Linux.
Recommendations
  • Add a corresponding note about memory reservations for system processes on Linux nodes, if applicable.
  • Clarify whether Linux nodes have similar or different system process reservations, and provide those values or references.
  • If there are platform-specific differences in resource reservations, present them in a side-by-side table or section for clear comparison.
  • Ensure that any Windows-specific information is matched by Linux/macOS details where relevant.
GitHub Create Pull Request
Aks Use NVIDIA GPU Operator on Azure Kubernetes Service (AKS) ...aks-docs/blob/main/articles/aks/nvidia-gpu-operator.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation references Windows tools and patterns before Linux equivalents, such as listing Azure PowerShell and Azure portal alongside Azure CLI for cluster creation, and includes a dedicated link for Azure PowerShell. There are no explicit Linux/macOS examples or mentions of Linux-specific workflows. The examples use Azure CLI, which is cross-platform, but the initial guidance and links show a Windows-first orientation.
Recommendations
  • List Linux/macOS options and workflows explicitly, such as using Bash or shell scripts for cluster creation.
  • Provide links to Linux/macOS-specific quickstart guides alongside Windows/PowerShell guides.
  • Ensure examples and instructions are not Windows-centric and clarify that Azure CLI works on all platforms.
  • Add notes or sections for Linux/macOS users where relevant, including troubleshooting or environment setup.
GitHub Create Pull Request
Aks Optimize Azure Kubernetes Service (AKS) usage and costs ...-aks-docs/blob/main/articles/aks/optimize-aks-costs.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
🔧 Windows Tools
Summary
The documentation page is largely platform-neutral, focusing on AKS concepts and Kubernetes features. However, there is a minor Windows bias in the Azure Hybrid Benefits section, which exclusively references bringing Windows Server and SQL Server licenses to Azure, without mentioning Linux licensing or equivalents. No command-line examples, tooling, or workflow instructions are present that favor Windows or PowerShell over Linux/macOS.
Recommendations
  • In the Azure Hybrid Benefits section, clarify that this benefit is specific to Windows workloads and mention that Linux workloads do not have an equivalent licensing program, or reference any Linux-specific cost optimization options if available.
  • Ensure future documentation includes platform-agnostic examples or provides both Windows and Linux/macOS instructions when command-line or tooling steps are involved.
GitHub Create Pull Request
Aks Outbound network and FQDN rules for Azure Kubernetes Service (AKS) clusters ...lob/main/articles/aks/outbound-rules-control-egress.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows Examples Windows Section
Summary
The documentation is generally cross-platform and AKS-focused, but there is a dedicated section for Windows Server node pools, listing Windows-specific FQDNs and update endpoints. Additionally, 'PowerShell' is mentioned as an example package in the context of apt-get operations, and Windows-related binaries and update endpoints are described in detail. However, Linux is also well-represented, with explicit mention of Ubuntu endpoints and apt-get operations. No PowerShell-only examples or Windows-first ordering is present, and Linux-specific requirements are covered where relevant.
Recommendations
  • Clarify that 'PowerShell' is available on Linux and macOS, not just Windows, when listing example packages.
  • Provide parity in detail for Linux and Windows node pool requirements (e.g., both should have explicit update endpoint tables and explanations).
  • Add a brief note in the Windows Server node pools section referencing the equivalent Linux update endpoints for clarity.
  • Ensure that any tools or binaries mentioned (e.g., PowerShell, Azure CLI) are described as cross-platform where applicable.
GitHub Create Pull Request
Aks AKS Regulated Cluster for PCI DSS 4.0.1 - Risk Assessment and Code Assets ...-aks-docs/blob/main/articles/aks/pci-ra-code-assets.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates mild Windows bias, primarily through references to Windows-specific tools (Visio file for architecture diagrams) and PowerShell cmdlets for configuring conditional access. These examples and resources are presented without Linux/macOS equivalents or alternatives, and Windows-centric tools are mentioned first or exclusively in relevant sections. However, most technical guidance is platform-agnostic and focuses on Azure and Kubernetes concepts.
Recommendations
  • Provide Linux/macOS equivalents for PowerShell commands, such as Azure CLI or REST API examples for conditional access policy management.
  • Offer architecture diagrams in open formats (e.g., SVG, PNG, PDF) alongside Visio files to accommodate non-Windows users.
  • Explicitly mention cross-platform tools and workflows where possible, ensuring parity in operational instructions.
  • Where jump box or management VM access is discussed, clarify that both Linux and Windows VMs are supported and provide examples for both.
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-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides parallel examples for both Azure CLI and Azure PowerShell throughout, but PowerShell (a Windows-centric tool) is given equal prominence as Azure CLI, and is presented in every major step. There are no explicit Linux/macOS examples or mentions of platform-specific considerations. Azure CLI is cross-platform, but PowerShell is primarily associated with Windows, and its inclusion may suggest a Windows bias. However, all critical tasks can be completed with Azure CLI, which works on Linux/macOS, and the only shell-specific commands outside Azure CLI/PowerShell are standard Bash commands (git, cd, helm, kubectl), which are cross-platform.
Recommendations
  • Clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Add explicit notes or tabs for Linux/macOS users, confirming that Azure CLI commands work natively on those platforms.
  • Consider placing Azure CLI examples before PowerShell examples to reduce perceived Windows-first bias.
  • Remove or de-emphasize PowerShell examples in sections where Azure CLI is sufficient, or add Bash-only workflows for Linux/macOS users.
  • Mention platform-specific installation steps for prerequisites (e.g., Helm, Azure CLI) for Linux/macOS.
GitHub Create Pull Request
Aks Deploy an application with the Dapr cluster extension for Azure Kubernetes Service (AKS) or Arc-enabled Kubernetes ...ure-aks-docs/blob/main/articles/aks/quickstart-dapr.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation lists both Azure CLI and Azure PowerShell as prerequisites, and provides resource cleanup instructions for both. However, Azure PowerShell (a Windows-centric tool) is mentioned alongside Azure CLI in prerequisites, and cleanup instructions are provided for both, with Azure CLI shown first. There are no exclusive Windows-only commands or examples, and all operational steps use cross-platform tools (git, kubectl, curl). No Linux/macOS equivalents are missing, and no Windows-only patterns or tools are used for the main workflow.
Recommendations
  • Clarify that Azure CLI is fully cross-platform, while Azure PowerShell is primarily used on Windows (though it can run on Linux/macOS).
  • Consider listing Azure CLI as the primary recommended tool, with Azure PowerShell as an alternative for Windows users.
  • Add a note for Linux/macOS users that Azure PowerShell is optional and Azure CLI is sufficient.
  • Ensure that any future examples or troubleshooting steps do not assume Windows-only environments.
GitHub Create Pull Request
Aks Manually scale nodes in an Azure Kubernetes Service (AKS) cluster ...azure-aks-docs/blob/main/articles/aks/scale-cluster.md
Low Priority View Details →
Scanned: 2026-01-13 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 scaling AKS clusters, but PowerShell is a Windows-centric tool and is presented as a primary alternative to Azure CLI. There are no Linux shell-specific examples (e.g., Bash scripts, shell pipelines), nor are Linux/macOS command-line patterns or tools mentioned. The structure gives equal weight to PowerShell and CLI, but PowerShell's inclusion may suggest a slight Windows bias, especially for users unfamiliar with it on non-Windows platforms.
Recommendations
  • Clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Add explicit Bash/shell examples where relevant, especially for scripting or automation.
  • Note that PowerShell Core is available on Linux/macOS, but most Linux users will prefer Bash/CLI.
  • Consider reordering sections to present Azure CLI first, emphasizing its cross-platform nature.
  • Provide guidance or links for Linux/macOS users on installing and using Azure CLI.
GitHub Create Pull Request
Aks Secure container access to resources ...docs/blob/main/articles/aks/secure-container-access.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page is focused on Linux security features for AKS containers, but there are minor instances of Windows bias. In the prerequisites for creating an AKS cluster, Windows tools (Azure PowerShell) are mentioned alongside Azure CLI and Portal, and the PowerShell link appears before the Portal link. However, all technical examples, security features, and walkthroughs are exclusively Linux-focused, and Windows node pools are explicitly called out as unsupported for these features. There are no PowerShell-specific commands or Windows-only configuration steps, but the initial cluster creation instructions could be more Linux-centric.
Recommendations
  • List Linux-friendly tools (Azure CLI, Portal) before Windows-specific tools (PowerShell) in prerequisites.
  • Clarify that all security features described are Linux-only at the start of the document.
  • Provide explicit guidance or links for Windows node pool users about alternative security approaches, if any.
  • Remove or de-emphasize Windows/PowerShell links in sections that are exclusively relevant to Linux.
  • Add a summary table comparing feature availability for Linux vs. Windows node pools.
GitHub Create Pull Request
Aks Stop and start an Azure Kubernetes Service (AKS) cluster ...-aks-docs/blob/main/articles/aks/start-stop-cluster.md
Low Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for stopping and starting AKS clusters. However, PowerShell examples are given equal prominence to CLI, and PowerShell is a Windows-centric tool. In the 'Before you begin' section, Azure PowerShell is mentioned before the Azure portal, and CLI is listed first. There are no Linux-specific instructions or notes about differences in experience for Linux/macOS users. The CLI examples are cross-platform, but the presence and equal emphasis on PowerShell may create a slight Windows bias.
Recommendations
  • Clearly indicate that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Add a note clarifying that Azure PowerShell is primarily for Windows and provide guidance for Linux/macOS users to use Azure CLI.
  • Consider listing Azure CLI instructions before PowerShell in all sections.
  • If possible, add troubleshooting notes or links for Linux/macOS users regarding Azure CLI installation and usage.
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-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows Examples Windows Linux Equivalence Windows First
Summary
The documentation provides both Windows and Linux information for AKS, but there is a notable bias toward Windows in several areas. Examples for installing and using kubectl are given for both Azure CLI and Azure PowerShell, but PowerShell (Windows-centric) is presented as an equal alternative to CLI, which is cross-platform. OS component tables consistently list Windows alongside Linux distributions, sometimes with Windows-specific tools and add-ons. In command examples, Windows tools (PowerShell cmdlets) are given equal prominence to CLI commands, and sometimes appear before Linux equivalents. However, Linux is well-represented in component lists and technical details.
Recommendations
  • Present Azure CLI (cross-platform) examples before PowerShell examples, and clarify that PowerShell is Windows-specific.
  • Explicitly state which commands/tools are cross-platform and which are Windows-only.
  • Where possible, provide bash/Linux shell equivalents for any PowerShell-specific instructions.
  • In tables and lists, group Linux and Windows components separately to avoid implying parity where it may not exist.
  • Add notes or links for Linux/macOS users on how to install or use tools if only Windows instructions are given.
GitHub Create Pull Request
← Previous Page 14 of 15 Next →