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 876-900 of 2334 flagged pages
Azure Arc Clean-Up Script for Workload Orchestration ...es/azure-arc/workload-orchestration/clean-up-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 exclusively provides a PowerShell script (RGCleanScript.ps1) and only PowerShell command examples for running the clean-up process. There are no Bash, shell, or cross-platform script alternatives, nor is there guidance for Linux/macOS users on how to perform the same task. The script and instructions are Windows-centric, creating friction for non-Windows users.
Recommendations
  • Provide a Bash or shell script equivalent for Linux/macOS users, or document how to run the PowerShell script using PowerShell Core (pwsh) on Linux/macOS.
  • Include command examples for Linux/macOS environments, such as using pwsh or Bash.
  • Clarify script compatibility (e.g., whether RGCleanScript.ps1 works with PowerShell Core on Linux/macOS, or if it is Windows-only).
  • If the script is Windows-only, offer guidance or alternatives for Linux/macOS users to achieve the same clean-up tasks (e.g., using Azure CLI commands).
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-27 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation exhibits Windows bias in several areas. The kubectl installation command uses 'winget', a Windows-only tool, with no Linux/macOS alternative provided. File extraction instructions use 'Expand-Archive', which is a PowerShell/Windows command, even in the Bash tab, and do not mention cross-platform alternatives like 'unzip'. Windows paths (e.g., 'C:\path\to\archive.zip') are used in examples, and Linux/macOS paths are not shown. These biases may cause friction for Linux/macOS users, especially during initial setup.
Recommendations
  • Provide Linux/macOS installation instructions for kubectl (e.g., using 'curl' or package managers like 'apt', 'brew').
  • In Bash examples, use cross-platform tools like 'unzip' for extracting ZIP files, and show Linux/macOS file paths (e.g., '/home/user/archive.zip').
  • Add explicit Linux/macOS alternatives wherever Windows-specific tools or patterns are mentioned.
  • Ensure that Bash tabs do not use PowerShell/Windows-only commands.
  • Consider including a section or table summarizing platform-specific steps for common tasks.
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-27 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 biased toward Windows environments. All onboarding scripts and usage examples are provided exclusively for PowerShell, with no mention of Bash, Linux, or macOS equivalents. Windows-specific tools like 'winget' are referenced for installing dependencies, and there are no instructions or guidance for Linux/macOS users. This creates significant friction for non-Windows users attempting to follow the onboarding process.
Recommendations
  • Provide Bash or shell script equivalents for the PowerShell onboarding scripts, or clarify if only PowerShell is supported.
  • Include instructions for installing Azure CLI and kubectl on Linux/macOS (e.g., using apt, yum, brew, or official install scripts) alongside the 'winget' command.
  • Explicitly state platform requirements and limitations at the top of the page if the scripts are only supported on Windows.
  • If possible, offer cross-platform onboarding scripts or containerized solutions.
  • Add notes or sections for Linux/macOS users, even if only to clarify current limitations and suggest alternatives.
GitHub Create Pull Request
Azure Arc Troubleshooting for Workload Orchestration ...es/azure-arc/workload-orchestration/troubleshooting.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 troubleshooting guide for workload orchestration in Azure Arc demonstrates notable Windows bias. Most command-line examples are provided exclusively in PowerShell syntax, even for tasks that are cross-platform (e.g., az CLI, kubectl, docker). Linux/bash equivalents are missing for critical troubleshooting steps, and PowerShell is used for scripting and manipulating outputs (e.g., Base64 encoding, JSON file creation). Bash examples are only present in the 'Troubleshoot service groups' section, where both Bash and PowerShell are shown, but elsewhere PowerShell is used exclusively and shown first.
Recommendations
  • Provide bash/Linux equivalents for all az CLI, kubectl, and docker commands, especially in sections where PowerShell is used for scripting (e.g., Base64 encoding, JSON file creation).
  • Show bash/Linux examples before or alongside PowerShell examples for cross-platform tools.
  • Avoid using PowerShell-specific syntax for az CLI, kubectl, and docker commands; use generic syntax where possible.
  • Add notes clarifying when a command is Windows-specific, and offer Linux/macOS alternatives.
  • For scripting tasks (e.g., manipulating connection strings, creating JSON files), provide bash/Linux shell alternatives (e.g., using jq, base64, echo, etc.).
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-26 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation provides authentication options for both Windows and Linux, but the 'Interactive browser login' is described as Windows-only and presented first. Windows certificate store usage is detailed, while Linux equivalents are not mentioned. The access token example references a Windows PowerShell cmdlet ('Get-AzAccessToken') without Linux alternatives. However, the overall command syntax and most examples are cross-platform.
Recommendations
  • Present authentication options in a platform-neutral order or clarify platform defaults for each.
  • For certificate-based authentication, mention Linux certificate storage options (e.g., file paths, permissions) and provide Linux-specific guidance.
  • For access token acquisition, include Linux/macOS alternatives (such as using Azure CLI: 'az account get-access-token') alongside PowerShell examples.
  • Explicitly state which authentication methods are available on Linux/macOS and provide parity in examples.
  • Where Windows-specific tools or stores are mentioned, add equivalent Linux/macOS instructions or links.
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-26 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. No Linux/macOS shell or cross-platform alternatives are mentioned, nor is there guidance for users who do not have access to PowerShell (e.g., Linux users). The page assumes PowerShell availability, which is a Windows-centric tool.
Recommendations
  • Provide a Bash or cross-platform script for migration, or clarify if PowerShell Core (pwsh) can be used on Linux/macOS.
  • Explicitly state PowerShell requirements and offer installation instructions for Linux/macOS if PowerShell Core is supported.
  • Add Linux/macOS usage examples, including how to run the script in PowerShell Core or alternative migration methods.
  • Mention any limitations or workarounds for non-Windows users.
GitHub Create Pull Request
Azure Arc Customer intent: As a system administrator, I want to configure a single-node Kubernetes cluster with adequate resources and storage provisions, so that I can deploy and manage applications effectively using Azure IoT Operations and Azure Container Storage. ...tainer-storage/includes/single-node-edge-essentials.md
Medium Priority View Details →
Scanned: 2026-02-26 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is focused on configuring AKS Edge Essentials for Linux, but uses PowerShell cmdlets (Invoke-AksEdgeNodeCommand) to interact with Linux nodes, rather than native Linux shell commands. There are no direct Linux shell examples for checking or setting sysctl parameters, and the text editor recommendation (Notepad) is Windows-centric.
Recommendations
  • Provide native Linux shell commands for checking and setting sysctl parameters (e.g., 'sysctl fs.inotify.max_user_instances', 'echo ... | sudo tee -a /etc/sysctl.conf && sudo sysctl -p').
  • Recommend Linux text editors (e.g., nano, vim, gedit) instead of Notepad.
  • Clarify when PowerShell cmdlets are required, and offer Linux-native alternatives where possible.
  • Ensure all critical steps can be completed using Linux tools without requiring Windows/PowerShell.
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-26 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides command 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. PowerShell is used for kubectl exec commands, and Windows-style command prompts are shown first. There is no explicit mention of Linux/macOS alternatives or parity, which may create friction for non-Windows users.
Recommendations
  • Provide bash/zsh shell examples alongside PowerShell for kubectl exec and sqlcmd commands.
  • Clarify that sqlcmd is cross-platform and provide installation instructions for Linux/macOS if needed.
  • Use generic shell prompt (e.g., $) or indicate both Windows and Linux/macOS command syntax where relevant.
  • Explicitly state that the steps are applicable to both Windows and Linux/macOS environments, unless there are OS-specific differences.
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-26 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides step-by-step instructions for migrating a SQL Server database to Azure Arc-enabled SQL Managed Instance, but several examples and instructions assume a Windows environment. For example, backup file paths and kubectl cp examples use Windows-style paths (e.g., C:\Backupfiles\test.bak) without providing Linux/macOS equivalents. Tools like SSMS are mentioned without Linux alternatives, and Visual Studio Code is referenced, which is cross-platform, but no explicit Linux/macOS instructions or screenshots are provided. This may cause friction for users on Linux or macOS.
Recommendations
  • Provide equivalent examples using Linux/macOS file paths (e.g., /home/user/backup/test.bak) alongside Windows paths.
  • Mention and provide examples using cross-platform or Linux-native tools for backup (e.g., sqlcmd, Azure Data Studio) where possible.
  • Clarify that Visual Studio Code is cross-platform and provide any Linux/macOS-specific steps if needed.
  • When referencing SSMS (which is Windows-only), suggest Azure Data Studio as an alternative for Linux/macOS users.
  • For kubectl cp commands, show both Windows and Linux/macOS source path examples.
GitHub Create Pull Request
Azure Arc Features and Capabilities of SQL Managed Instance enabled by Azure Arc ...n/articles/azure-arc/data/managed-instance-features.md
Medium Priority View Details →
Scanned: 2026-02-26 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools
Summary
The documentation lists several Windows-centric tools (SSMS, SQL Server Data Tools, SQL Server Profiler, SQL Server PowerShell) and explicitly mentions PowerShell scripting support as a manageability feature. While Azure PowerShell is marked as 'No', SQL Server PowerShell is marked as 'Yes', and PowerShell scripting is highlighted in the manageability section. There are no Linux/macOS-specific tools or scripting examples mentioned, nor is there guidance for Linux users on equivalent workflows.
Recommendations
  • Add examples or mention of cross-platform tools such as Azure Data Studio, which runs on Windows, Linux, and macOS.
  • Clarify that SQL Server PowerShell is primarily a Windows tool and provide alternatives for Linux/macOS users, such as Bash scripting or using sqlcmd.
  • Include references to command-line tools like sqlcmd and Azure CLI, which are cross-platform, and provide sample usage.
  • Explicitly state which features/tools are Windows-only and suggest Linux/macOS alternatives where possible.
  • Consider adding a section or table column indicating platform compatibility for each tool.
GitHub Create Pull Request
Azure Arc Rotate user-provided TLS certificate in indirectly connected SQL Managed Instance enabled by Azure Arc ...articles/azure-arc/data/rotate-user-tls-certificate.md
Medium Priority View Details →
Scanned: 2026-02-26 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation provides both Linux and Windows instructions for base64 encoding, but the Windows section is more detailed and appears after the Linux example. The Linux example uses the 'base64' command, while Windows users are directed to use 'certutil' and 'findstr'. However, the Linux example is brief and lacks guidance for removing headers, which is covered for Windows. The rest of the documentation is platform-neutral, focusing on Azure CLI, kubectl, and OpenSSL, which are cross-platform tools.
Recommendations
  • Add instructions for removing headers from base64 output on Linux/macOS, such as using 'grep' or 'sed'.
  • Clarify that OpenSSL, Azure CLI, and kubectl commands are cross-platform and provide any necessary notes for Windows users (e.g., file path syntax differences).
  • Consider providing Linux/macOS and Windows examples side-by-side for base64 encoding and header removal to ensure parity.
  • Explicitly mention that the steps are applicable to both Linux and Windows unless otherwise noted.
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-26 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, Configuration Manager, MSI installer, Msiexec) 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 update infrastructure is described in depth, while Linux package manager instructions are concise. Overall, Linux users can complete all tasks, but Windows-centric examples and tooling are more prominent.
Recommendations
  • Provide equivalent bash scripts for resource cleanup and automation tasks, not just PowerShell.
  • Balance the level of detail between Windows and Linux sections, especially for upgrade/uninstall procedures.
  • Where possible, mention Linux tools (e.g., cron, systemd, Ansible) for automation alongside Windows tools (Group Policy, WSUS).
  • Consider presenting Linux and Windows instructions in parallel or alternating order, rather than Windows-first.
  • Add troubleshooting tips for Linux environments, similar to those for Windows (e.g., log locations, service management).
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-26 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides troubleshooting guidance for Azure Arc resource bridge, which is a cross-platform solution. However, there are several instances of Windows bias: PowerShell is used for network troubleshooting examples, Windows paths are referenced in error messages, and Windows tools (such as Remote PowerShell and RDP) are mentioned. Linux-specific troubleshooting commands and examples are largely absent, and Windows/PowerShell instructions are often given before or instead of Linux equivalents. Some CLI commands reference Windows paths, and Linux troubleshooting is only briefly mentioned (e.g., glibc version error).
Recommendations
  • Provide Linux/macOS equivalents for all PowerShell and Windows command examples (e.g., use curl, wget, or openssl for network troubleshooting).
  • Include Linux/macOS-specific troubleshooting steps for common errors, such as SSH folder access, DNS resolution, and proxy configuration.
  • When referencing file paths or error messages, clarify if they are Windows-specific or provide Linux/macOS equivalents.
  • Ensure that CLI instructions and examples are platform-neutral or include both Windows and Linux/macOS variants.
  • Add troubleshooting guidance for Linux-specific issues, such as permission errors, file system differences, and environment variable configuration.
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-26 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, without showing Azure CLI or Bash equivalents. All deployment steps and examples use PowerShell syntax, which is native to Windows and less familiar to Linux/macOS users. While ARM templates are provided for both Linux and Windows extensions, the command-line instructions are Windows-centric, and PowerShell is presented as the primary (and only) method for template deployment.
Recommendations
  • Add Azure CLI examples for deploying ARM templates, such as 'az deployment group create' commands, alongside PowerShell examples.
  • Explicitly mention that Azure CLI can be used from Linux/macOS and provide equivalent CLI syntax for each deployment scenario.
  • Consider showing Bash script snippets for Linux users, or at least link to Azure CLI documentation for ARM template deployment.
  • If PowerShell is required (e.g., for certain advanced scenarios), clarify this and provide guidance for installing PowerShell Core on Linux/macOS.
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-26 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 Windows tools (such as New-AzStorageBlobSASToken and New-NetFirewallRule) throughout, with Windows-centric scripting and terminology. While the Run command feature supports both Windows and Linux, most examples (especially in PowerShell and REST API sections) are Windows-focused, and Linux-specific guidance is minimal or absent. REST API examples exclusively target Windows scenarios (firewall rule creation via New-NetFirewallRule), and PowerShell examples use Windows paths and scripts. Azure CLI examples use PowerShell syntax (Write-Host), which is not appropriate for Linux shell scripts. Linux-specific scripting, parameters, and REST API scenarios are missing.
Recommendations
  • Add Linux-specific examples for PowerShell, Azure CLI, and REST API sections, such as running bash scripts, configuring iptables/firewalld, and using Linux file paths.
  • In PowerShell examples, clarify how to run scripts on Linux Arc-enabled servers (e.g., using .sh files, bash commands, and relevant parameters).
  • For Azure CLI, provide both Windows (PowerShell) and Linux (bash) script examples, and avoid using Write-Host in CLI examples intended for Linux.
  • In REST API section, include Linux scenarios (e.g., running bash scripts to configure firewall rules with iptables or ufw) alongside Windows examples.
  • Ensure documentation consistently mentions Linux support and provides parity in guidance for both OS types.
  • Where referencing tools like New-AzStorageBlobSASToken, clarify alternatives or usage for Linux users.
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-26 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 and referencing a Windows-specific script. There are no Linux/macOS equivalents, examples, or guidance, and the section is titled 'Recover Arc resource bridge from a Windows machine,' implying Windows is the only supported platform for this operation.
Recommendations
  • Provide equivalent recovery instructions and scripts for Linux/macOS environments, using Bash or Python.
  • Clarify if recovery is only supported from Windows, and if so, explain why and mention any possible workarounds for Linux/macOS users.
  • If cross-platform support is possible, add Linux/macOS-specific prerequisites, script examples, and troubleshooting steps.
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-26 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page provides multiple methods for installing Arc agents at scale for VMware VMs, but there is a notable Windows bias. The 'Auto Arc-enablement script' section exclusively uses PowerShell and references Windows Task Scheduler for automation, with no Linux shell or cron examples. Windows tools and patterns (PowerShell, Task Scheduler) are mentioned before Linux equivalents, and Linux-specific guidance is limited to a brief sudo configuration note. While Ansible playbooks are mentioned as an out-of-band method, no Linux-centric automation examples or scripts are provided.
Recommendations
  • Provide equivalent Bash or shell script examples for Linux users, especially for the automation script.
  • Include instructions for running the automation script as a cron job on Linux, not just Windows Task Scheduler.
  • Offer guidance for using Linux-native tools (e.g., systemd timers, cron) for scheduled tasks.
  • Ensure parity in example commands and scripts for both Windows and Linux environments.
  • Expand Linux-specific prerequisites and troubleshooting sections.
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-26 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 PowerShell examples and references a .ps1 onboarding script, with no mention of Bash, Linux shell, or cross-platform alternatives. All scripting and command-line instructions are Windows-centric, and there are no Linux/macOS equivalents or guidance for non-Windows environments. This creates friction for Linux/macOS users attempting disaster recovery operations.
Recommendations
  • Provide equivalent Bash or shell script examples for Linux/macOS users, if supported.
  • Clarify whether the onboarding script can be run on Linux/macOS (e.g., with PowerShell Core), and provide instructions for doing so.
  • Mention any prerequisites or limitations for Linux/macOS users, including supported platforms for the onboarding script.
  • If the onboarding script is Windows-only, explicitly state this and suggest alternatives or workarounds for Linux/macOS users.
GitHub Create Pull Request
Azure Arc Remove your VMware vCenter environment from Azure Arc ...e-arc/vmware-vsphere/remove-vcenter-from-arc-vmware.md
Medium Priority View Details →
Scanned: 2026-02-26 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides a PowerShell-based deboarding script for removing VMware vCenter from Azure Arc, with detailed instructions for Windows users (PowerShell). There are no equivalent Linux/macOS instructions for running the script, and Windows-specific guidance (e.g., Set-ExecutionPolicy) is given before any mention of Linux alternatives. Manual removal steps are platform-neutral, but the scripted approach is Windows-centric.
Recommendations
  • Provide instructions for running the deboarding script on Linux/macOS, including prerequisites (e.g., PowerShell Core, Azure CLI) and any required permission settings.
  • Mention PowerShell Core as a cross-platform option and clarify if the script is compatible with it.
  • If the script is Windows-only, explicitly state this and offer a Linux/macOS alternative or manual steps.
  • Consider providing Bash or shell script alternatives for Linux users, or document how to use the manual removal steps as a fallback.
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-26 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 Linux/macOS shell or cross-platform script alternatives, and all usage examples are PowerShell-centric. The script is referenced as a .ps1 file, which is typically not natively supported on Linux/macOS without additional setup (e.g., installing PowerShell Core). No Bash or Azure CLI equivalents are mentioned.
Recommendations
  • Provide instructions for running the script using PowerShell Core on Linux/macOS, including installation guidance if needed.
  • Offer a Bash or Azure CLI equivalent script for Linux/macOS users, or clarify if the PowerShell script is cross-platform.
  • Explicitly state platform requirements and limitations for the script.
  • Add Linux/macOS usage examples, or note if the script is intended for Windows environments only.
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-26 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation consistently provides Azure CLI command examples in PowerShell syntax and references PowerShell scripts (.ps1) for automation. There are no Bash or Linux/macOS shell examples, nor are Linux-friendly scripts or instructions mentioned. The use of PowerShell and .ps1 files is presented as the default, with no Linux alternatives or parity.
Recommendations
  • Provide Azure CLI command examples in Bash syntax alongside PowerShell, or clarify that the CLI commands work cross-platform.
  • Offer equivalent Bash shell scripts (.sh) for bulk deployment and workflow deletion, or document how Linux/macOS users can perform the same tasks.
  • Explicitly state that the Azure CLI commands are cross-platform and can be run in any shell, not just PowerShell.
  • Add notes or sections for Linux/macOS users, including any required adaptations for file paths, script execution, or prerequisites.
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-26 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, including use of backticks for line continuation and explicit PowerShell script (.ps1) usage. File paths in JSON templates and scripts are Windows-style (e.g., C:\Users\...), and references to tools/scripts are exclusively PowerShell-based. There are no Bash, Linux, or macOS equivalents or guidance for users on non-Windows platforms, despite the topic being cross-platform (Azure Arc-enabled Kubernetes clusters can run on Linux). This bias may create friction for Linux/macOS users attempting to follow the instructions.
Recommendations
  • Provide Bash/zsh shell equivalents for all CLI/script examples, using standard Linux/macOS conventions (e.g., line continuation with \ or newlines, no backticks).
  • Include Linux-style file paths in JSON templates and scripts (e.g., /home/user/...).
  • Clarify whether the infra_onboarding.ps1 script is cross-platform (e.g., can it be run with PowerShell Core on Linux/macOS?), and provide guidance for Linux/macOS users if not.
  • Add explicit notes or sections for Linux/macOS users, including any prerequisites or alternative steps.
  • Where possible, use platform-neutral Azure CLI commands and avoid PowerShell-specific syntax.
  • Consider providing downloadable shell scripts (.sh) for Linux/macOS users.
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-26 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-specific Expand-Archive command and Windows file paths, which are not available on Linux/macOS. The recommended installation method for kubectl uses winget, a Windows-only package manager, with no Linux/macOS alternatives provided. Throughout, file paths and command examples often default to Windows conventions, and Linux-native tools (such as unzip or tar) are not mentioned. While Azure CLI and kubectl are cross-platform, the documentation does not provide Linux/macOS-specific instructions for critical setup steps.
Recommendations
  • Provide Linux/macOS equivalents for ZIP extraction, such as 'unzip' or 'tar' commands, and use POSIX-style file paths in Bash examples.
  • Include kubectl installation instructions for Linux/macOS (e.g., using 'curl', 'apt', 'brew', or 'snap') alongside winget.
  • Ensure Bash examples are platform-agnostic or offer separate tabs for Linux/macOS and Windows.
  • Review file path conventions in Bash examples to avoid Windows-only syntax.
  • Add explicit notes or sections for Linux/macOS users where Windows-specific tools are referenced.
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-26 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 biased towards Windows and PowerShell. All onboarding scripts and examples are provided only for PowerShell (.ps1 files), and users are instructed to use Windows-specific tools like 'winget'. There are no Bash, shell, or Linux/macOS equivalents or instructions, and no mention of how to run the scripts on non-Windows platforms. This creates friction for Linux/macOS users who may wish to automate onboarding for workload orchestration in Azure Arc.
Recommendations
  • Provide equivalent Bash or shell scripts for Linux/macOS users, or document how to run the PowerShell scripts cross-platform (e.g., with PowerShell Core).
  • Replace or supplement 'winget' installation instructions with cross-platform alternatives (e.g., 'apt', 'brew', or direct download links).
  • Explicitly state platform requirements for the scripts, and if Windows is required, clarify this early in the documentation.
  • Add notes or sections for Linux/macOS users, including any prerequisites, script modifications, or alternative onboarding steps.
  • If PowerShell Core is supported, provide instructions for installing and running the scripts on Linux/macOS.
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-26 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides CLI examples primarily using PowerShell syntax (with backticks for line continuation), especially in the May 2025 release section. Bash examples are used elsewhere, but PowerShell is shown first and exclusively in some cases. There are no Linux-specific tools or patterns mentioned, and the Azure CLI is inherently cross-platform, but the example bias may create friction for Linux/macOS users.
Recommendations
  • Provide both Bash and PowerShell examples for CLI commands, or default to Bash syntax for cross-platform parity.
  • Clarify that Azure CLI commands work identically on Linux/macOS and Windows, and note any OS-specific differences if present.
  • Avoid using Windows-specific line continuation (backticks) in CLI examples unless the section is Windows-only.
  • Where possible, add Linux/macOS-specific notes or troubleshooting tips.
GitHub Create Pull Request
← Previous Page 36 of 94 Next →