← Back to Dashboard
756
Pages Scanned
232
Pages Flagged
756
Changed Pages
30.7%
% Pages Flagged

Scan Information

Started At: 2026-01-08 00:53:04

Finished At: 2026-01-08 22:14:25

Status: completed

Target Repo: Azure Management

Current Phase: discovery

Files Queued: 756

Files Completed: 756

Problematic Pages

232 issues found
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 →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_paths ⚠️ windows_notes
Summary
The documentation provides both Windows and Linux examples for file operations (copying certificates/keys), but Windows instructions and notes are often presented first or given special attention. Windows-specific path syntax and troubleshooting notes are included, while Linux equivalents are present but sometimes secondary. There is no exclusive use of Windows tools, but the ordering and emphasis may suggest a slight Windows bias.
Recommendations
  • Present Linux and Windows instructions in parallel, or alternate which OS is listed first to avoid implicit prioritization.
  • Include troubleshooting notes for both Windows and Linux, not just Windows.
  • Clarify that both Windows and Linux are fully supported and provide parity in examples and troubleshooting.
  • Where possible, use OS-agnostic paths or explain path differences for both platforms.
  • Consider adding macOS instructions if relevant, or clarify platform support.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/connect-active-directory-sql-managed-instance.md .../data/connect-active-directory-sql-managed-instance.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-based tools (SSMS, ADS) are mentioned and visually highlighted, while Linux/Mac examples are limited to command-line usage. The Windows connection example is presented after the Linux example, but graphical tools are only shown for Windows, with no Linux GUI alternatives or parity. There is also an assumption of Windows environments for AD integration and DNS setup, and no mention of Linux-specific troubleshooting or alternative tools.
Recommendations
  • Include screenshots or instructions for connecting from Azure Data Studio on Linux and Mac OS.
  • Mention and provide examples for Linux-native SQL clients that support Kerberos/AD authentication (e.g., DBeaver, SquirrelSQL).
  • Add troubleshooting notes for common Linux Kerberos/AD integration issues.
  • Clarify that SSMS is Windows-only and suggest cross-platform alternatives.
  • Provide parity in graphical connection instructions for Linux/Mac users, not just Windows users.
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 →
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 by frequently referencing Windows-specific installation instructions and tools before Linux equivalents, providing PowerShell-specific notes, and lacking parity in Linux example details. For instance, kubectl installation links list Windows first, curl installation is more detailed for Windows, and there are notes about using cmd.exe and PowerShell on Windows, but no comparable Linux shell guidance. Linux instructions are often less explicit or relegated to brief mentions.
Recommendations
  • Present installation instructions for all platforms (Windows, Linux, macOS) in parallel, or list Linux first to balance historical bias.
  • Provide explicit Linux shell examples and troubleshooting notes, similar to those given for Windows (e.g., bash/zsh guidance for curl and kubectl).
  • Include Linux package manager commands (e.g., apt, yum, dnf) for installing tools like curl and kubectl.
  • Add notes about common Linux issues or environment specifics, just as PowerShell/cmd.exe notes are given for Windows.
  • Ensure extension installation instructions for Azure Data Studio mention Linux/macOS compatibility and steps if they differ.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/edge-rag/configure-endpoint-authentication.md ...zure-arc/edge-rag/configure-endpoint-authentication.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example ⚠️ windows_first
Summary
The documentation page demonstrates a Windows bias by providing only PowerShell-based examples and commands, including the use of '.\kubectl.exe', which is specific to Windows. There are no Bash or Linux shell equivalents, and Windows tools and patterns are mentioned exclusively. This may hinder Linux users from following the instructions seamlessly.
Recommendations
  • Provide equivalent Bash/Linux shell command examples alongside PowerShell commands.
  • Use platform-neutral syntax for kubectl (e.g., 'kubectl' instead of '.\kubectl.exe') where possible.
  • Explicitly mention any platform-specific differences or requirements.
  • Add notes or sections for Linux/macOS users to ensure parity and inclusivity.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/edge-rag/prepare-aks-cluster.md ...ain/articles/azure-arc/edge-rag/prepare-aks-cluster.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page exhibits a strong Windows bias. All command-line examples are provided in PowerShell syntax, and instructions reference Windows-specific tools and patterns (e.g., Restart-Service, Start-Sleep, PowerShell variable assignment). There are no Linux shell (bash) equivalents, nor guidance for Linux environments. The section on configuring a driver machine explicitly links to instructions for Windows, with no mention of Linux or macOS alternatives.
Recommendations
  • Provide equivalent bash shell examples for all PowerShell commands, especially for cluster status checks and node pool creation.
  • Include instructions for setting up a Linux (and optionally macOS) driver machine, with links to relevant setup scripts or documentation.
  • When referencing tools or commands (e.g., Restart-Service), mention Linux alternatives (e.g., systemctl) where applicable.
  • Present cross-platform instructions side-by-side or clearly indicate which steps apply to Windows vs. Linux environments.
  • Review linked scripts and documentation to ensure Linux parity and update references to avoid Windows-first language.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/edge-rag/uninstall-extension.md ...ain/articles/azure-arc/edge-rag/uninstall-extension.md
High Priority View Details →
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 Azure PowerShell examples, using Windows-centric scripting syntax, and omitting equivalent Linux/bash examples. The instructions and code blocks are written in PowerShell, and there is no mention of Linux shell commands or cross-platform alternatives. Even the kubectl command is presented in a PowerShell code block, which may confuse Linux users. The Azure portal instructions are platform-neutral, but all CLI guidance is Windows-focused.
Recommendations
  • Provide bash/Linux shell equivalents for all PowerShell commands, especially for az CLI and kubectl usage.
  • Use generic code blocks for cross-platform commands like kubectl, or show both PowerShell and bash syntax side-by-side.
  • Explicitly mention that az CLI and kubectl are cross-platform, and clarify any OS-specific steps.
  • Add a tabbed section for Linux/macOS users, mirroring the PowerShell tab, with bash commands and environment setup instructions.
  • Avoid using PowerShell variable syntax ($var) in examples unless also showing bash alternatives.
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 →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation mentions Azure PowerShell as the first option for running queries, which can imply a Windows-centric approach. There is no explicit mention of Linux shell examples (such as Bash), nor are there instructions or examples tailored for Linux users. The documentation does not reference Linux-specific tools or patterns, and the ordering of tools may reinforce a Windows-first perception.
Recommendations
  • Include explicit examples for running queries using Azure CLI in Bash or other Linux shells.
  • Reorder the list of query execution options to avoid listing Windows tools (PowerShell) first; consider listing Azure CLI or portal options before PowerShell.
  • Add notes or sections highlighting cross-platform compatibility and usage, especially for Linux and macOS users.
  • Reference Linux-specific documentation or provide links to resources for Linux users where relevant.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/arc-gateway.md ...cs/blob/main/articles/azure-arc/servers/arc-gateway.md
High Priority View Details →
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 tools and patterns (PowerShell, Windows Admin Center, Windows Update, Defender) are frequently referenced, often before or in greater detail than their Linux equivalents. Command examples are consistently provided for PowerShell, Azure CLI, and Portal, but PowerShell is always present, and CLI examples sometimes use Windows-style syntax (backticks). Linux-specific instructions are minimal or absent except for log file locations. Some features and scenarios (e.g., Windows OS Update Extension, Defender prerequisites) are Windows-centric, and Windows Admin Center is listed as a supported scenario without Linux alternatives. The onboarding and management instructions do not provide explicit Linux shell examples or highlight Linux-specific considerations.
Recommendations
  • Provide explicit Linux shell (bash/sh) examples alongside PowerShell and CLI, using Linux syntax and conventions.
  • Clarify when instructions or features are Windows-only, and offer Linux alternatives or note limitations.
  • Include Linux equivalents for Windows-centric tools and scenarios (e.g., mention Cockpit or other Linux management tools if relevant).
  • Ensure that CLI examples use syntax compatible with both Windows and Linux shells, or provide separate examples for each.
  • Expand documentation of Linux-specific requirements, troubleshooting, and log locations.
  • List Linux scenarios and extensions in parity with Windows scenarios (e.g., mention Linux OS update management tools/extensions).
  • Review endpoint requirements and examples to ensure Linux onboarding is equally detailed.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/cloud-native/next-steps.md .../articles/azure-arc/servers/cloud-native/next-steps.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows-centric onboarding methods (Windows Admin Center, Configuration Manager, GPOs, WSUS) and omitting explicit Linux equivalents or examples. Windows management tools and patterns are mentioned exclusively or first, while Linux onboarding and configuration approaches are not discussed.
Recommendations
  • Include onboarding instructions and examples for Linux servers, such as using shell scripts, Ansible, or cloud-init.
  • Mention Linux-native management tools (e.g., cron for automation, Linux package managers for updates) alongside Windows tools.
  • Provide parity in example scripts and workflows, showing both PowerShell and Bash/CLI equivalents.
  • Reference Linux security practices (e.g., sudoers, SELinux, auditd) when discussing RBAC and auditing.
  • Add links to Linux-specific Azure Arc documentation and training resources.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/resource-bridge/includes/network-requirements.md ...e-arc/resource-bridge/includes/network-requirements.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific services and tools (e.g., time.windows.com, sts.windows.net, login.windows.net) and mentioning Windows NTP as a default for Hyper-V without equivalent Linux details. Windows endpoints and terminology appear before or more prominently than Linux alternatives, and there are no explicit Linux configuration examples or references to Linux NTP servers or Linux management machine patterns.
Recommendations
  • Add explicit references to Linux equivalents for services such as NTP (e.g., pool.ntp.org) and authentication endpoints.
  • Provide examples or notes for configuring outbound/inbound connectivity on Linux management machines, including common Linux firewall and proxy tools (e.g., iptables, firewalld, ufw).
  • Clarify whether the management machine can be Linux and, if so, provide guidance for Linux-specific setup and troubleshooting.
  • Balance the mention of Windows and Linux endpoints, tools, and patterns throughout the documentation.
  • Include Linux-specific notes for time synchronization, package management, and network configuration.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/azcmagent-check.md ...lob/main/articles/azure-arc/servers/azcmagent-check.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page demonstrates Windows bias by referencing Windows-specific use cases (Windows Server Pay-as-you-go) in the flag descriptions, mentioning Windows before Linux, and omitting Linux-specific examples or scenarios. There are no examples or notes for Linux environments, such as common Linux server use cases or shell-specific instructions.
Recommendations
  • Add Linux-specific examples, such as checking connectivity on a Linux server or using the command in a bash shell.
  • Include references to Linux use cases (e.g., connectivity checks for Linux workloads managed by Azure Arc).
  • Balance mentions of Windows and Linux in flag descriptions, such as including links to Linux documentation or use cases alongside Windows Server references.
  • If there are platform-specific behaviors or requirements, explicitly document them for both Windows and Linux.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/cloud-native/scripting-task-automation.md ...-arc/servers/cloud-native/scripting-task-automation.md
High Priority View Details →
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 Windows bias by frequently referencing Windows-specific tools and workflows (such as RDP, PowerShell, SCCM, and Windows Task Scheduler) before or in preference to Linux equivalents. PowerShell is highlighted as the primary scripting language, and Windows-centric automation patterns are described in detail, while Linux examples and tools are only briefly mentioned or omitted. There are no concrete Linux command/script examples, and Linux-specific automation patterns are not explored.
Recommendations
  • Provide parallel Linux examples for each automation scenario, including sample Bash scripts and Linux command-line usage.
  • Mention Linux-native tools (e.g., cron, systemd timers, Ansible) alongside Windows tools like Task Scheduler and SCCM, and explain how Azure Arc integrates with them.
  • Balance the order of presentation so that Linux and Windows approaches are introduced together, rather than leading with Windows.
  • Include explicit examples of using Azure Run Command and SSH with Linux servers, including sample commands and scripts.
  • Highlight Linux authentication and management features (such as Microsoft Entra authentication for SSH) with equal prominence as Windows features.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/manage-automatic-vm-extension-upgrade.md ...e-arc/servers/manage-automatic-vm-extension-upgrade.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation generally presents Windows and Linux as supported platforms, but there is a subtle Windows bias. Windows-specific tools (PowerShell) are given equal prominence to cross-platform tools (Azure CLI), and Windows-only extensions are listed before Linux equivalents. PowerShell examples are included, and Windows-only extensions are called out explicitly, while Linux-only or Linux-first scenarios are not. The documentation mentions Azure CLI as cross-platform, but does not provide Linux-specific shell examples (e.g., bash scripting), nor does it highlight Linux-specific extension management patterns. The order of presentation (portal, CLI, PowerShell) also places Windows-centric tools before Linux-centric workflows.
Recommendations
  • Add explicit Linux shell (bash/zsh) examples for Azure CLI commands, including sample scripts for automation.
  • Include Linux-specific extension examples or call out Linux-only extensions if any exist.
  • When listing supported extensions, alternate or group by OS rather than listing Windows-only extensions first.
  • Clarify that Azure PowerShell is available on Linux, or provide equivalent bash/CLI automation examples for Linux users.
  • Consider presenting CLI examples before PowerShell to emphasize cross-platform parity.
  • Add troubleshooting and management scenarios specific to Linux environments (e.g., SELinux, systemd integration, log locations).
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 →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation mentions both Windows and Linux machines, but the workflow and examples are presented in a Windows-centric manner. The runbook naming convention (Add-UMMachinesToArc, Add-UMMachinesToArcWindowsChild) and references to Azure PowerShell for job status retrieval suggest a preference for Windows tools and patterns. There are no explicit Linux command-line examples or references to Linux-native tooling, and PowerShell is mentioned before any Linux alternatives.
Recommendations
  • Provide explicit Linux command-line examples (e.g., Bash, shell scripts) for key steps such as agent installation and verification.
  • Mention Linux-native tools (such as CLI commands, systemd services, log locations) alongside or before Windows/PowerShell equivalents.
  • Clarify that both Windows and Linux runbooks are equally supported, and provide sample output or troubleshooting steps for Linux systems.
  • Include screenshots or walkthroughs from a Linux perspective in addition to Windows.
  • Reference Azure CLI usage for job status retrieval, not just Azure PowerShell.
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 →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page references both Windows and Linux support, but the examples and guidance are heavily oriented toward Windows and PowerShell. The 'Next steps' section lists PowerShell before REST API, and there is no explicit mention of Linux shell scripting or Linux-specific usage patterns. There are no Linux command-line examples, and the documentation does not reference Linux tools or shell environments (e.g., Bash) in its examples or guidance.
Recommendations
  • Add explicit Linux shell (e.g., Bash) examples alongside PowerShell examples.
  • Include Linux-specific administrative scenarios (e.g., using apt/yum for updates, configuring iptables, checking systemd services) in the overview and examples.
  • Mention Linux shell scripting as a supported use case in the 'How it works' section.
  • Ensure parity in the 'Next steps' section by providing links to Linux/Bash usage documentation or examples.
  • Clarify that both Windows and Linux scripts can be executed, and provide guidance on script file formats and interpreter selection.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/modernize-server-management.md ...icles/azure-arc/servers/modernize-server-management.md
High Priority View Details →
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 licensing, Windows Server Software Assurance, and Windows-centric onboarding (Scheduled Task, Configuration Manager) before Linux alternatives. While Linux support is mentioned as a benefit, concrete Linux-specific examples, onboarding steps, or tools are missing. Windows tools (SCCM, SCVMM, SCOM) are discussed in detail, whereas Linux equivalents or migration guidance for Linux-centric environments are not provided.
Recommendations
  • Add explicit onboarding instructions for Linux servers, including example commands for agent installation (e.g., shell scripts, systemd units) and mention of Linux-native scheduling tools (cron, systemd timers) instead of only Scheduled Task.
  • Provide Linux-specific examples for functionality such as patching, configuration, and reporting (e.g., how Azure Update Manager works with Ubuntu or RHEL, sample policies for Linux, daemon monitoring).
  • Include references to Linux management tools and migration paths from Linux-centric environments (e.g., Ansible, Chef, Puppet) and how Azure Arc integrates or replaces these.
  • Balance the order of presentation so that Linux and Windows are treated equally in examples, guidance, and tool references.
  • Clarify any limitations or differences in feature parity for Linux servers and provide guidance for addressing gaps.
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 →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ windows_tools
Summary
The documentation page demonstrates a Windows bias by providing only Azure PowerShell examples for extension removal, listing Windows log and folder locations before Linux equivalents, and referencing Windows-specific tools and patterns (e.g., PowerShell cmdlets) without offering Linux CLI or shell alternatives. Linux instructions are present but consistently secondary and lack parity in example commands.
Recommendations
  • Provide equivalent Azure CLI (az) command examples for extension management, especially for Linux users.
  • Alternate the order of Windows and Linux instructions or present them side-by-side to avoid 'Windows first' bias.
  • Include Linux shell command examples (e.g., rm for folder deletion) alongside Windows Explorer instructions.
  • Reference Linux troubleshooting tools (e.g., journalctl, systemctl) where relevant.
  • Ensure all steps and examples are equally detailed for both Windows and Linux environments.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/system-center-virtual-machine-manager/enable-guest-management-at-scale.md ...al-machine-manager/enable-guest-management-at-scale.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ powershell_heavy
Summary
The documentation page demonstrates a Windows bias by prioritizing Windows VM scenarios, listing Windows operating systems and SCVMM versions first, and providing more detailed steps for Windows environments. Windows-specific tools (PowerShell, Group Policy, Configuration Manager) are mentioned before their Linux equivalents, and the Azure portal method is only available for Windows VMs. Linux instructions are present but less emphasized and sometimes relegated to notes or secondary methods.
Recommendations
  • Present Linux and Windows instructions with equal prominence and detail, including side-by-side examples where possible.
  • List supported Linux distributions explicitly in the prerequisites and installation sections, not just as a secondary note.
  • Include Linux-first examples and automation methods (e.g., Ansible, shell scripts) before or alongside Windows tools like PowerShell and Group Policy.
  • Expand Linux troubleshooting and credential guidance beyond the sudo note, matching the depth given to Windows.
  • Clarify which features are available for Linux VMs and provide parity where possible, or clearly state limitations.
  • Ensure that all programmatic and out-of-band methods include Linux-specific instructions, not just links to Windows-centric tools.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/quick-onboard-linux.md ...main/articles/azure-arc/servers/quick-onboard-linux.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_reference ⚠️ windows_terms ⚠️ windows_tools
Summary
The documentation is focused on Linux onboarding for Azure Arc and provides Linux-specific instructions and examples. However, there are minor instances of Windows bias: references to 'Windows computer name' in prerequisites, use of terms like 'Windows computer name' alongside 'Linux hostname', and mention of the Azure portal (which is platform-agnostic but often associated with Windows environments). There are no PowerShell examples, Windows-first ordering, or exclusive use of Windows tools, but some terminology and references could be more Linux-centric.
Recommendations
  • Replace or supplement 'Windows computer name' references with Linux-specific terminology or clarify that the reserved word/trademark restriction applies to both platforms.
  • Where possible, avoid unnecessary references to Windows in Linux-focused documentation unless directly relevant.
  • Ensure that all examples, screenshots, and tool references are Linux-specific and do not imply Windows as the default or primary platform.
  • Consider adding explicit notes or links for Linux users regarding any Azure portal steps that may differ from Windows environments.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/system-center-virtual-machine-manager/disaster-recovery.md ...em-center-virtual-machine-manager/disaster-recovery.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation exclusively provides recovery instructions and scripts for Windows environments, specifically using PowerShell. There are no examples, scripts, or guidance for performing the same recovery operation from a Linux machine. The recovery script is Windows-specific, and the use of PowerShell is highlighted without mention of Linux shell equivalents or cross-platform alternatives.
Recommendations
  • Provide equivalent recovery instructions and scripts for Linux environments, using Bash or cross-platform tools.
  • Explicitly mention whether the recovery process can be performed from Linux, and if not, clarify the limitation.
  • Offer downloadable scripts for Linux (e.g., Bash, Python) or document how to adapt the process for Linux users.
  • Ensure that examples and tooling are presented for both Windows and Linux, or at least note the absence of Linux support.
  • Consider using cross-platform scripting languages (such as Python) for automation tasks where possible.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/system-center-virtual-machine-manager/enable-virtual-hardware-scvmm.md ...rtual-machine-manager/enable-virtual-hardware-scvmm.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation is heavily focused on SCVMM (System Center Virtual Machine Manager), a Windows-centric virtualization management tool. All instructions, terminology, and screenshots are tailored to Windows environments, with no mention of Linux-based management tools, Linux VMs, or cross-platform alternatives. There are no examples or guidance for Linux users or administrators managing non-Windows VMs.
Recommendations
  • Include guidance for managing Linux-based VMs within SCVMM, if supported, or clarify limitations.
  • Provide examples or references for equivalent operations using Linux management tools (e.g., libvirt, KVM, or Azure Arc-enabled Linux VMs).
  • Add notes or sections addressing cross-platform scenarios, such as onboarding and managing Linux VMs with Azure Arc.
  • Ensure parity in screenshots and instructions for both Windows and Linux environments, where applicable.
  • Explicitly state the scope and limitations regarding non-Windows platforms to inform users.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/workload-orchestration/clean-up-script.md ...es/azure-arc/workload-orchestration/clean-up-script.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example ⚠️ windows_first
Summary
The documentation exclusively provides a PowerShell script for resource clean-up, with all usage examples and instructions tailored to PowerShell. There is no mention of Bash, shell scripts, or Linux-specific instructions, nor are alternative cross-platform approaches (such as Azure CLI or Python scripts) discussed. This creates a Windows-centric bias, making it less accessible for Linux or macOS users.
Recommendations
  • Provide equivalent Bash or shell script examples for Linux/macOS users.
  • Include instructions for running the clean-up using Azure CLI commands, which are cross-platform.
  • Mention how to execute PowerShell scripts on Linux/macOS (e.g., via PowerShell Core), if relevant.
  • Add a section comparing Windows and Linux approaches, listing prerequisites and environment setup for both.
  • Ensure ZIP folder contains both PowerShell and Bash scripts, or a cross-platform script (e.g., Python).
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 →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation exhibits a Windows bias by prioritizing PowerShell-based automation, referencing Windows-specific tools (e.g., Task Scheduler), and providing examples and instructions primarily for Windows environments. Linux equivalents for scripting, scheduling, and automation are either missing or mentioned only briefly, with no concrete examples or step-by-step guidance. The documentation assumes the use of Windows tools and patterns, making it less accessible for Linux administrators.
Recommendations
  • Provide equivalent Linux shell script examples for Arc agent installation and automation, including usage with bash and cron.
  • Include instructions for scheduling automation on Linux (e.g., using cron jobs), with sample crontab entries.
  • Offer guidance for running the helper script in Linux environments, including prerequisites, execution commands, and troubleshooting.
  • Ensure parity in examples and step-by-step instructions for both Windows and Linux, especially in sections currently focused on PowerShell and Windows Task Scheduler.
  • Explicitly mention cross-platform compatibility for scripts and tools, and clarify any OS-specific limitations or requirements.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/vmware-vsphere/azure-arc-agent.md ...n/articles/azure-arc/vmware-vsphere/azure-arc-agent.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ windows_heavy_detail
Summary
The documentation presents Windows agent installation details before Linux, provides more granular information about Windows-specific artifacts (services, security groups, environment variables, log locations, and post-uninstall remnants), and references Windows-specific tools and concepts (MSI installer, Group Policy, NT SERVICE accounts). Linux installation details are present but less detailed, lacking parity in areas such as security group creation and post-uninstall artifact explanation. Windows terminology and paths are often listed first or exclusively, and troubleshooting/logging guidance is more extensive for Windows.
Recommendations
  • Present Windows and Linux installation details in parallel sections, or alternate which OS is described first to avoid implicit prioritization.
  • Ensure Linux installation details include equivalent information to Windows, such as service accounts, security groups, environment variable configuration, and post-uninstall artifacts.
  • Provide Linux-specific troubleshooting and logging guidance at the same level of detail as Windows.
  • Avoid Windows-centric terminology (e.g., Group Policy, NT SERVICE) without Linux equivalents or explanations.
  • List both Windows and Linux paths and examples together, rather than Windows first.
  • Add explicit notes or tables comparing Windows and Linux behaviors, especially where they differ.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/workload-orchestration/how-to-stage.md ...icles/azure-arc/workload-orchestration/how-to-stage.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation provides both Bash and PowerShell examples for all major steps, ensuring cross-platform coverage. However, there are signs of Windows bias: PowerShell examples are given equal prominence to Bash, even for tasks that are not Windows-specific (e.g., Docker, kubectl, az CLI, which are cross-platform). Some PowerShell examples use Windows-specific patterns (e.g., Out-File, [Convert]::ToBase64String), and the instructions for editing files mention UTF-8 BOM encoding, which is primarily a Windows concern. There are no Linux-specific troubleshooting notes, and some PowerShell commands (e.g., armclient) are Windows-centric without Linux equivalents. The documentation does not provide explicit Linux-only examples or address Linux-specific edge cases.
Recommendations
  • Add explicit notes or troubleshooting sections for Linux users, such as handling file permissions, line endings, or common issues with az CLI, Docker, or kubectl on Linux.
  • Where PowerShell is used for file manipulation or encoding, provide equivalent Bash/Linux commands (e.g., for base64 encoding, file writing, or JSON formatting).
  • Clarify that PowerShell examples are intended for Windows users, and Bash for Linux/macOS, to avoid confusion.
  • If referencing tools like armclient, mention Linux alternatives or note cross-platform compatibility.
  • Include Linux-specific tips for editing files (e.g., using vim, nano, or sed for encoding changes) and troubleshooting UTF-8/BOM issues.
  • Consider providing a 'Linux Quick Start' or 'Linux-specific considerations' section for users deploying on Linux edge clusters.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/vmware-vsphere/whats-new.md ...ob/main/articles/azure-arc/vmware-vsphere/whats-new.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation page demonstrates a mild Windows bias: Windows-specific features (e.g., customizing Windows VM guest OS settings, Windows Server Management, Extended Security Updates for Windows Server) are highlighted, and Windows tools (PowerShell, System Center Configuration Manager, Group Policy) are mentioned explicitly. Linux is referenced only once (Arc agent installation via SSH), and there are no Linux-specific management tools or examples provided. Windows tools are listed before Linux equivalents, and some features appear exclusive to Windows environments.
Recommendations
  • Include equivalent Linux management examples and tools (e.g., shell scripts, Linux configuration management tools like Chef/Puppet/SaltStack).
  • Provide parity in feature descriptions, such as guest OS customization for Linux VMs.
  • List Linux and cross-platform tools alongside Windows tools, not after or instead of them.
  • Add explicit Linux-focused sections or callouts where Windows-specific features are described.
  • Ensure that SDK and CLI examples include both Windows and Linux usage scenarios.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/workload-orchestration/onboarding-scripts.md ...azure-arc/workload-orchestration/onboarding-scripts.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation is heavily biased towards Windows environments. All script examples use PowerShell (.ps1 files) and instruct users to open a PowerShell terminal. Prerequisites rely on Windows-specific tools like winget, and there are no Bash or Linux shell equivalents provided. No mention is made of how to run these scripts or set up the environment on Linux or macOS, nor are cross-platform alternatives discussed.
Recommendations
  • Provide Bash shell script equivalents (.sh) for infra and cm onboarding, or document how to run the PowerShell scripts on Linux/macOS using pwsh (PowerShell Core).
  • Include Linux/macOS installation instructions for Azure CLI and kubectl (e.g., using apt, yum, brew, or direct downloads), not just winget.
  • Add explicit notes about cross-platform compatibility of the onboarding scripts, and clarify any Windows-only limitations.
  • Present Linux/macOS examples alongside Windows/PowerShell examples, or at least mention them in parallel.
  • Consider reordering sections or examples so that Windows and Linux instructions are presented together, rather than Windows-first.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/workload-orchestration/migration-script.md ...s/azure-arc/workload-orchestration/migration-script.md
High Priority View Details →
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 Linux shell (bash/sh) equivalents or instructions for running the migration on Linux or macOS systems. The documentation assumes the use of Windows tools and does not mention cross-platform alternatives.
Recommendations
  • Provide a bash or shell script alternative for Linux/macOS users, or document how to run the PowerShell script using PowerShell Core on non-Windows platforms.
  • Explicitly mention cross-platform compatibility of the migration script, including any prerequisites for running PowerShell scripts on Linux/macOS.
  • Include example commands for Linux/macOS environments, such as using pwsh (PowerShell Core) or bash.
  • Clarify whether the migration process is supported on Linux/macOS and provide troubleshooting steps for those platforms.
GitHub Create Pull Request
Container Registry https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/container-registry-skus.md ...articles/container-registry/container-registry-skus.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation page demonstrates a moderate Windows bias. Examples and tool references for managing Azure Container Registry SKUs are presented first with Azure CLI (cross-platform), but PowerShell (Windows-centric) is always mentioned as the second option, with no mention of Bash, shell scripting, or Linux-specific package managers. The REST API is referenced, but not exemplified. There are no explicit Linux command-line examples, nor are Linux desktop tools or patterns discussed. The documentation assumes familiarity with Azure PowerShell, which is most commonly used on Windows.
Recommendations
  • Add explicit Bash or shell examples for common operations, such as changing SKUs or showing usage.
  • Clarify that Azure CLI is cross-platform and provide Linux-specific installation or usage notes.
  • Include references to Linux-native container tools (e.g., Podman, containerd) in example sections, not just in passing.
  • Provide REST API usage examples with curl or httpie for Linux users.
  • Balance the order of tool presentation (e.g., alternate between CLI and PowerShell, or group by platform).
  • Mention that Azure PowerShell is available on Linux, but provide parity for Linux users who may prefer Bash or other shells.
GitHub Create Pull Request
Quotas https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/quotas/networking-quota-requests.md ...blob/main/articles/quotas/networking-quota-requests.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation page displays Windows bias by listing Azure PowerShell as a primary method for viewing network quota usage, alongside Azure CLI and REST API. PowerShell is a Windows-centric tool, and its mention before Linux-native alternatives (such as Bash scripting or direct CLI usage) suggests a Windows-first approach. There are no Linux-specific examples or references to Linux tools, and the documentation does not provide parity for Linux users in terms of command-line instructions or workflows.
Recommendations
  • Provide explicit Linux/Bash examples for viewing and managing quotas using Azure CLI.
  • Reorder the list of tools to mention cross-platform options (Azure CLI, REST API) before Windows-specific ones (PowerShell).
  • Clarify that Azure CLI is available on Linux, macOS, and Windows, and provide sample commands for each platform where relevant.
  • Add guidance or links for Linux users on installing and using Azure CLI.
  • Avoid assuming PowerShell is the default or primary tool for all users; offer platform-neutral instructions where possible.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/backup-controller-database.md .../articles/azure-arc/data/backup-controller-database.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation page demonstrates Windows bias by providing command-line examples using PowerShell syntax and conventions (e.g., using double quotes for parameters, explicit mention of PowerShell blocks), without offering equivalent Linux shell (bash) examples. The SQL Server connectivity and restore commands are shown only in PowerShell context, and there is no mention of Linux-specific tools or patterns, despite the fact that Kubernetes and SQL Server on Linux are common in Azure Arc deployments. This may make the instructions less accessible to Linux users.
Recommendations
  • Provide equivalent bash shell examples for all PowerShell commands, especially for connecting to the SQL Server pod and running sqlcmd.
  • Clarify that the commands work on both Windows and Linux, and note any platform-specific differences (e.g., quoting, path separators).
  • Avoid labeling command blocks as 'powershell' unless they are truly PowerShell-specific; use 'console' or 'bash' where appropriate.
  • Mention Linux tools (such as base64 decoding with 'base64 -d') alongside generic instructions.
  • Add a note or section explicitly addressing Linux users and their workflow.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/container-storage/includes/single-node-edge-essentials.md ...tainer-storage/includes/single-node-edge-essentials.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation, while focused on Linux preparation, repeatedly uses Windows-centric tools and patterns. For example, it instructs users to open configuration files in Notepad (a Windows application), and uses the Invoke-AksEdgeNodeCommand cmdlet, which is a PowerShell/Windows-specific command, to interact with Linux nodes. There is no mention of Linux-native alternatives (e.g., nano, vi, direct SSH, or bash commands), and Windows/PowerShell tools are presented as the default method for managing Linux systems.
Recommendations
  • Provide Linux-native command-line alternatives for all management steps, such as using SSH and bash commands directly instead of PowerShell cmdlets.
  • Replace references to Notepad with Linux text editors like nano, vi, or vim, or suggest cross-platform editors.
  • Clarify when Windows tools are required and offer equivalent Linux workflows, ensuring users on Linux-only environments can follow the documentation.
  • Reorder examples so that Linux-native approaches are presented first or in parallel with Windows/PowerShell methods.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/choose-service.md ...nt-docs/blob/main/articles/azure-arc/choose-service.md
High Priority View Details →
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 in several ways. Windows-specific tools and terminology (e.g., SCVMM, Windows Server, SQL Server, Azure VMware Solution) are mentioned frequently and often before Linux equivalents. PowerShell is referenced as a primary automation tool, with no explicit Linux shell or scripting examples. Extended Security Updates are discussed only for Windows Server and SQL Server. There is a lack of Linux-specific examples, recommendations, or tooling throughout the document, and most onboarding and integration instructions reference Windows-centric workflows.
Recommendations
  • Include Linux-specific onboarding and management examples, such as shell scripts or Ansible playbooks, alongside PowerShell.
  • Highlight Linux management scenarios and capabilities (e.g., patching, monitoring, security) with equal detail as Windows.
  • Mention Linux distributions and their support explicitly in tables and feature lists.
  • Provide links to Linux-focused documentation and onboarding guides.
  • Balance references to Windows tools (SCVMM, PowerShell) with Linux equivalents (e.g., libvirt, cloud-init, bash scripting).
  • Discuss security and update management for Linux systems, not just Windows Extended Security Updates.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/container-storage/includes/multi-node-edge-essentials.md ...ntainer-storage/includes/multi-node-edge-essentials.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation page demonstrates a bias towards Windows by exclusively providing PowerShell-based examples (Invoke-AksEdgeNodeCommand) for configuring Linux nodes. It uses Windows-centric tooling to execute Linux commands, without showing direct Linux shell commands or instructions for users working natively on Linux. There are no bash or shell script examples, and the workflow assumes a Windows management environment.
Recommendations
  • Provide direct Linux shell command examples alongside PowerShell examples, so users managing Linux nodes natively can follow the instructions.
  • Include instructions for running these commands locally on Linux (e.g., using bash or SSH), not just via Windows-based tools.
  • Clarify when Windows tools are required and offer Linux-native alternatives for each step.
  • Consider reordering examples so that Linux-native instructions appear first, or at least in parallel with Windows/PowerShell methods.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/automated-integration-testing.md ...ticles/azure-arc/data/automated-integration-testing.md
High Priority View Details →
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 issues (CRLF vs LF line endings) are discussed in detail, with screenshots and instructions for VSCode, but no equivalent Linux/Mac guidance is provided. Azure CLI examples are shown in PowerShell terminals, and screenshots are Windows-centric. There is no mention of Linux tools for line ending conversion, nor are Linux/Mac terminal screenshots or instructions included. The order of presentation often assumes a Windows environment first, with Linux compatibility as an afterthought.
Recommendations
  • Provide explicit instructions and examples for Linux and Mac users, including terminal screenshots and tooling (e.g., using 'dos2unix' for line ending conversion).
  • Include guidance for Linux/Mac users on editing files, such as using 'nano', 'vim', or 'sed' to ensure LF line endings.
  • Balance screenshots between Windows and Linux/Mac environments to ensure parity.
  • When discussing Azure CLI usage, show examples in both PowerShell (Windows) and Bash (Linux/Mac) terminals.
  • Avoid assuming Windows as the default environment; structure instructions to address both platforms equally or in parallel.
  • Mention cross-platform editors and tools (e.g., VSCode, nano, vim) and how to check/convert line endings in each.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/create-data-controller-direct-prerequisites.md ...rc/data/create-data-controller-direct-prerequisites.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for connecting a Kubernetes cluster to Azure Arc, but PowerShell (a Windows-centric tool) is given equal prominence as Azure CLI, and there are no Linux shell-specific examples (e.g., bash scripts). The installation instructions for Azure CLI and Helm are platform-neutral, but the presence of PowerShell commands and lack of Linux-specific alternatives or notes may suggest a Windows bias. The document does not mention Linux-specific tools or patterns, nor does it provide troubleshooting or environment setup guidance for Linux users.
Recommendations
  • Add explicit bash/Linux shell examples for all commands, especially for connecting clusters and verifying pods.
  • Clarify that Azure CLI and Helm are cross-platform and provide installation instructions for both Windows and Linux.
  • If PowerShell is included, also include equivalent bash scripts or Linux command-line alternatives.
  • Add troubleshooting notes or environment setup guidance for Linux users (e.g., common issues with az CLI on Linux, permissions, etc.).
  • Order examples with platform-neutral or Linux-first commands before Windows/PowerShell examples to avoid implicit prioritization.
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 →
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 Active Directory object creation and management are provided using Windows tools (Active Directory Users and Computers GUI, PowerShell). The only automation example is in PowerShell, and there is no mention of Linux-compatible methods (such as using Samba, ldapadd, or other CLI tools). The prerequisite steps assume a Windows-based domain controller and link to a Windows Server-specific guide. No Linux or cross-platform alternatives are discussed.
Recommendations
  • Add instructions for managing Active Directory objects using cross-platform tools (e.g., ldapadd, ldapmodify, Samba's net utility) that can be run from Linux.
  • Include examples for creating OUs and users using Linux CLI tools or scripts.
  • Reference guides for setting up Active Directory-compatible services on Linux (such as Samba AD DC) where appropriate.
  • Clarify whether a Windows Server domain controller is strictly required, or if Linux-based AD-compatible controllers are supported.
  • Provide parity in screenshots and step-by-step instructions for Linux environments where possible.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/create-complete-managed-instance-directly-connected.md ...ttps://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/create-complete-managed-instance-directly-connected.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation demonstrates a Windows bias by referencing Windows file paths in command outputs, omitting Linux-specific examples or notes, and implicitly assuming a Windows environment for users. All examples and outputs use Windows conventions (e.g., backslashes in file paths), and there is no mention of Linux or macOS equivalents, nor guidance for users on those platforms.
Recommendations
  • Provide example outputs and instructions for both Windows and Linux/macOS environments, especially for file paths (e.g., ~/.kube/config for Linux/macOS).
  • Explicitly mention that the Azure CLI, kubectl, and Azure Data Studio are cross-platform, and provide installation or usage notes for Linux/macOS users.
  • Where command outputs differ by OS (such as file paths), show both variants or clarify with a note.
  • Ensure that screenshots and UI references are not specific to Windows unless unavoidable, and add clarifying notes for Linux/macOS users as needed.
  • Add a section or callout for Linux/macOS users highlighting any differences or additional steps required.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/deploy-active-directory-sql-managed-instance-cli.md ...ta/deploy-active-directory-sql-managed-instance-cli.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page demonstrates Windows bias primarily through its exclusive focus on Active Directory (AD) integration, which is a Windows-centric technology. All examples and instructions assume AD as the identity provider, with no mention of Linux-native alternatives (such as LDAP or Kerberos realms not backed by AD). The documentation does not provide guidance for Linux-based identity management or integration patterns, nor does it offer parity for Linux environments that do not use AD. The terminology and prerequisites are oriented toward Windows tools and infrastructure, and there are no Linux-first or cross-platform authentication examples.
Recommendations
  • Include examples and guidance for integrating SQL Managed Instance with Linux-native identity providers (e.g., OpenLDAP, MIT Kerberos).
  • Add documentation sections that explain how to deploy and manage SQL Managed Instance in environments without Active Directory, highlighting Linux authentication options.
  • Clarify prerequisites to indicate whether AD is mandatory or if alternatives are supported, and provide links to relevant Linux documentation if available.
  • Balance terminology and instructions to reference both Windows and Linux tools where applicable, or explicitly state platform limitations.
  • If AD is the only supported option, clearly state this limitation and provide rationale, while suggesting workarounds or future roadmap for Linux parity.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/configure-transparent-data-encryption-manually.md ...data/configure-transparent-data-encryption-manually.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ windows_path_examples
Summary
The documentation shows mild Windows bias by presenting Windows-specific instructions and examples before Linux equivalents in each tabbed section. Windows command-line tools and path conventions (e.g., 'type', '$HOME\sqlcerts\...') are used, and Windows-specific issues (such as kubectl cp path problems) are highlighted in notes. Linux instructions are present and correct, but are consistently listed after Windows, and Windows pathing is used in examples more prominently.
Recommendations
  • Alternate the order of Windows and Linux tabs so Linux is sometimes presented first.
  • Provide a general note at the top clarifying cross-platform support and parity, rather than only warning about Windows-specific issues.
  • Use neutral path examples (e.g., $HOME/sqlcerts/servercert.crt) in generic instructions, and only show platform-specific paths in their respective tabs.
  • Where possible, use platform-agnostic commands or highlight when commands work identically on both platforms.
  • Explicitly mention PowerShell only if it is required, and provide Bash equivalents if scripting is discussed.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/deploy-active-directory-sql-managed-instance.md ...c/data/deploy-active-directory-sql-managed-instance.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation demonstrates a moderate Windows bias. Windows-centric tools and patterns are referenced first or exclusively in several key steps, such as using 'Active Directory Users and Computers' for account creation and 'setspn' for SPN registration, both of which are Windows-only utilities. The process for generating keytab files does mention Linux tools and scripts, but Windows tools (like 'ktpass' and a PowerShell script) are listed alongside or before Linux equivalents. There is no explicit Linux example for creating the Active Directory account or registering SPNs, and the documentation assumes access to a Windows domain controller for these steps.
Recommendations
  • Provide explicit Linux-based alternatives for all steps, especially for creating Active Directory accounts and registering SPNs (e.g., using 'adutil' or 'ldapadd' for account creation, and 'adutil spn' for SPN registration).
  • List Linux tools and scripts before or alongside Windows tools, rather than after.
  • Include example commands for Linux environments where possible, not just for keytab generation but also for other Active Directory interactions.
  • Clarify which steps require Windows-only tools and suggest cross-platform or open-source alternatives where feasible.
  • Add a section or note on how to perform prerequisite steps (such as account and SPN creation) from a Linux or non-Windows environment, referencing official Microsoft documentation for 'adutil' and other relevant tools.
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 →
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 prioritizing Windows-centric tools (SQL Server Management Studio, Azure Data Studio) and workflows, mentioning them before Linux alternatives. There is a lack of explicit Linux client examples and no mention of Linux-native SQL tools (e.g., DBeaver, SquirrelSQL, or command-line utilities beyond sqlcmd). The special instructions for Azure VM networking and NSG configuration are presented using Azure CLI, which is cross-platform, but the overall workflow assumes familiarity with Windows environments and tools. Linux connection patterns and troubleshooting are not covered.
Recommendations
  • Include explicit examples for connecting from Linux-based SQL clients (e.g., DBeaver, SquirrelSQL, isql).
  • Provide step-by-step instructions for Linux users, including installation and usage of sqlcmd on Linux.
  • Mention Linux-native alternatives to SQL Server Management Studio and Azure Data Studio.
  • Add troubleshooting tips for Linux networking and firewall configuration, such as using iptables or ufw.
  • Ensure that all connection examples are shown for both Windows and Linux environments, with clear distinctions where necessary.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/deploy-system-managed-keytab-active-directory-connector.md ...eploy-system-managed-keytab-active-directory-connector.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation demonstrates Windows bias by referencing Windows-specific tools (e.g., 'netdom query fsmo' for identifying the primary domain controller) without offering Linux alternatives. Windows terminology and patterns (NetBIOS, pre-Windows 2000 name) are used throughout, and Windows-based methods are presented first or exclusively. There are no examples or guidance for performing equivalent tasks on Linux systems, such as querying AD domain controllers or managing service accounts.
Recommendations
  • Provide Linux-based alternatives for Active Directory domain controller discovery, such as using 'ldapsearch' or 'adcli' commands.
  • Include examples and instructions for querying and managing AD from Linux environments, especially for administrators who may not have access to Windows machines.
  • Balance terminology by referencing both Windows and Linux tools and patterns where applicable.
  • Add notes or links to cross-platform tools for AD management (e.g., Samba, Kerberos utilities) to improve accessibility for Linux users.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/managed-instance-high-availability.md ...s/azure-arc/data/managed-instance-high-availability.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. It repeatedly references Windows-centric tools such as SQL Server Management Studio (SSMS) for connecting and managing SQL Managed Instances, without mentioning Linux-native alternatives. Examples and instructions for connecting to the SQL instance and verifying high availability status are provided using SSMS, a Windows-only tool, and no Linux equivalents (such as Azure Data Studio or sqlcmd) are suggested. The documentation also refers to connecting from SSMS before mentioning any cross-platform options, and does not provide explicit examples for Linux users. There are no PowerShell-heavy examples, but the overall pattern favors Windows tooling and omits Linux-native workflows.
Recommendations
  • Include instructions and examples for connecting to SQL Managed Instance using cross-platform tools such as Azure Data Studio and sqlcmd.
  • Explicitly mention Linux-compatible alternatives wherever SSMS is referenced, and provide equivalent command-line examples.
  • Add a section or note highlighting how Linux users can perform all management and monitoring tasks without requiring Windows-only tools.
  • Ensure that examples and tool recommendations are presented in a platform-neutral order, or with Linux-first parity.
  • Where file paths or commands are given, clarify any platform-specific differences (e.g., path separators, file locations) for Linux environments.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/resize-persistent-volume-claim.md ...icles/azure-arc/data/resize-persistent-volume-claim.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation demonstrates Windows bias primarily in the PVC patching step, where the example uses a PowerShell variable assignment syntax ($newsize='...') to construct the JSON patch. This approach is specific to PowerShell and Windows environments, and no equivalent Linux shell (bash) example is provided. The rest of the commands use kubectl, which is cross-platform, but the patching step may confuse Linux users or those using bash, as the variable assignment and quoting are not portable.
Recommendations
  • Provide a Linux/bash-compatible example for the PVC patching step, e.g., using bash variable assignment and proper quoting.
  • Clarify that the $newsize variable assignment is for PowerShell, and offer alternative syntax for bash/zsh users.
  • Review all command examples to ensure they are platform-neutral or offer both Windows and Linux variants where necessary.
  • Add a note or table summarizing command differences between Windows (PowerShell) and Linux (bash) environments for common tasks.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/rotate-customer-managed-keytab.md ...icles/azure-arc/data/rotate-customer-managed-keytab.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation exhibits Windows bias by referencing Windows-specific tools (ktpass.exe), providing PowerShell scripts, and detailing password reset steps using Windows GUI tools (Server Manager, Active Directory Users and Computers). While a bash script is mentioned, the Windows approach (PowerShell/ktpass.exe) is listed alongside and Windows GUI instructions are given for password changes, with no Linux or cross-platform alternatives for domain management. There is no mention of Linux-based Active Directory management or equivalent CLI tools for password resets.
Recommendations
  • Provide explicit Linux-based instructions for resetting Active Directory passwords, such as using 'samba-tool' or 'ldapmodify' on Linux domain controllers.
  • List Linux/bash examples before or alongside Windows/PowerShell examples to avoid Windows-first ordering.
  • Mention Linux equivalents for Windows tools like 'ktpass.exe', such as 'ktutil' or 'adutil', and clarify their usage.
  • Include screenshots or CLI output for Linux-based management tools where Windows GUI screenshots are used.
  • Clarify which steps are platform-specific and offer parity for both Windows and Linux environments.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/managed-instance-features.md ...n/articles/azure-arc/data/managed-instance-features.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ powershell_heavy ⚠️ windows_authentication ⚠️ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing Windows-specific tools (SSMS, SQL Server Data Tools, SQL Server Profiler, PowerShell scripting) and features (Windows Authentication) without mentioning Linux equivalents or alternatives. PowerShell scripting is highlighted as a manageability feature, and Windows Authentication is listed as supported, while there is no mention of Linux authentication mechanisms or scripting environments (e.g., Bash). There are no examples or guidance for Linux users, and the order of tool presentation favors Windows-centric utilities.
Recommendations
  • Include examples and guidance for Linux environments, such as Bash scripting, and reference Linux-native tools (e.g., sqlcmd, Azure Data Studio on Linux).
  • Clarify authentication options for Linux users, such as Kerberos or Microsoft Entra ID, and document any limitations or alternatives to Windows Authentication.
  • Present cross-platform tools first (e.g., Azure Data Studio, Azure CLI) before Windows-only tools to avoid implicit prioritization.
  • Explicitly state platform compatibility for each tool and feature, and provide links to Linux installation and usage guides where available.
  • Add notes or sections highlighting differences and best practices for managing SQL Managed Instance enabled by Azure Arc on Linux.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/privacy-data-collection-and-reporting.md ...zure-arc/data/privacy-data-collection-and-reporting.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation page demonstrates a Windows bias in several ways: Windows is explicitly referenced in billing data examples (osType: Windows), and the example host is 'Hyper-V', a Windows virtualization technology. There are no Linux-specific examples, nor is Linux mentioned as an alternative in scenarios where OS type is relevant. The documentation also references SQL Server, which is traditionally Windows-centric, without clarifying Linux support or providing parity examples. No Linux tools, patterns, or OS-specific guidance are provided, and Windows appears as the default or only context in examples.
Recommendations
  • Provide explicit Linux examples alongside Windows examples, especially in billing data and resource inventory sections (e.g., osType: Linux, manufacturer: Dell, model: PowerEdge, etc.).
  • Clarify that Azure Arc-enabled data services support both Windows and Linux hosts, and describe any differences in data collection or reporting.
  • Include Linux-relevant tools and patterns (e.g., mention systemd, journalctl, or Linux VM types) where applicable.
  • Ensure that examples and sample JSON documents alternate or include both Windows and Linux scenarios.
  • Add a section or note on cross-platform support and any OS-specific considerations for data collection and reporting.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/upload-logs.md ...-docs/blob/main/articles/azure-arc/data/upload-logs.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools ⚠️ linux_parity_good
Summary
The documentation provides environment variable examples for Windows (CMD), PowerShell, and macOS/Linux, with Windows examples consistently presented first. Windows-specific tools (SET, Task Scheduler, .cmd/.bat/.ps1 scripts) are mentioned alongside Linux equivalents. However, Linux and macOS are well-represented, with shell script automation, use of cron, and explicit export commands. The overall parity is good, but the ordering and some tool mentions show a subtle Windows bias.
Recommendations
  • Alternate the order of platform examples, sometimes listing Linux/macOS first to avoid implicit prioritization of Windows.
  • Provide more detailed Linux automation examples (e.g., sample cron job entries) alongside Windows Task Scheduler instructions.
  • Where possible, use platform-neutral language and tools first (e.g., 'export' for environment variables, then show platform-specific alternatives).
  • Include explicit notes that all steps are equally supported on Linux/macOS and Windows, to reinforce parity.
  • Consider grouping automation script examples by platform, rather than listing Windows formats first.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/upload-metrics.md ...cs/blob/main/articles/azure-arc/data/upload-metrics.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell examples are consistently provided and often appear before Linux/macOS equivalents. Windows-specific tools and patterns (e.g., PowerShell environment variables, Windows Task Scheduler) are mentioned explicitly. In some sections, the Windows tab is marked as 'N/A', implying missing or incomplete Windows-specific guidance, while Linux/macOS instructions are more detailed. Automation examples focus on Linux shell scripting, with only brief mentions of Windows automation tools, and no concrete Windows script examples are given.
Recommendations
  • Provide concrete Windows automation script examples (e.g., .bat, .cmd, or PowerShell .ps1) alongside Linux shell scripts.
  • Ensure all CLI examples are available for both Windows and Linux/macOS, with clear instructions for each platform.
  • Mention Windows Task Scheduler and provide step-by-step guidance or examples for scheduling uploads on Windows, not just Linux cron/‘watch’.
  • Avoid marking Windows tabs as 'N/A' unless functionality is truly unavailable; otherwise, supply equivalent commands or note platform limitations.
  • Present platform examples in parallel, rather than always listing PowerShell/Windows first, to avoid implicit prioritization.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/upload-metrics-and-logs-to-azure-monitor.md ...e-arc/data/upload-metrics-and-logs-to-azure-monitor.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation page demonstrates a mild Windows bias. Windows and PowerShell examples are given explicit tabs and are often listed before Linux/macOS equivalents. Windows-specific notes (such as quoting conventions) are called out, and PowerShell environment variable syntax is included as a separate tab. The 'Related content' section links to a PowerShell-specific guide for service principals, rather than a cross-platform or CLI-focused resource. However, Linux/macOS examples are present and reasonably complete.
Recommendations
  • Ensure Linux/macOS examples are given equal prominence, possibly listing Linux/macOS first or side-by-side with Windows.
  • Provide links to cross-platform Azure CLI documentation in 'Related content', not just PowerShell guides.
  • Clarify that all CLI commands work equally on Linux/macOS/Windows, and avoid implying Windows is the default platform.
  • Where quoting or syntax differences exist, explain them in a neutral way without prioritizing Windows.
  • Consider merging PowerShell and Windows tabs if the commands are identical, or clarify when PowerShell is required versus standard CLI.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/view-billing-data-in-azure.md .../articles/azure-arc/data/view-billing-data-in-azure.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ missing_linux_example ⚠️ windows_first
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Windows-centric tools (Excel, Downloads folder) and patterns (downloading and opening CSV files in Excel), without providing equivalent instructions or examples for Linux users. There are no Linux-specific examples or alternative tools mentioned for viewing or manipulating downloaded billing data. The instructions assume a Windows environment (e.g., file paths, default applications) and do not offer parity for Linux workflows.
Recommendations
  • Include Linux-specific instructions for downloading and opening CSV files, such as using LibreOffice Calc, GNOME Spreadsheet, or command-line tools like 'csvkit' or 'awk'.
  • Mention alternative download locations and file navigation patterns for Linux (e.g., ~/Downloads instead of 'Downloads folder').
  • Provide examples of how to automate billing data uploads using Bash scripts or Linux-native tools, not just generic 'scripts'.
  • Ensure that references to file editors and viewers include cross-platform options and do not default to Windows-only applications.
  • Add screenshots or step-by-step guides for Linux users where relevant, especially for tasks performed outside the Azure portal.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/edge-rag/configure-driver-machine.md ...rticles/azure-arc/edge-rag/configure-driver-machine.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation is heavily biased towards Windows, providing only a Windows/PowerShell script and instructions for configuring a Windows machine. There are no Linux or cross-platform examples, and all tool installation steps use Windows-specific patterns and paths. The page title, description, and sample script exclusively reference Windows, omitting Linux equivalents and guidance.
Recommendations
  • Add equivalent instructions and sample scripts for Linux (e.g., Bash shell script) alongside the Windows/PowerShell example.
  • Include Linux-specific download and installation steps for Azure CLI, kubectl, and Helm, using appropriate package managers (apt, yum, etc.) and file paths.
  • Update the title and description to reflect cross-platform support, e.g., 'Configure Machine (Windows or Linux) to Manage Arc-Enabled Kubernetes Cluster'.
  • Present Windows and Linux instructions in parallel sections or tabs, ensuring parity in guidance and examples.
  • Mention cross-platform compatibility of Azure CLI, kubectl, and Helm, and provide links to official installation documentation for both Windows and Linux.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/edge-rag/deploy.md ...t-docs/blob/main/articles/azure-arc/edge-rag/deploy.md
High Priority View Details →
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 in its Azure CLI section by exclusively providing PowerShell-based examples and variable assignments, which are specific to Windows environments. There are no Bash or Linux shell equivalents provided, and the command syntax (e.g., use of `$variable` and backticks for line continuation) is tailored for PowerShell, making it less accessible for Linux or macOS users. The documentation also presents the Windows/PowerShell approach first and omits any mention of Linux-specific tools or patterns.
Recommendations
  • Provide equivalent Bash examples for all Azure CLI commands, including variable assignment and command execution.
  • Clearly indicate which examples are for PowerShell and which are for Bash, using tabs or callouts.
  • Avoid using PowerShell-specific syntax (such as backticks for line continuation) in generic CLI documentation, or provide alternatives for Bash.
  • Mention cross-platform compatibility of Azure CLI and provide guidance for both Windows and Linux/macOS users.
  • Include notes or links to Linux prerequisites or troubleshooting steps where relevant.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/edge-rag/enable-gpu-aks.md ...lob/main/articles/azure-arc/edge-rag/enable-gpu-aks.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example ⚠️ windows_first
Summary
The documentation page exclusively provides a PowerShell script using Windows-specific cmdlets (e.g., Get-PnpDevice, Disable-PnpDevice, pnputil) and patterns for enabling GPU support on AKS via Azure Arc. No Linux or cross-platform alternatives are mentioned, and the instructions assume a Windows environment throughout. There is no guidance for Linux hosts, nor are Linux tools or commands referenced.
Recommendations
  • Add equivalent Linux instructions and sample scripts (e.g., using lspci, lsmod, modprobe, and NVIDIA driver installation via apt/yum).
  • Clearly indicate platform requirements and provide parity for both Windows and Linux hosts.
  • Reference Linux tools and patterns (such as udev, systemctl, and bash scripting) alongside Windows examples.
  • Where possible, use cross-platform Azure CLI commands or Kubernetes-native approaches that work on both Windows and Linux.
  • Include a section that discusses differences and considerations for enabling GPU on Linux-based AKS clusters managed by Azure Arc.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/edge-rag/prepare-authentication.md .../articles/azure-arc/edge-rag/prepare-authentication.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation demonstrates Windows bias by referencing Windows-specific tools (e.g., Notepad) for storing credentials, and by exclusively using Azure Portal GUI instructions without mentioning command-line alternatives (such as Azure CLI or PowerShell). There are no Linux-specific examples or parity for storing credentials, nor are cross-platform command-line patterns provided.
Recommendations
  • Provide examples using Azure CLI for all major steps (app registration, role creation, user assignment), which work on both Windows and Linux.
  • Suggest cross-platform text editors (e.g., VS Code, nano, vim) for storing credentials, rather than only Windows Notepad.
  • Explicitly mention that all steps can be performed from Linux, macOS, or Windows, and link to relevant CLI documentation.
  • Add a section or note on how to perform these tasks in a Linux environment, including screenshots or terminal output where appropriate.
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 →
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 tools (Notepad, Administrator privileges, Windows file path). There are no examples or guidance for Linux or macOS users, such as editing /etc/hosts or using Linux text editors. The documentation assumes a Windows environment and does not mention cross-platform alternatives.
Recommendations
  • Add instructions for editing the hosts file on Linux (e.g., using sudo and a text editor like nano or vim to edit /etc/hosts).
  • Include macOS-specific guidance for editing /etc/hosts.
  • Present cross-platform instructions in parallel or in separate sections, ensuring Linux/macOS steps appear alongside or before Windows steps.
  • Avoid assuming the use of Windows-only tools (e.g., Notepad, Administrator privileges) and mention alternatives for other operating systems.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/edge-rag/prepare-contributor-permission.md ...s/azure-arc/edge-rag/prepare-contributor-permission.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation provides only PowerShell CLI examples for verifying contributor permissions, implicitly favoring Windows users. There is no mention of Linux/macOS shell equivalents, nor are cross-platform usage notes provided. The use of PowerShell syntax and lack of Bash or other shell examples may hinder Linux users.
Recommendations
  • Include Bash/zsh shell examples for the az CLI commands, demonstrating usage on Linux/macOS.
  • Clarify that the az CLI is cross-platform and can be run from any OS terminal, not just PowerShell.
  • Avoid presenting PowerShell syntax exclusively; provide both PowerShell and Bash examples side by side.
  • Add a note about installation and usage of the Azure CLI on Linux and macOS.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/edge-rag/prepare-networking-observability.md ...azure-arc/edge-rag/prepare-networking-observability.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page exclusively provides PowerShell command examples for installing MetalLB and observability modules, with no equivalent Linux shell (bash) commands. The use of PowerShell syntax and Windows-centric command patterns suggests a Windows-first approach, and there are no instructions or examples for Linux users, which may hinder accessibility for those deploying on Linux-based driver machines.
Recommendations
  • Add equivalent bash shell command examples for each PowerShell snippet, ensuring Linux users can follow the instructions without modification.
  • Explicitly state platform requirements or compatibility for each step, clarifying whether commands are intended for Windows, Linux, or both.
  • Where Azure CLI is used, provide cross-platform command syntax and highlight any OS-specific considerations.
  • Include a note or section on prerequisites for both Windows and Linux environments, such as required tools or shell environments.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/edge-rag/requirements.md .../blob/main/articles/azure-arc/edge-rag/requirements.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page shows mild Windows bias. Windows Server is mentioned first in the NFS setup guides, and a Windows machine is suggested as a management host for Azure Arc-enabled Kubernetes clusters. There are references to Windows-specific VM sizes and links to Windows Server documentation, while Linux equivalents are present but less emphasized. Linux examples and guidance are present but not as detailed or prioritized as Windows options.
Recommendations
  • Present Linux setup guides before or alongside Windows Server guides for NFS configuration.
  • Provide explicit Linux management host instructions and tooling recommendations, not just Windows.
  • Include Linux-specific VM sizing and resource links where applicable.
  • Ensure parity in example commands, walkthroughs, and troubleshooting steps for both Windows and Linux environments.
  • Clarify that management can be performed from Linux hosts and provide links to Linux documentation for Azure CLI, kubectl, and Helm installation.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/kubernetes/azure-rbac.md .../blob/main/articles/azure-arc/kubernetes/azure-rbac.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation primarily uses Azure CLI and Azure portal examples, which are available cross-platform, but there are subtle Windows biases. Windows and Mac installation instructions for kubelogin are mentioned before Linux, and Azure portal navigation is described in a way that assumes familiarity with Windows-centric UI patterns. There are no PowerShell examples, but the documentation does not provide Linux-specific alternatives for tasks like editing files (e.g., using 'vi' editor is mentioned, which is common on Linux but not on Windows). The documentation does not mention or provide parity for Linux-native tools or workflows (e.g., using bash scripts for automation, or alternatives to Azure CLI for Linux users). There are also missing Linux-specific troubleshooting steps or considerations.
Recommendations
  • Provide Linux-first or Linux-parallel instructions for all steps, especially for file editing and command-line operations.
  • Include explicit Linux and Windows installation instructions for tools like kubelogin, and ensure Linux instructions are not relegated to secondary status.
  • Offer alternative workflows for Linux users, such as using bash scripts or Linux-native editors (e.g., nano, emacs) alongside 'vi'.
  • Add troubleshooting steps or notes for Linux environments, such as SELinux/AppArmor considerations, file permissions, or systemd service management.
  • Clarify cross-platform compatibility for Azure CLI and portal steps, and mention any OS-specific caveats.
  • Where possible, provide examples using both Azure CLI and Linux-native tools (e.g., curl, jq) for interacting with Kubernetes clusters.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/includes/azure-arc.md ...ocs/blob/main/articles/azure-arc/includes/azure-arc.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal. While Azure CLI is cross-platform, the inclusion of Azure PowerShell (which is historically Windows-centric and still most commonly used on Windows) and the absence of explicit Linux shell examples (e.g., Bash) or references to Linux-native tools indicate a mild Windows bias. Additionally, PowerShell examples are given equal prominence to CLI, and there is no mention of Linux-specific usage patterns or troubleshooting.
Recommendations
  • Add explicit Bash or shell script examples for Linux users, especially for Azure CLI usage.
  • Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and provide any OS-specific notes if relevant.
  • Consider referencing Linux-native tools or patterns where appropriate (e.g., piping CLI output to jq for JSON parsing).
  • If PowerShell is included, note that PowerShell Core is available cross-platform, but also provide equivalent Bash examples for parity.
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 →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation consistently presents both Azure CLI and Azure PowerShell examples for all major operations. However, there is a slight Windows bias: PowerShell (a Windows-centric tool) is always presented as an equal alternative to Azure CLI, and in some sections, environment variable examples use Windows syntax ($Env:...) before or alongside Linux syntax (export ...). There are no explicit Linux shell script examples, nor are Linux-native tools (e.g., bash, curl, systemd) mentioned. The documentation does not clarify which commands are best suited for Linux environments, and PowerShell is not natively available on most Linux distributions. Additionally, there are no explicit instructions for Linux-specific proxy configuration or troubleshooting.
Recommendations
  • Add explicit Linux/Bash examples for environment variable configuration and command execution, especially for proxy setup.
  • Clarify that Azure CLI commands are cross-platform and provide guidance for running them on Linux/macOS.
  • When presenting environment variable setup, show Linux (export) syntax first, then Windows (PowerShell) syntax.
  • Include troubleshooting tips for common Linux proxy issues (e.g., certificate stores, systemd-resolved).
  • Mention that PowerShell is not installed by default on most Linux systems and provide installation instructions or alternatives.
  • Consider adding a 'Platform differences' section to highlight any OS-specific considerations for Azure Arc gateway usage.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/kubernetes/cluster-connect.md .../main/articles/azure-arc/kubernetes/cluster-connect.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for most steps, but the PowerShell examples are prominent and use Windows-specific syntax (e.g., environment variable assignment, base64 decoding). There are no explicit Linux shell examples (e.g., bash, zsh), and the guidance for environment variable handling and token extraction is tailored to Windows/PowerShell users. The use of PowerShell for token manipulation and output is not cross-platform, and there is no mention of Linux-specific considerations or alternative commands for non-Windows users.
Recommendations
  • Add explicit Linux/bash examples for all steps, especially for environment variable assignment and token extraction (e.g., use 'export VAR=value', 'base64 -d', etc.).
  • Where PowerShell is used for base64 decoding or other scripting, provide equivalent bash commands for Linux/macOS users.
  • Clarify which commands are cross-platform (e.g., Azure CLI, kubectl) and which are Windows-specific.
  • Consider reordering examples so that bash/Linux commands are presented first or side-by-side with PowerShell, to avoid implicit Windows-first bias.
  • Add a note or section on platform compatibility, highlighting any differences in command syntax or prerequisites for Linux/macOS users.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/kubernetes/diagnose-connection-issues.md ...les/azure-arc/kubernetes/diagnose-connection-issues.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_examples ⚠️ windows_first
Summary
The documentation provides both Linux and Windows examples for DNS troubleshooting, but the Windows-specific steps (using PowerShell and the Resolve-DnsName cmdlet) are called out separately and in detail. The use of Windows tools (PowerShell, Resolve-DnsName) is explicit, and the Windows example is given after the Linux example, but with more step-by-step detail. The reference to nslookup links to the Windows documentation, even though nslookup is available on Linux. There is no evidence of missing Linux examples, but Windows tools and patterns are highlighted.
Recommendations
  • Provide equal detail for Linux and Windows troubleshooting steps, ensuring parity in explanations and example outputs.
  • Link to cross-platform or Linux documentation for commands like nslookup, not just Windows documentation.
  • Explicitly state that commands like nslookup, host, and curl are available on both Linux and Windows, and provide examples for both where appropriate.
  • Consider grouping OS-specific instructions together and clearly labeling them, rather than interleaving them.
  • Ensure that Linux tools and patterns are mentioned first or equally, not only after Windows equivalents.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/kubernetes/quickstart-connect-cluster.md ...les/azure-arc/kubernetes/quickstart-connect-cluster.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation provides parallel instructions for Azure CLI and Azure PowerShell throughout, but PowerShell is a Windows-centric tool, and there are no explicit Linux shell (bash) or native Linux command examples for Azure management tasks. In several places, Windows and PowerShell usage are mentioned or implied before Linux equivalents. The only non-Azure management commands shown are for kubectl (which is cross-platform), but all Azure resource management is shown via Azure CLI or PowerShell, with no bash scripting or Linux-native workflow guidance. Additionally, when discussing cluster creation, Docker for Mac and Windows are mentioned, but Linux is not, despite being a common platform for Kubernetes.
Recommendations
  • Provide explicit bash/Linux shell examples for all Azure CLI commands, including environment variable setup and scripting patterns.
  • When listing cluster creation options, include explicit instructions or links for creating a Kubernetes cluster on Linux (e.g., using Minikube, KIND, or kubeadm on Ubuntu).
  • Avoid listing Windows or PowerShell options before Linux equivalents; present options in a neutral or Linux-first order, given Kubernetes' Linux-centric nature.
  • Where PowerShell environment variable syntax is shown, also show the equivalent bash export syntax for Linux users.
  • Clarify that Azure CLI is fully supported on Linux and macOS, and provide installation links for those platforms.
  • Add troubleshooting and cleanup steps that are specific to Linux environments, not just Azure CLI or PowerShell.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/kubernetes/resource-graph-samples.md ...rticles/azure-arc/kubernetes/resource-graph-samples.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation mentions Azure PowerShell before Azure CLI when listing query execution options, which may suggest a Windows-first approach. There is an explicit reference to Azure PowerShell, a tool most commonly associated with Windows environments, and no explicit Linux shell (e.g., Bash) or cross-platform CLI examples are provided. The documentation does not provide sample commands or instructions tailored for Linux users, nor does it mention Linux-specific tools or usage patterns.
Recommendations
  • List Azure CLI before Azure PowerShell when describing cross-platform options, as CLI is natively cross-platform.
  • Provide explicit sample commands for both Azure CLI (bash/zsh) and Azure PowerShell, showing usage on Linux and Windows.
  • Mention that Azure CLI is available on Linux, macOS, and Windows, and provide installation or usage links for Linux users.
  • Include examples or notes for running queries in Linux shells, and clarify any platform-specific differences.
  • Avoid implying PowerShell is the primary or default method unless justified by user data.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/kubernetes/system-requirements.md ...n/articles/azure-arc/kubernetes/system-requirements.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation page demonstrates a Windows bias by consistently presenting Azure PowerShell examples alongside Azure CLI, mentioning PowerShell before CLI in several sections, and referencing Windows-centric tools and patterns (such as PowerShell modules and commands). There is no mention of Linux-specific shell usage (e.g., Bash), nor are there examples tailored for Linux environments, despite the fact that Azure CLI is cross-platform and commonly used on Linux. The documentation also references installation paths and behaviors (e.g., Helm installed in the .azure folder) that may be more familiar to Windows users.
Recommendations
  • Provide explicit Bash/Linux shell examples alongside PowerShell, especially for Azure CLI commands.
  • Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
  • Include instructions for installing Azure CLI and extensions on Linux (e.g., apt, yum, zypper) and macOS (brew).
  • Mention Linux-native tools and patterns (e.g., using curl, wget, or package managers) where relevant.
  • Avoid presenting PowerShell examples before CLI, or alternate the order to avoid implicit prioritization.
  • Add notes about file paths and installation behaviors that differ between Windows and Linux environments.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/kubernetes/tutorial-gitops-flux2-ci-cd.md ...es/azure-arc/kubernetes/tutorial-gitops-flux2-ci-cd.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ azure_tools_heavy ⚠️ missing_linux_example
Summary
The documentation demonstrates a bias toward Windows/Azure-centric workflows by prioritizing Azure DevOps and Azure CLI tooling, with extensive step-by-step instructions for Azure DevOps before GitHub. There is a lack of explicit Linux-specific or cross-platform CLI examples (e.g., bash, shell scripting), and no mention of PowerShell, but the overall pattern is Azure/Windows-first. Linux-native alternatives and parity for open-source CI/CD tools are not discussed.
Recommendations
  • Add explicit Linux shell (bash) examples for key steps, such as environment variable management and secret creation.
  • Provide parity in depth and detail for GitHub Actions workflows, matching the step-by-step guidance given for Azure DevOps.
  • Include references to open-source CI/CD tools (e.g., Jenkins, GitLab CI) and how they could be integrated with Flux v2 in Azure Arc/AKS environments.
  • Clarify that all CLI commands (az, kubectl, helm) are cross-platform and provide any OS-specific caveats if relevant.
  • Add troubleshooting tips for Linux environments, such as permissions, file paths, or environment variable handling.
  • Consider reordering sections so that GitHub and Azure DevOps are presented with equal prominence, or provide a table of contents for both workflows up front.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/network-requirements-consolidated.md ...rticles/azure-arc/network-requirements-consolidated.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page demonstrates a bias toward Windows environments by prominently mentioning Windows-centric tools and services (e.g., System Center Virtual Machine Manager, Azure Stack HCI, ESU, VMware vSphere) and omitting explicit Linux-specific examples or references. There are no Linux command-line examples, and Windows/enterprise tools are listed first and in detail, while Linux equivalents or considerations are missing.
Recommendations
  • Add explicit Linux server examples and scenarios, such as Ubuntu or CentOS, in sections discussing Arc-enabled servers.
  • Include Linux command-line tools (e.g., curl, iptables, systemd) for network configuration and troubleshooting alongside any Windows/Powershell references.
  • Mention Linux-based management patterns and tools (e.g., Ansible, SSH) where appropriate.
  • Ensure endpoint and port requirements are illustrated with both Windows and Linux configuration steps.
  • Balance the order of presentation so that Linux and Windows environments are treated equally, or provide parallel examples.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/overview.md ...nagement-docs/blob/main/articles/azure-arc/overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by frequently referencing Windows-centric management tools (such as System Center Virtual Machine Manager and VMware vCenter) and mentioning them before or instead of Linux-native equivalents. There is a lack of explicit Linux tooling or examples, and no mention of Linux-specific management patterns or tools. The documentation refers to Azure PowerShell and CLI but does not provide parity or examples for Linux shell environments. Lifecycle management examples focus on Windows/VMware environments, with no comparable Linux virtualization or management solutions discussed.
Recommendations
  • Include explicit examples and references for Linux environments, such as managing KVM, libvirt, or other Linux-native virtualization platforms.
  • Provide Linux shell (bash) command examples alongside Azure CLI and PowerShell, especially for common management tasks.
  • Mention Linux-native configuration management tools (e.g., Ansible, Chef, Puppet) in the context of Azure Arc integration.
  • Ensure that references to management tools and environments are balanced, listing Linux and Windows options together or in parallel.
  • Add scenarios and guidance for Linux administrators, such as integrating with Linux authentication and security models.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/agent-release-notes-archive.md ...icles/azure-arc/servers/agent-release-notes-archive.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ powershell_heavy
Summary
The documentation page exhibits a moderate Windows bias. Download links for each version consistently list Windows first, with direct MSI links, while Linux links point to a generic installation guide. Windows-specific tools and technologies (PowerShell, .NET, MSI installer, Windows Event Logs, Windows Admin Center, WMI, Win32 API) are frequently mentioned, often with more detail than their Linux equivalents. PowerShell upgrades and requirements are highlighted, and Windows features (GUI installer, event logs, ESU, System Center integration) are described in detail, whereas Linux features are less emphasized or referenced generically. Some fixes and enhancements are explicitly marked as '[Windows Only]' or '[Linux Only]', but Windows features are often described first or in more depth.
Recommendations
  • Provide direct download links for Linux agent packages (RPM/DEB) alongside Windows MSI links for parity.
  • Ensure Linux-specific tools (e.g., systemd, journalctl, package managers) are described with the same level of detail as Windows tools.
  • Include Linux command-line examples (bash, systemctl, journalctl) where Windows PowerShell or GUI examples are given.
  • List Linux and Windows features/fixes in parallel, rather than Windows-first ordering.
  • Highlight Linux-specific enhancements and integrations (e.g., SELinux, systemd, package signing, supported distros) as prominently as Windows features.
  • Where Windows technologies (WMI, Win32 API, event logs) are mentioned, provide Linux equivalents (e.g., /proc, lsb_release, syslog, journald) if applicable.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/resource-bridge/security-overview.md ...rticles/azure-arc/resource-bridge/security-overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page references PowerShell and Azure CLI as methods to retrieve activity logs, but does not provide or mention Linux-specific tools or examples. PowerShell is listed before Azure CLI, which may indicate a Windows-first approach. There are no Linux shell (bash) or native Linux tool examples, nor is there guidance for Linux users on equivalent commands or workflows.
Recommendations
  • Include explicit Linux (bash) examples for retrieving activity logs using Azure CLI.
  • Mention that Azure CLI is cross-platform and provide usage instructions for Linux/macOS.
  • Avoid listing PowerShell before Azure CLI unless there is a technical reason; consider listing Azure CLI first or presenting both equally.
  • Add a note or section for Linux administrators, outlining any platform-specific considerations or steps.
  • Ensure parity in examples and tool recommendations for both Windows and Linux environments.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/resource-bridge/troubleshoot-resource-bridge.md ...re-arc/resource-bridge/troubleshoot-resource-bridge.md
High Priority View Details →
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 forms of Windows bias. Troubleshooting steps and command-line examples frequently reference Windows-specific tools and patterns, such as PowerShell cmdlets and Windows paths. In sections involving network and proxy troubleshooting, PowerShell is used for HTTP/2 testing and DNS resolution, while equivalent Linux commands (e.g., curl, dig, nslookup, wget) are missing or mentioned secondarily. Windows terminology (RDP, time.windows.com, Windows paths) is present throughout, and instructions for resolving errors often assume a Windows environment. Linux-specific troubleshooting (such as SELinux, systemd, or Linux file permissions) is largely absent, and Linux command examples are rare, with only a single reference to checking glibc version. This creates a perception that Windows is the primary or default platform for Azure Arc resource bridge management, potentially leaving Linux administrators without clear guidance.
Recommendations
  • Provide Linux equivalents for all PowerShell and Windows command examples (e.g., curl, wget, dig, nslookup, systemctl, journalctl).
  • Include troubleshooting steps for common Linux issues (e.g., file permissions, SELinux, systemd services, SSH folder access).
  • Mention Linux tools and patterns alongside or before Windows tools, especially in sections about network, DNS, and proxy troubleshooting.
  • Clarify that both Windows and Linux management machines are supported, and specify any platform-specific requirements or limitations.
  • Add explicit instructions for Linux environments when discussing CLI installation, proxy configuration, and log collection.
  • Ensure references to Windows-specific services (e.g., time.windows.com, RDP) are accompanied by Linux alternatives (e.g., ntpd/chrony, SSH).
  • Review error messages and troubleshooting guidance to ensure Linux administrators can follow all steps without ambiguity.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/agent-overview.md ...blob/main/articles/azure-arc/servers/agent-overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ windows_heavy_detail
Summary
The documentation provides detailed and extensive information about Windows agent installation, including MSI packaging, Windows-specific directories, services, accounts, security groups, environment variables, and troubleshooting logs. The Windows section appears first and is more verbose, with specific instructions about Group Policy and antivirus exclusions. Linux installation details are present and reasonably complete, but are presented after Windows and are less detailed in some areas (e.g., no mention of Linux security groups or user rights, less troubleshooting guidance). Windows-specific tools and patterns (MSI, Group Policy, NT SERVICE accounts) are mentioned exclusively, with no Linux equivalents or parity explanations.
Recommendations
  • Present Windows and Linux installation details in parallel sections or tables for direct comparison.
  • Add Linux-specific troubleshooting guidance, such as SELinux/AppArmor, systemd service management, and package manager issues.
  • Include Linux equivalents for Windows-specific concepts, such as service accounts, security groups, and user rights.
  • Provide antivirus/antimalware exclusion recommendations for Linux (e.g., ClamAV, Sophos) if relevant.
  • Ensure that Linux examples and instructions are as detailed and actionable as Windows ones.
  • Consider starting with a cross-platform overview before diving into OS-specific details, or alternate the order between Windows and Linux in different sections.
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 →
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 is consistently mentioned first in download links and feature tables. Troubleshooting and installation instructions provide detailed steps for Windows (e.g., using PowerShell, Command Prompt, msiexec, and GUI actions) but lack equivalent Linux command-line examples (e.g., rpm, dpkg, systemctl usage). Windows-specific issues and tools (elevated PowerShell, Run as administrator, msiexec) are described in detail, while Linux troubleshooting and installation guidance is minimal or missing.
Recommendations
  • Alternate the order of Windows and Linux in download links and feature tables, or list them alphabetically.
  • Provide Linux-specific troubleshooting steps and installation instructions (e.g., using rpm/dpkg, systemctl, sudo).
  • Include Linux command-line examples wherever Windows commands (PowerShell, msiexec) are shown.
  • Ensure parity in describing known issues and fixes for both platforms, not just Windows.
  • Reference Linux tools and patterns (e.g., journalctl, systemctl, package managers) alongside Windows tools.
  • Add explicit guidance for Linux users in sections currently focused on Windows (such as installer troubleshooting).
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/arc-gateway-endpoints.md ...in/articles/azure-arc/servers/arc-gateway-endpoints.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page lists a large number of endpoints, many of which are explicitly Windows-centric (e.g., windowsupdate.com, powershellgallery.com, windows.net, time.windows.com, etc.), and references to Microsoft and Windows services dominate the list. There is no mention of Linux-specific endpoints, nor any examples or guidance for Linux environments. The page implicitly assumes a Windows-first context and omits Linux parity in endpoint coverage or examples.
Recommendations
  • Add a section clarifying which endpoints are relevant for Linux-based Arc-enabled servers, and highlight any Linux-specific endpoints if applicable.
  • Include examples or notes for Linux administrators, such as how to verify endpoint access using Linux tools (e.g., curl, iptables, firewalld) alongside any Windows/Powershell references.
  • Review endpoint list for any Linux-specific services (such as packages.microsoft.com for Linux package updates) and provide context or guidance for those.
  • Balance documentation by explicitly stating that the endpoint list applies to both Windows and Linux, or provide separate lists if there are differences.
  • Avoid using Windows-centric terminology or references (such as Powershell Gallery) without Linux equivalents or alternatives.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/azcmagent-connect.md ...b/main/articles/azure-arc/servers/azcmagent-connect.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation shows a Windows-first bias in several areas. The authentication options section explicitly prioritizes Windows (interactive browser login is described as 'Windows only' and discussed first), while Linux is only mentioned as a default for device code login. The only explicit command for obtaining an access token references the Windows PowerShell cmdlet Get-AzAccessToken, with no equivalent Linux/Azure CLI example. There are no Linux-specific examples or shell commands (e.g., bash, sudo), and the documentation does not clarify cross-platform differences or provide parity in tooling references.
Recommendations
  • Provide Linux-specific or cross-platform examples where relevant, such as showing both PowerShell and bash commands for obtaining access tokens.
  • Avoid presenting Windows authentication methods first unless there is a technical reason; instead, clarify which methods are available on which platforms and present them in a neutral order.
  • For every mention of a Windows tool (e.g., Get-AzAccessToken), include the equivalent Azure CLI or Linux-native command (e.g., az account get-access-token) and usage example.
  • Explicitly state cross-platform compatibility for each authentication method and flag, and note any differences in behavior or prerequisites between Windows and Linux.
  • Add at least one example that demonstrates connecting from a Linux shell, including any necessary sudo usage or environment considerations.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/azcmagent-extension.md ...main/articles/azure-arc/servers/azcmagent-extension.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation demonstrates Windows bias by listing Windows service management commands (Stop-Service, Start-Service) before their Linux equivalents (systemctl stop/start), and by referencing a Windows-specific extension ('AzureMonitorWindowsAgent') in examples. There are no Linux-specific extension examples or Linux-centric usage scenarios provided.
Recommendations
  • Alternate the order of Windows and Linux commands, or list Linux commands first in some sections.
  • Provide Linux-specific extension examples, such as removing a Linux agent extension.
  • Include usage scenarios or troubleshooting tips relevant to Linux environments.
  • Clarify that all examples apply equally to both platforms, or annotate platform-specific differences where relevant.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/billing-extended-security-updates.md ...azure-arc/servers/billing-extended-security-updates.md
High Priority View Details →
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 and its ESU billing via Azure Arc, with no mention of Linux systems, Linux equivalents, or cross-platform scenarios. All examples, terminology, and processes are specific to Windows environments, and Windows-centric tools and licensing models are referenced exclusively.
Recommendations
  • Include examples or notes for Linux servers managed via Azure Arc, clarifying if and how ESU billing or similar processes apply.
  • Add a section comparing Windows and Linux server management in Azure Arc, especially regarding billing, licensing, and security updates.
  • Reference Linux-specific tools or patterns (e.g., package management, update mechanisms) where relevant, or explicitly state that the described processes are Windows-only.
  • Clarify whether any Azure Arc billing or management features differ for Linux servers, and provide guidance for Linux administrators.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/azure-monitor-agent-deployment.md ...es/azure-arc/servers/azure-monitor-agent-deployment.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page demonstrates a moderate Windows bias. PowerShell is repeatedly mentioned as a primary automation and management tool, with no equivalent Bash or Linux shell examples provided. The order of tool presentation (Azure portal, PowerShell, Azure CLI, ARM template) places Windows-centric options first, and there is no explicit mention of Linux-specific tools or workflows. The documentation refers to 'depending on the target operating system' only in passing, without concrete Linux guidance or examples.
Recommendations
  • Add explicit Bash or Linux shell examples for deploying the Azure Monitor agent, alongside PowerShell examples.
  • When listing deployment methods, alternate or parallelize the presentation of Windows and Linux tools (e.g., 'PowerShell or Bash').
  • Include references to Linux-native automation tools (such as Ansible, shell scripts, or systemd timers) where appropriate.
  • Provide step-by-step instructions or links for Linux users, not just generic references to 'depending on the target operating system'.
  • Ensure that screenshots, code samples, and walkthroughs are available for both Windows and Linux environments.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/cloud-native/governance-policy.md ...es/azure-arc/servers/cloud-native/governance-policy.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation page demonstrates a Windows bias by focusing on Windows-centric tools (Group Policy, Active Directory, Windows Firewall, RDP, registry settings) and providing examples and built-in policies exclusively for Windows servers. There is no mention of Linux equivalents (such as Linux configuration files, services, or compliance standards), nor are Linux-specific examples or policies discussed. The comparison and migration narrative centers on Windows administration patterns, leaving Linux users without guidance on parity or integration.
Recommendations
  • Include examples of Azure Policy auditing and enforcing settings on Linux servers (e.g., SSH configuration, firewall rules via iptables/firewalld, password policies in /etc/login.defs).
  • Reference Linux equivalents to Windows tools (such as systemd, PAM, auditd) when discussing policy enforcement and compliance.
  • Highlight built-in Azure Policy machine configuration policies for Linux, if available, and provide links or examples.
  • Discuss how Azure Policy interacts with Linux configuration management tools (e.g., Ansible, Chef, or native DSC for Linux).
  • Balance the narrative by describing hybrid environments that include both Windows and Linux servers, and how Azure Policy supports both.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/cloud-native/inventory-resource.md ...s/azure-arc/servers/cloud-native/inventory-resource.md
High Priority View Details →
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 referencing Windows-centric tools and concepts (Active Directory, SCCM, Group Policy Objects) as primary analogies for Azure resource organization. It mentions querying for 'Windows Server 2012' as an example in Azure Resource Graph, but does not provide Linux-specific examples or analogies (such as LDAP, Ansible, or Linux configuration management tools). There are no Linux/POSIX-centric organizational patterns or inventory examples, and no mention of Linux-specific resource attributes or queries.
Recommendations
  • Add Linux-centric analogies when describing resource organization (e.g., compare resource groups to LDAP organizational units or Ansible inventory groups).
  • Provide examples of Azure Resource Graph queries for Linux servers (e.g., finding all Ubuntu servers or servers with specific Linux distributions/tags).
  • Reference Linux configuration management tools (such as Chef, Puppet, or Ansible) alongside SCCM when discussing inventory and change tracking.
  • Include examples or screenshots showing both Windows and Linux servers in inventory views.
  • Mention Linux-specific attributes (such as /etc/os-release, systemd services, or package managers) when discussing change tracking and inventory.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/cloud-native/overview.md ...in/articles/azure-arc/servers/cloud-native/overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing traditional Windows management tools (Active Directory Group Policy, SCCM, MECM, PowerShell remoting, WSUS) as the primary examples of on-premises management. These tools are mentioned exclusively or before any Linux equivalents, and there are no references to common Linux management patterns (such as Ansible, Chef, Puppet, or Linux-native configuration management and patching tools). The examples and analogies are heavily oriented toward Windows administrators, with little guidance for users familiar with Linux server management.
Recommendations
  • Add references to common Linux management tools (e.g., Ansible, Chef, Puppet, cron, yum/apt for patching) when discussing traditional on-premises management.
  • Provide explicit Linux-focused examples or analogies alongside Windows ones, such as how Azure Policy or Machine Configuration can replace Linux configuration management tools.
  • Mention Linux-native scripting and remote management patterns (e.g., SSH, shell scripts) in parallel with PowerShell and RDP.
  • Clarify that Azure Arc supports both Windows and Linux servers, and highlight Linux-specific features or considerations where relevant.
  • Include Linux licensing and update scenarios (e.g., kernel patching, distribution-specific update management) in the licensing and patching sections.
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 →
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. Examples and scenarios focus on Windows (e.g., Remote Desktop, AD domain join, LAPS), with Linux access (SSH) only briefly mentioned and lacking detailed examples. There is minimal coverage of Linux-specific identity management practices or tools, and no Linux-focused walkthroughs or parity in examples.
Recommendations
  • Provide Linux-specific examples for identity and access management, such as using SSH with Microsoft Entra ID, and managing Linux local accounts.
  • Include Linux-native identity management tools and patterns (e.g., sudoers, PAM, SELinux, systemd-logind) alongside Windows tools like LAPS and Group Policy.
  • Ensure that examples and scenarios are presented for both Windows and Linux platforms, ideally in parallel, to avoid a Windows-first impression.
  • Add guidance for integrating Microsoft Entra ID with Linux authentication mechanisms, such as using SSSD or other Entra-compatible PAM modules.
  • Explicitly mention how hybrid identity configurations apply to Linux servers, not just AD domain-joined Windows servers.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/cloud-native/licensing-cost-management.md ...-arc/servers/cloud-native/licensing-cost-management.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation page focuses almost exclusively on Windows Server and SQL Server licensing options via Azure Arc, with all examples, scenarios, and tools described in a Windows-centric context. There are no references to Linux servers, Linux licensing models, or Linux-specific management patterns. Windows tools and concepts (such as product keys, CALs, ESUs, and Azure Update Manager for Windows) are mentioned throughout, while Linux equivalents are absent.
Recommendations
  • Add sections describing how Azure Arc licensing and cost management applies to Linux servers, including any differences or limitations.
  • Provide Linux-specific examples and workflows, such as onboarding Linux servers to Azure Arc, managing updates, and tracking licensing or subscription costs.
  • Mention Linux-compatible tools for update management and compliance reporting, and clarify whether features like pay-as-you-go licensing or ESUs are available for Linux workloads.
  • Ensure parity in documentation structure by presenting Windows and Linux scenarios side-by-side where possible, or at least referencing Linux applicability in each major section.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/cloud-native/monitor-alerts.md ...icles/azure-arc/servers/cloud-native/monitor-alerts.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation page demonstrates a mild Windows bias. Windows tools (System Center Operations Manager, Windows Event logs) are mentioned first or exclusively, and examples for Linux (such as syslog) are referenced only briefly and without detail. There are no Linux-specific monitoring or alerting examples, nor are Linux command-line tools or patterns discussed. The documentation assumes familiarity with Windows-centric monitoring approaches and does not provide parity for Linux administrators.
Recommendations
  • Provide explicit Linux monitoring examples, such as collecting logs from /var/log, using journalctl, or integrating with Linux-native tools.
  • Mention Linux equivalents to Windows tools (e.g., alternatives to SCOM, Linux event logging patterns) and provide guidance for Linux administrators.
  • Include sample data collection rules (DCRs) for both Windows and Linux, showing how to collect syslog, custom log files, and metrics from Linux systems.
  • Add command-line examples for Linux (bash, shell scripts) alongside any PowerShell or Windows CLI references.
  • Ensure that documentation sections do not default to Windows-first language or examples, and strive for equal coverage of both platforms.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/cloud-native/patch-management.md ...les/azure-arc/servers/cloud-native/patch-management.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page demonstrates Windows bias by referencing traditional Windows patch management tools (WSUS, SCCM) exclusively and first, providing examples and analogies based on Windows workflows, and giving detailed hotpatching coverage only for Windows Server. Linux support is mentioned but lacks equivalent detail, examples, or analogies to common Linux patching tools and patterns. There are no Linux-specific patching scenarios or step-by-step examples, and the Linux auto-update section is brief compared to Windows coverage.
Recommendations
  • Include references to traditional Linux patch management tools (e.g., apt, yum, dnf, zypper, cron jobs) alongside Windows tools in the introduction.
  • Provide Linux-specific patching workflow examples, such as scheduling updates with cron or using unattended-upgrades/dnf-automatic.
  • Offer analogies to Linux-native compliance reporting tools (e.g., log parsing, package manager history) when discussing dashboards.
  • Expand the hotpatching section to clarify Linux kernel live patching support (if any) or explicitly state its absence.
  • Add step-by-step Linux patching scenarios, including pre/post script examples using bash or Python.
  • Ensure parity in detail and examples for both Windows and Linux throughout the documentation.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/license-extended-security-updates.md ...azure-arc/servers/license-extended-security-updates.md
High Priority View Details →
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 environments, with all examples and scenarios exclusively referencing Windows Server hosts, VMs, and licensing models. There are no examples or guidance for Linux servers, nor are Linux tools or patterns mentioned. The documentation assumes the reader is managing Windows infrastructure and does not address cross-platform or Linux-specific considerations, despite Azure Arc supporting Linux servers.
Recommendations
  • Include equivalent licensing and provisioning guidance for Linux servers managed via Azure Arc, even if ESUs are not applicable, to clarify cross-platform support.
  • Add scenario-based examples that involve Linux VMs or mixed Windows/Linux environments to demonstrate parity and integration.
  • Explicitly mention any limitations or differences for Linux servers in the context of Azure Arc ESU licensing, and provide links to Linux-specific documentation where relevant.
  • Ensure that onboarding and management instructions reference both Windows and Linux tooling (e.g., Bash, SSH, Linux agents) where applicable.
  • Consider adding a section that addresses how organizations with hybrid Windows/Linux estates should approach ESU provisioning and Azure Arc management.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/manage-vm-extensions.md ...ain/articles/azure-arc/servers/manage-vm-extensions.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ windows_heavy_examples
Summary
The documentation page exhibits a Windows bias in several ways. The Windows extensions table is presented before the Linux extensions table, and the Windows table is significantly longer and more detailed, listing more extensions and providing more links. Windows-specific tools and patterns (e.g., Windows Admin Center, PowerShell, Windows Patch extension) are mentioned, while their Linux equivalents are either missing or less emphasized. The partner extensions also list Windows variants first. The deployment methods mention Azure PowerShell (primarily Windows-focused) alongside Azure CLI, but do not provide parity for Linux-native management tools or shell examples.
Recommendations
  • Present Windows and Linux extension tables side-by-side or alternate their order to avoid implicit prioritization.
  • Ensure the number and detail of Linux extension examples matches that of Windows, including parity in links and descriptions.
  • Add Linux-native management tool examples (e.g., Bash, shell scripts) where PowerShell is mentioned.
  • Highlight Linux-specific extensions and use-cases, such as SELinux, systemd, or other common Linux management patterns.
  • Where Windows-specific tools are referenced (e.g., Windows Admin Center), mention Linux alternatives or clarify their scope.
  • In partner extension tables, alternate the order of Windows and Linux variants or combine them where possible.
  • Review all extension documentation links to ensure Linux support is equally visible and accessible.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/deliver-extended-security-updates.md ...azure-arc/servers/deliver-extended-security-updates.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation is exclusively focused on Windows Server 2012 and its management via Azure Arc. All examples, screenshots, and instructions pertain to Windows environments, with no mention of Linux equivalents, Linux patching, or cross-platform scenarios. Windows-specific tools (WSUS, Configuration Manager) are referenced, and there are no Linux or PowerShell alternatives or parity examples. The documentation assumes the reader is managing Windows servers only, and does not address mixed or Linux-only environments.
Recommendations
  • Explicitly state that the process is Windows-only, or add guidance for Linux servers if Azure Arc supports similar ESU or lifecycle management for Linux.
  • Include examples or references for managing Linux servers in Azure Arc, if applicable, such as patching, compliance, or license management.
  • Mention Linux-compatible patching solutions (e.g., Azure Update Manager for Linux, third-party Linux patching tools) alongside Windows tools.
  • If Azure Arc ESU licensing is not available for Linux, clarify this limitation early in the documentation.
  • Add a section comparing Windows and Linux server lifecycle management in Azure Arc, highlighting differences and similarities.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/deployment-options.md .../main/articles/azure-arc/servers/deployment-options.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by providing several Windows-specific onboarding methods (Windows Admin Center, Group Policy, Configuration Manager) without Linux equivalents. PowerShell is mentioned as a cross-platform method, but Linux-native automation tools (e.g., shell scripts, cloud-init) are not highlighted. Windows tools and patterns (Group Policy, Configuration Manager, Windows Admin Center) are described in detail, whereas Linux-specific onboarding options are limited to Ansible and generic scripts, with no mention of popular Linux management frameworks. Windows-only methods are listed separately, and there are no Linux-only onboarding examples.
Recommendations
  • Add Linux-specific onboarding examples, such as using shell scripts, cloud-init, or native Linux configuration management tools (e.g., Puppet, Chef).
  • Provide parity for Windows-only methods by describing Linux equivalents (e.g., onboarding via Linux package managers, systemd services, or SSH-based automation).
  • Include Linux-first or Linux-native automation options in the onboarding methods table.
  • Ensure that PowerShell examples are supplemented with Bash or other Linux shell examples where applicable.
  • Highlight Linux management frameworks and tools alongside Windows tools to balance the documentation.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/includes/network-requirements.md ...les/azure-arc/servers/includes/network-requirements.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation demonstrates a moderate Windows bias. Windows-specific tools and concepts (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 Windows guidance and troubleshooting, but Linux is only briefly referenced with a link to OpenSSL. There are no Linux-specific troubleshooting steps or configuration examples, and Windows-centric terminology (e.g., 'Windows only' agent features, Windows Server version support) is used throughout. Linux is often mentioned second or as an afterthought.
Recommendations
  • Provide Linux-specific troubleshooting guidance and configuration steps, especially for TLS and networking issues.
  • Include Linux-first examples or mention Linux tools (e.g., OpenSSL configuration, firewall rules with iptables/nftables) alongside or before Windows tools.
  • Balance references to Windows Admin Center with equivalent Linux management tools or clarify when features are Windows-only.
  • Add parity in documentation structure: for every Windows-specific section or note, ensure a Linux equivalent is present or explicitly state differences.
  • Use neutral ordering (e.g., 'Linux and Windows') rather than 'Windows and Linux' to avoid implicit prioritization.
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 →
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 tools (such as PowerShell, Group Policy, Microsoft Update, and Msiexec) are often presented first, in greater detail, or with more context than their Linux equivalents. Windows-specific automation and update infrastructure (WSUS, Configuration Manager) are described extensively, while Linux package management is covered in a more generic, less integrated way. PowerShell examples are frequent, and Windows administrative patterns (Control Panel, Registry Editor) are explained in depth, whereas Linux instructions are more concise and lack similar operational context.
Recommendations
  • Provide Linux examples and instructions with equal detail and context as Windows, including automation methods (e.g., using Ansible, systemd, or shell scripts for upgrades and configuration).
  • Include Linux-first sections or alternate between Windows and Linux in ordering, rather than consistently leading with Windows.
  • Expand on Linux update infrastructure, such as integrating with enterprise tools like Red Hat Satellite, SUSE Manager, or Ubuntu Landscape, similar to how WSUS and Configuration Manager are covered for Windows.
  • Offer troubleshooting and operational guidance for Linux environments (e.g., log file locations, service management, package rollback) with the same depth as Windows.
  • Where PowerShell is used for Windows automation, provide Bash or Python script equivalents for Linux.
  • Clarify cross-platform differences and parity, and explicitly state when features or methods are Windows-only or Linux-only.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/managed-identity-authentication.md ...s/azure-arc/servers/managed-identity-authentication.md
High Priority View Details →
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 frequently mentioned first, with PowerShell examples and references to Windows-specific tools and groups appearing before their Linux equivalents. Some links and instructions are Windows-centric, and Linux examples are less detailed or presented as secondary. The prerequisites and example sections often prioritize Windows, and PowerShell is the only scripting language referenced for access policy assignment, with Azure CLI mentioned only in 'Next steps'.
Recommendations
  • Present Linux and Windows instructions/examples in parallel, or alternate which comes first.
  • Include Azure CLI and Bash examples wherever PowerShell is referenced, especially for access policy assignment.
  • Ensure links to Linux-specific tutorials and documentation are given equal prominence as Windows links.
  • Expand Linux prerequisites and group membership details to match the specificity given for Windows.
  • Add more detailed Linux/Bash examples and screenshots where PowerShell examples are shown.
  • Avoid using Windows-centric terminology (e.g., IIS, Administrators group) without Linux equivalents or context.
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 →
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 areas. Most code examples for enabling and updating VM extensions use Windows-specific tools and commands, such as 'powershell.exe' and PowerShell syntax in the Custom Script Extension. Extension examples (Antimalware, Datadog) are exclusively for Windows, with no Linux equivalents or examples shown. The naming and output samples also reference Windows extensions (e.g., 'DependencyAgentWindows'), and Linux-specific extension usage is not illustrated. There is a lack of parity in showing Linux shell commands or Linux-specific extension scenarios.
Recommendations
  • Include Linux-specific examples for enabling and updating extensions, such as using bash/sh commands in the Custom Script Extension.
  • Provide extension examples for popular Linux scenarios (e.g., DependencyAgentLinux, monitoring agents, security extensions for Linux).
  • Show both Windows and Linux extension names/types in output and command samples.
  • Balance the documentation by alternating Windows and Linux examples, or presenting them side-by-side.
  • Explicitly mention differences in extension usage or configuration between Windows and Linux where relevant.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/manage-vm-extensions-portal.md ...icles/azure-arc/servers/manage-vm-extensions-portal.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation page demonstrates subtle Windows bias. While it claims to support both Linux and Windows hybrid machines, the only specific example given is for deploying the Azure Monitor agent for Windows using a proxy. No Linux-specific extension configuration or example is provided. Additionally, the mention of Azure PowerShell (a Windows-centric tool) appears before the Azure CLI in both the note and related content, and no Linux command-line tools or patterns are highlighted.
Recommendations
  • Include explicit examples for deploying and configuring extensions on Linux machines, such as the Azure Monitor agent for Linux.
  • Provide screenshots or configuration field walkthroughs for Linux extensions, not just Windows.
  • When listing command-line tools, mention Azure CLI before Azure PowerShell, or clarify cross-platform compatibility.
  • Add notes or tips relevant to Linux users, such as common extension scenarios or troubleshooting steps for Linux servers.
  • Ensure parity in extension support documentation by listing any Linux-specific limitations or considerations.
GitHub Create Pull Request
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 →
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 prioritizing Windows-specific tools and workflows, such as Windows Admin Center, Windows Server Graphical Installer, and PowerShell, with limited or no equivalent Linux examples or tool references. Windows deployment methods are mentioned before Linux alternatives, and Linux-specific instructions or examples are missing in several key sections.
Recommendations
  • Add explicit Linux deployment examples and workflows, such as using Bash scripts, systemd, or native Linux package managers (apt, yum, zypper) for agent installation and management.
  • Include references to Linux configuration management tools (e.g., Chef, Puppet, SaltStack) alongside Ansible, and clarify their support for Azure Arc onboarding.
  • Provide step-by-step instructions or links for deploying Azure Arc and Azure Monitor Agent on popular Linux distributions, including troubleshooting and prerequisites.
  • Balance PowerShell examples with Bash or shell script equivalents, and ensure CLI instructions are cross-platform.
  • Mention Linux graphical tools (if any) or clarify that certain graphical installers are Windows-only, suggesting alternatives for Linux users.
  • Ensure that all sections referencing Windows-specific features (e.g., Windows Admin Center) also note Linux options or explicitly state platform limitations.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/manage-vm-extensions-template.md ...les/azure-arc/servers/manage-vm-extensions-template.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page exhibits a Windows bias primarily through exclusive use of PowerShell for deployment commands, reliance on Windows-centric tooling and paths in examples, and lack of Linux-native command-line alternatives. While ARM template samples are provided for both Linux and Windows extensions, all deployment instructions and command-line examples use PowerShell, with Windows-style file paths and no mention of Bash, Azure CLI, or Linux shell equivalents. This may hinder Linux users or those working in non-Windows environments.
Recommendations
  • Provide equivalent deployment instructions using Azure CLI (az deployment group create) and Bash shell commands alongside PowerShell examples.
  • Include Linux-style file paths (e.g., /home/user/Azure/Templates/...) in sample commands.
  • Explicitly state that both Linux and Windows machines can be managed, and offer platform-agnostic or platform-specific guidance as needed.
  • Add a section or note on how to run deployments from Linux/macOS environments, including prerequisites and any differences.
  • Ensure parity in troubleshooting and management links for both PowerShell and Azure CLI.
  • Consider reordering or balancing examples so that Linux and Windows are presented equally, rather than Windows-first or Windows-only.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/onboard-portal.md ...blob/main/articles/azure-arc/servers/onboard-portal.md
High Priority View Details →
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 steps and command examples for Windows (including PowerShell and msiexec usage), and references Windows-specific tools and patterns (such as MSI installers and Windows environment variables). Linux instructions are present and reasonably complete, but less detailed and appear after Windows. The scripted method for Windows is described with PowerShell, while the Linux equivalent uses bash, but the Windows section is more verbose and tool-specific.
Recommendations
  • Present Windows and Linux instructions in parallel or in separate, equally detailed sections to avoid ordering bias.
  • Ensure Linux examples are as detailed as Windows ones, including troubleshooting steps, log locations, and command explanations.
  • Where possible, use cross-platform terminology and avoid referencing Windows tools (e.g., msiexec, PowerShell) before their Linux equivalents.
  • Include Linux-specific notes (such as SELinux, systemd service management, or package manager troubleshooting) to match the depth of Windows notes.
  • Explicitly mention that both Windows and Linux are supported and provide a summary table or flowchart for both OSes at the start.
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 →
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 by referencing Azure PowerShell and the Azure portal as primary onboarding methods, mentioning Windows in examples before Linux, and lacking explicit Linux-specific tooling or command-line examples (e.g., Bash, shell scripts). While Linux is mentioned in passing, there are no detailed Linux-centric instructions, and Windows tools/patterns are referenced first or exclusively in several places.
Recommendations
  • Provide explicit Linux command-line examples (e.g., Bash scripts, CLI commands) alongside or before Windows/PowerShell examples.
  • Reference Linux-native automation tools (such as Ansible, shell scripting, or cloud-init) for agent deployment and management.
  • Ensure onboarding and management instructions are equally detailed for Linux and Windows, including prerequisites, troubleshooting, and update management.
  • Where Azure PowerShell is mentioned, also mention Azure CLI or other cross-platform tools, and provide equivalent instructions.
  • Clarify that all steps and tools are applicable to both Windows and Linux, or specify differences where relevant.
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 →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example ⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation exclusively describes onboarding Windows machines using Configuration Manager, with all examples and instructions focused on Windows tools (.msi installer, PowerShell scripts, Configuration Manager UI). There are no references to Linux equivalents, Linux agent packages, or cross-platform task sequence patterns. PowerShell is the only scripting language shown, and Windows Installer is the only packaging format mentioned.
Recommendations
  • Add parallel instructions for onboarding Linux machines, including references to the Linux agent package (.deb/.rpm) and command-line installation steps.
  • Provide example task sequences or deployment methods for Linux endpoints, such as using shell scripts or native Linux management tools (e.g., Ansible, Puppet, or SCCM for Linux).
  • Include Linux-specific verification steps and troubleshooting guidance.
  • Mention cross-platform considerations and clarify which steps are Windows-only.
  • Where PowerShell is used, offer Bash or shell script alternatives for Linux.
  • Reference Linux documentation and tools alongside Windows equivalents, ensuring parity in visibility and guidance.
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 →
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, including the creation of service principals and the installation script generation. PowerShell examples are given in detail, while Linux-specific command-line or automation examples are less emphasized or missing. The troubleshooting note refers specifically to Windows PowerShell, and there is more explicit guidance for Windows users (e.g., script file names, compatibility notes). Linux equivalents are referenced but not given equal detail or prominence.
Recommendations
  • Provide Linux-specific command-line examples (e.g., Bash, shell scripting) alongside PowerShell examples, especially for service principal creation and agent installation.
  • Ensure Linux instructions and examples are presented with equal prominence and detail as Windows instructions.
  • Add troubleshooting notes relevant to Linux environments (e.g., common permission issues, shell compatibility).
  • Clarify automation options for Linux (e.g., using Ansible, shell scripts) in addition to Windows automation tools.
  • Avoid Windows-first ordering in lists and examples; alternate or parallelize instructions for both platforms.
  • Explicitly mention supported Linux distributions and any platform-specific caveats.
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 →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation mentions both Windows and Linux support for Azure Arc-enabled servers, but several sections and linked resources prioritize Windows terminology, tools, and examples. PowerShell and Windows registry are referenced before Linux equivalents, and some links default to Windows tabs. There is a lack of explicit Linux command-line examples or references to Linux-specific management tools, which may make Linux users feel secondary.
Recommendations
  • Provide explicit Linux command-line examples (e.g., Bash, shell scripts) alongside PowerShell examples.
  • Ensure documentation links and tabs default to a neutral or Linux-first view where appropriate.
  • Mention Linux daemons and configuration files with equal prominence to Windows registry and files.
  • Reference Linux-native automation and monitoring tools (e.g., systemd, cron) where relevant.
  • Add step-by-step Linux onboarding and troubleshooting guides to match Windows coverage.
  • Review all linked articles to ensure Linux parity in examples and instructions.
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 →
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 examples and tools (e.g., PowerShell commands, Windows-specific instructions) are consistently presented before Linux equivalents. Some instructions, such as removing VM extensions, are described in detail for Windows (using the Azure portal and PowerShell), while Linux instructions are less detailed or refer users to external documentation. The page also references Windows tools and patterns (e.g., Remote Desktop Connection, WindowsAzureGuestAgent) more prominently. Although Linux examples are present, they are sometimes less thorough or secondary.
Recommendations
  • Present Linux and Windows instructions in parallel, giving equal prominence to both.
  • Provide direct, detailed Linux command examples for all steps, not just references to external documentation.
  • Include Linux-specific troubleshooting tips and caveats, similar to those provided for Windows.
  • Avoid listing Windows examples or tools first by default; alternate or combine instructions when possible.
  • Ensure that all screenshots, links, and resources are available for both Windows and Linux environments.
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 →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation demonstrates a mild Windows bias. Windows-specific tools and paths (e.g., Windows Admin Center, C:\Windows\System32\drivers\etc\hosts) are mentioned before their Linux equivalents. Windows instructions are provided first in the 'Single server scenarios' section, and Windows agent download links are more prominent. There is no mention of Linux-specific troubleshooting commands or tools, and some examples (such as firewall configuration) are generic but lack explicit Linux guidance. Powershell or Windows-centric management tools are referenced, while Linux alternatives are not.
Recommendations
  • Alternate the order of Windows and Linux instructions so that Linux is not always second.
  • Provide explicit Linux troubleshooting commands (e.g., dig, systemctl for agent status) alongside nslookup.
  • Include Linux-specific firewall configuration guidance (e.g., iptables, firewalld, ufw) in addition to generic advice.
  • Mention Linux management tools or workflows where Windows Admin Center is referenced.
  • Ensure agent download instructions for Linux are as detailed and visible as those for Windows.
  • Add examples using Linux shell commands for agent installation and verification.
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 →
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 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 default script type suggests a Windows-first approach, and there is no mention of Linux-specific usage or equivalent commands/tools. This may lead Linux users to feel unsupported or unclear about how to use the feature with their preferred shell environments.
Recommendations
  • Add Linux shell (bash/sh) script examples alongside PowerShell examples for all CLI commands.
  • Explicitly mention that both Windows and Linux Arc-enabled servers are supported, and clarify any differences in script execution environments.
  • Provide guidance on how to specify the script type or interpreter (e.g., bash vs PowerShell) when using 'az connectedmachine run-command'.
  • Ensure that documentation sections and examples alternate or balance between Windows and Linux scenarios to avoid implicit prioritization.
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 →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation page exhibits a strong Windows bias. All example scenarios, scripts, and parameters are tailored to Windows Server environments, specifically referencing Windows Server 2012/R2. The only script examples use PowerShell cmdlets (e.g., New-NetFirewallRule), and there is no mention or example of Linux shell scripts or Linux firewall tools. Additionally, instructions for generating SAS tokens exclusively reference the PowerShell tool New-AzStorageBlobSASToken, with no Linux CLI alternatives. The related content also prioritizes PowerShell and Windows-centric resources.
Recommendations
  • Add equivalent example scenarios for Linux Arc-enabled servers, such as configuring firewall rules using bash scripts and Linux tools (e.g., iptables, ufw, firewalld).
  • Provide sample REST API payloads for Linux, demonstrating how to execute shell scripts remotely.
  • Include instructions for generating SAS tokens using Azure CLI (az storage blob generate-sas), which is cross-platform and widely used on Linux.
  • Clarify in the prerequisites and examples that both Windows and Linux Arc-enabled servers are supported, and highlight any OS-specific considerations.
  • Balance related content links to include Linux-focused documentation and examples.
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 →
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 specific to Windows environments (e.g., Group Policy, Configuration Manager, SCVMM). There are no Linux-specific instructions, examples, or mentions of Linux tools or onboarding patterns. The documentation assumes the reader is managing Windows machines and does not address Linux server scenarios, even though Azure Arc supports both Windows and Linux servers.
Recommendations
  • Add explicit guidance and examples for onboarding Linux servers to Azure Arc for ESU delivery, including supported distributions and prerequisites.
  • Include Linux-specific deployment options, such as using shell scripts, Ansible, or other Linux-native automation tools for at-scale onboarding.
  • Mention how ESU delivery and Azure Arc features apply to Linux servers, or clarify if ESUs are only available for Windows Server (and state this clearly).
  • Provide parity in networking and certificate installation instructions for Linux environments, including relevant commands and troubleshooting steps.
  • If ESUs are not available for Linux, add a clear note at the beginning to set expectations for Linux users.
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 →
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, tools, and examples (such as PowerShell scripts and Group Policy Editor usage) are provided in detail, often before or instead of Linux equivalents. Windows onboarding scripts are shown explicitly, while Linux onboarding is described only in general terms. Windows tools (gpedit.msc, Group Policy) are mentioned without Linux alternatives. Linux requirements are listed, but practical examples and troubleshooting steps are missing.
Recommendations
  • Provide Linux onboarding script examples, including how to specify agent versions for limited support OSes.
  • Include Linux-specific troubleshooting steps and configuration guidance, such as managing systemd services or permissions.
  • Mention Linux equivalents for Windows tools (e.g., how to check service permissions or logs on Linux).
  • Balance the order of presentation so that Linux instructions/examples are given equal prominence to Windows.
  • Where Windows-specific features (like Group Policy) are discussed, add notes or sections for Linux system management practices.
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 →
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 agent installation section, Windows instructions (using PowerShell) are presented before Linux instructions, and the Windows example is more explicit about the shell to use ('elevated 64-bit PowerShell command prompt'). The Linux section is less detailed and lacks parity in terms of troubleshooting or alternative shell guidance. The script generation steps also reference Windows-centric terminology (e.g., 'folder or share'), and the overall flow assumes familiarity with Windows tools and patterns.
Recommendations
  • Alternate the order of Windows and Linux instructions in sections, or present them side-by-side for parity.
  • Provide equally detailed instructions for Linux, including specifying recommended shells (e.g., Bash, Zsh) and troubleshooting tips.
  • Avoid Windows-centric terminology like 'folder or share'; use cross-platform language such as 'directory or network location'.
  • Include example commands for both Windows (PowerShell) and Linux (Bash) in all relevant sections.
  • Ensure that any references to tools or environments (e.g., PowerShell) are matched with Linux equivalents (e.g., Bash, Terminal) and described with equal clarity.
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 →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation demonstrates a bias toward Windows and PowerShell by providing detailed PowerShell instructions and references before or instead of equivalent Linux/bash examples. While Azure CLI is mentioned, PowerShell is often presented first and in more detail. There is a lack of explicit Linux shell command examples, and references to exporting data (e.g., to CSV) use Windows-centric tooling. The installation of the Azure Guest Agent references both Windows and Linux, but the overall pattern prioritizes Windows tools and workflows.
Recommendations
  • Provide Linux/bash command examples alongside PowerShell, especially for tasks like listing extensions and exporting data.
  • When referencing exporting data (e.g., role assignments), include Linux-native options (such as using jq or awk with Azure CLI output).
  • Alternate the order of presenting Windows and Linux instructions to avoid implicit prioritization.
  • Ensure troubleshooting and migration steps include Linux-specific guidance and links.
  • Explicitly mention cross-platform compatibility for all tools and commands, and clarify when instructions differ between Windows and Linux.
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 →
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 by listing Windows file paths and group names before Linux equivalents, referencing Windows-specific concepts (such as 'local administrators'), and using Windows terminology (e.g., 'C:\ProgramData\...') as the primary example. Linux paths and groups are mentioned, but typically after the Windows ones. There are no explicit Linux command-line or tool examples, and no parity in showing Linux-specific management patterns.
Recommendations
  • Present Linux and Windows examples side-by-side or alternate which platform is listed first.
  • Include Linux-specific command-line examples (e.g., using bash or Linux tools) where relevant.
  • Clarify group and permission management for Linux (e.g., show how to add a user to the 'himds' group using Linux commands).
  • Avoid Windows-centric terminology when describing generic concepts (e.g., use 'system administrators' instead of 'local administrators').
  • Provide parity in troubleshooting steps and examples for both platforms.
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 →
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 by centering Azure Machine Configuration around PowerShell Desired State Configuration, mentioning Windows Admin Center (WAC) as a primary remote management tool, and providing more detailed descriptions and role assignments for Windows scenarios. Linux is referenced mainly in the context of SSH access, with fewer details and no equivalent to WAC or PowerShell DSC for Linux. Examples and tooling are Windows-centric, and Linux alternatives are not equally highlighted or explained.
Recommendations
  • Provide Linux-specific configuration and compliance examples, such as using Ansible, Chef, or native Linux tools alongside PowerShell DSC.
  • Introduce or reference Linux equivalents to Windows Admin Center for remote management, or clarify the parity of management experiences for Linux servers.
  • Ensure examples and instructions are given for both Windows and Linux, including role assignments, remote access setup, and agent configuration.
  • Balance the order of presentation so that Linux scenarios (e.g., SSH, sudoers management) are described with equal prominence and detail as Windows scenarios.
  • Explicitly mention limitations or differences in feature support between Windows and Linux to help administrators plan accordingly.
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 →
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 tools and patterns (e.g., Group Policy, Microsoft Configuration Manager, WSUS, BitLocker) are mentioned before or in more detail than their Linux equivalents. PowerShell is referenced as a primary automation method, with Linux alternatives (e.g., Ansible) mentioned but not elaborated. Some examples and guidance (such as Group Policy onboarding and update mechanisms) are Windows-centric, with less detail or missing examples for Linux. The onboarding credential section notes that interactive logons using a local web browser are 'Windows-only', but does not provide equivalent Linux guidance.
Recommendations
  • Provide Linux-specific onboarding examples, including interactive logon workflows and automation scripts using common Linux tools (e.g., shell scripts, Ansible playbooks).
  • Include detailed guidance for Linux update orchestration, such as using cron jobs, unattended-upgrades, or configuration management tools (e.g., Puppet, Chef) for agent updates.
  • Offer parity in secret protection strategies for Linux, such as using file permissions, encryption tools (e.g., GPG), or systemd service credentials.
  • Expand on Linux disk encryption options (e.g., dm-crypt, LUKS) with step-by-step instructions, similar to BitLocker references for Windows.
  • Balance references to Windows and Linux tools throughout the documentation, ensuring that Linux administrators have clear, actionable guidance equivalent to Windows users.
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 →
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 referencing PowerShell Desired State Configuration as the sole example for guest configuration policies, using Windows account names and SIDs before mentioning Linux equivalents, and providing extension allowlist examples that only reference Windows extensions. There are no Linux-specific configuration or extension examples, and the documentation does not mention Linux equivalents for PowerShell DSC or monitoring/defender extensions.
Recommendations
  • Include Linux-specific examples for guest configuration policies, such as using Ansible or native Linux configuration management tools.
  • Provide extension allowlist examples for common Linux monitoring and security extensions (e.g., AzureMonitorLinuxAgent, MDE.Linux).
  • Mention Linux account and service management patterns before or alongside Windows equivalents.
  • Clarify whether guest configuration policies can be authored and enforced using Linux-native tools, and provide guidance for Linux administrators.
  • Ensure that all CLI examples and extension references include both Windows and Linux variants where applicable.
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 →
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 by predominantly referencing PowerShell modules (Az.Ssh, Az.Ssh.ArcProxy), providing only PowerShell commands for module management, and mentioning Azure PowerShell before Azure CLI in several troubleshooting steps. There are no explicit Linux shell (bash) examples for installing or updating modules, and the troubleshooting guidance assumes familiarity with Windows/PowerShell tooling. Linux-specific troubleshooting steps and parity in examples are missing, especially for module installation and updates.
Recommendations
  • Provide equivalent Linux (bash) commands for installing and updating Az.Ssh and Az.Ssh.ArcProxy modules, such as instructions for using pip, apt, or manual download if available.
  • Include troubleshooting steps and examples for common Linux SSH client issues, such as permissions, path configuration, and binary installation.
  • Ensure that CLI examples (Azure CLI) are presented before or alongside PowerShell examples, and clarify cross-platform applicability.
  • Reference Linux-native tools and patterns (e.g., ~/.ssh directory, chmod for permissions) where relevant, not just Windows/PowerShell equivalents.
  • Explicitly state which steps or commands are platform-specific, and provide alternative instructions for both Windows and Linux environments.
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 →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example ⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation is exclusively focused on Windows Server 2012 and 2012 R2, with all troubleshooting steps, examples, and commands tailored to Windows environments. Only Windows tools (certutil, PowerShell, Windows Update Manager) are mentioned, and there are no Linux equivalents or cross-platform guidance. The documentation assumes the reader is working with Windows, omitting any mention of Linux or non-Windows Arc-enabled servers.
Recommendations
  • Clarify at the beginning that the guidance is specific to Windows Server 2012/2012 R2, and note whether Linux Arc-enabled servers are supported or not for ESU delivery.
  • If Linux Arc-enabled servers can participate in similar workflows, provide equivalent troubleshooting steps, commands, and examples for Linux (e.g., using OpenSSL or update mechanisms).
  • For certificate installation, include Linux methods (such as using 'update-ca-certificates' or 'openssl') if applicable.
  • Where PowerShell or Windows command prompt is used, offer Bash or shell equivalents for Linux.
  • Explicitly state any platform limitations or differences in ESU delivery and troubleshooting between Windows and Linux Arc-enabled servers.
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 →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation provides both Windows (PowerShell) and Linux (Bash/Azure CLI) examples, but there is a noticeable Windows bias. Windows-specific tools and patterns (PowerShell, Windows Server notes, OpenSSH for Windows links) are mentioned frequently and sometimes before Linux equivalents. Some sections, such as prerequisites and next steps, highlight Windows-specific instructions or resources more prominently. There is limited coverage of Linux-specific troubleshooting, and some advanced Linux scenarios (e.g., SELinux, systemd service management) are not addressed.
Recommendations
  • Ensure Linux examples and instructions are presented with equal prominence and detail as Windows examples.
  • Add Linux-specific troubleshooting and advanced configuration guidance (e.g., SELinux, systemd, package manager variations).
  • Include links to Linux OpenSSH documentation in the 'Next steps' section alongside Windows resources.
  • Avoid presenting Windows instructions or links before Linux equivalents; consider parallel presentation or tabs.
  • Expand Linux prerequisites to cover common distributions and edge cases (e.g., firewall configuration, SSH key management).
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 →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation page shows mild Windows bias. Windows examples and tools (such as PowerShell, Windows environment variables, and Windows file paths) are presented before or in more detail than their Linux equivalents. Windows-specific troubleshooting steps and references to Windows tools (e.g., PowerShell version requirements, %TEMP% and %ProgramData% paths) appear more frequently and are sometimes described before Linux alternatives. Linux examples are present but sometimes less detailed, and some troubleshooting steps reference Windows tools or patterns without Linux parity.
Recommendations
  • Ensure Linux examples are provided for every Windows example, with equal detail and visibility.
  • Present Windows and Linux instructions side-by-side or in parallel sections to avoid Windows-first ordering.
  • Reference Linux file paths and tools (e.g., /var/log, /tmp, sudo) wherever Windows paths/tools are mentioned.
  • Include Linux-specific troubleshooting steps (e.g., checking systemd service status, log file locations) alongside Windows steps.
  • Avoid referencing PowerShell or Windows environment variables without providing equivalent Linux commands or environment variable usage.
  • Explicitly mention Linux prerequisites and error remediation steps (e.g., package manager commands, permission troubleshooting) where Windows steps are given.
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 →
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 workflows. No Linux-specific troubleshooting examples or recommendations are provided, and Windows tools are presented first and exclusively in the contingency section.
Recommendations
  • Include Linux-specific local management tools (e.g., Cockpit, Ansible, SSH, systemd utilities) as alternatives to Windows Admin Center and Configuration Manager.
  • Provide troubleshooting examples or workflows for Linux servers in disconnected scenarios, such as checking agent status via systemctl or viewing logs.
  • Ensure parity by listing both Windows and Linux options side-by-side when discussing contingency management tools.
  • Explicitly mention that Azure Arc-enabled servers can be Linux or Windows, and tailor troubleshooting steps accordingly.
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 →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation page focuses exclusively on troubleshooting TLS configuration issues for Windows, providing only Windows-specific instructions and examples (PowerShell, Group Policy, Registry edits). There are no Linux equivalents or guidance for Linux-based Azure Arc-enabled servers, and all examples use Windows tools and patterns.
Recommendations
  • Add a dedicated section for troubleshooting TLS/cipher suite configuration on Linux servers, including relevant commands (e.g., using openssl, update-crypto-policy, or editing /etc/ssl/openssl.cnf).
  • Provide Linux command-line examples for listing enabled cipher suites (e.g., openssl ciphers -v).
  • Include instructions for enabling/disabling cipher suites on common Linux distributions (Ubuntu, RHEL, etc.).
  • Mention Linux-specific configuration files and tools alongside Windows methods.
  • Ensure parity in troubleshooting steps for both Windows and Linux environments.
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 →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation page shows a Windows bias by providing explicit instructions and examples for Windows event logs (e.g., referencing the 'Event' table as containing Windows event log data) without equivalent Linux log examples. The mention of the 'Event' table is Windows-specific, and there is no guidance for viewing or querying Linux logs (such as syslog or other Linux event sources). Additionally, Windows terminology and tools are referenced before Linux equivalents, and Linux-specific details are omitted.
Recommendations
  • Include explicit examples and instructions for viewing and querying Linux logs (e.g., syslog, auth.log) in Log Analytics.
  • Clarify which tables are relevant for Linux machines and provide sample queries for those tables.
  • Balance references to Windows and Linux by mentioning both platforms equally when discussing features or data sources.
  • Add screenshots and walkthroughs for Linux machines, not just Windows.
  • Where Windows-specific tools or terminology are used, provide Linux equivalents (e.g., mention syslog alongside Windows event log).
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 →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ windows_heavy_detail
Summary
The documentation provides a reasonably balanced overview for both Windows and Linux, but there is a noticeable Windows bias in several areas. 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 (e.g., MSI, NT SERVICE accounts, Group Policy) are described in detail, while Linux equivalents are covered more briefly and generically. The Linux section lacks comparable depth regarding service accounts, security groups, and troubleshooting tips. Additionally, some extension CPU limits are higher for Windows, and Windows extensions are listed first in some tables.
Recommendations
  • Present Windows and Linux installation details in parallel sections, or alternate which OS is described first.
  • Provide equivalent depth for Linux, including details about service accounts, security groups, and troubleshooting steps.
  • Include Linux-specific configuration tips (e.g., SELinux/AppArmor, systemd unit files, package manager commands) where relevant.
  • Ensure extension tables list Linux and Windows extensions in a neutral order or group by function rather than OS.
  • Add more Linux-focused troubleshooting guidance and references to common Linux administration patterns.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/system-center-virtual-machine-manager/create-custom-roles.md ...-center-virtual-machine-manager/create-custom-roles.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by focusing exclusively on Azure Arc-enabled SCVMM, a Windows-centric virtualization management solution, and by referencing tools and workflows (SCVMM, Azure portal, PowerShell) that are primarily used in Windows environments. There are no examples, references, or guidance for Linux-based equivalents or scenarios, nor is there mention of Linux management tools or cross-platform considerations.
Recommendations
  • Include examples or references for managing custom roles in environments that use Linux-based virtualization solutions (e.g., Azure Arc-enabled VMware or native Linux hosts).
  • Provide parity in documentation by mentioning Linux management tools (such as Azure CLI on Linux, or REST API usage from Linux shells) and showing command-line examples for both Windows (PowerShell) and Linux (Bash).
  • Clarify the scope of the documentation and explicitly state if the instructions are only applicable to Windows-based SCVMM environments, and provide links or guidance for Linux users where relevant.
  • Add a section comparing SCVMM with Linux-based alternatives and how Azure Arc custom roles apply or differ in those contexts.
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 →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation is heavily focused on Azure Arc-enabled SCVMM, which is a Windows-centric technology (System Center Virtual Machine Manager). All role definitions and actions are tailored to SCVMM resources, with no mention of Linux-based equivalents, cross-platform management, or Linux-specific tooling. There are no examples, references, or guidance for Linux environments, and the documentation assumes the use of Windows tools and patterns throughout.
Recommendations
  • Add context or links for users managing Linux-based environments with Azure Arc, such as Azure Arc for Linux servers.
  • Include examples or references to Linux management scenarios, even if only to clarify that SCVMM is Windows-only and suggest alternatives for Linux.
  • Explicitly state the Windows-centric nature of SCVMM and guide Linux users to relevant Azure Arc documentation.
  • Where possible, provide parity in documentation for Azure Arc features that apply to both Windows and Linux, or clarify feature limitations.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/system-center-virtual-machine-manager/create-virtual-machine.md ...nter-virtual-machine-manager/create-virtual-machine.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation is heavily focused on System Center Virtual Machine Manager (SCVMM), a Windows-only virtualization management tool. All examples and instructions are tailored to SCVMM environments, with no mention of Linux-based virtualization platforms (e.g., KVM, libvirt, oVirt) or Linux-specific workflows. The prerequisites and steps assume Windows-centric infrastructure and roles, and there are no Linux equivalents or cross-platform alternatives provided.
Recommendations
  • Include references or links to equivalent Linux-based virtualization management solutions (such as KVM, libvirt, or oVirt) and how they can be integrated with Azure Arc, if supported.
  • Provide examples or documentation for creating virtual machines using Azure Arc in Linux-based environments, or clarify the scope if only Windows/SCVMM is supported.
  • Add a section that discusses cross-platform support and explicitly states any limitations or platform-specific requirements.
  • If PowerShell or Windows tools are mentioned in reference sections, ensure parity by including Azure CLI, Bash, or other Linux-friendly methods where applicable.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/system-center-virtual-machine-manager/overview.md ...-arc/system-center-virtual-machine-manager/overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation page for Azure Arc-enabled System Center Virtual Machine Manager exhibits a Windows-centric bias. It primarily references Windows technologies (SCVMM, Windows Server, SQL Server), mentions PowerShell and Windows registry before Linux equivalents, and provides links and examples that focus on Windows management scenarios. Linux is mentioned as supported in some features, but there are no Linux-specific examples, tools, or guidance, and Windows tools/patterns are consistently referenced first or exclusively.
Recommendations
  • Include explicit Linux management examples and scenarios, such as onboarding Linux VMs managed by SCVMM, with step-by-step instructions.
  • Provide Linux-specific automation examples (e.g., Bash scripts, Linux CLI usage) alongside PowerShell examples.
  • Reference Linux tools and configuration patterns (e.g., systemd, Linux daemons) with equal prominence to Windows registry and services.
  • Add links to Linux-focused documentation for Azure Arc, VM extensions, and monitoring.
  • Ensure that mentions of supported OSes and features list Linux and Windows together, or alternate their order.
  • Clarify how Azure Arc-enabled SCVMM supports Linux VMs, including any limitations or differences compared to Windows VMs.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/system-center-virtual-machine-manager/deliver-esus-for-system-center-virtual-machine-manager-vms.md ...ver-esus-for-system-center-virtual-machine-manager-vms.md
High Priority View Details →
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 environments, specifically Windows Server 2012/2012 R2 VMs managed by SCVMM. All examples, prerequisites, and workflows are tailored exclusively to Windows, with no mention of Linux VMs, Linux management tools, or cross-platform scenarios. Patch management solutions referenced are primarily Microsoft/Windows-centric (WSUS, Microsoft Updates, Endpoint Configuration Manager), and there are no Linux equivalents or instructions for Linux VMs. The documentation assumes a Windows-only audience and does not provide parity for Linux users.
Recommendations
  • Add explicit statements clarifying whether Linux VMs are supported or not in this workflow.
  • If Linux VMs can be managed via Azure Arc-enabled SCVMM, provide equivalent instructions and examples for Linux environments.
  • Include references to Linux patch management solutions (e.g., apt, yum, dnf, zypper, or third-party tools like Landscape, Spacewalk, etc.) where appropriate.
  • If the ESU program is Windows-only, state this clearly at the beginning to avoid confusion for cross-platform administrators.
  • Consider adding a section comparing Windows and Linux management scenarios in Azure Arc-enabled SCVMM, even if only to clarify limitations.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/system-center-virtual-machine-manager/quickstart-connect-system-center-virtual-machine-manager-to-arc.md ...t-connect-system-center-virtual-machine-manager-to-arc.md
High Priority View Details →
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 Windows bias by prioritizing Windows-specific instructions, tools, and troubleshooting steps. Windows prerequisites (such as installing tar.exe and OpenSSH via Windows-specific methods) are detailed, while Linux equivalents are not explained. PowerShell is the primary scripting language, with Bash provided as a secondary option. Windows instructions and retry commands are presented before Linux, and Windows tools (Set-ExecutionPolicy, WinRM ports, copying binaries from Windows 11/Server) are referenced without Linux alternatives. Performance warnings for Linux are included, but not substantiated or explained.
Recommendations
  • Provide equal detail for Linux prerequisites, including installation steps for required tools (tar, OpenSSH) on common Linux distributions.
  • List Linux instructions and examples alongside Windows, not after them, or use a neutral order.
  • Offer troubleshooting and retry commands for Linux with the same level of detail as Windows.
  • Avoid language that discourages Linux usage (e.g., vague performance warnings) unless substantiated; provide guidance for optimizing Linux deployments.
  • Reference Linux-native tools and patterns (e.g., SSH, systemd, package managers) where appropriate.
  • Ensure all steps (such as copying files, configuring permissions, network setup) have Linux equivalents documented.
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 →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation page demonstrates a Windows bias by exclusively referencing System Center Virtual Machine Manager (SCVMM), a Windows-only tool, and providing instructions and agent management steps only for Windows environments. All examples and links (such as agent uninstall/disconnect) use Windows tabs or terminology, with no mention of Linux equivalents or cross-platform considerations. There are no Linux-specific instructions, examples, or references to Linux management tools.
Recommendations
  • Include instructions for environments where Linux VMs are managed via Arc, if supported.
  • Provide agent management steps for Linux (e.g., how to disconnect and uninstall the Linux agent) alongside Windows steps.
  • Clarify whether the process applies only to Windows-based SCVMM environments or if there are alternatives for Linux-based infrastructures.
  • Add examples or screenshots showing Linux VM management, if applicable.
  • Reference Linux documentation tabs or provide links to Linux agent management guides.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/system-center-virtual-machine-manager/remove-scvmm-from-azure-arc.md ...virtual-machine-manager/remove-scvmm-from-azure-arc.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation page exhibits a Windows bias by prioritizing Windows-specific instructions and tools. The deboarding script is only available for Windows/PowerShell, with no Linux equivalent or cross-platform alternative. Script execution and examples are exclusively PowerShell-based, and Windows instructions are presented before Linux ones. There is no guidance for Linux administrators on how to perform equivalent operations, especially for running the deboarding script or managing SCVMM resources from non-Windows environments.
Recommendations
  • Provide a cross-platform (Bash or Python) version of the deboarding script for Linux environments.
  • Include Linux CLI examples (e.g., Azure CLI in Bash) alongside PowerShell commands for agent disconnect and resource removal.
  • Clearly indicate parity of functionality for Linux users, or document any limitations.
  • Reorder sections to present Windows and Linux instructions in parallel tabs, rather than Windows-first.
  • Explicitly mention if certain operations are only supported on Windows, and suggest alternatives or workarounds for Linux users.
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 →
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 Windows bias by prioritizing Windows Server and SCVMM (a Windows-only tool) throughout. Windows-specific tools and patterns (WinRM, Windows Management Framework, OpenSSH for Windows, Windows Admin Center) are mentioned exclusively or before Linux equivalents. Linux support is referenced only as an alternative for agent installation, with no detailed Linux deployment examples or parity in troubleshooting guidance. The workstation section discourages Linux usage by warning of performance issues, without offering mitigation or best practices for Linux users.
Recommendations
  • Provide explicit Linux-based deployment examples and troubleshooting steps, especially for agent installation and resource bridge deployment.
  • Offer guidance or best practices for running helper scripts and deployments from Linux workstations, including performance optimization tips.
  • List Linux prerequisites and requirements with equal detail and prominence as Windows, including supported distributions and versions.
  • Include Linux equivalents for Windows tools (e.g., alternatives to WinRM, PowerShell, Windows Admin Center) where applicable, or clarify cross-platform support.
  • Avoid language that discourages Linux usage without actionable advice; instead, document known issues and recommended solutions for Linux environments.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/system-center-virtual-machine-manager/whats-new.md ...arc/system-center-virtual-machine-manager/whats-new.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation page for Azure Arc-enabled SCVMM demonstrates a Windows bias. Most features and enhancements are described in the context of Windows-centric tools and environments, such as SCVMM (a Windows-only product), Windows Server Management, Azure PowerShell, and Windows-specific deployment methods (Group Policy, System Center Configuration Manager). Linux equivalents or examples are missing or mentioned only after Windows tools, if at all. There is little to no explicit guidance for Linux VM management or integration, and Windows tooling is prioritized in descriptions and feature rollouts.
Recommendations
  • Include explicit examples and guidance for managing Linux VMs within SCVMM and Azure Arc contexts.
  • Provide parity in tooling by mentioning Linux-native tools (e.g., shell scripts, cloud-init, Ansible) alongside Windows tools, and ensure they are given equal prominence.
  • Add documentation sections or examples for deploying and managing Azure Arc agents on Linux VMs, including troubleshooting and best practices.
  • Where PowerShell or Windows Server Management is referenced, also provide equivalent instructions for Linux environments (e.g., Bash, Python scripts, Ansible playbooks).
  • Clarify which features are Windows-only and which are cross-platform, to help administrators understand platform limitations and capabilities.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/system-center-virtual-machine-manager/troubleshoot-scvmm.md ...m-center-virtual-machine-manager/troubleshoot-scvmm.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_first
Summary
The documentation is heavily focused on troubleshooting errors related to SCVMM (System Center Virtual Machine Manager), a Windows-only tool. All error examples reference Windows-specific technologies (e.g., PSSession, SCVMMServer, PowerShell cmdlets) with no mention of Linux equivalents or cross-platform troubleshooting steps. There are no Linux or bash examples, and Windows tools and patterns are referenced exclusively and first throughout the page.
Recommendations
  • Add troubleshooting steps and examples for Linux-based resource bridge deployments if supported.
  • Include references to Linux tools (e.g., SSH, Linux management commands) where applicable.
  • Clarify in the introduction if the guidance is only relevant for Windows environments, and provide links to Linux-specific documentation if available.
  • Ensure parity in error documentation by listing Linux-specific errors and their troubleshooting guides if Azure Arc resource bridge supports Linux hosts.
  • Provide cross-platform troubleshooting patterns, or explicitly state platform limitations.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/system-center-virtual-machine-manager/upgrade-azure-arc-resource-bridge.md ...l-machine-manager/upgrade-azure-arc-resource-bridge.md
High Priority View Details →
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-based tools and workflows. All examples and instructions reference Windows concepts (VHDX, SCVMM server, library share), and there are no Linux-specific instructions, examples, or parity checks. The use of Azure CLI is cross-platform, but the context and prerequisites are exclusively Windows-centric.
Recommendations
  • Provide explicit instructions and examples for Linux environments, if supported (e.g., how to perform the upgrade from a Linux workstation).
  • Clarify whether the resource bridge upgrade process is supported on Linux, and if so, include Linux-specific prerequisites and file formats (e.g., VHD vs VHDX, mounting/sharing requirements).
  • Mention Linux equivalents for concepts like 'library share' and disk space requirements, or note if these steps are Windows-only.
  • Include troubleshooting steps and notes for Linux users, or explicitly state if the process is not supported outside Windows.
  • Ensure that cross-platform compatibility of Azure CLI commands is highlighted, and provide sample commands run from Linux shells (bash/zsh) as well as PowerShell.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/vmware-vsphere/deliver-extended-security-updates-for-vmware-vms-through-arc.md ...r-extended-security-updates-for-vmware-vms-through-arc.md
High Priority View Details →
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 VMs, with all examples, terminology, and tooling centered around Windows environments. There are no Linux VM examples, and all patching and management solutions referenced (Azure Update Manager, WSUS, Microsoft Updates, Endpoint Configuration Manager) are Windows-centric. The documentation does not mention Linux equivalents or provide guidance for Linux VMs.
Recommendations
  • Include examples and guidance for managing ESUs or equivalent security updates for Linux VMs managed by Azure Arc-enabled VMware vSphere.
  • Reference Linux-compatible patch management solutions (such as Azure Update Manager for Linux, or third-party Linux patching tools) alongside Windows tools.
  • Clarify whether the ESU process is exclusive to Windows Server VMs or if similar processes exist for Linux VMs, and provide links or documentation for Linux scenarios if applicable.
  • Add screenshots and walkthroughs for Linux VM management in Azure Arc where relevant.
  • Explicitly state in the prerequisites and overview sections whether Linux VMs are supported or excluded, to avoid confusion for cross-platform administrators.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/vmware-vsphere/quick-start-connect-vcenter-to-arc-using-script.md ...ere/quick-start-connect-vcenter-to-arc-using-script.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation page demonstrates a moderate Windows bias. Windows and PowerShell are consistently mentioned before Linux and Bash, with Windows instructions and notes appearing first in sections such as 'Run the script' and 'Retry command'. There are Windows-specific troubleshooting notes (e.g., PowerShell ISE caveat) and commands (Set-ExecutionPolicy) that have no Linux equivalent, and the overall flow assumes familiarity with Windows tools and patterns. Linux instructions are present but secondary.
Recommendations
  • Alternate the order of Windows and Linux instructions in each section, or present them side-by-side for parity.
  • Add Linux-specific troubleshooting notes (e.g., common Bash script issues, permission requirements, shell compatibility).
  • Provide equivalent details for Linux where Windows-specific commands are given (e.g., mention chmod +x for script execution on Linux).
  • Ensure screenshots and UI references are platform-neutral or include Linux-specific visuals where relevant.
  • Review terminology to avoid Windows-centric language (e.g., refer to 'terminal' instead of 'PowerShell window' where possible).
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/vmware-vsphere/recover-from-resource-bridge-deletion.md ...mware-vsphere/recover-from-resource-bridge-deletion.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ missing_linux_example ⚠️ windows_tools ⚠️ windows_first
Summary
The documentation page demonstrates a Windows bias by exclusively providing PowerShell script examples and instructions, with no mention of Linux shell equivalents or cross-platform alternatives. The onboarding and recovery steps rely on PowerShell (.ps1) scripts and Windows-centric tooling, and there is no guidance for users operating from Linux or macOS environments. The documentation assumes the use of Windows tools and patterns throughout, without addressing Linux parity.
Recommendations
  • Provide equivalent onboarding and recovery instructions using Bash or shell scripts for Linux/macOS users.
  • Explicitly state platform requirements and offer cross-platform alternatives where possible.
  • Include examples of running the onboarding script from Linux (e.g., using Azure CLI, Bash, or Python).
  • Document any prerequisites or limitations for non-Windows environments.
  • Ensure that all steps (such as editing scripts, running commands) are described for both Windows and Linux platforms.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/vmware-vsphere/overview.md ...lob/main/articles/azure-arc/vmware-vsphere/overview.md
High Priority View Details →
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 prioritizing Windows Server management features, referencing Windows-specific tools and patterns (such as PowerShell and Windows registry), and providing links and examples that focus on Windows before Linux. Linux support is mentioned but often as a secondary consideration, and there are no explicit Linux-centric examples or guidance. Some features are described in a Windows-centric way (e.g., registry, Windows services) without Linux equivalents or parity in detail.
Recommendations
  • Ensure that all feature descriptions and examples explicitly mention Linux support and provide Linux-specific guidance where applicable.
  • When referencing automation tools (e.g., Azure Automation runbooks), provide balanced examples for both PowerShell (Windows) and Bash/Python (Linux).
  • In lists and feature descriptions, avoid placing Windows features or tools before Linux equivalents unless there is a technical reason; alternate order or present both together.
  • Expand documentation and links to include Linux-focused management scenarios, such as managing Linux daemons, configuration files, and package updates.
  • Include Linux-specific links and resources (e.g., Linux server management overview, Linux security update guidance) alongside Windows-focused links.
  • Where Windows registry or services are mentioned, also mention Linux equivalents (e.g., systemd services, configuration files) to provide parity.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/vmware-vsphere/remove-vcenter-from-arc-vmware.md ...e-arc/vmware-vsphere/remove-vcenter-from-arc-vmware.md
High Priority View Details →
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/Powershell instructions are presented first and in greater detail, especially for running the deboarding script, with no equivalent Linux instructions or script usage examples. The script is described as a PowerShell script, and guidance is focused on running it in Windows environments, including troubleshooting notes specific to Windows tools (PowerShell ISE). Linux agent removal is covered, but there are no Linux-specific instructions for running the deboarding script or managing the process from a Linux workstation.
Recommendations
  • Provide explicit instructions and examples for running the deboarding script from a Linux or macOS environment, including prerequisites and command syntax.
  • Clarify whether the deboarding script can be run cross-platform (e.g., via PowerShell Core on Linux/macOS) and provide troubleshooting notes for non-Windows platforms.
  • Present Windows and Linux instructions in parallel or side-by-side, rather than Windows-first, to ensure parity and equal visibility.
  • Include notes on Linux equivalents for any Windows-specific tools or steps (e.g., alternatives to Control Panel for agent removal, or using bash/zsh terminals for script execution).
  • If the script is Windows-only, explicitly state this and provide alternative manual steps for Linux users.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/vmware-vsphere/support-matrix-for-arc-enabled-vmware-vsphere.md ...phere/support-matrix-for-arc-enabled-vmware-vsphere.md
High Priority View Details →
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 listing Windows requirements (such as .NET Framework and PowerShell) before Linux equivalents, mentioning Windows-specific tools (PowerShell, Windows Management Framework) and providing download links for them, while Linux requirements are listed more generically and without equivalent detail or links. There are no Linux-specific usage examples or installation instructions, and the helper script referenced in 'Next steps' is not clarified as cross-platform or Linux-compatible.
Recommendations
  • Provide Linux-specific installation instructions and examples, including supported distributions and package managers.
  • List Linux requirements with equal detail and provide download or installation links for required tools (e.g., systemd, wget).
  • Clarify whether the onboarding/helper script is cross-platform and provide Linux usage examples if applicable.
  • Avoid listing Windows requirements before Linux ones; present both platforms in parallel or grouped sections.
  • Include troubleshooting steps or notes 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/workload-orchestration/bulk-deployment.md ...es/azure-arc/workload-orchestration/bulk-deployment.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example ⚠️ windows_first
Summary
The documentation page demonstrates a Windows bias by exclusively using PowerShell syntax for CLI commands, referencing only PowerShell scripts (e.g., bulk_deployment.ps1, workflow-delete.ps1), and omitting any Linux shell (bash/sh) equivalents or examples. There is no mention of Linux-specific usage patterns, nor are cross-platform considerations (such as .sh scripts or bash command syntax) addressed. Windows tools and patterns are presented first and exclusively, with no Linux parity.
Recommendations
  • Provide bash or shell script equivalents for all referenced PowerShell scripts (e.g., bulk_deployment.sh, workflow-delete.sh), and link to them.
  • Show CLI command examples in both PowerShell and bash syntax, using tabbed or side-by-side formatting.
  • Explicitly mention cross-platform compatibility for the Azure CLI commands, including any OS-specific considerations.
  • Add instructions for running scripts and commands on Linux/macOS, including file path conventions and prerequisites.
  • Clarify that JSON and YAML configuration files are OS-agnostic, and provide sample commands for editing/viewing them on Linux.
  • If any features are Windows-only, clearly state this and provide alternatives or workarounds for Linux users.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/workload-orchestration/diagnose-problems.md .../azure-arc/workload-orchestration/diagnose-problems.md
High Priority View Details →
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 strong Windows bias. All command-line examples use PowerShell syntax and conventions (e.g., backticks for line continuation, .ps1 scripts), with no Bash or Linux shell equivalents provided. File paths in JSON and examples use Windows-style (C:\, E:\) exclusively. There is no mention of Linux-specific tools or workflows, and instructions for running scripts or configuring resources assume a Windows environment. This may hinder Linux users from following the documentation effectively.
Recommendations
  • Provide equivalent Bash/Linux shell commands for all PowerShell examples, using standard Bash syntax and line continuation.
  • Include Linux-style file paths in examples and templates (e.g., /home/user/file.yaml) alongside Windows paths.
  • Explicitly mention cross-platform compatibility for scripts and tools, or provide separate instructions for Linux and macOS users.
  • Clarify any prerequisites or dependencies that are Windows-specific, and offer alternatives for Linux environments.
  • Where PowerShell scripts are referenced (.ps1), provide Bash script alternatives or note how to adapt the logic for Linux.
  • Add a section or callouts for Linux users, highlighting any differences in setup, troubleshooting, or file management.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/workload-orchestration/initial-setup-environment.md ...rc/workload-orchestration/initial-setup-environment.md
High Priority View Details →
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-specific tools and patterns are prioritized or exclusively mentioned, such as using 'winget' for installing kubectl (which is only available on Windows), and examples consistently use Windows-style paths (e.g., C:\path\to\archive.zip). Bash and PowerShell tabs are provided, but Bash examples often contain Windows-centric commands or syntax. There are no explicit Linux installation instructions for kubectl, nor are Linux-native tools (like unzip or tar) mentioned for extracting ZIP files. The documentation assumes a Windows environment for file paths and installation methods, and does not provide parity for Linux users in key setup steps.
Recommendations
  • Provide Linux-native installation instructions for kubectl (e.g., using curl or apt/yum/zypper).
  • Include Linux file extraction commands (e.g., unzip, tar) alongside Expand-Archive/winget.
  • Use cross-platform or Linux-style file paths in Bash examples (e.g., /home/user/archive.zip).
  • Clearly indicate which commands are Windows-only and offer Linux alternatives in all relevant steps.
  • Add a dedicated Linux prerequisites section, including package manager commands for required tools.
  • Review all examples to ensure they work as written on Linux and macOS, not just Windows.
  • Avoid assuming the use of Windows tools (winget, Expand-Archive) in Bash sections; use platform-appropriate tools.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/workload-orchestration/troubleshooting.md ...es/azure-arc/workload-orchestration/troubleshooting.md
High Priority View Details →
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 strong Windows bias, particularly in the troubleshooting sections for workload orchestration. Most command-line examples are provided exclusively in PowerShell, with Windows-specific syntax and patterns (e.g., use of `$` for variables, ConvertTo-Json, Out-File, [Convert]::ToBase64String). Linux/Bash equivalents are missing for nearly all steps except the 'service groups' section, where both Bash and PowerShell tabs are provided. Windows tools and idioms (such as file encoding notes about 'UTF-8 with BOM', PowerShell piping, and variable assignment) are used throughout, while Linux-native approaches (e.g., shell scripting, jq, sed, cat, base64) are absent.
Recommendations
  • Provide Bash/Linux shell equivalents for all PowerShell command examples, especially in troubleshooting steps for staging, authentication, network, and image issues.
  • Include Linux-native tools and idioms (e.g., use of export for environment variables, base64 for encoding, jq for JSON manipulation, cat/sed for file operations) alongside PowerShell commands.
  • Add notes about file encoding and editing that are relevant to Linux users (e.g., using iconv or nano/vim for file encoding changes).
  • Ensure that examples are presented in parallel tabs (PowerShell and Bash) for all command-line instructions, not just in the 'service groups' section.
  • Review variable naming and assignment to use syntax appropriate for both platforms (e.g., $var in PowerShell, $var or VAR=value in Bash).
  • Explicitly mention any platform-specific differences or requirements in troubleshooting steps.
GitHub Create Pull Request
Azure Portal https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-portal/quick-create-template.md ...ob/main/articles/azure-portal/quick-create-template.md
High Priority View Details →
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 exclusively providing PowerShell commands for VM creation, referencing Windows-specific username/password requirements, and naming the resource group 'SimpleWinVmResourceGroup'. There are no examples or instructions for Linux users (e.g., Bash in Cloud Shell, Azure CLI commands for Linux VMs), and Windows tools and patterns are presented first and exclusively.
Recommendations
  • Add parallel instructions and examples for creating a Linux VM, including Azure CLI and Bash commands.
  • Rename resource groups and VM names to be OS-neutral (e.g., 'SimpleVmResourceGroup').
  • Include links to both Windows and Linux VM username/password requirements.
  • Show how to use Bash in Cloud Shell and provide equivalent commands for Linux users.
  • Present both PowerShell and CLI/Bash options side-by-side, or clearly indicate OS-specific sections.
  • Explicitly mention that the dashboard can visualize both Windows and Linux VM performance.
GitHub Create Pull Request
Azure Portal https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-portal/quick-create-bicep.md .../blob/main/articles/azure-portal/quick-create-bicep.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation page exhibits Windows bias by exclusively deploying a Windows virtual machine (SimpleWinVM), referencing Windows-specific username and password requirements, and linking only to Windows VM documentation. There are no Linux VM examples or references, and the deployment scripts do not demonstrate how to use a Linux VM. The resource group and VM naming conventions also reinforce a Windows-centric approach.
Recommendations
  • Provide parallel examples for deploying a Linux VM, including a Linux-focused ARM template and Bicep file.
  • Include links to Linux VM documentation for username/password requirements and best practices.
  • Use neutral resource names (e.g., 'SimpleVmResourceGroup', 'SimpleVM') instead of Windows-specific names.
  • Add a tabbed example for Linux VM deployment in both Azure CLI and PowerShell sections.
  • Clarify that the dashboard can visualize both Windows and Linux VMs, and show how to adapt the Bicep file for Linux scenarios.
GitHub Create Pull Request
Azure Portal https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-portal/supportability/how-to-create-azure-support-request.md .../supportability/how-to-create-azure-support-request.md
High Priority View Details →
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 in several ways. In the 'Advanced diagnostic information logs' and 'Memory dump collection' sections, Windows-specific terminology and tools (e.g., kernel-mode dump, Hyper-V save state) are referenced exclusively, with no mention of Linux VM equivalents or diagnostic procedures. The examples and instructions for memory dump collection focus solely on Windows, omitting guidance for Linux-based Azure VMs. Additionally, the order and selection of referenced diagnostic logs and procedures prioritize Windows environments, with Linux support not addressed.
Recommendations
  • Add explicit instructions and examples for collecting diagnostic information and memory dumps from Linux-based Azure VMs, including references to Linux tools (e.g., kdump, crash, syslog).
  • Include links to troubleshooting guides for Linux VM support cases alongside Windows references.
  • Ensure that any mention of VM diagnostics, logs, or support procedures covers both Windows and Linux environments, or clearly states platform-specific differences.
  • Review and update the order of examples and references so that Linux and Windows are presented with equal prominence.
GitHub Create Pull Request
Container Registry https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/container-registry-authentication.md ...ontainer-registry/container-registry-authentication.md
High Priority View Details →
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 Windows bias by consistently presenting Azure PowerShell examples alongside or immediately after Azure CLI examples, with no explicit Bash or Linux shell examples for registry management tasks. Windows-specific tooling (PowerShell) is given parity with Azure CLI, but Linux-native tools and workflows are only briefly mentioned (e.g., podman) and not demonstrated in detail. The guidance and examples for authentication and registry management focus on Azure CLI and PowerShell, with no Linux shell scripting or non-Windows environment walkthroughs. The 'Next steps' section also only links to Azure CLI and PowerShell guides, omitting Linux/Bash or cross-platform alternatives.
Recommendations
  • Add explicit Bash/Linux shell examples for authentication and registry management tasks, especially for common workflows like service principal login and admin account management.
  • Provide parity for Linux-native container tools (e.g., podman, skopeo) in examples, not just mention them in passing.
  • Include a 'Linux/Bash' tab alongside 'Azure CLI' and 'Azure PowerShell' for all code examples, showing commands as run in a typical Linux environment.
  • In the 'Next steps' section, link to guides for Linux/Bash workflows and container management using Linux-native tools.
  • Clarify that Azure CLI is cross-platform and demonstrate its use in Linux environments, including installation and configuration steps for Linux.
  • Where PowerShell is mentioned, note its availability on Linux, but do not assume it is the default shell for Linux users.
GitHub Create Pull Request
Container Registry https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/container-registry-auth-service-principal.md ...-registry/container-registry-auth-service-principal.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation references both Azure CLI and Azure PowerShell sample scripts, but lists PowerShell examples and links alongside CLI examples, potentially giving Windows tools parity or priority. There is no explicit mention of Linux-specific shell scripting or environment setup, and examples use environment variables in a way that is compatible with both Bash and PowerShell, but do not clarify platform differences. No Linux-specific authentication patterns or troubleshooting are discussed, and the sample script links do not highlight Linux-first workflows.
Recommendations
  • Add explicit Linux/Bash shell script examples and clarify platform differences in environment variable usage.
  • Provide guidance for Linux users on installing and using Azure CLI, including authentication patterns specific to Linux environments.
  • Ensure that Linux tools (e.g., Bash, OpenSSL) are mentioned before or alongside Windows tools, and provide troubleshooting tips for Linux users.
  • Include links to Linux-focused sample repositories or documentation, and highlight Linux compatibility in all examples.
  • Add a section on using service principals in Linux CI/CD environments (e.g., GitHub Actions, Jenkins on Linux runners).
GitHub Create Pull Request
Container Registry https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/container-registry-authentication-managed-identity.md ...https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/container-registry-authentication-managed-identity.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all steps, but PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, which is more cross-platform. There is a notable emphasis on installing and using PowerShell on Ubuntu, which is not a typical Linux pattern. The documentation references Docker installation for macOS, Windows, and Linux equally, but the main walkthrough is focused on Ubuntu VMs. There are no explicit Linux shell-only examples (e.g., Bash scripts using REST APIs or SDKs), and PowerShell is presented as a first-class option for Linux users, which may not align with common Linux workflows.
Recommendations
  • Prioritize Azure CLI examples and make them the default or first-shown option, as CLI is more widely used on Linux.
  • Provide Bash shell script examples for key steps, especially authentication and Docker usage, without requiring PowerShell.
  • Clarify that PowerShell is optional on Linux, and suggest native Bash/CLI workflows for Linux users.
  • Add explicit guidance for Linux users who prefer not to install PowerShell, including alternatives using Azure CLI and REST APIs.
  • Consider including examples for other Linux distributions (not just Ubuntu), or generalize instructions where possible.
GitHub Create Pull Request
Container Registry https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/container-registry-get-started-docker-cli.md ...-registry/container-registry-get-started-docker-cli.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation page demonstrates a moderate Windows bias. While Docker CLI commands are platform-agnostic, Azure PowerShell examples are given equal prominence to Azure CLI, and Windows-centric tools (Visual Studio Code, Docker extension) are recommended. In several places, PowerShell is mentioned before or alongside CLI, but no Linux shell-specific examples (e.g., bash scripts) are provided. The use of 'Control+C' for stopping containers is a Windows-centric notation, and Visual Studio Code is promoted as a primary workflow tool, which is more common on Windows. There are no explicit Linux shell or macOS terminal examples, nor any mention of Linux-native tools or patterns.
Recommendations
  • Add explicit Linux shell (bash) examples for authentication and image management, especially for scripting scenarios.
  • Include macOS-specific notes where relevant (e.g., stopping containers, file paths).
  • Present Azure CLI (cross-platform) examples before PowerShell, and clarify CLI is recommended for Linux/macOS users.
  • Mention Linux-native editors (e.g., Vim, VS Code on Linux) and workflows alongside Visual Studio Code.
  • Use platform-neutral notation for keyboard shortcuts (e.g., 'press Ctrl+C or Cmd+C to stop the container').
  • Highlight Docker Desktop for Linux and provide links to Linux installation and troubleshooting guides.
  • Where PowerShell is referenced, clarify its availability on Linux and macOS, or provide alternative bash commands.
GitHub Create Pull Request
Container Registry https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/container-registry-get-started-portal.md ...iner-registry/container-registry-get-started-portal.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation provides sign-in instructions for Azure CLI and Azure PowerShell, with PowerShell being a Windows-centric tool. There are no explicit Linux shell (bash) examples for signing in, nor are Linux-specific patterns or tools mentioned in parity with Windows/PowerShell. The documentation references Docker installation for Mac, Windows, and Linux, but command-line examples for registry login and management are limited to Azure CLI and PowerShell, with no Linux shell or bash-specific guidance. The order of presentation also places PowerShell examples alongside CLI, potentially giving Windows tools equal or greater prominence than Linux equivalents.
Recommendations
  • Add explicit bash/Linux shell examples for registry login and management, especially for common scenarios (e.g., using az acr login from bash).
  • Clarify that Azure CLI commands work cross-platform and provide sample usage in bash or Linux terminal.
  • Consider presenting CLI (cross-platform) examples before PowerShell (Windows-centric) examples, or clearly label PowerShell as Windows-specific.
  • Include notes or sections for Linux users, highlighting any differences or additional steps required.
  • Ensure parity in troubleshooting and cleanup instructions for Linux environments (e.g., using az group delete from bash).
GitHub Create Pull Request
Container Registry https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/container-registry-get-started-bicep.md ...ainer-registry/container-registry-get-started-bicep.md
High Priority View Details →
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 referencing PowerShell and Visual Studio Code as primary tools, listing PowerShell deployment instructions before CLI, and omitting explicit Linux/macOS shell examples. The use of Windows-centric terminology and lack of parity in Linux-specific guidance may hinder accessibility for Linux users.
Recommendations
  • Add explicit Bash/Linux/macOS shell examples alongside PowerShell, especially for deployment and resource cleanup steps.
  • Present Azure CLI (which is cross-platform) instructions before PowerShell, or clarify that CLI commands work on all platforms.
  • Mention alternative editors (e.g., Vim, nano) for creating Bicep files, not just Visual Studio Code.
  • Include instructions for opening terminals on Linux/macOS (e.g., Terminal app, Ctrl+Alt+T) in addition to Windows shortcuts.
  • Ensure resource cleanup steps include CLI commands and clarify their cross-platform compatibility.
GitHub Create Pull Request
Container Registry https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/container-registry-health-error-reference.md ...-registry/container-registry-health-error-reference.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page shows evidence of Windows bias, particularly in the 'NOTARY_VERSION_ERROR' section, which provides explicit instructions for Windows users (e.g., using notary.exe, specifying the default Windows path) before mentioning Linux/macOS alternatives. There is a lack of parity in providing Linux-specific paths or commands, and several solution steps refer to adding executables to 'system variables' or 'system environment variables' without clarifying Linux equivalents (e.g., PATH modifications). No Linux-specific troubleshooting commands or examples are provided, and references to tools (Docker, Helm, Notary) are generic, but where details are given, Windows is prioritized.
Recommendations
  • Provide explicit Linux and macOS instructions alongside Windows steps, including default installation paths and commands for adding executables to PATH.
  • When mentioning system environment variables, clarify how to modify PATH on Linux/macOS (e.g., editing ~/.bashrc or ~/.profile).
  • In sections like 'NOTARY_VERSION_ERROR', list Linux/macOS instructions before or alongside Windows instructions, and specify download locations and installation steps for those platforms.
  • Include troubleshooting commands and examples for Linux (e.g., systemctl for restarting Docker daemon, checking permissions, etc.).
  • Ensure parity in examples and troubleshooting steps for all major platforms (Windows, Linux, macOS) to avoid implicit prioritization of Windows.
GitHub Create Pull Request
Container Registry https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/container-registry-manage-artifact.md ...ntainer-registry/container-registry-manage-artifact.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation provides both Linux/macOS and Windows examples for key ORAS commands, but Windows examples (using .cmd syntax and .\oras.exe) are consistently presented after Linux/macOS/WSL2 examples. There is a notable emphasis on Windows tooling, such as referencing Docker Desktop credential store (which is Windows-centric), and explicit Windows command syntax. However, Linux parity is generally maintained, with bash examples and clear instructions for Linux/WSL2/macOS users. There are no sections where only Windows examples are given, but the documentation does not mention Linux-specific credential stores or patterns, and Docker Desktop is referenced without alternatives for Linux.
Recommendations
  • Include Linux-specific credential store information (e.g., pass, gnome-keyring, or Docker's Linux credential helpers) when discussing authentication.
  • When referencing Docker Desktop, also mention Docker Engine for Linux and how credentials are managed on Linux systems.
  • Present command examples for Linux and Windows side-by-side, or clarify that the Linux/macOS/WSL2 example applies to most users, with Windows as an alternative.
  • Add notes or sections for common Linux troubleshooting or environment setup, such as permissions or package manager installation commands.
  • Ensure parity in tool recommendations (e.g., mention Linux-native signing tools if referencing Notation or similar Windows tools).
GitHub Create Pull Request
Container Registry https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/container-registry-import-images.md ...container-registry/container-registry-import-images.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation page provides examples exclusively for Azure CLI and Azure PowerShell, with no mention of Linux-specific shell environments or commands (e.g., bash, sh). PowerShell examples are given equal prominence to CLI, and Windows-specific images (such as 'windows/servercore:ltsc2019') are highlighted. There is no explicit guidance or examples for Linux users, nor are Linux-native tools or patterns referenced. The documentation assumes familiarity with PowerShell and Windows-centric workflows, which may disadvantage Linux users.
Recommendations
  • Add explicit Linux shell (bash/sh) usage examples, especially for Azure CLI commands, showing how to run them in typical Linux environments.
  • Clarify that Azure CLI commands are cross-platform and can be run on Linux, macOS, and Windows, and provide installation links for all platforms.
  • Include examples using Linux-native images (e.g., Ubuntu, Alpine) alongside Windows images to demonstrate parity.
  • Mention that Azure CLI can be used in Linux terminals and provide troubleshooting tips relevant to Linux environments (e.g., dealing with permissions, environment variables).
  • Reduce the emphasis on PowerShell by making CLI examples primary, or by providing bash script equivalents where appropriate.
  • Add a section or note for users working in Linux environments, highlighting any differences or considerations.
GitHub Create Pull Request
Copilot https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/copilot/ai-shell-overview.md ...t-docs/blob/main/articles/copilot/ai-shell-overview.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation page demonstrates a bias toward Windows and PowerShell environments. It repeatedly references PowerShell and the AIShell PowerShell module, with no mention of Bash, Linux, or cross-platform installation instructions. All examples and guidance focus on Azure CLI and PowerShell, omitting Linux-native shells and tools. The installation instructions specifically require a PowerShell module, and all documentation links point to PowerShell-centric resources.
Recommendations
  • Include explicit instructions and examples for using AI Shell with Bash or other Linux shells, not just PowerShell.
  • Provide installation steps for Linux and macOS environments, ensuring parity with Windows instructions.
  • Reference and link to cross-platform or Linux-specific documentation, not only PowerShell resources.
  • Show example workflows and troubleshooting steps using Bash or zsh, alongside PowerShell examples.
  • Clarify whether the AIShell module is available for non-Windows platforms, and if so, provide guidance for those users.
GitHub Create Pull Request
Copilot https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/copilot/capabilities.md ...gement-docs/blob/main/articles/copilot/capabilities.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation page demonstrates a moderate Windows bias. Script generation examples specifically mention PowerShell before Linux equivalents (Azure CLI, Terraform, Bicep), and troubleshooting scenarios reference Windows-centric tools (Power BI, Arc server extension) without explicit mention of Linux alternatives. The ordering and selection of examples tend to prioritize Windows-native tools and workflows, with Linux-specific tools and patterns either mentioned later or omitted.
Recommendations
  • Ensure Linux equivalents (e.g., Bash, shell scripting) are mentioned alongside PowerShell in script generation sections.
  • Provide troubleshooting examples that reference common Linux tools and scenarios (e.g., SSH, systemd, journalctl, Linux VM diagnostics).
  • When listing script generation capabilities, alternate or balance the order between Windows and Linux tools (e.g., mention Azure CLI and Bash scripts before or alongside PowerShell).
  • Explicitly state that Azure Copilot supports both Windows and Linux environments, and provide examples for both.
  • Include references to Linux-specific deployment and management workflows (e.g., Ansible, cloud-init) where relevant.
GitHub Create Pull Request
Copilot https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/copilot/optimization-agent.md ...-docs/blob/main/articles/copilot/optimization-agent.md
High Priority View Details →
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 explicitly mentioning PowerShell script generation for optimization tasks and listing PowerShell before Azure CLI. No Linux-specific examples or shell scripts (e.g., Bash) are provided, and the sample prompts focus on PowerShell and CLI without clarifying cross-platform usage or parity.
Recommendations
  • Include explicit Bash/Linux shell script examples alongside PowerShell and Azure CLI.
  • Clarify that Azure CLI is cross-platform and provide usage notes for Linux/macOS users.
  • Add sample prompts requesting Bash scripts for optimization tasks.
  • Ensure that references to script generation do not prioritize PowerShell over CLI or other cross-platform tools.
  • Mention Linux tools or workflows where relevant, and provide guidance for non-Windows environments.
GitHub Create Pull Request
Copilot https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/copilot/example-prompts.md ...ent-docs/blob/main/articles/copilot/example-prompts.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation page provides example prompts for Azure Copilot, with dedicated sections for both Azure CLI and PowerShell. However, PowerShell is highlighted as a primary scripting tool, which is traditionally associated with Windows environments. PowerShell examples are given equal prominence to Azure CLI, but there is no mention of Bash, Linux shell scripting, or Linux-specific tools. Additionally, the order of examples places PowerShell immediately after Azure CLI, reinforcing a Windows-centric workflow. There are no explicit Linux command-line or shell script examples, and no references to Linux-native management tools.
Recommendations
  • Add example prompts for Bash or Linux shell scripting to demonstrate parity with PowerShell.
  • Include references to Linux-native tools (such as SSH, scp, or systemctl) where relevant.
  • Alternate the order of CLI and PowerShell examples, or group them together under 'Scripting' to avoid implying a Windows-first approach.
  • Explicitly mention that Azure CLI is cross-platform and can be used on both Windows and Linux.
  • Provide prompts for common Linux administration tasks in Azure environments (e.g., managing Linux VMs, configuring SSH keys, using cloud-init).
GitHub Create Pull Request
Lighthouse https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/lighthouse/concepts/architecture.md ...blob/main/articles/lighthouse/concepts/architecture.md
High Priority View Details →
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 primarily referencing Azure PowerShell for resource creation and management tasks, mentioning PowerShell cmdlets before Azure CLI, and lacking explicit Linux or cross-platform examples. Windows-centric tools and patterns are referenced without equivalent Linux-focused guidance, which may disadvantage users on non-Windows platforms.
Recommendations
  • Provide Azure CLI examples alongside or before PowerShell examples, especially for resource creation and management tasks.
  • Explicitly mention that both Azure CLI and PowerShell are supported on Windows, Linux, and macOS, and provide installation links for each platform.
  • Include sample commands and workflows using Azure CLI to ensure Linux users have clear guidance.
  • Avoid referencing Windows-specific tools or patterns exclusively; ensure parity in documentation for all supported platforms.
  • Add notes or sections highlighting cross-platform compatibility and best practices for Linux users.
GitHub Create Pull Request
Lighthouse https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/lighthouse/how-to/monitor-at-scale.md ...ob/main/articles/lighthouse/how-to/monitor-at-scale.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example ⚠️ windows_first
Summary
The documentation page demonstrates a bias toward Windows environments by providing PowerShell-only examples for key tasks (such as registering resource providers), referencing Azure PowerShell as a primary automation method, and omitting equivalent instructions for Linux users (such as Bash/CLI or shell scripting). Windows tools and patterns are mentioned exclusively or before any Linux alternatives, and there is no mention of cross-platform command-line tools like Azure CLI or Bash scripts.
Recommendations
  • Provide equivalent Azure CLI (az) examples for all PowerShell commands, especially for resource provider registration and workspace creation.
  • Explicitly mention that automation can be performed from Linux/macOS environments using Azure CLI or REST APIs, not just PowerShell.
  • Include Bash or shell script examples alongside PowerShell where automation is discussed.
  • Reorder sections or examples so that cross-platform tools (Azure CLI, REST API) are presented before or alongside Windows-specific tools.
  • Add notes or tips for Linux users regarding prerequisites and environment setup for Azure automation.
GitHub Create Pull Request
Lighthouse https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/lighthouse/how-to/monitor-delegation-changes.md ...ticles/lighthouse/how-to/monitor-delegation-changes.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by providing detailed PowerShell scripts for querying delegation changes, referencing PowerShell first in code samples, and omitting equivalent Linux/bash examples for advanced scripting tasks. While Azure CLI is briefly mentioned for role assignment, all complex automation and querying is shown only in PowerShell, which is primarily a Windows tool. There are no bash, shell, or Python examples for Linux users, nor guidance for running these tasks natively on Linux.
Recommendations
  • Provide equivalent bash or shell script examples for querying the Tenant Activity Log using REST API calls, suitable for Linux environments.
  • Include Python sample scripts for automation, as Python is cross-platform and widely used on Linux.
  • When listing code samples, present Azure CLI and bash examples before or alongside PowerShell, rather than after.
  • Explicitly mention how Linux users can perform these tasks, including authentication and token acquisition, using native tools.
  • Clarify that PowerShell Core is cross-platform, but provide installation and usage notes for Linux if PowerShell scripts are retained.
  • Add guidance for running scripts in Azure Cloud Shell, which supports both bash and PowerShell, to emphasize platform neutrality.
GitHub Create Pull Request
Lighthouse https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/lighthouse/how-to/onboard-management-group.md ...articles/lighthouse/how-to/onboard-management-group.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation provides only a PowerShell example for assigning the policy, with no equivalent Azure CLI, Bash, or Linux-native instructions. The use of PowerShell as the sole automation example suggests a Windows-centric approach, and there is no mention of Linux tools or cross-platform alternatives for policy assignment.
Recommendations
  • Add Azure CLI examples for policy assignment, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Include Bash script samples for deploying the policy and parameters file.
  • Explicitly mention that PowerShell Core is available on Linux and macOS, if PowerShell must be used.
  • Provide guidance or links for Linux users on installing required tools and running the deployment commands.
  • Ensure that automation instructions (e.g., for Logic Apps) clarify platform independence and do not assume a Windows environment.
GitHub Create Pull Request
Lighthouse https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/lighthouse/how-to/onboard-customer.md ...ob/main/articles/lighthouse/how-to/onboard-customer.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation provides onboarding instructions for Azure Lighthouse with examples and tooling references for Azure Portal, Azure CLI, and Azure PowerShell. While Azure CLI is cross-platform, Azure PowerShell is typically associated with Windows environments, and its examples are given equal prominence. There is no mention of Linux-specific shell usage (e.g., Bash), nor are there any explicit Linux-oriented instructions or troubleshooting steps. The documentation does not reference Linux tools or patterns, and the order of presentation often places Azure PowerShell examples before or alongside CLI, which may reinforce a Windows-centric workflow. No explicit Linux shell examples (such as Bash scripts or usage in native Linux environments) are provided.
Recommendations
  • Add explicit Bash shell examples for template deployment and verification, demonstrating usage in native Linux environments.
  • Clarify that Azure CLI commands work identically on Linux, macOS, and Windows, and provide any platform-specific caveats if relevant.
  • Include troubleshooting steps or notes for common issues encountered on Linux (e.g., file permissions, path formats, environment variables).
  • Consider reordering examples to present Azure CLI (cross-platform) before Azure PowerShell (Windows-centric), or explicitly state platform parity.
  • Reference Linux-native tools (such as curl, jq, or shell scripting) where appropriate for automation or template manipulation.
  • Add a note or section highlighting cross-platform support and best practices for Linux users.
GitHub Create Pull Request
Lighthouse https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/lighthouse/how-to/policy-at-scale.md ...lob/main/articles/lighthouse/how-to/policy-at-scale.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools ⚠️ missing_linux_example ⚠️ windows_first
Summary
The documentation exclusively uses PowerShell for all examples and instructions, which is primarily a Windows-centric tool. There are no examples using Azure CLI, Bash, or other cross-platform tools. The focus on PowerShell commands and lack of Linux/macOS alternatives or parity demonstrates a clear Windows bias.
Recommendations
  • Add equivalent Azure CLI examples for all PowerShell commands, as Azure CLI is cross-platform and widely used on Linux and macOS.
  • Explicitly mention that PowerShell Core is available on Linux/macOS, and clarify if the examples are compatible.
  • Provide Bash script samples or instructions for common Linux workflows.
  • Reorder or balance examples so that Windows and Linux approaches are presented equally, rather than Windows/PowerShell first or exclusively.
  • Include notes on prerequisites for both Windows and Linux environments (e.g., installation of Azure CLI, PowerShell Core, required modules).
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/delete-azure-resources.md ...main/articles/azure-arc/data/delete-azure-resources.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page demonstrates Windows bias by exclusively referencing the Azure portal (a GUI tool most commonly used on Windows) for resource deletion steps, and by omitting any examples of using Linux-native tools or shell commands for managing Kubernetes resources. All CLI examples use the Azure CLI, which is cross-platform, but there are no Linux-specific instructions (e.g., kubectl commands, bash scripts) for deleting resources on the Kubernetes cluster itself, nor is there mention of Linux desktop tools or workflows.
Recommendations
  • Add Linux-specific examples, such as using kubectl commands to delete resources or namespaces directly from the Kubernetes cluster.
  • Include bash shell script examples for resource deletion, especially for indirect connectivity mode where Kubernetes is the source of truth.
  • Mention and provide steps for using Linux desktop environments and terminal workflows, not just the Azure portal.
  • Clarify that the Azure CLI commands work on both Windows and Linux, and provide sample commands for both bash and PowerShell where relevant.
  • Add guidance for users managing Azure Arc resources from Linux-only environments, including troubleshooting tips and tool recommendations.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/connectivity.md ...docs/blob/main/articles/azure-arc/data/connectivity.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page does not provide explicit Windows-only examples or tools, but it does exhibit subtle Windows bias by listing Azure portal, Azure Resource Manager APIs, and Azure CLI as primary provisioning and management options before mentioning Linux-native tools like Helm, kubectl, or oc. There are no explicit Linux command-line examples, and the documentation does not offer parity in showing Linux-specific workflows or tools, despite referencing Kubernetes and containerization (which are typically Linux-centric).
Recommendations
  • Provide explicit Linux command-line examples for provisioning, management, and connectivity tasks (e.g., using kubectl, Helm, or bash scripts).
  • List Linux-native tools (kubectl, Helm, oc) before or alongside Azure portal/CLI options to avoid Windows-first ordering.
  • Include example workflows for Linux environments, such as managing containers, authentication, and monitoring using Linux tools.
  • Clarify cross-platform compatibility for all tools mentioned, and specify when a tool or workflow is OS-agnostic.
  • Add references to Linux-specific documentation or guides for Azure Arc-enabled data services.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/edge-rag/observability.md ...blob/main/articles/azure-arc/edge-rag/observability.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation focuses exclusively on Azure portal and Azure Managed Grafana for monitoring Edge RAG metrics, with no mention of Linux-native tools or command-line examples (such as kubectl, Bash, or Linux monitoring utilities). The workflow and screenshots are centered around Azure UI experiences, which are more commonly used on Windows. There is no parity for Linux users who might prefer CLI or open-source monitoring solutions outside the Azure ecosystem.
Recommendations
  • Add Linux CLI examples using kubectl, Bash, or other Linux-native tools to retrieve and visualize Edge RAG metrics.
  • Include instructions for accessing metrics via Prometheus or Grafana running on Linux, not just Azure Managed Grafana.
  • Provide parity for infrastructure monitoring setup using Linux shell commands and scripts.
  • Mention open-source alternatives and how to integrate Edge RAG metrics with them on Linux platforms.
  • Ensure screenshots and walkthroughs include both portal (GUI) and CLI (terminal) workflows.
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
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation generally presents Windows examples and terminology before Linux equivalents, and uses PowerShell for Windows command examples while using Bash for Linux. In several sections, Windows instructions are listed first, and Windows-specific extension names are mentioned before Linux ones. However, Linux examples are present and reasonably complete, and the CLI tool (azcmagent) is cross-platform.
Recommendations
  • Alternate the order of Windows and Linux examples throughout the documentation, or present them side-by-side.
  • Explicitly state that all azcmagent commands work on both platforms, and clarify any platform-specific differences.
  • Provide more parity in extension naming and descriptions, ensuring Linux and Windows extensions are equally highlighted.
  • Where PowerShell is used for Windows, consider mentioning that Bash or other shells can be used on Windows (e.g., via WSL), to promote cross-platform usage.
  • Add a summary table of common extension names for both Windows and Linux to help users quickly identify equivalents.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/system-center-virtual-machine-manager/enable-scvmm-inventory-resources.md ...al-machine-manager/enable-scvmm-inventory-resources.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation is focused exclusively on SCVMM (System Center Virtual Machine Manager), a Windows-centric management tool, and does not mention or provide examples for Linux-based virtualization platforms or management tools. All instructions, screenshots, and terminology are tailored to Windows environments, with no guidance for Linux users or parity for Linux-based workflows.
Recommendations
  • Include references to Linux-based virtualization management tools (e.g., oVirt, KVM, libvirt) and describe if/how they can be integrated with Azure Arc, or clarify that the feature is Windows-only if applicable.
  • Provide alternative examples or guidance for users managing Linux virtual machines or clouds, if supported.
  • Explicitly state platform limitations and suggest equivalent Linux solutions or documentation where possible.
  • Add a section addressing cross-platform considerations and interoperability, if relevant.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/vmware-vsphere/create-virtual-machine.md ...les/azure-arc/vmware-vsphere/create-virtual-machine.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page primarily describes VM creation using the Azure portal and refers to administrator account/password authentication as the default, with Linux/SSH key authentication mentioned only as an alternative. No explicit Linux-specific examples, screenshots, or step-by-step instructions are provided, and Windows-style authentication is presented first. There is no mention of Linux tools, patterns, or parity in guest management or advanced settings.
Recommendations
  • Provide explicit Linux VM creation examples, including screenshots showing SSH key authentication as the primary method for Linux VMs.
  • Include step-by-step instructions for Linux VM deployment, highlighting differences in guest OS customization and management.
  • Mention Linux-specific considerations for guest management, agent installation, and connectivity.
  • Ensure that Linux authentication (SSH key) is presented equally or before Windows administrator/password in relevant sections.
  • Add references to Linux CLI tools and automation patterns (e.g., cloud-init, Ansible) in the 'Reference' section.
GitHub Create Pull Request
Container Registry https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/container-registry-rbac-built-in-roles-overview.md ...try/container-registry-rbac-built-in-roles-overview.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first
Summary
The documentation page lists Azure PowerShell as a primary method for performing role assignments alongside Azure CLI and Azure portal, but does not mention Linux-specific tools or shell environments (e.g., Bash, scripting with curl, etc.). Azure PowerShell is a Windows-centric tool, and its mention before any Linux equivalents (such as Bash or direct REST API calls) suggests a subtle Windows-first bias. No explicit Linux examples or references to Linux-native tools are provided, and PowerShell is listed as a top-level option for role assignment without clarifying cross-platform parity.
Recommendations
  • Explicitly mention that Azure CLI and Azure PowerShell are cross-platform, but highlight that Bash and shell scripting are common on Linux.
  • Provide example commands for role assignments using Bash (with Azure CLI) and/or REST API calls, demonstrating usage on Linux.
  • Clarify that Azure PowerShell is available on Linux, but most Linux users prefer Azure CLI or Bash scripting.
  • Add links or references to Linux-specific documentation or tutorials for managing Azure Container Registry permissions.
  • Ensure that examples and tool recommendations are balanced, with Linux-native approaches (e.g., Bash, CLI) presented before or alongside Windows/PowerShell options.
GitHub Create Pull Request
Quotas https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/quotas/storage-account-quota-requests.md ...main/articles/quotas/storage-account-quota-requests.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first
Summary
The documentation page demonstrates a mild Windows bias by listing Azure PowerShell (a Windows-centric tool) before Azure CLI and REST API when discussing command-line options for viewing storage account quota usage. No Linux-specific examples or tools are provided, and PowerShell is mentioned first, which may suggest a preference for Windows environments.
Recommendations
  • List Azure CLI before Azure PowerShell when presenting cross-platform command-line options, as CLI is natively supported on Linux and macOS.
  • Provide explicit examples for both Azure CLI and PowerShell, clarifying which platforms each tool supports.
  • Include guidance or links for using these tools on Linux/macOS, such as installation instructions or usage notes.
  • Consider mentioning cross-platform scripting patterns or automation approaches, not just Windows-centric ones.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/container-storage/howto-configure-onelake-identity.md .../container-storage/howto-configure-onelake-identity.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation demonstrates a Windows bias by referencing Power BI web links and portals, which are more commonly associated with Windows environments. There are no examples or instructions tailored for Linux users, such as CLI commands or Linux-specific tools, and the workflow assumes a graphical portal-based approach typical of Windows. No Linux equivalents or alternative methods (e.g., using Azure CLI, kubectl, or bash scripts) are provided.
Recommendations
  • Include Linux-specific instructions, such as using Azure CLI or kubectl to configure OneLake Identity and subvolumes.
  • Provide examples of configuration files and commands that can be executed in Linux environments.
  • Mention Linux-compatible tools and workflows alongside portal-based (Windows-centric) instructions.
  • Clarify that the steps are applicable regardless of operating system, and highlight any OS-specific differences.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/create-sql-managed-instance-using-kubernetes-native-tools.md ...ate-sql-managed-instance-using-kubernetes-native-tools.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation demonstrates mild Windows bias by presenting PowerShell as the first method for base64 encoding credentials, followed by Linux/macOS. Additionally, file path examples (e.g., C:\arc-data-services\sqlmi.yaml) use Windows conventions, and the recommended text editor is VS Code, which, while cross-platform, is often associated with Windows environments. However, most commands and tools (kubectl, yaml editing) are platform-neutral, and Linux/macOS equivalents are provided.
Recommendations
  • Present Linux/macOS and Windows examples side-by-side, or alternate which platform is shown first.
  • Include file path examples using both Windows (C:\...) and Linux/macOS (/home/user/...) formats.
  • Mention other cross-platform text editors (e.g., nano, vim, Sublime Text) alongside VS Code.
  • Explicitly state that all steps and tools are applicable to both Windows and Linux/macOS environments.
  • Ensure troubleshooting and related guides also provide parity in platform-specific instructions.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/managed-instance-disaster-recovery-portal.md ...-arc/data/managed-instance-disaster-recovery-portal.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation exclusively describes disaster recovery configuration using the Azure portal, which is a graphical interface accessible from any OS but is traditionally associated with Windows environments. There are no examples or mentions of Linux-specific tools, patterns, or command-line workflows (such as Bash or Linux-native CLI usage). The only alternative referenced is a separate CLI documentation page, but this page itself does not provide parity or direct Linux examples.
Recommendations
  • Add explicit references to cross-platform compatibility of the Azure portal, clarifying that it is accessible from Linux and macOS browsers as well as Windows.
  • Include direct examples or links for performing disaster recovery configuration using Linux-native tools (e.g., Azure CLI in Bash), either within this page or as prominent cross-references.
  • Mention any prerequisites or considerations for Linux users (such as browser compatibility, required packages, or differences in experience).
  • Ensure that screenshots and instructions do not imply Windows-only usage (e.g., avoid showing Windows-specific browser chrome or desktop environments).
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/storage-configuration.md .../main/articles/azure-arc/data/storage-configuration.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools
Summary
The documentation page demonstrates a mild Windows/Azure bias, primarily by presenting Azure-specific storage classes and examples before those of other platforms. The examples and recommendations focus heavily on Azure Kubernetes Service (AKS) and its storage classes, with detailed explanations and links, while AWS and GKE are covered in less detail and after Azure. There is also a reliance on Azure CLI tooling for configuration examples, with no mention of Linux-native alternatives or parity for Linux users. No PowerShell-specific examples are present, and all kubectl commands are cross-platform, but the overall narrative and examples favor Azure/Windows-centric tools and patterns.
Recommendations
  • Provide equivalent Linux-native CLI examples (e.g., kubectl, bash scripts) for configuration tasks currently shown only with Azure CLI.
  • Include more balanced examples and recommendations for AWS and GKE storage classes, with equal detail and links as given for AKS.
  • Add explicit Linux storage class examples (such as NFS, Ceph, or local SSD) and discuss their configuration and use cases.
  • Mention and link to Linux-specific documentation and best practices for Kubernetes storage alongside Azure/Windows resources.
  • Ensure that any references to Azure or Windows tools are paired with Linux alternatives or note their cross-platform compatibility.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/rotate-user-tls-certificate.md ...articles/azure-arc/data/rotate-user-tls-certificate.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first
Summary
The documentation provides both Linux and Windows instructions for base64 encoding, but the Windows-specific tool (certutil) is mentioned after the Linux example and receives additional explanation, including manual header removal and use of findstr. This section is the only place where platform-specific tooling is discussed, and Windows tools are given extra detail. The rest of the documentation uses cross-platform tools (OpenSSL, Azure CLI, kubectl) and does not show bias in command examples.
Recommendations
  • Provide equivalent Linux commands for header removal after base64 encoding, such as using grep or sed, to match the detail given for Windows.
  • When introducing platform-specific tools, present both Linux and Windows options together, or in parallel subsections, rather than giving extra detail to one platform.
  • Consider adding a table summarizing base64 encoding/decoding commands for both platforms for clarity.
  • Explicitly state that OpenSSL, Azure CLI, and kubectl commands are cross-platform and provide any necessary platform-specific notes if differences exist.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/migrate-to-managed-instance.md ...articles/azure-arc/data/migrate-to-managed-instance.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page demonstrates Windows bias by consistently presenting Windows-centric examples and file paths (e.g., C:\Backupfiles\test.bak) for backup operations, and by referencing Windows tools (Azure Data Studio, SSMS) without mentioning Linux equivalents or providing Linux-specific instructions. There are no examples showing how to perform backup operations on Linux systems, nor are Linux file paths or tools (such as sqlcmd or native Linux editors) mentioned. The use of Windows paths and instructions appears before any mention of Linux-compatible methods, and Linux users are left to infer how to adapt the steps.
Recommendations
  • Add explicit Linux examples for backup and restore commands, using Linux file paths (e.g., /home/user/backup/test.bak).
  • Mention and provide instructions for using Linux-native tools such as sqlcmd, nano/vim, and alternatives to SSMS/Azure Data Studio on Linux.
  • Clarify cross-platform compatibility for Azure Data Studio and Azure Storage Explorer, including installation instructions for Linux.
  • When showing kubectl cp examples, provide both Windows and Linux source file path formats.
  • Ensure that prerequisites and steps do not assume a Windows environment, and highlight any platform-specific differences.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/troubleshooting-get-logs.md ...in/articles/azure-arc/data/troubleshooting-get-logs.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page demonstrates Windows bias by providing a path example using Windows-style (C:\temp\logs) and omitting a Linux equivalent (such as /tmp/logs). No Linux-specific examples or notes are given for file paths or usage, despite the cross-platform nature of Azure CLI and Kubernetes tools.
Recommendations
  • Include Linux path examples (e.g., /tmp/logs) alongside Windows examples when demonstrating command usage.
  • Explicitly state that the Azure CLI and Kubernetes tools work on both Windows and Linux, and provide examples for both platforms.
  • Add notes or examples for common Linux shell usage patterns (such as using $HOME or ~ for home directories).
  • Ensure that folder hierarchy and output examples use platform-neutral or dual-platform paths.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/upload-usage-data.md ...blob/main/articles/azure-arc/data/upload-usage-data.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first
Summary
The documentation mentions both Linux and Windows automation options, but Windows tools (Task Scheduler, .cmd/.bat/.ps1 scripts) are listed alongside Linux options, and Windows-specific patterns are mentioned before Linux equivalents in some cases. However, the main scripting example is for Linux shell scripts, and Linux tools (cron, chmod, watch) are demonstrated explicitly.
Recommendations
  • Provide explicit Windows PowerShell or batch script examples for automating uploads, similar to the Linux shell script provided.
  • List Linux automation tools (cron) before Windows Task Scheduler to avoid subtle ordering bias.
  • Include step-by-step instructions for setting up scheduled tasks on Windows, not just mentioning Task Scheduler.
  • Clarify cross-platform compatibility of az arcdata commands and note any differences in usage or prerequisites between Windows and Linux.
  • Ensure that all examples and instructions are provided for both Linux and Windows environments, with equal detail.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/data/validation-program.md ...lob/main/articles/azure-arc/data/validation-program.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first
Summary
The documentation page shows mild Windows bias by referencing Microsoft-centric tools (Azure Data CLI, Azure Data Studio) and several partner solutions that are Windows-focused (e.g., DataON for Azure Stack HCI, Hitachi UCP with Microsoft AKS-HCI, Lenovo ThinkAgile MX). Linux-native or cross-platform alternatives are not explicitly mentioned, and Windows-oriented solutions are listed before Linux equivalents in some partner sections.
Recommendations
  • Explicitly mention Linux support for Azure Data CLI and Azure Data Studio, or provide alternative Linux-native tools if available.
  • Balance partner solution listings by alternating or grouping Windows and Linux-focused solutions, rather than listing Windows-first.
  • Add examples or guidance for Linux users, such as how to generate and use kubeconfig files on Linux systems.
  • Clarify platform compatibility for each tool and solution, especially for those that are Windows-centric.
  • Include references to Linux distributions and tools (e.g., Ubuntu, CentOS, OpenShift, etc.) in prerequisites and process sections.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/includes/azure-arc-enabled-servers.md ...ticles/azure-arc/includes/azure-arc-enabled-servers.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides examples for Azure CLI, Azure PowerShell, and the Azure Portal for each query. While Azure CLI is cross-platform, the inclusion of Azure PowerShell examples (which are most commonly used on Windows and have a Windows-centric history) and the explicit '[Azure PowerShell]' tab for every scenario introduces a subtle Windows bias. Additionally, the ordering of tabs consistently places Azure PowerShell immediately after Azure CLI, which can reinforce a Windows-first perception. There are no explicit Linux shell examples (e.g., Bash, shell scripting), nor are Linux-native tools or patterns mentioned. However, the use of Azure CLI does provide parity for Linux users, and the queries themselves are platform-neutral.
Recommendations
  • Add explicit Bash/shell script examples for Linux users, demonstrating how to run the Azure CLI queries in a Linux terminal.
  • Clarify that Azure CLI is fully supported on Linux and macOS, and link to installation instructions for those platforms.
  • Consider alternating the order of tabs or grouping Azure CLI and PowerShell under a generic 'Command Line' heading to avoid reinforcing a Windows-first mindset.
  • Where relevant, mention Linux-native tools (e.g., jq, grep) that can be used to process Azure CLI output.
  • If PowerShell examples are included, clarify that PowerShell Core is cross-platform and provide instructions for Linux/macOS installation.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/edge-rag/quickstart-edge-rag.md ...ain/articles/azure-arc/edge-rag/quickstart-edge-rag.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation demonstrates a Windows bias primarily in the 'Connect to the developer portal' section, where instructions for updating the hosts file are given exclusively for Windows (using Notepad and the Windows file path). There are no equivalent instructions for Linux or macOS users. Additionally, the mention of 'Switch to PowerShell' in Azure Cloud Shell may imply a Windows-first approach, though most command examples use Azure CLI and bash-like syntax.
Recommendations
  • Add instructions for updating the hosts file on Linux (e.g., using sudo nano /etc/hosts) and macOS.
  • Include notes or examples for common Linux/macOS editors (nano, vim, etc.) and file paths.
  • Clarify that the Azure CLI commands can be run in bash/zsh shells on Linux/macOS, and provide any necessary syntax adjustments (e.g., backtick line continuations vs. backslash).
  • When referencing Azure Cloud Shell, mention both Bash and PowerShell options, and clarify which shell is used in examples.
  • Review other sections for subtle Windows-centric language or assumptions, and ensure parity for Linux/macOS users.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/includes/arc-region-note.md ...ob/main/articles/azure-arc/includes/arc-region-note.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for listing regions, but the PowerShell example is given immediately after the CLI example, which may suggest a slight Windows-first or PowerShell-heavy bias. There is no explicit Linux shell (bash) example, nor is there mention of Linux-specific tools or patterns.
Recommendations
  • Include a bash shell example using Azure CLI to demonstrate parity for Linux users, e.g., 'az account list-locations --output table'.
  • Clarify that Azure CLI works cross-platform and is recommended for both Windows and Linux environments.
  • If mentioning PowerShell, note that PowerShell Core is available on Linux, or provide context for when to use each tool.
  • Consider listing examples in a neutral order or grouping them by platform to avoid perceived prioritization.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/kubernetes/extensions-troubleshooting.md ...les/azure-arc/kubernetes/extensions-troubleshooting.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools
Summary
The documentation page demonstrates a mild Windows bias in a few areas. The Azure CLI is used throughout, which is cross-platform, but some troubleshooting steps and examples reference Windows-centric tools and patterns before their Linux equivalents. For example, the use of iptables troubleshooting is described in the context of Oracle Linux, but the error message and remediation steps are presented in a way that assumes familiarity with Windows-style error output and troubleshooting. Additionally, the documentation references Azure-specific features and tools (such as Azure Policy, Azure Monitor, and Azure CLI) that are more commonly used and documented in Windows environments, with less emphasis on Linux-native alternatives or patterns.
Recommendations
  • Provide explicit Linux and macOS command examples alongside Azure CLI, especially for troubleshooting steps that may differ on non-Windows platforms.
  • Include references to Linux-native tools and troubleshooting patterns (e.g., systemd, journalctl, dmesg) where relevant, especially when discussing pod and container errors.
  • Clarify cross-platform compatibility of Azure CLI and other tools, and note any platform-specific caveats.
  • When discussing error messages or troubleshooting steps, include both Windows and Linux output formats if they differ.
  • Expand troubleshooting sections to mention Linux-specific issues and solutions, such as SELinux, AppArmor, or differences in networking stack behavior.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/kubernetes/includes/network-requirements-azure-cloud.md ...ubernetes/includes/network-requirements-azure-cloud.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ windows_tools
Summary
The documentation page demonstrates mild Windows bias by listing several endpoints with '.windows.net' and 'login.windows.net' before their Linux equivalents or alternatives. The use of 'windows.net' endpoints is prevalent, and Windows-centric terminology appears before Linux-specific references. However, there are some Linux mentions (e.g., 'linuxgeneva-microsoft.azurecr.io'), and the page does not provide command-line examples, so there is no Powershell-heavy or missing Linux example bias.
Recommendations
  • Ensure endpoint lists do not prioritize Windows-named endpoints over Linux or neutral ones; group them by function or alphabetical order.
  • Add explicit notes clarifying that endpoints such as 'login.windows.net' and 'sts.windows.net' are used by both Windows and Linux agents.
  • Where possible, provide parity in documentation language, e.g., mentioning Linux endpoints or tools alongside Windows ones.
  • If command-line examples are added, ensure both Powershell (Windows) and Bash (Linux) examples are provided.
  • Clarify that Azure Arc agents and endpoints are cross-platform, and avoid implying Windows exclusivity in endpoint naming.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/kubernetes/private-link.md ...lob/main/articles/azure-arc/kubernetes/private-link.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing the Azure portal (a web GUI commonly used by Windows administrators) for resource creation and management steps, and by omitting any Linux-specific or cross-platform command-line examples for critical operations such as DNS configuration, firewall setup, and resource provisioning. The only CLI example provided is for the Azure CLI, which is cross-platform, but there are no Linux shell commands or guidance for common Linux tools (e.g., iptables, systemd-resolved, BIND, dnsmasq) for DNS or firewall configuration. Troubleshooting steps use 'nslookup', which is available on both platforms, but do not mention Linux alternatives or context. There is no mention of PowerShell, but the overall workflow assumes familiarity with Azure portal and Windows-centric network administration patterns.
Recommendations
  • Add Linux-specific examples for DNS server configuration (e.g., BIND, dnsmasq, systemd-resolved) and provide sample configuration files or commands.
  • Include firewall configuration examples for common Linux firewalls (e.g., iptables, firewalld, ufw) alongside general guidance.
  • Provide CLI-based resource creation steps using Azure CLI or ARM templates, and clarify that these can be run on Linux, macOS, or Windows.
  • Explicitly mention that the Azure CLI commands and troubleshooting steps are cross-platform, and provide any necessary Linux-specific notes (e.g., package installation, command syntax differences).
  • Where screenshots of the Azure portal are used, offer equivalent CLI instructions for users who prefer or require command-line automation, especially for Linux environments.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/resource-bridge/system-requirements.md ...icles/azure-arc/resource-bridge/system-requirements.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by referencing Azure CLI installation links that default to Windows, and by not providing explicit Linux or macOS instructions or examples for management machine setup. There are no examples or guidance for Linux-specific installation, usage, or troubleshooting, despite Azure CLI being cross-platform. The documentation also omits mention of Linux tools or patterns, and does not clarify whether Linux management machines are supported or recommended.
Recommendations
  • Add explicit instructions and links for installing Azure CLI on Linux and macOS, alongside the Windows instructions.
  • Provide examples of deployment and management commands run from Linux and macOS environments.
  • Clarify that the management machine can be Linux, Windows, or macOS, and list any OS-specific requirements or caveats.
  • Include troubleshooting steps or notes for common issues on Linux (e.g., permissions, networking, file locations).
  • Ensure parity in documentation for all supported platforms, including screenshots or terminal output from Linux shells where appropriate.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/resource-bridge/maintenance.md ...main/articles/azure-arc/resource-bridge/maintenance.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation page describes Azure Arc resource bridge maintenance operations but does not provide platform-specific examples or instructions. However, there is a notable absence of Linux-specific guidance, and the only credential maintenance examples reference VMware vSphere and SCVMM, which are traditionally Windows-centric environments. All command-line instructions use the Azure CLI, which is cross-platform, but there are no explicit Linux shell or script examples, nor any mention of Linux-specific tools or patterns. The documentation implicitly assumes familiarity with Windows-centric infrastructure and omits Linux parity in examples and troubleshooting.
Recommendations
  • Add explicit Linux shell (bash) examples for Azure CLI commands, showing usage on Linux systems.
  • Include troubleshooting steps or maintenance patterns relevant to Linux-based appliance VMs, if supported.
  • Reference Linux-based infrastructure management scenarios alongside Windows/SCVMM and VMware vSphere.
  • Clarify whether the appliance VM can be Linux-based and provide credential update instructions for Linux environments.
  • Ensure parity in examples and guidance for both Windows and Linux administrators.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/azcmagent-disconnect.md ...ain/articles/azure-arc/servers/azcmagent-disconnect.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation shows mild Windows bias by listing Windows-specific authentication methods first and referencing PowerShell tools for access token retrieval, while Linux equivalents are not mentioned. The interactive browser login is described as 'Windows only' and presented before Linux-default device code login. The access token section references PowerShell's Get-AzAccessToken without mentioning Linux alternatives.
Recommendations
  • Present authentication options in a neutral order or alternate which OS is mentioned first.
  • For access token retrieval, mention Linux-compatible methods (e.g., Azure CLI's 'az account get-access-token') alongside PowerShell.
  • Clarify which authentication options are available on both Windows and Linux, and provide explicit Linux examples where appropriate.
  • Ensure that all examples and instructions are cross-platform, or provide parallel examples for both Windows and Linux environments.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/api-extended-security-updates.md ...les/azure-arc/servers/api-extended-security-updates.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation is focused exclusively on Windows Server 2012 and Windows Server 2012 R2, with all examples and API payloads referencing Windows-specific targets. There are no examples or guidance for Linux systems, nor is there mention of Linux equivalents or parity in license management. The only OS mentioned is Windows, and all operational instructions are tailored to Windows environments.
Recommendations
  • Add examples and guidance for managing Extended Security Updates licenses for Linux servers, if supported.
  • Explicitly state whether Linux systems are supported or not, and provide parity in API payloads and CLI commands for Linux targets.
  • Include references to Linux-specific tools or patterns (e.g., bash, shell scripts) alongside Azure CLI examples.
  • Clarify in the introduction that the scope is limited to Windows if Linux is not supported, or expand the scope to include Linux where possible.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/includes/esu-network-requirements.md ...azure-arc/servers/includes/esu-network-requirements.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page focuses exclusively on Windows Server 2012 and SQL Server 2012, with all examples and endpoint descriptions tailored to Windows environments. There are no mentions of Linux servers, Linux-specific endpoints, or guidance for Linux-based Azure Arc-enabled servers. The documentation assumes a Windows-centric use case and omits Linux parity in both product support and operational instructions.
Recommendations
  • Explicitly state whether Linux servers are supported or not for Extended Security Updates in Azure Arc, and clarify any limitations.
  • If Linux support exists, add equivalent endpoint tables and instructions for Linux-based Azure Arc-enabled servers.
  • Provide examples or notes for Linux package download/update mechanisms (e.g., using wget/curl, package managers) alongside Windows installation instructions.
  • Include guidance on certificate management and connectivity checks for Linux environments.
  • Ensure future documentation covers both Windows and Linux scenarios, or clearly marks Windows-only content.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/organize-inventory-servers.md ...ticles/azure-arc/servers/organize-inventory-servers.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation describes organizing and inventorying servers with Azure Arc, emphasizing platform breadth but provides examples and tool references (e.g., Azure PowerShell, Azure CLI) without explicit Linux-specific guidance or parity. Windows-centric tools and patterns are mentioned before Linux alternatives, and there are no Linux-specific examples or references to Linux-native management workflows.
Recommendations
  • Include explicit Linux examples for tagging and inventory operations, such as using Bash scripts or Linux-native tools.
  • Mention Linux-specific management patterns (e.g., integration with Ansible, SSH-based workflows) alongside Azure CLI/PowerShell.
  • Clarify that Azure CLI is cross-platform and provide sample commands executed on Linux terminals.
  • Add screenshots or walkthroughs showing Linux server onboarding and management in Azure Arc.
  • Reference Linux documentation or best practices for server organization and tagging in hybrid environments.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/security-data-privacy.md ...in/articles/azure-arc/servers/security-data-privacy.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation generally provides parity between Windows and Linux, especially in log file locations. However, there is evidence of Windows bias: Windows paths are consistently listed before Linux paths in tables, and the only example for retaining Azure Activity logs references PowerShell, with no mention of Bash or CLI alternatives for Linux users.
Recommendations
  • Alternate the order of OS examples in tables, or list Linux first in some cases to avoid implicit prioritization.
  • Provide equivalent Bash or Azure CLI examples alongside PowerShell for tasks such as retaining Azure Activity logs.
  • Explicitly state that all features and commands are supported on both Windows and Linux, and link to platform-specific guidance where relevant.
  • Review other sections for subtle language or tool prioritization and ensure Linux is equally represented.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/security-networking.md ...main/articles/azure-arc/servers/security-networking.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation mentions Windows Admin Center as a tool for server access, but does not mention any equivalent Linux tools (such as SSH clients or Cockpit). There are no examples or references to Linux-specific patterns or tools, and the only access method called out by name is Windows-centric. This creates a subtle bias towards Windows environments and may leave Linux administrators without clear guidance.
Recommendations
  • Mention Linux-native access methods such as SSH, and clarify their support or limitations with private endpoints.
  • If Windows Admin Center is referenced, also mention comparable Linux tools (e.g., Cockpit, Webmin) or standard SSH usage.
  • Provide examples or notes for both Windows and Linux environments when discussing server management and network access.
  • Explicitly state any differences in behavior or support between Windows and Linux servers for Azure Arc networking features.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/system-center-virtual-machine-manager/administer-arc-scvmm.md ...center-virtual-machine-manager/administer-arc-scvmm.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation focuses exclusively on Azure CLI commands and Azure portal workflows, which are cross-platform, but all operational context is centered on System Center Virtual Machine Manager (SCVMM)—a Windows-only technology. There are no Linux-specific examples, nor is there mention of Linux tools, shell commands, or Linux administration patterns. The only credential update and log collection examples assume Windows-based infrastructure and do not address Linux-based alternatives or mixed environments.
Recommendations
  • Explicitly state platform requirements and limitations (e.g., SCVMM is Windows-only) at the beginning of the documentation.
  • Provide guidance for administrators working from Linux or macOS workstations, such as how to install and use Azure CLI and SSH from those platforms.
  • Include example commands using Bash or other Linux shells for credential updates and log collection, especially where SSH is involved.
  • Clarify whether the Azure Arc resource bridge VM or management cluster can be administered from Linux, and provide instructions if possible.
  • Mention any Linux-compatible alternatives or integration points, if available, for hybrid environments.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/system-center-virtual-machine-manager/set-up-and-manage-self-service-access-scvmm.md ...manager/set-up-and-manage-self-service-access-scvmm.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation exclusively references SCVMM (System Center Virtual Machine Manager), a Windows-only tool, and provides instructions solely through the Azure portal UI without mentioning any Linux-based management tools, command-line interfaces, or cross-platform alternatives. There are no Linux or PowerShell/CLI examples, nor is there any guidance for users who might be managing resources from non-Windows environments.
Recommendations
  • Explicitly state that SCVMM is a Windows-only technology and clarify platform requirements.
  • Provide guidance or references for Linux users, such as how to interact with Azure Arc resources using Azure CLI or REST APIs from Linux systems.
  • Include examples of role assignment using cross-platform tools (e.g., Azure CLI, which runs on Linux, macOS, and Windows), not just portal UI steps.
  • Mention any limitations or alternatives for users who do not have access to Windows environments.
  • If possible, link to documentation on managing Azure Arc resources from Linux or other non-Windows platforms.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/system-center-virtual-machine-manager/terraform-vm-management.md ...ter-virtual-machine-manager/terraform-vm-management.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation focuses exclusively on SCVMM (System Center Virtual Machine Manager), a Windows-centric virtualization management platform, and provides only generic Terraform examples without any OS-specific instructions. All user variables and examples assume Windows conventions (e.g., 'Administrator' username, domain/workgroup settings), and there are no Linux-specific examples, notes, or parity guidance. The documentation does not mention Linux VMs, Linux authentication patterns, or provide examples for managing Linux-based SCVMM VMs.
Recommendations
  • Add explicit examples for provisioning and managing Linux VMs via SCVMM, including sample variables.tf and main.tf files with Linux conventions (e.g., 'adminuser', SSH keys, etc.).
  • Include notes or sections describing differences in VM provisioning for Linux vs. Windows, such as OS profile settings, authentication, and agent installation.
  • Provide guidance on installing the Azure Arc agent on Linux VMs managed by SCVMM, including required credentials and steps.
  • Ensure that documentation references both Windows and Linux VM management scenarios, and avoid using only Windows-centric terminology (e.g., 'Administrator', 'domain', 'workgroup') in generic examples.
  • Where possible, mention Linux equivalents or considerations alongside Windows-specific instructions, especially in prerequisites and best practices.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/vmware-vsphere/administer-arc-vmware.md ...cles/azure-arc/vmware-vsphere/administer-arc-vmware.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page demonstrates a Windows bias by exclusively referencing Azure CLI commands and workflows that are most commonly used on Windows, without providing explicit Linux or cross-platform alternatives. There are no examples or instructions for Linux-specific tools, shell environments, or command syntax (e.g., Bash, SSH usage from Linux, file paths). The instructions and screenshots focus on Azure Portal and CLI usage, which, while technically cross-platform, are presented in a way that assumes a Windows-centric environment (e.g., 'current CLI directory' without clarifying path conventions, no mention of Linux shell usage).
Recommendations
  • Add explicit Linux/Bash examples for all CLI commands, including sample shell syntax and file path conventions.
  • Clarify that Azure CLI is cross-platform and provide guidance for installation and usage on Linux systems.
  • Include instructions for using SSH from Linux workstations, with sample commands and expected output.
  • Mention differences in file storage locations and permissions between Windows and Linux environments when handling kubeconfig and .yaml files.
  • Add screenshots or terminal output from Linux environments to balance the visual representation.
  • Where relevant, reference Linux-native tools (e.g., scp, rsync) for file transfer and log collection.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/vmware-vsphere/create-custom-roles.md ...ticles/azure-arc/vmware-vsphere/create-custom-roles.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation consistently references the Azure portal and mentions Azure PowerShell before Azure CLI, with no explicit Linux-specific guidance or examples. There are no Linux shell or cross-platform command-line examples, and the workflow is described primarily through the Azure portal UI, which is platform-agnostic but often associated with Windows environments. The mention of Azure PowerShell before Azure CLI subtly prioritizes Windows tooling. No Linux-specific tools, shell commands, or screenshots are provided.
Recommendations
  • Provide explicit Azure CLI examples alongside or before PowerShell examples, as Azure CLI is cross-platform and widely used on Linux.
  • Include Linux shell command examples for managing custom roles, such as using az role definition create/update commands.
  • Clarify that the Azure portal and Azure CLI are fully supported on Linux, and add notes or links for Linux users where appropriate.
  • If screenshots are included, ensure they are not Windows-specific (e.g., avoid showing Windows taskbars or UI elements).
  • Consider adding a section or callout for Linux/macOS users, highlighting any platform-specific considerations or tips.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/vmware-vsphere/quick-start-create-a-vm.md ...es/azure-arc/vmware-vsphere/quick-start-create-a-vm.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page demonstrates a subtle Windows bias. VM templates and example variable values consistently use Windows-centric names (e.g., 'contoso-template-win22', 'Administrator' as the default username), and there are no Linux-specific examples or references. All sample code and walkthroughs omit Linux VM scenarios, Linux usernames, or Linux template IDs, despite VMware vCenter supporting both Windows and Linux guests.
Recommendations
  • Include Linux VM examples alongside Windows examples in both Bicep and Terraform sections (e.g., show template IDs for Linux VMs, use 'ubuntu' or 'centos' in variable values).
  • Provide sample values for Linux admin usernames (e.g., 'azureuser', 'root') and passwords.
  • Explicitly mention that both Windows and Linux VMs are supported and provide guidance for Linux-specific provisioning steps if any exist.
  • In best practices, add notes relevant to Linux VM management (e.g., SSH key usage, Linux guest agent installation).
  • Balance the documentation by alternating Windows and Linux references in variable names, template IDs, and walkthroughs.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/workload-orchestration/quickstart-solution-multiple-shared-adapter-dependency.md ...quickstart-solution-multiple-shared-adapter-dependency.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation consistently presents both Bash and PowerShell examples side-by-side for all CLI commands. However, PowerShell examples are given equal prominence and detail as Bash, and in some cases, PowerShell variable syntax is used in explanatory notes and code blocks. There are several places where PowerShell commands are shown before or alongside Bash, and variable references in notes use PowerShell syntax. No Linux-specific tools or patterns are mentioned, and there are no Linux-only examples or troubleshooting tips. The documentation does not mention Linux distributions, shells, or platform-specific considerations, and the use of PowerShell may suggest a Windows-centric approach, especially for users who expect Linux-first documentation for CLI/Kubernetes workflows.
Recommendations
  • Ensure Bash examples are presented first, as Bash is the default shell for most Linux environments.
  • Add explicit notes about platform compatibility (e.g., 'these commands work on Linux, macOS, and Windows').
  • Include troubleshooting tips for Linux environments (e.g., file permissions, environment variables, az CLI installation on Linux).
  • Avoid using PowerShell variable syntax in explanatory notes outside PowerShell tabs.
  • Consider adding examples for other shells (e.g., zsh, fish) or mention how to adapt commands for those environments.
  • Clarify that PowerShell examples are primarily for Windows users, and Bash is recommended for Linux/macOS.
  • Add a section on prerequisites for Linux environments, such as package installation commands (apt, yum, etc.) for az CLI and kubectl.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/workload-orchestration/external-validation.md ...zure-arc/workload-orchestration/external-validation.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for all CLI commands, ensuring parity for Linux and Windows users. However, PowerShell examples are always presented immediately after Bash, and the documentation consistently refers to PowerShell as the Windows scripting environment, with no mention of Linux-specific shells beyond Bash. There are no references to Linux-native tools or workflows outside of Bash, and no Linux GUI or desktop integration is discussed. The Azure portal instructions are platform-neutral, but the CLI instructions may implicitly favor Windows users by always including PowerShell and never mentioning other Linux shells (e.g., Zsh, Fish) or scripting environments.
Recommendations
  • Explicitly state that Bash examples are applicable to Linux and macOS environments, and PowerShell examples are for Windows (and optionally PowerShell Core on Linux).
  • Consider including notes about using PowerShell Core on Linux, or referencing other popular Linux shells (e.g., Zsh, Fish) where relevant.
  • Add a brief section clarifying cross-platform CLI usage, including any differences or caveats for Linux users (e.g., file path formats, environment variable syntax).
  • Ensure that any references to scripting environments do not imply Windows as the default or primary platform.
  • If possible, include troubleshooting or environment setup tips specific to Linux users (e.g., package installation, permissions).
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/workload-orchestration/initial-setup-configuration.md .../workload-orchestration/initial-setup-configuration.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for all steps, but PowerShell is given equal prominence as Bash, despite Bash being the default shell for most Linux environments. There is no explicit Linux-specific guidance, and PowerShell is typically associated with Windows, which may signal a Windows-centric approach. The order of examples (Bash first, then PowerShell) is appropriate, but the heavy inclusion of PowerShell may be unnecessary for Linux users. No Linux-specific tools, patterns, or troubleshooting are mentioned.
Recommendations
  • Clarify that Bash examples are intended for Linux/macOS environments and PowerShell for Windows.
  • Add explicit notes about which shell/environment each example is for, and recommend Bash for Linux users.
  • Consider providing only Bash examples in the main flow, with PowerShell as an optional tab for Windows users.
  • Include troubleshooting or environment setup notes for Linux (e.g., package dependencies, az CLI installation on Linux).
  • Mention Linux-specific considerations for file paths, permissions, or environment variables where relevant.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/workload-orchestration/quickstart-solution-shared-adapter-dependency.md ...ation/quickstart-solution-shared-adapter-dependency.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for all CLI commands, but PowerShell is always presented as the second tab after Bash. There are no Windows-specific tools or patterns mentioned, and the examples are parity between Bash (Linux/macOS) and PowerShell (Windows). However, the presence of PowerShell throughout and the explicit inclusion of PowerShell examples may indicate a slight Windows bias, especially since PowerShell is primarily a Windows shell (though available on Linux). There are no missing Linux examples, and no exclusive use of Windows tools.
Recommendations
  • Clarify that PowerShell examples are also valid for PowerShell Core on Linux/macOS, not just Windows.
  • Consider adding a note about shell compatibility (e.g., Bash for Linux/macOS, PowerShell for Windows and Linux).
  • Ensure that any platform-specific nuances (such as file path formats or environment variable syntax) are highlighted where relevant.
  • If possible, provide a generic 'CLI' tab using cross-platform syntax (e.g., az CLI commands without shell-specific variable assignment) for users who may use other shells.
  • Explicitly mention that all commands are tested on both Linux and Windows environments to reassure users of parity.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/workload-orchestration/tutorial-service-group-scenario-4.md ...oad-orchestration/tutorial-service-group-scenario-4.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for every command, but PowerShell is always presented as a first-class citizen alongside Bash, and in some sections (such as variable naming and command formatting), PowerShell patterns are emphasized. There is also a subtle 'Windows-first' bias in the validation steps, where PowerShell is given equal prominence to Bash, despite Linux being the primary environment for Kubernetes workloads. No Linux-specific tools (e.g., kubectl, grep, jq) are mentioned, and the Azure Portal is referenced as an alternative, which is more commonly used by Windows users.
Recommendations
  • Add explicit Linux validation steps using native Linux tools (e.g., kubectl, grep, jq) to check deployments, pods, and configurations.
  • Clarify that Bash examples are intended for Linux/macOS environments and PowerShell for Windows, and indicate which environment is recommended for Kubernetes operations.
  • Consider presenting Bash (Linux) examples before PowerShell (Windows) examples, as Kubernetes clusters are most commonly managed from Linux environments.
  • Include troubleshooting steps or tips that leverage Linux-native commands and utilities.
  • Reference Linux desktop environments or CLI tools where appropriate, not just the Azure Portal.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/workload-orchestration/service-group.md ...cles/azure-arc/workload-orchestration/service-group.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for all command-line operations, but PowerShell examples are consistently presented immediately after Bash, and often include more detailed scripting (such as use of ConvertFrom-JSON, Select-Object, and Set-Content). There is a slight 'Windows-first' bias in the sense that PowerShell is given equal or greater prominence, and some advanced scripting steps are only shown in PowerShell. There are no Linux-specific tools or patterns (such as jq, sed, or awk) used in the Bash examples, and no mention of Linux-specific troubleshooting or environment setup. All examples use Azure CLI, which is cross-platform, but PowerShell scripting is more advanced and assumes Windows familiarity.
Recommendations
  • Add Linux-specific scripting examples where advanced manipulation is required (e.g., use jq in Bash for JSON processing, instead of only showing ConvertFrom-JSON in PowerShell).
  • Ensure that Bash examples are as detailed and complete as PowerShell ones, especially for steps involving file manipulation or JSON editing.
  • Explicitly mention cross-platform compatibility of Azure CLI and clarify any OS-specific caveats (e.g., file path syntax, environment variable usage).
  • Include troubleshooting notes for common Linux shell issues (e.g., quoting, environment variables, file permissions).
  • Consider listing Bash examples before PowerShell, or alternating the order, to avoid implicit prioritization of Windows/PowerShell.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/workload-orchestration/tutorial-service-group-scenario-1.md ...oad-orchestration/tutorial-service-group-scenario-1.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for every step, but PowerShell is given equal prominence and detail as Bash, rather than being a secondary or optional path. The use of PowerShell tabs and examples throughout the page, and the absence of Linux-specific troubleshooting, environment setup, or tool recommendations, indicates a subtle Windows bias. Additionally, the documentation refers to the Azure portal (a GUI tool more commonly used on Windows) for validation, without mentioning Linux-native alternatives (e.g., kubectl, CLI-only workflows).
Recommendations
  • Add explicit notes about Linux compatibility and environment setup, including common Linux distributions and prerequisites.
  • Provide troubleshooting steps or tips specific to Linux environments (e.g., file permissions, shell differences, package installation).
  • Mention Linux-native tools and workflows for validation and troubleshooting (e.g., using kubectl, journalctl, or systemd for logs).
  • Clarify that PowerShell examples are optional and primarily for Windows users, while Bash is the default for Linux/macOS.
  • Include links to Linux documentation or community resources for further help.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/workload-orchestration/tutorial-service-group-scenario-3.md ...oad-orchestration/tutorial-service-group-scenario-3.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation consistently provides both Bash and PowerShell examples for all command-line steps. However, PowerShell examples are always presented immediately after Bash, and in some cases, PowerShell syntax and idioms (such as variable assignment and ForEach-Object) are used without Linux shell equivalents. There is no explicit mention of Linux-specific tools, nor are Linux desktop workflows or troubleshooting steps discussed. The documentation does not reference Linux distributions or their package managers, and validation steps are written in a way that assumes familiarity with Windows/PowerShell conventions.
Recommendations
  • Add explicit Linux validation and troubleshooting steps, such as using journalctl, systemctl, or kubectl for diagnostics.
  • Include notes about running commands on Linux distributions (e.g., Ubuntu, CentOS) and any OS-specific prerequisites or differences.
  • Provide parity in scripting idioms: for example, use Bash for loops and text processing in Bash sections, and avoid PowerShell-specific constructs in Bash examples.
  • Mention Linux desktop workflows (e.g., using GNOME Terminal, xterm) where appropriate, and clarify that all CLI steps are cross-platform.
  • Ensure that any references to the Azure portal or other GUI tools clarify that they are accessible from Linux browsers and environments.
GitHub Create Pull Request
Azure Portal https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-portal/azure-portal-dashboards-create-programmatically.md ...tal/azure-portal-dashboards-create-programmatically.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation page demonstrates mild Windows bias. In the 'Overview' and deployment sections, Azure PowerShell is listed before Azure CLI, and PowerShell is given equal prominence to CLI and REST API, despite CLI being cross-platform and more widely used on Linux. There are no explicit Linux shell examples, and PowerShell is referenced as a primary method for deployment. However, the dashboard JSON and links do reference both Linux and Windows VMs equally, and there are no Windows-only tools or patterns shown.
Recommendations
  • List Azure CLI before PowerShell in tool lists and deployment instructions, as CLI is cross-platform and preferred on Linux.
  • Provide explicit Bash or shell examples for Linux users alongside PowerShell examples.
  • Clarify that both Azure CLI and PowerShell are available on all platforms, but CLI is native to Linux.
  • Add links to Linux-specific quickstarts or documentation where relevant.
  • Consider including a note or section for deploying dashboards from Linux environments, with example commands.
GitHub Create Pull Request
Azure Portal https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-portal/get-subscription-tenant-id.md ...in/articles/azure-portal/get-subscription-tenant-id.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides both Azure PowerShell and Azure CLI options for programmatic access, but PowerShell is mentioned first in tips and links, and the CLI is often presented as an alternative rather than an equal. There are no explicit Linux-only examples, and PowerShell (historically Windows-centric) is given prominence, which may subtly favor Windows users.
Recommendations
  • Alternate the order of PowerShell and Azure CLI mentions, or mention CLI first in some cases to balance exposure.
  • Explicitly state that Azure CLI works cross-platform (Windows, Linux, macOS) and provide examples of usage on Linux terminals.
  • Include screenshots or instructions for copying IDs using Azure CLI in a Linux shell, not just via the portal.
  • Clarify that PowerShell Core is available cross-platform, if referenced, to reduce Windows association.
  • Add a section or tip for Linux users, e.g., how to install and use Azure CLI on Linux to retrieve subscription and tenant IDs.
GitHub Create Pull Request
Azure Portal https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-portal/mobile-app/microsoft-copilot-in-azure.md .../azure-portal/mobile-app/microsoft-copilot-in-azure.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation mentions 'Generate CLI and PowerShell scripts' as a key capability, listing PowerShell (a Windows-centric tool) alongside CLI. PowerShell is referenced before any Linux-specific shell or scripting language, and there are no explicit examples or mentions of Bash, Linux shell scripts, or Linux-specific tools. This ordering and emphasis may suggest a Windows-first or PowerShell-heavy bias, even though CLI is cross-platform.
Recommendations
  • Explicitly mention Bash or Linux shell script generation as a capability alongside PowerShell and CLI.
  • Provide examples or clarify that generated CLI scripts are compatible with both Windows and Linux environments.
  • Add a note or section highlighting Linux parity, ensuring users know that Azure Copilot supports Linux workflows and tools.
  • When listing script generation capabilities, alternate or randomize the order (e.g., 'Generate Bash, CLI, and PowerShell scripts') to avoid implicit prioritization.
GitHub Create Pull Request
Azure Portal https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-portal/quickstart-portal-dashboard-azure-cli.md .../azure-portal/quickstart-portal-dashboard-azure-cli.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page demonstrates a bias towards Windows by providing only a Windows VM creation example (using the 'win2016datacenter' image) and referencing Windows-specific username and password requirements. There are no equivalent Linux VM creation examples or references to Linux-specific requirements, which may hinder Linux users from following the guide effectively.
Recommendations
  • Include a Linux VM creation example alongside the Windows example, such as using '--image UbuntuLTS' and SSH key authentication.
  • Reference Linux-specific username and password/SSH requirements in addition to Windows requirements.
  • Clarify that the dashboard template and Azure CLI commands work equally well for Linux VMs.
  • Ensure that downloadable templates and instructions are not tailored exclusively to Windows environments.
GitHub Create Pull Request
Container Registry https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/authenticate-aks-cross-tenant.md ...es/container-registry/authenticate-aks-cross-tenant.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page demonstrates a subtle Windows bias by exclusively referencing the Azure portal (web UI) and Azure CLI, without providing any Linux-specific or cross-platform command-line examples. There are no PowerShell commands, but the lack of explicit Linux shell examples and the use of portal-based instructions may disadvantage Linux users who prefer terminal workflows. Additionally, the documentation does not mention Linux tools or patterns, nor does it provide examples for Linux-based AKS management.
Recommendations
  • Add explicit Linux shell (bash) examples for relevant steps, such as updating AKS service principal credentials and assigning roles.
  • Include Azure CLI commands with notes on cross-platform compatibility (Windows, macOS, Linux).
  • Provide guidance for performing steps via command line on Linux systems, not just via the Azure portal.
  • Clarify that the instructions are applicable to all platforms, and highlight any platform-specific considerations if present.
GitHub Create Pull Request
Container Registry https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/buffer-gate-public-content.md ...icles/container-registry/buffer-gate-public-content.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for importing images into Azure Container Registry, but it lists Azure PowerShell as a primary tool alongside Azure CLI and portal, which may suggest a Windows-centric approach. The PowerShell example is given equal prominence to the CLI example, and there are no explicit Linux shell (bash) or cross-platform scripting examples. There is no mention of Linux-specific tools or workflows, and PowerShell is traditionally associated with Windows environments, though it is now cross-platform. The documentation does not provide Linux-first or Linux-specific guidance, nor does it mention Linux package managers or shell scripting alternatives.
Recommendations
  • Add explicit bash or shell script examples for Linux users, especially for common workflows such as importing images.
  • Clarify that Azure CLI is cross-platform and provide usage notes for Linux and macOS environments.
  • Mention that PowerShell is available on Linux, but also provide native Linux shell alternatives where appropriate.
  • Include references to Linux-native tools or workflows, such as using curl, wget, or podman where relevant.
  • Order examples so that cross-platform or Linux-native tools are presented before Windows-centric tools like PowerShell.
  • Add a section or note on Linux authentication patterns and registry access, including integration with Linux-based CI/CD systems.
GitHub Create Pull Request
Container Registry https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/container-registry-auth-aci.md ...cles/container-registry/container-registry-auth-aci.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation page provides both Azure CLI and Azure PowerShell sample script links, but lists Azure PowerShell immediately after Azure CLI, giving it equal prominence. There is no explicit mention or example of Linux-specific tools or shell environments beyond a brief note about setting an environment variable for bash. The documentation does not provide Linux shell script examples inline, and PowerShell (primarily a Windows tool) is featured as a primary alternative to Azure CLI.
Recommendations
  • Add explicit Linux/bash script examples inline, not just via external links.
  • Mention Linux shell environments (e.g., bash, zsh) and provide guidance for common Linux scenarios.
  • If PowerShell is referenced, clarify cross-platform support or provide parity with Linux-native tools.
  • List Linux/Unix examples before or alongside Windows/PowerShell examples to avoid implicit prioritization.
  • Expand the note about 'export MSYS_NO_PATHCONV=1' to explain its relevance for Linux users, and provide troubleshooting tips for common Linux issues.
GitHub Create Pull Request
Container Registry https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/container-registry-helm-repos.md ...es/container-registry/container-registry-helm-repos.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page demonstrates a subtle Windows bias in its command examples and environment variable usage. The initial example for setting environment variables uses the Windows 'set' command, with no mention of the Linux/Unix 'export' equivalent. Throughout the page, commands are presented in a generic shell format, but the only explicit environment variable setting is Windows-style. There are no PowerShell-specific examples, but the lack of Linux-specific instructions (such as 'export' for environment variables) may confuse Linux users. No Windows-only tools or patterns are mentioned, but the order of presenting environment variable setup favors Windows.
Recommendations
  • Provide both Windows ('set VAR=value') and Linux/macOS ('export VAR=value') examples when setting environment variables.
  • Explicitly state which shell is assumed for each command block, or provide separate tabs/sections for Windows CMD, PowerShell, and Bash.
  • Ensure parity by including Linux/macOS-specific instructions where relevant, especially for authentication and environment setup.
  • Review all command examples to confirm they work as written on both Windows and Linux platforms, or annotate differences.
GitHub Create Pull Request
Container Registry https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/container-registry-rbac-custom-roles.md ...ainer-registry/container-registry-rbac-custom-roles.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation presents both Azure CLI and Azure PowerShell commands for listing permissions, but PowerShell is mentioned alongside CLI in a way that may suggest parity. However, PowerShell is a Windows-centric tool, and there are no explicit Linux shell examples (e.g., Bash, scripting patterns) or notes about cross-platform usage. Additionally, the order of mentioning Azure CLI and PowerShell is inconsistent, sometimes listing PowerShell first in links. There is no explicit bias in tool recommendations, but the lack of Linux-specific examples or clarifications may disadvantage Linux users.
Recommendations
  • Clearly indicate that Azure CLI works cross-platform (Windows, Linux, macOS) and is recommended for Linux environments.
  • Provide explicit Bash or Linux shell examples where relevant, especially for scripting or automation.
  • When listing tools, consistently mention Azure CLI before PowerShell to reflect its cross-platform nature.
  • Add notes clarifying that PowerShell Core is available on Linux, or link to installation instructions for Linux users.
  • Include troubleshooting or environment setup tips for Linux users, such as file path conventions or authentication differences.
GitHub Create Pull Request
Container Registry https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/container-registry-troubleshoot-access.md ...ner-registry/container-registry-troubleshoot-access.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation page does not provide explicit Windows-only examples or tools, but it demonstrates subtle Windows bias by omitting platform-specific troubleshooting steps and examples. For instance, when discussing Docker proxy configuration, it does not mention Linux-specific daemon configuration steps or environment variables. Additionally, while DNS troubleshooting tools like 'dig' and 'nslookup' are mentioned (which are available on both platforms), there are no explicit Linux command-line examples or references to Linux-specific patterns (e.g., systemd configuration for Docker, iptables, or Linux firewall tools). The documentation assumes parity but does not ensure it by providing Linux-centric guidance or examples.
Recommendations
  • Add explicit Linux troubleshooting examples, such as configuring Docker proxy settings via systemd drop-in files and environment variables (HTTP_PROXY, HTTPS_PROXY) for Linux.
  • Include Linux-specific commands for firewall and network diagnostics (e.g., iptables, ufw, firewalld) alongside any Windows equivalents.
  • Provide step-by-step instructions for common Linux distributions (Ubuntu, CentOS, etc.) when discussing Docker daemon restart and proxy configuration.
  • Reference Linux log file locations (e.g., /var/log/docker.log) and diagnostic tools (e.g., journalctl) where appropriate.
  • Ensure that any mention of network utilities includes installation instructions for Linux (e.g., 'apt install dnsutils' for dig/nslookup).
GitHub Create Pull Request
Container Registry https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/container-registry-tutorial-github-verify-notation-trusted-signing.md ...gistry-tutorial-github-verify-notation-trusted-signing.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides both Linux (bash) and Windows (PowerShell) examples for all command-line steps, but consistently lists Windows examples after Linux, indicating a 'windows_first' bias in terms of explicit inclusion and ordering. Additionally, Windows-specific tooling (PowerShell, Invoke-WebRequest, New-Item) is used for Windows examples, but no Linux-specific tools beyond curl and bash are mentioned. There is no evidence of missing Linux examples or exclusive use of Windows tools, but the pattern of always providing Windows examples and using PowerShell commands reflects a mild Windows bias.
Recommendations
  • Ensure that Linux and Windows examples are presented with equal prominence, possibly by randomizing or alternating the order in which they appear.
  • Consider including macOS-specific instructions or notes where relevant, to further improve cross-platform parity.
  • Where possible, use platform-agnostic commands or highlight cross-platform tools (e.g., using Python or Node.js scripts for downloads) to minimize reliance on OS-specific shells.
  • Explicitly state that all examples are available for both platforms at the start of the section, to reassure users of parity.
  • Review for any subtle differences in functionality or prerequisites between platforms and document them clearly.
GitHub Create Pull Request
Container Registry https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/includes/azure-container-registry.md ...ontainer-registry/includes/azure-container-registry.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for querying vulnerability assessment results, but the PowerShell example is given equal prominence to the CLI example, and there is no explicit Linux shell (bash) example or mention of Linux-specific usage patterns. The use of PowerShell (traditionally Windows-centric) and the lack of Linux shell examples may make the documentation feel Windows-biased, especially for users who prefer bash or other Linux shells.
Recommendations
  • Add explicit bash/Linux shell examples for running Azure CLI commands, including any necessary environment setup or authentication steps common in Linux environments.
  • Clarify that Azure CLI works cross-platform and provide guidance for Linux/macOS users (e.g., installation, authentication).
  • If PowerShell is mentioned, also mention alternatives for Linux users (e.g., bash, zsh) and provide equivalent examples.
  • Consider reordering examples to present Azure CLI (cross-platform) before PowerShell, or explicitly state platform applicability for each example.
  • Include troubleshooting notes or links for common Linux issues (e.g., az CLI installation, permissions).
GitHub Create Pull Request
Container Registry https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/quickstart-client-libraries.md ...cles/container-registry/quickstart-client-libraries.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_tools ⚠️ windows_first
Summary
The documentation page demonstrates mild Windows bias in the prerequisites section, where Azure PowerShell and Azure CLI are listed as options for creating a registry, with PowerShell (a Windows-centric tool) mentioned before Azure CLI. The example for creating a registry uses Azure CLI, which is cross-platform, but the ordering of options may suggest a Windows-first approach. The rest of the documentation is focused on cross-platform SDK usage and does not show significant bias in code samples, which are provided for multiple languages and do not rely on Windows-specific tools or patterns.
Recommendations
  • List Azure CLI before Azure PowerShell in the prerequisites, as CLI is cross-platform and more widely used on Linux.
  • Explicitly mention that Azure CLI is available on Linux/macOS/Windows, while PowerShell is primarily a Windows tool (though it is available cross-platform, many users still associate it with Windows).
  • Where possible, provide Linux/macOS-specific notes or instructions for common developer workflows, such as environment variable setup or authentication.
  • Ensure that any references to tooling or shell commands are either cross-platform or have Linux/macOS equivalents provided.
  • Consider adding a note clarifying that all SDK examples are platform-agnostic and can be run on Linux, macOS, or Windows.
GitHub Create Pull Request
Container Registry https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/container-registry/quickstart-connected-registry-arc-cli.md ...iner-registry/quickstart-connected-registry-arc-cli.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for generating the protected settings JSON file, but the PowerShell example is given immediately after Bash and is not clearly marked as Windows-specific. The overall flow does not show a strong bias toward Windows, but the PowerShell example is present and could be interpreted as giving parity to Windows users. There are no exclusive references to Windows tools, and all CLI commands are cross-platform (Azure CLI, kubectl). However, the PowerShell example is included before any mention of Linux-specific shell variants (e.g., zsh, fish), and there is no explicit guidance for Linux users beyond Bash.
Recommendations
  • Clearly label the PowerShell example as 'Windows (PowerShell)' and the Bash example as 'Linux/macOS (Bash)' to avoid confusion.
  • Provide additional Linux shell variants if relevant (e.g., zsh, fish), or clarify that Bash is the recommended shell for Linux/macOS.
  • Ensure that Bash examples are presented first, or in a way that makes it clear they are the default for Linux/macOS users.
  • Add a note indicating that all Azure CLI commands are cross-platform and can be run on Windows, Linux, or macOS.
  • Consider including a table or section summarizing platform compatibility for all commands and tools used.
GitHub Create Pull Request
Lighthouse https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/lighthouse/how-to/remove-delegation.md ...b/main/articles/lighthouse/how-to/remove-delegation.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation page presents PowerShell instructions before Azure CLI examples in the 'Service providers' section, and refers to PowerShell-specific commands and patterns. While Azure CLI examples are included, there is a subtle preference for Windows/PowerShell tooling, which may be less familiar or accessible to Linux users. No Linux-specific shell examples (e.g., bash scripts) or explicit mention of Linux environments are provided.
Recommendations
  • Present Azure CLI examples before PowerShell examples, as CLI is cross-platform and more commonly used on Linux.
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide guidance for Linux users where relevant.
  • Include bash script examples or usage notes for Linux environments, such as how to run these commands in a Linux shell.
  • Avoid language that assumes use of PowerShell or Windows tools as the default; clarify that both PowerShell and CLI are supported across platforms.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/azcmagent-genkey.md ...ob/main/articles/azure-arc/servers/azcmagent-genkey.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ missing_linux_example
Summary
The documentation provides a generic CLI example without specifying platform-specific instructions. However, it does not include any examples or notes about running the command on Linux systems, nor does it mention Linux shell usage or considerations. There is no explicit Windows bias in terms of Windows/Powershell examples or tools, but the absence of Linux-specific guidance may hinder Linux users.
Recommendations
  • Add explicit examples showing usage in both Windows (Command Prompt/Powershell) and Linux (Bash) environments.
  • Include notes about any platform-specific prerequisites or differences in behavior.
  • Mention how to locate the azcmagent binary on Linux (e.g., /usr/bin/azcmagent) and Windows (e.g., C:\Program Files\azcmagent\azcmagent.exe).
  • Clarify if the command syntax or output differs between platforms.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/azcmagent-config.md ...ob/main/articles/azure-arc/servers/azcmagent-config.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ missing_linux_example
Summary
The documentation provides command-line usage and examples for the azcmagent config tool, but all examples are generic and do not reference platform-specific shells or tools. However, there is a subtle bias in that none of the examples clarify usage in Linux environments (such as bash syntax, environment variables, or file paths), nor do they mention Linux-specific considerations. Additionally, the extension example references 'AzureMonitorWindowsAgent', which is Windows-specific, without mentioning Linux equivalents.
Recommendations
  • Include example commands explicitly showing usage in Linux shells (e.g., bash), such as using single quotes, escaping, or referencing environment variables.
  • Add examples or notes for Linux-specific agents or extensions (e.g., AzureMonitorLinuxAgent) alongside Windows examples.
  • Mention any differences in configuration file locations or permissions between Windows and Linux.
  • Clarify that the azcmagent tool is cross-platform and provide parity in documentation for both Windows and Linux users.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/azcmagent.md ...docs/blob/main/articles/azure-arc/servers/azcmagent.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ windows_first
Summary
The documentation page mentions the Windows installation path and PATH variable update before the Linux equivalent, giving Windows precedence in the installation location section. No PowerShell-specific examples or Windows-only tools are present, and Linux is mentioned with parity in most other sections.
Recommendations
  • List Windows and Linux installation paths together, or mention Linux first in alternating documentation updates.
  • Provide explicit Linux shell command examples (e.g., how to verify PATH or run the CLI from the Linux path) alongside Windows instructions.
  • Ensure troubleshooting and usage examples include both Windows (cmd/PowerShell) and Linux (bash/sh) contexts where relevant.
GitHub Create Pull Request
Azure Arc https://github.com/MicrosoftDocs/azure-management-docs/blob/main/articles/azure-arc/servers/run-command-security.md ...ain/articles/azure-arc/servers/run-command-security.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ windows_first
Summary
The documentation presents the Windows example before the Linux example when demonstrating how to block or allow Run command extensions locally. While both platforms are covered and examples are provided for each, the ordering prioritizes Windows, which may subtly reinforce a Windows-centric perspective.
Recommendations
  • Alternate the order of platform examples across documentation pages, or present Linux examples first where appropriate.
  • Explicitly state that the instructions apply equally to both Windows and Linux, and clarify any platform-specific differences.
  • Consider grouping platform-specific instructions under neutral headings (e.g., 'Platform-specific examples') to avoid implicit prioritization.
  • Ensure parity in detail and clarity between Windows and Linux examples.
GitHub Create Pull Request