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 126-150 of 2334 flagged pages
Azure Arc Plan for deployment ...phere/support-matrix-for-arc-enabled-vmware-vsphere.md
High Priority View Details →
Scanned: 2026-01-11 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 displays a Windows bias by listing Windows requirements and tools (such as .NET Framework and PowerShell) before Linux equivalents, referencing Windows-specific download links, and mentioning Windows Admin Center and PowerShell explicitly. There are no Linux command examples or detailed Linux tool requirements beyond a brief mention of systemd and wget. Windows tooling is described in more detail and with direct download links, while Linux requirements are minimal and lack parity in guidance.
Recommendations
  • Provide Linux installation examples and commands (e.g., bash scripts, package manager instructions) alongside Windows/PowerShell examples.
  • List Linux requirements with equal detail, including supported distributions, required packages, and troubleshooting steps.
  • Include direct links to Linux installation guides and resources, similar to those provided for Windows.
  • Mention Linux tools and patterns (e.g., SSH, systemd service management) with the same prominence as Windows tools.
  • Ensure that networking requirements and scenarios are described for both Windows and Linux environments, including Linux-specific use cases.
GitHub Create Pull Request
Azure Arc Upgrade the Azure Arc resource bridge ...l-machine-manager/upgrade-azure-arc-resource-bridge.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily oriented toward Windows environments, specifically SCVMM (System Center Virtual Machine Manager), and assumes the use of Windows servers and workstations. All examples and instructions reference Windows tools and workflows, such as VHDX files, SCVMM servers, and do not mention or provide Linux equivalents or cross-platform alternatives. There are no Linux-specific instructions or examples, and the upgrade process is described solely in the context of Windows infrastructure.
Recommendations
  • Include explicit guidance for Linux environments, such as how to perform upgrades from Linux workstations if supported.
  • Provide examples using Linux-compatible tools and formats (e.g., mention VHD rather than only VHDX, or clarify cross-platform support).
  • Clarify whether the az arcappliance CLI and upgrade process can be run from Linux or macOS, and provide instructions if so.
  • Add troubleshooting steps and prerequisites relevant to Linux systems (e.g., file permissions, storage locations, etc.).
  • If the resource bridge is Windows-only by design, clearly state this limitation early in the documentation.
GitHub Create Pull Request
Azure Arc Customer intent: "As a network administrator, I want to configure secure outbound connectivity for the Azure Connected Machine agent so that I can ensure proper communication with Azure Arc while adhering to my organization's security policies." ...les/azure-arc/servers/includes/network-requirements.md
High Priority View Details →
Scanned: 2026-01-11 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 several signs of Windows bias. Windows-specific tools and terminology (e.g., Windows Admin Center, Windows installation package, Windows TLS configuration issues) are mentioned before or more prominently than their Linux equivalents. The cryptographic protocol section provides detailed information and troubleshooting links for Windows, while Linux guidance is limited to referencing OpenSSL. There are no Linux-specific configuration or troubleshooting examples, and Windows scenarios (such as hotpatching, pay-as-you-go billing, and TLS registry settings) are described in detail, whereas Linux scenarios are not. Windows-related endpoints and features are listed before Linux ones in tables and descriptions.
Recommendations
  • Provide Linux-specific configuration and troubleshooting examples, such as how to verify TLS settings using OpenSSL or update cipher suites.
  • Include parity in endpoint tables, such as listing Linux installation and update URLs before or alongside Windows equivalents.
  • Add references to Linux management tools (e.g., Cockpit, Ansible) where Windows Admin Center is mentioned.
  • Offer detailed guidance for Linux-specific scenarios (e.g., SELinux, iptables/firewalld configuration for outbound connectivity).
  • Ensure troubleshooting links and sections are available for Linux, not just Windows.
  • Balance the order of presentation so that Linux and Windows are treated equally in examples and explanations.
GitHub Create Pull Request
Azure Arc Automatic extension upgrade for Azure Arc-enabled servers ...e-arc/servers/manage-automatic-vm-extension-upgrade.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page provides guidance for both Windows and Linux Azure Arc-enabled servers, but there is a noticeable Windows bias. Windows-specific tools (Azure PowerShell) are given equal prominence to cross-platform tools (Azure CLI), and PowerShell examples are included alongside CLI examples. Windows-only extensions are listed explicitly, while Linux-only extensions are not. The ordering of tools and examples often places Windows-centric options (PowerShell) before or alongside cross-platform or Linux-native options, and there is no explicit Linux shell example (e.g., bash script) beyond generic CLI usage.
Recommendations
  • Add explicit Linux shell (bash/zsh) examples for common operations, especially in the CLI section.
  • List any Linux-only extensions if applicable, to balance the explicit mention of Windows-only extensions.
  • Consider reordering tool guidance to present cross-platform options (Azure CLI) before Windows-centric ones (PowerShell).
  • Clarify that Azure CLI commands work natively in Linux environments and provide sample usage in a Linux shell context.
  • Where PowerShell is mentioned, also mention Linux-native scripting alternatives if available.
  • Ensure screenshots and UI references do not assume a Windows environment unless necessary.
GitHub Create Pull Request
Azure Arc Enable VM Extensions Using Azure Resource Manager Template ...les/azure-arc/servers/manage-vm-extensions-template.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exhibits a Windows bias primarily through exclusive use of PowerShell for deployment commands, with no equivalent Azure CLI or Bash examples for Linux users. All command-line instructions are shown in PowerShell syntax, and file paths use Windows-style formatting (e.g., 'D:\Azure\Templates\...'). While ARM template JSON examples are provided for both Linux and Windows extensions, the operational instructions and deployment workflow are centered around Windows tooling and patterns. There is no demonstration of Linux-native workflows or cross-platform command-line parity.
Recommendations
  • Add equivalent Azure CLI examples for deploying ARM templates, especially for Linux users.
  • Include Bash shell command examples for template deployment, using Linux-style file paths.
  • Present deployment commands for both Windows and Linux side-by-side, or in separate sections, to avoid Windows-first ordering.
  • Explicitly mention cross-platform tooling options and clarify which commands are suitable for Linux environments.
  • Ensure that references to file paths and environment variables include both Windows and Linux formats.
GitHub Create Pull Request
Azure Arc Manage and maintain the Azure Connected Machine agent ...s/blob/main/articles/azure-arc/servers/manage-agent.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation generally maintains parity between Windows and Linux by providing separate, detailed instructions for both platforms. However, there is evidence of Windows bias: Windows instructions and tools (such as PowerShell, Group Policy, Microsoft Update, and Control Panel) are often presented first or in greater detail, and Windows-specific management patterns (like WSUS, Configuration Manager, and MSI installer options) are described extensively. PowerShell examples are frequently included, while equivalent Linux scripting or automation examples are missing. Windows-centric terminology and workflows (e.g., registry editing, Group Policy) are covered in depth, whereas Linux alternatives (such as systemd, package manager hooks, or shell scripting) are not discussed.
Recommendations
  • Alternate the order of Windows and Linux sections to avoid consistently presenting Windows first.
  • Provide Linux automation examples (e.g., Bash scripts for upgrades/uninstalls, systemd unit file management) where PowerShell scripts are given for Windows.
  • Include Linux equivalents for Windows-specific management tools (e.g., describe how to automate agent upgrades/removal using Ansible, Chef, or shell scripts).
  • Expand Linux troubleshooting and logging guidance to match the depth of Windows instructions (e.g., mention relevant log files, systemctl commands, etc.).
  • Reference Linux configuration management and update infrastructure (e.g., unattended-upgrades, dnf-automatic, zypper services) alongside Windows Update/WSUS.
  • Where registry or Group Policy is discussed for Windows, mention Linux configuration file or environment variable management approaches.
GitHub Create Pull Request
Azure Arc Enable VM Extensions Using the Azure CLI (Windows and Linux) ...articles/azure-arc/servers/manage-vm-extensions-cli.md
High Priority View Details →
Scanned: 2026-01-11 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 Windows bias in several ways. Most code examples for enabling and updating extensions use Windows-specific tools and commands (e.g., powershell.exe in Custom Script Extension settings). Extension types and examples (Antimalware, DatadogWindowsAgent, DependencyAgentWindows) are predominantly Windows-focused, with little or no explicit Linux equivalent shown. Linux-specific extension types (e.g., KeyVaultForLinux) are mentioned only as alternatives, not demonstrated. There are no examples showing Linux shell commands or scripts, nor are Linux-specific extension settings or patterns illustrated.
Recommendations
  • Provide parallel Linux examples for each extension operation, using bash/sh commands in Custom Script Extension settings.
  • Show how to enable Linux-specific extensions (e.g., DependencyAgentLinux, DatadogLinuxAgent) with full example commands.
  • Balance extension examples to include both Windows and Linux scenarios, with clear indication of OS applicability.
  • When showing Custom Script Extension, alternate between powershell.exe and bash/sh scripts in the 'commandToExecute' parameter.
  • Add notes or tables summarizing which extensions are available for Windows, Linux, or both, and link to relevant documentation.
  • Ensure troubleshooting and related content includes Linux-specific guidance and references.
GitHub Create Pull Request
Azure Arc VM Extension Management with Azure Arc-Enabled Servers ...ain/articles/azure-arc/servers/manage-vm-extensions.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Windows Heavy Examples
Summary
The documentation page demonstrates a Windows bias in several ways: Windows extensions are listed and described before Linux extensions, the Windows table is significantly longer and more detailed, and several Windows-specific tools and patterns (e.g., Windows Admin Center, PowerShell, Windows Patch extension) are highlighted. There are more Windows-only extensions and features described, and Windows tools are mentioned explicitly, while Linux equivalents are less emphasized or missing. The deployment methods list Azure PowerShell (Windows-centric) before CLI, and Windows Admin Center is featured as a management tool without a Linux counterpart.
Recommendations
  • Present Windows and Linux extension tables in parallel or interleaved, rather than listing Windows first and in more detail.
  • Ensure parity in extension descriptions and examples for Linux, including more Linux-specific extensions and management tools.
  • Highlight Linux management tools (such as Cockpit, Ansible, or native SSH) where appropriate, similar to the mention of Windows Admin Center.
  • Provide Linux-first or cross-platform examples for extension deployment, and avoid listing Windows-centric tools (e.g., PowerShell) before cross-platform alternatives (e.g., Azure CLI).
  • Expand documentation to include Linux-specific automation and configuration scenarios, ensuring equal coverage for both platforms.
GitHub Create Pull Request
Azure Arc How to modernize server management from Configuration Manager to Azure Arc ...icles/azure-arc/servers/modernize-server-management.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. While it mentions Linux support and parity as a benefit of Azure Arc, examples and onboarding guidance are primarily Windows-centric. Windows-specific tools and licensing (Scheduled Task, Windows Server Software Assurance) are referenced, and onboarding instructions focus on Windows scenarios. There are no explicit Linux onboarding examples, nor are Linux-native tools or patterns (e.g., systemd, cron) mentioned. The functional mapping and feature descriptions generally treat Windows as the default, with Linux support noted as an enhancement rather than a core scenario.
Recommendations
  • Add explicit onboarding instructions and examples for Linux servers, including use of Linux-native tools (e.g., systemd timers, cron jobs) for agent installation and management.
  • Provide Linux-specific examples in sections describing functionality (e.g., patching, configuration, reporting), such as referencing Linux package managers, configuration files, and security tools.
  • Balance references to Windows licensing and tools with equivalent Linux scenarios (e.g., mention Linux support contracts or open-source alternatives).
  • Ensure that all feature descriptions and guidance highlight Linux support as a first-class scenario, not just as an add-on.
  • Include screenshots or command-line examples for both Windows (PowerShell, Scheduled Task) and Linux (bash, systemd, cron) where relevant.
GitHub Create Pull Request
Azure Arc Connect machines at scale with a Configuration Manager custom task sequence ...c/servers/onboard-configuration-manager-custom-task.md
High Priority View Details →
Scanned: 2026-01-11 00:00
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 strong Windows bias. All examples and instructions are exclusively for Windows environments, specifically using Microsoft Configuration Manager and Windows Installer (.msi) packages. The agent download and installation steps reference only the Windows version, and all automation is shown via PowerShell scripts. There is no mention of Linux equivalents, Linux agent packages, or cross-platform deployment strategies. The use of Windows-specific tools and patterns (Configuration Manager, PowerShell, .msi) is pervasive throughout the guide.
Recommendations
  • Add parallel instructions and examples for Linux environments, including how to deploy the Connected Machine Agent on Linux servers at scale.
  • Reference and provide download links for the Linux agent package (typically .deb or .rpm) alongside the Windows .msi.
  • Include sample task sequences or automation scripts using Bash or other Linux-native tools (e.g., shell scripts, Ansible, or cloud-init).
  • Describe how to use cross-platform deployment tools (such as Ansible, Puppet, or Azure Automation) for onboarding Linux machines.
  • Explicitly state platform support and clarify any differences in process or tooling between Windows and Linux.
  • Provide troubleshooting and verification steps for Linux machines, not just Windows.
GitHub Create Pull Request
Azure Arc Connect hybrid machines to Azure at scale ...rticles/azure-arc/servers/onboard-service-principal.md
High Priority View Details →
Scanned: 2026-01-11 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 several instances of Windows bias. Windows and PowerShell tools are mentioned first or exclusively in multiple sections, such as the creation of service principals and script generation. PowerShell examples are provided in detail, while Linux equivalents (e.g., Bash, shell commands) are less emphasized or missing. Windows-specific tools and patterns (e.g., .ps1 scripts, PowerShell requirements) are highlighted, and Linux instructions are often referenced only as alternatives, not as primary examples.
Recommendations
  • Ensure Linux/Bash examples are provided alongside PowerShell, with equal detail and prominence.
  • Present Linux and Windows instructions in parallel, rather than listing Windows first.
  • Explicitly mention Linux tools and automation patterns (e.g., Bash scripting, Ansible) where PowerShell is discussed.
  • Include screenshots or walkthroughs for Linux onboarding, not just Windows/PowerShell.
  • Clarify any platform-specific limitations or requirements for both Windows and Linux.
  • Review and update output examples to show both .ps1 and .sh script results.
  • Avoid language that implies Windows is the default or preferred platform.
GitHub Create Pull Request
Azure Arc Connect hybrid machines to Azure using a deployment script ...blob/main/articles/azure-arc/servers/onboard-portal.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page presents Windows installation instructions before Linux, provides more detailed Windows examples (including PowerShell commands and references to Windows Installer tools), and uses Windows-specific tooling and terminology (e.g., msiexec, PowerShell, Windows Installer package). Linux instructions are present and reasonably detailed, but Windows patterns and tools are introduced first and with more depth, indicating a Windows-first and Windows-tooling bias.
Recommendations
  • Alternate the order of Windows and Linux sections, or present both in parallel where possible.
  • Provide equally detailed Linux examples, including troubleshooting steps, log locations, and command-line options.
  • Reference Linux package management tools (e.g., apt, yum, rpm) and shell scripting patterns where appropriate.
  • Avoid assuming PowerShell or Windows Installer familiarity; provide equivalent Linux context (e.g., systemctl for service management, environment variable configuration via shell).
  • Ensure that links to further documentation and troubleshooting guides are equally available for Linux users.
GitHub Create Pull Request
Azure Arc Connect machines from Azure Automation Update Management ...zure-arc/servers/onboard-update-management-machines.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page describes onboarding both Windows and Linux machines to Azure Arc via Automation Update Management, but the examples and tooling references are Windows-centric. The runbook names use 'Add-UMMachinesToArcWindowsChild' and 'Add-UMMachinesToArcLinuxChild', but all references to viewing job status and logs mention Azure PowerShell and the Azure portal, with no mention of Linux-native tools or CLI usage. There are no explicit Linux command examples, and the troubleshooting and verification steps rely on graphical interfaces or Windows-oriented tools.
Recommendations
  • Provide explicit Linux command-line examples for onboarding and verification, such as using Bash or shell scripts.
  • Mention Linux-native tools (e.g., journalctl, systemctl) for troubleshooting agent installation and connectivity.
  • Include instructions for viewing job status and logs using Azure CLI on Linux, not just PowerShell or portal.
  • Balance references to Windows and Linux throughout the documentation, ensuring parity in examples and troubleshooting steps.
GitHub Create Pull Request
Azure Arc Plan and Deploy Azure Arc-Enabled Servers ...articles/azure-arc/servers/plan-at-scale-deployment.md
High Priority View Details →
Scanned: 2026-01-11 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 demonstrates a Windows bias in several ways: Windows and PowerShell tools are mentioned first or exclusively (e.g., service principal creation via Azure PowerShell), and there is a lack of explicit Linux command-line or automation examples. References to automation and onboarding scripts mention both Linux and Windows, but do not provide parity in examples or highlight Linux-specific tooling or patterns. The documentation assumes familiarity with Windows-centric tools and does not provide equivalent Linux shell or automation guidance.
Recommendations
  • Provide explicit Linux shell (bash) and automation examples alongside PowerShell examples for all onboarding and management tasks.
  • Mention Linux-native tools (such as shell scripts, Ansible, or cloud-init) where automation is discussed, not just Windows/PowerShell.
  • Ensure that instructions for creating service principals and other Azure resources include CLI (az) and bash options, not only Azure PowerShell or portal.
  • Where sample scripts are referenced, include direct links to both Linux and Windows versions, and clarify any OS-specific steps.
  • Review all sections for implicit Windows-first ordering and alternate with Linux-first or neutral presentation.
  • Add troubleshooting and management guidance specific to Linux environments, including common issues and solutions.
GitHub Create Pull Request
Azure Arc How to prepare to deliver Extended Security Updates for Windows Server 2012 through Azure Arc ...azure-arc/servers/prepare-extended-security-updates.md
High Priority View Details →
Scanned: 2026-01-11 00:00
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 (e.g., Group Policy, Configuration Manager, SCVMM). There are no Linux-specific instructions, examples, or mentions of Linux equivalents for onboarding, patching, or certificate management. Windows tools and patterns are referenced exclusively, and Linux scenarios are not addressed.
Recommendations
  • Add explicit guidance for onboarding Linux servers to Azure Arc, including supported distributions and prerequisites.
  • Provide Linux-specific deployment examples (e.g., using shell scripts, Ansible, or native Linux automation tools) alongside Windows methods.
  • Include instructions for managing certificates on Linux systems, such as using OpenSSL or system trust stores.
  • Clarify whether ESU delivery via Azure Arc is available for Linux servers, and if not, explicitly state the scope.
  • Where possible, mention cross-platform tools or approaches for hybrid environments, and avoid assuming Windows-only infrastructure.
GitHub Create Pull Request
Azure Arc Quickstart - Connect a machine to Arc-enabled servers (Windows or Linux install script) ...n/articles/azure-arc/servers/quick-enable-hybrid-vm.md
High Priority View Details →
Scanned: 2026-01-11 00:00
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. Windows instructions (PowerShell usage) are presented before Linux instructions, and the Windows section explicitly references PowerShell as the required tool, while the Linux section is more generic. The documentation refers to Windows-specific tools (PowerShell, Local Administrators group) and patterns before their Linux equivalents, and the Windows agent installation steps are described first in the 'Install the agent by using the script' section.
Recommendations
  • Alternate the order of Windows and Linux instructions, or present them side-by-side to avoid implicit prioritization.
  • Explicitly mention Linux tools (e.g., Bash, sudo) in the prerequisites and installation steps, similar to how PowerShell is referenced for Windows.
  • Provide parity in detail and troubleshooting steps for both platforms, ensuring Linux instructions are as comprehensive as Windows.
  • Include screenshots or command-line output examples for Linux, not just Windows.
  • Where possible, use neutral language and avoid assuming Windows as the default (e.g., avoid phrases like 'Open an elevated PowerShell prompt' without a Linux equivalent).
GitHub Create Pull Request
Azure Arc Azure Arc-enabled servers Overview ...-docs/blob/main/articles/azure-arc/servers/overview.md
High Priority View Details →
Scanned: 2026-01-11 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 describes Azure Arc-enabled servers as supporting both Windows and Linux, but several sections and linked resources prioritize Windows tools and patterns. Examples include referencing PowerShell and Windows registry before Linux equivalents, linking to Windows-specific tabs in automation guides, and mentioning Windows features (registry, files) before Linux daemons. There are no explicit Linux command-line or tool examples, and Windows terminology is often used first or exclusively.
Recommendations
  • Ensure all examples and linked guides provide parity between Windows and Linux, including Bash and Linux command-line instructions where PowerShell is mentioned.
  • When listing supported features (e.g., configuration assessment), mention Linux equivalents (e.g., systemd services, config files) alongside Windows registry and files.
  • Avoid defaulting to Windows tabs or examples in linked documentation; provide equal visibility for Linux scenarios.
  • Include explicit Linux tool references and examples (e.g., shell scripts, Linux package managers) in configuration and automation sections.
  • Review terminology to avoid Windows-first phrasing; use 'Windows and Linux' or 'Linux and Windows' interchangeably.
GitHub Create Pull Request
Azure Arc Connected Machine agent prerequisites .../blob/main/articles/azure-arc/servers/prerequisites.md
High Priority View Details →
Scanned: 2026-01-11 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 demonstrates a moderate Windows bias. Windows-specific instructions and tools (such as PowerShell scripts and Group Policy Editor) are presented in detail, often before or in greater depth than Linux equivalents. For example, installation script modifications for limited support OS are shown only for Windows (with PowerShell), while Linux is mentioned briefly without example. Windows tools like 'gpedit.msc' and Group Policy are described extensively, whereas Linux system management requirements are listed but not explained. Resource provider registration examples are given for both Azure PowerShell and Azure CLI, but the PowerShell example appears first.
Recommendations
  • Provide Linux-specific installation script examples, especially for limited support scenarios, to match the detail given for Windows.
  • Include Linux system management equivalents for tasks like user rights assignment (e.g., systemd service configuration, user/group permissions).
  • Alternate the order of Windows and Linux instructions/examples to avoid consistently presenting Windows first.
  • Expand on Linux troubleshooting and configuration steps where Windows tools (like Group Policy Editor) are described in detail.
  • Ensure parity in examples and guidance for both platforms throughout the documentation.
GitHub Create Pull Request
Azure Arc Use Azure Private Link to Connect Servers to Azure Arc by Using a Private Endpoint ...in/articles/azure-arc/servers/private-link-security.md
High Priority View Details →
Scanned: 2026-01-11 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 demonstrates a moderate Windows bias. Windows terminology, tools, and examples are often presented first or exclusively, such as referencing Windows Admin Center, using Windows file paths in examples, and listing Windows agent download links before Linux equivalents. Linux instructions are present but less detailed, and there is a lack of parity in troubleshooting and configuration examples for Linux environments.
Recommendations
  • Ensure Linux instructions are given equal prominence and detail as Windows instructions, including explicit Linux agent download and installation steps.
  • Provide Linux-specific troubleshooting commands and examples, such as using dig or systemd-resolved for DNS checks.
  • Mention Linux tools (e.g., SSH, firewalld, iptables) alongside Windows tools (e.g., Windows Admin Center), and clarify which features are available or unsupported on each platform.
  • When listing steps for editing hosts files or configuring DNS, present Linux and Windows instructions side-by-side, rather than Windows first.
  • Include explicit references to Linux package managers (apt, yum, zypper) and agent installation commands.
  • Avoid using Windows-centric terminology (e.g., 'server' to mean Windows Server) when referring to cross-platform machines; use 'machine' or 'host' where appropriate.
GitHub Create Pull Request
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
High Priority View Details →
Scanned: 2026-01-11 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 exclusively providing PowerShell script examples (e.g., 'Write-Host Hello World!') and omitting any Linux shell script (bash/sh) examples. The use of PowerShell syntax as the sole example implies a Windows-first approach, and there is no mention of Linux-specific patterns, tools, or script types. This may lead Linux users to believe the feature is primarily for Windows environments or that Linux is not fully supported.
Recommendations
  • Include Linux shell script examples (e.g., 'echo Hello World!') alongside PowerShell examples in all relevant command samples.
  • Explicitly state that both Windows and Linux Arc-enabled servers are supported, and clarify any differences in usage or script syntax.
  • Add a section or note describing how to use the run-command feature for Linux servers, including common use cases and troubleshooting tips.
  • Where possible, alternate the order of examples or provide parallel examples for both platforms to avoid implicit prioritization of Windows.
GitHub Create Pull Request
Azure Arc Migrate Azure Arc-enabled server to Azure ...rticles/azure-arc/servers/scenario-migrate-to-azure.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by frequently referencing Azure PowerShell and Windows-centric tools first, providing detailed PowerShell commands and workflows, and omitting explicit Linux shell (bash) examples. While Linux is mentioned in passing (e.g., Linux agent), there are no concrete Linux CLI commands or instructions, and PowerShell is consistently presented as the primary method for management tasks.
Recommendations
  • Provide equivalent Linux shell (bash) command examples alongside PowerShell commands, especially for inventorying extensions and managing role assignments.
  • Explicitly mention and link to Linux-specific documentation or tools where available, such as az CLI usage in bash environments.
  • Ensure that instructions for installing and managing agents and extensions are equally detailed for both Windows and Linux, including troubleshooting steps.
  • Avoid presenting Windows/PowerShell methods first; alternate or parallelize instructions for both platforms.
  • Include screenshots or code snippets from Linux environments to reinforce parity.
GitHub Create Pull Request
Azure Arc Security overview ...b/main/articles/azure-arc/servers/security-overview.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by referencing PowerShell Desired State Configuration as the basis for guest configuration policies, without mentioning Linux equivalents (such as Ansible, Chef, or native shell scripts). Windows service accounts (e.g., NT SERVICE\himds, Local System, Network Service) are described in detail before their Linux counterparts, and examples (such as extension allowlists) focus on Windows-specific extensions. There are no explicit Linux configuration or security examples, and Linux tools or patterns are not discussed.
Recommendations
  • Include Linux-native configuration management equivalents (e.g., Ansible, Chef, shell scripts) in the guest configuration section.
  • Provide examples of extension allowlists and agent lockdown for Linux servers, referencing Linux-specific extensions and security tools.
  • Describe Linux service/daemon management patterns (e.g., systemd units, user accounts) with equal detail and prominence as Windows service accounts.
  • Mention Linux compliance and security best practices alongside Windows, such as SELinux, AppArmor, or auditd.
  • Ensure examples and recommendations are presented for both Windows and Linux platforms, or clarify platform-specific differences where relevant.
GitHub Create Pull Request
Azure Arc REST API Requests for the Run Command on Azure Arc-enabled Servers (Preview) ...ob/main/articles/azure-arc/servers/run-command-rest.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a strong Windows bias. All example scenarios use Windows Server as the target OS, with scripts written in PowerShell (New-NetFirewallRule). There are no examples for Linux servers, nor any mention of Linux shell scripting or Linux firewall tools. Windows-specific tools (PowerShell, New-AzStorageBlobSASToken) are referenced exclusively, and the documentation assumes a Windows-centric workflow throughout.
Recommendations
  • Add example scenarios for Linux Arc-enabled servers, including REST API payloads that execute bash scripts or use Linux-native firewall commands (e.g., ufw, iptables).
  • Explicitly mention Linux as a supported OS in the introduction and prerequisites.
  • Provide parity in script examples: for every PowerShell example, include a bash/sh example for Linux.
  • Reference Linux tools for generating SAS tokens and managing blobs, if available, or provide cross-platform alternatives.
  • Clarify any OS-specific limitations or differences in Run command support.
  • Update related content links to include Linux-focused documentation or guides.
GitHub Create Pull Request
Azure Arc Run command on Azure Arc-enabled servers (Preview) ...cs/blob/main/articles/azure-arc/servers/run-command.md
High Priority View Details →
Scanned: 2026-01-11 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 subtle Windows bias. While it claims support for both Windows and Linux, examples and next steps focus on Azure CLI and PowerShell, with PowerShell (a Windows-centric tool) given equal prominence to CLI and REST. There are no explicit Linux shell (bash) examples or references to Linux-native tooling. Windows tools and patterns (PowerShell, Remote Desktop Protocol) are mentioned, while SSH (the Linux equivalent) is referenced only in passing. The documentation does not provide Linux-specific usage patterns or examples.
Recommendations
  • Add explicit Linux shell (bash) examples for using Run command, alongside PowerShell examples.
  • Mention SSH as the Linux equivalent to RDP when discussing remote access alternatives.
  • Clarify and demonstrate Linux-native script execution (e.g., running bash scripts) in the overview.
  • Ensure that Linux tools and patterns are referenced with equal prominence to Windows tools.
  • Include troubleshooting or usage notes specific to Linux environments.
GitHub Create Pull Request
Azure Arc Configuration and remote access ...es/azure-arc/servers/security-machine-configuration.md
High Priority View Details →
Scanned: 2026-01-11 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 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 explanations for Windows-specific tools and patterns. Linux equivalents (such as Ansible, SSH management, or Linux-native configuration tools) are not mentioned or are only referenced in passing. There are no Linux-specific configuration or remote management examples, and the documentation assumes familiarity with Windows-centric tools and workflows.
Recommendations
  • Include Linux-native configuration management examples (e.g., using Ansible, Chef, or native Linux DSC).
  • Provide parity in remote access tooling by mentioning and documenting Linux equivalents to Windows Admin Center, or clarify that such equivalents do not exist and suggest best practices for Linux management.
  • Offer example workflows for Linux systems, such as SSH-based management, sudo configuration, and compliance checking using Linux tools.
  • Balance the order of presentation so that Linux and Windows scenarios are introduced together, rather than Windows tools and roles being described first or in greater detail.
  • Add explicit Linux-focused sections or callouts to ensure Linux administrators can find relevant guidance without needing to interpret Windows-centric instructions.
GitHub Create Pull Request
← Previous Page 6 of 94 Next →