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 126-150 of 354 flagged pages
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-12 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides parity for both Windows/macOS and Linux users in most sections, especially regarding Docker installation and AKS agent deployment. However, in the 'Verify Docker installation and start Docker daemon' section, instructions for starting Docker are presented as 'macOS/Windows' first, followed by Linux. This is a minor ordering bias, but all necessary Linux instructions are present. No PowerShell-only examples, Windows tools, or missing Linux examples are detected.
Recommendations
  • Present Linux instructions alongside or before Windows/macOS instructions in sections where order may imply priority.
  • Consider grouping OS-specific instructions in a neutral order or explicitly stating that all OSes are equally supported.
  • Continue to ensure all CLI and tool usage examples are cross-platform and avoid Windows-specific tooling unless required.
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-02-12 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 options for resource cleanup, but consistently lists Azure CLI (cross-platform) before PowerShell. There are no Windows-specific tools or commands used elsewhere, and all example commands (kubectl, curl, git) are cross-platform and compatible with Linux/macOS. The only minor bias is the inclusion of Azure PowerShell as an alternative, which is more common on Windows, but this is balanced by Azure CLI instructions. No critical steps are Windows-only.
Recommendations
  • Continue to list Azure CLI (cross-platform) as the primary option for all tasks.
  • Explicitly mention that all commands (kubectl, curl, git) work on Linux/macOS and Windows.
  • Consider adding brief notes for Linux/macOS users about installing Azure CLI and PowerShell, if relevant.
  • Ensure parity in future updates by avoiding Windows-only tools unless the feature 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-12 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 both PowerShell and CLI are cross-platform, the PowerShell section is more prominent and detailed, and PowerShell is traditionally associated with Windows. The PowerShell prerequisites and instructions are listed before Azure CLI, and the PowerShell section includes extra guidance about installation and usage on Windows, macOS, and Linux, but the CLI section is less emphasized. There are no missing Linux examples, and both PowerShell and CLI commands work on Linux/macOS, but the structure and emphasis favor PowerShell/Windows users.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is more widely used and natively cross-platform.
  • Balance the detail level between PowerShell and CLI sections, ensuring CLI instructions are as thorough as PowerShell.
  • Explicitly mention that both PowerShell and CLI are cross-platform, and highlight CLI as the preferred option for Linux/macOS users.
  • Add a note recommending Azure CLI for Linux/macOS users, or provide links to CLI installation instructions for all platforms.
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-12 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 for installation and management, which are available on Windows, Linux, and macOS. However, in the section 'Listing the CRDs in your cluster', the example uses 'kubectl get crds | findstr dapr.io', which is a Windows/PowerShell command (findstr) and does not provide a Linux/macOS equivalent (e.g., using grep). Additionally, the use of PowerShell-style variables (e.g., $MY_RESOURCE_GROUP) in CLI examples may be confusing for Bash users, though this is minor.
Recommendations
  • Provide Linux/macOS equivalents for commands using Windows-specific tools, e.g., 'kubectl get crds | grep dapr.io' alongside the findstr example.
  • Clarify variable syntax for both Bash and PowerShell users in CLI examples, or use cross-shell compatible syntax.
  • Review all CLI snippets to ensure they work seamlessly on Bash shells, not just PowerShell.
  • Consider showing both Windows and Linux/macOS command examples where shell-specific differences exist.
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-12 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 PowerShell alongside Azure CLI in the 'Before you begin' section and links to PowerShell documentation. The only explicit PowerShell mention is for listing subnets, but no Linux-specific alternatives (e.g., Bash, shell scripting) are given. Azure CLI is used for all command-line examples, which is cross-platform, but PowerShell is mentioned first in some places. No Linux/macOS-specific friction is present, but the PowerShell references may create minor bias.
Recommendations
  • Where PowerShell is mentioned, clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Provide Bash or shell alternatives for listing subnets (e.g., using Azure CLI), rather than referencing PowerShell.
  • Consider listing Azure CLI before PowerShell in prerequisite steps to reinforce Linux parity.
  • Explicitly state that all Azure CLI commands work on Linux/macOS/Windows.
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-12 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 (a Windows-centric tool) alongside CLI. The CLI is cross-platform, but PowerShell is presented equally, which may imply Windows as a primary platform. There are no Linux-specific examples or explicit mentions of Linux/macOS workflows. However, all core commands (Azure CLI, Helm, kubectl, git) are cross-platform, and the bash shell is used for Helm and Kubernetes commands.
Recommendations
  • Clarify that Azure CLI is recommended for Linux/macOS users, and PowerShell is primarily for Windows.
  • Consider showing Azure CLI examples first, or labeling them as the default for cross-platform users.
  • Add a note indicating that PowerShell examples are for Windows users, and CLI examples are for all platforms.
  • Explicitly mention that Helm, kubectl, and git commands work on Linux/macOS and Windows.
  • Optionally, provide Linux/macOS-specific installation instructions for Azure CLI, Helm, and kubectl.
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-11 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 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. Additionally, in the example output for certificate signing requests, Windows node names (e.g., 'akswinp7000000') are shown, but Linux equivalents are not. All command-line examples use Azure CLI and bash, which are cross-platform, and most instructions are Linux-centric.
Recommendations
  • When showing example output, include both Linux and Windows node names for parity.
  • In the 'Verify TLS Bootstrapping' section, mention Linux file paths first, as AKS is primarily Linux-based.
  • Explicitly state that all commands are applicable to both Linux and Windows node pools unless otherwise noted.
  • Add clarifications or links for Windows users on how to run bash commands (e.g., using WSL or Azure Cloud Shell).
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-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides troubleshooting steps for the Agentic CLI for AKS and covers both Windows/macOS and Linux environments. However, in several sections, Windows/macOS instructions (e.g., 'Launch Docker Desktop') are listed before Linux equivalents, and Linux-specific solutions are sometimes less detailed or presented after Windows steps. There are no PowerShell examples, but Windows tools (Docker Desktop) are mentioned before Linux commands. Azure CLI examples are platform-neutral, but some troubleshooting steps (e.g., Docker permission issues) are more detailed for Linux. Overall, Linux users are supported but not always given equal prominence.
Recommendations
  • Present Linux and Windows/macOS troubleshooting steps in parallel or with equal prominence, rather than listing Windows/macOS first.
  • Add more detailed Linux troubleshooting steps where appropriate (e.g., for Docker Desktop alternatives on Linux).
  • Where possible, clarify which steps apply to all platforms and which are platform-specific.
  • Consider including explicit macOS/Linux/Windows tabs or sections for clarity.
  • Ensure Linux examples are as comprehensive as Windows/macOS examples.
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-11 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 focus on Azure CLI commands. While most steps are cross-platform, there is a subtle Windows bias in the Docker daemon startup instructions: 'macOS/Windows' users are told to launch Docker Desktop, while Linux users are given explicit shell commands. Additionally, the verification step for client mode cleanup uses 'ls ~/.azure/aksAgent.config', which is Unix-specific and may not work on Windows. No PowerShell examples are provided, but Windows users are implicitly assumed to use Docker Desktop, which may not be the only option. The ordering of instructions sometimes puts Windows/macOS first. Overall, the bias is minor and does not prevent Linux/macOS users from completing the tasks.
Recommendations
  • Provide explicit instructions for starting Docker daemon on Windows (e.g., using Windows Services or PowerShell, not just Docker Desktop).
  • Clarify the location of configuration files for Windows users (e.g., mention %USERPROFILE%\.azure\aksAgent.config).
  • Include PowerShell examples for Windows users where shell commands are given for Linux/macOS.
  • Ensure all file path examples are cross-platform or provide alternatives for Windows.
  • Where possible, avoid ordering instructions as 'macOS/Windows' first; consider 'Linux/macOS/Windows' or platform-neutral ordering.
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-11 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) examples for troubleshooting, but consistently presents PowerShell examples immediately after CLI and gives them equal prominence. There are no Windows-only tools or patterns, but the PowerShell tab is always present, which may create minor friction for Linux/macOS users. All YAML examples and portal instructions are platform-neutral, and the Azure CLI is featured first, but parity is not perfect.
Recommendations
  • Consider clarifying that Azure PowerShell is primarily for Windows users, and Azure CLI is cross-platform.
  • Add explicit notes or tips for Linux/macOS users, e.g., 'Azure CLI works on Linux, macOS, and Windows.'
  • If possible, provide Bash shell examples for IP retrieval (e.g., using curl or wget) alongside Azure CLI.
  • Review tab order and ensure Azure CLI is always shown first, with PowerShell as an optional alternative.
  • Mention that Cloud Shell supports both Bash and PowerShell, and users can select their preferred environment.
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-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides examples for Azure portal, Azure PowerShell, and Azure CLI. The PowerShell section is detailed and includes instructions for installing/upgrading PowerShell on Windows, macOS, and Linux. However, PowerShell is a Windows-centric tool, and its section appears before the Azure CLI section, which is more native to Linux/macOS environments. There is a minor bias in presenting PowerShell before CLI and giving PowerShell-specific guidance, but Linux/macOS users are not blocked and can use Azure CLI.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is more cross-platform and native for Linux/macOS users.
  • Explicitly mention that Azure CLI is recommended for Linux/macOS users.
  • Add a note clarifying that PowerShell is available cross-platform, but Azure CLI is often preferred on Linux/macOS.
  • Ensure parity in example depth and clarity between PowerShell and CLI sections.
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-11 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 for installation and management, which are available on both Windows and Linux/macOS. However, there is a minor bias in the 'Listing the CRDs in your cluster' section, where only a Windows/PowerShell example (using 'findstr') is provided for filtering CRDs, and no Linux/macOS equivalent (e.g., using 'grep') is shown. Additionally, the PowerShell example is presented without alternatives, which may create friction for non-Windows users.
Recommendations
  • Add Linux/macOS equivalents for command examples, especially for filtering CRDs (e.g., 'kubectl get crds | grep dapr.io').
  • Where possible, present cross-platform commands side-by-side or note the differences.
  • Review other sections for similar single-platform command patterns and provide parity.
  • Consider a short note clarifying that Azure CLI and Bicep are available on all major OS platforms.
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-11 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 cluster creation and subnet listing, but references to PowerShell are present and often mentioned alongside or after Azure CLI. The Azure CLI is used for all main walkthrough steps, but PowerShell is referenced in the 'Before you begin' section and for subnet listing. There are no Linux/macOS-specific examples, but the CLI commands are cross-platform. Windows tools (PowerShell) are mentioned, and in some cases, Windows/PowerShell is referenced before Linux alternatives. However, the main workflow uses kubectl and Azure CLI, which are cross-platform.
Recommendations
  • Where PowerShell is mentioned, clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Consider providing explicit Bash/Linux shell examples for any Azure CLI commands that use variables or scripting.
  • If referencing PowerShell, always mention the Linux/macOS equivalent (Azure CLI or Bash) first.
  • Remove PowerShell references where not strictly necessary, or add parity for Linux/macOS users.
  • Add a note early in the document stating that Azure CLI is recommended for Linux/macOS users.
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-02-11 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 are standard on Linux/macOS. However, all CLI examples are shown using the Azure CLI, and there is no mention of PowerShell or Windows-specific tools. The order of examples does not favor Windows, but the use of Azure CLI may be perceived as slightly Windows-first, since some users associate CLI usage with Windows environments, though Azure CLI is fully cross-platform. No Linux-specific commands or package manager instructions (e.g., apt, yum, brew) are provided, but none are needed for the described tasks.
Recommendations
  • Explicitly state that Azure CLI and kubectl commands work on Windows, Linux, and macOS.
  • Add a note clarifying that Azure CLI can be installed on Linux/macOS and provide a link to installation instructions for those platforms.
  • Ensure parity by mentioning that all commands are cross-platform and do not require Windows.
  • If possible, provide alternative instructions for users who prefer using Bash scripts or native Linux tools for automation.
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-11 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 setup, but Windows-specific instructions (such as registering feature flags and creating Windows admin credentials) are presented in a dedicated section immediately after the Linux section. Windows tools and concepts (like HNS ACLPolicies) are mentioned alongside Linux equivalents (IPTables), and Windows node pool support is discussed in the context of Calico and Azure NPM. However, Linux instructions and examples are generally present and complete, and the page is not Windows-only.
Recommendations
  • Ensure Linux and Windows instructions are equally prominent and parallel in structure.
  • When describing network policy engines, list Linux and Windows support together rather than Windows-specific features first.
  • Where possible, provide Linux and Windows examples side-by-side, especially for cluster creation and network policy application.
  • Clarify when steps are Windows-specific to avoid confusion for Linux users.
  • Consider adding explicit notes or tables summarizing feature parity and limitations for both OSes.
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-02-11 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 resource cleanup, but lists Azure CLI first. The prerequisites mention both Azure CLI and Azure PowerShell, but do not show any Linux-specific shell or tool examples. All command-line examples use Bash syntax (compatible with Linux/macOS), and there are no PowerShell-specific examples for the main workflow. No Windows-only tools are referenced, and the workflow is cross-platform. However, the presence of Azure PowerShell instructions and its mention in prerequisites may slightly favor Windows users.
Recommendations
  • Clarify that all Bash commands work on Linux/macOS and Windows (with WSL or Git Bash), and explicitly mention cross-platform compatibility.
  • Consider listing Azure CLI as the default/primary method for resource management, with PowerShell as an alternative, and clarify that Azure CLI is cross-platform.
  • Add a note in the prerequisites that Azure CLI is recommended for Linux/macOS users, while Azure PowerShell is primarily for Windows.
  • Ensure parity in examples: if PowerShell is shown for cleanup, consider showing Bash alternatives for all steps, or clarify that Azure CLI is preferred for non-Windows platforms.
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-11 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 tasks, but consistently presents Azure CLI (which is cross-platform) before Azure PowerShell (which is Windows-centric). There are no explicit Linux/macOS-specific examples or notes, but the CLI instructions are suitable for Linux/macOS. Bash commands are used for Helm and git operations, which are platform-neutral. No Windows-only tools or patterns are mentioned, and no critical steps are Windows-exclusive.
Recommendations
  • Explicitly state that Azure CLI commands are cross-platform and recommended for Linux/macOS users.
  • Add a note clarifying that Azure PowerShell is primarily for Windows users, while Azure CLI works on all platforms.
  • Consider including a brief section or callout for Linux/macOS users, confirming that all CLI steps are compatible.
  • Ensure that any references to PowerShell do not imply it is required for Linux/macOS users.
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-11 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 containers (user namespaces, AppArmor, seccomp), and explicitly states these are Linux-only. However, in prerequisite sections, Windows tools (Azure PowerShell) are mentioned alongside Azure CLI and Portal, and are listed before Linux equivalents in some places. All technical examples, commands, and walkthroughs are Linux-centric, with no Windows-specific instructions or tools used for the main tasks. No PowerShell-only examples or Windows tools are used for the actual security configuration.
Recommendations
  • In prerequisite lists, mention Azure CLI before Azure PowerShell to prioritize Linux-native tooling.
  • Clarify that Azure PowerShell is optional and not required for Linux users.
  • Consider adding a note that all technical steps are Linux-only and Windows node pools are not supported for these features, to avoid confusion.
  • If possible, provide links to Linux-specific quickstart guides before Windows/PowerShell equivalents.
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-11 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 provided throughout. In some sections, PowerShell is listed before the portal, and the 'devx-track-azurepowershell' custom metadata suggests a PowerShell focus. There are no missing Linux examples, as Azure CLI is fully supported on Linux/macOS and is always included. No Windows-only tools or patterns are mentioned outside of PowerShell.
Recommendations
  • Consider listing Azure CLI examples before Azure PowerShell in each section, as CLI is cross-platform and more commonly used by Linux/macOS users.
  • Explicitly note that Azure CLI commands work on Linux/macOS, and that Azure PowerShell is available on Linux/macOS (if true), to avoid implicit Windows bias.
  • If possible, add a short note or section for users who prefer Bash scripting or other Linux-native tools, clarifying that Azure CLI is the recommended cross-platform approach.
  • Review metadata and page structure to ensure CLI is not deprioritized in favor of PowerShell.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation provides examples and instructions for both Linux and Windows environments, but there is a minor bias in mentioning Windows file paths alongside Linux paths (sometimes Windows first), and referencing Windows-specific tools (e.g., C:\k\bootstrap-config) without always providing equivalent Linux instructions first. However, most commands and examples are cross-platform (Azure CLI, kubectl, bash/curl/openssl), and Linux paths are generally included. No critical steps are Windows-only.
Recommendations
  • Ensure Linux examples and file paths are always presented before Windows equivalents, as Linux is the default for AKS.
  • Where Windows paths are mentioned, explicitly clarify Linux paths and context first.
  • If showing file paths or commands for both OSes, use side-by-side tables or clear separation to avoid confusion.
  • Review for any subtle ordering bias and adjust to prioritize Linux, as AKS clusters are predominantly Linux-based.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation is generally cross-platform and AKS-focused, but there are subtle signs of Windows bias. In several sections, Windows/macOS instructions (e.g., starting Docker Desktop) are mentioned before Linux equivalents. The Docker daemon startup instructions list Windows/macOS first, then Linux. All CLI examples use Azure CLI, which is cross-platform, but there are no PowerShell-specific examples or Windows-only tools. However, the documentation does not provide explicit Linux/macOS parity in some instructions (e.g., launching Docker Desktop vs. starting Docker daemon on Linux).
Recommendations
  • Present Linux instructions before or alongside Windows/macOS instructions, especially in sections about starting Docker.
  • Add explicit notes or links for Linux users where only Windows/macOS instructions are given (e.g., how to launch Docker on Linux desktops).
  • Ensure parity in troubleshooting and cleanup instructions, such as verifying Docker images or configuration files, by providing Linux-specific commands where appropriate.
  • Consider adding a table or section summarizing OS-specific steps for Docker installation and startup.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides troubleshooting steps for the Agentic CLI for AKS and includes examples for Docker issues on macOS/Windows and Linux. However, Windows/macOS solutions are often listed before Linux, and some steps (such as restarting Docker Desktop) are Windows/macOS-centric without equivalent Linux guidance. There are no PowerShell-specific commands, but Windows tools (Docker Desktop) are referenced. Azure CLI and kubectl commands are cross-platform, but minor bias exists in ordering and completeness of Linux instructions.
Recommendations
  • Present Linux solutions before or alongside Windows/macOS solutions for parity.
  • Clarify that Docker Desktop is not available on Linux and provide equivalent Linux troubleshooting steps (e.g., systemctl restart docker, checking service status).
  • Where Windows/macOS instructions reference GUI actions (like launching Docker Desktop), provide Linux command-line alternatives.
  • Ensure all troubleshooting steps are equally detailed for Linux, including guidance for common Linux-specific issues (e.g., SELinux/AppArmor, systemd status checks).
  • Explicitly mention that Azure CLI and kubectl commands are cross-platform, and provide any OS-specific caveats if needed.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation provides both Azure CLI and PowerShell options for prerequisite steps, but references to PowerShell are present alongside Azure CLI in the 'Before you begin' section. The PowerShell cmdlet (Get-AzVirtualNetworkSubnetConfig) is mentioned as an alternative to Azure CLI for listing subnets, but no Linux-specific guidance or parity for PowerShell is provided. Azure CLI is used for all command-line examples, which is cross-platform, but PowerShell is referenced before Linux shell alternatives in some places.
Recommendations
  • Clarify that Azure PowerShell is optional and primarily for Windows users; consider mentioning Bash or other Linux-native tools where relevant.
  • Where PowerShell is referenced, ensure Linux/macOS users are guided to use Azure CLI or provide equivalent Bash commands.
  • If PowerShell is mentioned, add a note that Azure CLI is fully supported and preferred for cross-platform use.
  • Review the order of tool mentions in the 'Before you begin' section: list Azure CLI (cross-platform) before PowerShell (Windows-centric).
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-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides examples for Azure portal, Azure PowerShell, and Azure CLI. While Azure CLI is cross-platform, the PowerShell section is prominent and includes detailed instructions for installation and usage, with Windows mentioned first in upgrade instructions. The PowerShell section is more elaborate than the CLI section, potentially favoring Windows users. However, CLI instructions are present and usable for Linux/macOS users.
Recommendations
  • Ensure Azure CLI instructions are as detailed as PowerShell instructions, including environment setup and troubleshooting.
  • When mentioning installation or upgrade instructions for PowerShell, list Linux/macOS before Windows or equally.
  • Highlight Azure CLI as the recommended cross-platform tool for Linux/macOS users.
  • Add explicit notes clarifying that both Azure CLI and PowerShell are fully supported on Linux/macOS.
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-10 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 for installation and management, which are available on Windows, Linux, and macOS. 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. The use of 'findstr' is Windows-specific, and no Linux/macOS equivalent (such as 'grep') is provided. Additionally, this Windows example appears before any alternative, creating minor friction for Linux/macOS users.
Recommendations
  • Provide both Windows and Linux/macOS command examples for shell operations, e.g., show 'kubectl get crds | grep dapr.io' alongside the 'findstr' example.
  • Where possible, use cross-platform commands or note OS-specific differences.
  • Review other shell command examples to ensure parity for all platforms.
GitHub Create Pull Request
← Previous Page 6 of 15 Next →