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 1026-1050 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-02-18 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 notable Windows bias. The auto-enablement script is PowerShell-based, with instructions and examples exclusively for Windows (e.g., Set-ExecutionPolicy, Windows Task Scheduler). There are no equivalent Linux shell or cron job examples. Windows tools and patterns (PowerShell, Task Scheduler) are mentioned before Linux alternatives, and Linux-specific guidance is limited to a brief sudo configuration note. Out-of-band methods mention Ansible, but most scripted automation is Windows-centric.
Recommendations
  • Provide a Bash or shell script version of the auto-enablement script for Linux/macOS users, with usage instructions.
  • Include examples for scheduling the script as a cron job on Linux, not just Windows Task Scheduler.
  • Offer guidance for running the PowerShell script on Linux (using PowerShell Core), or clarify limitations.
  • Ensure parity in examples for both Windows and Linux, especially in automation and at-scale deployment scenarios.
  • Highlight any differences or prerequisites for Linux/macOS environments (e.g., script execution, authentication).
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-18 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed, step-by-step instructions for running the deboarding script on Windows using PowerShell, but does not mention or provide equivalent instructions for running the script on Linux or macOS. The script section is labeled 'Windows' and all example commands are PowerShell-specific, with no Bash or cross-platform alternatives. This creates friction for Linux/macOS users who may also need to remove vCenter environments from Azure Arc.
Recommendations
  • Explicitly state whether the deboarding script can be run on Linux/macOS, and if so, provide equivalent Bash or shell instructions.
  • If the script is PowerShell-only, clarify this limitation early in the section and provide guidance for Linux/macOS users (e.g., using PowerShell Core, or running the script from a Windows machine).
  • If a cross-platform version of the script exists or can be made available, include download and usage instructions for Linux/macOS.
  • Present both Windows and Linux/macOS instructions in parallel where applicable, or at least acknowledge the experience for non-Windows 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-18 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 bulk deployment and workflow deletion. There are no Bash or Linux/macOS shell examples, and the only provided automation scripts are Windows PowerShell (.ps1) files. This creates friction for Linux/macOS users, who may need to adapt commands and cannot use the provided scripts directly.
Recommendations
  • Provide Azure CLI command examples in Bash syntax alongside PowerShell, especially since Azure CLI is cross-platform.
  • Offer equivalent Bash shell scripts for bulk deployment and workflow deletion, or clarify how Linux/macOS users can perform these tasks.
  • Explicitly note any OS requirements for scripts and provide guidance for Linux/macOS users where PowerShell scripts are referenced.
  • Add a section or callout explaining how Linux/macOS users can adapt the workflow, including script alternatives or manual steps.
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-18 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 a PowerShell script (RGCleanScript.ps1) and only demonstrates usage in PowerShell, with no mention of Bash, shell scripts, or cross-platform alternatives. There are no Linux/macOS-specific instructions or examples, and the script appears to be designed primarily for Windows environments.
Recommendations
  • Provide a Bash or shell script equivalent (e.g., RGCleanScript.sh) for Linux/macOS users, or clarify if the PowerShell script is compatible with PowerShell Core on Linux/macOS.
  • Include explicit instructions and command-line examples for running the script on Linux/macOS, using PowerShell Core (pwsh) if applicable.
  • Mention any prerequisites or dependencies for running the script on non-Windows platforms (e.g., installation of PowerShell Core, az CLI).
  • If the script is Windows-only, clearly state this limitation at the beginning of the documentation and suggest manual clean-up steps or alternative approaches for Linux/macOS users.
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-18 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 extensive PowerShell-based examples and scripts for enabling and managing diagnostics, log collection, and orchestration on Azure Arc-enabled Kubernetes clusters. All CLI and scripting instructions are given in PowerShell syntax, with no Bash or Linux shell equivalents. File paths in JSON templates and scripts use Windows-style paths (e.g., C:\Users\...), and references to running scripts are exclusively in PowerShell (.ps1). There are no Linux/macOS-specific instructions or examples, and the documentation assumes a Windows environment for orchestration and onboarding.
Recommendations
  • Add Bash or Linux shell equivalents for all PowerShell commands and scripts, especially for az CLI usage.
  • Provide examples using Linux/macOS file paths and conventions in JSON templates and onboarding instructions.
  • Clarify whether the onboarding scripts and tooling are cross-platform or Windows-only; if cross-platform, provide guidance for Linux/macOS users.
  • Include notes or sections for Linux/macOS users, highlighting any differences or prerequisites.
  • Where possible, use platform-neutral az CLI commands instead of PowerShell-specific syntax (e.g., avoid backticks for line continuation).
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-18 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits Windows bias in several areas. The example for installing kubectl uses 'winget', a Windows-only package manager, with no Linux/macOS alternative. The file extraction example under the Bash tab uses 'Expand-Archive', which is a PowerShell/Windows command, not a Bash/Linux-native tool. There are no Linux/macOS-specific instructions for these steps, and Windows paths are used throughout. While Azure CLI and kubectl are cross-platform, the documentation prioritizes Windows tools and patterns, creating friction for Linux/macOS users.
Recommendations
  • Provide Linux/macOS installation instructions for kubectl (e.g., using 'curl' or 'apt', 'brew').
  • Replace 'Expand-Archive' in Bash examples with 'unzip' or 'tar' for Linux/macOS users.
  • Include Linux/macOS file path examples alongside Windows paths.
  • Ensure Bash tab examples use Bash-native commands, not PowerShell/Windows commands.
  • Add explicit notes or sections for Linux/macOS users where steps differ.
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-18 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides CLI examples primarily in PowerShell syntax, especially in the May 2025 release section. Bash examples are shown elsewhere, but PowerShell is used for configuration commands without equivalent Bash/Linux syntax. The Azure CLI is cross-platform, but the use of PowerShell-specific syntax (backticks, variables like $rg) may confuse Linux/macOS users. There is a minor tendency to show Windows-style CLI examples first or exclusively in some sections.
Recommendations
  • Provide Bash/Linux equivalents for all PowerShell CLI examples, especially for configuration commands.
  • Use generic CLI syntax (without OS-specific shell features) when possible, or show both PowerShell and Bash versions side-by-side.
  • Clarify that Azure CLI commands work on all platforms and highlight any OS-specific differences.
  • Avoid using PowerShell-specific syntax (backticks, $variables) in generic documentation unless the section is Windows-specific.
GitHub Create Pull Request
Azure Arc Troubleshooting for Workload Orchestration ...es/azure-arc/workload-orchestration/troubleshooting.md
Medium Priority View Details →
Scanned: 2026-02-18 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The troubleshooting guidance for workload orchestration is heavily biased toward PowerShell and Windows-style command usage. Most examples, including those for Azure CLI, Docker, and Kubernetes, are provided only in PowerShell syntax, with no equivalent Bash or Linux shell examples for critical steps. Windows-specific scripting patterns (e.g., variable assignment, Base64 encoding, file encoding checks) are used throughout, and Linux/macOS users are not given parity guidance. Bash examples are only provided in the 'service groups' section, and even there, PowerShell is shown first or equally, but the rest of the document is Windows-centric.
Recommendations
  • Provide Bash/Linux shell equivalents for all PowerShell command examples, especially for Azure CLI, Docker, and Kubernetes steps.
  • Use cross-platform variable syntax and avoid Windows-specific scripting patterns (e.g., PowerShell variable assignment, Base64 encoding).
  • Explicitly mention file encoding checks for Linux/macOS users (e.g., how to check/save UTF-8 files in Linux editors).
  • Ensure that troubleshooting steps can be followed on Linux/macOS, including Docker and kubectl commands.
  • Where PowerShell is used for scripting, offer Bash alternatives or clarify which steps are Windows-only.
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-17 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides recovery instructions exclusively for Windows machines, including a PowerShell script and Windows-centric steps. There are no examples or guidance for Linux/macOS users, nor is there mention of equivalent tools or scripts for non-Windows platforms.
Recommendations
  • Provide equivalent recovery instructions for Linux/macOS users, including Bash or Python scripts.
  • Clarify whether the recovery process is supported or unsupported on Linux/macOS, and if not, explain why.
  • If the script is Windows-only, consider offering a cross-platform version or documenting manual steps for Linux users.
  • Mention any prerequisites or limitations for Linux/macOS environments explicitly.
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-17 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 preparing Linux with AKS Edge Essentials, but it uses Windows-centric tools and patterns. Specifically, it relies on the PowerShell cmdlet Invoke-AksEdgeNodeCommand for Linux node configuration, without providing native Linux shell alternatives. Notepad is mentioned as a text editor, which is Windows-specific, and there are no Linux-first or Linux-native examples for editing configuration files or running sysctl commands directly on Linux.
Recommendations
  • Provide native Linux shell commands for sysctl configuration, such as using 'sysctl' and editing '/etc/sysctl.conf' with 'nano', 'vim', or 'vi'.
  • Replace or supplement Notepad references with Linux text editors (e.g., nano, vim, vi) when editing configuration files.
  • Offer direct bash commands for steps currently using PowerShell cmdlets, so Linux users can perform tasks without needing Windows tools.
  • Ensure all examples and instructions are accessible from a Linux terminal, not just via 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-17 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 pod using sqlcmd, but these examples are shown exclusively as PowerShell commands. There is no mention of Linux/macOS shell equivalents (e.g., Bash), nor are Linux-specific tools or patterns referenced. The use of PowerShell syntax (e.g., command lines prefixed with 'powershell') and lack of Bash examples creates friction for Linux/macOS users, even though the underlying tools (kubectl, sqlcmd) are cross-platform.
Recommendations
  • Provide Bash shell examples alongside PowerShell for commands involving kubectl and sqlcmd.
  • Clarify that sqlcmd and kubectl commands can be run from any OS terminal, not just Windows/PowerShell.
  • Remove PowerShell-specific notation unless the command is truly Windows-only.
  • Add notes or examples for Linux/macOS users, especially for decoding base64 secrets (e.g., using 'base64 -d').
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-17 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides several examples and instructions that are Windows-centric, such as using Windows file paths (e.g., 'C:\Backupfiles\test.bak') and referencing tools like SQL Server Management Studio (SSMS) without mentioning Linux alternatives. There are no explicit Linux/macOS examples for backup file creation or copying files, and Windows paths are shown first and exclusively in critical steps.
Recommendations
  • Include Linux/macOS examples for backing up databases, such as using '/home/user/Backupfiles/test.bak' or '/tmp/test.bak' as file paths.
  • Mention cross-platform tools like Azure Data Studio alongside SSMS, and clarify that Visual Studio Code and Azure Storage Explorer are available on Linux/macOS.
  • Provide kubectl cp examples using Linux/macOS source file paths.
  • Explicitly state that the backup and restore steps can be performed on Linux/macOS, and provide any relevant command-line 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-17 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 (e.g., SSMS, SQL Server PowerShell, SQL Server Profiler) and highlights PowerShell scripting support as a manageability feature. While it does mention cross-platform tools like Azure CLI and Visual Studio Code, Windows tools are often listed first and in greater detail. There are no explicit Linux/macOS command-line examples or references to Linux-native management patterns, which may create friction for non-Windows users.
Recommendations
  • Add explicit examples or references for managing SQL Managed Instance enabled by Azure Arc from Linux/macOS environments, such as using Azure CLI, sqlcmd, or cross-platform scripting.
  • List cross-platform tools (Azure CLI, VS Code) before Windows-only tools in tables and sections.
  • Clarify which tools are cross-platform and which are Windows-only, possibly with an OS compatibility column.
  • Provide links to documentation for Linux/macOS equivalents where available (e.g., sqlcmd, Azure Data Studio).
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-17 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation for `azcmagent connect` shows some Windows bias, particularly in the authentication options section. The interactive browser login is described as 'Windows only' and presented first, while Linux is mentioned later for device code login. Windows certificate store options are detailed, but Linux equivalents (such as storing certificates in files) are not described with equal prominence. The access token section references PowerShell (`Get-AzAccessToken`) as a way to obtain tokens, without mentioning Linux/macOS alternatives. However, most examples and instructions are generic and applicable to both platforms.
Recommendations
  • Present authentication options in a platform-neutral order, or explicitly note Linux/macOS options alongside Windows.
  • For certificate-based authentication, provide equivalent Linux instructions (e.g., storing certificates in PEM/PFX files, using OpenSSL).
  • For access token acquisition, mention cross-platform methods (e.g., Azure CLI `az account get-access-token`) in addition to PowerShell.
  • Add explicit Linux/macOS examples where Windows-specific tools or flows are referenced.
  • Clarify that device code login is default for Linux, and provide Linux-specific command examples if needed.
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-17 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, with no Azure CLI or Bash examples. All deployment commands are shown in PowerShell syntax, which may create friction for Linux/macOS users who prefer Bash or Azure CLI. Additionally, PowerShell commands are presented before any mention of alternatives, and file paths in examples use Windows-style paths (e.g., 'D:\Azure\Templates\...'), which may confuse Linux users.
Recommendations
  • Add equivalent Azure CLI deployment commands alongside PowerShell examples, especially for template deployments.
  • Include Bash shell examples for Linux/macOS users, or clarify that Azure CLI can be used cross-platform.
  • Show file path examples using both Windows and Linux conventions (e.g., 'D:\Azure\Templates\...' and '/home/user/Azure/Templates/...').
  • Explicitly state that Azure PowerShell is available cross-platform, but Azure CLI is also supported and may be preferred on Linux/macOS.
  • Consider presenting Azure CLI examples first or side-by-side with PowerShell to avoid implicit Windows-first bias.
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-17 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation is generally cross-platform, but several sections show Windows bias. PowerShell is used for troubleshooting HTTP2 errors, and Windows-specific terminology (e.g., 'Remote PowerShell', 'RDP', 'time.windows.com') appears without Linux equivalents. CLI examples are mostly generic, but some troubleshooting steps (e.g., DNS resolution, proxy testing) use Windows tools or show Windows-first approaches. Linux-specific commands and troubleshooting are only occasionally mentioned (e.g., glibc error, ldd --version), and Linux CLI examples are rare.
Recommendations
  • For troubleshooting steps, provide both Windows and Linux/macOS command examples (e.g., nslookup, ping, Resolve-DnsName, curl, dig).
  • When referencing PowerShell, also mention Bash or shell equivalents for Linux/macOS users.
  • Include Linux/macOS proxy configuration guidance alongside Windows instructions.
  • Where Windows-specific endpoints (e.g., time.windows.com) are mentioned, clarify Linux alternatives (e.g., ntp.ubuntu.com, chrony).
  • Add explicit notes or sections for Linux/macOS users where CLI commands or troubleshooting steps 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-02-17 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 scripts and examples, with no mention of Linux/macOS equivalents or cross-platform alternatives. All script examples and instructions assume the use of PowerShell, which is traditionally Windows-centric, and there are no Bash or shell script alternatives provided. The onboarding script is referenced as a .ps1 file, reinforcing the Windows-first approach.
Recommendations
  • Provide 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, including whether PowerShell Core (pwsh) is supported on Linux/macOS.
  • If the onboarding script is Windows-only, offer guidance for Linux/macOS users (e.g., running PowerShell Core, using a Windows VM, or alternative methods).
  • Mention any prerequisites or limitations for non-Windows environments early in the documentation.
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-17 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 notable Windows bias. The auto-enablement script is PowerShell-based, with instructions and examples focused on Windows terminals and Windows Task Scheduler for automation. Windows tools and patterns (PowerShell, Task Scheduler) are mentioned exclusively or before Linux equivalents. While Linux is acknowledged (e.g., sudo configuration), there are no Linux shell script examples or guidance for running the helper script on Linux/macOS. Out-of-band methods mention Ansible playbooks, but Windows-centric approaches (Group Policy, Configuration Manager) are listed first.
Recommendations
  • Provide equivalent Bash shell script examples for Linux/macOS users, especially for the auto-enablement script.
  • Include instructions for scheduling the script as a cron job on Linux, not just Windows Task Scheduler.
  • Clarify whether the PowerShell script can be run cross-platform (e.g., with PowerShell Core on Linux/macOS) and provide guidance if so.
  • List Linux-friendly automation methods (e.g., Ansible, Bash) before or alongside Windows methods in out-of-band approaches.
  • Add explicit Linux/macOS CLI usage examples 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-17 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides detailed, step-by-step instructions for running the deboarding script on Windows using PowerShell, but does not mention or provide instructions for running the script on Linux or macOS. The Windows instructions are presented first and exclusively, creating friction for non-Windows users. Additionally, there is no mention of whether the deboarding script can be run on Linux/macOS, or if an alternative is available.
Recommendations
  • Clarify whether the deboarding script can be run on Linux or macOS. If so, provide equivalent instructions for those platforms, including shell commands and any prerequisites.
  • If the script is Windows/PowerShell-only, explicitly state this limitation and, if possible, provide a cross-platform alternative (e.g., a Bash script or Azure CLI commands).
  • Present instructions for all supported platforms in parallel or in separate sections, rather than only for Windows.
  • Add a note at the start of the deboarding script section indicating platform support and any requirements.
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-17 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page consistently provides command-line examples and scripts using PowerShell syntax (e.g., .ps1 scripts, PowerShell-style CLI invocation), and references only PowerShell scripts for automation. There are no Bash or Linux shell equivalents, nor is there guidance for Linux/macOS users on running Azure CLI commands or automating bulk operations. This creates friction for non-Windows users, especially since Azure CLI is cross-platform.
Recommendations
  • Provide Azure CLI command examples using Bash syntax, including how to run commands in Linux/macOS terminals.
  • Offer equivalent Bash shell scripts for bulk deployment and workflow deletion, or explain how to use the provided .ps1 scripts on Linux/macOS (e.g., via PowerShell Core).
  • Clarify that Azure CLI commands can be run on any OS, and avoid using PowerShell-specific syntax (e.g., parameter quoting, .ps1 script references) as the default.
  • Add notes or tabs for Linux/macOS users, showing how to perform the same tasks in their environments.
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-17 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 section for extracting ZIP files uses the Windows-native Expand-Archive command and Windows file paths, which are not available on Linux/macOS. The kubectl installation example uses winget, a Windows-only tool, with no Linux/macOS alternative provided. Throughout, file path examples and instructions default to Windows conventions, and Linux/macOS equivalents are missing or not mentioned. While Azure CLI and kubectl are cross-platform, the initial setup steps and examples favor Windows users.
Recommendations
  • Provide Linux/macOS alternatives for extracting ZIP files (e.g., 'unzip archive.zip -d /path/to/dir').
  • Offer kubectl installation instructions for Linux/macOS (e.g., using 'curl' or package managers like 'apt', 'brew').
  • Use generic or platform-neutral file paths in examples, or show both Windows and Linux/macOS path formats.
  • Ensure that all critical steps have Linux/macOS equivalents, especially for tool installation and file operations.
  • Consider adding a platform-specific tab for Linux/macOS where needed, similar to the Bash/PowerShell split.
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-17 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 PowerShell command examples for resource cleanup. There are no Bash, shell, or cross-platform script alternatives, nor any mention of how Linux/macOS users can perform the same task. The script appears to require PowerShell, which is traditionally Windows-centric, though PowerShell Core is available cross-platform. However, the documentation does not clarify compatibility or provide Linux/macOS usage guidance.
Recommendations
  • Explicitly state whether RGCleanScript.ps1 is compatible with PowerShell Core on Linux/macOS.
  • Provide Bash or shell script alternatives, or document how Linux/macOS users can run the PowerShell script (e.g., using PowerShell Core).
  • Include Linux/macOS-specific instructions and examples, such as running PowerShell scripts from a terminal or using Azure CLI for similar cleanup tasks.
  • Mention any prerequisites or limitations for non-Windows platforms.
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-17 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, and file paths in JSON templates use Windows-style (backslash) paths. There are no Bash or Linux/macOS shell equivalents for any of the automation or CLI steps. The onboarding scripts are referenced as PowerShell (.ps1) scripts, with no mention of Bash or cross-platform alternatives. Windows file patterns and tools are mentioned first and exclusively, creating friction for Linux/macOS users.
Recommendations
  • Provide Bash/zsh shell equivalents for all PowerShell CLI/script examples, especially for az CLI commands.
  • Use cross-platform file path examples (e.g., forward slashes, or note both Windows and Linux path formats).
  • Clarify whether the onboarding scripts (.ps1) are required to be run on Windows, or provide a Bash version if possible.
  • Add explicit notes about Linux/macOS support and any limitations, including how Linux users can perform equivalent tasks.
  • Where possible, use az CLI syntax that works identically across platforms, and avoid PowerShell-specific parameter formatting.
  • Include sample Linux file paths in JSON templates, or note how to adapt them for Linux/macOS environments.
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-17 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 no mention of a Bash or cross-platform alternative. The instructions exclusively reference running the script in PowerShell, which is typically a Windows tool, and do not address Linux or macOS users or provide equivalent guidance for those platforms.
Recommendations
  • Provide a Bash or shell script alternative for Linux/macOS users, or clarify if the PowerShell script is compatible with PowerShell Core on Linux/macOS.
  • Explicitly state platform compatibility for the migration script and offer installation instructions for PowerShell on non-Windows systems if applicable.
  • Include Linux/macOS-specific usage examples and troubleshooting tips.
GitHub Create Pull Request
Azure Arc Troubleshooting for Workload Orchestration ...es/azure-arc/workload-orchestration/troubleshooting.md
Medium Priority View Details →
Scanned: 2026-02-17 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, with only a few Bash alternatives provided (and only in the 'service groups' section). Many steps assume PowerShell scripting, and some commands (e.g., Base64 encoding, file manipulation) are only shown in PowerShell. Linux/macOS users may struggle to adapt instructions, especially for scripting and file handling tasks.
Recommendations
  • Provide Bash/Linux equivalents for all PowerShell commands, especially for az CLI, kubectl, docker, and file manipulation steps.
  • Show Bash examples first or side-by-side with PowerShell to avoid implicit Windows prioritization.
  • Clarify which steps are OS-agnostic and which require adaptation, and offer guidance for Linux/macOS users.
  • For scripting tasks (e.g., Base64 encoding, JSON file creation), include Linux shell commands (e.g., base64, jq, echo) and editor instructions.
  • Review variable usage and syntax to ensure compatibility across platforms.
GitHub Create Pull Request
← Previous Page 42 of 94 Next →