Aks

535
Total Pages
430
Linux-Friendly Pages
105
Pages with Bias
19.6%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

365 issues found
Showing 251-275 of 365 flagged pages
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-01-30 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation provides both Linux and Windows examples for AKS network policy engines, but Windows-specific instructions (such as registering preview features and creating Windows admin credentials) are presented in a dedicated section immediately after the Linux instructions. The documentation references Windows-specific tools (Host Network Service ACLPolicies) and includes Windows node pool configuration steps. However, Linux instructions and examples are present and complete, and the overall flow does not prevent Linux/macOS users from following the guide.
Recommendations
  • Ensure that Linux and Windows instructions are presented with equal prominence, possibly by grouping them under parallel headings (e.g., 'Create an AKS cluster with Azure Network Policy Manager (Linux)' and '(Windows)').
  • Where possible, provide side-by-side examples for both Linux and Windows node pool creation, rather than separating them into sequential sections.
  • Clarify in each section which operating system the instructions apply to, to reduce confusion.
  • Ensure that Linux-specific limitations and features are as thoroughly documented as Windows-specific ones.
  • If Windows-specific tools or patterns are mentioned (e.g., HNS ACLPolicies), briefly note the Linux equivalents (e.g., IPTables/BPF) for parity.
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-01-27 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides parallel instructions for Azure CLI, Azure PowerShell, and Azure portal. However, Azure PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and examples for both are provided in every section. In some sections, PowerShell is listed before the portal, and the introductory context mentions Azure PowerShell before Azure portal. There are no Linux-specific examples or notes about platform differences, and the use of PowerShell may create friction for Linux/macOS users who typically use Bash and Azure CLI.
Recommendations
  • Clarify that Azure PowerShell is available cross-platform, but most Linux/macOS users prefer Azure CLI.
  • List Azure CLI examples before Azure PowerShell in each section, as CLI is the default on Linux/macOS.
  • Add a note at the start explaining which tools are recommended for each OS (e.g., CLI for Linux/macOS, PowerShell for Windows).
  • Consider removing PowerShell examples from the main flow or moving them to an appendix, unless there is a strong user base for PowerShell on Linux/macOS.
  • Explicitly mention that all CLI commands work on Linux, macOS, and Windows, and provide troubleshooting links for non-Windows platforms if needed.
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-01-27 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI (Linux/macOS-friendly) and Azure PowerShell (Windows-centric) instructions for managing AKS authorized IP ranges and credentials. However, the PowerShell tab is presented immediately after the CLI tab, and both are given equal prominence. There are no examples or references to Windows-only tools or patterns outside of PowerShell, and the main workflow is portal-based (cross-platform). No Linux/macOS-specific examples are missing, but the PowerShell instructions may be unnecessary for most non-Windows users.
Recommendations
  • Make clear that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Consider listing Azure CLI instructions first or labeling them as recommended for Linux/macOS.
  • Add a brief note clarifying that PowerShell instructions are primarily for Windows users.
  • If possible, provide bash-only examples for Linux/macOS users where relevant.
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-01-27 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all Azure-related operations, with PowerShell examples presented in parallel tabs. There is a slight Windows bias in that PowerShell is featured as an equal alternative to Azure CLI, even though Azure CLI is cross-platform and PowerShell is most commonly used on Windows. However, the core workflow (Helm, kubectl, git, bash commands) is presented in a platform-neutral way, and no critical steps are Windows-only. The Azure CLI is shown first in each section, which helps Linux/macOS parity.
Recommendations
  • Clarify that Azure PowerShell is available on Linux/macOS, or note that Azure CLI is recommended for cross-platform use.
  • Consider adding a brief note at the start of the prerequisites section indicating that all steps can be completed on Linux/macOS using Azure CLI and bash.
  • If possible, add explicit confirmation that all bash commands (git, helm, kubectl) work on Linux/macOS and Windows (with WSL or native tools).
  • Optionally, add a 'Linux/macOS' tab in sections where platform-specific instructions might be relevant, even if the commands are the same.
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-01-26 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all Azure resource creation and management steps, with clear tabbed separation. However, PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and in some places, PowerShell examples are shown before or alongside CLI, which may imply parity or preference for Windows users. There are no Linux-specific examples or notes, and the prerequisites mention both Azure CLI and Azure PowerShell without clarifying that CLI is cross-platform and PowerShell is primarily Windows-focused (though PowerShell Core is available on Linux/macOS). All Helm and kubectl commands are shown in bash syntax, which is cross-platform, and there are no Windows-only tools or patterns used. The documentation does not omit Linux/macOS equivalents, but the presence of PowerShell throughout may create mild friction for non-Windows users.
Recommendations
  • Clarify in prerequisites that Azure CLI is cross-platform and preferred for Linux/macOS, while Azure PowerShell is primarily for Windows (with PowerShell Core available for Linux/macOS).
  • Consider showing Azure CLI examples first, as CLI is the default and most widely used cross-platform tool.
  • Add a note or section for Linux/macOS users confirming that all CLI commands work natively, and that PowerShell examples are optional.
  • If possible, provide explicit bash/zsh shell examples for resource management steps, or link to Linux/macOS setup guides.
  • Ensure that tabbed examples default to Azure CLI (not PowerShell) for broader accessibility.
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-01-26 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides parallel instructions for Azure CLI, Azure PowerShell, and Azure portal, but PowerShell examples and references are prominent throughout. PowerShell is a Windows-centric tool, and its inclusion alongside Azure CLI (which is cross-platform) may suggest a slight Windows bias. In some sections, PowerShell instructions are listed before or equally with CLI, rather than CLI being clearly prioritized for Linux/macOS users. However, all tasks can be completed using Azure CLI, which works on Linux and macOS, and there are no Windows-only tools or patterns required.
Recommendations
  • Explicitly state that Azure CLI is cross-platform and recommended for Linux/macOS users.
  • List Azure CLI instructions before PowerShell in each tabbed section to subtly prioritize Linux/macOS parity.
  • Add a brief note clarifying that PowerShell is primarily for Windows users, while CLI works on all platforms.
  • Consider reducing the prominence of PowerShell examples unless there is a Windows-specific scenario.
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-01-24 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides parallel instructions for Azure CLI, Azure PowerShell, and Azure portal. However, Azure PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and examples for PowerShell are present throughout. In some sections, PowerShell examples appear before portal instructions, and the introductory context mentions Azure PowerShell before Azure CLI. There are no Linux-specific examples or notes about differences for Linux/macOS users, but the CLI instructions are cross-platform. No critical tasks are Windows-only, and Linux users can complete all steps using Azure CLI.
Recommendations
  • Clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Consider listing Azure CLI instructions before Azure PowerShell in each section.
  • Add a brief note at the start explaining that Azure PowerShell is primarily for Windows, while Azure CLI works on all platforms.
  • Where possible, highlight any platform-specific considerations (e.g., shell syntax differences) for Linux/macOS users.
  • Ensure that CLI examples are shown first, as the default/preferred method for most users.
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-01-23 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides parallel instructions for Azure CLI, Azure PowerShell, and Azure portal throughout. However, Azure PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and in some sections, PowerShell examples are presented before or alongside CLI examples. There is a slight 'windows_first' bias in the ordering and inclusion of PowerShell, but Linux users can fully complete all tasks using the Azure CLI, which is cross-platform. No critical steps are Windows-only, and Linux parity is maintained.
Recommendations
  • Consider listing Azure CLI examples before Azure PowerShell in all sections, as CLI is cross-platform and preferred by many Linux/macOS users.
  • Explicitly note that Azure CLI is available on Linux/macOS and is recommended for non-Windows environments.
  • Where PowerShell is mentioned, clarify that it is primarily for Windows users, and that CLI is the preferred option for Linux/macOS.
  • Ensure screenshots and portal instructions do not assume Windows-only conventions (e.g., file paths, UI elements).
GitHub Create Pull Request
Aks Deploy an Amazon Web Services (AWS) web application to Azure ...zure-aks-docs/blob/main/articles/aks/eks-web-deploy.md
Low Priority View Details →
Scanned: 2026-01-14 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 resource management tasks (listing and deleting resources), but presents Azure CLI examples first and PowerShell examples second. All deployment and operational scripts are written in Bash, which is Linux/macOS-friendly and neutral. No Windows-specific tools, patterns, or PowerShell-only instructions are present in the core deployment workflow. There are no missing Linux examples, and no Windows-only tools are used.
Recommendations
  • Consider alternating the order of Azure CLI and PowerShell tabs, or explicitly state that Azure CLI is cross-platform while PowerShell is primarily for Windows (though it is available on Linux/macOS).
  • Add a brief note clarifying that Bash scripts are intended for Linux/macOS environments, and Windows users should use WSL or a compatible shell.
  • If possible, provide PowerShell equivalents for Bash scripts or link to guidance for running Bash scripts on Windows.
GitHub Create Pull Request
Aks Quickstart: Deploy an Azure Kubernetes Service (AKS) cluster using an ARM template ...icles/aks/learn/quick-kubernetes-deploy-rm-template.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for all major steps, but examples and tabs for PowerShell are presented alongside CLI, and in some sections, PowerShell is mentioned before Linux-native alternatives. There is no explicit Linux/macOS example section, and PowerShell is treated as a primary workflow, which may create friction for Linux/macOS users who do not use PowerShell. However, Azure CLI is cross-platform and all critical tasks can be completed using CLI, which is well documented.
Recommendations
  • Make clear that Azure CLI is fully supported and cross-platform, and recommend it as the default for Linux/macOS users.
  • Present Azure CLI examples before PowerShell examples, or clarify that CLI is the preferred method for Linux/macOS.
  • Add explicit notes or sections for Linux/macOS users, confirming that all steps can be completed without PowerShell.
  • Where PowerShell is referenced, clarify that it is optional and not required for Linux/macOS users.
  • Consider removing or de-emphasizing PowerShell tabs unless there is a Windows-specific need.
GitHub Create Pull Request
Aks Deploy an AI Model on Azure Kubernetes Service (AKS) with the AI Toolchain Operator in the Azure Portal (Preview) ...ain/articles/aks/ai-toolchain-operator-azure-portal.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI (cross-platform) and Azure PowerShell (Windows-centric) instructions for connecting to AKS, but lists Azure CLI first. There is no evidence of exclusive Windows tooling or missing Linux/macOS examples. The use of Azure Cloud Shell (which is cross-platform and browser-based) is encouraged, and all critical commands (kubectl, az) are available on Linux/macOS. No steps are Windows-only, and no Windows-specific tools are required.
Recommendations
  • Explicitly mention that Azure CLI and kubectl are available on Linux/macOS and provide links to installation instructions for those platforms.
  • Clarify that Azure PowerShell is primarily for Windows users, and suggest Azure CLI for Linux/macOS users.
  • Add a brief note in the prerequisites or connection section indicating that all steps are cross-platform unless otherwise stated.
GitHub Create Pull Request
Aks Create an AKS-managed GPU node pool on Azure Kubernetes Service (AKS) ...s-docs/blob/main/articles/aks/aks-managed-gpu-nodes.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation mentions Windows/PowerShell as a primary method for creating AKS clusters before Linux alternatives, and includes a quickstart link for Azure PowerShell alongside Azure CLI and Portal. However, all actual examples and instructions for GPU node pool creation use Azure CLI, which is cross-platform. No PowerShell or Windows-specific commands are shown for the main workflow, and Linux (Ubuntu and Azure Linux) is the only supported OS for managed GPU node pools. Windows node pools are explicitly called out as unsupported for this feature.
Recommendations
  • List Azure CLI as the primary recommended method for cluster creation, with PowerShell and Portal as alternatives, to avoid implying Windows-first workflows.
  • If mentioning PowerShell, clarify its cross-platform support or provide parity examples for Linux/macOS users where relevant.
  • Consider moving Linux/CLI instructions before mentioning PowerShell in 'Before you begin' to reinforce Linux parity.
  • Ensure that any future examples for cluster creation or management include both CLI and PowerShell (if PowerShell is relevant and cross-platform), or clarify platform limitations.
GitHub Create Pull Request
Aks Fine-tune and deploy an AI model on Azure Kubernetes Service (AKS) with the AI toolchain operator add-on ...b/main/articles/aks/ai-toolchain-operator-fine-tune.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation references Windows/PowerShell tooling before Linux equivalents in the AKS cluster creation step, listing Azure PowerShell and Azure CLI (cross-platform) together, but mentioning PowerShell before the Azure portal and CLI. However, all technical examples and commands throughout the main workflow use cross-platform tools (Azure CLI, kubectl, bash), and no Windows-only tools or patterns are present in the core instructions.
Recommendations
  • List Azure CLI (cross-platform) before Azure PowerShell in the 'Before you begin' section to signal Linux parity.
  • Explicitly note that all command-line examples work on Linux, macOS, and Windows.
  • Consider adding a brief note or link for Linux/macOS users about shell compatibility if environment variable syntax or quoting may differ.
  • If possible, provide links to Linux/macOS-specific quickstart guides alongside PowerShell and portal options.
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-01-14 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation generally provides Linux-centric examples and commands, but in the section 'Verify TLS Bootstrapping is enabled on current agent node pool', the file path for Linux is listed before the Windows path. This is a minor instance of ordering bias, but overall, the documentation is balanced and provides parity for both Linux and Windows users. No critical sections are Windows-only, and all commands are cross-platform or Linux-focused.
Recommendations
  • Continue listing Linux and Windows paths together when relevant.
  • Consider adding explicit notes or examples for both Linux and Windows where file paths or commands differ, especially in troubleshooting scenarios.
  • Ensure parity in troubleshooting and verification steps for both OS types if future updates introduce OS-specific procedures.
GitHub Create Pull Request
Aks Concepts - Access and identity in Azure Kubernetes Services (AKS) ...e-aks-docs/blob/main/articles/aks/concepts-identity.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation page is generally cross-platform and does not focus on Windows-specific features or tools. However, there is a subtle 'windows_first' bias in the ordering and phrasing of command-line instructions: the use of Azure CLI ('az') and 'kubectl' is presented without explicit mention of platform differences, and browser-based authentication is described in a way that may assume a Windows-centric workflow. No PowerShell-only examples or Windows-exclusive tools are present, and Linux/macOS users can follow all instructions as written.
Recommendations
  • Explicitly state that Azure CLI ('az') and 'kubectl' are cross-platform and provide links or notes for installation on Linux/macOS.
  • Clarify that browser-based authentication works on all major platforms and mention any platform-specific caveats if they exist.
  • If there are differences in authentication flows or CLI usage on Linux/macOS, add brief notes or links to relevant guidance.
  • Consider adding a short section or callout confirming that all steps are applicable to Linux/macOS unless otherwise noted.
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-01-14 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 PowerShell is a Windows-centric tool and is featured equally alongside CLI. The introductory metadata and tab structure present PowerShell as a first-class option, which may suggest a Windows bias. However, all CLI examples use Bash-style syntax and are cross-platform, and there are no exclusive Windows tools or patterns. No Linux-specific examples (e.g., Bash scripts, Linux package installation) are missing, but PowerShell's prominence may create friction for Linux/macOS users unfamiliar with it.
Recommendations
  • Clarify that Azure CLI is fully cross-platform and recommend it as the default for Linux/macOS users.
  • Consider listing Azure CLI examples before PowerShell in each section to emphasize cross-platform usage.
  • Add a note that PowerShell Core is available on Linux/macOS, but most Linux users will prefer Azure CLI.
  • Ensure any references to installation or usage of tools include Linux/macOS instructions (currently present for CLI, but PowerShell install links could mention PowerShell Core).
GitHub Create Pull Request
Aks Configure Azure CNI Pod Subnet - Dynamic IP Allocation and enhanced subnet support ...icles/aks/configure-azure-cni-dynamic-ip-allocation.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides all command-line examples using Azure CLI and Bash syntax, which are cross-platform and suitable for both Windows (via WSL or native bash) and Linux/macOS users. However, there is a subtle bias in the absence of explicit Linux/macOS-specific guidance or examples (e.g., no mention of Linux package managers, shell differences, or environment setup for non-Windows users). Additionally, the documentation references the Azure portal for viewing metrics, which is platform-neutral, but does not address any Linux-specific tooling or troubleshooting patterns. The examples are not Windows/PowerShell-specific, but the lack of explicit Linux/macOS context may create minor friction for non-Windows users.
Recommendations
  • Add a brief note confirming that all Azure CLI and kubectl commands work natively on Linux/macOS and Windows (with WSL or Azure CLI installed).
  • Include any Linux/macOS-specific setup steps if relevant (e.g., installing Azure CLI via apt, Homebrew, etc.).
  • Clarify that the Bash syntax shown is cross-platform and provide links to Azure CLI installation guides for Linux/macOS.
  • If there are any platform-specific caveats (e.g., file paths, environment variables), mention them explicitly.
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-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides configuration instructions for Azure CNI networking in AKS using three approaches: Azure portal, Azure PowerShell, and Azure CLI. The PowerShell section is prominent and includes detailed instructions for installing/upgrading Azure PowerShell on Windows, macOS, and Linux, but PowerShell is a Windows-centric tool and its usage is generally more familiar to Windows users. The PowerShell example is shown before the CLI example, and the CLI example (which is more cross-platform and native for Linux/macOS users) is present but not prioritized. There is a slight bias toward Windows tooling and patterns, though Linux/macOS users can complete all tasks using the CLI.
Recommendations
  • Prioritize Azure CLI examples before PowerShell, as CLI is the default and most widely used cross-platform tool.
  • Clarify that Azure CLI is the recommended approach for Linux/macOS users, and PowerShell is optional.
  • Add explicit notes or callouts for Linux/macOS users, such as mentioning that all CLI commands work natively on these platforms.
  • Consider reducing the emphasis on PowerShell installation/upgrade instructions, or move them to a dedicated PowerShell section.
  • Ensure parity in troubleshooting and advanced configuration examples for CLI and PowerShell.
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-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows Example Present Windows Linux Difference Noted
Summary
The documentation is generally cross-platform and neutral, describing AKS storage concepts applicable to both Linux and Windows node pools. However, there is a minor bias in the persistent volume claim section, where mounting instructions for Linux containers are given first, followed by a separate example for Windows containers. Additionally, the documentation notes that persistent volumes cannot be shared between Windows and Linux pods due to filesystem differences, but this is a technical limitation rather than a documentation bias.
Recommendations
  • Present Linux and Windows mounting examples side-by-side or clarify that the Linux example applies to Linux containers and the Windows example to Windows containers.
  • Explicitly state at the beginning of mounting sections which examples are for Linux and which are for Windows to improve clarity.
  • Ensure that any YAML or CLI examples are provided for both platforms when relevant, or clearly indicate platform specificity.
  • Add a brief note or table summarizing platform differences for storage features, where relevant.
GitHub Create Pull Request
Aks Install the Dapr extension for Azure Kubernetes Service (AKS) and Arc-enabled Kubernetes ...softDocs/azure-aks-docs/blob/main/articles/aks/dapr.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation is generally cross-platform, focusing on Azure CLI and Bicep for managing Dapr on AKS and Arc-enabled Kubernetes clusters. However, there is a minor Windows bias in the 'Listing the CRDs in your cluster' section, where the example uses PowerShell's 'findstr' command with kubectl, which is specific to Windows. No equivalent Linux/macOS example (e.g., using 'grep') is provided, and the PowerShell example appears first and exclusively.
Recommendations
  • Provide Linux/macOS equivalents for command-line examples, especially where platform-specific tools like 'findstr' are used. For example, add 'kubectl get crds | grep dapr.io' for Linux/macOS.
  • Clarify that Azure CLI and kubectl commands are cross-platform, and note any platform-specific differences where relevant.
  • Where possible, avoid using platform-specific shell commands in generic Kubernetes contexts, or present both Windows and Linux/macOS variants side by side.
GitHub Create Pull Request
Aks Delete an Azure Kubernetes Service (AKS) node pool ...re-aks-docs/blob/main/articles/aks/delete-node-pool.md
Low Priority View Details →
Scanned: 2026-01-14 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 deleting AKS node pools, with PowerShell examples given equal prominence to CLI. The PowerShell example is presented as a separate tab, which is helpful for Windows users but may be unnecessary for Linux/macOS users, as PowerShell is less commonly used on those platforms. The CLI examples are cross-platform, but the inclusion of PowerShell as a primary method could suggest a slight Windows bias. However, all critical operations can be performed using the Azure CLI, which works on Linux, macOS, and Windows. No tasks are Windows-only, and Linux/macOS users can complete all steps.
Recommendations
  • Make clear that Azure CLI is cross-platform and generally recommended for Linux/macOS users.
  • Consider listing Azure CLI examples first to emphasize platform neutrality.
  • Optionally, add a note that PowerShell examples are primarily for Windows users, but PowerShell Core is available cross-platform if desired.
  • Ensure that any future examples or troubleshooting steps do not assume use of Windows-only tools.
GitHub Create Pull Request
Aks Deploy to Azure Kubernetes Service with Azure Pipelines ...ure-aks-docs/blob/main/articles/aks/devops-pipeline.md
Low Priority View Details →
Scanned: 2026-01-14 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 PowerShell instructions for resource creation, but PowerShell examples are shown after CLI. However, the PowerShell section is more verbose and detailed, including additional steps (such as registering resource providers and creating a log analytics workspace) that are not present in the CLI section. The documentation does not mention Linux or macOS specifically, nor does it provide shell-specific guidance for those platforms. The Azure CLI examples are cross-platform, but PowerShell is Windows-centric, and its inclusion may imply a slight Windows bias, especially since the PowerShell section is more comprehensive.
Recommendations
  • Ensure parity between Azure CLI and PowerShell instructions by including all necessary steps (e.g., log analytics workspace creation) in both sections.
  • Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and recommend CLI for cross-platform users.
  • Consider providing bash/zsh shell examples for Linux/macOS users, or clarify that Azure CLI is the preferred method for non-Windows platforms.
  • Add a note that PowerShell Core is available on Linux/macOS, but most users on those platforms will use Azure CLI.
GitHub Create Pull Request
Aks Delete an Azure Kubernetes Service (AKS) cluster ...zure-aks-docs/blob/main/articles/aks/delete-cluster.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides examples for deleting an AKS cluster using Azure CLI, Azure PowerShell, and the Azure portal. While the Azure CLI example is cross-platform and shown first, the inclusion of Azure PowerShell (which is primarily used on Windows) as a dedicated example, without mentioning Linux/macOS alternatives for scripting, may create a slight Windows bias. However, the Azure CLI example is fully suitable for Linux/macOS users and is presented before PowerShell, minimizing the impact.
Recommendations
  • Clarify that Azure PowerShell is available cross-platform, but is most commonly used on Windows.
  • Consider adding a note for Linux/macOS users that Azure CLI is the recommended tool for scripting and automation.
  • If relevant, mention that PowerShell Core is available on Linux/macOS, but most users on those platforms use Azure CLI.
  • Ensure that future documentation continues to present Azure CLI examples first for parity.
GitHub Create Pull Request
Aks Deploy an AKS cluster with Confidential Containers (preview) ...s/aks/deploy-confidential-containers-default-policy.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page primarily uses Azure CLI and bash commands for cluster deployment and management, which are cross-platform. However, there are subtle signs of Windows bias: Azure CLI examples are presented as 'azurecli-interactive', which can be run on Windows, Linux, or macOS, but there is no explicit mention of Linux/macOS environments or shell differences. The documentation does not provide any PowerShell-specific examples, but it also does not clarify that all commands work equally well on Linux/macOS. There is a minor 'windows_first' bias in that Azure CLI is often associated with Windows in Azure documentation, and there is no explicit Linux parity guidance. No Windows-only tools or patterns are mentioned, and the feature itself is not Windows-specific.
Recommendations
  • Explicitly state that all Azure CLI and bash commands work on Linux, macOS, and Windows (with WSL or native bash).
  • Add a note or section for Linux/macOS users, clarifying any environment setup differences (e.g., using bash vs. PowerShell, file path formats).
  • Where environment variables are set, mention that syntax may differ in PowerShell and provide equivalent commands if relevant.
  • Ensure that references to Azure Cloud Shell clarify its cross-platform nature.
  • Consider adding troubleshooting tips for Linux/macOS users if any commands behave differently.
GitHub Create Pull Request
Aks Deploy a Java application with Open Liberty/WebSphere Liberty on an Azure Kubernetes Service (AKS) cluster ...lob/main/articles/aks/howto-deploy-java-liberty-app.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for all command-line steps, but PowerShell is presented as the only Windows option, and examples for Bash (Linux/macOS) and PowerShell (Windows) are always given in parallel. However, in some places, PowerShell examples are shown before Bash, and there is no mention of native Windows Command Prompt (cmd.exe) usage. The prerequisites recommend Unix-like OS or Windows Subsystem for Linux for Windows users, which is positive for Linux parity. No Windows-only tools or patterns are used, and all critical steps are possible on Linux/macOS. The bias is minor and mostly in the ordering and emphasis on PowerShell for Windows users.
Recommendations
  • Present Bash examples before PowerShell, or alternate the order to avoid implicit prioritization.
  • Explicitly state that Bash examples apply to Linux/macOS and Windows Subsystem for Linux, and PowerShell examples are for Windows users.
  • Consider providing Windows Command Prompt (cmd.exe) equivalents for users who do not use PowerShell.
  • Add a note clarifying that all steps are fully supported on Linux/macOS and Windows (via WSL or PowerShell).
GitHub Create Pull Request
← Previous Page 11 of 15 Next →