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 1351-1375 of 2334 flagged pages
Azure Arc Azure CLI Requests for the Run Command on Azure Arc-enabled Servers (Preview) ...lob/main/articles/azure-arc/servers/run-command-cli.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page provides only PowerShell/Windows-style script examples (e.g., 'Write-Host Hello World!') when demonstrating Azure CLI usage, without any Linux shell (bash/sh) script examples. This may confuse or exclude Linux/macOS users, as it is unclear how to use the feature with bash scripts. The terminology and scripting patterns are Windows-centric.
Recommendations
  • Provide parallel Linux/bash shell script examples (e.g., --script "echo Hello World!") alongside PowerShell examples.
  • Explicitly state that both PowerShell and bash scripts are supported, if applicable, and clarify any OS-specific behaviors.
  • Add a section or table showing example scripts for both Windows and Linux Arc-enabled servers.
  • Avoid using only Windows scripting constructs (like Write-Host) in generic CLI documentation.
GitHub Create Pull Request
Azure Arc Configuration and remote access ...es/azure-arc/servers/security-machine-configuration.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a notable Windows bias. Azure Machine Configuration is described as PowerShell DSC-based, with no mention of Linux-native configuration tools or examples. Windows Admin Center (WAC) is highlighted as a primary remote management tool, with a dedicated section and detailed explanation, while Linux management is only briefly mentioned in the context of SSH. Examples and tooling references (PowerShell, WAC) are Windows-centric, and there are no Linux-specific configuration or remote access examples (e.g., using Ansible, SSH command-line, or Linux admin tools). Windows scenarios and tools are described in greater detail and appear before Linux equivalents.
Recommendations
  • Add Linux-native configuration examples, such as using Ansible, Chef, or native SSH commands.
  • Provide parity in remote management tooling by mentioning Linux equivalents to Windows Admin Center, or clarify how Linux servers are managed interactively.
  • Include Linux-specific RBAC role assignment and authentication flows, with step-by-step examples.
  • Balance the order and detail of Windows and Linux sections to ensure equal visibility and guidance.
  • Explicitly state PowerShell DSC limitations or alternatives for Linux environments.
GitHub Create Pull Request
Azure Arc Security overview ...b/main/articles/azure-arc/servers/security-overview.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. It references Windows-specific concepts (such as NT SERVICE accounts, Local System, Network Service) before their Linux equivalents, and describes guest configuration policies as being written in PowerShell Desired State Configuration without mentioning Linux alternatives. The example extension allowlist references only Windows agents, and there are no explicit Linux/macOS command or extension examples. The documentation also uses Windows terminology and patterns first, with Linux details as secondary notes.
Recommendations
  • Provide explicit Linux/macOS examples alongside Windows ones, especially for extension allowlists and agent configuration.
  • Mention Linux equivalents for guest configuration policies, such as Ansible or native Linux configuration management tools, if supported.
  • Include Linux/macOS agent extension IDs in allowlist examples.
  • Clarify whether PowerShell Desired State Configuration is required on Linux, or if there are alternative mechanisms.
  • Balance terminology by listing Linux service accounts and patterns before or alongside Windows ones.
GitHub Create Pull Request
Azure Arc Security onboarding and updates ...main/articles/azure-arc/servers/security-onboarding.md
Medium Priority View Details →
Scanned: 2026-01-13 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 page exhibits a moderate Windows bias. Windows-specific tools and patterns (Group Policy, WSUS, Microsoft Update) are mentioned before or in more detail than their Linux equivalents. PowerShell is referenced for extension management and onboarding, with no equivalent Linux shell examples. Some onboarding methods are described as Windows-only, and links to Windows-specific guidance are provided, while Linux automation tools (e.g., Ansible) are only briefly mentioned. Linux update mechanisms are covered, but with less detail and fewer actionable examples.
Recommendations
  • Provide Linux shell (bash) examples alongside PowerShell for onboarding and extension management tasks.
  • Include links to Linux-specific onboarding and automation guidance, similar to the Group Policy onboarding link for Windows.
  • Expand coverage of Linux automation tools (e.g., Ansible, Chef, Puppet) with concrete examples for protecting secrets and orchestrating onboarding.
  • Present update management instructions for Linux (e.g., using apt/yum/zypper) with step-by-step guidance, not just a brief mention.
  • Ensure that Linux tools and patterns are described with equal detail and prominence as Windows tools.
  • Where features are Windows-only (e.g., interactive logon via local browser), clearly state Linux alternatives or workarounds.
GitHub Create Pull Request
Azure Arc Troubleshoot SSH access to Azure Arc-enabled servers ...ain/articles/azure-arc/servers/ssh-arc-troubleshoot.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a notable Windows bias. Troubleshooting steps and examples frequently reference Azure PowerShell modules (Az.Ssh, Az.Ssh.ArcProxy) and provide PowerShell commands for module management and error resolution. The guidance for resolving client-side issues is centered around PowerShell and Windows-specific error messages, with Linux equivalents mentioned less prominently or only as error output. Examples for enabling SSH on the server are given for both Azure CLI and PowerShell, but PowerShell is emphasized throughout the document. There is limited coverage of Linux/macOS workflows, and no explicit Linux/macOS installation or troubleshooting steps for the Azure CLI or SSH client tools are provided.
Recommendations
  • Add explicit Linux/macOS troubleshooting steps, including installation and path configuration for SSH clients and Azure CLI.
  • Provide Linux/macOS-specific error messages and their resolutions alongside Windows/PowerShell examples.
  • Include Bash or shell command alternatives for PowerShell module management and SSH connectivity.
  • Ensure examples and instructions for Azure CLI are shown before or alongside PowerShell, not after.
  • Clarify which steps are platform-agnostic and which are platform-specific, and provide parity for both.
GitHub Create Pull Request
Azure Arc Tutorial - Monitor a hybrid machine with Azure Monitor VM insights ...icles/azure-arc/servers/tutorial-enable-vm-insights.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides a general tutorial for enabling VM insights on hybrid machines, claiming support for both Linux and Windows. However, when discussing log events, it only references the Windows event log and does not provide equivalent Linux log examples (e.g., syslog). The Event table is described as containing Windows event log data, with no mention of Linux log sources or queries. There are no Linux-specific screenshots, examples, or instructions, and Windows terminology (event log) is used exclusively in the data viewing section.
Recommendations
  • Add explicit examples and screenshots for Linux machines, showing how Linux logs (such as syslog or journald) are collected and queried.
  • Clarify what tables and data are available for Linux machines in Log Analytics, and provide sample queries.
  • Use neutral terminology when describing log events (e.g., 'system logs') and mention both Windows and Linux sources.
  • Ensure parity in instructions and visuals for both platforms throughout the tutorial.
GitHub Create Pull Request
Azure Arc Overview of the Azure Arc-enabled System Center Virtual Machine Manager ...-arc/system-center-virtual-machine-manager/overview.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. It focuses on System Center Virtual Machine Manager (SCVMM), a Windows-only tool, and repeatedly references Windows-specific management features (e.g., Windows Server management, Windows registry, Windows services). PowerShell is mentioned as a primary automation tool, and Windows-centric update and configuration scenarios are highlighted before Linux equivalents. Linux support is mentioned but not detailed, and examples or guidance for Linux users are minimal or absent.
Recommendations
  • Add explicit examples and guidance for Linux VM management, including onboarding, configuration, and monitoring steps.
  • Provide parity in automation examples (e.g., Bash, Python scripts for Linux alongside PowerShell for Windows).
  • Highlight Linux-specific features and scenarios where applicable, such as Linux daemon management, package updates, and security hardening.
  • Clarify which features are Windows-only and which are cross-platform, to help Linux/macOS users understand applicability.
  • Include links to Linux-focused documentation and best practices for hybrid management.
GitHub Create Pull Request
Azure Arc Create custom roles with Azure Arc-enabled SCVMM ...-center-virtual-machine-manager/create-custom-roles.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation focuses on Azure Arc-enabled SCVMM, a Windows-centric virtualization manager, and describes custom role creation exclusively through the Azure portal. While it mentions Azure PowerShell and Azure CLI as alternatives, the main instructions and screenshots are portal-based, which is platform-neutral but implicitly Windows-oriented due to SCVMM's Windows-only nature. There are no Linux/macOS-specific examples or guidance, and the documentation does not address cross-platform considerations for CLI or scripting.
Recommendations
  • Explicitly mention that Azure CLI is cross-platform and provide CLI examples for custom role creation.
  • Clarify any platform requirements for SCVMM and role management, especially for users on Linux/macOS.
  • Add a section comparing Azure PowerShell and Azure CLI usage for custom roles, highlighting Linux/macOS compatibility.
  • Include links or references to Linux/macOS setup guides for Azure CLI.
  • State limitations for non-Windows users, if any, and suggest workarounds.
GitHub Create Pull Request
Azure Arc Deliver ESUs for SCVMM VMs through Arc ...ver-esus-for-system-center-virtual-machine-manager-vms.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily focused on Windows Server 2012/2012 R2 VMs managed by SCVMM, with all examples, terminology, and processes centered around Windows environments. Windows-specific tools (SCVMM, WSUS, Microsoft Endpoint Configuration Manager) are mentioned exclusively or before alternatives, and there are no Linux/macOS examples or guidance for non-Windows VMs. The documentation does not address how Linux or macOS VMs could participate in ESU delivery or management through Arc in this scenario.
Recommendations
  • Clarify early in the documentation that the process is specific to Windows Server 2012/2012 R2 and SCVMM-managed VMs, and explicitly state that Linux/macOS VMs are not supported for ESU delivery in this workflow.
  • If Azure Arc supports similar patching or management workflows for Linux/macOS VMs, provide links or references to those workflows for parity.
  • When listing patch management solutions, mention Linux-compatible options (e.g., Ansible, Chef, native Linux update tools) and clarify their applicability.
  • Consider adding a section or FAQ addressing Linux/macOS scenarios, even if only to state their exclusion and suggest alternatives.
GitHub Create Pull Request
Azure Arc Install Arc agent on SCVMM VMs ...al-machine-manager/enable-guest-management-at-scale.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation exhibits a moderate Windows bias: Windows operating systems and tools are mentioned first and more prominently, especially in the Azure portal section, which is only available for Windows VMs. Windows-specific tools like PowerShell and Group Policy are referenced before Linux equivalents. However, Linux support is present via scripts and Ansible, and Linux instructions are included in the manual installation section.
Recommendations
  • Explicitly state Linux support and parity in the introduction and relevant sections.
  • Provide Linux examples and instructions alongside Windows, not after or as exceptions.
  • List Linux automation tools (e.g., Ansible, shell scripts) before or alongside Windows tools (e.g., PowerShell, Group Policy) in out-of-band methods.
  • Clarify which features are Windows-only and offer alternative workflows for Linux users.
  • Add screenshots and walkthroughs for Linux VM onboarding where possible.
GitHub Create Pull Request
Azure Arc Quickstart for Azure Arc-enabled System Center Virtual Machine Manager (SCVMM) ...t-connect-system-center-virtual-machine-manager-to-arc.md
Medium Priority View Details →
Scanned: 2026-01-13 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 demonstrates a moderate Windows bias. Windows-specific tools (PowerShell, WinRM, tar.exe, archiveint.dll) are discussed in detail, and Windows instructions are presented before Linux equivalents. Prerequisites and troubleshooting focus on Windows environments, with Linux guidance being less detailed and sometimes described as slower or less performant. Some steps, such as copying tar.exe and archiveint.dll, are only relevant to Windows, and there is no mention of Linux alternatives or troubleshooting steps for Linux users.
Recommendations
  • Provide Linux-first or side-by-side examples for all steps, including troubleshooting and prerequisites.
  • Offer detailed Linux prerequisites (e.g., required packages, permissions, dependencies) and troubleshooting guidance.
  • Avoid language that discourages Linux usage (e.g., 'deployment takes a bit longer'), or provide actionable advice to mitigate performance issues.
  • List Linux tools and commands where Windows tools are mentioned (e.g., alternatives to WinRM, tar.exe, archiveint.dll).
  • Ensure parity in script functionality and documentation for both PowerShell and Bash versions.
GitHub Create Pull Request
Azure Arc Support matrix for Azure Arc-enabled System Center Virtual Machine Manager ...pport-matrix-for-system-center-virtual-machine-manager.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. Windows Server and SCVMM (a Windows-only product) are naturally central, but the page repeatedly references Windows-specific tools and patterns (e.g., WinRM, Windows Management Framework, PowerShell/Win32-OpenSSH), and provides more detail for Windows environments. Linux is mentioned only in passing, with minimal guidance and no concrete examples or parity in troubleshooting or deployment steps. The only Linux-specific note is that deployments from Linux workstations may be slower, but no Linux-specific instructions or optimizations are provided.
Recommendations
  • Provide explicit Linux workstation deployment instructions, including any required dependencies, troubleshooting steps, and performance tips.
  • Where Windows-specific tools (e.g., WinRM, Windows Management Framework) are mentioned, clarify their Linux equivalents or note if not applicable.
  • Include Linux examples or callouts wherever scripts or commands are referenced, especially for onboarding and agent installation.
  • Balance the order of presentation so that Linux and Windows requirements/examples are given equal prominence.
  • Clarify any limitations or differences for Linux users up front, and link to relevant Linux documentation where possible.
GitHub Create Pull Request
Azure Arc Deliver ESUs for VMware VMs through Arc ...r-extended-security-updates-for-vmware-vms-through-arc.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation is exclusively focused on managing Extended Security Updates (ESUs) for Windows Server 2012/2012 R2 VMs via Azure Arc on VMware vSphere. All examples, screenshots, and instructions pertain to Windows Server environments, with no mention of Linux VMs, Linux patching tools, or cross-platform considerations. Windows-centric patching solutions (WSUS, Microsoft Updates, Configuration Manager) are referenced, while Linux equivalents are absent.
Recommendations
  • Clarify early in the document that the ESU process described is Windows-specific, and note whether Linux VMs are supported or not.
  • If Azure Arc supports similar update management for Linux VMs, add parallel instructions and examples for Linux environments.
  • Reference Linux patch management solutions (e.g., Azure Update Manager for Linux, third-party Linux patching tools) where appropriate.
  • Include a section or note about ESU applicability to non-Windows operating systems, if relevant.
  • Ensure screenshots and UI descriptions indicate OS scope (e.g., 'Windows Server VMs only').
GitHub Create Pull Request
Azure Arc What's new in Azure Arc-enabled SCVMM ...arc/system-center-virtual-machine-manager/whats-new.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation page for Azure Arc-enabled SCVMM exhibits a moderate Windows bias. Windows-centric tools (SCVMM, PowerShell, Windows Server Management, Group Policy, System Center Configuration Manager) are mentioned exclusively or before Linux alternatives. Examples and features are often described in terms of Windows tooling, with Linux-native approaches (e.g., Ansible) only occasionally referenced and never prioritized. There are no explicit Linux/macOS examples or instructions, and the documentation assumes familiarity with Windows environments.
Recommendations
  • Add explicit Linux/macOS examples for agent installation and VM management, such as shell scripts, systemd unit files, or Linux-native automation tools.
  • Include parity in documentation for Linux-based VM management, e.g., using Azure CLI, REST API, or SDKs on Linux.
  • Mention Linux equivalents alongside Windows tools (e.g., contrast Group Policy with Linux configuration management tools).
  • Provide guidance for integrating SCVMM with Linux VMs or hybrid environments, if supported.
  • Ensure that cross-platform automation tools (like Ansible) are given equal prominence and detailed examples.
GitHub Create Pull Request
Azure Arc Azure Arc agent ...n/articles/azure-arc/vmware-vsphere/azure-arc-agent.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page presents Windows agent installation details before Linux, with more granular information about Windows-specific tools, services, accounts, and troubleshooting paths. Windows terminology (MSI, Group Policy, NT SERVICE accounts) is emphasized, and Windows examples (directory paths, service names) are listed first. Linux instructions are present and reasonably detailed, but the overall structure and depth favor Windows, which may create friction for Linux users seeking parity.
Recommendations
  • Present Linux and Windows agent installation details in parallel sections or alternate which OS is described first.
  • Provide equivalent depth for Linux, including details on service accounts, security groups, and troubleshooting steps.
  • Include Linux-specific tips for permissions, service management (systemd), and log file analysis.
  • Avoid Windows-centric terminology (e.g., MSI, Group Policy) without Linux equivalents or explanations.
  • Ensure all examples (paths, commands) are shown for both platforms, and highlight differences clearly.
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-01-13 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 page demonstrates a notable Windows bias. The primary automation script is a PowerShell script, with instructions and examples focused on Windows environments (PowerShell terminal, Windows Task Scheduler for cron jobs). There is no equivalent Linux shell script or example for running at scale on Linux/macOS, nor are Linux scheduling tools (like cron) mentioned. Out-of-band methods reference Ansible (Linux-friendly), but most step-by-step guidance and examples are Windows-centric, with Linux-specific instructions limited to a sudo configuration note.
Recommendations
  • Provide a Bash or Python script equivalent for Linux/macOS users, with usage instructions.
  • Include examples for running the automation script on Linux (e.g., using cron, shell commands).
  • Mention Linux-native scheduling tools (cron, systemd timers) alongside Windows Task Scheduler.
  • Ensure all automation steps and prerequisites are covered for both Windows and Linux environments.
  • Present examples for both platforms in parallel, or clearly indicate platform-specific instructions.
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-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exclusively provides instructions and examples for running a PowerShell script (RGCleanScript.ps1) to clean up Azure resources. All usage examples are in PowerShell syntax, and there is no mention of Linux/macOS-compatible alternatives (such as Bash scripts or cross-platform instructions). The documentation assumes the user is on Windows or has PowerShell available, which may not be the case for many Linux/macOS users.
Recommendations
  • Provide equivalent Bash or shell script examples for Linux/macOS users.
  • Clarify whether the PowerShell script can be run using PowerShell Core (pwsh) on Linux/macOS, and provide instructions for doing so.
  • Offer guidance on installing PowerShell on non-Windows platforms if the script is not available in another format.
  • Consider providing a cross-platform script (e.g., written in Python or Bash) or instructions for using Azure CLI directly for resource cleanup.
  • Explicitly state platform compatibility and any prerequisites for non-Windows 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-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page exhibits a moderate Windows bias. Windows-specific management features (e.g., Windows Server management, Extended Security Updates for Windows Server and SQL Server) are highlighted, and Windows tools (PowerShell, Windows registry, Windows-specific tabs/links) are mentioned before or more prominently than their Linux equivalents. While Linux is referenced in some scenarios (e.g., Azure Update Manager, VM extensions), examples and links often default to Windows, and Linux-specific instructions or parity are less visible or absent.
Recommendations
  • Provide explicit Linux/macOS examples and instructions alongside Windows ones, especially for agent installation, automation, and VM extension management.
  • Ensure links and tabs (e.g., for Azure Automation, VM extensions) include Linux-focused content and are not Windows-default.
  • Highlight Linux management features and benefits equally with Windows, including security, update, and monitoring scenarios.
  • Include CLI/bash examples and Linux-native automation tools (e.g., shell scripts) where PowerShell is referenced.
  • Clarify any limitations or differences for Linux/macOS users in supported scenarios and next steps.
GitHub Create Pull Request
Azure Arc Plan for deployment ...phere/support-matrix-for-arc-enabled-vmware-vsphere.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific tools (PowerShell, .NET Framework) are explicitly listed as requirements, while Linux requirements are more generic. Windows tools are mentioned first and with download links, whereas Linux requirements lack similar guidance. No Linux-specific examples or troubleshooting are provided, and Windows-centric URLs (e.g., *.servicebus.windows.net for Windows Admin Center) are highlighted.
Recommendations
  • Provide Linux-specific installation instructions and troubleshooting steps, equivalent to the Windows guidance.
  • Include download links or package manager commands for Linux prerequisites (e.g., systemd, wget).
  • Offer example commands for both Windows (PowerShell) and Linux (bash/shell) when referencing onboarding scripts or agent installation.
  • Balance the order of presentation so Linux requirements/examples are not always listed after Windows.
  • Clarify which URLs are relevant for Linux scenarios (e.g., SSH) versus Windows Admin Center.
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-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation consistently uses PowerShell syntax for CLI commands and references PowerShell scripts (.ps1) for automation, without providing Bash or shell script equivalents. There is no mention of Linux/macOS-specific instructions, and all examples and automation scripts are Windows-centric, creating friction for users on non-Windows platforms.
Recommendations
  • Provide CLI command examples in Bash syntax alongside PowerShell, especially for az CLI commands.
  • Offer equivalent shell scripts (e.g., bulk_deployment.sh) for Linux/macOS users, or document how to run the provided .ps1 scripts using cross-platform tools like PowerShell Core.
  • Explicitly state platform compatibility for scripts and commands, and provide troubleshooting or installation guidance for Linux/macOS environments.
  • Ensure documentation sections do not assume Windows-first usage; alternate examples should be shown for Linux/macOS where relevant.
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-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation exhibits Windows bias primarily in the file extraction step, where only Windows-specific tools (Expand-Archive, winget) are referenced and no Linux/macOS alternatives (such as unzip, tar, or Homebrew) are provided. The examples for extracting ZIP files and installing kubectl use Windows-centric commands and tools, which may not work on Linux/macOS. Additionally, the Bash tab for extracting ZIP files incorrectly uses Expand-Archive (a PowerShell/Windows command), further confusing Linux/macOS users. The ordering of examples sometimes places Windows tools first or exclusively.
Recommendations
  • Add Linux/macOS-specific instructions for extracting ZIP files (e.g., 'unzip archive.zip -d /path/to/folder').
  • Provide alternative installation methods for kubectl for Linux/macOS (e.g., curl, apt, yum, Homebrew).
  • Ensure Bash examples use cross-platform commands and avoid Windows-only tools.
  • Clearly separate Windows/PowerShell and Linux/macOS instructions, and provide parity in all steps.
  • Review and correct any Bash tabs that use Windows-only commands.
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-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation provides only a PowerShell migration script example, assumes use of PowerShell, and does not mention or provide equivalent instructions for Linux/macOS users (e.g., Bash or cross-platform scripting). The migration process appears Windows-centric, creating friction for non-Windows users.
Recommendations
  • Provide a Bash or shell script alternative for Linux/macOS users.
  • Clarify whether the PowerShell script can be run with PowerShell Core on Linux/macOS, and provide instructions for doing so if possible.
  • Explicitly mention cross-platform compatibility or limitations of the migration script.
  • Include Linux/macOS command-line examples and usage notes alongside Windows/PowerShell instructions.
GitHub Create Pull Request
Azure Arc Release Notes for Workload Orchestration ...cles/azure-arc/workload-orchestration/release-notes.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page predominantly provides CLI examples using PowerShell syntax, especially in the May 2025 release section, without offering equivalent Bash or Linux/macOS shell examples. While most CLI instructions use the Azure CLI (which is cross-platform), the explicit use of PowerShell syntax (backticks for line continuation, $variable notation) is Windows-centric and may confuse Linux/macOS users. No Linux/macOS-specific instructions or examples are provided, and Windows-style examples are presented first and exclusively where scripting is shown.
Recommendations
  • Provide Bash/Linux/macOS shell examples alongside PowerShell examples for all CLI commands, especially where line continuation or variable usage is shown.
  • Add a note clarifying that Azure CLI is cross-platform and provide guidance for Linux/macOS users on adapting examples (e.g., using \ for line continuation, $VAR for variables).
  • Where possible, alternate the order of examples so Linux/macOS instructions are not always secondary or missing.
  • Explicitly mention platform compatibility for all CLI commands and extensions.
GitHub Create Pull Request
Azure Arc CLI reference for `azcmagent extension` ...main/articles/azure-arc/servers/azcmagent-extension.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation demonstrates Windows bias by listing Windows service management commands (Stop-Service/Start-Service) before their Linux equivalents (systemctl stop/start), and by referencing a Windows-specific extension ('AzureMonitorWindowsAgent') in the example for removing an extension. No Linux-specific extension examples are provided, and Windows tools/patterns are mentioned first in service management instructions.
Recommendations
  • Alternate the order of Windows and Linux service management instructions, or present them side-by-side.
  • Provide Linux-specific extension examples (e.g., removing 'AzureMonitorLinuxAgent') alongside Windows examples.
  • Explicitly state cross-platform applicability in examples and command usage.
  • Where possible, use generic extension names or provide both Windows and Linux extension names in examples.
GitHub Create Pull Request
Azure Arc CLI reference for `azcmagent disconnect` ...ain/articles/azure-arc/servers/azcmagent-disconnect.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page exhibits mild Windows bias by presenting Windows-specific authentication options first and referencing PowerShell tools (Get-AzAccessToken) for access token retrieval without mentioning Linux equivalents. The interactive browser login is described as 'Windows only' and is discussed before Linux-default methods. No Linux-specific tools or shell examples are provided for access token retrieval.
Recommendations
  • Present authentication options in a platform-neutral order, or explicitly alternate between Windows and Linux-first approaches.
  • For access token retrieval, mention cross-platform methods (e.g., Azure CLI's 'az account get-access-token') alongside PowerShell.
  • Include Linux-specific notes or examples where appropriate, such as shell commands or authentication flows.
  • Clarify which authentication options are available on Linux and provide parity in documentation for both platforms.
GitHub Create Pull Request
← Previous Page 55 of 94 Next →