← Back to Dashboard
229
Pages Scanned
48
Pages Flagged
229
Changed Pages
21.0%
% Pages Flagged

Live Progress

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

Scan Information

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

Finished At: In Progress

Status: in_progress

Target Repo: Azure Management

Current Phase: discovery

Files Queued: 229

Files Completed: 229

Problematic Pages

51 issues found
Azure Arc Onboarding Scripts for Workload Orchestration ...azure-arc/workload-orchestration/onboarding-scripts.md
High Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation page for onboarding scripts in workload orchestration is heavily biased toward Windows environments. All script examples are provided as PowerShell scripts (.ps1), and users are instructed to use PowerShell terminals. Prerequisites reference Windows-specific tools like 'winget' for installing dependencies, with no mention of Linux/macOS alternatives. There are no Bash or shell script equivalents, and no guidance for running these scripts on non-Windows platforms. This creates significant friction for Linux/macOS users, who may not be able to follow the onboarding process as described.
Recommendations
  • Provide equivalent onboarding scripts in Bash or cross-platform scripting languages, or clarify if the scripts are Windows-only.
  • Include installation instructions for Azure CLI and kubectl using platform-appropriate package managers (e.g., apt, yum, brew) for Linux/macOS.
  • Add explicit notes about platform support and any requirements or limitations for non-Windows users.
  • If PowerShell Core (pwsh) is supported on Linux/macOS, document how to use it and how to run the scripts in those environments.
  • Reorder or supplement examples so Linux/macOS instructions are given equal prominence.
GitHub Create Pull Request
Azure Arc Back up controller database .../articles/azure-arc/data/backup-controller-database.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides SQL connectivity examples using PowerShell syntax and references the use of sqlcmd via PowerShell, without offering equivalent Linux/macOS shell examples. The use of PowerShell for kubectl exec commands may create friction for Linux/macOS users, as Bash or other shells are more common in those environments.
Recommendations
  • Provide Linux/macOS shell (e.g., Bash) equivalents for all PowerShell examples, especially for kubectl exec and sqlcmd commands.
  • Ensure that examples are presented in a cross-platform manner, or explicitly note when a command is platform-specific.
  • Consider showing Bash examples first or alongside PowerShell to improve parity.
  • Clarify that sqlcmd and kubectl commands can be run from any shell, not just PowerShell.
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 exclusively for Windows, including a PowerShell script and Windows-specific steps. There are no equivalent instructions, scripts, or examples for Linux or macOS users, and the section is titled 'Recover Arc resource bridge from a Windows machine,' implying Windows is the only supported platform for recovery.
Recommendations
  • Provide equivalent recovery instructions for Linux/macOS, including Bash or Python scripts.
  • Clarify if recovery is possible from non-Windows platforms; if not, explicitly state Windows is required.
  • If the script is Windows-only, consider offering a cross-platform version or documenting manual steps for Linux users.
  • Add a section titled 'Recover Arc resource bridge from a Linux/macOS machine' if supported.
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 ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation page provides only PowerShell examples and references the onboarding script as a PowerShell (.ps1) script, with no mention of Linux/macOS-compatible alternatives or instructions. All command-line examples are Windows-centric, and there is no guidance for users on Linux or macOS platforms. The onboarding workflow assumes the use of PowerShell and does not address cross-platform usage.
Recommendations
  • Provide Bash or shell script equivalents for onboarding and recovery steps, or clarify if the onboarding script is cross-platform.
  • Explicitly state platform requirements for the onboarding script and offer guidance for Linux/macOS users (e.g., using PowerShell Core, prerequisites, or alternative steps).
  • Add examples or notes for running the onboarding script on Linux/macOS, including any necessary modifications or dependencies.
  • Mention Azure CLI usage where possible, as it is cross-platform, and provide relevant command examples.
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 focused on Linux preparation for AKS Edge Essentials, but uses Windows-centric tools (Invoke-AksEdgeNodeCommand) for Linux node configuration, and does not provide native Linux shell or SSH command alternatives. The text editor example (Notepad) is also Windows-specific, and Linux-native editors are not mentioned.
Recommendations
  • Provide native Linux shell/SSH command examples for sysctl configuration, such as using 'ssh' and 'sudo sysctl ...' directly.
  • Mention Linux text editors (e.g., nano, vim) alongside Notepad for editing configuration files.
  • Clarify if Invoke-AksEdgeNodeCommand is required even for Linux hosts, or provide Linux-native alternatives.
  • Ensure all steps can be completed from a Linux admin workstation without reliance on Windows tools.
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 lists several Windows-centric tools (SSMS, SQL Server Data Tools, SQL Server Profiler, SQL Server PowerShell) and explicitly mentions PowerShell scripting support as a manageability feature. While Azure CLI and Visual Studio Code are included, there are no Linux-specific tools or examples, and Windows tools are referenced without Linux alternatives or parity discussion.
Recommendations
  • Add explicit mention of cross-platform tools such as Azure Data Studio, which runs on Linux/macOS.
  • Clarify which tools are Windows-only and which are cross-platform.
  • Provide examples or links for using SQL Managed Instance enabled by Azure Arc from Linux/macOS environments (e.g., using Azure CLI, sqlcmd, or Azure Data Studio).
  • Consider listing Azure CLI and Visual Studio Code before Windows-only tools to reduce Windows-first impression.
  • Note PowerShell scripting support is primarily for Windows, and suggest Bash/CLI alternatives for Linux/macOS users.
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: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation frequently presents Windows-centric tools and paths first (e.g., SSMS, C:\ paths, Windows file copy examples) and does not provide equivalent Linux/macOS examples for key steps such as database backup and file copying. This creates friction for users on non-Windows platforms.
Recommendations
  • Provide explicit examples for Linux/macOS users, such as using sqlcmd or Azure Data Studio for backup/restore operations.
  • When showing file paths, include both Windows (C:\...) and Linux (/home/user/...) examples.
  • For file copy steps, show both Windows (C:\...) and Linux/macOS (~/ or /tmp/) source paths in kubectl cp commands.
  • Mention cross-platform tools like Azure Data Studio alongside SSMS.
  • Clarify that Visual Studio Code, Azure Storage Explorer, and kubectl are cross-platform, and provide installation links for all OSes.
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
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ missing_linux_example ⚠ī¸ windows_first
Summary
The documentation provides both Linux and Windows methods for base64 encoding files, but the Windows example is more detailed and includes additional steps (removing headers) that are not explained for Linux. The Linux example is presented first, but the Windows section is more prominent and includes links to Windows-specific tools. There is no PowerShell bias, but Windows tools (certutil, findstr) are mentioned, and the Linux equivalent for header removal is missing. All other steps use cross-platform tools (OpenSSL, Azure CLI, kubectl), and the overall workflow is platform-neutral.
Recommendations
  • Add Linux/macOS equivalent commands for removing certificate headers after base64 encoding (e.g., using grep or sed).
  • Clarify that the base64 encoding step can be performed on both Linux and Windows, and provide parity in instructions for both platforms.
  • Consider linking to documentation for Linux/macOS base64 and text processing utilities, similar to the Windows certutil link.
  • Ensure that examples for Linux/macOS are as detailed as Windows examples, especially for multi-step tasks.
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 is evidence of Windows bias: PowerShell is referenced for troubleshooting HTTP2 issues, Windows-style paths and error messages are shown first, and Linux-specific troubleshooting steps (such as using bash or Linux CLI commands) are rarely provided. For example, the PowerShell cmdlet is given for HTTP2 troubleshooting, but no equivalent Linux curl command is shown. The GLIBC error is explained, but Linux troubleshooting is minimal compared to Windows/PowerShell. Windows terminology (RDP, PowerShell, Windows paths) appears more frequently and often before Linux equivalents.
Recommendations
  • Provide Linux/macOS equivalents for PowerShell troubleshooting commands (e.g., curl with HTTP2 for HTTP2 errors).
  • Show Linux CLI commands (such as nslookup, dig, curl) alongside Windows commands for network/DNS troubleshooting.
  • Ensure error messages and troubleshooting steps reference both Windows and Linux paths and environments.
  • Add explicit guidance for Linux users where only Windows instructions are given (e.g., for Azure CLI installation/downgrade, SSH folder permissions, proxy configuration).
  • Balance the order of examples so Linux/macOS instructions are not always secondary to Windows/PowerShell.
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 both Linux and Windows ARM template examples for all VM extensions, ensuring parity in template content. However, all deployment commands and walkthroughs exclusively use Azure PowerShell, with no Azure CLI or Bash examples. Additionally, PowerShell commands are presented first and only, which may create friction for Linux/macOS users who prefer Bash or Azure CLI. The documentation is not Windows-only, but the deployment workflow is PowerShell-centric.
Recommendations
  • Add Azure CLI deployment examples alongside PowerShell commands, especially for template deployments (e.g., az deployment group create).
  • Explicitly mention that Azure PowerShell can be used on Linux/macOS, but also provide Bash/CLI alternatives.
  • Consider showing CLI examples before or alongside PowerShell to avoid 'windows_first' bias.
  • Clarify in prerequisites that either PowerShell or CLI can be used, and link to installation guides for both.
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 demonstrates notable Windows bias, especially in the 'Auto Arc-enablement script' section, which exclusively provides PowerShell-based automation and references Windows Task Scheduler for cron jobs. Windows tools and patterns (PowerShell, Task Scheduler) are mentioned first and exclusively, with no equivalent Linux/macOS automation examples. While Linux is referenced in prerequisites and out-of-band methods, the main scalable automation script is Windows-centric, creating friction for Linux/macOS users.
Recommendations
  • Provide a Bash or Python version of the batch enablement script for Linux/macOS users.
  • Include examples for running the script as a cron job on Linux (using crontab) alongside Windows Task Scheduler.
  • Clarify whether the helper script can be run cross-platform, and if not, offer guidance or alternatives for Linux/macOS environments.
  • Ensure that out-of-band automation methods (e.g., Ansible) are highlighted as viable for Linux users, and provide links or examples.
  • Where PowerShell is used, note if PowerShell Core (cross-platform) is supported, and provide installation guidance for Linux/macOS.
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 steps and examples for Windows users, especially for running the deboarding script, with PowerShell-specific instructions and notes. There is no equivalent guidance for Linux/macOS users on how to run the deboarding script, and Windows instructions are presented first and in greater detail. While uninstall instructions for the agent are given for both Windows and Linux, the script execution section is Windows-centric.
Recommendations
  • Add explicit instructions for running the deboarding script on Linux/macOS, including shell commands and prerequisites.
  • Clarify whether the deboarding script can be run cross-platform (e.g., if it's a PowerShell script, mention PowerShell Core support and provide Linux/macOS usage examples).
  • Present Windows and Linux/macOS instructions in parallel sections or clearly indicate platform-specific steps.
  • Add notes about any limitations or requirements for Linux/macOS users (such as needing PowerShell Core or Azure CLI).
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 all CLI examples and references PowerShell scripts (.ps1) for automation, without providing equivalent Bash or shell script examples. There is no mention of Linux/macOS-specific instructions or alternative scripting approaches, and PowerShell is presented as the default/only option for scripting and command execution.
Recommendations
  • Provide CLI command examples in Bash syntax (e.g., az ... with Bash variable usage) alongside PowerShell examples.
  • Offer equivalent shell scripts (e.g., bulk_deployment.sh) for Linux/macOS users, or clarify if the .ps1 scripts are cross-platform via PowerShell Core.
  • Explicitly state that the Azure CLI commands work on all platforms and clarify any platform-specific requirements for scripts.
  • Add notes or tabs indicating how to run these commands/scripts on Linux/macOS, including installation instructions for PowerShell Core if required.
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 ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page provides almost exclusively PowerShell-based examples and scripts for enabling diagnostics, onboarding clusters, and managing settings. Paths in JSON templates use Windows-style backslashes and drive letters. There are no Bash, shell, or Linux/macOS CLI examples, nor guidance for running scripts on non-Windows platforms. The use of PowerShell and Windows file paths is pervasive, and Linux/macOS users are not provided with equivalent instructions or examples.
Recommendations
  • Add Bash/shell script equivalents for all PowerShell examples, especially for az CLI commands and onboarding scripts.
  • Provide Linux/macOS file path examples in JSON templates (e.g., /home/user/config.yaml) alongside Windows paths.
  • Clarify whether the onboarding scripts (infra_onboarding.ps1) can be run cross-platform, or provide alternatives for Linux/macOS users.
  • Explicitly mention OS requirements for scripts and tools, and link to cross-platform installation instructions for Azure CLI.
  • Where possible, use az CLI commands in a platform-neutral way (without PowerShell-specific syntax or variables).
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 for migration and instructs users to run it in PowerShell, without mentioning or providing alternatives for Linux/macOS users (such as Bash or cross-platform scripting). This creates friction for non-Windows users, as PowerShell is not natively available on Linux/macOS and may require additional setup.
Recommendations
  • Provide a Bash or cross-platform script for migration, or document how to run the PowerShell script using PowerShell Core on Linux/macOS.
  • Explicitly mention PowerShell Core compatibility and provide installation instructions for Linux/macOS users.
  • Offer alternative commands or scripts if possible, or clarify if the script is Windows-only and why.
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 a PowerShell script (RGCleanScript.ps1) and only PowerShell-based usage examples, with no mention of Bash, shell, or cross-platform alternatives. There is no guidance for Linux/macOS users on how to run the script or whether it is compatible with PowerShell Core or Azure CLI, creating friction for non-Windows users.
Recommendations
  • Clarify whether RGCleanScript.ps1 is compatible with PowerShell Core (pwsh) on Linux/macOS.
  • Provide explicit instructions for running the script on Linux/macOS, including installation steps for PowerShell Core if needed.
  • Offer equivalent Bash or Azure CLI examples/scripts, or note if none exist.
  • Add a note about cross-platform support or limitations for the script.
  • If the script is Windows-only, state this clearly and suggest alternatives for Linux/macOS users if possible.
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 ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation exhibits Windows bias in several areas. The 'winget' command is provided as the only example for installing kubectl, which is a Windows-specific tool, with no Linux/macOS installation instructions. In the section about extracting ZIP files, the Bash tab uses the Windows-native 'Expand-Archive' command (which is not available on Linux/macOS Bash), and all example paths are Windows-style (e.g., 'C:\path\to\archive.zip'). There are no Linux/macOS-specific instructions or examples for these steps, and the documentation consistently presents Windows tools and patterns first or exclusively.
Recommendations
  • Provide Linux/macOS installation instructions for kubectl, such as using 'curl' or 'apt/yum/brew'.
  • For extracting ZIP files, include Linux/macOS Bash commands (e.g., 'unzip archive.zip -d /path/to/workspace') and use POSIX-style paths.
  • Add explicit notes or tabs for Linux/macOS users throughout, especially in sections where Windows tools are referenced.
  • Ensure that all code examples are cross-platform or clearly indicate which OS they are for.
  • Consider showing Linux/macOS examples before or alongside Windows examples to avoid 'windows_first' bias.
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 for workload orchestration is heavily biased toward Windows/PowerShell usage. Most command examples throughout the troubleshooting sections are provided only in PowerShell syntax, with no equivalent Bash or Linux shell examples. Windows-specific scripting patterns (e.g., variable assignment, ConvertTo-Json, Out-File, Base64 encoding in PowerShell) are used exclusively. Only in the 'Troubleshoot service groups' section are Bash examples provided alongside PowerShell, but the rest of the document lacks Linux parity. This creates friction for Linux/macOS users, who must translate PowerShell commands to Bash or other shells themselves.
Recommendations
  • Provide Bash/Linux shell equivalents for all PowerShell command examples, especially for az CLI, kubectl, and docker commands.
  • Use cross-platform scripting patterns (e.g., environment variables, file encoding, Base64 encoding) and document both PowerShell and Bash approaches.
  • Where PowerShell-specific constructs are used (e.g., ConvertTo-Json, Out-File), show how to achieve the same result in Bash (e.g., using jq, echo, cat, etc.).
  • Ensure variable assignment and usage examples are shown for both Windows (PowerShell) and Linux (Bash) environments.
  • Review the troubleshooting steps to confirm that all tasks can be completed on Linux/macOS and clarify any OS-specific requirements.
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: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides release notes for both Windows and Linux versions of the Azure Connected Machine agent, with clear parity in feature and bug fix listings for both platforms. However, there is a consistent pattern of listing Windows download links and version numbers before Linux, and occasional references to Windows-specific tools (e.g., PowerShell, msiexec) in troubleshooting and known issues sections. There are no missing Linux examples or features, but Windows terminology and tools are sometimes mentioned without Linux equivalents.
Recommendations
  • Alternate the order of Windows and Linux download links and version numbers, or present them side-by-side to avoid implicit prioritization.
  • When referencing Windows-specific tools or installation methods (e.g., msiexec, PowerShell), provide equivalent Linux instructions or clarify that the guidance is Windows-only.
  • In troubleshooting sections, if a Windows-specific issue is described, consider adding a note about whether similar issues exist or do not exist on Linux.
  • Where possible, use neutral language (e.g., 'For Windows, do X. For Linux, do Y.') to ensure both platforms are equally addressed.
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: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation provides both Bash and PowerShell examples for all steps, but the Bash tab is presented first. There are no Windows-specific tools or patterns, and all commands use the Azure CLI, which is cross-platform. No Linux/macOS examples are missing, and no Windows tools are mentioned exclusively or before their Linux equivalents.
Recommendations
  • Ensure both Bash and PowerShell tabs are equally prominent and accessible.
  • Consider explicitly mentioning that Azure CLI commands work on Linux, macOS, and Windows.
  • Add a brief note clarifying that Bash examples are suitable for Linux/macOS users, while PowerShell is for Windows users.
  • If possible, provide a generic 'CLI' tab or clarify that Bash is the default for Linux/macOS.
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, in several sections, PowerShell examples are presented immediately after Bash, which is a minor 'windows_first' bias. No Windows-specific tools or patterns are mentioned, and all instructions are cross-platform via Azure CLI. No critical Linux/macOS gaps are present.
Recommendations
  • Consider alternating the order of Bash and PowerShell examples, or explicitly state that Bash is suitable for Linux/macOS and PowerShell for Windows.
  • Add a brief note clarifying that all Azure CLI commands work on Linux, macOS, and Windows, and that Bash examples are intended for Linux/macOS users.
  • Ensure screenshots and portal instructions are not Windows-centric (current screenshot is neutral).
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 command, ensuring parity for Linux/macOS and Windows users. However, in each section, Bash examples are presented first, followed by PowerShell. There are no Windows-specific tools or patterns, and all commands use cross-platform Azure CLI and Helm. No Linux/macOS examples are missing, and there is no exclusive mention of Windows tools or patterns.
Recommendations
  • Continue to provide both Bash and PowerShell examples for all commands.
  • Consider alternating the order of Bash and PowerShell tabs in different sections, or explicitly state that Bash is shown first for consistency, not preference.
  • Ensure that any future additions (e.g., troubleshooting, environment setup) include Linux/macOS guidance if Windows-specific steps are added.
GitHub Create Pull Request
Azure Portal Get subscription and tenant IDs in the Azure portal ...in/articles/azure-portal/get-subscription-tenant-id.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides both Azure PowerShell and Azure CLI options for programmatic access to subscription and tenant IDs. However, PowerShell is consistently mentioned first, and the tip sections use Windows-centric terminology (e.g., 'text document'), which may subtly prioritize Windows users. No Linux/macOS-specific examples or screenshots are provided, but the Azure CLI is referenced, which is cross-platform.
Recommendations
  • Alternate the order of PowerShell and Azure CLI mentions to avoid Windows-first bias.
  • Explicitly state that Azure CLI works on Linux and macOS, and consider adding a brief example or screenshot for those platforms.
  • Use more neutral terminology (e.g., 'text editor' instead of 'text document') to avoid Windows-centric language.
  • Ensure parity in programmatic examples, such as showing both PowerShell and CLI commands side-by-side.
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: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation mentions generating CLI and PowerShell scripts as a key scenario, listing PowerShell before CLI. This ordering subtly prioritizes Windows tooling. No explicit Linux/macOS examples or tools are referenced, and PowerShell is presented as a primary scripting option, which may create friction for Linux/macOS users who typically use Bash or other shells.
Recommendations
  • Explicitly mention Bash or shell script generation alongside PowerShell and CLI.
  • Provide examples or clarify that Azure Copilot can generate scripts for Bash and other Linux/macOS environments.
  • Reorder the list to avoid always listing Windows tools first, or use neutral phrasing (e.g., 'Generating scripts for Azure CLI, Bash, and PowerShell').
GitHub Create Pull Request
Container Registry Azure Container Registry SKU Features and Limits ...articles/container-registry/container-registry-skus.md
Low 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 and showing usage), but consistently lists PowerShell examples after CLI and does not provide explicit Linux/macOS shell examples or mention Bash/Zsh. The CLI examples are cross-platform, but the PowerShell examples are Windows-centric. There is no mention of Linux-specific tools or patterns, and no explicit Bash or shell script examples.
Recommendations
  • Clarify that Azure CLI commands are cross-platform and can be used on Linux, macOS, and Windows.
  • Add explicit Bash/Zsh shell examples where appropriate, especially for Linux/macOS users.
  • Mention that Azure PowerShell is available cross-platform, but highlight that CLI is generally preferred for Linux/macOS.
  • Consider including links or notes about installing Azure CLI and PowerShell on Linux/macOS.
  • Where PowerShell is referenced, add a note for Linux/macOS users about using CLI or PowerShell Core.
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 page primarily references SQL Server Management Studio (SSMS), a Windows-only tool, as the first example for connecting to SQL Managed Instance enabled by Azure Arc. While sqlcmd (cross-platform) is mentioned, SSMS is listed first and no Linux-native GUI tools (such as Azure Data Studio or DBeaver) are referenced. The examples for connecting use sqlcmd, which is available on both Windows and Linux, but there is no explicit Linux/macOS-specific guidance or mention of Linux GUI alternatives. The Azure CLI commands are cross-platform, but the overall tone and tool recommendations favor Windows users.
Recommendations
  • Mention cross-platform SQL client tools such as Azure Data Studio, DBeaver, or Squirrel SQL alongside SSMS.
  • Provide explicit Linux/macOS connection instructions, including any prerequisites for installing sqlcmd on Linux/macOS.
  • List sqlcmd as the primary example, or show both SSMS and sqlcmd examples equally.
  • Add a note about how to install sqlcmd on Linux/macOS, or link to relevant installation documentation.
  • Consider including screenshots or walkthroughs for Linux/macOS users where appropriate.
GitHub Create Pull Request
Azure Arc Install client tools ...b/main/articles/azure-arc/data/install-client-tools.md
Low 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 links for client tools across Windows, Linux, and macOS, but Windows links are often listed first and some instructions (e.g., for curl and kubectl) reference Windows-specific behaviors and PowerShell. Linux installation instructions are less explicit (e.g., 'install curl package'), and there is a note about using cmd.exe instead of PowerShell for curl, but no equivalent Linux/macOS guidance. The documentation assumes familiarity with Windows environments and tools, creating minor friction for Linux/macOS users.
Recommendations
  • List installation instructions for all platforms equally, and avoid always putting Windows first.
  • Provide explicit Linux/macOS installation commands (e.g., 'sudo apt install curl' or 'brew install curl') instead of vague instructions.
  • Add notes for Linux/macOS users where Windows-specific caveats are mentioned (e.g., clarify curl usage differences on Linux/macOS).
  • Where PowerShell-specific notes are given, add equivalent Linux/macOS shell guidance.
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
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_first
Summary
The documentation includes references to Windows-specific services (e.g., 'time.windows.com' as the NTP server, 'sts.windows.net', 'servicebus.windows.net') and lists Windows NTP as the default in notes. Windows terminology and endpoints are mentioned before Linux equivalents, and Windows-specific URLs are present. However, Linux endpoints and requirements are also included (e.g., 'packages.microsoft.com' for Linux packages, 'linuxgeneva-microsoft.azurecr.io' for log collection). No examples or instructions are given that are Windows-only, and Linux requirements are not missing.
Recommendations
  • Clarify that NTP can use Linux-based servers (e.g., 'pool.ntp.org') and provide guidance for both Windows and Linux environments.
  • Avoid listing Windows-specific endpoints (e.g., 'time.windows.com') as the default; instead, mention both Windows and Linux options equally.
  • Where Windows terminology is used (e.g., 'Windows NTP'), add equivalent Linux terminology or examples.
  • Ensure that any references to Windows tools or endpoints are balanced with Linux alternatives, especially in notes and examples.
GitHub Create Pull Request
Azure Arc Manage and maintain the Azure Connected Machine agent ...s/blob/main/articles/azure-arc/servers/manage-agent.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 comprehensive coverage for both Windows and Linux platforms, including installation, upgrade, uninstallation, and proxy configuration. However, there is a mild Windows bias: Windows examples and sections are often presented first, and Windows-specific tools (PowerShell, Group Policy, WSUS, Configuration Manager) are described in greater detail. The cleanup script for removing stale resources is only provided in PowerShell, with no equivalent Bash or Azure CLI example for Linux users. Overall, Linux parity is strong, but Windows-centric tools and ordering create minor friction.
Recommendations
  • Provide equivalent cleanup scripts or guidance for Linux users (e.g., Bash or Azure CLI examples) alongside PowerShell scripts.
  • Where possible, present Windows and Linux instructions in parallel or alternate their ordering to avoid always showing Windows first.
  • Add references to Linux-native automation tools (such as cron, systemd, or Ansible) for agent lifecycle management, similar to the Windows update infrastructure examples.
  • Ensure that all Azure CLI and azcmagent command examples are clearly labeled as cross-platform.
  • Consider including a summary table at the top showing parity of features and management tasks across Windows and Linux.
GitHub Create Pull Request
Azure Arc Azure Arc resource bridge system requirements ...icles/azure-arc/resource-bridge/system-requirements.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation consistently refers to Azure CLI installation and usage, but in the 'Management machine requirements' section, the Azure CLI installation link points to the Windows-specific install page first, and the text refers to 'Azure CLI x64' without clarifying OS parity. There are no explicit Linux/macOS examples or links, and no mention of Linux-specific requirements or considerations for the management machine, despite Azure CLI being cross-platform. No PowerShell or Windows-only tools are referenced, but the ordering and linking suggest a Windows-first bias.
Recommendations
  • Update the 'Management machine requirements' section to clarify that Azure CLI is supported on Windows, Linux, and macOS, and provide install links for all platforms.
  • Explicitly state that the management machine can be any supported OS (Windows, Linux, macOS) and provide guidance for Linux/macOS users.
  • Add examples or notes for Linux/macOS users where relevant, such as file paths, CLI usage, or prerequisites.
  • Avoid linking only to Windows install pages for cross-platform tools like Azure CLI.
GitHub Create Pull Request
Azure Arc CLI reference for `azcmagent connect` ...b/main/articles/azure-arc/servers/azcmagent-connect.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation for `azcmagent connect` shows minor Windows bias by describing the interactive browser login as 'Windows only' and mentioning Windows certificate store options before Linux equivalents. The access token section references the Windows PowerShell cmdlet `Get-AzAccessToken` without mentioning Linux alternatives. However, Linux authentication methods are well-covered, and most examples are generic and applicable cross-platform.
Recommendations
  • Add explicit Linux/macOS equivalents for obtaining access tokens (e.g., using Azure CLI: `az account get-access-token`).
  • Clarify certificate authentication options for Linux (e.g., specify typical Linux certificate storage locations and usage patterns).
  • Present authentication options in a platform-neutral order, or explicitly note Linux/macOS methods where relevant.
  • Where Windows-specific tools (like PowerShell) are mentioned, also provide Linux/macOS alternatives.
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 parity between Windows and Linux VM extensions for Azure Arc-enabled servers, listing both platforms' extensions in separate, equally detailed tables. However, Windows extensions are presented first, which may subtly prioritize Windows users. All deployment methods (Azure CLI, PowerShell, Portal, ARM templates) are mentioned without platform bias, and partner extensions are shown for both OSes. No critical Linux features are missing, and Linux examples are present where relevant.
Recommendations
  • Consider alternating the order of Windows and Linux extension tables, or presenting them side-by-side, to avoid implicit prioritization.
  • Explicitly state that all deployment methods (CLI, PowerShell, Portal, ARM templates) are available for both Windows and Linux, and provide links to Linux-specific usage guides where possible.
  • Ensure that any referenced 'additional information' links for Linux extensions are as comprehensive as their Windows counterparts.
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 both Windows and Linux support for Run command on Azure Arc-enabled servers, but Windows is listed first in the 'Operating Systems' section. There are no explicit Windows-only examples or tools, and Linux-specific notes are included. However, the page links to separate guides for Azure CLI, PowerShell, and REST API usage, which may have further bias but are not analyzed here.
Recommendations
  • List operating systems in alphabetical order (e.g., 'Linux and Windows') to avoid subtle Windows-first bias.
  • Ensure linked pages (CLI, PowerShell, REST) provide parity in examples for both Windows and Linux, including shell/script differences.
  • Add explicit examples or notes highlighting Linux usage where relevant, such as shell script execution or command syntax differences.
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 log file paths are presented first, and PowerShell-specific commands are used for Windows, while Linux examples are given later. Windows-specific tools and paths (e.g., %ProgramData%, PowerShell, .exe invocation) are mentioned before their Linux equivalents. Some error codes reference Windows tools (e.g., PowerShell version requirements) without Linux analogs.
Recommendations
  • Alternate the order of Windows and Linux examples in sections to avoid always presenting Windows first.
  • Where possible, provide Linux-specific troubleshooting tips alongside Windows-specific ones (e.g., for log file locations, permissions, and command syntax).
  • Ensure error codes referencing Windows tools (like PowerShell) also mention Linux equivalents or clarify if not applicable.
  • Use neutral language and structure (e.g., 'On Windows...' and 'On Linux...') instead of always starting with Windows.
  • Highlight Linux log file paths and commands equally, and consider including macOS guidance if applicable.
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 with managed identity on Azure Arc-enabled servers. However, the Windows/PowerShell example is presented first, with more detailed script and output, and references to Windows tools (PowerShell, IIS) appear before Linux equivalents. The 'Related content' section also mentions PowerShell before Azure CLI. Overall, Linux parity is maintained, but Windows is prioritized in ordering and tool references.
Recommendations
  • Present Windows and Linux examples side-by-side or alternate their order to avoid Windows-first bias.
  • Ensure equal detail and explanation for both PowerShell and Bash examples, including output screenshots.
  • In 'Related content', mention Azure CLI before or alongside PowerShell to reflect cross-platform tooling.
  • Where possible, reference Linux tools (e.g., Apache) alongside Windows tools (e.g., IIS) when discussing use cases.
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 focused on Azure Arc-enabled System Center Virtual Machine Manager (SCVMM), which is inherently a Windows-centric technology. The page consistently references Windows Server, Windows Management Framework, WinRM, and Windows operating systems first. Linux is mentioned only as a possible guest OS for VMs, with limited guidance. Windows tools and patterns (such as WinRM, Windows Management Framework, and PowerShell/Win32-OpenSSH) are referenced exclusively or before Linux equivalents. Linux users are advised that deployments from Linux workstations may be slower, but no Linux-specific troubleshooting or parity guidance is provided.
Recommendations
  • Clarify that SCVMM is a Windows-only management platform and that Linux support is limited to guest OS scenarios.
  • Provide explicit guidance for Linux guest OS management, including supported distributions, limitations, and troubleshooting.
  • Where scripts or tools are referenced (such as onboarding scripts), ensure Linux usage is documented and supported, or clarify limitations.
  • Add more details for Linux prerequisites and performance considerations, including recommended configurations.
  • If possible, provide Linux-first examples for installing Arc agents and clarify any differences in the process.
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 provides a balanced overview of Azure Arc-enabled VMware vSphere, but there are subtle signs of Windows bias. Windows/PowerShell examples and tools are sometimes mentioned before Linux equivalents, and PowerShell is highlighted as a primary automation option. However, Linux support is acknowledged throughout, and most features are described as available for both Windows and Linux VMs.
Recommendations
  • Ensure Linux and macOS CLI examples are provided alongside PowerShell, especially in automation and onboarding sections.
  • Mention Linux tools and workflows (e.g., Bash, shell scripting) equally when listing supported automation options.
  • When referencing Azure Automation, clarify that Python runbooks and Linux management are fully supported.
  • Review links and tabs to ensure Linux documentation is as prominent as Windows documentation.
  • Where possible, alternate the order of Windows and Linux mentions to avoid 'Windows-first' perception.
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 presents a generally balanced overview of new features for Azure Arc-enabled VMware vSphere, mentioning both Windows and Linux enhancements. However, Windows-specific features (such as customizing guest OS settings for Windows VMs and Windows Server Management) are listed before Linux-related improvements. Additionally, Azure PowerShell is referenced alongside Azure CLI and REST APIs, but there is no explicit Linux shell example or mention of Bash-specific tooling. Windows tools (like System Center Configuration Manager, Group Policy) are mentioned before Linux equivalents (Ansible), and Windows VM management features are highlighted more prominently.
Recommendations
  • Ensure Linux-related features and examples are given equal prominence and ordering as Windows features.
  • When listing management tools, mention Linux-native tools (e.g., Ansible, Bash scripts) alongside or before Windows tools.
  • Provide explicit Linux shell (Bash) examples for agent installation and VM management where PowerShell is referenced.
  • Clarify when features are Windows-only to avoid confusion for Linux users.
  • Add links or references to Linux documentation and guides where relevant.
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: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation provides both Windows (PowerShell) and Linux (Bash) examples for running the onboarding script, but Windows instructions and notes are presented first in several sections. The retry command is also shown for Windows before Linux. There is no evidence of missing Linux examples or exclusive mention of Windows tools; parity is maintained, but Windows is prioritized in ordering.
Recommendations
  • Present Windows and Linux instructions side-by-side or in parallel tabs to avoid implicit prioritization.
  • Alternate the order of Windows and Linux sections, or explicitly state that both platforms are equally supported.
  • Ensure screenshots and UI references do not assume Windows environments unless necessary.
  • Add a brief statement at the start clarifying that both Windows and Linux workstations are fully supported.
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 every command, but consistently presents Bash examples first. No Windows-specific tools or patterns are mentioned, and Linux parity is maintained throughout. There is a minor bias in example ordering, but all tasks are fully documented for Linux/macOS users.
Recommendations
  • Continue providing both Bash and PowerShell examples for all commands.
  • Consider explicitly stating that Bash examples are suitable for Linux/macOS terminals, and PowerShell for Windows environments.
  • Optionally, alternate the order of examples or clarify that Bash is the default for cross-platform use.
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: 1 bias type
Detected Bias Types
⚠ī¸ windows_first
Summary
The documentation provides both Bash and PowerShell examples for all major steps, ensuring Linux/macOS and Windows users are covered. However, PowerShell examples are consistently shown after Bash, indicating a minor 'windows_first' bias in ordering. No Windows-only tools or patterns are used, and Linux examples are present throughout.
Recommendations
  • Consider alternating the order of Bash and PowerShell tabs in some sections to avoid implicit prioritization.
  • Explicitly mention that Bash examples are suitable for Linux/macOS and PowerShell for Windows, for clarity.
  • Ensure any troubleshooting or advanced sections also provide parity between Bash and PowerShell.
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 every CLI operation, ensuring parity for Linux/macOS and Windows users. However, in most sections, Bash examples are presented before PowerShell, which is a minor bias in favor of Linux/macOS users rather than Windows. There are no Windows-only tools or patterns, and all commands use the cross-platform Azure CLI. No critical steps are Windows-only, and Linux/macOS users can complete the tutorial without friction.
Recommendations
  • Maintain the current parity by continuing to provide both Bash and PowerShell examples.
  • Consider alternating the order of Bash and PowerShell examples or explicitly stating that both are equally supported.
  • Ensure any future additions (such as troubleshooting or advanced scripting) include both Bash and PowerShell variants.
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 all command-line steps, ensuring parity for Linux/macOS and Windows users. However, in each section, Bash examples are presented before PowerShell, which is the opposite of a Windows bias (i.e., a slight Linux-first ordering). No exclusive Windows tools, PowerShell-heavy content, or missing Linux examples are present.
Recommendations
No action needed. The documentation already provides both Bash (Linux/macOS) and PowerShell (Windows) examples for all commands, and does not favor Windows tools or patterns. If desired, clarify in the introduction that both platforms are fully supported and users can select their preferred tab.
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
⚠ī¸ powershell_heavy ⚠ī¸ 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 present throughout, and in some sections (such as variable naming and file paths), Windows conventions (e.g., backslashes in file paths) are used. Bash examples are always shown first, but the PowerShell tab is equally detailed. No Windows-only tools or patterns are used; all commands rely on the Azure CLI and Helm, which are cross-platform.
Recommendations
  • Ensure that file path examples in PowerShell use forward slashes or note that backslashes are Windows-specific.
  • Clarify that PowerShell examples are intended for Windows users, while Bash is for Linux/macOS.
  • Consider adding a brief note at the start explaining that all commands are cross-platform and that users should choose the tab matching their OS.
  • Double-check that all referenced files (e.g., YAML, JSON) are accessible and usable on both platforms.
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 release notes for Azure Arc Workload Orchestration generally provide cross-platform guidance, focusing on Azure CLI and portal usage. However, in the May 2025 release, CLI examples are shown exclusively in PowerShell syntax, which is Windows-centric. Bash syntax is used elsewhere, but PowerShell appears first and is the only example for configuration file operations, suggesting a mild Windows bias.
Recommendations
  • Provide equivalent Bash examples alongside PowerShell for CLI commands, especially for configuration operations.
  • Clarify that Azure CLI is cross-platform and can be used on Linux/macOS, not just Windows.
  • Ensure that CLI instructions are not presented exclusively in Windows syntax.
  • Consider alternating the order of examples or showing Bash first in some cases.
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, in each section, Bash examples are shown first, followed by PowerShell. No Windows-specific tools, patterns, or terminology are used exclusively or prioritized. All commands use the Azure CLI, which is cross-platform. There are no missing Linux examples or Windows-only instructions.
Recommendations
  • Maintain the current parity between Bash and PowerShell examples.
  • Consider explicitly stating that all examples are cross-platform and that Azure CLI works on Windows, Linux, and macOS.
  • If possible, add a brief note about using Azure CLI in macOS environments to further reassure non-Windows 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 examples for both Azure CLI and Azure PowerShell, but the PowerShell section is given its own heading and is presented after the CLI section. The CLI examples are cross-platform, but the PowerShell section is Windows-centric, as PowerShell is most commonly used on Windows (though available on Linux/macOS). There are no explicit Linux/macOS shell examples (e.g., Bash), but the CLI commands are suitable for all platforms. No Windows-only tools or patterns are used, and the documentation does not omit Linux equivalents.
Recommendations
  • Clarify that Azure CLI commands work on Windows, Linux, and macOS, and consider explicitly stating this in the CLI section.
  • Optionally, add a short Bash shell script example for deploying a dashboard template to reinforce Linux parity.
  • In the PowerShell section, mention that PowerShell Core is available cross-platform, or link to instructions for installing PowerShell on Linux/macOS.
  • Continue to provide Azure CLI examples as the primary cross-platform method, and ensure PowerShell is presented as an alternative, not the default.
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: 2 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first
Summary
The documentation provides examples for both Azure CLI and Azure PowerShell throughout, but consistently presents PowerShell examples alongside CLI, and references PowerShell-specific tools and patterns. There is a minor Windows bias in the use of PowerShell, which is more commonly associated with Windows environments, and in the explicit mention of PowerShell installation and usage. However, Azure CLI is cross-platform and all examples are available for it, mitigating the impact for Linux/macOS users. No Linux-specific tools or shell examples (e.g., Bash) are provided, but the CLI examples are sufficient for Linux parity.
Recommendations
  • Clarify that Azure CLI is fully supported on Linux/macOS and is the recommended cross-platform option.
  • Consider adding brief Bash shell example snippets for common import scenarios, or explicitly state that Azure CLI commands work identically on Linux/macOS.
  • Mention that PowerShell Core is available cross-platform, but highlight Azure CLI as the default for Linux/macOS users.
  • Add a note in the prerequisites section indicating that Linux/macOS users should use Azure CLI, and provide a link to CLI installation for those platforms.
GitHub Create Pull Request
Container Registry Manage Public Content in Private Container Registry ...icles/container-registry/buffer-gate-public-content.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 Azure CLI and Azure PowerShell examples for importing images into Azure Container Registry. However, the PowerShell example is given equal prominence to the CLI example, and PowerShell is a Windows-centric tool, which may create friction for Linux/macOS users. Additionally, the order of tools mentioned when creating a registry lists Azure PowerShell before other tools, which subtly prioritizes Windows tooling. No Linux-specific examples or shell scripts are provided, and there is no explicit mention of Linux/macOS workflows or tools.
Recommendations
  • Provide Bash or shell script examples for Linux/macOS users alongside Azure CLI and PowerShell examples.
  • Clarify that Azure CLI is cross-platform and recommend it as the primary tool for Linux/macOS users.
  • When listing tools, mention Azure CLI before PowerShell to avoid subtle Windows-first bias.
  • Add explicit statements or links for Linux/macOS users regarding authentication and registry management workflows.
GitHub Create Pull Request
Container Registry Azure Container Registry Authentication Options Explained ...ontainer-registry/container-registry-authentication.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_first ⚠ī¸ minor_windows_tools
Summary
The documentation provides authentication examples for both Azure CLI and Azure PowerShell throughout, but PowerShell is featured equally alongside CLI, which is cross-platform. However, PowerShell examples are given in every section, and the 'Next steps' section lists PowerShell before Linux-native alternatives. There are no explicit Linux/macOS examples (e.g., Bash, shell scripting), and Windows-centric tools (PowerShell) are mentioned as a primary option, even though PowerShell Core is cross-platform. The use of Docker and Azure CLI is platform-neutral, but the documentation does not highlight Linux/macOS usage or shell-specific nuances. The mention of setting DOCKER_COMMAND for Podman is a positive step for Linux parity.
Recommendations
  • Add explicit Bash/shell examples for authentication flows, especially for token handling and scripting.
  • Clarify that Azure CLI and Docker commands work on Linux/macOS, and provide any OS-specific notes (e.g., file paths, environment variable syntax).
  • Balance 'Next steps' by including links to Linux/macOS guides or Bash-based workflows.
  • Consider mentioning PowerShell Core's cross-platform nature, or linking to Linux/macOS installation guides.
  • Where PowerShell is featured, also show equivalent Bash or shell scripting approaches.
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, as Helm and Azure CLI are available on Windows, Linux, and macOS. However, there are subtle signs of Windows bias: the environment variable example uses the Windows 'set' command instead of the cross-platform 'export', and the prerequisites list Azure PowerShell as an option for creating AKS clusters before mentioning the Azure portal. No explicit Linux/macOS-specific instructions or examples are provided, and the 'set' command may confuse Linux/macOS users. All CLI examples otherwise use cross-platform tools (Helm, Azure CLI), but the ordering and lack of Linux/macOS parity in environment variable examples create minor friction.
Recommendations
  • Replace the 'set' command for environment variables with 'export' (or show both, e.g., 'set' for Windows CMD, 'export' for Bash/Linux/macOS).
  • Explicitly state that Helm and Azure CLI commands are cross-platform and provide any OS-specific notes where relevant.
  • When listing options for creating AKS clusters, mention Azure CLI and Azure portal before Azure PowerShell, or clarify PowerShell is Windows-specific.
  • Add a note or section for Linux/macOS users where commands differ (e.g., environment variable syntax).
GitHub Create Pull Request