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 701-725 of 2334 flagged pages
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-07 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 context in its introduction and scope, but several sections show a Windows-first bias. Windows-specific tools (Windows Admin Center, Windows Server Graphical Installer, Group Policy) are mentioned explicitly and before Linux equivalents. PowerShell is referenced as a primary scripting method, and Linux-specific tools (e.g., shell scripts, Ansible) are mentioned but not emphasized equally. There are no explicit Linux command examples, and the standalone agent installation section only covers Windows clients.
Recommendations
  • Provide explicit Linux/Bash command examples alongside PowerShell where scripts are referenced.
  • Mention Linux tools (e.g., shell scripts, systemd, Ansible) with equal prominence and detail as Windows tools.
  • Include a section or link for standalone Azure Monitor Agent installation on Linux client machines, or clarify if not supported.
  • When listing deployment options, alternate the order or group by OS to avoid always listing Windows tools first.
  • Add Linux-specific troubleshooting or configuration notes where relevant.
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-07 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. There are no instructions, scripts, or examples for performing the recovery from Linux or macOS systems, nor is there mention of cross-platform alternatives.
Recommendations
  • Provide equivalent recovery instructions and scripts for Linux/macOS environments, using Bash or cross-platform tools where possible.
  • Clearly indicate if the recovery process is only supported from Windows, and explain why (e.g., dependencies on Windows-only tools or APIs).
  • If feasible, offer a platform-agnostic solution (such as an Azure CLI or Python script) to enable recovery from non-Windows systems.
  • Explicitly state OS requirements and limitations in the prerequisites section.
GitHub Create Pull Request
Azure Arc Install Arc agent at scale for your VMware VMs ...arc/vmware-vsphere/enable-guest-management-at-scale.md
Medium Priority View Details →
Scanned: 2026-03-07 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page exhibits a moderate Windows bias. The primary automation script for at-scale agent installation is a PowerShell script, with instructions focused on Windows environments (e.g., PowerShell terminal usage, Windows Task Scheduler for cron jobs, and Set-ExecutionPolicy). Windows-specific tools and patterns (PowerShell, Windows Task Scheduler) are mentioned exclusively or before Linux equivalents. While Linux is referenced (e.g., sudo configuration), there are no Linux/bash script examples or guidance for running the automation at scale on Linux/macOS. Out-of-band methods mention Ansible, but Windows-centric approaches (Group Policy, Configuration Manager) are listed first and in greater detail.
Recommendations
  • Provide equivalent bash or shell script examples for Linux/macOS users, including instructions for running at scale.
  • Include guidance for scheduling automation on Linux (e.g., using cron) alongside Windows Task Scheduler.
  • List Linux-friendly automation methods (e.g., Ansible, shell scripts) before or alongside Windows methods.
  • Clarify which methods are cross-platform and which are Windows-only, and provide parity where possible.
  • Add explicit examples for Linux/macOS environments (e.g., running the helper script in bash, using chmod for permissions).
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-07 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 PowerShell examples and instructions for running the onboarding script, with no mention of Bash, Linux shell, or cross-platform alternatives. The onboarding script is referenced with a .ps1 extension and all example code is in PowerShell, implying Windows-centric tooling and workflows. There is no guidance for Linux/macOS users or mention of how to run the onboarding script on non-Windows platforms.
Recommendations
  • Add explicit instructions for running the onboarding script on Linux/macOS, including prerequisites (such as PowerShell Core or Bash alternatives).
  • Provide Bash or shell script examples alongside PowerShell, or clarify if the onboarding script is cross-platform.
  • Mention any required tools for Linux/macOS users (e.g., PowerShell Core, Azure CLI) and how to install them.
  • State platform compatibility for the onboarding script and highlight any limitations or workarounds for non-Windows 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-03-07 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 changes and script invocation, but does not offer equivalent Linux/macOS guidance. The script section is labeled 'Windows' and lacks information on running the script from Linux or macOS, despite Azure CLI and PowerShell Core being cross-platform. Manual steps are portal-based and platform-neutral, but the scripted removal is Windows-centric.
Recommendations
  • Add instructions for running the deboarding script on Linux/macOS, including prerequisites (e.g., PowerShell Core, Azure CLI), script invocation, and any differences in handling execution policies.
  • Clarify whether the deboarding script can be run on Linux/macOS, and if not, provide a Linux-compatible version or alternative.
  • Present both Windows and Linux/macOS script instructions side-by-side, or note any limitations for non-Windows users.
  • Explicitly mention supported platforms for the deboarding script and provide troubleshooting tips for Linux/macOS environments.
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-07 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 a bulk deployment script in PowerShell (.ps1). There are no Bash or Linux/macOS shell examples, and the only script provided is Windows-specific. This creates friction for Linux/macOS users, who may need to adapt commands and cannot use the provided script directly.
Recommendations
  • Provide Azure CLI command examples in Bash syntax (e.g., using single quotes, proper escaping) alongside PowerShell examples.
  • Offer a Bash shell script equivalent to bulk_deployment.ps1, or note how Linux/macOS users can perform bulk deployment without the PowerShell script.
  • Clarify that Azure CLI commands are cross-platform, and specify any OS-specific considerations.
  • Mention that the .ps1 script is Windows-only and suggest alternatives for Linux/macOS users.
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-07 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits moderate Windows bias, especially in the file extraction step. The Bash tab uses Windows-specific commands (Expand-Archive, cd with Windows-style paths) and references Windows paths (e.g., C:\path\to\archive.zip), with no Linux/macOS equivalent (such as unzip or tar). The kubectl installation command uses winget, a Windows-only tool, and does not provide a Linux/macOS alternative. Throughout, examples and variable placeholders are often Windows-centric, and Linux/macOS users must infer or adapt steps. However, Azure CLI and kubectl commands are cross-platform, and most orchestration steps are generic.
Recommendations
  • Provide Linux/macOS equivalents for file extraction (e.g., unzip <archive.zip> -d <folder> or tar -xf <archive.tar.gz> -C <folder>).
  • Add instructions for installing kubectl on Linux/macOS (e.g., curl or apt/yum/brew commands).
  • Use generic path placeholders or show both Windows and Unix-style paths in examples.
  • Clarify that Bash examples are intended for both Windows (WSL/Git Bash) and Linux/macOS, and offer platform-specific notes where needed.
  • Ensure all steps that reference Windows tools (winget, Expand-Archive) have Linux/macOS alternatives.
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-07 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation exclusively provides instructions for running a PowerShell script (RGCleanScript.ps1) and only shows Windows/PowerShell command examples. There is no mention of Linux/macOS equivalents, such as Bash or cross-platform scripting, nor guidance for running the script on non-Windows platforms. The script appears to be distributed only as a .ps1 file, which is traditionally Windows-centric, and PowerShell is referenced as the primary tool.
Recommendations
  • Provide instructions for running the script on Linux/macOS, including installation of PowerShell Core (pwsh) if required.
  • Clarify whether the script is compatible with PowerShell Core (cross-platform) or only Windows PowerShell.
  • Offer Bash or shell script alternatives if possible, or note limitations for Linux/macOS users.
  • Explicitly state platform requirements and offer guidance for Linux/macOS users to achieve equivalent functionality.
  • Add examples using 'pwsh' for Linux/macOS if the script is compatible.
GitHub Create Pull Request
Azure Arc Troubleshooting for Workload Orchestration ...es/azure-arc/workload-orchestration/troubleshooting.md
Medium Priority View Details →
Scanned: 2026-03-07 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 are provided only in PowerShell syntax, even for tasks that are cross-platform (e.g., Azure CLI, Docker, Kubernetes). Linux/Bash equivalents are missing for critical troubleshooting steps, except for the 'service groups' section, which offers Bash and PowerShell tabs. This bias creates friction for Linux/macOS users, as they must translate PowerShell commands to Bash or other shells.
Recommendations
  • Provide Bash/Linux equivalents for all PowerShell command examples, especially for Azure CLI, Docker, and Kubernetes commands.
  • Use cross-platform syntax for Azure CLI commands (e.g., avoid PowerShell-specific variable assignment and piping).
  • Clearly indicate when a command is Windows-only or cross-platform.
  • Add notes or tabs for macOS/Linux users where file encoding or path conventions differ.
  • Review and update troubleshooting steps to ensure Linux parity, especially for edge device operations.
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-07 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 example, with no mention of Linux/macOS-compatible alternatives or instructions. The script is a .ps1 file, which is traditionally associated with Windows environments, and there are no Bash or cross-platform script options provided.
Recommendations
  • Provide a Bash or Python migration script for Linux/macOS users, or clarify if the PowerShell script is compatible with PowerShell Core on Linux/macOS.
  • Add explicit instructions for running the migration on Linux/macOS, including any prerequisites (e.g., PowerShell Core installation).
  • Mention whether the script is cross-platform or Windows-only, and if Windows is required, state this clearly in the prerequisites.
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-06 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides troubleshooting guidance for Azure Arc resource bridge, which is a cross-platform solution. However, there are several instances of Windows bias: PowerShell is referenced for troubleshooting HTTP2 issues, Windows paths are shown in error messages, and Windows-specific tools (like Remote PowerShell and RDP) are discussed. Linux-specific troubleshooting commands are rarely given, and Linux CLI examples (such as for checking DNS or network connectivity) are missing or less prominent. The GLIBC error is the only explicit Linux troubleshooting section. Azure CLI is used throughout, which is cross-platform, but some instructions (e.g., downgrading Azure CLI via pip) are not clearly separated for Linux/macOS users. Windows tools and patterns are mentioned first or exclusively in several sections.
Recommendations
  • Provide Linux/macOS equivalents for PowerShell troubleshooting commands (e.g., using curl or wget for HTTP2 tests).
  • Add Linux/macOS examples for common troubleshooting steps, such as checking DNS resolution (e.g., dig, nslookup, ping), file permissions, and network connectivity.
  • Clarify when instructions differ for Windows vs. Linux/macOS, especially for Azure CLI installation/downgrade and SSH folder permissions.
  • Avoid referencing Windows tools (PowerShell, RDP) exclusively; mention SSH and Linux-native tools where applicable.
  • Ensure error messages and troubleshooting steps are not Windows-path-centric (e.g., C:\ paths), and provide Linux/macOS equivalents.
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-06 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation provides only PowerShell examples and scripts for disaster recovery operations, with no mention of Bash, Linux shell, or cross-platform alternatives. All script editing and execution instructions assume a Windows environment, creating friction for Linux/macOS users. The onboarding script is referenced as a .ps1 file and only PowerShell commands are shown.
Recommendations
  • Provide equivalent Bash or shell script examples for Linux/macOS users, or clarify if the onboarding script is cross-platform.
  • Explicitly state platform requirements for the onboarding script (e.g., 'Windows/PowerShell required' or 'works on Linux with PowerShell Core').
  • If possible, offer guidance for running the onboarding script on Linux/macOS (e.g., using PowerShell Core, prerequisites, or alternative workflows).
  • Add a note at the start of the article about supported platforms for the disaster recovery process.
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-06 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 Windows-style command lines (e.g., kubectl exec ... -- /opt/mssql-tools/bin/sqlcmd), without offering equivalent Linux/macOS shell examples. PowerShell is used for SQL queries, and Windows command patterns are shown first and exclusively, even though the underlying operations are cross-platform. There are no explicit Linux/macOS shell examples for connecting to SQL Server or decoding secrets.
Recommendations
  • Provide Linux/macOS shell examples (e.g., using bash) alongside PowerShell examples for connecting to SQL Server in the pod.
  • Show how to decode base64 secrets using Linux/macOS tools (e.g., echo ... | base64 -d) in addition to any Windows/PowerShell methods.
  • Clarify that the sqlcmd tool and kubectl commands work on any OS, and offer sample commands for both environments.
  • Avoid using PowerShell syntax exclusively; use generic shell syntax or provide both variants.
  • Ensure that examples are OS-neutral or explicitly show parity between Windows and 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-03-06 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 backup file paths using Windows-style (C:\Backupfiles\...), and references to tools like SQL Server Management Studio (SSMS) without mentioning Linux alternatives. There are no explicit Linux/macOS examples for file paths or tools, and Windows paths are shown first and exclusively in backup/restore steps. The use of Visual Studio Code is cross-platform, but the instructions do not clarify this or provide Linux/macOS-specific guidance.
Recommendations
  • Add Linux/macOS examples for backup file paths (e.g., /home/user/Backupfiles/test.bak) alongside Windows examples.
  • Mention cross-platform alternatives to SSMS, such as Azure Data Studio, and clarify which tools are available on Linux/macOS.
  • Explicitly state that Visual Studio Code and Azure Storage Explorer are cross-platform, and provide installation links for Linux/macOS.
  • Provide guidance for Linux/macOS users on connecting to SQL Server and running backup/restore commands.
  • Show kubectl cp examples using Linux/macOS source file paths.
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-06 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 Windows-centric Azure PowerShell cmdlets (Invoke-AksEdgeNodeCommand) for Linux node configuration, without providing native Linux shell alternatives. This creates friction for Linux users who may not have PowerShell installed or prefer standard Linux tools.
Recommendations
  • Provide equivalent Linux shell commands for sysctl configuration, such as 'sysctl fs.inotify.max_user_instances' and 'echo ... | sudo tee -a /etc/sysctl.conf && sudo sysctl -p', directly in Bash.
  • Clarify whether PowerShell is required on Linux, and if so, provide installation instructions or alternatives.
  • Where possible, use native Linux commands and tools for Linux node management, or offer both PowerShell and Bash examples.
  • Review all steps to ensure Linux users can complete them without relying on Windows-centric tools.
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-03-06 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 presented first or more prominently. For example, kubectl installation links list Windows before Linux/macOS, and curl installation notes focus on Windows and PowerShell, with Linux instructions being less explicit. There is also a note about using cmd.exe on Windows 10, but no comparable Linux shell guidance. Linux installation instructions are sometimes missing or less detailed.
Recommendations
  • Present installation instructions for all platforms (Windows, Linux, macOS) in parallel, or rotate the order to avoid Windows-first bias.
  • Provide explicit Linux/macOS installation instructions for tools like curl, not just 'install curl package'.
  • Add Linux shell guidance where Windows-specific shell guidance is given (e.g., if mentioning cmd.exe for Windows, mention bash/zsh for Linux/macOS).
  • Clarify PowerShell-specific notes and provide equivalent Linux/macOS command examples where relevant.
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-03-06 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 such as SQL Server Management Studio (SSMS), SQL Server PowerShell, and Windows Authentication as supported features. PowerShell scripting support is explicitly listed, and Windows Authentication is included in the security features. However, Linux equivalents (such as sqlcmd, mssql-tools, or Linux authentication mechanisms) are not mentioned. The order of tools and features does not strongly prioritize Windows, but the lack of Linux-specific examples or tools creates friction for Linux/macOS users.
Recommendations
  • Add examples or references for Linux/macOS management tools such as sqlcmd, mssql-tools, Azure Data Studio, and relevant CLI usage.
  • Clarify authentication options for Linux deployments, such as Microsoft Entra ID or SQL authentication, and note limitations of Windows Authentication on non-Windows platforms.
  • Include PowerShell alternatives (e.g., Bash, Python scripts) for manageability tasks.
  • Explicitly state cross-platform compatibility for features and tools where applicable.
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-06 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 release notes for both Windows and Linux versions of the Azure Connected Machine agent, with most features and fixes clearly marked for each OS. However, there is a consistent pattern of Windows download links and examples being listed before Linux, and troubleshooting steps (e.g., file permission changes) are only given for Windows, with no Linux equivalents. Command-line examples and known issue resolutions are exclusively shown for Windows (Command Prompt/PowerShell), and Windows-specific tools and patterns (e.g., .msi installers, PowerShell scripts) are referenced without Linux alternatives or parity in guidance.
Recommendations
  • When providing troubleshooting steps (such as editing permissions on agentconfig.json), include equivalent Linux commands (e.g., using chmod or chown) if the issue can occur on Linux, or explicitly state if it is Windows-only.
  • Alternate the order of download links and examples, or present both Windows and Linux instructions side-by-side to avoid a 'Windows-first' impression.
  • Where PowerShell or Windows command-line examples are given, provide equivalent Bash or shell commands for Linux users.
  • Ensure that improvements or features that are Linux-specific are highlighted with the same prominence as Windows-specific ones.
  • If a known issue or fix is Windows-only, clearly label it as such and confirm that Linux users are not affected.
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-06 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
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 examples for Azure CLI or Bash. This creates friction for Linux/macOS users, as PowerShell is not their default shell and Azure CLI is more commonly used on those platforms. The documentation also omits explicit Linux/macOS instructions for editing parameter files and running deployments.
Recommendations
  • Add Azure CLI deployment examples alongside PowerShell commands, especially for deploying ARM templates.
  • Explicitly mention that Azure CLI can be used on Linux/macOS and provide equivalent CLI syntax for each deployment step.
  • Include instructions or tips for editing parameter files on Linux/macOS (e.g., using nano, vim, or VS Code).
  • Consider showing Azure CLI examples first or side-by-side with PowerShell to avoid implicit Windows-first bias.
  • Clarify that PowerShell is cross-platform, but Azure CLI is often preferred on Linux/macOS.
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-06 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides deployment options for both Linux and Windows, but PowerShell is prominently featured as a cross-platform onboarding method, despite its primary association with Windows. Windows-specific tools and methods (Windows Admin Center, Configuration Manager, Group Policy) are listed separately and in detail, while Linux-specific automation tools (such as Ansible) are mentioned but not given equal prominence or example depth. PowerShell is presented as a universal solution, which may create friction for Linux users who prefer native shell scripting or other Linux-centric tools.
Recommendations
  • Provide explicit Bash or shell script examples for Linux onboarding, alongside PowerShell.
  • Highlight Linux-native automation tools (e.g., shell scripts, cron, systemd) as alternatives to PowerShell for Linux users.
  • Ensure that Linux-specific onboarding methods are described with equal detail and clarity as Windows methods.
  • Clarify that PowerShell is cross-platform but may not be the preferred tool for all Linux users.
  • Consider listing Linux and Windows methods separately or in parallel to avoid implicit Windows-first ordering.
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-06 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, uninstallation, and proxy configuration. However, there is a mild Windows bias: Windows examples and instructions are often presented first, and Windows-specific tools (PowerShell, Group Policy, WSUS, Configuration Manager) are described in greater detail. The cleanup script for removing stale resources is only provided in PowerShell, with no equivalent Bash or Azure CLI example for Linux users. Some Windows-specific automation and update infrastructure are discussed without Linux analogs.
Recommendations
  • Present Linux and Windows instructions in parallel or alternate order to avoid 'windows_first' bias.
  • Provide equivalent Bash or Azure CLI scripts for resource cleanup tasks, not just PowerShell.
  • Where Windows-specific tools (e.g., Group Policy, WSUS) are discussed, mention Linux equivalents (e.g., cron jobs, package managers, systemd timers) or clarify if no direct equivalent exists.
  • Ensure Linux sections are as detailed as Windows sections, especially for automation and update management.
  • Consider adding troubleshooting and automation examples for Linux environments (e.g., using shell scripts).
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-06 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 Windows-specific tools (Windows Admin Center, Windows Server Graphical Installer) are mentioned explicitly for Azure Arc deployment, while Linux equivalents are not. PowerShell is referenced as a primary scripting method, and Windows deployment options are described before Linux options. There are no explicit Linux example commands or references to Linux-native tools (e.g., SSH, Linux package managers), and Bash is only mentioned generically. This creates friction for Linux users seeking parity in deployment guidance.
Recommendations
  • Add explicit Linux deployment examples, such as using Bash scripts, SSH, or Linux package managers.
  • Mention Linux-native tools and workflows (e.g., Ansible, systemd, cron) alongside Windows tools.
  • Provide Linux-specific guidance for agent installation, configuration, and troubleshooting.
  • Ensure that Linux deployment options are described with equal prominence and detail as Windows options.
  • Include example commands for Linux environments (e.g., Bash, Azure CLI on Linux).
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-06 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 provides extensive PowerShell examples and references Windows-specific tools (such as New-AzStorageBlobSASToken and New-NetFirewallRule) throughout. Windows examples and terminology are often presented first or exclusively, especially in the REST API section, which only shows Windows firewall configuration. There is a lack of Linux-specific script examples (e.g., bash or shell scripts for Linux firewall management), and Linux usage is only briefly mentioned in notes or as an afterthought. This creates friction for Linux users, who must infer how to adapt the instructions for their systems.
Recommendations
  • Add Linux-specific script examples throughout, such as using bash or shell scripts for common administrative tasks (e.g., configuring firewall rules with iptables or ufw).
  • Provide parity in REST API examples, showing both Windows (PowerShell) and Linux (bash) scenarios.
  • When referencing tools like New-AzStorageBlobSASToken, include CLI alternatives or note how Linux users can generate SAS tokens.
  • Ensure that both Windows and Linux are equally represented in introductory and example sections, rather than presenting Windows first.
  • Clarify OS-specific requirements and limitations in each example, not just in notes.
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-06 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy
Summary
The documentation provides recovery instructions and a downloadable script only for Windows environments, specifically using PowerShell. There are no equivalent instructions, scripts, or guidance for performing the recovery from a Linux or macOS machine, nor is it stated whether such recovery is possible or not. The section is explicitly titled 'Recover Arc resource bridge from a Windows machine', and no alternative is given.
Recommendations
  • Clarify whether recovery is supported from non-Windows (Linux/macOS) environments. If not, state this explicitly to set user expectations.
  • If possible, provide equivalent recovery scripts and instructions for Linux/macOS environments (e.g., Bash, Python).
  • If the PowerShell script can be run cross-platform (e.g., with PowerShell Core), document how to do so on Linux/macOS.
  • Add a note at the top of the recovery section indicating platform support and any limitations.
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-06 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 demonstrates a notable Windows bias. The primary automation script for at-scale enablement is a PowerShell script, with instructions and scheduling examples exclusively using Windows tools (PowerShell, Task Scheduler). There are no equivalent Bash or Linux-native examples for running the script or scheduling jobs. Out-of-band methods mention Ansible but provide more detailed steps and links for Windows-centric tools (Configuration Manager, Group Policy, PowerShell). Linux users are left to infer or adapt steps, creating friction.
Recommendations
  • Provide a Bash or shell script equivalent for the auto Arc-enablement script, or clarify if the script is cross-platform.
  • Include explicit instructions and examples for running the automation script on Linux/macOS (e.g., using Bash, cron).
  • Show how to schedule the script as a cron job on Linux, not just with Windows Task Scheduler.
  • Ensure parity in out-of-band methods by providing detailed Linux automation examples (e.g., systemd timers, Bash scripts), not just referencing Ansible.
  • Clearly indicate OS compatibility for all scripts and tools.
  • Where possible, present Linux/macOS examples alongside or before Windows examples, or in parallel tabs.
GitHub Create Pull Request
← Previous Page 29 of 94 Next →