Aks

529
Total Pages
422
Linux-Friendly Pages
107
Pages with Bias
20.2%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

301 issues found
Showing 126-150 of 301 flagged pages
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-13 23:55
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) examples for managing AKS API server authorized IP ranges. However, the PowerShell example is presented as a primary tab alongside Azure CLI, which may signal a Windows-first approach. There are no explicit Linux/macOS-specific examples or troubleshooting steps, and PowerShell is referenced without noting its limited support on non-Windows platforms. The rest of the documentation is portal-centric and does not show command-line bias, but the troubleshooting section could be improved for Linux parity.
Recommendations
  • Clearly indicate that Azure PowerShell is primarily for Windows and may require additional setup on Linux/macOS.
  • Provide explicit Linux/macOS command-line examples (e.g., using curl or wget to retrieve public IP) alongside Azure CLI.
  • Present Azure CLI examples before PowerShell, as CLI is cross-platform.
  • Add troubleshooting notes for Linux/macOS users, especially regarding network tools and connectivity.
  • Consider removing PowerShell as a primary tab or demoting it below CLI for tasks that are platform-agnostic.
GitHub Create Pull Request
Aks Quickstart: Deploy an Azure Kubernetes Service (AKS) cluster with Flatcar Container Linux for AKS (preview) using an ARM template ...rticles/aks/learn/quick-flatcar-deploy-arm-template.md
Low Priority View Details →
Scanned: 2026-01-13 23:55
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for key operations (connecting to the cluster, deleting resources), but PowerShell examples are given equal prominence and sometimes appear before or alongside CLI examples. There is a notable presence of Windows-centric tooling (PowerShell cmdlets) and references to Azure Cloud Shell, which is cross-platform but often associated with Windows users. Linux-native commands (e.g., ssh-keygen, bash) are present but not consistently prioritized. There are no explicit Linux/macOS-only examples or guidance, and the documentation does not mention platform-specific considerations for Linux or macOS users.
Recommendations
  • Prioritize Azure CLI and bash examples, as these are more universally applicable across Linux, macOS, and Windows.
  • Clearly indicate that Azure CLI commands work on all platforms and are recommended for cross-platform parity.
  • Move PowerShell examples to a secondary position or into expandable sections, making CLI/bash the default.
  • Add explicit notes or sections for Linux/macOS users, including troubleshooting tips or platform-specific nuances.
  • Ensure all steps (especially SSH key generation, file uploads, and resource management) include Linux/macOS workflows and clarify any differences.
GitHub Create Pull Request
Aks Deploy an AKS cluster using the Bicep Kubernetes extension ...https://github.com/MicrosoftDocs/azure-aks-docs/blob/main/articles/aks/learn/quick-kubernetes-deploy-bicep-kubernetes-extension.md
Low Priority View Details →
Scanned: 2026-01-13 23:55
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 deployment and deletion tasks, but PowerShell (a Windows-centric tool) is given equal prominence and is presented immediately after CLI examples. There is no explicit Linux shell example (e.g., bash), and PowerShell is not marked as Windows-only, potentially implying parity or preference. Visual Studio Code is recommended as the editor, which is cross-platform, but no mention is made of alternative Linux-native editors. The SSH key generation instructions do include both Azure CLI and ssh-keygen (Linux/Unix tool), which is positive for parity.
Recommendations
  • Clearly label PowerShell examples as Windows-specific, and Azure CLI examples as cross-platform.
  • Present Azure CLI (cross-platform) examples first in every section, with PowerShell as an alternative.
  • Add explicit bash shell examples for Linux/macOS users where relevant, especially for file operations and environment setup.
  • Mention Linux-native editors (e.g., Vim, Nano) as alternatives to Visual Studio Code for editing Bicep files.
  • Add a note clarifying that Azure CLI works on Linux/macOS/Windows, while PowerShell is primarily for Windows users.
GitHub Create Pull Request
Aks Quickstart: Deploy an Azure Kubernetes Service (AKS) cluster using the Azure portal ...n/articles/aks/learn/quick-kubernetes-deploy-portal.md
Low Priority View Details →
Scanned: 2026-01-13 23:55
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 connecting to the AKS cluster, but PowerShell is mentioned explicitly as a local option before Azure CLI, and PowerShell-specific commands are given equal prominence to CLI commands. There are no Linux/macOS-specific instructions or examples for local environments, and the upload/download file instructions do not mention platform-specific tooling (e.g., scp, curl, etc.). However, the main workflow is platform-neutral, and the use of Azure Cloud Shell (which is Linux-based) is encouraged.
Recommendations
  • Explicitly mention Linux/macOS as supported local environments and provide instructions for connecting to Azure from those platforms (e.g., using Azure CLI on Linux/macOS).
  • List Azure CLI instructions before PowerShell, as CLI is cross-platform and more commonly used on Linux/macOS.
  • Add notes or examples for uploading files from Linux/macOS (e.g., using scp, curl, or Azure CLI storage commands), not just the portal upload button.
  • Clarify that PowerShell is primarily for Windows users, and recommend Azure CLI for Linux/macOS users.
  • Consider adding a table or section comparing platform-specific steps for local environments.
GitHub Create Pull Request
Aks Monitor Azure Kubernetes Service (AKS) ...s/azure-aks-docs/blob/main/articles/aks/monitor-aks.md
Low Priority View Details →
Scanned: 2026-01-13 23:55
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation is largely platform-neutral and focuses on Azure-native tools and Kubernetes concepts. However, there are subtle signs of Windows bias: Windows is frequently mentioned alongside Linux ("Linux and Windows node pools"), and Azure PowerShell is referenced as a method for configuration, but Linux-specific CLI tools (like Bash scripts or shell commands) are not given equal prominence. Examples and instructions often mention Azure CLI and PowerShell, but do not provide explicit Linux shell or macOS Terminal examples. In the node metrics section, Windows support is detailed, sometimes before Linux, and Windows limitations are called out, but Linux-specific troubleshooting or examples are not provided. There are no explicit Linux-only examples, and the ordering of OS mentions sometimes puts Windows first or equally, even when the feature is Linux-centric.
Recommendations
  • Add explicit Linux/macOS shell command examples (e.g., Bash) alongside Azure CLI and PowerShell instructions.
  • When referencing OS support, list Linux first for features that are primarily Linux-centric (such as Cilium).
  • Provide troubleshooting steps or examples for Linux environments, not just generic or Windows-specific notes.
  • Clarify when instructions or tools (like PowerShell) are Windows-only, and offer Linux/macOS alternatives.
  • Include screenshots or walkthroughs from Linux/macOS environments in addition to Azure portal and Windows examples.
GitHub Create Pull Request
Aks Node resource reservations in Azure Kubernetes Service (AKS) ...s/blob/main/articles/aks/node-resource-reservations.md
Low Priority View Details →
Scanned: 2026-01-13 23:55
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation is largely neutral, but there is a notable Windows-specific note regarding AKS reserving an extra 2 GB for system processes on Windows nodes. This is the only OS-specific mention, and it appears before any equivalent Linux details (which are not provided). No Linux-specific examples, tools, or patterns are discussed, and the documentation does not clarify whether similar reservations or considerations apply to Linux nodes.
Recommendations
  • Add a corresponding note for Linux nodes, specifying if and how much memory is reserved for system processes on Linux.
  • Clarify any differences in resource reservation between Windows and Linux nodes, ideally in a comparative table.
  • Ensure that OS-specific details are presented in parallel, not with Windows-first ordering.
  • Provide links or references to further documentation for both Windows and Linux node resource management.
GitHub Create Pull Request
Aks Use OpenFaaS on Azure Kubernetes Service (AKS) ...Docs/azure-aks-docs/blob/main/articles/aks/openfaas.md
Low Priority View Details →
Scanned: 2026-01-13 23:55
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page displays mild Windows bias by listing Windows-centric tools and patterns first, such as Azure PowerShell and Azure portal, before Linux alternatives. Azure CLI is mentioned, but PowerShell is given equal prominence. There are no explicit Linux/macOS examples, and installation instructions for MongoDB tools use Homebrew (macOS), but do not mention apt/yum for Linux. The use of Azure Cloud Shell is platform-neutral, but the lack of explicit Linux command examples and the ordering of Windows tools before Linux ones may create minor friction for Linux/macOS users.
Recommendations
  • List Azure CLI (cross-platform) before Azure PowerShell and Azure portal when describing cluster creation.
  • Provide explicit Linux installation instructions for MongoDB tools (e.g., apt, yum) alongside Homebrew.
  • Add notes or examples for Linux/macOS users where platform-specific commands or tools are referenced.
  • Clarify that Azure Cloud Shell works on all platforms and is recommended for parity.
  • Ensure that any references to PowerShell are balanced with Bash or shell equivalents.
GitHub Create Pull Request
Aks Optimize Azure Kubernetes Service (AKS) usage and costs ...-aks-docs/blob/main/articles/aks/optimize-aks-costs.md
Low Priority View Details →
Scanned: 2026-01-13 23:55
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
🔧 Windows Tools
Summary
The documentation page is generally cross-platform and does not provide command-line examples or tooling instructions that are specific to Windows or PowerShell. However, the Azure Hybrid Benefits section mentions bringing on-premises Windows Server and SQL Server licenses to Azure, which is a Windows-centric offering. No Linux/macOS-specific cost optimization features or licensing benefits are mentioned, and the discounts section is skewed toward Windows licensing scenarios.
Recommendations
  • Add information about Linux-specific cost optimization strategies, such as using Azure Hybrid Benefits for Linux (if available) or other licensing programs relevant to Linux workloads.
  • Clarify whether Reserved Instances and Savings Plans apply equally to Linux-based AKS clusters and provide examples or notes for Linux users.
  • If there are Linux/macOS-specific tools or patterns for optimizing AKS costs (e.g., open-source cost monitoring solutions), mention them alongside Windows-centric options.
  • Ensure that any licensing or discount features exclusive to Windows are clearly marked as such, and provide alternative recommendations for Linux users where possible.
GitHub Create Pull Request
Aks Outbound network and FQDN rules for Azure Kubernetes Service (AKS) clusters ...lob/main/articles/aks/outbound-rules-control-egress.md
Low Priority View Details →
Scanned: 2026-01-13 23:55
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows Examples Separated Windows Node Pool Section
Summary
The documentation provides a comprehensive list of outbound network and FQDN rules for AKS clusters, covering both Linux and Windows node pools. While the majority of the content is platform-neutral or Linux-focused (reflecting AKS's default Linux node pool), there is a dedicated section for Windows Server-based node pools, listing Windows-specific endpoints and update sources. Additionally, some examples (such as mentioning PowerShell in package repositories) reference Windows tools, but these are not exclusive and are presented alongside Linux equivalents (e.g., apt-get). There is no evidence of Windows-first ordering, Powershell-heavy examples, or critical missing Linux instructions.
Recommendations
  • Ensure that Linux and Windows node pool requirements are presented with equal prominence and clarity, possibly grouping them side-by-side for easier comparison.
  • Where package repositories are mentioned (e.g., packages.microsoft.com), clarify which endpoints are used by Linux (apt-get) and which by Windows (PowerShell), and provide explicit examples for both.
  • If referencing tools (e.g., PowerShell, apt-get), provide brief context or links to platform-specific usage guides.
  • Consider adding a summary table comparing Linux and Windows node pool outbound requirements for quick reference.
GitHub Create Pull Request
Aks AKS Regulated Cluster for PCI DSS 4.0.1 - Risk Assessment and Code Assets ...-aks-docs/blob/main/articles/aks/pci-ra-code-assets.md
Low Priority View Details →
Scanned: 2026-01-13 23:55
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page shows mild Windows bias, primarily through references to Windows-specific tools (Visio file download), PowerShell cmdlets for conditional access policy management, and the use of Azure Bastion/jump box patterns that are more common in Windows-centric environments. Examples and guidance for Linux/macOS alternatives (e.g., OpenSSH, bash, Linux-native automation) are not provided, and Windows tools are mentioned first or exclusively in some sections.
Recommendations
  • Provide Linux/macOS equivalents for PowerShell cmdlets, such as Azure CLI or REST API examples for conditional access policy management.
  • Offer architecture diagrams in open formats (e.g., SVG, PNG, PDF) alongside Visio files to support users on non-Windows platforms.
  • Clarify that Azure Bastion/jump box access supports SSH and Linux-based management, and provide examples using Linux-native tools.
  • Where management operations are described, include both Windows (PowerShell) and Linux/macOS (bash, Azure CLI) workflows.
  • Explicitly mention cross-platform support for all tools and workflows, and avoid assuming Windows as the default environment.
GitHub Create Pull Request
Aks Deploy an application with the Dapr cluster extension for Azure Kubernetes Service (AKS) or Arc-enabled Kubernetes ...ure-aks-docs/blob/main/articles/aks/quickstart-dapr.md
Low Priority View Details →
Scanned: 2026-01-13 23:55
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation lists both Azure CLI and Azure PowerShell as prerequisites and provides resource cleanup instructions for both. However, Azure PowerShell (a Windows-centric tool) is mentioned alongside Azure CLI throughout, and PowerShell examples are given equal prominence to CLI examples. The cleanup section presents Azure CLI first, but PowerShell is included as a tabbed alternative. No Linux/macOS-specific tools or patterns are mentioned, but all command-line examples (git, kubectl, curl) are cross-platform. There is no evidence of missing Linux examples or exclusive use of Windows tools.
Recommendations
  • Clarify that Azure CLI is fully cross-platform and recommend it as the default for Linux/macOS users.
  • Explicitly state that all command-line steps (git, kubectl, curl) work on Linux/macOS.
  • Consider listing Azure CLI before Azure PowerShell in all sections, or add a note that PowerShell is primarily for Windows users.
  • Add a brief section or note confirming Linux/macOS compatibility for all steps.
  • If possible, provide links to Linux/macOS installation instructions for Azure CLI and kubectl.
GitHub Create Pull Request
Aks Resize Node Pools in Azure Kubernetes Service (AKS) ...re-aks-docs/blob/main/articles/aks/resize-node-pool.md
Low Priority View Details →
Scanned: 2026-01-13 23:55
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 AKS node pool resizing tasks. Azure PowerShell is a Windows-centric tool, and its inclusion as a primary tab alongside Azure CLI introduces a Windows bias. The PowerShell examples are given equal prominence to CLI, despite CLI being cross-platform and PowerShell being less commonly used on Linux/macOS. However, all critical commands (including node pool management and Kubernetes operations) are shown with Azure CLI and kubectl, which are fully supported on Linux/macOS. No essential steps are Windows-only, and Linux/macOS users can complete all tasks using the CLI instructions.
Recommendations
  • Make Azure CLI the default or first tab in all code example sections, as it is cross-platform.
  • Clearly indicate that Azure PowerShell is primarily for Windows users, and that Azure CLI is recommended for Linux/macOS.
  • Consider adding a note about Azure CLI and kubectl being available and supported on all platforms.
  • Optionally, provide Bash script examples for automation, or highlight shell compatibility where relevant.
GitHub Create Pull Request
Aks Security bulletins for Azure Kubernetes Service (AKS) .../blob/main/articles/aks/security-bulletins/overview.md
Low Priority View Details →
Scanned: 2026-01-13 23:55
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation provides security bulletins for both Linux and Windows AKS node images, but several sections (AKS-2025-004, AKS-2025-003, AKS-2025-002) focus exclusively on Windows-specific vulnerabilities and remediation steps. These Windows sections list only Windows node image versions and upgrade instructions, with no equivalent Linux details or parity in structure. However, Linux vulnerabilities (e.g., runc, Calico) are also covered in separate bulletins, and the overall document is not overwhelmingly Windows-centric. There are no PowerShell-heavy examples, and most instructions are platform-neutral. Windows issues are presented in a block, but not always before Linux ones.
Recommendations
  • For each Windows-specific vulnerability, clarify if Linux users are unaffected, and explicitly state the Linux equivalent status (e.g., 'Linux node images are not impacted by this CVE').
  • When listing upgrade instructions for Windows node images, provide a similar format for Linux node images if relevant, or state that no action is required for Linux.
  • Ensure parity in the structure and detail of Linux and Windows sections, so Linux users can easily find relevant information.
  • Add a summary table at the top showing which bulletins affect Windows, Linux, or both, for quick reference.
GitHub Create Pull Request
Aks Secure container access to resources ...docs/blob/main/articles/aks/secure-container-access.md
Low Priority View Details →
Scanned: 2026-01-13 23:55
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page is focused on Linux security features for AKS, but there is mild evidence of Windows bias in the 'Before you begin' section, where Windows tools (Azure PowerShell) and the Azure portal are mentioned before Linux-native tools (Azure CLI) for cluster creation. Additionally, some references to Windows node pools are present in limitations, but no Windows security feature equivalents or examples are provided. All technical examples and walkthroughs are Linux-centric, with no PowerShell or Windows command-line examples, and Linux is explicitly required for most features. However, the page does not provide Linux examples first in all cases, and Windows tools are mentioned alongside Linux tools.
Recommendations
  • List Azure CLI (Linux-native) as the primary method for cluster creation before Azure PowerShell and Azure portal.
  • Explicitly state that all examples are Linux-only and provide guidance for Windows users where possible (e.g., how to connect to Linux nodes from Windows).
  • If relevant, mention any Windows security features or alternatives for Windows node pools, or clarify that such features are not available.
  • Remove or de-emphasize PowerShell and Azure portal links in 'Before you begin' if the features are Linux-only.
  • Add a clear note at the top that the page is Linux-focused and Windows parity is not available for these features.
GitHub Create Pull Request
Aks Manually scale nodes in an Azure Kubernetes Service (AKS) cluster ...azure-aks-docs/blob/main/articles/aks/scale-cluster.md
Low Priority View Details →
Scanned: 2026-01-13 23:55
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 instructions for scaling AKS clusters. While Azure CLI is cross-platform, Azure PowerShell is primarily used on Windows, and its inclusion as a first-class example may signal a Windows bias. The examples and outputs are presented in parallel tabs, but PowerShell is given equal prominence despite being less common on Linux/macOS. No critical Linux/macOS functionality is missing, as all essential operations are covered by Azure CLI, which works on all platforms.
Recommendations
  • Clarify that Azure CLI is cross-platform and recommended for Linux/macOS users.
  • Consider listing Azure CLI examples before PowerShell, or explicitly state platform compatibility for each method.
  • Add a brief note for Linux/macOS users indicating that PowerShell examples are optional and that CLI is fully supported.
  • Ensure that any future documentation includes bash or shell script examples if relevant.
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-01-13 23:55
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 stopping and starting AKS clusters. However, Azure PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and is referenced as a primary method for cluster creation and management. The CLI examples are cross-platform, but PowerShell is not natively available on Linux/macOS and requires additional installation steps. The order of tools in the 'Before you begin' section lists Azure CLI first, but PowerShell is mentioned immediately after, reinforcing parity rather than prioritizing Linux-native workflows.
Recommendations
  • Clearly indicate that Azure CLI is the recommended and most cross-platform method for Linux/macOS users.
  • Add a note clarifying that Azure PowerShell is primarily for Windows users, and may require extra setup on Linux/macOS.
  • Consider moving PowerShell instructions to a separate section or appendix, or marking them as 'Windows only' where appropriate.
  • Provide troubleshooting or installation links for Azure CLI and PowerShell on Linux/macOS if PowerShell is to be included.
  • Ensure that all examples and output formats are shown for both CLI and PowerShell, but default to CLI for cross-platform parity.
GitHub Create Pull Request
Aks Start and stop a node pool on Azure Kubernetes Service (AKS) ...ks-docs/blob/main/articles/aks/start-stop-nodepools.md
Low Priority View Details →
Scanned: 2026-01-13 23:55
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation mentions Azure PowerShell and the Azure portal as options for creating an AKS cluster before mentioning the Azure CLI. While the main examples use the Azure CLI (which is cross-platform), the initial 'Before you begin' section lists PowerShell (Windows-centric) before CLI, and links to a PowerShell-specific quickstart. There are no Linux/macOS-specific instructions or examples, and no mention of shell differences or installation notes for non-Windows platforms.
Recommendations
  • List Azure CLI (cross-platform) before PowerShell in 'Before you begin' to emphasize platform neutrality.
  • Add notes or links about installing and using Azure CLI on Linux/macOS.
  • If mentioning PowerShell, also mention Bash or other common Linux shells for parity.
  • Clarify that all shown commands work identically on Linux/macOS, or note any platform-specific caveats.
  • Provide links to Linux/macOS quickstart guides if available.
GitHub Create Pull Request
Aks Handle AKS node upgrades with GitHub Actions ...-docs/blob/main/articles/aks/upgrade-github-actions.md
Low Priority View Details →
Scanned: 2026-01-13 23:55
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Mention
Summary
The documentation mentions Windows and PowerShell as options for creating an AKS cluster before Linux/CLI alternatives, and references Windows-based VMs alongside Linux-based VMs. However, all actionable examples and workflow steps use Azure CLI and Ubuntu runners, which are platform-neutral and Linux-friendly. No PowerShell-specific commands or Windows-only tools are used in the main workflow.
Recommendations
  • List Linux/CLI options before Windows/PowerShell when describing prerequisites or setup steps.
  • Provide parity in quickstart links: ensure Linux/CLI documentation is referenced as prominently as Windows/PowerShell.
  • Clarify that all workflow steps are cross-platform and do not require Windows or PowerShell.
  • Consider removing or balancing references to Windows/PowerShell in introductory sections unless specifically relevant.
GitHub Create Pull Request
Aks Upgrade the Azure Kubernetes Service (AKS) cluster control plane ...cs/blob/main/articles/aks/upgrade-aks-control-plane.md
Low Priority View Details →
Scanned: 2026-01-13 23:55
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 upgrade operations, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and is always listed immediately after CLI examples. There are no Linux-specific shell examples (e.g., Bash), nor any mention of Linux/macOS platform nuances. The CLI examples are cross-platform, but the presence and prominence of PowerShell may suggest a Windows bias, especially for users unfamiliar with PowerShell on non-Windows systems.
Recommendations
  • Clarify that Azure CLI commands work natively on Linux/macOS and Windows, while PowerShell is primarily a Windows tool (though cross-platform PowerShell exists).
  • Consider listing Azure CLI examples first, as it is the most cross-platform tool.
  • Add explicit Bash shell examples or notes for Linux/macOS users where relevant (e.g., environment variable usage, file paths).
  • Add a note or section addressing platform compatibility for both CLI and PowerShell.
  • If PowerShell is not required for any step, consider de-emphasizing it or moving it to an appendix.
GitHub Create Pull Request
Aks Use Microsoft Entra pod-managed identities in AKS (Preview) ...cs/blob/main/articles/aks/use-azure-ad-pod-identity.md
Low Priority View Details →
Scanned: 2026-01-13 23:55
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation relies exclusively on Azure CLI commands and tools, which are cross-platform but have a strong association with Windows environments. There are no explicit Linux/macOS-specific instructions, nor are there examples using native Linux tools or shell patterns (e.g., Bash scripting, package managers). The documentation does not mention PowerShell, but all command-line examples use Azure CLI, which is available on Linux but often presented as a Windows-first tool. There are no references to Linux-specific installation methods for Azure CLI, nor troubleshooting steps for non-Windows platforms. The documentation does note that pod-managed identities are only supported on Linux node pools, but this is a feature limitation, not a documentation parity issue.
Recommendations
  • Add explicit instructions for installing Azure CLI on Linux and macOS, including package manager commands (apt, yum, brew).
  • Include troubleshooting tips for Azure CLI on Linux/macOS (e.g., PATH issues, permission errors).
  • Provide example shell scripts using Bash syntax for automation.
  • Clarify that all CLI commands work on Linux/macOS and provide links to platform-specific installation guides.
  • If relevant, mention differences in environment variable usage or file paths between Windows and Linux/macOS.
GitHub Create Pull Request
Aks Use GPUs on Azure Kubernetes Service (AKS) ...zure-aks-docs/blob/main/articles/aks/use-nvidia-gpu.md
Low Priority View Details →
Scanned: 2026-01-13 23:55
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation page mentions Windows tooling (Azure PowerShell and Azure portal) as options for creating an AKS cluster before Linux alternatives, but all technical examples and instructions are Linux-focused (Azure CLI, kubectl, YAML manifests). No PowerShell or Windows-specific commands are provided, and the workflow is entirely Linux-oriented. The only evidence of Windows bias is the order in which cluster creation options are listed.
Recommendations
  • List Linux-first options (Azure CLI) before Windows options (PowerShell, portal) when introducing cluster creation methods.
  • Explicitly state that all subsequent examples are Linux-based and that Windows users should use WSL or Azure Cloud Shell.
  • Consider providing a brief note or link for Windows users on how to run Azure CLI and kubectl (e.g., via WSL, Cloud Shell, or native Windows installs).
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-01-13 23:55
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows Reference Windows First
Summary
The documentation references Windows and PowerShell environments in notes about shell differences, and links to the Kubernetes JSONPath documentation specifically for Windows/PowerShell users. However, all command examples use Azure CLI and Bash syntax, which are cross-platform and Linux-friendly. There are no PowerShell-specific examples, nor are Windows-only tools or patterns used. The mention of Windows environments appears before any Linux-specific shell discussion, but Linux is the default context throughout.
Recommendations
  • Clarify that Azure CLI and Bash examples work on Linux, macOS, and Windows (with WSL or Bash installed).
  • Provide explicit PowerShell examples if Windows users are a significant audience, or link to a page with equivalent PowerShell syntax.
  • If mentioning shell differences, also note common Linux/macOS shell issues (e.g., quoting, environment variables) for parity.
  • Consider rephrasing notes to mention both Linux and Windows environments equally, or provide links for both.
GitHub Create Pull Request
Aks Use AMD GPUs on Azure Kubernetes Service (AKS) .../azure-aks-docs/blob/main/articles/aks/use-amd-gpus.md
Low Priority View Details →
Scanned: 2026-01-13 23:55
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation mentions Windows as an unsupported OS for AMD GPU node pools, and in the 'Before you begin' section, it lists Azure CLI, Azure PowerShell, and Azure Portal as options for cluster creation, with PowerShell (Windows-centric) mentioned before the Portal. However, all technical examples and commands throughout the guide use Azure CLI and kubectl, which are cross-platform and Linux-friendly. No PowerShell-specific commands or Windows-only tools are provided, and Linux is clearly the supported OS for AMD GPU node pools.
Recommendations
  • List Linux-focused options (Azure CLI) before Windows-centric ones (PowerShell) in the 'Before you begin' section to reinforce Linux parity.
  • Explicitly state that all example commands are cross-platform and provide links to Linux/macOS installation guides for Azure CLI and kubectl.
  • Consider removing or de-emphasizing PowerShell as a recommended option for cluster creation in this context, since AMD GPU node pools do not support Windows.
  • Add a note clarifying that all steps are intended for Linux-based node pools and that Windows is not supported for AMD GPU workloads.
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-01-13 23:55
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation provides both Linux and Windows examples for AKS network policy setup, but Windows-specific instructions (such as preview feature registration and administrator credential setup) are more detailed and appear before Linux equivalents in some sections. Windows tools and patterns (e.g., HNS ACLPolicies, Windows admin credential creation) are mentioned explicitly, while Linux-specific details are less emphasized. The overall flow sometimes gives Windows steps more prominence, and there is no explicit parity in troubleshooting or limitations sections for Linux versus Windows.
Recommendations
  • Ensure Linux and Windows instructions are presented with equal prominence and in parallel structure, especially in step-by-step guides.
  • Add explicit Linux troubleshooting steps and limitations where Windows-specific issues are discussed.
  • Where Windows tools (e.g., HNS ACLPolicies) are mentioned, provide equivalent Linux details (e.g., IPTables) with equal depth.
  • Avoid presenting Windows steps before Linux steps unless there is a technical reason; consider grouping by OS or using tabs.
  • Clarify which commands and procedures are OS-agnostic and which are OS-specific, to help users quickly find relevant information.
GitHub Create Pull Request
Aks Use Azure Policy to secure your Azure Kubernetes Service (AKS) clusters ...re-aks-docs/blob/main/articles/aks/use-azure-policy.md
Low Priority View Details →
Scanned: 2026-01-13 23:55
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias in the prerequisites section, where Windows tools (Azure PowerShell) are mentioned before Linux equivalents (Azure CLI). The creation of AKS clusters references Azure CLI, Azure PowerShell, and Azure portal, with PowerShell (Windows-centric) listed before the portal. However, all operational examples (kubectl commands, YAML manifests) are platform-agnostic and work on Linux, macOS, and Windows equally. No critical steps are Windows-only, and Linux users can complete all tasks.
Recommendations
  • List Azure CLI before Azure PowerShell in prerequisites, as CLI is cross-platform and more commonly used on Linux/macOS.
  • Explicitly state that all kubectl commands and YAML examples work on Linux, macOS, and Windows.
  • Where PowerShell is mentioned, provide parity by referencing Bash or shell scripts for Linux/macOS users.
  • Consider adding a note that Azure portal and Azure CLI are fully supported on all platforms.
GitHub Create Pull Request
← Previous Page 6 of 13 Next →