Azure Arc

926
Total Pages
755
Linux-Friendly Pages
171
Pages with Bias
18.5%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

432 issues found
Showing 151-175 of 432 flagged pages
Azure Arc Install Arc agent at scale for your VMware VMs ...arc/vmware-vsphere/enable-guest-management-at-scale.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page demonstrates a notable Windows bias. The primary automation script for Arc agent installation is a PowerShell script, with instructions and examples focused on Windows environments (e.g., PowerShell terminal, Windows Task Scheduler for cron jobs). There are no equivalent Linux shell script examples or Linux-native scheduling instructions (e.g., cron). Out-of-band methods mention Ansible, but most examples and links are for Windows-centric tools and patterns. Linux guidance is limited to a single sudo configuration note.
Recommendations
  • Provide a Bash or Python version of the helper script for Linux/macOS users.
  • Include Linux/macOS terminal usage instructions alongside PowerShell examples.
  • Add instructions for scheduling the script using Linux cron (crontab) and systemd timers.
  • Ensure parity in example commands and automation tooling for both Windows and Linux platforms.
  • Highlight Ansible and other cross-platform tools more prominently, with direct Linux usage examples.
GitHub Create Pull Request
Azure Arc Deliver ESUs for VMware VMs through Arc ...r-extended-security-updates-for-vmware-vms-through-arc.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
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/2012 R2 VMs, with all examples, screenshots, and patching solutions referencing Windows-specific tools and workflows. There are no Linux or macOS examples, nor any mention of how ESUs or Azure Arc features might apply to non-Windows operating systems. Windows-centric patching tools (WSUS, Microsoft Updates, Endpoint Configuration Manager) are listed, with no Linux equivalents or guidance.
Recommendations
  • Clarify in the introduction that ESUs are only applicable to Windows Server, and note if Linux VMs are not supported.
  • If Azure Arc features for ESU delivery are or will be available for Linux VMs, add equivalent Linux guidance and examples.
  • List third-party patch management solutions that support Linux, or provide links to Azure Arc documentation for Linux VM management.
  • Where patching solutions are mentioned, include Linux-native options (e.g., apt, yum, Azure Update Manager for Linux) if relevant.
  • Add a note for cross-platform administrators about the scope and limitations regarding Linux/macOS support.
GitHub Create Pull Request
Azure Arc What is Azure Arc-enabled VMware vSphere? ...lob/main/articles/azure-arc/vmware-vsphere/overview.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
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 moderate Windows bias. Windows-specific management features (e.g., Windows Server management, Extended Security Updates for Windows Server and SQL Server) are highlighted, often before or in greater detail than Linux equivalents. Examples and links for automation and configuration (such as Azure Automation runbooks) default to Windows tabs or PowerShell, with Linux options mentioned but not equally emphasized. Some next steps and feature links are Windows-centric, and Linux-specific guidance/examples are less visible or missing.
Recommendations
  • Ensure all automation and configuration examples (e.g., Azure Automation, VM extensions) provide Linux-specific instructions and examples alongside Windows/PowerShell.
  • Balance mentions of Windows Server management and Extended Security Updates with equivalent Linux management features, such as patching, compliance, and lifecycle management for Linux VMs.
  • Where links default to Windows tabs or examples, provide equal prominence to Linux tabs/examples.
  • Add explicit Linux/macOS CLI examples and workflows for common tasks (e.g., onboarding, agent installation, automation).
  • Highlight Linux compatibility and supported scenarios in summary and feature lists, not just in detailed sections.
GitHub Create Pull Request
Azure Arc Set up and manage self-service access to VMware resources through Azure RBAC ...vmware-vsphere/setup-and-manage-self-service-access.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively references the Azure portal UI for role assignment and management, which is most commonly accessed via Windows. There are no examples or instructions for performing these tasks using cross-platform tools such as Azure CLI, PowerShell Core (which is cross-platform), or REST API, nor are Linux/macOS-specific workflows mentioned. This creates friction for users who prefer or require command-line or automated approaches, especially on Linux/macOS.
Recommendations
  • Add equivalent instructions for assigning roles using Azure CLI, which is available on Windows, Linux, and macOS.
  • Include PowerShell Core examples, noting its cross-platform compatibility.
  • Provide REST API sample calls for role assignment to support automation and non-Windows environments.
  • Explicitly mention that the Azure portal is accessible from any modern browser on any OS, to reduce perceived Windows bias.
  • Consider a section comparing UI and CLI/API approaches for common tasks.
GitHub Create Pull Request
Azure Arc Remove your VMware vCenter environment from Azure Arc ...e-arc/vmware-vsphere/remove-vcenter-from-arc-vmware.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates moderate Windows bias, especially in the section on running the deboarding script, where only Windows/PowerShell instructions are provided and Windows-specific tools (PowerShell, Set-ExecutionPolicy) are referenced. The script execution steps are detailed for Windows users, while Linux/macOS users are left without equivalent instructions or examples. Additionally, Windows instructions are presented before Linux ones in the agent uninstall section.
Recommendations
  • Provide explicit instructions for running the deboarding script on Linux/macOS, including prerequisites (e.g., PowerShell Core, Azure CLI) and command examples.
  • Mention how to set script execution policies or permissions on Linux/macOS (e.g., chmod +x, ./arcvmware-deboard.ps1 with PowerShell Core).
  • Include Linux/macOS-specific notes about input prompts and script behavior.
  • Where possible, present Windows and Linux/macOS instructions side-by-side or in parallel sections.
  • Ensure parity in troubleshooting and caveats for both platforms.
GitHub Create Pull Request
Azure Arc Bulk Review, Publish, and Deploy with Workload Orchestration ...es/azure-arc/workload-orchestration/bulk-deployment.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation consistently uses PowerShell syntax for CLI commands and references PowerShell scripts (.ps1) as the primary automation method, with no mention of Bash, shell scripts, or Linux/macOS-specific instructions. All code blocks are labeled as 'powershell', and there is no guidance for running commands in Linux/macOS terminals. The bulk deployment automation is provided only as a PowerShell script, and workflow deletion is also Windows-centric. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer native shell environments.
Recommendations
  • Provide CLI command examples using Bash syntax and clarify cross-platform usage (e.g., az CLI works on Linux/macOS).
  • Offer equivalent Bash or shell scripts for bulk deployment and workflow deletion, or document how to use PowerShell Core on Linux/macOS.
  • Explicitly state platform requirements for provided scripts and tools, and link to cross-platform installation guides if PowerShell is required.
  • Reorder examples so that cross-platform CLI usage is shown before or alongside PowerShell-specific instructions.
  • Add notes or tabs indicating how Linux/macOS users can perform the same tasks, including any required environment setup.
GitHub Create Pull Request
Azure Arc Prepare the Environment for Workload Orchestration ...rc/workload-orchestration/initial-setup-environment.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits several Windows-centric biases. Windows tools (winget) are used for installing kubectl with no Linux/macOS alternative. The Bash example for extracting ZIP files incorrectly uses PowerShell's Expand-Archive, which is not available on native Bash/Linux/macOS. Throughout, Windows/PowerShell patterns and tools are presented first or exclusively, and Linux/macOS-specific commands (e.g., unzip, tar) are missing. This creates friction for non-Windows users attempting to follow the setup steps.
Recommendations
  • Provide Linux/macOS-specific installation instructions for kubectl (e.g., using curl or package managers like apt, brew, yum).
  • Replace Expand-Archive in Bash examples with unzip or tar commands for cross-platform compatibility.
  • Ensure all command examples are valid for native Bash on Linux/macOS, not just Bash on Windows.
  • Alternate the order of examples so Linux/macOS commands are shown first in some sections.
  • Explicitly mention platform-specific differences and provide parity in instructions for all major OSes.
GitHub Create Pull Request
Azure Arc Release Notes for Workload Orchestration ...cles/azure-arc/workload-orchestration/release-notes.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page predominantly provides CLI examples using PowerShell syntax (with backticks for line continuation and variable notation like $rg), which is specific to Windows environments. There are no equivalent Bash or Linux/macOS shell examples for configuration tasks, especially in the May 2025 release section. While the Azure CLI is cross-platform, the examples and instructions are tailored to Windows users, potentially creating friction for Linux/macOS users who may not be familiar with PowerShell conventions.
Recommendations
  • Provide Bash shell examples alongside PowerShell for all CLI commands, especially for configuration tasks.
  • Explicitly state that the Azure CLI commands work on Linux/macOS and show examples with appropriate line continuation (using \) and variable syntax.
  • Add notes or sections clarifying cross-platform usage and any OS-specific considerations.
  • Ensure that documentation does not assume a Windows environment by default, and avoid using Windows-specific syntax unless explicitly targeting Windows users.
GitHub Create Pull Request
Azure Arc Troubleshooting for Workload Orchestration ...es/azure-arc/workload-orchestration/troubleshooting.md
Medium Priority View Details →
Scanned: 2026-01-13 06:17
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, especially in the 'Troubleshoot staging' and related orchestration sections. Most troubleshooting steps and code examples use PowerShell syntax and Windows-centric command patterns, with little to no mention of Linux/macOS equivalents. Only in the 'Troubleshoot service groups' section are Bash examples provided alongside PowerShell, but elsewhere, Linux users are left to adapt Windows-specific instructions themselves.
Recommendations
  • Provide Bash/Linux shell equivalents for all PowerShell commands, especially for az, docker, and kubectl usage.
  • Avoid using PowerShell-specific constructs (e.g., ConvertTo-Json, Out-File, [Convert]::ToBase64String) without showing how to achieve the same in Bash.
  • Explicitly mention cross-platform compatibility for commands and clarify any OS-specific requirements.
  • Order examples so that Bash/Linux commands are presented first or side-by-side with PowerShell, not only in a separate tab for a single section.
  • Review file encoding instructions to include Linux/macOS editors and workflows.
GitHub Create Pull Request
Azure Arc Choosing the right Azure Arc service for machines ...nt-docs/blob/main/articles/azure-arc/choose-service.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific features (e.g., Extended Security Updates for Windows Server, SQL Server management, SCVMM integration) are highlighted, and onboarding instructions for Azure VMware Solution link to Windows-specific tabs. Automation examples mention PowerShell before Python, and there is frequent reference to Windows-centric management tools (SCVMM, Microsoft Defender for Endpoint, Azure Update Manager). Linux is mentioned as supported, but Linux-specific examples, patterns, or tools are not provided, and Windows features are often described first or in more detail.
Recommendations
  • Include Linux-specific onboarding instructions and examples, especially for agent installation and management tasks.
  • Provide parity in automation examples, such as showing Bash or shell scripts alongside PowerShell.
  • Highlight Linux management features and scenarios with equal detail as Windows (e.g., mention Linux security and update management tools).
  • Ensure links and tabs for onboarding (e.g., Azure VMware Solution) include Linux-focused documentation, not just Windows.
  • Add explicit Linux compatibility notes for features that are Windows-centric (e.g., ESUs, SCVMM).
GitHub Create Pull Request
Azure Arc Customer intent: As a system administrator, I want to configure a single-node Kubernetes cluster with adequate resources and storage provisions, so that I can deploy and manage applications effectively using Azure IoT Operations and Azure Container Storage. ...tainer-storage/includes/single-node-edge-essentials.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation page is focused on preparing Linux with AKS Edge Essentials, but it uses Windows-centric tools and patterns, notably the Invoke-AksEdgeNodeCommand cmdlet, which is a PowerShell command. There are no direct Linux shell command equivalents provided for critical configuration steps, and the use of Notepad as the default text editor is a Windows-first pattern. This creates friction for Linux users who may not have access to PowerShell or Windows tools.
Recommendations
  • Provide Linux-native shell command equivalents for all PowerShell cmdlets, especially for sysctl configuration.
  • Recommend Linux text editors (e.g., nano, vim) alongside Notepad for editing configuration files.
  • Clarify whether Invoke-AksEdgeNodeCommand can be run from Linux, or provide alternative instructions for Linux-only environments.
  • Ensure all steps can be completed using standard Linux tools without requiring Windows or PowerShell.
GitHub Create Pull Request
Azure Arc Deploy Azure Arc-enabled data services in Active Directory authentication - prerequisites ...icles/azure-arc/data/active-directory-prerequisites.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example Windows First
Summary
The documentation page demonstrates a notable Windows bias. All examples and instructions for creating and managing Active Directory objects rely exclusively on Windows tools (Active Directory Users and Computers GUI, PowerShell cmdlets). There are no Linux or cross-platform alternatives provided, and the only referenced guide for setting up a domain controller is Windows-specific. This creates friction for Linux/macOS users, as they cannot follow the steps without access to a Windows environment.
Recommendations
  • Include instructions for managing Active Directory objects using cross-platform tools such as ldapadd, ldapmodify, or Samba utilities.
  • Provide examples using Linux command-line tools (e.g., ldap-utils) for OU and user creation.
  • Reference guides for setting up Active Directory domain controllers on Linux (e.g., using Samba as an AD DC).
  • Clearly indicate which steps require Windows-only tools and suggest alternatives where possible.
  • Add parity in example ordering, showing Linux/macOS approaches alongside or before Windows examples.
GitHub Create Pull Request
Azure Arc Back up controller database .../articles/azure-arc/data/backup-controller-database.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides SQL Server connectivity examples using Powershell syntax and Windows-style command lines (e.g., sqlcmd invocation), without offering equivalent Linux/macOS shell examples. Powershell is used for kubectl exec commands, and no mention is made of Linux-specific tools or shell syntax. The order of examples and instructions implicitly favors Windows users, potentially creating friction for Linux/macOS users.
Recommendations
  • Provide Linux/macOS shell (bash/sh) examples alongside Powershell, especially for kubectl exec and sqlcmd invocations.
  • Clarify that sqlcmd and kubectl can be run from any OS, and provide OS-agnostic instructions where possible.
  • Explicitly mention installation and usage of sqlcmd on Linux/macOS, including any differences in path or invocation.
  • Avoid labeling command blocks as 'powershell' unless the syntax is truly Powershell-specific; use 'console' or 'bash' where appropriate.
  • Add notes or sections for Linux/macOS users, highlighting any OS-specific considerations.
GitHub Create Pull Request
Azure Arc Install Arc agent at scale for your VMware VMs ...arc/vmware-vsphere/enable-guest-management-at-scale.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation demonstrates a notable Windows bias. PowerShell is the only shell used in automation examples, and the helper script is presented for use in a PowerShell terminal with Windows Task Scheduler for cron jobs. There are no Linux shell (bash) or cron job examples, and Windows-centric tools and patterns (PowerShell, Task Scheduler, Group Policy) are mentioned before or instead of Linux equivalents. Linux-specific instructions are limited to a sudo configuration note, and Linux users are left to infer how to adapt Windows-centric steps.
Recommendations
  • Provide equivalent bash shell examples for running the helper script on Linux/macOS.
  • Include instructions for scheduling the script via Linux cron (crontab) rather than only Windows Task Scheduler.
  • Offer explicit Linux/macOS usage steps for the helper script, including permission and execution policy guidance.
  • Mention Linux-native automation tools (e.g., systemd timers, cron) alongside Windows tools.
  • Ensure parity in example order and detail for both Windows and Linux/macOS environments.
GitHub Create Pull Request
Azure Arc Deploy Active Directory-integrated SQL Managed Instance enabled by Azure Arc ...c/data/deploy-active-directory-sql-managed-instance.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation shows a moderate Windows bias. Windows tools and workflows (Active Directory Users and Computers, setspn, ktpass, PowerShell scripts) are mentioned first or exclusively in critical steps such as account creation and SPN registration. While Linux alternatives (adutil, ktutil, Bash scripts) are provided for keytab generation, the initial instructions and examples often assume Windows environments and tools, potentially creating friction for Linux/macOS users.
Recommendations
  • Provide explicit Linux/macOS instructions for all steps, especially for Active Directory account creation and SPN registration (e.g., using Samba tools like 'samba-tool' or 'ldapmodify').
  • List Linux tools and scripts before or alongside Windows equivalents, not after.
  • Include examples using Linux command-line utilities for DNS record creation and management.
  • Clarify which steps require Windows-only tools and offer workarounds or alternatives for Linux/macOS users.
  • Add a parity table summarizing which tools/scripts are available for each OS.
GitHub Create Pull Request
Azure Arc Deploy Active Directory integrated SQL Managed Instance enabled by Azure Arc using Azure CLI ...ta/deploy-active-directory-sql-managed-instance-cli.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation is focused on deploying Active Directory integrated SQL Managed Instance using Azure CLI, which is cross-platform. However, there is a notable Windows bias: Active Directory (AD) is a Windows-centric technology, and the documentation does not mention or provide guidance for Linux-based equivalents (such as using Samba for AD integration or Kerberos on Linux). All examples use Windows-style DNS names and AD accounts, and there is no discussion of Linux-specific setup, troubleshooting, or alternative patterns. There are no PowerShell-only examples, but the overall context assumes a Windows AD environment and omits Linux AD integration details.
Recommendations
  • Add guidance or references for integrating with Linux-based AD-compatible services (e.g., Samba, MIT Kerberos).
  • Include examples or troubleshooting steps for Linux environments, such as how to generate keytabs or configure AD accounts from Linux.
  • Clarify cross-platform requirements and limitations, especially for users deploying on Linux-based Kubernetes clusters.
  • Provide parity in documentation for Linux/macOS users, including any OS-specific caveats or configuration steps.
GitHub Create Pull Request
Azure Arc Tutorial – Deploy Active Directory connector in system-managed keytab mode ...eploy-system-managed-keytab-active-directory-connector.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page demonstrates Windows bias by referencing Windows-specific tools (e.g., 'netdom query fsmo' for identifying the Primary Domain Controller) without providing Linux/macOS alternatives. The only example for determining the PDC uses a Windows command, and no Linux/macOS method is mentioned. Windows terminology and patterns (NetBIOS, domain controller discovery) are presented first and exclusively, with no cross-platform guidance.
Recommendations
  • Provide Linux/macOS equivalents for Windows-only commands, such as using 'ldapsearch' or 'samba-tool' to discover the Primary Domain Controller.
  • Include examples or references for performing Active Directory-related tasks from non-Windows systems.
  • Add notes or sections clarifying how Linux/macOS administrators can obtain required AD information.
  • Ensure that all critical steps (e.g., domain controller discovery, account management) are documented for both Windows and Linux environments.
GitHub Create Pull Request
Azure Arc Features and Capabilities of SQL Managed Instance enabled by Azure Arc ...n/articles/azure-arc/data/managed-instance-features.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation lists several Windows-centric tools (SSMS, SQL Server Data Tools, SQL Server Profiler, SQL Server PowerShell) and highlights PowerShell scripting support as a manageability feature. Windows Authentication is explicitly called out as supported, while Linux/macOS equivalents (e.g., Bash scripting, cross-platform authentication) are not mentioned. Windows tools are listed before cross-platform options, and there are no Linux-specific examples or tool recommendations.
Recommendations
  • Add explicit mention and examples of Linux/macOS management options, such as Bash scripting, and clarify support for cross-platform authentication methods.
  • Include Linux-native tools (e.g., sqlcmd, Azure Data Studio on Linux) and provide parity in documentation for their usage.
  • Reorder tool lists to present cross-platform tools (Azure CLI, Azure Data Studio) before Windows-only tools.
  • Clarify PowerShell support on Linux (PowerShell Core) or provide Bash/CLI alternatives for common management tasks.
  • Document authentication options for non-Windows environments, such as Microsoft Entra ID or certificate-based authentication.
GitHub Create Pull Request
Azure Arc Migrate a database from SQL Server to SQL Managed Instance enabled by Azure Arc ...articles/azure-arc/data/migrate-to-managed-instance.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias by providing backup examples that use Windows file paths (e.g., C:\Backupfiles\test.bak) and omitting equivalent Linux/macOS examples (e.g., /home/user/test.bak). The instructions and code samples assume a Windows environment for local file operations, and do not mention or show how Linux/macOS users should perform these steps.
Recommendations
  • Add explicit Linux/macOS examples for backup file creation, using appropriate file paths (e.g., /home/user/test.bak).
  • Clarify that the backup process can be performed on both Windows and Linux, and provide platform-specific instructions where needed.
  • When showing kubectl cp usage, include Linux/macOS source file paths in examples.
  • Mention cross-platform tools (e.g., Azure Data Studio is available on Windows, Linux, and macOS) and provide installation links for all platforms.
  • Avoid showing Windows paths exclusively; present both formats side-by-side or note the difference.
GitHub Create Pull Request
Azure Arc Data collection and reporting | Azure Arc-enabled data services ...zure-arc/data/privacy-data-collection-and-reporting.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page focuses on Azure Arc-enabled data services data collection and reporting. While it is generally platform-neutral, there are subtle signs of Windows bias. For example, in the billing data section for Arc-enabled SQL Server, the JSON example includes 'osType': 'Windows', 'manufacturer': 'Microsoft', and 'model': 'Hyper-V', with no equivalent Linux example. There are no explicit Linux or macOS examples, nor are Linux-specific tools or patterns mentioned. The documentation does not provide parity for Linux environments in its examples or descriptions, which may create friction for non-Windows users.
Recommendations
  • Include Linux-based examples in the billing data section, such as 'osType': 'Linux', and common Linux VM models.
  • Add notes or examples for Linux/macOS environments wherever platform-specific properties are shown.
  • Clarify that the data collection and reporting process applies equally to Linux-based SQL Server instances, if applicable.
  • Mention Linux-compatible tools or commands (e.g., Bash, shell scripts) alongside Azure CLI and Kubernetes references.
  • Ensure that all JSON examples reflect both Windows and Linux scenarios where relevant.
GitHub Create Pull Request
Azure Arc What is Azure Arc-enabled VMware vSphere? ...lob/main/articles/azure-arc/vmware-vsphere/overview.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation page demonstrates a moderate Windows bias. Windows-specific management features (e.g., Windows Server management, Extended Security Updates) are highlighted, and Windows tools (PowerShell, Windows registry, etc.) are mentioned before or more prominently than Linux equivalents. Examples and links often default to Windows tabs or features, and Linux-specific instructions or parity are less visible or absent. PowerShell is listed as a primary automation tool, with less emphasis on Bash or Linux-native scripting. Some links and scenarios are Windows-centric, and Linux examples are missing or less detailed.
Recommendations
  • Ensure all automation and management examples include both Windows (PowerShell) and Linux (Bash, shell) equivalents.
  • Highlight Linux management features and parity (e.g., Linux VM extensions, Linux daemons, Linux update management) alongside Windows features.
  • Provide links and tabs for Linux-specific documentation where Windows tabs are present.
  • Explicitly mention Linux support in all relevant scenarios, especially in onboarding, configuration, and monitoring sections.
  • Include Linux-focused use cases and examples in the 'Next steps' and 'Supported scenarios' sections.
GitHub Create Pull Request
Azure Arc Rotate customer-managed keytab ...icles/azure-arc/data/rotate-customer-managed-keytab.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Powershell Heavy
Summary
The documentation exhibits Windows bias by referencing Windows-specific tools (ktpass.exe), providing a PowerShell script, and describing password rotation using Windows GUI tools (Server Manager, Active Directory Users and Computers). While a bash script is provided for Linux/macOS users, Windows tools and workflows are mentioned first and in more detail. There is no mention of Linux-native alternatives for Active Directory password changes, and the troubleshooting section assumes familiarity with Linux commands but does not provide parity for all steps.
Recommendations
  • Provide Linux/macOS equivalents for Active Directory password rotation, such as using 'samba-tool' or 'ldapmodify' for password changes.
  • Present bash and PowerShell scripts side-by-side, or alternate which is shown first, to avoid Windows-first ordering.
  • Explicitly mention which steps are platform-specific and provide guidance for both Windows and Linux/macOS administrators.
  • Include references to Linux-native tools for keytab management and Active Directory interaction.
  • Clarify which scripts and tools are required for each OS, and provide installation instructions if needed.
GitHub Create Pull Request
Azure Arc Verify Contributor Role for Edge RAG Preview Enabled by Azure Arc ...s/azure-arc/edge-rag/prepare-contributor-permission.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation provides only PowerShell/CLI examples for verifying contributor permissions, with no mention of Linux/macOS-specific shell usage or alternative commands. The use of PowerShell syntax and lack of explicit Linux/macOS instructions creates friction for non-Windows users.
Recommendations
  • Include equivalent bash/zsh examples for Linux/macOS users (e.g., show az CLI commands in a generic shell context).
  • Clarify that the az CLI commands work cross-platform and provide instructions for installing the Azure CLI on Linux/macOS.
  • Avoid using PowerShell-specific formatting unless necessary; use generic shell examples when possible.
  • Explicitly state platform compatibility for the commands shown.
GitHub Create Pull Request
Azure Arc Deploy the Edge RAG Extension ...t-docs/blob/main/articles/azure-arc/edge-rag/deploy.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation for deploying the Edge RAG extension provides Azure CLI instructions exclusively using PowerShell syntax and variable assignment, which is specific to Windows environments. There are no Bash or Linux/macOS shell examples, and the CLI section assumes a Windows/PowerShell context. This creates friction for Linux/macOS users who may not be familiar with PowerShell or its variable syntax.
Recommendations
  • Add equivalent Bash examples for all CLI commands, using Bash variable assignment and syntax.
  • Explicitly state that both PowerShell and Bash can be used, and provide tabs or sections for each.
  • Avoid using Windows-specific variable assignment (e.g., $var) in generic CLI instructions; use cross-platform syntax where possible.
  • Include notes or guidance for Linux/macOS users regarding any differences in command usage or prerequisites.
GitHub Create Pull Request
Azure Arc Install Networking and Observability Components for Edge RAG Preview Enabled by Azure Arc ...azure-arc/edge-rag/prepare-networking-observability.md
Medium Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation exclusively provides PowerShell-based examples and commands, assuming a Windows environment. There are no bash, shell, or Linux/macOS-specific instructions, and all command snippets use Windows-centric syntax and tools. This creates friction for Linux/macOS users who may need to adapt the instructions themselves.
Recommendations
  • Provide equivalent bash/shell command examples for Linux/macOS users alongside PowerShell examples.
  • Clarify which commands are OS-agnostic (e.g., az CLI, kubectl, helm) and which require adaptation.
  • Explicitly state platform requirements and offer guidance for non-Windows environments.
  • Reorder examples or present both Windows and Linux instructions in parallel to avoid Windows-first bias.
GitHub Create Pull Request
← Previous Page 7 of 18 Next →