165
Pages Scanned
17
Pages Flagged
165
Changed Pages
10.3%
% Pages Flagged
Live Progress
đ´ Connecting...
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:08
Scan Information
Started At: 2026-03-05 00:00:08
Finished At: In Progress
Status: in_progress
Target Repo: Azure Aks
Current Phase: discovery
Files Queued: 165
Files Completed: 165
Problematic Pages
17 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 documentation provides parallel instructions for Azure CLI, Azure PowerShell, and Azure Developer CLI, but PowerShell examples and terminology are prominent throughout. PowerShell is a Windows-centric tool, and its inclusion as a primary option may create friction for Linux/macOS users. Additionally, PowerShell instructions are often given equal prominence to Azure CLI, rather than Azure CLI being presented as the default cross-platform method. There are no explicit Linux/macOS-specific examples or notes, and the documentation does not clarify that PowerShell is not natively available on most Linux/macOS systems.
Recommendations
- Clearly indicate that Azure CLI is the default, cross-platform method and recommend it for Linux/macOS users.
- Add explicit notes or sections for Linux/macOS users, clarifying that PowerShell is optional and not required.
- Consider presenting Azure CLI instructions first, followed by PowerShell as an alternative for Windows users.
- Include links or brief instructions for installing Azure CLI and kubectl on Linux/macOS.
- Where possible, avoid PowerShell-specific terminology in general guidance, or clarify its platform limitations.
Create Pull Request
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 generally provides cross-platform instructions and download links for Windows, macOS, and Linux. However, there are minor Windows biases: Windows keyboard shortcuts are often listed first, and some tips (e.g., WSL configuration) are Windows-specific. There are no Linux/macOS-specific troubleshooting tips or examples, and some instructions (e.g., Docker credential issues) mention Windows limitations without offering equivalent Linux/macOS guidance. All CLI examples use bash syntax, which is standard for Linux/macOS but also works in Windows with WSL or PowerShell. Overall, parity is good, but Linux/macOS users may find minor friction due to Windows-first ordering and lack of platform-specific troubleshooting.
Recommendations
- Alternate keyboard shortcut ordering (sometimes list macOS/Linux first)
- Add Linux/macOS-specific troubleshooting tips, especially for Docker and credential management
- Include explicit PowerShell examples for Windows users, and bash examples for Linux/macOS users, where relevant
- Clarify any platform-specific limitations or requirements for all platforms, not just Windows
- Ensure download instructions and links are equally prominent for all platforms
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 troubleshooting documentation provides both Windows/macOS and Linux solutions for Docker-related issues, but Windows/macOS steps (using Docker Desktop) are consistently listed before Linux steps. Windows tooling (Docker Desktop) is referenced as the primary solution for Windows/macOS, while Linux-specific commands are provided separately. Azure CLI and kubectl commands are platform-neutral, but minor ordering bias exists.
Recommendations
- Alternate the order of Windows/macOS and Linux instructions to avoid implicit prioritization.
- Explicitly state that all steps apply equally to Linux, macOS, and Windows where possible.
- Provide parity in troubleshooting details, ensuring Linux instructions are as comprehensive as Windows/macOS.
- Consider grouping platform-specific instructions under clear subheadings (e.g., 'Linux', 'Windows/macOS') for clarity.
Aks
Certificate Rotation in Azure Kubernetes Service (AKS)
...ks-docs/blob/main/articles/aks/certificate-rotation.md
Low Priority
View Details â
Detected Bias Types
windows_first
missing_linux_example
Summary
The documentation is generally cross-platform and AKS is a Linux-first service, but there are minor indications of Windows bias. In the section 'Verify TLS Bootstrapping is enabled on current agent node pool', the Windows file path ('C:\k\bootstrap-config') is mentioned immediately after the Linux path, and no additional Windows-specific commands or examples are provided elsewhere. However, most examples and instructions are Linux-centric (bash, Azure CLI, kubectl), and Windows is only referenced for file paths. There are no PowerShell examples or Windows-only tools used.
Recommendations
- Ensure that Windows file paths are not mentioned before Linux paths unless Windows is the primary target.
- Where Windows is referenced, consider providing equivalent PowerShell or Windows command-line examples for certificate inspection or rotation, if applicable.
- Clarify that most AKS clusters are Linux-based and that Windows node pools are a special case, linking to Windows node pool documentation for Windows-specific tasks.
- Add a brief note explaining that most commands are for Linux-based clusters, and Windows node pool users should refer to the Windows node pool documentation for any differences.
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 PowerShell is a Windows-centric tool and is featured equally alongside Azure CLI. There are no Linux-specific shell examples (e.g., Bash), and PowerShell is presented as a primary option despite its limited adoption on Linux/macOS. In some sections, PowerShell is listed after CLI, but overall, the parity is maintained between CLI and PowerShell, with no explicit Linux shell or tooling examples.
Recommendations
- Clarify that Azure CLI commands are cross-platform and preferred for Linux/macOS users.
- Add explicit Bash shell examples for setting environment variables and running Azure CLI commands (e.g., export MYACR=mycontainerregistry instead of MYACR=mycontainerregistry for Bash).
- Mention that PowerShell examples are primarily for Windows users, and recommend Azure CLI for Linux/macOS.
- Consider adding a section or note for Linux/macOS users, highlighting any differences or additional steps (such as file creation commands, environment variable syntax, etc.).
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
windows_example
Summary
The documentation is generally cross-platform and neutral, but there is a minor bias in the 'Persistent volume claims' section, where Windows container mounting instructions and YAML examples are presented immediately after Linux-style examples, without clear separation or parity. The Windows example is given, but no equivalent Linux example is provided for mounting multiple volumes. Additionally, the Windows-specific instructions are not clearly labeled as such, which could cause confusion for Linux/macOS users.
Recommendations
- Clearly label Windows-specific YAML examples and instructions as 'For Windows containers' and Linux-specific examples as 'For Linux containers'.
- Provide equivalent Linux examples for mounting multiple volumes, if applicable.
- Ensure that Windows and Linux instructions/examples are presented in parallel sections or tables, rather than Windows instructions being appended after Linux examples.
- Add clarifying notes when a feature or syntax is Windows-only, to avoid confusion.
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 instructions for configuring Azure CNI networking in AKS using three methods: Azure portal, Azure PowerShell, and Azure CLI. While all methods are presented, the PowerShell section is prominent and includes detailed instructions for installation and usage, which may be perceived as Windows-centric. Additionally, PowerShell is listed before CLI, which is more commonly used on Linux/macOS. However, the CLI section is present and includes full examples, and PowerShell installation instructions reference macOS and Linux, mitigating some bias.
Recommendations
- Present Azure CLI instructions before PowerShell, as CLI is the default cross-platform tool.
- Clarify that Azure PowerShell can be used on Linux/macOS, and provide explicit examples of running PowerShell on those platforms.
- Add a note highlighting that Azure CLI is recommended for Linux/macOS users.
- Ensure parity in example detail and troubleshooting tips between PowerShell and CLI sections.
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 migration option alongside Azure CLI and Azure Portal, but does not provide Linux-specific guidance or examples. Azure CLI is used for all command-line examples, which is cross-platform, but Azure PowerShell is mentioned before Azure CLI in the migration section. No PowerShell-specific examples are given, and all YAML and kubectl examples are Linux-oriented. There are no missing Linux examples, but the mention of Azure PowerShell as a migration tool without clarifying its cross-platform support may cause confusion.
Recommendations
- Clarify that Azure PowerShell is available on Linux and macOS, or link to installation instructions for non-Windows platforms.
- List Azure CLI before Azure PowerShell when describing migration options, as CLI is more commonly used cross-platform.
- Explicitly state that all command-line steps can be performed on Linux/macOS using Azure CLI.
- If referencing Azure PowerShell, provide a note about its cross-platform compatibility or suggest Azure CLI as the preferred tool for Linux/macOS users.
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, but there are minor signs of Windows bias. Windows paths and conventions are mentioned first or alongside Linux equivalents in several places, and Windows-specific instructions are provided for mounting Azure Files in Windows containers. Azure CLI is used throughout, which is available on Linux and macOS, but some commands and examples reference Windows path conventions or tools before Linux equivalents.
Recommendations
- When referencing mount paths, ensure Linux and Windows conventions are presented equally, ideally with Linux examples first since AKS clusters are predominantly Linux-based.
- Where commands differ between platforms (e.g., PowerShell vs Bash), provide both examples and clarify which is for which OS.
- In sections about Windows containers, explicitly state that the instructions are Windows-specific and provide Linux alternatives where relevant.
- Review output examples and ensure they are not exclusively Windows-formatted unless the section is Windows-specific.
- Consider including a brief note at the start clarifying that most examples are Linux-based unless otherwise stated.
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
windows_first
Summary
The documentation is generally cross-platform, focusing on Azure CLI and Bicep for managing Dapr on AKS or Arc-enabled Kubernetes clusters. However, there is a minor bias in the 'List the CRDs in your cluster' section, where the example uses 'kubectl get crds | findstr dapr.io'. 'findstr' is a Windows command-line tool, and no equivalent Linux/macOS example (such as using 'grep') is provided. Additionally, the Windows-specific example appears without mentioning Linux/macOS alternatives.
Recommendations
- Provide both Windows and Linux/macOS command examples when filtering kubectl output. For example, show both 'kubectl get crds | findstr dapr.io' (Windows) and 'kubectl get crds | grep dapr.io' (Linux/macOS).
- Explicitly state that the Azure CLI and Bicep commands are cross-platform and supported on Windows, Linux, and macOS.
- Review documentation for any other subtle Windows-first patterns, such as command syntax or tool references, and ensure parity in examples.
Low Priority
View Details â
Detected Bias Types
windows_tools
windows_first
Summary
The documentation provides both Azure CLI and PowerShell options for prerequisite steps, but consistently mentions Azure PowerShell alongside Azure CLI and the Azure Portal when describing how to create an AKS cluster. It also references PowerShell cmdlets (e.g., Get-AzVirtualNetworkSubnetConfig) as alternatives to Azure CLI commands for listing subnets. However, all actual step-by-step examples and YAML manifests use cross-platform tools (kubectl, Azure CLI), and there are no PowerShell-specific walkthroughs or Windows-only commands for the main task. The bias is minor and mostly in the order and inclusion of PowerShell references.
Recommendations
- When listing options for creating an AKS cluster, mention Azure CLI and Portal first, and clarify that Azure PowerShell is primarily for Windows users.
- Where PowerShell cmdlets are referenced (e.g., Get-AzVirtualNetworkSubnetConfig), provide equivalent Linux/macOS commands (such as Azure CLI) before or alongside PowerShell.
- Consider adding a note that all main walkthrough steps use cross-platform tools and are suitable for Linux/macOS users.
- If referencing PowerShell, clarify its platform specificity and provide links to Azure CLI documentation as the primary cross-platform option.
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 consistently lists Azure PowerShell after Azure CLI and offers no Linux/macOS-specific guidance. The PowerShell examples are included even though PowerShell is primarily used on Windows, and there is no mention of Bash or other Linux-native tools. However, the main workflow is portal-based and platform-neutral, and the Azure CLI examples are suitable for Linux/macOS users.
Recommendations
- Explicitly state that Azure CLI commands work on Linux, macOS, and Windows, while Azure PowerShell is primarily for Windows users.
- Consider adding Bash-specific or Linux/macOS-specific instructions for retrieving the public IP address (e.g., using 'curl' or 'dig'), or clarify that the Azure CLI example is cross-platform.
- If possible, reorder the troubleshooting tabs so that Azure CLI (cross-platform) is shown first, and PowerShell (Windows-centric) second.
- Add a note clarifying that PowerShell is available on Linux/macOS, but CLI is generally preferred for those platforms.
Aks
Use a Service Principal with Azure Kubernetes Service (AKS)
...blob/main/articles/aks/kubernetes-service-principal.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all major operations, but PowerShell is featured equally and sometimes with more detailed steps (e.g., decrypting secrets, creating PSCredential objects). Azure PowerShell is primarily used on Windows, and its inclusion may create friction for Linux/macOS users. However, Azure CLI examples are present throughout, and the documentation does not rely on Windows-only tools or patterns. The order of examples sometimes puts PowerShell before CLI, and there are minor references to Windows conventions (e.g., PowerShell secure strings), but Linux parity is generally maintained.
Recommendations
- Ensure Azure CLI examples are always shown first, as CLI is cross-platform and preferred for Linux/macOS users.
- Clarify that Azure PowerShell is primarily for Windows users, and recommend Azure CLI for Linux/macOS.
- Where PowerShell-specific steps are given (e.g., decrypting secure strings), provide equivalent CLI guidance or note that such steps are unnecessary with CLI.
- Explicitly state that all commands can be run from Linux/macOS terminals using Azure CLI.
- Add a brief section or note highlighting cross-platform compatibility and preferred tools for each OS.
Aks
Connect to Azure Kubernetes Service (AKS) cluster nodes
...s/azure-aks-docs/blob/main/articles/aks/node-access.md
Low Priority
View Details â
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides parity for both Linux and Windows node access in AKS, with clear sections for each OS. However, Windows-specific instructions (such as host process containers and PowerShell usage) are presented in detail, and Windows node access methods are described after Linux/macOS methods. PowerShell commands are used heavily for Windows node troubleshooting, but Linux users are given bash-based examples and SSH instructions. The order of presentation slightly favors Linux, but Windows instructions are comprehensive and not exclusive.
Recommendations
- Ensure Linux and Windows sections are equally prominent and clearly separated.
- Where possible, provide Linux/macOS equivalents for any troubleshooting commands or scripts shown for Windows nodes.
- Add explicit notes when a method is Windows-only or Linux-only to avoid confusion.
- Consider including a summary table comparing Linux and Windows node access methods for quick reference.
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 for all Azure-related steps, but PowerShell is featured equally alongside CLI, which is more commonly used on Linux/macOS. The PowerShell examples and terminology may create friction for Linux/macOS users, as PowerShell is primarily a Windows-centric tool, though it is available cross-platform. There are no explicit Windows-only tools or patterns, and the core Kubernetes and Helm steps use standard bash commands. Azure CLI is presented first in each section, which is positive for Linux parity.
Recommendations
- Clarify that Azure PowerShell is optional and primarily for users familiar with PowerShell; Azure CLI is recommended for Linux/macOS.
- Consider labeling Azure CLI as the default or preferred method for cross-platform users.
- Add a brief note at the start of the 'Prerequisites' section indicating that Azure CLI is the most common tool for Linux/macOS, while PowerShell is an alternative.
- Ensure that bash commands (e.g., git, helm, kubectl) are clearly marked as cross-platform.
- Optionally, provide a table or summary comparing Azure CLI and PowerShell for users to choose their preferred 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
Summary
The documentation provides both Linux and Windows examples for AKS network policy management, but Windows-specific instructions (such as registering preview features and creating Windows admin credentials) are presented in a dedicated section and sometimes before Linux equivalents. However, all CLI examples use Azure CLI and Bash, which are cross-platform, and Kubernetes commands are standard. There is a slight bias in the ordering and prominence of Windows-specific instructions, but Linux parity is generally maintained.
Recommendations
- Ensure Linux and Windows instructions are presented with equal prominence and clarity.
- When describing steps for both OS types, use parallel structure and headings (e.g., 'Create an AKS cluster with Azure Network Policy Manager (Linux)' and '(Windows)').
- If Windows-specific steps are required, clarify their purpose and provide Linux equivalents or explicitly state when they are not needed.
- Consider grouping OS-specific instructions together and referencing them from a main workflow, rather than interleaving.
- Add explicit notes when a feature or step is only relevant to one OS, to avoid confusion.
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 uses Azure CLI examples throughout, which are cross-platform. However, the environment variable syntax shown ($VARIABLE) is Bash-style and not Windows CMD/PowerShell, but the page does not explicitly mention Linux/macOS compatibility or provide alternative Windows PowerShell syntax. There is no evidence of Windows-specific tools or patterns, but the lack of explicit Linux/macOS guidance and the absence of PowerShell/CMD examples could create minor friction for Windows users. No Linux bias is present, but Windows bias is minimal and limited to the order and implicit assumption of Bash usage.
Recommendations
- Add a note clarifying that Azure CLI commands work on Windows, Linux, and macOS.
- Provide PowerShell syntax for environment variables alongside Bash examples, or link to Azure CLI cross-platform usage documentation.
- Explicitly mention that the instructions are platform-agnostic and that Azure CLI is supported on all major OSes.