170
Pages Scanned
18
Pages Flagged
170
Changed Pages
10.6%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:08
Scan Information
Started At: 2026-03-08 00:00:08
Finished At: In Progress
Status: in_progress
Target Repo: Azure Aks
Current Phase: discovery
Files Queued: 170
Files Completed: 170
Problematic Pages
19 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_tools
windows_first
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and Azure Developer CLI, but PowerShell is featured equally alongside CLI and is referenced for installing tools and managing AKS clusters. PowerShell is a Windows-centric tool, and its inclusion may create friction for Linux/macOS users. Additionally, PowerShell installation and usage instructions are presented before any Linux-specific alternatives. There is no explicit Linux/macOS example or mention of Bash or native shell commands for kubectl installation or AKS cluster creation outside of Azure CLI. The documentation assumes Azure CLI and PowerShell are the primary interfaces, potentially overlooking Linux-native workflows.
Recommendations
- Add explicit Bash/Linux/macOS instructions for installing kubectl (e.g., using curl or package managers like apt, brew, yum).
- Clarify that Azure CLI commands work on Linux/macOS and Windows, and provide any OS-specific notes if needed.
- Consider including a Bash example for setting environment variables (e.g., export ACRNAME=...) and SSH key generation.
- Mention that PowerShell is primarily for Windows users, and suggest alternatives for Linux/macOS users.
- Ensure that Azure CLI examples are presented first, as it is cross-platform, and clarify its parity across OSes.
Create Pull Request
Aks
Install Dapr Extension for Azure Kubernetes Service (AKS)
...softDocs/azure-aks-docs/blob/main/articles/aks/dapr.md
Medium Priority
View Details â
Detected Bias Types
missing_linux_example
windows_tools
Summary
The documentation is generally cross-platform, using Azure CLI and Bicep for all installation and management steps, which are available 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 relies on the Windows-specific 'findstr' command. There is no equivalent Linux/macOS example (e.g., using 'grep'), and the Windows tool is presented without alternatives.
Recommendations
- Provide both Windows and Linux/macOS examples for shell commands involving OS-specific tools. For example, show both 'kubectl get crds | findstr dapr.io' (Windows) and 'kubectl get crds | grep dapr.io' (Linux/macOS).
- When using OS-specific commands, explicitly label them as such and offer alternatives for other platforms.
- Review all shell command examples to ensure they are either cross-platform or have platform-specific variants.
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, followed by Azure PowerShell (which is primarily used on Windows). There are no Linux-specific examples or mentions of Linux tools/patterns, but the CLI instructions are suitable for Linux/macOS users. The only minor bias is the inclusion of PowerShell examples and terminology, which may be less relevant for Linux/macOS users.
Recommendations
- Consider clarifying that Azure CLI is fully cross-platform and preferred for Linux/macOS users, while Azure PowerShell is primarily for Windows.
- Add explicit notes or callouts for Linux/macOS users, confirming that all CLI commands work natively on their platforms.
- Optionally, add a 'Linux/macOS' tab for commands where there might be platform-specific nuances (e.g., installation, file paths, shell syntax), even if the CLI commands are identical.
- Mention that Azure Cloud Shell is available in-browser and works on any OS, reducing platform friction.
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 generally provides parity between Windows/macOS and Linux, especially in Docker setup instructions. However, in the section 'Start the Docker daemon', instructions for macOS/Windows (Docker Desktop) are listed before Linux (systemctl commands), which is a minor 'windows_first' bias. All CLI examples are cross-platform, and Linux-specific commands (kubectl, bash) are included. No PowerShell-specific examples or Windows-only tools are present.
Recommendations
- Present Linux instructions before or alongside Windows/macOS instructions in the Docker daemon startup section.
- Explicitly mention that Docker Desktop is available for macOS as well as Windows, to avoid implying it's Windows-only.
- Consider grouping OS-specific instructions in a table or tabbed format for clarity and parity.
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 guidance, but in the Docker troubleshooting section, instructions for macOS/Windows are listed before Linux, and Docker Desktop (a Windows/macOS-specific tool) is mentioned first. However, Linux-specific commands are also provided, and most examples throughout the document use cross-platform tools (Azure CLI, kubectl). No critical Linux gaps are present.
Recommendations
- Present Linux, macOS, and Windows instructions in parallel or in a consistent order (e.g., Linux first, then macOS, then Windows) to avoid implicit prioritization.
- Clarify that Docker Desktop is only for macOS/Windows, and suggest the equivalent for Linux (e.g., starting the Docker daemon via systemd).
- Where possible, provide unified troubleshooting steps that highlight differences only where necessary.
- Continue to ensure all command-line examples work on Linux, macOS, and Windows (where applicable).
Aks
Configure multiple ingress controllers and NGINX ingress annotations with the application routing add-on for Azure Kubernetes Service (AKS)
...b/main/articles/aks/app-routing-nginx-configuration.md
Low Priority
View Details â
Detected Bias Types
windows_tools
Summary
The documentation page primarily uses Azure CLI commands for cluster and network configuration, which are cross-platform but often associated with Windows environments. There are no explicit Windows/PowerShell-only examples, and all shell commands are shown in Bash syntax. However, there is a minor bias in that Azure CLI is referenced as the main tool for cluster management, with no mention of Linux-native alternatives (such as direct use of kubectl or cloud-native tools) or explicit instructions for macOS/Linux users. No PowerShell or Windows-specific tools are used, and the examples are generally applicable to all platforms.
Recommendations
- Clarify that Azure CLI is cross-platform and provide installation instructions for Linux/macOS users.
- Mention that all Bash commands work on Linux/macOS and in Windows environments with WSL or Git Bash.
- Add a note that Azure Cloud Shell is available in-browser and works identically across platforms.
- Optionally, provide links to Azure CLI installation guides for Linux and macOS.
- Ensure that any references to saving YAML files or running Bash commands are clear for Windows users (e.g., using WSL, Git Bash, or Azure Cloud Shell).
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 Windows file paths are mentioned immediately after Linux paths, and no explicit Linux command-line example is given for checking the file. Additionally, in certificate verification output examples, Windows node names (e.g., akswinp7000000) are shown, but Linux node examples are not. However, all command-line instructions use bash/Azure CLI, which are cross-platform and primarily Linux-focused.
Recommendations
- Provide explicit Linux command-line examples for verifying TLS Bootstrapping, such as using 'ls' or 'cat' to check the existence and contents of '/var/lib/kubelet/bootstrap-kubeconfig'.
- Include Linux node name examples in output snippets alongside Windows node names to clarify parity.
- Where file paths are mentioned, clarify the OS context and provide commands for both Linux and Windows nodes.
- Ensure that any output examples or instructions referencing Windows nodes are balanced with Linux node equivalents.
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_first
Summary
The documentation provides parallel examples for both Azure CLI and Azure PowerShell throughout, but the inclusion of PowerShell is a sign of Windows bias, as PowerShell is primarily a Windows-centric tool (though it is available cross-platform). The page consistently presents Azure CLI and PowerShell examples side-by-side, but PowerShell is referenced in the metadata and tool tracking, and is given equal prominence to Azure CLI. There are no Linux-specific examples, and no mention of Bash scripting or Linux shell usage. However, Azure CLI commands are cross-platform and the documentation does not use Windows-only tools or patterns. The severity is low, as Linux/macOS users can complete all tasks using Azure CLI.
Recommendations
- Clarify that Azure CLI is fully cross-platform and preferred for Linux/macOS users.
- Add a brief note that PowerShell examples are optional and Azure CLI is recommended for Linux/macOS.
- Consider including Bash shell scripting examples or highlighting Linux-native workflows where relevant.
- Ensure that Azure CLI examples are shown first, or explicitly state that both CLI and PowerShell are supported equally.
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 PowerShell-specific workflows. Additionally, PowerShell instructions are presented before Azure CLI, which is more universally cross-platform. There is a slight bias toward Windows/PowerShell patterns, but Linux users are not blocked from completing the task.
Recommendations
- Present Azure CLI instructions before PowerShell, as CLI is more cross-platform and preferred by many Linux/macOS users.
- Add explicit notes clarifying that both Azure CLI and PowerShell can be used on Linux/macOS, and highlight CLI as the recommended option for non-Windows users.
- Ensure parity in detail between PowerShell and CLI sections, such as including troubleshooting or environment preparation steps for CLI users.
- Consider adding a brief comparison table of CLI vs PowerShell for AKS operations, emphasizing cross-platform support.
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 platform-neutral and covers storage concepts for AKS without favoring Windows-specific tools or patterns. However, in the section on mounting volumes in pods, the Windows example is presented immediately after the Linux example, which could be perceived as a minor 'windows_first' bias. No PowerShell or Windows-only tooling is referenced, and Linux parity is maintained throughout the document.
Recommendations
- Ensure Linux and Windows examples are presented with equal prominence, perhaps by grouping them together or explicitly labeling them as platform-specific.
- Consider adding clarifying notes to examples to indicate which OS they apply to, especially in YAML manifests.
- If possible, provide both Linux and Windows examples side-by-side for volume mounting to reinforce parity.
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 alongside Azure CLI and the Azure portal as migration tools, but does not provide PowerShell-specific examples. The Azure CLI is used for all command-line examples, which are cross-platform. However, Azure PowerShell is mentioned before Azure CLI in the migration step, and there is no explicit mention that Azure PowerShell is Windows-only or that Azure CLI is preferred for Linux/macOS users. All example manifests and kubectl commands are Linux-oriented, and there are no Windows-specific Kubernetes node pool references.
Recommendations
- Clarify that Azure PowerShell is primarily for Windows users and recommend Azure CLI for Linux/macOS.
- List Azure CLI before Azure PowerShell when describing migration options to prioritize cross-platform tools.
- Optionally, provide a brief note about Azure PowerShell's platform limitations.
- Ensure that all example commands are available for both Azure CLI and Azure PowerShell, or explicitly state which platforms each tool supports.
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 cluster authorized IP ranges, but consistently presents Azure CLI (Linux/macOS-friendly) first, followed by Azure PowerShell (Windows-centric). However, the PowerShell section is equally detailed and not prioritized over CLI. No Windows-only tools or patterns are mentioned, and all examples are cross-platform. There are no missing Linux/macOS examples, and the YAML manifests explicitly target Linux node pools. The overall bias is minimal and does not impede Linux/macOS users.
Recommendations
- Maintain parity by continuing to provide both Azure CLI and Azure PowerShell examples.
- Consider clarifying that Azure CLI works on Windows, Linux, and macOS, while PowerShell is primarily for Windows users (though available cross-platform).
- If possible, add a short note for each command section indicating platform compatibility.
- Ensure future troubleshooting or advanced sections do not default to Windows-only tools or 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
powershell_heavy
Summary
The documentation is generally cross-platform and AKS-centric, with most examples using Linux conventions and tools (bash, Azure CLI, kubectl). However, there are minor signs of Windows bias: Windows paths and PowerShell/CMD syntax are mentioned in a few places, and Windows-specific instructions sometimes appear before Linux equivalents or are highlighted in notes. The section on Windows containers provides both Linux/Mac and Windows PowerShell/CMD commands, but Linux is shown first. Overall, Linux parity is strong, but Windows is occasionally foregrounded.
Recommendations
- Ensure Linux/macOS examples are always shown first, with Windows-specific notes clearly separated.
- Where Windows paths or PowerShell/CMD syntax are mentioned, provide equivalent Linux/macOS examples side-by-side.
- Clarify when instructions are Windows-only or Linux-only to avoid confusion.
- Review output examples to ensure they are not Windows-centric unless the section is explicitly about Windows containers.
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation provides both Azure CLI and PowerShell options for some prerequisite steps, but the PowerShell tool is mentioned alongside Azure CLI and portal, and a PowerShell cmdlet is referenced for subnet listing. However, all actual operational examples (creating manifests, deploying, querying services) use kubectl and Azure CLI, which are cross-platform. The PowerShell references are not exclusive or prioritized, but their presence without equivalent Linux/macOS alternatives (e.g., Bash, shell scripting) may create minor friction for non-Windows users.
Recommendations
- When referencing PowerShell cmdlets (e.g., Get-AzVirtualNetworkSubnetConfig), always provide the equivalent Azure CLI command (which is already present for subnet listing).
- Consider clarifying that Azure CLI is fully cross-platform and preferred for Linux/macOS users, and PowerShell is optional for Windows users.
- If mentioning PowerShell, ensure Linux/macOS users are not left wondering if a step is Windows-only; explicitly state that Azure CLI is recommended for non-Windows platforms.
- Avoid listing PowerShell before Azure CLI unless the task is Windows-specific.
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. Azure CLI is cross-platform (Linux, macOS, Windows), while Azure PowerShell is primarily used on Windows (though it is available on Linux/macOS). The examples are presented in parallel tabs, but the introductory section lists Azure CLI, Azure PowerShell, and Azure Portal in that order, and PowerShell examples are given equal prominence. There are no Windows-only tools or patterns, and no missing Linux/macOS examples, but PowerShell is a Windows-centric tool and its inclusion alongside CLI may create minor bias.
Recommendations
- Clarify that Azure CLI is the recommended cross-platform tool for Linux/macOS users.
- Consider adding a note that Azure PowerShell is available on Linux/macOS, but Azure CLI is more commonly used on those platforms.
- Ensure that Azure CLI examples are shown first or marked as the default for cross-platform scenarios.
- Optionally, add a Bash shell example for Linux users (though Azure CLI commands are already suitable).
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 is largely cross-platform, focusing on Azure CLI and kubectl commands, which are available on Linux, macOS, and Windows. There are brief references to Windows and PowerShell environments in notes about shell differences, but no Windows-specific examples, tools, or patterns are prioritized or exclusively presented.
Recommendations
- Clarify that all CLI and kubectl commands work on Linux, macOS, and Windows.
- If shell differences are significant, provide example commands for both Bash (Linux/macOS) and PowerShell (Windows), or link to relevant shell-specific guidance.
- Consider adding a brief section or note for macOS users if there are any unique considerations.
Aks
Subscribe to Azure Kubernetes Service events with Azure Event Grid
...s-docs/blob/main/articles/aks/quickstart-event-grid.md
Low Priority
View Details â
Detected Bias Types
windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all steps, ensuring cross-platform parity. However, in each section, Azure CLI (Linux/macOS-friendly) examples are presented before Azure PowerShell (Windows-centric) examples. No Windows-only tools or patterns are mentioned, and Linux/macOS users can complete all tasks using Azure CLI. There are no missing Linux examples or Windows-exclusive instructions.
Recommendations
- Maintain the current structure, as Azure CLI is presented first and is cross-platform.
- Consider explicitly stating that Azure CLI commands work on Linux, macOS, and Windows, while Azure PowerShell is primarily for Windows users.
- Add a brief note in the prerequisites clarifying the cross-platform nature of Azure CLI and the Windows-centric nature of Azure PowerShell.
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
windows_first
Summary
The documentation provides parity between Azure CLI, Azure PowerShell, and Azure portal methods for upgrading AKS clusters. However, Azure PowerShell examples are presented alongside Azure CLI examples throughout, and PowerShell version requirements are mentioned in the 'Before you begin' section. Azure PowerShell is a Windows-centric tool, and its inclusion may suggest a Windows bias, especially since PowerShell is not as commonly used on Linux/macOS. However, Azure CLI is cross-platform and is always presented first, and all examples are available for Linux/macOS users. No critical tasks are Windows-only, and Linux parity is maintained.
Recommendations
- Clarify that Azure CLI is recommended for Linux/macOS users, and PowerShell is primarily for Windows users.
- Consider adding a note in the 'Before you begin' section indicating that Azure CLI is cross-platform and PowerShell is most commonly used on Windows.
- Ensure that Azure CLI examples remain first in all sections to reinforce Linux/macOS parity.
- Optionally, provide bash shell script examples for common tasks to further support Linux/macOS 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
powershell_heavy
windows_tools
Summary
The documentation provides examples and instructions for both Linux and Windows node pools in AKS, but Windows-specific steps (such as registering feature flags and creating Windows admin credentials) are given prominent, detailed sections. Windows node pool creation is described in depth, including preview features and CLI steps, while Linux instructions are more concise. Some CLI commands (az CLI) are cross-platform, but Windows-specific tools and concepts (HNS ACLPolicies, Windows admin username/password) are mentioned before or in more detail than their Linux equivalents. However, Linux parity is generally maintained, and most critical tasks are achievable on Linux.
Recommendations
- Ensure Linux and Windows instructions are equally detailed and structured.
- Where Windows-specific steps are described (feature flag registration, admin credential creation), provide clear Linux equivalents or clarify that these steps are not needed for Linux.
- Avoid placing Windows node pool instructions before Linux unless the feature is Windows-only.
- Consider grouping Linux and Windows instructions separately to avoid confusion.
- Explicitly state which steps are OS-specific and which are cross-platform.