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 151-175 of 618 flagged pages
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 instructions for configuring Azure CNI networking in AKS using three methods: Azure portal, Azure PowerShell, and Azure CLI. While all methods are presented, the PowerShell section is prominent and includes detailed instructions for installation and usage, which may be perceived as Windows-centric. Additionally, PowerShell is listed before CLI, which is more commonly used on Linux/macOS. However, the CLI section is present and includes full examples, and PowerShell installation instructions reference macOS and Linux, mitigating some bias.
Recommendations
- Present Azure CLI instructions before PowerShell, as CLI is the default cross-platform tool.
- Clarify that Azure PowerShell can be used on Linux/macOS, and provide explicit examples of running PowerShell on those platforms.
- Add a note highlighting that Azure CLI is recommended for Linux/macOS users.
- Ensure parity in example detail and troubleshooting tips between PowerShell and CLI sections.
Create Pull Request
Aks
Move Azure Disk persistent volumes to another AKS cluster in the same or a different subscription
.../blob/main/articles/aks/csi-disk-move-subscriptions.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation references Azure PowerShell as a migration option alongside Azure CLI and Azure Portal, but does not provide Linux-specific guidance or examples. Azure CLI is used for all command-line examples, which is cross-platform, but Azure PowerShell is mentioned before Azure CLI in the migration section. No PowerShell-specific examples are given, and all YAML and kubectl examples are Linux-oriented. There are no missing Linux examples, but the mention of Azure PowerShell as a migration tool without clarifying its cross-platform support may cause confusion.
Recommendations
- Clarify that Azure PowerShell is available on Linux and macOS, or link to installation instructions for non-Windows platforms.
- List Azure CLI before Azure PowerShell when describing migration options, as CLI is more commonly used cross-platform.
- Explicitly state that all command-line steps can be performed on Linux/macOS using Azure CLI.
- If referencing Azure PowerShell, provide a note about its cross-platform compatibility or suggest Azure CLI as the preferred tool for Linux/macOS users.
Aks
Create and Manage Persistent Volumes with Azure Files in Azure Kubernetes Service (AKS)
...cs/blob/main/articles/aks/create-volume-azure-files.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation is generally cross-platform, but there are minor signs of Windows bias. Windows paths and conventions are mentioned first or alongside Linux equivalents in several places, and Windows-specific instructions are provided for mounting Azure Files in Windows containers. Azure CLI is used throughout, which is available on Linux and macOS, but some commands and examples reference Windows path conventions or tools before Linux equivalents.
Recommendations
- When referencing mount paths, ensure Linux and Windows conventions are presented equally, ideally with Linux examples first since AKS clusters are predominantly Linux-based.
- Where commands differ between platforms (e.g., PowerShell vs Bash), provide both examples and clarify which is for which OS.
- In sections about Windows containers, explicitly state that the instructions are Windows-specific and provide Linux alternatives where relevant.
- Review output examples and ensure they are not exclusively Windows-formatted unless the section is Windows-specific.
- Consider including a brief note at the start clarifying that most examples are Linux-based unless otherwise stated.
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
Windows First
Summary
The documentation is generally cross-platform, focusing on Azure CLI and Bicep for managing Dapr on AKS or Arc-enabled Kubernetes clusters. However, there is a minor bias in the 'List the CRDs in your cluster' section, where the example uses 'kubectl get crds | findstr dapr.io'. 'findstr' is a Windows command-line tool, and no equivalent Linux/macOS example (such as using 'grep') is provided. Additionally, the Windows-specific example appears without mentioning Linux/macOS alternatives.
Recommendations
- Provide both Windows and Linux/macOS command examples when filtering kubectl output. For example, show both 'kubectl get crds | findstr dapr.io' (Windows) and 'kubectl get crds | grep dapr.io' (Linux/macOS).
- Explicitly state that the Azure CLI and Bicep commands are cross-platform and supported on Windows, Linux, and macOS.
- Review documentation for any other subtle Windows-first patterns, such as command syntax or tool references, and ensure parity in examples.
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 the Azure Portal when describing how to create an AKS cluster. It also references PowerShell cmdlets (e.g., Get-AzVirtualNetworkSubnetConfig) as alternatives to Azure CLI commands for listing subnets. However, all actual step-by-step examples and YAML manifests use cross-platform tools (kubectl, Azure CLI), and there are no PowerShell-specific walkthroughs or Windows-only commands for the main task. The bias is minor and mostly in the order and inclusion of PowerShell references.
Recommendations
- When listing options for creating an AKS cluster, mention Azure CLI and Portal first, and clarify that Azure PowerShell is primarily for Windows users.
- Where PowerShell cmdlets are referenced (e.g., Get-AzVirtualNetworkSubnetConfig), provide equivalent Linux/macOS commands (such as Azure CLI) before or alongside PowerShell.
- Consider adding a note that all main walkthrough steps use cross-platform tools and are suitable for Linux/macOS users.
- If referencing PowerShell, clarify its platform specificity and provide links to Azure CLI documentation as the primary cross-platform option.
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 managing AKS API server authorized IP ranges, but consistently lists Azure PowerShell after Azure CLI and offers no Linux/macOS-specific guidance. The PowerShell examples are included even though PowerShell is primarily used on Windows, and there is no mention of Bash or other Linux-native tools. However, the main workflow is portal-based and platform-neutral, and the Azure CLI examples are suitable for Linux/macOS users.
Recommendations
- Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, while Azure PowerShell is primarily for Windows users.
- Consider adding Bash-specific or Linux/macOS-specific instructions for retrieving the public IP address (e.g., using 'curl' or 'dig'), or clarify that the Azure CLI example is cross-platform.
- If possible, reorder the troubleshooting tabs so that Azure CLI (cross-platform) is shown first, and PowerShell (Windows-centric) second.
- Add a note clarifying that PowerShell is available on Linux/macOS, but CLI is generally preferred for those platforms.
Aks
Use a Service Principal with Azure Kubernetes Service (AKS)
...blob/main/articles/aks/kubernetes-service-principal.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all major operations, but PowerShell is featured equally and sometimes with more detailed steps (e.g., decrypting secrets, creating PSCredential objects). Azure PowerShell is primarily used on Windows, and its inclusion may create friction for Linux/macOS users. However, Azure CLI examples are present throughout, and the documentation does not rely on Windows-only tools or patterns. The order of examples sometimes puts PowerShell before CLI, and there are minor references to Windows conventions (e.g., PowerShell secure strings), but Linux parity is generally maintained.
Recommendations
- Ensure Azure CLI examples are always shown first, as CLI is cross-platform and preferred for Linux/macOS users.
- Clarify that Azure PowerShell is primarily for Windows users, and recommend Azure CLI for Linux/macOS.
- Where PowerShell-specific steps are given (e.g., decrypting secure strings), provide equivalent CLI guidance or note that such steps are unnecessary with CLI.
- Explicitly state that all commands can be run from Linux/macOS terminals using Azure CLI.
- Add a brief section or note highlighting cross-platform compatibility and preferred tools for each OS.
Aks
Connect to Azure Kubernetes Service (AKS) cluster nodes
...s/azure-aks-docs/blob/main/articles/aks/node-access.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides parity for both Linux and Windows node access in AKS, with clear sections for each OS. However, Windows-specific instructions (such as host process containers and PowerShell usage) are presented in detail, and Windows node access methods are described after Linux/macOS methods. PowerShell commands are used heavily for Windows node troubleshooting, but Linux users are given bash-based examples and SSH instructions. The order of presentation slightly favors Linux, but Windows instructions are comprehensive and not exclusive.
Recommendations
- Ensure Linux and Windows sections are equally prominent and clearly separated.
- Where possible, provide Linux/macOS equivalents for any troubleshooting commands or scripts shown for Windows nodes.
- Add explicit notes when a method is Windows-only or Linux-only to avoid confusion.
- Consider including a summary table comparing Linux and Windows node access methods for quick reference.
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 for all Azure-related steps, but PowerShell is featured equally alongside CLI, which is more commonly used on Linux/macOS. The PowerShell examples and terminology may create friction for Linux/macOS users, as PowerShell is primarily a Windows-centric tool, though it is available cross-platform. There are no explicit Windows-only tools or patterns, and the core Kubernetes and Helm steps use standard bash commands. Azure CLI is presented first in each section, which is positive for Linux parity.
Recommendations
- Clarify that Azure PowerShell is optional and primarily for users familiar with PowerShell; Azure CLI is recommended for Linux/macOS.
- Consider labeling Azure CLI as the default or preferred method for cross-platform users.
- Add a brief note at the start of the 'Prerequisites' section indicating that Azure CLI is the most common tool for Linux/macOS, while PowerShell is an alternative.
- Ensure that bash commands (e.g., git, helm, kubectl) are clearly marked as cross-platform.
- Optionally, provide a table or summary comparing Azure CLI and PowerShell for users to choose their preferred tool.
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
Summary
The documentation provides both Linux and Windows examples for AKS network policy management, but Windows-specific instructions (such as registering preview features and creating Windows admin credentials) are presented in a dedicated section and sometimes before Linux equivalents. However, all CLI examples use Azure CLI and Bash, which are cross-platform, and Kubernetes commands are standard. There is a slight bias in the ordering and prominence of Windows-specific instructions, but Linux parity is generally maintained.
Recommendations
- Ensure Linux and Windows instructions are presented with equal prominence and clarity.
- When describing steps for both OS types, use parallel structure and headings (e.g., 'Create an AKS cluster with Azure Network Policy Manager (Linux)' and '(Windows)').
- If Windows-specific steps are required, clarify their purpose and provide Linux equivalents or explicitly state when they are not needed.
- Consider grouping OS-specific instructions together and referencing them from a main workflow, rather than interleaving.
- Add explicit notes when a feature or step is only relevant to one OS, to avoid confusion.
Aks
Create an OpenID Connect (OIDC) Provider for your Azure Kubernetes Service (AKS) Cluster
...ure-aks-docs/blob/main/articles/aks/use-oidc-issuer.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation uses Azure CLI examples throughout, which are cross-platform. However, the environment variable syntax shown ($VARIABLE) is Bash-style and not Windows CMD/PowerShell, but the page does not explicitly mention Linux/macOS compatibility or provide alternative Windows PowerShell syntax. There is no evidence of Windows-specific tools or patterns, but the lack of explicit Linux/macOS guidance and the absence of PowerShell/CMD examples could create minor friction for Windows users. No Linux bias is present, but Windows bias is minimal and limited to the order and implicit assumption of Bash usage.
Recommendations
- Add a note clarifying that Azure CLI commands work on Windows, Linux, and macOS.
- Provide PowerShell syntax for environment variables alongside Bash examples, or link to Azure CLI cross-platform usage documentation.
- Explicitly mention that the instructions are platform-agnostic and that Azure CLI is supported on all major OSes.
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, covering both client mode (local Docker) and cluster mode (Helm/Kubernetes). In the Docker daemon startup instructions, Windows/macOS (Docker Desktop) are mentioned before Linux (systemctl), and the 'Verify Docker installation' section lists Windows/macOS steps first. However, all examples and instructions are cross-platform, and Linux-specific commands are included where relevant. No PowerShell-specific commands, Windows-only tools, or missing Linux examples are present.
Recommendations
- Consider presenting Linux instructions alongside or before Windows/macOS steps, especially in sections about starting Docker.
- Explicitly state that all commands are cross-platform unless otherwise noted.
- Add clarifying notes for any OS-specific differences in Docker installation or Azure CLI usage.
- Ensure parity in troubleshooting and cleanup instructions for all 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 includes both Windows/macOS and Linux guidance. However, in several Docker-related troubleshooting sections, Windows/macOS instructions (e.g., 'Launch Docker Desktop') are listed before Linux commands, and Docker Desktop (a Windows/macOS tool) is mentioned prominently. Linux-specific solutions are present but sometimes secondary. Azure CLI and kubectl examples are platform-neutral, but the ordering and tool references show minor Windows bias.
Recommendations
- Present Linux and Windows/macOS troubleshooting steps in parallel or in a neutral order, rather than always listing Windows/macOS first.
- Explicitly mention that Docker Desktop is not available on Linux and clarify Linux alternatives (e.g., systemd-managed Docker).
- Where possible, provide platform-specific subsections or tabs to avoid mixing instructions and to ensure parity.
- Ensure Linux commands and solutions are as detailed as Windows/macOS ones (e.g., include restart instructions for Linux Docker service).
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 generally covers all major platforms (Windows, macOS, Linux) and provides download links and instructions for each. However, there are subtle signs of Windows bias: Windows keyboard shortcuts and VS Code instructions are often listed first, and some tips (e.g., WSL configuration) are Windows-specific. While Linux is supported throughout, there are few explicit Linux/macOS-specific troubleshooting tips or examples, and Windows is sometimes prioritized in ordering or detail.
Recommendations
- Ensure Linux/macOS keyboard shortcuts and instructions are given equal prominence and ordering, not always after Windows.
- Add explicit Linux/macOS troubleshooting tips, especially for Docker and VS Code scenarios (e.g., permissions, user IDs, common issues).
- Where Windows-specific advice is given (e.g., WSL), provide equivalent Linux/macOS advice (e.g., for running Docker containers or configuring Azure credentials).
- Include Linux/macOS-specific example commands or clarify any platform-specific differences in setup, especially for Docker and binary execution.
- Review ordering of download links and instructions to avoid always listing Windows first.
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. PowerShell is often associated with Windows, though it is cross-platform. The CLI section is less detailed, and Linux/macOS users may perceive minor friction due to the PowerShell emphasis and ordering.
Recommendations
- Ensure Azure CLI instructions are as detailed as PowerShell, including environment preparation, version checks, and troubleshooting.
- Consider presenting Azure CLI examples before PowerShell, as CLI is the default for many Linux/macOS users.
- Clarify that both PowerShell and CLI are fully cross-platform, and provide links to installation guides for all OSes in both sections.
- Add explicit notes or examples for Linux/macOS users where relevant, such as SSH key generation or file paths.
Aks
Create and Manage Persistent Volumes with Azure Files in Azure Kubernetes Service (AKS)
...cs/blob/main/articles/aks/create-volume-azure-files.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation is generally cross-platform and AKS-centric, but there are some minor signs of Windows bias. Windows path conventions and PowerShell/CMD syntax are mentioned before or alongside Linux equivalents in a few places. Windows-specific instructions are provided in the section about Windows containers, but Linux instructions are always present and prioritized elsewhere. Azure CLI is used throughout, which is available on all platforms, but some output examples use Windows-style paths or reference Windows tools.
Recommendations
- When referencing path conventions, list Linux/macOS examples first, or provide both equally.
- Where Windows-specific syntax is shown (e.g., PowerShell/CMD), ensure Linux/macOS syntax is equally prominent.
- Clarify that Azure CLI commands work on all platforms, and provide any necessary notes for Linux/macOS users if output or behavior differs.
- Review output examples for path conventions and ensure Linux/macOS paths are not overshadowed by Windows paths.
- Consider adding explicit notes or examples for Linux/macOS where only Windows is referenced.
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-focused, but there is a minor bias in the section 'Verify TLS Bootstrapping is enabled on current agent node pool', where the Windows file path is mentioned after the Linux path. However, there are no Windows-only commands or tools used, and the examples throughout the page are primarily Linux-oriented (bash, Azure CLI, kubectl). No PowerShell or Windows-specific tools are used, and Linux paths/scripts are shown first and most often. The only minor bias is the order of mentioning Windows after Linux, and the lack of explicit Linux/macOS instructions for some Azure CLI commands (e.g., if there are differences in shell usage or file paths).
Recommendations
- Ensure Linux/macOS users are aware of any differences in Azure CLI usage or file paths, especially for commands like az vm run-command invoke.
- Add clarifications or notes if any commands require adaptation for Linux/macOS terminals (e.g., escaping, file path formats).
- Continue to prioritize Linux examples, as AKS is predominantly Linux-based.
Aks
Move Azure Disk persistent volumes to another AKS cluster in the same or a different subscription
.../blob/main/articles/aks/csi-disk-move-subscriptions.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation references Azure PowerShell as a migration tool alongside Azure CLI and Azure Portal, but does not provide any PowerShell-specific examples. Azure CLI is used throughout for command-line examples, which is cross-platform. However, Azure PowerShell is mentioned before Azure CLI in the migration options list, and there are no Linux-specific notes or examples. The documentation does not show any explicit Windows-only commands or patterns, but the mention of Azure PowerShell as a primary tool may imply Windows bias.
Recommendations
- Clarify that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
- Reorder the migration tool list to mention Azure CLI before Azure PowerShell, or explicitly state that Azure PowerShell is Windows-centric.
- Add a note that Azure PowerShell is primarily for Windows users, and Linux/macOS users should use Azure CLI.
- Consider including a brief example or link for using Azure CLI on Linux/macOS, especially in the 'Before you begin' section.
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 critical troubleshooting steps, but consistently presents Azure CLI (Linux/macOS-friendly) first, followed by Azure PowerShell (Windows-centric). There are no exclusive Windows tools or patterns, and all examples are cross-platform. However, the presence of PowerShell examples and the explicit labeling of 'Azure PowerShell' tabs may create minor friction for Linux/macOS users, though workarounds and parity are maintained.
Recommendations
- Ensure that Azure CLI examples are always presented first for cross-platform parity.
- Explicitly mention that Azure CLI works on Windows, Linux, and macOS, and that PowerShell is primarily for Windows users.
- Consider adding Bash shell examples for common Linux/macOS scenarios, if relevant.
- Clarify in the prerequisites or troubleshooting sections that all Azure CLI commands are cross-platform.
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, using Azure CLI and Bicep (both cross-platform tools) for all main workflows. However, in the section for deleting Dapr CRDs, the example uses 'findstr' (a Windows-specific command) piped from 'kubectl', and the code block is marked as PowerShell. There are no equivalent Linux/macOS examples (e.g., using 'grep'). This minor bias could cause friction for Linux/macOS users unfamiliar with 'findstr'.
Recommendations
- Provide both Windows (findstr) and Linux/macOS (grep) examples for filtering CRDs with kubectl.
- Mark the code block as 'shell' or provide tabbed examples for PowerShell and Bash.
- Review for any other Windows-specific command usage and ensure parity with Linux/macOS equivalents.
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 references PowerShell cmdlets (e.g., Get-AzVirtualNetworkSubnetConfig) as equivalent to Azure CLI commands. Azure CLI is cross-platform, but PowerShell is traditionally Windows-centric, though now available on Linux/macOS. The PowerShell examples are not given first, but their inclusion and mention may create a mild Windows bias. No Linux/macOS-specific examples or notes are provided, but all core instructions use Azure CLI and kubectl, which are cross-platform.
Recommendations
- Clarify that Azure CLI and PowerShell are both available cross-platform, and link to PowerShell installation for Linux/macOS if PowerShell examples are provided.
- Consider prioritizing Azure CLI examples, as they are more universally cross-platform.
- If mentioning PowerShell, explicitly state its cross-platform availability to avoid implying Windows-only usage.
- Add notes for Linux/macOS users where relevant, such as shell syntax differences or installation instructions for Azure CLI 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 tasks, but PowerShell is featured equally alongside CLI throughout. There is no explicit Windows bias in the core Kubernetes/Helm steps, which use bash commands. However, PowerShell is included as a primary option, which is mainly relevant for Windows users, and the tabs for CLI/PowerShell are presented together, sometimes with PowerShell first. There are no Linux-specific examples or explicit mentions of Linux tools, and the documentation does not clarify that Azure PowerShell is not available on Linux/macOS (though Azure CLI is cross-platform).
Recommendations
- Clarify that Azure PowerShell is primarily for Windows users and that Azure CLI is recommended for Linux/macOS.
- Consider showing Azure CLI examples first, as it is cross-platform, and PowerShell second.
- Add explicit notes or guidance for Linux/macOS users, e.g., 'Azure CLI is supported on Linux/macOS; Azure PowerShell is primarily for Windows.'
- Ensure that any PowerShell-specific instructions are accompanied by equivalent CLI instructions, which is already mostly done.
- Add a short section or callout about cross-platform compatibility for Azure CLI, Helm, and kubectl.
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-centric tool, and its inclusion may suggest a Windows bias. Additionally, PowerShell examples are given equal prominence to Azure CLI, rather than being secondary. There are no explicit Linux/macOS-specific instructions or mentions of Bash or shell scripting outside of Azure Cloud Shell, and no Linux-first examples.
Recommendations
- Clarify that Azure PowerShell is primarily for Windows users, and recommend Azure CLI for Linux/macOS users.
- Provide explicit Bash/Linux/macOS instructions or notes where relevant, especially for local installations.
- Consider listing Azure CLI examples first, as it is the cross-platform default for Azure.
- Add a note explaining that Azure CLI commands work natively on Linux/macOS, while PowerShell is mainly for Windows.
- Include troubleshooting steps for Linux/macOS users (e.g., SSH key generation, file permissions) where appropriate.
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
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 given their own section and appear before Linux equivalents in some places. The examples and CLI commands are mostly cross-platform (bash/azurecli), but Windows-specific steps are highlighted and sometimes presented first. There is no evidence of missing Linux examples or exclusive use of Windows tools, but the Windows instructions are prominent.
Recommendations
- Ensure Linux and Windows instructions are presented in parallel sections, with clear headings for each OS.
- When providing CLI examples, clarify which OS each command applies to, and avoid presenting Windows-specific steps before Linux unless the feature is Windows-only.
- Consider grouping Linux and Windows node pool instructions together, or providing a summary table for parity.
- Explicitly state when a command or step is OS-agnostic.
- Review the order of sections to ensure Linux instructions are not overshadowed by Windows-specific content.
Aks
Create an OpenID Connect (OIDC) Provider for your Azure Kubernetes Service (AKS) Cluster
...ure-aks-docs/blob/main/articles/aks/use-oidc-issuer.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides Azure CLI examples using environment variable syntax ($VARIABLE) and command-line patterns that are compatible with both Linux/macOS and Windows (PowerShell). However, there is a subtle bias in that the examples use the '$VARIABLE' syntax, which is native to Bash (Linux/macOS) but also works in PowerShell on Windows. The documentation does not explicitly mention Linux/macOS or provide alternative Bash-specific instructions, nor does it clarify cross-platform compatibility. There are no Windows-only tools or PowerShell-specific commands, but the examples could be ambiguous for users unfamiliar with PowerShell or Bash.
Recommendations
- Explicitly state that the Azure CLI commands are cross-platform and work in Bash (Linux/macOS) and PowerShell (Windows).
- Add a note clarifying that '$VARIABLE' syntax is for Bash and PowerShell, and provide examples for both if needed.
- Consider including sample commands using export (for Bash) and $env:VARIABLE (for PowerShell) to demonstrate Linux/macOS and Windows usage.
- Mention that Azure CLI is available on all major platforms and link to installation instructions for each.