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 826-850 of 2334 flagged pages
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-03-01 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page provides multiple methods for installing Arc agents at scale on VMware VMs, but shows notable Windows bias. The primary automation script is PowerShell-based, with instructions for running it in PowerShell and scheduling via Windows Task Scheduler. Windows tools and patterns (PowerShell, Task Scheduler) are mentioned exclusively, and Linux equivalents (such as Bash or cron) are not provided. Windows terminology and examples appear first and more frequently, while Linux-specific guidance is minimal and only in a single note about sudo configuration.
Recommendations
  • Provide a Bash or shell script equivalent for the automation 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.
  • Add Linux/macOS-specific examples for agent installation and automation, including how to set execution permissions and run scripts.
  • Ensure parity in prerequisites and troubleshooting for both Windows and Linux VMs.
  • Clarify whether the helper script is PowerShell-only or can be run in other environments.
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-01 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 instructions for running the script on Linux or macOS, nor is there mention of cross-platform compatibility for the script. Windows steps are presented first and in greater detail, while Linux users are left without guidance for script execution.
Recommendations
  • Add explicit instructions for running the deboarding script on Linux/macOS, including prerequisites (e.g., PowerShell Core, Azure CLI), script invocation, and any required permissions.
  • Clarify whether the deboarding script is cross-platform (PowerShell Core compatible) or Windows-only. If Windows-only, provide a Bash or Python alternative for Linux/macOS users.
  • Present Windows and Linux/macOS instructions in parallel or clearly indicate platform-specific steps.
  • Include troubleshooting tips for Linux/macOS environments, such as handling script execution permissions and Azure CLI authentication.
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-01 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 Bash example for extracting ZIP files uses the Windows-native Expand-Archive command and Windows file paths, which is not available on Linux/macOS. The recommended installation method for kubectl uses winget, a Windows-only package manager, with no Linux/macOS alternative provided. Throughout the page, file paths and examples default to Windows conventions. While Azure CLI and kubectl are cross-platform, the documentation does not consistently provide Linux/macOS-specific instructions or alternatives, especially for initial setup steps.
Recommendations
  • Provide Linux/macOS alternatives for extracting ZIP files (e.g., 'unzip archive.zip -d /path/to/workspace').
  • Offer Linux/macOS installation instructions for kubectl (e.g., using 'curl' or 'apt', 'brew', etc.), not just winget.
  • Use generic or platform-neutral file paths in examples, or show both Windows and Linux/macOS paths.
  • Ensure all critical steps have Linux/macOS equivalents, especially for setup and installation.
  • Consider adding explicit tabs or sections for Linux/macOS users where commands differ.
GitHub Create Pull Request
Azure Arc Perform disaster recovery operations ...mware-vsphere/recover-from-resource-bridge-deletion.md
Medium Priority View Details →
Scanned: 2026-03-01 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 references the onboarding script as a PowerShell script (.ps1), with no mention of Bash, Linux, or macOS equivalents. All command-line instructions and code snippets are Windows/PowerShell-centric, and there is no guidance for Linux/macOS users on how to perform the same operations. The script editing and execution steps assume a Windows environment, creating friction for non-Windows users.
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 requires PowerShell Core, which is available on Linux/macOS, or if it is Windows-only).
  • Add guidance for Linux/macOS users on how to edit and run the onboarding script, including prerequisites and installation instructions for PowerShell Core if needed.
  • Mention any limitations or alternative approaches for Linux/macOS users if the script or process is not fully supported.
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-01 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation consistently presents all CLI command examples and automation scripts using PowerShell syntax (e.g., `$rg`, `$subId`, `.ps1` scripts), and only references PowerShell scripts for bulk operations and workflow cleanup. There are no Bash or Linux/macOS shell equivalents, nor are there instructions for running these tasks on non-Windows platforms. This creates friction for Linux/macOS users, especially since Azure CLI is cross-platform.
Recommendations
  • Provide all Azure CLI command examples in both PowerShell and Bash syntax, or use syntax-agnostic variable notation.
  • Offer Bash (.sh) script equivalents for the referenced PowerShell scripts (bulk_deployment.ps1, workflow-delete.ps1), or clarify if the scripts are cross-platform.
  • Explicitly state if the scripts are Windows-only, or provide instructions for running them on Linux/macOS.
  • Add notes or tabs indicating how to perform the same tasks on Linux/macOS, including any required dependencies or differences.
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-01 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 a PowerShell (.ps1) script for resource cleanup, with all usage examples and instructions tailored to Windows/PowerShell environments. There are no Bash, shell, or cross-platform alternatives, nor any mention of how Linux or macOS users can perform the same cleanup.
Recommendations
  • Provide a Bash or cross-platform shell script equivalent to RGCleanScript.ps1, or document how Linux/macOS users can run the script (e.g., via PowerShell Core on Linux).
  • Include explicit instructions or examples for running the cleanup process on Linux/macOS, such as using pwsh (PowerShell Core) or Azure CLI commands if possible.
  • Clarify script requirements and compatibility (e.g., does it require Windows PowerShell, or is it compatible with PowerShell Core on all platforms?).
  • If only PowerShell is supported, add a note for Linux/macOS users on how to install and use PowerShell Core to run the script.
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-03-01 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 a notable Windows bias. All CLI/script examples are provided exclusively in PowerShell syntax, with no Bash or Linux shell equivalents. Paths in JSON templates use Windows-style (C:\, E:\) and the onboarding scripts are referenced as PowerShell (.ps1) only. There are no instructions or examples for Linux/macOS users, even though the Azure CLI and Kubernetes tools are cross-platform. This creates friction for non-Windows users, who must adapt commands and scripts themselves.
Recommendations
  • Provide Bash/Linux shell equivalents for all PowerShell CLI examples (e.g., az commands with Bash syntax and environment variables).
  • Use platform-neutral file paths in JSON templates, or provide examples for both Windows and Linux/macOS.
  • Document onboarding steps for Linux/macOS, including how to run scripts (e.g., using Bash or Python instead of PowerShell).
  • Clarify any platform requirements for scripts and tools, and link to cross-platform alternatives where available.
  • If PowerShell scripts are required, offer guidance for Linux PowerShell Core users, or provide Bash alternatives.
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-01 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 (WOGAMigration.ps1) for the migration process and instructs users to run it in PowerShell, with no mention of Linux/macOS-compatible alternatives or instructions. This creates friction for non-Windows users, as PowerShell is not natively available on Linux/macOS and the script may not be cross-platform.
Recommendations
  • Provide a Bash or Python script alternative for Linux/macOS users, or clarify if the PowerShell script is compatible with PowerShell Core on Linux/macOS.
  • Include explicit instructions for running the migration script on Linux/macOS, including any prerequisites (e.g., installing PowerShell Core).
  • Mention any limitations or required adaptations for non-Windows environments.
  • If the script is Windows-only, offer guidance for Linux/macOS users to perform the migration manually or request support.
GitHub Create Pull Request
Azure Arc Troubleshooting for Workload Orchestration ...es/azure-arc/workload-orchestration/troubleshooting.md
Medium Priority View Details →
Scanned: 2026-03-01 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 use PowerShell syntax and variables, even for cross-platform Azure CLI and Kubernetes tasks. There are no explicit Linux/bash equivalents for critical troubleshooting steps, except for the 'service groups' section, which provides both Bash and PowerShell tabs. Some commands (e.g., Docker, kubectl) are shown in PowerShell context, but these tools are cross-platform. This bias creates friction for Linux/macOS users, who must adapt PowerShell syntax and variable usage to their environments.
Recommendations
  • Provide Bash/Linux equivalents for all troubleshooting steps, especially for Azure CLI, Docker, and kubectl commands.
  • Use cross-platform variable syntax (e.g., $VAR for Bash, $var for PowerShell) or clarify variable usage for each platform.
  • Where possible, avoid PowerShell-specific constructs (e.g., ConvertTo-Json, Out-File) and offer alternatives for Bash/Linux (e.g., jq, echo, cat).
  • For file encoding instructions, specify cross-platform editors and commands.
  • Clearly indicate which steps are platform-specific and which are cross-platform.
GitHub Create Pull Request
Azure Arc Onboarding Scripts for Workload Orchestration ...azure-arc/workload-orchestration/onboarding-scripts.md
Medium Priority View Details →
Scanned: 2026-03-01 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, with all onboarding scripts and examples provided exclusively in PowerShell (.ps1) format. Prerequisites reference Windows-specific tools (winget), and there are no Bash, shell, or Linux/macOS equivalents or instructions. All command-line examples and script usage assume a Windows/PowerShell context, creating friction for Linux/macOS users.
Recommendations
  • Provide equivalent Bash or shell scripts for Linux/macOS users, or document how to run the onboarding process on those platforms.
  • Replace or supplement 'winget' installation instructions with cross-platform alternatives (e.g., apt, yum, brew, or direct download links).
  • Explicitly state if the onboarding scripts are Windows-only, or clarify cross-platform support if available.
  • Add Linux/macOS command-line examples alongside PowerShell examples.
  • Document any prerequisites or dependencies for non-Windows environments (e.g., PowerShell Core, Azure CLI installation on Linux/macOS).
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-28 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 there is a notable Windows bias: Windows tools (Admin Center, Graphical Installer) are mentioned explicitly, and PowerShell is referenced before Bash. Linux equivalents (such as SSH, Linux package managers, or Linux-specific deployment tools) are not mentioned or are less prominent. Windows deployment options are described in more detail, and Windows examples/tools appear first in several sections.
Recommendations
  • Add explicit Linux deployment examples and tools (e.g., SSH, Linux package managers, or Linux-specific scripts) alongside Windows options.
  • Mention Bash and PowerShell equally, and provide sample Bash commands/scripts for Linux users.
  • Include references to Linux graphical installers or management tools if available.
  • Ensure Linux deployment at scale (e.g., Ansible) is described with parity to Windows tools like Group Policy.
  • Where Windows tools are mentioned (Admin Center, Graphical Installer), add a note about Linux alternatives or clarify if none exist.
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-28 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation exclusively provides 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 Bash or cross-platform alternatives. The script and all usage instructions assume a Windows/PowerShell environment, which may exclude or confuse users on other platforms.
Recommendations
  • Provide a Bash or cross-platform shell script alternative (e.g., `RGCleanScript.sh`) for Linux/macOS users, or clarify if the script is compatible with PowerShell Core (pwsh) on all platforms.
  • Add explicit instructions for running the script on Linux/macOS, including any prerequisites (such as installing PowerShell Core or required modules).
  • If only PowerShell is supported, clearly state that the script requires PowerShell and provide guidance for installing PowerShell Core on non-Windows systems.
  • Consider including az CLI command examples for common clean-up tasks as an alternative for users who prefer not to use PowerShell scripts.
GitHub Create Pull Request
Azure Arc Back up controller database .../articles/azure-arc/data/backup-controller-database.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 command-line examples for connecting to the SQL Server instance using PowerShell syntax and references the use of sqlcmd, but does not offer equivalent Linux/macOS shell examples. The PowerShell examples are shown first and exclusively, which may create friction for Linux/macOS users, even though the underlying tools (kubectl, sqlcmd) are cross-platform.
Recommendations
  • Provide Linux/macOS shell (bash) examples alongside PowerShell, especially for commands using kubectl exec and sqlcmd.
  • Clarify that sqlcmd and kubectl are cross-platform and can be used from any OS, and specify any OS-specific requirements.
  • Show both PowerShell and bash syntax for connecting to the pod and running SQL commands.
  • Avoid using PowerShell-specific formatting (e.g., backticks, command continuation) unless necessary; use generic shell syntax where possible.
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-28 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is mostly Linux-focused, but it introduces Windows-centric tools (Invoke-AksEdgeNodeCommand) for Linux node configuration, without providing native Linux shell equivalents. The use of PowerShell-like commands for Linux tasks may confuse Linux/macOS users and limits their ability to follow instructions directly.
Recommendations
  • Provide native Linux shell (bash) command equivalents for sysctl configuration steps, e.g., 'sysctl fs.inotify.max_user_instances' and 'echo ... | sudo tee -a /etc/sysctl.conf && sudo sysctl -p'.
  • Clarify whether Invoke-AksEdgeNodeCommand is required or if standard Linux commands can be used directly on the node.
  • Add explicit instructions for Linux users to SSH into the node and run commands natively, rather than using Windows/PowerShell tools.
  • Ensure all steps can be completed using standard Linux tooling, and present Linux-native commands before any Windows/PowerShell alternatives.
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-28 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation lists several Windows-centric tools (SSMS, SQL Server Data Tools, SQL Server PowerShell, SQL Server Profiler) and highlights PowerShell scripting support as a manageability feature. While Azure CLI and Visual Studio Code are mentioned, Windows tools are listed first and more prominently. There are no Linux-specific tools or examples provided, and PowerShell is referenced without mention of Bash or Linux scripting alternatives.
Recommendations
  • Add examples or references for Linux/macOS users, such as Bash scripting or cross-platform tools.
  • Mention and provide guidance for using Azure Data Studio, which is cross-platform.
  • Clarify which tools are available on Linux/macOS and which are Windows-only.
  • Include parity tables or notes for tool support across operating systems.
  • Highlight Azure CLI usage with Linux/macOS examples where possible.
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-28 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation frequently presents Windows-centric examples and tools first (e.g., file paths like C:\Backupfiles\test.bak, use of SSMS, and screenshots/steps for Azure Storage Explorer on Windows), with no explicit Linux/macOS equivalents or guidance. Linux users are left to infer how to adapt the instructions, especially for backup file creation and local file path usage.
Recommendations
  • Provide parallel examples for Linux/macOS users, such as using /home/username/Backupfiles/test.bak as the backup path.
  • Mention cross-platform alternatives to SSMS, such as Azure Data Studio, and clarify that Visual Studio Code is available on all platforms.
  • For Azure Storage Explorer, clarify that it is cross-platform and provide links or notes for Linux/macOS installation and usage.
  • When showing commands with file paths, show both Windows and Linux/macOS formats side by side.
  • Explicitly state that all steps can be performed from Linux/macOS unless a step is Windows-only, and provide any required adaptations.
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-02-28 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides release notes for both Windows and Linux versions of the Azure Connected Machine agent, with clear parity in most feature tables. However, Windows-specific tools (Command Prompt, PowerShell, MSI installer) are referenced exclusively in troubleshooting and known issues, and Windows command examples are provided without Linux equivalents. Windows download links and version numbers are consistently listed before Linux. This creates friction for Linux users, especially in troubleshooting scenarios.
Recommendations
  • For troubleshooting and known issues, provide equivalent Linux commands and instructions (e.g., how to modify agentconfig.json permissions on Linux, using chmod/chown).
  • Where Windows tools (PowerShell, Command Prompt, MSI installer) are mentioned, add Linux alternatives (bash, shell scripts, RPM/DEB installers) and examples.
  • Alternate the order of Windows and Linux download links and version numbers, or present them side-by-side.
  • Explicitly state when an issue or fix is Windows-only or Linux-only to avoid confusion.
  • Ensure that all critical operational instructions are available for both platforms.
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-28 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 Linux and Windows. However, several onboarding methods are Windows-specific (e.g., Windows Admin Center, Group Policy, Configuration Manager), and PowerShell is highlighted as a cross-platform tool but is more commonly associated with Windows. Windows-specific tools and methods are listed separately and in greater detail, while Linux-specific automation tools (other than Ansible) are not mentioned. The order of examples and methods tends to prioritize Windows tools and workflows.
Recommendations
  • Add Linux/macOS-specific onboarding examples, such as using Bash scripts or native Linux automation tools (e.g., shell scripts, cron jobs, Puppet, Chef).
  • Clarify PowerShell's cross-platform support and provide equivalent Bash or shell script examples for Linux users.
  • Consider balancing the order of methods so Linux and Windows approaches are presented equally.
  • Include links or references to Linux-specific documentation where available.
  • Explicitly state when a method is Windows-only and suggest Linux alternatives where possible.
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-28 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. PowerShell is a Windows-centric tool, though it is available cross-platform. Additionally, PowerShell deployment commands are presented first and exclusively, which may create friction for Linux/macOS users who prefer Azure CLI or Bash. The template examples themselves are balanced, but the operational guidance is Windows-first.
Recommendations
  • Add Azure CLI deployment examples alongside PowerShell, e.g., az deployment group create.
  • Explicitly mention that PowerShell is available cross-platform, but provide Bash/CLI alternatives for Linux/macOS users.
  • Consider showing Azure CLI examples first or in parallel with PowerShell to avoid Windows-first impression.
  • Clarify that the templates can be deployed from any OS, not just Windows.
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-28 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation claims support for both Windows and Linux Arc-enabled servers, but the majority of concrete examples (especially in PowerShell and REST API sections) are Windows-centric. PowerShell examples use Windows-style paths and scripts, and REST API examples exclusively show Windows firewall configuration (New-NetFirewallRule, .ps1 scripts). There are no Linux-specific script examples (e.g., bash, shell scripts, or Linux firewall commands like iptables or ufw). Azure CLI examples use PowerShell-style commands (Write-Host), and there are no Linux shell script examples. The documentation also references Windows tools (e.g., New-AzStorageBlobSASToken) without mentioning Linux alternatives. Linux is only mentioned in passing, and Linux-specific scripting patterns are not demonstrated.
Recommendations
  • Add Linux-specific script examples in all sections (PowerShell, Azure CLI, REST API), such as running bash scripts, using Linux shell commands (e.g., echo, id, iptables, ufw), and referencing .sh files.
  • In the REST API section, provide a Linux scenario (e.g., configuring a firewall rule with iptables or ufw) alongside the Windows example.
  • When showing how to upload or reference scripts, include Linux file paths and script types (.sh) as well as Windows (.ps1).
  • For Azure CLI examples, use Linux-native commands (e.g., echo, id) and show both Windows and Linux script invocations.
  • Reference cross-platform tools or clarify that New-AzStorageBlobSASToken is available on all platforms, or provide az CLI equivalents.
  • Explicitly call out any differences in script parameter handling between Windows and Linux, and provide examples for both.
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-28 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 it clarified whether recovery is possible from non-Windows systems. The section is titled 'Recover Arc resource bridge from a Windows machine', and no alternative is offered.
Recommendations
  • Clarify whether recovery is possible from Linux/macOS, and if not, explicitly state that the process is Windows-only.
  • If feasible, provide equivalent recovery instructions and scripts for Linux/macOS users (e.g., Bash or Python scripts).
  • Add a note about platform requirements and limitations to set user expectations.
  • If the script is Windows-only due to dependencies, explain the technical reasons for this.
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-28 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation page for disaster recovery operations of the Azure Arc resource bridge VM provides only PowerShell script examples and references, with no mention of Linux/macOS shell equivalents or cross-platform onboarding script usage. The onboarding and recovery steps are described exclusively using PowerShell syntax, and there is no guidance for users on Linux or macOS systems. This creates friction for non-Windows users attempting to perform the same operations.
Recommendations
  • Provide onboarding script usage examples for Bash or other Linux/macOS shells if the script supports cross-platform execution.
  • Clarify whether the onboarding script is Windows-only or cross-platform; if Windows-only, state this explicitly to set expectations.
  • If possible, offer instructions or alternatives for Linux/macOS users, such as using Azure CLI or a platform-neutral method.
  • Include notes about required environments and dependencies for running the onboarding script.
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-28 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation consistently uses PowerShell syntax for all CLI examples and references only PowerShell scripts (e.g., bulk_deployment.ps1, workflow-delete.ps1) for automation, without providing equivalent Bash or cross-platform alternatives. There are no Linux/macOS-specific instructions or examples, and the use of .ps1 scripts assumes a Windows or PowerShell Core environment.
Recommendations
  • Provide CLI command examples in both PowerShell and Bash syntax, or use a neutral shell format.
  • Offer equivalent Bash scripts (e.g., bulk_deployment.sh) for Linux/macOS users, or document how to run the .ps1 scripts with PowerShell Core on those platforms.
  • Explicitly state that the .ps1 scripts can be run with PowerShell Core on Linux/macOS, and provide installation guidance if needed.
  • Where possible, avoid using shell-specific features in CLI examples, or clarify any platform dependencies.
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-28 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page exhibits notable Windows bias in its automation section. The primary script for batch Arc agent installation is a PowerShell script, with instructions focused on Windows environments (e.g., PowerShell terminal, Set-ExecutionPolicy, Windows Task Scheduler for cron jobs). Windows tools and patterns are mentioned first and exclusively in several sections, while Linux equivalents (such as bash scripting or cron) are missing. Although Linux is referenced in prerequisites and out-of-band methods, the main scalable automation example is Windows-centric.
Recommendations
  • Provide a bash or shell script equivalent for batch Arc agent installation, with instructions for Linux/macOS users.
  • Include examples for scheduling the script using Linux cron jobs, not just Windows Task Scheduler.
  • Offer guidance for running the script in cross-platform environments (e.g., Azure Cloud Shell, WSL, or native Linux/macOS terminals).
  • Ensure out-of-band methods include Linux-focused automation examples (e.g., Ansible, shell scripts) with equal prominence.
  • Where possible, show both Windows and Linux command examples side-by-side.
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-28 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Windows and Linux instructions for uninstalling the Azure Connected Machine agent, but the deboarding script section is heavily PowerShell-centric and only provides Windows/PowerShell instructions for running the script. Windows instructions and notes are presented first and in greater detail, while Linux/macOS users are not given equivalent guidance for running the deboarding script or troubleshooting.
Recommendations
  • Add explicit instructions for running the deboarding script on Linux/macOS, including prerequisites (e.g., PowerShell Core, Azure CLI), command syntax, and troubleshooting notes.
  • Mention PowerShell Core as a cross-platform option and clarify if the script can be run on Linux/macOS, or provide an alternative Bash script if not.
  • Present Windows and Linux instructions in parallel sections, or clarify platform limitations up front.
  • Add troubleshooting tips for Linux/macOS users, similar to the PowerShell ISE note for Windows.
GitHub Create Pull Request
← Previous Page 34 of 94 Next →