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 201-225 of 301 flagged pages
Aks
Manage local accounts with AKS-managed Microsoft Entra integration
...articles/aks/manage-local-accounts-managed-azure-ad.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page primarily uses Azure CLI commands, which are cross-platform, but the only explicit file path example given is Windows-style (C:\Users\<username>\.kube\config). No Linux/macOS file path equivalents are shown, and the output examples use Windows conventions. There are no PowerShell-specific commands, but the documentation implicitly assumes a Windows environment in its output and context.
Recommendations
- Include Linux/macOS file path examples (e.g., ~/.kube/config) alongside Windows paths.
- Add notes clarifying that Azure CLI commands work on Linux/macOS and provide example outputs for those platforms.
- Avoid using only Windows-style paths in output; show both formats or use platform-neutral notation.
- Explicitly mention cross-platform compatibility in the prerequisites or introductory sections.
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 →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page is largely platform-neutral, but there is a notable Windows-specific note: AKS reserves an extra 2 GB for system processes in Windows nodes, which is not part of the calculated memory. This is the only explicit mention of Windows, and there are no equivalent details or examples for Linux nodes. The Windows-specific information is presented before any Linux-specific details (which are absent), indicating a minor 'windows_first' bias. No PowerShell examples or Windows-only instructions are present, and the core resource reservation concepts apply to both platforms.
Recommendations
- Add a corresponding note for Linux nodes, specifying if and how much memory is reserved for system processes.
- Clarify whether the resource reservation formulas differ for Linux nodes, or explicitly state that the formulas apply equally to both Windows and Linux.
- If there are platform-specific behaviors, provide examples or tables for both Windows and Linux nodes.
- Consider grouping platform-specific notes together or presenting Linux information first if Linux is the more common AKS node OS.
Aks
Azure Kubernetes Service (AKS) Managed Gateway API Installation
...aks-docs/blob/main/articles/aks/managed-gateway-api.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation page relies exclusively on Azure CLI (az) commands for installation, management, and uninstallation steps. Azure CLI is available on Linux and macOS, but its usage is more closely associated with Windows environments, and no Linux/macOS-specific tools or alternative workflows (such as bash scripts, kubectl-only approaches, or cloud-native YAML manifests) are provided. All examples use Azure CLI first, with no mention of Linux-specific package managers, shell environments, or platform differences. However, the page does include kubectl commands, which are cross-platform.
Recommendations
- Explicitly state that Azure CLI is cross-platform and provide installation instructions for Linux/macOS.
- Include alternative workflows using kubectl and YAML manifests for users who prefer not to use Azure CLI.
- Mention platform-specific considerations, such as environment variable syntax differences between Windows (PowerShell/CMD) and Linux/macOS (bash/zsh).
- Provide example commands for Linux/macOS shells (bash/zsh) alongside Azure CLI commands, especially for environment setup.
- Clarify that all commands are intended to work on Linux, macOS, and Windows, and note any exceptions.
Aks
Use NVIDIA GPU Operator on Azure Kubernetes Service (AKS)
...aks-docs/blob/main/articles/aks/nvidia-gpu-operator.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation page demonstrates a mild Windows bias by listing Windows-centric tools (Azure PowerShell) before Linux alternatives, referencing Windows Server in limitations, and including PowerShell as a primary method for cluster creation. However, the main workflow uses Azure CLI, which is cross-platform, and does not provide Windows-only examples or omit Linux instructions.
Recommendations
- List Linux and macOS options (e.g., Bash, Azure CLI) before or alongside Windows/PowerShell in prerequisites and cluster creation steps.
- Explicitly mention Linux/macOS compatibility for all commands and tools.
- Provide example commands for both PowerShell and Bash where relevant.
- Clarify that Azure CLI works on Windows, Linux, and macOS, and link to platform-specific installation guides.
Aks
Optimize Azure Kubernetes Service (AKS) usage and costs
...-aks-docs/blob/main/articles/aks/optimize-aks-costs.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Summary
The documentation page is generally cross-platform and does not show strong Windows bias in its examples or guidance. However, the 'Azure Hybrid Benefits' section exclusively references bringing Windows Server and SQL Server licenses to Azure, which is a Windows-specific cost optimization option. No Linux equivalent (such as Azure Hybrid Benefit for Linux or similar programs) is mentioned.
Recommendations
- Clarify that Azure Hybrid Benefits are specific to Windows workloads, and note if there are any equivalent programs or cost-saving options for Linux users.
- Consider including information about cost optimization strategies for Linux-based AKS clusters, such as using open-source software, leveraging Linux-specific VM discounts, or other relevant Azure programs.
- Ensure that any platform-specific features are clearly labeled as such, and provide parity guidance for Linux/macOS users where possible.
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 →
Detected Bias Types
Windows Tools
Windows Examples
Windows Section
Summary
The documentation provides a comprehensive list of required outbound network rules and FQDNs 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 pools), there is a dedicated section for 'Windows Server based node pools required FQDN / application rules' and several mentions of Windows-specific endpoints (e.g., Windows Update, PowerShell, onegetcdn). However, there is no evidence of Windows-first ordering, Powershell-heavy examples, or missing Linux examples. The Linux requirements are well covered, and Linux endpoints (such as Ubuntu update mirrors) are listed before Windows-specific ones. No CLI examples (Windows or Linux) are present.
Recommendations
- Ensure parity in detail and clarity between Linux and Windows node pool sections.
- Explicitly mention if any rules or endpoints differ for macOS-based AKS agents (if supported in future).
- If providing example commands in future updates, include both Linux (bash) and Windows (PowerShell) variants.
- Consider grouping platform-specific requirements under clear subheadings for easier navigation.
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 →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation page exhibits mild Windows bias, primarily in the Identity and Access Management section, where PowerShell cmdlets are referenced for configuring conditional access policies. The only downloadable architecture diagram is a Visio file, a format most commonly used on Windows. There is no explicit mention of Linux/macOS equivalents or CLI alternatives for these tasks, and Windows-centric tools (PowerShell, Visio) are referenced before any cross-platform or Linux-native options.
Recommendations
- Provide Azure CLI or REST API examples for configuring conditional access policies, alongside PowerShell examples.
- Offer downloadable architecture diagrams in open formats (e.g., SVG, PDF) in addition to Visio files.
- Explicitly mention Linux/macOS compatibility for management tasks and tools.
- Where PowerShell is referenced, add notes or links to equivalent steps using Bash, Azure CLI, or other cross-platform tools.
- Ensure that any referenced scripts or automation can be run from Linux/macOS environments.
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 →
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 and PowerShell second. Both tools are cross-platform, but PowerShell is more closely associated with Windows. No Linux/macOS-specific tools or patterns are omitted, and all command-line examples (git, kubectl, curl) are platform-agnostic. There is a slight bias in listing Windows-oriented PowerShell as an equal alternative, but no critical sections are Windows-only.
Recommendations
- Explicitly mention that both Azure CLI and PowerShell are cross-platform and provide installation links for Linux/macOS.
- Consider listing Azure CLI (the more common cross-platform tool) as the primary method, with PowerShell as an alternative.
- Add a note clarifying that all command-line examples work on Linux/macOS unless stated otherwise.
- If possible, include screenshots or instructions for Linux/macOS terminal environments alongside any Windows screenshots.
Aks
Develop on Azure Kubernetes Service (AKS) with Helm
...ure-aks-docs/blob/main/articles/aks/quickstart-helm.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all Azure resource management steps, with PowerShell (a Windows-centric tool) given equal prominence. There is no explicit Linux bias, but the presence of PowerShell examples and references may be unnecessary for Linux/macOS users, and Azure CLI (cross-platform) is not clearly prioritized. No Linux-specific tools or shell patterns are shown, and PowerShell is presented as a primary option alongside CLI throughout.
Recommendations
- Clearly indicate Azure CLI as the recommended/default approach for cross-platform users, with PowerShell as an alternative for Windows users.
- Move Azure CLI examples before PowerShell examples in each section, or collapse PowerShell examples behind a tab or expandable section.
- Add a note clarifying that Azure CLI works on Linux/macOS/Windows, while PowerShell is primarily for Windows.
- Consider omitting PowerShell examples from the main flow, or providing them only in a dedicated Windows section.
- Add explicit Linux/macOS shell instructions where relevant (e.g., for installing prerequisites, using bash/zsh, etc.).
Aks
Security bulletins for Azure Kubernetes Service (AKS)
.../blob/main/articles/aks/security-bulletins/overview.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation provides security bulletins for both Linux and Windows AKS node images. However, several bulletins (AKS-2025-004, AKS-2025-003, AKS-2025-002) focus exclusively on Windows-specific vulnerabilities and remediation steps, listing only Windows node image versions and upgrade instructions. These Windows sections appear in sequence, and there are no equivalent Linux-specific security bulletins or upgrade instructions for those issues. While Linux vulnerabilities (e.g., runc, Calico) are covered elsewhere, the Windows bulletins are presented with more granularity and detail, and Linux instructions are sometimes less explicit.
Recommendations
- Ensure Linux and Windows vulnerabilities are presented with equal detail and clarity.
- For Windows-only bulletins, clarify if Linux is unaffected and provide equivalent Linux node image version information where relevant.
- When listing upgrade instructions, include both Linux and Windows node image versions if applicable, or explicitly state which OS is affected.
- Consider alternating or grouping Windows and Linux sections to avoid perceived prioritization.
- Add explicit Linux troubleshooting or mitigation steps for parity where possible.
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page is strongly Linux-focused, as AKS container security features (user-namespaces, AppArmor, seccomp) are only available on Linux nodes. However, there is some mild Windows bias in the 'Before you begin' section, where Windows tools (Azure PowerShell, Azure portal) are mentioned alongside Azure CLI for cluster creation, and in the references to limitations (explicitly calling out lack of support for Windows node pools). No PowerShell-only examples are given, and all technical walkthroughs use Linux-native tools and concepts. There are no examples or guidance for securing containers on Windows node pools, and the documentation does not provide Linux alternatives for Windows-only features.
Recommendations
- Clarify that all technical steps and examples are for Linux node pools only, and provide a clear section for Windows node pool users explaining what security features are (and are not) available.
- If possible, add parity guidance for Windows node pools (e.g., mention Windows container security features, or link to relevant documentation).
- In the 'Before you begin' section, list Azure CLI first (as it is cross-platform), and clarify that Azure PowerShell and Azure portal are available on Windows and macOS, but Linux users may prefer CLI.
- Explicitly state that Linux security features (AppArmor, seccomp, user-namespaces) do not apply to Windows containers, and provide links to Windows container security documentation.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for scaling AKS clusters. However, PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, despite CLI being cross-platform and more commonly used on Linux/macOS. There are no Linux-specific shell examples (e.g., Bash), and the tab order presents Azure CLI first but does not explicitly favor Windows tools. No Windows-only tools or patterns are mentioned, and all commands shown are available cross-platform. The bias is minor and mainly in the equal treatment of PowerShell, which may be less relevant for Linux/macOS users.
Recommendations
- Clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Consider adding Bash shell script examples for common Linux workflows.
- Optionally, reorder tabs to show Azure CLI as the default/preferred method for cross-platform usage.
- Explicitly mention that PowerShell examples are primarily for Windows users.
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 →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation references both Azure CLI and Azure PowerShell as ways to create an AKS cluster, listing PowerShell (Windows-centric) alongside CLI and portal options. However, all operational examples (start/stop node pool) use Azure CLI, which is cross-platform. There are no PowerShell-specific examples, but PowerShell is mentioned before Linux-native alternatives in the 'Before you begin' section, and no explicit Linux/macOS instructions or parity notes are provided.
Recommendations
- Clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
- List Linux/macOS options (Azure CLI) before or alongside PowerShell in the 'Before you begin' section.
- Add a note or section explicitly confirming Linux/macOS compatibility for all commands.
- Consider providing example commands for PowerShell only if there are meaningful differences, otherwise focus on CLI.
- Avoid implying PowerShell is required for non-Windows users.
Aks
Supported Kubernetes versions in Azure Kubernetes Service (AKS).
...lob/main/articles/aks/supported-kubernetes-versions.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for managing AKS clusters, but does not offer Linux/macOS-specific command-line examples (e.g., bash, shell scripts) or mention Linux-native tools. Windows tools (PowerShell) are given equal prominence to Azure CLI, and in some cases, Windows-specific components and instructions (such as Install-AzAksKubectl) are highlighted. There are no explicit Linux/macOS biases in the main AKS lifecycle or support policy content, but the command-line guidance and tooling references are Windows-centric.
Recommendations
- Add explicit bash/shell examples for Linux/macOS users alongside Azure CLI and PowerShell examples.
- Clarify that Azure CLI works cross-platform and is recommended for Linux/macOS users.
- Where PowerShell is mentioned, also mention bash/zsh equivalents or note platform compatibility.
- Highlight Linux-native tools or workflows where relevant (e.g., kubectl installation via package managers like apt, yum, or Homebrew).
- Ensure that any references to Windows-specific components (e.g., Windows2022) are balanced with Linux equivalents and not presented first unless contextually necessary.
Aks
Kubernetes on Azure tutorial - Deploy an application to Azure Kubernetes Service (AKS)
...articles/aks/tutorial-kubernetes-deploy-application.md
Low Priority
View Details →
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 the CLI is cross-platform, PowerShell is primarily a Windows tool (though available on Linux/macOS). The documentation does not provide explicit Linux/macOS shell examples (e.g., Bash), and PowerShell instructions are given equal prominence to CLI, potentially signaling a Windows-centric approach. However, all critical tasks can be completed using the CLI, which is cross-platform.
Recommendations
- Clarify that Azure CLI commands work on Linux/macOS and Windows equally, and consider explicitly mentioning Bash or zsh compatibility.
- Add explicit Bash/zsh shell examples or notes for Linux/macOS users, especially for steps involving file editing or environment variables.
- Relegate PowerShell instructions to a separate section or after CLI instructions, to avoid implying Windows-first workflow.
- Include a note about PowerShell availability on Linux/macOS if PowerShell instructions are retained.
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 →
Detected Bias Types
Powershell Heavy
Windows First
Windows Tools
Summary
The documentation provides parallel examples for Azure CLI (cross-platform) and Azure PowerShell (Windows-centric), but PowerShell is given equal prominence throughout, and some instructions reference Windows-specific tools and patterns. There is no explicit Linux/macOS bias, but the presence and parity of PowerShell examples may suggest a slight Windows bias, especially for users unfamiliar with PowerShell. No critical steps are Windows-only, and all essential tasks can be completed with Azure CLI, which is cross-platform.
Recommendations
- Clarify that Azure CLI is fully cross-platform and recommend it as the default for Linux/macOS users.
- Consider moving Azure CLI examples before PowerShell examples in each section to reinforce CLI as the primary, cross-platform approach.
- Add explicit notes or tabs for Bash or macOS users if there are any OS-specific considerations (e.g., environment variable syntax differences).
- Reduce emphasis on PowerShell unless a feature is only available in PowerShell.
- Ensure all screenshots and UI references are OS-neutral or include Linux/macOS variants if relevant.
Aks
Upgrade the Azure Kubernetes Service (AKS) cluster control plane
...cs/blob/main/articles/aks/upgrade-aks-control-plane.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all upgrade operations, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and is always presented immediately after CLI examples. There are no Linux-specific shell examples (e.g., Bash, zsh), nor is there explicit mention of Linux/macOS compatibility for the CLI commands. The 'Before you begin' section lists Azure PowerShell alongside Azure CLI, potentially implying parity or preference for Windows tooling. However, the Azure CLI is cross-platform and all provided CLI commands are compatible with Linux/macOS.
Recommendations
- Clarify that Azure CLI commands work on Linux, macOS, and Windows.
- Consider listing Azure CLI examples first and PowerShell second, as CLI is cross-platform.
- Add explicit notes or callouts for Linux/macOS users, confirming that all CLI commands are supported on their platforms.
- Remove or de-emphasize PowerShell instructions unless there is a Windows-specific scenario.
- Include example shell environments (e.g., Bash) in screenshots or outputs where relevant.
Aks
Upgrade Azure Kubernetes Service (AKS) node images
...-aks-docs/blob/main/articles/aks/upgrade-node-image.md
Low Priority
View Details →
Detected Bias Types
Windows Reference In Notes
Summary
The documentation is largely cross-platform, using Azure CLI and kubectl commands that work on Linux, macOS, and Windows. However, in two notes, it references Windows and PowerShell environments specifically when discussing potential differences in the kubectl JSONPath command, without providing equivalent Linux/macOS-specific guidance or examples. No Windows-only tools or PowerShell-heavy examples are present, and command syntax is generic.
Recommendations
- When mentioning shell differences, provide explicit examples for both Windows/PowerShell and Linux/macOS shells, or link to relevant shell-specific documentation for all platforms.
- Clarify if any commands require adaptation for Linux/macOS users, and provide those adaptations if necessary.
- Avoid referencing only Windows/PowerShell environments in notes; include Linux/macOS for parity.
Aks
Use AMD GPUs on Azure Kubernetes Service (AKS)
.../azure-aks-docs/blob/main/articles/aks/use-amd-gpus.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions Windows as an OS option when discussing AKS cluster creation and node pool support, but quickly clarifies that Windows is not supported for AMD GPU node pools. In the 'Before you begin' section, cluster creation options are listed as Azure CLI, Azure PowerShell, and Azure Portal—with PowerShell (Windows-centric) mentioned before the Portal. However, all technical examples and instructions throughout the page use cross-platform tools (Azure CLI, kubectl, bash), and there are no PowerShell-specific commands or Windows-only tooling. No critical steps are Windows-only, and Linux is clearly the supported platform for AMD GPU node pools.
Recommendations
- List Azure Portal before PowerShell when suggesting cluster creation methods, or clarify that PowerShell is Windows-specific.
- Explicitly state that all examples are for Linux node pools, and that Windows node pools are not supported for AMD GPU workloads.
- Consider adding a brief note for macOS users regarding Azure CLI and kubectl installation if relevant.
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 →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for scaling AKS nodes, but PowerShell (a Windows-centric tool) is given equal prominence to the cross-platform Azure CLI. PowerShell version requirements and installation links are included, which may be unnecessary for Linux/macOS users. The CLI and PowerShell tabs are presented together, but PowerShell is a Windows-specific tool, and no Linux/macOS shell examples (e.g., Bash) are provided. There is a slight Windows-first bias in mentioning PowerShell alongside CLI, and the documentation assumes familiarity with Windows tooling.
Recommendations
- Make it clear that Azure PowerShell is primarily for Windows users, and recommend Azure CLI for cross-platform usage.
- Present Azure CLI examples first, and note its cross-platform compatibility.
- Remove or de-emphasize PowerShell requirements for Linux/macOS users.
- Add explicit Bash shell examples or notes for Linux/macOS users where relevant.
- Clarify that all kubectl commands are cross-platform and can be run from any OS.
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 →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page exhibits minor Windows bias in the prerequisites section, where Windows tools (Azure PowerShell) are mentioned before Linux equivalents (Azure CLI), and both are referenced as options for creating AKS clusters. However, the main workflow and all command-line examples use kubectl, which is cross-platform and standard for Kubernetes management. No critical steps are Windows-only, and Linux/macOS users can follow all instructions without issue.
Recommendations
- List Azure CLI before Azure PowerShell in prerequisites, as CLI is cross-platform and preferred by many Linux/macOS users.
- Explicitly state that all kubectl commands work on Windows, Linux, and macOS.
- Where Azure PowerShell is mentioned, provide a direct link or note for Linux/macOS installation and usage.
- Consider adding a brief note in the prerequisites about platform compatibility for Azure CLI and PowerShell.
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 →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a mild Windows bias in its use of Azure CLI commands and patterns. While AKS clusters only support Linux node pools for pod-managed identities (explicitly stated), the documentation does not provide any Windows-specific examples, nor does it mention Windows tools or PowerShell. However, the page consistently uses Azure CLI commands and Bash-style environment variables (e.g., export), which are native to Linux/macOS but can be run on Windows via WSL, Azure Cloud Shell, or the Windows version of Azure CLI. There is no explicit guidance for Windows users on how to adapt these commands, nor are PowerShell equivalents provided. The documentation assumes the user is comfortable with Bash syntax and Linux conventions, which may create minor friction for Windows users unfamiliar with these tools.
Recommendations
- Add a brief note at the start of the prerequisites section clarifying that Azure CLI commands and Bash syntax are used, and provide guidance for Windows users (e.g., recommend using Azure Cloud Shell, WSL, or provide PowerShell equivalents where possible).
- Where environment variables are set with 'export', provide PowerShell equivalents (e.g., $env:IDENTITY_RESOURCE_GROUP = 'myIdentityResourceGroup') for Windows users.
- Explicitly mention that pod-managed identities are only supported on Linux node pools, and clarify that Windows node pools are not supported.
- Consider adding a short section or callout for Windows users, explaining how to run the commands (e.g., using Azure CLI for Windows, Cloud Shell, or WSL).
Aks
Configure Metrics Server VPA in Azure Kubernetes Service (AKS)
...cles/aks/use-metrics-server-vertical-pod-autoscaler.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page shows a mild Windows bias by referencing Azure Cloud Shell and its file upload UI in multiple places, but does not provide equivalent guidance for Linux/macOS users. The prerequisites mention using 'kubectl' installed locally or via Azure Cloud Shell, but do not mention Linux-specific shell environments or file management approaches. All command-line examples use Bash syntax, which is cross-platform, and there are no PowerShell-specific commands or Windows-only tools referenced.
Recommendations
- Add explicit instructions for Linux/macOS users on how to upload or create the YAML manifest file, such as using 'scp', 'curl', or text editors.
- Clarify that Bash commands work on Linux/macOS and Windows (with WSL or Git Bash), and mention alternatives if needed.
- When referencing Azure Cloud Shell's file upload UI, also mention equivalent Linux/macOS workflows (e.g., using 'nano', 'vim', or direct file creation in the terminal).
- Consider adding a note that all commands are Bash-compatible and provide PowerShell equivalents only if needed.
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 →
Detected Bias Types
Windows First
Summary
The documentation page mentions Windows tooling (Azure PowerShell) as a primary option for creating an AKS cluster in the prerequisites section, listing it before Linux-native alternatives. However, all actual command examples throughout the page use Azure CLI and kubectl, which are cross-platform and work on Linux, macOS, and Windows. No PowerShell-specific examples or Windows-only tools are used in the step-by-step instructions.
Recommendations
- List Linux-native options (Azure CLI) before Windows-specific ones (Azure PowerShell) in the prerequisites section to avoid implicit prioritization.
- Explicitly state that all shown commands work on Linux, macOS, and Windows to reassure non-Windows users.
- Consider adding a note clarifying that Azure PowerShell is primarily for Windows users, while Azure CLI is cross-platform.
- If mentioning PowerShell, provide parity by mentioning Bash or other Linux shells as alternatives.
Aks
Secure Pod Traffic with Network Policies in Azure Kubernetes Service (AKS)
...ks-docs/blob/main/articles/aks/use-network-policies.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation provides parity for both Linux and Windows AKS clusters, but there is a slight Windows bias in several areas. Windows-specific tools and terminology (such as HNS ACLPolicies) are mentioned before or alongside Linux equivalents (IPTables), and Windows node pool setup is described in detail, including credential creation. The documentation sometimes presents Windows-specific instructions and limitations before or alongside Linux, and Windows features (such as admin credential setup) are highlighted even in sections that apply to both platforms. However, Linux examples and instructions are present and complete, and most commands are cross-platform (bash/Azure CLI).
Recommendations
- Ensure Linux instructions/examples are presented first where possible, especially in sections that apply to both platforms.
- Balance the mention of platform-specific tools (e.g., explain IPTables for Linux before HNS for Windows, or present them together with equal detail).
- Where credential setup is required for Windows, clarify that it is only necessary for Windows node pools and avoid including it in Linux-only sections.
- Add explicit notes or tables summarizing which steps apply to which OS, to reduce confusion.
- Consider adding more Linux/macOS-specific troubleshooting or caveats if any exist.