Azure Arc

465
Total Pages
253
Linux-Friendly Pages
212
Pages with Bias
45.6%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

2334 issues found
Showing 26-50 of 2334 flagged pages
Azure Arc Sample - Enable GPU for AKS on Azure Arc ...lob/main/articles/azure-arc/edge-rag/enable-gpu-aks.md
High Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation provides only a PowerShell script using Windows-specific cmdlets and tools (e.g., Get-PnpDevice, pnputil, Dismount-VMHostAssignableDevice), with no mention of Linux or cross-platform alternatives. All instructions and examples are tailored to Windows environments, creating friction for Linux/macOS users who may be running AKS on Azure Arc on non-Windows hosts.
Recommendations
  • Add equivalent instructions or scripts for Linux hosts, using bash and Linux-native tools (e.g., lspci, nvidia-smi, modprobe, etc.) for GPU detection and driver management.
  • Clarify in the prerequisites or introduction if the procedure is only supported on Windows-based Azure Local hosts, or provide guidance for Linux/macOS users.
  • If Windows is a hard requirement, explicitly state this at the top of the page to prevent confusion.
  • Provide links or references to official Azure Arc documentation for Linux GPU enablement if available.
GitHub Create Pull Request
Azure Arc Connect machines at scale with a Configuration Manager custom task sequence ...c/servers/onboard-configuration-manager-custom-task.md
High Priority View Details →
Scanned: 2026-01-14 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 is heavily focused on Windows environments, specifically using Microsoft Configuration Manager (SCCM) and Windows Installer (.msi) packages. All examples and instructions are tailored for Windows, with exclusive use of PowerShell scripts and Windows-specific tooling. There are no references to Linux or macOS equivalents, nor guidance for onboarding non-Windows machines at scale using similar automation or deployment strategies.
Recommendations
  • Clarify early in the documentation that the process described is only applicable to Windows endpoints managed by Configuration Manager, if that is the intent.
  • If onboarding Linux servers at scale is supported, provide parallel instructions for Linux environments, such as using shell scripts, Linux package managers (deb/rpm), and automation tools like Ansible or Puppet.
  • Include references or links to documentation for onboarding non-Windows machines to Azure Arc at scale, if available.
  • Explicitly state any platform limitations to set expectations for cross-platform users.
GitHub Create Pull Request
Azure Arc Remove your VMware vCenter environment from Azure Arc ...e-arc/vmware-vsphere/remove-vcenter-from-arc-vmware.md
High Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation demonstrates a Windows bias in the section about running the deboarding script: only PowerShell instructions for Windows are provided, with no Linux/macOS equivalent. The script appears to be a PowerShell script (.ps1), and there are no instructions or guidance for running the script from Linux/macOS. Additionally, the Windows instructions are presented first and exclusively, while Linux users are left without clear guidance for this critical step.
Recommendations
  • Provide instructions for running the deboarding script from Linux/macOS, if supported (e.g., via PowerShell Core, Azure CLI, or Bash).
  • If the script is Windows-only, explicitly state this limitation and offer alternative manual steps for Linux/macOS users.
  • Consider offering a cross-platform version of the deboarding script (e.g., Bash or Python) or document how to use PowerShell Core on Linux/macOS.
  • Present manual removal steps in a way that is platform-neutral, ensuring Linux/macOS users can follow along without friction.
GitHub Create Pull Request
Azure Arc Onboarding Scripts for Workload Orchestration ...azure-arc/workload-orchestration/onboarding-scripts.md
High Priority View Details →
Scanned: 2026-01-14 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on Windows and PowerShell, with all onboarding script examples and instructions given exclusively for PowerShell (.ps1) scripts and Windows-specific tools like 'winget'. There are no Linux/macOS shell script equivalents, nor are there instructions for running these scripts on non-Windows platforms. The use of Windows-first tools and lack of cross-platform guidance creates friction for Linux/macOS users.
Recommendations
  • Provide equivalent Bash/shell script examples for Linux/macOS users, or clarify if the scripts are Windows-only.
  • Replace or supplement 'winget' installation instructions with cross-platform alternatives (e.g., apt, yum, brew, or direct download links).
  • Explicitly state platform requirements for the onboarding scripts (e.g., 'These scripts require Windows/PowerShell'), or provide cross-platform versions.
  • Add a section describing how Linux/macOS users can onboard, including any prerequisites and script execution steps.
  • If PowerShell Core (pwsh) is supported on Linux/macOS, clarify compatibility and provide usage instructions.
GitHub Create Pull Request
Azure Arc Troubleshoot Azure Arc-enabled servers networking issues .../articles/azure-arc/servers/troubleshoot-networking.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation focuses exclusively on troubleshooting TLS configuration issues for Windows servers. All examples, commands, and procedures use Windows-specific tools (PowerShell, Group Policy, Registry Editor), with no mention of Linux or macOS equivalents. There are no instructions or guidance for Linux-based Arc-enabled servers, leaving Linux users without actionable steps for similar networking issues.
Recommendations
  • Add a dedicated section for troubleshooting TLS/cipher suite issues on Linux servers, including relevant commands (e.g., using openssl, update-crypto-policy, or editing configuration files like /etc/ssl/openssl.cnf).
  • Provide cross-platform parity by including both Windows and Linux/macOS examples for checking and enabling cipher suites.
  • Clarify which troubleshooting steps apply only to Windows and direct Linux/macOS users to appropriate resources or documentation.
  • List Linux troubleshooting steps before or alongside Windows steps to avoid implicit prioritization.
GitHub Create Pull Request
Azure Arc Recover from accidental deletion of resource bridge VM ...em-center-virtual-machine-manager/disaster-recovery.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation provides recovery instructions exclusively for Windows, using a downloadable PowerShell script. There are no examples, scripts, or guidance for Linux or macOS users, nor any mention of equivalent Linux tooling or steps. The section is explicitly titled 'Recover Arc resource bridge from a Windows machine', and no alternatives are offered.
Recommendations
  • Provide equivalent recovery instructions for Linux/macOS, including a Bash or Python script.
  • Clarify whether the recovery process is possible from non-Windows platforms, and if not, explain the limitation.
  • If the PowerShell script is required, document how to run it on Linux/macOS (e.g., via PowerShell Core), or provide a cross-platform version.
  • Add Linux/macOS-specific prerequisites and troubleshooting steps.
GitHub Create Pull Request
Azure Arc Switch to the new version of Arc-enabled SCVMM ...ual-machine-manager/switch-to-the-new-version-scvmm.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily oriented towards Windows environments, referencing System Center Virtual Machine Manager (SCVMM), which is a Windows-only tool. All examples and instructions assume the use of Windows-based management servers and agents. References to agent management link only to Windows-specific instructions, with no mention of Linux or macOS equivalents or scenarios. There is no guidance for users managing Linux VMs or using non-Windows platforms.
Recommendations
  • Clarify that SCVMM is a Windows-only tool and explicitly state platform limitations at the beginning.
  • If Azure Arc supports Linux VMs or management from Linux/macOS, provide parallel instructions and examples for those platforms.
  • Include links or references to Linux agent management documentation where applicable.
  • Add notes or sections for users who may be managing mixed environments, outlining any differences or additional steps for Linux VMs.
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
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page demonstrates a strong Windows bias by exclusively referencing Windows-specific tools (Active Directory Users and Computers MMC, PowerShell), providing only Windows-based examples and screenshots, and omitting any guidance for Linux or cross-platform environments. There are no instructions for performing equivalent tasks on Linux (e.g., using Samba, ldap-utils, or cross-platform AD management tools), nor is there mention of how to interact with AD from non-Windows systems.
Recommendations
  • Add instructions and examples for managing Active Directory objects from Linux systems, such as using ldapadd, ldapmodify, or Samba tools.
  • Include cross-platform PowerShell (PowerShell Core) examples and clarify any differences when running on Linux/macOS.
  • Reference Azure Active Directory and hybrid scenarios where AD management may be performed from cloud or Linux-based environments.
  • Provide links or guidance for setting up and managing AD from Linux, including open-source tools and best practices.
  • Reorder examples so that cross-platform or Linux methods are presented alongside or before Windows-specific instructions.
GitHub Create Pull Request
Azure Arc Configure Machine to Manage Arc-Enabled Kubernetes Cluster ...rticles/azure-arc/edge-rag/configure-driver-machine.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily biased towards Windows, providing only a PowerShell script and instructions for configuring a Windows machine. All examples, download links, and environment variable manipulations are Windows-specific, with no mention of Linux or macOS equivalents. Linux users are left without guidance or scripts to perform the same setup.
Recommendations
  • Provide equivalent setup instructions and sample scripts for Linux/macOS, using Bash or shell scripting.
  • Include download links for kubectl, Helm, and Azure CLI for Linux/macOS.
  • Document environment variable and PATH updates for Linux/macOS (e.g., modifying ~/.bashrc or ~/.profile).
  • Clearly state cross-platform requirements and offer parity in step-by-step instructions.
  • Add a section or note indicating how Linux/macOS users can adapt the process.
GitHub Create Pull Request
Azure Arc Sample - Enable GPU for AKS on Azure Arc ...lob/main/articles/azure-arc/edge-rag/enable-gpu-aks.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation provides only a Windows PowerShell script for enabling GPU on AKS via Azure Arc, relying heavily on Windows-specific cmdlets and tools (e.g., Get-PnpDevice, pnputil, Restart-Service). No Linux or cross-platform alternatives are mentioned, and the instructions assume a Windows environment throughout.
Recommendations
  • Add equivalent instructions and sample scripts for Linux hosts, using bash and Linux-native tools (e.g., lspci, lsmod, modprobe, systemctl).
  • Clarify OS requirements and explicitly state if the procedure is Windows-only, or provide guidance for Linux/macOS users.
  • If Azure Arc supports Linux nodes, document the GPU enablement workflow for those platforms.
  • Present examples for both Windows and Linux side-by-side, or indicate which steps are OS-specific.
GitHub Create Pull Request
Azure Arc Cloud-native licensing and cost management with Azure Arc-enabled servers ...-arc/servers/cloud-native/licensing-cost-management.md
High Priority View Details →
Scanned: 2026-01-13 00:00
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 and scenarios centered on Windows environments. There is no mention of Linux licensing, Linux server management, or equivalent Linux tools. Windows-specific tools and patterns (e.g., Azure Update Manager, ESUs for Windows Server) are referenced throughout, and Windows scenarios are presented first and exclusively.
Recommendations
  • Add sections or examples describing how Azure Arc licensing and cost management applies to Linux servers, including any differences or limitations.
  • Include Linux-specific licensing scenarios, such as integration with RHEL, SUSE, or other commercial Linux distributions, and how pay-as-you-go or subscription models work for those platforms.
  • Mention Linux-compatible update and patch management tools available via Azure Arc, and clarify whether similar centralized billing and compliance features exist for Linux workloads.
  • Ensure that examples and guidance are balanced between Windows and Linux, or explicitly state if features are Windows-only.
GitHub Create Pull Request
Azure Arc Customer intent: "As a system administrator managing Azure Arc-enabled servers, I want to understand the required endpoints for Extended Security Updates so that I can ensure proper connectivity and compliance during installation and updates." ...azure-arc/servers/includes/esu-network-requirements.md
High Priority View Details →
Scanned: 2026-01-13 00:00
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 SQL Server 2012, with all endpoint descriptions referencing Windows installation packages and Extended Security Updates for Windows products. There are no examples, instructions, or endpoint references for Linux or macOS systems, nor any mention of Linux equivalents or considerations. The documentation implicitly assumes a Windows environment and does not address cross-platform scenarios.
Recommendations
  • Clarify whether Extended Security Updates via Azure Arc are available for Linux servers, and if so, include relevant endpoints and instructions.
  • If Linux is not supported, explicitly state this to avoid confusion for non-Windows users.
  • If Linux support is planned, provide parity in documentation with Linux-specific examples, endpoints, and installation/update instructions.
  • Consider adding a section or note about cross-platform applicability, including any limitations or differences for Linux/macOS users.
GitHub Create Pull Request
Azure Arc Connect machines at scale with a Configuration Manager custom task sequence ...c/servers/onboard-configuration-manager-custom-task.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily biased toward Windows environments. All examples, instructions, and screenshots are based on Windows tools (Configuration Manager, .msi installers, PowerShell scripts). There is no mention of Linux/macOS equivalents, nor guidance for deploying the Connected Machine Agent at scale on non-Windows platforms. The use of PowerShell and .msi files further excludes Linux users, and the workflow is entirely centered on Windows-specific deployment patterns.
Recommendations
  • Add a dedicated section for Linux/macOS onboarding at scale, including supported automation tools (e.g., Ansible, shell scripts, Linux package managers).
  • Provide examples for downloading and installing the Connected Machine Agent on Linux (e.g., using .deb/.rpm packages, wget/curl commands).
  • Include sample task automation scripts for Linux (e.g., Bash, Python) and show how to connect to Azure Arc from Linux using azcmagent.
  • Clarify whether Configuration Manager supports Linux/macOS endpoints for this scenario, or recommend alternative management solutions for non-Windows platforms.
  • Present both Windows and Linux workflows side-by-side or in parallel sections to ensure parity.
GitHub Create Pull Request
Azure Arc REST API Requests for the Run Command on Azure Arc-enabled Servers (Preview) ...ob/main/articles/azure-arc/servers/run-command-rest.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page is heavily biased towards Windows. All example scenarios, scripts, and references are specific to Windows Server (e.g., Windows Server 2012/R2, PowerShell cmdlets like New-NetFirewallRule). There are no examples or guidance for Linux or macOS servers, nor are Linux shell scripts or tools mentioned. Even instructions for generating SAS tokens reference PowerShell tools (New-AzStorageBlobSASToken) exclusively.
Recommendations
  • Add example scenarios for Linux Arc-enabled servers, including REST API payloads with bash or shell scripts (e.g., using iptables or ufw for firewall rules).
  • Explicitly mention Linux support in the introduction and prerequisites, clarifying any OS-specific limitations.
  • Provide Linux/macOS equivalents for SAS token generation (e.g., using Azure CLI az storage blob generate-sas).
  • Alternate examples between Windows and Linux, or present both side-by-side.
  • Reference Linux documentation and tools in the 'Related content' section.
GitHub Create Pull Request
Azure Arc How to troubleshoot delivery of Extended Security Updates for Windows Server 2012 through Azure Arc ...-arc/servers/troubleshoot-extended-security-updates.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation is exclusively focused on troubleshooting Extended Security Updates for Windows Server 2012 through Azure Arc, with all examples, commands, and instructions tailored to Windows environments. Only Windows Server operating systems are mentioned as eligible, and all troubleshooting steps (such as certificate installation and error resolution) use Windows-specific tools (certutil, PowerShell). No Linux or macOS equivalents, examples, or considerations are provided, and Windows terminology and tools are used throughout.
Recommendations
  • Explicitly state that the process and troubleshooting steps are only applicable to Windows Server 2012/2012 R2, and clarify if Linux/macOS are not supported.
  • If Linux or macOS Arc-enabled servers could be relevant, provide troubleshooting steps, eligibility criteria, and examples for those platforms.
  • Where possible, mention cross-platform alternatives or note the absence of Linux/macOS support for ESU delivery.
  • Add a section addressing common questions for non-Windows users (e.g., 'Can I use ESU with Linux Arc-enabled servers?').
GitHub Create Pull Request
Azure Arc Azure built-in roles for Azure Arc-enabled SCVMM ...ystem-center-virtual-machine-manager/built-in-roles.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
🔧 Windows Tools
Summary
The documentation is focused on Azure Arc-enabled SCVMM, which is inherently a Windows-centric technology (System Center Virtual Machine Manager). All role definitions and permissions revolve around SCVMM resources and actions, which are only available on Windows. There are no examples, instructions, or references to Linux or macOS tools, nor is there any mention of how these roles or resources could be managed or accessed from non-Windows platforms.
Recommendations
  • Explicitly state the Windows-only nature of SCVMM and its management tools at the top of the documentation.
  • If any Azure Arc management tasks can be performed from Linux/macOS (e.g., via Azure CLI, REST API), provide examples or links.
  • Clarify which aspects (if any) of Azure Arc-enabled SCVMM can be accessed or managed cross-platform.
  • Add a section for Linux/macOS users explaining limitations and possible alternatives for managing virtual machines in hybrid environments.
GitHub Create Pull Request
Azure Arc Enable SCVMM inventory resources in Azure Arc center ...al-machine-manager/enable-scvmm-inventory-resources.md
High Priority View Details →
Scanned: 2026-01-13 00:00
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-only management tool, and provides instructions only for enabling SCVMM resources in Azure via the Azure portal. There are no references to Linux or cross-platform alternatives, and all examples and screenshots are based on Windows-centric tools and workflows.
Recommendations
  • Clarify early in the documentation that SCVMM is a Windows-only tool, and that these instructions are specific to environments using SCVMM.
  • Provide links or references to equivalent workflows for Linux-based virtualization platforms (such as VMware vSphere, KVM, or Hyper-V on Linux) if supported by Azure Arc.
  • If Azure Arc supports onboarding Linux VMs or resources, include a 'Linux and cross-platform resources' section with relevant instructions or links.
  • Consider adding a comparison table showing supported platforms and management tools, highlighting where Linux users should look for guidance.
GitHub Create Pull Request
Azure Arc Enable VM CRUD and power cycle operational ability in an SCVMM managed Arc-enabled server machine ...rtual-machine-manager/enable-virtual-hardware-scvmm.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily focused on SCVMM (System Center Virtual Machine Manager), a Windows-only virtualization management tool. All operational steps, terminology, and screenshots are based on Windows tools and Azure portal integration with SCVMM. There are no Linux or macOS equivalents, nor are alternative management patterns for non-Windows environments discussed.
Recommendations
  • Clarify in the prerequisites and introduction that SCVMM is a Windows-only tool and that the instructions are not applicable to Linux-based virtualization platforms.
  • Provide links or references to equivalent Azure Arc onboarding and VM management documentation for Linux-based hypervisors (e.g., KVM, VMware on Linux).
  • If possible, include a comparison table or section outlining how similar CRUD and power cycle operations can be performed on Linux-managed VMs using Azure Arc.
  • Explicitly state the platform limitations to help Linux/macOS users quickly determine applicability.
GitHub Create Pull Request
Azure Arc Troubleshoot SCVMM-specific Azure Arc resource bridge deployment errors ...m-center-virtual-machine-manager/troubleshoot-scvmm.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation is heavily focused on troubleshooting errors specific to SCVMM (System Center Virtual Machine Manager), a Windows-only tool. All error codes and troubleshooting steps reference Windows technologies (e.g., PSSession, SCVMMServer), with no mention of Linux or macOS equivalents, nor any cross-platform guidance. There are no Linux/macOS examples or alternative instructions.
Recommendations
  • Clarify early in the documentation that SCVMM is a Windows-only technology, and that the troubleshooting steps are relevant only for Windows environments.
  • If Azure Arc resource bridge supports Linux-based resource managers, provide equivalent troubleshooting steps for those platforms.
  • Where possible, include cross-platform notes or links to Linux/macOS troubleshooting guides for Azure Arc resource bridge.
  • Explicitly state platform requirements and limitations to avoid confusion for non-Windows users.
GitHub Create Pull Request
Azure Arc Upgrade the Azure Arc resource bridge ...l-machine-manager/upgrade-azure-arc-resource-bridge.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation is heavily oriented towards Windows environments, specifically SCVMM (System Center Virtual Machine Manager), and assumes the use of Windows servers and workstations. All examples and instructions reference Windows tools and patterns (e.g., VHDX, SCVMM server, Azure Portal), with no mention of Linux or macOS equivalents, nor guidance for users operating outside of Windows. There are no Linux/macOS-specific instructions or troubleshooting steps.
Recommendations
  • Clarify platform requirements early in the document, explicitly stating if the upgrade process is only supported on Windows/SCVMM environments.
  • If possible, provide instructions or notes for Linux/macOS users, such as how to use the Azure CLI and manage configuration files on those platforms.
  • Include examples of commands run from Linux/macOS terminals, or specify any limitations for non-Windows users.
  • Mention alternative virtualization formats (e.g., VHD, VMDK) or tools if supported, or clarify that only VHDX/SCVMM is supported.
  • Add troubleshooting and prerequisite sections relevant to Linux/macOS environments if applicable.
GitHub Create Pull Request
Azure Arc Remove your VMware vCenter environment from Azure Arc ...e-arc/vmware-vsphere/remove-vcenter-from-arc-vmware.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation shows a notable Windows bias in the deboarding script section, where only Windows/PowerShell instructions are provided for running the cleanup script. The script is described as a PowerShell script, and all usage examples and troubleshooting notes are Windows/PowerShell-centric. There is no mention of how to run the script on Linux or macOS, nor are alternative instructions or parity examples given for non-Windows platforms. The agent uninstall instructions are well-balanced between Windows and Linux, but the critical deboarding step is Windows-only.
Recommendations
  • Provide instructions for running the deboarding script on Linux/macOS, including prerequisites (e.g., PowerShell Core, Azure CLI) and any platform-specific steps.
  • If the script is Windows-only, offer an equivalent Bash or cross-platform script, or document manual cleanup steps for Linux/macOS users.
  • Clearly state platform requirements and limitations for the deboarding script at the start of the section.
  • Add troubleshooting notes for Linux/macOS environments, similar to the PowerShell ISE note for Windows.
GitHub Create Pull Request
Azure Arc Diagnostics of Edge-Related Logs and Errors in Workload Orchestration .../azure-arc/workload-orchestration/diagnose-problems.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page exhibits a strong Windows bias. All command-line examples and automation scripts are provided exclusively in PowerShell, with no Bash, shell, or Linux/macOS equivalents. File paths in JSON templates use Windows-style backslashes and drive letters (e.g., C:\, E:\), and script instructions reference PowerShell scripts (.ps1) only. There is no mention of how to perform these tasks on Linux or macOS, nor are alternative shell commands or cross-platform notes provided.
Recommendations
  • Provide Bash or shell script equivalents for all PowerShell commands and scripts, especially for az CLI usage.
  • Use platform-agnostic file path examples or show both Windows and Linux/macOS path formats.
  • Explicitly note any platform requirements or limitations for provided scripts, and offer guidance for Linux/macOS users.
  • Include instructions for running automation tasks on Linux/macOS, such as using shell scripts (.sh) or direct az CLI commands.
  • Add cross-platform compatibility notes for JSON templates and configuration files.
GitHub Create Pull Request
Azure Arc Onboarding Scripts for Workload Orchestration ...azure-arc/workload-orchestration/onboarding-scripts.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation is heavily biased towards Windows, with all onboarding scripts and examples provided only in PowerShell (.ps1) format. Prerequisites use Windows-specific tools (winget), and there are no Bash, shell, or Linux/macOS equivalents or instructions. All example commands and instructions assume a Windows environment, making it difficult for Linux/macOS users to follow or execute the onboarding process without significant adaptation.
Recommendations
  • Provide equivalent Bash/shell scripts for infra and cm onboarding, or document how to run the PowerShell scripts on Linux/macOS (e.g., via pwsh).
  • Include Linux/macOS installation instructions for prerequisites (e.g., use apt, yum, brew for Azure CLI and kubectl, instead of winget).
  • Offer examples and command syntax for both Windows (PowerShell) and Linux/macOS (Bash) side-by-side.
  • Explicitly state cross-platform requirements and limitations, and link to guidance for running PowerShell scripts on non-Windows platforms.
  • Clarify whether the scripts are compatible with PowerShell Core (pwsh) on Linux/macOS, and provide troubleshooting tips for non-Windows environments.
GitHub Create Pull Request
Azure Arc Troubleshooting for Workload Orchestration ...es/azure-arc/workload-orchestration/troubleshooting.md
High Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The troubleshooting documentation for workload orchestration is heavily biased toward Windows and PowerShell usage. Most command-line examples (especially in critical troubleshooting sections) use PowerShell syntax and Windows-specific patterns, with little to no equivalent Bash or Linux shell examples. Windows tools and conventions (such as PowerShell variables, ConvertTo-Json, Out-File, and [Convert]::ToBase64String) are used exclusively, and Linux alternatives are not mentioned. Only in the 'service groups' section are Bash examples provided, and even there, PowerShell is shown first in some places. This creates friction for Linux/macOS users attempting to follow the troubleshooting steps.
Recommendations
  • Provide Bash/Linux shell equivalents for all PowerShell commands, especially in troubleshooting steps.
  • Replace or supplement Windows-specific tools (e.g., ConvertTo-Json, Out-File) with cross-platform alternatives (e.g., jq, echo, cat, base64).
  • Ensure variable syntax is compatible with Bash (e.g., $var vs. ${var}).
  • Clearly indicate which commands are platform-specific and offer alternatives or notes for Linux/macOS users.
  • Where possible, use platform-neutral Azure CLI commands and avoid PowerShell-only constructs.
  • Present Bash/Linux examples before or alongside PowerShell examples to avoid implicit prioritization.
GitHub Create Pull Request
Azure Arc Tutorial – Deploy Active Directory connector in system-managed keytab mode ...eploy-system-managed-keytab-active-directory-connector.md
High Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page exhibits Windows bias by referencing Windows-specific tools (e.g., 'netdom query fsmo' to find the primary domain controller) without providing Linux or cross-platform alternatives. The only example for discovering domain controller roles is a Windows command, and there is no mention of how to perform equivalent tasks from Linux or other platforms. The documentation also assumes familiarity with Windows/Active Directory concepts and does not provide parity for Linux administrators.
Recommendations
  • Provide equivalent Linux-based commands or procedures for discovering Active Directory domain controller roles, such as using 'ldapsearch' or 'samba-tool'.
  • When referencing Windows tools, also mention cross-platform or open-source alternatives where possible.
  • Add explicit examples or notes for Linux environments, especially for tasks like querying AD information, managing keytabs, and interacting with AD from non-Windows systems.
  • Clarify any platform-specific requirements or limitations, and ensure instructions are inclusive of both Windows and Linux administrators.
GitHub Create Pull Request
← Previous Page 2 of 94 Next →