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 351-375 of 618 flagged pages
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 throughout, but PowerShell is featured equally alongside CLI, which is more commonly used on Windows. There are no explicit Linux/macOS-specific instructions or examples, and the PowerShell sections may be less relevant for Linux/macOS users. Azure CLI is cross-platform, but the documentation does not clarify this or prioritize CLI examples. The use of PowerShell is not exclusive, but its presence may create confusion or friction for Linux/macOS users.
Recommendations
- Explicitly state that Azure CLI is cross-platform and recommended for Linux/macOS users.
- Consider presenting Azure CLI examples first, or labeling them as the default for non-Windows platforms.
- Add brief notes clarifying that PowerShell examples are primarily for Windows users.
- Include a short section or callout for Linux/macOS users, confirming that all steps can be completed with Azure CLI and bash.
- Ensure that any shell commands (e.g., git, helm, kubectl) are shown in bash syntax, and clarify compatibility.
Create Pull Request
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
Summary
The documentation covers both Linux and Windows scenarios for AKS network policies, but Windows-specific instructions and tools (such as Windows admin credentials setup and feature flag registration) are presented before or alongside Linux equivalents. Windows node pool creation steps are detailed separately and prominently, and Windows-specific limitations and features are discussed in depth. However, Linux examples and instructions are also present and complete, and the page is not Windows-exclusive.
Recommendations
- Ensure Linux instructions/examples are presented first in each section unless Windows is the primary focus.
- Clearly separate Linux and Windows instructions with headings for easier navigation.
- Add explicit notes when a command or step is Windows-only, and provide Linux equivalents where possible.
- Consider grouping Windows-specific steps (such as admin credential setup and feature flag registration) in a dedicated section to avoid interleaving with Linux steps.
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 signs of Windows bias. In the section 'Verify TLS Bootstrapping is enabled on current agent node pool', the Windows file path is mentioned immediately after the Linux path, but no explicit example is given for how to check on Windows. Additionally, throughout the document, all command-line examples use Azure CLI and bash/kubectl, which are Linux/macOS-friendly, but there are no PowerShell or Windows Command Prompt examples for Windows users. However, the document does not exclusively favor Windows tools or patterns, and Linux parity is mostly maintained.
Recommendations
- Provide explicit Windows command examples (e.g., PowerShell or Command Prompt) for checking certificate expiration and TLS Bootstrapping, especially when referencing Windows file paths.
- Clarify any differences in procedure for Windows node pools, if applicable.
- When mentioning file paths for both Linux and Windows, consider giving a brief example for each platform.
- Ensure that all steps that reference file paths or commands are clear for both Linux and Windows users.
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 cross-platform 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 platform-neutral (Azure CLI, Docker, kubectl), and Linux-specific guidance is present where relevant.
Recommendations
- In the 'Start the Docker daemon' section, present Linux instructions before or alongside Windows/macOS instructions, or clarify that all platforms are equally supported.
- Consider explicitly stating that all commands (Azure CLI, Docker, kubectl) work on Linux, macOS, and Windows, and provide links to platform-specific installation guides where relevant.
- If possible, add a brief note that Docker Desktop is not available on Linux, and that Linux users should use systemd/systemctl.
Aks
Troubleshoot the Agentic CLI for Azure Kubernetes Service (AKS)
...ob/main/articles/aks/cli-agent-for-aks-troubleshoot.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Missing
Minor Windows Tools
Summary
The documentation provides troubleshooting steps for the agentic CLI for AKS, with Docker-related issues addressed for macOS/Windows and Linux separately. Windows and macOS instructions are grouped together and presented before Linux in several places. There are no PowerShell-specific examples, but Windows users are directed to use Docker Desktop, a Windows/macOS-specific tool, while Linux users are given command-line instructions. All Azure CLI and Kubernetes commands are cross-platform. No critical troubleshooting steps are Windows-only, and Linux parity is generally maintained.
Recommendations
- Where possible, provide Linux instructions before or alongside Windows/macOS instructions, rather than after.
- Explicitly mention that Docker Desktop is not available for Linux and clarify alternatives for Linux users.
- Consider adding PowerShell examples for Windows users if Bash is not the default shell, or clarify that Bash commands work in Windows Terminal.
- Ensure that all troubleshooting steps are equally detailed for Linux, macOS, and Windows users.
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 platform-agnostic, focusing on Azure CLI and Bicep for managing the Dapr extension on AKS and Arc-enabled Kubernetes clusters. However, there is a minor Windows bias in the CRD deletion section, where the example for listing CRDs uses PowerShell's 'findstr' command with 'kubectl', which is Windows-specific. This command is shown without a Linux/macOS alternative (e.g., using 'grep'). Additionally, the PowerShell example is presented first and exclusively in that context.
Recommendations
- Provide Linux/macOS equivalents for commands that use Windows-specific tools (e.g., show 'kubectl get crds | grep dapr.io' alongside the PowerShell 'findstr' example).
- When giving shell command examples, consider presenting both Windows and Linux/macOS versions, or use cross-platform commands where possible.
- Explicitly state that the command works on Windows and provide alternatives for other platforms to improve accessibility.
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 three parallel approaches: Azure portal, Azure PowerShell, and Azure CLI. The PowerShell section is prominent and detailed, with explicit instructions for installation and usage across 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. There are no missing Linux examples, as Azure CLI is included and installation links for PowerShell on Linux/macOS are present. The ordering and emphasis on PowerShell may create minor friction for Linux/macOS users.
Recommendations
- Consider placing the Azure CLI section before the Azure PowerShell section, as CLI is more cross-platform and native to Linux/macOS.
- Explicitly mention that Azure CLI is recommended for Linux/macOS users.
- Add a short note clarifying that PowerShell is available cross-platform, but Azure CLI is often preferred on Linux/macOS.
- Ensure that all code blocks and instructions are equally clear for both CLI and PowerShell users.
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation provides both Azure CLI and PowerShell options for some prerequisite tasks, but consistently mentions Azure PowerShell alongside Azure CLI and portal as ways to create an AKS cluster. In the section on listing subnets, both Azure CLI and PowerShell are referenced, but PowerShell is mentioned after Azure CLI. No PowerShell-specific examples are shown for core AKS operations, which are all demonstrated with kubectl and Azure CLI. There are no Linux/macOS-specific examples or explicit parity notes, but the overall guidance is cross-platform, with only minor bias toward Windows tools.
Recommendations
- Clarify that Azure PowerShell is optional and primarily for Windows users; consider listing Azure CLI first in all cases.
- Add explicit notes that Azure CLI and kubectl commands work on Linux/macOS as well as Windows.
- Where PowerShell is mentioned, provide equivalent Bash or shell scripting examples for Linux/macOS users.
- Consider removing PowerShell references from core AKS workflow unless a Windows-specific scenario is being described.
Aks
Azure Kubernetes Service (AKS) Managed Gateway API Installation (preview)
...aks-docs/blob/main/articles/aks/managed-gateway-api.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation primarily uses Azure CLI examples, which are cross-platform, and includes kubectl commands that work on Linux/macOS/Windows. However, all CLI examples are shown in the Azure CLI interactive block, which may be perceived as Windows-first due to the historical association of Azure CLI with Windows/PowerShell. There are no PowerShell-specific commands or Windows-only tools mentioned, and Linux/macOS users can complete all tasks as described. The order of examples does not explicitly favor Windows, but there is a minor bias in not mentioning Linux/macOS usage or shell compatibility.
Recommendations
- Explicitly state that Azure CLI and kubectl commands are cross-platform and work on Linux/macOS/Windows.
- Add a note or section clarifying that all examples are compatible with Bash, Zsh, and other common Linux/macOS shells.
- Consider including example commands for Bash and PowerShell if there are any syntax differences.
- Mention that Azure CLI can be installed and used on Linux/macOS, linking to installation instructions.
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 consistently presents Azure CLI (Linux/macOS-friendly) first, followed by Azure PowerShell (Windows-centric). However, there is a slight bias in the troubleshooting section where PowerShell is given equal prominence, and no explicit Linux/macOS shell example (e.g., Bash) is provided for retrieving the public IP address. All other instructions are portal-based and platform-neutral.
Recommendations
- Add explicit Bash shell examples for Linux/macOS users to retrieve their public IP address (e.g., `curl ifconfig.me`).
- Clarify that Azure CLI commands work cross-platform and can be run in Bash, Zsh, or other shells.
- Consider mentioning that Azure PowerShell is primarily for Windows users, while Azure CLI is cross-platform.
- If possible, provide a table or clear separation of instructions for Windows, Linux, and macOS users.
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 tasks. However, Azure PowerShell (which is most commonly used on Windows) is given equal prominence to Azure CLI, and PowerShell examples are included throughout. There is a minor bias in that PowerShell is featured heavily, and the documentation sometimes lists PowerShell before Linux-native tools or patterns. No critical Linux/macOS friction is present, as Azure CLI is fully supported cross-platform and all tasks can be completed with CLI or portal.
Recommendations
- Consider listing Azure CLI examples before Azure PowerShell in each section, as CLI is cross-platform and more widely used on Linux/macOS.
- Explicitly note that Azure CLI is recommended for Linux/macOS users, and PowerShell is primarily for Windows users.
- Where possible, clarify that Azure PowerShell is available cross-platform, but is most commonly used on Windows.
- Ensure that all screenshots and output examples are not Windows-specific (e.g., avoid PowerShell console screenshots unless necessary).
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 consistently presents Azure CLI (which is cross-platform) before Azure PowerShell (which is Windows-centric). There are no explicit Windows-only tools or commands, and Linux/macOS users are not excluded from any steps. Bash commands are used for Helm and kubectl operations, which are cross-platform. However, the PowerShell examples are unnecessary for Linux/macOS users, and their inclusion may create minor friction or confusion.
Recommendations
- Clearly indicate that Azure PowerShell is primarily for Windows users, and Azure CLI is recommended for Linux/macOS.
- Consider grouping Azure CLI and PowerShell examples under separate headings, or use tabs labeled 'Windows' and 'Linux/macOS' to clarify relevance.
- Add a note at the top of the page stating that Azure CLI is cross-platform and preferred for Linux/macOS.
- Optionally, provide only Azure CLI examples in the main flow, with PowerShell examples in a separate section for Windows 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
Windows Tools
Summary
The documentation provides both Linux and Windows examples for AKS network policy engines, but Windows-specific instructions (such as administrator credential setup and feature flag registration) are given their own section and are presented immediately after the Linux section. Windows node pool creation steps are detailed, including Azure CLI commands and environment variable setup, while Linux steps are similar but less emphasized. The documentation mentions Windows-specific tools (HNS ACLPolicy) alongside Linux tools (IPTables), but does not prioritize Windows tools over Linux. All CLI examples use Azure CLI and Bash, which are cross-platform, but Bash is shown as the default shell for environment variable setup, which may not be native on Windows.
Recommendations
- Clarify that Bash commands are cross-platform and provide PowerShell equivalents for Windows users where relevant.
- Ensure Linux and Windows instructions are equally detailed and presented in parallel, rather than sequentially.
- Add explicit notes about how Windows users can run Bash commands (e.g., via WSL or Git Bash) or provide alternative PowerShell syntax.
- Consider a tabbed interface for Linux/Windows steps to improve clarity and parity.
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 Linux and Windows/macOS instructions for Docker daemon startup, but Windows/macOS instructions are listed first. All CLI examples use cross-platform Azure CLI and Bash commands, and there are no PowerShell or Windows-specific tools mentioned. The documentation is largely platform-neutral, but the ordering of instructions shows a minor Windows bias.
Recommendations
- List Linux instructions before Windows/macOS, or group all OS instructions together for Docker daemon startup.
- Explicitly mention that all Azure CLI and Bash commands are cross-platform and provide links to platform-specific installation guides if needed.
- Ensure parity in troubleshooting and cleanup verification steps by referencing both Linux and Windows/macOS file paths and commands where applicable.
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 instances of Windows bias. In the 'Verify TLS Bootstrapping is enabled on current agent node pool' section, the Windows file path is listed after the Linux path, but no command-line example is provided for Windows users (e.g., how to check the file exists). All command examples use Bash or Azure CLI, which are cross-platform, but there are no PowerShell or Windows CMD examples for Windows users. The documentation does not mention Windows tools or patterns exclusively, nor does it prioritize Windows-specific instructions over Linux ones.
Recommendations
- Add explicit Windows command-line examples (e.g., PowerShell or CMD) for checking file existence at 'C:\k\bootstrap-config'.
- Clarify that Azure CLI and kubectl commands work on Windows, and provide any necessary Windows-specific flags or considerations.
- Consider including a note or example for Windows users on how to decode base64 or use openssl if not installed.
- Ensure parity in troubleshooting steps for both Linux and Windows nodes where applicable.
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 parallel instructions for Azure portal, Azure PowerShell, and Azure CLI. However, the PowerShell section is notably detailed, with explicit instructions for installation and version checks, and is presented before the CLI section. The PowerShell instructions reference Windows tools and patterns, but do include links for macOS and Linux installation. The CLI section is less detailed and does not mention OS-specific considerations. There are no missing Linux examples, but the prominence and detail of PowerShell instructions may create a perception of Windows bias.
Recommendations
- Expand Azure CLI instructions to include OS-specific installation and troubleshooting links for Linux/macOS, similar to the PowerShell section.
- Ensure that CLI examples are as detailed as PowerShell examples, including version checks and environment preparation.
- Consider presenting CLI instructions before PowerShell, or at least in parallel, to avoid 'windows_first' bias.
- Add explicit notes that both PowerShell and CLI are fully cross-platform, and highlight Linux/macOS parity where relevant.
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 references Azure PowerShell and its cmdlets alongside Azure CLI. In the 'Before you begin' section, Azure PowerShell is mentioned as an option for creating an AKS cluster before Azure CLI and the Azure portal. Additionally, the PowerShell cmdlet 'Get-AzVirtualNetworkSubnetConfig' is referenced for listing subnets, but no Linux/macOS equivalent (such as Azure CLI or Bash) is shown alongside it. All main procedural examples use kubectl and Azure CLI, which are cross-platform, but the inclusion and ordering of PowerShell references may create minor friction for Linux/macOS users.
Recommendations
- When listing options for creating AKS clusters, mention Azure CLI first, as it is cross-platform, followed by Azure PowerShell for Windows users.
- For listing subnets, provide only Azure CLI examples or clearly indicate that PowerShell is Windows-specific and Azure CLI is recommended for Linux/macOS.
- If PowerShell is referenced, always provide an Azure CLI equivalent and note platform differences.
- Consider grouping Windows-specific tools in a separate section or appendix, rather than mixing them with cross-platform options.
Aks
Troubleshoot the Agentic CLI for Azure Kubernetes Service (AKS)
...ob/main/articles/aks/cli-agent-for-aks-troubleshoot.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides troubleshooting steps for the agentic CLI for AKS, but in several places, Windows/macOS solutions (e.g., 'Launch Docker Desktop') are mentioned before Linux equivalents. Some instructions for Docker issues are Windows/macOS-centric, and Linux-specific solutions are sometimes secondary. There are no PowerShell-specific commands, but Windows Desktop patterns are referenced. All Azure CLI and kubectl examples are cross-platform, but the ordering and phrasing show a mild Windows bias.
Recommendations
- Present Linux, macOS, and Windows solutions in parallel or grouped by OS, rather than listing Windows/macOS first.
- Clarify that Docker Desktop is not available on Linux and provide explicit Linux alternatives (e.g., systemd commands) before or alongside Windows/macOS instructions.
- Where possible, add notes for Linux-specific troubleshooting steps (e.g., checking Docker group membership, restarting Docker service).
- Ensure that examples and solutions are equally detailed for all platforms.
- Avoid phrases like 'On macOS/Windows' unless truly identical; separate instructions for each OS where they differ.
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 generally cross-platform and focuses on Azure CLI and Bicep, both of which are available on Windows, Linux, and macOS. 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 relies on the Windows 'findstr' command. No equivalent Linux/macOS example (e.g., using 'grep') is provided, and the PowerShell/Windows syntax is shown first and exclusively in this context.
Recommendations
- Provide Linux/macOS equivalent commands alongside Windows examples, such as 'kubectl get crds | grep dapr.io'.
- When showing shell commands, clarify which OS they apply to or use cross-platform syntax where possible.
- Consider listing both Windows and Linux/macOS command variants in troubleshooting or operational sections.
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
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for managing AKS authorized IP ranges. However, the PowerShell section is presented immediately after the Azure CLI section, and both are given equal prominence. No Linux-specific tools or commands (such as bash or Linux-native utilities) are mentioned, but the Azure CLI example uses 'dig', which is available on Linux/macOS by default. There are no Windows-only tools or patterns, and the documentation is generally neutral and portal-focused. The PowerShell example is not prioritized over the CLI, and Linux users can complete all tasks using the Azure CLI instructions.
Recommendations
- Explicitly note that Azure CLI commands are cross-platform and suitable for Linux/macOS users.
- Consider adding a brief note or section clarifying that PowerShell examples are primarily for Windows users, while Azure CLI is recommended for Linux/macOS.
- If possible, add a bash-only example for retrieving the public IP address (e.g., using 'curl' or 'wget') for Linux/macOS users who may not have 'dig' installed.
- Ensure that any future troubleshooting steps or examples do not default to Windows tools unless necessary.
Aks
Configure LocalDNS in Azure Kubernetes Service (AKS)
...ure-aks-docs/blob/main/articles/aks/localdns-custom.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides links to AKS cluster creation guides for Azure CLI, Azure PowerShell, and Azure Portal, listing PowerShell before Portal. However, all configuration, verification, and troubleshooting steps use cross-platform tools (Azure CLI, kubectl, YAML), and the feature itself is only supported on Azure Linux or Ubuntu node pools. No Windows-specific tools, patterns, or examples are given, and Linux parity is strong throughout.
Recommendations
- Consider listing Azure CLI and Portal before PowerShell in the prerequisites to reinforce Linux/macOS parity.
- Explicitly note that all commands are cross-platform and can be run from Linux, macOS, or Windows environments.
- Optionally, provide a brief note that PowerShell is primarily for Windows users, while Azure CLI is recommended for all platforms.
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 tasks. However, Azure PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and PowerShell examples are included throughout. Azure CLI is cross-platform, but PowerShell is primarily used on Windows, and its inclusion may create friction for Linux/macOS users. In some sections, PowerShell is listed before Azure portal, but not before Azure CLI. No Windows-specific tools or patterns are mentioned, and Linux/macOS users can complete all tasks using Azure CLI or portal. There are no missing Linux examples, and the documentation does not favor Windows tools exclusively.
Recommendations
- Clarify that Azure CLI is fully cross-platform and recommended for Linux/macOS users.
- Consider moving Azure PowerShell examples after Azure CLI and Azure portal, or explicitly note PowerShell is primarily for Windows users.
- Add a brief note at the start indicating Azure CLI is the preferred tool for non-Windows environments.
- Ensure all references to PowerShell are accompanied by Azure CLI equivalents (already done here).
Aks
Secure Container Access to Resources in Azure Kubernetes Service (AKS)
...docs/blob/main/articles/aks/secure-container-access.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page is focused on Linux security features for AKS containers, with all technical examples, commands, and walkthroughs targeting Linux environments. However, in several prerequisite sections, Windows tools (Azure PowerShell) are mentioned alongside Azure CLI and Portal, and are listed before Linux equivalents. No PowerShell-specific examples or Windows-only tools are used, and all technical steps are Linux-centric. There are no missing Linux examples, nor are Windows tools used exclusively.
Recommendations
- In prerequisite lists, consider listing Azure CLI (cross-platform) before Azure PowerShell, or clarifying that PowerShell is primarily for Windows users.
- Where possible, provide parity in introductory guidance for Linux/macOS users (e.g., highlight Azure CLI as the default for cross-platform scenarios).
- Explicitly state that all technical steps and examples are Linux-only, and clarify that Windows node pools are not supported for these features.
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 three main approaches: Azure portal, Azure PowerShell, and Azure CLI. Azure PowerShell is featured prominently, with detailed instructions and prerequisites, including references to Windows, macOS, and Linux installation. However, PowerShell is a Windows-centric tool, and its section appears before the Azure CLI, which is more cross-platform and native to Linux/macOS. The PowerShell section is more verbose and detailed compared to the CLI section. There are no missing Linux examples, as Azure CLI is included, but the ordering and emphasis favor Windows/PowerShell.
Recommendations
- Present Azure CLI instructions before Azure PowerShell, as CLI is more universally supported across platforms.
- Ensure parity in detail between PowerShell and CLI sections; expand CLI instructions if needed.
- Explicitly mention that Azure CLI is recommended for Linux/macOS users.
- Consider adding a note clarifying that PowerShell is available on Linux/macOS, but Azure CLI is the default for those platforms.
Aks
Configure LocalDNS in Azure Kubernetes Service (AKS)
...ure-aks-docs/blob/main/articles/aks/localdns-custom.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides links to AKS cluster creation guides for Azure CLI, PowerShell, and Portal, with PowerShell (a Windows-centric tool) mentioned alongside CLI and Portal. However, all actual configuration, verification, and troubleshooting examples use Azure CLI and kubectl, which are cross-platform tools. There are no PowerShell-specific commands or Windows-only tools used in the main instructions. The documentation explicitly states LocalDNS is only supported on Azure Linux or Ubuntu node pools, not Windows, and does not present Windows-specific patterns or tools.
Recommendations
- When referencing AKS creation guides, list Azure CLI and Portal before PowerShell, or clarify PowerShell is Windows-specific.
- Consider adding a note that Azure CLI and kubectl are fully supported on Linux/macOS, and that PowerShell is optional for Windows users.
- Ensure all example commands are cross-platform (which they currently are).