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 751-775 of 2334 flagged pages
Azure Arc Migrate Existing Target Resources to General Availability ...s/azure-arc/workload-orchestration/migration-script.md
Medium Priority View Details →
Scanned: 2026-03-05 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 migration script and usage example, with no mention of Linux/macOS-compatible alternatives or instructions. The script appears to require PowerShell, which is traditionally Windows-centric, and there is no guidance for users on Linux or macOS platforms.
Recommendations
  • Provide instructions for running the migration script using PowerShell Core (pwsh), which is cross-platform, and clarify compatibility.
  • Offer a Bash or shell script alternative if feasible, or explain how Linux/macOS users can use PowerShell Core to run the script.
  • Explicitly state platform requirements and provide troubleshooting tips for non-Windows environments.
  • Add examples for Linux/macOS users, including installation steps for PowerShell Core if required.
GitHub Create Pull Request
Azure Arc Troubleshooting for Workload Orchestration ...es/azure-arc/workload-orchestration/troubleshooting.md
Medium Priority View Details →
Scanned: 2026-03-05 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The troubleshooting guidance heavily favors PowerShell syntax and Windows command patterns throughout most sections. Nearly all code examples (except for a few kubectl and docker commands) are provided in PowerShell, with no equivalent Bash or Linux shell examples for critical steps. Even commands that are cross-platform (az CLI, docker, kubectl) are often shown in PowerShell syntax or with Windows-specific variable usage. Bash/Linux parity is only provided in the 'Troubleshoot service groups' section, where both Bash and PowerShell tabs are present. This creates friction for Linux/macOS users, who must translate PowerShell commands and variable handling to their environment.
Recommendations
  • Provide Bash/Linux shell equivalents for all PowerShell examples, especially for az CLI, docker, and kubectl commands.
  • Use cross-platform variable syntax (e.g., $VAR for PowerShell, $VAR for Bash) and avoid Windows-specific PowerShell constructs where possible.
  • Where file encoding is discussed, clarify how to check and convert encoding on Linux/macOS (e.g., using iconv or file editors like nano/vim).
  • For steps involving JSON manipulation, provide jq or Bash alternatives to PowerShell's ConvertTo-Json.
  • Ensure all troubleshooting steps can be followed on Linux/macOS by explicitly stating any OS-specific requirements or limitations.
GitHub Create Pull Request
Azure Arc Clean-Up Script for Workload Orchestration ...es/azure-arc/workload-orchestration/clean-up-script.md
Medium Priority View Details →
Scanned: 2026-03-04 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 and PowerShell command examples for resource clean-up, without mentioning or providing equivalent Bash/shell scripts or instructions for Linux/macOS users. The script appears to require PowerShell, which is traditionally a Windows tool, and there is no guidance for running the script on Linux/macOS or using alternative tools.
Recommendations
  • Provide instructions for running the PowerShell script on Linux/macOS using PowerShell Core (pwsh), including installation guidance if needed.
  • Offer Bash or shell script alternatives for the clean-up process, or clarify if only PowerShell is supported.
  • Explicitly state platform compatibility for the script (Windows, Linux, macOS) and note any limitations.
  • If PowerShell is required, add a section for Linux/macOS users explaining how to install and use PowerShell Core.
  • Include example commands for Linux/macOS users (using pwsh or Bash) alongside Windows/PowerShell examples.
GitHub Create Pull Request
Azure Arc Diagnostics of Edge-Related Logs and Errors in Workload Orchestration .../azure-arc/workload-orchestration/diagnose-problems.md
Medium Priority View Details →
Scanned: 2026-03-04 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 all CLI/script examples exclusively in PowerShell syntax, assumes Windows-style file paths (e.g., C:\, E:\), and references PowerShell scripts (.ps1) for orchestration. There are no Bash, shell, or Linux/macOS equivalents for commands or scripts, and Windows file path conventions are used throughout JSON templates. This creates friction for Linux/macOS users, who must adapt commands and scripts themselves.
Recommendations
  • Provide Bash or shell equivalents for all PowerShell CLI examples, especially for az CLI commands.
  • Use cross-platform file path examples in JSON templates (e.g., /home/user/schema.yaml) or note how to adapt for Linux/macOS.
  • Offer .sh script alternatives or document how to run orchestration scripts on Linux/macOS.
  • Clarify which steps are Windows-specific and which are cross-platform.
  • Add notes or links for Linux/macOS users on adapting PowerShell scripts and file paths.
GitHub Create Pull Request
Azure Arc Perform disaster recovery operations ...mware-vsphere/recover-from-resource-bridge-deletion.md
Medium Priority View Details →
Scanned: 2026-03-04 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page provides only PowerShell examples and references a PowerShell onboarding script for disaster recovery operations. There are no Bash or Linux/macOS shell equivalents, nor guidance for running the script on non-Windows platforms. The onboarding script and instructions are Windows-centric, creating friction for Linux/macOS users.
Recommendations
  • Provide Bash or shell script equivalents for onboarding and recovery steps, or clarify if the onboarding script is cross-platform.
  • Explicitly mention whether the onboarding script can be run on Linux/macOS (e.g., via PowerShell Core or Azure CLI), and provide instructions for those environments if possible.
  • Add notes or links for Linux/macOS users about prerequisites and alternative tooling.
  • If the onboarding script is Windows-only, state this clearly and suggest workarounds or alternatives 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-03-04 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is generally Linux-focused, but it uses the Windows-specific PowerShell cmdlet Invoke-AksEdgeNodeCommand for Linux node configuration, without providing native Linux shell alternatives. This creates friction for Linux users who may not have access to PowerShell or prefer standard Linux command-line tools.
Recommendations
  • Provide native Linux shell commands (e.g., using ssh, sysctl, echo, and tee) for configuring fs.inotify.max_user_instances directly on Linux nodes.
  • Clarify when PowerShell is required and offer equivalent Bash or Linux-native instructions.
  • Ensure all steps can be completed on Linux without reliance on Windows tools or 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-03-04 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides several command-line examples using PowerShell syntax (e.g., 'kubectl exec ...' and 'kubectl get secret ...') with the code block language explicitly set to 'powershell', even though the commands themselves are cross-platform. There are no Linux/macOS-specific shell examples or notes, and the use of PowerShell syntax highlighting may confuse non-Windows users. All examples are shown in a Windows-centric style, with no mention of Linux/macOS equivalents or shell environments.
Recommendations
  • Change code block language from 'powershell' to 'console' or 'shell' for cross-platform commands like 'kubectl' and 'sqlcmd'.
  • Add explicit notes clarifying that all commands work on Linux/macOS terminals as well as Windows (with appropriate tools installed).
  • Where relevant, provide example commands using bash or sh syntax (especially for decoding base64, e.g., 'echo <string> | base64 -d').
  • Avoid using Windows-specific terminology or highlighting unless the command is truly Windows-only.
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-03-04 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 default to Windows tools and file paths (e.g., Visual Studio Code, SQL Server Management Studio, Azure Storage Explorer, and Windows-style paths like C:\Backupfiles\test.bak) without offering equivalent Linux/macOS alternatives or mentioning cross-platform options. Linux/macOS users may need to infer how to adapt steps, especially for backup file creation and tool usage.
Recommendations
  • Include Linux/macOS file path examples (e.g., /home/user/Backupfiles/test.bak) alongside Windows paths.
  • Mention and provide instructions for cross-platform tools such as Azure Storage Explorer (which is available for Linux/macOS) and alternatives to SQL Server Management Studio (e.g., Azure Data Studio, which is cross-platform).
  • Clarify that Visual Studio Code and Azure Storage Explorer are available on Linux/macOS, and provide installation links for those platforms.
  • For backup creation, show T-SQL examples using Linux/macOS file paths and explain how to run them from cross-platform clients.
  • Explicitly state that all steps can be performed from Linux/macOS unless there are Windows-only requirements.
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-03-04 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 methods for base64 encoding files, but the Windows example (using certutil) is more detailed and includes additional steps (removing headers) not explained for Linux. The Linux example is brief and lacks parity in guidance. Windows tools (certutil, findstr) are mentioned explicitly, while Linux alternatives for header removal are not provided. The rest of the guide uses cross-platform tools (openssl, Azure CLI, kubectl), but the Windows encoding section is more prominent.
Recommendations
  • Expand Linux guidance for base64 encoding to include instructions for removing headers (e.g., using grep or sed).
  • Present Linux and Windows examples side-by-side for parity, rather than giving Windows-specific tools more detail.
  • Mention macOS where appropriate, as its base64 utility and file handling are similar to Linux.
  • Clarify that the base64 command works on macOS as well.
  • Add a note about how to decode base64 files on Linux/macOS, matching the Windows certutil decode example if given.
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-03-04 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides troubleshooting guidance for Azure Arc resource bridge, which is a cross-platform solution. While most examples and instructions are generic or CLI-based, there are several instances where Windows tools and patterns are referenced before Linux equivalents, and PowerShell is used for network troubleshooting (e.g., Invoke-WebRequest, Resolve-DnsName). Windows terminology (e.g., 'Remote PowerShell', 'RDP') is mentioned, and some commands are shown in Windows-centric contexts. Linux-specific troubleshooting is present (e.g., GLIBC errors), but Linux commands are less prominent and often appear after Windows examples.
Recommendations
  • Provide Linux/macOS equivalents for PowerShell commands (e.g., use curl or wget for HTTP troubleshooting, dig or nslookup for DNS resolution).
  • When referencing CLI commands, clarify if they work equally on Linux/macOS and Windows, and note any OS-specific requirements.
  • If troubleshooting steps involve Windows tools (like RDP or PowerShell), offer alternatives for Linux/macOS (e.g., SSH, terminal access).
  • Ensure Linux-specific errors and solutions are as detailed and visible as Windows ones.
  • Where possible, show Linux/macOS commands before or alongside Windows commands to improve parity.
GitHub Create Pull Request
Azure Arc What's new with Azure Connected Machine agent ...main/articles/azure-arc/servers/agent-release-notes.md
Medium Priority View Details →
Scanned: 2026-03-04 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation generally presents Windows download links and examples before Linux equivalents and provides Windows-specific troubleshooting steps (e.g., using attrib and PowerShell commands) without Linux equivalents. Some installer and configuration issues are described only for Windows, and Windows tools (e.g., PowerShell, attrib, msiexec) are referenced without mentioning Linux alternatives. However, Linux support is present and release notes are generally parity-focused.
Recommendations
  • When providing troubleshooting steps (such as editing permissions on config files), include equivalent Linux commands (e.g., chmod/chown) alongside Windows commands.
  • Where possible, present Windows and Linux download links and instructions in parallel or grouped by OS, rather than always listing Windows first.
  • If a known issue or workaround is Windows-only, clearly label it as such and consider adding a note if Linux is unaffected.
  • When referencing Windows tools (PowerShell, attrib, msiexec), provide Linux equivalents (bash, chmod, rpm/dpkg, etc.) where applicable.
  • Consider adding a section or callout for Linux-specific known issues or troubleshooting steps if any exist.
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-03-04 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 (PowerShell, Group Policy, Microsoft Update, WSUS, Configuration Manager) are often presented first or in greater detail, and a critical cleanup script is only provided in PowerShell with no Linux/bash equivalent. Windows-specific tools and patterns are described extensively, while Linux instructions are more generic and lack advanced automation examples.
Recommendations
  • Provide equivalent bash or shell scripts for Linux users, especially for tasks like cleanup of stale resources.
  • Ensure Linux examples are given equal prominence and detail, including automation and at-scale management scenarios.
  • Where Windows tools (e.g., Group Policy, WSUS, Configuration Manager) are discussed, mention Linux equivalents or clarify their absence.
  • Consider alternating the order of Windows and Linux sections, or presenting them side-by-side, to avoid 'windows_first' bias.
  • Expand Linux sections to include troubleshooting, logging, and advanced management scenarios similar to Windows.
GitHub Create Pull Request
Azure Arc How to migrate from legacy Log Analytics agents in non-Azure environments with Azure Arc ...in/articles/azure-arc/servers/migrate-legacy-agents.md
Medium Priority View Details →
Scanned: 2026-03-04 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation provides both Windows and Linux context, but there is a notable Windows bias. Windows tools (Windows Admin Center, Windows Server Graphical Installer, Group Policy) are mentioned explicitly, with no equivalent Linux tools highlighted. PowerShell is referenced before Bash, and deployment examples/tools for Linux (such as Ansible) are mentioned only in passing. No explicit Linux-specific examples or workflows are provided, and Windows deployment options are described in more detail.
Recommendations
  • Add explicit Linux deployment examples and workflows, such as using Ansible, shell scripts, or Linux-native package managers.
  • Mention Linux tools (e.g., systemd, cron, SSH) for agent management alongside Windows tools.
  • Provide Bash or shell script examples before or alongside PowerShell examples.
  • Highlight Linux-specific considerations for agent installation, configuration, and troubleshooting.
  • Balance the order and detail of Windows and Linux instructions to ensure parity.
GitHub Create Pull Request
Azure Arc Azure Connected Machine Agent Deployment Options .../main/articles/azure-arc/servers/deployment-options.md
Medium Priority View Details →
Scanned: 2026-03-04 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page provides deployment options for the Azure Connected Machine agent across both Linux and Windows platforms. However, there is a noticeable bias toward Windows, with PowerShell-based onboarding methods highlighted (including at scale), Windows-specific tools (Windows Admin Center, Configuration Manager, Group Policy) receiving dedicated sections, and Windows-only methods listed after the cross-platform options. Linux-specific automation tools (such as Ansible) are mentioned, but PowerShell is presented as a cross-platform method, despite its stronger association with Windows. No Linux-first or Linux-only onboarding methods (e.g., Bash scripts, cloud-init, or native Linux tools) are described in detail or given equal prominence.
Recommendations
  • Add explicit Linux-specific onboarding examples and methods, such as Bash scripts, shell commands, or cloud-init for at-scale deployments.
  • Clarify which PowerShell methods are truly cross-platform and provide equivalent Linux command-line examples where possible.
  • Ensure Linux automation tools (e.g., Ansible, Puppet, Chef) are given equal prominence and detail as Windows tools.
  • Consider listing Linux and Windows methods in parallel or alternating order to avoid 'windows_first' bias.
  • Provide links to Linux-specific documentation or walkthroughs for onboarding.
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-03-04 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 instructions and sample commands exclusively use Azure PowerShell, with no Azure CLI or Bash examples. Additionally, PowerShell commands are presented first and are the only method shown for deploying templates, which may create friction for Linux/macOS users who prefer CLI or Bash. The documentation does not mention or demonstrate Linux-native tools or deployment patterns, and file path examples use Windows-style paths.
Recommendations
  • Add Azure CLI deployment examples (e.g., az deployment group create) alongside PowerShell commands.
  • Show Bash shell usage for Linux/macOS users, including file path examples with Linux conventions.
  • Explicitly state that both PowerShell and CLI can be used, and link to Azure CLI documentation for ARM template deployment.
  • Consider alternating the order of Linux and Windows template examples to avoid Windows-first bias.
  • Include a note clarifying that PowerShell is cross-platform, but CLI is often preferred 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-03-04 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 covers both Windows and Linux Arc-enabled servers, but exhibits notable Windows bias. PowerShell examples dominate, with Windows-centric tools (e.g., New-AzStorageBlobSASToken, New-NetFirewallRule) featured prominently. REST API examples are exclusively Windows-focused (firewall rule via PowerShell cmdlet), and Linux-specific scripting or scenarios are largely absent. Azure CLI examples use PowerShell syntax ('Write-Host'), and there are no explicit Linux shell script examples. Windows terminology and tools are mentioned first or exclusively in several places.
Recommendations
  • Add Linux-specific examples for REST API usage, such as configuring iptables or ufw via shell scripts.
  • Provide Azure CLI examples using bash/sh syntax (e.g., 'echo Hello World!' or 'id') instead of PowerShell ('Write-Host').
  • Balance PowerShell and shell script examples in the PowerShell and CLI sections, clearly indicating which are for Windows and which are for Linux.
  • Include guidance for Linux users on generating SAS tokens (e.g., using Azure CLI or portal) rather than only PowerShell.
  • Clarify which parameters or features are OS-specific, and provide parity where possible.
  • Add Linux-focused administrative scenarios (e.g., patching, log auditing, firewall configuration) alongside Windows examples.
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-03-04 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 and a downloadable script exclusively for Windows/PowerShell environments, with no mention of Linux or cross-platform alternatives. All example commands and tooling are Windows-specific, and there are no instructions for performing the recovery from a Linux or macOS machine.
Recommendations
  • Provide equivalent recovery instructions and scripts for Linux/macOS environments, ideally using Bash or cross-platform tools.
  • Explicitly state if the recovery process is only supported from Windows, and explain why (e.g., SCVMM/PowerShell dependencies).
  • If possible, offer a platform-agnostic solution or clarify any technical limitations.
  • Add a note about the lack of Linux/macOS support if it is intentional, to set user expectations.
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-03-04 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation shows a notable Windows bias, especially in the automation/scripted installation section. The primary at-scale enablement script is a PowerShell script, and instructions for running it reference Windows-only tools (PowerShell, Task Scheduler). There are no equivalent Bash/Linux shell examples, and Linux automation options are not given equal prominence. Out-of-band methods mention Ansible but provide more detailed links and examples for Windows-centric tools (Configuration Manager, Group Policy).
Recommendations
  • Provide a Bash or cross-platform shell script for at-scale Arc agent installation, or clearly link to such resources if they exist.
  • Include Linux/macOS terminal instructions for running the automation script (e.g., using cron, bash, or systemd timers) alongside the Windows Task Scheduler example.
  • Ensure that out-of-band methods give equal detail and prominence to Linux automation tools (e.g., Ansible, shell scripts) as to Windows tools.
  • Where PowerShell is used, clarify if the script is compatible with PowerShell Core on Linux/macOS, or provide a native Bash alternative.
  • Add explicit Linux/macOS examples for all major steps, not just notes about sudo.
GitHub Create Pull Request
Azure Arc Remove your VMware vCenter environment from Azure Arc ...e-arc/vmware-vsphere/remove-vcenter-from-arc-vmware.md
Medium Priority View Details →
Scanned: 2026-03-04 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides explicit PowerShell instructions for running the deboarding script on Windows, including execution policy guidance and notes about PowerShell ISE. There are no equivalent instructions or examples for running the script on Linux or macOS, nor is there mention of cross-platform script support. Windows instructions are presented first and in detail, while Linux users are left to infer compatibility or usage.
Recommendations
  • Add explicit instructions for running the deboarding script on Linux and macOS, including prerequisites (e.g., PowerShell Core, Azure CLI) and any differences in execution.
  • Clarify whether the deboarding script is cross-platform (PowerShell Core compatible) or Windows-only. If it is Windows-only, state this clearly; if cross-platform, provide Linux/macOS usage examples.
  • Provide sample commands for running the script on Linux/macOS, including how to set execution policy and handle script prompts.
  • Mention any required dependencies or installation steps for PowerShell on non-Windows platforms.
GitHub Create Pull Request
Azure Arc Bulk Review, Publish, and Deploy with Workload Orchestration ...es/azure-arc/workload-orchestration/bulk-deployment.md
Medium Priority View Details →
Scanned: 2026-03-04 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 Linux/macOS shell equivalents. There are no Linux/macOS-specific instructions or examples, and PowerShell is presented as the default scripting environment, which may create friction for non-Windows users.
Recommendations
  • Provide Azure CLI command examples in Bash syntax (e.g., using $ variables and shell quoting) alongside PowerShell.
  • Offer equivalent Bash scripts for bulk deployment and workflow deletion, or clarify if the PowerShell scripts are cross-platform (e.g., via PowerShell Core).
  • Explicitly state that Azure CLI commands can be run in any shell, and provide guidance for Linux/macOS users where relevant.
  • Add notes or sections addressing Linux/macOS usage, including any prerequisites or differences in file path handling, quoting, or script execution.
GitHub Create Pull Request
Azure Arc Prepare the Environment for Workload Orchestration ...rc/workload-orchestration/initial-setup-environment.md
Medium Priority View Details →
Scanned: 2026-03-04 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 the Windows-specific 'winget' tool, 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 command. Throughout, Windows-centric tools and patterns are presented first or exclusively, and Linux/macOS equivalents are missing or not prioritized.
Recommendations
  • For kubectl installation, provide Linux/macOS installation commands (e.g., 'curl' or 'apt/yum/brew').
  • In Bash file extraction, use standard Linux commands like 'unzip' or 'tar' instead of 'Expand-Archive'.
  • Ensure Bash examples use cross-platform commands, not Windows/PowerShell-specific ones.
  • Present Linux/macOS instructions alongside Windows instructions, or at least not always after.
  • Explicitly note platform differences and provide guidance for Linux/macOS users where Windows tools are referenced.
GitHub Create Pull Request
Azure Arc Migrate Existing Target Resources to General Availability ...s/azure-arc/workload-orchestration/migration-script.md
Medium Priority View Details →
Scanned: 2026-03-04 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 mentioning Linux/macOS alternatives or providing Bash or cross-platform script options. This creates friction for non-Windows users who may not have access to PowerShell or may need to install it separately.
Recommendations
  • Provide a Bash or shell script alternative for Linux/macOS users.
  • Document how to run the PowerShell script using PowerShell Core on Linux/macOS, including installation instructions if needed.
  • Clarify whether the migration script is cross-platform or Windows-only, and update prerequisites accordingly.
  • Add explicit guidance for Linux/macOS users, including troubleshooting and environment setup.
GitHub Create Pull Request
Azure Arc Troubleshooting for Workload Orchestration ...es/azure-arc/workload-orchestration/troubleshooting.md
Medium Priority View Details →
Scanned: 2026-03-04 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 in Azure Arc is heavily biased toward Windows/PowerShell usage. Most command examples are provided only in PowerShell syntax, even for tasks that are cross-platform (e.g., Azure CLI, Docker, kubectl). Linux/Bash equivalents are missing or appear only in a few sections. Windows-specific scripting patterns (e.g., PowerShell variable assignment, ConvertTo-Json, Out-File, Base64 encoding via .NET) are used throughout, creating friction for Linux/macOS users.
Recommendations
  • Provide Bash/Linux equivalents for all PowerShell examples, especially for Azure CLI, Docker, and kubectl commands.
  • Use cross-platform scripting patterns (e.g., environment variables, standard file manipulation tools) instead of Windows/PowerShell-specific constructs.
  • Clearly indicate when a command is platform-specific and offer alternatives or notes for Linux/macOS users.
  • Review and update file encoding instructions to reference Linux tools (e.g., iconv, file) alongside Windows editors.
  • Ensure Base64 encoding examples use standard Linux tools (e.g., base64) as well as PowerShell.
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-03-03 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 VM extensions, ensuring parity in template content. However, all deployment commands and walkthroughs exclusively use Azure PowerShell, with no Azure CLI or Bash examples. PowerShell is a Windows-centric tool, though it is available cross-platform. Additionally, PowerShell deployment commands are presented first and exclusively, which may create friction for Linux/macOS users who prefer Azure CLI or Bash.
Recommendations
  • Add Azure CLI deployment examples alongside PowerShell for template deployment.
  • Explicitly note that PowerShell is available cross-platform, but also provide Bash/CLI alternatives for Linux/macOS users.
  • Consider showing Azure CLI examples first or in parallel with PowerShell to avoid Windows-first bias.
  • Clarify that the templates themselves are OS-agnostic and can be deployed from any platform.
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-03-03 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 and a downloadable script exclusively for Windows (PowerShell), with no mention of Linux or cross-platform alternatives. All examples and tooling are Windows-centric, and there is no guidance for users operating from Linux or macOS environments.
Recommendations
  • Provide equivalent recovery instructions and scripts for Linux/macOS environments, using Bash or cross-platform tools where possible.
  • Clearly state if recovery is only supported from Windows, and explain why, or document any limitations.
  • If possible, offer a platform-agnostic recovery method (e.g., via Azure CLI, REST API, or containerized tooling).
  • Add a section addressing Linux/macOS users, even if only to clarify current limitations and suggest workarounds.
GitHub Create Pull Request
← Previous Page 31 of 94 Next →