170
Pages Scanned
17
Pages Flagged
170
Changed Pages
10.0%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:07
Scan Information
Started At: 2026-03-07 00:00:07
Finished At: In Progress
Status: in_progress
Target Repo: Azure Aks
Current Phase: discovery
Files Queued: 170
Files Completed: 170
Problematic Pages
18 issues found
Aks
Kubernetes on Azure tutorial - Create an Azure Kubernetes Service (AKS) cluster
...ain/articles/aks/tutorial-kubernetes-deploy-cluster.md
Medium Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The tutorial provides parallel instructions for Azure CLI, Azure PowerShell, and Azure Developer CLI, but PowerShell is featured prominently as a first-class option throughout. PowerShell examples and terminology are used, which may be unfamiliar or less relevant to Linux/macOS users. The documentation sometimes presents PowerShell instructions before Azure CLI, and does not explicitly mention Bash or Linux shell usage outside of Azure Cloud Shell. There are no explicit Linux/macOS-specific examples or guidance, and the install instructions for kubectl focus on Azure CLI/PowerShell commands rather than native package managers (e.g., apt, brew).
Recommendations
- Add explicit Bash/Linux/macOS shell examples alongside PowerShell, especially for local environments.
- Include instructions for installing kubectl using native package managers (apt, yum, brew) for Linux/macOS users.
- Clarify that Azure CLI commands can be run in Bash on Linux/macOS, not just in Azure Cloud Shell.
- Ensure Azure CLI examples are presented before PowerShell, as CLI is more cross-platform.
- Add notes or links for Linux/macOS users about prerequisites and environment setup.
Create Pull Request
Aks
Configure Azure CNI Networking in Azure Kubernetes Service (AKS)
...aks-docs/blob/main/articles/aks/configure-azure-cni.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_first
Summary
The documentation provides examples for Azure portal, Azure PowerShell, and Azure CLI, covering both Windows and Linux environments. However, the PowerShell section is notably detailed, with explicit instructions for installing/upgrading PowerShell on Windows, macOS, and Linux, and references to Windows-specific tools (e.g., Connect-AzAccount). The PowerShell section appears before the CLI section, which is more universally used across platforms. While Linux and macOS are mentioned for PowerShell installation, the overall structure and emphasis favor Windows/PowerShell patterns.
Recommendations
- Present Azure CLI examples before PowerShell, as CLI is more platform-neutral and widely used.
- Ensure equal detail for Azure CLI instructions, including environment preparation and troubleshooting for Linux/macOS users.
- Add explicit notes or links for Linux/macOS users regarding any differences or prerequisites for Azure CLI usage.
- Consider highlighting Azure CLI as the recommended cross-platform tool for AKS management.
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 operations, but consistently presents Azure CLI (which is cross-platform) first and Azure PowerShell (which is Windows-centric) second. There are no Linux-specific examples or explicit mentions of Linux tools, but the use of Azure CLI covers Linux/macOS users. No critical steps are Windows-only, but the PowerShell examples may create an impression of Windows preference.
Recommendations
- Clarify that Azure CLI is fully cross-platform and recommended for Linux/macOS users.
- Consider adding explicit notes or callouts for Linux/macOS users, especially in the prerequisites section.
- Optionally, provide bash shell script examples for end-to-end workflow, or highlight that all CLI commands work on Linux/macOS.
- Remove or de-emphasize PowerShell examples unless there is a specific Windows audience need.
- Add a table or section summarizing OS compatibility for each tool (Azure CLI, PowerShell, Helm, kubectl).
Aks
Secure Pod Traffic with Network Policies in Azure Kubernetes Service (AKS)
...ks-docs/blob/main/articles/aks/use-network-policies.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides 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 prominent placement and detail. The Windows node pool creation section is longer and more detailed than the Linux section, and Windows-specific tooling (like HNS ACLPolicy) is mentioned alongside Linux equivalents (IPTables). However, Linux parity is generally maintained, and all critical tasks are possible on Linux.
Recommendations
- Ensure Linux and Windows instructions are equally detailed and structured.
- Where possible, present Linux and Windows examples side-by-side or clearly separated, rather than Windows-first.
- Clarify when steps are Windows-only versus Linux-only to reduce confusion.
- Add explicit notes or links for Linux users when Windows-specific steps are described.
- Review the order of sections to avoid implicit prioritization of Windows workflows.
Aks
Create an OpenID Connect (OIDC) Provider for your Azure Kubernetes Service (AKS) Cluster
...ure-aks-docs/blob/main/articles/aks/use-oidc-issuer.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation exclusively uses Azure CLI commands with Bash-style environment variables (e.g., $RESOURCE_GROUP), which are cross-platform but shown in a way that is most familiar to Linux/macOS users. However, there is no evidence of Windows bias: no PowerShell-specific examples, Windows tools, or Windows-first ordering. The examples are generic and work on all platforms where Azure CLI is installed.
Recommendations
- No changes needed for Linux parity. If desired, add a note clarifying that Azure CLI commands work on Windows, macOS, and Linux, and that users on Windows can use these commands in PowerShell or CMD (with appropriate syntax adjustments).
- Optionally, provide PowerShell syntax examples for Windows users, but this is not required for Linux parity.
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 installation and usage instructions for the Agentic CLI for AKS, supporting both client (local/Docker) and cluster (Helm/Kubernetes) modes. In the section about starting the Docker daemon, instructions for macOS/Windows (Docker Desktop) are presented before Linux (systemctl commands). However, all examples and instructions are cross-platform, and Linux-specific commands are included where relevant. No PowerShell-only examples, Windows-only tools, or missing Linux equivalents are found.
Recommendations
- Consider presenting Linux instructions before or alongside Windows/macOS instructions in sections like 'Start the Docker daemon', to avoid subtle ordering bias.
- Explicitly mention that all commands (e.g., Azure CLI, Docker) are cross-platform and provide links to Linux/macOS installation guides where possible.
- Ensure parity in troubleshooting and cleanup instructions for all platforms, including any nuances for Linux (such as Docker daemon management or file locations).
Aks
Troubleshoot the Agentic CLI for Azure Kubernetes Service (AKS)
.../main/articles/aks/agentic-cli-for-aks-troubleshoot.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation generally provides cross-platform troubleshooting steps for the Agentic CLI for AKS, with explicit instructions for Linux, macOS, and Windows. However, in the Docker troubleshooting section, instructions for starting Docker are presented as 'macOS/Windows' first, with Linux instructions following. This ordering may create a minor perception of Windows/macOS priority, but all platforms are covered and Linux-specific commands are present.
Recommendations
- Present platform instructions in a consistent order (e.g., Linux, macOS, Windows or alphabetical) to avoid perceived prioritization.
- Where possible, group platform instructions together under clear headings (e.g., 'On Linux', 'On macOS', 'On Windows') for clarity.
- Ensure that all examples and solutions are present for each supported platform, as is already done here.
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 download links and instructions for Windows, macOS, and Linux. However, there are subtle signs of Windows bias: VS Code keyboard shortcuts and extension installation instructions consistently list Windows shortcuts first, and some tips (e.g., WSL configuration) are Windows-centric. The Docker section includes notes about Windows-specific credential issues, but does not provide equivalent troubleshooting for Linux/macOS. There are no explicit Linux/macOS command-line examples (e.g., for setting file permissions or troubleshooting), and troubleshooting tips focus more on Windows scenarios.
Recommendations
- Alternate keyboard shortcut order between Windows and Linux/macOS, or list both equally.
- Add Linux/macOS-specific troubleshooting tips (e.g., file permissions, environment variable setup, Docker user IDs).
- Provide explicit Linux/macOS command-line examples for common tasks (e.g., setting executable permissions on downloaded binaries, verifying paths).
- Expand Docker credential troubleshooting to include Linux/macOS scenarios.
- Ensure that all platform-specific notes (such as WSL) are matched with equivalent guidance for Linux/macOS users.
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 a minor bias in the section 'Verify TLS Bootstrapping is enabled on current agent node pool', where the Windows node path ('C:\k\bootstrap-config') is mentioned after the Linux path. However, there are no PowerShell-specific examples, Windows tools, or Windows-only commands. All command-line examples use Azure CLI and Bash, which are cross-platform and primarily Linux-focused. The documentation does not provide Windows-specific command examples or instructions, nor does it omit Linux equivalents.
Recommendations
- When mentioning file paths for both Linux and Windows, consider listing Linux first (as AKS is primarily Linux-based) and clarifying parity for both OSes.
- If possible, provide explicit instructions for accessing Windows node paths (e.g., using PowerShell or Windows-native tools) to match the detail level of Linux instructions.
- Ensure that any troubleshooting or maintenance instructions for Windows nodes are as detailed as those for Linux nodes.
- Add a note clarifying that Azure CLI and Bash commands are cross-platform and can be run on Windows via WSL, Git Bash, or Azure Cloud Shell.
Aks
Integrate Azure Container Registry with Azure Kubernetes Service (AKS)
...articles/aks/cluster-container-registry-integration.md
Low Priority
View Details â
Detected Bias Types
powershell_heavy
windows_tools
windows_first
Summary
The documentation provides parallel examples for Azure CLI and Azure PowerShell throughout, but PowerShell (a Windows-centric tool) is featured equally with Azure CLI. There are no Linux-specific shell examples (e.g., Bash), and PowerShell is presented as a primary option alongside Azure CLI, which may create friction for Linux/macOS users. Additionally, the documentation references PowerShell modules and commands without mentioning Linux-native alternatives or clarifying PowerShell Core cross-platform support. Azure CLI is cross-platform, but the prominence of PowerShell and lack of explicit Linux/Bash examples constitute a mild Windows bias.
Recommendations
- Clarify that Azure PowerShell can be used on Linux/macOS via PowerShell Core, or link to installation instructions for non-Windows platforms.
- Add Bash shell examples for Azure CLI commands, showing variable assignment and command usage in Bash syntax.
- Explicitly state that Azure CLI is recommended for Linux/macOS users, and PowerShell is optional.
- Consider including a section on using Terraform (already referenced) for users preferring infrastructure-as-code and cross-platform tooling.
- Where PowerShell is mentioned, note its cross-platform capabilities or provide links to relevant documentation.
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 cross-platform and AKS-centric, focusing on Azure storage options for Kubernetes clusters. However, in the section describing how to mount volumes in pods, Windows container examples are provided immediately after the Linux example, with no additional Linux-specific guidance or parity in example complexity. The Windows example is given its own explicit subsection, which could be perceived as 'windows_first' bias, though the impact is minor.
Recommendations
- Ensure Linux and Windows examples are presented with equal prominence and detail.
- If showing a Windows-specific YAML snippet, also provide a Linux-specific snippet with similar complexity and explanation.
- Clarify that Linux paths use forward slashes and Windows paths use drive letters and backslashes, to help users unfamiliar with both.
- Consider grouping OS-specific examples under a clear 'Linux example' and 'Windows example' heading for parity.
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 and Linux-focused, but there are minor signs of Windows bias. Windows-specific instructions and path conventions are mentioned in several places, sometimes before or alongside Linux equivalents. In the 'Use Azure Files with Windows containers' section, both Linux/MacOS and Windows PowerShell/CMD commands are provided, but the Windows variant is shown second. Windows path conventions are referenced in pod manifests, but Linux examples are predominant throughout. Azure CLI (cross-platform) is used for setup, and PowerShell is not used for core tasks.
Recommendations
- Ensure Linux and Windows instructions/examples are always paired and equally prominent.
- Where Windows-specific path conventions are mentioned, clarify Linux defaults and highlight parity.
- If Windows-specific commands are given, provide Linux/MacOS equivalents first or in parallel.
- Review output examples to ensure they are not Windows-centric unless contextually relevant.
- Consider a brief section summarizing Linux/macOS compatibility and any limitations.
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 PowerShell is a Windows-centric tool, and its mention before Azure CLI (which is cross-platform) may suggest a slight Windows bias. However, all command examples throughout the guide use Azure CLI and bash/kubectl, which are cross-platform and Linux-friendly. No PowerShell-specific commands or Windows-only patterns are present.
Recommendations
- List Azure CLI before Azure PowerShell when describing migration options, emphasizing CLI as the default cross-platform tool.
- Clarify that Azure PowerShell is optional and primarily for users already on Windows, while Azure CLI works on Linux/macOS/Windows.
- Consider linking to Linux/macOS installation instructions for Azure CLI.
- If mentioning Azure PowerShell, briefly note its platform limitations.
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation provides both Azure CLI and PowerShell options for some prerequisite steps, but Azure CLI is used for all main examples. However, PowerShell is mentioned before Azure CLI in the 'Before you begin' section, and a PowerShell cmdlet is referenced alongside Azure CLI for subnet listing. There are no Linux/macOS-specific examples or explicit parity notes, but the main workflow uses cross-platform tools (kubectl, Azure CLI).
Recommendations
- List Azure CLI before PowerShell in prerequisite sections to emphasize cross-platform tools.
- Explicitly note that Azure CLI and kubectl are cross-platform and preferred for Linux/macOS users.
- Provide Linux/macOS-specific guidance for any steps where PowerShell is referenced (e.g., subnet listing), or clarify that Azure CLI is the recommended approach.
- Consider removing PowerShell references unless they are necessary for Windows-only scenarios, or provide equivalent Bash commands.
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
windows_tools
missing_linux_example
Summary
The documentation is generally cross-platform, using Azure CLI and Bicep for all main instructions, which are supported on Windows, Linux, and macOS. However, in the 'List the CRDs in your cluster' section, the example uses 'kubectl get crds | findstr dapr.io', which employs the Windows-specific 'findstr' command. There is no equivalent Linux/macOS example (e.g., using 'grep'), which may cause confusion or friction for non-Windows users.
Recommendations
- Provide both Windows and Linux/macOS command examples when using OS-specific tools. For example, add 'kubectl get crds | grep dapr.io' as the Linux/macOS equivalent.
- Where possible, prefer cross-platform commands or explicitly note OS differences.
- Review for any other subtle Windows-first patterns, though none are apparent in the main installation flow.
Aks
Access Kubernetes Resources using the Azure Portal
...e-aks-docs/blob/main/articles/aks/kubernetes-portal.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for updating AKS API server authorized IP ranges, but the PowerShell example is given equal prominence and appears directly after the CLI example. There are no Linux/macOS-specific examples or explicit mentions of Linux tools, and the PowerShell example may be less relevant for Linux/macOS users. However, the CLI example is cross-platform and appears first, mitigating the bias. No Windows-only tools or patterns are used elsewhere, and the YAML manifests target Linux node pools.
Recommendations
- Explicitly note that Azure PowerShell is Windows-centric and that Azure CLI is recommended for Linux/macOS users.
- Consider adding a note or tab for Bash-only or Linux/macOS-specific instructions where relevant.
- Clarify that all portal-based steps are OS-agnostic.
- If possible, provide a Bash command for retrieving the public IP address (e.g., `curl ifconfig.me` or `dig`), as not all Linux users have `dig` installed.
Aks
Upgrade Azure Kubernetes Service (AKS) node images
...-aks-docs/blob/main/articles/aks/upgrade-node-image.md
Low Priority
View Details â
Detected Bias Types
windows_reference
Summary
The documentation provides Azure CLI and kubectl examples, which are cross-platform. However, there are repeated notes referencing Windows and PowerShell environments when discussing shell command differences, but no actual Windows/PowerShell-specific examples are provided. The documentation does not prioritize Windows tools or patterns, nor does it omit Linux/macOS equivalents.
Recommendations
- Clarify shell differences with concrete examples for both Windows (PowerShell/CMD) and Linux/macOS (bash/zsh) if relevant.
- If referencing Windows/PowerShell environments, also mention Linux/macOS environments for parity.
- Ensure notes about shell differences are balanced and provide actionable guidance for all platforms.
Aks
Stop and start an Azure Kubernetes Service (AKS) cluster
...-aks-docs/blob/main/articles/aks/start-stop-cluster.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for stopping and starting AKS clusters. However, PowerShell examples are presented alongside CLI examples, and PowerShell is referenced in the 'Before you begin' section as an option for creating a cluster. There are no Linux-specific examples or notes, but the Azure CLI is cross-platform and the PowerShell examples do not dominate the page. No Windows-only tools or patterns are mentioned, and Linux users can complete all tasks using the Azure CLI.
Recommendations
- Clarify that Azure CLI commands work on Linux, macOS, and Windows, and are the recommended cross-platform approach.
- Consider listing Azure CLI examples before PowerShell examples to reinforce Linux parity.
- Add a note in the 'Before you begin' section explicitly stating that Azure CLI is available on Linux and macOS, while PowerShell is primarily for Windows users (though PowerShell Core is cross-platform, most Linux users prefer CLI).
- If possible, add a brief section or callout for Linux/macOS users to confirm that all steps are fully supported on their platforms.