Aks
529
Total Pages
427
Linux-Friendly Pages
102
Pages with Bias
19.3%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
343 issues found
Showing 1-25 of 343 flagged pages
Aks
Provision Azure NetApp Files SMB volumes for Azure Kubernetes Service
...-docs/blob/main/articles/aks/azure-netapp-files-smb.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation is heavily focused on provisioning SMB volumes for Windows-based AKS workloads. All pod examples use Windows containers (IIS on Windows Server Core), and node selectors are set to Windows. There are no Linux pod/container examples, nor any discussion of mounting SMB volumes from Linux containers. The only usage examples for accessing the SMB share are via Windows tools (cmd.exe, dir). The documentation does not mention Linux compatibility, limitations, or provide Linux-specific guidance for SMB volumes.
Recommendations
- Add examples for Linux pods mounting SMB volumes, including sample manifests and verification steps using Linux commands (e.g., mount, ls, df).
- Clarify whether SMB volumes can be mounted by Linux containers in AKS, and document any prerequisites or limitations.
- Provide parity in troubleshooting and verification steps for both Windows and Linux pods.
- If SMB volumes are Windows-only, explicitly state this limitation early in the documentation.
- Include links or references to NFS documentation for Linux workloads, and guidance on choosing between SMB and NFS based on OS.
Create Pull Request
Aks
Enable Group Managed Service Accounts (GMSA) for your Windows Server nodes on your Azure Kubernetes Service (AKS) cluster
...ain/articles/aks/use-group-managed-service-accounts.md
High Priority
View Details →
Detected Bias Types
Windows Only
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
This documentation is exclusively focused on enabling Group Managed Service Accounts (GMSA) for Windows Server nodes in AKS. All examples, YAML manifests, and troubleshooting steps are tailored to Windows containers and Windows authentication mechanisms. PowerShell scripts and Windows-specific tools (e.g., IIS, Windows features, Log Monitor) are used throughout, with no mention of Linux equivalents or how Linux nodes might interact with GMSA. There are no Linux container examples, and the guide does not address Linux/macOS users except in general Azure CLI usage.
Recommendations
- Clearly state at the beginning that GMSA is a Windows-only feature and that the guide is not applicable to Linux nodes.
- Provide links or references to equivalent Linux authentication mechanisms (e.g., Kerberos integration for Linux containers, if available in AKS).
- Add a section describing how authentication and service accounts work for Linux nodes in AKS, and how they differ from GMSA.
- If possible, provide parity documentation for Linux service account management in AKS, or cross-link to such resources.
- Ensure troubleshooting and verification steps clarify their Windows-only applicability, and suggest alternatives for Linux users where relevant.
Aks
About the Agentic CLI for Azure Kubernetes Service (AKS)
...s/blob/main/articles/aks/cli-agent-for-aks-overview.md
Medium Priority
View Details →
Detected Bias Types
Missing Linux Example
Windows First
Summary
The documentation describes the Agentic CLI for AKS in a platform-neutral manner but subtly exhibits Windows bias by referencing 'local Azure CLI credentials' and 'Docker' without clarifying Linux/macOS support. There are no explicit Linux/macOS examples or instructions, and prerequisites are listed generically (e.g., 'Docker'), which may imply Windows as the default environment. The absence of Linux/macOS-specific guidance or troubleshooting creates friction for non-Windows users.
Recommendations
- Explicitly state that the Agentic CLI for AKS supports Windows, Linux, and macOS platforms.
- Provide installation and usage examples for Linux and macOS, including any platform-specific prerequisites or troubleshooting tips.
- Clarify that Docker and Azure CLI are cross-platform tools, and link to their Linux/macOS installation guides.
- Add a section or table highlighting any differences or considerations for Linux/macOS users.
Aks
Develop on Azure Kubernetes Service (AKS) with Helm
...ure-aks-docs/blob/main/articles/aks/quickstart-helm.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides parallel Azure CLI and Azure PowerShell instructions for all Azure-related steps, but PowerShell is featured equally alongside CLI. There are no Windows-only tools or patterns, but PowerShell is a Windows-centric tool and is presented as a primary option. The document does not provide Linux-specific shell examples (e.g., Bash for Azure CLI) or highlight Linux/macOS parity. Azure CLI is cross-platform, but PowerShell is not as widely used on Linux/macOS. The ordering of examples is neutral, but the presence of PowerShell throughout may create friction for Linux/macOS users.
Recommendations
- Clarify that Azure CLI is the recommended cross-platform tool for Linux/macOS users.
- Consider adding explicit Bash shell examples for Azure CLI commands to reinforce Linux/macOS parity.
- Mention that Azure PowerShell is primarily for Windows users, and provide guidance for Linux/macOS users to use Azure CLI.
- Add notes or callouts where PowerShell is used, indicating alternative approaches for Linux/macOS users.
- Ensure that all steps can be completed using Azure CLI alone, and highlight this in the prerequisites.
Aks
Kubernetes on Azure tutorial - Upgrade an Azure Kubernetes Service (AKS) cluster
...in/articles/aks/tutorial-kubernetes-upgrade-cluster.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides parallel examples for Azure CLI, Azure PowerShell, and Azure portal for all major tasks. However, Azure PowerShell is featured equally alongside Azure CLI, which is more cross-platform, and PowerShell is primarily a Windows-centric tool (though available on Linux/macOS). In some sections, PowerShell examples are given before Azure CLI, and PowerShell-specific installation instructions are included. There are no Linux-specific shell examples (e.g., Bash), nor explicit mention of Linux/macOS command-line environments. The documentation does not use Windows-only tools, but the prominence of PowerShell may create friction for Linux/macOS users.
Recommendations
- Clearly indicate that Azure CLI is recommended for Linux/macOS users, and that PowerShell is optional.
- Add brief notes clarifying that Azure CLI commands work on all platforms, while PowerShell is more common on Windows.
- Consider including Bash shell examples or notes for Linux/macOS users, especially for common tasks.
- Reorder examples to show Azure CLI first, followed by PowerShell, to reduce Windows-first bias.
- Add a short section or callout for Linux/macOS users, linking to Azure CLI installation and usage guidance.
Aks
Develop on Azure Kubernetes Service (AKS) with Helm
...ure-aks-docs/blob/main/articles/aks/quickstart-helm.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all Azure resource management tasks, with PowerShell examples given equal prominence. However, there are no Linux-specific instructions or examples for using native Linux tools or shell environments. The use of PowerShell is highlighted as a primary method alongside Azure CLI, which may create friction for Linux/macOS users who do not use PowerShell.
Recommendations
- Clarify that Azure PowerShell examples are intended for Windows users and that Azure CLI is cross-platform.
- Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, and recommend CLI for non-Windows environments.
- Consider listing Azure CLI examples before PowerShell examples, or defaulting to CLI in mainline instructions, with PowerShell as an alternative.
- Add notes or links for Linux/macOS users regarding installation and usage of Azure CLI and kubectl in their environments.
- Remove or de-emphasize PowerShell examples in sections where CLI is sufficient and more broadly applicable.
Aks
Upgrade the Azure Kubernetes Service (AKS) cluster control plane
...cs/blob/main/articles/aks/upgrade-aks-control-plane.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all upgrade operations, with Azure PowerShell (a Windows-centric tool) given equal prominence and detail as Azure CLI. In some sections, PowerShell examples are presented before or alongside CLI examples, and there is explicit mention of installing/upgrading Azure PowerShell. However, there are no Linux-specific shell examples (e.g., bash, zsh), and the documentation does not mention Linux/macOS compatibility for Azure CLI commands, nor does it clarify that PowerShell Core is cross-platform. The bias is moderate, as Linux/macOS users can complete all tasks using Azure CLI, but the equal focus on PowerShell may create friction or confusion for non-Windows users.
Recommendations
- Clarify that Azure CLI is fully supported on Linux and macOS, and recommend it as the primary tool for cross-platform scenarios.
- Note that Azure PowerShell is available cross-platform via PowerShell Core, but is most commonly used on Windows.
- Consider presenting Azure CLI examples first, as it is the default for Linux/macOS users.
- Add a brief note for Linux/macOS users about installing Azure CLI and running commands in bash/zsh.
- Remove unnecessary emphasis on PowerShell unless there are Windows-specific steps.
Aks
API Server Authorized IP Ranges in Azure Kubernetes Service (AKS)
...b/main/articles/aks/api-server-authorized-ip-ranges.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides both Azure CLI (cross-platform) and Azure PowerShell (Windows-centric) instructions for all major tasks, but PowerShell examples and Windows-specific tooling are given equal or greater prominence. In the 'Find your IP address' section, Windows-specific methods (PowerShell command and Microsoft support link) are mentioned, while Linux/macOS alternatives are less visible or not explicitly described. The use of PowerShell and references to Windows tools may create friction for Linux/macOS users, though CLI examples are present throughout.
Recommendations
- For every PowerShell example, ensure a Linux/macOS shell equivalent is provided (e.g., bash, curl, dig).
- In the 'Find your IP address' section, add explicit Linux/macOS commands (e.g., curl ifconfig.me, dig, or ip addr) and mention them before or alongside Windows methods.
- Clarify that Azure CLI commands work on all platforms and highlight platform-agnostic approaches.
- Review all sections for implicit Windows-first assumptions and rephrase to be platform-neutral where possible.
Aks
Provision Azure NetApp Files dual-protocol volumes for Azure Kubernetes Service
.../main/articles/aks/azure-netapp-files-dual-protocol.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Summary
The documentation provides comprehensive instructions for both NFS (Linux) and SMB (Windows) dual-protocol volumes in AKS. However, the SMB example is exclusively Windows-focused, with pod manifests using Windows containers (IIS), nodeSelector for Windows nodes, and Windows shell commands (cmd.exe, dir). There are no SMB pod examples for Linux containers, nor guidance for mounting SMB volumes on Linux nodes, despite SMB being supported on Linux via the CSI driver. The SMB section implicitly prioritizes Windows usage and tools.
Recommendations
- Add SMB pod manifest examples for Linux containers, demonstrating mounting SMB volumes on Linux nodes.
- Include Linux shell commands (e.g., bash, ls, df) for verifying SMB mounts in Linux pods, alongside Windows examples.
- Clarify in the SMB section that SMB volumes can be mounted on both Windows and Linux nodes, and provide parity in instructions.
- Consider reordering or parallelizing examples so that both Linux and Windows use cases are equally represented for SMB.
Aks
Troubleshoot the Agentic CLI for Azure Kubernetes Service (AKS)
...ob/main/articles/aks/cli-agent-for-aks-troubleshoot.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation includes a troubleshooting step for 'ImportError: DLL load failed while importing win32file', which is a Windows-specific error and references reinstalling the Azure CLI client without mentioning Linux/macOS equivalents. There are no Linux/macOS-specific troubleshooting steps or examples, and the guidance does not clarify platform differences for CLI installation or error resolution.
Recommendations
- Add troubleshooting steps for common Linux/macOS errors (e.g., library issues, permission errors, missing dependencies).
- Clarify that 'ImportError: DLL load failed while importing win32file' is a Windows-specific error and provide equivalent Linux/macOS error messages and solutions if applicable.
- Include platform-specific instructions for reinstalling the Azure CLI (e.g., apt, yum, Homebrew commands for Linux/macOS).
- Explicitly state when a troubleshooting step is only relevant to Windows users.
Aks
Deploy an Azure Kubernetes application by using an ARM template
.../blob/main/articles/aks/deploy-application-template.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for accepting marketplace terms, but the PowerShell example is given immediately after the CLI example, and no explicit Linux/macOS shell example is shown. The CLI command is generic, but the PowerShell reference may create a perception of Windows preference. There are no Linux-specific instructions or screenshots, and the workflow assumes familiarity with the Azure portal, which is cross-platform but may be more familiar to Windows users. No Linux tools or shell scripting examples are provided.
Recommendations
- Clarify that Azure CLI commands work on Windows, Linux, and macOS, and explicitly mention this in the relevant section.
- Remove or de-emphasize PowerShell examples unless there is a unique Windows-only step.
- Add a Linux/macOS shell example for downloading and deploying the ARM template, such as using curl, wget, or bash scripting.
- Include a note or section highlighting cross-platform compatibility and any OS-specific caveats.
- Ensure screenshots and instructions do not assume a Windows environment (e.g., file paths, shell conventions).
Aks
AKS Regulated Cluster for PCI DSS 4.0.1 - Enhanced MFA Implementation
...b/main/articles/aks/pci-enhanced-mfa-implementation.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides several implementation examples using PowerShell scripts and references to Azure AD Conditional Access, which are typically managed via the Azure Portal or PowerShell. There are no Linux/macOS-specific CLI or automation examples (e.g., Bash, Azure CLI, REST API) for creating Conditional Access policies or managing MFA, and PowerShell is presented as the only scripting method for policy creation. Additionally, Windows-centric tools and workflows (PowerShell, Azure Portal navigation) are mentioned before any cross-platform alternatives, and Linux-native approaches are not discussed.
Recommendations
- Add equivalent Bash/Azure CLI examples for creating and managing Conditional Access policies and MFA enforcement.
- Reference REST API methods for Conditional Access policy management, which are platform-agnostic.
- Clarify that PowerShell is one option and provide links or examples for Linux/macOS users.
- Where possible, use Azure CLI for all AKS and Azure AD operations, as it is cross-platform.
- Explicitly mention that all steps can be performed from Linux/macOS using Azure CLI or REST API, and provide sample commands.
Aks
AKS Regulated Cluster for PCI DSS 4.0.1 - Risk Assessment and Code Assets
...-aks-docs/blob/main/articles/aks/pci-ra-code-assets.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation is generally cross-platform and AKS-focused, with most examples and guidance applicable to both Linux and Windows environments. However, there is a notable instance of Windows bias in the Identity and Access Management section, where PowerShell cmdlets are referenced for configuring conditional access policies, without mentioning equivalent CLI or REST API options for Linux/macOS users. Additionally, the PowerShell example is presented first and exclusively, which may create friction for non-Windows users.
Recommendations
- Include Azure CLI and/or REST API examples alongside PowerShell for configuring conditional access policies, ensuring Linux/macOS users have clear guidance.
- When referencing management tools or automation, provide cross-platform alternatives or clarify platform requirements.
- Review other sections for subtle Windows-first patterns and ensure parity in tooling and examples where possible.
Aks
AKS Regulated Cluster for PCI DSS 4.0.1 - Security Awareness Training
...b/main/articles/aks/pci-security-awareness-training.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides a PowerShell script as the sole example for automating training completion tracking, without offering equivalent Linux/macOS (e.g., Bash, Python, Azure CLI) alternatives. This may create friction for users who primarily work in Linux environments, as AKS is often managed from Linux/macOS systems. Additionally, the PowerShell example appears before any Linux-friendly tooling is mentioned, suggesting a Windows-first approach in automation guidance.
Recommendations
- Provide equivalent Bash or Azure CLI examples for tracking training completion and updating Azure AD user properties.
- Clarify that the PowerShell script is one option and suggest cross-platform alternatives (e.g., Python SDK, REST API, Azure CLI).
- Ensure automation and scripting examples are presented in a way that is accessible to both Windows and Linux/macOS users.
- Where possible, use platform-agnostic tools (e.g., Azure CLI, REST API) for examples involving Azure services.
Aks
Kubernetes on Azure tutorial - Create an Azure Container Registry and build images
...b/main/articles/aks/tutorial-kubernetes-prepare-acr.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for most steps, but PowerShell is emphasized as an alternative throughout, and is presented in dedicated tabs. The CLI examples use environment variables in a way that is ambiguous for Linux/macOS users (e.g., $ACRNAME), and there are no explicit Linux/macOS shell examples or notes about shell differences. PowerShell is a Windows-centric tool, and its inclusion as a primary alternative may create friction for Linux/macOS users. There are no Linux-specific instructions or examples, and the documentation does not clarify how to set environment variables or run commands in Bash/zsh.
Recommendations
- Add explicit Bash/zsh examples for Linux/macOS users, especially for environment variable usage (e.g., export ACRNAME=myregistry123).
- Clarify how environment variables should be set and used in different shells (Windows CMD, PowerShell, Bash/zsh).
- Consider presenting Azure CLI (cross-platform) examples first, and PowerShell as a secondary option.
- Add notes or tabs for Linux/macOS users where command syntax or behavior differs.
- Avoid assuming PowerShell is available or preferred on Linux/macOS.
Aks
Control cluster and node access using Conditional Access with AKS-managed Microsoft Entra integration
...b/main/articles/aks/access-control-managed-azure-ad.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias by focusing exclusively on Azure portal workflows and Azure CLI commands, which are cross-platform but often more familiar to Windows users. There are no explicit Linux/macOS-specific instructions or examples, and no mention of Linux-native SSH tools or workflows. The SSH example uses 'az ssh vm', which is Azure-specific and does not discuss standard OpenSSH usage or alternatives for Linux/macOS users. The documentation also references Azure portal navigation and Microsoft Entra ID features, which may be more familiar to Windows-centric administrators.
Recommendations
- Add explicit Linux/macOS examples for SSH access, such as using OpenSSH with Entra ID integration.
- Include notes or sections on how to perform equivalent tasks using Linux-native tools and command-line workflows.
- Clarify that Azure CLI is cross-platform and provide installation instructions for Linux/macOS users.
- Provide parity in troubleshooting steps or verification methods for Linux/macOS environments.
- Mention any differences in authentication flows or device compliance checks for non-Windows endpoints.
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Summary
The documentation page demonstrates a moderate Windows bias. Azure CLI examples dominate, and all traffic management, DNS, and cluster operations use Azure CLI commands, which are most easily run on Windows or via PowerShell. There is no mention of Linux-specific tools, nor are Linux-native command-line alternatives (e.g., bash scripts, Linux DNS utilities) provided. Windows-centric Azure Traffic Manager and DNS update patterns are shown first and exclusively. No PowerShell scripts are present, but the CLI usage and Azure-centric tooling are more familiar to Windows users. Linux users can follow along, but the lack of explicit Linux/macOS guidance or parity examples creates friction.
Recommendations
- Add explicit notes or examples for Linux/macOS users, including how to install and use Azure CLI on those platforms.
- Provide bash-native alternatives for DNS switching (e.g., using dig/nsupdate for validation).
- Include references to Linux-native tools for monitoring and scripting (e.g., systemd timers, cron jobs, shell scripts) alongside Azure CLI.
- Clarify that Azure CLI is cross-platform and provide links to installation guides for Linux/macOS.
- Where possible, show both Azure CLI and REST API/cURL equivalents for cluster operations.
- Add troubleshooting steps that mention Linux-specific issues (e.g., shell quoting, file permissions).
Medium Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation is heavily focused on Windows workloads and tools. All examples pertain to enabling Azure Hybrid Benefit for Windows Server licenses, and the only admin user shown is a Windows admin. The PowerShell examples reinforce a Windows-centric approach, and there are no Linux-specific examples or mention of Linux workloads. The documentation does not clarify if or how Azure Hybrid Benefit applies to Linux nodes, and the 'Next steps' section exclusively references Windows containers.
Recommendations
- Clarify early in the documentation that Azure Hybrid Benefit is only applicable to Windows Server workloads, if that is the case. If Linux workloads are supported, provide equivalent examples for Linux nodes.
- Include a statement or FAQ addressing the applicability (or lack thereof) of Azure Hybrid Benefit to Linux workloads.
- If possible, provide Linux/macOS shell (bash) equivalents for any Azure CLI commands, and clarify that Azure CLI is cross-platform.
- Balance the 'Next steps' section by including resources for both Windows and Linux containers on AKS, or explicitly state the Windows focus.
- Avoid using only Windows admin usernames and passwords in examples; consider using neutral or cross-platform examples.
Aks
Provision Azure NetApp Files dual-protocol volumes for Azure Kubernetes Service
.../main/articles/aks/azure-netapp-files-dual-protocol.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Powershell Heavy
Summary
The documentation provides detailed, step-by-step instructions for both NFS (Linux) and SMB (Windows) volume provisioning in AKS with Azure NetApp Files. However, the SMB section is heavily oriented toward Windows usage: it exclusively demonstrates mounting SMB volumes in Windows pods (using IIS and Windows ServerCore images), uses Windows-specific commands (cmd.exe, dir), and sets nodeSelector for Windows nodes. There are no examples or guidance for mounting SMB volumes in Linux pods, nor any mention of Linux-compatible SMB usage. The SMB CSI driver installation instructions explicitly enable Windows support, and all verification steps for SMB are Windows-centric.
Recommendations
- Add examples for mounting SMB volumes in Linux pods, including sample YAML manifests and verification steps using Linux containers (e.g., Ubuntu, Alpine).
- Document any Linux-specific requirements or limitations for SMB volumes in AKS (e.g., supported images, mount options, troubleshooting).
- Include Linux command-line examples for verifying SMB mounts (e.g., using 'mount', 'df -h', 'ls') alongside Windows commands.
- Clarify in the SMB section that SMB volumes can be mounted by both Windows and Linux pods, if supported, or explicitly state any platform limitations.
- Present NFS and SMB instructions in parallel, with equal detail and visibility for both Linux and Windows use cases.
Aks
Configure Azure NetApp Files for Azure Kubernetes Service
...-aks-docs/blob/main/articles/aks/azure-netapp-files.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation exhibits mild Windows bias by referencing SMB volumes as only supported on Windows worker nodes and mentioning AD DS integration requirements, which are Windows-centric. All command-line examples use Azure CLI, which is cross-platform, but there are no explicit Linux/macOS-specific instructions or clarifications. The documentation does not provide parity for Linux users regarding SMB volumes, and Windows requirements are mentioned before alternatives or limitations for Linux.
Recommendations
- Clarify which steps and features are cross-platform and which are Windows-only (e.g., SMB support).
- Provide explicit guidance or alternatives for Linux/macOS users, especially regarding SMB volumes and AD DS integration.
- Add Linux/macOS-specific notes or examples where relevant, or link to documentation covering those scenarios.
- Consider reordering sections so that platform-neutral or Linux-friendly options (NFS, dynamic provisioning) are presented first.
- Explicitly state limitations for Linux/macOS users up front, and suggest workarounds or alternatives.
Aks
Troubleshoot the Agentic CLI for Azure Kubernetes Service (AKS)
...ob/main/articles/aks/cli-agent-for-aks-troubleshoot.md
Medium Priority
View Details →
Detected Bias Types
Windows Tools
Missing Linux Example
Summary
The documentation includes an error ('ImportError: DLL load failed while importing win32file') that is specific to Windows environments, referencing a Windows-only Python module (win32file) and suggesting to reinstall the Azure CLI client without clarifying platform differences or providing Linux/macOS equivalents. No Linux/macOS-specific troubleshooting steps or examples are present, and the guidance does not address how Linux/macOS users should handle similar issues.
Recommendations
- Add troubleshooting steps for Linux/macOS users, especially for platform-specific errors.
- Clarify that 'win32file' errors are Windows-specific and provide equivalent Linux/macOS error messages and solutions.
- Include examples and troubleshooting guidance for common Linux/macOS issues (e.g., permissions, missing dependencies, environment variable setup).
- Explicitly state platform requirements or differences where relevant.
Aks
Integrate Azure Container Registry with Azure Kubernetes Service (AKS)
...articles/aks/cluster-container-registry-integration.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides parallel examples for Azure CLI and Azure PowerShell throughout, but PowerShell is a Windows-centric tool and is listed as a primary method alongside CLI. There are no Linux/macOS-specific shell examples (e.g., Bash), and PowerShell is presented as an equal alternative, which may imply Windows bias. The troubleshooting section only references Azure CLI, but the main workflows consistently offer PowerShell examples. The documentation does not mention Linux-specific tools or patterns, nor does it clarify cross-platform compatibility for PowerShell. Azure CLI is cross-platform, but PowerShell is traditionally associated with Windows, and its inclusion may create friction for Linux/macOS users.
Recommendations
- Clarify that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
- Explicitly state that Azure PowerShell is available on Linux/macOS, or provide installation instructions for those platforms.
- Add Bash shell examples where appropriate, especially for variable assignment and scripting.
- Consider listing Azure CLI examples before PowerShell to signal cross-platform parity.
- Mention that all kubectl commands are cross-platform and can be run from any OS with the tool installed.
Aks
Concepts - Access and identity in Azure Kubernetes Services (AKS)
...e-aks-docs/blob/main/articles/aks/concepts-identity.md
Medium Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation page consistently presents Azure CLI commands (e.g., az login, az aks get-credentials) and workflow steps without specifying platform differences, but implicitly assumes a Windows environment by referencing browser-based authentication and omitting explicit Linux/macOS instructions or examples. There are no PowerShell-specific commands, but the lack of Linux/macOS parity (such as alternative authentication flows, CLI installation, or environment-specific notes) creates friction for non-Windows users.
Recommendations
- Add explicit instructions or notes for Linux/macOS users, such as how to install Azure CLI, handle browser-based authentication, and manage kubeconfig files.
- Include example commands and workflows for Linux/macOS environments, especially where file paths, authentication prompts, or CLI usage may differ.
- Clarify any platform-specific prerequisites or troubleshooting steps, such as handling device authentication on headless Linux servers.
- Ensure parity in screenshots and UI references (e.g., Azure portal) by noting any differences for non-Windows platforms.
Aks
Configure Azure CNI Networking in Azure Kubernetes Service (AKS)
...aks-docs/blob/main/articles/aks/configure-azure-cni.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation provides examples for Azure Portal, Azure PowerShell, and Azure CLI, but the PowerShell section is notably detailed and references Windows-centric tools. PowerShell is traditionally a Windows-first tool, and its inclusion as a primary method (with instructions for local installation and usage) can signal a Windows bias, especially since the PowerShell module is referenced before CLI and with more setup detail. The CLI section is present and cross-platform, but PowerShell is given more prominence and explanation. There are no explicit Linux/macOS-only examples or troubleshooting tips, and the PowerShell instructions reference Windows upgrade paths before Linux/macOS.
Recommendations
- Ensure Azure CLI examples are as detailed as PowerShell examples, since CLI is natively cross-platform.
- Add troubleshooting or environment setup notes specific to Linux/macOS, especially for PowerShell usage.
- Consider listing CLI instructions before PowerShell, or clarify that CLI is recommended for Linux/macOS users.
- Explicitly mention that PowerShell is available cross-platform, but CLI may be more familiar to Linux/macOS users.
- Provide parity in example depth and setup instructions for both CLI and PowerShell.
Aks
Deploy an Azure Kubernetes application by using an ARM template
.../blob/main/articles/aks/deploy-application-template.md
Medium Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for accepting marketplace terms, but the PowerShell example is included without a corresponding Linux/macOS shell alternative. The flow assumes use of the Azure portal (web), which is cross-platform, but command-line instructions mention PowerShell specifically and do not show Linux/macOS shell equivalents. The CLI example is shown first, but the PowerShell example may cause confusion for non-Windows users. There is no explicit mention of Linux/macOS compatibility or alternative shell commands.
Recommendations
- Clarify that Azure CLI commands work on Linux/macOS and Windows equally.
- Remove or de-emphasize PowerShell examples unless there is a Linux/macOS shell equivalent.
- Add explicit bash/zsh shell examples for Linux/macOS users where appropriate.
- Add a note indicating cross-platform compatibility for all CLI commands.
- If PowerShell is mentioned, clarify its availability on Linux/macOS or provide alternative shell commands.