Azure Arc

465
Total Pages
253
Linux-Friendly Pages
212
Pages with Bias
45.6%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

2334 issues found
Showing 776-800 of 2334 flagged pages
Azure Arc Diagnostics of Edge-Related Logs and Errors in Workload Orchestration .../azure-arc/workload-orchestration/diagnose-problems.md
Medium Priority View Details →
Scanned: 2026-03-03 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page provides almost exclusively PowerShell-based examples and scripts for enabling and managing diagnostics, log collection, and orchestration on Azure Arc-enabled Kubernetes clusters. File paths in JSON templates and scripts are Windows-style, and there are no Bash or Linux/macOS CLI equivalents. The use of PowerShell is pervasive, and Linux users are not given alternative instructions or scripts, creating friction for non-Windows users.
Recommendations
  • Provide Bash or shell script equivalents for all PowerShell commands, especially for az CLI operations.
  • Use cross-platform file path examples in JSON templates (e.g., /home/user/schema.yaml) or clarify that paths must be adapted for Linux/macOS.
  • Explicitly state whether the infra_onboarding.ps1 script is Windows-only, and offer a Linux-compatible onboarding script if possible.
  • Add notes or sections for Linux/macOS users, highlighting any differences in setup or command usage.
  • Where possible, show az CLI commands in Bash syntax (with line continuations using \) alongside PowerShell examples.
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 →
Scanned: 2026-03-03 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows Authentication
Summary
The documentation references Windows-centric tools and features such as PowerShell scripting support, SQL Server Management Studio (SSMS), SQL Server Data Tools (SSDT), and Windows Authentication. PowerShell scripting is highlighted as a manageability feature, and Windows Authentication is listed as supported, but there is no mention of Linux/macOS equivalents or alternatives. The tools section lists several Windows-only or Windows-preferred tools, with no explicit mention of cross-platform or Linux-native tools (e.g., sqlcmd, Azure Data Studio).
Recommendations
  • Add examples or references for Linux/macOS users, such as using sqlcmd or Azure Data Studio.
  • Clarify which tools are cross-platform and which are Windows-only.
  • Provide guidance for Linux/macOS users on authentication alternatives to Windows Authentication.
  • Mention PowerShell Core (pwsh) support if available, or provide Bash scripting examples.
  • Explicitly state tool/platform compatibility in the tools table.
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 →
Scanned: 2026-03-03 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is focused on configuring AKS Edge Essentials on Linux, but uses Windows-centric tools and patterns. Specifically, it relies on the Invoke-AksEdgeNodeCommand PowerShell cmdlet for Linux node configuration, without providing native Linux shell alternatives. Notepad is mentioned as a text editor, and there is no guidance for Linux-native editing or command-line approaches. This creates friction for Linux users who may not have access to PowerShell or Windows tools.
Recommendations
  • Provide native Linux shell command examples for checking and setting sysctl parameters (e.g., using 'sysctl' directly in bash).
  • Replace or supplement Notepad references with Linux text editors (e.g., 'nano', 'vim', 'gedit').
  • Clarify whether PowerShell is required on Linux, and if so, provide installation instructions or alternatives.
  • Ensure all steps can be completed using standard Linux tools and commands, not just Windows/PowerShell-based ones.
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 →
Scanned: 2026-03-03 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides several examples and tool recommendations that are Windows-centric, such as using SQL Server Management Studio (SSMS), Visual Studio Code, and specifying Windows file paths (e.g., C:\Backupfiles\test.bak). There are no explicit Linux/macOS equivalents or examples for backup/restore commands, file paths, or tool usage, and Windows paths and tools are presented first or exclusively.
Recommendations
  • Add Linux/macOS examples for file paths (e.g., /home/user/Backupfiles/test.bak) alongside Windows examples.
  • Mention cross-platform tools such as Azure Data Studio or command-line utilities (sqlcmd) that work on Linux/macOS, not just SSMS and Visual Studio Code.
  • Clarify that Azure Storage Explorer and Visual Studio Code are cross-platform, and provide installation/use instructions for Linux/macOS.
  • Provide explicit instructions or examples for Linux/macOS users, especially for backup/restore steps and kubectl cp usage.
  • Where possible, avoid referencing Windows-only tools or paths exclusively, or provide parity for other platforms.
GitHub Create Pull Request
Azure Arc Troubleshoot Azure Arc resource bridge issues ...re-arc/resource-bridge/troubleshoot-resource-bridge.md
Medium Priority View Details →
Scanned: 2026-03-03 00:00
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, there are several instances of Windows bias: PowerShell is used for network troubleshooting examples (e.g., Invoke-WebRequest, Resolve-DnsName), Windows paths are referenced in error messages, and Windows-specific terminology (e.g., RDP, time.windows.com) appears. Linux equivalents (such as curl, dig, or nslookup) are not consistently provided alongside PowerShell examples. In some sections, Windows tools or patterns are mentioned first or exclusively, creating friction for Linux/macOS users.
Recommendations
  • For every PowerShell example, provide a Linux/macOS equivalent (e.g., curl for Invoke-WebRequest, dig/nslookup for Resolve-DnsName).
  • When referencing Windows paths or error messages, clarify Linux/macOS equivalents or note differences.
  • Mention Linux/macOS troubleshooting steps and tools (e.g., SSH, terminal commands) alongside Windows instructions.
  • Ensure that CLI commands (az arcappliance) are shown to work on both Windows and Linux, and note any OS-specific requirements.
  • Where possible, avoid using Windows terminology (e.g., RDP) exclusively; mention SSH or console access for Linux/macOS.
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 →
Scanned: 2026-03-03 00:00
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 tasks (install, upgrade, uninstall, proxy configuration). However, Windows examples and tools (PowerShell, Group Policy, Microsoft Update, Control Panel, Registry Editor) are often presented first and in greater detail. Some automation scripts (e.g., stale resource cleanup) are only provided in PowerShell, with no Linux/bash equivalent. Windows-specific tools and patterns are referenced more frequently and with more explanation, while Linux instructions are concise and rely on standard package managers.
Recommendations
  • Provide bash or Azure CLI scripts for resource cleanup and automation tasks, not just PowerShell.
  • Ensure Linux instructions are as detailed as Windows instructions, including troubleshooting and automation options.
  • When listing upgrade/uninstall methods, alternate the order or present Linux and Windows equally (not always Windows first).
  • Add examples for managing agent lifecycle at scale on Linux (e.g., using Ansible, shell scripts, cron jobs).
  • Where Windows tools (e.g., Group Policy, Control Panel) are described, consider mentioning Linux equivalents (e.g., systemd, configuration management tools) or clarifying their absence.
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 →
Scanned: 2026-03-03 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides both Windows and Linux context, but Windows-specific tools and examples (PowerShell, Windows Admin Center, Windows Server Graphical Installer) are mentioned explicitly and before Linux equivalents. Deployment instructions reference PowerShell and Windows tools, but do not provide explicit Linux-focused examples or mention Linux-native tools (e.g., shell scripts, Linux package managers) in equal detail. Linux users may need to infer their deployment approach or consult external sources for parity.
Recommendations
  • Add explicit Linux deployment examples alongside Windows ones, such as Bash scripts or instructions for using Linux package managers.
  • Mention Linux-native tools (e.g., Ansible, shell scripting) with equal prominence as Windows tools.
  • Provide sample commands for both Windows (PowerShell) and Linux (Bash) when referencing script-based deployment.
  • Clarify that Azure Monitor Agent and Azure Arc support both Windows and Linux, and link to OS-specific guidance.
  • Ensure that graphical deployment options for Linux (if any) are mentioned, or clarify their absence.
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 →
Scanned: 2026-03-03 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides extensive PowerShell examples and references to Windows tools (such as New-NetFirewallRule and New-AzStorageBlobSASToken), with Windows-centric scripting and REST API scenarios. Linux-specific examples are minimal or absent, and Linux scripting patterns (e.g., bash, shell, iptables) are not demonstrated. Windows terminology and tools are mentioned first or exclusively in several sections, especially in REST API and PowerShell tabs.
Recommendations
  • Add Linux-specific script examples for Azure PowerShell and Azure CLI, such as using bash or shell scripts (e.g., 'echo Hello World!' or 'sudo apt update').
  • Include REST API examples for Linux scenarios, such as configuring firewall rules with iptables or ufw.
  • Balance PowerShell and CLI examples by showing both Windows and Linux script usage, and clarify OS-specific parameters or behaviors.
  • Mention Linux tools and scripting patterns alongside Windows tools, and avoid referencing Windows tools exclusively unless the feature is Windows-only.
  • In parameter explanations, provide Linux equivalents (e.g., for script file paths, show both Windows and Linux formats).
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 →
Scanned: 2026-03-03 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively provides instructions and examples for running a PowerShell script (RGCleanScript.ps1) to clean up Azure Arc workload orchestration resources. There are no examples or guidance for Linux/macOS users, such as using Bash, shell scripts, or cross-platform alternatives. The script appears to require PowerShell, which is traditionally Windows-centric, and no mention is made of running it on PowerShell Core (pwsh) or using Azure CLI directly.
Recommendations
  • Clarify whether the script is compatible with PowerShell Core (pwsh) on Linux/macOS, and provide instructions for those platforms if so.
  • If the script is Windows-only, explicitly state this limitation and suggest alternative clean-up methods for Linux/macOS users (e.g., using Azure CLI commands or providing a Bash version of the script).
  • Add examples for running the script on Linux/macOS, or provide equivalent Bash/shell scripts.
  • Mention cross-platform tools (like Azure CLI) and provide sample commands for resource clean-up.
GitHub Create Pull Request
Azure Arc Remove your VMware vCenter environment from Azure Arc ...e-arc/vmware-vsphere/remove-vcenter-from-arc-vmware.md
Medium Priority View Details →
Scanned: 2026-03-03 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed Windows/PowerShell instructions for running the deboarding script, including execution policy guidance and script invocation. There are no equivalent Linux/macOS instructions for running the script, nor is it clarified whether the script can be run on Linux/macOS. Windows instructions are presented first and in greater detail, while Linux users are left without guidance for this critical step.
Recommendations
  • Clarify whether the deboarding script can be run on Linux/macOS (e.g., via PowerShell Core or Azure CLI).
  • If supported, provide explicit Linux/macOS instructions for downloading and running the script, including any prerequisites (such as PowerShell Core installation, script permissions, etc.).
  • If the script is Windows-only, state this clearly and provide alternative manual steps or guidance for Linux/macOS users.
  • Present Windows and Linux/macOS instructions in parallel sections or clearly label them to improve parity.
  • Consider providing cross-platform script versions or tools if feasible.
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 →
Scanned: 2026-03-03 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation consistently uses PowerShell syntax for Azure CLI commands and references PowerShell scripts (.ps1) for automation, without providing Bash or Linux/macOS equivalents. There are no explicit Linux/macOS examples or instructions, and the scripting guidance is Windows-centric, which may create friction for non-Windows users.
Recommendations
  • Provide Azure CLI command examples in Bash syntax alongside PowerShell, especially since Azure CLI is cross-platform.
  • Offer Bash shell script equivalents for bulk_deployment.ps1 and workflow-delete.ps1, or clarify if the scripts are compatible with Linux/macOS environments.
  • Explicitly mention cross-platform compatibility for all CLI commands and scripts, and note any Windows-only limitations.
  • Add notes or sections for Linux/macOS users, including any required adaptations or dependencies.
GitHub Create Pull Request
Azure Arc Prepare the Environment for Workload Orchestration ...rc/workload-orchestration/initial-setup-environment.md
Medium Priority View Details →
Scanned: 2026-03-03 00:00
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 'winget', a Windows-only tool, without providing a Linux/macOS alternative. The file extraction example under the Bash tab uses 'Expand-Archive', which is a PowerShell/Windows command, not a Bash/Linux-native tool. There are no Linux/macOS equivalents (e.g., 'apt', 'brew', 'curl', 'unzip', 'tar') for these steps. Bash and PowerShell tabs are provided throughout, but Bash examples sometimes use Windows-specific commands. This creates friction for Linux/macOS users, especially in initial setup steps.
Recommendations
  • Provide Linux/macOS installation instructions for kubectl (e.g., using curl, apt, brew).
  • Replace 'Expand-Archive' in Bash examples with 'unzip' or 'tar' for Linux/macOS users.
  • Ensure Bash examples use cross-platform commands, not Windows-specific ones.
  • Add notes or tabs for macOS-specific instructions where relevant.
  • Review all Bash sections to confirm they are valid for Linux/macOS environments.
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 →
Scanned: 2026-03-03 00:00
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 migration script (WOGAMigration.ps1) and instructs users to run it in PowerShell, with no mention of Linux/macOS alternatives or cross-platform scripting. This creates friction for non-Windows users, as PowerShell is not natively available on Linux/macOS and no Bash or platform-neutral instructions are provided.
Recommendations
  • Provide a Bash or cross-platform script equivalent to WOGAMigration.ps1, or clarify if PowerShell Core (pwsh) can be used on Linux/macOS.
  • Add explicit instructions for running the migration script on Linux/macOS, including any prerequisites (e.g., installing PowerShell Core).
  • Mention whether the migration process is supported on non-Windows platforms, and if not, clarify the limitation.
  • Consider offering a platform-neutral migration tool or Azure CLI-based alternative.
GitHub Create Pull Request
Azure Arc Troubleshooting for Workload Orchestration ...es/azure-arc/workload-orchestration/troubleshooting.md
Medium Priority View Details →
Scanned: 2026-03-03 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The troubleshooting guidance for workload orchestration is heavily biased toward Windows/PowerShell usage. Most command-line examples are provided only in PowerShell syntax, even for tasks that are cross-platform (e.g., Azure CLI, Docker, kubectl). Bash/Linux equivalents are missing for critical steps, except in the 'service groups' section, which offers both Bash and PowerShell tabs. Windows/PowerShell commands are presented first and exclusively in most sections, creating friction for Linux/macOS users.
Recommendations
  • Provide Bash/Linux shell equivalents for all PowerShell command examples, especially for Azure CLI, Docker, and kubectl commands.
  • Where possible, use cross-platform syntax (e.g., Azure CLI commands without PowerShell-specific variable syntax).
  • Ensure that file manipulation steps (e.g., Base64 encoding, JSON creation) are shown in both PowerShell and Bash.
  • Review the order of examples to avoid always presenting Windows/PowerShell first.
  • Clarify when a command is Windows-only, and offer alternatives for Linux/macOS users.
GitHub Create Pull Request
Azure Arc Release Notes for Workload Orchestration ...cles/azure-arc/workload-orchestration/release-notes.md
Medium Priority View Details →
Scanned: 2026-03-02 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides CLI examples primarily in PowerShell syntax, especially in the May 2025 release section, and does not offer equivalent Bash or Linux shell examples. While the Azure CLI is cross-platform, the use of PowerShell-specific syntax (backticks for line continuation, variables with $) may confuse Linux/macOS users. Most other CLI instructions use generic Bash syntax, but the PowerShell examples are shown first and exclusively in some sections.
Recommendations
  • Provide Bash/Linux shell examples alongside PowerShell examples for CLI commands, especially where PowerShell syntax is used.
  • Clarify that Azure CLI commands work on all platforms and note any OS-specific syntax differences.
  • Use platform-neutral syntax (e.g., avoid PowerShell line continuations and variables in generic CLI documentation) or show both variants.
  • Add a note explaining how to adapt PowerShell examples for Bash 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 →
Scanned: 2026-03-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is intended for configuring a Linux-based AKS Edge Essentials cluster, but it relies heavily on the Windows-specific PowerShell cmdlet 'Invoke-AksEdgeNodeCommand' for Linux node configuration. There are no native Linux shell examples for checking or setting sysctl parameters, and the text editor example references Notepad, a Windows tool, instead of a Linux editor.
Recommendations
  • Provide native Linux shell commands for checking and setting sysctl parameters (e.g., 'sysctl fs.inotify.max_user_instances', 'echo ... | sudo tee ...').
  • Replace or supplement 'Notepad' with Linux text editors like 'nano', 'vim', or 'gedit' when editing configuration files.
  • Clarify whether 'Invoke-AksEdgeNodeCommand' is available cross-platform or provide Linux alternatives if not.
  • Ensure all critical steps can be completed using Linux-native tools and commands.
GitHub Create Pull Request
Azure Arc Install client tools ...b/main/articles/azure-arc/data/install-client-tools.md
Medium Priority View Details →
Scanned: 2026-03-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides installation instructions for client tools across platforms, but Windows links are often listed first, and there is a notable emphasis on Windows-specific behaviors (e.g., PowerShell alias for curl, cmd.exe usage). Linux installation instructions are less explicit, sometimes only referenced as 'install curl package' without a link or detailed guidance. There are no explicit Linux/macOS command examples or troubleshooting notes, and Windows-specific notes are more prominent.
Recommendations
  • List Linux/macOS installation links before or alongside Windows links to avoid Windows-first bias.
  • Provide explicit Linux/macOS installation instructions for tools like curl, including package manager commands (e.g., 'sudo apt install curl', 'brew install curl').
  • Add Linux/macOS-specific troubleshooting notes (e.g., for curl or kubectl usage) similar to the PowerShell alias note.
  • Include example commands for checking versions or installing tools on Linux/macOS, not just Windows.
  • Ensure parity in detail and clarity for Linux/macOS users throughout the documentation.
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 →
Scanned: 2026-03-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page lists several Windows-centric tools (SSMS, SQL Server Data Tools, SQL Server PowerShell, SQL Server Profiler) and explicitly mentions PowerShell scripting support as a manageability feature. While Azure CLI and Visual Studio Code are also mentioned, Windows tools are listed prominently and PowerShell is referenced as a core scripting method. There are no Linux-specific examples, tools, or scripting alternatives provided, and Windows authentication is listed as a supported security feature without mention of Linux/macOS equivalents.
Recommendations
  • Add examples or references for Linux/macOS-compatible tools (e.g., sqlcmd, Azure Data Studio, mssql-cli).
  • Clarify cross-platform support for scripting (e.g., Bash, Python, or Azure CLI usage for manageability tasks).
  • Mention authentication options suitable for Linux/macOS environments (e.g., Microsoft Entra ID, if supported, or other cross-platform authentication methods).
  • Balance tool listings by including Linux/macOS-friendly options alongside Windows tools, rather than focusing on Windows tools first.
  • If PowerShell is referenced, also mention Bash or other scripting alternatives for Linux/macOS users.
GitHub Create Pull Request
Azure Arc Back up controller database .../articles/azure-arc/data/backup-controller-database.md
Medium Priority View Details →
Scanned: 2026-03-02 00:00
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 PowerShell syntax and references the use of sqlcmd, which is often associated with Windows environments. The examples for verifying connectivity and executing SQL commands are given in PowerShell format, and no explicit Linux/macOS shell alternatives (such as Bash or sh) are provided. The documentation does not mention Linux-specific tools or provide parity examples for Linux/macOS users, even though the context is Kubernetes and Azure Arc, which are cross-platform.
Recommendations
  • Provide Bash/sh examples alongside PowerShell for kubectl exec and sqlcmd usage, ensuring Linux/macOS users can follow along easily.
  • Clarify that sqlcmd is available on Linux/macOS and provide installation instructions or links for those platforms.
  • Use generic shell syntax (e.g., $ kubectl ...) instead of PowerShell-specific formatting where possible.
  • Explicitly mention that all commands are cross-platform unless otherwise noted, and highlight any OS-specific caveats.
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 →
Scanned: 2026-03-02 00:00
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 tools and file paths, such as using SQL Server Management Studio (SSMS), Visual Studio Code, and Windows-style paths (e.g., C:\Backupfiles\test.bak). There are no explicit Linux/macOS examples for creating backups or copying files, and Linux file paths are only used in restore commands, not in backup steps. The instructions for copying files into pods with kubectl cp only show Windows source paths, and do not mention Linux/macOS equivalents.
Recommendations
  • Add explicit Linux/macOS examples for backup commands, using typical Linux file paths (e.g., /home/user/backup/test.bak).
  • Mention cross-platform tools for connecting to SQL Server, such as Azure Data Studio, in addition to SSMS and Visual Studio Code.
  • Provide kubectl cp examples using Linux/macOS source paths (e.g., /home/user/backup/test.bak) and clarify that the command works on all platforms.
  • Clarify that Azure Storage Explorer and Visual Studio Code are cross-platform, and provide installation links for Linux/macOS where applicable.
  • Include notes or sections for Linux/macOS users, highlighting any differences or additional steps.
GitHub Create Pull Request
Azure Arc Troubleshoot Azure Arc resource bridge issues ...re-arc/resource-bridge/troubleshoot-resource-bridge.md
Medium Priority View Details →
Scanned: 2026-03-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation is generally cross-platform, referencing Azure CLI and supporting both Windows and Linux management machines. However, there are several areas of Windows bias: PowerShell is used for troubleshooting (e.g., HTTP2 errors, DNS resolution), Windows-specific terminology (e.g., 'Remote PowerShell', 'RDP'), and Windows examples are sometimes given before Linux equivalents. Some CLI troubleshooting steps (e.g., downgrading Azure CLI with pip) mention Linux, but PowerShell commands are used for network validation and DNS resolution, with no equivalent Linux commands provided. Additionally, folder permission errors reference 'SSH folder' generically, but troubleshooting steps are not platform-specific. The documentation could be improved by providing Linux/macOS equivalents for PowerShell commands and ensuring parity in troubleshooting steps.
Recommendations
  • For every PowerShell command, provide a Bash/Linux equivalent (e.g., use curl or wget for HTTP2 troubleshooting, dig/nslookup for DNS resolution).
  • When referencing Windows tools (e.g., RDP, PowerShell), clarify Linux/macOS alternatives (e.g., SSH, terminal access).
  • Ensure troubleshooting steps for folder permissions, network connectivity, and CLI errors include Linux/macOS-specific guidance.
  • Where CLI commands are shown, explicitly state they are cross-platform and provide any OS-specific caveats.
  • Review the order of examples to avoid consistently showing Windows-first patterns.
GitHub Create Pull Request
Azure Arc What's new with Azure Connected Machine agent ...main/articles/azure-arc/servers/agent-release-notes.md
Medium Priority View Details →
Scanned: 2026-03-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation generally provides both Windows and Linux release notes and download links, but there is a notable bias in troubleshooting and known issues sections, where only Windows-specific commands and tools (e.g., attrib, PowerShell) are provided. Windows examples and instructions are often presented first, and Linux equivalents for troubleshooting are missing. Some improvements and bug fixes are described only for Windows tools (e.g., MSI installer, PowerShell scripts), with no Linux alternatives or guidance.
Recommendations
  • For every troubleshooting or known issue section that provides Windows command-line or PowerShell instructions, add equivalent Linux shell commands or guidance if the issue could affect Linux users.
  • When listing download links or examples, alternate the order or provide a neutral presentation (e.g., 'Download for Linux or Windows').
  • If a fix or improvement is Windows-only, clearly label it as such, and ensure Linux users are not left without guidance for similar scenarios.
  • Where possible, provide parity in scripting examples (e.g., show both PowerShell and Bash commands for common tasks).
GitHub Create Pull Request
Azure Arc Azure Connected Machine Agent Deployment Options .../main/articles/azure-arc/servers/deployment-options.md
Medium Priority View Details →
Scanned: 2026-03-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation presents several onboarding methods for the Azure Connected Machine agent, with both Linux and Windows options. However, PowerShell-based methods are highlighted prominently, and Windows-specific tools (Windows Admin Center, Group Policy, Configuration Manager) are listed in dedicated sections. Windows methods are shown first in the 'at scale' section, and Linux-specific automation tools (e.g., Ansible) are mentioned but not emphasized equally. There is a notable focus on Windows tooling and scripting, which may create friction for Linux users.
Recommendations
  • Provide Linux-specific examples and automation methods (e.g., Bash scripts, systemd, cron) alongside PowerShell.
  • Ensure that Linux onboarding methods (such as Ansible, shell scripts) are given equal prominence and detail as Windows methods.
  • Add links or references to Linux-native tools for at-scale deployment (e.g., Puppet, Chef, SaltStack) if supported.
  • Clarify which methods are best suited for Linux environments and provide step-by-step guides for Linux users.
  • Consider reordering the table or grouping methods by OS type to avoid implicit Windows-first bias.
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 →
Scanned: 2026-03-02 00:00
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 lifecycle tasks (install, upgrade, uninstall, proxy config), using clear tabbed sections for each OS. However, there are several areas where Windows bias is evident: Windows examples and tools (PowerShell, Group Policy, Control Panel, Msiexec) are often described in greater detail, with more step-by-step guidance, and appear first in some sections. The cleanup script for stale Arc resources is PowerShell-only, with no Linux/bash equivalent. Windows-specific tools and patterns (e.g., Group Policy, WSUS, Configuration Manager) are mentioned exclusively, while Linux equivalents (e.g., automation via cron or systemd) are not discussed. Linux instructions are present and generally sufficient, but less detailed and less contextual.
Recommendations
  • Provide a bash or Azure CLI script example for stale Arc resource cleanup, or at least mention how Linux users can achieve the same task.
  • Where Windows tools (e.g., Group Policy, WSUS, Configuration Manager) are discussed, add notes about Linux equivalents or alternative automation approaches (e.g., using cron, systemd, or Ansible).
  • Ensure Linux instructions are as detailed as Windows ones, including troubleshooting, logging, and automation tips.
  • Consider alternating the order of Windows and Linux sections, or presenting them in parallel, to avoid 'windows_first' bias.
  • Where PowerShell is used for Azure operations, provide Azure CLI equivalents (which are cross-platform).
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 →
Scanned: 2026-03-02 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides ARM template examples for both Linux and Windows Arc-enabled servers, but all deployment instructions and command-line examples use Azure PowerShell exclusively. There are no Azure CLI or Bash examples for deploying templates, and PowerShell is presented as the default/only method. Additionally, PowerShell deployment commands are shown before any mention of Azure CLI, which is only referenced in the 'Related content' section.
Recommendations
  • Add Azure CLI deployment examples alongside PowerShell, especially for template deployments (e.g., az deployment group create ...).
  • Explicitly state that both PowerShell and Azure CLI can be used, and provide links or inline examples for Linux/macOS users.
  • Consider showing Azure CLI examples first or in parallel with PowerShell to avoid implicit Windows-first bias.
  • Clarify that the template files themselves are cross-platform, and the deployment tooling can be used from any OS.
GitHub Create Pull Request
← Previous Page 32 of 94 Next →