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 276-300 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 output examples and file path references (e.g., C:\Users\<username>\.kube\config) are Windows-specific. There are no Linux/macOS path examples, and the output messages reference Windows file system conventions, which may cause confusion for non-Windows users.
Recommendations
- Include Linux/macOS equivalents for file paths in output examples (e.g., ~/.kube/config).
- Add a note clarifying that Azure CLI works on Windows, Linux, and macOS, and that file paths will differ by OS.
- Show output examples for both Windows and Linux/macOS where file paths are mentioned.
- Avoid using only Windows-style paths in documentation output unless the section is explicitly Windows-only.
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 Only Note
Summary
The documentation is mostly platform-neutral, but it contains a note specifically about Windows nodes: AKS reserves an extra 2 GB for system processes in Windows nodes, which is not part of the calculated memory. No equivalent details or examples are provided for Linux nodes, nor are Linux-specific behaviors or caveats mentioned. The documentation does not provide examples or instructions that are exclusive to Windows or PowerShell, but the only OS-specific detail is about Windows.
Recommendations
- Add a corresponding note for Linux nodes, describing any OS-level reservations or differences in resource allocation, if applicable.
- Clarify whether the extra 2 GB reservation for system processes is unique to Windows or if Linux nodes have a similar (or different) reservation.
- If there are Linux-specific resource reservation behaviors, document them explicitly.
- Ensure parity in OS-specific notes so Linux/macOS users have clear expectations.
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 provide command-line examples or tooling instructions that are specific to Windows or PowerShell. However, in the 'Azure discounts' section, the Azure Hybrid Benefits are described as applicable to 'on-premises Windows Server and SQL Server licenses,' which is a Windows-centric offering. No Linux equivalent discount or benefit is mentioned, and the section does not clarify whether Linux users have similar options.
Recommendations
- Clarify whether Azure Hybrid Benefits or similar cost-saving programs exist for Linux workloads, such as Red Hat or SUSE subscriptions, and mention them if applicable.
- Explicitly state the applicability of Azure discounts to Linux-based AKS clusters, or provide links to relevant Linux cost optimization programs.
- Ensure that future documentation sections on licensing or discounts do not focus exclusively on Windows Server unless it is truly the only supported platform.
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
Summary
The documentation page displays mild Windows bias by listing Windows-centric tools (Azure PowerShell) before Linux alternatives and referencing Windows Server in the limitations section. While the main examples use Azure CLI (cross-platform), the instructions for creating an AKS cluster mention Azure PowerShell before Linux-friendly options, and there is no explicit mention of Linux shell commands or patterns. No critical steps are Windows-only, but the ordering and tool references may subtly favor Windows users.
Recommendations
- List Linux-native options (Azure CLI, Bash) before Windows-specific tools (PowerShell) when presenting alternatives.
- Explicitly mention that Azure CLI works on Linux/macOS and provide links to Bash or shell usage guides.
- Add examples or notes for Linux/macOS users, such as verifying prerequisites or installing Azure CLI on those platforms.
- Avoid referencing Windows Server in limitations without equivalent Linux context unless necessary.
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 Section
Summary
The documentation is generally cross-platform and AKS-focused, with explicit callouts for both Linux and Windows node pools. However, there is a dedicated section for Windows Server-based node pools listing required FQDNs for Windows updates and binaries, while the Linux equivalents are listed in a separate 'Optional recommended FQDN / application rules' section. Some Microsoft-specific tools (e.g., PowerShell) are mentioned as examples of packages, but not in a way that prioritizes Windows over Linux. No PowerShell-heavy examples or Windows-first ordering is present, and Linux-specific requirements (such as Ubuntu NTP and update endpoints) are clearly documented.
Recommendations
- Move the Linux update endpoints (security.ubuntu.com, etc.) from 'Optional recommended' to a more prominent section, similar to the Windows node pool section, to emphasize their importance for Linux clusters.
- When listing example packages (e.g., in 'packages.microsoft.com'), clarify which are relevant for Linux and which for Windows, and provide parity in mentioning common Linux tools (e.g., apt, bash) alongside PowerShell.
- Ensure that any future configuration or command examples include both Linux (bash/apt) and Windows (PowerShell) variants if relevant.
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 displays mild Windows bias, most notably by referencing PowerShell cmdlets for conditional access configuration and providing a Visio architecture diagram (a Windows-centric format). Windows tools and patterns (PowerShell, Visio) are mentioned before or instead of Linux/macOS equivalents. There are no explicit Linux/macOS command examples or alternative tool suggestions for these cases.
Recommendations
- Provide equivalent Linux/macOS command-line examples for conditional access configuration, such as Azure CLI or REST API usage.
- Offer architecture diagrams in open formats (e.g., SVG, PDF) alongside Visio files.
- When referencing tools (e.g., PowerShell), mention cross-platform alternatives and link to their documentation.
- Ensure that examples and guidance are not solely focused on Windows tooling, and include Linux/macOS workflows where relevant.
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 mentions both Azure CLI and Azure PowerShell as prerequisites and provides cleanup instructions for both, but consistently lists Azure CLI (cross-platform) before Azure PowerShell (Windows-centric). There are no PowerShell-only examples, and all command-line instructions use bash/kubectl/curl, which are cross-platform. No Windows-only tools or patterns are present, and Linux/macOS users can follow all steps without friction.
Recommendations
- Maintain parity by continuing to provide Azure CLI examples first, as it is cross-platform.
- Consider explicitly noting that all kubectl and curl commands work on Linux, macOS, and Windows (with WSL or appropriate tools installed).
- If PowerShell examples are provided, ensure equivalent bash/CLI examples are always present and shown first.
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 operations, with PowerShell examples presented in parallel tabs. While Azure CLI is cross-platform, Azure PowerShell is primarily a Windows-centric tool (though it is available for Linux/macOS). There are no explicit Linux shell examples for Azure resource management, and the documentation references Azure Cloud Shell (which is cross-platform) but does not provide native Linux command alternatives for tasks like resource group or registry creation. The ordering of examples is generally Azure CLI first, which is positive for Linux parity, but the presence of PowerShell throughout may signal a Windows bias.
Recommendations
- Clarify that Azure CLI commands are fully cross-platform and preferred for Linux/macOS users.
- Explicitly mention that Azure PowerShell is optional and primarily for users familiar with Windows/PowerShell environments.
- Consider adding native Bash shell script examples for common tasks, especially for Linux users who may prefer scripting over Azure CLI.
- Add a note or section highlighting Linux/macOS compatibility and any differences in setup or usage.
- Ensure that any references to tools (e.g., Azure Cloud Shell, kubectl, Helm) clearly state their cross-platform nature.
Aks
Resize Node Pools in Azure Kubernetes Service (AKS)
...re-aks-docs/blob/main/articles/aks/resize-node-pool.md
Low Priority
View Details →
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 may indicate a Windows bias. The CLI examples are cross-platform, but PowerShell is highlighted equally, despite being less relevant for Linux/macOS users. There are no Linux-specific tools or patterns mentioned, and no macOS-specific guidance. The order of tabs (CLI first, then PowerShell) is appropriate, but the presence of PowerShell examples may create friction for non-Windows users.
Recommendations
- Clearly indicate that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Consider demoting PowerShell examples to a secondary section or providing a note that PowerShell is Windows-only.
- Add explicit guidance for Linux/macOS users, such as installation instructions for Azure CLI.
- If possible, provide Bash script examples for automation on Linux/macOS.
- Review whether PowerShell examples are necessary for every step, or if CLI coverage is sufficient.
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
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for scaling AKS clusters, but PowerShell (a Windows-centric tool) is given equal prominence as Azure CLI, despite CLI being cross-platform. There are no Linux/macOS-specific examples or notes, and PowerShell examples may be less relevant for non-Windows users. The ordering of examples does not favor Windows, but the inclusion of PowerShell throughout creates a subtle bias.
Recommendations
- Clarify that Azure CLI is cross-platform and recommended for Linux/macOS users.
- Add explicit notes or sections for Linux/macOS users, confirming that all CLI commands work natively on those platforms.
- Consider moving PowerShell examples to a separate section or appendix, or clearly indicate their Windows focus.
- Provide bash shell examples for common tasks, where appropriate.
- Add troubleshooting notes for Linux/macOS environments if any differences exist.
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 node images in AKS. 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 examples or upgrade instructions in those sections. The Linux node image is mentioned in AKS-2025-0012, but the Windows-specific bulletins are more detailed and frequent, suggesting a mild Windows bias in coverage and remediation guidance.
Recommendations
- For each Windows-specific vulnerability and remediation, provide equivalent Linux node image information if applicable, or explicitly state that Linux is not affected.
- Ensure that upgrade instructions and examples are provided for both Linux and Windows node images where relevant.
- When listing affected versions and remediation steps, present Linux and Windows information in parallel to avoid the perception of Windows-first bias.
- If a vulnerability is Windows-only, clarify why Linux is not affected to help Linux users understand the scope.
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 First
Powershell Heavy
Summary
The documentation references Windows-centric tools (Azure PowerShell) before Linux alternatives (Azure CLI) when listing cluster creation options. While all operational examples use Azure CLI, which is cross-platform, the initial mention of PowerShell and the ordering may subtly prioritize Windows users. No exclusive Windows-only commands or missing Linux examples are present.
Recommendations
- List Azure CLI before Azure PowerShell when suggesting cluster creation methods, as CLI is cross-platform and more commonly used on Linux/macOS.
- Clarify that Azure CLI commands work equally on Windows, Linux, and macOS.
- Consider including explicit notes or examples for Linux/macOS users where relevant, especially in setup or prerequisites.
- Avoid implying PowerShell is the default or preferred method unless contextually justified.
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
Windows Examples
Windows Linux Equivalence
Windows First
Summary
The documentation provides both Windows and Linux information for AKS, but there is a notable presence of Windows-specific tools (e.g., Azure PowerShell, Windows containerd versions, Windows node manager components) and examples. In sections about installing kubectl and listing available Kubernetes versions, Windows (PowerShell) commands are presented alongside Azure CLI, but sometimes with more emphasis or detail. OS component tables consistently list Windows and Linux side-by-side, but Windows-specific add-ons and components are called out explicitly. There are no critical sections that are Windows-only, but Windows tooling and examples are given equal or slightly more prominence than Linux, which may create minor friction for Linux/macOS users.
Recommendations
- Ensure Linux examples and tools (Azure CLI, Bash) are presented first, or at least equally, in all code blocks and instructions.
- Clarify when a command or tool is Windows-only, and provide Linux/macOS equivalents where possible.
- Add explicit Bash or shell examples for tasks currently shown only in PowerShell (if any).
- Review add-on/component tables to ensure Linux and Windows parity in documentation and explanations.
- Consider a dedicated section for Linux/macOS users outlining best practices and tools.
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 Tools
Windows First
Missing Linux Example
Summary
The documentation is heavily focused on Azure CLI commands and Azure portal steps, which are cross-platform but have a strong association with Windows environments. There is no explicit mention of Windows-only tools (like PowerShell), but all command-line examples use Azure CLI and bash-style scripting, which is more common on Linux/macOS but also available on Windows. The documentation does not provide any Linux-specific troubleshooting, nor does it mention platform-specific differences or considerations. However, the documentation does note that pod-managed identities are only supported on Linux node pools, which is a technical limitation rather than a documentation bias. There are no PowerShell-only examples, and kubectl usage is shown, which is cross-platform. The Azure portal instructions are generic, but the overall flow assumes familiarity with Azure CLI, which is available on all platforms but most commonly used on Windows.
Recommendations
- Explicitly state that all CLI commands work on Linux, macOS, and Windows, and provide links to installation guides for each platform.
- Add notes or sections for platform-specific troubleshooting (e.g., common issues on Linux/macOS vs. Windows).
- Provide PowerShell equivalents for Azure CLI commands for Windows users, or bash equivalents for Linux/macOS users if PowerShell is shown.
- Clarify that bash-style variable usage (e.g., $VAR) is for bash shells and provide Windows CMD/PowerShell equivalents where appropriate.
- Highlight that Azure CLI and kubectl are cross-platform and provide installation instructions for each OS.
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 minor Windows bias by mentioning Azure Cloud Shell (which defaults to Bash, but is often associated with Windows environments) and by referencing 'your computer' without specifying OS. There are no explicit Windows-only tools, PowerShell examples, or Windows-specific instructions, but the guidance to use Cloud Shell's 'Manage files' and 'Upload' features is presented before any mention of Linux/macOS equivalents (such as using scp, cp, or other CLI tools). No Linux/macOS-specific instructions or troubleshooting are provided, but all commands are cross-platform.
Recommendations
- Explicitly mention that all kubectl commands and YAML files work on Linux, macOS, and Windows.
- Provide Linux/macOS-specific instructions for uploading files (e.g., using scp, cp, or curl) alongside Cloud Shell guidance.
- Clarify that Azure Cloud Shell is available from any OS and defaults to Bash, not PowerShell.
- Add troubleshooting notes for common Linux/macOS issues (e.g., file permissions, line endings).
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
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples throughout, but PowerShell is featured as a first-class option in every major section, including environment setup, resource creation, and Kubernetes configuration. This can be interpreted as a Windows bias, since PowerShell is primarily a Windows tool (though it is available cross-platform), and its inclusion may signal to Linux/macOS users that it is expected or preferred. However, all critical steps are covered with Azure CLI, which is fully supported on Linux/macOS. No steps are Windows-only, and Linux users can complete the tutorial using CLI. The order of presentation sometimes puts PowerShell before CLI, and there are no explicit bash examples for environment variable creation (e.g., using export), which may cause minor friction for Linux users.
Recommendations
- Add explicit bash examples for environment variable creation (using export) to improve clarity for Linux/macOS users.
- Clearly indicate that Azure CLI is cross-platform and preferred for Linux/macOS users, while PowerShell is optional.
- Consider presenting Azure CLI examples before PowerShell in each section to reduce perceived Windows-first bias.
- Add a short note at the beginning clarifying tool parity and platform support.
Aks
Handle AKS node upgrades with GitHub Actions
...-docs/blob/main/articles/aks/upgrade-github-actions.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Mention
Summary
The documentation mentions Windows and PowerShell options before Linux equivalents in the 'Before you begin' section, listing Azure CLI, Azure PowerShell, and Azure Portal as ways to create an AKS cluster. However, the main workflow and all actionable examples use Azure CLI and Ubuntu runners, which are cross-platform and Linux-friendly. There are no PowerShell-only examples, and all steps for the actual upgrade process are platform-neutral.
Recommendations
- List Linux-first options when describing how to create an AKS cluster, e.g., mention Azure CLI before PowerShell.
- Clarify that Azure CLI is cross-platform and works on Windows, Linux, and macOS.
- Consider removing or de-emphasizing PowerShell in introductory lists unless a PowerShell-specific workflow is provided.
- Add a note that all steps are applicable on Linux, macOS, and Windows (with Azure CLI installed).
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 Mention
Windows First
Summary
The documentation is generally cross-platform, using Azure CLI and kubectl commands that work on Linux, macOS, and Windows. However, there are repeated notes referencing Windows and PowerShell environments before mentioning Linux shells, and guidance on JSONPath differences is linked specifically for Windows/PowerShell users. No Linux-specific examples or parity issues are present, but Windows environments are mentioned first and more explicitly.
Recommendations
- Balance notes about shell differences by mentioning Linux/macOS shells equally or first.
- If shell-specific guidance is provided, include explicit examples for both Windows (PowerShell/CMD) and Linux/macOS (bash/zsh).
- Clarify that all shown commands work on Linux/macOS unless otherwise noted.
- Add a brief section or note confirming Linux/macOS compatibility for all commands.
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 unsupported OS for AMD GPU node pools, and in the 'Before you begin' section, it lists Windows (via PowerShell) as one of the options for creating an AKS cluster before Linux. However, all technical instructions, examples, and commands provided in the main workflow use cross-platform tools (Azure CLI, kubectl, bash), and there are no PowerShell-specific or Windows-only examples. The documentation is generally Linux-focused, as AMD GPU support is only available for Linux node pools.
Recommendations
- List Linux options before Windows/PowerShell in the 'Before you begin' section to reflect actual support and workflow.
- Clarify that AMD GPU support is Linux-only earlier in the document, and consider removing Windows/PowerShell references from prerequisite steps to avoid confusion.
- If mentioning Windows/PowerShell, explicitly state that these are not supported for AMD GPU node pools and provide guidance for Linux users.
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 mentions Windows-specific tools (Azure PowerShell) alongside cross-platform options (Azure CLI and Azure portal) when describing how to create an AKS cluster. However, Azure PowerShell is listed before Azure portal, and the reference to PowerShell may suggest a Windows-first approach. No Linux-specific tools or shell examples are provided, but all command-line examples use kubectl, which is cross-platform. There are no exclusive Windows-only instructions, but the ordering and inclusion of PowerShell may create a slight bias.
Recommendations
- List Azure CLI before Azure PowerShell when describing prerequisites, as CLI is cross-platform and preferred for Linux/macOS.
- Explicitly mention that Azure CLI and kubectl commands work on Windows, Linux, and macOS.
- Consider adding a note or section for Linux/macOS users, confirming parity and pointing to platform-specific installation guides if needed.
- Remove or de-emphasize PowerShell unless a unique Windows-only step is required.
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 lists Windows tooling (Azure PowerShell) before Linux/macOS equivalents (Azure CLI) in the prerequisites for creating an AKS cluster. However, all actual command examples use Azure CLI and bash/kubectl, which are cross-platform and commonly used on Linux/macOS. No PowerShell-specific or Windows-only commands are provided, and Linux users can follow all steps without friction.
Recommendations
- List Azure CLI before Azure PowerShell in the prerequisites to reflect the cross-platform nature of CLI and its usage in the examples.
- Clarify that all command examples use Azure CLI and bash, which are supported on Windows, Linux, and macOS.
- Optionally, provide a note or link for users who prefer PowerShell, but ensure CLI is presented as the primary, cross-platform method.
Aks
Trusted Launch with Azure Kubernetes Service (AKS)
...-aks-docs/blob/main/articles/aks/use-trusted-launch.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page shows mild Windows bias in its external references and link ordering. Key conceptual links for Secure Boot, TPM, and attestation point to Windows documentation first (e.g., /windows-hardware/design/device-experiences/oem-secure-boot, /windows/security/information-protection/tpm/trusted-platform-module-overview), even though the AKS feature is available for both Linux and Windows nodes. However, all command-line examples use Azure CLI and kubectl, which are cross-platform, and the documentation explicitly states that Windows Server node pools are not supported for Trusted Launch, focusing implementation on Linux. No PowerShell or Windows-only command examples are present.
Recommendations
- Provide or prioritize Linux-focused external documentation links for Secure Boot, TPM, and attestation (e.g., point to Linux kernel documentation or Azure Linux docs where available).
- Clarify in the overview that Secure Boot and vTPM are supported for select Linux distributions and provide a link to the relevant Linux support matrix.
- Add a brief note or section on how Trusted Launch applies to Linux vs. Windows, including any differences in implementation or troubleshooting.
- Ensure troubleshooting links (e.g., verify Secure Boot failures) include Linux-specific guidance and not just Windows VM references.
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 both Linux and Windows examples for AKS network policy setup, but Windows-specific instructions (such as registering preview features and creating Windows admin credentials) are given their own dedicated section and are described in detail before Linux equivalents. Windows tooling (HNS ACLPolicy) is mentioned alongside Linux (IPTables), but the documentation does not provide Linux-specific troubleshooting or advanced examples. The overall flow and examples are Azure CLI-based, which is cross-platform, but the Windows setup is more prominently featured and detailed.
Recommendations
- Ensure Linux and Windows instructions are presented with equal prominence and detail, ideally side-by-side or in parallel sections.
- Add advanced Linux troubleshooting and feature parity notes where Windows limitations are discussed.
- Where Windows-specific tools (HNS ACLPolicy) are mentioned, provide equivalent Linux tool details (IPTables) and usage examples.
- Consider starting with Linux examples, as AKS clusters are Linux-first by default, or alternate the order in different sections.
- Explicitly call out any differences in workflow or limitations for both platforms, not just Windows.
Aks
Use GPUs on Azure Kubernetes Service (AKS)
...zure-aks-docs/blob/main/articles/aks/use-nvidia-gpu.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page references Windows tooling and patterns before Linux equivalents in the 'Before you begin' section, listing Azure PowerShell and Azure portal before mentioning the Azure CLI. However, all actual command-line examples and step-by-step instructions use Linux-native tools (Azure CLI, kubectl, bash), and the AKS GPU support is explicitly for Linux node pools. No PowerShell-specific examples or Windows-only tools are provided for the main workflow.
Recommendations
- List Linux-first options (Azure CLI) before Windows-centric options (PowerShell, portal) in introductory sections.
- Clarify that AKS GPU support is for Linux node pools only, and that Windows node pools are not supported for GPU workloads.
- Remove or de-emphasize references to Azure PowerShell and the Azure portal in 'Before you begin', or provide parity by linking to Linux-specific quickstarts first.
- Explicitly state that all examples are Linux-based and that Windows users should use WSL or a Linux VM for these workflows.
Aks
Validate and test a PostgreSQL database deployment on AKS
...-docs/blob/main/articles/aks/validate-postgresql-ha.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation consistently uses Azure CLI (az) commands and Azure-specific patterns throughout, which are cross-platform but originate from the Windows ecosystem and are most familiar to Windows users. There is a notable reliance on Azure CLI for resource management, storage, and identity operations, with no mention of Linux-native alternatives or parity for Azure CLI installation and usage on Linux/macOS. All examples use Bash shell syntax, which is Linux/macOS-friendly, but the documentation does not clarify cross-platform requirements or provide guidance for Linux/macOS users regarding Azure CLI installation, authentication, or differences in behavior. There are no PowerShell-specific examples, but Azure CLI is a Microsoft tool and may be perceived as Windows-centric.
Recommendations
- Explicitly state that Azure CLI is cross-platform and provide installation instructions for Linux and macOS users.
- Mention any differences in Azure CLI usage or authentication on Linux/macOS, if applicable.
- Where possible, reference open-source or platform-neutral alternatives for Azure resource management (e.g., Terraform, REST API).
- Add a note clarifying that all Bash commands work on Linux/macOS and provide PowerShell equivalents for Windows users if needed.
- Ensure that any prerequisites (such as Azure CLI) are clearly documented for all platforms.