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 426-450 of 2334 flagged pages
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/migrate-legacy-agents.md ...in/articles/azure-arc/servers/migrate-legacy-agents.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by mentioning Windows-specific tools (Windows Admin Center, Windows Server Graphical Installer) and deployment methods before Linux equivalents. PowerShell is referenced as a primary scripting option, while Bash is mentioned only in passing and no Linux-specific deployment tools (e.g., cloud-init, systemd, shell scripts) are highlighted. There are no explicit Linux examples or guidance for Linux environments, and standalone agent installation is only described for Windows clients.
Recommendations
  • Add explicit Linux deployment examples, such as using shell scripts, cloud-init, or systemd for agent installation and configuration.
  • Mention Linux-native tools (e.g., Ansible, Chef, Puppet) with equal prominence to Windows tools for at-scale deployment.
  • Provide standalone Azure Monitor Agent installation instructions for Linux client machines, not just Windows.
  • Ensure that scripting examples (e.g., PowerShell, Bash) are presented in parallel, with full examples for both platforms.
  • List deployment options for Windows and Linux together, or alternate the order to avoid Windows-first presentation.
  • Reference Linux-specific documentation links where appropriate, similar to the Windows client installer link.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/onboard-configuration-manager-custom-task.md ...c/servers/onboard-configuration-manager-custom-task.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a clear Windows bias: all examples and instructions are tailored exclusively for Windows environments, specifically using Microsoft Configuration Manager and Windows Installer (.msi) packages. The agent download, application creation, and task sequence steps are Windows-centric, with no mention of Linux equivalents or cross-platform considerations. PowerShell is the only scripting language referenced, and there are no examples or guidance for onboarding Linux servers or using Linux-native tools.
Recommendations
  • Add equivalent instructions for onboarding Linux machines at scale, including agent download and installation steps for Linux (e.g., .deb, .rpm packages).
  • Provide sample task sequences or automation scripts using Linux-native tools (such as shell scripts, Ansible, or cloud-init) and demonstrate how to connect Linux servers to Azure Arc.
  • Include examples using Bash or other Linux scripting languages alongside PowerShell.
  • Clarify which steps are Windows-specific and offer parallel guidance for Linux environments.
  • Reference cross-platform management tools or workflows where applicable, not just Configuration Manager.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/onboard-service-principal.md ...rticles/azure-arc/servers/onboard-service-principal.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows and PowerShell are mentioned first or more prominently in several places, such as the creation of service principals and installation scripts. PowerShell examples are provided in detail, while Linux-specific command-line examples are less emphasized or absent. The troubleshooting and agent installation sections also focus on Windows tools and patterns, with limited Linux-specific troubleshooting or automation guidance.
Recommendations
  • Ensure Linux examples (e.g., Bash, shell scripting) are provided alongside or before Windows/PowerShell examples.
  • Balance the order of presentation so that Linux and Windows instructions alternate or are grouped together, rather than Windows-first.
  • Include Linux-specific troubleshooting steps and notes, especially for common issues encountered during onboarding.
  • Provide parity in automation guidance, such as sample scripts for Linux environments (e.g., Bash, Ansible) where PowerShell scripts are shown for Windows.
  • Explicitly mention cross-platform compatibility for tools like Azure CLI and azcmagent, and clarify any OS-specific limitations.
  • Add links to Linux admin guides or best practices for Azure Arc onboarding, similar to those provided for Windows.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/plan-at-scale-deployment.md ...articles/azure-arc/servers/plan-at-scale-deployment.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows and PowerShell are mentioned before Linux in several places, such as when creating a service principal ('using Azure PowerShell or from the Azure portal') and in onboarding scripts. There is a lack of explicit Linux command-line or automation tool examples (e.g., Bash, SSH, Ansible), and no Linux-specific tooling or patterns are highlighted. Most examples and instructions are either generic or Windows/PowerShell-centric, with Linux only referenced as an afterthought or in combined links.
Recommendations
  • Provide explicit Linux command-line examples (e.g., Bash scripts, CLI commands) alongside PowerShell and portal instructions.
  • Mention Linux automation tools (e.g., Ansible, Chef, Puppet) as options for deploying the Connected Machine agent.
  • Ensure that Linux is referenced equally or first in lists and examples, not only as a secondary option.
  • Include troubleshooting and management instructions specific to Linux environments (e.g., systemd service management, log file locations).
  • Highlight Linux-specific considerations (e.g., package managers, SELinux/AppArmor, root permissions) where relevant.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/prerequisites.md .../blob/main/articles/azure-arc/servers/prerequisites.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates several forms of Windows bias. Windows-specific tools (such as PowerShell and Group Policy Editor) are mentioned and explained in detail, while Linux equivalents are either omitted or referenced only briefly. Script examples for agent installation adjustments are provided only for Windows (PowerShell), with no corresponding Linux command-line example. Windows configuration steps (e.g., user rights assignment) are described with screenshots and step-by-step instructions, whereas Linux system requirements are listed without further guidance. In sections where both platforms are relevant, Windows instructions and tools are presented first or exclusively.
Recommendations
  • Provide Linux-specific onboarding script examples, especially for limited support scenarios, such as showing how to install a specific agent version using package managers (e.g., apt, yum, zypper).
  • Include Linux equivalents for configuration tasks, such as managing service permissions or troubleshooting agent startup (e.g., systemd service configuration, checking logs).
  • Balance the order of presentation so that Linux instructions and examples are given equal prominence and detail as Windows.
  • Add screenshots or step-by-step instructions for common Linux administrative tasks relevant to the agent (e.g., verifying required packages, checking service status).
  • Explicitly mention Linux tools and patterns (e.g., sudo, systemctl, package repositories) where appropriate, not just in passing.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/onboard-update-management-machines.md ...zure-arc/servers/onboard-update-management-machines.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation describes onboarding both Windows and Linux machines to Azure Arc via Automation Update Management, but operational details and examples are Windows-centric. Runbook names and references (e.g., Add-UMMachinesToArc, Add-UMMachinesToArcWindowsChild) use PowerShell-style naming conventions, and instructions for monitoring and troubleshooting refer to Azure PowerShell and Windows-first workflows. There are no explicit Linux command-line examples or references to Linux-native tools, and the documentation does not provide parity in Linux-specific guidance.
Recommendations
  • Include explicit Linux command-line examples (e.g., Bash, shell scripts) for onboarding and verification steps.
  • Reference Linux-native tools (such as CLI commands, systemd, journalctl) alongside or before Windows equivalents.
  • Provide screenshots or walkthroughs from Linux environments in addition to Windows/Azure portal views.
  • Clarify that runbooks and automation workflows support both PowerShell and Bash, and provide sample scripts for each.
  • Ensure troubleshooting and verification steps include Linux-specific guidance (e.g., checking agent status via systemctl, reviewing logs in /var/log).
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/plan-evaluate-on-azure-virtual-machine.md ...-arc/servers/plan-evaluate-on-azure-virtual-machine.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 mild Windows bias. Windows examples and tools (PowerShell, WindowsAzureGuestAgent, New-NetFirewallRule) are consistently presented first, with more detailed and explicit instructions. Linux equivalents are provided, but sometimes with less detail or with references to external documentation. Windows-specific tooling (PowerShell, Windows firewall) is mentioned before Linux alternatives, and some Linux instructions are less direct (e.g., 'consult your distribution's documentation').
Recommendations
  • Alternate the order of Windows and Linux instructions throughout the documentation to avoid consistently prioritizing Windows.
  • Provide equally detailed, step-by-step Linux instructions for all major distributions (not just Ubuntu, Red Hat, SUSE), or link to official docs for each.
  • Include direct Linux command examples for all steps where Windows PowerShell is used, rather than referring users to external documentation.
  • Where Windows tools are mentioned (e.g., PowerShell, Windows firewall), ensure Linux equivalents (e.g., iptables, nftables, firewalld) are described with similar clarity and completeness.
  • Add troubleshooting tips and verification steps for Linux users, matching those provided for Windows.
  • Review and update links to ensure Linux VM deployment templates are correct (the Ubuntu link currently points to a Windows template).
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/prepare-extended-security-updates.md ...azure-arc/servers/prepare-extended-security-updates.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on Windows Server 2012/2012 R2, with all examples, deployment options, and tooling references tailored to Windows environments. There are no Linux-specific instructions, examples, or mentions of Linux equivalents for onboarding, patching, or managing servers with Azure Arc. Windows tools and patterns (Group Policy, Configuration Manager, SCVMM, VDI, MAK keys) are referenced exclusively, and no parity is provided for Linux systems.
Recommendations
  • Add explicit statements clarifying whether Linux servers are supported or not for ESU delivery via Azure Arc.
  • If Linux onboarding is possible, provide equivalent Linux examples (e.g., shell scripts, Linux agent installation, Linux patching workflows).
  • Include Linux-centric deployment options (such as Ansible, SSH, or Linux-native automation tools) alongside Windows tools like Group Policy and Configuration Manager.
  • Mention Linux-specific networking and certificate installation steps if applicable.
  • Ensure documentation structure does not assume Windows-first by default; provide parallel guidance for Linux where relevant.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/run-command-rest.md ...ob/main/articles/azure-arc/servers/run-command-rest.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. All example scenarios, scripts, and references are exclusively for Windows Server (specifically Windows Server 2012/R2) and use PowerShell cmdlets (e.g., New-NetFirewallRule). There are no examples or guidance for Linux servers, nor are Linux shell scripts or tools mentioned. Even instructions for generating SAS tokens reference PowerShell tools (New-AzStorageBlobSASToken) without Linux alternatives.
Recommendations
  • Add parallel example scenarios for Linux Arc-enabled servers, including sample shell scripts (e.g., using iptables or ufw for firewall rules).
  • Explicitly mention Linux support and provide guidance for Linux-specific Run command usage.
  • Include instructions for generating SAS tokens using Azure CLI or REST API, which are cross-platform.
  • Clarify in the prerequisites or introduction which OS platforms are supported and ensure both Windows and Linux are covered.
  • Balance references to PowerShell with equivalent Bash or shell script examples and tools.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/quick-enable-hybrid-vm.md ...n/articles/azure-arc/servers/quick-enable-hybrid-vm.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates a moderate Windows bias. In the installation section, Windows instructions (using PowerShell) are presented before Linux instructions, and the Windows steps are more detailed (e.g., specifying 'elevated 64-bit PowerShell'). The Linux section is shorter and less detailed. The script generation and portal steps are OS-neutral, but the overall pattern prioritizes Windows terminology and tools.
Recommendations
  • Alternate the order of Windows and Linux instructions in each section, or present them in parallel tabs to avoid implicit prioritization.
  • Provide equally detailed steps for Linux, including information about required permissions, shell environment, and any prerequisites (e.g., bash version, package manager).
  • Where PowerShell is referenced for Windows, mention the equivalent shell (e.g., Bash) for Linux in the same level of detail.
  • Avoid using Windows-specific terminology (e.g., 'elevated PowerShell') without providing the Linux equivalent (e.g., 'run as root or with sudo').
  • Consider including screenshots or command-line examples for both platforms to ensure parity.
  • Where possible, use cross-platform language and tools, or clearly indicate when a step is OS-specific.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/run-command-cli.md ...lob/main/articles/azure-arc/servers/run-command-cli.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 exclusively providing PowerShell script examples (e.g., 'Write-Host Hello World!') and omitting any Linux shell script (bash/sh) examples. The only script shown uses a Windows-centric command, and there is no mention of Linux tools or patterns. This may lead Linux users to feel unsupported or unclear about how to use the feature with bash scripts.
Recommendations
  • Add equivalent Linux shell script examples (e.g., 'echo Hello World!') alongside PowerShell examples.
  • Explicitly state that both Windows and Linux Arc-enabled servers are supported, and clarify any platform-specific considerations.
  • Where possible, provide side-by-side examples for common tasks (e.g., one PowerShell, one bash) to ensure parity.
  • Mention any differences in script execution environments or output handling between Windows and Linux.
  • Avoid using only Windows-centric commands in introductory examples; alternate or combine with Linux equivalents.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/scenario-migrate-to-azure.md ...rticles/azure-arc/servers/scenario-migrate-to-azure.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation demonstrates a Windows bias by prioritizing Azure PowerShell examples and references, mentioning PowerShell before Azure CLI, and providing detailed PowerShell instructions without equivalent Linux shell examples. While Linux is mentioned in the context of the Azure Guest Agent, there are no explicit Linux command-line examples or references to Linux-native tools, and PowerShell is presented as the primary method for inventorying and managing resources.
Recommendations
  • Provide Linux shell (bash) command examples alongside PowerShell, especially for inventorying extensions and managing role assignments.
  • Explicitly mention and demonstrate how to perform key steps (such as uninstalling the Connected Machine agent and managing VM extensions) on Linux systems, including relevant commands.
  • Ensure that references to Azure CLI are given equal prominence and detail as PowerShell, and consider listing CLI examples before or alongside PowerShell to avoid Windows-first ordering.
  • Include troubleshooting and migration guidance specific to Linux environments, such as handling Linux-specific agents and extensions.
  • Add links to Linux documentation and best practices where Windows documentation is referenced.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/run-command.md ...cs/blob/main/articles/azure-arc/servers/run-command.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page mentions support for both Windows and Linux, but the examples and next steps prioritize PowerShell and Azure CLI (which often have Windows-centric usage patterns). There are no explicit Linux shell (bash) examples, and the documentation refers to PowerShell before CLI and REST, suggesting a Windows-first perspective. There is no mention of Linux-specific tools, shell scripts, or usage patterns, and no examples tailored for Linux administrators.
Recommendations
  • Add explicit Linux shell (bash) examples for using Run command, including sample scripts and command invocations.
  • Ensure parity in documentation by providing both Windows (PowerShell) and Linux (bash/sh) script examples in all relevant sections.
  • Mention Linux-specific administrative tasks (e.g., apt/yum updates, iptables configuration) alongside Windows tasks.
  • Reorder examples and references so that Windows and Linux are treated equally, or alternate which is mentioned first.
  • Clarify any differences in usage or limitations between Windows and Linux environments.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/security-machine-configuration.md ...es/azure-arc/servers/security-machine-configuration.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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 Windows bias by emphasizing PowerShell Desired State Configuration as the foundation for Azure Machine Configuration, mentioning Windows Admin Center (WAC) as a primary remote management tool, and providing detailed descriptions of Windows-specific workflows and roles. Linux is referenced mainly in the context of SSH access, but there are no Linux-specific configuration or management examples, and Windows tools/patterns are described first and in more detail.
Recommendations
  • Include Linux-specific examples for configuration management, such as using native Linux tools (e.g., Ansible, Chef, or native shell scripts) alongside PowerShell DSC.
  • Provide parity in remote management tooling by mentioning or recommending Linux equivalents to Windows Admin Center, such as Cockpit or Webmin, and describe how they can be integrated with Azure Arc.
  • Present examples and workflows for both Windows and Linux systems side-by-side, ensuring that Linux instructions are not omitted or relegated to secondary status.
  • Clarify role assignments and access patterns for Linux systems, including details on how RBAC and Entra ID integration work for Linux beyond SSH.
  • Add troubleshooting and best practices sections for Linux environments, similar to those provided for Windows.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/security-onboarding.md ...main/articles/azure-arc/servers/security-onboarding.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page demonstrates a Windows bias in several areas: Windows-specific tools and patterns (Group Policy, Microsoft Update, WSUS) are mentioned before or in more detail than their Linux equivalents; PowerShell is referenced for extension management and onboarding, but Linux command-line examples are absent; onboarding guidance links to Windows/PowerShell-specific instructions without Linux parity; and automation tooling examples prioritize Microsoft Configuration Manager and Group Policy over Linux-first tools like Ansible.
Recommendations
  • Provide Linux-specific onboarding examples and guidance, including shell script and configuration file encryption best practices.
  • Include Linux command-line examples (bash, shell, etc.) alongside PowerShell for extension management and onboarding.
  • Reference Linux-native automation tools (e.g., Chef, Puppet, SaltStack) equally with Windows tools.
  • Ensure links to onboarding guidance include Linux-focused documentation, not just Group Policy/PowerShell.
  • Present update management instructions for Linux (apt, yum, etc.) before or alongside Windows update mechanisms.
  • Clarify disk encryption recommendations with Linux-first examples (e.g., dm-crypt, LUKS) and provide parity with BitLocker.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/security-identity-authorization.md ...s/azure-arc/servers/security-identity-authorization.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias. File paths and group names are consistently listed with Windows examples first (e.g., 'C:\ProgramData\...' before '/var/opt/...'), and Windows-specific terminology (such as 'administrators', 'Hybrid agent extension applications') is mentioned before Linux equivalents. The documentation references Windows tools and patterns (e.g., access control lists, directory structure) and omits explicit Linux command-line or shell examples, focusing more on Windows conventions.
Recommendations
  • Alternate the order of Windows and Linux examples so that Linux is sometimes presented first.
  • Provide explicit Linux shell command examples (e.g., chmod, chown) for managing access to certificate and token directories.
  • Clarify group and user mappings for Linux (e.g., explain 'himds' and how to add users to this group on Linux).
  • Include Linux-specific troubleshooting steps and patterns where relevant.
  • Ensure parity in screenshots and video content, showing both Windows and Linux environments.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/security-overview.md ...b/main/articles/azure-arc/servers/security-overview.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates Windows bias in several ways: it references PowerShell Desired State Configuration as the basis for guest configuration policies without mentioning Linux equivalents, describes Windows service accounts in detail before Linux, and provides extension allowlist examples only for Windows agents. There are no explicit Linux command examples or references to Linux-native configuration tools or patterns.
Recommendations
  • Provide Linux-specific examples for extension allowlists and agent configuration, including azcmagent commands relevant to Linux environments.
  • Mention Linux equivalents to PowerShell Desired State Configuration, such as Ansible, Chef, or native shell scripts, for guest configuration policies.
  • Describe Linux service/daemon accounts with equal detail and order as Windows service accounts.
  • Include references to Linux security best practices (e.g., SELinux, AppArmor, systemd hardening) alongside Windows recommendations.
  • Ensure all examples and recommendations are presented for both Windows and Linux, or clarify when a feature is Windows-only.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/ssh-arc-troubleshoot.md ...ain/articles/azure-arc/servers/ssh-arc-troubleshoot.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a Windows bias by prioritizing PowerShell-based troubleshooting steps and examples, referencing Windows-specific error codes (e.g., WinError), and focusing on Azure PowerShell modules and commands. Linux equivalents (such as bash or shell commands) are either missing or mentioned only in error messages, with no corresponding troubleshooting steps or examples. The guidance assumes the use of PowerShell and Windows tools, with little attention to Linux-native workflows or commands.
Recommendations
  • Provide Linux-specific troubleshooting steps and examples alongside PowerShell instructions, such as using bash or shell commands for module installation and updates.
  • Include guidance for managing PATH and SSH client binaries on Linux systems, with explicit examples for common distributions.
  • Offer parity in error resolution steps for both Windows and Linux, including installation and permission troubleshooting using Linux-native tools (e.g., apt, yum, chmod).
  • Reference Linux package managers and environment variables where appropriate, not just PowerShell Gallery and Windows PATH.
  • Ensure that CLI examples are not limited to Azure CLI and PowerShell, but also include relevant Linux shell commands where applicable.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/troubleshoot-connectivity.md ...rticles/azure-arc/servers/troubleshoot-connectivity.md
High Priority View Details →
Scanned: 2026-01-09 00:34
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, without referencing equivalent Linux tools or approaches. No Linux-specific examples or management strategies are provided, and Windows tools are presented first and solely, implying a Windows-centric perspective.
Recommendations
  • Include Linux management tool options such as Cockpit, Webmin, or command-line utilities for local server management in disconnected scenarios.
  • Provide examples or guidance for troubleshooting and managing disconnected Arc-enabled servers on Linux, including relevant commands and best practices.
  • Ensure parity in documentation by listing both Windows and Linux tools and approaches, ideally presenting them side-by-side or in separate subsections.
  • Clarify that Azure Arc-enabled servers support both Windows and Linux, and tailor troubleshooting steps to both platforms.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/troubleshoot-agent-onboard.md ...ticles/azure-arc/servers/troubleshoot-agent-onboard.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias. Windows examples and tools are presented before Linux equivalents in several sections (e.g., verbose logging commands, log file locations). Windows-specific tools and terminology (such as PowerShell, elevated command prompt, %ProgramData%, %TEMP%) are mentioned explicitly, while Linux equivalents are sometimes only referenced after or less prominently. The error and exit code tables often list Windows paths first, and PowerShell requirements are called out in error codes. However, Linux examples and troubleshooting steps are generally present and reasonably complete.
Recommendations
  • Present Windows and Linux examples side-by-side or alternate their order to avoid implicit prioritization.
  • Explicitly mention Linux equivalents for all Windows-specific tools, paths, and terminology (e.g., clarify that %TEMP% on Windows corresponds to /tmp on Linux).
  • Include Linux-specific troubleshooting steps and log file locations with equal prominence.
  • Avoid using Windows-centric language (such as 'elevated command prompt') without also referencing Linux equivalents (such as 'sudo' or 'root').
  • Where PowerShell is referenced, clarify if Bash or other shells are supported and provide examples.
  • Ensure that error codes and remediation steps are equally detailed for both platforms.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/troubleshoot-networking.md .../articles/azure-arc/servers/troubleshoot-networking.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation page focuses exclusively on troubleshooting TLS configuration issues for Windows, providing only Windows-specific instructions and examples (PowerShell commands, Group Policy, Registry edits). There is no mention of Linux equivalents, nor are any Linux troubleshooting steps or commands provided. The use of Windows tools and patterns is pervasive, and Linux users are left without guidance.
Recommendations
  • Add a dedicated section for Linux TLS configuration troubleshooting, including relevant commands (e.g., using openssl, update-crypto-policy, or editing /etc/ssl/openssl.cnf).
  • Provide Linux-specific examples for checking and enabling cipher suites, such as using 'openssl ciphers' or inspecting system-wide TLS settings.
  • Clarify which steps apply only to Windows and ensure Linux parity by listing corresponding Linux procedures.
  • Reference Linux documentation or official guides for managing TLS cipher suites on common distributions (Ubuntu, RHEL, etc.).
  • Consider presenting Windows and Linux instructions side-by-side or in parallel sections for easier cross-platform comparison.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/tutorial-enable-vm-insights.md ...icles/azure-arc/servers/tutorial-enable-vm-insights.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates Windows bias by providing explicit instructions and examples for Windows event logs (e.g., referencing the 'Event' table for Windows event log entries) while omitting equivalent details for Linux systems (such as syslog or Linux-specific event tables). The mention of event logs and Log Analytics queries is Windows-centric, and there are no Linux-specific examples or references to Linux logging mechanisms. Additionally, Windows terminology and tools (event log) are mentioned before or instead of Linux equivalents.
Recommendations
  • Include explicit examples and instructions for Linux machines, such as how to view syslog or other Linux event tables in Log Analytics.
  • Mention Linux-specific logging mechanisms (e.g., syslog, journald) alongside Windows event logs when discussing collected data.
  • Provide sample queries for both Windows and Linux event data in Log Analytics.
  • Clarify which tables and data types are available for Linux machines and how to interpret them.
  • Ensure parity in screenshots and walkthroughs by showing both Windows and Linux machine perspectives.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/troubleshoot-extended-security-updates.md ...-arc/servers/troubleshoot-extended-security-updates.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example Powershell Heavy 🔧 Windows Tools
Summary
The documentation is heavily focused on Windows Server 2012 and 2012 R2, with all troubleshooting steps, examples, and commands tailored exclusively for Windows environments. There are no Linux equivalents or cross-platform guidance, and Windows-specific tools and patterns (e.g., certutil, PowerShell, Windows file paths) are used throughout. The documentation assumes the reader is working with Windows servers, with no mention of Linux scenarios or how similar troubleshooting might apply to non-Windows Arc-enabled machines.
Recommendations
  • Add explicit statements clarifying that the guidance is only applicable to Windows Server 2012/2012 R2, and provide links or references for troubleshooting ESU delivery on Linux or other platforms if relevant.
  • Where possible, include Linux equivalents for Azure Arc-enabled servers, such as how to check agent status, manage certificates, or troubleshoot connectivity and enrollment issues on Linux.
  • If certain steps (e.g., certificate installation, agent updates) have Linux alternatives, provide corresponding commands (e.g., using openssl, update-ca-certificates, systemctl) and file paths.
  • Ensure parity in troubleshooting steps for both Windows and Linux Arc-enabled servers, or clearly state platform limitations.
  • Avoid assuming PowerShell or Windows command prompt as the only available shell; mention Bash or other shells where appropriate.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/system-center-virtual-machine-manager/agent-overview-scvmm.md ...center-virtual-machine-manager/agent-overview-scvmm.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Windows Heavy Detail
Summary
The documentation provides detailed, step-by-step information for both Windows and Linux agent installation and configuration. However, Windows installation details are presented first and in greater depth, including specifics about MSI packages, Windows services, security groups, and Group Policy adjustments. Windows-specific tools and patterns (MSI, NT SERVICE accounts, Group Policy) are described before their Linux equivalents, and troubleshooting/logging paths are Windows-first. Linux instructions are present and reasonably detailed, but some advanced configuration and troubleshooting guidance (e.g., security groups, service accounts) are more thoroughly covered for Windows.
Recommendations
  • Alternate the order of Windows and Linux sections, or present them in parallel tables to avoid Windows-first bias.
  • Ensure Linux installation details include equivalent information on service accounts, security groups, and permissions, if applicable.
  • Provide Linux-specific troubleshooting tips, such as SELinux/AppArmor considerations, systemd unit file locations, and log rotation.
  • Mention Linux package management commands (e.g., apt, yum, zypper) for agent installation and removal.
  • If Group Policy is discussed for Windows, mention Linux equivalents (e.g., PAM, sudoers, systemd service permissions) where relevant.
  • Include parity in advanced configuration examples, such as environment variable management and post-uninstall cleanup steps.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/system-center-virtual-machine-manager/built-in-roles.md ...ystem-center-virtual-machine-manager/built-in-roles.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation is focused exclusively on Azure Arc-enabled SCVMM, a Windows-centric technology (System Center Virtual Machine Manager). All role definitions and actions pertain to SCVMM resources, which are only available on Windows. There are no references to Linux equivalents, Linux management tools, or cross-platform scenarios. The documentation does not mention or provide examples for Linux-based environments, nor does it clarify the lack of Linux support.
Recommendations
  • Explicitly state in the introduction that Azure Arc-enabled SCVMM is a Windows-only solution and not applicable to Linux environments.
  • Provide links or references to Azure Arc documentation for Linux-based management (e.g., Azure Arc for Linux servers, Azure Arc for Kubernetes) to guide Linux users.
  • Add a comparison table or section outlining Azure Arc features for both Windows (SCVMM) and Linux, clarifying where each applies.
  • If possible, mention alternative Azure Arc built-in roles or management approaches for Linux workloads.
  • Ensure that related documentation pages (e.g., 'Next steps') include Linux-relevant links and guidance for parity.
GitHub Create Pull Request
← Previous Page 18 of 94 Next →