← Back to Dashboard
222
Pages Scanned
47
Pages Flagged
222
Changed Pages
21.2%
% Pages Flagged

Live Progress

🔴 Connecting...
100%
Phase: discovery
Processing: Initializing...
Activity Feed
00:00:08 Scan started

Scan Information

Started At: 2026-02-13 00:00:08

Finished At: In Progress

Status: in_progress

Target Repo: Azure Management

Current Phase: discovery

Files Queued: 222

Files Completed: 222

Problematic Pages

50 issues found
Azure Arc Install client tools ...b/main/articles/azure-arc/data/install-client-tools.md
Medium 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 installation instructions for client tools across platforms, but Windows is often mentioned first or receives special notes. For example, kubectl installation links list Windows first, and curl installation provides a Windows link but only mentions 'Linux: install curl package' without a link. There are PowerShell-specific notes (e.g., curl alias) and guidance for Windows cmd.exe, but no equivalent Linux/macOS shell guidance. Linux/macOS users may need to infer steps or search for links themselves.
Recommendations
  • Provide explicit installation links for curl on Linux and macOS, similar to Windows.
  • When listing installation links for tools, rotate or randomize the order, or list all platforms equally (e.g., Windows | Linux | macOS).
  • Add notes for Linux/macOS shell usage where PowerShell/cmd.exe notes are given (e.g., for curl or kubectl).
  • Ensure that all examples and guidance are provided for Linux/macOS as well as Windows, not just referenced or implied.
GitHub Create Pull Request
Azure Arc Clean-Up Script for Workload Orchestration ...es/azure-arc/workload-orchestration/clean-up-script.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation exclusively provides instructions and examples for running a PowerShell script (RGCleanScript.ps1) to clean up Azure Arc workload orchestration resources. There are no examples or guidance for Linux/macOS users, such as running the script with PowerShell Core on those platforms or providing Bash/CLI alternatives. The documentation assumes the use of Windows tools and does not mention cross-platform compatibility.
Recommendations
  • Clarify whether RGCleanScript.ps1 is compatible with PowerShell Core on Linux/macOS. If so, provide explicit instructions for running the script on those platforms.
  • If the script is Windows-only, offer an alternative clean-up method for Linux/macOS users, such as an Azure CLI or Bash script.
  • Add a note about platform compatibility and prerequisites for running the script.
  • Include examples for Linux/macOS users, such as running PowerShell scripts via pwsh or using Azure CLI commands for resource deletion.
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 →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation is generally Linux-focused, but it uses Windows-centric tools (Invoke-AksEdgeNodeCommand) for Linux node configuration, and does not provide native Linux shell/SSH alternatives. This creates friction for Linux/macOS users who may not have access to PowerShell or Windows tools.
Recommendations
  • Provide native Linux shell/SSH command examples for sysctl configuration (e.g., using ssh or direct shell access).
  • Clarify whether Invoke-AksEdgeNodeCommand is available cross-platform or suggest alternatives for Linux/macOS users.
  • Add explicit instructions for editing aksedge-config.json using Linux text editors (e.g., nano, vim) instead of Notepad.
  • Ensure all steps can be completed from a Linux/macOS environment without requiring Windows tools.
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 →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation page demonstrates a moderate Windows bias. Windows tools (SQL Server Management Studio, Notepad, OneNote) are mentioned exclusively, and backup examples use Windows file paths (C:\Backupfiles\test.bak) without Linux/macOS equivalents. Instructions for creating backups and copying files into pods show Windows examples first and do not provide Linux/macOS alternatives for file paths or tools. There is no explicit guidance for Linux users on how to perform equivalent tasks (e.g., using Azure Data Studio, specifying Linux file paths, or using Linux-native editors).
Recommendations
  • Provide Linux/macOS equivalents for backup file paths (e.g., /home/user/backup/test.bak) in SQL commands and kubectl cp examples.
  • Mention cross-platform tools such as Azure Data Studio alongside SQL Server Management Studio, and clarify that Visual Studio Code is available on all platforms.
  • Suggest Linux/macOS alternatives for saving SAS tokens (e.g., gedit, nano, TextEdit) instead of only Notepad/OneNote.
  • Explicitly state that all steps can be performed on Linux/macOS and highlight any platform-specific considerations.
  • Add notes or examples for Linux/macOS users in sections where Windows tools or conventions are referenced.
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 →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation page lists several Windows-centric tools (SSMS, SQL Server Data Tools, SQL Server Profiler, SQL Server PowerShell) and mentions PowerShell scripting support as a manageability feature. While Azure CLI and VS Code are included, there is a notable emphasis on Windows-native tools and PowerShell, with no explicit mention of Linux/macOS alternatives or parity for scripting and management tasks.
Recommendations
  • Explicitly mention cross-platform tools such as Azure Data Studio, which runs on Windows, Linux, and macOS.
  • Clarify PowerShell scripting support: note that PowerShell Core is cross-platform, and provide examples or links for Linux/macOS usage.
  • Add examples or references for using Azure CLI and VS Code extensions on Linux/macOS.
  • Include guidance for Linux/macOS users on managing SQL Managed Instance enabled by Azure Arc, such as using containerized tools or relevant open-source alternatives.
GitHub Create Pull Request
Azure Arc Customer intent: "As a network administrator, I want to configure outbound and inbound connectivity settings for the appliance VM and management machine, so that I can ensure smooth communication and functionality for the Arc resource bridge." ...e-arc/resource-bridge/includes/network-requirements.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 both Windows and Linux-related endpoints, but there is a notable Windows bias: Windows NTP server ('time.windows.com') is mentioned specifically, and several endpoints reference Windows in their names (e.g., 'login.windows.net', 'servicebus.windows.net'). Windows-specific tools and services (such as Azure CLI installer download, Windows NTP, and diagnostic data from Windows) are referenced, while Linux equivalents (e.g., Linux NTP servers) are not mentioned or explained. The ordering of examples and notes often puts Windows endpoints first or exclusively, with Linux details only briefly referenced (e.g., 'Download Linux installation package' for packages.microsoft.com).
Recommendations
  • Explicitly mention Linux NTP server options (e.g., 'ntp.ubuntu.com', 'pool.ntp.org') alongside 'time.windows.com', and clarify when Windows NTP is required versus when Linux NTP is supported.
  • For endpoints and services that are cross-platform (e.g., Azure CLI), clarify installation steps or requirements for both Windows and Linux management machines.
  • Add notes or examples for Linux-based management machines and appliance VMs, especially where Windows-specific endpoints or tools are referenced.
  • Ensure Linux-related endpoints and tools are presented with equal prominence and detail as Windows ones.
  • Where diagnostic data is referenced as 'from Windows', clarify if Linux appliance VMs also send diagnostic data and provide relevant endpoints.
GitHub Create Pull Request
Azure Arc Troubleshoot Azure Arc resource bridge issues ...re-arc/resource-bridge/troubleshoot-resource-bridge.md
Medium 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 troubleshooting guidance for Azure Arc resource bridge, which is a cross-platform solution. However, there are several instances of Windows bias: PowerShell and Windows command-line examples are given for troubleshooting network issues (e.g., Invoke-WebRequest, Resolve-DnsName, ping), and Windows paths are referenced in error messages. Linux equivalents (such as curl, dig, or nslookup) are not provided alongside these examples. Additionally, Windows tools and terminology (e.g., RDP, Windows folder paths) are mentioned before or instead of Linux/macOS alternatives. While some Linux-specific errors (GLIBC version) are addressed, overall, Linux/macOS users may experience friction due to the lack of parity in troubleshooting steps and examples.
Recommendations
  • Provide Linux/macOS equivalents for all PowerShell and Windows command-line examples (e.g., curl for Invoke-WebRequest, dig/nslookup for Resolve-DnsName).
  • Include troubleshooting steps and commands for Linux/macOS environments wherever Windows-specific instructions are given.
  • Clarify that the management machine can be Windows, Linux, or macOS, and specify any OS-specific requirements or limitations.
  • Add Linux/macOS file path examples and permissions troubleshooting alongside Windows paths.
  • Ensure error messages and troubleshooting steps reference both Windows and Linux/macOS environments equally.
GitHub Create Pull Request
Azure Arc Manage and maintain the Azure Connected Machine agent ...s/blob/main/articles/azure-arc/servers/manage-agent.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation provides comprehensive coverage for both Windows and Linux platforms, including installation, upgrade, uninstall, and proxy configuration. However, there are several areas where Windows bias is evident: Windows examples and instructions are often presented first; Windows-specific tools and infrastructure (such as Microsoft Update, Group Policy, Configuration Manager, WSUS) are described in detail, while Linux equivalents are not discussed; PowerShell is heavily used for scripting and automation, with no Linux shell script equivalents for tasks like cleaning up stale resources.
Recommendations
  • Alternate the order of Windows and Linux sections so Linux instructions are not always second.
  • Provide equivalent Linux shell scripts (e.g., Bash) for automation tasks such as cleaning up stale Arc-enabled servers.
  • Add more detail about Linux update infrastructure (e.g., using unattended-upgrades, cron jobs, or configuration management tools like Ansible or Puppet) for agent updates.
  • Where Windows-specific tools are discussed (e.g., Group Policy, WSUS), briefly mention Linux alternatives or clarify that these are Windows-only.
  • Ensure parity in troubleshooting and management examples for both platforms.
GitHub Create Pull Request
Azure Arc Enable VM Extensions Using Azure Resource Manager Template ...les/azure-arc/servers/manage-vm-extensions-template.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides deployment instructions exclusively using Azure PowerShell commands, with no equivalent Azure CLI or Bash examples. All deployment steps use PowerShell syntax, which is native to Windows but available on Linux/macOS only if PowerShell is installed. While ARM template samples are provided for both Linux and Windows VM extensions, the deployment workflow is Windows-centric. Additionally, PowerShell examples are presented before mentioning Azure CLI as an alternative in the 'Related content' section.
Recommendations
  • Add Azure CLI deployment examples alongside PowerShell commands, especially for template deployment (e.g., az deployment group create).
  • Explicitly note that PowerShell Core can be used on Linux/macOS, and provide Bash/CLI alternatives where possible.
  • Consider showing Azure CLI examples first or in parallel with PowerShell to avoid Windows-first bias.
  • Clarify prerequisites for PowerShell usage on non-Windows platforms.
GitHub Create Pull Request
Azure Arc Azure Arc resource bridge system requirements ...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 for Azure Arc resource bridge system requirements exhibits mild Windows bias. Azure CLI installation links and requirements are primarily referenced with Windows-specific URLs and terminology (e.g., 'Azure CLI x64' linking to the Windows install page). There are no explicit Linux/macOS examples or references for management machine setup, CLI installation, or file paths, despite Azure CLI being cross-platform. The examples and instructions assume a Windows environment, potentially creating friction for Linux/macOS users.
Recommendations
  • Add explicit instructions and links for installing Azure CLI on Linux and macOS, alongside the Windows instructions.
  • Clarify that the management machine can be Linux, macOS, or Windows, and provide parity in requirements and examples.
  • Include example file paths and CLI usage for Linux/macOS environments (e.g., home directories, shell commands).
  • Ensure CLI commands and configuration file handling are described in a platform-agnostic way, or provide platform-specific notes as needed.
GitHub Create Pull Request
Azure Arc CLI reference for `azcmagent connect` ...b/main/articles/azure-arc/servers/azcmagent-connect.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation provides authentication options for both Windows and Linux, but several sections show Windows bias. The 'Interactive browser login' is described as Windows-only and is listed first. Windows certificate store usage is detailed, while Linux equivalents are not mentioned. The access token example references PowerShell's Get-AzAccessToken without mentioning Linux alternatives. Overall, Windows tools and patterns are mentioned before or instead of Linux equivalents.
Recommendations
  • Reorder authentication options so Linux-default methods (device code, Azure CLI) are presented first or equally.
  • Add explicit Linux/macOS guidance for certificate-based authentication, such as storing certificates in standard file paths and using PEM/PFX files.
  • For access token acquisition, mention cross-platform methods (e.g., Azure CLI's 'az account get-access-token') alongside PowerShell.
  • Clarify that all examples are cross-platform unless otherwise noted, and add notes for Linux-specific behaviors where relevant.
GitHub Create Pull Request
Azure Arc Recover from accidental deletion of resource bridge VM ...em-center-virtual-machine-manager/disaster-recovery.md
Medium 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 recovery instructions and a downloadable script exclusively for Windows, using PowerShell. There are no examples or guidance for Linux/macOS users, nor is there mention of equivalent tools or scripts for those platforms. The section is explicitly titled 'Recover Arc resource bridge from a Windows machine', and no Linux/macOS recovery path is described.
Recommendations
  • Provide equivalent recovery instructions for Linux/macOS users, including Bash or Python scripts if possible.
  • Mention whether the recovery process is supported or unsupported on Linux/macOS, and clarify any platform limitations.
  • If the script is Windows-only, explicitly state this and offer alternatives or workarounds for non-Windows environments.
  • Consider offering cross-platform scripts or containerized solutions to improve accessibility.
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 →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation page presents a notable Windows bias in its automation examples and tooling. The primary automation script is a PowerShell (.ps1) script, and instructions for running it reference PowerShell terminals and Windows Task Scheduler for cron-like automation. Windows tools and patterns (PowerShell, Task Scheduler) are mentioned exclusively or before Linux equivalents. While Linux is referenced in prerequisites and out-of-band methods (e.g., Ansible), there are no Linux shell script examples or guidance for running the automation at scale on Linux/macOS. The bias creates friction for Linux/macOS users who wish to automate Arc agent installation at scale.
Recommendations
  • Provide a Bash/shell script equivalent for the PowerShell automation script, or document how to run the PowerShell script on Linux/macOS (e.g., via PowerShell Core).
  • Include instructions for scheduling the automation on Linux (e.g., using cron) alongside Windows Task Scheduler examples.
  • Offer Linux/macOS terminal usage examples for running the script, not just PowerShell.
  • Ensure parity in examples for both Windows and Linux, especially for scale operations.
  • Clarify if the provided PowerShell script is cross-platform (PowerShell Core), and if not, offer a Linux-compatible alternative.
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 →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation provides detailed Windows/PowerShell instructions for running the deboarding script, including execution policy and script invocation, but does not offer equivalent Linux/macOS guidance. The script is referenced as a PowerShell script (.ps1), and only Windows-specific steps are described for its execution. Linux agent removal is covered, but Linux/macOS users are left without clear instructions for running the deboarding script or manual alternatives.
Recommendations
  • Provide explicit instructions for running the deboarding script on Linux/macOS, including prerequisites (e.g., PowerShell Core installation) and command examples.
  • Clarify whether the script can be run cross-platform or if a Bash version is available; if not, suggest manual steps or alternative scripts for Linux/macOS users.
  • List Linux/macOS steps alongside Windows steps, rather than only after or omitting them.
  • Mention PowerShell Core as an option for non-Windows users, with installation links and usage examples.
  • Add a note about script compatibility and any limitations for Linux/macOS environments.
GitHub Create Pull Request
Azure Arc Perform disaster recovery operations ...mware-vsphere/recover-from-resource-bridge-deletion.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page provides only PowerShell examples and scripts for disaster recovery operations, with no mention of Bash, Linux shell, or cross-platform alternatives. The onboarding script and its usage are shown exclusively in PowerShell syntax, and there is no guidance for Linux/macOS users on how to perform equivalent steps. The script editing and execution instructions assume a Windows environment, creating friction for non-Windows users.
Recommendations
  • Provide Bash or shell script equivalents for onboarding and recovery operations, or clarify if the onboarding script is cross-platform.
  • Explicitly state platform requirements for the onboarding script (e.g., if it requires Windows/PowerShell, mention this early in the documentation).
  • If possible, offer Azure CLI-only workflows that do not depend on PowerShell.
  • Add guidance for Linux/macOS users on how to edit and run the onboarding script, including any prerequisites or limitations.
  • Mention any cross-platform compatibility of the onboarding script, or provide links to Linux/macOS-specific instructions.
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 →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation consistently uses PowerShell syntax for Azure CLI commands and references PowerShell scripts (e.g., bulk_deployment.ps1, workflow-delete.ps1) without providing equivalent Bash or shell examples. There are no Linux/macOS-specific instructions or examples, and PowerShell is assumed as the default shell for CLI usage. This creates friction for Linux/macOS users who may not use PowerShell or .ps1 scripts.
Recommendations
  • Provide Azure CLI command examples in Bash syntax as well as PowerShell, using cross-platform conventions (e.g., az workload-orchestration ... in Bash).
  • Offer equivalent Bash shell scripts for bulk deployment and workflow deletion, or document how to use the .ps1 scripts on Linux/macOS (e.g., with PowerShell Core).
  • Clarify that Azure CLI commands can be run in any shell and indicate any shell-specific syntax differences.
  • Add explicit notes or sections for Linux/macOS users, including prerequisites for running PowerShell scripts (such as installing PowerShell Core), or alternative approaches.
GitHub Create Pull Request
Azure Arc Diagnostics of Edge-Related Logs and Errors in Workload Orchestration .../azure-arc/workload-orchestration/diagnose-problems.md
Medium 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 provides extensive PowerShell-based examples and scripts for enabling diagnostics, onboarding, and log collection, with no equivalent Bash or Linux shell examples. File paths in JSON templates and scripts are Windows-style (e.g., C:\, E:\), and the onboarding scripts are referenced as .ps1 (PowerShell), implying Windows as the default environment. There are no Linux/macOS-specific instructions, and the use of PowerShell and Windows paths is pervasive throughout the guide.
Recommendations
  • Add Bash or shell script equivalents for all PowerShell (.ps1) commands and onboarding steps.
  • Provide Linux/macOS file path examples in JSON templates (e.g., /home/user/schema.yaml) alongside Windows paths.
  • Explicitly state OS requirements for scripts, and offer cross-platform alternatives where possible.
  • Mention that Azure CLI commands can be run from Bash or PowerShell, and provide syntax for both.
  • Clarify if the onboarding scripts (.ps1) are required to be run on Windows, or provide cross-platform versions (e.g., Python, Bash).
GitHub Create Pull Request
Azure Arc Onboarding Scripts for Workload Orchestration ...azure-arc/workload-orchestration/onboarding-scripts.md
Medium 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 is heavily biased toward Windows environments. All onboarding scripts and examples are provided exclusively in PowerShell, with no mention of Bash or Linux shell equivalents. The prerequisites recommend using 'winget', a Windows-only package manager, to install Azure CLI and kubectl. There are no instructions or examples for Linux/macOS users, nor are alternative tools or commands provided. This creates friction for non-Windows users attempting to follow the onboarding process.
Recommendations
  • Provide Bash or shell script equivalents for onboarding scripts, or clarify if PowerShell Core is required and supported cross-platform.
  • Include Linux/macOS installation instructions for Azure CLI and kubectl (e.g., using apt, yum, brew, or direct download).
  • Mention cross-platform compatibility of the scripts, or explicitly state if they are Windows-only.
  • Add examples showing how to run the scripts on Linux/macOS, or provide guidance for adapting them.
  • Consider providing Docker-based or containerized onboarding options for greater platform parity.
GitHub Create Pull Request
Azure Arc Prepare the Environment for Workload Orchestration ...rc/workload-orchestration/initial-setup-environment.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation exhibits Windows bias in several areas. The example for installing kubectl uses the Windows-specific 'winget' tool, with no Linux/macOS alternative provided. In the section on extracting ZIP files, the Bash example incorrectly uses the Windows-native 'Expand-Archive' command, which is not available on Linux/macOS. Throughout, examples and variable paths are shown using Windows-style paths (e.g., 'C:\path\to\archive.zip') and Windows tools are referenced first or exclusively. There is a lack of explicit Linux/macOS instructions for key setup steps, which may confuse or hinder non-Windows users.
Recommendations
  • Provide Linux/macOS alternatives for installing kubectl, such as 'curl' or 'apt/yum/brew' commands.
  • Correct the Bash example for extracting ZIP files to use 'unzip' or 'tar' for Linux/macOS, and clarify Windows vs. Linux/macOS instructions.
  • Use platform-neutral or platform-specific path examples (e.g., '/home/user/archive.zip' for Linux/macOS).
  • Ensure that all steps referencing Windows tools (like 'winget' or 'Expand-Archive') are accompanied by Linux/macOS equivalents.
  • Consider adding a table or tabs for Windows, Linux, and macOS where commands differ.
GitHub Create Pull Request
Azure Arc Migrate Existing Target Resources to General Availability ...s/azure-arc/workload-orchestration/migration-script.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation provides only a PowerShell script (WOGAMigration.ps1) and instructs users to run it in PowerShell, with no mention of Bash, Linux shell, or cross-platform alternatives. There are no Linux/macOS-specific instructions or examples, and the migration script appears to be Windows-centric.
Recommendations
  • Provide a Bash or shell script equivalent for Linux/macOS users, or clarify if the PowerShell script can be run cross-platform (e.g., with PowerShell Core on Linux/macOS).
  • Add explicit instructions for Linux/macOS users, including how to install PowerShell Core if required.
  • Mention any prerequisites for running the script on non-Windows platforms, or state if Windows is required.
  • If the migration process is Windows-only, clarify this up front to set user expectations.
GitHub Create Pull Request
Azure Arc Troubleshooting for Workload Orchestration ...es/azure-arc/workload-orchestration/troubleshooting.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The troubleshooting guidance heavily favors PowerShell syntax and Windows command patterns throughout most sections, especially in the 'Troubleshoot staging' and registry/token troubleshooting. Linux/Bash equivalents are missing for many critical steps, and PowerShell is used even for commands that could be cross-platform. Bash examples are only provided in the 'Troubleshoot service groups' section, and are presented after the PowerShell-heavy sections. This creates friction for Linux/macOS users, who may not have PowerShell installed or prefer Bash.
Recommendations
  • Provide Bash equivalents for all PowerShell commands, especially for Azure CLI and Docker/Kubectl operations.
  • Use cross-platform syntax for Azure CLI commands (e.g., avoid PowerShell-specific variable assignment and piping where possible).
  • Clearly indicate which steps require PowerShell and which can be performed in Bash or other shells.
  • Add notes or tabs for Linux/macOS users where file encoding or text manipulation is required.
  • Review all troubleshooting steps to ensure Linux parity, especially for edge device and registry management.
GitHub Create Pull Request
Container Registry Azure Container Registry Authentication Options Explained ...ontainer-registry/container-registry-authentication.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for authentication, but PowerShell is given equal or greater prominence than is typical for cross-platform parity. PowerShell is a Windows-centric tool, and its inclusion alongside CLI in every example may create friction for Linux/macOS users. Additionally, PowerShell commands are shown in detail, and the CLI/PowerShell tab structure sometimes lists PowerShell first. There is minimal mention of Linux/macOS-specific shell environments, and no explicit Bash or shell script examples are provided. However, the core authentication flows use Azure CLI and Docker, which are cross-platform.
Recommendations
  • Prioritize Azure CLI examples and ensure they are always listed before PowerShell, as CLI is the primary cross-platform tool.
  • Clearly indicate that PowerShell is optional and primarily for Windows users; consider moving PowerShell examples to a separate section or tab.
  • Add explicit Bash/shell script examples for Linux/macOS users, especially for scripting scenarios.
  • Where PowerShell is mentioned, add a note that Azure CLI is recommended for Linux/macOS.
  • Ensure that all instructions referencing environment variables or scripting use syntax compatible with Bash as well as PowerShell.
GitHub Create Pull Request
Container Registry Azure Container Registry SKU Features and Limits ...articles/container-registry/container-registry-skus.md
Medium 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 both Azure CLI and Azure PowerShell examples for key operations (such as changing registry SKU), but consistently lists PowerShell after CLI and does not provide Linux/macOS-specific guidance or examples (e.g., Bash scripting, shell usage). REST API references are included, but no explicit Linux/macOS command-line examples or notes about cross-platform usage. The PowerShell examples are Windows-centric, and there is no mention of Linux tools or patterns.
Recommendations
  • Add explicit Bash or shell examples for Linux/macOS users alongside Azure CLI and PowerShell.
  • Clarify that Azure CLI is cross-platform and can be used on Linux, macOS, and Windows.
  • Where PowerShell is mentioned, note that PowerShell Core is available cross-platform, or provide Bash alternatives.
  • Add notes or examples for common Linux container tools (e.g., Podman, Docker CLI usage on Linux).
  • Ensure that references to Azure CLI are prominent and clarify its parity with PowerShell for registry management.
GitHub Create Pull Request
Azure Arc Run command on Azure Arc-enabled servers (Preview) ...cs/blob/main/articles/azure-arc/servers/run-command.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation mentions Windows and Linux support, but Windows is listed first in the 'Operating Systems' section. No examples are provided on this page, but the navigation links prioritize Azure CLI, PowerShell, and REST API equally. There is a minor bias in ordering, but Linux support is explicitly stated and a Linux-specific note is included.
Recommendations
  • List Linux and Windows in alphabetical order or clarify that both are equally supported.
  • Ensure that linked pages (CLI, PowerShell, REST) provide balanced examples for both Windows and Linux environments.
  • Add explicit statements or examples showing Linux usage where possible, especially in introductory sections.
GitHub Create Pull Request
Azure Arc Connect VMware vCenter Server to Azure Arc by using the helper script ...ere/quick-start-connect-vcenter-to-arc-using-script.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Windows (PowerShell) and Linux (Bash) onboarding scripts and instructions, but Windows/PowerShell instructions are consistently presented first and with more detailed notes (e.g., warnings about PowerShell ISE). The retry/cleanup commands also show Windows first. There are no missing Linux examples, and Linux is supported throughout, but the ordering and extra detail for Windows indicate a mild Windows-first bias.
Recommendations
  • Alternate the order of Windows and Linux instructions in each section, or present them in parallel tabs to avoid implying priority.
  • Provide equally detailed notes for Linux users (e.g., mention any common Bash shell pitfalls or requirements, if any).
  • Ensure screenshots and UI references are OS-neutral or provide Linux-specific equivalents where relevant.
  • Explicitly state that both Windows and Linux are fully supported and that users should select the script matching their OS.
GitHub Create Pull Request
Azure Arc Delete Resources in Workload Orchestration ...s/azure-arc/workload-orchestration/delete-resources.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation provides both Bash and PowerShell examples for each command, but consistently presents Bash examples first. There are no Windows-specific tools or patterns mentioned, and all instructions are cross-platform via Azure CLI. No Linux examples are missing, and no Windows tools are referenced exclusively.
Recommendations
  • Maintain Bash examples first, as this is already Linux-friendly.
  • Consider clarifying that Azure CLI commands are cross-platform and can be run on Windows, Linux, and macOS.
  • Optionally, add a note about how to install Azure CLI on Linux/macOS for completeness.
GitHub Create Pull Request
Azure Arc Solution with a Non-Leaf Target ...oad-orchestration/tutorial-service-group-scenario-2.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation provides both Bash and PowerShell examples for every step, ensuring parity for Linux/macOS and Windows users. However, PowerShell examples are consistently presented after Bash examples, which is a minor 'windows_first' bias. No Windows-specific tools or patterns are used, and all commands are cross-platform (az CLI, Helm).
Recommendations
  • Continue to provide both Bash and PowerShell examples for all steps.
  • Consider alternating the order of Bash and PowerShell tabs or explicitly stating that both are equally supported.
  • Add a brief note clarifying that all commands are cross-platform and can be run on Linux, macOS, and Windows.
GitHub Create Pull Request
Azure Arc Create a Solution with Shared Adapter Dependency with Workload Orchestration ...ation/quickstart-solution-shared-adapter-dependency.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation provides both Bash and PowerShell examples for all CLI commands and variable definitions. Bash examples are consistently shown before PowerShell, but there are no Windows-specific tools or patterns used, and Linux parity is maintained throughout. No critical sections are Windows-only, and all tasks can be completed on Linux/macOS. The only minor bias is Bash examples appearing first, which is a standard pattern but could be improved for parity.
Recommendations
  • Consider alternating the order of Bash and PowerShell examples in sections, or explicitly state that both are equally supported.
  • Add a brief note in the introduction clarifying that all CLI commands are cross-platform and supported on Linux, macOS, and Windows.
  • Ensure that any future examples or troubleshooting steps do not reference Windows-only tools or paths.
GitHub Create Pull Request
Azure Arc Multiple Solutions with a Single Shared Dependency at Different Levels ...oad-orchestration/tutorial-service-group-scenario-4.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation provides both Bash and PowerShell examples for every step, but PowerShell examples are consistently shown after Bash. There are no Windows-only tools or patterns, and Linux parity is maintained throughout. No Windows-specific tools or commands are used; all instructions rely on cross-platform Azure CLI and Helm. However, Bash examples are always presented first, which is a minor ordering bias.
Recommendations
  • Consider alternating the order of Bash and PowerShell examples in different sections to avoid implicit prioritization.
  • Explicitly state that both Bash and PowerShell are fully supported and that users can choose either based on their OS.
  • Add a brief note clarifying that all commands are cross-platform and work on Linux, macOS, and Windows.
GitHub Create Pull Request
Container Registry Store Helm Charts in Azure Container Registry ...es/container-registry/container-registry-helm-repos.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation is generally cross-platform, focusing on Helm and Azure CLI, which are available on Windows, Linux, and macOS. However, there are minor signs of Windows bias: the environment variable setup uses the Windows-style 'set' command without a Linux/macOS equivalent, and the order of Kubernetes cluster creation options lists Azure PowerShell before the Azure portal and Azure CLI. No PowerShell-specific commands are given, and most CLI examples use bash syntax, but the lack of explicit Linux/macOS instructions for environment variables may cause friction.
Recommendations
  • Add Linux/macOS equivalents for environment variable setup, e.g., 'export ACR_NAME=<container-registry-name>' alongside 'set' for Windows.
  • When listing options for creating AKS clusters, consider listing Azure CLI first, as it is the most cross-platform tool.
  • Explicitly state that all CLI commands are cross-platform and, where relevant, provide both Windows and Linux/macOS command variants.
  • Review for any other commands (e.g., file operations) that may differ between platforms and clarify usage.
GitHub Create Pull Request
Azure Arc Connect to SQL Managed Instance enabled by Azure Arc ...in/articles/azure-arc/data/connect-managed-instance.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation references SQL Server Management Studio (SSMS) as the primary GUI client, which is Windows-only, and mentions it before sqlcmd (which is cross-platform). However, the main connection example uses sqlcmd and explicitly notes Linux compatibility. There are no Linux-specific client GUI tools (like Azure Data Studio or DBeaver) mentioned, and SSMS is referenced first throughout. No PowerShell-specific commands are used, but the focus on SSMS as the preferred GUI tool creates a mild Windows bias.
Recommendations
  • Mention cross-platform GUI clients such as Azure Data Studio or DBeaver alongside SSMS.
  • Provide explicit Linux/macOS connection instructions or examples where relevant.
  • List sqlcmd as the first example, or clarify that it is available on both Windows and Linux.
  • Add a note about SSMS being Windows-only and suggest alternatives for Linux/macOS users.
GitHub Create Pull Request
Azure Arc Back up controller database .../articles/azure-arc/data/backup-controller-database.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides command-line examples for connecting to the SQL Server instance using sqlcmd, but the examples are shown using PowerShell syntax (e.g., kubectl exec ...), which is more familiar to Windows users. There is no explicit mention of Linux/macOS shell equivalents, and the PowerShell prompt is used in code blocks. However, the overall workflow is cross-platform, relying on Kubernetes and SQL Server tools, which are available on Linux/macOS. The bias is mostly in the presentation of examples, not in the actual steps or required tools.
Recommendations
  • Provide example commands using Bash/zsh syntax for Linux/macOS users alongside PowerShell examples.
  • Use a generic shell prompt (e.g., $) instead of PowerShell (>) in code blocks where the command is not Windows-specific.
  • Explicitly mention that sqlcmd and kubectl commands work on Linux/macOS as well, and provide installation links for those platforms.
  • Add notes clarifying that the steps are cross-platform and can be executed from any OS with the required tools.
GitHub Create Pull Request
Azure Arc Rotate user-provided TLS certificate in indirectly connected SQL Managed Instance enabled by Azure Arc ...articles/azure-arc/data/rotate-user-tls-certificate.md
Low 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 separately and with additional manual steps. The Linux example (base64) is presented first, but Windows users are given a distinct workflow. No PowerShell or Windows-first examples dominate, and the main certificate generation and rotation steps are cross-platform. The bias is minor and limited to the encoding step.
Recommendations
  • Clarify that certutil is available on Windows by default, and suggest alternative cross-platform tools (e.g., OpenSSL or Python) for base64 encoding.
  • Provide a PowerShell example for base64 encoding as an additional option for Windows users.
  • Explicitly state that all other steps (openssl, az CLI, kubectl) work identically on Windows, Linux, and macOS, to reassure non-Windows users.
  • Consider grouping encoding instructions by OS for clarity, or provide a table summarizing encoding commands for Linux, Windows (certutil), and macOS.
GitHub Create Pull Request
Azure Arc What's new with Azure Connected Machine agent ...main/articles/azure-arc/servers/agent-release-notes.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation provides release notes for both Windows and Linux versions of the Azure Connected Machine agent, with parity in most features and fixes. However, Windows download links and version numbers are consistently listed first. Windows-specific tools (MSI installer, PowerShell, Command Prompt) are referenced in installation instructions and troubleshooting, while Linux equivalents are not mentioned. Some improvements reference Windows scripts (e.g., ExtensionCleanup.ps1) and MSI signature verification, but Linux-specific tools are not similarly highlighted. There are occasional Windows-only or Linux-only fixes, but these are clearly marked.
Recommendations
  • Alternate the order of Windows and Linux download links and version numbers to avoid implicit prioritization.
  • Include Linux installation troubleshooting tips (e.g., using sudo, package managers) alongside Windows installer guidance.
  • When referencing Windows tools/scripts (e.g., PowerShell, MSI), provide Linux equivalents (e.g., Bash scripts, RPM/DEB commands) where relevant.
  • Ensure that improvements or bug fixes referencing Windows tools/scripts are matched with Linux equivalents if applicable.
GitHub Create Pull Request
Azure Arc VM Extension Management with Azure Arc-Enabled Servers ...ain/articles/azure-arc/servers/manage-vm-extensions.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation provides comprehensive coverage of VM extensions for both Windows and Linux, with clear separation of tables and examples. However, Windows extensions are presented first, which is a minor 'windows_first' bias. All deployment methods (Azure CLI, PowerShell, Portal, ARM templates) are listed together, and Linux-specific extensions are well documented. No critical sections are Windows-only, and Linux users can complete all tasks described.
Recommendations
  • Consider alternating the order of Windows and Linux sections or presenting them side-by-side to avoid implicit prioritization.
  • Explicitly state at the beginning that both Windows and Linux are equally supported to reinforce parity.
  • Ensure that linked deployment guides (e.g., Azure CLI, PowerShell) include Linux-specific examples and instructions where relevant.
GitHub Create Pull Request
Azure Arc Access Azure resources with managed identity on Azure Arc-enabled servers ...s/azure-arc/servers/managed-identity-authentication.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Windows (PowerShell) and Linux (Bash) examples for acquiring access tokens, but the Windows/PowerShell example is presented first and in greater detail, including a screenshot. PowerShell is highlighted as the primary tool for Windows, while Bash is used for Linux. The prerequisites and related content sections mention both platforms and tools, but PowerShell is listed before Azure CLI in related content, and Windows group membership is described before Linux equivalents.
Recommendations
  • Alternate the order of Windows and Linux examples, or present them side-by-side to avoid implicit prioritization.
  • Ensure screenshots and example outputs are provided for both Windows and Linux, not just Windows.
  • In related content, list Azure CLI and PowerShell equally, or mention Azure CLI first for Linux parity.
  • Expand Linux-specific guidance where possible, such as troubleshooting or group membership requirements.
  • Use neutral language when describing prerequisites and steps, e.g., 'On Windows...' and 'On Linux...' rather than always listing Windows first.
GitHub Create Pull Request
Azure Arc Troubleshoot Azure Connected Machine agent connection issues ...ticles/azure-arc/servers/troubleshoot-agent-onboard.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ windows_tools
Summary
The documentation provides troubleshooting guidance for both Windows and Linux, but there are signs of Windows bias. Windows examples and PowerShell syntax are presented first in the verbose log section, and Windows-specific file paths and tools (e.g., PowerShell, %TEMP%, %ProgramData%) are referenced throughout. Linux equivalents are included, but often after Windows, and some remediation steps reference Windows tools or paths without always providing Linux alternatives.
Recommendations
  • Present Linux and Windows examples in parallel or alternate order, rather than always Windows first.
  • When referencing file paths or logs, always provide both Windows and Linux locations side-by-side.
  • Where PowerShell or Windows-specific commands are shown, provide equivalent Bash or Linux shell commands.
  • Ensure troubleshooting steps and remediation guidance include Linux-specific details (e.g., log locations, service management commands) wherever Windows details are given.
  • Consider a summary table or section that clearly distinguishes Windows and Linux troubleshooting steps for each major error.
GitHub Create Pull Request
Azure Arc Support matrix for Azure Arc-enabled System Center Virtual Machine Manager ...pport-matrix-for-system-center-virtual-machine-manager.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools ⚠ī¸ powershell_heavy
Summary
The documentation is intentionally focused on System Center Virtual Machine Manager (SCVMM), a Windows-only product. Most requirements, examples, and supported operating systems are Windows-centric. Linux is mentioned only in passing, with limited guidance. Windows tools and patterns (such as WinRM, Windows Management Framework, and Windows Server versions) are referenced throughout, and Windows operating systems are listed first and in detail. Linux support is acknowledged but not elaborated, and Linux users are warned of potential performance issues.
Recommendations
  • Clarify that SCVMM is a Windows-only management platform and that the documentation is intentionally Windows-focused.
  • Expand Linux guidance for Arc agent installation, including step-by-step instructions and troubleshooting tips.
  • Provide more parity in examples and requirements for Linux VMs managed by SCVMM, such as supported distributions and versions.
  • If possible, offer performance optimization tips for Linux deployments, or explain the limitations in more detail.
  • Ensure that Linux prerequisites and network requirements are as clearly documented as Windows equivalents.
GitHub Create Pull Request
Azure Arc What is Azure Arc-enabled VMware vSphere? ...lob/main/articles/azure-arc/vmware-vsphere/overview.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation generally presents Azure Arc-enabled VMware vSphere as a cross-platform solution, supporting both Windows and Linux VMs. However, there are subtle signs of Windows bias: PowerShell is mentioned as a primary automation tool, and Windows-related features (such as Windows Server management and Extended Security Updates) are referenced before Linux equivalents. Some links and examples (e.g., Azure Automation runbooks, AVS deployment) default to Windows tabs or Windows-centric guidance, with Linux mentioned second or as an afterthought.
Recommendations
  • Ensure Linux examples and tools (such as Bash, Linux CLI usage) are presented alongside PowerShell, not after.
  • When referencing automation, highlight Bash and Python scripts equally with PowerShell.
  • For features like Azure Automation, provide clear Linux runbook examples and links.
  • When linking to deployment guides or management features, offer both Windows and Linux tabs or links equally.
  • Review the order of presentation so Linux is not always secondary to Windows.
GitHub Create Pull Request
Azure Arc Plan for deployment ...phere/support-matrix-for-arc-enabled-vmware-vsphere.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Windows and Linux requirements for guest management, but Windows tools (.NET Framework, PowerShell) are listed first and with download links, while Linux requirements are listed second and less prominently. Windows download links and tooling are more detailed. There are no Linux-specific examples or download links, and Windows terminology (e.g., 'Windows Admin Center') appears in networking requirements. However, Linux is supported and mentioned throughout.
Recommendations
  • List Linux requirements before or alongside Windows requirements to avoid 'Windows first' bias.
  • Provide download links or installation instructions for Linux prerequisites (e.g., wget, systemd) similar to Windows.
  • Include Linux-specific examples or references where appropriate (such as installation commands for the Arc agent).
  • Clarify that both Windows and Linux are equally supported, and provide parity in detail for both OS types.
GitHub Create Pull Request
Azure Portal Use Azure Copilot with the Azure mobile app ...main/articles/azure-portal/mobile-app/azure-copilot.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation mentions 'Generating CLI and PowerShell scripts' as a key scenario, listing PowerShell alongside CLI. While this is a minor bias, as PowerShell is often associated with Windows, the documentation does not provide examples or instructions that are Windows-specific, nor does it omit Linux/macOS equivalents. The rest of the content is platform-neutral, focusing on the Azure mobile app available for both iOS and Android.
Recommendations
  • Clarify that Azure Copilot can generate both Bash (for Azure CLI) and PowerShell scripts, and that these are useful for Windows, Linux, and macOS users.
  • Consider listing 'CLI and Bash scripts' before 'PowerShell scripts' to avoid implicit Windows-first ordering.
  • If examples are added in the future, ensure both PowerShell and Bash/CLI examples are provided.
GitHub Create Pull Request
Azure Arc Whats new in Azure Arc-enabled VMware vSphere ...ob/main/articles/azure-arc/vmware-vsphere/whats-new.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation page lists new features for Azure Arc-enabled VMware vSphere. While most features are platform-neutral or explicitly mention both Windows and Linux, there are minor instances of Windows bias: Windows VM customization is mentioned before Linux, and Azure PowerShell is listed before Azure CLI in the June 2024 section. However, Linux support is referenced (e.g., Arc agent installation on Linux via SSH, Ansible playbook for agent installation), and SDKs/tools for multiple languages are included.
Recommendations
  • When listing VM customization features, mention Linux and Windows parity or clarify if Linux customization is supported.
  • List Azure CLI before PowerShell or together, as CLI is cross-platform and more common for Linux/macOS users.
  • Ensure that all automation examples (e.g., agent installation at scale) include both Windows (e.g., Group Policy, SCCM) and Linux (e.g., Ansible, shell scripts) methods equally.
  • Explicitly state Linux support in sections where Windows features are highlighted, to reassure Linux users.
  • Consider adding links to Linux-specific documentation or examples where relevant.
GitHub Create Pull Request
Azure Arc Staging Resources Before Deployment ...icles/azure-arc/workload-orchestration/how-to-stage.md
Low 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 major steps, but PowerShell examples are sometimes shown immediately after Bash, and there is occasional use of Windows-specific encoding instructions. However, Linux parity is generally maintained, and no critical steps are Windows-only.
Recommendations
  • Ensure Bash and PowerShell examples are equally prominent and consistently ordered (e.g., Bash first for Linux/macOS users).
  • Clarify any OS-specific instructions, such as encoding file formats, with explicit guidance for both Windows and Linux/macOS.
  • Where PowerShell-specific commands are used (e.g., base64 encoding), provide the equivalent Bash command alongside.
  • Consider adding a brief note at the top indicating that both Linux/macOS and Windows are fully supported, and users should select the tab appropriate for their environment.
GitHub Create Pull Request
Azure Arc External Validation for Workload Orchestration ...zure-arc/workload-orchestration/external-validation.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation provides both Bash and PowerShell examples for all CLI operations, ensuring parity for Linux/macOS and Windows users. However, PowerShell examples are consistently presented immediately after Bash, which could be interpreted as a minor 'windows_first' bias, but no critical Windows-only tools or patterns are used. All instructions are cross-platform via Azure CLI, and there are no missing Linux examples or exclusive Windows tools mentioned.
Recommendations
  • Consider alternating the order of Bash and PowerShell examples in some sections to avoid implicit prioritization.
  • Explicitly state that all Azure CLI commands work on Linux, macOS, and Windows to reassure non-Windows users.
  • Add a brief note at the start clarifying that PowerShell examples are for Windows users and Bash for Linux/macOS, and both are fully supported.
GitHub Create Pull Request
Azure Arc Set Up Workload Orchestration .../workload-orchestration/initial-setup-configuration.md
Low 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 the PowerShell section is presented after Bash and is equally detailed. There is no evidence of Windows-only tools or patterns, nor are Windows tools mentioned exclusively. However, PowerShell is included as a primary scripting option, which may indicate a slight Windows bias, especially since PowerShell is most commonly used on Windows, though it is now cross-platform. Bash is presented first, which helps mitigate bias.
Recommendations
  • Clarify that PowerShell examples are compatible with PowerShell Core on Linux/macOS, not just Windows.
  • Consider adding a note about Bash and PowerShell availability on all platforms, and recommend using Bash for Linux/macOS users.
  • If possible, provide explicit instructions or links for installing PowerShell on Linux/macOS for users who may prefer it.
  • Ensure that all az CLI commands are tested and work identically on Linux/macOS and Windows.
GitHub Create Pull Request
Azure Arc Release Notes for Workload Orchestration ...cles/azure-arc/workload-orchestration/release-notes.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides CLI examples primarily using PowerShell syntax (with backticks for line continuation), especially in the May 2025 release section. Bash syntax is used elsewhere, but PowerShell appears first and is used for configuration-related examples. There is no explicit mention of Linux/macOS equivalents or alternative shell usage, and no Linux-specific tools or patterns are referenced.
Recommendations
  • Provide CLI examples in both Bash and PowerShell syntax, or clarify that the CLI commands are cross-platform and can be run in any shell.
  • When showing CLI commands, use Bash syntax (with \ for line continuation) as the default, or show both Bash and PowerShell versions side by side.
  • Add a note indicating that Azure CLI commands work on Windows, Linux, and macOS, and specify any OS-specific considerations if relevant.
  • Avoid using PowerShell-specific syntax (backticks) unless the feature is Windows-only, and provide Bash alternatives for Linux/macOS users.
GitHub Create Pull Request
Azure Arc Solution with a Leaf Target ...oad-orchestration/tutorial-service-group-scenario-1.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation provides both Bash and PowerShell examples for every step, ensuring parity between Linux/macOS and Windows users. However, in each section, Bash examples are presented before PowerShell, which is a minor bias in favor of Linux/macOS users (not Windows). There are no Windows-specific tools, patterns, or references that exclude Linux/macOS users, and all commands use cross-platform Azure CLI and Helm tools.
Recommendations
  • No action needed. The documentation already provides full parity for Linux/macOS and Windows users.
  • If desired, alternate the order of Bash and PowerShell tabs in different sections to further balance presentation.
GitHub Create Pull Request
Azure Arc Solution with Multiple Shared Dependencies at Different Hierarchy Levels ...oad-orchestration/tutorial-service-group-scenario-3.md
Low 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 consistently presents Bash examples first. There is no evidence of Windows-only tools or patterns, and the Azure CLI and Helm are cross-platform. However, the PowerShell examples are present throughout, which may suggest a slight Windows bias, especially since PowerShell is less commonly used on Linux/macOS. No Linux-specific examples or troubleshooting are missing, and all commands are cross-platform.
Recommendations
  • Clarify that PowerShell examples are for users who prefer PowerShell, and Bash is suitable for Linux/macOS and Windows (via WSL or Git Bash).
  • Consider adding a note at the top explaining that all commands are cross-platform unless otherwise stated.
  • Optionally, include a brief section on running PowerShell on Linux/macOS for users who may want to use those examples.
  • Ensure parity in troubleshooting or environment setup instructions for both Bash and PowerShell users.
GitHub Create Pull Request
Azure Portal Programmatically create Azure Dashboards ...tal/azure-portal-dashboards-create-programmatically.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides deployment instructions for Azure dashboards using the Azure portal, Azure CLI, and Azure PowerShell. While the Azure CLI is cross-platform and is presented before PowerShell, the PowerShell section is included as a first-class option, which may be seen as a Windows-centric tool. However, there are no exclusive Windows tools or patterns, and all critical tasks can be completed using the Azure CLI or portal, both of which are cross-platform. The order of presentation (CLI before PowerShell) is appropriate, but the inclusion of PowerShell as a main deployment method may be seen as slightly Windows-biased. All code examples and instructions are otherwise platform-neutral.
Recommendations
  • Clarify that Azure PowerShell is available cross-platform (Windows, macOS, Linux) via PowerShell Core, to reduce perceived Windows bias.
  • Explicitly state that all deployment steps using Azure CLI and the portal are fully supported on Linux and macOS.
  • Consider adding a short note or table summarizing tool/platform compatibility for Azure CLI and PowerShell.
  • If possible, provide Bash or shell script examples for common tasks, or clarify that Azure CLI commands work in Bash and other shells.
GitHub Create Pull Request
Container Registry Import Container Images to ACR using Azure APIs ...container-registry/container-registry-import-images.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation provides parity between Azure CLI and Azure PowerShell throughout, but consistently presents Azure CLI examples first, followed by Azure PowerShell. Azure CLI is fully cross-platform (Linux, macOS, Windows), while PowerShell is traditionally Windows-centric, though now available cross-platform. No Windows-only tools or patterns are used, and all examples are equally applicable to Linux/macOS users. There are no missing Linux/macOS examples, and no exclusive mention of Windows tools.
Recommendations
  • Consider explicitly stating that Azure CLI is cross-platform and recommended for Linux/macOS users.
  • Add a brief note clarifying that Azure PowerShell is available on Linux/macOS, but Azure CLI is often preferred for those environments.
  • Optionally, reorder or alternate the order of CLI and PowerShell examples to avoid 'windows_first' bias.
  • Ensure links to Azure CLI installation instructions highlight Linux/macOS options.
GitHub Create Pull Request