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 301-325 of 618 flagged pages
Aks
Kubernetes on Azure tutorial - Upgrade an Azure Kubernetes Service (AKS) cluster
...in/articles/aks/tutorial-kubernetes-upgrade-cluster.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides parity between Azure CLI, Azure PowerShell, and Azure portal for all AKS upgrade operations. However, Azure PowerShell examples are included throughout, which is primarily a Windows tool, and in some sections, PowerShell is listed before Azure CLI. There are no Linux-specific shell examples (e.g., Bash), but Azure CLI is cross-platform and is presented as the main tool. No Windows-only tools or patterns are used, and Linux users can complete all tasks using Azure CLI or portal.
Recommendations
- Ensure Azure CLI examples are always presented first, as it is cross-platform and preferred for Linux/macOS users.
- Clarify that Azure PowerShell is primarily for Windows users, and recommend Azure CLI for Linux/macOS.
- Consider adding Bash shell examples for common tasks (e.g., scripting upgrades, validating output) to further improve Linux parity.
- Explicitly state that Azure CLI works on Linux/macOS/Windows, while Azure PowerShell is Windows-centric.
- Add a note for Linux/macOS users that Azure CLI is the recommended tool for command-line operations.
Create Pull Request
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. The PowerShell section is prominent and detailed, with installation/upgrade instructions for Windows, macOS, and Linux. However, PowerShell is a Windows-centric tool, and its section appears before the Azure CLI, which is more native to Linux/macOS users. The CLI section is present and functional, but the ordering and emphasis on PowerShell may create friction for Linux/macOS users.
Recommendations
- Present Azure CLI examples before Azure PowerShell, as CLI is more cross-platform and native for Linux/macOS users.
- Explicitly mention that both Azure CLI and PowerShell are fully supported on Linux/macOS, and link to installation instructions for both.
- Consider adding Bash shell examples where relevant, or clarify that Azure CLI commands work in Bash, Zsh, etc.
- Balance the detail level between PowerShell and CLI sections to avoid implying PowerShell is preferred.
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 cluster authorized IP ranges, but consistently presents Azure CLI (Linux/macOS-friendly) examples first. However, the PowerShell section is equally detailed and not prioritized over Linux tools. No Windows-specific tools, patterns, or PowerShell-only instructions are present elsewhere. The documentation is largely platform-neutral, focusing on portal-based workflows and Azure CLI, with PowerShell as an alternative.
Recommendations
- Maintain Azure CLI examples as the primary cross-platform option, as currently done.
- Consider explicitly stating that Azure CLI works on Windows, Linux, and macOS, and that PowerShell is an alternative for Windows users.
- If possible, add a note clarifying that all portal and Azure CLI instructions are OS-agnostic.
- Ensure that any future troubleshooting or command-line sections continue to offer both CLI and PowerShell options, with CLI shown first.
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 Windows-specific guidance appears after the Linux example. There are no PowerShell-heavy examples, Windows tools, or missing Linux examples. The only evidence of bias is that Windows container mounting instructions are presented after Linux, which is a minor ordering preference.
Recommendations
- Consider presenting Linux and Windows container volume mounting examples side-by-side or with equal prominence.
- Explicitly clarify when instructions apply to Linux, Windows, or both, to improve clarity for cross-platform users.
- Ensure all YAML and CLI examples are provided for both Linux and Windows scenarios where relevant.
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 both Windows/macOS and Linux instructions for Docker daemon startup, but lists Windows/macOS instructions before Linux. All CLI examples use cross-platform Azure CLI and Bash commands, and there are no PowerShell-specific or Windows-only tools mentioned. The documentation is generally neutral, but the ordering of instructions for Docker startup shows a minor 'windows_first' bias.
Recommendations
- Present Linux instructions before or alongside Windows/macOS instructions, especially for Docker daemon startup.
- Explicitly state that all CLI examples work on Linux, macOS, and Windows.
- Where possible, use OS-neutral language and avoid implying Windows/macOS as the default environment.
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
Windows Tools
Summary
The documentation provides examples and instructions for both Linux and Windows environments, but in some sections, Windows paths are mentioned alongside Linux paths (e.g., in the TLS Bootstrapping section), and Windows nodes are referenced in example output. However, the majority of commands and examples are cross-platform (Azure CLI, kubectl, openssl, curl), and Linux paths are generally shown first. There is minor bias in mentioning Windows paths and node names in output examples, but no critical Windows-only instructions or tools are used.
Recommendations
- Ensure Linux and Windows examples are presented with equal prominence, ideally listing Linux instructions first if Linux is the default AKS node type.
- Where output examples reference Windows node names (e.g., 'akswinp7000000'), add Linux node name examples for parity.
- Clarify that Azure CLI and kubectl commands are cross-platform and provide any OS-specific caveats if needed.
- For file paths, always show both Linux and Windows variants together, and note which applies to which node type.
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
Powershell Missing
Windows Tools
Summary
The documentation provides troubleshooting steps for the Agentic CLI for AKS and covers both Windows/macOS and Linux environments. However, there is a mild bias: Windows/macOS solutions (e.g., 'Launch Docker Desktop') are listed before Linux solutions, and Windows tooling (Docker Desktop) is mentioned without referencing Linux alternatives (such as dockerd or systemd management). There are no PowerShell examples, but Windows users are expected to use Docker Desktop, which is a Windows/macOS-specific tool. All CLI commands are cross-platform, and Linux-specific commands are included, so Linux users can complete all tasks.
Recommendations
- Present Linux and Windows/macOS troubleshooting steps in parallel or with equal prominence.
- Mention Linux-native Docker management tools (dockerd, systemctl) alongside Docker Desktop.
- Add explicit notes about differences in Docker installation and management between platforms.
- Consider including Linux-first examples where appropriate, or alternate the order.
- Clarify that Docker Desktop is not available on Linux and provide links to Linux Docker installation guides.
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation provides both Azure CLI and PowerShell options for some prerequisite steps, but the PowerShell tool is mentioned alongside Azure CLI and portal as a way to create an AKS cluster. Additionally, the PowerShell cmdlet 'Get-AzVirtualNetworkSubnetConfig' is referenced for listing subnets, but no Linux/macOS equivalent (such as Azure CLI or Bash) is shown in that context. Azure CLI is used for most examples, which is cross-platform, but PowerShell is referenced without clear parity for Linux users in those sections.
Recommendations
- When listing ways to create an AKS cluster, mention Azure CLI and portal first, and clarify that PowerShell is primarily for Windows users.
- For subnet listing, provide Azure CLI examples before or alongside PowerShell, and clarify that Azure CLI works on Linux/macOS.
- Where PowerShell is referenced, always provide the Azure CLI equivalent and note its cross-platform compatibility.
- Consider removing PowerShell-only references unless the feature is Windows-specific, or add a note about platform compatibility.
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 parallel Azure CLI and Azure PowerShell examples for all Azure-related tasks, but consistently includes Azure PowerShell (a Windows-centric tool) as a primary option alongside Azure CLI. Azure PowerShell examples are given equal prominence, and in some sections, PowerShell is mentioned before Linux-native alternatives. However, all core Kubernetes and Helm commands use cross-platform bash examples, and there are no Windows-only tools or patterns used for the main Helm/AKS workflow.
Recommendations
- Consider clarifying that Azure PowerShell is primarily for Windows users, and Azure CLI is cross-platform (Linux, macOS, Windows).
- Where possible, show Azure CLI examples first, as it is the default for Linux/macOS users.
- Add brief notes indicating that Azure PowerShell is not available natively on most Linux distributions, and recommend Azure CLI for Linux/macOS users.
- Ensure that bash commands and Helm/Kubectl instructions are always shown as the default, with PowerShell as an optional alternative for 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 First
Windows Tools
Summary
The documentation provides examples for Azure CLI and Azure PowerShell, with PowerShell (a Windows-centric tool) given equal prominence to Azure CLI. In some sections, Windows-specific tools and OS versions are mentioned alongside Linux equivalents, but there is no clear bias toward Windows-only tools or patterns. No Linux/macOS-specific CLI examples (such as Bash or shell scripting) are provided, but Azure CLI is cross-platform. Windows and Linux OS components are listed together in breaking changes tables, and Windows is not prioritized over Linux in descriptions.
Recommendations
- Add explicit Bash or shell examples for Linux/macOS users where Azure CLI is used, clarifying cross-platform compatibility.
- Consider mentioning that Azure CLI works on Linux/macOS and Windows, and provide links to installation instructions for all platforms.
- If referencing PowerShell, clarify its availability on Linux/macOS and link to cross-platform installation guides.
- Ensure that any OS-specific instructions or examples are grouped or labeled by platform, so Linux/macOS users can easily find relevant information.
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 Linux-focused, but there is a minor bias in the 'Verify TLS Bootstrapping is enabled on current agent node pool' section, where Windows file paths are mentioned alongside Linux paths, but the Windows path is listed second. There are no PowerShell-specific examples, and all command-line instructions use Azure CLI and Bash, which are cross-platform and primarily Linux-oriented. However, there is a lack of explicit Windows command examples (e.g., PowerShell or CMD) for users who may be operating AKS clusters with Windows agent nodes.
Recommendations
- Add explicit Windows command examples (e.g., PowerShell or CMD) for relevant operations, especially where file paths or certificate checks are mentioned for Windows nodes.
- Ensure parity in troubleshooting and verification steps for both Linux and Windows node pools, including examples of how to access and verify certificates on Windows nodes.
- Consider listing Windows and Linux examples side-by-side in sections where both are relevant, rather than only mentioning file paths.
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-related operations, but consistently presents Azure CLI (Linux/macOS-friendly) examples first, followed by Azure PowerShell (Windows-centric) examples. There are no Windows-only tools or commands used, and all shell commands (git, helm, kubectl) are shown in bash syntax, which is cross-platform. However, the presence of Azure PowerShell throughout may suggest a slight Windows bias, but Linux parity is maintained.
Recommendations
- Continue to present Azure CLI examples first, as this is the most cross-platform approach.
- Consider clarifying that Azure PowerShell is available on Linux/macOS as well, to avoid the perception that it is Windows-only.
- Ensure that all bash commands are explicitly noted as compatible with Linux/macOS/Windows (via WSL or Git Bash).
- Optionally, add a brief note at the start indicating that all steps can be performed on Linux, macOS, or Windows.
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 tasks (such as installing kubectl and listing AKS versions), but consistently presents Azure CLI (cross-platform) examples first, followed by Azure PowerShell (Windows-centric) examples. No Linux-specific commands or tools are mentioned, but Azure CLI is inherently cross-platform. There are no Windows-only tools or patterns prioritized, and Linux support is clearly referenced in component tables. No critical tasks are Windows-only, and Linux users can complete all tasks using Azure CLI.
Recommendations
- Explicitly mention that Azure CLI is cross-platform and recommended for Linux/macOS users.
- Add a note clarifying that Azure PowerShell is primarily for Windows users.
- Consider including example commands for Bash or shell scripting where relevant.
- Where possible, add explicit Linux/macOS instructions or highlight parity.
- Ensure that any references to Azure CLI or PowerShell are accompanied by a statement about platform compatibility.
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 parity for Linux, macOS, and Windows users in most sections. However, in the Docker daemon startup instructions, Windows/macOS steps (Docker Desktop) are mentioned before Linux steps (systemctl), which is a minor 'windows_first' bias. All CLI examples and tool references are cross-platform, and Linux-specific instructions are present where relevant.
Recommendations
- Consider listing Linux instructions before or alongside Windows/macOS steps in Docker daemon startup guidance to avoid implicit prioritization.
- Explicitly mention that all Azure CLI and Docker commands are cross-platform, and provide links to Linux-specific installation guides where possible.
- Ensure that troubleshooting and cleanup verification steps include Linux, macOS, and Windows variations equally.
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 provides platform-specific instructions and download links for Windows, macOS, and Linux, and generally covers all major OSes. However, Windows is often mentioned first in lists and keyboard shortcut instructions, and some tips (such as WSL configuration) are Windows-specific. There are no Linux/macOS-specific troubleshooting tips or examples, and Docker instructions reference Windows-specific credential issues without providing equivalent Linux/macOS guidance. Linux is not omitted, but parity in troubleshooting and tips could be improved.
Recommendations
- Alternate the order of platform mentions (e.g., sometimes list Linux/macOS before Windows).
- Provide Linux/macOS-specific troubleshooting tips, especially for Docker credential management and VS Code integration.
- Add explicit Linux/macOS instructions for common issues (e.g., how to check Azure credentials, kubeconfig paths, and permission troubleshooting).
- Include Linux/macOS-specific keyboard shortcuts and configuration tips alongside Windows/WSL guidance.
- Ensure that Docker credential instructions are clear for Linux/macOS users, not just Windows.
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
Powershell Missing
Linux Parity Good
Summary
The documentation provides troubleshooting steps for the Agentic CLI for AKS with clear differentiation between Windows/macOS and Linux environments. Windows/macOS instructions (Docker Desktop) are listed before Linux instructions (systemd), but Linux-specific commands are included and explained. No PowerShell examples are given, and all CLI commands are cross-platform (bash and Azure CLI). There is minor bias in listing Windows/macOS steps first, but Linux users are not blocked or disadvantaged.
Recommendations
- Consider listing Linux instructions before or alongside Windows/macOS steps to avoid implicit prioritization.
- Explicitly mention that Azure CLI commands are cross-platform and can be run on Linux, macOS, or Windows.
- Add PowerShell examples for Windows users if relevant, or clarify that bash/Azure CLI commands are preferred.
- Where possible, clarify any OS-specific nuances (e.g., Docker group membership is not needed on Windows/macOS).
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. The PowerShell section is prominent and includes detailed instructions, but it does mention installation and usage on macOS and Linux. However, PowerShell is a Windows-centric tool, and its section appears before the Azure CLI, which is more native to Linux/macOS. There are no Linux-specific shell examples (e.g., Bash), and the CLI section is less detailed.
Recommendations
- Provide Bash shell examples for Linux users alongside PowerShell examples.
- Move Azure CLI examples before PowerShell, as CLI is more cross-platform and native to Linux/macOS.
- Clarify that PowerShell instructions are equally applicable on Linux/macOS, or highlight CLI as the preferred method for Linux/macOS users.
- Add explicit notes or tabs for Linux/macOS workflows, such as using Bash or Zsh.
- Ensure parity in detail between PowerShell and CLI sections.
Aks
Install the Dapr extension for Azure Kubernetes Service (AKS) and Arc-enabled Kubernetes
...softDocs/azure-aks-docs/blob/main/articles/aks/dapr.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation is largely cross-platform, focusing on Azure CLI and Bicep for installing the Dapr extension on AKS and Arc-enabled Kubernetes clusters. However, there is a minor Windows bias in the 'Listing the CRDs in your cluster' section, where the example uses 'kubectl get crds | findstr dapr.io', which is a Windows/PowerShell pattern. No Linux/macOS equivalent (e.g., using 'grep') is provided. Additionally, the use of Azure CLI throughout is platform-neutral, but the CLI examples and instructions are shown first, which may slightly favor Windows users if they are assumed to use CLI more often.
Recommendations
- Provide Linux/macOS equivalent commands for listing CRDs, such as 'kubectl get crds | grep dapr.io'.
- Explicitly mention that Azure CLI is cross-platform and link to installation instructions for Linux/macOS.
- Where shell commands are shown, offer both Windows (findstr) and Linux/macOS (grep) examples side by side.
- Review other sections for similar shell command patterns and ensure parity.
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation provides both Azure CLI and PowerShell options for prerequisite steps, but consistently mentions Azure PowerShell alongside Azure CLI and portal as ways to create an AKS cluster. It also references the PowerShell cmdlet Get-AzVirtualNetworkSubnetConfig as an alternative to the Azure CLI for listing subnets. However, all actual walkthroughs and code examples use cross-platform tools (kubectl, Azure CLI), and there are no PowerShell-specific examples for the main task. The mention of PowerShell is always as an alternative, but it is listed alongside CLI and portal, rather than after Linux/macOS-friendly options.
Recommendations
- List Azure CLI as the primary recommended tool for Linux/macOS parity, and mention PowerShell as an alternative for Windows users only.
- Where PowerShell is referenced, clarify that it is for Windows users, and provide equivalent Azure CLI commands first.
- Consider removing PowerShell references from prerequisite steps unless there is a Windows-specific workflow.
- Ensure all main task examples use cross-platform tools (kubectl, Azure CLI), as currently done.
Aks
Kubernetes on Azure tutorial - Create an Azure Kubernetes Service (AKS) cluster
...ain/articles/aks/tutorial-kubernetes-deploy-cluster.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides parallel instructions for Azure CLI, Azure PowerShell, and Azure Developer CLI. However, Azure PowerShell is featured equally alongside Azure CLI, which is more commonly used on Linux/macOS. PowerShell is primarily a Windows-centric tool, and its inclusion may suggest Windows bias. Additionally, PowerShell examples are given equal prominence, and in some sections, PowerShell is mentioned before Azure CLI, which could be perceived as 'windows_first'. No Linux-specific examples, shell patterns, or explicit Linux/macOS guidance are provided, but the Azure CLI instructions are cross-platform.
Recommendations
- Clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Consider adding explicit Bash shell examples or notes for Linux/macOS users, especially for environment variable usage and SSH key management.
- Reorder sections to consistently present Azure CLI instructions before PowerShell, as CLI is more universal.
- Add a brief note explaining that PowerShell is primarily for Windows users, while Azure CLI works on all platforms.
Aks
Install and Use the Agentic CLI for Azure Kubernetes Service (AKS) (Preview)
...cs/blob/main/articles/aks/cli-agent-for-aks-install.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Windows/macOS and Linux instructions for Docker daemon startup, but presents Windows/macOS steps first. All CLI examples use Azure CLI, which is cross-platform, and shell commands are shown in Bash, suitable for Linux/macOS. No PowerShell or Windows-specific tools are referenced, and Linux parity is generally maintained.
Recommendations
- Present Linux instructions before Windows/macOS in Docker daemon startup steps, or group them equally.
- Explicitly mention that all Azure CLI commands work on Linux, macOS, and Windows.
- Consider adding a note that Bash commands are applicable to Linux/macOS, and Windows users may use WSL or Docker Desktop terminal.
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 troubleshooting, but PowerShell examples are presented immediately after CLI and are given equal prominence. There is no explicit Linux/macOS bias, but the PowerShell section may be unnecessary for Linux/macOS users. The rest of the documentation is portal-centric and platform-agnostic, with all YAML examples targeting Linux node pools. No Windows-specific tools or patterns are mentioned outside the PowerShell section.
Recommendations
- Clearly indicate that Azure PowerShell examples are for Windows users, and Azure CLI examples are cross-platform.
- Consider presenting Azure CLI examples first, and PowerShell examples in a separate, clearly labeled section for Windows users.
- Add a note clarifying that Azure CLI commands work on Linux, macOS, and Windows, while PowerShell is Windows-centric.
- If possible, provide Bash alternatives for retrieving the public IP address, or clarify that the CLI example works on Linux/macOS.
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 (such as installing kubectl and listing AKS versions), but consistently presents Azure CLI (cross-platform) examples first, followed by Azure PowerShell (Windows-centric) examples. No Linux-specific commands or tools are mentioned, but Azure CLI is inherently cross-platform. There are no Windows-only tools or patterns, and Linux is referenced equally in component tables. No critical tasks are Windows-only.
Recommendations
- Explicitly mention that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Consider adding a brief note or example for Linux/macOS users (e.g., installation of Azure CLI or kubectl via package managers like apt, brew, or curl).
- Where PowerShell is referenced, clarify its Windows focus and suggest Azure CLI for Linux/macOS.
- Add links or references to Linux/macOS installation guides for Azure CLI and kubectl.
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. While both PowerShell and CLI are cross-platform, the PowerShell section is notably detailed and references Windows tools and patterns (such as PowerShell cmdlets and Cloud Shell), and is presented before the Azure CLI section. The PowerShell section includes explicit instructions for Windows, macOS, and Linux installation, but the CLI section is less prominent. There is a slight bias toward Windows/PowerShell usage, but Linux/macOS users can complete all tasks using Azure CLI or PowerShell.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is more universally used across platforms.
- Expand Azure CLI instructions to match the detail provided in the PowerShell section, including environment setup and prerequisites for Linux/macOS.
- Explicitly mention that both PowerShell and CLI are fully supported on Linux/macOS, and provide links to installation guides for each platform.
- Consider adding Bash shell examples or highlighting CLI usage in Linux/macOS contexts.
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 a single example of a Windows file path for verifying TLS Bootstrapping ('C:\k\bootstrap-config'), while the Linux equivalent is also mentioned but not shown first. All other examples and commands are either cross-platform (Azure CLI, kubectl, bash, curl) or explicitly reference Linux file paths. There are no PowerShell-specific commands, Windows tools, or Windows-only patterns used. The Windows path is mentioned after the Linux path, but no Linux-specific troubleshooting or parity notes are provided.
Recommendations
- Ensure Linux and Windows examples are presented with equal prominence, ideally side-by-side or with clear parity.
- Add explicit notes or troubleshooting steps for Linux users where file paths or behaviors may differ.
- Where file paths are given, clarify any differences in permissions, access, or tooling between Linux and Windows nodes.
- Consider adding a brief section on accessing Linux agent nodes for certificate checks, as is done for Windows nodes.