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 1101-1125 of 2334 flagged pages
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-14 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, step-by-step instructions and script usage for Windows/PowerShell, including explicit PowerShell commands and environment-specific notes, while omitting equivalent instructions or scripts for Linux/macOS users. The deboarding script section is Windows/PowerShell-centric, with no mention of how to run the script on Linux/macOS, or whether a cross-platform version exists. Linux instructions are only provided for agent uninstallation, not for the main deboarding workflow.
Recommendations
  • Provide instructions for running the deboarding script on Linux/macOS, or clarify if it is Windows-only.
  • If a cross-platform (e.g., Bash or Python) version of the deboarding script exists, link to it and provide usage examples.
  • If the script is PowerShell Core compatible, document how to run it on Linux/macOS using pwsh.
  • Reorder sections or provide parallel instructions so Linux/macOS users are not left behind in critical workflows.
  • Explicitly state OS requirements and alternatives for all scripts and commands.
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 →
Scanned: 2026-02-14 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 demonstrates notable Windows bias. All CLI/script examples are provided in PowerShell syntax, with no Bash or Linux shell equivalents. Paths in JSON templates use Windows-style backslashes and drive letters. The onboarding scripts are referenced as PowerShell (.ps1) only, with no mention of Bash or cross-platform alternatives. There are no Linux/macOS-specific instructions or examples, and Windows tools/patterns (PowerShell, Windows file paths) are used throughout.
Recommendations
  • Provide Bash or cross-platform shell examples alongside PowerShell for all CLI/script instructions.
  • Use platform-neutral file path examples in JSON templates, or provide both Windows and Linux versions.
  • Clarify whether the onboarding scripts (.ps1) are supported on Linux/macOS (via PowerShell Core), and provide guidance for Linux users.
  • Mention any prerequisites or limitations for Linux/macOS users explicitly.
  • Where possible, use Azure CLI commands in Bash syntax, or note that the commands work in both PowerShell and Bash.
  • Add Linux/macOS-specific troubleshooting or log collection guidance if applicable.
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-14 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 package manager, with no Linux/macOS alternative. The file extraction example under the Bash tab uses 'Expand-Archive', which is a PowerShell/Windows command, not a native Bash/Linux tool. There are no Linux/macOS-specific instructions for these steps, and Windows-centric tools and paths (e.g., 'C:\path\to\archive.zip') are used throughout. While Azure CLI and kubectl are cross-platform, the documentation does not provide parity for Linux/macOS users in critical setup steps.
Recommendations
  • Provide Linux/macOS alternatives for installing kubectl, such as 'curl' or 'apt/yum/brew' commands.
  • Replace 'Expand-Archive' in Bash examples with 'unzip' or 'tar' commands for Linux/macOS users.
  • Use generic file paths (e.g., '/home/user/archive.zip') in Bash examples instead of Windows-style paths.
  • Clearly indicate which commands are Windows-specific and provide equivalent commands for other platforms.
  • Add a section or tab for Linux/macOS users where needed, especially for installation and file extraction steps.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides CLI examples using PowerShell syntax (backticks for line continuation, $variable notation), which is Windows-centric. Bash examples are present for az extension installation/update, but configuration examples are only shown in PowerShell. There is no mention of Linux/macOS shell equivalents or usage patterns, and PowerShell examples appear before any Bash alternatives.
Recommendations
  • Provide equivalent Bash examples for all CLI commands, especially for configuration set/download tasks.
  • Clarify that the Azure CLI works cross-platform and show both Windows (PowerShell) and Linux/macOS (Bash) command syntax where relevant.
  • Use generic CLI syntax in documentation examples, or alternate between Bash and PowerShell to avoid implicit platform prioritization.
  • Add notes or links for Linux/macOS users about line continuation and variable usage differences.
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-14 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 provides only a PowerShell script for migration, with no mention of Linux/macOS-compatible alternatives or instructions. The script is referenced as a .ps1 file, which is traditionally Windows-centric, and the usage example is exclusively PowerShell. There is no guidance for users on Linux or macOS platforms, nor any mention of Bash or cross-platform scripting.
Recommendations
  • Provide instructions for running the migration script on Linux/macOS, such as using PowerShell Core (pwsh), if supported.
  • Clarify whether the script is compatible with PowerShell Core on non-Windows platforms. If not, offer an alternative Bash or Python script for Linux/macOS users.
  • Include explicit Linux/macOS usage examples and troubleshooting notes.
  • Mention prerequisites for running PowerShell scripts on non-Windows systems (e.g., installing PowerShell Core).
GitHub Create Pull Request
Azure Arc Troubleshooting for Workload Orchestration ...es/azure-arc/workload-orchestration/troubleshooting.md
Medium Priority View Details →
Scanned: 2026-02-14 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 PowerShell and Windows-style command usage. Most examples, including those for Azure CLI, Docker, and Kubernetes, are provided only in PowerShell syntax or with Windows-specific command patterns. Linux/Bash equivalents are missing for critical troubleshooting steps, except for the 'service group' section, which does provide both Bash and PowerShell tabs. This creates friction for Linux/macOS users, especially in sections where only PowerShell commands are given and Windows-style variable usage is assumed.
Recommendations
  • Provide Bash/Linux equivalents for all PowerShell commands, especially for Azure CLI, Docker, and Kubernetes operations.
  • Use cross-platform variable syntax (e.g., $VAR for PowerShell, $VAR for Bash) and clarify which shell is expected.
  • Add notes or tabs indicating which commands are for Windows/PowerShell and which are for Bash/Linux.
  • Ensure Docker and kubectl examples are shown in Bash syntax as well, since these tools are widely used on Linux/macOS.
  • Review and update file encoding instructions to clarify cross-platform editors and encoding differences.
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-13 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 is often mentioned first or receives special notes. For example, kubectl installation links list Windows first, and curl installation provides a Windows link but only mentions 'Linux: install curl package' without a link. There are PowerShell-specific notes (e.g., curl alias) and guidance for Windows cmd.exe, but no equivalent Linux/macOS shell guidance. Linux/macOS users may need to infer steps or search for links themselves.
Recommendations
  • Provide explicit installation links for curl on Linux and macOS, similar to Windows.
  • When listing installation links for tools, rotate or randomize the order, or list all platforms equally (e.g., Windows | Linux | macOS).
  • Add notes for Linux/macOS shell usage where PowerShell/cmd.exe notes are given (e.g., for curl or kubectl).
  • Ensure that all examples and guidance are provided for Linux/macOS as well as Windows, not just referenced or implied.
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-02-13 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 running the script with PowerShell Core on those platforms or providing Bash/CLI alternatives. The documentation assumes the use of Windows tools and does not mention cross-platform compatibility.
Recommendations
  • Clarify whether RGCleanScript.ps1 is compatible with PowerShell Core on Linux/macOS. If so, provide explicit instructions for running the script on those platforms.
  • If the script is Windows-only, offer an alternative clean-up method for Linux/macOS users, such as an Azure CLI or Bash script.
  • Add a note about platform compatibility and prerequisites for running the script.
  • Include examples for Linux/macOS users, such as running PowerShell scripts via pwsh or using Azure CLI commands for resource deletion.
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-13 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-centric tools (Invoke-AksEdgeNodeCommand) for Linux node configuration, and does not provide native Linux shell/SSH alternatives. This creates friction for Linux/macOS users who may not have access to PowerShell or Windows tools.
Recommendations
  • Provide native Linux shell/SSH command examples for sysctl configuration (e.g., using ssh or direct shell access).
  • Clarify whether Invoke-AksEdgeNodeCommand is available cross-platform or suggest alternatives for Linux/macOS users.
  • Add explicit instructions for editing aksedge-config.json using Linux text editors (e.g., nano, vim) instead of Notepad.
  • Ensure all steps can be completed from a Linux/macOS environment without requiring Windows tools.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. Windows tools (SQL Server Management Studio, Notepad, OneNote) are mentioned exclusively, and backup examples use Windows file paths (C:\Backupfiles\test.bak) without Linux/macOS equivalents. Instructions for creating backups and copying files into pods show Windows examples first and do not provide Linux/macOS alternatives for file paths or tools. There is no explicit guidance for Linux users on how to perform equivalent tasks (e.g., using Azure Data Studio, specifying Linux file paths, or using Linux-native editors).
Recommendations
  • Provide Linux/macOS equivalents for backup file paths (e.g., /home/user/backup/test.bak) in SQL commands and kubectl cp examples.
  • Mention cross-platform tools such as Azure Data Studio alongside SQL Server Management Studio, and clarify that Visual Studio Code is available on all platforms.
  • Suggest Linux/macOS alternatives for saving SAS tokens (e.g., gedit, nano, TextEdit) instead of only Notepad/OneNote.
  • Explicitly state that all steps can be performed on Linux/macOS and highlight any platform-specific considerations.
  • Add notes or examples for Linux/macOS users in sections where Windows tools or conventions are referenced.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools
Summary
The documentation page lists several Windows-centric tools (SSMS, SQL Server Data Tools, SQL Server Profiler, SQL Server PowerShell) and mentions PowerShell scripting support as a manageability feature. While Azure CLI and VS Code are included, there is a notable emphasis on Windows-native tools and PowerShell, with no explicit mention of Linux/macOS alternatives or parity for scripting and management tasks.
Recommendations
  • Explicitly mention cross-platform tools such as Azure Data Studio, which runs on Windows, Linux, and macOS.
  • Clarify PowerShell scripting support: note that PowerShell Core is cross-platform, and provide examples or links for Linux/macOS usage.
  • Add examples or references for using Azure CLI and VS Code extensions on Linux/macOS.
  • Include guidance for Linux/macOS users on managing SQL Managed Instance enabled by Azure Arc, such as using containerized tools or relevant open-source alternatives.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page lists both Windows and Linux-related endpoints, but there is a notable Windows bias: Windows NTP server ('time.windows.com') is mentioned specifically, and several endpoints reference Windows in their names (e.g., 'login.windows.net', 'servicebus.windows.net'). Windows-specific tools and services (such as Azure CLI installer download, Windows NTP, and diagnostic data from Windows) are referenced, while Linux equivalents (e.g., Linux NTP servers) are not mentioned or explained. The ordering of examples and notes often puts Windows endpoints first or exclusively, with Linux details only briefly referenced (e.g., 'Download Linux installation package' for packages.microsoft.com).
Recommendations
  • Explicitly mention Linux NTP server options (e.g., 'ntp.ubuntu.com', 'pool.ntp.org') alongside 'time.windows.com', and clarify when Windows NTP is required versus when Linux NTP is supported.
  • For endpoints and services that are cross-platform (e.g., Azure CLI), clarify installation steps or requirements for both Windows and Linux management machines.
  • Add notes or examples for Linux-based management machines and appliance VMs, especially where Windows-specific endpoints or tools are referenced.
  • Ensure Linux-related endpoints and tools are presented with equal prominence and detail as Windows ones.
  • Where diagnostic data is referenced as 'from Windows', clarify if Linux appliance VMs also send diagnostic data and provide relevant endpoints.
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-13 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 and Windows command-line examples are given for troubleshooting network issues (e.g., Invoke-WebRequest, Resolve-DnsName, ping), and Windows paths are referenced in error messages. Linux equivalents (such as curl, dig, or nslookup) are not provided alongside these examples. Additionally, Windows tools and terminology (e.g., RDP, Windows folder paths) are mentioned before or instead of Linux/macOS alternatives. While some Linux-specific errors (GLIBC version) are addressed, overall, Linux/macOS users may experience friction due to the lack of parity in troubleshooting steps and examples.
Recommendations
  • Provide Linux/macOS equivalents for all PowerShell and Windows command-line examples (e.g., curl for Invoke-WebRequest, dig/nslookup for Resolve-DnsName).
  • Include troubleshooting steps and commands for Linux/macOS environments wherever Windows-specific instructions are given.
  • Clarify that the management machine can be Windows, Linux, or macOS, and specify any OS-specific requirements or limitations.
  • Add Linux/macOS file path examples and permissions troubleshooting alongside Windows paths.
  • Ensure error messages and troubleshooting steps reference both Windows and Linux/macOS environments equally.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides comprehensive coverage for both Windows and Linux platforms, including installation, upgrade, uninstall, and proxy configuration. However, there are several areas where Windows bias is evident: Windows examples and instructions are often presented first; Windows-specific tools and infrastructure (such as Microsoft Update, Group Policy, Configuration Manager, WSUS) are described in detail, while Linux equivalents are not discussed; PowerShell is heavily used for scripting and automation, with no Linux shell script equivalents for tasks like cleaning up stale resources.
Recommendations
  • Alternate the order of Windows and Linux sections so Linux instructions are not always second.
  • Provide equivalent Linux shell scripts (e.g., Bash) for automation tasks such as cleaning up stale Arc-enabled servers.
  • Add more detail about Linux update infrastructure (e.g., using unattended-upgrades, cron jobs, or configuration management tools like Ansible or Puppet) for agent updates.
  • Where Windows-specific tools are discussed (e.g., Group Policy, WSUS), briefly mention Linux alternatives or clarify that these are Windows-only.
  • Ensure parity in troubleshooting and management examples for both platforms.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides deployment instructions exclusively using Azure PowerShell commands, with no equivalent Azure CLI or Bash examples. All deployment steps use PowerShell syntax, which is native to Windows but available on Linux/macOS only if PowerShell is installed. While ARM template samples are provided for both Linux and Windows VM extensions, the deployment workflow is Windows-centric. Additionally, PowerShell examples are presented before mentioning Azure CLI as an alternative in the 'Related content' section.
Recommendations
  • Add Azure CLI deployment examples alongside PowerShell commands, especially for template deployment (e.g., az deployment group create).
  • Explicitly note that PowerShell Core can be used on Linux/macOS, and provide Bash/CLI alternatives where possible.
  • Consider showing Azure CLI examples first or in parallel with PowerShell to avoid Windows-first bias.
  • Clarify prerequisites for PowerShell usage on non-Windows platforms.
GitHub Create Pull Request
Azure Arc Azure Arc resource bridge system requirements ...icles/azure-arc/resource-bridge/system-requirements.md
Medium Priority View Details →
Scanned: 2026-02-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page for Azure Arc resource bridge system requirements exhibits mild Windows bias. Azure CLI installation links and requirements are primarily referenced with Windows-specific URLs and terminology (e.g., 'Azure CLI x64' linking to the Windows install page). There are no explicit Linux/macOS examples or references for management machine setup, CLI installation, or file paths, despite Azure CLI being cross-platform. The examples and instructions assume a Windows environment, potentially creating friction for Linux/macOS users.
Recommendations
  • Add explicit instructions and links for installing Azure CLI on Linux and macOS, alongside the Windows instructions.
  • Clarify that the management machine can be Linux, macOS, or Windows, and provide parity in requirements and examples.
  • Include example file paths and CLI usage for Linux/macOS environments (e.g., home directories, shell commands).
  • Ensure CLI commands and configuration file handling are described in a platform-agnostic way, or provide platform-specific notes as needed.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides authentication options for both Windows and Linux, but several sections show Windows bias. The 'Interactive browser login' is described as Windows-only and is listed first. Windows certificate store usage is detailed, while Linux equivalents are not mentioned. The access token example references PowerShell's Get-AzAccessToken without mentioning Linux alternatives. Overall, Windows tools and patterns are mentioned before or instead of Linux equivalents.
Recommendations
  • Reorder authentication options so Linux-default methods (device code, Azure CLI) are presented first or equally.
  • Add explicit Linux/macOS guidance for certificate-based authentication, such as storing certificates in standard file paths and using PEM/PFX files.
  • For access token acquisition, mention cross-platform methods (e.g., Azure CLI's 'az account get-access-token') alongside PowerShell.
  • Clarify that all examples are cross-platform unless otherwise noted, and add notes for Linux-specific behaviors where relevant.
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-13 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 downloadable 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 explicitly titled 'Recover Arc resource bridge from a Windows machine', and no Linux/macOS recovery path is described.
Recommendations
  • Provide equivalent recovery instructions for Linux/macOS users, including Bash or Python scripts if possible.
  • Mention whether the recovery process is supported or unsupported on Linux/macOS, and clarify any platform limitations.
  • If the script is Windows-only, explicitly state this and offer alternatives or workarounds for non-Windows environments.
  • Consider offering cross-platform scripts or containerized solutions to improve accessibility.
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-13 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 in its automation examples and tooling. The primary automation script is a PowerShell (.ps1) script, and instructions for running it reference PowerShell terminals and Windows Task Scheduler for cron-like automation. Windows tools and patterns (PowerShell, Task Scheduler) are mentioned exclusively or before Linux equivalents. While Linux is referenced in prerequisites and out-of-band methods (e.g., Ansible), there are no Linux shell script examples or guidance for running the automation at scale on Linux/macOS. The bias creates friction for Linux/macOS users who wish to automate Arc agent installation at scale.
Recommendations
  • Provide a Bash/shell script equivalent for the PowerShell automation script, or document how to run the PowerShell script on Linux/macOS (e.g., via PowerShell Core).
  • Include instructions for scheduling the automation on Linux (e.g., using cron) alongside Windows Task Scheduler examples.
  • Offer Linux/macOS terminal usage examples for running the script, not just PowerShell.
  • Ensure parity in examples for both Windows and Linux, especially for scale operations.
  • Clarify if the provided PowerShell script is cross-platform (PowerShell Core), and if not, offer a Linux-compatible alternative.
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-13 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 and script invocation, but does not offer equivalent Linux/macOS guidance. The script is referenced as a PowerShell script (.ps1), and only Windows-specific steps are described for its execution. Linux agent removal is covered, but Linux/macOS users are left without clear instructions for running the deboarding script or manual alternatives.
Recommendations
  • Provide explicit instructions for running the deboarding script on Linux/macOS, including prerequisites (e.g., PowerShell Core installation) and command examples.
  • Clarify whether the script can be run cross-platform or if a Bash version is available; if not, suggest manual steps or alternative scripts for Linux/macOS users.
  • List Linux/macOS steps alongside Windows steps, rather than only after or omitting them.
  • Mention PowerShell Core as an option for non-Windows users, with installation links and usage examples.
  • Add a note about script compatibility and any limitations for Linux/macOS environments.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation page provides only PowerShell examples and scripts for disaster recovery operations, with no mention of Bash, Linux shell, or cross-platform alternatives. The onboarding script and its usage are shown exclusively in PowerShell syntax, and there is no guidance for Linux/macOS users on how to perform equivalent steps. The script editing and execution instructions assume a Windows environment, creating friction for non-Windows users.
Recommendations
  • Provide Bash or shell script equivalents for onboarding and recovery operations, or clarify if the onboarding script is cross-platform.
  • Explicitly state platform requirements for the onboarding script (e.g., if it requires Windows/PowerShell, mention this early in the documentation).
  • If possible, offer Azure CLI-only workflows that do not depend on PowerShell.
  • Add guidance for Linux/macOS users on how to edit and run the onboarding script, including any prerequisites or limitations.
  • Mention any cross-platform compatibility of the onboarding script, or provide links to Linux/macOS-specific 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 →
Scanned: 2026-02-13 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 examples. There are no Linux/macOS-specific instructions or examples, and PowerShell is assumed as the default shell for CLI usage. This creates friction for Linux/macOS users who may not use PowerShell or .ps1 scripts.
Recommendations
  • Provide Azure CLI command examples in Bash syntax as well as PowerShell, using cross-platform conventions (e.g., az workload-orchestration ... in Bash).
  • Offer equivalent Bash shell scripts for bulk deployment and workflow deletion, or document how to use the .ps1 scripts on Linux/macOS (e.g., with PowerShell Core).
  • Clarify that Azure CLI commands can be run in any shell and indicate any shell-specific syntax differences.
  • Add explicit notes or sections for Linux/macOS users, including prerequisites for running PowerShell scripts (such as installing PowerShell Core), or alternative approaches.
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 →
Scanned: 2026-02-13 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 provides extensive PowerShell-based examples and scripts for enabling diagnostics, onboarding, and log collection, with no equivalent Bash or Linux shell examples. File paths in JSON templates and scripts are Windows-style (e.g., C:\, E:\), and the onboarding scripts are referenced as .ps1 (PowerShell), implying Windows as the default environment. There are no Linux/macOS-specific instructions, and the use of PowerShell and Windows paths is pervasive throughout the guide.
Recommendations
  • Add Bash or shell script equivalents for all PowerShell (.ps1) commands and onboarding steps.
  • Provide Linux/macOS file path examples in JSON templates (e.g., /home/user/schema.yaml) alongside Windows paths.
  • Explicitly state OS requirements for scripts, and offer cross-platform alternatives where possible.
  • Mention that Azure CLI commands can be run from Bash or PowerShell, and provide syntax for both.
  • Clarify if the onboarding scripts (.ps1) are required to be run on Windows, or provide cross-platform versions (e.g., Python, Bash).
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-13 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 is heavily biased toward Windows environments. All onboarding scripts and examples are provided exclusively in PowerShell, with no mention of Bash or Linux shell equivalents. The prerequisites recommend using 'winget', a Windows-only package manager, to install Azure CLI and kubectl. There are no instructions or examples for Linux/macOS users, nor are alternative tools or commands provided. This creates friction for non-Windows users attempting to follow the onboarding process.
Recommendations
  • Provide Bash or shell script equivalents for onboarding scripts, or clarify if PowerShell Core is required and supported cross-platform.
  • Include Linux/macOS installation instructions for Azure CLI and kubectl (e.g., using apt, yum, brew, or direct download).
  • Mention cross-platform compatibility of the scripts, or explicitly state if they are Windows-only.
  • Add examples showing how to run the scripts on Linux/macOS, or provide guidance for adapting them.
  • Consider providing Docker-based or containerized onboarding options for greater platform parity.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation exhibits Windows bias in several areas. The example for installing kubectl uses the Windows-specific 'winget' tool, with no Linux/macOS alternative provided. In the section on extracting ZIP files, the Bash example incorrectly uses the Windows-native 'Expand-Archive' command, which is not available on Linux/macOS. Throughout, examples and variable paths are shown using Windows-style paths (e.g., 'C:\path\to\archive.zip') and Windows tools are referenced first or exclusively. There is a lack of explicit Linux/macOS instructions for key setup steps, which may confuse or hinder non-Windows users.
Recommendations
  • Provide Linux/macOS alternatives for installing kubectl, such as 'curl' or 'apt/yum/brew' commands.
  • Correct the Bash example for extracting ZIP files to use 'unzip' or 'tar' for Linux/macOS, and clarify Windows vs. Linux/macOS instructions.
  • Use platform-neutral or platform-specific path examples (e.g., '/home/user/archive.zip' for Linux/macOS).
  • Ensure that all steps referencing Windows tools (like 'winget' or 'Expand-Archive') are accompanied by Linux/macOS equivalents.
  • Consider adding a table or tabs for Windows, Linux, and macOS where commands differ.
GitHub Create Pull Request
← Previous Page 45 of 94 Next →