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 1076-1100 of 2334 flagged pages
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-15 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 is a mild Windows bias: Windows examples and instructions are often presented first, Windows-specific tools (PowerShell, Group Policy, WSUS, Configuration Manager) are described in greater detail, and a cleanup script for stale resources is only provided in PowerShell. Linux instructions are present and clear, but advanced automation examples (like scripting for stale resource cleanup) are Windows/PowerShell-only.
Recommendations
  • Present Linux and Windows instructions in parallel or alternate order to avoid 'windows_first' bias.
  • Provide equivalent Linux automation scripts (e.g., Bash or Python) for tasks like stale resource cleanup.
  • Expand Linux-specific guidance for update automation (e.g., using cron, unattended-upgrades, or package manager hooks).
  • Where Windows tools are mentioned (e.g., Group Policy, WSUS), briefly note Linux equivalents or alternatives (e.g., configuration management tools like Ansible, Puppet, or native package managers).
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-15 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides troubleshooting guidance for Azure Arc resource bridge, which is a cross-platform solution. However, there are signs of Windows bias: PowerShell is referenced for troubleshooting HTTP/2 errors, Windows paths are shown in error messages, and Windows-specific tools (RDP, remote PowerShell) are discussed. Linux-specific troubleshooting commands and examples are largely missing or appear after Windows ones. The GLIBC error is the only explicit Linux issue covered, but Linux CLI troubleshooting is not as prominent as Windows/PowerShell.
Recommendations
  • Add Linux/macOS equivalents for PowerShell troubleshooting steps, such as using curl with HTTP/2 or OpenSSL for certificate validation.
  • Provide Linux/macOS-specific examples for CLI commands, including file paths and permission troubleshooting (e.g., SSH folder access).
  • Mention Linux/macOS methods for network diagnostics (e.g., using 'ping', 'nslookup', 'dig', 'curl', 'traceroute') alongside Windows tools.
  • Ensure error messages and troubleshooting steps reference both Windows and Linux environments equally.
  • Clarify when a step is Windows-only and provide alternative instructions for Linux/macOS users.
GitHub Create Pull Request
Azure Arc Recover from accidental deletion of resource bridge VM ...em-center-virtual-machine-manager/disaster-recovery.md
Medium Priority View Details →
Scanned: 2026-02-15 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 Windows/PowerShell-based recovery script and workflow, with no mention of Linux/macOS equivalents or alternative methods. All instructions and downloadable scripts are Windows/PowerShell-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 such as Azure CLI.
  • Explicitly state if recovery is only supported from Windows, and if so, clarify the technical limitations.
  • If possible, offer a cross-platform script (e.g., in Python or Bash) or containerized solution.
  • Add a note in the prerequisites section about supported operating systems for the recovery process.
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-15 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides ARM template examples for both Linux and Windows Arc-enabled servers, ensuring parity in template content. However, all deployment commands and instructions are exclusively shown using Azure PowerShell, with no Azure CLI or Bash examples. Additionally, PowerShell commands are presented first and as the only method for deploying templates, which may create friction for Linux/macOS users who prefer CLI or Bash. The file path examples use Windows-style paths (e.g., D:\Azure\Templates), further reinforcing Windows-first patterns.
Recommendations
  • Add Azure CLI deployment examples alongside PowerShell, e.g., 'az deployment group create --resource-group <resource-group-name> --template-file <template-filename.json> --parameters <parameter-filename.json>'.
  • Provide Bash script samples for Linux/macOS users where appropriate.
  • Include Linux-style file path examples (e.g., /home/user/Azure/Templates) in sample commands.
  • Clarify that both PowerShell and CLI can be used on any platform, and link to cross-platform deployment 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-15 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page exhibits notable Windows bias, especially in the 'Auto Arc-enablement script' section, which exclusively provides PowerShell-based automation and references Windows Task Scheduler for cron jobs. Windows tools and patterns (PowerShell, Task Scheduler) are mentioned before Linux equivalents, and Linux-specific automation (e.g., Bash, systemd timers, cron) is missing. While Linux is acknowledged in prerequisites and out-of-band methods, the primary scripted automation and scheduling guidance is Windows-centric.
Recommendations
  • Provide Bash or shell script equivalents for the automation script, or clarify if the helper script is cross-platform.
  • Include instructions for running the automation at scale on Linux/macOS, such as using cron or systemd timers instead of Windows Task Scheduler.
  • Add examples for Linux users, including how to set execution permissions (chmod +x), and how to run the script from a Bash terminal.
  • Clarify whether the helper script is PowerShell-only or if a cross-platform version exists.
  • Ensure parity in automation and scheduling guidance for both Windows and Linux 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-15 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both Windows and Linux instructions for uninstalling the Arc agent, but the deboarding script section is Windows/PowerShell-only. The script is only shown as a PowerShell script, and there are no instructions or mention of running the script from Linux/macOS, nor is there a Bash or cross-platform alternative. Additionally, Windows/PowerShell instructions are presented first and in more detail.
Recommendations
  • If the deboarding script is PowerShell-only and cannot be run on Linux/macOS, explicitly state this limitation and provide manual removal steps for Linux/macOS users.
  • If possible, provide a Bash or cross-platform version of the deboarding script, or document how to run the PowerShell script using PowerShell Core (pwsh) on Linux/macOS.
  • Present Windows and Linux/macOS instructions in parallel sections or clarify platform requirements at the start of each section.
  • Add a note about script compatibility (e.g., whether it works with PowerShell Core on non-Windows platforms).
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-15 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 provides only PowerShell examples and references, with no mention of Bash, Linux shell, or cross-platform alternatives. The onboarding script and its usage are shown exclusively in PowerShell syntax, and there is no guidance for Linux/macOS users on how to perform equivalent operations. The script editing and execution steps assume a Windows environment, creating friction for non-Windows users.
Recommendations
  • Provide Bash or shell script examples alongside PowerShell for onboarding and recovery operations.
  • Clarify whether the onboarding script is cross-platform or Windows-only; if cross-platform, show Linux/macOS usage.
  • Mention prerequisites for Linux/macOS users, such as PowerShell Core installation or alternative tools.
  • Add explicit instructions for editing and running the onboarding script on Linux/macOS, including command syntax and environment requirements.
  • Consider referencing Azure CLI commands where possible, as Azure CLI is cross-platform.
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-15 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 examples. There are no Linux/macOS-specific instructions or script alternatives, and PowerShell is presented as the default for CLI usage, which may create friction for Linux/macOS users.
Recommendations
  • Provide Azure CLI command examples in Bash syntax, or clarify that the CLI commands work identically in Bash and PowerShell.
  • Offer Bash or shell script equivalents for bulk_deployment.ps1 and workflow-delete.ps1, or note if the scripts are cross-platform.
  • Explicitly state platform requirements for scripts and commands, and link to guidance for Linux/macOS users if PowerShell is required.
  • Add a note clarifying that Azure CLI commands can be run in any shell environment, not just PowerShell.
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-15 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 Windows-specific tooling (winget), with no Linux/macOS alternative. The file extraction example in the Bash tab uses Expand-Archive, which is a PowerShell/Windows command, not a native Bash/Linux tool. There are no Linux/macOS-specific instructions for these steps, and Windows paths are used throughout. Bash and PowerShell tabs are provided, but Bash examples often use Windows commands, creating confusion for Linux/macOS users.
Recommendations
  • Provide Linux/macOS-specific instructions for installing kubectl (e.g., using curl or package managers like apt, yum, or brew).
  • Replace Expand-Archive in Bash examples with native Linux/macOS commands (e.g., unzip or tar).
  • Use cross-platform file path examples (e.g., /home/user/path or ~/workspace) in Bash sections.
  • Ensure Bash examples use commands available on Linux/macOS, not Windows-only tools.
  • Add explicit notes or tabs for macOS if there are platform-specific differences.
  • Review all Bash examples to confirm they are valid for Linux/macOS environments.
GitHub Create Pull Request
Azure Arc Troubleshooting for Workload Orchestration ...es/azure-arc/workload-orchestration/troubleshooting.md
Medium Priority View Details →
Scanned: 2026-02-15 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, even for tasks that are cross-platform (e.g., Azure CLI, Docker, kubectl). There are no explicit Linux/bash equivalents for critical troubleshooting steps, except in the 'Troubleshoot service groups' section, which provides both Bash and PowerShell tabs. This creates friction for Linux/macOS users, especially in sections where only PowerShell is shown and Windows-specific scripting patterns (e.g., ConvertTo-Json, Out-File, [Convert]::ToBase64String) are used.
Recommendations
  • Provide Bash/Linux equivalents for all PowerShell examples, especially for Azure CLI, Docker, and kubectl commands.
  • Avoid using Windows-specific scripting constructs (e.g., ConvertTo-Json, Out-File) without showing cross-platform alternatives (e.g., jq, echo, cat, base64).
  • Where possible, use platform-neutral Azure CLI syntax and highlight cross-platform compatibility.
  • Clearly indicate when a command is Windows-only, and provide guidance for Linux/macOS users.
  • Review and update sections to ensure Linux/macOS users can follow troubleshooting steps without friction.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides ARM template examples for both Linux and Windows Arc-enabled servers, ensuring parity in template content. However, all deployment commands and walkthroughs exclusively use Azure PowerShell, with no Azure CLI or Bash examples. Additionally, PowerShell commands are presented first and as the only method for deploying templates, which may create friction for Linux/macOS users who prefer CLI or Bash. The template examples themselves are balanced, but the deployment instructions are Windows-centric.
Recommendations
  • Add Azure CLI deployment examples alongside PowerShell, e.g., 'az deployment group create' commands.
  • Explicitly mention that Azure CLI can be used from Linux/macOS and provide sample Bash scripts.
  • Consider showing CLI examples before or alongside PowerShell to avoid Windows-first bias.
  • Clarify that PowerShell is cross-platform, but also provide CLI alternatives for users who do not use PowerShell.
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-14 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 instructions and examples for running a PowerShell script (RGCleanScript.ps1) to perform clean-up operations. There are no references to Linux/macOS shell equivalents, nor are there instructions for running the script in cross-platform environments (e.g., PowerShell Core, Bash). The documentation assumes the user is on Windows and using Windows PowerShell, which may create friction for Linux/macOS users.
Recommendations
  • Clarify whether RGCleanScript.ps1 is compatible with PowerShell Core (pwsh) on Linux/macOS. If so, provide example commands for running the script on those platforms.
  • If the script is Windows PowerShell-only, consider providing a cross-platform version or a Bash alternative for Linux/macOS users.
  • Explicitly mention prerequisites for Linux/macOS users, such as installing PowerShell Core, and provide installation instructions or links.
  • Add notes or troubleshooting tips for common issues encountered when running PowerShell scripts on non-Windows platforms.
GitHub Create Pull Request
Azure Arc Customer intent: As a system administrator, I want to configure a single-node Kubernetes cluster with adequate resources and storage provisions, so that I can deploy and manage applications effectively using Azure IoT Operations and Azure Container Storage. ...tainer-storage/includes/single-node-edge-essentials.md
Medium Priority View Details →
Scanned: 2026-02-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is intended for configuring AKS Edge Essentials on Linux, but it uses Windows-centric tools (Invoke-AksEdgeNodeCommand) for Linux node configuration and does not provide native Linux shell equivalents. This creates friction for Linux users who may not have access to Windows tools or PowerShell, and there are missing examples for performing the same tasks directly on Linux.
Recommendations
  • Provide native Linux shell (bash) commands for checking and setting sysctl parameters, e.g., '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 available on Linux or only via Windows/PowerShell, and offer alternatives if not.
  • Ensure all steps for Linux node configuration can be completed from a Linux environment without requiring Windows tools.
  • Add explicit Linux command-line examples alongside any PowerShell/Windows-centric instructions.
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-14 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 instructions for client tools across platforms, but Windows-specific guidance is often mentioned first or in greater detail. For example, 'kubectl' installation links list Windows first, and the note about installing via curl specifically references Windows cmd.exe and PowerShell, without equivalent Linux/macOS instructions. The curl section gives a Windows link and only mentions 'Linux: install curl package' without a link or command. PowerShell-specific behavior for curl is noted, but no Linux/macOS shell nuances are discussed.
Recommendations
  • Present installation instructions for all platforms (Windows, Linux, macOS) in parallel, not Windows-first.
  • Provide explicit Linux/macOS installation links and example commands for tools like curl, not just a brief mention.
  • Include shell-specific notes for Linux/macOS (e.g., bash/zsh) where PowerShell-specific notes are given.
  • Balance platform-specific guidance and troubleshooting tips.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation frequently presents Windows-centric tools and file paths first (e.g., SSMS, C:\ paths), and does not provide equivalent Linux/macOS examples for key steps such as creating backups or copying files. This may cause friction for users on non-Windows platforms.
Recommendations
  • Provide parallel examples using Linux/macOS tools (e.g., Azure Data Studio, sqlcmd, or VS Code on Linux/macOS) for connecting to SQL Server and running backup/restore commands.
  • Show backup file paths using both Windows (C:\Backupfiles\test.bak) and Linux (/home/user/backup/test.bak) formats.
  • When referencing tools like SSMS, mention cross-platform alternatives such as Azure Data Studio.
  • In kubectl cp examples, include a Linux/macOS source path (e.g., ~/Backupfiles/test.bak) alongside the Windows example.
  • Clarify that all steps can be performed from Linux/macOS where supported, and note any Windows-only requirements.
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-14 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 instance using sqlcmd, but these examples are shown exclusively with PowerShell syntax (e.g., kubectl exec ...), and the sqlcmd usage is presented in a way that assumes Windows/PowerShell familiarity. There are no explicit Linux/macOS shell examples, nor is there guidance for Linux users on connecting to the SQL Server pod or decoding secrets. The use of PowerShell syntax and lack of Linux/macOS parity creates friction for non-Windows users.
Recommendations
  • Provide equivalent Linux/macOS shell examples (e.g., using bash) for connecting to the SQL Server pod, running sqlcmd, and decoding base64 secrets.
  • Clarify that sqlcmd is cross-platform and provide installation instructions for Linux/macOS if needed.
  • Show both Windows (PowerShell) and Linux/macOS (bash) command variants side-by-side where applicable.
  • Explicitly mention that kubectl and sqlcmd commands can be run from any OS, and note any OS-specific differences.
GitHub Create Pull Request
Azure Arc Rotate user-provided TLS certificate in indirectly connected SQL Managed Instance enabled by Azure Arc ...articles/azure-arc/data/rotate-user-tls-certificate.md
Medium Priority View Details →
Scanned: 2026-02-14 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 instructions are more detailed and appear after the Linux example. The Windows section references Windows-specific tools (certutil, findstr) and requires manual header removal, while the Linux example is simpler. There is no PowerShell bias, but the Windows instructions are more prominent and lack parity in automation compared to Linux. All other steps use cross-platform tools (OpenSSL, Azure CLI, kubectl), but the Windows base64 encoding process is less streamlined.
Recommendations
  • Provide a more streamlined Windows example for base64 encoding, possibly using PowerShell's built-in Base64 capabilities for parity with Linux simplicity.
  • Mention cross-platform alternatives (e.g., using OpenSSL for base64 on Windows, or PowerShell's [Convert]::ToBase64String) to avoid reliance on certutil/findstr.
  • Ensure Linux and Windows instructions are equally detailed and placed side-by-side for clarity.
  • Clarify that Azure CLI and kubectl commands are cross-platform and can be run on Windows, Linux, or macOS.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides troubleshooting guidance for Azure Arc resource bridge, which is a cross-platform solution. However, there are several instances of Windows bias: Windows/PowerShell examples are given (e.g., PowerShell cmdlets for troubleshooting HTTP2 errors), Windows paths and error messages are shown first, and Linux-specific troubleshooting steps are sometimes missing or less detailed (e.g., SSH folder access, proxy configuration, and CLI usage). While Linux is mentioned (e.g., glibc errors, Azure Linux OS), Linux/macOS users may encounter friction due to the lack of parity in examples and troubleshooting steps.
Recommendations
  • Provide Linux/macOS equivalents for all PowerShell and Windows-specific troubleshooting steps (e.g., use curl or wget for HTTP2 troubleshooting instead of PowerShell).
  • Include Linux/macOS CLI examples for commands such as az arcappliance, pip installation, and SSH folder permission troubleshooting.
  • Ensure proxy and DNS troubleshooting steps are platform-agnostic, or provide separate sections for Windows and Linux/macOS.
  • When referencing file paths or error messages, include both Windows and Linux/macOS formats.
  • Review all troubleshooting steps for assumptions about Windows environments and add Linux/macOS guidance where missing.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Windows and Linux instructions for managing the Azure Connected Machine agent, but Windows examples and tools (such as PowerShell scripts, Microsoft Update, Group Policy, and Msiexec) are often presented first or in greater detail. The cleanup script for stale resources is only provided in PowerShell, with no Linux/bash equivalent. Windows-specific tools and patterns (e.g., Control Panel, Registry Editor, Group Policy) are described in depth, while Linux instructions are more concise and rely on standard package managers. Overall, Linux parity is good for core agent operations, but automation and scripting examples favor Windows.
Recommendations
  • Provide equivalent bash or shell scripts for Linux users, especially for tasks like cleaning up stale Arc-enabled server resources.
  • Where possible, present Linux and Windows instructions side-by-side or in parallel, rather than Windows-first.
  • Expand Linux sections to include troubleshooting tips and automation examples similar to those provided for Windows.
  • Include references to Linux-native tools for managing updates and configuration (e.g., cron jobs, systemd services) where relevant.
  • Clarify when a method is Windows-only and offer Linux alternatives if available.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation provides authentication options and examples for both Windows and Linux, but there is a notable Windows-first bias in the ordering and phrasing. The 'Interactive browser login' is described as Windows-only and appears first, while Linux is mentioned secondarily. Windows certificate store options are detailed, but Linux equivalents (such as using PEM/PFX files) are not given equal prominence. The access token example references a Windows PowerShell cmdlet ('Get-AzAccessToken') without mentioning a Linux alternative. Overall, Linux users can complete the task, but Windows-specific tools and patterns are mentioned first or exclusively in some cases.
Recommendations
  • Reorder authentication options so Linux-relevant methods (device code, Azure CLI) are not always secondary to Windows methods.
  • Provide Linux-specific guidance or examples for certificate-based authentication, such as storing PEM/PFX files in typical Linux locations and using Linux file permissions.
  • For access token acquisition, mention cross-platform methods (e.g., Azure CLI 'az account get-access-token') alongside PowerShell.
  • Clarify that all examples and flags are cross-platform unless stated otherwise, and explicitly note any Windows-only features.
  • Add explicit Linux/macOS example commands where possible, especially for authentication and certificate handling.
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-14 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 Windows/PowerShell-based recovery script and instructions, with no mention of Linux or cross-platform alternatives. All recovery steps assume the administrator is using a Windows machine, and the provided script is a PowerShell script. There are no Bash, Linux, or macOS instructions or scripts.
Recommendations
  • Provide equivalent recovery instructions and scripts for Linux/macOS environments, ideally using Bash or cross-platform scripting languages.
  • Explicitly state if the recovery process is only supported on Windows, and clarify any platform limitations.
  • If possible, offer a cross-platform CLI or Azure CLI-based solution.
  • Add a note in the prerequisites about supported operating systems for the recovery process.
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-14 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 exhibits notable Windows bias, especially in the 'Auto Arc-enablement script' section, where only PowerShell and Windows Task Scheduler examples are provided. The script usage instructions assume a Windows environment, with no mention of Linux/macOS equivalents (e.g., Bash, cron). Additionally, Windows tools and patterns (PowerShell, Task Scheduler) are referenced exclusively or before Linux alternatives. While there is a brief note about sudo configuration for Linux, there are no Linux-specific automation examples or guidance for running the helper script on Linux/macOS.
Recommendations
  • Provide Bash or shell script examples for Linux/macOS users, including instructions for running the helper script in a Linux environment.
  • Include guidance for scheduling the script via cron on Linux, not just Windows Task Scheduler.
  • Clarify whether the helper script is cross-platform or Windows-only; if cross-platform, add Linux/macOS usage instructions.
  • Where PowerShell is used, offer equivalent Bash commands or note limitations for non-Windows users.
  • Ensure automation approaches (e.g., Ansible, Azure CLI) are presented with parity for both Windows and Linux environments.
GitHub Create Pull Request
Azure Arc What is Azure Arc-enabled VMware vSphere? ...lob/main/articles/azure-arc/vmware-vsphere/overview.md
Medium Priority View Details →
Scanned: 2026-02-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page for Azure Arc-enabled VMware vSphere is generally cross-platform, but there are several areas where Windows bias is evident. PowerShell is mentioned as a primary automation tool, and Windows examples or references (such as Windows Server management, Windows registry, and Windows-specific tabs in links) are often listed before Linux equivalents. Linux is supported in many features, but Linux-specific examples, tools, or guidance are less prominent or missing, especially in automation and configuration sections.
Recommendations
  • Provide Linux-specific examples and guidance alongside Windows examples, especially for automation tasks (e.g., using Bash, shell scripts, or Linux-native tools).
  • Mention Linux tools and patterns (such as systemd, cron, or Linux daemons) equally with Windows tools (like PowerShell and Windows registry).
  • Ensure links and documentation tabs are balanced, offering both Windows and Linux instructions where applicable.
  • Highlight cross-platform SDKs and CLI usage with explicit Linux/macOS compatibility notes.
  • When referencing Azure Automation, include examples for Python and Bash runbooks, not just PowerShell.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exclusively provides PowerShell examples and references the onboarding script as a PowerShell (.ps1) script, with no mention of Bash, Linux shell, or cross-platform alternatives. All scripting and command-line instructions are Windows-centric, and there are no Linux/macOS equivalents or guidance for non-Windows users. This creates friction for Linux/macOS administrators attempting disaster recovery operations.
Recommendations
  • Provide Bash or shell script equivalents for onboarding and recovery operations, or clarify if the onboarding script is cross-platform.
  • Explicitly state OS requirements for running the onboarding script (e.g., if PowerShell Core is supported on Linux/macOS).
  • Add examples and instructions for running the onboarding script on Linux/macOS, including installation prerequisites and command syntax.
  • Mention any Azure CLI alternatives if available, or clarify if only PowerShell is supported.
  • Ensure documentation is clear about platform support and limitations for disaster recovery operations.
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-14 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 uses PowerShell syntax for all CLI examples and references only PowerShell scripts (e.g., bulk_deployment.ps1, workflow-delete.ps1) for automation. There are no Bash or Linux/macOS shell examples, nor are Linux-friendly scripts or instructions provided. The use of PowerShell and .ps1 scripts is presented as the default, with no mention of cross-platform alternatives or guidance for Linux/macOS users.
Recommendations
  • Provide CLI command examples in Bash syntax alongside PowerShell, or clarify that Azure CLI commands are cross-platform and can be run in Bash, Zsh, etc.
  • Offer equivalent Bash scripts for bulk deployment and workflow deletion, or provide instructions for running the PowerShell scripts on Linux/macOS (e.g., using PowerShell Core).
  • Explicitly state that Azure CLI commands are not limited to Windows and can be executed on any supported OS.
  • Add notes or sections for Linux/macOS users, including any prerequisites or differences in file paths, script execution, or environment setup.
GitHub Create Pull Request
← Previous Page 44 of 94 Next →