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 326-350 of 2334 flagged pages
Azure Arc Diagnostics of Edge-Related Logs and Errors in Workload Orchestration .../azure-arc/workload-orchestration/diagnose-problems.md
High Priority View Details →
Scanned: 2026-01-10 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 strong Windows bias. All command-line examples use PowerShell syntax (with backticks for line continuation and Windows-style paths), and there are no bash, Linux shell, or cross-platform CLI examples. File paths in JSON templates and scripts use Windows drive letters and backslashes. Script automation is exclusively shown with PowerShell scripts (.ps1), with no mention of bash or shell alternatives. There is no guidance for Linux or macOS users, nor any mention of how to adapt the instructions for non-Windows environments.
Recommendations
  • Provide equivalent bash or shell script examples for all PowerShell commands, using POSIX-compliant syntax and Linux-style paths.
  • Show how to run Azure CLI commands in Linux/macOS terminals, including line continuation with '\' and environment variable usage.
  • Include notes or sections for Linux/macOS users, highlighting any differences in file paths, script execution, or prerequisites.
  • Offer downloadable script templates in both PowerShell (.ps1) and bash (.sh) formats.
  • Avoid using Windows-only file paths in JSON templates; use relative paths or examples compatible with both platforms.
  • Explicitly state cross-platform compatibility for all tools and extensions, and provide troubleshooting tips for Linux environments.
GitHub Create Pull Request
Azure Arc Migrate Existing Target Resources to General Availability ...s/azure-arc/workload-orchestration/migration-script.md
High Priority View Details →
Scanned: 2026-01-10 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 demonstrates a Windows bias by providing only a PowerShell migration script example, referencing a .ps1 file (PowerShell script), and instructing users to run the script in PowerShell. There are no equivalent instructions or examples for Linux users (e.g., Bash scripts or cross-platform alternatives), nor is there mention of how to perform the migration on non-Windows systems.
Recommendations
  • Provide a Bash or shell script alternative for Linux users, or clarify if the PowerShell script can be run using PowerShell Core on Linux/macOS.
  • Include explicit instructions for running the migration on Linux and macOS, including installation steps for PowerShell Core if needed.
  • Mention cross-platform compatibility of the migration script, if applicable, and test/document any platform-specific caveats.
  • Ensure that examples and instructions for Linux are given equal prominence and detail as those for Windows.
GitHub Create Pull Request
Azure Arc Onboarding Scripts for Workload Orchestration ...azure-arc/workload-orchestration/onboarding-scripts.md
High Priority View Details →
Scanned: 2026-01-10 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 strong Windows bias. All script examples use PowerShell (.ps1) and instruct users to open a PowerShell terminal, with no mention of Bash, Linux shell, or cross-platform alternatives. Prerequisites use 'winget', a Windows-only package manager, to install tools like Azure CLI and kubectl, without providing equivalent Linux/macOS instructions (e.g., apt, yum, brew). There are no Linux-specific onboarding script examples, nor any notes about running these scripts on non-Windows platforms.
Recommendations
  • Provide equivalent onboarding script examples for Bash/shell environments, including .sh scripts if available.
  • List Linux/macOS installation commands for prerequisites (e.g., use apt, yum, or brew for Azure CLI and kubectl).
  • Clarify whether the onboarding scripts are cross-platform, and if not, provide guidance or alternatives for Linux/macOS users.
  • Mention and document any required dependencies or compatibility notes for running the scripts on non-Windows systems.
  • Consider using cross-platform scripting languages (e.g., Python) or provide containerized solutions for onboarding.
GitHub Create Pull Request
Azure Arc Release Notes for Workload Orchestration ...cles/azure-arc/workload-orchestration/release-notes.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page predominantly features CLI examples using Powershell syntax (backticks for line continuation, variable notation), which is specific to Windows environments. There are no Bash or Linux shell equivalents provided, and the only explicit CLI examples for configuration management use Powershell. This suggests a bias towards Windows users, potentially making it less accessible for Linux users who use Bash or other shells.
Recommendations
  • Provide equivalent Bash examples for all CLI commands, especially those currently shown only in Powershell.
  • When presenting CLI instructions, use cross-platform syntax (e.g., avoid Powershell-specific line continuation and variable notation) or show both Windows and Linux variants.
  • Explicitly mention that the Azure CLI is cross-platform and clarify any OS-specific instructions.
  • Review all examples and ensure Linux users are equally supported, including troubleshooting and file path conventions.
GitHub Create Pull Request
Azure Arc Troubleshooting for Workload Orchestration ...es/azure-arc/workload-orchestration/troubleshooting.md
High Priority View Details →
Scanned: 2026-01-10 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 strong Windows bias. Most troubleshooting steps and command examples are provided exclusively in PowerShell, with Windows-centric syntax and patterns (e.g., use of variables like $var, ConvertTo-Json, Out-File, [Convert]::ToBase64String). Linux/Bash equivalents are missing for nearly all steps except the service group queries, which are presented in both Bash and PowerShell. Windows tools and workflows (PowerShell, Windows file encoding notes) are mentioned without Linux alternatives, and Windows commands are presented first or exclusively in most sections.
Recommendations
  • Provide Bash/Linux equivalents for all PowerShell commands, especially for az, kubectl, docker, and file manipulation steps.
  • Include Linux-specific instructions for file encoding and editing (e.g., using iconv, nano, or vim instead of Windows Notepad encoding advice).
  • Use cross-platform variable syntax in examples (e.g., $var for PowerShell, $var for Bash, and avoid Windows-only constructs like @{ } | ConvertTo-Json).
  • Explicitly state platform requirements or differences where applicable, and ensure troubleshooting steps are accessible to Linux users.
  • Review all command snippets to ensure they work on both Windows and Linux shells, or provide clear tabs/sections for each OS.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/active-directory-prerequisites.md ...icles/azure-arc/data/active-directory-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 a strong Windows bias. All examples and instructions for managing Active Directory objects (OUs, users, permissions) are given using Windows GUI tools (Active Directory Users and Computers) and Windows PowerShell. There are no examples or guidance for performing these tasks from Linux environments, nor is there mention of cross-platform tools or alternatives. The prerequisite steps assume a Windows-based domain controller and link to a Windows Server-specific guide for setting up AD.
Recommendations
  • Include instructions and examples for managing Active Directory objects using cross-platform tools such as ldapadd, ldapmodify, or samba-tool, which can be run from Linux.
  • Mention and provide guidance for using remote management tools (e.g., RSAT from Windows, or LDAP tools from Linux) to interact with Active Directory.
  • Add Linux shell command equivalents for PowerShell examples, where possible.
  • Clarify whether a Windows Server domain controller is strictly required, or if Samba-based AD DCs are supported.
  • Provide links to documentation for setting up and managing Active Directory from Linux environments.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/configure-transparent-data-encryption-sql-managed-instance.md ...igure-transparent-data-encryption-sql-managed-instance.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 Path Examples Windows Note Highlight
Summary
The documentation provides both Windows and Linux examples for file operations (copying certificates and keys), but Windows instructions and examples are consistently presented before Linux ones. Windows-specific issues (such as absolute path problems) are highlighted in notes, and Windows path syntax is used in examples. There are no PowerShell-only or Windows-only tools, but the ordering and emphasis show a subtle Windows bias.
Recommendations
  • Alternate the order of Windows and Linux instructions/examples, or present Linux first to match the prevalence of Linux in container/Kubernetes environments.
  • Use neutral path variables in examples (e.g., $HOME/sqlcerts/servercert.crt) before showing OS-specific syntax.
  • Add notes for Linux-specific issues if any, to balance the attention given to Windows.
  • Consider grouping OS-specific instructions in expandable sections, or clarify that Linux is the default/preferred environment for Kubernetes workloads.
  • Review all examples to ensure parity in detail and clarity between Windows and Linux instructions.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/connect-managed-instance.md ...in/articles/azure-arc/data/connect-managed-instance.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 Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by primarily referencing Windows-centric tools (SQL Server Management Studio), mentioning Windows tools before Linux alternatives, and lacking explicit Linux client examples or instructions. While Azure Data Studio and sqlcmd are cross-platform, the documentation does not provide Linux-specific connection instructions or highlight Linux-native SQL clients. The network configuration guidance is focused on Azure VM scenarios, which are often Windows-based, and does not address Linux VM nuances.
Recommendations
  • Include explicit examples for connecting from Linux environments, such as using Linux-native SQL clients (e.g., DBeaver, SquirrelSQL) or command-line tools.
  • Provide step-by-step instructions for configuring firewall rules and network access on Linux VMs, including relevant iptables or firewalld commands.
  • Present connection instructions for both Windows and Linux platforms in parallel, ensuring parity and clarity for users of either OS.
  • Mention Linux package installation steps for sqlcmd and Azure Data Studio, and clarify any OS-specific prerequisites.
  • Add troubleshooting tips for common Linux connectivity issues (e.g., SELinux, ufw, etc.).
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/install-client-tools.md ...b/main/articles/azure-arc/data/install-client-tools.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 exhibits mild Windows bias. Windows installation links are listed before Linux/macOS in some tool rows (e.g., kubectl, curl), and there are specific notes about using cmd.exe instead of PowerShell for curl on Windows 10. The footnote about curl in PowerShell is Windows-specific, and there are no equivalent Linux shell notes. Linux installation instructions are sometimes less explicit (e.g., 'install curl package' vs. a direct link). No Linux-specific troubleshooting or usage notes are provided.
Recommendations
  • Present installation links for all platforms in parallel order (e.g., Linux, macOS, Windows) or alphabetically to avoid Windows-first bias.
  • Provide explicit Linux installation instructions or direct links, not just 'install curl package'.
  • Include Linux shell usage notes where Windows/PowerShell notes are given (e.g., clarify curl behavior in bash/zsh).
  • Add troubleshooting tips for Linux environments if Windows-specific ones are included.
  • Ensure examples and footnotes cover both Windows and Linux usage patterns equally.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/edge-rag/prepare-dns.md ...s/blob/main/articles/azure-arc/edge-rag/prepare-dns.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 exclusively providing instructions for editing the hosts file using Windows-specific tools (Notepad, Administrator privileges, C:\Windows\System32\drivers\etc\hosts), without mentioning Linux or macOS equivalents. There are no examples or guidance for users on non-Windows platforms, and Windows patterns/tools are presented as the default.
Recommendations
  • Add instructions for editing the hosts file on Linux (e.g., using sudo and editing /etc/hosts with nano or vi).
  • Include macOS-specific guidance for updating /etc/hosts.
  • Present platform-specific instructions in parallel sections or a table, rather than only Windows steps.
  • Avoid assuming Windows as the default environment; clarify that steps may differ by OS.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/kubernetes/arc-gateway-simplify-networking.md ...zure-arc/kubernetes/arc-gateway-simplify-networking.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 provides both Azure CLI and Azure PowerShell examples for all major operations, but PowerShell is given equal prominence and detail, despite being primarily a Windows tool. There are no explicit Linux shell script examples (e.g., bash), and environment variable examples for proxy configuration use both Windows (PowerShell `$Env:`) and Linux (`export`) syntax, but the PowerShell examples are presented first in some sections. There is no mention of Linux-specific tools or patterns beyond Azure CLI, and no troubleshooting or operational guidance for Linux environments.
Recommendations
  • Add explicit bash/Linux shell script examples for key operations, especially for proxy configuration and environment setup.
  • Ensure that Linux environment variable examples (using `export`) are presented before or alongside PowerShell examples, not after.
  • Include troubleshooting steps or operational notes specific to Linux environments (e.g., SELinux, systemd, log locations).
  • Clarify that Azure CLI is cross-platform and recommend it as the default for Linux users.
  • Avoid presenting PowerShell as the primary or default method for cross-platform tasks; make it clear when PowerShell is Windows-specific.
  • Add notes or links to Linux-specific documentation where relevant.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/agent-release-notes.md ...main/articles/azure-arc/servers/agent-release-notes.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 exhibits several signs of Windows bias. Windows is consistently mentioned first in download links and feature tables. Troubleshooting and installation instructions focus on Windows-specific tools and patterns (e.g., 'msiexec', PowerShell, Command Prompt), with no equivalent Linux guidance provided. Known issues and fixes often detail Windows installer behaviors without Linux parallels. While Linux releases and features are included, examples and instructions are disproportionately Windows-centric.
Recommendations
  • Alternate the order of Windows and Linux references in download links and feature tables, or present them together to avoid implicit prioritization.
  • Provide Linux-specific troubleshooting and installation instructions (e.g., using 'rpm', 'dpkg', 'systemctl', or shell commands) alongside Windows examples.
  • Include Linux equivalents for all Windows-only notes, especially in sections like 'Known Issues' and installation guidance.
  • Ensure parity in the level of detail for both platforms when describing fixes, features, and configuration steps.
  • Add explicit Linux command-line examples and clarify any platform-specific requirements or behaviors.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/resource-graph-samples.md ...blob/main/articles/azure-arc/resource-graph-samples.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 mentions Azure PowerShell before Azure CLI when describing how to run queries, which may suggest a Windows-first bias. There is no mention of Linux-specific tools, shell environments, or examples (such as Bash), nor are there instructions tailored for Linux users. The page does not provide parity in examples or guidance for Linux users, focusing instead on Windows-centric tools and patterns.
Recommendations
  • List Azure CLI before Azure PowerShell when describing cross-platform usage, as CLI is natively supported on both Windows and Linux.
  • Include explicit examples for running queries in Bash or other Linux shells, demonstrating cross-platform compatibility.
  • Mention that Azure CLI and Resource Graph Explorer are available on Linux and macOS, not just Windows.
  • Add a section or note highlighting Linux usage patterns and any relevant differences or considerations for Linux users.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/cloud-native/identity-access.md ...cles/azure-arc/servers/cloud-native/identity-access.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 Missing Linux Example
Summary
The documentation page demonstrates a Windows-first perspective, referencing Windows-centric identity management concepts (Active Directory, Group Policy, LAPS) and tools before mentioning Linux equivalents. Windows access patterns (Remote Desktop) are described in detail, while Linux access (SSH) is mentioned only briefly and without example. Windows tools like LAPS are discussed exclusively, with no mention of Linux alternatives for local account management. There are no Linux-specific examples or guidance for hybrid identity scenarios.
Recommendations
  • Provide Linux-specific examples for identity and access management, such as using SSH with Microsoft Entra ID, and managing local Linux accounts.
  • Mention Linux-native tools or solutions for local account rotation and management, such as sssd, sudoers, or third-party password rotation tools.
  • Ensure parity in describing access patterns: give equal detail to SSH access for Linux as is given to Remote Desktop for Windows.
  • Include hybrid identity scenarios involving Linux servers, such as integrating Linux PAM with Microsoft Entra ID or Azure Arc.
  • Avoid assuming AD or Windows-centric management as the default; explicitly address both Windows and Linux environments throughout.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/manage-agent.md ...s/blob/main/articles/azure-arc/servers/manage-agent.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. Windows instructions and tooling (such as PowerShell, Group Policy, Microsoft Update, WSUS, Configuration Manager) are often described in greater detail, with more context and step-by-step guidance than their Linux equivalents. Windows examples frequently appear before Linux ones, and Windows-specific tooling is referenced extensively, while Linux instructions rely on standard package managers with less narrative. Some advanced configuration scenarios (e.g., update infrastructure, proxy environment variables) provide richer Windows guidance, including PowerShell scripts and GUI walkthroughs, compared to more basic Linux command-line instructions.
Recommendations
  • Provide parity in narrative detail for Linux instructions, including step-by-step guides for common Linux administration scenarios (e.g., using configuration management tools like Ansible, Puppet, or Chef for agent lifecycle management).
  • Include Linux-first or at least parallel examples when describing agent installation, upgrade, and removal, rather than listing Windows first.
  • Expand Linux proxy configuration guidance to match the depth of Windows coverage, including troubleshooting, service management, and environment variable persistence across distributions.
  • Reference Linux equivalents to Windows tools (e.g., systemd for service management, cron for scheduled upgrades, or package manager hooks for automation).
  • Offer more advanced Linux automation examples (e.g., shell scripts for bulk operations, integration with enterprise Linux management solutions).
  • Ensure that all tables and lists present Windows and Linux options with equal prominence and detail.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/manage-vm-extensions-cli.md ...articles/azure-arc/servers/manage-vm-extensions-cli.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 Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias in several ways: most command examples for VM extensions use Windows-specific tools (e.g., 'powershell.exe' in Custom Script Extension settings), extension types and names are often Windows-centric (e.g., 'IaaSAntimalware', 'DatadogWindowsAgent'), and Linux equivalents are either missing or mentioned secondarily (e.g., 'KeyVaultForLinux or KeyVaultForWindows'). There are no explicit Linux shell script examples, and the extension configuration examples do not show Linux usage patterns.
Recommendations
  • Provide parallel Linux examples for all extension commands, especially for Custom Script Extension (e.g., using bash/sh instead of powershell.exe).
  • Include Linux-specific extension types and settings (e.g., 'DependencyAgentLinux', 'DatadogLinuxAgent') in examples.
  • When listing extension types or names, mention Linux and Windows options equally and explicitly.
  • Add sample extension settings using Linux shell commands (e.g., 'commandToExecute': 'bash -c "ps aux | awk ..."').
  • Clarify which extensions are cross-platform and which are OS-specific, and provide guidance for both.
  • Avoid using Windows tools (like powershell.exe) as the default in examples; alternate or pair with Linux equivalents.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/overview.md ...-docs/blob/main/articles/azure-arc/servers/overview.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 describes Azure Arc-enabled servers as supporting both Windows and Linux, but several sections and linked resources prioritize Windows terminology, tools, and examples. PowerShell and Windows registry are mentioned explicitly, while Linux equivalents (such as shell scripting or Linux configuration files) are not. Some links and tabs default to Windows, and there is a lack of Linux-specific guidance or examples, especially in automation and configuration sections.
Recommendations
  • Provide equal coverage and examples for Linux, such as shell scripting and Linux-specific configuration management.
  • Ensure that documentation links and tabs offer both Windows and Linux options, and avoid defaulting to Windows.
  • Mention Linux tools and patterns (e.g., systemd, cron, package managers) alongside Windows tools like PowerShell and registry.
  • Add Linux-specific scenarios and walkthroughs, especially for automation, monitoring, and configuration.
  • Review terminology to avoid Windows-centric language and ensure parity in describing supported features for both OS types.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/security-extensions.md ...main/articles/azure-arc/servers/security-extensions.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 generally presents Windows examples and terminology before Linux equivalents, especially in command examples and best practices. PowerShell is used for Windows instructions, while Linux examples use Bash, but Windows commands are often listed first. Windows-specific tools and scenarios (e.g., Active Directory domain controllers, Windows Server 2012 ESU) are mentioned, sometimes without equivalent Linux context. However, Linux examples are present and reasonably complete.
Recommendations
  • Alternate the order of Windows and Linux examples to avoid consistently listing Windows first.
  • Provide Linux-specific context for scenarios that currently only mention Windows (e.g., mention Linux equivalents for domain controllers or ESU scenarios if applicable).
  • Ensure that any Windows-specific tool or pattern is matched with a Linux equivalent, or explicitly state when a feature is Windows-only.
  • Where PowerShell is used for Windows, consider providing Bash examples for Linux in parallel, and clarify any differences in command usage or required privileges.
  • Review terminology to ensure equal emphasis on both platforms throughout the documentation.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/ssh-arc-overview.md ...ob/main/articles/azure-arc/servers/ssh-arc-overview.md
High Priority View Details →
Scanned: 2026-01-09 00:34
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides both Windows and Linux instructions, but there is a noticeable Windows bias. Windows-specific tools (PowerShell, OpenSSH for Windows) are mentioned frequently and sometimes before Linux equivalents. PowerShell examples are given for most operations, and there are explicit references to Windows features and installation steps. Linux instructions are present but less detailed, and some examples (such as checking SSH status) are more thorough for Windows. The 'Next steps' section highlights Windows OpenSSH documentation but omits similar Linux resources.
Recommendations
  • Ensure Linux instructions are as detailed as Windows instructions, including troubleshooting and configuration steps.
  • Provide Linux-first examples or alternate between Windows and Linux to avoid prioritizing one platform.
  • Include links to Linux OpenSSH documentation and troubleshooting guides in the 'Next steps' section.
  • Balance the use of PowerShell and Bash examples throughout the documentation.
  • Add explicit guidance for common Linux distributions (e.g., Ubuntu, CentOS) where package names or commands may differ.
  • Where Windows-specific notes are given (e.g., OpenSSH installed by default), provide equivalent Linux notes (e.g., which distros have OpenSSH pre-installed).
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/private-link-security.md ...in/articles/azure-arc/servers/private-link-security.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 mild Windows bias. Windows terminology and tooling (e.g., Windows Admin Center, Windows agent, C:\Windows\System32\drivers\etc\hosts) are mentioned first or exclusively in several places. Powershell and Windows-centric instructions are given before Linux equivalents, and some examples (such as editing the Hosts file) provide more detail for Windows than Linux. References to Windows tools (Windows Admin Center) are present, while Linux alternatives (such as SSH) are mentioned only briefly and with less guidance. There is a lack of parity in example commands and troubleshooting steps for Linux users.
Recommendations
  • Ensure Linux instructions are given equal prominence and detail as Windows instructions, especially in configuration and troubleshooting sections.
  • Provide example commands for Linux environments (e.g., using dig or host for DNS troubleshooting, systemctl for agent management).
  • Mention Linux tools and workflows (such as Cockpit for remote management) alongside Windows Admin Center, or clarify parity and limitations.
  • When listing agent download links, provide direct Linux package manager commands (e.g., apt, yum, zypper) for installing the agent.
  • In sections where Windows is mentioned first (e.g., Hosts file editing), alternate the order or provide parallel step-by-step instructions for both OSes.
  • Expand troubleshooting guidance to include Linux-specific scenarios, such as SELinux, iptables, or systemd service status.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/resource-graph-samples.md ...n/articles/azure-arc/servers/resource-graph-samples.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 references Azure PowerShell and Azure CLI as methods to run queries, but lists Azure PowerShell first, which may suggest a Windows-first approach. There are no explicit examples or instructions for running queries on Linux systems, nor is there mention of Linux-specific tools or shell environments. The absence of Linux command-line examples or references to Bash or other Linux shells indicates a bias towards Windows usage patterns.
Recommendations
  • List Azure CLI before Azure PowerShell, as CLI is cross-platform and more commonly used on Linux.
  • Provide explicit examples of running queries using Azure CLI in Bash or other Linux shells.
  • Mention that both Azure CLI and PowerShell are available on Linux, and provide installation or usage notes for Linux users.
  • Include sample queries or instructions tailored for Linux environments, such as using Bash scripts or integrating with Linux automation tools.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/troubleshoot-vm-extensions.md ...ticles/azure-arc/servers/troubleshoot-vm-extensions.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 🔧 Windows Tools
Summary
The documentation shows a moderate Windows bias: PowerShell is the only CLI example given for extension removal, and Windows paths and tools are consistently listed before Linux equivalents. Windows-specific tools and patterns (PowerShell, C: drive paths) are mentioned more prominently, while Linux commands and tooling are not demonstrated or are listed second.
Recommendations
  • Provide equivalent CLI examples for Linux, such as Azure CLI or shell commands, alongside PowerShell examples.
  • Alternate the order of Windows and Linux instructions to avoid always listing Windows first.
  • Include Linux-specific troubleshooting steps and commands where relevant (e.g., systemctl for service management, journalctl for logs).
  • Explicitly mention that both Windows and Linux are supported and ensure parity in examples and guidance.
  • Where file paths or logs are referenced, present both Windows and Linux locations together, or in parallel columns.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/system-center-virtual-machine-manager/switch-to-the-new-version-scvmm.md ...ual-machine-manager/switch-to-the-new-version-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 Missing Linux Example 🔧 Windows Tools
Summary
The documentation page focuses exclusively on System Center Virtual Machine Manager (SCVMM), a Windows-centric virtualization management tool. All instructions, references, and linked guides pertain to Windows environments, with no mention of Linux equivalents, Linux-based management tools, or cross-platform considerations. Examples and agent management instructions are specific to Windows, and the documentation assumes the user is operating in a Windows ecosystem.
Recommendations
  • Include information about Linux-based virtualization management options, if supported by Azure Arc.
  • Provide equivalent instructions or guidance for managing Linux VMs, including agent installation/uninstallation and onboarding steps.
  • Add notes or links clarifying platform support and limitations, especially for users managing non-Windows environments.
  • Where possible, offer cross-platform examples or highlight differences in process for Linux versus Windows VMs.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/vmware-vsphere/enable-guest-management-at-scale.md ...arc/vmware-vsphere/enable-guest-management-at-scale.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 providing PowerShell-based automation scripts and examples, referencing Windows-specific tools such as Task Scheduler, and omitting equivalent Linux automation examples (e.g., Bash scripts, cron usage). Windows terminology and patterns (local administrator group, Task Scheduler) are mentioned before or instead of Linux equivalents, and Linux-specific instructions are minimal and relegated to notes.
Recommendations
  • Provide Linux/Bash script examples for Arc agent installation and automation, including how to run the helper script from a Linux shell.
  • Include instructions for scheduling automated agent installation on Linux using cron, with sample crontab entries.
  • Mention Linux equivalents for administrative privileges (e.g., sudo/root) alongside Windows local administrator group references.
  • Ensure parity in troubleshooting and prerequisites for both Windows and Linux VMs.
  • Where PowerShell is referenced, also provide Bash or shell script alternatives for Linux users.
  • Clarify which steps or scripts are cross-platform and which are Windows-specific, and offer alternatives where needed.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/system-center-virtual-machine-manager/support-matrix-for-system-center-virtual-machine-manager.md ...pport-matrix-for-system-center-virtual-machine-manager.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 🔧 Windows Tools Powershell Heavy
Summary
The documentation page exhibits a clear Windows bias. It consistently references Windows Server, SCVMM (a Windows-only product), and Windows-specific tools and patterns (e.g., WinRM, Windows Management Framework, PowerShell/OpenSSH for Windows). Windows operating systems are listed first and in detail, while Linux support is mentioned only as an alternative with less detail and no concrete examples. The workstation section notes Linux is supported but with performance caveats, and there are no Linux-specific configuration or troubleshooting examples. Windows tools and ports (WinRM, Windows Admin Center) are referenced exclusively or before Linux equivalents.
Recommendations
  • Provide Linux-specific deployment and configuration examples, especially for agent installation and network setup.
  • Include troubleshooting steps and performance optimization tips for Linux workstations.
  • List supported Linux operating systems with the same level of detail as Windows, including version numbers and requirements.
  • Mention Linux tools (e.g., SSH, systemctl) where relevant, and provide parity in instructions for both platforms.
  • Avoid language that discourages Linux usage (e.g., 'deployment takes a bit longer and you might experience performance issues') without offering solutions or context.
  • Where Windows tools (e.g., WinRM, Windows Management Framework) are referenced, provide Linux equivalents or alternatives.
GitHub Create Pull Request
← Previous Page 14 of 94 Next →