Aks
540
Total Pages
431
Linux-Friendly Pages
109
Pages with Bias
20.2%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
618 issues found
Showing 126-150 of 618 flagged pages
Aks
Access Kubernetes Resources using the Azure Portal
...e-aks-docs/blob/main/articles/aks/kubernetes-portal.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for updating AKS API server authorized IP ranges, but the PowerShell example is given equal prominence and appears directly after the CLI example. There are no Linux/macOS-specific examples or explicit mentions of Linux tools, and the PowerShell example may be less relevant for Linux/macOS users. However, the CLI example is cross-platform and appears first, mitigating the bias. No Windows-only tools or patterns are used elsewhere, and the YAML manifests target Linux node pools.
Recommendations
- Explicitly note that Azure PowerShell is Windows-centric and that Azure CLI is recommended for Linux/macOS users.
- Consider adding a note or tab for Bash-only or Linux/macOS-specific instructions where relevant.
- Clarify that all portal-based steps are OS-agnostic.
- If possible, provide a Bash command for retrieving the public IP address (e.g., `curl ifconfig.me` or `dig`), as not all Linux users have `dig` installed.
Create Pull Request
Aks
Upgrade Azure Kubernetes Service (AKS) node images
...-aks-docs/blob/main/articles/aks/upgrade-node-image.md
Low Priority
View Details →
Detected Bias Types
Windows Reference
Summary
The documentation provides Azure CLI and kubectl examples, which are cross-platform. However, there are repeated notes referencing Windows and PowerShell environments when discussing shell command differences, but no actual Windows/PowerShell-specific examples are provided. The documentation does not prioritize Windows tools or patterns, nor does it omit Linux/macOS equivalents.
Recommendations
- Clarify shell differences with concrete examples for both Windows (PowerShell/CMD) and Linux/macOS (bash/zsh) if relevant.
- If referencing Windows/PowerShell environments, also mention Linux/macOS environments for parity.
- Ensure notes about shell differences are balanced and provide actionable guidance for all platforms.
Aks
Stop and start an Azure Kubernetes Service (AKS) cluster
...-aks-docs/blob/main/articles/aks/start-stop-cluster.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for stopping and starting AKS clusters. However, PowerShell examples are presented alongside CLI examples, and PowerShell is referenced in the 'Before you begin' section as an option for creating a cluster. There are no Linux-specific examples or notes, but the Azure CLI is cross-platform and the PowerShell examples do not dominate the page. No Windows-only tools or patterns are mentioned, and Linux users can complete all tasks using the Azure CLI.
Recommendations
- Clarify that Azure CLI commands work on Linux, macOS, and Windows, and are the recommended cross-platform approach.
- Consider listing Azure CLI examples before PowerShell examples to reinforce Linux parity.
- Add a note in the 'Before you begin' section explicitly stating that Azure CLI is available on Linux and macOS, while PowerShell is primarily for Windows users (though PowerShell Core is cross-platform, most Linux users prefer CLI).
- If possible, add a brief section or callout for Linux/macOS users to confirm that all steps are fully supported on their platforms.
Aks
About the Agentic CLI for Azure Kubernetes Service (AKS)
...blob/main/articles/aks/agentic-cli-for-aks-overview.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation describes the Agentic CLI for AKS in a platform-neutral way, but it implicitly assumes Windows or Windows-like environments by referencing 'local Azure CLI credentials' and 'Docker' without clarifying Linux/macOS compatibility. No explicit Linux/macOS examples, prerequisites, or troubleshooting guidance are provided, and Windows-centric terminology (e.g., 'local machine', 'local credentials') appears first. However, there are no overt Windows-only tools or PowerShell-specific instructions.
Recommendations
- Explicitly state that the Agentic CLI for AKS supports Linux and macOS, not just Windows.
- Add installation and usage examples for Linux/macOS, including Docker and Azure CLI setup.
- Clarify any platform-specific prerequisites or troubleshooting steps (e.g., Docker installation on Linux/macOS).
- Ensure terminology and instructions are inclusive of all supported platforms (e.g., 'your local machine' instead of implying Windows).
- Provide links to platform-specific documentation for Docker and Azure CLI.
Aks
Create an OpenID Connect (OIDC) Provider for your Azure Kubernetes Service (AKS) Cluster
...ure-aks-docs/blob/main/articles/aks/use-oidc-issuer.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation uses Azure CLI commands throughout, which are cross-platform. However, all shell examples use environment variable syntax ($VARIABLE) and multi-line commands with backslashes, which are typical of Bash (Linux/macOS), not Windows/PowerShell. There are no explicit Windows/PowerShell examples, but the instructions do not clarify compatibility or provide PowerShell syntax. The Azure CLI is the only tool used, which is available on all platforms. The documentation does not mention Windows tools or patterns, nor does it show Windows-specific instructions. However, the lack of explicit Linux/macOS mention or examples may cause minor friction for Windows users unfamiliar with Bash syntax.
Recommendations
- Add a note clarifying that Azure CLI commands are cross-platform and can be run on Windows, macOS, and Linux.
- Provide PowerShell syntax for environment variable assignment and multi-line commands, or link to Azure CLI usage guidance for Windows users.
- Explicitly state that the examples are Bash shell syntax and offer equivalent Windows/PowerShell examples where appropriate.
Aks
Install and Use the Agentic CLI for Azure Kubernetes Service (AKS) (Preview)
.../blob/main/articles/aks/agentic-cli-for-aks-install.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides platform-agnostic instructions for installing and using the Agentic CLI for AKS, but in the Docker daemon startup section, Windows/macOS instructions (Docker Desktop) are mentioned before Linux instructions (systemctl). All other examples and commands are cross-platform or explicitly include Linux guidance. No PowerShell-specific commands, Windows-only tools, or missing Linux examples are present.
Recommendations
- When describing how to start the Docker daemon, present Linux instructions first or equally alongside Windows/macOS instructions.
- Explicitly mention that Docker Desktop is available for both Windows and macOS, and that Linux users should use systemctl or their distribution's service manager.
- Consider adding clarifying notes for Linux users where relevant (e.g., permissions, sudo usage, config file locations).
Aks
Connect your Azure Kubernetes Service (AKS) cluster to AI agents using the Model Context Protocol (MCP) server
...main/articles/aks/aks-model-context-protocol-server.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides cross-platform instructions and download links for Windows, macOS, and Linux, and generally maintains parity across platforms. However, there are minor signs of Windows bias: keyboard shortcuts and VS Code instructions often list Windows first (e.g., 'Ctrl+Shift+P on Windows/Linux or Cmd+Shift+P on macOS'), and the VS Code extension workflow is described as the recommended path, which is more common among Windows users. There is also frequent mention of Docker Desktop, which is more prevalent on Windows, and tips for WSL (Windows Subsystem for Linux) users. PowerShell is not used for commands, but Windows is prioritized in some UI instructions and download tables.
Recommendations
- Alternate keyboard shortcut orders (e.g., list macOS first sometimes) or use neutral phrasing.
- Explicitly state that all workflows are equally supported on Linux/macOS, not just Windows.
- Add tips for Linux/macOS users where Windows-specific advice is given (e.g., Docker Desktop alternatives).
- Ensure troubleshooting and common issues sections mention Linux/macOS-specific scenarios as well as Windows.
- Where WSL is mentioned, also mention alternatives for Linux/macOS users (e.g., native Bash shells).
Aks
Troubleshoot the Agentic CLI for Azure Kubernetes Service (AKS)
.../main/articles/aks/agentic-cli-for-aks-troubleshoot.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation generally provides cross-platform troubleshooting steps and examples, with clear distinctions between Linux and macOS/Windows where relevant. However, in the Docker troubleshooting section, instructions for starting Docker on macOS/Windows are listed before Linux, which is a minor instance of 'windows_first' bias. All critical commands and solutions are provided for both Linux and macOS/Windows, and there are no missing Linux examples or exclusive use of Windows tools.
Recommendations
- When listing platform-specific instructions, consider rotating the order or grouping Linux and macOS together, or explicitly stating that the order is arbitrary.
- Where possible, provide parallel command-line examples for all platforms, even if the steps are similar.
- If one platform's instructions are more complex, consider providing a table or collapsible sections for clarity.
Aks
Certificate Rotation in Azure Kubernetes Service (AKS)
...ks-docs/blob/main/articles/aks/certificate-rotation.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides both Linux and Windows file paths for verifying TLS Bootstrapping, but Windows is mentioned second. All command-line examples use Azure CLI and Bash commands, which are cross-platform but default to Linux-style shell syntax. There are no PowerShell or Windows Command Prompt examples. However, in the section 'Verify TLS Bootstrapping is enabled on current agent node pool', the Linux path is listed first, and the Windows path is listed second. No Windows-specific tools or patterns are prioritized or exclusively mentioned. There are no missing Linux examples, but Windows users may need to adapt Bash syntax to PowerShell or Command Prompt.
Recommendations
- Add explicit PowerShell/Windows Command Prompt equivalents for Azure CLI and kubectl commands where possible, or note that Azure CLI and kubectl are cross-platform.
- Clarify that Bash syntax is shown, but Azure CLI and kubectl commands work on Windows, macOS, and Linux.
- Consider including a note or section for Windows users on adapting Bash commands to PowerShell/Command Prompt.
- Ensure parity in example order (alternate Linux/Windows first in file path listings).
Aks
Integrate Azure Container Registry with Azure Kubernetes Service (AKS)
...articles/aks/cluster-container-registry-integration.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides parallel examples for both Azure CLI and Azure PowerShell throughout, but PowerShell is a Windows-centric tool and is featured equally alongside Azure CLI. The page metadata and content frequently mention Azure PowerShell, and the tab structure presents PowerShell examples immediately after CLI, sometimes with explicit PowerShell module instructions. There are no Linux-specific shell examples (e.g., Bash, zsh), and no explicit mention of Linux/macOS parity for PowerShell commands. However, Azure CLI is cross-platform and is presented first in all cases, mitigating the impact. No Windows-only tools or patterns are used, and all tasks can be completed on Linux/macOS using Azure CLI.
Recommendations
- Clarify that Azure PowerShell is primarily for Windows users, and recommend Azure CLI for Linux/macOS users.
- Add explicit notes or guidance for Linux/macOS users, such as 'Azure CLI is recommended for Linux/macOS environments.'
- Consider including Bash/zsh shell command examples where relevant, or clarify that Azure CLI commands are compatible with Bash/zsh.
- Mention that PowerShell Core is available cross-platform, but Azure CLI is the default for Linux/macOS.
- Review troubleshooting and setup sections to ensure Linux/macOS users are not directed to Windows-only tools.
Aks
Concepts - Storage in Azure Kubernetes Services (AKS)
...re-aks-docs/blob/main/articles/aks/concepts-storage.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Linux and Windows container examples for volume mounting, but the Windows example is presented immediately after the Linux example, without additional context or parity issues. No PowerShell, Windows-only tools, or Windows-specific patterns are used except where necessary (e.g., Windows container mount paths). All storage concepts, YAML manifests, and instructions are generic and applicable to both Linux and Windows AKS node pools. The only notable bias is that the Windows example is shown after the Linux example, which is a minor ordering preference.
Recommendations
- Consider explicitly stating that all YAML manifests are applicable to both Linux and Windows containers, except where mount paths differ.
- When showing both Linux and Windows examples, clarify the differences and ensure equal prominence (e.g., use headings or side-by-side presentation).
- Add a brief note in the 'Persistent volumes' section explaining the limitations of sharing volumes between Windows and Linux pods, as already done.
- Ensure future updates include Linux/macOS CLI examples if any CLI commands are added.
Aks
Configure Azure CNI Networking in Azure Kubernetes Service (AKS)
...aks-docs/blob/main/articles/aks/configure-azure-cni.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides examples for Azure portal, Azure PowerShell, and Azure CLI, covering all major platforms. However, the PowerShell section is notably detailed, with explicit instructions for installation and usage on Windows, macOS, and Linux. The PowerShell instructions and references appear before the Azure CLI section, which is more universally applicable across platforms. The PowerShell section also includes more guidance on environment setup, potentially favoring Windows users and PowerShell workflows.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is more platform-neutral and widely used on Linux/macOS.
- Ensure CLI instructions are as detailed as PowerShell instructions, including environment setup and version requirements.
- Highlight that Azure CLI is the recommended cross-platform tool for Linux/macOS users.
- Consider adding explicit Bash shell examples or notes for Linux/macOS users where relevant.
- Balance the depth of guidance between PowerShell and CLI sections to avoid perceived preference.
Aks
Access Kubernetes Resources using the Azure Portal
...e-aks-docs/blob/main/articles/aks/kubernetes-portal.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for managing AKS authorized IP ranges, but the PowerShell section is presented immediately after the CLI section and is equally prominent. There are no Linux/macOS-specific examples or explicit mentions of their usage, and the PowerShell commands are Windows-centric. However, the main workflow is portal-based and platform-agnostic, and Azure CLI is cross-platform.
Recommendations
- Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and that PowerShell commands are primarily for Windows users.
- Consider showing Azure CLI examples first, as CLI is cross-platform and more widely used outside Windows.
- Add a note clarifying that PowerShell commands are for Windows users, while Azure CLI is recommended for Linux/macOS.
- If possible, provide bash shell examples for Linux/macOS users (e.g., using curl or dig for IP retrieval).
Aks
Create and Manage Persistent Volumes with Azure Files in Azure Kubernetes Service (AKS)
...cs/blob/main/articles/aks/create-volume-azure-files.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation is generally cross-platform and AKS-centric, but there are mild signs of Windows bias. Windows-specific instructions (such as path conventions and PowerShell/CMD syntax) are sometimes mentioned before or alongside Linux equivalents, and Windows paths are referenced in pod manifests. However, Linux examples are present throughout, and the majority of instructions and YAML manifests are platform-neutral or Linux-first. The only CLI examples are Azure CLI (cross-platform), and kubectl commands are universal. Windows-specific tools or patterns are not dominant, and Linux parity is mostly maintained.
Recommendations
- When referencing Windows path conventions or commands, ensure Linux/macOS equivalents are always shown first or equally.
- Clarify when examples are platform-specific, and provide both Linux and Windows syntax where relevant (e.g., for kubectl exec commands).
- Avoid referencing Windows paths in generic pod manifests unless the section is explicitly about Windows containers.
- Where possible, add explicit Linux/macOS instructions for any ambiguous steps (e.g., environment variable handling).
Aks
Move Azure Disk persistent volumes to another AKS cluster in the same or a different subscription
.../blob/main/articles/aks/csi-disk-move-subscriptions.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation mentions Azure PowerShell as a migration tool alongside Azure CLI and the Azure portal, but does not provide PowerShell-specific examples. Azure CLI is used throughout for command-line examples, which is cross-platform. However, Azure PowerShell is listed before Azure CLI in the migration section, and there are no Linux-specific notes or examples. The overall guidance is platform-neutral, but the ordering and mention of Windows tools (PowerShell) slightly favors Windows users.
Recommendations
- List Azure CLI before Azure PowerShell when describing migration options, as CLI is cross-platform and more commonly used on Linux/macOS.
- Clarify that Azure CLI commands work on Windows, Linux, and macOS.
- Consider adding a note that Azure PowerShell is primarily for Windows users, and recommend Azure CLI for Linux/macOS.
- If mentioning PowerShell, provide equivalent Bash or shell examples if relevant.
- Explicitly state that all steps can be performed from Linux/macOS environments.
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation provides both Azure CLI and PowerShell options for prerequisite cluster creation and subnet/resource group queries, but consistently mentions Azure PowerShell alongside Azure CLI and references PowerShell cmdlets before or equally with CLI commands. However, all main walkthroughs and examples use cross-platform tools (kubectl, Azure CLI), and no critical steps are Windows-only. The bias is minor and mostly in tool mentions, not in actual instructions.
Recommendations
- When listing options for cluster creation or resource queries, mention Azure CLI first, as it is cross-platform, and clarify that Azure PowerShell is Windows-centric.
- Where PowerShell cmdlets are referenced, provide equivalent Bash/Linux commands or clarify that Azure CLI is recommended for Linux/macOS users.
- Consider grouping Azure CLI and PowerShell instructions in separate tabs or sections to avoid implying PowerShell is equally relevant for all platforms.
- Review links and references to ensure Linux/macOS parity, and avoid listing PowerShell before CLI unless the feature is Windows-specific.
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
Powershell Heavy
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all Azure-related tasks, but PowerShell is featured equally and sometimes before Linux-native alternatives. There are no explicit Linux/macOS-specific instructions or examples (e.g., Bash scripting, Linux package installation), and PowerShell is presented as a primary option alongside Azure CLI, which may create friction for Linux/macOS users. However, the core Kubernetes and Helm steps use Bash commands, and the Azure CLI is cross-platform, so Linux/macOS users can complete all tasks.
Recommendations
- Clarify that Azure PowerShell is primarily for Windows users and Azure CLI is recommended for Linux/macOS.
- Explicitly note that Azure CLI commands work on Linux, macOS, and Windows, and PowerShell is optional.
- Consider showing Azure CLI examples first, as it is the cross-platform default.
- Add brief instructions for installing Azure CLI and Helm on Linux/macOS (with links).
- Mention that Bash commands are native to Linux/macOS and provide alternatives for Windows users if needed.
Aks
Stop and start an Azure Kubernetes Service (AKS) cluster
...-aks-docs/blob/main/articles/aks/start-stop-cluster.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for stopping and starting AKS clusters. However, the PowerShell examples are presented immediately after the CLI examples in each section, and the introductory 'Before you begin' section lists Azure CLI, Azure PowerShell, and Azure Portal as options for creating a cluster, with PowerShell mentioned before Portal. There are no Linux-specific examples or explicit mention of Linux/macOS compatibility for the CLI commands, but the Azure CLI is cross-platform and the examples are generic. No Windows-only tools or patterns are used, and Linux users can fully complete the tasks using the Azure CLI.
Recommendations
- Explicitly state that Azure CLI commands work on Linux, macOS, and Windows.
- Consider mentioning Linux/macOS compatibility in the 'Before you begin' section.
- If possible, add a note clarifying that PowerShell is primarily for Windows users, while Azure CLI is cross-platform.
- Ensure that CLI examples are shown first (as they are), and avoid implying PowerShell is required for Linux/macOS users.
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
Powershell Heavy
Summary
The documentation provides parity for both Linux and Windows node pools in AKS, but there is a slight bias in the ordering and example focus. Windows-specific instructions (such as registering feature flags and creating Windows admin credentials) are presented in detail and appear before Linux equivalents in some sections. All CLI examples use Azure CLI and Bash, which are cross-platform, but there are no PowerShell-specific examples. The documentation does not omit Linux examples and covers Linux node pools thoroughly, but Windows instructions are sometimes more prominent.
Recommendations
- Ensure Linux instructions and examples are presented before Windows-specific sections, especially in cluster creation and feature registration.
- Add explicit notes clarifying that Azure CLI and Bash commands work on Linux, macOS, and Windows (with WSL or Bash shell).
- Consider including PowerShell equivalents for Windows users, or clarify that Bash examples are recommended for cross-platform compatibility.
- Maintain parity in detail and structure between Linux and Windows sections.
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 First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for key operations (installing kubectl, listing available Kubernetes versions), but consistently presents Azure CLI (cross-platform) examples first, followed by Azure PowerShell (Windows-centric) examples. No Linux-specific tools or shell commands are missing, but there are no explicit bash or Linux/macOS shell examples. The documentation does not use Windows-only tools or patterns, nor does it omit Linux equivalents. The bias is minor and mostly in the ordering and inclusion of PowerShell examples.
Recommendations
- Add explicit bash/Linux/macOS shell examples where relevant, especially for commands that can be run in a Linux terminal.
- Clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Consider including a 'Bash' or 'Linux/macOS' tab for commands, or note that Azure CLI commands can be run in any shell.
- Ensure parity in example ordering (e.g., Azure CLI, Bash, then PowerShell) to reinforce cross-platform support.
Aks
Connect your Azure Kubernetes Service (AKS) cluster to AI agents using the Model Context Protocol (MCP) server
...main/articles/aks/aks-model-context-protocol-server.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation generally provides cross-platform instructions and download links for Windows, macOS, and Linux. However, there are minor Windows biases: Windows keyboard shortcuts are often listed first, and some tips (e.g., WSL configuration) are Windows-specific. There are no Linux/macOS-specific troubleshooting tips or examples, and some instructions (e.g., Docker credential issues) mention Windows limitations without offering equivalent Linux/macOS guidance. All CLI examples use bash syntax, which is standard for Linux/macOS but also works in Windows with WSL or PowerShell. Overall, parity is good, but Linux/macOS users may find minor friction due to Windows-first ordering and lack of platform-specific troubleshooting.
Recommendations
- Alternate keyboard shortcut ordering (sometimes list macOS/Linux first)
- Add Linux/macOS-specific troubleshooting tips, especially for Docker and credential management
- Include explicit PowerShell examples for Windows users, and bash examples for Linux/macOS users, where relevant
- Clarify any platform-specific limitations or requirements for all platforms, not just Windows
- Ensure download instructions and links are equally prominent for all platforms
Aks
Troubleshoot the Agentic CLI for Azure Kubernetes Service (AKS)
.../main/articles/aks/agentic-cli-for-aks-troubleshoot.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The troubleshooting documentation provides both Windows/macOS and Linux solutions for Docker-related issues, but Windows/macOS steps (using Docker Desktop) are consistently listed before Linux steps. Windows tooling (Docker Desktop) is referenced as the primary solution for Windows/macOS, while Linux-specific commands are provided separately. Azure CLI and kubectl commands are platform-neutral, but minor ordering bias exists.
Recommendations
- Alternate the order of Windows/macOS and Linux instructions to avoid implicit prioritization.
- Explicitly state that all steps apply equally to Linux, macOS, and Windows where possible.
- Provide parity in troubleshooting details, ensuring Linux instructions are as comprehensive as Windows/macOS.
- Consider grouping platform-specific instructions under clear subheadings (e.g., 'Linux', 'Windows/macOS') for clarity.
Aks
Certificate Rotation in Azure Kubernetes Service (AKS)
...ks-docs/blob/main/articles/aks/certificate-rotation.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation is generally cross-platform and AKS is a Linux-first service, but there are minor indications of Windows bias. In the section 'Verify TLS Bootstrapping is enabled on current agent node pool', the Windows file path ('C:\k\bootstrap-config') is mentioned immediately after the Linux path, and no additional Windows-specific commands or examples are provided elsewhere. However, most examples and instructions are Linux-centric (bash, Azure CLI, kubectl), and Windows is only referenced for file paths. There are no PowerShell examples or Windows-only tools used.
Recommendations
- Ensure that Windows file paths are not mentioned before Linux paths unless Windows is the primary target.
- Where Windows is referenced, consider providing equivalent PowerShell or Windows command-line examples for certificate inspection or rotation, if applicable.
- Clarify that most AKS clusters are Linux-based and that Windows node pools are a special case, linking to Windows node pool documentation for Windows-specific tasks.
- Add a brief note explaining that most commands are for Linux-based clusters, and Windows node pool users should refer to the Windows node pool documentation for any differences.
Aks
Integrate Azure Container Registry with Azure Kubernetes Service (AKS)
...articles/aks/cluster-container-registry-integration.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides parallel examples for both Azure CLI and Azure PowerShell throughout, but PowerShell is a Windows-centric tool and is featured equally alongside Azure CLI. There are no Linux-specific shell examples (e.g., Bash), and PowerShell is presented as a primary option despite its limited adoption on Linux/macOS. In some sections, PowerShell is listed after CLI, but overall, the parity is maintained between CLI and PowerShell, with no explicit Linux shell or tooling examples.
Recommendations
- Clarify that Azure CLI commands are cross-platform and preferred for Linux/macOS users.
- Add explicit Bash shell examples for setting environment variables and running Azure CLI commands (e.g., export MYACR=mycontainerregistry instead of MYACR=mycontainerregistry for Bash).
- Mention that PowerShell examples are primarily for Windows users, and recommend Azure CLI for Linux/macOS.
- Consider adding a section or note for Linux/macOS users, highlighting any differences or additional steps (such as file creation commands, environment variable syntax, etc.).
Aks
Concepts - Storage in Azure Kubernetes Services (AKS)
...re-aks-docs/blob/main/articles/aks/concepts-storage.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Example
Summary
The documentation is generally cross-platform and neutral, but there is a minor bias in the 'Persistent volume claims' section, where Windows container mounting instructions and YAML examples are presented immediately after Linux-style examples, without clear separation or parity. The Windows example is given, but no equivalent Linux example is provided for mounting multiple volumes. Additionally, the Windows-specific instructions are not clearly labeled as such, which could cause confusion for Linux/macOS users.
Recommendations
- Clearly label Windows-specific YAML examples and instructions as 'For Windows containers' and Linux-specific examples as 'For Linux containers'.
- Provide equivalent Linux examples for mounting multiple volumes, if applicable.
- Ensure that Windows and Linux instructions/examples are presented in parallel sections or tables, rather than Windows instructions being appended after Linux examples.
- Add clarifying notes when a feature or syntax is Windows-only, to avoid confusion.