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 851-875 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-02-28 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 page demonstrates a notable Windows bias. All CLI/script examples are provided in PowerShell syntax, with no Bash or Linux/macOS shell equivalents. Paths in JSON templates use Windows-style (C:\, E:\) exclusively. The onboarding and diagnostic scripts are referenced as PowerShell (.ps1) files, with no mention of Bash or cross-platform alternatives. This creates friction for Linux/macOS users, who may not be able to follow the steps directly.
Recommendations
  • Provide Bash/zsh shell equivalents for all PowerShell CLI examples, especially for az CLI commands, which are cross-platform.
  • Include Linux/macOS file path examples in JSON templates alongside Windows paths.
  • Document how to run onboarding and diagnostic scripts on Linux/macOS (e.g., provide Bash scripts or instructions for using PowerShell Core on non-Windows platforms).
  • Clarify if the infra_onboarding.ps1 script is supported on Linux/macOS, and if not, offer a cross-platform alternative.
  • Where possible, use platform-neutral language and tools (e.g., az CLI, kubectl) and avoid assuming Windows as the default environment.
GitHub Create Pull Request
Azure Arc Onboarding Scripts for Workload Orchestration ...azure-arc/workload-orchestration/onboarding-scripts.md
Medium Priority View Details →
Scanned: 2026-02-28 00:00
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 oriented toward Windows environments: all examples use PowerShell scripts (.ps1), instructions explicitly reference opening a PowerShell terminal, and prerequisites use Windows-specific tooling (winget). There are no Bash/shell script equivalents, nor are there instructions for running these onboarding scripts on Linux or macOS. This creates friction for non-Windows users and may prevent them from completing onboarding without significant adaptation.
Recommendations
  • Provide equivalent Bash or shell scripts for Linux/macOS users, or document how to run the existing scripts with PowerShell Core on those platforms.
  • Replace or supplement 'winget' installation instructions with cross-platform alternatives (e.g., apt, yum, brew, or direct download links).
  • Explicitly state whether the onboarding scripts are supported on Linux/macOS, and if not, provide guidance or alternatives.
  • Include example commands and terminal instructions for both Windows (PowerShell) and Linux/macOS (Bash or PowerShell Core).
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-02-28 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. In the 'Extract ZIP' section, the Bash tab uses 'Expand-Archive', which is a PowerShell/Windows command, not a native Bash/Linux command. There are no Linux/macOS-specific instructions for these steps, and Windows paths are used in examples. The structure of the page consistently presents Windows-centric tools and patterns first or exclusively, creating friction for Linux/macOS users.
Recommendations
  • Provide Linux/macOS alternatives for installing kubectl (e.g., using 'curl' or package managers like 'apt', 'brew', or 'yum').
  • In the 'Extract ZIP' section, use native Bash/Linux commands such as 'unzip' or 'tar' instead of 'Expand-Archive'.
  • Include Linux/macOS file path examples alongside Windows paths.
  • Review all Bash sections to ensure they use cross-platform commands and do not rely on Windows-specific tools.
  • Clearly indicate which instructions are Windows-only and provide parity for Linux/macOS users wherever possible.
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-02-28 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 script for migration, with instructions to run it in PowerShell. There are no examples or guidance for Linux/macOS users, such as Bash or cross-platform alternatives. The script filename and usage imply Windows-centric tooling, creating friction for non-Windows users.
Recommendations
  • Provide a Bash or shell script alternative for Linux/macOS users, or clarify if the PowerShell script is compatible with PowerShell Core on Linux/macOS.
  • Add explicit instructions for running the migration script on Linux/macOS, including any prerequisites (e.g., installing PowerShell Core).
  • Mention cross-platform compatibility if the script works on all OSes, or offer a platform-neutral migration method.
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-02-28 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides CLI examples primarily in PowerShell syntax, especially in the May 2025 release section, and does not offer equivalent Bash/Linux CLI examples. The Azure CLI is cross-platform, but the use of PowerShell-style command formatting and variables may create friction for Linux/macOS users. Most other CLI examples use Bash syntax, but the PowerShell examples are shown first and exclusively in some sections.
Recommendations
  • Provide Bash/Linux equivalents for all PowerShell CLI examples, especially for configuration set/download commands.
  • When showing CLI examples, use cross-platform syntax (e.g., Bash) or explicitly note both Windows (PowerShell) and Linux/macOS (Bash) versions.
  • Avoid using PowerShell-specific variable syntax (e.g., $rg, $solutionName) in CLI examples unless also showing Bash equivalents.
  • Review all CLI documentation for consistent cross-platform parity.
GitHub Create Pull Request
Azure Arc Troubleshooting for Workload Orchestration ...es/azure-arc/workload-orchestration/troubleshooting.md
Medium Priority View Details →
Scanned: 2026-02-28 00:00
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 notable Windows bias. Most command-line examples are provided only in PowerShell syntax, even for tasks that are cross-platform (e.g., az CLI, kubectl, docker). There are no explicit Linux/bash equivalents for critical troubleshooting steps, except in the 'service groups' section, where both Bash and PowerShell tabs are provided. Windows/PowerShell syntax is used by default throughout, and some commands (e.g., Base64 encoding, file manipulation) use PowerShell-specific patterns without Linux alternatives.
Recommendations
  • Provide Bash/Linux equivalents for all az CLI, kubectl, and docker commands, especially for steps involving file manipulation, Base64 encoding, and JSON creation.
  • Use cross-platform syntax for az CLI commands (e.g., avoid PowerShell variable syntax and backticks in examples).
  • Add explicit notes or tabs for Linux/macOS users, clarifying any OS-specific steps.
  • Ensure file encoding instructions are relevant for Linux/macOS editors (e.g., mention how to check/save UTF-8 encoding in Vim/Nano).
  • For Base64 encoding, provide Linux command (e.g., echo -n '<token>' | base64) alongside PowerShell.
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-02-27 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows Authentication
Summary
The documentation references several Windows-centric tools (SSMS, SQL Server Data Tools, SQL Server PowerShell, SQL Server Profiler) and features (Windows Authentication, PowerShell scripting support) without providing Linux/macOS alternatives or parity. While Azure CLI and Visual Studio Code are cross-platform, the emphasis on Windows tools and authentication options creates friction for non-Windows users.
Recommendations
  • Explicitly mention cross-platform alternatives for management and scripting, such as Azure Data Studio, sqlcmd, and Bash scripting.
  • Clarify which tools/features are Windows-only and provide guidance for Linux/macOS users where possible.
  • Add examples or links for using Azure CLI and VS Code on Linux/macOS for common management tasks.
  • Note limitations for Windows Authentication and PowerShell scripting on non-Windows platforms, and suggest alternatives (e.g., Microsoft Entra authentication, Azure CLI).
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-02-27 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is generally Linux-focused, but it uses Windows/PowerShell-specific tooling (Invoke-AksEdgeNodeCommand) for Linux node configuration, without providing native Linux shell alternatives. The text editor example (Notepad) is also Windows-centric, and there are no Linux-native command examples for sysctl configuration.
Recommendations
  • Provide native Linux shell commands for sysctl configuration (e.g., 'sysctl fs.inotify.max_user_instances', 'echo ... | sudo tee ...').
  • Replace or supplement Notepad with Linux text editors (e.g., nano, vim) when editing configuration files.
  • Clarify whether Invoke-AksEdgeNodeCommand is required or if direct Linux shell access is possible, and provide Linux-native instructions if so.
  • Ensure all steps can be completed using standard Linux tools, not only Azure/Windows-specific wrappers.
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-02-27 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-specific details and links are often presented first or more prominently. For example, installation links for 'kubectl' and 'curl' list Windows before Linux/macOS, and there is a note about using cmd.exe instead of PowerShell for curl on Windows, but no equivalent Linux/macOS guidance. The explanation about PowerShell's curl alias is Windows-specific, with no mention of similar issues on other platforms. Linux installation instructions for curl are vague ('install curl package') compared to the explicit Windows link.
Recommendations
  • Present installation links for all platforms in parallel or alphabetical order (e.g., Linux, macOS, Windows) to avoid Windows-first bias.
  • Provide equally detailed installation instructions for Linux and macOS (e.g., specify package manager commands for curl on Linux and Homebrew for macOS).
  • Add notes about platform-specific issues for Linux/macOS where relevant, not just Windows (e.g., clarify curl usage differences on Linux shells).
  • Avoid PowerShell-specific notes unless there are equivalent notes for Bash/zsh or other shells.
  • Ensure that all examples and guidance are cross-platform unless the tool is Windows-only.
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-02-27 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 instructions that assume a Windows environment, such as using Windows file paths (e.g., C:\Backupfiles\test.bak) and referencing tools like SQL Server Management Studio (SSMS) without mentioning Linux alternatives. There are no explicit Linux/macOS examples for creating backups or copying files, and the file path examples are Windows-centric. This may cause friction for Linux/macOS users attempting to follow the guide.
Recommendations
  • Provide parallel examples using Linux/macOS file paths (e.g., /home/user/backup/test.bak) wherever Windows paths are shown.
  • Mention and give examples using cross-platform tools (e.g., Azure Data Studio, sqlcmd) in addition to or instead of SSMS.
  • Clarify that the backup and file copy steps can be performed from Linux/macOS, and show the equivalent commands.
  • Where GUI tools are referenced (e.g., Azure Storage Explorer), note their cross-platform availability or suggest CLI alternatives (e.g., azcopy, Azure CLI).
GitHub Create Pull Request
Azure Arc CLI reference for `azcmagent connect` ...b/main/articles/azure-arc/servers/azcmagent-connect.md
Medium Priority View Details →
Scanned: 2026-02-27 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation provides authentication options and examples for connecting servers to Azure Arc using the azcmagent CLI. While the overall guidance is cross-platform, there is evidence of Windows bias: Windows authentication methods are described first, Windows certificate store options are detailed without Linux equivalents, and the access token section references PowerShell's Get-AzAccessToken as the primary method for obtaining tokens. Linux-specific guidance (such as using device code login and Azure CLI) is present but not as prominently featured or explained.
Recommendations
  • Reorder authentication options so Linux-default methods (device code, Azure CLI) are described before Windows-only options.
  • Add Linux-specific examples for obtaining access tokens (e.g., using Azure CLI: 'az account get-access-token') alongside PowerShell examples.
  • Clarify certificate storage and usage for Linux (e.g., recommended file locations, permissions, and certificate formats) to match the detail given for Windows certificate stores.
  • Explicitly state cross-platform support in examples and highlight any OS-specific caveats.
  • Provide a table or section summarizing authentication methods by OS (Windows, Linux, macOS) for quick reference.
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-02-27 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), but Windows examples and tools (PowerShell, Group Policy, WSUS, MSI installer) are often presented first or in greater detail. The cleanup script for stale resources is only provided in PowerShell, with no Linux/bash equivalent. Windows-specific tools and patterns (Control Panel, Registry, Group Policy) are described in depth, while Linux instructions are more concise and rely on standard package managers.
Recommendations
  • Provide bash or Azure CLI equivalents for PowerShell scripts, especially for resource cleanup.
  • Ensure Linux instructions are as detailed as Windows, including troubleshooting and automation tips.
  • Where possible, present Windows and Linux instructions side-by-side or in parallel tabs, rather than Windows-first.
  • Add links or references to Linux-native automation tools (e.g., cron, systemd) for agent maintenance.
  • For proxy configuration, clarify Linux service restart requirements and provide more detail on environment variable management.
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 →
Scanned: 2026-02-27 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation includes references to Windows-specific services (e.g., time.windows.com, sts.windows.net, login.windows.net, servicebus.windows.net) and mentions Windows NTP as a default for Hyper-V, but does not provide equivalent Linux examples or clarify Linux alternatives. Windows terminology and endpoints appear before Linux-specific ones (e.g., Microsoft open source packages manager for Linux is listed after Windows NTP). There are no explicit PowerShell or Windows-only command examples, but the service/endpoint bias and ordering favor Windows.
Recommendations
  • Add Linux NTP server examples (e.g., ntp.ubuntu.com or pool.ntp.org) alongside time.windows.com, and clarify when to use each.
  • Clarify that sts.windows.net, login.windows.net, and servicebus.windows.net are cross-platform endpoints, not Windows-only, or provide Linux-specific guidance if needed.
  • Reorder the firewall/proxy table to group Linux and Windows endpoints/services equally, or add notes indicating Linux alternatives where relevant.
  • Explicitly mention Linux management machines and appliance VMs, and ensure Linux-specific requirements (such as packages.microsoft.com) are highlighted equally.
  • Add a short section or note confirming that both Windows and Linux management machines/appliance VMs are supported, and link to OS-specific configuration guidance if available.
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-02-27 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page includes several examples and troubleshooting steps that reference Windows-specific tools and patterns, such as PowerShell cmdlets and Windows folder paths. Windows terminology (e.g., 'Remote PowerShell', 'RDP', 'time.windows.com') is mentioned before or instead of Linux equivalents. While Linux is referenced in some troubleshooting (e.g., glibc errors), Linux-specific commands and guidance are often missing or less prominent. Most CLI examples are generic, but where OS-specific troubleshooting is required, Windows is prioritized.
Recommendations
  • Provide Linux/macOS equivalents for all PowerShell and Windows-specific commands (e.g., use curl or wget for HTTP troubleshooting, and show how to test HTTP/2 with Linux tools).
  • Add explicit Linux/macOS instructions for SSH folder permissions, DNS resolution (e.g., using dig or nslookup), and proxy configuration.
  • Where Windows paths or tools are referenced (e.g., 'C:\Program Files'), add corresponding Linux/macOS paths and troubleshooting steps.
  • Ensure that troubleshooting steps for network, proxy, and certificate issues include Linux/macOS guidance (e.g., how to check SSL proxy trust, how to configure environment variables for proxies).
  • When referencing time synchronization (e.g., NTP), clarify how to check and configure NTP on Linux/macOS hosts.
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-02-27 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides deployment options for the Azure Connected Machine agent across both Linux and Windows, but there is a notable emphasis on Windows-specific tools and methods. PowerShell is highlighted as a primary onboarding method for both OS types, and several Windows-only methods (Windows Admin Center, Configuration Manager, Group Policy) are listed separately. Windows tools and patterns (e.g., PowerShell, Configuration Manager, Group Policy) are mentioned more frequently and in greater detail than Linux equivalents. Linux-specific automation tools (such as Ansible) are included, but PowerShell is presented as a cross-platform solution, which may not be optimal for Linux users. The order of methods also places Windows-centric approaches before Linux-specific ones in several places.
Recommendations
  • Provide explicit Linux shell (bash) examples and scripts alongside PowerShell examples for onboarding and automation.
  • Highlight Linux-native automation tools (such as Ansible, shell scripts) earlier and more prominently, rather than positioning PowerShell as the default cross-platform solution.
  • Add links or references to Linux package managers (e.g., apt, yum) for agent installation.
  • Clarify which methods are best suited for Linux environments and provide guidance tailored to Linux administrators.
  • Balance the order of presentation so that Linux and Windows methods are equally visible and accessible.
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-02-27 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, ensuring parity in template content. However, all deployment commands and walkthroughs exclusively use Azure PowerShell, with no Azure CLI or Bash examples. Additionally, PowerShell commands are presented first and as the only method for deploying templates, which may create friction for Linux/macOS users who prefer CLI or Bash. Windows file paths are used in example commands, further reinforcing Windows-centric patterns.
Recommendations
  • Add Azure CLI deployment examples alongside PowerShell commands, e.g., 'az deployment group create --resource-group <resource-group-name> --template-file <template-filename.json> --parameters <parameter-filename.json>'.
  • Mention that Azure CLI and Bash can be used on Linux/macOS for template deployment, and provide sample commands.
  • Use generic file paths (e.g., './AzureMonitorAgent.json') or note that file paths should be adapted for Linux/macOS environments.
  • Consider presenting CLI and PowerShell examples side-by-side, or at least referencing CLI options in the 'Deployment commands' section.
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-02-27 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-specific tools (such as New-AzStorageBlobSASToken and New-NetFirewallRule), with Windows-focused scripting and REST API scenarios. Linux equivalents are mentioned but not demonstrated, and Linux-specific examples (such as shell scripting or firewall configuration) are missing. The REST API section exclusively uses Windows Server and PowerShell cmdlets, with no Linux scenario or shell script example.
Recommendations
  • Add Linux-specific script examples in PowerShell, Azure CLI, and REST API sections (e.g., bash scripts, Linux firewall commands like ufw or iptables).
  • Provide REST API examples targeting a Linux Arc-enabled server, including sample shell scripts.
  • Balance PowerShell and Azure CLI examples by showing both Windows and Linux use cases.
  • Mention and demonstrate Linux tools for generating SAS tokens (e.g., Azure CLI az storage blob generate-sas) instead of only PowerShell.
  • Clarify when examples are Windows-specific and provide Linux alternatives where possible.
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-02-27 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 context but tends to mention Windows-specific tools (Windows Admin Center, Windows Server Graphical Installer, PowerShell) before Linux equivalents. PowerShell is highlighted as a deployment method, and Windows-specific graphical tools are referenced, while Linux tools (e.g., Bash, Ansible) are mentioned but not given equal prominence or example detail. There are no explicit Linux command examples or step-by-step Linux deployment instructions, and Windows deployment options are listed first.
Recommendations
  • Provide explicit Linux deployment examples, such as Bash scripts or command-line instructions for onboarding Linux servers to Azure Arc.
  • Mention Linux tools (e.g., Ansible, Bash) before or alongside Windows tools in deployment sections.
  • Add references or links to Linux-specific documentation for Azure Monitor Agent and Azure Arc onboarding.
  • Ensure parity in graphical and programmatic deployment guidance for Linux environments.
  • Include sample commands or scripts for Linux environments where PowerShell or Windows tools are shown.
GitHub Create Pull Request
Azure Arc Recover from accidental deletion of resource bridge VM ...em-center-virtual-machine-manager/disaster-recovery.md
Medium Priority View Details →
Scanned: 2026-02-27 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides recovery instructions and a script exclusively for Windows, using PowerShell. There are no examples or guidance for Linux/macOS users, nor is there mention of equivalent tools or scripts for those platforms. The section is titled 'Recover Arc resource bridge from a Windows machine', and no alternative is provided.
Recommendations
  • Provide equivalent recovery instructions and scripts for Linux/macOS users, using Bash or Python.
  • Clarify if the recovery process is supported only on Windows, and if so, explain the rationale.
  • If possible, offer a cross-platform script or containerized tool to perform the recovery.
  • Add a note about platform requirements for the disaster recovery script.
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 →
Scanned: 2026-02-27 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page presents a notable Windows bias, especially in the 'Auto Arc-enablement script' section, where only PowerShell scripts and Windows Task Scheduler are used for automation. The script usage instructions and scheduling examples are Windows-centric, with no Linux/macOS equivalents provided. Windows tools (PowerShell, Task Scheduler) are mentioned exclusively, and Windows instructions are often presented before Linux ones. While Linux is acknowledged in prerequisites and out-of-band methods, Linux/macOS users lack parity in automation and scheduling guidance.
Recommendations
  • Provide Bash or shell script equivalents for the auto-enablement script, or clarify if the script is cross-platform.
  • Include instructions for running the script on Linux/macOS, such as using cron for scheduling instead of Windows Task Scheduler.
  • Offer Linux/macOS-specific examples for script execution, including handling permissions and sudo usage.
  • Clarify any OS limitations of the helper script and provide alternatives if it is Windows-only.
  • Ensure parity in example ordering and tool recommendations (e.g., mention Ansible, cron, Bash alongside PowerShell and Task Scheduler).
GitHub Create Pull Request
Azure Arc Perform disaster recovery operations ...mware-vsphere/recover-from-resource-bridge-deletion.md
Medium Priority View Details →
Scanned: 2026-02-27 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exclusively provides PowerShell examples and references the onboarding script as a PowerShell (.ps1) script, with no mention of Bash, Linux, or macOS equivalents. All command-line instructions and code snippets are Windows-centric, and there is no guidance for users on Linux or macOS platforms. This creates friction for non-Windows users attempting disaster recovery operations for Azure Arc-enabled VMware vSphere environments.
Recommendations
  • Provide equivalent Bash or shell script examples for Linux/macOS users, or clarify if the onboarding script is cross-platform.
  • Explicitly state platform requirements for the onboarding script (e.g., if it must be run on Windows/PowerShell, mention this up front).
  • If possible, offer a cross-platform onboarding script or instructions for running PowerShell scripts on Linux/macOS (e.g., via PowerShell Core).
  • Add notes or links for Linux/macOS users about prerequisites or alternative tooling.
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-02-27 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page provides detailed instructions for both Windows and Linux VM agent removal, but when it comes to running the deboarding script for removing VMware vSphere resources from Azure Arc, only Windows/PowerShell instructions are given. The script is presented as a PowerShell script with no mention of a Linux or cross-platform equivalent, and Windows instructions are shown first and exclusively. This creates friction for Linux/macOS users who may not have access to PowerShell or Windows environments for this critical step.
Recommendations
  • Provide clear instructions or an alternative script for Linux/macOS users, such as a Bash or Python version, or document how to run the PowerShell script cross-platform (e.g., with PowerShell Core on Linux/macOS).
  • Explicitly state any platform limitations for the deboarding script and offer guidance for Linux/macOS users (e.g., using PowerShell Core, or manual steps).
  • Consider including manual removal steps in greater detail for users unable to run the PowerShell script.
  • Present Windows and Linux instructions in parallel or clarify which steps are platform-specific.
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-02-27 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 (e.g., bulk_deployment.ps1, workflow-delete.ps1) without providing equivalent Bash or shell script examples. There are no Linux/macOS-specific instructions or examples, and the PowerShell syntax is used exclusively for CLI commands, which may confuse or hinder Linux/macOS users. The documentation does not mention how to run these scripts or commands on Linux/macOS, nor does it provide alternative shell script options.
Recommendations
  • Provide Azure CLI command examples in Bash syntax, not just PowerShell.
  • Add Linux/macOS-specific instructions for running bulk deployment and workflow deletion, including Bash shell script equivalents for bulk_deployment.ps1 and workflow-delete.ps1.
  • Clarify that Azure CLI commands can be run in Bash or PowerShell, and show both syntaxes where appropriate.
  • Mention any prerequisites or dependencies for Linux/macOS users (e.g., how to install Azure CLI, how to execute scripts).
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-02-27 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 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, as PowerShell is not natively available and no alternative script or instructions are provided.
Recommendations
  • Provide a Bash or cross-platform script for migration, or document how to run the PowerShell script on Linux/macOS (e.g., using PowerShell Core).
  • Explicitly state if the script is compatible with PowerShell Core on Linux/macOS, and provide installation instructions if needed.
  • Offer equivalent Linux/macOS command examples where possible.
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-02-27 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. Bash syntax is used elsewhere, but PowerShell is shown first and exclusively in some cases. There are no explicit Linux/macOS-specific examples or references to Linux tools, and the CLI commands are presented in a way that may be more familiar to Windows users. However, the Azure CLI is cross-platform, and most commands are generic, but the example formatting could create friction for Linux/macOS users.
Recommendations
  • Provide both Bash and PowerShell examples for CLI commands, especially where PowerShell is used.
  • Show Bash examples first or side-by-side with PowerShell to emphasize cross-platform support.
  • Explicitly mention that Azure CLI commands work on Linux/macOS and Windows.
  • Avoid using PowerShell-specific syntax (e.g., backticks for line continuation) unless also providing Bash equivalents.
  • Add notes or links for Linux/macOS users about CLI installation and usage.
GitHub Create Pull Request
← Previous Page 35 of 94 Next →