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 976-1000 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-02-20 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 (WOGAMigration.ps1) and instructs users to run it in PowerShell, with no mention of Linux/macOS-compatible alternatives or instructions. This creates friction for non-Windows users who may not have access to PowerShell or may prefer Bash or other native tools.
Recommendations
  • Provide a Bash or cross-platform script for Linux/macOS users, or document how to run the PowerShell script using PowerShell Core on Linux/macOS.
  • Explicitly state PowerShell Core compatibility if applicable, and provide installation instructions for Linux/macOS.
  • Offer example commands for Linux/macOS environments alongside Windows/PowerShell instructions.
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-20 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page provides CLI examples primarily in PowerShell syntax, especially in the May 2025 release section. Bash examples are used elsewhere, but PowerShell is shown in some critical configuration scenarios. There is no explicit mention of Linux/macOS equivalents or alternative shell usage, and PowerShell examples appear before Bash in the release chronology.
Recommendations
  • Provide CLI examples in both Bash and PowerShell syntax, or use Bash as the default for cross-platform parity.
  • Explicitly state that Azure CLI commands work on Linux/macOS and Windows, and clarify any OS-specific differences.
  • Where PowerShell syntax is used, add a Bash equivalent immediately after.
  • Review all CLI examples to ensure they are not using Windows-specific shell features (e.g., backticks, variable syntax) unless necessary.
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-20 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides SQL connectivity examples using PowerShell syntax (e.g., kubectl exec ... -- /opt/mssql-tools/bin/sqlcmd ...), which is typically associated with Windows environments. The examples are labeled as 'powershell', and no equivalent Linux/macOS shell examples (e.g., bash) are provided. Additionally, the PowerShell examples appear before any mention of Linux alternatives, creating a Windows-first impression.
Recommendations
  • Provide Linux/macOS shell (bash) examples alongside PowerShell examples for commands involving kubectl and sqlcmd.
  • Remove or clarify the 'powershell' label on code blocks where the command is cross-platform and not specific to PowerShell.
  • Explicitly state that the commands can be run from any OS with kubectl and sqlcmd installed, and provide guidance for Linux/macOS users.
  • Consider showing bash examples first or in parallel to avoid Windows-first bias.
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-20 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is mostly Linux-focused but introduces Windows-centric tools (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 Windows-specific Azure tools.
Recommendations
  • Provide native Linux shell (bash) command examples for sysctl configuration, such as 'sysctl fs.inotify.max_user_instances' and 'echo "fs.inotify.max_user_instances = 1024" | sudo tee -a /etc/sysctl.conf && sudo sysctl -p'.
  • Clarify whether Invoke-AksEdgeNodeCommand is required or optional, and if so, explain how Linux users can install or use it, or provide alternatives.
  • Ensure all critical configuration steps have Linux-native command examples alongside any Windows/PowerShell/Invoke-AksEdgeNodeCommand usage.
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-20 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 and some instructions (e.g., for curl and kubectl) reference Windows-specific behaviors or PowerShell. Linux installation instructions are less explicit, sometimes just referencing 'install curl package' without a link or detailed guidance. There is also a note about using cmd.exe on Windows, but no equivalent Linux/macOS guidance.
Recommendations
  • Provide explicit installation links or commands for Linux and macOS, not just Windows.
  • Ensure Linux/macOS instructions are as detailed as Windows instructions (e.g., for curl, kubectl).
  • Avoid referencing Windows-specific behaviors (like PowerShell curl alias) without mentioning Linux/macOS equivalents.
  • List installation options in a neutral order or group by OS, rather than Windows first.
  • Add sample commands for Linux/macOS where Windows-specific notes are given.
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-20 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows Authentication
Summary
The documentation references Windows-centric tools (SSMS, SQL Server Data Tools, SQL Server PowerShell, SQL Server Profiler) and mentions Windows Authentication as a supported feature. PowerShell scripting support is highlighted in the manageability section. However, Azure PowerShell is marked as unsupported, and Azure CLI is listed as supported. There are no explicit Linux/macOS examples or tool recommendations, but the page does not present critical tasks as Windows-only.
Recommendations
  • Add explicit mention of cross-platform tools (e.g., Azure Data Studio, Azure CLI, Visual Studio Code) and clarify their Linux/macOS compatibility.
  • Provide examples or links for using SQL Managed Instance enabled by Azure Arc from Linux/macOS environments.
  • Clarify that Windows Authentication is only relevant for Windows environments and suggest alternatives for Linux/macOS users (e.g., SQL Server Authentication, Microsoft Entra authentication when available).
  • Highlight PowerShell alternatives (such as Bash or Azure CLI) for scripting and automation on Linux/macOS.
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-20 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 cross-platform alternatives. There are no explicit Linux/macOS examples for performing backups, and Windows paths are used exclusively in key steps, which may confuse or hinder Linux/macOS users.
Recommendations
  • Include Linux/macOS equivalents for file paths in backup examples (e.g., /home/user/backup/test.bak).
  • Mention cross-platform tools such as Azure Data Studio alongside SSMS, especially for backup/restore operations.
  • When referencing tools like Azure Storage Explorer and Visual Studio Code, clarify their cross-platform availability.
  • Provide example commands for both Windows and Linux/macOS environments where file operations are involved.
  • Explicitly state that the instructions apply to all supported platforms, or call out any platform-specific differences.
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-20 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation includes several examples and troubleshooting steps that reference Windows tools and patterns, such as PowerShell commands and Windows-specific error messages (e.g., 'connectex', 'wsarecv'). PowerShell is used for network troubleshooting and DNS resolution, but equivalent Linux commands are not provided. Windows terminology and error codes are often shown first or exclusively, while Linux alternatives are mentioned less frequently or only in passing. There are also sections where only Windows-based troubleshooting steps are given, such as using PowerShell for HTTP/2 troubleshooting, and no Linux/macOS equivalents are offered.
Recommendations
  • Provide Linux/macOS equivalents for all PowerShell examples (e.g., use curl, wget, or openssl for HTTP/2 troubleshooting).
  • Include Linux/macOS commands for DNS resolution (e.g., dig, nslookup, host) alongside Windows/PowerShell examples.
  • When referencing Windows-specific error codes (e.g., 'connectex', 'wsarecv'), also mention typical Linux/macOS error messages for similar scenarios.
  • Ensure that troubleshooting steps and CLI instructions are platform-neutral or clearly indicate if a step is Windows-only.
  • Add explicit guidance for Linux/macOS users where file paths, permissions, or CLI usage may differ.
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-20 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 the azcmagent CLI. While the overall content is cross-platform, there is evidence of Windows bias: Windows authentication methods are described first, Windows certificate store options are detailed, and PowerShell tools (Get-AzAccessToken) are referenced for access token retrieval without mentioning Linux/macOS equivalents. Linux authentication methods are present but not prioritized, and Linux-specific tooling is not referenced.
Recommendations
  • Present authentication options in a platform-neutral order, or explicitly state platform applicability for each method.
  • For access token retrieval, provide Linux/macOS alternatives (such as Azure CLI commands like 'az account get-access-token') alongside PowerShell examples.
  • When describing certificate-based authentication, clarify Linux/macOS certificate storage and retrieval methods, not just Windows certificate stores.
  • Add explicit Linux/macOS examples where relevant, such as shell commands for hostname retrieval or certificate handling.
  • Ensure that all examples and instructions are equally applicable to Linux/macOS, or provide platform-specific sections as needed.
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-20 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 mild signs of Windows bias: Windows examples and sections are often presented first, PowerShell scripts are used for cleanup and automation tasks without equivalent Bash scripts, and Windows-specific tools (e.g., Group Policy, WSUS, Configuration Manager) are described in detail, while Linux equivalents (such as package management automation or systemd integration) are not. The cleanup script for stale resources is only provided in PowerShell, with no Bash or CLI equivalent for Linux users.
Recommendations
  • Present Linux and Windows examples in parallel or alternate order, rather than always Windows first.
  • Provide Bash or Azure CLI scripts for automation tasks (e.g., stale resource cleanup) alongside PowerShell scripts.
  • Include guidance for automating agent upgrades and removals on Linux (e.g., using cron, systemd, or Ansible), similar to the detail given for Windows tools like Group Policy and WSUS.
  • Expand Linux sections to mention log locations, package management automation, and integration with Linux-native monitoring/configuration tools.
  • Where PowerShell is used for Azure resource management, offer Azure CLI equivalents for cross-platform parity.
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-20 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation provides ARM template examples for both Linux and Windows VM extensions, but all deployment instructions and commands are exclusively shown using Azure PowerShell. There are no Azure CLI or Bash examples, and PowerShell is presented as the only method for deploying templates, which may create friction for Linux/macOS users. Additionally, PowerShell commands and Windows-style file paths are shown first and exclusively in deployment sections.
Recommendations
  • Add Azure CLI examples for deploying ARM templates (e.g., using 'az deployment group create') alongside PowerShell commands.
  • Include Bash shell command examples where appropriate, especially for Linux users.
  • Mention that Azure PowerShell can be used cross-platform, but provide explicit guidance for Linux/macOS users who may prefer Azure CLI.
  • Show both Windows and Linux file path conventions in examples (e.g., 'D:\Azure\Templates\...' and '/home/user/Azure/Templates/...').
  • Consider presenting CLI and PowerShell deployment options side-by-side, or at least clarify that both are supported.
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-20 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 Windows/PowerShell-based recovery instructions and scripts for the Azure Arc resource bridge VM. There are no Linux/macOS examples, nor is there mention of equivalent tools or scripts for non-Windows platforms. The recovery script is explicitly designed for Windows, and Linux users are not given guidance or alternatives.
Recommendations
  • Provide equivalent recovery instructions and scripts for Linux/macOS users, using Bash or Python.
  • Explicitly state platform requirements and limitations, clarifying if recovery is only supported from Windows.
  • If possible, offer a cross-platform script or containerized solution.
  • Add a section explaining why Linux/macOS support is unavailable if this is a technical limitation.
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-20 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. However, the 'Auto Arc-enablement script' section is heavily PowerShell-centric, with instructions and examples exclusively for Windows (PowerShell terminal, Set-ExecutionPolicy, Windows Task Scheduler). The script is not described for Linux/macOS users, and there are no Bash or cron examples. Windows tools and patterns (PowerShell, Task Scheduler) are mentioned before Linux equivalents. While there is a brief note about sudo configuration for Linux, the main automation example is Windows-only.
Recommendations
  • Provide equivalent Bash or shell script examples for Linux/macOS users.
  • Include instructions for running the automation script on Linux (e.g., using cron instead of Windows Task Scheduler).
  • Clarify if the helper script is cross-platform or provide a Linux version.
  • Show both PowerShell and Bash usage examples side-by-side.
  • Mention Linux tools (e.g., cron, systemd timers) alongside Windows Task Scheduler.
  • Ensure out-of-band methods (like Ansible) are highlighted for Linux users.
GitHub Create Pull Request
Azure Arc Upgrade the Azure Arc resource bridge ...l-machine-manager/upgrade-azure-arc-resource-bridge.md
Medium Priority View Details →
Scanned: 2026-02-20 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation assumes the user is operating from a Windows/SCVMM environment, referencing the SCVMM server as the location to run commands and does not provide Linux/macOS equivalents or clarify cross-platform support for the Azure CLI steps. All examples and instructions are Windows-centric, with no mention of Linux or macOS environments.
Recommendations
  • Clarify whether the Azure CLI commands (az arcappliance) can be run from Linux/macOS workstations, and if so, provide explicit instructions or examples for those platforms.
  • If the upgrade process is supported only from Windows/SCVMM environments, state this explicitly at the beginning of the article.
  • If Linux/macOS are supported, add notes about any required tools or configuration differences (e.g., file paths, shell syntax).
  • Where possible, provide cross-platform command examples or note any platform-specific limitations.
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-20 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation page for disaster recovery operations of the Azure Arc resource bridge VM is heavily focused on PowerShell scripts and commands, with no mention of Linux/macOS equivalents or cross-platform alternatives. All script examples and instructions are given in PowerShell syntax, and there is no guidance for users who may be operating from Linux or macOS environments. The onboarding script is referenced as a .ps1 file, implying Windows/PowerShell usage, and no Bash or shell alternatives are provided.
Recommendations
  • Provide equivalent Bash or shell script examples for Linux/macOS users, or clarify if the onboarding script is cross-platform.
  • Explicitly state the platform requirements for running the onboarding script (e.g., Windows/PowerShell only, or if PowerShell Core is supported on Linux/macOS).
  • If the onboarding script can be run using PowerShell Core on Linux/macOS, add instructions for installation and usage on those platforms.
  • Mention any prerequisites or limitations for Linux/macOS users, and offer guidance for completing the recovery process from those environments.
GitHub Create Pull Request
Azure Arc Remove your VMware vCenter environment from Azure Arc ...e-arc/vmware-vsphere/remove-vcenter-from-arc-vmware.md
Medium Priority View Details →
Scanned: 2026-02-20 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed Windows/PowerShell instructions for running the deboarding script, including execution policy steps and script invocation. There are no equivalent instructions or examples for running the script on Linux or macOS, nor is it clarified whether the script can be run cross-platform. Windows instructions are presented first and exclusively, creating friction for Linux users.
Recommendations
  • Clarify whether the deboarding script can be run on Linux/macOS (e.g., with PowerShell Core or Azure CLI).
  • Provide explicit Linux/macOS instructions for downloading and running the script, including any prerequisites (such as PowerShell Core or bash).
  • If the script is Windows-only, state this clearly and offer alternative manual steps for Linux/macOS users.
  • Present both Windows and Linux/macOS instructions in parallel or note platform-specific differences.
  • Consider providing a bash or cross-platform version of the deboarding script if feasible.
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-20 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 almost exclusively PowerShell-based examples and scripts for enabling diagnostics, onboarding, and log collection. All CLI/script instructions are given in PowerShell syntax, with no Bash or Linux/macOS shell equivalents. Paths in JSON templates use Windows-style backslashes and drive letters. There is no mention of Linux/macOS alternatives or cross-platform compatibility for the scripts, and Windows tools (PowerShell, Windows file paths) are referenced before any Linux equivalents, which are missing.
Recommendations
  • Provide Bash or shell script equivalents for all PowerShell commands, especially for az CLI usage.
  • Clarify whether the infra_onboarding.ps1 script is cross-platform or provide a Linux/macOS version (e.g., infra_onboarding.sh).
  • Use platform-neutral file paths in JSON templates, or provide examples for both Windows and Linux/macOS.
  • Mention prerequisites for Linux/macOS users, including any required tools or environment setup.
  • Add notes or sections explicitly addressing Linux/macOS usage and troubleshooting.
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-20 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 (e.g., bulk_deployment.ps1, workflow-delete.ps1) without providing equivalent Bash or shell script examples. There are no explicit Linux/macOS instructions or examples, and the PowerShell syntax is shown for all CLI commands, which may create friction for Linux/macOS users who typically use Bash. The documentation does not mention Linux tools or patterns, nor does it clarify cross-platform usage for the scripts.
Recommendations
  • Provide CLI command examples in Bash syntax as well as PowerShell, or use generic CLI syntax that works across platforms.
  • Offer equivalent Bash shell scripts for bulk_deployment.ps1 and workflow-delete.ps1, or clarify if the PowerShell scripts are cross-platform (e.g., PowerShell Core).
  • Add notes or sections explaining how Linux/macOS users can run the Azure CLI commands and scripts, including any prerequisites or differences.
  • Explicitly state whether the scripts are compatible with PowerShell Core on Linux/macOS, or provide alternatives.
  • Consider showing Bash examples first or side-by-side with PowerShell to improve parity.
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-20 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exhibits Windows bias primarily in the 'kubectl' installation instructions, where only the Windows-specific 'winget' command is provided and no Linux/macOS installation method is mentioned. Additionally, the file extraction example under the Bash tab uses the Windows-native 'Expand-Archive' command with Windows-style paths, which is not available on Linux/macOS Bash shells. Throughout the page, examples and variable naming conventions often use Windows paths and tools first, and Linux/macOS equivalents are missing or unclear.
Recommendations
  • Provide Linux/macOS installation instructions for 'kubectl', such as using 'apt', 'brew', or downloading from the official Kubernetes site.
  • For file extraction, include cross-platform Bash examples (e.g., 'unzip archive.zip -d /path/to/dir') and clarify which commands are Windows-only.
  • Use generic or platform-neutral path examples in Bash sections, or provide separate examples for Windows and Linux/macOS.
  • Review all Bash examples to ensure they are valid for Linux/macOS environments, not just Windows.
  • Add a note clarifying when a command or tool is Windows-specific and provide alternatives for other platforms.
GitHub Create Pull Request
Azure Arc Troubleshooting for Workload Orchestration ...es/azure-arc/workload-orchestration/troubleshooting.md
Medium Priority View Details →
Scanned: 2026-02-20 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 use PowerShell, even for tasks that are cross-platform (e.g., Azure CLI, Docker, kubectl), and do not provide equivalent Bash or Linux shell examples. Windows-specific patterns (e.g., PowerShell variable syntax, ConvertTo-Json, Out-File) are used without Linux alternatives. Only in the 'Troubleshoot service groups' section are Bash examples provided alongside PowerShell, but elsewhere Linux users must adapt Windows-centric instructions.
Recommendations
  • Provide Bash/Linux shell equivalents for all PowerShell examples, especially for Azure CLI, Docker, and kubectl commands.
  • Avoid using Windows-specific PowerShell constructs (e.g., Out-File, ConvertTo-Json) without showing cross-platform alternatives (e.g., jq, echo, cat, >).
  • When referencing file encoding, clarify how to check and convert encoding on Linux/macOS (e.g., using iconv or file command).
  • Show both Bash and PowerShell tabs for all command sections, not just service group queries.
  • Use cross-platform variable syntax in Azure CLI examples (e.g., $var for PowerShell, $var or ${var} for Bash).
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-19 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides comprehensive coverage for both Windows and Linux platforms, including installation, upgrade, uninstallation, and proxy configuration. However, there is a notable Windows bias in several areas: PowerShell scripts and Windows-specific tools (e.g., Group Policy, WSUS, Configuration Manager) are described in detail, often with step-by-step instructions and example scripts, while equivalent Linux automation (e.g., Bash scripts for cleanup, package manager automation, systemd integration) is not provided. Windows methods and tools are sometimes presented first or with more depth. The cleanup script for stale resources is PowerShell-only, with no Linux CLI or Bash equivalent. Proxy configuration for Windows includes detailed environment variable handling and service restart instructions, while Linux relies on a bundled script but lacks deeper automation examples.
Recommendations
  • Provide equivalent Bash or shell scripts for Linux users, especially for tasks like cleanup of stale Arc resources.
  • Include automation examples for Linux (e.g., using cron, systemd, or Ansible) where Windows automation is described (e.g., Group Policy, WSUS).
  • Balance the depth of instructions: offer step-by-step guidance for Linux package manager automation and system configuration, similar to Windows.
  • When presenting methods, alternate the order or group by OS rather than consistently leading with Windows.
  • Expand Linux proxy configuration guidance to include manual environment variable setup and service restart instructions, matching Windows detail.
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-19 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, as they must adapt the examples and cannot use the provided scripts directly.
Recommendations
  • Provide Azure CLI command examples in Bash syntax, as Azure CLI is cross-platform.
  • Offer equivalent Bash shell scripts for bulk deployment and workflow deletion, or note how Linux/macOS users can achieve the same workflow.
  • Explicitly state that the PowerShell scripts are Windows-only and provide guidance for Linux/macOS users.
  • Add a section clarifying cross-platform support and any limitations for Linux/macOS users.
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-19 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively provides a PowerShell (.ps1) script for clean-up operations, with all usage examples and instructions tailored to PowerShell. There are no Bash, shell, or cross-platform alternatives, nor any mention of how Linux/macOS users can perform the same tasks. This creates friction for non-Windows users.
Recommendations
  • Provide a Bash or shell script equivalent for Linux/macOS users, or document how to run the PowerShell script using PowerShell Core (pwsh) on non-Windows platforms.
  • Include explicit instructions and examples for running the script on Linux/macOS, such as using PowerShell Core or adapting the script for Bash.
  • Clarify any Windows-specific dependencies or limitations of the script, and suggest alternatives if possible.
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-19 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, with no mention of Bash, Linux shell alternatives, or cross-platform scripting. This creates friction for Linux/macOS users who may not have PowerShell installed or prefer native tools.
Recommendations
  • Provide a Bash or shell script equivalent for Linux/macOS users.
  • Document how to run the PowerShell script using PowerShell Core on Linux/macOS, including installation instructions if necessary.
  • Clarify whether the migration script is cross-platform or Windows-only, and update prerequisites accordingly.
  • If only PowerShell is supported, explicitly state this and offer guidance for Linux/macOS users to install PowerShell Core.
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-19 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides SQL connectivity examples using PowerShell syntax and references Windows-style command lines (e.g., PowerShell blocks for kubectl exec/sqlcmd), without offering equivalent Linux/macOS shell examples. The use of PowerShell is unnecessary for cross-platform tools like kubectl and sqlcmd, and may confuse Linux/macOS users. Additionally, Windows-style command blocks are shown first and exclusively.
Recommendations
  • Replace PowerShell code blocks with generic shell (bash/sh) examples, or provide both PowerShell and bash versions.
  • Clarify that kubectl and sqlcmd commands are cross-platform and can be run from any OS terminal.
  • Add explicit Linux/macOS shell examples for connecting to the SQL Server pod and running sqlcmd.
  • Use 'console' or 'shell' code block syntax instead of 'powershell' for cross-platform commands.
GitHub Create Pull Request
← Previous Page 40 of 94 Next →