Azure Arc
465
Total Pages
253
Linux-Friendly Pages
212
Pages with Bias
45.6%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
2334 issues found
Showing 226-250 of 2334 flagged pages
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation demonstrates Windows bias by referencing Windows-specific tools (ktpass.exe), providing a PowerShell script, and detailing password reset steps using Windows GUI tools (Server Manager, Active Directory Users and Computers) without mentioning Linux alternatives. The Linux bash script is mentioned, but Windows tools and workflows are described first and in more detail, while Linux domain controller management is omitted.
Recommendations
- Add instructions for resetting the Active Directory user password using Linux tools (e.g., samba-tool, ldapmodify) for environments where the domain controller is Samba-based or managed from Linux.
- Provide parity in example scripts and workflows, ensuring bash/Linux instructions are as detailed as PowerShell/Windows ones.
- Mention Linux equivalents for Active Directory management, such as using RSAT on Linux, or direct LDAP commands.
- Reorder sections to present Linux and Windows options equally, or clarify which environments each applies to.
- Include troubleshooting steps for Linux-based domain controllers and clarify any differences in keytab rotation processes.
Create Pull Request
High Priority
View Details →
Detected Bias Types
Windows First
Azure Heavy
Missing Linux Example
Summary
The documentation page demonstrates a bias towards Azure and Windows-centric environments. Storage class examples and recommendations are almost exclusively focused on Azure Kubernetes Service (AKS), with detailed coverage of Azure-specific storage classes and tools. There is minimal mention of Linux-native storage solutions or patterns, and no explicit Linux or open-source example is provided. The documentation also presents Azure/Windows options before AWS and GCP, and does not offer parity in terms of Linux command-line or storage configuration examples.
Recommendations
- Include examples of configuring storage classes using Linux-native tools and environments, such as NFS, Ceph, or local SSDs on Linux nodes.
- Provide sample YAML manifests for storage classes and persistent volumes that are not Azure-specific, demonstrating usage on generic Kubernetes clusters (including on-premises Linux clusters).
- Add explicit Linux command-line examples (e.g., using bash, sed, jq) for configuration tasks, not just Azure CLI.
- Balance the order of cloud provider recommendations, and include open-source solutions (e.g., Longhorn, Rook/Ceph) as first-class options.
- Reference Linux documentation and best practices for storage configuration alongside Azure/Windows resources.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation provides examples for PowerShell and Windows, often listing PowerShell first and sometimes omitting explicit Linux/macOS instructions or relegating them to secondary tabs. Windows-specific tools and patterns (e.g., Task Scheduler, .cmd/.bat scripts) are mentioned before or alongside Linux equivalents, but Linux automation (cron, shell scripts) is only briefly covered. Some sections (e.g., role assignment, managed identity retrieval) have 'N/A' for Windows, but PowerShell is used as the primary scripting example, and Windows environment variable syntax is shown. Linux-specific guidance is less detailed, and Linux-first patterns are not emphasized.
Recommendations
- Provide Linux/macOS examples with equal prominence and detail as Windows/PowerShell examples, including shell scripting and automation patterns.
- List Linux/macOS instructions before or alongside Windows/PowerShell instructions to avoid Windows-first bias.
- Expand Linux automation guidance (e.g., cron usage, systemd timers) and provide sample scripts for Linux environments.
- Include troubleshooting and environment setup steps specific to Linux, such as permissions, package dependencies, and common issues.
- When mentioning Windows tools (e.g., Task Scheduler), also mention Linux equivalents (cron, systemd) with equal detail.
- Avoid using PowerShell as the default scripting language; provide Bash/sh examples where appropriate.
- Ensure all steps (e.g., managed identity retrieval, role assignment) have clear, working Linux/macOS instructions, not just 'N/A' for Windows.
Azure Arc
Upload usage data, metrics, and logs to Azure
...e-arc/data/upload-metrics-and-logs-to-azure-monitor.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides examples for Windows, macOS/Linux, and PowerShell, but Windows examples and notes are presented first in each section. There are specific notes about Windows quoting conventions and environment variable setting, and PowerShell is given its own tab, reinforcing a Windows-centric approach. References to related content include a PowerShell-specific link for service principals. There is no evidence of missing Linux examples, but the ordering and emphasis favor Windows users.
Recommendations
- Present Linux/macOS examples before or alongside Windows examples, rather than always listing Windows first.
- Include Bash scripting examples or references where PowerShell is mentioned, to improve parity for Linux users.
- Add links to Linux-specific documentation for service principal management, not just PowerShell.
- Clarify that Azure CLI commands are cross-platform and highlight any platform-specific differences equally.
- Review related content links to ensure parity between Windows/PowerShell and Linux/Bash resources.
Azure Arc
Configure Machine to Manage Arc-Enabled Kubernetes Cluster
...rticles/azure-arc/edge-rag/configure-driver-machine.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation is heavily biased toward Windows, providing only a Windows/Powershell script and instructions. All examples, folder paths, and installation steps use Windows conventions and tools (e.g., .msi installers, C:\ paths, PowerShell scripting). There is no mention of Linux or cross-platform alternatives, nor are equivalent Linux shell commands or installation instructions provided.
Recommendations
- Add equivalent Linux setup instructions, including a Bash shell script for Ubuntu/CentOS.
- Include Linux-specific download and installation commands for Azure CLI, kubectl, and Helm.
- Present both Windows and Linux examples side-by-side, or clearly indicate platform-specific sections.
- Reference Linux file paths and environment variable management (e.g., ~/.bashrc, /usr/local/bin).
- Mention cross-platform compatibility of Azure CLI, kubectl, and Helm, and link to official installation guides for both Windows and Linux.
Azure Arc
Sample - Enable GPU for AKS on Azure Arc
...lob/main/articles/azure-arc/edge-rag/enable-gpu-aks.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Missing Linux Example
Windows First
Summary
The documentation page provides only a Windows PowerShell script for enabling GPU on AKS enabled by Azure Arc. It exclusively uses Windows-specific tools (e.g., Get-PnpDevice, pnputil, Restart-Service) and patterns, with no mention or example for Linux hosts. There is no guidance for Linux users, and Windows tooling is presented as the default and only option.
Recommendations
- Add equivalent Linux instructions and sample scripts (e.g., using lspci, lsmod, modprobe, systemctl, etc.) for GPU enablement.
- Explicitly state platform requirements and clarify if the procedure is Windows-only, or provide parity for Linux-based Azure Arc hosts.
- Include a section comparing Windows and Linux approaches, highlighting differences and prerequisites for each.
- Ensure related content links include Linux-specific documentation if available.
Azure Arc
Prepare AKS Cluster on Azure Local for Edge RAG Preview Enabled by Azure Arc
...ain/articles/azure-arc/edge-rag/prepare-aks-cluster.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias. All command-line examples use PowerShell syntax, and instructions reference Windows-specific tools and services (e.g., Hyper-V, PowerShell cmdlets). There are no Linux shell (bash) equivalents provided, nor are Linux management scenarios discussed. The guidance for setting up a management machine only links to Windows setup scripts, omitting Linux or macOS alternatives.
Recommendations
- Provide equivalent bash shell commands for all PowerShell examples, especially for az CLI usage and node pool creation.
- Include instructions for managing AKS Arc clusters from Linux and macOS machines, with links to relevant setup guides.
- Mention Linux virtualization technologies (such as KVM) where Hyper-V is referenced, or clarify platform requirements.
- Ensure that references to scripts or configuration guides include both Windows and Linux versions.
- Add notes or sections highlighting cross-platform support and any platform-specific caveats.
Azure Arc
Configure DNS for Edge RAG Preview Enabled by Azure Arc
...s/blob/main/articles/azure-arc/edge-rag/prepare-dns.md
High Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Windows Tools
Summary
The documentation page demonstrates Windows bias by exclusively providing instructions for editing the hosts file using Windows-specific paths and tools (Notepad, C:\Windows\System32\drivers\etc\hosts), without mentioning Linux or macOS equivalents. No examples or guidance are given for non-Windows platforms, despite their prevalence in cloud and edge environments.
Recommendations
- Add instructions for editing the hosts file on Linux (e.g., /etc/hosts) and macOS.
- Include examples using common Linux text editors (e.g., nano, vim) and note the need for sudo/root privileges.
- Present platform-specific instructions in parallel or as tabs, ensuring equal visibility for Windows, Linux, and macOS.
- Avoid assuming Windows as the default environment; clarify that steps may differ by OS.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in its Azure CLI section by exclusively providing PowerShell-based examples and variable assignments, which are specific to Windows environments. There are no bash or Linux shell equivalents, and the use of PowerShell syntax may confuse or exclude Linux/macOS users. The ordering and example structure implicitly prioritize Windows users, with no mention of cross-platform compatibility or alternative shell instructions.
Recommendations
- Provide equivalent Azure CLI examples using bash syntax, including variable assignments and command execution, to support Linux/macOS users.
- Explicitly state that the Azure CLI commands can be run on any platform, and clarify any platform-specific differences.
- Add a tabbed section for 'Bash (Linux/macOS)' alongside 'PowerShell (Windows)' in the CLI instructions.
- Avoid using PowerShell-specific syntax (e.g., `$variable = value`) as the sole example; include bash-style variable assignment (e.g., `variable=value`).
- Mention prerequisites or installation steps for Azure CLI on Linux/macOS, if relevant.
Azure Arc
Configure Authentication for Edge RAG Preview Enabled by Azure Arc
.../articles/azure-arc/edge-rag/prepare-authentication.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Missing Linux Example
Summary
The documentation page demonstrates Windows bias by referencing Windows-specific tools (e.g., Windows Notepad) as the default for storing configuration values, and by exclusively using Azure Portal GUI instructions without mentioning command-line alternatives (such as Azure CLI or PowerShell for Windows, Bash for Linux). There are no examples or guidance for Linux users, nor are cross-platform tools or workflows discussed.
Recommendations
- Replace references to Windows-only tools (e.g., Notepad) with cross-platform alternatives (e.g., 'a text editor of your choice, such as Notepad, nano, or vim').
- Provide command-line instructions using Azure CLI, which works on both Windows and Linux, alongside GUI steps.
- Explicitly mention that the steps can be performed on any OS and highlight platform-agnostic tools.
- Include screenshots or examples for Linux environments where relevant.
- Add a note or section for Linux/macOS users to clarify any differences in workflow or tool usage.
Azure Arc
Verify Contributor Role for Edge RAG Preview Enabled by Azure Arc
...s/azure-arc/edge-rag/prepare-contributor-permission.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Missing Linux Example
Windows Tools
Summary
The documentation page provides command examples using PowerShell syntax and references the 'az' CLI commands in a way that suggests Windows usage, without mentioning or providing Linux/macOS shell equivalents. There is no explicit guidance or examples for Linux users, such as bash/zsh syntax or platform-specific considerations, which may make the instructions less accessible to non-Windows users.
Recommendations
- Include Linux/macOS shell examples (e.g., bash/zsh) alongside PowerShell commands.
- Clarify that the 'az' CLI is cross-platform and provide instructions for installing and running it on Linux/macOS.
- Avoid assuming PowerShell as the default shell; use generic CLI syntax or provide both PowerShell and bash examples.
- Mention any platform-specific prerequisites or differences in command usage, if applicable.
Azure Arc
Install Networking and Observability Components for Edge RAG Preview Enabled by Azure Arc
...azure-arc/edge-rag/prepare-networking-observability.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page exclusively provides PowerShell-based examples and commands, assuming the user is on Windows or using PowerShell. There are no Bash, Linux shell, or cross-platform CLI examples. Windows-centric tools and patterns (e.g., PowerShell variables, 'start-sleep') are used throughout, and no Linux alternatives or instructions are mentioned.
Recommendations
- Provide equivalent Bash/Linux shell command examples alongside PowerShell, especially for az CLI and kubectl/helm operations.
- Clarify platform requirements and note that commands can be run from Linux/macOS terminals as well, adjusting syntax as needed.
- Avoid using PowerShell-specific constructs (e.g., $variables, start-sleep) without offering cross-platform alternatives.
- Explicitly mention that Azure CLI, kubectl, and helm are cross-platform, and show how to use them from Linux/macOS.
- Add a section or note for Linux users, including installation prerequisites and environment setup.
Azure Arc
Use cluster connect to securely connect to Azure Arc-enabled Kubernetes clusters.
.../main/articles/azure-arc/kubernetes/cluster-connect.md
High 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 the PowerShell examples are given equal prominence as CLI, and in some cases, PowerShell-specific syntax is used (e.g., variable assignment, base64 decoding). There are no explicit Linux shell examples (e.g., bash, zsh), and the use of PowerShell for environment variable handling and token extraction may not be directly applicable to Linux/macOS users. The documentation does not mention Linux-specific tools or patterns, and the shell commands (kubectl, echo, etc.) are shown in a way that may be ambiguous for non-Windows users.
Recommendations
- Add explicit bash/zsh examples for all steps involving environment variables, token extraction, and file manipulation, especially for Linux/macOS users.
- Clarify which commands are cross-platform (e.g., kubectl, az CLI) and provide OS-specific notes where syntax differs.
- For variable assignment and token extraction, show both PowerShell and bash syntax side-by-side, or use tabs for 'Linux/macOS (bash)' and 'Windows (PowerShell)'.
- Avoid using PowerShell-specific syntax (e.g., $TOKEN = ...) without providing the bash equivalent.
- Mention that Azure CLI and kubectl are cross-platform and provide installation instructions for Linux/macOS as well as Windows.
Azure Arc
Requirements for Edge RAG Preview, Enabled by Azure Arc
.../blob/main/articles/azure-arc/edge-rag/requirements.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias by listing Windows Server NFS setup guides before Linux equivalents, referencing Windows VM sizes and links, and mentioning a Windows machine as a management host. There is a lack of parity in example depth and ordering, with Windows resources and links often appearing first or exclusively. Linux management scenarios and tools are not described in detail, and some references (e.g., VM sizes) are Windows-centric.
Recommendations
- Present Linux and Windows setup guides in parallel, or list Linux first when the default OS is Linux.
- Add explicit instructions and examples for managing Azure Arc-enabled Kubernetes clusters from Linux hosts, including installation of Azure CLI, kubectl, and Helm on Linux.
- Include Linux VM sizing references and links, not just Windows Server VM sizes.
- Ensure that all tooling and configuration steps (e.g., driver machine setup) have Linux-specific guidance and troubleshooting.
- Review all links and examples to ensure Linux parity and avoid Windows-first ordering.
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by providing all command-line examples in PowerShell syntax, referencing Azure PowerShell and Azure CLI usage with PowerShell variables, and omitting equivalent Linux shell (bash) examples. The instructions assume the use of PowerShell, which is native to Windows, and do not mention or demonstrate how to perform the same actions on Linux or macOS systems. Additionally, the use of PowerShell syntax for kubectl commands is atypical for Linux environments.
Recommendations
- Add bash shell examples alongside PowerShell examples for all command-line instructions.
- Explicitly mention that the steps can be performed on Linux/macOS and provide any necessary adjustments (e.g., environment variable syntax differences).
- Use generic CLI syntax (e.g., az, kubectl) without PowerShell-specific variable assignment when possible.
- Clarify that Azure CLI and kubectl are cross-platform tools and provide installation or usage notes for Linux/macOS users.
- Consider reordering examples to present bash/Linux instructions first or in parallel tabs.
Azure Arc
Customer intent: As a cloud administrator, I want to list all Azure Arc-enabled Kubernetes resources, so that I can monitor and manage the connected clusters and their configurations effectively.
...les/azure-arc/includes/azure-arc-enabled-kubernetes.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides command-line examples only for Azure CLI and Azure PowerShell, with PowerShell being a Windows-centric tool. There are no explicit Linux shell (bash, zsh) or scripting examples, nor is there mention of Linux-specific patterns or tools. The PowerShell tab is always present and listed before the portal tab, which may reinforce a Windows-first perspective. No Linux-specific guidance or troubleshooting is included.
Recommendations
- Add bash/zsh shell examples for each scenario, using Azure CLI commands as they would be run on Linux.
- Explicitly state that Azure CLI commands work cross-platform and provide any necessary Linux-specific notes (e.g., quoting, environment variables).
- Include troubleshooting or usage notes for Linux environments, such as package installation or authentication differences.
- Consider reordering tabs so that Azure CLI (cross-platform) is listed before PowerShell, or clarify the cross-platform nature of CLI.
- If PowerShell is included, mention PowerShell Core and its availability on Linux, or provide bash equivalents.
Azure Arc
Customer intent: "As a cloud administrator, I want to retrieve the list of enabled resource types for Azure Arc-enabled custom locations, so that I can manage and utilize those resources effectively in our hybrid cloud environment."
...ocs/blob/main/articles/azure-arc/includes/azure-arc.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Missing Linux Example
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal. While Azure CLI is cross-platform, the inclusion of Azure PowerShell (which is historically Windows-centric, though now available on Linux) and the absence of explicit Linux shell (bash) or scripting examples, as well as no mention of Linux-native tools or patterns, suggests a Windows bias. Azure PowerShell is presented as a primary method alongside Azure CLI, and there are no examples using bash, shell scripts, or Linux-specific instructions.
Recommendations
- Add explicit bash/shell examples for running Azure CLI commands on Linux, including environment setup and output parsing.
- Clarify that Azure CLI is cross-platform and provide usage notes for both Windows and Linux environments.
- If Azure PowerShell is recommended, note its availability on Linux and provide installation/usage guidance for Linux users.
- Consider including Linux-native scripting patterns (e.g., using jq for JSON output parsing) to improve parity.
- Review the ordering and prominence of examples to ensure Linux and Windows users are equally supported.
Azure Arc
Simplify network configuration requirements with Azure Arc gateway (preview)
...zure-arc/kubernetes/arc-gateway-simplify-networking.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation consistently presents both Azure CLI and Azure PowerShell examples for all major workflows. However, PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and in some sections, PowerShell is mentioned before Linux-native patterns. There are no explicit Linux shell script examples, nor any references to Linux-specific tools or package managers. Environment variable examples for proxy configuration are shown for both CLI (Linux-style) and PowerShell (Windows-style), but there is no mention of Linux-specific nuances (such as systemd proxy configuration, bash scripting, or troubleshooting on Linux). The documentation does not reference Linux package managers or provide troubleshooting steps for Linux environments.
Recommendations
- Add explicit Linux shell script examples for key workflows (e.g., using bash, curl, or kubectl in Linux environments).
- Include troubleshooting steps or notes for common Linux proxy configuration issues (such as systemd, environment variables in bash, etc.).
- Reference Linux package managers (e.g., apt, yum) for installing Azure CLI, and clarify prerequisites for Linux environments.
- Consider reordering examples to present Azure CLI (cross-platform, Linux-native) before PowerShell, or clearly indicate CLI as the recommended/default for Linux.
- Add notes on file permissions, SELinux/AppArmor, or other Linux-specific security considerations when onboarding clusters.
Azure Arc
Quickstart: Connect an existing Kubernetes cluster to Azure Arc
...les/azure-arc/kubernetes/quickstart-connect-cluster.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Examples and instructions are consistently provided for Azure CLI and Azure PowerShell, with PowerShell being a Windows-centric tool. Where cluster creation is discussed, Docker for Windows is mentioned explicitly and equally with Mac, but Linux is not mentioned, despite being a common platform for Kubernetes. Proxy environment variable examples are given for Bash (cross-platform) and PowerShell (Windows), but no Linux-specific shell or tool examples are provided. There is no mention of Linux-native alternatives to PowerShell, nor are Linux-specific instructions or troubleshooting steps highlighted. The documentation assumes familiarity with Windows tools and patterns, and does not provide parity for Linux users in terms of example commands or environment setup.
Recommendations
- Add explicit instructions and examples for Linux users, such as using Bash or other Linux shells for environment variable configuration.
- Include references to Docker for Linux when discussing cluster creation options, not just Docker for Mac and Windows.
- Provide troubleshooting steps and environment setup examples for Linux environments, including common Linux package managers and shell usage.
- Mention Linux-native alternatives to PowerShell where appropriate, or clarify that Azure CLI is fully supported on Linux.
- Ensure that all examples and instructions are platform-neutral or include platform-specific tabs for Windows, Mac, and Linux where differences exist.
Azure Arc
Diagnose connection issues for Azure Arc-enabled Kubernetes clusters
...les/azure-arc/kubernetes/diagnose-connection-issues.md
High Priority
View Details →
Detected Bias Types
Windows Tools
Powershell Heavy
Windows First
Summary
The documentation provides both Linux and Windows examples for DNS troubleshooting, but the Windows-specific steps (using PowerShell and the Resolve-DnsName cmdlet) are given in detail, including instructions for running a Windows test pod and executing PowerShell commands. The Linux example is more generic, while the Windows example is more elaborate and uses Windows-specific tools. The documentation also references Windows command documentation for nslookup, even though the example uses a Debian pod. Overall, Windows tools and patterns are mentioned explicitly and in detail, sometimes before or in more depth than their Linux equivalents.
Recommendations
- Provide equally detailed Linux troubleshooting steps, such as using dig or other Linux-native DNS tools, and include example outputs.
- Reference Linux documentation for commands like nslookup and host, not just Windows command documentation.
- Ensure that Linux steps are presented with the same level of detail and clarity as Windows steps, including pod creation, command execution, and expected output.
- Consider presenting Linux examples first, or in parallel with Windows examples, to avoid Windows-first bias.
- Clarify when steps are OS-specific and provide clear guidance for both Linux and Windows environments.
Azure Arc
Troubleshoot extension issues for Azure Arc-enabled Kubernetes clusters
...les/azure-arc/kubernetes/extensions-troubleshooting.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Powershell Heavy
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows bias. Azure CLI commands are shown throughout, which are cross-platform, but some troubleshooting steps (such as enabling AKS feature flags and force-deleting extensions) are more familiar to Windows/Azure users. There is a lack of explicit Linux shell or distribution-specific examples, and no mention of Linux-specific troubleshooting tools or patterns (e.g., systemd, journalctl, bash scripting). The only OS-specific troubleshooting is for Oracle Linux, but even there, the solution is generic. No PowerShell-specific commands are present, but the overall flow assumes Azure CLI and Azure-centric workflows, which are more common in Windows environments. There are no examples using Linux-native tools like grep, sed, or direct shell scripting, and no mention of Linux package managers or service management.
Recommendations
- Add explicit Linux shell examples (e.g., bash, zsh) for common troubleshooting tasks.
- Include troubleshooting steps using Linux-native tools (e.g., journalctl, systemctl, grep, sed) where relevant.
- Provide parity for Linux distributions beyond Oracle Linux, such as Ubuntu, CentOS, or SUSE, especially for extension installation and troubleshooting.
- Mention Linux package managers or service management commands when discussing dependencies or required modules.
- Clarify that Azure CLI is cross-platform, and provide guidance for installing and using it on Linux systems.
- Where AKS or Azure-specific commands are shown, offer alternative approaches for clusters running on Linux outside Azure (e.g., on-premises, other clouds).
Azure Arc
Customer intent: As a network administrator, I want to configure outbound network access for Azure Arc agents in the Azure public cloud, so that they can connect to necessary endpoints for proper functionality and management of connected clusters.
...ubernetes/includes/network-requirements-azure-cloud.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page exhibits Windows bias by listing endpoints and authentication domains with Windows-centric naming (e.g., login.windows.net, sts.windows.net, servicebus.windows.net) before mentioning Linux-specific resources. There is reference to Windows tools and endpoints, but no explicit Linux command-line examples or Linux firewall/proxy configuration guidance. The only Linux-specific endpoint (linuxgeneva-microsoft.azurecr.io) is mentioned last, and there are no examples or instructions tailored for Linux environments.
Recommendations
- Provide Linux-specific examples for configuring outbound network access, such as iptables, firewalld, or ufw commands.
- Include sample Linux shell commands for endpoint testing (e.g., curl, wget, nc) alongside any REST or PowerShell examples.
- Ensure that Linux endpoints and tools are mentioned with equal prominence and ordering as Windows equivalents.
- Add guidance for configuring proxies and firewalls on common Linux distributions.
- Clarify that the endpoints are platform-agnostic and provide explicit instructions for both Windows and Linux environments.
Azure Arc
Azure Resource Graph sample queries for Azure Arc-enabled Kubernetes
...rticles/azure-arc/kubernetes/resource-graph-samples.md
High Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Missing Linux Example
Summary
The documentation references Azure PowerShell before Azure CLI when listing query execution options, which can suggest a Windows-first approach. The mention of Azure PowerShell (commonly associated with Windows environments) and the custom metadata 'devx-track-azurepowershell' reinforce this bias. There are no explicit Linux shell examples (e.g., Bash), nor are Linux-specific tools or instructions provided.
Recommendations
- List Azure CLI before Azure PowerShell when describing cross-platform query execution options, as CLI is natively supported on Linux and macOS.
- Include explicit Bash/Linux shell examples for running queries using Azure CLI.
- Add metadata tags that reflect Linux parity, such as 'devx-track-linux' or similar.
- Clarify that Azure CLI is cross-platform and provide installation/use instructions for Linux environments.
- Avoid implying PowerShell is the primary or default method unless justified by user data.
Azure Arc
Azure Arc-enabled Kubernetes system requirements
...n/articles/azure-arc/kubernetes/system-requirements.md
High Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows Tools
Windows First
Summary
The documentation page demonstrates a moderate Windows bias. Azure PowerShell is featured prominently alongside Azure CLI in all management tool and resource provider registration examples, with PowerShell commands shown before or alongside CLI commands. The documentation references Azure PowerShell and its installation, which is primarily a Windows-centric tool, and does not mention Linux-native alternatives or shell environments (e.g., Bash, zsh) for command-line operations. There is no explicit mention of Linux-specific tooling or patterns, and the examples do not clarify cross-platform usage or provide parity for Linux users beyond Azure CLI.
Recommendations
- Explicitly state that Azure CLI is cross-platform and recommend it as the primary tool for Linux and macOS users.
- Provide Bash/zsh shell examples for Linux users where appropriate, especially for installation and resource provider registration steps.
- Clarify that Azure PowerShell is available on Linux and macOS, but is more commonly used on Windows, and link to installation instructions for non-Windows platforms.
- Add notes or sections highlighting Linux-native workflows and tools, ensuring Linux users are aware of best practices and supported environments.
- Review the ordering of examples to avoid listing Windows/PowerShell commands first by default; alternate or prioritize CLI/Bash examples for broader accessibility.
Azure Arc
Tutorial: Implement CI/CD with GitOps (Flux v2)
...es/azure-arc/kubernetes/tutorial-gitops-flux2-ci-cd.md
High Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation demonstrates a moderate Windows/Azure bias. Azure DevOps (a Microsoft/Windows-centric tool) is presented first and in greater detail than GitHub. The tutorial assumes Azure CLI and Azure DevOps familiarity, with step-by-step instructions focused on Azure DevOps workflows, service connections, and permissions. There are no explicit Linux-specific or cross-platform alternatives mentioned for key steps (e.g., service connections, environment variable management, or pipeline setup). The use of Azure CLI and Azure DevOps UI is emphasized, with no mention of Linux-native tools or patterns (such as shell scripts, open-source CI/CD tools like Jenkins, or Linux desktop workflows). While Kubernetes and Helm commands are platform-neutral, the overall flow and examples are tailored to Azure-centric, Windows-preferred environments.
Recommendations
- Provide Linux-specific or cross-platform alternatives for Azure DevOps steps, such as using open-source CI/CD tools (Jenkins, GitLab CI, ArgoCD) and shell scripting.
- Include examples of managing secrets, environment variables, and service connections using Linux-native tools (e.g., kubectl, bash scripts, or open-source secret managers).
- Balance the order and depth of Azure DevOps and GitHub sections, or add a third section for a fully open-source, non-Microsoft workflow.
- Explicitly mention that all CLI commands (Azure CLI, kubectl, Helm) work on Linux, macOS, and Windows, and provide installation instructions for each OS.
- Add troubleshooting tips for Linux users (e.g., file permissions, environment setup, CLI installation issues).
- Reference Linux desktop workflows and editors (VS Code, Vim, etc.) alongside Windows tools where relevant.