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 1276-1300 of 2334 flagged pages
Azure Arc Configuration and remote access ...es/azure-arc/servers/security-machine-configuration.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation introduces Azure Machine Configuration as a PowerShell Desired State Configuration-based tool, which may suggest a Windows-first approach. Windows Admin Center (WAC) is described as a key remote management scenario, with detailed role assignments and workflow, while Linux remote access is covered primarily through SSH. The documentation provides more detail and context for Windows tools and workflows (WAC, PowerShell DSC) than for Linux equivalents, and Windows terminology and examples appear before Linux ones.
Recommendations
  • Provide equivalent Linux configuration management examples, such as integration with Ansible or Chef, if supported.
  • Include Linux-first or cross-platform examples for compliance and configuration, not just PowerShell DSC.
  • Expand the SSH section to include more details about Linux-specific workflows, troubleshooting, and best practices.
  • Clarify that PowerShell DSC is not required for Linux machines, and mention any Linux-native alternatives if available.
  • Balance the coverage of Windows Admin Center with information about Linux management tools or clarify that WAC is Windows-only.
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-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation mentions both Windows and Linux support, but the examples and next steps prioritize Windows-centric tools (PowerShell) and list Windows-oriented experiences before Linux equivalents (Azure CLI). There are no Linux-specific examples or references to Linux shell scripting, and PowerShell is highlighted as a primary method, which may create friction for Linux users who prefer Bash or native Linux tools.
Recommendations
  • Add explicit Linux shell (Bash) examples and references alongside PowerShell, especially in introductory sections.
  • Ensure that Azure CLI examples are shown before or alongside PowerShell examples, as CLI is more cross-platform.
  • Clarify that Run command supports both Windows and Linux scripts, and provide sample use cases for each OS.
  • Include links to Linux-specific documentation or best practices for using Run command on Linux Arc-enabled servers.
GitHub Create Pull Request
Azure Arc Security overview ...b/main/articles/azure-arc/servers/security-overview.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation generally describes Azure Arc-enabled servers in a cross-platform manner, noting differences between Windows and Linux for agent services. However, the only concrete example given for extension allowlisting references Windows-specific extensions (AzureMonitorWindowsAgent, MDE.Windows) and does not provide Linux equivalents or mention how to configure for Linux scenarios. The guest configuration section references PowerShell Desired State Configuration, which is primarily a Windows technology, without discussing Linux alternatives or limitations.
Recommendations
  • Provide example allowlist configurations for Linux servers, referencing Linux-specific extensions (e.g., AzureMonitorLinuxAgent, MDE.Linux) where applicable.
  • Clarify the applicability and limitations of guest configuration policies for Linux, and mention any Linux-compatible alternatives.
  • When giving examples, include both Windows and Linux scenarios, or explicitly state when an example is Windows-only.
  • Consider referencing cross-platform tools and patterns before Windows-specific ones, or present them in parallel.
GitHub Create Pull Request
Azure Arc Troubleshoot Azure Arc-enabled servers in disconnected scenarios ...rticles/azure-arc/servers/troubleshoot-connectivity.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example
Summary
The documentation references Windows-specific tools (Windows Admin Center, Configuration Manager) as contingency options for managing disconnected servers, without mentioning equivalent Linux tools or approaches. No Linux/macOS management alternatives or examples are provided, which may leave non-Windows users without clear guidance.
Recommendations
  • Add references to Linux-compatible management tools (e.g., Cockpit, Ansible, SSH, or other local Linux administration utilities) for managing Arc-enabled servers in disconnected scenarios.
  • Include examples or guidance for Linux/macOS users on how to monitor, manage, and troubleshoot Arc-enabled servers when disconnected.
  • Clarify that the contingency options are not limited to Windows environments and provide parity for Linux/macOS users.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation generally covers both Windows and Linux scenarios for Azure Arc-enabled servers, but there are several instances of Windows bias. Windows-specific tools (Group Policy, Configuration Manager, WSUS) are mentioned before Linux equivalents, and PowerShell is referenced more frequently than Linux shell commands. Windows update mechanisms are described in detail before Linux package management. Some examples and links (e.g., Group Policy onboarding guidance) are Windows-centric, and Windows terminology appears first in several sections.
Recommendations
  • Provide Linux shell (bash) examples alongside PowerShell where relevant, especially for onboarding and extension management.
  • Mention Linux automation tools (e.g., Ansible, Chef, Puppet) with equal prominence to Windows tools like Group Policy and Configuration Manager.
  • Ensure update instructions for Linux (apt, yum, dnf, zypper) are presented with the same level of detail and priority as Windows Update/WSUS.
  • Where links or references are Windows-specific (e.g., Group Policy onboarding), offer equivalent Linux guidance or clarify when features are Windows-only.
  • Alternate the order of Windows and Linux examples to avoid consistently listing Windows first.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page for troubleshooting SSH access to Azure Arc-enabled servers demonstrates a notable Windows/PowerShell bias. Many troubleshooting steps and examples reference Azure PowerShell modules (Az.Ssh, Az.Ssh.ArcProxy) and provide PowerShell commands exclusively, with no equivalent instructions for Linux/macOS users. In sections where both Azure CLI and PowerShell could be used, PowerShell is often mentioned first or exclusively. There is a lack of explicit Linux/macOS guidance for installing required modules or resolving common issues, and some error messages are Windows-specific.
Recommendations
  • Provide Linux/macOS-specific troubleshooting steps, including installation and usage of Azure CLI for SSH access.
  • Include bash or shell command examples alongside PowerShell commands, especially for module installation and updates.
  • Clarify which steps are platform-agnostic and which are Windows-specific, and offer alternatives for non-Windows environments.
  • Add guidance for resolving PATH and permissions issues on Linux/macOS, not just referencing PowerShell.
  • Ensure error messages and solutions cover both Windows and Linux/macOS scenarios equally.
GitHub Create Pull Request
Azure Arc Troubleshoot Azure Arc-enabled servers networking issues .../articles/azure-arc/servers/troubleshoot-networking.md
Medium Priority View Details →
Scanned: 2026-01-14 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 focuses exclusively on troubleshooting TLS cipher suite configuration for Windows, providing only PowerShell, Group Policy, and Windows Registry methods. There are no Linux or macOS examples, nor any mention of how to check or configure cipher suites on non-Windows Arc-enabled servers, despite Azure Arc supporting Linux servers.
Recommendations
  • Add equivalent instructions for Linux systems, such as how to check enabled TLS cipher suites using 'openssl' or 'nmap', and how to configure cipher suites in common Linux distributions (e.g., by editing OpenSSL or GnuTLS configuration files).
  • Include a section clarifying whether Linux servers are affected by the same requirements, or if the issue is Windows-specific.
  • If the troubleshooting is only relevant for Windows, state this clearly at the top of the section to avoid confusion for Linux users.
  • Provide parity in troubleshooting steps for both Windows and Linux Arc-enabled servers where applicable.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation claims to support both Linux and Windows hybrid machines, but examples and details are primarily Windows-centric. The section on viewing log events specifically references the Windows event log and does not provide equivalent guidance or examples for Linux systems (e.g., syslog or journald). Additionally, the Event table is described only in the context of Windows, with no Linux log table example or query shown.
Recommendations
  • Explicitly describe and provide examples for viewing Linux log events (e.g., syslog, journald) in Log Analytics.
  • Include screenshots or queries for Linux-specific log tables, such as Syslog or Linux-specific performance counters.
  • Clarify differences in data collection and available tables between Windows and Linux machines.
  • Ensure that instructions and UI references apply equally to Linux systems, or note any differences.
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-14 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 moderate Windows bias, particularly in the 'Auto Arc-enablement script' section, which provides only PowerShell-based automation examples and references Windows Task Scheduler for cron jobs. The script usage instructions assume a Windows environment, with no mention of Linux/macOS equivalents or alternatives. While out-of-band methods do mention Ansible (Linux-friendly), most step-by-step examples and automation focus on Windows tools and patterns, and Windows-centric instructions are presented first.
Recommendations
  • Provide equivalent Linux/macOS automation examples for the auto-enablement script, such as Bash scripts and instructions for running as a cron job on Linux.
  • Include cross-platform instructions for downloading and running the helper script, clarifying compatibility and prerequisites for Linux/macOS.
  • When presenting automation examples, alternate or parallelize Windows and Linux/macOS instructions to avoid Windows-first bias.
  • Explicitly mention how Linux users can schedule agent installation tasks (e.g., using cron) and provide sample crontab entries.
  • Ensure that all referenced scripts and tools are cross-platform or provide platform-specific alternatives.
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-01-14 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. All command-line examples use PowerShell syntax and conventions (e.g., backticks for line continuation, .ps1 scripts), and file paths in JSON templates are Windows-style (e.g., C:\Users\...). There are no Bash, Linux shell, or cross-platform CLI examples, nor any mention of how to adapt the instructions for Linux/macOS environments. The use of PowerShell and Windows file paths is pervasive, and Linux users are left to infer how to run these commands or adapt scripts.
Recommendations
  • Provide equivalent Bash/Linux shell examples for all PowerShell commands, especially for az CLI usage.
  • Use cross-platform file path conventions in templates, or provide separate examples for Windows and Linux/macOS.
  • Document how to run onboarding scripts (.ps1) on Linux/macOS, or provide alternative scripts (e.g., Bash).
  • Clarify which steps are platform-agnostic and which require adaptation for non-Windows environments.
  • Add notes or sections explicitly addressing Linux/macOS usage and 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-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides only a PowerShell script for migration and instructs users to run it in PowerShell, with no mention of Bash, Linux shell, or cross-platform alternatives. This creates friction for Linux/macOS users who may not have PowerShell installed or prefer native shell environments.
Recommendations
  • Provide a Bash or cross-platform shell script alternative for Linux/macOS users.
  • Document how to run the PowerShell script on Linux/macOS (e.g., using PowerShell Core, installation instructions, and compatibility notes).
  • Explicitly state platform requirements and offer guidance for non-Windows environments.
GitHub Create Pull Request
Azure Arc Perform disaster recovery operations ...mware-vsphere/recover-from-resource-bridge-deletion.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation exclusively provides PowerShell examples and references a '.ps1' onboarding script, with no mention of Bash, shell, or Linux/macOS-compatible alternatives. All code snippets and instructions assume a Windows environment, creating friction for users on Linux or macOS platforms.
Recommendations
  • Provide equivalent onboarding scripts and instructions for Bash/shell environments, or clarify if the script is cross-platform.
  • Include Linux/macOS-specific steps for running the onboarding script, such as using Azure CLI or PowerShell Core on non-Windows systems.
  • Explicitly state platform requirements and offer guidance for Linux/macOS users (e.g., using PowerShell Core, prerequisites, or alternative tooling).
  • If the onboarding script is Windows-only, consider providing a containerized or cross-platform version.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides only PowerShell script examples and instructions, with no mention of Linux/macOS equivalents or how to run the clean-up script on non-Windows platforms. The script is a .ps1 file, which is natively supported only on Windows, and there are no Bash, shell, or cross-platform alternatives discussed.
Recommendations
  • Provide instructions for running the PowerShell script using PowerShell Core (pwsh) on Linux/macOS, if supported.
  • Explicitly state whether the script is compatible with PowerShell Core on non-Windows platforms.
  • If the script is Windows-only, offer a Bash or shell script alternative for Linux/macOS users.
  • Add example commands for Linux/macOS environments, including prerequisites for installing PowerShell Core if needed.
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-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits Windows bias in several areas. The example for installing kubectl uses Windows-specific tooling (winget) without providing a Linux/macOS alternative. In the section on extracting ZIP files, the Bash tab incorrectly uses the Windows PowerShell command Expand-Archive, which does not exist on Linux/macOS. There are no Linux/macOS-specific instructions for these basic setup steps, which may cause confusion or friction for non-Windows users. Throughout the rest of the document, Bash and PowerShell examples are provided in parallel, but the initial steps and tooling favor Windows.
Recommendations
  • For kubectl installation, provide platform-specific instructions: use apt, yum, brew, or direct download for Linux/macOS users.
  • In the ZIP extraction section, replace Expand-Archive in the Bash tab with a Linux/macOS-compatible command such as unzip or tar.
  • Review all example commands to ensure they are valid and tested on Linux/macOS environments.
  • Consider listing Linux/macOS instructions before or alongside Windows instructions to avoid implicit prioritization.
  • Add explicit notes or tabs for macOS if there are platform-specific considerations.
GitHub Create Pull Request
Azure Arc Troubleshooting for Workload Orchestration ...es/azure-arc/workload-orchestration/troubleshooting.md
Medium Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The troubleshooting documentation for workload orchestration in Azure Arc shows a notable Windows bias. Most command-line examples outside the 'service groups' section are given only in PowerShell syntax, with no Bash or Linux shell equivalents. Tasks such as registry management, token handling, and image inspection use PowerShell-specific constructs and variables, which may not work natively on Linux/macOS. Only the 'service groups' section provides both Bash and PowerShell tabs, while the majority of troubleshooting steps assume a Windows/PowerShell environment.
Recommendations
  • Provide Bash/Linux shell equivalents for all PowerShell commands, especially for az CLI, kubectl, and docker operations.
  • Avoid using PowerShell-specific syntax (e.g., variable assignment, piping to ConvertTo-Json, Out-File) in generic Azure CLI or Kubernetes examples; use cross-platform syntax or clearly separate Windows and Linux instructions.
  • Explicitly note any platform-specific requirements, and offer guidance for Linux/macOS users where differences exist (e.g., file encoding, JSON creation).
  • Where possible, use az CLI commands in a platform-neutral way, and clarify when PowerShell is required.
GitHub Create Pull Request
Azure Arc Deploy the Edge RAG Extension ...t-docs/blob/main/articles/azure-arc/edge-rag/deploy.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 provides Azure CLI deployment instructions exclusively using PowerShell syntax and variable assignment, which is native to Windows. There are no Bash or Linux/macOS shell examples, and the CLI section assumes a Windows environment. This creates friction for Linux/macOS users, who must adapt the instructions to their shell. The Azure portal instructions are platform-neutral, but the CLI section is Windows-centric.
Recommendations
  • Provide equivalent Bash examples for Azure CLI commands, including variable assignment and command execution.
  • Explicitly note that PowerShell syntax is shown and provide guidance for Linux/macOS users.
  • Consider presenting Bash and PowerShell examples side-by-side or in tabs.
  • Avoid using Windows-specific variable assignment (e.g., $var) in CLI documentation unless clearly marked as PowerShell-only.
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-01-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page is generally cross-platform and references Azure Arc-enabled data services, which run on Kubernetes and are managed via Azure CLI and Azure Data Studio (both cross-platform). However, there is evidence of Windows bias in the 'Arc-enabled SQL Server' billing data JSON example, where 'osType' is set to 'Windows', 'manufacturer' is 'Microsoft', and 'model' is 'Hyper-V'. There are no explicit Linux/macOS examples or references to Linux-specific environments, and the only OS-specific example is Windows. Additionally, SQL Server is a product historically associated with Windows, and no parity is shown for Linux deployments or examples, even though SQL Server is available on Linux. The order of presentation also puts Windows-centric examples first.
Recommendations
  • Add explicit Linux/macOS examples in the billing data section, e.g., show 'osType': 'Linux', 'manufacturer': 'Dell', 'model': 'PowerEdge', etc.
  • Clarify that SQL Server can run on Linux and provide example JSON payloads for Linux-based deployments.
  • Where OS-specific properties are shown, provide a table or section describing possible values for both Windows and Linux environments.
  • Ensure that any references to tools (Azure CLI, Azure Data Studio) highlight their cross-platform nature and provide links to installation instructions for Linux/macOS.
  • If PowerShell or Windows tools are referenced elsewhere, add Bash or Linux shell equivalents.
GitHub Create Pull Request
Azure Arc Uninstall Edge RAG Extension ...ain/articles/azure-arc/edge-rag/uninstall-extension.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 demonstrates a Windows bias by providing all CLI examples in PowerShell syntax, referencing PowerShell explicitly, and omitting Linux/macOS shell equivalents. The instructions assume use of PowerShell, even for commands that are cross-platform (e.g., az, kubectl), and do not offer bash/zsh examples or mention Linux-specific considerations.
Recommendations
  • Add a Bash/zsh/Linux/macOS tab alongside the Azure PowerShell tab, showing equivalent commands in standard shell syntax.
  • Clarify that az and kubectl commands are cross-platform and provide examples for both Windows (PowerShell) and Linux/macOS (bash).
  • Avoid using PowerShell variable syntax ($var) in generic CLI examples; use environment variables or inline arguments for broader compatibility.
  • Explicitly mention that the instructions apply to Linux/macOS as well, and note any OS-specific steps if relevant.
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-13 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation mentions Windows service management commands ('Stop-Service ExtensionService', 'Start-Service ExtensionService') before their Linux equivalents ('systemctl stop extd', 'systemctl start extd'). The extension removal example uses a Windows-specific extension ('AzureMonitorWindowsAgent'), and there are no Linux/macOS-specific examples or extension names. The documentation does not provide Linux/macOS-specific usage patterns or troubleshooting tips.
Recommendations
  • Present Linux and Windows service management commands side-by-side, or alternate which platform is listed first.
  • Include examples using Linux/macOS-specific extensions (e.g., 'AzureMonitorLinuxAgent').
  • Add notes or examples relevant to Linux/macOS users, such as common extension names or troubleshooting steps.
  • Clarify any platform-specific differences in extension management, if applicable.
GitHub Create Pull Request
Azure Arc Simplify Network Configuration Requirements with Azure Arc Gateway ...cs/blob/main/articles/azure-arc/servers/arc-gateway.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 tools and PowerShell commands are consistently presented alongside Azure CLI, and in some cases, Windows-specific instructions (such as log file locations) are described before or in more detail than their Linux equivalents. Some scenarios (e.g., Windows Admin Center, Windows OS Update Extension) are highlighted without Linux alternatives or parity notes. The onboarding and management instructions do include Azure CLI examples, which are cross-platform, but PowerShell is given equal prominence, and Windows-specific patterns (like referencing Windows installation packages and prerequisites) are more detailed than Linux ones.
Recommendations
  • Ensure Linux examples and instructions are presented with equal detail and prominence as Windows ones, including log file locations, onboarding steps, and troubleshooting.
  • Where PowerShell is used, clarify that Azure CLI commands are cross-platform and provide explicit Bash/Linux shell examples where appropriate.
  • For scenarios listed as 'Windows only' (e.g., Windows Admin Center, Windows OS Update Extension), add notes about Linux alternatives or clarify Linux support status.
  • Review all endpoint and prerequisite lists to ensure Linux-specific requirements are fully documented and not overshadowed by Windows-centric notes.
  • Consider presenting CLI (cross-platform) examples before PowerShell (Windows-only) in each tabbed section.
GitHub Create Pull Request
Azure Arc How to evaluate Azure Arc-enabled servers with an Azure virtual machine ...-arc/servers/plan-evaluate-on-azure-virtual-machine.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 examples and PowerShell commands are consistently presented before Linux equivalents. Windows-specific tools (PowerShell, WindowsAzureGuestAgent, New-NetFirewallRule) are described in detail, while Linux instructions sometimes refer users to external documentation or provide less guidance. The VM creation links for Linux are inconsistent, and some Linux steps (e.g., firewall configuration) require users to consult their own distribution's documentation, whereas Windows steps are fully detailed.
Recommendations
  • Present Linux and Windows examples side-by-side or alternate which comes first.
  • Provide direct, detailed Linux command examples for all major distributions (Ubuntu, Red Hat, SUSE) rather than referring users to external documentation.
  • Ensure VM creation links for Linux point to the correct template (the Ubuntu link currently points to the Windows template).
  • Offer parity in troubleshooting and error messages for both platforms.
  • Include more context and explanation for Linux-specific steps, matching the detail given to Windows instructions.
GitHub Create Pull Request
Azure Arc Troubleshoot Azure Arc-enabled servers in disconnected scenarios ...rticles/azure-arc/servers/troubleshoot-connectivity.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 page demonstrates Windows bias by exclusively mentioning Windows-specific tools (Windows Admin Center, Configuration Manager) as local management options for disconnected servers. There are no references to Linux/macOS equivalents or examples, and Windows tools are presented first and solely, which may leave Linux users without clear guidance for managing Arc-enabled servers in disconnected scenarios.
Recommendations
  • Include Linux/macOS management tool options (e.g., Cockpit, Ansible, SSH, systemd) alongside Windows Admin Center and Configuration Manager.
  • Provide examples or guidance for Linux users on how to monitor, manage, and troubleshoot Arc-enabled servers when disconnected.
  • Add parity in recommendations for local troubleshooting and configuration steps for both Windows and Linux platforms.
  • Explicitly state which steps or tools are platform-specific and offer alternatives for other operating systems.
GitHub Create Pull Request
Azure Arc Troubleshoot Azure Arc-enabled servers VM extension issues ...ticles/azure-arc/servers/troubleshoot-vm-extensions.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 🔧 Windows Tools
Summary
The documentation page demonstrates moderate Windows bias. PowerShell is the only CLI example shown for extension removal, with no equivalent Linux shell command provided. Windows file paths and troubleshooting steps are consistently listed before Linux equivalents, and Windows-specific tools (PowerShell) are referenced without parity for Linux users. While Linux information is present, it is secondary and less actionable.
Recommendations
  • Provide Linux shell (bash) command examples alongside PowerShell, such as using the Azure CLI for extension removal.
  • Alternate the order of Windows and Linux instructions or present them in parallel to avoid Windows-first bias.
  • Reference Linux-native tools and troubleshooting patterns (e.g., systemctl, journalctl) where appropriate.
  • Ensure all actionable steps (such as extension removal) have clear instructions for both platforms.
GitHub Create Pull Request
Azure Arc Remove your SCVMM environment from Azure Arc ...virtual-machine-manager/remove-scvmm-from-azure-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 exhibits a notable Windows bias. Windows examples and tools (e.g., PowerShell scripts, Control Panel instructions) are presented first and in greater detail. The deboarding script is only available as a Windows PowerShell script, with no Linux or cross-platform alternative. Manual steps and UI flows are described in a way that assumes a Windows-centric SCVMM environment, and Linux users are left without equivalent automation or scripting guidance.
Recommendations
  • Provide a cross-platform (e.g., Bash or Python) version of the deboarding script, or at least document manual CLI steps for Linux environments.
  • Present Linux and Windows instructions with equal prominence, possibly using side-by-side tabs or sections.
  • Include Linux-specific automation examples for agent removal and resource cleanup, not just manual commands.
  • Clarify any platform limitations up front, and offer workarounds or alternatives for non-Windows users.
  • Where PowerShell is used, note if it can be run on PowerShell Core on Linux/macOS, or provide equivalent Bash/CLI commands.
GitHub Create Pull Request
Azure Arc Perform disaster recovery operations ...mware-vsphere/recover-from-resource-bridge-deletion.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 exclusively provides PowerShell script examples and instructions, with no mention of Linux/macOS shell equivalents or cross-platform onboarding scripts. All command-line steps assume a Windows environment and tooling, creating friction for users on Linux or macOS.
Recommendations
  • Provide equivalent Bash or shell script examples for Linux/macOS users.
  • Clarify whether the onboarding script can be run on Linux/macOS, and provide instructions if so.
  • Explicitly mention platform requirements and alternatives for non-Windows users.
  • If the onboarding script is Windows-only, offer a containerized or cross-platform version.
GitHub Create Pull Request
← Previous Page 52 of 94 Next →