Aks
540
Total Pages
431
Linux-Friendly Pages
109
Pages with Bias
20.2%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
618 issues found
Showing 276-300 of 618 flagged pages
Aks
Develop on Azure Kubernetes Service (AKS) with Helm
...ure-aks-docs/blob/main/articles/aks/quickstart-helm.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides parallel Azure CLI and Azure PowerShell instructions throughout, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI. In some sections, PowerShell examples are shown before or alongside CLI, which may create friction for Linux/macOS users. However, all critical tasks can be completed with Azure CLI, and bash commands are used for Helm and kubectl, ensuring Linux parity.
Recommendations
- Consider making Azure CLI the primary/default example, as it is cross-platform, and move PowerShell instructions to secondary tabs or sections.
- Explicitly state that Azure CLI is recommended for Linux/macOS users, and PowerShell is for Windows users.
- Ensure that all bash commands (helm, kubectl, git) are clearly marked as cross-platform and do not reference Windows-specific shell behaviors.
- Add a brief note clarifying that PowerShell is not required for Linux/macOS users.
Create Pull Request
Aks
Supported Kubernetes Versions in Azure Kubernetes Service (AKS)
...lob/main/articles/aks/supported-kubernetes-versions.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for key tasks (such as installing/updating kubectl and listing available Kubernetes versions), but consistently presents Azure CLI (Linux/macOS-friendly) examples first. There are no Windows-only tools or patterns, and Linux-specific information is included where relevant (e.g., OS components, Azure Linux retirement). However, there are no explicit bash or Linux shell examples, and PowerShell is always presented as an alternative, not exclusively. No critical tasks are Windows-only, and Linux parity is maintained.
Recommendations
- Consider adding explicit bash or Linux shell examples for commands where Azure CLI is used, to reinforce Linux/macOS parity.
- Clarify that Azure CLI commands work cross-platform (Windows, Linux, macOS) and are recommended for Linux/macOS users.
- Add a brief note that Azure PowerShell is primarily for Windows users, while Azure CLI is cross-platform.
- If possible, provide links to Linux/macOS installation instructions for Azure CLI and kubectl.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides parity for both Linux and Windows node pools in AKS, but there is a slight bias toward Windows in some sections. Windows-specific steps (such as registering preview features and creating Windows admin credentials) are presented in detail and sometimes before Linux equivalents. However, Linux examples and instructions are present and comprehensive. All CLI examples use Bash/Azure CLI, not PowerShell, and Linux is referenced throughout, but Windows-specific tooling and steps are highlighted in dedicated sections.
Recommendations
- Ensure Linux and Windows instructions are presented with equal prominence and clarity.
- Where possible, group Linux and Windows steps side-by-side for easier comparison.
- Clarify when steps are Windows-only and provide Linux equivalents or explicitly state when not applicable.
- Maintain consistent ordering (e.g., Linux first, Windows second, or vice versa) throughout the document.
- Add explicit notes when a feature or step is not available for Linux or Windows, to avoid confusion.
Aks
Kubernetes on Azure tutorial - Create an Azure Kubernetes Service (AKS) cluster
...ain/articles/aks/tutorial-kubernetes-deploy-cluster.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides parallel instructions for Azure CLI, Azure PowerShell, and Azure Developer CLI, but PowerShell examples are prominent and given equal weight to Azure CLI. PowerShell is primarily a Windows tool, and its inclusion alongside Azure CLI (which is cross-platform) may create a perception of Windows bias. Additionally, PowerShell is mentioned before Linux-native alternatives in some sections, and there are no explicit Bash/Linux shell examples outside of Azure CLI. However, Azure CLI is presented as the main cross-platform tool, and the tutorial does not rely on Windows-only features.
Recommendations
- Clarify that Azure CLI commands are fully supported on Linux/macOS and recommend it as the primary cross-platform option.
- Add explicit Bash shell examples for common tasks (e.g., setting environment variables, running Azure CLI commands) to reinforce Linux parity.
- Consider moving Azure CLI examples before PowerShell in each section to emphasize cross-platform support.
- Mention that PowerShell Core is available on Linux/macOS, but highlight Azure CLI as the default for non-Windows users.
- Add a note in the 'Before you begin' section indicating that Azure CLI is recommended for Linux/macOS users.
Aks
Install and Use the Agentic CLI for Azure Kubernetes Service (AKS) (Preview)
.../blob/main/articles/aks/agentic-cli-for-aks-install.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides installation and usage instructions for the Agentic CLI for AKS, supporting both client mode (local Docker) and cluster mode (in-cluster Helm deployment). While the content is generally cross-platform, there is a minor bias in the Docker daemon startup instructions: Windows/macOS instructions (Docker Desktop) are mentioned before Linux instructions (systemctl commands). All CLI examples use Azure CLI, which is cross-platform, and there are no PowerShell-specific commands or Windows-only tools referenced. Linux examples and instructions are present, but not always shown first.
Recommendations
- Present Linux instructions alongside or before Windows/macOS instructions for Docker daemon startup.
- Explicitly mention that Azure CLI and Docker commands are cross-platform and provide links to Linux/macOS-specific installation guides where relevant.
- Consider adding a short section clarifying parity and supported OSes for the Agentic CLI, Docker, and Azure CLI.
- Ensure that any troubleshooting or FAQ sections also include Linux/macOS-specific guidance if applicable.
Aks
Troubleshoot the Agentic CLI for Azure Kubernetes Service (AKS)
.../main/articles/aks/agentic-cli-for-aks-troubleshoot.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation generally provides cross-platform troubleshooting steps, but in the Docker daemon troubleshooting section, instructions for macOS/Windows are listed before Linux, and the Windows/macOS solution is described in more detail (mentioning the system tray/menu bar). Linux instructions are present and accurate, but are listed after Windows/macOS. All other sections use cross-platform or Linux-first tools (kubectl, az CLI), and provide Linux-specific solutions where relevant.
Recommendations
- Present Linux, macOS, and Windows instructions in parallel or in a consistent order (e.g., Linux, macOS, Windows) to avoid implicit prioritization.
- Ensure that all platforms receive equally detailed instructions (e.g., mention how to start Docker on Linux, macOS, and Windows with similar clarity).
- Where possible, use platform-agnostic language or group instructions by platform with clear headings.
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-focused, but there is a minor Windows bias in the section 'Verify TLS Bootstrapping is enabled on current agent node pool', where Windows file paths are mentioned before Linux paths and Linux instructions are not always as prominent. However, the majority of examples and commands are Linux-oriented (bash, Azure CLI, kubectl), and Windows-specific tools (PowerShell, CMD) are not used. The bias is minor and does not prevent Linux/macOS users from completing the tasks.
Recommendations
- List Linux file paths before Windows file paths in relevant sections.
- Provide explicit Linux/macOS instructions/examples where Windows paths or behaviors are mentioned.
- Clarify that all CLI and kubectl commands are cross-platform unless otherwise noted.
- Add a note confirming parity for Linux/macOS users, especially in sections referencing file paths or node access.
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 examples for Azure portal, Azure PowerShell, and Azure CLI. The PowerShell section is detailed and references Windows tools, but also includes instructions for macOS and Linux. However, PowerShell is presented before CLI, and PowerShell is traditionally associated with Windows, which may create a perception of Windows bias. Azure CLI, which is more cross-platform, is included with full examples, but is listed after PowerShell.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is more universally used across Linux/macOS and Windows.
- Explicitly note that both Azure PowerShell and Azure CLI are fully supported on Linux and macOS, and provide links to installation instructions for all platforms.
- Consider adding a brief note about the cross-platform nature of Azure PowerShell and Azure CLI to reduce perceived Windows bias.
- Ensure that any PowerShell instructions reference Linux/macOS usage equally, perhaps with explicit example commands for those platforms.
Aks
Install Dapr Extension for Azure Kubernetes Service (AKS)
...softDocs/azure-aks-docs/blob/main/articles/aks/dapr.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation is generally cross-platform, focusing on Azure CLI and Bicep, which are available on Windows, Linux, and macOS. However, in the 'List the CRDs in your cluster' section, only a Windows-specific example is given using 'kubectl get crds | findstr dapr.io', which relies on the Windows 'findstr' command. No Linux/macOS equivalent (such as 'grep') is provided. Additionally, the use of PowerShell syntax for variable assignment (e.g., '$MY_RESOURCE_GROUP') may confuse Linux/macOS users, as Bash uses a different syntax. The rest of the documentation avoids Windows-specific tools and patterns, but these minor examples create friction for non-Windows users.
Recommendations
- Provide Linux/macOS equivalents for commands using Windows tools, e.g., 'kubectl get crds | grep dapr.io' alongside the 'findstr' example.
- Clarify variable assignment syntax for Bash users, e.g., 'export MY_RESOURCE_GROUP=...' or note that '$MY_RESOURCE_GROUP' is PowerShell syntax.
- Where possible, show both Windows and Linux/macOS command examples in troubleshooting and scripting sections.
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 to PowerShell are present and the PowerShell cmdlet is mentioned before its Linux equivalent in the subnet listing section. Azure CLI is used for all main examples, which is cross-platform, but the inclusion and ordering of PowerShell references may create minor friction for Linux/macOS users.
Recommendations
- When listing tools for prerequisites or resource queries, mention Azure CLI first as it is cross-platform, and PowerShell second.
- Where PowerShell cmdlets are referenced, ensure equivalent Azure CLI commands are also provided and shown first.
- Consider clarifying that Azure CLI works on Windows, Linux, and macOS, and that PowerShell is optional for Windows users.
- If PowerShell is referenced, provide a brief note for Linux/macOS users that Azure CLI is the recommended tool.
Aks
Azure Kubernetes Service (AKS) Managed Gateway API Installation (preview)
...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 for installation and management, which are cross-platform. However, Azure CLI examples are presented using the 'azurecli-interactive' code block, which is often associated with Windows/PowerShell environments, and there is no explicit mention of Linux/macOS shell usage or alternative instructions. The verification steps use 'kubectl' and 'jq', which are standard tools on Linux/macOS, but no explicit guidance is given for Linux/macOS users. Overall, the bias is minor and mostly in the ordering and implicit assumptions.
Recommendations
- Clarify that Azure CLI commands are cross-platform and can be run on Linux, macOS, and Windows.
- Add explicit notes or examples for Linux/macOS users, such as installation instructions for Azure CLI and 'jq'.
- Use generic shell code blocks (e.g., 'bash') for Azure CLI commands instead of 'azurecli-interactive', or provide both PowerShell and bash examples if relevant.
- Mention that 'kubectl' and 'jq' are available on all platforms and provide links to their installation guides for Linux/macOS.
Aks
Kubernetes on Azure tutorial - Create an Azure Kubernetes Service (AKS) cluster
...ain/articles/aks/tutorial-kubernetes-deploy-cluster.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides parallel instructions for Azure CLI, Azure PowerShell, and Azure Developer CLI. However, Azure PowerShell is featured equally alongside Azure CLI, which is more commonly used on Linux/macOS. PowerShell is primarily a Windows tool, and its inclusion may suggest a Windows-centric approach. Additionally, PowerShell examples are given equal prominence to Azure CLI, rather than being secondary or optional. There are no explicit Linux/macOS-specific examples or notes, and the documentation does not mention Linux shell patterns (e.g., Bash, zsh) or package managers for installing tools. However, all core tasks can be completed using Azure CLI, which is cross-platform, and there are no critical sections that are Windows-only.
Recommendations
- Clarify that Azure CLI is the recommended cross-platform tool for Linux/macOS users, and PowerShell is primarily for Windows environments.
- Add explicit notes or sections for Linux/macOS users, such as installation instructions for kubectl using native package managers (apt, brew, yum).
- Provide Bash/zsh shell command examples where relevant, especially for environment variable usage.
- Consider listing Azure CLI instructions before PowerShell, or marking PowerShell as 'Windows only' where appropriate.
- Mention that Azure Cloud Shell is available in Bash and PowerShell modes, and clarify which mode is used in examples.
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, PowerShell examples are included throughout, which is primarily a Windows-centric tool, and the documentation references Azure PowerShell alongside Azure CLI in nearly every section. In some sections, PowerShell is mentioned before the portal, but Azure CLI (cross-platform) is always presented first. There are no missing Linux/macOS examples, and all CLI commands are cross-platform. No Windows-specific tools or patterns are used, and Linux is referenced in node image upgrade guidance.
Recommendations
- Clarify that Azure PowerShell is primarily for Windows users, and Azure CLI is recommended for cross-platform (Linux/macOS/Windows) environments.
- Consider adding a note at the top indicating that Azure CLI is the preferred tool for Linux/macOS users.
- Ensure that Azure CLI examples are always presented first, as is currently done.
- Optionally, provide bash/zsh shell script examples for common tasks to further assist Linux/macOS users.
Aks
Concepts - Storage in Azure Kubernetes Services (AKS)
...re-aks-docs/blob/main/articles/aks/concepts-storage.md
Low Priority
View Details →
Detected Bias Types
Windows Example Present
Windows First
Summary
The documentation is largely platform-neutral and focuses on AKS storage concepts applicable to both Linux and Windows node pools. However, in the 'Persistent volume claims' section, Windows container volume mounting is mentioned after the Linux example, but only briefly. The Windows example is provided, but Linux is implicitly the default throughout. There are no PowerShell or Windows-specific tooling examples, and no critical storage concepts are presented as Windows-only unless explicitly noted (e.g., file system incompatibility).
Recommendations
- Ensure parity in example depth: The Windows container volume mount example is brief and lacks context compared to the Linux example. Consider expanding the Windows example to include a full pod manifest, and clarify any Windows-specific requirements or limitations.
- Explicitly state Linux/Windows applicability: Where storage classes, volume types, or CSI drivers differ between Linux and Windows, add notes or links to platform-specific documentation.
- Balance example ordering: If both Linux and Windows examples are provided, alternate their order or present them side-by-side to avoid implicit platform prioritization.
- Add troubleshooting or caveats for Windows: If there are known issues or limitations for Windows containers (e.g., file system support, volume sharing), highlight them with actionable guidance.
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 includes PowerShell (a Windows-centric tool) alongside CLI. The PowerShell examples are given equal prominence, and in some sections, PowerShell is mentioned before Linux-native alternatives. However, all critical steps (including Helm, kubectl, git, and bash commands) are cross-platform, and the Azure CLI is fully supported on Linux/macOS. No Windows-only tools or patterns are used for Kubernetes/Helm operations.
Recommendations
- Consider clarifying that Azure PowerShell is primarily for Windows users, while Azure CLI is cross-platform.
- Explicitly note that Azure CLI commands work on Linux/macOS and Windows, and that PowerShell is optional.
- Where possible, show Azure CLI as the default or primary example, with PowerShell as an alternative for Windows users.
- Add a brief section or note about using Azure CLI in Bash or Zsh shells on Linux/macOS.
- Ensure that Linux/macOS users are not confused by PowerShell references; link to Azure CLI installation instructions for their platforms.
Aks
Troubleshoot the Agentic CLI for Azure Kubernetes Service (AKS)
.../main/articles/aks/agentic-cli-for-aks-troubleshoot.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation provides troubleshooting steps for the Agentic CLI for AKS and covers both Windows/macOS and Linux environments. However, in several sections (especially Docker-related issues), Windows/macOS solutions are listed before Linux solutions, and Windows tools (Docker Desktop) are mentioned explicitly. Linux solutions are present and explained, but Windows/macOS are prioritized in ordering and tool references.
Recommendations
- Present Linux and Windows/macOS solutions in parallel or in a neutral order (e.g., Linux first, or alphabetical).
- Explicitly mention Linux alternatives for Docker Desktop (such as dockerd/systemctl) where appropriate.
- Ensure that all troubleshooting steps for Azure CLI, kubectl, and Docker are equally detailed for Linux, macOS, and Windows.
- Where possible, use generic language (e.g., 'Start Docker daemon') and then provide OS-specific instructions.
- Consider adding a summary table or section outlining OS-specific troubleshooting steps for quick reference.
Aks
Install and Use the Agentic CLI for Azure Kubernetes Service (AKS) (Preview)
.../blob/main/articles/aks/agentic-cli-for-aks-install.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides cross-platform instructions for installing and using the Agentic CLI for AKS, including both Linux and Windows/macOS examples. However, in the section about starting the Docker daemon, instructions for macOS/Windows (using Docker Desktop) are presented before Linux (using systemctl), which is a minor 'windows_first' bias. All other examples, commands, and tool references are platform-neutral or include Linux-specific guidance where appropriate.
Recommendations
- Present Linux instructions before or alongside Windows/macOS instructions when describing how to start Docker, to avoid implicit prioritization.
- Explicitly mention that Docker Desktop is not available for Linux and clarify the distinction between Linux and Windows/macOS approaches.
- Ensure parity in troubleshooting and cleanup instructions by verifying that all steps are equally applicable to Linux, macOS, and Windows users.
Aks
Connect your Azure Kubernetes Service (AKS) cluster to AI agents using the Model Context Protocol (MCP) server
...main/articles/aks/aks-model-context-protocol-server.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides cross-platform instructions and download links for Windows, macOS, and Linux, and generally avoids Windows-specific tools or patterns. However, in several places, keyboard shortcuts and UI instructions list Windows first (e.g., 'Ctrl+Shift+P on Windows/Linux or Cmd+Shift+P on macOS'), and troubleshooting tips reference Windows (e.g., WSL configuration) before Linux. There are no explicit Linux-specific troubleshooting examples or tips, and some Docker credential instructions mention Windows limitations but do not provide equivalent Linux guidance. Overall, Linux parity is good, but minor bias exists in ordering and lack of Linux-specific troubleshooting.
Recommendations
- Alternate keyboard shortcut ordering (e.g., list macOS first sometimes, or use 'on Windows/Linux' and 'on macOS' equally).
- Add Linux-specific troubleshooting tips, especially for Docker credential mounting and Azure authentication.
- Provide explicit examples for Linux users where Windows-specific instructions are given (e.g., WSL tips could be matched with Linux container tips).
- Ensure parity in troubleshooting and common issues sections by including Linux/macOS scenarios.
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, Windows file paths are mentioned alongside Linux, but Windows is listed second. However, in certificate rotation verification examples, output includes Windows node names (e.g., 'akswinp7000000'), which may confuse Linux users. There are no PowerShell-specific commands or Windows-only tools used, and all CLI examples are cross-platform. No critical steps are Windows-only.
Recommendations
- Ensure Linux examples and file paths are always listed first, as AKS is primarily Linux-based.
- Clarify that output examples containing Windows node names are applicable to both Linux and Windows node pools, or provide separate examples for each.
- Add explicit notes or examples for Linux/macOS users where Windows-specific paths or node names are shown.
- Where possible, provide parallel examples for both Linux and Windows node pools, especially in output sections.
Aks
Concepts - Storage in Azure Kubernetes Services (AKS)
...re-aks-docs/blob/main/articles/aks/concepts-storage.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation is generally cross-platform and focuses on AKS storage concepts relevant to both Linux and Windows node pools. However, in the section on mounting volumes in pods, the Linux example is presented first, followed by a Windows-specific example. There are no PowerShell-heavy examples, Windows tools, or missing Linux examples. The only evidence of bias is the ordering of examples, with Linux shown first and Windows second.
Recommendations
- Ensure that both Linux and Windows examples are presented with equal prominence, possibly by grouping them under clear subheadings (e.g., 'Mounting volumes in Linux containers' and 'Mounting volumes in Windows containers').
- Clarify that the majority of examples are Linux-centric by default, and provide links to Windows-specific documentation for users running Windows node pools.
- If possible, provide parity in YAML manifest examples for both Linux and Windows containers throughout the documentation, not just in the volume mount section.
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 examples for Azure portal, Azure PowerShell, and Azure CLI, covering all major platforms. However, the PowerShell section is more detailed, with explicit instructions for installation and version checks, and is presented before the CLI section. The PowerShell instructions reference Windows tools and patterns more prominently, but also include links for macOS and Linux installation. The CLI section is less detailed and appears after PowerShell, which may subtly prioritize Windows users.
Recommendations
- Ensure parity in detail between Azure PowerShell and Azure CLI sections, including environment preparation, version checks, and troubleshooting.
- Consider presenting Azure CLI examples before PowerShell, as CLI is cross-platform and widely used.
- Explicitly mention that both PowerShell and CLI are available on Windows, macOS, and Linux, and provide equal guidance for each.
- Add troubleshooting or environment setup notes for CLI users on Linux/macOS, similar to PowerShell.
- Where possible, avoid referencing Windows-specific tools or patterns unless necessary, and ensure Linux/macOS equivalents are equally visible.
Low Priority
View Details →
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 Azure PowerShell alongside Azure CLI in the 'Before you begin' section and links to PowerShell-specific commands before Linux equivalents. The PowerShell cmdlet (Get-AzVirtualNetworkSubnetConfig) is mentioned as an option for listing subnets, but no Linux/macOS equivalent is provided (such as Azure CLI or REST API). However, all core examples for load balancer creation, service deployment, and management use kubectl and Azure CLI, which are cross-platform. There are no PowerShell-only critical steps, and Linux/macOS users can complete all tasks.
Recommendations
- When referencing Azure PowerShell, always mention Azure CLI first and clarify that Azure CLI is cross-platform.
- For subnet listing, provide Azure CLI examples before PowerShell, and explicitly note that Azure CLI works on Linux/macOS.
- Where PowerShell is mentioned, add a note that Azure CLI is recommended for non-Windows users.
- Consider removing PowerShell links from the main flow or placing them in a separate 'Windows alternative' section.
- Ensure all critical steps have Azure CLI examples and avoid PowerShell-only instructions.
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) first, followed by Azure PowerShell (Windows-centric). However, the PowerShell section is equally detailed and not prioritized over CLI. No Windows-only tools or patterns are mentioned, and all examples are cross-platform. There are no missing Linux/macOS examples, and the YAML deployment targets Linux node pools. The bias is minor, limited to the ordering of examples and the inclusion of PowerShell.
Recommendations
- Continue to provide Azure CLI examples first, as CLI is cross-platform.
- Ensure that all PowerShell commands are accompanied by Azure CLI equivalents.
- Consider clarifying that Azure CLI works on Windows, Linux, and macOS, while PowerShell is primarily for Windows users.
- If possible, add a Bash-only example for IP address retrieval for Linux/macOS users (e.g., using curl or wget), though 'dig' is already used.
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 PowerShell is featured equally alongside CLI, which is more common on Windows. The structure consistently presents Azure CLI examples first, followed by PowerShell, potentially favoring Windows users. However, all critical steps are covered with cross-platform tools (Azure CLI, Helm, kubectl, git), and Linux/macOS users can follow the CLI instructions without issue. No Windows-only tools or patterns are used, and Linux parity is maintained throughout.
Recommendations
- Consider clarifying that Azure CLI is fully cross-platform and recommended for Linux/macOS users.
- Explicitly state that PowerShell examples are primarily for Windows users, while Azure CLI works on all platforms.
- Add a note at the top indicating that Linux/macOS users should use Azure CLI and ignore PowerShell sections.
- Ensure that any future examples or troubleshooting steps do not assume PowerShell as the default shell.
Aks
Supported Kubernetes Versions in Azure Kubernetes Service (AKS)
...lob/main/articles/aks/supported-kubernetes-versions.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides command examples for both Azure CLI and Azure PowerShell, but consistently lists Azure PowerShell (a Windows-centric tool) examples immediately after Azure CLI, and references PowerShell-specific commands (e.g., Install-AzAksKubectl, Get-AzAksVersion) without Linux/macOS equivalents. There are no bash or shell script examples, and no explicit mention of Linux/macOS-specific tools or workflows. However, Azure CLI is cross-platform and is shown first in all cases, mitigating the impact. No critical tasks are Windows-only.
Recommendations
- Explicitly state that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Add bash/shell script examples where relevant, especially for common tasks like checking Kubernetes versions or installing kubectl.
- Clarify that Azure PowerShell is primarily for Windows users, and provide parity with Linux/macOS instructions when referencing PowerShell.
- Consider including links or references to Linux/macOS-specific documentation or tools (e.g., Homebrew for kubectl installation).