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 801-825 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-02 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, but there is a notable Windows bias: Windows tools (Admin Center, Graphical Installer) are mentioned explicitly, and PowerShell is referenced before Bash. Linux equivalents (e.g., Linux graphical installers, Linux-specific deployment tools) are not mentioned or are less prominent. Windows deployment options are described in more detail and appear first in lists.
Recommendations
  • Add explicit Linux deployment examples and tools, such as Linux graphical installers or common Linux management platforms.
  • Ensure Bash and PowerShell examples are given equal prominence, possibly showing Bash first or side-by-side.
  • Mention Linux-specific automation tools (e.g., Puppet, Chef) alongside Ansible and Configuration Manager.
  • Clarify which steps or tools are applicable to Linux, and provide links to Linux-specific guidance where available.
  • Balance the order of Windows and Linux references in lists and explanations.
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-02 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation claims support for both Windows and Linux Arc-enabled servers, but the majority of concrete examples, especially in PowerShell and REST API sections, are Windows-centric. PowerShell examples dominate, and REST API examples exclusively use Windows-specific scripts (e.g., New-NetFirewallRule). There is a lack of Linux-specific script examples (e.g., using bash or Linux firewall tools), and guidance for SAS token generation only references Windows tooling (New-AzStorageBlobSASToken). The CLI section also uses a PowerShell command as its script example. Linux is only mentioned in passing, and Linux-specific scenarios are not demonstrated.
Recommendations
  • Add Linux-specific script examples throughout, especially for common tasks such as configuring firewall rules (e.g., using iptables, ufw, or firewalld in bash scripts).
  • In the Azure CLI section, provide at least one example using a bash script (e.g., 'echo Hello World!' or a simple shell command) instead of PowerShell syntax.
  • In the REST API section, include a Linux scenario (e.g., running a bash script to configure a Linux firewall or perform a Linux-specific administrative task).
  • When referencing SAS token generation, mention cross-platform tools (e.g., Azure CLI's az storage blob generate-sas) and not just PowerShell commands.
  • Wherever possible, alternate or parallelize Windows and Linux examples to demonstrate parity and reduce friction for Linux 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-03-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation exclusively provides recovery instructions for the Azure Arc resource bridge VM from a Windows machine, using a PowerShell script. There are no examples or guidance for Linux/macOS users, nor is there mention of equivalent tools or scripts for non-Windows platforms. The Windows approach is presented as the only method, creating friction for administrators who may use Linux or macOS.
Recommendations
  • Provide equivalent recovery instructions for Linux/macOS, including Bash or Python scripts if available.
  • Clarify if the recovery process is inherently Windows-only due to dependencies (e.g., SCVMM or PowerShell), or explicitly state platform limitations.
  • If possible, offer cross-platform tools or containerized solutions to enable recovery from non-Windows environments.
  • Mention any prerequisites or limitations for Linux/macOS users, and link to relevant resources if available.
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-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. The primary automation script for Arc agent installation is a PowerShell script, with instructions and examples focused on PowerShell usage and Windows Task Scheduler for cron-like automation. Linux-specific guidance is limited to a brief sudo configuration note, and there are no Bash or Linux shell script examples. Windows tools and patterns (PowerShell, Task Scheduler) are mentioned exclusively or before Linux equivalents, and Linux automation options (e.g., cron, Bash) are not provided.
Recommendations
  • Provide equivalent Bash or shell script examples for Linux users, alongside PowerShell scripts.
  • Include instructions for running the automation script on Linux/macOS, such as using cron for scheduled tasks.
  • Clarify whether the helper script can run cross-platform, or provide a Linux-specific version if not.
  • Add Linux-first or Linux-parity examples in sections where Windows tools are referenced (e.g., Task Scheduler).
  • Expand the out-of-band methods section to include more Linux automation approaches (e.g., systemd timers, Bash scripts).
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-02 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 and script invocation, but does not offer equivalent Linux/macOS guidance. The script is referenced as a PowerShell script, and only Windows-specific instructions are given for its execution. Linux agent removal is covered, but Linux/macOS users are left without clear steps for running the deboarding script, creating friction for non-Windows users.
Recommendations
  • Add explicit instructions for running the deboarding script on Linux/macOS, including prerequisites (such as PowerShell Core installation) and command-line examples.
  • Clarify whether the script is cross-platform (PowerShell Core compatible) or Windows-only; if Windows-only, provide alternative manual steps or scripts for Linux/macOS users.
  • Present Linux/macOS instructions alongside Windows instructions, not after or omitted.
  • Mention any required tools (e.g., Azure CLI, PowerShell Core) for Linux/macOS users.
  • If the script is not cross-platform, consider providing a Bash or Python equivalent.
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-02 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-based onboarding script examples and instructions, with no mention of Bash, Linux shell, or cross-platform alternatives. All code snippets and script references assume a Windows/PowerShell environment, which may exclude or confuse Linux/macOS users managing Azure Arc-enabled VMware vSphere environments.
Recommendations
  • Provide equivalent onboarding script instructions and examples for Bash or cross-platform shells if supported.
  • Clarify in the prerequisites or introduction whether the onboarding script is only supported on Windows/PowerShell, or if there are Linux/macOS alternatives.
  • If the onboarding script is cross-platform, include both PowerShell and Bash examples, and note any OS-specific requirements.
  • Explicitly state OS requirements for running the onboarding script, so users on non-Windows platforms are aware of their options.
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-02 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools Windows First
Summary
The documentation exclusively provides a PowerShell script (`RGCleanScript.ps1`) and only demonstrates usage via PowerShell commands. There are no examples or instructions for running the clean-up script on Linux or macOS, nor is there mention of a cross-platform or Bash/sh alternative. This creates friction for non-Windows users who may not have access to PowerShell or cannot run `.ps1` scripts natively.
Recommendations
  • Provide a Bash or shell script alternative (e.g., `RGCleanScript.sh`) for Linux/macOS users, or clarify if the PowerShell script is compatible with PowerShell Core (pwsh) on all platforms.
  • Include explicit instructions for running the script on Linux/macOS, such as using PowerShell Core (`pwsh`) if supported.
  • Add example commands for Linux/macOS environments, and note any prerequisites (e.g., installing PowerShell Core).
  • If the script is truly Windows-only, clearly state this limitation at the top of the documentation.
GitHub Create Pull Request
Azure Arc Diagnostics of Edge-Related Logs and Errors in Workload Orchestration .../azure-arc/workload-orchestration/diagnose-problems.md
Medium Priority View Details →
Scanned: 2026-03-02 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 page exhibits a notable Windows/PowerShell bias. All provided automation and scripting examples use PowerShell scripts (e.g., .ps1 files and PowerShell syntax), and file paths in JSON templates use Windows-style paths (e.g., C:\Users\...). There are no equivalent Bash/shell scripts or Linux/macOS command-line examples. The use of PowerShell is assumed throughout, and Linux users are not provided with guidance for adapting the instructions. Additionally, Windows paths and tools are referenced before any cross-platform alternatives.
Recommendations
  • Provide equivalent Bash or shell script examples for all PowerShell scripts, especially for onboarding and enabling diagnostics.
  • Use cross-platform file path examples (or note how to adapt them for Linux/macOS) in JSON templates and documentation.
  • Explicitly state if the provided scripts are only supported on Windows, and offer guidance or references for Linux/macOS users if possible.
  • Where Azure CLI commands are shown, use shell-agnostic syntax or provide both PowerShell and Bash variants.
  • Add notes or sections for Linux/macOS users, clarifying any differences in setup or troubleshooting.
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-02 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 Windows-centric, and there are no Bash or cross-platform options discussed.
Recommendations
  • Clarify whether the PowerShell script is compatible with PowerShell Core (pwsh) on Linux/macOS, and provide instructions for running it on those platforms if applicable.
  • If the script is Windows-only, offer a Bash or Python alternative for Linux/macOS users, or explicitly state that Linux/macOS users must use Windows or PowerShell Core.
  • Add examples for running the migration on Linux/macOS, including any prerequisites or dependencies.
  • Mention any limitations or required adaptations for non-Windows 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-02 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 all CLI examples and references PowerShell scripts (e.g., bulk_deployment.ps1, workflow-delete.ps1) without providing equivalent Bash or shell script examples. There is no mention of Linux/macOS usage or alternative scripting approaches, and the PowerShell examples are presented as the default/only option, which may create friction for Linux/macOS users.
Recommendations
  • Provide CLI examples in Bash syntax alongside PowerShell, especially for az CLI commands, which are cross-platform.
  • Offer equivalent Bash or shell scripts for bulk_deployment.ps1 and workflow-delete.ps1, or explain how Linux/macOS users can achieve the same workflow.
  • Explicitly state that az CLI commands work on all platforms and clarify any platform-specific requirements for scripts.
  • Add notes or sections addressing Linux/macOS users, including troubleshooting or usage tips.
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-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation exhibits Windows bias in several areas. The kubectl installation command uses 'winget', a Windows-only tool, with no Linux/macOS alternative provided. The file extraction example in the Bash tab uses 'Expand-Archive', which is a PowerShell/Windows command, rather than standard Linux/macOS tools like 'unzip'. Throughout, Windows tools and patterns are mentioned or shown first, and Linux/macOS equivalents are missing or not prioritized. This creates friction for non-Windows users, especially in initial setup steps.
Recommendations
  • Provide Linux/macOS-specific instructions for installing kubectl (e.g., using 'curl' or 'apt', 'brew').
  • Replace or supplement 'Expand-Archive' in Bash examples with 'unzip' or 'tar' commands for Linux/macOS users.
  • Ensure Bash examples use cross-platform commands and avoid Windows-specific paths and tools.
  • Clearly indicate which commands are Windows-only and provide parity for Linux/macOS wherever possible.
  • Review the ordering of examples so that Linux/macOS instructions are not always secondary or omitted.
GitHub Create Pull Request
Azure Arc Troubleshooting for Workload Orchestration ...es/azure-arc/workload-orchestration/troubleshooting.md
Medium Priority View Details →
Scanned: 2026-03-02 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The troubleshooting guidance for workload orchestration is heavily biased toward PowerShell and Windows-style command usage. Most examples, including those for az CLI, kubectl, and Docker, are presented in PowerShell syntax (with variables like $var and PowerShell-specific constructs), and there are no equivalent Bash/Linux shell examples for the majority of the troubleshooting steps. Only in the 'Troubleshoot service groups' section are both Bash and PowerShell examples provided. This creates friction for Linux/macOS users, who may not be familiar with PowerShell syntax or variable usage.
Recommendations
  • For all az CLI, kubectl, and Docker command examples, provide both Bash and PowerShell versions, using appropriate variable syntax for each shell.
  • Where PowerShell-specific constructs are used (e.g., ConvertTo-Json, Out-File, [Convert]::ToBase64String), provide equivalent Bash/Linux commands (e.g., jq, echo, base64, etc.).
  • Avoid using PowerShell variable syntax ($var) in generic CLI examples; instead, use placeholders or Bash-style variables where appropriate.
  • Clearly indicate which commands are for Windows/PowerShell and which are for Bash/Linux/macOS, using tabbed sections as done in the 'Troubleshoot service groups' section.
  • Review all troubleshooting steps to ensure Linux/macOS users can follow them without needing to translate PowerShell commands.
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-01 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools
Summary
The documentation is focused on Linux preparation for AKS Edge Essentials, but it uses Windows-specific PowerShell cmdlets (Invoke-AksEdgeNodeCommand) to configure Linux nodes. This assumes the administrator is working from a Windows environment and does not provide native Linux shell alternatives for critical steps, creating friction for Linux/macOS users.
Recommendations
  • Provide equivalent Linux-native commands for sysctl configuration steps, such as using SSH or direct shell access.
  • Clarify whether Invoke-AksEdgeNodeCommand is required, and if so, offer guidance for Linux/macOS users (e.g., using SSH or Azure CLI).
  • Ensure all configuration steps can be performed from a Linux or macOS workstation, not just Windows/PowerShell.
  • Add Linux shell examples alongside PowerShell examples where applicable.
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-01 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 PowerShell syntax, specifically with the sqlcmd tool, but does not offer equivalent Linux/macOS shell examples. The use of PowerShell syntax (e.g., command blocks labeled as 'powershell') and the absence of bash or Linux shell alternatives may create friction for Linux/macOS users. Additionally, Windows-oriented command blocks are presented first and exclusively, despite the Azure Arc Data Controller being a cross-platform Kubernetes workload.
Recommendations
  • Provide Linux/macOS shell (bash) examples alongside PowerShell examples, especially for commands using kubectl and sqlcmd.
  • Label command blocks appropriately (e.g., 'console', 'bash', 'powershell') to clarify which platforms are supported.
  • Explicitly mention that sqlcmd is available cross-platform and provide installation instructions for Linux/macOS if needed.
  • Ensure that all steps can be performed on Linux/macOS, and highlight any platform-specific differences.
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-01 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 paths and examples first (e.g., backup file paths like C:\Backupfiles\test.bak), and omits explicit Linux/macOS equivalents for key steps such as database backup and file copying. Tools like Visual Studio Code and Azure Storage Explorer are cross-platform, but all file path and command examples default to Windows conventions, which may confuse Linux/macOS users.
Recommendations
  • For every example using a Windows file path (e.g., C:\Backupfiles\test.bak), provide a Linux/macOS equivalent (e.g., /home/user/backup/test.bak) alongside.
  • Explicitly mention that Visual Studio Code and Azure Storage Explorer are cross-platform, and provide links or notes for Linux/macOS installation if relevant.
  • In kubectl cp examples, show both Windows and Linux/macOS source file path formats.
  • Clarify that SQL Server Management Studio (SSMS) is Windows-only, and suggest Azure Data Studio or sqlcmd as alternatives for Linux/macOS users.
  • Add a note in prerequisites or relevant steps indicating that all steps are supported on Linux/macOS unless otherwise stated.
GitHub Create Pull Request
Azure Arc Data collection and reporting | Azure Arc-enabled data services ...zure-arc/data/privacy-data-collection-and-reporting.md
Medium Priority View Details →
Scanned: 2026-03-01 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation is generally cross-platform, focusing on Azure Arc-enabled data services, which run on Kubernetes and are managed via Azure CLI. However, in the 'Arc-enabled SQL Server' billing data example, the payload includes 'osType': 'Windows', 'manufacturer': 'Microsoft', and 'model': 'Hyper-V', which are Windows-specific. There are no Linux/macOS equivalents or examples provided for this section, and Windows terminology appears first and exclusively in this context.
Recommendations
  • Add Linux-based billing data examples for Arc-enabled SQL Server, showing payloads with 'osType': 'Linux', and relevant Linux VM details.
  • Clarify whether the billing data structure is identical for Linux-based SQL Server instances, or note any differences.
  • Where possible, provide parity in examples for both Windows and Linux environments, especially in sections where OS-specific fields are shown.
  • Explicitly state if certain features or reporting fields are Windows-only, to avoid confusion for Linux users.
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-01 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools
Summary
The documentation page lists several Windows-centric tools (SSMS, SQL Server Data Tools, SQL Server PowerShell, SQL Server Profiler) and explicitly mentions PowerShell scripting support as a manageability feature. However, it also includes cross-platform tools such as Azure CLI and Visual Studio Code extension. No Linux/macOS-specific tools or examples are provided, and Windows tools are presented as standard options without Linux alternatives.
Recommendations
  • Add examples or mention of Linux/macOS-compatible tools for managing SQL Managed Instance enabled by Azure Arc, such as sqlcmd, Azure Data Studio, or relevant open-source SQL management tools.
  • Clarify which tools are cross-platform and which are Windows-only, especially for SSMS, SQL Server PowerShell, and SQL Server Profiler.
  • Include guidance or links for Linux/macOS users on how to perform common management tasks (e.g., scripting, backup, monitoring) using supported tools.
  • Consider listing Azure CLI and Visual Studio Code extension before Windows-only tools to emphasize cross-platform options.
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-01 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 network issues (e.g., Invoke-WebRequest), Windows paths are shown in error messages, and Windows-specific tools (RDP, remote PowerShell) are discussed. Linux troubleshooting commands are rarely provided, and Linux equivalents for CLI operations or network diagnostics are missing. In some sections, Windows tools and patterns are mentioned first or exclusively, creating friction for Linux/macOS users.
Recommendations
  • Provide Linux/macOS equivalents for PowerShell commands (e.g., use curl or wget for HTTP/2 troubleshooting).
  • Include Linux/macOS examples for CLI operations, such as collecting logs, checking DNS resolution, and network connectivity (e.g., use nslookup, dig, ping, curl).
  • Mention Linux file paths and permission troubleshooting alongside Windows paths.
  • Clarify when instructions are platform-specific and offer alternatives for other OSes.
  • Add troubleshooting steps for common Linux/macOS issues (e.g., glibc errors, SSH folder permissions).
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-01 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides release notes for both Windows and Linux versions of the Azure Connected Machine agent. However, Windows examples, tools, and troubleshooting steps are often presented first or exclusively (e.g., command prompt and PowerShell commands for editing config files, installer instructions for Windows). Windows-specific improvements and issues are described in detail, while Linux equivalents are sometimes missing or less emphasized. Download links and version tables consistently list Windows before Linux.
Recommendations
  • Include Linux-specific troubleshooting steps and command examples alongside Windows instructions, especially in the 'Known Issues' section.
  • When listing download links, alternate the order or present both platforms equally.
  • Add Linux command-line examples (e.g., chmod/chown for config file permissions) where only Windows commands are given.
  • Ensure parity in explanations for installer issues (e.g., provide guidance for Linux package managers or service management).
  • Highlight Linux improvements and bug fixes with equal detail as Windows items.
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-03-01 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation provides authentication options for both Windows and Linux, but it introduces Windows-specific methods first and references Windows tools (such as Get-AzAccessToken) without mentioning Linux equivalents. The 'Interactive browser login' is labeled as Windows-only and described first, and certificate store authentication is only detailed for Windows. Access token acquisition is shown via PowerShell, with no Linux CLI example. Overall, Linux parity is mostly present, but Windows-specific methods and tools are prioritized or exclusively described.
Recommendations
  • Present authentication options in a neutral order (not Windows-first).
  • For access token acquisition, provide both PowerShell (Windows) and Azure CLI (Linux/macOS) examples (e.g., 'az account get-access-token').
  • Clarify certificate-based authentication for Linux (e.g., how to use PEM/PFX files on Linux, file permissions, etc.).
  • Explicitly state which authentication options are available on Linux/macOS and provide relevant examples.
  • Where Windows certificate store options are described, mention Linux equivalents or clarify that they are not available.
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-01 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, and uninstall instructions for multiple Linux distributions. However, Windows examples and tools (such as PowerShell scripts, Microsoft Update, Group Policy, and Control Panel) are often presented first or in greater detail. The cleanup script for stale Arc resources is only provided in PowerShell, with no Linux/bash equivalent. Windows-specific management tools are discussed in depth, while Linux equivalents (e.g., using bash or shell scripts for automation) are not mentioned.
Recommendations
  • Provide bash or shell script examples for resource cleanup, similar to the PowerShell script, to assist Linux users.
  • Where possible, present Linux and Windows instructions in parallel or in a neutral order, rather than Windows first.
  • Include references to Linux-native automation tools (e.g., cron, systemd, shell scripting) for agent lifecycle management.
  • Expand guidance for Linux users on managing agent upgrades and configuration at scale, similar to the Windows Group Policy and WSUS sections.
  • Consider adding notes or links for Linux users on how to automate tasks using Azure CLI or scripting.
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-01 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page presents both Linux and Windows onboarding options for the Azure Connected Machine agent, but there is a notable emphasis on Windows-specific tools and PowerShell-based methods. PowerShell is mentioned as a cross-platform option, but several onboarding methods (e.g., Windows Admin Center, Configuration Manager, Group Policy) are Windows-only and listed separately. Additionally, the PowerShell method is highlighted before Linux-native automation tools like Ansible, and Windows-specific methods are detailed more extensively.
Recommendations
  • Ensure Linux-native automation tools (e.g., Bash scripts, shell commands, Ansible, Puppet, Chef) are given equal prominence and example coverage as PowerShell.
  • Add explicit Linux/macOS onboarding examples for each method where possible, especially for interactive and at-scale deployments.
  • Consider grouping Windows-only methods in a separate section to clarify their scope and avoid overshadowing cross-platform options.
  • Where PowerShell is used as a cross-platform tool, clarify its compatibility and provide alternative Linux-native command/script examples.
  • Review linked pages to ensure Linux onboarding steps are as detailed as Windows ones.
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-01 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Linux and Windows ARM template examples for all VM extensions, ensuring parity in template content. However, all deployment instructions and sample commands are exclusively given in PowerShell, with no Azure CLI or Bash equivalents. PowerShell is a Windows-centric tool, although it is available cross-platform. Additionally, PowerShell deployment commands are presented first and exclusively, which may create friction for Linux/macOS users who prefer Azure CLI or Bash. Minor bias is also present in the ordering of Windows examples (sometimes Windows template shown before Linux), but both OSes are covered.
Recommendations
  • Add Azure CLI deployment command examples alongside PowerShell for deploying ARM templates, e.g., 'az deployment group create --resource-group <resource-group-name> --template-file <template-filename.json> --parameters @<parameter-filename.json>'.
  • Explicitly state that PowerShell commands work cross-platform, but provide CLI/Bash alternatives for Linux/macOS users.
  • Where possible, alternate the order of Linux and Windows template examples, or group them together to avoid implicit prioritization.
  • Clarify in the prerequisites or intro that both PowerShell and Azure CLI can be used for deployment, linking to relevant docs.
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-01 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides recovery instructions exclusively for Windows, including a PowerShell script and Windows-centric steps. There are no Linux/macOS examples, nor is there mention of equivalent recovery scripts or procedures for non-Windows platforms. The section is titled 'Recover Arc resource bridge from a Windows machine,' and no alternative is offered for Linux users.
Recommendations
  • Provide equivalent recovery instructions for Linux/macOS, including Bash or Python scripts.
  • Clarify whether the recovery process is supported or unsupported on Linux/macOS platforms.
  • If Windows is required, explicitly state this limitation and explain why.
  • Offer guidance for Linux users, such as alternative tools or manual steps, if possible.
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-01 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 claims support for both Windows and Linux Arc-enabled servers, but the majority of concrete examples (especially in PowerShell and REST API sections) are Windows-centric. PowerShell examples dominate, and REST API examples exclusively show Windows commands (e.g., New-NetFirewallRule), with no Linux shell or firewall (e.g., iptables, firewalld) equivalents. The Azure CLI section uses a PowerShell command as its script example, and there are references to Windows tools (e.g., .ps1 scripts, New-AzStorageBlobSASToken) without Linux alternatives. Linux-specific guidance is minimal and often relegated to notes or brief mentions.
Recommendations
  • For every PowerShell example, provide a parallel Bash/shell example for Linux (e.g., using bash scripts, sh, or common Linux commands).
  • In the REST API section, include Linux-focused scenarios (e.g., using iptables or ufw to configure firewall rules) alongside the Windows examples.
  • In Azure CLI examples, use Linux shell scripts (e.g., echo "Hello World!" or id) as the script payload, not PowerShell.
  • When referencing script files, show both .ps1 (PowerShell) and .sh (Bash) file examples.
  • When discussing SAS token generation, mention az CLI equivalents (e.g., az storage blob generate-sas) for Linux users.
  • Add a table or section summarizing any OS-specific limitations or differences in parameter handling.
GitHub Create Pull Request
← Previous Page 33 of 94 Next →