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 101-125 of 618 flagged pages
Aks Certificate Rotation in Azure Kubernetes Service (AKS) ...ks-docs/blob/main/articles/aks/certificate-rotation.md
Low Priority View Details →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation is generally cross-platform and AKS is a Linux-first service, but there is a minor bias in the section 'Verify TLS Bootstrapping is enabled on current agent node pool', where Windows file paths are mentioned immediately after Linux paths, and no explicit Linux command-line example is given for checking the file. Additionally, in certificate verification output examples, Windows node names (e.g., akswinp7000000) are shown, but Linux node examples are not. However, all command-line instructions use bash/Azure CLI, which are cross-platform and primarily Linux-focused.
Recommendations
  • Provide explicit Linux command-line examples for verifying TLS Bootstrapping, such as using 'ls' or 'cat' to check the existence and contents of '/var/lib/kubelet/bootstrap-kubeconfig'.
  • Include Linux node name examples in output snippets alongside Windows node names to clarify parity.
  • Where file paths are mentioned, clarify the OS context and provide commands for both Linux and Windows nodes.
  • Ensure that any output examples or instructions referencing Windows nodes are balanced with Linux node equivalents.
GitHub Create Pull Request
Aks Integrate Azure Container Registry with Azure Kubernetes Service (AKS) ...articles/aks/cluster-container-registry-integration.md
Low Priority View Details →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides parallel examples for both Azure CLI and Azure PowerShell throughout, but the inclusion of PowerShell is a sign of Windows bias, as PowerShell is primarily a Windows-centric tool (though it is available cross-platform). The page consistently presents Azure CLI and PowerShell examples side-by-side, but PowerShell is referenced in the metadata and tool tracking, and is given equal prominence to Azure CLI. There are no Linux-specific examples, and no mention of Bash scripting or Linux shell usage. However, Azure CLI commands are cross-platform and the documentation does not use Windows-only tools or patterns. The severity is low, as Linux/macOS users can complete all tasks using Azure CLI.
Recommendations
  • Clarify that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
  • Add a brief note that PowerShell examples are optional and Azure CLI is recommended for Linux/macOS.
  • Consider including Bash shell scripting examples or highlighting Linux-native workflows where relevant.
  • Ensure that Azure CLI examples are shown first, or explicitly state that both CLI and PowerShell are supported equally.
GitHub Create Pull Request
Aks Configure Azure CNI Networking in Azure Kubernetes Service (AKS) ...aks-docs/blob/main/articles/aks/configure-azure-cni.md
Low Priority View Details →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides examples for Azure portal, Azure PowerShell, and Azure CLI, covering both Windows and Linux environments. However, the PowerShell section is notably detailed, with explicit instructions for installing/upgrading PowerShell on Windows, macOS, and Linux, and references to PowerShell-specific workflows. Additionally, PowerShell instructions are presented before Azure CLI, which is more universally cross-platform. There is a slight bias toward Windows/PowerShell patterns, but Linux users are not blocked from completing the task.
Recommendations
  • Present Azure CLI instructions before PowerShell, as CLI is more cross-platform and preferred by many Linux/macOS users.
  • Add explicit notes clarifying that both Azure CLI and PowerShell can be used on Linux/macOS, and highlight CLI as the recommended option for non-Windows users.
  • Ensure parity in detail between PowerShell and CLI sections, such as including troubleshooting or environment preparation steps for CLI users.
  • Consider adding a brief comparison table of CLI vs PowerShell for AKS operations, emphasizing cross-platform support.
GitHub Create Pull Request
Aks Concepts - Storage in Azure Kubernetes Services (AKS) ...re-aks-docs/blob/main/articles/aks/concepts-storage.md
Low Priority View Details →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation is generally platform-neutral and covers storage concepts for AKS without favoring Windows-specific tools or patterns. However, in the section on mounting volumes in pods, the Windows example is presented immediately after the Linux example, which could be perceived as a minor 'windows_first' bias. No PowerShell or Windows-only tooling is referenced, and Linux parity is maintained throughout the document.
Recommendations
  • Ensure Linux and Windows examples are presented with equal prominence, perhaps by grouping them together or explicitly labeling them as platform-specific.
  • Consider adding clarifying notes to examples to indicate which OS they apply to, especially in YAML manifests.
  • If possible, provide both Linux and Windows examples side-by-side for volume mounting to reinforce parity.
GitHub 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 →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation references Azure PowerShell alongside Azure CLI and the Azure portal as migration tools, but does not provide PowerShell-specific examples. The Azure CLI is used for all command-line examples, which are cross-platform. However, Azure PowerShell is mentioned before Azure CLI in the migration step, and there is no explicit mention that Azure PowerShell is Windows-only or that Azure CLI is preferred for Linux/macOS users. All example manifests and kubectl commands are Linux-oriented, and there are no Windows-specific Kubernetes node pool references.
Recommendations
  • Clarify that Azure PowerShell is primarily for Windows users and recommend Azure CLI for Linux/macOS.
  • List Azure CLI before Azure PowerShell when describing migration options to prioritize cross-platform tools.
  • Optionally, provide a brief note about Azure PowerShell's platform limitations.
  • Ensure that all example commands are available for both Azure CLI and Azure PowerShell, or explicitly state which platforms each tool supports.
GitHub Create Pull Request
Aks Access Kubernetes Resources using the Azure Portal ...e-aks-docs/blob/main/articles/aks/kubernetes-portal.md
Low Priority View Details →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for updating AKS cluster 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 manifests explicitly target Linux node pools. The overall bias is minimal and does not impede Linux/macOS users.
Recommendations
  • Maintain parity by continuing to provide both Azure CLI and Azure PowerShell examples.
  • Consider clarifying that Azure CLI works on Windows, Linux, and macOS, while PowerShell is primarily for Windows users (though available cross-platform).
  • If possible, add a short note for each command section indicating platform compatibility.
  • Ensure future troubleshooting or advanced sections do not default to Windows-only tools or instructions.
GitHub Create Pull Request
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 →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation is generally cross-platform and AKS-centric, with most examples using Linux conventions and tools (bash, Azure CLI, kubectl). However, there are minor signs of Windows bias: Windows paths and PowerShell/CMD syntax are mentioned in a few places, and Windows-specific instructions sometimes appear before Linux equivalents or are highlighted in notes. The section on Windows containers provides both Linux/Mac and Windows PowerShell/CMD commands, but Linux is shown first. Overall, Linux parity is strong, but Windows is occasionally foregrounded.
Recommendations
  • Ensure Linux/macOS examples are always shown first, with Windows-specific notes clearly separated.
  • Where Windows paths or PowerShell/CMD syntax are mentioned, provide equivalent Linux/macOS examples side-by-side.
  • Clarify when instructions are Windows-only or Linux-only to avoid confusion.
  • Review output examples to ensure they are not Windows-centric unless the section is explicitly about Windows containers.
GitHub Create Pull Request
Aks Create an internal load balancer ...s/azure-aks-docs/blob/main/articles/aks/internal-lb.md
Low Priority View Details →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation provides both Azure CLI and PowerShell options for some prerequisite steps, but the PowerShell tool is mentioned alongside Azure CLI and portal, and a PowerShell cmdlet is referenced for subnet listing. However, all actual operational examples (creating manifests, deploying, querying services) use kubectl and Azure CLI, which are cross-platform. The PowerShell references are not exclusive or prioritized, but their presence without equivalent Linux/macOS alternatives (e.g., Bash, shell scripting) may create minor friction for non-Windows users.
Recommendations
  • When referencing PowerShell cmdlets (e.g., Get-AzVirtualNetworkSubnetConfig), always provide the equivalent Azure CLI command (which is already present for subnet listing).
  • Consider clarifying that Azure CLI is fully cross-platform and preferred for Linux/macOS users, and PowerShell is optional for Windows users.
  • If mentioning PowerShell, ensure Linux/macOS users are not left wondering if a step is Windows-only; explicitly state that Azure CLI is recommended for non-Windows platforms.
  • Avoid listing PowerShell before Azure CLI unless the task is Windows-specific.
GitHub Create Pull Request
Aks Stop and start an Azure Kubernetes Service (AKS) cluster ...-aks-docs/blob/main/articles/aks/start-stop-cluster.md
Low Priority View Details →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for stopping and starting AKS clusters. Azure CLI is cross-platform (Linux, macOS, Windows), while Azure PowerShell is primarily used on Windows (though it is available on Linux/macOS). The examples are presented in parallel tabs, but the introductory section lists Azure CLI, Azure PowerShell, and Azure Portal in that order, and PowerShell examples are given equal prominence. There are no Windows-only tools or patterns, and no missing Linux/macOS examples, but PowerShell is a Windows-centric tool and its inclusion alongside CLI may create minor bias.
Recommendations
  • Clarify that Azure CLI is the recommended cross-platform tool for Linux/macOS users.
  • Consider adding a note that Azure PowerShell is available on Linux/macOS, but Azure CLI is more commonly used on those platforms.
  • Ensure that Azure CLI examples are shown first or marked as the default for cross-platform scenarios.
  • Optionally, add a Bash shell example for Linux users (though Azure CLI commands are already suitable).
GitHub Create Pull Request
Aks Upgrade Azure Kubernetes Service (AKS) node images ...-aks-docs/blob/main/articles/aks/upgrade-node-image.md
Low Priority View Details →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows Reference
Summary
The documentation is largely cross-platform, focusing on Azure CLI and kubectl commands, which are available on Linux, macOS, and Windows. There are brief references to Windows and PowerShell environments in notes about shell differences, but no Windows-specific examples, tools, or patterns are prioritized or exclusively presented.
Recommendations
  • Clarify that all CLI and kubectl commands work on Linux, macOS, and Windows.
  • If shell differences are significant, provide example commands for both Bash (Linux/macOS) and PowerShell (Windows), or link to relevant shell-specific guidance.
  • Consider adding a brief section or note for macOS users if there are any unique considerations.
GitHub Create Pull Request
Aks Kubernetes on Azure tutorial - Upgrade an Azure Kubernetes Service (AKS) cluster ...in/articles/aks/tutorial-kubernetes-upgrade-cluster.md
Low Priority View Details →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides parity between Azure CLI, Azure PowerShell, and Azure portal methods for upgrading AKS clusters. However, Azure PowerShell examples are presented alongside Azure CLI examples throughout, and PowerShell version requirements are mentioned in the 'Before you begin' section. Azure PowerShell is a Windows-centric tool, and its inclusion may suggest a Windows bias, especially since PowerShell is not as commonly used on Linux/macOS. However, Azure CLI is cross-platform and is always presented first, and all examples are available for Linux/macOS users. No critical tasks are Windows-only, and Linux parity is maintained.
Recommendations
  • Clarify that Azure CLI is recommended for Linux/macOS users, and PowerShell is primarily for Windows users.
  • Consider adding a note in the 'Before you begin' section indicating that Azure CLI is cross-platform and PowerShell is most commonly used on Windows.
  • Ensure that Azure CLI examples remain first in all sections to reinforce Linux/macOS parity.
  • Optionally, provide bash shell script examples for common tasks to further support Linux/macOS users.
GitHub Create Pull Request
Aks Secure Pod Traffic with Network Policies in Azure Kubernetes Service (AKS) ...ks-docs/blob/main/articles/aks/use-network-policies.md
Low Priority View Details →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides examples and instructions for both Linux and Windows node pools in AKS, but Windows-specific steps (such as registering feature flags and creating Windows admin credentials) are given prominent, detailed sections. Windows node pool creation is described in depth, including preview features and CLI steps, while Linux instructions are more concise. Some CLI commands (az CLI) are cross-platform, but Windows-specific tools and concepts (HNS ACLPolicies, Windows admin username/password) are mentioned before or in more detail than their Linux equivalents. However, Linux parity is generally maintained, and most critical tasks are achievable on Linux.
Recommendations
  • Ensure Linux and Windows instructions are equally detailed and structured.
  • Where Windows-specific steps are described (feature flag registration, admin credential creation), provide clear Linux equivalents or clarify that these steps are not needed for Linux.
  • Avoid placing Windows node pool instructions before Linux unless the feature is Windows-only.
  • Consider grouping Linux and Windows instructions separately to avoid confusion.
  • Explicitly state which steps are OS-specific and which are cross-platform.
GitHub Create Pull Request
Aks Configure Azure CNI Networking in Azure Kubernetes Service (AKS) ...aks-docs/blob/main/articles/aks/configure-azure-cni.md
Low Priority View Details →
Scanned: 2026-03-07 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides examples for Azure portal, Azure PowerShell, and Azure CLI, covering both Windows and Linux environments. However, the PowerShell section is notably detailed, with explicit instructions for installing/upgrading PowerShell on Windows, macOS, and Linux, and references to Windows-specific tools (e.g., Connect-AzAccount). The PowerShell section appears before the CLI section, which is more universally used across platforms. While Linux and macOS are mentioned for PowerShell installation, the overall structure and emphasis favor Windows/PowerShell patterns.
Recommendations
  • Present Azure CLI examples before PowerShell, as CLI is more platform-neutral and widely used.
  • Ensure equal detail for Azure CLI instructions, including environment preparation and troubleshooting for Linux/macOS users.
  • Add explicit notes or links for Linux/macOS users regarding any differences or prerequisites for Azure CLI usage.
  • Consider highlighting Azure CLI as the recommended cross-platform tool for AKS management.
GitHub Create Pull Request
Aks Develop on Azure Kubernetes Service (AKS) with Helm ...ure-aks-docs/blob/main/articles/aks/quickstart-helm.md
Low Priority View Details →
Scanned: 2026-03-07 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all Azure-related operations, but consistently presents Azure CLI (which is cross-platform) first and Azure PowerShell (which is Windows-centric) second. There are no Linux-specific examples or explicit mentions of Linux tools, but the use of Azure CLI covers Linux/macOS users. No critical steps are Windows-only, but the PowerShell examples may create an impression of Windows preference.
Recommendations
  • Clarify that Azure CLI is fully cross-platform and recommended for Linux/macOS users.
  • Consider adding explicit notes or callouts for Linux/macOS users, especially in the prerequisites section.
  • Optionally, provide bash shell script examples for end-to-end workflow, or highlight that all CLI commands work on Linux/macOS.
  • Remove or de-emphasize PowerShell examples unless there is a specific Windows audience need.
  • Add a table or section summarizing OS compatibility for each tool (Azure CLI, PowerShell, Helm, kubectl).
GitHub Create Pull Request
Aks Secure Pod Traffic with Network Policies in Azure Kubernetes Service (AKS) ...ks-docs/blob/main/articles/aks/use-network-policies.md
Low Priority View Details →
Scanned: 2026-03-07 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
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 preview features and creating Windows admin credentials) are given prominent placement and detail. The Windows node pool creation section is longer and more detailed than the Linux section, and Windows-specific tooling (like HNS ACLPolicy) is mentioned alongside Linux equivalents (IPTables). However, Linux parity is generally maintained, and all critical tasks are possible on Linux.
Recommendations
  • Ensure Linux and Windows instructions are equally detailed and structured.
  • Where possible, present Linux and Windows examples side-by-side or clearly separated, rather than Windows-first.
  • Clarify when steps are Windows-only versus Linux-only to reduce confusion.
  • Add explicit notes or links for Linux users when Windows-specific steps are described.
  • Review the order of sections to avoid implicit prioritization of Windows workflows.
GitHub Create Pull Request
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 →
Scanned: 2026-03-07 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides installation and usage instructions for the Agentic CLI for AKS, supporting both client (local/Docker) and cluster (Helm/Kubernetes) modes. In the section about starting the Docker daemon, instructions for macOS/Windows (Docker Desktop) are presented before Linux (systemctl commands). However, all examples and instructions are cross-platform, and Linux-specific commands are included where relevant. No PowerShell-only examples, Windows-only tools, or missing Linux equivalents are found.
Recommendations
  • Consider presenting Linux instructions before or alongside Windows/macOS instructions in sections like 'Start the Docker daemon', to avoid subtle ordering bias.
  • Explicitly mention that all commands (e.g., Azure CLI, Docker) are cross-platform and provide links to Linux/macOS installation guides where possible.
  • Ensure parity in troubleshooting and cleanup instructions for all platforms, including any nuances for Linux (such as Docker daemon management or file locations).
GitHub Create Pull Request
Aks Troubleshoot the Agentic CLI for Azure Kubernetes Service (AKS) .../main/articles/aks/agentic-cli-for-aks-troubleshoot.md
Low Priority View Details →
Scanned: 2026-03-07 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation generally provides cross-platform troubleshooting steps for the Agentic CLI for AKS, with explicit instructions for Linux, macOS, and Windows. However, in the Docker troubleshooting section, instructions for starting Docker are presented as 'macOS/Windows' first, with Linux instructions following. This ordering may create a minor perception of Windows/macOS priority, but all platforms are covered and Linux-specific commands are present.
Recommendations
  • Present platform instructions in a consistent order (e.g., Linux, macOS, Windows or alphabetical) to avoid perceived prioritization.
  • Where possible, group platform instructions together under clear headings (e.g., 'On Linux', 'On macOS', 'On Windows') for clarity.
  • Ensure that all examples and solutions are present for each supported platform, as is already done here.
GitHub Create Pull Request
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 →
Scanned: 2026-03-07 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides a generally cross-platform approach, with download links and instructions for Windows, macOS, and Linux. However, there are subtle signs of Windows bias: VS Code keyboard shortcuts and extension installation instructions consistently list Windows shortcuts first, and some tips (e.g., WSL configuration) are Windows-centric. The Docker section includes notes about Windows-specific credential issues, but does not provide equivalent troubleshooting for Linux/macOS. There are no explicit Linux/macOS command-line examples (e.g., for setting file permissions or troubleshooting), and troubleshooting tips focus more on Windows scenarios.
Recommendations
  • Alternate keyboard shortcut order between Windows and Linux/macOS, or list both equally.
  • Add Linux/macOS-specific troubleshooting tips (e.g., file permissions, environment variable setup, Docker user IDs).
  • Provide explicit Linux/macOS command-line examples for common tasks (e.g., setting executable permissions on downloaded binaries, verifying paths).
  • Expand Docker credential troubleshooting to include Linux/macOS scenarios.
  • Ensure that all platform-specific notes (such as WSL) are matched with equivalent guidance for Linux/macOS users.
GitHub Create Pull Request
Aks Certificate Rotation in Azure Kubernetes Service (AKS) ...ks-docs/blob/main/articles/aks/certificate-rotation.md
Low Priority View Details →
Scanned: 2026-03-07 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation is generally cross-platform and AKS is a Linux-first service, but there is a minor bias in the section 'Verify TLS Bootstrapping is enabled on current agent node pool', where the Windows node path ('C:\k\bootstrap-config') is mentioned after the Linux path. However, there are no PowerShell-specific examples, Windows tools, or Windows-only commands. All command-line examples use Azure CLI and Bash, which are cross-platform and primarily Linux-focused. The documentation does not provide Windows-specific command examples or instructions, nor does it omit Linux equivalents.
Recommendations
  • When mentioning file paths for both Linux and Windows, consider listing Linux first (as AKS is primarily Linux-based) and clarifying parity for both OSes.
  • If possible, provide explicit instructions for accessing Windows node paths (e.g., using PowerShell or Windows-native tools) to match the detail level of Linux instructions.
  • Ensure that any troubleshooting or maintenance instructions for Windows nodes are as detailed as those for Linux nodes.
  • Add a note clarifying that Azure CLI and Bash commands are cross-platform and can be run on Windows via WSL, Git Bash, or Azure Cloud Shell.
GitHub Create Pull Request
Aks Integrate Azure Container Registry with Azure Kubernetes Service (AKS) ...articles/aks/cluster-container-registry-integration.md
Low Priority View Details →
Scanned: 2026-03-07 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides parallel examples for Azure CLI and Azure PowerShell throughout, but PowerShell (a Windows-centric tool) is featured equally with Azure CLI. There are no Linux-specific shell examples (e.g., Bash), and PowerShell is presented as a primary option alongside Azure CLI, which may create friction for Linux/macOS users. Additionally, the documentation references PowerShell modules and commands without mentioning Linux-native alternatives or clarifying PowerShell Core cross-platform support. Azure CLI is cross-platform, but the prominence of PowerShell and lack of explicit Linux/Bash examples constitute a mild Windows bias.
Recommendations
  • Clarify that Azure PowerShell can be used on Linux/macOS via PowerShell Core, or link to installation instructions for non-Windows platforms.
  • Add Bash shell examples for Azure CLI commands, showing variable assignment and command usage in Bash syntax.
  • Explicitly state that Azure CLI is recommended for Linux/macOS users, and PowerShell is optional.
  • Consider including a section on using Terraform (already referenced) for users preferring infrastructure-as-code and cross-platform tooling.
  • Where PowerShell is mentioned, note its cross-platform capabilities or provide links to relevant documentation.
GitHub Create Pull Request
Aks Concepts - Storage in Azure Kubernetes Services (AKS) ...re-aks-docs/blob/main/articles/aks/concepts-storage.md
Low Priority View Details →
Scanned: 2026-03-07 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation is generally cross-platform and AKS-centric, focusing on Azure storage options for Kubernetes clusters. However, in the section describing how to mount volumes in pods, Windows container examples are provided immediately after the Linux example, with no additional Linux-specific guidance or parity in example complexity. The Windows example is given its own explicit subsection, which could be perceived as 'windows_first' bias, though the impact is minor.
Recommendations
  • Ensure Linux and Windows examples are presented with equal prominence and detail.
  • If showing a Windows-specific YAML snippet, also provide a Linux-specific snippet with similar complexity and explanation.
  • Clarify that Linux paths use forward slashes and Windows paths use drive letters and backslashes, to help users unfamiliar with both.
  • Consider grouping OS-specific examples under a clear 'Linux example' and 'Windows example' heading for parity.
GitHub Create Pull Request
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 →
Scanned: 2026-03-07 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation is generally cross-platform and Linux-focused, but there are minor signs of Windows bias. Windows-specific instructions and path conventions are mentioned in several places, sometimes before or alongside Linux equivalents. In the 'Use Azure Files with Windows containers' section, both Linux/MacOS and Windows PowerShell/CMD commands are provided, but the Windows variant is shown second. Windows path conventions are referenced in pod manifests, but Linux examples are predominant throughout. Azure CLI (cross-platform) is used for setup, and PowerShell is not used for core tasks.
Recommendations
  • Ensure Linux and Windows instructions/examples are always paired and equally prominent.
  • Where Windows-specific path conventions are mentioned, clarify Linux defaults and highlight parity.
  • If Windows-specific commands are given, provide Linux/MacOS equivalents first or in parallel.
  • Review output examples to ensure they are not Windows-centric unless contextually relevant.
  • Consider a brief section summarizing Linux/macOS compatibility and any limitations.
GitHub 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 →
Scanned: 2026-03-07 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation mentions Azure PowerShell as a tool for moving resources, alongside Azure CLI and the Azure portal. Azure PowerShell is a Windows-centric tool, and its mention before Azure CLI (which is cross-platform) may suggest a slight Windows bias. However, all command examples throughout the guide use Azure CLI and bash/kubectl, which are cross-platform and Linux-friendly. No PowerShell-specific commands or Windows-only patterns are present.
Recommendations
  • List Azure CLI before Azure PowerShell when describing migration options, emphasizing CLI as the default cross-platform tool.
  • Clarify that Azure PowerShell is optional and primarily for users already on Windows, while Azure CLI works on Linux/macOS/Windows.
  • Consider linking to Linux/macOS installation instructions for Azure CLI.
  • If mentioning Azure PowerShell, briefly note its platform limitations.
GitHub Create Pull Request
Aks Create an internal load balancer ...s/azure-aks-docs/blob/main/articles/aks/internal-lb.md
Low Priority View Details →
Scanned: 2026-03-07 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation provides both Azure CLI and PowerShell options for some prerequisite steps, but Azure CLI is used for all main examples. However, PowerShell is mentioned before Azure CLI in the 'Before you begin' section, and a PowerShell cmdlet is referenced alongside Azure CLI for subnet listing. There are no Linux/macOS-specific examples or explicit parity notes, but the main workflow uses cross-platform tools (kubectl, Azure CLI).
Recommendations
  • List Azure CLI before PowerShell in prerequisite sections to emphasize cross-platform tools.
  • Explicitly note that Azure CLI and kubectl are cross-platform and preferred for Linux/macOS users.
  • Provide Linux/macOS-specific guidance for any steps where PowerShell is referenced (e.g., subnet listing), or clarify that Azure CLI is the recommended approach.
  • Consider removing PowerShell references unless they are necessary for Windows-only scenarios, or provide equivalent Bash commands.
GitHub Create Pull Request
Aks Install Dapr Extension for Azure Kubernetes Service (AKS) ...softDocs/azure-aks-docs/blob/main/articles/aks/dapr.md
Low Priority View Details →
Scanned: 2026-03-07 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation is generally cross-platform, using Azure CLI and Bicep for all main instructions, which are supported on Windows, Linux, and macOS. However, in the 'List the CRDs in your cluster' section, the example uses 'kubectl get crds | findstr dapr.io', which employs the Windows-specific 'findstr' command. There is no equivalent Linux/macOS example (e.g., using 'grep'), which may cause confusion or friction for non-Windows users.
Recommendations
  • Provide both Windows and Linux/macOS command examples when using OS-specific tools. For example, add 'kubectl get crds | grep dapr.io' as the Linux/macOS equivalent.
  • Where possible, prefer cross-platform commands or explicitly note OS differences.
  • Review for any other subtle Windows-first patterns, though none are apparent in the main installation flow.
GitHub Create Pull Request
← Previous Page 5 of 25 Next →