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 926-950 of 2334 flagged pages
Azure Arc Troubleshoot Azure Arc resource bridge issues ...re-arc/resource-bridge/troubleshoot-resource-bridge.md
Medium Priority View Details →
Scanned: 2026-02-23 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 issues and is intended for cross-platform environments. However, there are several instances where Windows/PowerShell tools and patterns are mentioned first or exclusively, and Linux equivalents are missing or less emphasized. For example, PowerShell is referenced for troubleshooting HTTP2 errors, and Windows-centric terminology (e.g., 'Remote PowerShell', 'RDP', 'time.windows.com') appears without Linux alternatives. Some CLI commands and troubleshooting steps are described generically, but when OS-specific instructions are given, Windows is prioritized or Linux is omitted.
Recommendations
  • Provide Linux/macOS equivalents for PowerShell commands (e.g., use curl or wget for HTTP2 troubleshooting).
  • When referencing folder permissions or SSH access, include Linux/macOS file path and permission examples alongside Windows.
  • Mention Linux/macOS tools (e.g., terminal, SSH, nslookup, dig) wherever Windows tools (PowerShell, RDP) are discussed.
  • Clarify that Azure CLI commands work equally on Linux/macOS and Windows, and provide OS-specific install/downgrade instructions.
  • Replace or supplement references to 'time.windows.com' with cross-platform NTP sources.
  • Ensure troubleshooting steps for network, DNS, and proxy issues include Linux/macOS command examples and guidance.
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-23 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides ARM template examples for both Linux and Windows Arc-enabled servers, ensuring parity in template content. However, all deployment commands and walkthroughs exclusively use Azure PowerShell, with no Azure CLI or Bash examples. Additionally, PowerShell deployment commands are presented first and solely, which may create friction for Linux/macOS users who prefer CLI or Bash. The documentation does not mention or show Linux-native tools or deployment patterns, and file path examples use Windows-style paths (e.g., 'D:\Azure\Templates\...') in command samples.
Recommendations
  • Add Azure CLI deployment command examples alongside PowerShell, especially for template deployments.
  • Show Bash or shell scripting alternatives for Linux/macOS users.
  • Include Linux-style file path examples (e.g., '/home/user/Azure/Templates/...') in command samples.
  • Explicitly state that both PowerShell and CLI are supported, and link to relevant CLI documentation.
  • Consider presenting CLI and PowerShell examples side-by-side or alternating their order.
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-23 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 tools (such as PowerShell, Group Policy, Microsoft Update, WSUS, Configuration Manager) are presented in greater detail and often appear before Linux equivalents. The cleanup script for removing stale resources is only provided in PowerShell, with no Linux/bash alternative. Windows-specific tools and patterns (e.g., Control Panel, Registry Editor, Msiexec) are described extensively, while Linux instructions are more concise and lack advanced scripting or automation examples.
Recommendations
  • Provide equivalent bash or shell scripts for Linux users, especially for tasks like cleanup of stale Arc resources.
  • Ensure Linux examples are given equal prominence and detail as Windows examples, including automation and advanced usage.
  • Where possible, mention Linux tools (e.g., cron, systemd, package managers) alongside Windows tools (e.g., Group Policy, WSUS).
  • Consider adding troubleshooting and automation guidance for Linux environments, similar to the PowerShell scripts provided for Windows.
  • When listing upgrade methods or tools, alternate the order or provide a neutral listing (e.g., alphabetical, or 'Windows and Linux' together).
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-23 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 recovery instructions and a script for Windows users, using PowerShell and referencing a Windows-specific script. There are no examples, scripts, or guidance for Linux or macOS users, nor any mention of equivalent tools or workflows for non-Windows platforms.
Recommendations
  • Provide equivalent recovery instructions and scripts for Linux/macOS users, using Bash or Python.
  • Clarify whether the recovery process is supported only on Windows, or if cross-platform options exist.
  • If the script is Windows-only, explicitly state this limitation and offer alternative manual steps for Linux/macOS users.
  • Include examples for Linux (e.g., using curl, ssh, or Azure CLI) where possible.
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-23 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 instructions and examples for Windows users, especially for running the deboarding script via PowerShell. Linux users are not given equivalent script execution guidance, and Windows instructions are presented first and in greater detail. The script appears to be PowerShell-based, with no mention of a Linux-compatible version or how to run it on Linux/macOS. Manual removal steps are platform-neutral, but the automation is Windows-centric.
Recommendations
  • Provide instructions for running the deboarding script on Linux/macOS, or clarify if the script is Windows-only.
  • If the script is PowerShell-only, consider offering a Bash or cross-platform version, or document how to use PowerShell Core on Linux/macOS.
  • Present Linux and Windows instructions in parallel, rather than Windows-first.
  • Explicitly state platform limitations for the script, so Linux/macOS users know their options.
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-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page exhibits moderate Windows bias. The primary automation script for Arc agent installation is a PowerShell script, with instructions focused on Windows environments (e.g., PowerShell terminal, Set-ExecutionPolicy, Windows Task Scheduler). Linux-specific guidance is limited to a brief sudo configuration note, and Linux/macOS equivalents for scripting and scheduling are missing. Windows tools and patterns (PowerShell, Task Scheduler) are mentioned exclusively or before Linux alternatives.
Recommendations
  • Provide a Bash or Python version of the automation script for Linux/macOS users, or document how to run the PowerShell script cross-platform (e.g., with PowerShell Core).
  • Include example instructions for running the script on Linux/macOS, such as using cron for scheduling instead of Windows Task Scheduler.
  • Add Linux/macOS terminal usage examples alongside PowerShell examples.
  • Clarify any OS-specific requirements for the script and agent installation.
  • Ensure parity in out-of-band automation methods (e.g., show Ansible, Bash, or Python examples before or alongside Windows tools).
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-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation for disaster recovery operations of the Azure Arc resource bridge VM is heavily focused on PowerShell scripting, with all code examples and onboarding instructions provided exclusively in PowerShell. There is no mention of Bash, Linux shell, or cross-platform alternatives, nor are Linux/macOS usage patterns or tools referenced. The onboarding script is referenced as a .ps1 file, implying Windows/PowerShell usage, and no Linux-specific guidance or parity is provided.
Recommendations
  • Provide Bash or shell script equivalents for onboarding and recovery steps, or clarify if the onboarding script is cross-platform.
  • Explicitly state platform requirements for the onboarding script (e.g., if it must be run on Windows/PowerShell, mention this up front).
  • If possible, offer Azure CLI or cross-platform alternatives for steps currently requiring PowerShell.
  • Add guidance for Linux/macOS users, including how to install/run PowerShell Core if required, or how to adapt the script for their environment.
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-23 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 all CLI commands and references PowerShell scripts (.ps1) for automation, without providing Bash or shell equivalents. There are no explicit Linux/macOS examples or guidance, and PowerShell is presented as the default scripting environment, which may create friction for Linux/macOS users.
Recommendations
  • Provide CLI command examples using Bash syntax (e.g., az ... in Bash, not PowerShell).
  • Offer equivalent Bash shell scripts for bulk deployment and workflow deletion, or clarify if the .ps1 scripts are cross-platform (e.g., PowerShell Core).
  • Explicitly mention if the Azure CLI commands are platform-agnostic and can be run in Bash or other shells.
  • Add notes or examples for Linux/macOS users, including any required adaptations for file paths or script execution.
  • Clarify if PowerShell Core is required for non-Windows platforms, and link to installation instructions if so.
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-23 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page provides almost exclusively PowerShell-based examples and scripts for orchestration diagnostics, onboarding, and log collection. Paths in JSON templates use Windows-style backslashes and drive letters. There are no Bash or Linux/macOS shell equivalents, and no mention of Linux-specific tools or patterns. The use of PowerShell and Windows file paths is pervasive, even though the topic (Azure Arc-enabled Kubernetes clusters and workload orchestration) is cross-platform and commonly used on Linux.
Recommendations
  • Add Bash/CLI examples alongside PowerShell scripts for all az commands and onboarding steps.
  • Provide Linux/macOS file path examples in JSON templates (e.g., /home/user/config.yaml) and clarify path conventions.
  • Explicitly state that scripts can be run from Linux/macOS with az CLI and provide guidance for non-Windows users.
  • Where PowerShell is used for scripting, offer Bash equivalents or note any limitations.
  • Review screenshots and instructions to ensure parity for Linux/macOS users accessing Azure portal and Log Analytics.
GitHub Create Pull Request
Azure Arc Whats new in Azure Arc-enabled VMware vSphere ...ob/main/articles/azure-arc/vmware-vsphere/whats-new.md
Medium Priority View Details →
Scanned: 2026-02-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page lists new features for Azure Arc-enabled VMware vSphere, with some bias toward Windows. Windows-specific features (e.g., guest OS customization for Windows VMs, Windows Server Management, Extended Security Updates for Windows Server/SQL Server) are mentioned before Linux equivalents or without Linux parity. Azure PowerShell is listed alongside Azure CLI and REST APIs, but no Linux-specific CLI tools are highlighted. Windows tools (System Center Configuration Manager, Group Policy) are mentioned for agent installation, with only one Linux tool (Ansible) referenced. Some features are Windows-only by nature, but overall, Linux examples and tools are less prominent.
Recommendations
  • Ensure Linux-specific features (e.g., guest OS customization for Linux VMs) are mentioned with equal prominence and detail.
  • Provide Linux-first or cross-platform examples where possible, especially for agent installation and VM management.
  • Include references to Linux-native tools (e.g., shell scripts, cloud-init, Puppet, Chef) alongside Windows tools for at-scale operations.
  • When listing SDKs or CLI tools, clarify their cross-platform compatibility and provide Linux usage examples.
  • Balance the order of Windows and Linux features to avoid 'windows_first' impression.
GitHub Create Pull Request
Azure Arc Troubleshooting for Workload Orchestration ...es/azure-arc/workload-orchestration/troubleshooting.md
Medium Priority View Details →
Scanned: 2026-02-23 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 command-line patterns. Most examples use PowerShell syntax, even for cross-platform tools like Azure CLI, and some commands (e.g., Base64 encoding, file manipulation) are given only in PowerShell. Linux/macOS equivalents (bash or shell) are missing for critical steps, except in the 'service groups' section, which provides both Bash and PowerShell tabs. This creates friction for Linux/macOS users, especially in sections involving scripting, file encoding, and registry management.
Recommendations
  • Provide Bash/shell equivalents for all PowerShell examples, especially for Azure CLI commands, file manipulation, and Base64 encoding.
  • Clearly indicate which commands are cross-platform and which are Windows-specific.
  • Add notes or tabs for Linux/macOS users where PowerShell syntax is used, explaining how to achieve the same result in Bash.
  • Review file encoding and manipulation steps to ensure Linux/macOS compatibility (e.g., use 'iconv', 'cat', or 'sed' instead of PowerShell-specific 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-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation shows evidence of Windows bias in several areas. The 'winget' command is used as the only example for installing kubectl, which is a Windows-specific tool, with no Linux/macOS installation guidance provided. In the section on extracting ZIP files, the Bash tab uses the Windows-native 'Expand-Archive' command (not available on Linux/macOS), and all example paths are Windows-style (e.g., 'C:\path\to\archive.zip'). There are no Linux/macOS-specific commands or examples for these steps. The rest of the documentation uses Azure CLI and kubectl, which are cross-platform, but the initial setup steps may create friction for Linux/macOS users.
Recommendations
  • Provide Linux/macOS installation instructions for kubectl (e.g., using 'curl' or 'apt/yum/brew').
  • For extracting ZIP files, offer Linux/macOS Bash examples using 'unzip' or 'tar' alongside Windows 'Expand-Archive'.
  • Use generic file paths or show both Windows and Linux/macOS path formats.
  • Ensure all critical setup steps have Linux/macOS equivalents and are presented equally.
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-23 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The release notes for Workload Orchestration in Azure Arc generally provide cross-platform guidance, with most CLI examples using the Azure CLI (az), which is available on Windows, Linux, and macOS. However, in the May 2025 release section, CLI examples are given in PowerShell syntax (using backticks for line continuation and variables with $), which is Windows-centric and may confuse Linux/macOS users. Additionally, PowerShell examples are shown before Bash equivalents, and Bash is not provided for those commands.
Recommendations
  • Provide Bash syntax examples alongside PowerShell for CLI commands, especially for configuration set/download.
  • Clarify that Azure CLI commands are cross-platform and provide OS-specific guidance where relevant.
  • Use generic CLI syntax (without OS-specific line continuation or variable conventions) in documentation unless the feature is Windows-only.
  • Consider showing Bash examples first or equally with PowerShell to avoid implicit Windows prioritization.
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-22 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides backup and restore examples using Windows file paths (e.g., 'C:\Backupfiles\test.bak') and references Windows tools (SQL Server Management Studio, Visual Studio Code) without offering equivalent Linux/macOS examples or guidance. The 'kubectl cp' example also uses a Windows path, and there is no mention of Linux file paths or tools for creating backups, which may create friction for Linux/macOS users.
Recommendations
  • Add Linux/macOS file path examples alongside Windows examples (e.g., '/home/user/Backupfiles/test.bak').
  • Mention and provide guidance for Linux-compatible tools for connecting to SQL Server (e.g., Azure Data Studio, sqlcmd).
  • Clarify that the backup file can be created on any OS and provide instructions for Linux/macOS users.
  • Include notes or sections for Linux/macOS users, highlighting any differences or additional steps required.
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-22 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 referenced for troubleshooting HTTP2 errors, Windows paths are shown in error messages, and Windows-specific tools (like Remote PowerShell and RDP) are discussed. Linux-specific troubleshooting steps and examples are minimal or missing, and Windows tools or patterns are often mentioned first or exclusively. For example, the PowerShell example for HTTP2 troubleshooting is given, but no Linux equivalent (such as curl with --http2) is provided. The GLIBC error is explained, but no guidance is given for checking or upgrading glibc on Linux. In DNS troubleshooting, Windows tools (Resolve-DnsName, ping) are shown, but Linux equivalents (dig, nslookup) are not. The documentation does not provide parity in examples or troubleshooting steps for Linux/macOS users.
Recommendations
  • Add Linux/macOS equivalents for all PowerShell and Windows command examples (e.g., curl --http2 for HTTP2 troubleshooting, dig/nslookup for DNS troubleshooting).
  • Mention Linux/macOS tools alongside Windows tools when discussing troubleshooting steps (e.g., SSH folder permissions, network diagnostics).
  • Provide guidance for resolving GLIBC errors on Linux, including commands to check and upgrade glibc.
  • Ensure that troubleshooting steps and error messages reference both Windows and Linux paths and environments.
  • Where possible, use cross-platform CLI commands (such as Azure CLI) and clarify any OS-specific requirements.
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-22 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 and examples for connecting servers to Azure Arc using azcmagent. While most examples and instructions are generic and applicable to both Windows and Linux, there is a notable Windows bias in several areas: the interactive browser login is described as Windows-only and presented first; certificate-based authentication includes detailed instructions for Windows certificate stores but lacks equivalent Linux guidance; and access token acquisition references only the Windows PowerShell Get-AzAccessToken cmdlet, omitting Linux alternatives.
Recommendations
  • Present authentication options in a neutral order or explicitly note Linux defaults where relevant.
  • Add Linux/macOS-specific guidance for certificate-based authentication, such as how to use PEM/PFX files and recommended storage locations.
  • Include Linux-compatible methods for obtaining access tokens, such as using Azure CLI (az account get-access-token) or Microsoft Entra clients for Linux.
  • Where Windows tools are mentioned, provide equivalent Linux commands or links.
  • Clarify which examples and flags are cross-platform, and highlight any OS-specific limitations.
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-22 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides only a Windows/PowerShell-based recovery script and instructions. There are no examples, scripts, or guidance for performing the recovery from a Linux or macOS machine. The script provided is a PowerShell script, which is not natively available on Linux/macOS, and there is no mention of cross-platform alternatives.
Recommendations
  • Provide equivalent recovery instructions and scripts for Linux/macOS users, using Bash or cross-platform PowerShell Core if possible.
  • Explicitly state if the recovery process is only supported from Windows, and explain why.
  • If possible, offer a containerized or cross-platform CLI tool for the recovery process.
  • Clarify any Windows-specific dependencies in the prerequisites section.
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-22 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 shows notable Windows bias. The auto-enablement script is PowerShell-based, with instructions and examples for Windows terminals and Windows Task Scheduler. Windows tools and automation patterns (PowerShell, Task Scheduler, Group Policy, Configuration Manager) are mentioned before Linux equivalents. Linux-specific guidance is minimal and not as prominent, with only a brief sudo configuration note and a mention of Ansible playbooks in the out-of-band section.
Recommendations
  • Provide a Bash or cross-platform version of the auto-enablement script, or document how Linux/macOS users can run the PowerShell script (e.g., via PowerShell Core).
  • Include Linux/macOS terminal instructions alongside Windows/PowerShell examples, such as how to run the script from Bash or zsh.
  • Offer examples for scheduling automation on Linux (e.g., using cron) in addition to Windows Task Scheduler.
  • Highlight Ansible and other cross-platform automation tools earlier and more prominently, not only in the out-of-band section.
  • Ensure parity in prerequisites and troubleshooting steps for Linux/macOS users.
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-22 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation consistently uses PowerShell syntax for Azure CLI commands and references PowerShell scripts (.ps1) for automation, without providing Bash or shell script equivalents. There are no Linux/macOS-specific examples or guidance, and the use of PowerShell is shown first and exclusively, which may create friction for Linux/macOS users.
Recommendations
  • Provide Azure CLI command examples in Bash syntax (e.g., using single quotes, escaping, and variable conventions for Bash).
  • Offer Bash or shell script equivalents for the referenced PowerShell automation scripts (e.g., bulk_deployment.ps1 and workflow-delete.ps1).
  • Clarify that Azure CLI commands can be run in Bash or PowerShell, and highlight any OS-specific considerations.
  • Add notes or sections for Linux/macOS users, including sample commands and scripts.
  • Ensure file paths and variable conventions are compatible with Linux/macOS environments.
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-22 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 using Bash, shell scripts, or cross-platform alternatives. The script and its usage are presented as Windows-first, with no mention of how to run or adapt the script on non-Windows platforms.
Recommendations
  • Provide instructions for running the script on Linux/macOS, such as using PowerShell Core (pwsh) which is cross-platform.
  • Include example commands for Linux/macOS terminals, e.g., using './RGCleanScript.ps1' with pwsh.
  • Clarify whether the script is compatible with PowerShell Core or only Windows PowerShell; if not, offer a Bash or shell script alternative.
  • Mention prerequisites for Linux/macOS users, such as installing PowerShell Core and ensuring script execution permissions.
  • Consider providing a platform-agnostic cleanup tool (e.g., a Python or Bash script) or guidance for Linux users.
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-22 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides only a PowerShell script for migration and instructs users to run it in PowerShell, without offering a Bash or Linux-compatible alternative. There is no mention of how Linux/macOS users can perform the migration, nor is there guidance for running the script cross-platform.
Recommendations
  • Provide a Bash or cross-platform script for Linux/macOS users.
  • Document how to run the PowerShell script using PowerShell Core on Linux/macOS, if applicable.
  • Explicitly state platform requirements and offer alternatives or workarounds for non-Windows environments.
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-22 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 diagnostics and onboarding, with no equivalent Bash, Linux shell, or cross-platform CLI examples. File paths in JSON templates and scripts are Windows-style (e.g., C:\, E:\), and all automation is shown via PowerShell scripts (.ps1), which are not natively supported on Linux/macOS. Azure CLI commands are embedded in PowerShell scripts, further reinforcing Windows-centric workflows. No Linux/macOS alternatives or guidance are offered, creating friction for non-Windows users.
Recommendations
  • Provide Bash or shell script equivalents for all PowerShell examples, especially for onboarding and diagnostics.
  • Use cross-platform file path conventions in JSON templates (e.g., /home/user/path/file.yaml) or document how to adapt paths for Linux/macOS.
  • Clearly indicate which scripts are Windows-only and offer alternatives for Linux/macOS users.
  • Where Azure CLI is used, show direct CLI commands outside PowerShell context, and clarify that Azure CLI works on all platforms.
  • Add notes or sections for Linux/macOS users, including troubleshooting tips and platform-specific instructions.
GitHub Create Pull Request
Azure Arc Troubleshooting for Workload Orchestration ...es/azure-arc/workload-orchestration/troubleshooting.md
Medium Priority View Details →
Scanned: 2026-02-22 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 syntax. Most examples, including those for Azure CLI, kubectl, and Docker, are presented in PowerShell format, with no explicit Bash or Linux shell equivalents for critical steps. Only the 'service groups' section provides both Bash and PowerShell tabs, but the rest of the document assumes PowerShell usage, which creates friction for Linux/macOS users.
Recommendations
  • Provide Bash/Linux shell equivalents for all PowerShell command examples, especially for Azure CLI, kubectl, and Docker commands.
  • Clearly indicate when commands are cross-platform and when they require Windows/PowerShell-specific syntax.
  • Add notes or tabs for Bash and PowerShell throughout the troubleshooting steps, not just in the 'service groups' section.
  • Review variable syntax and file manipulation steps to ensure they are compatible with Linux/macOS environments.
  • Where PowerShell-specific features (e.g., ConvertTo-Json, Out-File) are used, offer alternatives for Bash users (e.g., jq, echo, cat).
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-22 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 links for client tools across Windows, Linux, and macOS, but Windows links are often listed first. There is a specific note about using cmd.exe instead of PowerShell for curl on Windows, but no equivalent Linux/macOS guidance. The curl installation section gives a Windows link but only mentions 'install curl package' for Linux, lacking a direct link or command. There is also a PowerShell-specific note about curl aliasing, but no similar shell-specific notes for Linux/macOS. Overall, the page is usable for Linux/macOS users but could be improved for parity.
Recommendations
  • List Linux/macOS installation links alongside Windows, not after or below them.
  • Provide direct Linux/macOS installation commands or links for curl, not just 'install curl package'.
  • Add shell-specific notes for Linux/macOS (e.g., bash/zsh) where PowerShell-specific notes are given.
  • Ensure examples and guidance are equally detailed for all platforms.
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-22 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
Although the documentation is titled and scoped for Linux preparation with AKS Edge Essentials, it uses Windows-centric tools and patterns (Invoke-AksEdgeNodeCommand) for Linux node configuration. There are no native Linux shell or SSH examples for critical sysctl configuration steps, and the text editor suggestion (Notepad) is Windows-first. This creates friction for Linux/macOS users who may not have access to Windows tools or expect Linux-native workflows.
Recommendations
  • Provide equivalent Linux-native commands (e.g., using SSH or local shell) for sysctl configuration, such as 'sudo sysctl fs.inotify.max_user_instances' and editing /etc/sysctl.conf directly.
  • Suggest Linux text editors (e.g., nano, vim) instead of Notepad for editing aksedge-config.json.
  • Clarify when Windows tools are required and offer alternative workflows for Linux-only environments.
  • Add explicit notes or sections for macOS users if relevant.
GitHub Create Pull Request
← Previous Page 38 of 94 Next →