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 276-300 of 365 flagged pages
Aks Use Image Integrity to validate signed images before deploying them to your Azure Kubernetes Service (AKS) clusters (Preview) ...ure-aks-docs/blob/main/articles/aks/image-integrity.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 for 'Use Image Integrity to validate signed images before deploying them to your Azure Kubernetes Service (AKS) clusters (Preview)' shows mild Windows bias. In the prerequisites, both Azure CLI and Azure PowerShell are mentioned, but PowerShell is listed alongside CLI without clarifying platform parity. All command-line examples use Azure CLI and kubectl, which are cross-platform, but there are no explicit Linux/macOS-specific instructions or examples. The installation links for Azure CLI and Azure PowerShell are provided, but PowerShell is not required for any step shown, which may confuse Linux/macOS users. No Linux-specific tools, shell patterns, or troubleshooting are mentioned, and Windows is implicitly assumed in some variable naming conventions and resource group naming. However, all critical steps can be completed on Linux/macOS, and the commands shown are cross-platform.
Recommendations
  • Clarify that Azure CLI and kubectl are fully supported on Linux/macOS and provide installation links for those platforms.
  • Remove Azure PowerShell from prerequisites unless it is actually required for any step.
  • Explicitly state that all shown commands work on Linux/macOS and provide troubleshooting tips for those platforms if needed.
  • Add a note or section confirming parity for Linux/macOS users, especially for Azure CLI and kubectl usage.
  • If any step requires Windows-only tooling, clearly mark it as such and provide Linux/macOS alternatives.
GitHub Create Pull Request
Aks Customer intent: "As a cloud administrator, I want to log in to Azure using the CLI with a workaround, so that I can securely access my subscription and manage resources without issues." ...cs/blob/main/articles/aks/includes/azd/azd-login-ts.md
Low Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows Only Announcement
Summary
The documentation is generally cross-platform, using Azure CLI and curl, which are available on Windows, Linux, and macOS. However, there is a section in the HTML output that specifically announces a Windows-only feature (Web Account Manager broker) and provides Windows-specific instructions. This announcement and the related commands are only relevant for Windows users, with no equivalent or alternative guidance for Linux/macOS users.
Recommendations
  • Clearly separate Windows-only instructions from general guidance, using callouts or sections labeled 'Windows only'.
  • Provide equivalent information or explicitly state if no similar broker feature exists for Linux/macOS.
  • Add a note clarifying that the WAM broker instructions are not applicable to Linux/macOS users.
  • Consider including troubleshooting or alternative authentication guidance for Linux/macOS users if relevant.
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-01-14 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 prerequisite steps and subnet listing, but references to PowerShell are given alongside or immediately after Azure CLI, and links to PowerShell instructions are present. There are no Linux-specific examples, but the main workflow uses kubectl and Azure CLI, which are cross-platform. The mention of PowerShell is not exclusive or prioritized, but it is present without explicit Linux shell alternatives (e.g., Bash scripting for subnet listing).
Recommendations
  • Clarify that Azure CLI commands work on Windows, Linux, and macOS, and recommend CLI for cross-platform usage.
  • Move PowerShell references to a separate section or note, or after CLI examples, to avoid implying Windows-first workflow.
  • Where PowerShell is mentioned (e.g., subnet listing), provide a Bash/Azure CLI equivalent explicitly for Linux/macOS users.
  • Add a brief note in the prerequisites that Azure CLI is recommended for Linux/macOS users, and PowerShell for Windows users.
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-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 (bash/Linux/macOS) and Azure PowerShell (Windows) examples for managing AKS API server authorized IP ranges. However, the PowerShell example is presented immediately after the CLI example, and both are given equal prominence. There is no exclusive use of Windows tools, but PowerShell is included as a first-class option. The rest of the documentation is platform-neutral, focusing on portal-based workflows and YAML manifests that are not OS-specific.
Recommendations
  • Clarify that both Azure CLI and PowerShell examples work on Windows, macOS, and Linux (Azure CLI is cross-platform; PowerShell Core is available on Linux/macOS).
  • Explicitly mention that Azure CLI commands can be run from Cloud Shell (browser-based, cross-platform) or any OS.
  • If possible, indicate which commands are most common for Linux/macOS users (Azure CLI) and which for Windows users (PowerShell), to help users choose the best fit.
  • Consider listing Azure CLI examples first, as it is the default for cross-platform usage.
  • Add a note that PowerShell Core is available for Linux/macOS, if relevant.
GitHub Create Pull Request
Aks Quickstart: Deploy an Azure Kubernetes Service (AKS) cluster using Bicep ...in/articles/aks/learn/quick-kubernetes-deploy-bicep.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 all major steps, but PowerShell is featured as a first-class option throughout, and examples for both are shown side-by-side. There is a slight Windows-first bias in that PowerShell is presented as an equal alternative to Azure CLI, even though PowerShell is primarily a Windows-centric tool (though it is cross-platform now). No Linux-specific tools or shell examples (e.g., Bash scripts) are given, but Azure CLI is cross-platform and is the recommended way for Linux/macOS users. There are no steps that are Windows-only, and Linux users can follow all instructions using Azure CLI. The SSH key generation example includes both Azure CLI and ssh-keygen, which is standard for Linux/macOS users.
Recommendations
  • Clarify that Azure CLI is the recommended approach for Linux/macOS users, and PowerShell is optional for those who prefer it.
  • Consider listing Azure CLI examples before PowerShell examples to reduce perceived Windows-first bias.
  • Explicitly state that all steps can be performed on Linux/macOS using Azure CLI and standard tools.
  • Add a note that PowerShell Core is available on Linux/macOS, but most users on those platforms will prefer Azure CLI.
GitHub Create Pull Request
Aks Manage local accounts with AKS-managed Microsoft Entra integration ...articles/aks/manage-local-accounts-managed-azure-ad.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 Azure CLI examples that are cross-platform, but the output example for merging kubeconfig explicitly references a Windows file path (C:\Users\<username>\.kube\config) without mentioning the Linux/macOS equivalent (~/.kube/config). This is a minor Windows-first bias in output representation.
Recommendations
  • Include both Windows and Linux/macOS file path examples when showing kubeconfig merge output (e.g., 'C:\Users\<username>\.kube\config' and '~/.kube/config').
  • Add a note clarifying that Azure CLI commands work on Windows, Linux, and macOS, and that file paths will differ by OS.
GitHub Create Pull Request
Aks Azure Kubernetes Service (AKS) Managed Gateway API Installation ...aks-docs/blob/main/articles/aks/managed-gateway-api.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 primarily uses Azure CLI commands and kubectl, which are cross-platform, but does not provide explicit Linux/macOS-specific guidance or examples. There is a slight bias in assuming the user environment is set up for Azure CLI and kubectl without addressing platform-specific installation or usage nuances. No PowerShell or Windows-only tools are referenced, but the lack of Linux/macOS-specific notes or troubleshooting can create minor friction for non-Windows users.
Recommendations
  • Add a section clarifying that Azure CLI and kubectl are cross-platform, with links to installation guides for Linux/macOS.
  • Include troubleshooting notes or environment setup tips for Linux/macOS users (e.g., permissions, shell differences, package manager commands).
  • Explicitly mention that all commands are intended to work on Windows, Linux, and macOS, and note any platform-specific caveats if they exist.
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-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 connecting to and deleting the AKS cluster, but consistently lists Azure PowerShell examples after Azure CLI. There are no explicit Windows-only tools or patterns, and Linux-native commands (e.g., ssh-keygen, kubectl) are included. However, PowerShell is given parity with CLI, which may be unnecessary for Linux/macOS users, and the structure could imply a slight Windows-first bias by always listing CLI first and PowerShell second. No critical Linux/macOS gaps are present.
Recommendations
  • Clearly indicate that Azure PowerShell instructions are optional and primarily for Windows users.
  • Consider grouping CLI and PowerShell instructions under OS-specific tabs (Windows, Linux/macOS) to clarify relevance.
  • Add explicit notes that all CLI commands work on Linux/macOS and that PowerShell is not required for those platforms.
  • Where possible, provide Linux/macOS-specific guidance for tasks like uploading files to Cloud Shell.
  • Ensure that examples using Azure CLI are marked as cross-platform and clarify any OS-specific caveats.
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-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 deployment and resource management, but PowerShell examples are given equal prominence and are presented in parallel tabs, which may suggest a slight Windows bias. There is no explicit mention of Linux/macOS-specific tools or workflows, and the instructions for creating SSH keys are cross-platform. However, PowerShell is a Windows-centric tool, and its inclusion alongside CLI may create friction for Linux/macOS users who are less likely to use PowerShell.
Recommendations
  • Clearly indicate that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Add a note clarifying that PowerShell examples are primarily for Windows users, while Azure CLI works on all platforms.
  • Consider listing Azure CLI examples first or as the default, with PowerShell as an alternative tab for Windows users.
  • Explicitly mention that all steps can be completed on Linux/macOS using Azure CLI and standard tools.
  • Where file upload is mentioned (Cloud Shell), clarify how Linux/macOS users can upload files (e.g., drag-and-drop, scp, etc.).
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-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 connecting to the AKS cluster, but the PowerShell workflow is given equal prominence and is described before Linux/macOS alternatives in some places. There is explicit mention of connecting via PowerShell locally, and the use of PowerShell-specific cmdlets (Import-AzAksCredential) is highlighted. However, Linux/macOS users are supported via Azure CLI and Cloud Shell, and all critical workflows (cluster creation, deployment, testing, deletion) are fully accessible from Linux/macOS environments.
Recommendations
  • Present Azure CLI (cross-platform) instructions before PowerShell instructions to reduce perceived Windows-first bias.
  • Clarify that Azure CLI and Cloud Shell are recommended for Linux/macOS users, and that PowerShell is primarily for Windows users.
  • Where local environment setup is discussed, explicitly mention Linux/macOS terminal usage and provide links to installation guides for kubectl and Azure CLI on those platforms.
  • Add a brief note that all steps can be completed from Linux/macOS using Azure CLI and Cloud Shell, and that PowerShell is optional for Windows users.
GitHub Create Pull Request
Aks Connect to Azure Kubernetes Service (AKS) cluster nodes ...s/azure-aks-docs/blob/main/articles/aks/node-access.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 🔧 Windows Tools
Summary
The documentation provides clear guidance for both Linux/macOS and Windows node access in AKS, but Windows-specific instructions (such as PowerShell and host process containers) are presented in dedicated sections with more detail and complexity. Windows access methods rely heavily on PowerShell and Windows-specific container images, while Linux instructions use standard SSH and kubectl debug. Windows examples are given their own sections and sometimes appear before Linux alternatives in those sections. However, Linux access is well-covered and not omitted.
Recommendations
  • Ensure Linux and Windows instructions are presented with equal prominence and clarity.
  • When introducing node access methods, explicitly state which OS each method applies to before diving into details.
  • For Windows sections, consider referencing equivalent Linux troubleshooting workflows (where applicable) to aid cross-platform users.
  • Add a summary table at the top comparing Linux and Windows access methods for quick reference.
  • Avoid presenting Windows-specific tools or patterns (e.g., PowerShell, host process containers) before Linux equivalents unless contextually necessary.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation mentions Windows/PowerShell tooling (Azure PowerShell) before Linux equivalents (Azure CLI) when listing options for creating an AKS cluster. However, all command-line examples throughout the guide use cross-platform tools (Azure CLI, kubectl, helm, faas-cli, curl) and do not show Windows-specific commands or PowerShell scripts. The only minor bias is the ordering of Windows tooling before Linux alternatives in the prerequisites.
Recommendations
  • List Azure CLI before Azure PowerShell when presenting options for creating AKS clusters, as Azure CLI is cross-platform and more commonly used on Linux/macOS.
  • Explicitly state that all commands are cross-platform and can be run on Linux, macOS, or Windows.
  • Consider adding a note or section clarifying any OS-specific differences if relevant (e.g., installation commands for faas-cli or MongoDB tools on different platforms).
GitHub Create Pull Request
Aks Best practices for cluster security ...ticles/aks/operator-best-practices-cluster-security.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 cluster upgrades, but consistently lists PowerShell examples immediately after CLI, which may subtly prioritize Windows tooling. There is no explicit Linux bias, but the ordering and inclusion of PowerShell examples could be seen as slightly Windows-centric. All critical operations (upgrades, security, node management) are covered with cross-platform tools (Azure CLI and kubectl), and Linux-specific best practices (AppArmor, seccomp, unattended upgrades) are included. No tasks are Windows-only except for the clearly separated Windows Server node update section.
Recommendations
  • Consider listing Azure CLI examples first, as it is cross-platform, and clearly label PowerShell examples as Windows-specific.
  • Add explicit notes clarifying that Azure CLI commands work on Linux, macOS, and Windows, while PowerShell examples are for Windows users.
  • Ensure parity in example ordering and visibility, possibly by defaulting to CLI and providing PowerShell as an alternative.
  • Continue to highlight Linux-specific security features and practices, as is done with AppArmor and seccomp.
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-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 resource cleanup, but lists Azure CLI first. PowerShell is referenced as an alternative for installation and cleanup, but no Linux-specific tools or shell patterns are mentioned. All command-line examples (kubectl, curl, git) are cross-platform, and there are no Windows-only tools or commands used. However, the presence of PowerShell instructions and references, and the ordering of CLI before PowerShell, indicate a minor Windows-first and PowerShell-heavy bias.
Recommendations
  • Explicitly state that all kubectl, curl, and git commands work on Linux/macOS as well as Windows.
  • Add notes or links for Linux/macOS users regarding Azure CLI installation and usage.
  • Consider including bash/zsh shell examples for resource cleanup (e.g., az group delete) to reinforce Linux parity.
  • Clarify that Azure PowerShell is optional and not required for Linux/macOS users.
  • When listing prerequisites, mention that Azure CLI is cross-platform and preferred for Linux/macOS.
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-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 all Azure resource management steps, with PowerShell examples given equal prominence. However, there is a mild Windows bias in that PowerShell is featured as a primary alternative to Azure CLI, and the tabs are labeled 'Azure CLI' and 'Azure PowerShell' rather than 'Linux/macOS' and 'Windows'. No Linux-specific tools or shell patterns are mentioned, but all CLI commands are cross-platform. The workflow after resource creation (Helm, kubectl, git, bash commands) is platform-neutral and suitable for Linux/macOS users.
Recommendations
  • Clarify in the prerequisites that Azure CLI is fully supported on Linux/macOS, and PowerShell is primarily for Windows users (though it is cross-platform).
  • Consider labeling the tabs as 'CLI (Linux/macOS/Windows)' and 'PowerShell (Windows)' to help users quickly identify which instructions are most relevant to their OS.
  • Add a brief note for Linux/macOS users confirming that all Azure CLI commands work natively in bash/zsh terminals.
  • If possible, add a short section or note on using Azure CLI in Linux/macOS environments (e.g., installation, shell compatibility).
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-14 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 AKS node pool resizing, with full parity in steps and outputs. However, the inclusion of Azure PowerShell examples introduces a mild Windows bias, as PowerShell is primarily a Windows-centric tool (despite cross-platform support). The documentation presents CLI and PowerShell examples in parallel tabs, but CLI is shown first, which is more Linux/macOS friendly. All core Kubernetes commands (kubectl) are platform-neutral and use bash syntax, ensuring Linux/macOS users can follow the guide without friction.
Recommendations
  • Clarify that Azure PowerShell is available cross-platform, but is most familiar to Windows users.
  • Consider adding a note that Azure CLI is fully supported on Linux/macOS and is the recommended approach for non-Windows environments.
  • Optionally, provide a brief comparison or guidance on choosing Azure CLI vs Azure PowerShell for AKS operations.
  • Maintain CLI as the first example, but ensure PowerShell instructions do not assume a Windows-only audience.
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-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 scaling AKS clusters, but consistently presents PowerShell (a Windows-centric tool) as a primary alternative to Azure CLI. There are no Linux/macOS-specific shell examples (e.g., Bash), and PowerShell instructions are given equal prominence to CLI, which may create friction for Linux/macOS users who do not use PowerShell.
Recommendations
  • Clarify that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
  • Consider adding Bash shell example snippets for common tasks, especially where output parsing or scripting is involved.
  • Reorder examples to present Azure CLI first, and clearly label PowerShell as a Windows-centric alternative.
  • Explicitly state that PowerShell examples are intended for Windows users, and that Azure CLI is recommended for Linux/macOS.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation mentions both Azure CLI and Azure PowerShell as options for creating an AKS cluster, but lists PowerShell before the Azure portal and does not provide Linux/macOS-specific guidance or examples. All command examples use Azure CLI, which is cross-platform, but the initial 'Before you begin' section could imply a slight Windows-first bias by listing PowerShell before the portal. No Linux-specific tools or shell examples (e.g., Bash) are provided, and there is no explicit mention of Linux/macOS compatibility for the commands.
Recommendations
  • List Azure CLI first in the 'Before you begin' section, as it is cross-platform and preferred for Linux/macOS users.
  • Explicitly mention that Azure CLI commands work on Windows, Linux, and macOS.
  • Provide a brief note or link for installing Azure CLI on Linux/macOS.
  • If PowerShell is mentioned, clarify that it is available cross-platform, or provide Bash equivalents 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-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 stopping and starting AKS clusters. However, PowerShell examples are given equal prominence and are listed immediately after CLI examples, which may suggest a slight Windows bias. The introductory section lists Azure CLI, PowerShell, and Portal as options for cluster creation, but does not mention Linux-specific shell environments or clarify that Azure CLI is cross-platform. No Linux/macOS-specific examples or notes are provided.
Recommendations
  • Clarify that Azure CLI is fully cross-platform and can be used on Linux/macOS as well as Windows.
  • Consider listing Azure CLI examples first, as it is the primary cross-platform tool for Azure management.
  • Add a brief note for Linux/macOS users confirming that all CLI commands work natively in Bash/zsh/fish shells.
  • Optionally, provide example commands in a Linux/macOS shell context (e.g., Bash prompt) to reinforce parity.
  • If PowerShell is mentioned, clarify that PowerShell Core is available cross-platform, or note that PowerShell examples are primarily for Windows users.
GitHub Create Pull Request
Aks Supported Kubernetes versions in Azure Kubernetes Service (AKS). ...lob/main/articles/aks/supported-kubernetes-versions.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 key operations (such as installing kubectl and listing available Kubernetes versions), but consistently lists Azure PowerShell examples after Azure CLI. There are no Linux-specific command line examples (e.g., Bash, shell scripts), but the CLI examples are cross-platform. No Windows-only tools or patterns are promoted, and Linux is referenced in OS support tables. The bias is minor, mostly in the ordering and lack of explicit Linux shell examples.
Recommendations
  • Add explicit Bash/shell examples for common operations (e.g., installing kubectl, querying AKS versions) to demonstrate parity for Linux/macOS users.
  • Clarify that Azure CLI commands are cross-platform and work on Linux/macOS/Windows.
  • Consider listing CLI (cross-platform) examples before PowerShell in all sections, or provide a 'Linux/macOS' tab for shell-specific instructions if relevant.
  • Where OS-specific instructions are needed (e.g., installing kubectl), link to upstream Kubernetes docs for Linux/macOS installation.
GitHub Create Pull Request
Aks Kubernetes on Azure tutorial - Deploy an application to Azure Kubernetes Service (AKS) ...articles/aks/tutorial-kubernetes-deploy-application.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 key steps, with PowerShell examples and references included alongside CLI. While Azure CLI is cross-platform, Azure PowerShell is primarily used on Windows, and its inclusion as a main tab may signal a Windows-first approach. However, the actual commands for deploying and managing Kubernetes resources use kubectl, which is cross-platform, and there are no steps that require Windows-only tools or patterns. No Linux/macOS examples are missing, but the presence of PowerShell as a primary option may create mild friction for non-Windows users.
Recommendations
  • Clarify that Azure CLI is recommended for cross-platform use, and consider listing CLI examples first.
  • Add explicit notes that Azure PowerShell is optional and mainly for users already familiar with it.
  • Consider including bash or shell scripting examples for manifest editing or automation, especially for Linux/macOS users.
  • Ensure that any text editor instructions mention cross-platform editors (e.g., VS Code, nano, vim) rather than assuming Notepad or Windows tools.
GitHub Create Pull Request
Aks Kubernetes on Azure tutorial - Use PaaS services with an Azure Kubernetes Service (AKS) cluster ...main/articles/aks/tutorial-kubernetes-paas-services.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 PowerShell (a Windows-centric tool) is given equal prominence as Azure CLI, and examples are presented in parallel tabs. There is minor Windows bias in the sense that PowerShell is highlighted as a primary option, which may not be as relevant for Linux/macOS users. However, all tasks can be completed using Azure CLI, which is fully cross-platform. No steps are Windows-only, and Linux/macOS users are not blocked from completing the tutorial.
Recommendations
  • Make Azure CLI the default or first example in each section, as it is cross-platform and preferred for Linux/macOS users.
  • Clarify in the introduction that Azure CLI is recommended for Linux/macOS users, while PowerShell is primarily for Windows users.
  • Consider adding a note that PowerShell Core is available on Linux/macOS, but most users on those platforms use Azure CLI.
  • Ensure that all CLI commands are tested and work on Linux/macOS shells (e.g., bash/zsh).
GitHub Create Pull Request
Aks Kubernetes on Azure tutorial - Scale applications in Azure Kubernetes Service (AKS) ...cs/blob/main/articles/aks/tutorial-kubernetes-scale.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 scaling AKS nodes, but PowerShell examples are presented alongside CLI examples, and PowerShell is a Windows-centric tool. There is a slight Windows-first bias in listing PowerShell as an alternative to CLI, but all core Kubernetes operations use kubectl, which is cross-platform. No critical Linux/macOS parity issues are present, as Azure CLI and kubectl are fully supported on Linux/macOS.
Recommendations
  • Clarify that Azure PowerShell is primarily for Windows users and that Azure CLI is recommended for cross-platform usage.
  • List Azure CLI examples before PowerShell examples to reinforce CLI as the default, cross-platform tool.
  • Add a note indicating that all shown commands (except PowerShell) work on Linux/macOS, and that PowerShell is optional for Windows users.
  • Consider providing bash shell examples for scripting where relevant.
GitHub Create Pull Request
Aks Use node taints in an Azure Kubernetes Service (AKS) cluster ...ure-aks-docs/blob/main/articles/aks/use-node-taints.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 mentions Windows/PowerShell as an option for creating an AKS cluster before Linux alternatives, but all command-line examples use Azure CLI and kubectl, which are cross-platform. No PowerShell-specific examples or Windows-only tools are used, and Linux/macOS users can follow all instructions without issue.
Recommendations
  • List Linux/Azure CLI options before Windows/PowerShell in the prerequisites section to avoid subtle ordering bias.
  • Clarify that Azure CLI and kubectl are cross-platform and provide links to installation instructions for all major OSes.
  • Consider removing mention of PowerShell in the prerequisites unless PowerShell-specific instructions are provided.
GitHub Create Pull Request
Aks Use system node pools in Azure Kubernetes Service (AKS) ...re-aks-docs/blob/main/articles/aks/use-system-pools.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 provides parallel examples for Azure CLI and Azure PowerShell throughout, but does not offer Linux/macOS-specific guidance or shell examples (e.g., Bash). Azure PowerShell is a Windows-centric tool, and its usage is presented equally alongside Azure CLI, which is cross-platform. However, the documentation does not mention or show Linux-specific patterns (such as Bash scripting), nor does it clarify that all CLI examples work identically on Linux/macOS. The order of presentation sometimes puts PowerShell examples immediately after CLI, but CLI is always shown first. There are no references to Windows-only tools, but the lack of explicit Linux/macOS shell examples or notes may create mild friction for non-Windows users.
Recommendations
  • Add explicit notes clarifying that Azure CLI commands work identically on Linux and macOS.
  • Include Bash shell scripting examples for common operations, especially for tasks involving multiple commands or automation.
  • Where PowerShell is referenced, clarify that it is primarily used on Windows, and suggest Bash or other shells for Linux/macOS users.
  • Consider adding a brief section on cross-platform usage, highlighting any differences or considerations for Linux/macOS users.
GitHub Create Pull Request
← Previous Page 12 of 15 Next →