← Back to Dashboard
754
Pages Scanned
132
Pages Flagged
754
Changed Pages
17.5%
% Pages Flagged

Scan Information

Started At: 2026-01-14 00:00:33

Finished At: 2026-01-14 05:21:13

Status: completed

Target Repo: Azure Management

Current Phase: discovery

Files Queued: 754

Files Completed: 754

Problematic Pages

134 issues found
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 →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example ⚠️ windows_first
Summary
The documentation provides only a PowerShell script using Windows-specific cmdlets and tools (e.g., Get-PnpDevice, pnputil, Dismount-VMHostAssignableDevice), with no mention of Linux or cross-platform alternatives. All instructions and examples are tailored to Windows environments, creating friction for Linux/macOS users who may be running AKS on Azure Arc on non-Windows hosts.
Recommendations
  • Add equivalent instructions or scripts for Linux hosts, using bash and Linux-native tools (e.g., lspci, nvidia-smi, modprobe, etc.) for GPU detection and driver management.
  • Clarify in the prerequisites or introduction if the procedure is only supported on Windows-based Azure Local hosts, or provide guidance for Linux/macOS users.
  • If Windows is a hard requirement, explicitly state this at the top of the page to prevent confusion.
  • Provide links or references to official Azure Arc documentation for Linux GPU enablement if available.
GitHub Create Pull Request
Azure Arc Connect machines at scale with a Configuration Manager custom task sequence ...c/servers/onboard-configuration-manager-custom-task.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_first
Summary
The documentation is heavily focused on Windows environments, specifically using Microsoft Configuration Manager (SCCM) and Windows Installer (.msi) packages. All examples and instructions are tailored for Windows, with exclusive use of PowerShell scripts and Windows-specific tooling. There are no references to Linux or macOS equivalents, nor guidance for onboarding non-Windows machines at scale using similar automation or deployment strategies.
Recommendations
  • Clarify early in the documentation that the process described is only applicable to Windows endpoints managed by Configuration Manager, if that is the intent.
  • If onboarding Linux servers at scale is supported, provide parallel instructions for Linux environments, such as using shell scripts, Linux package managers (deb/rpm), and automation tools like Ansible or Puppet.
  • Include references or links to documentation for onboarding non-Windows machines to Azure Arc at scale, if available.
  • Explicitly state any platform limitations to set expectations for cross-platform users.
GitHub Create Pull Request
Azure Arc Remove your VMware vCenter environment from Azure Arc ...e-arc/vmware-vsphere/remove-vcenter-from-arc-vmware.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation demonstrates a Windows bias in the section about running the deboarding script: only PowerShell instructions for Windows are provided, with no Linux/macOS equivalent. The script appears to be a PowerShell script (.ps1), and there are no instructions or guidance for running the script from Linux/macOS. Additionally, the Windows instructions are presented first and exclusively, while Linux users are left without clear guidance for this critical step.
Recommendations
  • Provide instructions for running the deboarding script from Linux/macOS, if supported (e.g., via PowerShell Core, Azure CLI, or Bash).
  • If the script is Windows-only, explicitly state this limitation and offer alternative manual steps for Linux/macOS users.
  • Consider offering a cross-platform version of the deboarding script (e.g., Bash or Python) or document how to use PowerShell Core on Linux/macOS.
  • Present manual removal steps in a way that is platform-neutral, ensuring Linux/macOS users can follow along without friction.
GitHub Create Pull Request
Azure Arc Onboarding Scripts for Workload Orchestration ...azure-arc/workload-orchestration/onboarding-scripts.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example ⚠️ windows_first
Summary
The documentation is heavily focused on Windows and PowerShell, with all onboarding script examples and instructions given exclusively for PowerShell (.ps1) scripts and Windows-specific tools like 'winget'. There are no Linux/macOS shell script equivalents, nor are there instructions for running these scripts on non-Windows platforms. The use of Windows-first tools and lack of cross-platform guidance creates friction for Linux/macOS users.
Recommendations
  • Provide equivalent Bash/shell script examples for Linux/macOS users, or clarify if the scripts are Windows-only.
  • Replace or supplement 'winget' installation instructions with cross-platform alternatives (e.g., apt, yum, brew, or direct download links).
  • Explicitly state platform requirements for the onboarding scripts (e.g., 'These scripts require Windows/PowerShell'), or provide cross-platform versions.
  • Add a section describing how Linux/macOS users can onboard, including any prerequisites and script execution steps.
  • If PowerShell Core (pwsh) is supported on Linux/macOS, clarify compatibility and provide usage instructions.
GitHub Create Pull Request
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
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page demonstrates a notable Windows bias. All command-line examples are provided in PowerShell syntax, including variable assignment and command invocation. There are no Bash or Linux/macOS shell equivalents, and instructions for configuring the management machine explicitly reference Windows setup scripts. This creates friction for Linux/macOS users, who must adapt PowerShell examples and may lack guidance for their platforms.
Recommendations
  • Provide Bash/Linux/macOS shell equivalents for all PowerShell command examples, especially for az CLI usage and variable assignment.
  • Include instructions or scripts for configuring a Linux/macOS management machine, not just Windows.
  • Clarify which steps are platform-agnostic and which are Windows-specific, and offer parity where possible.
  • Where PowerShell is used only for variable assignment and az CLI invocation, switch to Bash syntax for broader compatibility.
GitHub Create Pull Request
Azure Arc Install Networking and Observability Components for Edge RAG Preview Enabled by Azure Arc ...azure-arc/edge-rag/prepare-networking-observability.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation provides only PowerShell-based examples and commands for installing MetalLB and observability modules, with no Linux/macOS shell equivalents. It assumes the use of PowerShell (e.g., $variables, start-sleep), which is uncommon on Linux/macOS. This creates friction for non-Windows users attempting to follow the instructions.
Recommendations
  • Provide equivalent Bash shell examples for all PowerShell commands, using standard Linux/macOS CLI syntax.
  • Clarify whether commands must be run on Windows, or if they can be executed from any OS with the Azure CLI and kubectl installed.
  • Replace PowerShell-specific constructs (e.g., $variables, start-sleep) with cross-platform alternatives in Bash.
  • Explicitly mention OS requirements and provide guidance for Linux/macOS users where applicable.
GitHub Create Pull Request
Azure Arc Connected Machine agent prerequisites .../blob/main/articles/azure-arc/servers/prerequisites.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ windows_first
Summary
The documentation provides both Windows and Linux coverage for Azure Arc Connected Machine agent prerequisites. However, there is a notable Windows bias in several areas: PowerShell examples are given for Windows installation scripts and resource provider registration, with Windows-specific tools (Group Policy Editor) described in detail. Windows installation script modifications are explained step-by-step, while Linux instructions are minimal and lack equivalent detail or examples. In some sections, Windows instructions or tools are presented first or exclusively, with Linux coverage being less thorough.
Recommendations
  • Provide equivalent Linux installation script modification examples, especially for limited support OS scenarios.
  • Include Linux-specific troubleshooting steps or configuration guidance where Windows tools (like Group Policy Editor) are described.
  • Balance example order: present Azure CLI (cross-platform) before or alongside PowerShell, and ensure Linux commands are shown with equal prominence.
  • Expand Linux prerequisites and configuration details to match the depth given to Windows (e.g., permissions, service management).
GitHub Create Pull Request
Azure Arc How to migrate from legacy Log Analytics agents in non-Azure environments with Azure Arc ...in/articles/azure-arc/servers/migrate-legacy-agents.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation provides both Windows and Linux context at a high level, but several sections prioritize Windows-specific tools and workflows. Windows deployment options (Windows Admin Center, Windows Server Graphical Installer) are mentioned explicitly, while Linux equivalents are not. Example commands and automation tools are referenced generically (PowerShell, Bash, Azure CLI), but no explicit Linux-focused walkthroughs or examples are given. Windows client installation is called out in detail, with no parallel guidance for Linux clients.
Recommendations
  • Add explicit Linux deployment examples and workflows, such as using Ansible, shell scripts, or Linux package managers.
  • Include Linux-specific installation instructions for the Azure Monitor Agent, especially for standalone scenarios.
  • Mention Linux graphical tools (if any) or clarify that certain graphical installers are Windows-only.
  • Provide example Bash/CLI commands for common Linux migration tasks, not just generic references.
  • Ensure parity in troubleshooting and agent configuration guidance for Linux environments.
GitHub Create Pull Request
Azure Arc Azure CLI Requests for the Run Command on Azure Arc-enabled Servers (Preview) ...lob/main/articles/azure-arc/servers/run-command-cli.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation provides only Windows PowerShell script examples (e.g., 'Write-Host Hello World!') when demonstrating Azure CLI usage for Run Command on Arc-enabled servers. There are no Bash or Linux shell script examples, which may cause confusion or friction for Linux/macOS users managing non-Windows Arc-enabled servers.
Recommendations
  • Include parallel examples using Bash or shell scripts (e.g., 'echo Hello World!') to demonstrate usage for Linux Arc-enabled servers.
  • Clarify in the introduction that the Run Command feature supports both Windows and Linux servers, and examples are applicable to both.
  • Add notes or sections specifying any platform-specific differences in script execution or output handling.
GitHub Create Pull Request
Azure Arc Troubleshoot Azure Arc-enabled servers VM extension issues ...ticles/azure-arc/servers/troubleshoot-vm-extensions.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides a PowerShell example for removing extensions but does not offer an equivalent Azure CLI or Linux-native command example in the main troubleshooting steps. Windows paths and tools are often mentioned before Linux equivalents, though Linux information is present. This creates a mild bias toward Windows users, especially in command-line guidance.
Recommendations
  • Include Azure CLI examples alongside PowerShell for extension management tasks, especially for removal and installation.
  • Present Linux and Windows file paths and troubleshooting steps in parallel, rather than listing Windows first.
  • Explicitly mention Linux-native commands or scripts where applicable, or link to Linux-specific troubleshooting guides.
  • Clarify that both PowerShell and CLI can be used on any platform, and provide cross-platform instructions.
GitHub Create Pull Request
Azure Arc Bulk Review, Publish, and Deploy with Workload Orchestration ...es/azure-arc/workload-orchestration/bulk-deployment.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation page consistently uses PowerShell syntax for CLI examples and references PowerShell scripts (.ps1) for automation, without providing Bash or Linux/macOS equivalents. There are no explicit instructions or examples for Linux/macOS users, which may create friction for those not using Windows.
Recommendations
  • Provide CLI command examples in Bash syntax alongside PowerShell, especially for az CLI commands, which are cross-platform.
  • Offer equivalent Bash scripts for automation tasks, or document how to run the provided PowerShell scripts on Linux/macOS (e.g., via PowerShell Core).
  • Clarify that az CLI commands work on all platforms and note any platform-specific requirements for scripts.
  • Include notes or tabs for Linux/macOS users where workflows or file paths may differ.
GitHub Create Pull Request
Azure Arc Release Notes for Workload Orchestration ...cles/azure-arc/workload-orchestration/release-notes.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ windows_first
Summary
The documentation provides CLI examples for installing and updating the Azure Workload Orchestration extension using the Azure CLI, which is cross-platform. However, in the May 2025 release section, CLI usage examples are shown using PowerShell syntax (backticks for line continuation and $variable notation), which is specific to Windows/PowerShell environments. No equivalent Bash/Linux shell examples are provided, and PowerShell syntax appears before any Linux alternatives.
Recommendations
  • Provide Bash/Linux shell examples alongside PowerShell examples for CLI commands, especially for multi-line commands and variable usage.
  • Use generic CLI syntax (without shell-specific line continuations or variable notation) when possible, or show both PowerShell and Bash versions.
  • Add a note clarifying that Azure CLI is cross-platform and can be used from Bash, PowerShell, or other shells.
GitHub Create Pull Request
Azure Arc Customer intent: As a system administrator managing a multi-node cluster, I want to configure Linux with HugePages and NVME modules, so that I can optimize performance for AKS Edge Essentials. ...ntainer-storage/includes/multi-node-edge-essentials.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
Although the documentation is for configuring Linux nodes, all examples use the Windows PowerShell cmdlet Invoke-AksEdgeNodeCommand to execute Linux commands remotely. There are no direct Linux shell examples, and the workflow assumes users are operating from a Windows environment, which may not be the case for many Linux administrators.
Recommendations
  • Provide equivalent Linux-native instructions, such as direct bash commands to be run on each node.
  • Include SSH-based examples for executing commands on Linux nodes from a Linux/macOS admin workstation.
  • Clarify whether Invoke-AksEdgeNodeCommand is available cross-platform, and if not, offer alternatives for Linux/macOS users.
GitHub Create Pull Request
Azure Arc Customer intent: As a system administrator, I want to configure a single-node Kubernetes cluster with adequate resources and storage provisions, so that I can deploy and manage applications effectively using Azure IoT Operations and Azure Container Storage. ...tainer-storage/includes/single-node-edge-essentials.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools
Summary
While the documentation is focused on configuring AKS Edge Essentials for Linux, it relies on the Windows-only PowerShell cmdlet Invoke-AksEdgeNodeCommand to execute Linux system commands, rather than providing native Linux shell instructions. This creates friction for users managing Linux hosts directly, as the examples assume a Windows management environment.
Recommendations
  • Provide equivalent Linux-native commands for checking and setting sysctl parameters (e.g., using bash directly on the Linux node).
  • Clarify when Windows tools (like PowerShell cmdlets) are required and offer alternatives for users managing Linux hosts from Linux/macOS.
  • Add explicit instructions for users who may be SSHing into Linux hosts, rather than managing them via Windows.
  • Ensure all critical steps can be completed natively on Linux without requiring Windows tools.
GitHub Create Pull Request
Azure Arc Back up controller database .../articles/azure-arc/data/backup-controller-database.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides command-line examples for connecting to the SQL Server instance using sqlcmd, but consistently uses PowerShell syntax (e.g., command blocks labeled as 'powershell') and Windows-style command formatting. There are no explicit Linux/macOS shell examples, nor is there mention of using bash or alternative shell environments. The documentation assumes familiarity with PowerShell and Windows conventions, which may create friction for Linux/macOS users.
Recommendations
  • Provide example commands using bash/sh syntax alongside PowerShell, especially for kubectl exec and sqlcmd usage.
  • Clarify that sqlcmd and kubectl commands can be run from Linux/macOS terminals, and provide sample commands for those environments.
  • Avoid labeling generic command blocks as 'powershell' when the commands are cross-platform.
  • Mention installation steps or prerequisites for sqlcmd on Linux/macOS if relevant.
GitHub Create Pull Request
Azure Arc Resize persistent volume claim (PVC) for Azure Arc-enabled data services volume ...icles/azure-arc/data/resize-persistent-volume-claim.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides a key example for patching the PVC using a PowerShell-style variable assignment ($newsize=...), which is not directly usable on Linux/macOS shells. All command examples use kubectl, which is cross-platform, but the PVC patching step assumes a Windows/PowerShell environment by showing only a PowerShell variable assignment and interpolation pattern, without a Linux/macOS shell equivalent.
Recommendations
  • Add equivalent Linux/macOS shell examples for variable assignment and kubectl patch usage, e.g., using Bash syntax: newsize='{"spec":{"resources":{"requests":{"storage":"50Gi"}}}}'; kubectl patch pvc ... --patch "$newsize"
  • Explicitly state that the example shown is for PowerShell, and provide a Bash/Zsh alternative for Linux/macOS users.
  • Consider using direct kubectl patch commands without variable assignment for simplicity and parity.
GitHub Create Pull Request
Azure Arc Install client tools ...b/main/articles/azure-arc/data/install-client-tools.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation provides installation instructions for several client tools, often listing Windows installation links before Linux/macOS, and includes Windows-specific notes (e.g., using cmd.exe instead of PowerShell for curl). There is a PowerShell-specific caveat for curl, but no equivalent Linux shell guidance. Some installation instructions for Linux are less explicit than for Windows (e.g., 'install curl package' vs. direct link for Windows). Overall, while Linux and macOS are mentioned, Windows patterns and caveats are prioritized or more detailed.
Recommendations
  • Provide explicit installation instructions or links for Linux and macOS for all tools, not just Windows.
  • Include Linux shell equivalents for PowerShell-specific notes (e.g., explain curl usage in bash/zsh).
  • Present installation options for all platforms in parallel, rather than listing Windows first.
  • Add troubleshooting notes relevant to Linux/macOS environments, not just Windows (e.g., curl aliasing in Linux shells).
GitHub Create Pull Request
Azure Arc Features and Capabilities of SQL Managed Instance enabled by Azure Arc ...n/articles/azure-arc/data/managed-instance-features.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ windows_authentication_first
Summary
The documentation lists several Windows-centric tools (SSMS, SQL Server PowerShell, SQL Server Profiler) and features (Windows Authentication, PowerShell scripting support) without equivalent Linux/macOS alternatives or parity notes. PowerShell scripting support is highlighted in the manageability section, and Windows Authentication is listed as a supported feature, while Microsoft Entra authentication is marked as unsupported. The tools section prioritizes Windows tools, with only Azure Data Studio and Azure CLI being cross-platform. There are no Linux/macOS-specific examples or guidance.
Recommendations
  • Explicitly mention cross-platform alternatives where available (e.g., Azure Data Studio, Azure CLI) and clarify which tools are Windows-only.
  • Add notes or links to Linux/macOS setup guides for SQL Managed Instance management.
  • Provide scripting examples using Bash/CLI alongside PowerShell where relevant.
  • Clarify authentication options for non-Windows environments, especially since Microsoft Entra authentication is not supported.
GitHub Create Pull Request
Azure Arc Migrate a database from SQL Server to SQL Managed Instance enabled by Azure Arc ...articles/azure-arc/data/migrate-to-managed-instance.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation provides examples and instructions that prioritize Windows environments, such as using Windows file paths (C:\Backupfiles\...) and referencing Windows tools (Notepad, OneNote) for copying credentials. There are no explicit Linux/macOS examples for backup file paths or alternative tools, which may create friction for users on non-Windows platforms.
Recommendations
  • Include Linux/macOS equivalents for file paths in backup and restore examples (e.g., /home/user/Backupfiles/test.bak).
  • Mention cross-platform editors (e.g., VS Code, nano) alongside Notepad/OneNote for saving credentials.
  • Clarify that Azure Data Studio and Azure Storage Explorer are available on Linux/macOS and provide installation links for those platforms.
  • Provide example commands for copying backup files from Linux/macOS systems using kubectl cp.
  • Add notes or callouts where steps differ for Linux/macOS users.
GitHub Create Pull Request
Azure Arc Upload metrics to Azure Monitor ...cs/blob/main/articles/azure-arc/data/upload-metrics.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation provides examples for PowerShell and macOS/Linux for most commands, but the Windows tab is frequently marked as 'N/A' or only provides basic SET/echo commands. The automation section gives a Linux shell script example and mentions Windows Task Scheduler, but does not provide a concrete Windows batch or PowerShell script for automating uploads. PowerShell examples are shown before Linux/macOS in most cases, and Linux-specific tools (like jq) are used without Windows alternatives. There is a lack of parity in scripting and automation guidance for Windows users.
Recommendations
  • Provide Windows batch (.bat/.cmd) and PowerShell script examples for automating metric uploads, similar to the Linux shell script provided.
  • Include Windows-friendly alternatives to Linux tools (e.g., suggest PowerShell's ConvertFrom-Json instead of jq for parsing JSON).
  • Ensure that all command examples are available for Windows users, not just marked as 'N/A'.
  • Present Linux/macOS and Windows examples side-by-side or in a consistent order to avoid implicit prioritization.
GitHub Create Pull Request
Azure Arc Configure "BYOM" Endpoint Authentication for Edge RAG ...zure-arc/edge-rag/configure-endpoint-authentication.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example ⚠️ windows_first
Summary
The documentation page provides all command-line examples using PowerShell syntax and Windows-specific patterns (e.g., .\kubectl.exe), without any Bash or Linux/macOS shell equivalents. This creates friction for Linux/macOS users, who must adapt the commands themselves. The use of PowerShell-specific constructs (e.g., [System.Text.Encoding]::UTF8.GetString) and explicit references to .exe files further reinforce a Windows-first approach.
Recommendations
  • Provide equivalent Bash/Linux/macOS shell commands alongside PowerShell examples.
  • Use platform-agnostic kubectl commands (e.g., 'kubectl' instead of '.\kubectl.exe') unless Windows-only behavior is required.
  • Replace PowerShell-specific base64 decoding with cross-platform alternatives (e.g., 'base64 --decode' in Bash).
  • Add a note clarifying any platform-specific differences and how Linux/macOS users should adapt the instructions.
GitHub Create Pull Request
Azure Arc Deploy the Edge RAG Extension ...t-docs/blob/main/articles/azure-arc/edge-rag/deploy.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_first
Summary
The documentation provides Azure CLI deployment instructions exclusively using PowerShell syntax and variable assignment, without any Bash or Linux shell equivalents. All CLI examples use Windows-style PowerShell variables and line continuations, which may confuse or hinder Linux/macOS users. There are no Bash examples or notes for Linux users, and PowerShell is presented as the default scripting environment for CLI usage.
Recommendations
  • Add equivalent Bash shell examples for Azure CLI commands, using Bash variable assignment and syntax.
  • Include a note clarifying that Azure CLI works cross-platform and provide guidance for Linux/macOS users.
  • Present both PowerShell and Bash examples side-by-side or in tabs, or default to Bash for CLI documentation unless Windows-specific features are required.
  • Avoid using Windows-specific line continuations (backtick `) in CLI examples; use standard Bash line continuations (backslash \) for Linux/macOS.
  • Explicitly mention any platform-specific requirements if PowerShell is required for certain steps.
GitHub Create Pull Request
Azure Arc Verify Contributor Role for Edge RAG Preview Enabled by Azure Arc ...s/azure-arc/edge-rag/prepare-contributor-permission.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation provides only PowerShell CLI examples for verifying contributor permissions, without mentioning or demonstrating equivalent Linux/macOS shell usage. This may create friction for non-Windows users, as the Azure CLI is cross-platform and typically used via Bash or other shells on Linux/macOS.
Recommendations
  • Include example commands using Bash or generic shell syntax to demonstrate Azure CLI usage on Linux/macOS.
  • Clarify that the Azure CLI commands are cross-platform and can be run in any shell, not just PowerShell.
  • Avoid using PowerShell-specific formatting unless the task is Windows-only.
GitHub Create Pull Request
Azure Arc Configure DNS for Edge RAG Preview Enabled by Azure Arc ...s/blob/main/articles/azure-arc/edge-rag/prepare-dns.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation provides only Windows-specific instructions for updating the hosts file (using Notepad, referencing the Windows hosts file path), with no mention of how to perform the equivalent task on Linux or macOS. This creates friction for non-Windows users who need to configure DNS for Edge RAG deployments.
Recommendations
  • Add instructions for editing the hosts file on Linux and macOS, including the typical file path (/etc/hosts) and required permissions (sudo/root).
  • Include example commands for editing the hosts file using common Linux/macOS tools (e.g., nano, vim, or echo with sudo).
  • Clarify that the process is similar across platforms, but file paths and required privileges differ.
  • Consider presenting platform-agnostic steps first, or grouping instructions by OS.
GitHub Create Pull Request
Azure Arc Quickstart: Install Edge RAG on Azure Kubernetes Service ...ain/articles/azure-arc/edge-rag/quickstart-edge-rag.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation demonstrates a Windows bias in the 'Connect to the developer portal' section, where instructions for editing the hosts file are provided exclusively for Windows (using Notepad and the Windows file path). There are no equivalent instructions for Linux or macOS users, nor is there mention of alternative editors or file locations for those platforms. Additionally, the use of PowerShell-style variable assignment and backtick line continuation in Azure CLI examples may be confusing for non-Windows users, though the commands themselves are cross-platform.
Recommendations
  • Add instructions for editing the hosts file on Linux (e.g., using sudo nano /etc/hosts) and macOS (e.g., sudo open -e /etc/hosts or sudo nano /etc/hosts).
  • Mention the location of the hosts file on Linux/macOS (/etc/hosts) and provide example commands for editing and saving the file.
  • Clarify that the Azure CLI commands can be run on any platform, and provide alternative syntax for variable assignment and line continuation for Bash/zsh (e.g., export rg="edge-rag-aks-rg" and using \ for line continuation).
  • Where PowerShell-specific instructions are given, offer Bash/zsh equivalents or note the differences.
GitHub Create Pull Request
Azure Arc Uninstall Edge RAG Extension ...ain/articles/azure-arc/edge-rag/uninstall-extension.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation provides only PowerShell examples for command-line operations, including Azure CLI and kubectl commands, and does not offer equivalent Linux/macOS shell examples. The use of PowerShell syntax (e.g., $variable assignment) and code blocks labeled as 'powershell' may confuse or hinder Linux/macOS users. There is no mention of Bash or shell alternatives, and Windows-centric patterns are shown first and exclusively.
Recommendations
  • Provide Bash/shell examples alongside PowerShell, especially for Azure CLI and kubectl commands, using standard shell variable syntax.
  • Clarify that Azure CLI and kubectl are cross-platform and can be used from Linux/macOS terminals.
  • Label code blocks appropriately (e.g., 'bash' for shell examples) and avoid PowerShell-only variable assignment for cross-platform commands.
  • Add a note or tab for Linux/macOS users, showing equivalent steps.
GitHub Create Pull Request
Azure Arc Customer intent: "As a network administrator, I want to configure outbound and inbound connectivity settings for the appliance VM and management machine, so that I can ensure smooth communication and functionality for the Arc resource bridge." ...e-arc/resource-bridge/includes/network-requirements.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools
Summary
The documentation lists both Windows and Linux-related endpoints, but there is a subtle Windows bias: Windows NTP is mentioned explicitly before any Linux time source, and endpoints such as sts.windows.net, login.windows.net, and time.windows.com are highlighted. The notes for NTP mention only the Windows NTP server and Hyper-V defaults, with no reference to Linux NTP servers or alternatives. The Azure CLI installer download is mentioned, but there is no explicit guidance for Linux package managers or installation methods. Overall, the documentation assumes familiarity with Windows-centric endpoints and patterns.
Recommendations
  • Add explicit references to Linux NTP servers (e.g., pool.ntp.org) and clarify when time.windows.com is only needed for Windows-based deployments.
  • Provide guidance or notes for Linux management machines, such as how to install Azure CLI via native package managers (apt, yum, etc.), and clarify if any endpoints are Windows-specific.
  • Where endpoints or tools are Windows-specific (e.g., sts.windows.net, login.windows.net), clarify their relevance for Linux deployments or provide Linux equivalents if applicable.
  • Ensure examples and notes mention both Windows and Linux scenarios, especially for network configuration and tool installation.
GitHub Create Pull Request
Azure Arc Troubleshoot Azure Arc resource bridge issues ...re-arc/resource-bridge/troubleshoot-resource-bridge.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation provides troubleshooting guidance for Azure Arc resource bridge, which is a cross-platform solution. However, several examples and troubleshooting steps show a Windows-first bias: PowerShell is used for network and DNS troubleshooting, Windows paths are referenced in error messages, and some CLI troubleshooting steps (such as downgrading Azure CLI) mention Windows installer methods before Linux alternatives. There are few explicit Linux/macOS command examples, and some troubleshooting steps (e.g., SSH folder access, DNS resolution) use Windows-centric tools or terminology. The documentation does mention Linux-specific errors (GLIBC version), but overall, Linux/macOS users may need to adapt instructions or infer equivalent steps.
Recommendations
  • Provide Linux/macOS equivalents for all PowerShell and Windows command examples (e.g., use dig, nslookup, ping, or host for DNS troubleshooting).
  • When referencing CLI installation or downgrade, include explicit instructions for Linux/macOS (e.g., apt, yum, brew, or direct download).
  • Ensure troubleshooting steps for file permissions, SSH folder access, and networking include Linux/macOS guidance (e.g., chmod, chown, ls -l).
  • Where Windows paths or error messages are shown, clarify Linux/macOS equivalents or note differences.
  • If PowerShell is used for HTTP/HTTPS troubleshooting, offer curl or wget alternatives for Linux/macOS.
GitHub Create Pull Request
Azure Arc Simplify Network Configuration Requirements with Azure Arc Gateway ...cs/blob/main/articles/azure-arc/servers/arc-gateway.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation provides examples for Azure portal, Azure CLI, and PowerShell for all major operations. PowerShell examples are included and sometimes shown before or alongside CLI, but there is no explicit mention of Linux shell equivalents (e.g., Bash) or guidance for Linux-specific usage patterns. In some sections, PowerShell is referenced for log collection and command execution, with Linux instructions given separately but less prominently. The documentation references Windows installation packages and folders before Linux equivalents, and some examples (such as log file locations) list Windows paths first. There are no explicit Bash or Linux shell script examples, and the CLI examples use backticks (`) for line continuation, which is a Windows/PowerShell convention and not valid in Bash.
Recommendations
  • Provide explicit Bash/Linux shell examples for CLI commands, using correct line continuation (\) and syntax.
  • When listing file paths or installation instructions, present Linux and Windows examples with equal prominence, or alternate their order.
  • Clarify that Azure CLI commands can be run on Linux/macOS and provide any necessary platform-specific notes (e.g., environment variables, permissions).
  • Ensure that Linux onboarding and troubleshooting steps are as detailed as Windows ones, including log file locations and script execution.
  • Avoid using Windows-centric conventions (such as backticks for line continuation) in CLI examples; use platform-neutral or dual examples.
GitHub Create Pull Request
Azure Arc Deploy Azure Monitor agent on Arc-enabled servers ...es/azure-arc/servers/azure-monitor-agent-deployment.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation describes deployment methods for the Azure Monitor agent on both Windows and Linux Arc-enabled servers, but examples and tooling references (e.g., PowerShell, Azure CLI) are presented generically or with a slight Windows-first bias. PowerShell is mentioned before Python when discussing Azure Automation, and there are no explicit Linux shell (bash) or Linux-specific example commands. The documentation does not provide parity in showing Linux-native tooling or step-by-step Linux examples, which may create friction for Linux users.
Recommendations
  • Add explicit Linux shell (bash) examples for deploying the extension via Azure CLI and ARM templates.
  • When referencing scripting in Azure Automation, provide both PowerShell and Python examples, and clarify which is recommended for Linux targets.
  • Include links or sections specifically for Linux users, such as troubleshooting Linux agent installation or verifying agent status on Linux.
  • Ensure that references to PowerShell are balanced with Linux equivalents (e.g., bash, sh, or Python) where appropriate.
GitHub Create Pull Request
Azure Arc CLI reference for `azcmagent show` ...blob/main/articles/azure-arc/servers/azcmagent-show.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ windows_first
Summary
The documentation examples use Windows-style quoting (double quotes) and file redirection syntax (e.g., "> agent-status.json"), which may not work as shown on Linux/macOS shells. No Linux/macOS-specific examples or notes are provided.
Recommendations
  • Add Linux/macOS shell examples using single quotes and appropriate file redirection syntax.
  • Include a note clarifying shell differences for quoting and redirection.
  • Show both Windows (cmd/PowerShell) and Linux/macOS (bash/zsh) example commands side by side.
GitHub Create Pull Request
Azure Arc Cloud-native governance and policy with Azure Arc-enabled servers ...es/azure-arc/servers/cloud-native/governance-policy.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation page focuses heavily on Windows-centric governance concepts, such as Group Policy Objects (GPOs), Resultant Set of Policy (RSoP), and Windows security baselines. Examples and scenarios almost exclusively reference Windows servers, with no mention of Linux equivalents (e.g., Linux security baselines, Linux configuration policies, or Linux-specific compliance scenarios). The documentation does not provide Linux-specific examples or guidance for Azure Arc-enabled Linux servers, despite Azure Policy and machine configuration supporting both Windows and Linux.
Recommendations
  • Add explicit examples and scenarios for Azure Policy and machine configuration on Linux servers, such as auditing and enforcing SSH settings, file permissions, or Linux service configurations.
  • Reference Linux equivalents to Windows concepts (e.g., compare GPO with Linux configuration management tools like Ansible, Chef, or native OS mechanisms).
  • Include links to documentation about Azure Policy for Linux, and mention built-in policies relevant to Linux security/compliance.
  • Clarify which features or policies are cross-platform and which are Windows-only, to help Linux/macOS administrators understand applicability.
  • Provide sample DSC or policy definitions for Linux settings (e.g., password complexity, firewall rules) alongside Windows examples.
GitHub Create Pull Request
Azure Arc Cloud-native licensing and cost management with Azure Arc-enabled servers ...-arc/servers/cloud-native/licensing-cost-management.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation focuses almost exclusively on Windows Server and SQL Server licensing options via Azure Arc, with all examples and scenarios centered around Windows environments. There is no mention of Linux server licensing, cost management, or how Azure Arc features apply to Linux workloads. The structure and examples assume Windows as the primary use case, potentially leaving Linux users unclear about their options.
Recommendations
  • Add a section describing how Azure Arc licensing and cost management applies to Linux servers, even if only to clarify that Linux OS licensing is not managed through Azure Arc.
  • Include explicit statements about the scope of Azure Arc cost management for Linux workloads (e.g., monitoring, inventory, billing for other software, etc.).
  • If SQL Server on Linux is supported, clarify whether pay-as-you-go licensing via Arc applies to those instances.
  • Provide parity in examples, such as cost management for Linux servers, or note differences in licensing models.
GitHub Create Pull Request
Azure Arc Next steps for cloud-native server management with Azure Arc-enabled servers .../articles/azure-arc/servers/cloud-native/next-steps.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation page demonstrates a mild Windows bias. Windows-centric tools and workflows (Windows Admin Center, Configuration Manager, WSUS, GPOs) are mentioned first and in detail, while Linux onboarding and management equivalents are not described or linked. There are no explicit Linux onboarding examples, and Linux-native tools or patterns are not referenced, which may cause friction for Linux users seeking parity.
Recommendations
  • Add explicit onboarding instructions or links for Linux servers, such as using shell scripts or Ansible for agent deployment.
  • Mention Linux-native management tools (e.g., cron, systemd, configuration management systems like Chef/Puppet/Ansible) when discussing automation and configuration.
  • Provide examples or references for patching and compliance management on Linux (e.g., using Azure Update Manager with Linux, or alternatives to GPO/WSUS).
  • Ensure that examples and tool references are balanced between Windows and Linux, or clarify when a tool is Windows-only.
GitHub Create Pull Request
Azure Arc Identity and access management with Azure Arc-enabled servers ...cles/azure-arc/servers/cloud-native/identity-access.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page generally describes identity and access management for Azure Arc-enabled servers in a cross-platform manner. However, it shows a subtle Windows bias: Windows/Active Directory scenarios are described first and in greater detail, and concrete examples (such as Remote Desktop access) are given for Windows, while Linux access (via SSH) is mentioned only briefly and without example commands or further explanation. There are no Linux-specific management scenarios or tools discussed.
Recommendations
  • Provide concrete Linux examples alongside Windows ones, such as showing how to use SSH with Microsoft Entra ID credentials to access Linux Arc-enabled servers.
  • Include Linux-specific management scenarios, such as using Azure CLI or automation tools on Linux servers.
  • Balance the order of presentation so that Linux and Windows are treated equally, or explicitly state when a feature or example is Windows-only.
  • Mention Linux equivalents for tools or processes (e.g., alternatives to Group Policy, LAPS, etc.) where relevant.
GitHub Create Pull Request
Azure Arc Cloud-native server management with Azure Arc-enabled servers ...in/articles/azure-arc/servers/cloud-native/overview.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first
Summary
The documentation references several Windows-centric management tools (Active Directory Group Policy, SCCM, MECM, PowerShell remoting, WSUS) as examples of legacy/on-premises solutions that Azure Arc replaces, with limited mention of Linux equivalents. Windows tools and patterns are described first and in more detail, while Linux management paradigms (such as Ansible, Chef, or native Linux configuration management) are not referenced. However, the core Azure Arc features are described as supporting both Windows and Linux servers.
Recommendations
  • Include references to common Linux management tools (e.g., Ansible, Chef, Puppet, cron, SSH) when discussing legacy/on-premises solutions that Azure Arc replaces.
  • Provide examples or analogies for Linux system administrators, such as how Azure Policy and Machine Configuration can replace Linux configuration management tools.
  • Clarify that features like Azure Update Manager, Run Command, and inventory work for both Windows and Linux, and provide links or notes about Linux-specific usage where relevant.
  • Balance the introductory discussion so that both Windows and Linux audiences see their familiar tools and workflows represented.
GitHub Create Pull Request
Azure Arc Manage and maintain the Azure Connected Machine agent ...s/blob/main/articles/azure-arc/servers/manage-agent.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation provides both Windows and Linux instructions for all major agent lifecycle operations (install, upgrade, uninstall, proxy config). However, Windows-specific tools and patterns (Control Panel, Msiexec, PowerShell, Group Policy, WSUS, Configuration Manager) are described in greater detail, with more step-by-step guidance and context than their Linux equivalents. Windows examples and sections are frequently presented first, and PowerShell is used heavily for Windows automation, while Linux instructions are more concise and rely on standard package manager commands. The Linux sections are present and functional, but lack the depth and troubleshooting detail provided for Windows.
Recommendations
  • Add more detailed Linux troubleshooting and automation guidance, similar to the Windows sections (e.g., scripting upgrades/uninstalls, handling package manager errors).
  • Provide parity in step-by-step instructions for Linux package manager configuration and agent management, including links to relevant Linux admin tools and best practices.
  • Include Linux-first examples in some sections, or alternate the order of Windows and Linux instructions to avoid implicit prioritization.
  • Expand on Linux-specific update infrastructure (e.g., using unattended-upgrades, cron jobs, or configuration management tools like Ansible or Chef) for agent lifecycle management.
  • Ensure that advanced scenarios (e.g., proxy configuration, environment variable migration) are equally covered for both platforms, with troubleshooting tips for Linux.
GitHub Create Pull Request
Azure Arc Cloud-native scripting and task automation with Azure Arc-enabled servers ...-arc/servers/cloud-native/scripting-task-automation.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. Windows tools and patterns (RDP, PowerShell, SCCM, Task Scheduler) are mentioned first and more frequently, while Linux equivalents (SSH, cron) are referenced less prominently. Examples and explanations often default to Windows-centric workflows, with limited explicit Linux scripting or automation examples. There is mention of Linux support (SSH, Entra authentication), but practical Linux-specific examples and tool parity are lacking.
Recommendations
  • Add explicit Linux scripting examples (e.g., Bash scripts, use of cron for scheduling) alongside PowerShell examples.
  • Mention Linux-native tools and patterns (cron, systemd timers) when discussing automation and scheduling, not just Windows Task Scheduler or SCCM.
  • Provide sample commands for Linux environments using Bash or Python, not only PowerShell.
  • Ensure that examples and explanations alternate or balance Windows and Linux scenarios, rather than defaulting to Windows-first.
  • Clarify any feature limitations or differences between Windows and Linux Arc-enabled servers.
GitHub Create Pull Request
Azure Arc Azure Connected Machine Agent Deployment Options .../main/articles/azure-arc/servers/deployment-options.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ windows_tools
Summary
The documentation lists both Linux and Windows as supported OS types for most onboarding methods, but there is a notable emphasis on Windows-specific tools and workflows. PowerShell is highlighted as a cross-platform option, but several onboarding methods (Windows Admin Center, Configuration Manager, Group Policy) are Windows-only and presented in detail. The PowerShell onboarding method is listed before Linux-native automation tools like Ansible, and there is no explicit mention of Linux shell (bash) or native Linux configuration management tools (e.g., shell scripts, cloud-init) for onboarding. Windows-centric tooling is described in more depth, and Windows-specific methods are given dedicated sections.
Recommendations
  • Add explicit Linux shell (bash) script examples and onboarding instructions alongside PowerShell examples.
  • Include references to Linux-native automation tools (e.g., cloud-init, shell scripts, Puppet, Chef) where appropriate.
  • Ensure that Linux onboarding methods are presented with equal prominence and detail as Windows methods.
  • Clarify which onboarding steps or scripts are cross-platform and provide OS-specific guidance where necessary.
  • Consider listing Linux and Windows methods in parallel or grouping them by OS type for clarity.
GitHub Create Pull Request
Azure Arc Enable VM Extensions Using Azure Resource Manager Template ...les/azure-arc/servers/manage-vm-extensions-template.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation provides ARM template examples for both Linux and Windows VM extensions, but all deployment command examples use Azure PowerShell exclusively, with no Azure CLI or Bash alternatives. This creates friction for Linux/macOS users who may prefer or require CLI or Bash-based workflows. Additionally, file path examples use Windows-style paths (e.g., D:\Azure\Templates), and the Windows custom script extension example hardcodes PowerShell usage, with no mention of Bash or shell alternatives for Linux. The documentation does mention that extensions can be deployed to Linux or Windows machines, but the operational instructions are Windows-centric.
Recommendations
  • Add equivalent Azure CLI deployment commands alongside PowerShell examples, especially for deploying ARM templates.
  • Include Linux/macOS file path examples (e.g., /home/user/Azure/Templates) where relevant.
  • Clarify that the commandToExecute parameter for Linux custom script extensions should use shell commands (e.g., bash script.sh), and provide an explicit example.
  • Add a note or section on how to perform these deployments from Linux/macOS environments, including prerequisites (e.g., Azure CLI installation).
GitHub Create Pull Request
Azure Arc Connect machines from Azure Automation Update Management ...zure-arc/servers/onboard-update-management-machines.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation generally describes a process that applies to both Windows and Linux machines, but several sections and examples show a Windows-first pattern. References to Azure PowerShell for status retrieval are given without equivalent Linux CLI examples, and there is a lack of explicit Linux command-line or shell examples. The runbook naming convention also puts 'Windows' first, and troubleshooting/verification steps reference PowerShell and portal workflows more familiar to Windows users.
Recommendations
  • Provide explicit Linux shell (bash) examples alongside PowerShell examples for tasks such as retrieving job statuses.
  • Mention Azure CLI commands for verification and management, not just Azure PowerShell.
  • Ensure that runbook and automation instructions clarify parity for Linux users, including any OS-specific steps.
  • Add screenshots or walkthroughs for Linux onboarding and verification, if they differ from Windows.
  • Review the order of presentation so that Windows and Linux are treated equally (e.g., alternate which OS is mentioned first, or present both together).
GitHub Create Pull Request
Azure Arc REST API Requests for the Run Command on Azure Arc-enabled Servers (Preview) ...ob/main/articles/azure-arc/servers/run-command-rest.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation page for REST API Requests for the Run Command on Azure Arc-enabled Servers demonstrates a notable Windows bias. All example scenarios, scripts, and references are specific to Windows Server (e.g., Windows Server 2012/R2), using PowerShell cmdlets (New-NetFirewallRule) and Windows-specific tools (New-AzStorageBlobSASToken). There are no examples, scripts, or guidance for Linux Arc-enabled servers, nor any mention of Linux shell commands or tools. The documentation assumes a Windows context throughout, creating friction for Linux users who wish to use the REST API for remote command execution.
Recommendations
  • Add parallel example scenarios for Linux Arc-enabled servers, such as configuring firewall rules using bash scripts or iptables.
  • Include sample REST API payloads with Linux shell scripts (e.g., inline bash or referencing .sh files in blob storage).
  • Mention Linux equivalents for generating SAS tokens (e.g., using Azure CLI az storage commands).
  • Clarify in the introduction that the REST API supports both Windows and Linux servers, and provide links to Linux-specific documentation if available.
  • Ensure references to tools and scripting languages are balanced between Windows and Linux contexts.
GitHub Create Pull Request
Azure Arc Migrate Azure Arc-enabled server to Azure ...rticles/azure-arc/servers/scenario-migrate-to-azure.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation frequently references Azure PowerShell commands and workflows, often listing PowerShell before Azure CLI. Examples and instructions for inventorying extensions and reviewing access rights are PowerShell-centric, with CLI mentioned but not exemplified. Export instructions (e.g., to CSV) are PowerShell-focused, and there is a lack of explicit Linux/macOS shell examples (e.g., Bash). While the Azure Guest Agent section does mention both Windows and Linux agents, most procedural steps and examples prioritize Windows/PowerShell tools.
Recommendations
  • Provide Bash/Azure CLI examples alongside PowerShell for all relevant steps, especially for inventorying extensions and exporting data.
  • Explicitly mention Linux/macOS workflows where applicable, such as uninstalling the Connected Machine agent or installing the Linux Guest Agent.
  • Ensure that CLI and PowerShell instructions are presented with equal prominence, or group them by platform to avoid Windows-first ordering.
  • Add notes or links for Linux/macOS users for steps that differ from Windows, such as file export formats and shell commands.
GitHub Create Pull Request
Azure Arc Configuration and remote access ...es/azure-arc/servers/security-machine-configuration.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation introduces Azure Machine Configuration as a PowerShell Desired State Configuration-based tool, which may suggest a Windows-first approach. Windows Admin Center (WAC) is described as a key remote management scenario, with detailed role assignments and workflow, while Linux remote access is covered primarily through SSH. The documentation provides more detail and context for Windows tools and workflows (WAC, PowerShell DSC) than for Linux equivalents, and Windows terminology and examples appear before Linux ones.
Recommendations
  • Provide equivalent Linux configuration management examples, such as integration with Ansible or Chef, if supported.
  • Include Linux-first or cross-platform examples for compliance and configuration, not just PowerShell DSC.
  • Expand the SSH section to include more details about Linux-specific workflows, troubleshooting, and best practices.
  • Clarify that PowerShell DSC is not required for Linux machines, and mention any Linux-native alternatives if available.
  • Balance the coverage of Windows Admin Center with information about Linux management tools or clarify that WAC is Windows-only.
GitHub Create Pull Request
Azure Arc Run command on Azure Arc-enabled servers (Preview) ...cs/blob/main/articles/azure-arc/servers/run-command.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation mentions both Windows and Linux support, but the examples and next steps prioritize Windows-centric tools (PowerShell) and list Windows-oriented experiences before Linux equivalents (Azure CLI). There are no Linux-specific examples or references to Linux shell scripting, and PowerShell is highlighted as a primary method, which may create friction for Linux users who prefer Bash or native Linux tools.
Recommendations
  • Add explicit Linux shell (Bash) examples and references alongside PowerShell, especially in introductory sections.
  • Ensure that Azure CLI examples are shown before or alongside PowerShell examples, as CLI is more cross-platform.
  • Clarify that Run command supports both Windows and Linux scripts, and provide sample use cases for each OS.
  • Include links to Linux-specific documentation or best practices for using Run command on Linux Arc-enabled servers.
GitHub Create Pull Request
Azure Arc Security overview ...b/main/articles/azure-arc/servers/security-overview.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation generally describes Azure Arc-enabled servers in a cross-platform manner, noting differences between Windows and Linux for agent services. However, the only concrete example given for extension allowlisting references Windows-specific extensions (AzureMonitorWindowsAgent, MDE.Windows) and does not provide Linux equivalents or mention how to configure for Linux scenarios. The guest configuration section references PowerShell Desired State Configuration, which is primarily a Windows technology, without discussing Linux alternatives or limitations.
Recommendations
  • Provide example allowlist configurations for Linux servers, referencing Linux-specific extensions (e.g., AzureMonitorLinuxAgent, MDE.Linux) where applicable.
  • Clarify the applicability and limitations of guest configuration policies for Linux, and mention any Linux-compatible alternatives.
  • When giving examples, include both Windows and Linux scenarios, or explicitly state when an example is Windows-only.
  • Consider referencing cross-platform tools and patterns before Windows-specific ones, or present them in parallel.
GitHub Create Pull Request
Azure Arc Troubleshoot Azure Arc-enabled servers in disconnected scenarios ...rticles/azure-arc/servers/troubleshoot-connectivity.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation references Windows-specific tools (Windows Admin Center, Configuration Manager) as contingency options for managing disconnected servers, without mentioning equivalent Linux tools or approaches. No Linux/macOS management alternatives or examples are provided, which may leave non-Windows users without clear guidance.
Recommendations
  • Add references to Linux-compatible management tools (e.g., Cockpit, Ansible, SSH, or other local Linux administration utilities) for managing Arc-enabled servers in disconnected scenarios.
  • Include examples or guidance for Linux/macOS users on how to monitor, manage, and troubleshoot Arc-enabled servers when disconnected.
  • Clarify that the contingency options are not limited to Windows environments and provide parity for Linux/macOS users.
GitHub Create Pull Request
Azure Arc Security onboarding and updates ...main/articles/azure-arc/servers/security-onboarding.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation generally covers both Windows and Linux scenarios for Azure Arc-enabled servers, but there are several instances of Windows bias. Windows-specific tools (Group Policy, Configuration Manager, WSUS) are mentioned before Linux equivalents, and PowerShell is referenced more frequently than Linux shell commands. Windows update mechanisms are described in detail before Linux package management. Some examples and links (e.g., Group Policy onboarding guidance) are Windows-centric, and Windows terminology appears first in several sections.
Recommendations
  • Provide Linux shell (bash) examples alongside PowerShell where relevant, especially for onboarding and extension management.
  • Mention Linux automation tools (e.g., Ansible, Chef, Puppet) with equal prominence to Windows tools like Group Policy and Configuration Manager.
  • Ensure update instructions for Linux (apt, yum, dnf, zypper) are presented with the same level of detail and priority as Windows Update/WSUS.
  • Where links or references are Windows-specific (e.g., Group Policy onboarding), offer equivalent Linux guidance or clarify when features are Windows-only.
  • Alternate the order of Windows and Linux examples to avoid consistently listing Windows first.
GitHub Create Pull Request
Azure Arc Troubleshoot SSH access to Azure Arc-enabled servers ...ain/articles/azure-arc/servers/ssh-arc-troubleshoot.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page for troubleshooting SSH access to Azure Arc-enabled servers demonstrates a notable Windows/PowerShell bias. Many troubleshooting steps and examples reference Azure PowerShell modules (Az.Ssh, Az.Ssh.ArcProxy) and provide PowerShell commands exclusively, with no equivalent instructions for Linux/macOS users. In sections where both Azure CLI and PowerShell could be used, PowerShell is often mentioned first or exclusively. There is a lack of explicit Linux/macOS guidance for installing required modules or resolving common issues, and some error messages are Windows-specific.
Recommendations
  • Provide Linux/macOS-specific troubleshooting steps, including installation and usage of Azure CLI for SSH access.
  • Include bash or shell command examples alongside PowerShell commands, especially for module installation and updates.
  • Clarify which steps are platform-agnostic and which are Windows-specific, and offer alternatives for non-Windows environments.
  • Add guidance for resolving PATH and permissions issues on Linux/macOS, not just referencing PowerShell.
  • Ensure error messages and solutions cover both Windows and Linux/macOS scenarios equally.
GitHub Create Pull Request
Azure Arc Troubleshoot Azure Arc-enabled servers networking issues .../articles/azure-arc/servers/troubleshoot-networking.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example ⚠️ windows_first
Summary
The documentation focuses exclusively on troubleshooting TLS cipher suite configuration for Windows, providing only PowerShell, Group Policy, and Windows Registry methods. There are no Linux or macOS examples, nor any mention of how to check or configure cipher suites on non-Windows Arc-enabled servers, despite Azure Arc supporting Linux servers.
Recommendations
  • Add equivalent instructions for Linux systems, such as how to check enabled TLS cipher suites using 'openssl' or 'nmap', and how to configure cipher suites in common Linux distributions (e.g., by editing OpenSSL or GnuTLS configuration files).
  • Include a section clarifying whether Linux servers are affected by the same requirements, or if the issue is Windows-specific.
  • If the troubleshooting is only relevant for Windows, state this clearly at the top of the section to avoid confusion for Linux users.
  • Provide parity in troubleshooting steps for both Windows and Linux Arc-enabled servers where applicable.
GitHub Create Pull Request
Azure Arc Tutorial - Monitor a hybrid machine with Azure Monitor VM insights ...icles/azure-arc/servers/tutorial-enable-vm-insights.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation claims to support both Linux and Windows hybrid machines, but examples and details are primarily Windows-centric. The section on viewing log events specifically references the Windows event log and does not provide equivalent guidance or examples for Linux systems (e.g., syslog or journald). Additionally, the Event table is described only in the context of Windows, with no Linux log table example or query shown.
Recommendations
  • Explicitly describe and provide examples for viewing Linux log events (e.g., syslog, journald) in Log Analytics.
  • Include screenshots or queries for Linux-specific log tables, such as Syslog or Linux-specific performance counters.
  • Clarify differences in data collection and available tables between Windows and Linux machines.
  • Ensure that instructions and UI references apply equally to Linux systems, or note any differences.
GitHub Create Pull Request
Azure Arc Install Arc agent at scale for your VMware VMs ...arc/vmware-vsphere/enable-guest-management-at-scale.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ windows_first
Summary
The documentation page demonstrates a moderate Windows bias, particularly in the 'Auto Arc-enablement script' section, which provides only PowerShell-based automation examples and references Windows Task Scheduler for cron jobs. The script usage instructions assume a Windows environment, with no mention of Linux/macOS equivalents or alternatives. While out-of-band methods do mention Ansible (Linux-friendly), most step-by-step examples and automation focus on Windows tools and patterns, and Windows-centric instructions are presented first.
Recommendations
  • Provide equivalent Linux/macOS automation examples for the auto-enablement script, such as Bash scripts and instructions for running as a cron job on Linux.
  • Include cross-platform instructions for downloading and running the helper script, clarifying compatibility and prerequisites for Linux/macOS.
  • When presenting automation examples, alternate or parallelize Windows and Linux/macOS instructions to avoid Windows-first bias.
  • Explicitly mention how Linux users can schedule agent installation tasks (e.g., using cron) and provide sample crontab entries.
  • Ensure that all referenced scripts and tools are cross-platform or provide platform-specific alternatives.
GitHub Create Pull Request
Azure Arc Diagnostics of Edge-Related Logs and Errors in Workload Orchestration .../azure-arc/workload-orchestration/diagnose-problems.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page demonstrates a notable Windows bias. All command-line examples use PowerShell syntax and conventions (e.g., backticks for line continuation, .ps1 scripts), and file paths in JSON templates are Windows-style (e.g., C:\Users\...). There are no Bash, Linux shell, or cross-platform CLI examples, nor any mention of how to adapt the instructions for Linux/macOS environments. The use of PowerShell and Windows file paths is pervasive, and Linux users are left to infer how to run these commands or adapt scripts.
Recommendations
  • Provide equivalent Bash/Linux shell examples for all PowerShell commands, especially for az CLI usage.
  • Use cross-platform file path conventions in templates, or provide separate examples for Windows and Linux/macOS.
  • Document how to run onboarding scripts (.ps1) on Linux/macOS, or provide alternative scripts (e.g., Bash).
  • Clarify which steps are platform-agnostic and which require adaptation for non-Windows environments.
  • Add notes or sections explicitly addressing Linux/macOS usage and troubleshooting.
GitHub Create Pull Request
Azure Arc Migrate Existing Target Resources to General Availability ...s/azure-arc/workload-orchestration/migration-script.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation provides only a PowerShell script for migration and instructs users to run it in PowerShell, with no mention of Bash, Linux shell, or cross-platform alternatives. This creates friction for Linux/macOS users who may not have PowerShell installed or prefer native shell environments.
Recommendations
  • Provide a Bash or cross-platform shell script alternative for Linux/macOS users.
  • Document how to run the PowerShell script on Linux/macOS (e.g., using PowerShell Core, installation instructions, and compatibility notes).
  • Explicitly state platform requirements and offer guidance for non-Windows environments.
GitHub Create Pull Request
Azure Arc Perform disaster recovery operations ...mware-vsphere/recover-from-resource-bridge-deletion.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation exclusively provides PowerShell examples and references a '.ps1' onboarding script, with no mention of Bash, shell, or Linux/macOS-compatible alternatives. All code snippets and instructions assume a Windows environment, creating friction for users on Linux or macOS platforms.
Recommendations
  • Provide equivalent onboarding scripts and instructions for Bash/shell environments, or clarify if the script is cross-platform.
  • Include Linux/macOS-specific steps for running the onboarding script, such as using Azure CLI or PowerShell Core on non-Windows systems.
  • Explicitly state platform requirements and offer guidance for Linux/macOS users (e.g., using PowerShell Core, prerequisites, or alternative tooling).
  • If the onboarding script is Windows-only, consider providing a containerized or cross-platform version.
GitHub Create Pull Request
Azure Arc Clean-Up Script for Workload Orchestration ...es/azure-arc/workload-orchestration/clean-up-script.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation provides only PowerShell script examples and instructions, with no mention of Linux/macOS equivalents or how to run the clean-up script on non-Windows platforms. The script is a .ps1 file, which is natively supported only on Windows, and there are no Bash, shell, or cross-platform alternatives discussed.
Recommendations
  • Provide instructions for running the PowerShell script using PowerShell Core (pwsh) on Linux/macOS, if supported.
  • Explicitly state whether the script is compatible with PowerShell Core on non-Windows platforms.
  • If the script is Windows-only, offer a Bash or shell script alternative for Linux/macOS users.
  • Add example commands for Linux/macOS environments, including prerequisites for installing PowerShell Core if needed.
GitHub Create Pull Request
Azure Arc Prepare the Environment for Workload Orchestration ...rc/workload-orchestration/initial-setup-environment.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation exhibits Windows bias in several areas. The example for installing kubectl uses Windows-specific tooling (winget) without providing a Linux/macOS alternative. In the section on extracting ZIP files, the Bash tab incorrectly uses the Windows PowerShell command Expand-Archive, which does not exist on Linux/macOS. There are no Linux/macOS-specific instructions for these basic setup steps, which may cause confusion or friction for non-Windows users. Throughout the rest of the document, Bash and PowerShell examples are provided in parallel, but the initial steps and tooling favor Windows.
Recommendations
  • For kubectl installation, provide platform-specific instructions: use apt, yum, brew, or direct download for Linux/macOS users.
  • In the ZIP extraction section, replace Expand-Archive in the Bash tab with a Linux/macOS-compatible command such as unzip or tar.
  • Review all example commands to ensure they are valid and tested on Linux/macOS environments.
  • Consider listing Linux/macOS instructions before or alongside Windows instructions to avoid implicit prioritization.
  • Add explicit notes or tabs for macOS if there are platform-specific considerations.
GitHub Create Pull Request
Azure Arc Troubleshooting for Workload Orchestration ...es/azure-arc/workload-orchestration/troubleshooting.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The troubleshooting documentation for workload orchestration in Azure Arc shows a notable Windows bias. Most command-line examples outside the 'service groups' section are given only in PowerShell syntax, with no Bash or Linux shell equivalents. Tasks such as registry management, token handling, and image inspection use PowerShell-specific constructs and variables, which may not work natively on Linux/macOS. Only the 'service groups' section provides both Bash and PowerShell tabs, while the majority of troubleshooting steps assume a Windows/PowerShell environment.
Recommendations
  • Provide Bash/Linux shell equivalents for all PowerShell commands, especially for az CLI, kubectl, and docker operations.
  • Avoid using PowerShell-specific syntax (e.g., variable assignment, piping to ConvertTo-Json, Out-File) in generic Azure CLI or Kubernetes examples; use cross-platform syntax or clearly separate Windows and Linux instructions.
  • Explicitly note any platform-specific requirements, and offer guidance for Linux/macOS users where differences exist (e.g., file encoding, JSON creation).
  • Where possible, use az CLI commands in a platform-neutral way, and clarify when PowerShell is required.
GitHub Create Pull Request
Azure Portal Create an Azure portal dashboard by using a Bicep file .../blob/main/articles/azure-portal/quick-create-bicep.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation provides deployment instructions using both Azure CLI and Azure PowerShell, but the example VM is hard-coded as a Windows VM ('SimpleWinVM'), and all username/password requirements link to Windows VM documentation. There are no examples or guidance for deploying a Linux VM or adapting the dashboard for Linux workloads. The PowerShell example is given equal prominence to CLI, but the overall workflow is Windows-centric.
Recommendations
  • Add instructions and examples for deploying a Linux VM (e.g., Ubuntu) as the dashboard target, including links to Linux VM username/password requirements.
  • Clarify that the dashboard can be adapted for Linux VMs and provide sample Bicep/ARM templates for Linux VM scenarios.
  • Ensure that CLI examples do not assume Windows-specific VM names or parameters, and provide alternative values for Linux users.
  • Mention that Azure CLI is cross-platform and highlight its use for Linux/macOS users.
GitHub Create Pull Request
Azure Portal Create an Azure portal dashboard by using an Azure Resource Manager template ...ob/main/articles/azure-portal/quick-create-template.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_first
Summary
The documentation page demonstrates a notable Windows bias in its instructions for creating the prerequisite VM. Only PowerShell commands are provided, with explicit selection of PowerShell in Azure Cloud Shell, and references to Windows-specific username/password requirements. There are no Bash or Azure CLI examples, nor guidance for Linux users, even though the Azure Cloud Shell supports Bash and Linux VMs are common in Azure. The resource group and VM names also use 'Win' and imply a Windows VM, but the dashboard creation itself is not inherently Windows-specific.
Recommendations
  • Provide equivalent Bash/Azure CLI instructions for creating the resource group and VM, including examples for Linux VM creation.
  • Clarify that users may use either PowerShell or Bash in Cloud Shell, and link to documentation for both.
  • Use more neutral resource group and VM names (e.g., 'SimpleVmResourceGroup', 'myVM1') unless the dashboard template is strictly Windows VM-specific.
  • Include notes or links for Linux VM username/password requirements if relevant.
GitHub Create Pull Request
Container Registry Azure Container Registry Authentication Options Explained ...ontainer-registry/container-registry-authentication.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation provides both Azure CLI and PowerShell examples for authentication, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI throughout, and is referenced in nearly every authentication scenario. Examples and instructions for Linux-native workflows (e.g., Bash, shell scripting) are minimal, and PowerShell is presented before or alongside CLI in most cases. There are no explicit Linux/macOS shell script examples for common tasks (e.g., using environment variables, credential management), and the 'Next steps' section only links to Azure CLI and PowerShell guides, omitting Linux-specific or cross-platform container tool guides. The section on alternative container tools (podman) is brief and lacks detailed Linux workflow examples.
Recommendations
  • Add explicit Bash/shell script examples for authentication flows, especially for service principal and token-based logins.
  • Include Linux/macOS-specific instructions for credential management and environment variable usage.
  • Expand the section on alternative container tools (podman) with step-by-step Linux workflow examples, including troubleshooting and best practices.
  • In 'Next steps', link to cross-platform container tool guides (e.g., podman, nerdctl) and Linux/macOS getting started guides.
  • Consider presenting Azure CLI (cross-platform) examples before PowerShell, and clarify that PowerShell is primarily for Windows users.
GitHub Create Pull Request
Azure Portal Create an Azure portal dashboard with Azure CLI .../azure-portal/quickstart-portal-dashboard-azure-cli.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page demonstrates a bias towards Windows by providing only a Windows VM creation example and referencing Windows-specific username/password requirements. There are no examples or guidance for creating Linux VMs, which are equally supported in Azure and commonly used. This may cause friction for Linux users attempting to follow the quickstart.
Recommendations
  • Add a Linux VM creation example alongside the Windows example, using an appropriate image (e.g., UbuntuLTS) and Linux authentication options (e.g., SSH keys).
  • Include notes or links to Linux VM username/password requirements and best practices.
  • Clarify that the dashboard template and Azure CLI commands work for both Windows and Linux VMs.
  • Present both Windows and Linux examples in parallel, or indicate how to adapt the instructions for Linux users.
GitHub Create Pull Request
Container Registry Quickstart - Create Registry - Bicep ...ainer-registry/container-registry-get-started-bicep.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying the Bicep file, but PowerShell is presented as an equal option and is mentioned in the instructions to 'open PowerShell or Azure CLI.' The instructions for opening the integrated Visual Studio Code terminal use the 'ctrl + ` ' shortcut, which is Windows-centric. There are no explicit Linux/macOS examples or notes about platform differences, and PowerShell is not natively available on Linux/macOS by default. The documentation does not mention Bash or shell alternatives, nor does it clarify cross-platform usage for PowerShell.
Recommendations
  • Clarify that Azure CLI commands work on Windows, Linux, and macOS, and recommend it as the default cross-platform option.
  • Add explicit Bash/shell instructions or notes for Linux/macOS users, including how to open the terminal in VS Code on those platforms.
  • Note that PowerShell Core is available on Linux/macOS, but Azure CLI is typically more common for cross-platform scenarios.
  • Present Azure CLI examples first, as it is the most universally available tool.
GitHub Create Pull Request
Container Registry Push & Pull Container Image using Azure Container Registry ...-registry/container-registry-get-started-docker-cli.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for authentication and image removal, but PowerShell examples are given equal prominence despite being Windows-specific. There are no explicit Linux shell (bash) or macOS Terminal examples for Azure authentication or image removal, and Windows-centric tools (PowerShell, Visual Studio Code) are mentioned before Linux alternatives. Minor friction exists for Linux/macOS users who may prefer bash or shell scripting over PowerShell.
Recommendations
  • Add explicit bash/shell examples for Azure authentication and image removal, using Azure CLI and native shell commands.
  • Clarify that PowerShell examples are primarily for Windows users, and provide equivalent steps for Linux/macOS users.
  • Mention Linux/macOS-friendly editors (e.g., VS Code is cross-platform, but alternatives like JetBrains IDEs or command-line workflows could be referenced).
  • Ensure that CLI examples are shown before or alongside PowerShell examples, and label tabs clearly for each platform.
GitHub Create Pull Request
Container Registry Error Reference for Registry Health Checks ...-registry/container-registry-health-error-reference.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation generally describes errors and solutions in a cross-platform manner, referencing CLI tools (Docker, Helm, Notary) that are available on Windows, Linux, and macOS. However, some sections show Windows bias: Windows paths and .exe files are mentioned first or exclusively (e.g., Notary client installation), environment variable instructions use Windows terminology ('system variables'), and Linux/macOS installation paths/examples are less detailed or omitted. There are no explicit Linux/macOS command examples or troubleshooting steps, which may create friction for non-Windows users.
Recommendations
  • Provide Linux/macOS-specific installation instructions and paths alongside Windows examples (e.g., where to place Notary binaries, how to update PATH).
  • Use cross-platform terminology for environment variables (e.g., 'system environment variables' vs. 'PATH variable'), and give examples for both Windows (setx, GUI) and Linux/macOS (export, ~/.bashrc, ~/.zshrc).
  • When referencing executables, clarify platform differences (e.g., notary.exe for Windows, notary for Linux/macOS).
  • Add troubleshooting steps and example commands for Linux/macOS users where relevant.
GitHub Create Pull Request
Container Registry Import Container Images to ACR using Azure APIs ...container-registry/container-registry-import-images.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation provides examples exclusively for Azure CLI and Azure PowerShell, with no mention of Linux/macOS-specific shell environments or command patterns. PowerShell examples are given equal prominence to CLI, and in some sections, Windows-specific images (e.g., Windows Server Core) are highlighted. There are no bash or Linux-native command examples, nor any discussion of platform-specific considerations for Linux/macOS users.
Recommendations
  • Add explicit bash examples for Linux/macOS users, especially for Azure CLI commands, demonstrating usage in typical Linux shells.
  • Clarify that Azure CLI commands work cross-platform and provide notes or examples for Linux/macOS environments (e.g., using bash, zsh, etc.).
  • When referencing PowerShell, note its availability on Linux/macOS, or provide equivalent bash commands where possible.
  • Avoid highlighting Windows container images unless the scenario is Windows-specific; provide parity by showing Linux container image examples (e.g., Ubuntu, Alpine) alongside Windows ones.
  • Include troubleshooting notes for common Linux/macOS issues (e.g., authentication, environment variables, shell quoting).
GitHub Create Pull Request
Container Registry Store Helm Charts in Azure Container Registry ...es/container-registry/container-registry-helm-repos.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page provides command-line examples for Helm and Azure CLI, which are cross-platform tools. However, there is evidence of Windows bias in the use of the 'set' command for environment variable assignment, which is specific to Windows CMD. No equivalent Linux/macOS example (e.g., 'export') is provided. Additionally, the order of Kubernetes cluster creation options lists Azure CLI first, but also mentions Azure PowerShell and Azure Portal, which is acceptable. Most other commands use Bash-style syntax, which is cross-platform, but the initial environment variable example may cause confusion for Linux/macOS users.
Recommendations
  • Provide both Windows and Linux/macOS environment variable assignment examples (e.g., 'set' for Windows CMD, 'export' for Bash).
  • Clarify which commands are platform-specific and offer alternatives where needed.
  • Consider using Bash syntax for environment variables throughout, as Azure CLI and Helm are typically used in Bash on all platforms.
  • Add a note or table summarizing command differences for Windows, Linux, and macOS users.
GitHub Create Pull Request
Copilot Use Azure Copilot with AI Shell ...t-docs/blob/main/articles/copilot/ai-shell-overview.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation page for 'Use Azure Copilot with AI Shell' demonstrates a notable bias toward Windows and PowerShell. It emphasizes PowerShell usage (including requiring the AIShell PowerShell module), references PowerShell-specific resources, and does not provide explicit examples or guidance for Linux/macOS users or alternative shells. There are no Linux/macOS installation instructions or examples, and the documentation links point to PowerShell-centric resources.
Recommendations
  • Provide explicit instructions and examples for installing and using AI Shell on Linux and macOS terminals (e.g., bash, zsh).
  • Clarify whether the AIShell module is available or necessary for non-Windows platforms, or provide alternative modules/tools if needed.
  • Include examples of AI Shell generating Azure CLI commands in Linux/macOS environments, not just PowerShell.
  • Reference cross-platform documentation and repositories, not only PowerShell-specific ones.
  • Add a section addressing platform compatibility and any limitations for non-Windows users.
GitHub Create Pull Request
Copilot Optimization agent capabilities in Agents (preview) in Azure Copilot ...-docs/blob/main/articles/copilot/optimization-agent.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation mentions both Azure CLI and PowerShell script generation, but the sample prompts explicitly show PowerShell first and only mention CLI generically, without specifying Bash or Linux-specific usage. There are no Linux/macOS-specific examples or references to shell environments other than PowerShell, and PowerShell is presented as the default scripting option in the sample prompts.
Recommendations
  • Provide explicit examples of both PowerShell and Bash/Azure CLI scripts in sample prompts, ensuring parity for Linux/macOS users.
  • Clarify that Azure CLI scripts can be used in Bash or other shell environments on Linux/macOS.
  • Include a note or section on running optimization scripts on Linux/macOS, with links to relevant Azure CLI documentation.
  • Alternate the order of PowerShell and CLI examples, or present them side-by-side, to avoid Windows-first bias.
GitHub Create Pull Request
Lighthouse Azure Lighthouse architecture ...blob/main/articles/lighthouse/concepts/architecture.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation page on Azure Lighthouse architecture demonstrates a moderate Windows bias. PowerShell is referenced as the primary example for creating registration definitions, and Azure PowerShell is mentioned before Azure CLI or other cross-platform tools. While Azure CLI is referenced in the 'Next steps' section, the main body of the documentation prioritizes PowerShell, which is more commonly associated with Windows environments. No explicit Linux/macOS examples or workflows are provided.
Recommendations
  • Include Azure CLI examples alongside PowerShell for key operations such as creating registration definitions and assignments.
  • Clarify that both Azure PowerShell and Azure CLI are cross-platform, and provide links or code snippets for both.
  • Consider adding a brief section or callout for Linux/macOS users, highlighting any platform-specific considerations or confirming parity.
  • Ensure that references to management tools do not implicitly suggest Windows-only workflows.
GitHub Create Pull Request
Lighthouse Monitor delegated resources at scale ...ob/main/articles/lighthouse/how-to/monitor-at-scale.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias, particularly in the section about registering resource providers in the managing tenant. The only provided automation example uses Azure PowerShell, with no mention of Azure CLI or REST API alternatives, which are more cross-platform and commonly used on Linux/macOS. The documentation also refers to PowerShell before any other tool, and does not provide Linux/macOS-specific guidance for these steps.
Recommendations
  • Add Azure CLI examples alongside PowerShell for resource provider registration and service principal creation.
  • Explicitly mention that Azure CLI and REST API can be used on Linux/macOS for all automation steps.
  • Where PowerShell is referenced, provide equivalent commands for other platforms or link to cross-platform documentation.
  • Clarify that the Azure portal and Resource Manager templates are platform-agnostic, and highlight their use for Linux/macOS users.
GitHub Create Pull Request
Lighthouse Onboard all subscriptions in a management group ...articles/lighthouse/how-to/onboard-management-group.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_first
Summary
The documentation provides only a PowerShell example for assigning the policy at the management group level, with no equivalent CLI (az), Bash, or ARM template instructions. This creates friction for Linux/macOS users who may not use PowerShell, and the example is presented as the sole method for this critical step.
Recommendations
  • Add Azure CLI (az policy assignment create) instructions for assigning the policy at the management group level.
  • Provide Bash or cross-platform scripting examples where possible.
  • Clarify that PowerShell is one option and link to documentation for other methods (e.g., Azure Portal, ARM templates, REST API).
  • Consider presenting CLI or cross-platform examples before or alongside PowerShell to avoid Windows-first impression.
GitHub Create Pull Request
Lighthouse Monitor delegation changes in your managing tenant ...ticles/lighthouse/how-to/monitor-delegation-changes.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_first
Summary
The documentation provides detailed PowerShell scripts for querying delegation changes, but does not offer equivalent examples using Bash, shell scripting, or cross-platform tools. While Azure CLI is mentioned for role assignment, the main workflow for querying and reporting is PowerShell-centric, which may create friction for Linux/macOS users. PowerShell examples are shown first and in greater detail, with no alternative Linux-native scripting guidance.
Recommendations
  • Provide equivalent Bash or shell script examples for querying the Tenant Activity Log using Azure CLI and REST API calls.
  • Highlight cross-platform approaches, such as using Python or other language SDKs, for automation tasks.
  • Clarify that PowerShell Core is available cross-platform, but also offer guidance for users who prefer native Linux/macOS tools.
  • Ensure that Azure CLI examples are as detailed as PowerShell ones, especially for querying and reporting delegation changes.
GitHub Create Pull Request
Lighthouse Deploy Azure Policy to delegated subscriptions at scale ...lob/main/articles/lighthouse/how-to/policy-at-scale.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools ⚠️ windows_first
Summary
The documentation exclusively provides PowerShell examples and references Azure PowerShell cmdlets for all steps, without mentioning or providing equivalent instructions for Azure CLI, Bash, or other cross-platform tools. This creates friction for Linux/macOS users who may not have PowerShell installed or prefer native shell environments.
Recommendations
  • Add equivalent Azure CLI examples for all major steps (querying Resource Graph, deploying ARM templates, validating policy, and cleanup).
  • Explicitly mention that PowerShell is available cross-platform, but provide installation guidance for Linux/macOS if PowerShell is required.
  • Where possible, show both PowerShell and Azure CLI/Bash examples side-by-side, or link to CLI documentation.
  • Clarify tool prerequisites for non-Windows users at the start of the document.
GitHub Create Pull Request
Azure Arc CLI reference for `azcmagent disconnect` ...ain/articles/azure-arc/servers/azcmagent-disconnect.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ windows_first
Summary
The documentation provides authentication options for both Windows and Linux, but the interactive browser login is described as 'Windows only' and presented first, while the Linux-default device code login is described second. All examples and instructions are otherwise platform-neutral, and Linux authentication flows are clearly documented.
Recommendations
  • Present authentication options in a platform-neutral order, or explicitly state which options are default for each OS before listing them.
  • Consider grouping Windows and Linux authentication flows together, or providing parallel examples for each platform where differences exist.
  • Clarify that the 'interactive browser login' is available on Windows desktop, but device code is default on Linux and Windows Server Core, to avoid implying Windows is primary.
GitHub Create Pull Request
Azure Arc Limit access to Run command ...ain/articles/azure-arc/servers/run-command-security.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ windows_first
Summary
The documentation provides both Windows and Linux examples for managing Run command access, but the Windows example is presented before the Linux example. There are no missing Linux examples or exclusive references to Windows tools; both platforms are treated with parity in terms of actionable guidance.
Recommendations
  • Alternate the order of Windows and Linux examples in documentation, or present them side-by-side to avoid the perception of platform preference.
  • Consider clarifying that both Windows and Linux are supported equally in introductory sections.
GitHub Create Pull Request
Azure Arc Delete Resources in Workload Orchestration ...s/azure-arc/workload-orchestration/delete-resources.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ windows_first
Summary
The documentation provides both Bash and PowerShell examples for all commands, but consistently lists Bash examples before PowerShell. There are no Windows-specific tools or patterns, and Linux users are fully supported via Bash examples. No Linux parity issues are present, but the ordering could be improved for neutrality.
Recommendations
  • Continue providing both Bash and PowerShell examples to support cross-platform usage.
  • Consider alternating the order of Bash and PowerShell examples, or explicitly state that both are equally supported.
  • Add a brief note clarifying that all commands work on Linux, macOS, and Windows (with Bash or PowerShell), to reassure users.
GitHub Create Pull Request
Azure Arc Multiple Solutions with a Single Shared Dependency at Different Levels ...oad-orchestration/tutorial-service-group-scenario-4.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ windows_first
Summary
The documentation provides both Bash and PowerShell examples for all steps, but consistently lists Bash examples before PowerShell. There are no Windows-only tools or patterns, and all commands use cross-platform Azure CLI and Helm. No Linux examples are missing, and no Windows-specific tools are mentioned. The only minor bias is the ordering of Bash before PowerShell, which may slightly favor Linux/macOS users rather than Windows.
Recommendations
  • Consider clarifying that both Bash and PowerShell examples are equally supported and that users can choose either based on their environment.
  • Optionally, alternate the order of Bash and PowerShell tabs in different sections to avoid perceived preference.
  • Ensure that any environment setup instructions (linked from prerequisites) also provide parity for both Bash and PowerShell users.
GitHub Create Pull Request
Azure Arc Create a Solution with Multiple Dependencies with Workload Orchestration ...quickstart-solution-multiple-shared-adapter-dependency.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for every CLI step, but PowerShell examples are consistently shown after Bash. There is no exclusive use of Windows tools or patterns, and Linux parity is maintained throughout. However, the presence of PowerShell examples for every command, even when Bash is sufficient for cross-platform use, can be considered a mild Windows bias.
Recommendations
  • Consider listing Bash examples first, as Bash is the default shell on Linux and macOS, and is also available on Windows via WSL and Git Bash.
  • Clarify that Bash examples work on Linux, macOS, and Windows (with WSL or Git Bash), while PowerShell is primarily for Windows users.
  • Where possible, consolidate examples to Bash unless there is a specific PowerShell-only scenario.
  • Add a short note at the top explaining shell compatibility for Linux/macOS/Windows users.
GitHub Create Pull Request
Azure Arc Solution with a Non-Leaf Target ...oad-orchestration/tutorial-service-group-scenario-2.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ windows_first
Summary
The documentation provides both Bash and PowerShell examples for every step, but consistently lists Bash examples before PowerShell. There are no Windows-specific tools or patterns, and Linux parity is maintained throughout. No Linux examples are missing, and all commands use cross-platform Azure CLI and Helm tools.
Recommendations
  • Consider alternating the order of Bash and PowerShell tabs in different sections to avoid perceived preference.
  • Explicitly state that both Bash and PowerShell examples are equivalent and supported on their respective platforms.
  • Add a short note at the top clarifying that all examples are cross-platform unless otherwise noted.
GitHub Create Pull Request
Container Registry Managed Identity Authentication for ACR ...https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/container-registry-authentication-managed-identity.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all major steps, but PowerShell is a Windows-centric tool (even though it can run on Linux). The structure consistently presents Azure CLI examples first, followed by PowerShell, which is a minor 'Windows-first' bias. There are no examples or instructions that are Windows-only, and all VM creation and Docker installation steps target Ubuntu Linux. No critical Linux gaps are present.
Recommendations
  • Clarify that Azure PowerShell is cross-platform and provide guidance for Linux/macOS users on installing and using PowerShell if they are unfamiliar.
  • Consider adding Bash-only or native Linux shell examples for steps that do not require Azure CLI or PowerShell, where appropriate.
  • Explicitly state that all instructions are tested and supported on Linux VMs, and highlight any OS-specific caveats if they exist.
  • If possible, include a short section or note for macOS users, especially for Docker installation and Azure CLI/PowerShell usage.
GitHub Create Pull Request
Container Registry Azure Container Registry custom roles ...ainer-registry/container-registry-rbac-custom-roles.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for listing permissions, but PowerShell is mentioned alongside CLI in a way that may suggest parity. However, PowerShell is a Windows-centric tool, and its inclusion may create friction for Linux/macOS users. Additionally, in several places, Azure PowerShell is listed before or alongside Azure CLI, which is cross-platform, but there are no Linux/macOS-specific notes or examples. No Windows-only tools or patterns are exclusively used, and the core instructions are platform-neutral.
Recommendations
  • Prioritize Azure CLI examples and references, as CLI is cross-platform and preferred by Linux/macOS users.
  • Add explicit notes clarifying that Azure PowerShell is available on Linux/macOS, but CLI is recommended for those platforms.
  • Where multiple tool options are listed, present Azure CLI first, followed by PowerShell, to reduce perceived Windows bias.
  • Consider including a brief section or note for Linux/macOS users, confirming that all steps can be completed with Azure CLI.
GitHub Create Pull Request
Azure Arc Turn on transparent data encryption in SQL Managed Instance enabled by Azure Arc (preview) ...igure-transparent-data-encryption-sql-managed-instance.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ windows_first
Summary
The documentation provides both Windows and Linux examples for file operations involving kubectl, but Windows examples are consistently presented before Linux equivalents in several sections. There is no exclusive use of Windows tools, PowerShell, or missing Linux examples; parity is maintained in the instructions themselves.
Recommendations
  • Alternate the order of Windows and Linux examples in each section, or present Linux examples first in some sections to avoid implicit prioritization.
  • Add a short note at the beginning clarifying that both Windows and Linux are supported and examples for both are provided.
  • Consider grouping platform-specific instructions side-by-side or in a tabbed format to emphasize equal support.
GitHub Create Pull Request
Azure Arc Encrypt a database with transparent data encryption manually in SQL Managed Instance enabled by Azure Arc ...data/configure-transparent-data-encryption-manually.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ windows_first
Summary
The documentation provides both Windows and Linux examples for all relevant commands, using tabbed sections to distinguish them. However, in each case, the Windows example is presented first, which may subtly signal a Windows-first approach. There is no evidence of missing Linux examples, PowerShell-heavy content, or exclusive mention of Windows tools.
Recommendations
  • Alternate the order of Windows and Linux tabs in different sections to avoid consistently prioritizing Windows.
  • Consider presenting Linux examples first in some sections, especially since SQL Managed Instance enabled by Azure Arc is often deployed on Linux-based Kubernetes clusters.
  • Add a brief note at the top clarifying that both Windows and Linux are supported and that examples for both are provided.
GitHub Create Pull Request
Azure Arc Quickstart - Deploy Azure Arc-enabled data services - directly connected mode - Azure portal ...ttps://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/create-complete-managed-instance-directly-connected.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools
Summary
The documentation exhibits minor Windows bias, primarily in the ordering and presentation of examples and outputs. The Azure CLI output for 'az aks get-credentials' shows a Windows-style file path (C:<current path>\.kube\config), and the documentation does not mention Linux/macOS equivalents or clarify cross-platform differences. All commands are cross-platform, but the examples and screenshots implicitly assume a Windows environment. No PowerShell-specific commands or Windows-only tools are present, and all core steps are achievable on Linux/macOS.
Recommendations
  • Include example outputs for both Windows and Linux/macOS, especially for file paths (e.g., ~/.kube/config for Linux/macOS).
  • Add notes clarifying that all CLI commands work on Linux/macOS and highlight any OS-specific considerations.
  • Where screenshots or instructions reference Windows-specific UI elements or paths, add Linux/macOS equivalents or clarifications.
  • Explicitly state cross-platform compatibility of Azure Data Studio and CLI tools.
GitHub Create Pull Request
Azure Arc Prerequisites | Direct connect mode ...rc/data/create-data-controller-direct-prerequisites.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for connecting a Kubernetes cluster to Azure Arc, but the PowerShell example is given equal prominence and is presented immediately after the CLI example. There is no explicit Linux/macOS example, and PowerShell is a Windows-centric tool, which may create friction for Linux/macOS users. However, the main workflow (using Azure CLI and Helm) is cross-platform, and Linux users can follow the CLI instructions without issue.
Recommendations
  • Clarify that Azure CLI and Helm are cross-platform and recommended for Linux/macOS users.
  • Explicitly state that PowerShell is primarily for Windows users, and that Linux/macOS users should use Azure CLI.
  • Consider presenting CLI examples first, and PowerShell examples in a separate, clearly marked section for Windows users.
  • Add a note or table summarizing tool compatibility across OS platforms.
GitHub Create Pull Request
Azure Arc Deploy a new SQL Managed Instance enabled by Azure Arc using Kubernetes tools ...ate-sql-managed-instance-using-kubernetes-native-tools.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ windows_first
Summary
The documentation generally provides cross-platform guidance, but in the example for creating the SQL managed instance with kubectl, the file path example uses a Windows-style path (C:\arc-data-services\sqlmi.yaml) without also providing a Linux/macOS equivalent. Additionally, the PowerShell example for base64 encoding is shown before the Linux/macOS example, which may subtly prioritize Windows users.
Recommendations
  • Provide both Windows and Linux/macOS file path examples when showing kubectl commands (e.g., C:\arc-data-services\sqlmi.yaml and /home/user/arc-data-services/sqlmi.yaml).
  • Alternate the order of PowerShell and Linux/macOS CLI examples, or present them side by side to avoid implying priority.
  • Explicitly state that the instructions apply equally to Windows, Linux, and macOS, and that users should adapt file paths and commands to their environment.
  • Consider including a note or table summarizing equivalent commands for each platform where relevant.
GitHub Create Pull Request
Azure Arc Rotate user-provided TLS certificate in indirectly connected SQL Managed Instance enabled by Azure Arc ...articles/azure-arc/data/rotate-user-tls-certificate.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_example_present
Summary
The documentation is generally cross-platform, using OpenSSL, Azure CLI, and kubectl, which are available on Linux, macOS, and Windows. However, in the section about base64 encoding, the Linux method is presented first, and then a Windows-specific alternative using certutil is provided. The Windows instructions require manual header removal or an additional command, which is explained. No Linux/macOS equivalents are missing, and the main workflow is platform-neutral. The only minor bias is the explicit mention of Windows tools and extra steps for Windows users.
Recommendations
  • Clarify that the Linux base64 command is also available on macOS.
  • For parity, mention that certutil is not available by default on all Windows editions, and suggest using PowerShell's [Convert]::ToBase64String() as an alternative.
  • Provide a PowerShell example for base64 encoding/decoding for Windows users who may not have certutil.
  • Explicitly state that all other steps (OpenSSL, Azure CLI, kubectl) are cross-platform and provide links to installation guides for each OS.
GitHub Create Pull Request
Azure Arc Get logs to troubleshoot Azure Arc-enabled data services ...in/articles/azure-arc/data/troubleshooting-get-logs.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation provides a CLI-based approach for log collection that is cross-platform, but the only explicit example of a target folder uses a Windows-style path (C:\temp\logs). There are no Linux/macOS path examples, and the documentation does not clarify cross-platform usage or show Linux/macOS equivalents. This may cause minor friction for non-Windows users.
Recommendations
  • Include Linux/macOS path examples (e.g., /tmp/logs) alongside Windows examples when specifying target folders.
  • Add a note clarifying that the az CLI and arcdata extension are cross-platform and work on Windows, Linux, and macOS.
  • Show example commands with both Windows and Linux/macOS paths to reinforce parity.
  • Explicitly mention any OS-specific considerations, if any, for file permissions or path formats.
GitHub Create Pull Request
Azure Arc Upload logs to Azure Monitor ...-docs/blob/main/articles/azure-arc/data/upload-logs.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation provides environment variable examples for Windows (CMD), PowerShell, and Linux/macOS, but consistently lists Windows and PowerShell examples before Linux/macOS. It also mentions Windows Task Scheduler before Linux equivalents when discussing automation. However, Linux/macOS examples are present and functional throughout, and the main workflow uses cross-platform Azure CLI and kubectl commands.
Recommendations
  • Alternate the order of example tabs so Linux/macOS is shown first in some sections.
  • Explicitly mention cron before or alongside Windows Task Scheduler when discussing automation.
  • Where possible, provide parity in scripting examples (e.g., show a sample cron job entry).
  • Consider grouping environment variable examples together or using a table for parity.
GitHub Create Pull Request
Azure Arc Upload usage data to Azure ...blob/main/articles/azure-arc/data/upload-usage-data.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ linux_example_present ⚠️ windows_tools_mentioned
Summary
The documentation provides both Linux and Windows automation options, but Linux shell scripting is presented first and in more detail. Windows automation tools (Task Scheduler, .cmd/.bat/.ps1 scripts) are mentioned, but no explicit Windows script example is given. The main command-line instructions use the cross-platform Azure CLI, and there is no PowerShell-specific or Windows-only command bias. Minor bias exists in the order of tool mentions and lack of explicit Windows script examples.
Recommendations
  • Add explicit Windows script examples (e.g., .bat, .cmd, or PowerShell) alongside the Linux shell script example.
  • Provide step-by-step instructions for automating uploads using Windows Task Scheduler, similar to the Linux cron/`watch` example.
  • Clarify that the Azure CLI commands work on both Windows and Linux, and provide any OS-specific caveats if relevant.
GitHub Create Pull Request
Azure Arc Configure Authentication for Edge RAG Preview Enabled by Azure Arc .../articles/azure-arc/edge-rag/prepare-authentication.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page demonstrates mild Windows bias primarily in its suggestion to use Windows Notepad for storing copied IDs, without mentioning cross-platform alternatives. All instructions rely on the Azure portal web interface, which is platform-agnostic, but there are no Linux/macOS-specific examples or tool recommendations. The page does not provide command-line or automation examples for Linux/macOS users, and the only explicit tool mentioned is Windows Notepad.
Recommendations
  • Replace or supplement 'Windows Notepad' with cross-platform alternatives such as 'any text editor (e.g., Notepad, TextEdit, gedit, nano, VS Code)'.
  • If command-line workflows are supported, provide Azure CLI or PowerShell examples for both Windows and Linux/macOS.
  • Explicitly state that the Azure portal is accessible from any OS with a web browser.
  • Add notes or examples for Linux/macOS users where relevant, especially for storing credentials or automating steps.
GitHub Create Pull Request
Azure Arc Requirements for Edge RAG Preview, Enabled by Azure Arc .../blob/main/articles/azure-arc/edge-rag/requirements.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools
Summary
The documentation generally maintains Linux parity, as Edge RAG is validated on Azure Local with Linux VMs. However, there are minor signs of Windows bias: the NFS setup guide links to Windows Server first, and the optional driver machine section mentions Windows as an example before Linux. Additionally, references to Windows VM sizes and a link to AKS on Windows Server may create confusion, though the minimum OS requirement is Linux.
Recommendations
  • Present Linux and Windows NFS setup guides in parallel or list Linux first, given the minimum OS requirement is Linux.
  • Clarify that the driver machine can be Linux or Windows, and provide explicit Linux setup instructions or links.
  • Remove or clarify references to Windows VM sizes and AKS on Windows Server, as the minimum OS requirement is Linux.
  • Ensure all tooling instructions (Azure CLI, kubectl, Helm) include Linux installation steps and examples.
GitHub Create Pull Request
Azure Arc Customer intent: "As a cloud administrator, I want to understand how to get the region segment of regional endpoints , so that I can configure Azure services in specific regions without errors." ...ob/main/articles/azure-arc/includes/arc-region-note.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for listing regions, but the PowerShell example is shown immediately after the CLI example, and no explicit Linux/macOS shell example (such as Bash) is provided. The use of Azure PowerShell may implicitly favor Windows users, as PowerShell is native to Windows, though it is available cross-platform. The CLI example is cross-platform, but the documentation could further clarify Linux/macOS usage.
Recommendations
  • Explicitly state that Azure CLI works on Windows, Linux, and macOS.
  • Add a Bash shell example for Linux/macOS users, e.g., showing how to parse the output.
  • Clarify that Azure PowerShell is available cross-platform, but CLI is often preferred on Linux/macOS.
GitHub Create Pull Request
Azure Arc Use cluster connect to securely connect to Azure Arc-enabled Kubernetes clusters. .../main/articles/azure-arc/kubernetes/cluster-connect.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ minor_shell_inconsistency
Summary
The documentation provides both Azure CLI (cross-platform) and Azure PowerShell (Windows-centric) examples in parallel throughout, but frequently lists PowerShell examples after CLI. However, some shell commands (such as kubectl and environment variable usage) are shown in a way that is more natural for Bash/Linux, even in PowerShell sections. There is no exclusive use of Windows tools, but the presence of PowerShell examples may suggest a slight Windows bias, and some shell commands (like echo $TOKEN) are not idiomatic PowerShell.
Recommendations
  • Clarify that Azure CLI examples are fully supported on Linux/macOS and are the recommended cross-platform approach.
  • Consider removing or de-emphasizing PowerShell examples unless there is a Windows-specific workflow.
  • Ensure shell commands in PowerShell sections use proper PowerShell syntax (e.g., Write-Output instead of echo).
  • Add explicit notes about Linux/macOS compatibility where appropriate.
  • If possible, provide a single set of CLI examples with notes for platform-specific differences, rather than duplicating for PowerShell.
GitHub Create Pull Request
Azure Arc Simplify network configuration requirements with Azure Arc gateway (preview) ...zure-arc/kubernetes/arc-gateway-simplify-networking.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all major tasks, but PowerShell examples are consistently presented alongside CLI, sometimes with more detail. The ordering of tabs and examples sometimes places PowerShell before or at parity with CLI, which may imply a slight Windows bias. However, Linux/macOS users are not blocked from completing any tasks, as Azure CLI is fully supported and environment variable examples use standard Linux/macOS syntax (export). There are no Windows-only tools or patterns, and kubectl is used for cluster operations, which is cross-platform.
Recommendations
  • Ensure that Azure CLI examples are always presented first, as CLI is cross-platform and preferred for Linux/macOS users.
  • Explicitly mention that Azure CLI and kubectl commands work on Linux/macOS, and clarify any OS-specific steps if needed.
  • Add a note stating that Azure PowerShell is primarily for Windows, and recommend Azure CLI for Linux/macOS users.
  • Where environment variables are set, provide both Linux/macOS (export) and Windows (set) syntax for parity.
GitHub Create Pull Request
Azure Arc Diagnose connection issues for Azure Arc-enabled Kubernetes clusters ...les/azure-arc/kubernetes/diagnose-connection-issues.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_examples ⚠️ windows_first
Summary
This documentation provides both Linux and Windows examples for DNS troubleshooting in Kubernetes pods, but Windows-specific tools (PowerShell, Resolve-DnsName) are given dedicated sections and explicit instructions, while Linux tools are presented first. The use of Windows containers and PowerShell is included for parity, but the documentation does not show Linux/macOS alternatives for some steps (e.g., file upload in support requests), and references to Windows commands (nslookup) link to Windows documentation, even though the context is Linux containers.
Recommendations
  • Ensure that references to command-line tools (e.g., nslookup) link to cross-platform or Linux documentation when used in Linux containers.
  • Clarify that most troubleshooting steps (kubectl, Azure CLI) are cross-platform and provide explicit macOS/Linux instructions where relevant.
  • For support request steps, mention any OS-specific differences in file upload or log collection if they exist.
  • In sections where Windows-specific steps are shown (e.g., PowerShell in Windows pods), explicitly state that these are only needed for Windows node pools, and provide links to Linux/macOS equivalents if available.
  • Consider grouping Linux/macOS and Windows instructions separately for clarity, or use tabs to allow users to select their OS.
GitHub Create Pull Request
Azure Arc Quickstart: Connect an existing Kubernetes cluster to Azure Arc ...les/azure-arc/kubernetes/quickstart-connect-cluster.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for all steps, but PowerShell is a Windows-centric tool and is presented as an equal alternative throughout. When discussing how to create a Kubernetes cluster, the documentation lists Docker for Mac and Docker for Windows together, but does not show any Linux-specific desktop instructions (e.g., Minikube for Linux, Docker Desktop for Linux). In the outbound proxy section, environment variable examples are shown for Bash (Linux/macOS) and PowerShell (Windows), but PowerShell is given its own dedicated section. Overall, the documentation is not missing Linux examples for the main workflow, but does show a slight bias toward Windows/PowerShell by presenting it as a first-class option and not providing Linux-specific desktop cluster creation instructions.
Recommendations
  • Add explicit instructions or links for creating a Kubernetes cluster on Linux desktop environments (e.g., Minikube, Docker Desktop for Linux).
  • Clarify that Azure CLI is cross-platform and can be used on Windows, Linux, and macOS, while PowerShell is primarily for Windows users.
  • Consider listing Linux options first or equally when mentioning cluster creation methods.
  • Ensure parity in troubleshooting and proxy configuration instructions for Linux environments.
GitHub Create Pull Request
Azure Arc Azure Arc-enabled Kubernetes system requirements ...n/articles/azure-arc/kubernetes/system-requirements.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for connecting Kubernetes clusters to Azure Arc and registering resource providers. However, Azure PowerShell (a Windows-centric tool) is mentioned alongside Azure CLI throughout, and examples for both are given. There is a slight bias in mentioning Azure PowerShell as an equal management tool, which may create friction for Linux/macOS users who typically use Azure CLI. The documentation does not provide Linux/macOS-specific instructions or clarify that Azure PowerShell is cross-platform, nor does it prioritize CLI examples over PowerShell.
Recommendations
  • Clarify that Azure PowerShell is available cross-platform (Windows, Linux, macOS) to avoid the impression that it is Windows-only.
  • Prioritize Azure CLI examples and instructions, as CLI is the default and most widely used tool on Linux/macOS.
  • Explicitly mention that all steps can be performed on Linux/macOS using Azure CLI.
  • Add a note for Linux/macOS users confirming that no Windows-specific steps are required.
  • Consider providing Linux/macOS shell command examples for related tasks (e.g., verifying Helm installation, checking prerequisites).
GitHub Create Pull Request
Azure Arc Azure Arc resource bridge security overview ...rticles/azure-arc/resource-bridge/security-overview.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation mentions retrieving Azure activity logs using PowerShell and Azure CLI, listing PowerShell first. This ordering may subtly suggest a Windows-first approach, and the mention of PowerShell could be seen as favoring Windows tooling. However, Azure CLI is cross-platform and no examples are given, so the impact is minor.
Recommendations
  • When listing tools, mention Azure CLI before PowerShell to emphasize cross-platform support.
  • Provide explicit examples for both Azure CLI and PowerShell, or clarify that Azure CLI is available on Linux/macOS.
  • Add a brief note highlighting that all management tasks can be performed on Linux/macOS using Azure CLI.
GitHub Create Pull Request
Azure Arc CLI reference for `azcmagent extension` ...main/articles/azure-arc/servers/azcmagent-extension.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools
Summary
The documentation mentions Windows service management commands (Stop-Service/Start-Service) before their Linux equivalents (systemctl stop/start), and uses a Windows-specific extension ('AzureMonitorWindowsAgent') in the example for removing an extension. However, Linux commands are present and the CLI itself is cross-platform.
Recommendations
  • Present Linux and Windows service management commands side-by-side or alternate their order to avoid Windows-first bias.
  • Include examples that reference both Windows and Linux extensions (e.g., 'AzureMonitorLinuxAgent') to demonstrate parity.
  • Add a note clarifying that extension names may differ between Windows and Linux, and provide examples for both platforms.
GitHub Create Pull Request
Azure Arc What's new with Azure Connected Machine agent ...main/articles/azure-arc/servers/agent-release-notes.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools
Summary
The release notes for the Azure Connected Machine agent generally provide parity between Windows and Linux, listing features and fixes for both platforms. However, there is a subtle Windows bias: Windows download links and version numbers are consistently listed first, and installation troubleshooting focuses exclusively on Windows tools (e.g., PowerShell, Command Prompt, msiexec) without mentioning Linux equivalents. Some improvements and bug fixes are described with Windows-centric terminology (e.g., 'Run as administrator', 'UAC prompt'), and PowerShell scripts are referenced without Linux shell alternatives. Linux-specific issues and improvements are present, but Windows patterns and tools are more prominently featured.
Recommendations
  • Alternate the order of Windows and Linux in tables and download links, or present them side-by-side.
  • Include Linux-specific troubleshooting steps and commands (e.g., using sudo, rpm, systemctl) where Windows installation issues are discussed.
  • When referencing scripts (e.g., ExtensionCleanup.ps1), clarify if a Linux equivalent exists or provide a Bash/sh alternative if possible.
  • Ensure that bug fixes and improvements are described in platform-neutral language where applicable.
  • Add a section for common Linux installation issues and their solutions, similar to the Windows installer troubleshooting.
GitHub Create Pull Request
Azure Arc CLI reference for `azcmagent connect` ...b/main/articles/azure-arc/servers/azcmagent-connect.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation exhibits mild Windows bias in the authentication options section, where the interactive browser login is described as 'Windows only' and presented first. Additionally, the access token example references PowerShell's Get-AzAccessToken cmdlet before mentioning other Microsoft Entra clients, which may create friction for Linux/macOS users unfamiliar with PowerShell. However, the majority of examples and instructions are OS-neutral, and Linux authentication flows are explicitly described.
Recommendations
  • Present authentication options in a neutral order (e.g., device code first, as it is default for Linux).
  • For access token retrieval, provide Azure CLI equivalents (e.g., 'az account get-access-token') alongside PowerShell examples.
  • Clarify that most commands and flags are cross-platform and provide explicit Linux/macOS command snippets where relevant.
  • Where Windows-only methods are described, immediately follow with Linux/macOS alternatives.
GitHub Create Pull Request
Azure Arc Archive for What's new with Azure Connected Machine agent ...icles/azure-arc/servers/agent-release-notes-archive.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ powershell_heavy
Summary
The documentation provides release notes for both Windows and Linux versions of the Azure Connected Machine agent. While Linux-specific features and fixes are regularly called out, Windows examples, tools, and terminology (such as MSI installers, PowerShell, Windows Event Logs, and Windows-specific system metadata) are often mentioned first or in greater detail. Windows download links are shown before Linux, and Windows tools (PowerShell, WMI, Win32 API) are referenced more frequently than Linux equivalents. Some features (e.g., Windows Event Logs, MSI certificate handling) are Windows-only, but Linux parity is generally maintained for core agent functionality.
Recommendations
  • Alternate the order of Windows and Linux download links or present them together to avoid implicit prioritization.
  • Where Windows tools (e.g., PowerShell, Event Logs) are mentioned, provide equivalent Linux commands or log locations (e.g., journalctl, syslog) when possible.
  • Ensure Linux-specific enhancements and fixes are highlighted with equal prominence as Windows features.
  • Add explicit examples or references for Linux management tools and troubleshooting steps alongside Windows ones.
  • Consider a summary table for OS-specific features/fixes to clarify parity and differences.
GitHub Create Pull Request
Azure Arc Customer intent: "As a network administrator, I want to configure secure outbound connectivity for the Azure Connected Machine agent so that I can ensure proper communication with Azure Arc while adhering to my organization's security policies." ...les/azure-arc/servers/includes/network-requirements.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools
Summary
The documentation generally maintains parity between Windows and Linux, especially in the context of Azure Arc-enabled servers, which support both platforms. However, there are minor signs of Windows bias: Windows-related resources (e.g., download.microsoft.com for Windows installers) are consistently listed before Linux equivalents (packages.microsoft.com), and Windows-specific tools like Windows Admin Center are mentioned and given their own service tag. The cryptographic protocol section focuses on Windows cipher suite configuration and troubleshooting, with more detailed references for Windows than Linux. No critical steps are Windows-only, and Linux users can complete all tasks, but Windows examples and tools tend to be presented first.
Recommendations
  • Alternate the order of Windows and Linux resources in tables and lists to avoid consistently prioritizing Windows.
  • Provide equal troubleshooting and configuration guidance for Linux (e.g., OpenSSL configuration for TLS/cipher suites), similar to the detailed Windows section.
  • Clarify when Windows-specific tools (like Windows Admin Center) are optional or not applicable to Linux, and highlight Linux management alternatives if relevant.
  • Where possible, include links to Linux-specific documentation for network configuration, proxy setup, and TLS/cipher suite management.
GitHub Create Pull Request
Azure Arc Connect hybrid machines to Azure using a deployment script ...blob/main/articles/azure-arc/servers/onboard-portal.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation provides both Windows and Linux onboarding instructions for Azure Arc-enabled servers. However, Windows installation steps and examples are presented before Linux, and Windows-specific tooling (msiexec, PowerShell) is described in detail. The scripted method for Windows explicitly requires PowerShell, while the Linux equivalent uses shell scripts. Windows command-line options and troubleshooting paths are more thoroughly documented, with references to Windows Installer and PowerShell environment variable management. Linux instructions are present and functional, but Windows examples and tools are given more prominence and detail.
Recommendations
  • Present Windows and Linux installation instructions in parallel sections or alternate their order to avoid implicit prioritization.
  • Provide equivalent detail for Linux installation, including troubleshooting steps, log locations, and command-line options for package managers (e.g., apt, yum).
  • Include Linux-specific proxy configuration examples (e.g., environment variables, systemd service overrides) alongside Windows PowerShell examples.
  • Reference Linux package management documentation for users unfamiliar with .DEB/.RPM installation.
  • Clarify that both Windows and Linux onboarding are equally supported and provide links to OS-specific guides where appropriate.
GitHub Create Pull Request
Azure Arc Authenticate against Azure resources with Azure Arc-enabled servers ...s/azure-arc/servers/managed-identity-authentication.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation provides both Windows/PowerShell and Linux/Bash examples for authenticating against Azure resources with Azure Arc-enabled servers. However, Windows/PowerShell examples and references are consistently presented first, and PowerShell is emphasized for access policy assignment and token retrieval. Some links and instructions default to PowerShell before mentioning Azure CLI or Linux equivalents, and screenshots are Windows-centric.
Recommendations
  • Alternate the order of Windows and Linux examples throughout the documentation, or present them side-by-side to avoid implicit prioritization.
  • Provide equal prominence to Azure CLI instructions and examples for access policy assignment, not just PowerShell.
  • Include Linux/Bash screenshots or output examples alongside Windows/PowerShell ones.
  • Where possible, clarify that both Windows and Linux are supported and link to both sets of instructions in prerequisite and next steps sections.
  • Explicitly mention cross-platform tools (e.g., Azure CLI, REST API) as alternatives to PowerShell for all relevant tasks.
GitHub Create Pull Request
Azure Arc Connect hybrid machines to Azure at scale ...rticles/azure-arc/servers/onboard-service-principal.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation provides both Windows and Linux guidance for onboarding hybrid machines to Azure Arc at scale, but there is a mild Windows bias. Windows/PowerShell tools and examples are often mentioned first, and there are more explicit references to Windows-specific tooling (e.g., PowerShell, Windows PowerShell script limitations). While Linux is supported and referenced throughout, Windows-centric patterns and terminology are slightly prioritized.
Recommendations
  • Alternate the order of Windows and Linux references/examples to avoid Windows-first bias.
  • Explicitly show Linux Bash/CLI examples alongside PowerShell examples, especially in the 'Install the agent and connect to Azure' section.
  • Clarify that both .ps1 (Windows) and .sh (Linux) scripts are generated and supported, and provide sample Linux script snippets.
  • Add troubleshooting notes relevant to Linux environments.
  • Ensure parity in automation tool recommendations (mention Ansible, shell scripts, etc., not just PowerShell).
GitHub Create Pull Request
Azure Arc Plan and Deploy Azure Arc-Enabled Servers ...articles/azure-arc/servers/plan-at-scale-deployment.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation generally maintains cross-platform parity, referencing both Windows and Linux throughout. However, there is mild bias in the ordering and example selection: Azure PowerShell and portal methods are mentioned before Linux CLI equivalents, and some tasks (such as service principal creation) reference Azure PowerShell without explicit mention of Azure CLI or Linux-native alternatives. No critical deployment steps are Windows-only, but the ordering and tool references may create minor friction for Linux/macOS users.
Recommendations
  • Explicitly mention Azure CLI as an alternative to Azure PowerShell for service principal creation and other management tasks, with example commands for Linux/macOS.
  • When listing onboarding scripts and deployment options, ensure Linux and Windows are referenced equally and provide clear links or code samples for both.
  • Where automation tools are discussed, include examples or references for Linux-native tools (e.g., Bash scripts, Ansible) alongside PowerShell.
  • In tables and lists, alternate or randomize the order of Windows and Linux references to avoid implicit prioritization.
GitHub Create Pull Request
Azure Arc Use Azure Private Link to Connect Servers to Azure Arc by Using a Private Endpoint ...in/articles/azure-arc/servers/private-link-security.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ windows_first
Summary
The documentation generally maintains parity between Windows and Linux, offering instructions and download links for both platforms. However, in the 'Single server scenarios' section, the Windows Hosts file example is presented before the Linux equivalent, which is a minor instance of 'windows_first' bias. No critical steps or examples are Windows-only, and Linux users can complete all tasks described.
Recommendations
  • Present Windows and Linux examples in parallel or alternate which is shown first.
  • Explicitly mention that all steps are applicable to both Windows and Linux unless otherwise noted.
  • Where screenshots or UI instructions differ for Linux (e.g., agent installation), provide Linux-specific visuals or CLI examples.
GitHub Create Pull Request
Azure Arc Extensions security for Azure Arc-enabled servers ...main/articles/azure-arc/servers/security-extensions.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation generally maintains OS parity, providing both Windows and Linux instructions and examples. However, in several sections, Windows examples (using PowerShell) are presented before Linux equivalents (using Bash), and PowerShell is referenced as a primary example language. The listing of extension types also sometimes lists Windows before Linux. These are minor presentation biases rather than substantive gaps.
Recommendations
  • Alternate the order of Windows and Linux examples, or present them side-by-side to reinforce parity.
  • Where possible, use generic CLI examples first (e.g., Azure CLI), then show OS-specific command-line examples.
  • Explicitly state that all features and controls described apply equally to both Windows and Linux unless otherwise noted.
  • Ensure that links to further documentation (e.g., listing installed extensions) include both PowerShell and CLI/Linux instructions equally.
GitHub Create Pull Request
Azure Arc Troubleshoot Azure Connected Machine agent connection issues ...ticles/azure-arc/servers/troubleshoot-agent-onboard.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation provides troubleshooting guidance for both Windows and Linux, but Windows examples and tools (such as PowerShell syntax and Windows-specific paths) are presented before Linux equivalents in several sections. Windows command examples use PowerShell syntax, while Linux examples use Bash, but Windows examples are listed first. Some troubleshooting steps reference Windows file paths and tools before mentioning Linux equivalents.
Recommendations
  • Alternate the order of Windows and Linux examples so that Linux is sometimes presented first.
  • Where possible, present platform-agnostic instructions before platform-specific details.
  • Ensure that Linux file paths and troubleshooting steps are given equal prominence and clarity as Windows equivalents.
  • Add explicit notes clarifying differences in commands, file locations, and permissions between Windows and Linux.
  • Consider grouping platform-specific instructions under clear subheadings to improve parity and discoverability.
GitHub Create Pull Request
Azure Arc Upgrade the Azure Arc resource bridge ...l-machine-manager/upgrade-azure-arc-resource-bridge.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools
Summary
The documentation is focused on upgrading the Azure Arc resource bridge in a System Center Virtual Machine Manager (SCVMM) environment. SCVMM is a Windows-only product, and all instructions, examples, and prerequisites are tailored to Windows environments (e.g., VHDX format, SCVMM server, Azure CLI commands run from Windows workstations). There are no Linux/macOS-specific instructions or examples, but this is intentional due to the Windows-only nature of SCVMM.
Recommendations
No changes needed for Linux parity, as SCVMM and its resource bridge are Windows-only technologies. If any cross-platform Azure Arc resource bridge scenarios are supported in the future, consider adding Linux/macOS-specific instructions and examples.
GitHub Create Pull Request
Azure Arc Staging Resources Before Deployment ...icles/azure-arc/workload-orchestration/how-to-stage.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for all major steps, ensuring Linux/macOS and Windows users are supported. However, PowerShell examples are consistently presented after Bash, and some PowerShell snippets use Windows-specific idioms (e.g., Out-File, [Convert]::ToBase64String). There are no sections that are Windows-only, and Linux parity is generally maintained. Minor bias exists in the ordering and some command details.
Recommendations
  • Explicitly mention that Bash examples are suitable for Linux/macOS and PowerShell for Windows, to guide users.
  • Where PowerShell uses Windows-specific idioms (e.g., Out-File, [Convert]::ToBase64String), ensure Bash equivalents are shown and clarify any differences.
  • Consider providing a short summary at the top explaining cross-platform support and how to choose the correct tab.
  • If possible, add a macOS-specific note for any edge cases (e.g., file encoding or line endings).
GitHub Create Pull Request
Azure Arc What is Azure Arc-enabled VMware vSphere? ...lob/main/articles/azure-arc/vmware-vsphere/overview.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation provides a balanced overview of Azure Arc-enabled VMware vSphere, but there are several instances where Windows-centric tools, examples, and terminology are mentioned before or more prominently than Linux equivalents. PowerShell and Windows-specific management features are referenced first or exclusively in some automation and configuration contexts, and links to Windows-focused guides are more visible than those for Linux. However, Linux support is acknowledged in several places, and most features are cross-platform.
Recommendations
  • Ensure that automation and configuration examples mention Bash/CLI and Linux tools alongside PowerShell, or present both in parallel.
  • When referencing runbooks or automation, clarify that Python and Bash scripts are supported, and provide links to Linux-specific documentation where available.
  • In lists of supported VM extensions, explicitly mention Linux support and provide links to Linux extension documentation.
  • Where Windows management features are highlighted, balance with equivalent Linux management features if available, or clarify Windows-only scope.
  • In 'Next steps' and quickstart links, include Linux-focused guides or tabs where possible.
GitHub Create Pull Request
Azure Arc External Validation for Workload Orchestration ...zure-arc/workload-orchestration/external-validation.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ windows_first
Summary
The documentation provides both Bash and PowerShell examples for all CLI operations, ensuring parity for Linux/macOS and Windows users. However, PowerShell examples are consistently presented immediately after Bash, which may subtly reinforce a Windows-first perspective. No Windows-only tools or patterns are used, and all instructions are cross-platform via the Azure CLI.
Recommendations
  • Continue providing both Bash and PowerShell examples to maintain parity.
  • Consider alternating the order of Bash and PowerShell examples in some sections, or explicitly state that Bash examples are for Linux/macOS and PowerShell for Windows, to reinforce cross-platform support.
  • Add a brief note at the top clarifying that all CLI commands work on Linux, macOS, and Windows, and that Bash examples are for Linux/macOS users.
GitHub Create Pull Request
Azure Arc Create a Solution with Shared Adapter Dependency with Workload Orchestration ...ation/quickstart-solution-shared-adapter-dependency.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ windows_first
Summary
The documentation provides both Bash and PowerShell examples for every CLI step, ensuring parity for Linux/macOS and Windows users. However, PowerShell examples are consistently presented after Bash, which is the standard order for cross-platform Azure documentation. No Windows-specific tools, patterns, or terminology are prioritized, and all commands use the Azure CLI, which is fully supported on Linux/macOS. No critical steps are Windows-only, and Linux users can complete the tutorial without friction.
Recommendations
  • Maintain the current approach of providing both Bash and PowerShell examples for all CLI commands.
  • Consider explicitly stating at the top that all CLI steps are cross-platform and supported on Linux/macOS and Windows.
  • If possible, add a brief note for macOS users regarding any minor differences in shell usage (e.g., environment variable syntax), though none are present in this guide.
GitHub Create Pull Request
Azure Arc Service Groups for Workload Orchestration ...cles/azure-arc/workload-orchestration/service-group.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ windows_first
Summary
The documentation provides both Bash and PowerShell examples for all command-line steps, but PowerShell examples are consistently shown after Bash. There are no Windows-exclusive tools or patterns, and all commands use the Azure CLI, which is cross-platform. No Linux/macOS examples are missing, and no Windows-only tools are referenced. The only minor bias is that PowerShell examples are present and shown second, which may slightly favor Windows users in terms of visibility but does not impact Linux/macOS users' ability to follow the documentation.
Recommendations
  • Consider alternating the order of Bash and PowerShell tabs in different sections to avoid implicit prioritization.
  • Explicitly state at the beginning that all commands work on Linux, macOS, and Windows, provided Azure CLI is installed.
  • Add a brief note clarifying that Bash examples are suitable for Linux/macOS and PowerShell for Windows, to help users quickly identify which examples to use.
GitHub Create Pull Request
Azure Arc Create a Basic Solution with Common Configurations with Workload Orchestration ...ation/quickstart-solution-with-common-configuration.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for every step, ensuring parity for Linux/macOS and Windows users. However, in each section, PowerShell examples are consistently shown after Bash, and PowerShell is given equal prominence even though Bash is the default shell on most Linux/macOS systems. There are no Windows-only tools or patterns, and all CLI commands are cross-platform (az CLI). No Linux examples are missing, and no Windows-specific tools are mentioned.
Recommendations
  • Maintain Bash as the first example in each tab, as Bash is the default on Linux/macOS.
  • Consider explicitly stating that all az CLI commands work on Linux, macOS, and Windows.
  • Optionally, clarify that PowerShell examples are for users who prefer PowerShell on any platform, not just Windows.
  • Ensure that any future platform-specific instructions (e.g., file paths, environment setup) include Linux/macOS details if relevant.
GitHub Create Pull Request
Azure Arc Solution with Multiple Shared Dependencies at Different Hierarchy Levels ...oad-orchestration/tutorial-service-group-scenario-3.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for every step, but PowerShell examples are always presented after Bash. There is no evidence of exclusive use of Windows tools or missing Linux examples, and all commands use cross-platform tools (Azure CLI, Helm). However, the presence of PowerShell examples and their explicit inclusion may indicate a slight Windows bias, especially since PowerShell is less commonly used on Linux/macOS compared to Bash.
Recommendations
  • Consider clarifying that Bash examples are intended for Linux/macOS and PowerShell for Windows, to help users choose the appropriate tab.
  • Optionally, add a note that PowerShell is available on Linux/macOS, but Bash is more typical for those platforms.
  • Ensure that any platform-specific prerequisites (e.g., installing Azure CLI, Helm) are covered for both Windows and Linux/macOS.
  • If possible, provide guidance for users who may be using WSL (Windows Subsystem for Linux) or PowerShell Core on non-Windows platforms.
GitHub Create Pull Request
Azure Portal Use Azure Copilot with the Azure mobile app ...main/articles/azure-portal/mobile-app/azure-copilot.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ windows_first
Summary
The documentation mentions 'Generating CLI and PowerShell scripts' as a key capability, listing PowerShell before CLI. This ordering may subtly prioritize Windows/PowerShell over Linux/bash, though both are supported. No explicit Windows-only tools or examples are present, and the page is generally cross-platform.
Recommendations
  • List 'CLI and PowerShell scripts' in alphabetical order or clarify that both Bash (Azure CLI) and PowerShell are supported equally.
  • Consider providing a brief example or clarification that generated scripts can target both Bash (for Linux/macOS) and PowerShell (for Windows), ensuring parity.
  • Explicitly mention that Azure Copilot supports script generation for multiple platforms.
GitHub Create Pull Request
Azure Portal Get subscription and tenant IDs in the Azure portal ...in/articles/azure-portal/get-subscription-tenant-id.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation provides both Azure PowerShell and Azure CLI options for programmatically retrieving subscription and tenant IDs, but PowerShell is consistently mentioned first and receives slightly more emphasis. There are no explicit Linux/macOS examples or screenshots, and the workflow descriptions (e.g., copying to clipboard, pasting into a text document) are generic but could be interpreted as Windows-centric. No Linux-specific tools or shell commands are discussed.
Recommendations
  • Alternate the order of PowerShell and CLI mentions, or mention Azure CLI first in at least one section to avoid implicit Windows-first bias.
  • Include explicit examples or screenshots showing Azure CLI usage on Linux/macOS terminals.
  • Clarify that Azure CLI is cross-platform and works on Linux/macOS, and provide links to installation guides for those platforms.
  • Add notes or tips for Linux/macOS users regarding clipboard operations or text editors if relevant.
GitHub Create Pull Request
Container Registry Manage Public Content in Private Container Registry ...icles/container-registry/buffer-gate-public-content.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for importing images into Azure Container Registry, but the PowerShell example is given equal prominence and is presented immediately after the CLI example. There is a slight 'windows_first' bias in mentioning Azure PowerShell as a primary tool alongside CLI, which may be less relevant for Linux/macOS users. However, the CLI example is cross-platform and shown first, and no critical steps are Windows-only. No Linux-specific tools or shell examples (e.g., Bash scripts) are provided, but the CLI coverage is sufficient for Linux/macOS users.
Recommendations
  • Clarify that Azure CLI is cross-platform and recommended for Linux/macOS users.
  • Optionally, add a Bash shell example for common workflows (e.g., scripting image imports).
  • Explicitly state that Azure PowerShell is primarily for Windows users, and that Linux/macOS users should use Azure CLI.
  • Consider adding a note about Azure Cloud Shell availability for both Bash and PowerShell, and which is recommended for different OS users.
GitHub Create Pull Request
Container Registry Access Registry Images from ACI ...cles/container-registry/container-registry-auth-aci.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell sample scripts, but references to PowerShell are prominent and placed alongside CLI examples, which may suggest a slight Windows bias. The main example uses Azure CLI, which is cross-platform, but PowerShell is highlighted as an alternative, and the note about 'export MSYS_NO_PATHCONV=1' is relevant for Bash on Windows, not Linux/macOS. There are no explicit Linux/macOS examples or references to platform-specific considerations for those users.
Recommendations
  • Add explicit notes or examples for Linux/macOS users, such as confirming Azure CLI commands work natively on those platforms.
  • Clarify that Azure CLI is cross-platform and provide troubleshooting tips for Linux/macOS environments if needed.
  • Consider including links to sample scripts or documentation specifically for Bash or other common Linux shells.
  • If mentioning PowerShell, note its availability on Linux/macOS and provide guidance for those platforms if there are differences.
GitHub Create Pull Request
Container Registry Quickstart - Create Registry in Portal ...iner-registry/container-registry-get-started-portal.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for signing in to the registry, but Azure PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and appears immediately after it. There are no Linux-specific command-line examples (e.g., Bash), and PowerShell is not available by default on most Linux/macOS systems. However, Docker installation instructions do link to Linux, Mac, and Windows guides, and the core workflow is cross-platform.
Recommendations
  • Clarify that Azure PowerShell is primarily for Windows users, and recommend Azure CLI for Linux/macOS users.
  • Consider providing Bash or shell script examples for Linux/macOS users where relevant.
  • Explicitly state that Azure CLI commands work on all platforms, while PowerShell is most common on Windows.
  • In tabbed instructions, list Azure CLI first and highlight its cross-platform nature.
  • Add a note for Linux/macOS users that PowerShell is optional and not required.
GitHub Create Pull Request
Container Registry Manage OCI Artifacts and Supply Chain Artifacts with ORAS ...ntainer-registry/container-registry-manage-artifact.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides both Linux/macOS and Windows command examples for key ORAS CLI operations, but consistently lists Linux/macOS instructions first and Windows examples second. Windows examples use Windows CMD syntax (with ^ line continuation and .\oras.exe), while Linux/macOS use Bash. No PowerShell-specific examples are present, and all major workflows are covered for both platforms. There is minor bias in the ordering of examples, with Linux/macOS shown first, but no omission of Windows or Linux instructions.
Recommendations
  • Consider alternating the order of platform examples in different sections to avoid perceived bias.
  • Explicitly mention that both Linux/macOS and Windows are supported, and clarify which syntax to use for each.
  • Add PowerShell examples for Windows users who prefer it over CMD, or clarify that CMD is recommended.
  • Ensure all examples are functionally equivalent and tested on both platforms.
GitHub Create Pull Request
Container Registry Azure Container Registry SKU Features and Limits ...articles/container-registry/container-registry-skus.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for key operations (such as changing SKUs and showing registry usage), but consistently lists PowerShell examples immediately after CLI examples and explicitly mentions PowerShell commands before Linux/macOS alternatives (such as Bash scripts or REST API usage). There are no Linux-specific examples (e.g., Bash, shell scripting), and PowerShell is presented as a primary alternative to the CLI, which may create friction for Linux/macOS users unfamiliar with PowerShell.
Recommendations
  • Add explicit Bash/shell script examples for common operations, especially for tasks like changing SKUs and querying usage.
  • Present REST API usage examples in a cross-platform way (e.g., using curl) alongside CLI and PowerShell.
  • When listing command options, alternate the order or clarify that Azure CLI is cross-platform and PowerShell is Windows-centric.
  • Consider adding a note that Azure CLI works natively on Linux/macOS, while PowerShell is primarily used on Windows.
GitHub Create Pull Request
Container Registry Customer intent: "As a security analyst, I want to view vulnerability assessment results for container images, so that I can ensure all security issues are identified and resolved in our container registry." ...ontainer-registry/includes/azure-container-registry.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for querying vulnerability assessment results, but PowerShell is given its own tab and is listed before the portal option. There is a slight Windows bias due to the inclusion and prominence of PowerShell, which is primarily a Windows tool, and the ordering of examples (CLI, then PowerShell, then Portal). However, the Azure CLI example is fully cross-platform and no critical functionality is Windows-only.
Recommendations
  • Clarify that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Consider listing Azure CLI before PowerShell to emphasize cross-platform support.
  • Explicitly mention that PowerShell Core is available on Linux/macOS if relevant.
  • Add a note for Linux/macOS users confirming that all functionality is available via Azure CLI.
GitHub Create Pull Request
Container Registry Quickstart: Deploying the Connected Registry Arc Extension ...iner-registry/quickstart-connected-registry-arc-cli.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ windows_first
Summary
The documentation provides both Bash and PowerShell examples for generating the protected settings JSON file, but the Bash example is shown first and is more clearly explained. There is no evidence of exclusive use of Windows tools, PowerShell-heavy bias, or missing Linux examples. All critical steps are covered with cross-platform CLI and kubectl commands.
Recommendations
  • Ensure that both Bash and PowerShell examples are equally detailed and placed side-by-side or clearly marked as alternatives.
  • Explicitly state that Bash commands work on Linux/macOS and that PowerShell commands are for Windows users.
  • Consider including a short note at the top clarifying platform compatibility for each example.
GitHub Create Pull Request
Copilot Example prompts for Azure Copilot ...ent-docs/blob/main/articles/copilot/example-prompts.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides example prompts for Azure Copilot across a wide range of Azure services. While most examples are platform-neutral or reference cross-platform tools (such as Azure CLI), there is a mild Windows bias in the ordering and representation of scripting tools: PowerShell examples are given their own section and appear immediately after Azure CLI, with no equivalent section for Bash or Linux shell scripting. No Linux/macOS-specific tools or examples (such as Bash scripts or SSH commands) are provided alongside PowerShell, and PowerShell is presented as a primary automation tool, which may create friction for Linux/macOS users who prefer Bash or other shells.
Recommendations
  • Add example prompts for Bash or Linux shell scripting alongside PowerShell and Azure CLI, such as 'How do I create a resource group using Bash?' or 'Generate a Bash script to list all VMs.'
  • Explicitly mention that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
  • Consider reordering or grouping scripting examples to avoid implying PowerShell is the default or preferred option for all users.
  • Include prompts relevant to Linux/macOS workflows, such as SSH commands, Bash automation, or integration with Linux tools.
GitHub Create Pull Request
Copilot Azure Copilot capabilities ...gement-docs/blob/main/articles/copilot/capabilities.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation lists 'Generate PowerShell scripts' as a primary example of Azure Copilot's code generation capabilities, and PowerShell is mentioned before Linux-native equivalents such as Bash or Azure CLI. While the page also references Azure CLI and Terraform, the ordering and explicit PowerShell mention may subtly prioritize Windows tooling. No explicit Linux examples or tools (e.g., Bash scripts) are given, and PowerShell is not contextualized as cross-platform.
Recommendations
  • Add explicit examples or references to Linux-native scripting (e.g., Bash) alongside PowerShell.
  • Clarify that PowerShell is cross-platform, or provide guidance for Linux/macOS users on using PowerShell Core.
  • Ensure that Azure CLI examples are given equal prominence and ordering to PowerShell.
  • Consider including links or references to Linux/macOS-specific workflows where relevant.
GitHub Create Pull Request
Lighthouse Cross-tenant management experiences ...hthouse/concepts/cross-tenant-management-experience.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides both Azure PowerShell and Azure CLI examples for cross-tenant management, but PowerShell is mentioned first and in more detail. There is a slight tendency to reference Windows-centric tools (PowerShell) before cross-platform alternatives (CLI), which may create minor friction for Linux/macOS users. However, Linux and non-Windows scenarios (e.g., Azure Arc for Linux servers, AKS, Azure CLI) are referenced throughout, and no critical functionality is Windows-only.
Recommendations
  • Present Azure CLI and PowerShell examples in parallel, or alternate which is shown first.
  • Explicitly state that both CLI and PowerShell are cross-platform and provide links to installation/use on Linux/macOS.
  • Where PowerShell cmdlets are referenced, ensure equivalent CLI commands are also provided and described.
  • Add a brief note clarifying that all management tasks can be performed from Linux/macOS using Azure CLI and REST APIs.
GitHub Create Pull Request
Quotas Increase Azure Storage account quotas ...main/articles/quotas/storage-account-quota-requests.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation lists Azure PowerShell as the first tool for viewing storage account quota usage, followed by Azure CLI and REST API. While Azure CLI and REST API are cross-platform, the ordering and explicit mention of PowerShell may subtly prioritize Windows users. No Linux/macOS-specific examples or screenshots are provided, but the core instructions are platform-neutral and focus on the Azure portal.
Recommendations
  • List Azure CLI before Azure PowerShell when presenting command-line options, as CLI is cross-platform and more widely used outside Windows.
  • Provide explicit example commands for both Azure CLI and PowerShell, ensuring parity.
  • Include a note clarifying that all tools (PowerShell, CLI, REST API) are available on Windows, Linux, and macOS, except where features are Windows-specific.
  • If screenshots or UI differ on non-Windows platforms (unlikely for Azure portal), mention any differences.
GitHub Create Pull Request
Quotas Increase networking quotas ...blob/main/articles/quotas/networking-quota-requests.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation lists Azure PowerShell as a primary method for viewing quota usage, and it is mentioned before Linux-native tools (Azure CLI and REST API). While Azure CLI is cross-platform, the ordering and inclusion of PowerShell may subtly favor Windows users. No explicit Linux/macOS examples or screenshots are provided, but the main workflow is via the Azure portal, which is platform-agnostic.
Recommendations
  • List Azure CLI before Azure PowerShell to prioritize cross-platform tooling.
  • Provide explicit examples or screenshots for Linux/macOS users where relevant.
  • Clarify that Azure CLI is available on all major platforms and link to installation instructions for Linux/macOS.
  • If PowerShell is mentioned, note that PowerShell Core is available cross-platform.
GitHub Create Pull Request