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 101-125 of 354 flagged pages
Aks
Certificate Rotation in Azure Kubernetes Service (AKS)
...ks-docs/blob/main/articles/aks/certificate-rotation.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is generally cross-platform and AKS is a Linux-first service, but there are minor instances of Windows bias. In the 'Verify TLS Bootstrapping is enabled on current agent node pool' section, the Windows file path is listed after the Linux path, but no command-line example is provided for Windows users (e.g., how to check the file exists). All command examples use Bash or Azure CLI, which are cross-platform, but there are no PowerShell or Windows CMD examples for Windows users. The documentation does not mention Windows tools or patterns exclusively, nor does it prioritize Windows-specific instructions over Linux ones.
Recommendations
- Add explicit Windows command-line examples (e.g., PowerShell or CMD) for checking file existence at 'C:\k\bootstrap-config'.
- Clarify that Azure CLI and kubectl commands work on Windows, and provide any necessary Windows-specific flags or considerations.
- Consider including a note or example for Windows users on how to decode base64 or use openssl if not installed.
- Ensure parity in troubleshooting steps for both Linux and Windows nodes where applicable.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides parallel instructions for Azure portal, Azure PowerShell, and Azure CLI. However, the PowerShell section is notably detailed, with explicit instructions for installation and version checks, and is presented before the CLI section. The PowerShell instructions reference Windows tools and patterns, but do include links for macOS and Linux installation. The CLI section is less detailed and does not mention OS-specific considerations. There are no missing Linux examples, but the prominence and detail of PowerShell instructions may create a perception of Windows bias.
Recommendations
- Expand Azure CLI instructions to include OS-specific installation and troubleshooting links for Linux/macOS, similar to the PowerShell section.
- Ensure that CLI examples are as detailed as PowerShell examples, including version checks and environment preparation.
- Consider presenting CLI instructions before PowerShell, or at least in parallel, to avoid 'windows_first' bias.
- Add explicit notes that both PowerShell and CLI are fully cross-platform, and highlight Linux/macOS parity where relevant.
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation provides both Azure CLI and PowerShell options for prerequisite steps, but references Azure PowerShell and its cmdlets alongside Azure CLI. In the 'Before you begin' section, Azure PowerShell is mentioned as an option for creating an AKS cluster before Azure CLI and the Azure portal. Additionally, the PowerShell cmdlet 'Get-AzVirtualNetworkSubnetConfig' is referenced for listing subnets, but no Linux/macOS equivalent (such as Azure CLI or Bash) is shown alongside it. All main procedural examples use kubectl and Azure CLI, which are cross-platform, but the inclusion and ordering of PowerShell references may create minor friction for Linux/macOS users.
Recommendations
- When listing options for creating AKS clusters, mention Azure CLI first, as it is cross-platform, followed by Azure PowerShell for Windows users.
- For listing subnets, provide only Azure CLI examples or clearly indicate that PowerShell is Windows-specific and Azure CLI is recommended for Linux/macOS.
- If PowerShell is referenced, always provide an Azure CLI equivalent and note platform differences.
- Consider grouping Windows-specific tools in a separate section or appendix, rather than mixing them with cross-platform options.
Aks
Troubleshoot the Agentic CLI for Azure Kubernetes Service (AKS)
...ob/main/articles/aks/cli-agent-for-aks-troubleshoot.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides troubleshooting steps for the agentic CLI for AKS, but in several places, Windows/macOS solutions (e.g., 'Launch Docker Desktop') are mentioned before Linux equivalents. Some instructions for Docker issues are Windows/macOS-centric, and Linux-specific solutions are sometimes secondary. There are no PowerShell-specific commands, but Windows Desktop patterns are referenced. All Azure CLI and kubectl examples are cross-platform, but the ordering and phrasing show a mild Windows bias.
Recommendations
- Present Linux, macOS, and Windows solutions in parallel or grouped by OS, rather than listing Windows/macOS first.
- Clarify that Docker Desktop is not available on Linux and provide explicit Linux alternatives (e.g., systemd commands) before or alongside Windows/macOS instructions.
- Where possible, add notes for Linux-specific troubleshooting steps (e.g., checking Docker group membership, restarting Docker service).
- Ensure that examples and solutions are equally detailed for all platforms.
- Avoid phrases like 'On macOS/Windows' unless truly identical; separate instructions for each OS where they differ.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation is generally cross-platform and focuses on Azure CLI and Bicep, both of which are available on Windows, Linux, and macOS. However, there is a minor Windows bias in the 'Listing the CRDs in your cluster' section, where the example uses 'kubectl get crds | findstr dapr.io', which relies on the Windows 'findstr' command. No equivalent Linux/macOS example (e.g., using 'grep') is provided, and the PowerShell/Windows syntax is shown first and exclusively in this context.
Recommendations
- Provide Linux/macOS equivalent commands alongside Windows examples, such as 'kubectl get crds | grep dapr.io'.
- When showing shell commands, clarify which OS they apply to or use cross-platform syntax where possible.
- Consider listing both Windows and Linux/macOS command variants in troubleshooting or operational sections.
Aks
Access Kubernetes Resources using the Azure Portal
...e-aks-docs/blob/main/articles/aks/kubernetes-portal.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for managing AKS authorized IP ranges. However, the PowerShell section is presented immediately after the Azure CLI section, and both are given equal prominence. No Linux-specific tools or commands (such as bash or Linux-native utilities) are mentioned, but the Azure CLI example uses 'dig', which is available on Linux/macOS by default. There are no Windows-only tools or patterns, and the documentation is generally neutral and portal-focused. The PowerShell example is not prioritized over the CLI, and Linux users can complete all tasks using the Azure CLI instructions.
Recommendations
- Explicitly note that Azure CLI commands are cross-platform and suitable for Linux/macOS users.
- Consider adding a brief note or section clarifying that PowerShell examples are primarily for Windows users, while Azure CLI is recommended for Linux/macOS.
- If possible, add a bash-only example for retrieving the public IP address (e.g., using 'curl' or 'wget') for Linux/macOS users who may not have 'dig' installed.
- Ensure that any future troubleshooting steps or examples do not default to Windows tools unless necessary.
Aks
Configure LocalDNS in Azure Kubernetes Service (AKS)
...ure-aks-docs/blob/main/articles/aks/localdns-custom.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides links to AKS cluster creation guides for Azure CLI, Azure PowerShell, and Azure Portal, listing PowerShell before Portal. However, all configuration, verification, and troubleshooting steps use cross-platform tools (Azure CLI, kubectl, YAML), and the feature itself is only supported on Azure Linux or Ubuntu node pools. No Windows-specific tools, patterns, or examples are given, and Linux parity is strong throughout.
Recommendations
- Consider listing Azure CLI and Portal before PowerShell in the prerequisites to reinforce Linux/macOS parity.
- Explicitly note that all commands are cross-platform and can be run from Linux, macOS, or Windows environments.
- Optionally, provide a brief note that PowerShell is primarily for Windows users, while Azure CLI is recommended for all platforms.
Aks
Kubernetes on Azure tutorial - Upgrade an Azure Kubernetes Service (AKS) cluster
...in/articles/aks/tutorial-kubernetes-upgrade-cluster.md
Low Priority
View Details →
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 PowerShell examples are included throughout. Azure CLI is cross-platform, but PowerShell is primarily used on Windows, and its inclusion may create friction for Linux/macOS users. In some sections, PowerShell is listed before Azure portal, but not before Azure CLI. No Windows-specific tools or patterns are mentioned, and Linux/macOS users can complete all tasks using Azure CLI or portal. There are no missing Linux examples, and the documentation does not favor Windows tools exclusively.
Recommendations
- Clarify that Azure CLI is fully cross-platform and recommended for Linux/macOS users.
- Consider moving Azure PowerShell examples after Azure CLI and Azure portal, or explicitly note PowerShell is primarily for Windows users.
- Add a brief note at the start indicating Azure CLI is the preferred tool for non-Windows environments.
- Ensure all references to PowerShell are accompanied by Azure CLI equivalents (already done here).
Aks
Secure Container Access to Resources in Azure Kubernetes Service (AKS)
...docs/blob/main/articles/aks/secure-container-access.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page is focused on Linux security features for AKS containers, with all technical examples, commands, and walkthroughs targeting Linux environments. However, in several prerequisite sections, Windows tools (Azure PowerShell) are mentioned alongside Azure CLI and Portal, and are listed before Linux equivalents. No PowerShell-specific examples or Windows-only tools are used, and all technical steps are Linux-centric. There are no missing Linux examples, nor are Windows tools used exclusively.
Recommendations
- In prerequisite lists, consider listing Azure CLI (cross-platform) before Azure PowerShell, or clarifying that PowerShell is primarily for Windows users.
- Where possible, provide parity in introductory guidance for Linux/macOS users (e.g., highlight Azure CLI as the default for cross-platform scenarios).
- Explicitly state that all technical steps and examples are Linux-only, and clarify that Windows node pools are not supported for these features.
Aks
Configure Azure CNI Networking in Azure Kubernetes Service (AKS)
...aks-docs/blob/main/articles/aks/configure-azure-cni.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides three main approaches: Azure portal, Azure PowerShell, and Azure CLI. Azure PowerShell is featured prominently, with detailed instructions and prerequisites, including references to Windows, macOS, and Linux installation. However, PowerShell is a Windows-centric tool, and its section appears before the Azure CLI, which is more cross-platform and native to Linux/macOS. The PowerShell section is more verbose and detailed compared to the CLI section. There are no missing Linux examples, as Azure CLI is included, but the ordering and emphasis favor Windows/PowerShell.
Recommendations
- Present Azure CLI instructions before Azure PowerShell, as CLI is more universally supported across platforms.
- Ensure parity in detail between PowerShell and CLI sections; expand CLI instructions if needed.
- Explicitly mention that Azure CLI is recommended for Linux/macOS users.
- Consider adding a note clarifying that PowerShell is available on Linux/macOS, but Azure CLI is the default for those platforms.
Aks
Configure LocalDNS in Azure Kubernetes Service (AKS)
...ure-aks-docs/blob/main/articles/aks/localdns-custom.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides links to AKS cluster creation guides for Azure CLI, PowerShell, and Portal, with PowerShell (a Windows-centric tool) mentioned alongside CLI and Portal. However, all actual configuration, verification, and troubleshooting examples use Azure CLI and kubectl, which are cross-platform tools. There are no PowerShell-specific commands or Windows-only tools used in the main instructions. The documentation explicitly states LocalDNS is only supported on Azure Linux or Ubuntu node pools, not Windows, and does not present Windows-specific patterns or tools.
Recommendations
- When referencing AKS creation guides, list Azure CLI and Portal before PowerShell, or clarify PowerShell is Windows-specific.
- Consider adding a note that Azure CLI and kubectl are fully supported on Linux/macOS, and that PowerShell is optional for Windows users.
- Ensure all example commands are cross-platform (which they currently are).
Aks
Troubleshoot the Agentic CLI for Azure Kubernetes Service (AKS)
...ob/main/articles/aks/cli-agent-for-aks-troubleshoot.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides troubleshooting steps for the agentic CLI for AKS and generally includes both Windows/macOS and Linux instructions. However, in the Docker daemon troubleshooting section, Windows/macOS steps are listed before Linux steps, which is a minor 'windows_first' bias. All other examples and solutions are cross-platform or Linux-first, and Linux-specific issues (such as Docker permissions) are addressed directly.
Recommendations
- Present Linux and Windows/macOS instructions in parallel or in the same order throughout the documentation.
- Consider using tabs or clear section headers to distinguish platform-specific instructions, ensuring equal visibility.
- Review other sections for ordering and ensure Linux instructions are not consistently placed after Windows/macOS instructions.
Aks
Certificate Rotation in Azure Kubernetes Service (AKS)
...ks-docs/blob/main/articles/aks/certificate-rotation.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is generally cross-platform and Linux-centric, but there are minor instances of Windows bias. In the 'Verify TLS Bootstrapping is enabled on current agent node pool' section, the Windows file path ('C:\k\bootstrap-config') is mentioned after the Linux path, which is good, but no Windows-specific command examples are provided. Most examples use bash, Azure CLI, and kubectl, which are standard for Linux/macOS. However, there are no PowerShell or Windows command-line examples for Windows users, and the documentation assumes Linux as the default for node access and certificate checks.
Recommendations
- Add Windows-specific command examples (e.g., PowerShell or Command Prompt) for checking certificate expiration and accessing node files.
- Clarify in sections where file paths differ between Linux and Windows, and provide explicit instructions for Windows users.
- Ensure parity by including Windows node pool scenarios where relevant, or explicitly state if steps are Linux-only.
- Consider adding a note about using Azure CLI and kubectl on Windows, including any prerequisites or differences.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation page provides installation and usage instructions for the Agentic CLI for AKS, with a focus on Azure CLI commands. While most examples are cross-platform (Azure CLI and bash), there is a subtle Windows bias in the ordering and presentation of Docker daemon startup instructions: Windows/macOS (Docker Desktop) are mentioned before Linux (systemctl), and Linux instructions are less detailed. Additionally, some verification steps (e.g., checking config file removal) use bash commands without explicit Windows equivalents, and there are no PowerShell examples for Windows users. However, the overall impact is minor, as the Azure CLI and Docker are cross-platform, and Linux/macOS users can follow the instructions with minimal friction.
Recommendations
- Present Linux instructions for Docker daemon startup before or alongside Windows/macOS instructions, and provide more detail for Linux users.
- Include PowerShell equivalents for bash commands where relevant (e.g., checking file removal, listing Docker images) to improve parity for Windows users.
- Explicitly mention that Azure CLI commands are cross-platform and provide links to platform-specific installation guides.
- Add troubleshooting notes for common Linux/macOS issues (e.g., Docker daemon permissions, systemctl failures).
Aks
Azure Kubernetes Service (AKS) Managed Gateway API Installation
...aks-docs/blob/main/articles/aks/managed-gateway-api.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation primarily uses Azure CLI commands and kubectl examples, which are cross-platform. However, all CLI examples are shown using Azure CLI (az), which is available on Windows, Linux, and macOS, but the documentation does not mention Linux/macOS-specific considerations or alternative commands. There is a minor bias in that Windows is implicitly assumed as the default environment, as no Linux/macOS shell-specific notes or troubleshooting are provided.
Recommendations
- Explicitly state that Azure CLI and kubectl commands work on Windows, Linux, and macOS.
- Add notes about installing Azure CLI and kubectl on Linux/macOS, including links to official installation guides.
- Mention any potential differences in environment variables, shell syntax, or command output between platforms.
- If relevant, provide troubleshooting tips for Linux/macOS users (e.g., permissions, PATH issues).
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 →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation is largely cross-platform, focusing on Azure CLI and Bicep for Dapr extension management on AKS and Arc-enabled Kubernetes. However, there is a minor Windows bias in the CRD deletion section, where the example for listing CRDs uses PowerShell's 'findstr' command with 'kubectl', which is Windows-specific. Additionally, this example is given without a Linux/macOS equivalent, and the PowerShell usage appears before any mention of Linux tools.
Recommendations
- Provide Linux/macOS equivalents for the CRD listing command, such as 'kubectl get crds | grep dapr.io'.
- When giving shell command examples, show both Windows (PowerShell) and Linux/macOS (bash) versions side-by-side or indicate which platforms they apply to.
- Consider using platform-neutral commands or note platform-specific differences where relevant.
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation provides both Azure CLI and PowerShell options for prerequisite steps, but consistently mentions Azure PowerShell alongside Azure CLI and portal, and links to PowerShell-specific resources. In the section about listing subnets, both Azure CLI and PowerShell are referenced, but PowerShell is mentioned second. There are no PowerShell-specific examples in the main workflow, and all command-line examples use Azure CLI or kubectl, which are cross-platform. However, the presence of PowerShell links and references may create minor friction for Linux/macOS users.
Recommendations
- Where PowerShell is referenced, ensure equivalent Bash or cross-platform CLI options are always provided and shown first.
- Clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Consider removing PowerShell references from main instructions unless a feature is PowerShell-only.
- Add explicit notes or links for Linux/macOS users where PowerShell is mentioned, pointing to Azure CLI alternatives.
Aks
Access Kubernetes Resources using the Azure Portal
...e-aks-docs/blob/main/articles/aks/kubernetes-portal.md
Low Priority
View Details →
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) instructions first, followed by Azure PowerShell (Windows-centric) instructions. No Windows-specific tools or patterns are mentioned exclusively, and all examples are cross-platform. However, the PowerShell section is present, which may be unnecessary for Linux/macOS users, but parity is maintained. There are no missing Linux examples, and the YAML deployment targets Linux node pools.
Recommendations
- Clarify that Azure CLI commands are cross-platform and preferred for Linux/macOS users.
- Consider explicitly stating that Azure PowerShell is primarily for Windows users.
- Add a brief note indicating that Azure CLI works on Windows, Linux, and macOS, while PowerShell is mainly Windows-focused.
- Ensure that any screenshots or UI instructions do not reference Windows-specific behaviors.
- If possible, provide Bash-only examples for Linux users, or highlight that Cloud Shell supports Bash and PowerShell.
Aks
Develop on Azure Kubernetes Service (AKS) with Helm
...ure-aks-docs/blob/main/articles/aks/quickstart-helm.md
Low Priority
View Details →
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 presents Azure CLI (which is cross-platform) before Azure PowerShell (which is Windows-centric). There are no Windows-only tools or commands, and all critical steps are achievable with Azure CLI, which works on Linux/macOS. Bash commands are used for Helm and kubectl, and no Windows-specific patterns or tools are mentioned. However, the presence of Azure PowerShell throughout and its parity with Azure CLI may create a slight perception of Windows bias.
Recommendations
- Consider clarifying that Azure PowerShell is primarily for Windows users and Azure CLI is cross-platform.
- Optionally, add a note at the start of the PowerShell sections indicating that Linux/macOS users should use Azure CLI.
- Ensure that bash commands and cross-platform tools (Helm, kubectl) are always shown and not replaced by Windows-specific alternatives.
- If possible, add explicit Linux/macOS instructions for installing Azure CLI, Helm, and kubectl (linking to their install docs).
Aks
Kubernetes on Azure tutorial - Upgrade an Azure Kubernetes Service (AKS) cluster
...in/articles/aks/tutorial-kubernetes-upgrade-cluster.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides full parity between Azure CLI, Azure PowerShell, and Azure portal for all AKS upgrade tasks. However, Azure PowerShell (which is Windows-centric) is given equal prominence to Azure CLI, and is sometimes mentioned before Linux-native tools. There are no missing Linux examples, but the presence of PowerShell examples and references may create minor friction for Linux/macOS users, as PowerShell is less commonly used on those platforms.
Recommendations
- Consider listing Azure CLI examples first in each section, as it is the most cross-platform and widely used tool.
- Explicitly note that Azure PowerShell is available on Linux/macOS, but Azure CLI is recommended for those platforms.
- Add brief guidance for Linux/macOS users, clarifying that Azure CLI is the preferred tool and that all examples are fully supported on those platforms.
- If possible, reduce the prominence of PowerShell in cross-platform tutorials, or move PowerShell examples to a secondary position.
Aks
Access Kubernetes Resources using the Azure Portal
...e-aks-docs/blob/main/articles/aks/kubernetes-portal.md
Low Priority
View Details →
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. However, PowerShell examples are also included, which is good parity. There are no Windows-only tools or patterns, and all examples are cross-platform. The YAML manifests explicitly target Linux node pools, but this is standard for AKS and not Windows-biased. No critical tasks are Windows-only.
Recommendations
- Maintain the current structure of presenting Azure CLI examples first, as this is inclusive for Linux/macOS users.
- Continue to provide both Azure CLI and PowerShell examples for administrative tasks.
- Consider adding a brief note clarifying that Azure CLI commands work on Linux, macOS, and Windows, while PowerShell commands are primarily for Windows users.
- Ensure screenshots and portal instructions do not reference Windows-specific UI elements or terminology.
Aks
Kubernetes on Azure tutorial - Upgrade an Azure Kubernetes Service (AKS) cluster
...in/articles/aks/tutorial-kubernetes-upgrade-cluster.md
Low Priority
View Details →
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 mentioned before or alongside CLI. There are no Linux-specific examples (e.g., Bash scripting, Linux-native tools), but Azure CLI is cross-platform and the examples are not exclusive to Windows. No critical tasks are Windows-only, and Linux/macOS users can complete all steps using Azure CLI or portal.
Recommendations
- Clarify that Azure CLI is fully cross-platform and recommended for Linux/macOS users.
- Consider listing Azure CLI examples before PowerShell in each section, or explicitly note CLI as the default for non-Windows environments.
- Add brief notes or links for Linux/macOS users about installing Azure CLI and using Bash/zsh shells.
- If possible, provide Bash script snippets for common operations (e.g., looping over node pools).
Aks
Azure Kubernetes Service (AKS) Managed Gateway API Installation
...aks-docs/blob/main/articles/aks/managed-gateway-api.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation primarily uses Azure CLI commands and kubectl, which are cross-platform tools. However, it does not explicitly mention Linux/macOS environments or provide guidance for those platforms. The examples and instructions are generic, but there is a subtle bias in that Windows is implicitly assumed (e.g., no mention of shell differences, environment variable syntax, or installation nuances for Linux/macOS). There are no PowerShell-specific commands or Windows-only tools, but the lack of explicit Linux/macOS guidance may create minor friction.
Recommendations
- Add a note clarifying that Azure CLI and kubectl commands work on Windows, Linux, and macOS, and provide links to installation instructions for each platform.
- Include example environment variable syntax for both Windows (e.g., $RESOURCE_GROUP) and Linux/macOS (e.g., export RESOURCE_GROUP=...).
- Mention any potential differences in command usage or prerequisites for Linux/macOS users, such as package managers or shell requirements.
- Ensure that all CLI examples are tested and confirmed to work on Linux/macOS terminals.
Aks
Troubleshoot the Agentic CLI for Azure Kubernetes Service (AKS)
...ob/main/articles/aks/cli-agent-for-aks-troubleshoot.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Missing
Minor Windows Tools
Summary
The documentation provides troubleshooting steps for the Agentic CLI for AKS and generally includes both Windows/macOS and Linux guidance. However, in several sections (especially Docker-related issues), Windows/macOS instructions are listed before Linux, and Windows-specific tools (Docker Desktop) are referenced. There are no PowerShell examples, but Windows/macOS users are directed to GUI actions (launch Docker Desktop), while Linux users are given CLI commands. All Azure CLI and kubectl examples are cross-platform. The bias is minor and does not prevent Linux/macOS users from completing tasks.
Recommendations
- Alternate the order of Windows/macOS and Linux instructions to avoid 'windows_first' bias.
- Provide explicit Linux/macOS CLI alternatives for Docker Desktop actions (e.g., 'systemctl start docker' for macOS with Homebrew installs).
- Clarify that Docker Desktop is not available on Linux and provide links to Linux-specific Docker troubleshooting.
- Consider adding PowerShell examples for Windows users if CLI is preferred, or Bash equivalents for macOS.
- Ensure parity in troubleshooting steps for all platforms, including edge cases (e.g., Docker on macOS without Docker Desktop).
Aks
About the Agentic CLI for Azure Kubernetes Service (AKS)
...s/blob/main/articles/aks/cli-agent-for-aks-overview.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation describes the Agentic CLI for AKS in a platform-neutral manner, but the 'Client mode' section references Docker and Azure CLI credentials without clarifying Linux/macOS compatibility or providing Linux/macOS-specific instructions. There are no explicit Windows-only tools mentioned, but the lack of Linux/macOS examples and prerequisites creates mild friction for non-Windows users.
Recommendations
- Explicitly state that the Agentic CLI for AKS supports Windows, Linux, and macOS platforms.
- Provide installation and usage instructions for Linux/macOS, including Docker and Azure CLI setup on those platforms.
- Mention any platform-specific considerations (e.g., Docker installation differences, Azure CLI authentication nuances) for Linux/macOS users.
- Add example commands or screenshots for Linux/macOS terminals alongside any Windows examples.