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 176-200 of 618 flagged pages
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 documentation provides troubleshooting steps for the agentic CLI for AKS with both Windows/macOS and Linux instructions. However, in several sections, Windows/macOS solutions (e.g., launching Docker Desktop) are mentioned before Linux equivalents, and Windows-specific tools like Docker Desktop are referenced. Linux instructions are present and generally complete, but Windows/macOS steps are often listed first, which may create minor friction for Linux users.
Recommendations
- Present Linux instructions before or alongside Windows/macOS steps, especially in Docker troubleshooting sections.
- Explicitly mention parity between platforms where applicable (e.g., clarify that Docker Desktop is not available on Linux and provide alternative Linux-specific troubleshooting tips).
- Ensure that all CLI examples (az, kubectl) are platform-neutral and clarify any OS-specific prerequisites.
- Consider grouping troubleshooting steps by OS, or using tabs to allow users to select their platform.
Create Pull Request
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 is generally neutral and covers storage concepts for AKS without favoring Windows-specific tools or patterns. However, in the section on mounting volumes in pods, Windows container examples are presented immediately after Linux-style examples, with a brief note on specifying drive letters and paths for Windows. There are no PowerShell-heavy examples, Windows tools, or missing Linux examples. The only minor bias is that Windows mounting syntax is shown directly after the Linux example, but this is not significant.
Recommendations
- Ensure that Linux/macOS examples are always presented first unless the section is explicitly Windows-specific.
- Consider clarifying in the mounting section that the Linux-style path is the default for most AKS clusters, and Windows mounting is only relevant for Windows node pools.
- Add a brief note or link to documentation about Linux/macOS volume mounting for completeness, if not already present.
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 is minor evidence of Windows bias. In the section 'Verify TLS Bootstrapping is enabled on current agent node pool', the Windows file path is mentioned alongside the Linux path, but the Linux path is listed first. However, in the example output for certificate signing requests (CSRs), Windows node names (e.g., 'akswinp7000000') are used, but there is no explicit Linux node example. All command-line examples use Azure CLI and bash, which are cross-platform, but the documentation does not provide PowerShell or Windows-specific CLI examples, nor does it mention Windows tools preferentially.
Recommendations
- Add explicit Linux node examples in output sections, especially where Windows node names are shown.
- Ensure that when referencing file paths or node names, both Linux and Windows examples are provided for parity.
- Consider adding notes or examples for Windows users where relevant, such as PowerShell equivalents for Azure CLI commands, if applicable.
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
Windows Tools
Summary
The documentation is generally cross-platform, focusing on Kubernetes and Azure Files usage for both Linux and Windows containers. However, there are minor signs of Windows bias: Windows path conventions and PowerShell/CMD syntax are mentioned in some places before Linux equivalents, and Azure CLI examples (which are cross-platform but often associated with Windows environments) are used exclusively for Azure resource creation. The documentation does not provide explicit Linux shell alternatives for Azure resource setup, but all Kubernetes examples and mount options are Linux-centric by default, with Windows-specific notes added where relevant.
Recommendations
- Where Windows path conventions are mentioned, ensure Linux path conventions are equally prominent and shown first if the majority of AKS users are on Linux.
- For Azure resource creation, clarify that Azure CLI is cross-platform and works on Linux/macOS as well as Windows.
- When showing commands that differ between platforms (e.g., file paths, kubectl exec syntax), provide both Linux and Windows variants side by side.
- Consider adding a brief section or note about using Azure CLI on Linux/macOS, including installation links.
- Review the order of examples and notes to ensure Linux is not consistently secondary to Windows.
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 the PowerShell section is prominent and detailed, it does include instructions for installing/upgrading PowerShell 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 users. The CLI section is present and provides parity, but the ordering and emphasis on PowerShell may create friction for Linux/macOS users.
Recommendations
- Consider placing Azure CLI examples before PowerShell examples, as CLI is more universal across platforms.
- Explicitly note that Azure CLI is recommended for Linux/macOS users, while PowerShell is an option for those who prefer it.
- Ensure that all PowerShell instructions referencing local installation or usage clearly indicate cross-platform support.
- Add brief notes or links about running Azure CLI in Cloud Shell for Linux/macOS users.
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 references Azure PowerShell as a tool for moving resources, alongside Azure CLI and Azure Portal. Azure PowerShell is a Windows-centric tool, and its mention is placed before Azure CLI in the list of migration options. However, all command-line examples provided use Azure CLI and Bash, which are cross-platform and Linux-friendly. No PowerShell-specific commands or Windows-only instructions are present.
Recommendations
- List Azure CLI before Azure PowerShell in migration tool options, as Azure CLI is more universally supported across platforms.
- Clarify that Azure PowerShell is available on Linux/macOS as well, or link to cross-platform installation instructions.
- Consider removing Azure PowerShell from the main flow unless a PowerShell-specific example is provided, or add equivalent Linux/macOS instructions if PowerShell is used.
- Explicitly state that all provided CLI examples work on Linux, macOS, and Windows.
Aks
Install Dapr Extension for Azure Kubernetes Service (AKS)
...softDocs/azure-aks-docs/blob/main/articles/aks/dapr.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows Tools
Summary
The documentation is generally cross-platform, using Azure CLI and Bicep (both cross-platform tools) for all installation and management steps. However, in the 'List the CRDs in your cluster' section, the example uses 'kubectl get crds | findstr dapr.io', which relies on the Windows-specific 'findstr' command. No Linux/macOS equivalent (e.g., using 'grep') is provided. This is a minor bias, as most of the guide is platform-agnostic, but this step could cause confusion or friction for Linux/macOS users.
Recommendations
- Provide both Windows and Linux/macOS examples for shell commands involving OS-specific utilities. For example, add 'kubectl get crds | grep dapr.io' alongside the existing 'findstr' example.
- Where possible, prefer cross-platform commands or explicitly note platform differences.
- Review for other minor shell command examples that may assume a Windows environment 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 cluster creation and subnet listing, but references to PowerShell (Get-AzVirtualNetworkSubnetConfig) are given alongside Azure CLI without Linux-specific alternatives. Azure PowerShell is mentioned as a tool for cluster creation before the Azure portal, and PowerShell cmdlets are referenced for subnet listing. However, all actual walkthroughs and examples use kubectl and Azure CLI, which are cross-platform. No critical steps are Windows-only, but minor bias exists in tool mentions.
Recommendations
- Clarify that Azure PowerShell is Windows-centric and recommend Azure CLI as the primary cross-platform tool.
- List Azure CLI before Azure PowerShell in prerequisite sections.
- Where PowerShell cmdlets are mentioned, provide equivalent Azure CLI commands or note that Azure CLI is preferred for Linux/macOS users.
- Explicitly state that all kubectl and Azure CLI commands work on Linux/macOS/Windows.
- Consider removing PowerShell references from sections not requiring Windows-specific functionality.
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 API server authorized IP ranges, but the PowerShell section is given equal prominence and appears directly after the CLI example. There are no Linux/macOS-specific examples or explicit mentions of Linux tools (e.g., bash, curl) for retrieving the public IP address. The CLI example uses 'dig', which is available on Linux/macOS but not by default on Windows, while the PowerShell example is Windows-specific. However, the overall workflow is portal-centric and platform-agnostic, and the YAML deployment targets Linux node pools.
Recommendations
- Add a bash/curl example for retrieving the public IP address for Linux/macOS users (e.g., `curl ifconfig.me` or `curl ipinfo.io/ip`).
- Clarify that Azure CLI commands can be run on any OS, and that 'dig' may need to be installed on Windows.
- Consider mentioning that Cloud Shell is platform-agnostic and available from the portal for all users.
- Explicitly state that both Azure CLI and PowerShell are cross-platform, but PowerShell is most commonly used on Windows.
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
Windows Tools
Summary
The documentation provides both Linux and Windows examples for AKS network policy setup, but Windows-specific instructions (such as registering preview features and creating Windows admin credentials) are given their own section and are detailed before Linux equivalents in some places. The use of Azure CLI is platform-neutral, but there are Windows-specific steps and terminology (e.g., HNS ACLPolicies) discussed before Linux equivalents. However, Linux parity is generally maintained, and most examples are cross-platform.
Recommendations
- Ensure Linux and Windows instructions are presented in parallel, with clear separation and equal prominence.
- When discussing tools or concepts (e.g., IPTables vs. HNS ACLPolicies), provide Linux explanations first or side-by-side.
- Where possible, clarify which steps are platform-neutral and which are platform-specific.
- Add explicit notes or callouts to help Linux/macOS users skip Windows-only steps.
- Consider adding a table or section summarizing differences and steps for each OS, rather than interleaving them.
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 instructions throughout, but PowerShell is featured equally and sometimes referenced first. There is no explicit Windows bias in the examples themselves, as Azure CLI is cross-platform and bash commands are used for Helm and kubectl. However, the presence of Azure PowerShell instructions may create friction for Linux/macOS users, as PowerShell is less commonly used on those platforms. There are no missing Linux examples, and Windows-specific tools or patterns are not mentioned exclusively.
Recommendations
- Clarify that Azure CLI is recommended for Linux/macOS users, and PowerShell is optional or primarily for Windows users.
- Consider presenting Azure CLI instructions before PowerShell instructions, as CLI is more universally supported.
- Add a note indicating that Azure PowerShell is available cross-platform, but CLI is the default for Linux/macOS.
- Ensure that bash commands (helm, kubectl, git) are shown as the primary workflow for Linux/macOS users.
- Optionally, provide a table or section summarizing which tools are best suited for each OS.
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 examples for Azure CLI, Azure PowerShell, and Azure Developer CLI throughout, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI. There are no explicit Linux/macOS examples (e.g., Bash shell, native package managers), and PowerShell is presented as a primary option, which may create friction for Linux/macOS users. However, Azure CLI is cross-platform and is shown first in most sections, mitigating the bias. No critical steps are Windows-only, and Linux/macOS users can complete the tutorial using Azure CLI.
Recommendations
- Clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
- Add explicit Bash shell examples or mention native installation methods for kubectl on Linux/macOS (e.g., apt, yum, Homebrew).
- De-emphasize PowerShell for non-Windows users, or add notes indicating PowerShell is primarily for Windows.
- Consider adding a section or callout for Linux/macOS users to highlight relevant tools and commands.
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 both Windows and Linux environments. However, the PowerShell section is notably detailed, with explicit instructions for Windows, macOS, and Linux installation and upgrade, and PowerShell is presented before Azure CLI. This ordering and emphasis may create a perception of Windows/PowerShell bias, though Linux users are not blocked from completing the task.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is more universally used across platforms.
- Add explicit notes clarifying that Azure CLI works natively on Linux/macOS and is often preferred for cross-platform scripting.
- Balance the detail level between PowerShell and CLI sections, ensuring Linux/macOS users have equally comprehensive guidance.
- Consider adding Bash shell examples or highlighting CLI usage in Linux environments.
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 tool for moving resources, alongside Azure CLI and the Azure portal. Azure CLI is used for all command-line examples, which are cross-platform, but Azure PowerShell is listed before Azure CLI in the section describing migration options. No PowerShell-specific examples are provided, and all YAML and kubectl examples are Linux-oriented. There are no missing Linux examples, but the mention of Azure PowerShell and its placement could create minor friction for Linux/macOS users.
Recommendations
- List Azure CLI before Azure PowerShell when describing migration options, as Azure CLI is cross-platform and more widely used in Linux/macOS environments.
- Clarify that Azure PowerShell is primarily for Windows users, and recommend Azure CLI for Linux/macOS users.
- Optionally, provide a brief note that all command-line examples use Azure CLI, which works on Windows, Linux, and macOS.
- Ensure that any future PowerShell examples are accompanied by equivalent Azure CLI examples.
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 for creating an AKS cluster using Azure CLI, Azure PowerShell, and the Azure portal, with PowerShell mentioned alongside CLI and portal. However, all configuration, verification, and troubleshooting examples use cross-platform tools (Azure CLI and kubectl), and the feature itself is explicitly Linux-only (supported only on Azure Linux or Ubuntu 22.04+ node pools). There are no Windows-specific commands, tools, or patterns used in the main instructions. The only minor bias is mentioning PowerShell as an option for cluster creation, but this does not impact Linux/macOS users.
Recommendations
- Consider listing Azure CLI and Azure portal first, as they are fully cross-platform, and clarify that Azure PowerShell is primarily for Windows users.
- Explicitly state that all configuration and management steps are cross-platform and can be performed from Linux, macOS, or Windows.
- If possible, provide a note that Azure PowerShell is not required for Linux users, and that Azure CLI is the recommended tool.
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
Windows Tools
Summary
The documentation provides parity for both Linux and Windows node pools in AKS, but there is a slight bias toward Windows in some sections. Windows-specific instructions (such as registering feature flags and creating admin credentials) are given their own section and are detailed before Linux equivalents in some places. The use of Azure CLI is platform-neutral, but Windows-specific tools and patterns (feature flag registration, admin credential setup) are highlighted. Linux examples are present and complete, but Windows instructions are sometimes more verbose and prominent.
Recommendations
- Ensure Linux and Windows instructions are presented in parallel sections, with equal prominence and detail.
- Where possible, provide Linux-specific notes or examples alongside Windows-specific steps (e.g., admin credential creation).
- Avoid presenting Windows-specific steps before Linux unless required by technical order.
- Clarify which steps are platform-neutral and which are platform-specific.
- Consider adding a summary table or section that clearly delineates Linux vs Windows steps for cluster creation and management.
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, especially regarding Docker and Kubernetes commands. However, in the 'Verify Docker installation and start Docker daemon' section, instructions for starting Docker are presented as 'macOS/Windows' first, followed by Linux. This is a minor ordering bias, but all platforms are covered. No PowerShell-specific commands, Windows-only tools, or missing Linux examples are found.
Recommendations
- When listing platform-specific instructions, alternate the order or explicitly state that instructions apply equally to Linux, macOS, and Windows.
- Consider grouping instructions by platform or using tabs for clarity.
- Ensure that Linux instructions are not consistently listed after Windows/macOS instructions to avoid perceived bias.
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 documentation provides troubleshooting steps for the agentic CLI for AKS, with Docker-related solutions often mentioning Windows/macOS tools (Docker Desktop) before Linux equivalents. Windows/macOS instructions are listed first in several sections, and Docker Desktop is referenced as the primary tool for Windows/macOS users, while Linux instructions rely on systemd and command-line utilities. However, Linux-specific guidance is present and generally complete, and most examples are cross-platform.
Recommendations
- Alternate the order of platform instructions (e.g., list Linux first in some sections).
- Explicitly mention that Docker Desktop is not available on Linux and clarify the Linux workflow.
- Provide parity in troubleshooting steps, ensuring Linux/macOS/Windows are equally covered.
- Consider grouping platform-specific instructions under clear headings for each OS.
- Add notes about platform differences where relevant (e.g., Docker Desktop vs. systemd).
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 a generally cross-platform approach, with explicit download links and instructions for Windows, macOS, and Linux. However, in several sections (especially VS Code instructions), Windows keyboard shortcuts are mentioned first, and Linux-specific troubleshooting or configuration details are less prominent. The Docker section includes Linux-specific user guidance, but overall, Linux examples and tips are less detailed compared to Windows. There are no PowerShell-only examples or Windows-exclusive tools, but Linux users may find minor friction due to the ordering and lack of explicit Linux-focused troubleshooting.
Recommendations
- Ensure Linux keyboard shortcuts and configuration steps are given equal prominence to Windows (e.g., list Linux shortcuts first or side-by-side).
- Add explicit Linux troubleshooting tips (e.g., common permission issues, file path conventions, user/group mapping for Docker containers).
- Include more Linux-specific example commands and configuration scenarios, especially for Docker and manual binary installation.
- Consider a dedicated Linux/macOS section for common issues, as is done for Windows/WSL.
- Review all download and install instructions to ensure Linux users are not required to infer steps from Windows-centric guidance.
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 both Linux and Windows file paths when verifying TLS Bootstrapping, but Linux paths are mentioned first. All command examples use cross-platform tools (Azure CLI, kubectl, curl, openssl), and there are no PowerShell or Windows-specific command examples. However, Windows file paths are mentioned in the context of node access, and Azure CLI is used throughout, which is available on both platforms. There is a minor mention of Windows nodes in example output, but no Windows-only tools or patterns are prioritized.
Recommendations
- Ensure all file path examples for both Linux and Windows nodes are equally explained and contextualized.
- If Windows-specific commands or PowerShell are needed, provide equivalent Linux/bash examples.
- Clarify that Azure CLI and kubectl commands are cross-platform and provide links to installation instructions for both Windows and Linux.
- If referencing Windows file paths, briefly explain how to access them (e.g., via RDP or Azure Serial Console) for parity with Linux SSH instructions.
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
Windows Tools
Summary
The documentation is generally cross-platform, focusing on Kubernetes and Azure Files usage for both Linux and Windows containers. However, there are minor signs of Windows bias: Windows path conventions and PowerShell/CMD syntax are mentioned before Linux equivalents in some places, and Windows-specific notes are sometimes presented first. Azure CLI and kubectl are used throughout, which are cross-platform tools, but Windows path examples and references to Windows conventions appear before Linux in some sections.
Recommendations
- When providing examples for Windows and Linux/macOS, alternate which platform is shown first or present both together.
- Ensure Linux/macOS path conventions and shell syntax are always included alongside Windows examples.
- Where Windows-specific notes are given, add equivalent Linux/macOS notes if applicable.
- Review output examples to ensure they are not only Windows-centric (e.g., path formats, command syntax).
Aks
Install Dapr Extension for Azure Kubernetes Service (AKS)
...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, focusing on Azure CLI and Bicep, which are available on Windows, Linux, and macOS. However, in the 'List the CRDs in your cluster' section, only a Windows/PowerShell example is provided (`kubectl get crds | findstr dapr.io`), and no Linux/macOS equivalent (e.g., using `grep`) is shown. Additionally, the use of PowerShell syntax for variable assignment in the Bicep section (`MY_RESOURCE_GROUP=<your-resource-group>`) could be confusing, but it is actually Bash syntax, so this is not a bias. The rest of the documentation uses Azure CLI commands, which are cross-platform, and does not mention Windows tools or patterns exclusively.
Recommendations
- Add a Linux/macOS example for listing CRDs, such as `kubectl get crds | grep dapr.io`.
- Where possible, show both Windows and Linux/macOS command variants side-by-side, especially for shell commands.
- Clarify that Azure CLI and Bicep are cross-platform and can be used on any OS.
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 listing, but references to PowerShell (Get-AzVirtualNetworkSubnetConfig) are given alongside Azure CLI without Linux equivalents. The 'Before you begin' section lists Azure CLI, PowerShell, and Portal, but Azure CLI is mentioned first. All main walkthroughs use kubectl and Azure CLI, which are cross-platform, but PowerShell is referenced as an alternative tool without mentioning Bash or Linux-native scripting. There are no Linux-specific examples or explicit parity notes.
Recommendations
- Where PowerShell is referenced, also mention Bash or Linux-native alternatives (e.g., az CLI in Bash, or shell scripting).
- Clarify that Azure CLI commands work on Linux/macOS and Windows equally.
- Consider providing Linux/macOS-specific guidance or examples where scripting or environment setup is discussed.
- If referencing PowerShell, note its availability on Linux/macOS, or provide Bash equivalents.
- In prerequisite lists, avoid listing PowerShell before cross-platform tools unless the feature is Windows-only.
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 Linux tools or shell patterns (e.g., bash, curl), and the CLI example uses 'dig', which is available on Linux/macOS but not natively on Windows. However, the overall guidance is platform-neutral, focusing on portal-based workflows and Azure CLI/PowerShell, which are cross-platform tools. Minor bias is present in the troubleshooting section where PowerShell is given equal prominence, but no Linux/macOS-specific troubleshooting or shell examples are provided.
Recommendations
- Explicitly mention that Azure CLI commands are cross-platform and can be run on Linux, macOS, and Windows.
- Add bash-specific or Linux/macOS shell examples for retrieving the public IP address (e.g., using 'curl' or 'wget'), since 'dig' may not be installed by default.
- Clarify that Azure PowerShell is available on all platforms, but provide guidance for Linux/macOS users who may prefer bash or zsh.
- Consider providing a simple bash command for IP retrieval, such as 'curl ifconfig.me', alongside the 'dig' example.
- Ensure troubleshooting steps reference Linux/macOS environments where relevant, especially for network connectivity and IP retrieval.
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 as a primary option alongside Azure CLI, which is more commonly used on Linux/macOS, and PowerShell is typically associated with Windows environments. The examples and instructions for PowerShell are given equal prominence, potentially implying Windows as a first-class platform. There are no explicit Linux/macOS-specific examples or notes, but the Azure CLI instructions are cross-platform and the use of Bash/Cloud Shell is mentioned. No critical steps are Windows-only, and Linux/macOS users can complete the tutorial without friction.
Recommendations
- Clarify that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
- Add explicit notes or examples for Linux/macOS users, such as using Bash or Zsh shells.
- Mention that PowerShell Core is available on Linux/macOS, but Azure PowerShell is most commonly used on Windows.
- Consider listing Azure CLI instructions first, as it is the default for cross-platform usage.
- Add a brief section or callout for Linux/macOS users, confirming that all steps are supported and providing any shell-specific tips.