← Back to Dashboard
225
Pages Scanned
49
Pages Flagged
225
Changed Pages
21.8%
% Pages Flagged

Live Progress

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

Scan Information

Started At: 2026-03-05 00:00:08

Finished At: In Progress

Status: in_progress

Target Repo: Azure Management

Current Phase: discovery

Files Queued: 225

Files Completed: 225

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_first ⚠ī¸ windows_tools ⚠ī¸ missing_linux_example
Summary
The documentation page is heavily biased toward Windows environments. All script examples use PowerShell (.ps1) and require opening a PowerShell terminal. The prerequisites recommend using 'winget', a Windows-only package manager, for installing Azure CLI and kubectl. No Bash or Linux/macOS shell equivalents are provided, and there is no mention of how to run the onboarding scripts or set up the environment on Linux or macOS. This creates friction for non-Windows users and may prevent them from completing the onboarding process without significant adaptation.
Recommendations
  • Provide Bash or shell script equivalents for onboarding (e.g., infra_onboarding.sh, cm_onboarding.sh) or document how to run the PowerShell scripts on Linux/macOS (using PowerShell Core).
  • Add instructions for installing Azure CLI and kubectl using platform-agnostic methods (e.g., apt, yum, brew, or manual download) instead of only 'winget'.
  • Explicitly state PowerShell Core compatibility and provide guidance for Linux/macOS users on how to install and use PowerShell if scripts are cross-platform.
  • Include Linux/macOS terminal examples alongside PowerShell examples, or at least clarify any limitations.
  • Add a note about supported platforms and any required adaptations for non-Windows environments.
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 nearly all CLI and scripting examples using PowerShell syntax, assumes Windows-style file paths in JSON templates, and references PowerShell scripts for orchestration tasks. There are no Bash or Linux shell equivalents, and Windows file paths (e.g., C:\, E:\) are used throughout. This creates friction for Linux/macOS users, who must adapt examples and scripts to their environments.
Recommendations
  • Provide Bash or Linux shell equivalents for all PowerShell CLI examples, especially for az commands.
  • Use cross-platform file path conventions in JSON templates (e.g., /home/user/...), or clarify how to adapt for Linux/macOS.
  • Offer sample onboarding scripts in Bash or Python, or note how Linux users can run the same orchestration steps.
  • Mention that PowerShell scripts can be run on Linux/macOS with PowerShell Core, or provide guidance for native shell usage.
  • Add notes or sections for Linux/macOS users, highlighting any differences or adaptations needed.
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 for disaster recovery operations of the Azure Arc resource bridge VM provides only PowerShell examples and instructions, with no mention of Bash, Linux, or macOS equivalents. The onboarding script is referenced and shown as a PowerShell script (.ps1), and all command-line instructions are given in PowerShell syntax. There is no guidance for Linux or macOS users, nor any indication of cross-platform compatibility for the onboarding script.
Recommendations
  • Clarify whether the onboarding script can be run on Linux/macOS, or if it is strictly Windows/PowerShell-only.
  • If the onboarding script is cross-platform, provide Bash or shell examples and instructions for Linux/macOS users.
  • If the onboarding script is Windows-only, explicitly state this limitation early in the documentation.
  • Mention any prerequisites for Linux/macOS users, such as needing PowerShell Core or alternative tools.
  • Consider providing a table or section comparing Windows and Linux/macOS steps, or linking to Linux-specific guidance if available.
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 Azure PowerShell cmdlets (Invoke-AksEdgeNodeCommand) for Linux node configuration, without providing native Linux shell alternatives. There is an assumption that the user is running commands from a Windows environment, even when targeting Linux nodes. No Linux-native commands (e.g., SSH, direct sysctl usage) are shown for critical configuration steps.
Recommendations
  • Provide native Linux shell commands for sysctl configuration, such as 'ssh user@linux-node sudo sysctl ...' or direct shell access.
  • Clarify whether Invoke-AksEdgeNodeCommand is required, or if Linux users can perform these steps directly on the node.
  • Add examples using Linux tools and patterns (e.g., nano/vim for editing files, direct bash commands) alongside PowerShell/Windows-centric examples.
  • Explicitly state if the workflow assumes a Windows management workstation, and offer Linux/macOS alternatives if possible.
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 provides examples and instructions that are primarily Windows-centric, such as using Windows file paths (C:\Backupfiles\test.bak), referencing Windows tools (SQL Server Management Studio, Notepad/OneNote), and omitting explicit Linux/macOS equivalents for backup and file copy operations. Linux/macOS users are left to infer how to adapt steps for their platforms, creating friction.
Recommendations
  • Include Linux/macOS file path examples (e.g., /home/user/backup/test.bak) alongside Windows paths.
  • Mention cross-platform alternatives to Notepad/OneNote (e.g., gedit, nano, TextEdit) when suggesting where to save credentials.
  • Clarify that SQL Server Management Studio (SSMS) is Windows-only and suggest Azure Data Studio or command-line tools (sqlcmd) for Linux/macOS users.
  • Provide explicit instructions or examples for backing up databases on Linux/macOS SQL Server instances.
  • Show kubectl cp examples using Linux/macOS source paths.
  • Add notes or sections highlighting any platform-specific differences or prerequisites.
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: 3 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_authentication
Summary
The documentation references several Windows-centric tools and features, such as PowerShell scripting support, SQL Server Management Studio (SSMS), SQL Server Data Tools (SSDT), and Windows Authentication. PowerShell scripting is listed as a manageability feature, and Windows Authentication is included as a security feature. While Azure PowerShell is marked as 'No' in the tools table, SQL Server PowerShell is marked as 'Yes'. The documentation does not provide Linux/macOS-specific examples or mention cross-platform alternatives (e.g., Bash scripting, Linux authentication mechanisms, or Linux-native SQL tools). However, the overall impact is moderate, as most features are platform-agnostic and Azure Arc SQL Managed Instance is intended to be cross-platform.
Recommendations
  • Add examples or references for Linux/macOS users, such as Bash scripting or cross-platform CLI usage.
  • Mention cross-platform tools like Azure Data Studio, which runs on Windows, Linux, and macOS.
  • Clarify the limitations of Windows Authentication for non-Windows environments and suggest alternatives (e.g., Microsoft Entra authentication, SQL authentication).
  • Highlight Linux-native management patterns or tools where applicable.
GitHub Create Pull Request
Azure Arc What's new with Azure Connected Machine agent ...main/articles/azure-arc/servers/agent-release-notes.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 both Windows and Linux release notes and download links, but consistently lists Windows first in download links and tables. Known issues and troubleshooting steps are exclusively for Windows, with only Windows/PowerShell/Command Prompt commands provided. Some improvements and bug fixes are described only for Windows tools (e.g., MSI installer, PowerShell scripts), with no Linux equivalents or troubleshooting guidance. Linux-specific issues are less detailed, and Linux users may need to consult external links for installation or troubleshooting.
Recommendations
  • Alternate the order of Windows and Linux in download links and tables, or present them side-by-side to avoid implicit prioritization.
  • For troubleshooting and known issues, provide Linux equivalents or explicitly state if the issue is Windows-only. If Linux users may encounter similar issues, include Linux commands (e.g., chmod/chown for file permissions) where appropriate.
  • When referencing Windows tools (e.g., PowerShell, MSI), add Linux equivalents (e.g., shell scripts, RPM/DEB package management) or clarify if a feature/fix is Windows-only.
  • Ensure Linux-specific known issues and troubleshooting steps are as detailed as Windows ones, or state explicitly if there are none.
  • Consider a dedicated section for Linux troubleshooting if parity is not possible in-line.
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 HTTP/2 issues, and Windows-specific tools (e.g., Remote PowerShell, RDP) are mentioned. Linux-specific troubleshooting commands are largely absent, and Windows terminology (e.g., 'management machine', 'console session', 'RDP') is used preferentially. Examples for checking DNS resolution and connectivity are often given using Windows tools (PowerShell, ping, nslookup) with Linux equivalents missing or mentioned second. The GLIBC error is the only section directly referencing Linux, but overall, Linux/macOS users may face friction due to lack of parity in examples and troubleshooting steps.
Recommendations
  • Add Linux/macOS equivalents for all troubleshooting commands (e.g., curl, wget, dig, ping, ssh) alongside Windows/PowerShell examples.
  • When referencing PowerShell, also provide Bash or shell script alternatives for Linux/macOS users.
  • Clarify that 'management machine' can be Windows, Linux, or macOS, and provide guidance for each platform.
  • Include troubleshooting steps for Linux-specific issues (e.g., file permissions, SSH folder access) and reference common Linux distributions.
  • Ensure that CLI commands and environment variable configuration examples (e.g., HTTPS_PROXY, NO_PROXY) are shown for both Windows and Linux/macOS shells.
GitHub Create Pull Request
Azure Arc Simplify Network Configuration Requirements with Azure Arc Gateway ...cs/blob/main/articles/azure-arc/servers/arc-gateway.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example ⚠ī¸ windows_tools
Summary
The documentation generally provides both Azure CLI and PowerShell examples for resource creation and management, but PowerShell (a Windows-centric tool) is consistently presented as a primary option. In several sections, PowerShell commands are shown alongside CLI, but there is no explicit mention of Bash or Linux shell usage for the CLI commands, nor are there Linux-specific command-line nuances or troubleshooting tips. The 'Monitor Azure Arc gateway traffic' section does provide both Windows and Linux log file locations, but overall, the documentation assumes familiarity with Windows tools and sometimes omits Linux-first perspectives.
Recommendations
  • Explicitly state that Azure CLI commands can be run on Linux/macOS and provide Bash-style command examples where appropriate.
  • Add Linux/macOS-specific notes or troubleshooting steps where differences exist (e.g., file paths, permissions, environment variables).
  • When listing command-line options, consider showing Bash (Linux/macOS) syntax first or equally alongside PowerShell.
  • Clarify that PowerShell is not required for Linux/macOS users and that all operations can be performed with Azure CLI.
  • In sections referencing Windows tools or paths, always provide the Linux/macOS equivalent immediately after or in parallel.
GitHub Create Pull Request
Azure Arc Azure Connected Machine Agent Deployment Options .../main/articles/azure-arc/servers/deployment-options.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 deployment options for both Linux and Windows, but several onboarding methods are Windows-specific or use Windows-centric tools (e.g., PowerShell, Windows Admin Center, Configuration Manager, Group Policy). PowerShell is mentioned as a cross-platform option, but Windows-specific methods are listed separately and in greater detail. Linux-specific automation tools (like Bash scripts or cloud-init) are not highlighted, and PowerShell is presented as a primary automation method, which may create friction for Linux users.
Recommendations
  • Add Linux-specific onboarding examples using Bash scripts, shell commands, or cloud-init, especially for at-scale deployments.
  • Clarify which PowerShell methods are cross-platform and provide equivalent Linux command-line examples where possible.
  • Highlight Ansible and other Linux-native automation tools earlier in the onboarding methods table to improve parity.
  • Consider adding a section or links for Linux/macOS users outlining recommended tools and workflows for onboarding.
  • Ensure that Linux and Windows onboarding options are presented with equal prominence and detail.
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 both Windows and Linux instructions for all major lifecycle tasks (install, upgrade, uninstall, proxy config), using clear tabbed sections. However, Windows examples and tools (PowerShell, Group Policy, Microsoft Update, Control Panel, Msiexec) are often described first and in greater detail, with more step-by-step guidance and scripting. The cleanup script for stale resources is only provided in PowerShell, with no Linux shell equivalent. Windows-specific tools and patterns (e.g., Group Policy, Control Panel, Msiexec, Windows Update) are mentioned exclusively, while Linux instructions rely on standard package managers but lack advanced scripting or automation examples.
Recommendations
  • Provide Linux shell (bash) equivalents for the PowerShell cleanup script, using Azure CLI or azcmagent.
  • Ensure scripting and automation examples are available for Linux, not just Windows/PowerShell.
  • Where possible, present Windows and Linux instructions in parallel, rather than Windows-first.
  • Add more detail to Linux instructions, such as troubleshooting, automation, and advanced usage.
  • Mention Linux-native tools for update automation (e.g., cron, unattended-upgrades) where relevant.
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 each VM extension, ensuring parity in template usage. However, all deployment commands and walkthroughs exclusively use Azure PowerShell, with no Azure CLI or Bash examples. Additionally, PowerShell commands and Windows-style file paths are shown first and exclusively in deployment sections, which may create friction for Linux/macOS users.
Recommendations
  • Add Azure CLI deployment examples alongside PowerShell commands, especially for template deployment.
  • Mention that Azure CLI can be used on Linux/macOS and provide equivalent CLI syntax.
  • Use platform-neutral file paths (e.g., './Templates/AzureMonitorAgent.json') or clarify path conventions for different OSes.
  • Explicitly state that PowerShell is cross-platform, but highlight CLI as a native option for Linux/macOS users.
GitHub Create Pull Request
Azure Arc How to migrate from legacy Log Analytics agents in non-Azure environments with Azure Arc ...in/articles/azure-arc/servers/migrate-legacy-agents.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 both Windows and Linux context, but Windows-specific tools (Windows Admin Center, Windows Server Graphical Installer) and PowerShell are mentioned first or exclusively in several deployment sections. Linux equivalents (e.g., Bash, Ansible) are referenced, but Windows approaches are prioritized or described in more detail. Some deployment options and standalone agent installation guidance are Windows-centric.
Recommendations
  • Ensure Linux deployment examples (e.g., Bash scripts, Ansible) are given equal prominence and detail alongside Windows/PowerShell examples.
  • Add explicit instructions or links for Linux graphical installers or management tools, if available.
  • When listing deployment methods, alternate the order or group by OS rather than listing Windows tools first.
  • Provide standalone Azure Monitor Agent installation guidance for Linux client machines, if supported, or clarify OS limitations.
GitHub Create Pull Request
Azure Arc Run command on Azure Arc-enabled servers (preview) ...cs/blob/main/articles/azure-arc/servers/run-command.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 provides extensive PowerShell-based examples and references to Windows-specific tools (e.g., New-NetFirewallRule, .ps1 scripts, New-AzStorageBlobSASToken), with Windows scenarios and terminology often appearing first or exclusively. Linux-specific examples and guidance are minimal or missing, especially in REST API and PowerShell sections, making it harder for Linux users to follow or adapt the instructions.
Recommendations
  • Add Linux-specific script examples (e.g., using bash or shell scripts) alongside PowerShell examples in all sections.
  • In REST API examples, include a Linux scenario (e.g., configuring iptables or ufw) and reference .sh scripts.
  • Balance PowerShell and Azure CLI coverage, ensuring both Windows and Linux use cases are equally represented.
  • When referencing tools like New-AzStorageBlobSASToken, clarify alternatives for Linux users (e.g., Azure CLI commands).
  • Where possible, avoid defaulting to Windows terminology or examples; alternate order or provide parallel examples.
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
⚠ī¸ windows_first ⚠ī¸ powershell_heavy ⚠ī¸ missing_linux_example
Summary
The documentation provides recovery instructions and a downloadable script exclusively for Windows environments, using PowerShell syntax and terminology. There are no examples or guidance for performing the recovery from Linux or macOS systems, nor is there mention of cross-platform alternatives.
Recommendations
  • Provide equivalent recovery instructions and scripts for Linux/macOS environments, using Bash or cross-platform tools where possible.
  • Clearly indicate if the recovery process is only supported from Windows, and explain why (e.g., dependencies on Windows-only tools or APIs).
  • If feasible, offer a platform-agnostic version of the recovery script (e.g., written in Python or using Azure CLI) to support non-Windows users.
  • Add a section or note addressing Linux/macOS users, even if only to clarify current limitations or provide workarounds.
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: 4 bias types
Detected Bias Types
⚠ī¸ powershell_heavy ⚠ī¸ windows_tools ⚠ī¸ windows_first ⚠ī¸ missing_linux_example
Summary
The documentation demonstrates a notable Windows bias, especially in the 'Auto Arc-enablement script' section, where only PowerShell scripts and Windows Task Scheduler are referenced for automation, with no equivalent Linux shell or cron job examples. The instructions for running the helper script assume a Windows environment (e.g., PowerShell, Set-ExecutionPolicy), and there is no guidance for Linux/macOS users on how to automate at scale. Out-of-band methods mention Ansible, but the primary at-scale automation path is Windows-centric.
Recommendations
  • Provide equivalent Bash/shell script examples for Linux/macOS environments, including instructions for running the helper script on those platforms.
  • Include examples for scheduling the script with Linux cron, not just Windows Task Scheduler.
  • Clarify whether the helper script is cross-platform (PowerShell Core or Bash), and if not, provide a Linux-compatible version.
  • In sections where PowerShell is used, add parallel Linux/macOS command examples or explicitly state if only Windows is supported.
  • Ensure that links to automation methods (e.g., Ansible) are surfaced as equally viable, not just as out-of-band alternatives.
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 steps and script invocation. There are no equivalent instructions or examples for running the script on Linux/macOS, nor is it clarified whether the script is cross-platform. Windows instructions are presented first and in greater detail, while Linux users are left without guidance for script execution.
Recommendations
  • Clarify whether the deboarding script can be run on Linux/macOS (e.g., with PowerShell Core or Azure CLI).
  • Provide explicit instructions for running the script on Linux/macOS, including prerequisites and command examples.
  • Mention any platform-specific limitations or requirements for the script.
  • Present Windows and Linux/macOS instructions in parallel or note platform differences clearly.
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 Bash, shell, or Linux/macOS command examples, nor any mention of how to run the script or achieve equivalent functionality on non-Windows platforms. The script is distributed only as a .ps1 file, which is a Windows/PowerShell format.
Recommendations
  • Provide instructions for running the PowerShell script on Linux/macOS using PowerShell Core (pwsh), including example commands.
  • Offer a Bash or shell script alternative for Linux/macOS users, or clarify if PowerShell Core is required and how to install it.
  • Explicitly state platform requirements and compatibility for the script.
  • Add a section addressing Linux/macOS users, including troubleshooting or prerequisites for using PowerShell scripts on those platforms.
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 ways: Windows tools (winget) are used for kubectl installation without Linux/macOS alternatives; archive extraction instructions use Expand-Archive (a Windows/PowerShell cmdlet) in both Bash and PowerShell tabs, with no Linux/macOS equivalent (e.g., unzip); Bash examples frequently use Windows-style file paths (C:\path\to\...), and Windows tools are mentioned before Linux-native ones. These patterns create friction for Linux/macOS users, especially in initial setup steps.
Recommendations
  • Provide Linux/macOS installation instructions for kubectl (e.g., using curl or package managers like apt, brew, or yum).
  • Replace or supplement Expand-Archive with unzip or tar commands for Bash/Linux/macOS users.
  • Use platform-appropriate file path examples in Bash sections (e.g., /home/user/archive.zip for Linux/macOS).
  • Explicitly mention cross-platform alternatives and clarify which commands are Windows-only.
  • Ensure Bash examples are truly Bash/Linux/macOS compatible, not just PowerShell syntax reused.
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_tools ⚠ī¸ missing_linux_example
Summary
The documentation consistently uses PowerShell syntax for all CLI examples (e.g., variable references like $rg, $subId, and .ps1 scripts), and provides only PowerShell scripts for automation (bulk_deployment.ps1, workflow-delete.ps1). There are no Bash/Linux shell equivalents or instructions for Linux/macOS users, and no mention of how to run the provided scripts or commands on non-Windows platforms.
Recommendations
  • Provide all Azure CLI command examples in both PowerShell and Bash syntax, or use cross-platform syntax (e.g., az CLI commands with Bash-style variable references).
  • Offer Bash shell script equivalents for automation tasks currently only available as .ps1 PowerShell scripts, or clarify if the .ps1 scripts are cross-platform (e.g., via PowerShell Core).
  • Explicitly state whether the provided PowerShell scripts can be run on Linux/macOS using PowerShell Core, and provide installation instructions if so.
  • Add notes or tabs for Linux/macOS users where relevant, especially for automation and scripting sections.
  • Avoid using Windows-specific variable syntax (e.g., $var) in generic CLI examples, or provide both Windows and Linux/macOS variants.
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 migration script and usage example, with no mention of Linux/macOS-compatible alternatives or instructions. The script appears to require PowerShell, which is traditionally Windows-centric, and there is no guidance for users on Linux or macOS platforms.
Recommendations
  • Provide instructions for running the migration script using PowerShell Core (pwsh), which is cross-platform, and clarify compatibility.
  • Offer a Bash or shell script alternative if feasible, or explain how Linux/macOS users can use PowerShell Core to run the script.
  • Explicitly state platform requirements and provide troubleshooting tips for non-Windows environments.
  • Add examples for Linux/macOS users, including installation steps for PowerShell Core if required.
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. Nearly all code examples (except for a few kubectl and docker commands) are provided in PowerShell, with no equivalent Bash or Linux shell examples for critical steps. Even commands that are cross-platform (az CLI, docker, kubectl) are often shown in PowerShell syntax or with Windows-specific variable usage. Bash/Linux parity is only provided in the 'Troubleshoot service groups' section, where both Bash and PowerShell tabs are present. This creates friction for Linux/macOS users, who must translate PowerShell commands and variable handling to their environment.
Recommendations
  • Provide Bash/Linux shell equivalents for all PowerShell examples, especially for az CLI, docker, and kubectl commands.
  • Use cross-platform variable syntax (e.g., $VAR for PowerShell, $VAR for Bash) and avoid Windows-specific PowerShell constructs where possible.
  • Where file encoding is discussed, clarify how to check and convert encoding on Linux/macOS (e.g., using iconv or file editors like nano/vim).
  • For steps involving JSON manipulation, provide jq or Bash alternatives to PowerShell's ConvertTo-Json.
  • Ensure all troubleshooting steps can be followed on Linux/macOS by explicitly stating any OS-specific requirements or limitations.
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 ⚠ī¸ missing_linux_example
Summary
The documentation provides authentication options for Azure Container Registry, with examples for both Azure CLI and Azure PowerShell. However, PowerShell examples are given equal prominence to CLI examples, and PowerShell is a Windows-centric tool. The CLI examples are generic and cross-platform, but there is no explicit mention of Linux/macOS-specific workflows or shell environments (e.g., Bash). Additionally, the 'Next steps' section lists PowerShell before Linux-focused alternatives, and there are no Linux/macOS-specific troubleshooting tips or examples. The documentation assumes familiarity with Docker and Azure CLI, which are cross-platform, but the presence of PowerShell throughout and lack of explicit Linux/macOS guidance creates friction for non-Windows users.
Recommendations
  • Add explicit Bash/Linux/macOS shell examples alongside Azure CLI commands (e.g., show export of tokens, environment variable usage in Bash).
  • Clarify that Azure CLI commands are cross-platform and provide links or tips for installing CLI on Linux/macOS.
  • Include troubleshooting tips for Linux/macOS users, such as Docker daemon issues or file permissions.
  • Balance the prominence of PowerShell and CLI examples, or note that PowerShell is primarily for Windows users.
  • In 'Next steps', add links for Linux/macOS getting started guides or make CLI the first recommendation.
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 instructions for client tools across platforms, but Windows links are often listed first and Windows-specific notes (e.g., cmd.exe vs PowerShell, PowerShell's curl alias) are emphasized. Linux installation instructions are less explicit (e.g., 'install curl package' without a link), and Linux/macOS are sometimes mentioned after Windows. There is a minor bias toward Windows in ordering and detail.
Recommendations
  • List Linux/macOS installation links before or alongside Windows, rather than after.
  • Provide explicit Linux/macOS installation instructions or links for all tools (e.g., link to curl installation for Linux/macOS, not just 'install curl package').
  • Balance Windows-specific notes (e.g., PowerShell quirks) with equivalent Linux/macOS notes where relevant.
  • Ensure all examples and instructions are equally detailed for Linux/macOS users.
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: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ windows_tools
Summary
The documentation provides troubleshooting guidance for both Windows and Linux, but in several sections Windows is presented first (e.g., log file paths, command examples), and Windows-specific tools and patterns (such as PowerShell syntax and environment variables) are referenced. Linux parity is generally maintained, but Windows examples and terminology are often prioritized or shown before Linux equivalents.
Recommendations
  • Present Windows and Linux examples side-by-side or alternate their order to avoid Windows-first bias.
  • Ensure Linux log file paths and troubleshooting steps are as prominent as Windows paths.
  • Where Windows-specific tools (e.g., PowerShell, environment variables) are mentioned, provide equivalent Linux commands and environment variable usage.
  • Clarify that both Windows and Linux are equally supported, and avoid defaulting to Windows terminology when describing generic steps.
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 on Azure Arc-enabled servers. However, the Windows/PowerShell example is presented first, with more detailed scripting and output imagery. PowerShell is referenced as the primary tool for Windows, while Bash is used for Linux. The prerequisites and links are balanced, but Windows is subtly prioritized in ordering and detail.
Recommendations
  • Alternate the order of Windows and Linux examples, or present them side-by-side for parity.
  • Ensure output examples and screenshots are equally detailed for both platforms.
  • Explicitly mention cross-platform tools (e.g., Azure CLI) in the main workflow, not just in 'Related content'.
  • Clarify that both Windows and Linux are fully supported and provide links to platform-specific troubleshooting.
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 the 'Run the script' and 'Retry command' sections. There is a minor bias in ordering, but Linux parity is maintained throughout with equivalent instructions and tools.
Recommendations
  • Present Windows and Linux instructions in parallel or alternate their order in sections to avoid implicit prioritization.
  • Explicitly state that both Windows and Linux are fully supported at the beginning of relevant sections.
  • Consider grouping OS-specific instructions in tabs or collapsible sections for equal visibility.
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 consistently presents Bash examples first, followed by PowerShell. There are no Windows-specific tools or patterns used; all commands rely on the Azure CLI and Helm, which are cross-platform. No critical steps are Windows-only, and Linux/macOS users can complete all tasks without friction.
Recommendations
  • Continue to provide both Bash and PowerShell examples for parity.
  • Consider alternating the order of Bash and PowerShell tabs in future documentation to avoid subtle 'windows_first' bias.
  • Explicitly state that all commands are cross-platform and supported on Linux, macOS, and Windows.
  • Add a brief note clarifying that Helm and Azure CLI are available on all major OS 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: 1 bias type
Detected Bias Types
⚠ī¸ none
Summary
The documentation for 'Release Notes for Workload Orchestration' is cross-platform and neutral. It consistently uses Azure CLI examples (which are cross-platform) and does not reference Windows-specific tools, PowerShell, or Windows-first workflows. No Windows bias is present.
Recommendations
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 is mentioned and a Linux-compatible command is provided, SSMS is listed first and no Linux-native GUI tools (such as Azure Data Studio or DBeaver) are referenced. The documentation does not provide parity in GUI client recommendations for Linux/macOS users, but does include a command-line example usable on both platforms.
Recommendations
  • Mention cross-platform SQL client tools such as Azure Data Studio, DBeaver, or Squirrel SQL alongside SSMS.
  • Provide explicit Linux/macOS connection instructions and examples, including screenshots or steps for using Azure Data Studio.
  • Clarify that sqlcmd is available on Linux/macOS and provide installation instructions or links.
  • Avoid listing Windows-only tools first unless the feature is Windows-specific.
GitHub Create Pull Request
Azure Arc Simplify network configuration requirements with Azure Arc gateway ...zure-arc/kubernetes/arc-gateway-simplify-networking.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 all critical operations, but PowerShell is consistently presented as the only alternative to CLI, with no mention of Bash, shell scripting, or Linux-native tools. In some sections, PowerShell examples are shown before or alongside CLI, and environment variable examples for PowerShell are given for proxy configuration. There are no Linux-specific instructions or troubleshooting tips, and the documentation assumes users are familiar with PowerShell if not using CLI.
Recommendations
  • Add explicit Bash/shell scripting examples for Linux/macOS users, especially for environment variable configuration and command-line usage.
  • Clarify that Azure CLI commands work cross-platform and can be run in Bash, zsh, or other shells on Linux/macOS.
  • Where PowerShell is referenced, note that PowerShell Core is available cross-platform, or provide equivalent Bash commands.
  • Include troubleshooting tips or notes relevant to Linux environments (e.g., proxy configuration nuances, file permissions).
  • When listing tabs for command examples, consider ordering CLI (Bash) first, then PowerShell, to reflect cross-platform parity.
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: 3 bias types
Detected Bias Types
⚠ī¸ windows_tools ⚠ī¸ windows_example ⚠ī¸ linux_first
Summary
The documentation provides both Linux and Windows methods for base64 encoding files, with Linux (base64) presented first and Windows (certutil) as an alternative. The Windows example includes extra steps (removing headers) and references Windows-specific utilities. All other examples (openssl, Azure CLI, kubectl) are cross-platform or Linux-centric. No PowerShell-specific commands or Windows-first ordering is present outside the base64 encoding section.
Recommendations
  • Clarify that certutil is available on Windows and provide a PowerShell-native alternative (e.g., [Convert]::ToBase64String) for users who prefer PowerShell.
  • Explicitly state that openssl, Azure CLI, and kubectl commands are cross-platform and provide links or notes on installation for Windows users.
  • Consider providing a macOS-specific note if there are any differences in certificate handling or base64 encoding.
  • Ensure parity in example output and instructions for both Linux and Windows users, especially regarding file manipulation (e.g., header removal).
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 page provides network requirements for Azure Arc Resource Bridge, listing both outbound and inbound connectivity. There is minor evidence of Windows bias: Windows NTP server ('time.windows.com') is mentioned as the default for Hyper-V, and several URLs/services reference 'windows.net' or 'windows.com'. However, Linux-specific requirements are also included (e.g., 'packages.microsoft.com' for Linux package downloads, SSH connectivity, and container registries). Windows tools and endpoints are mentioned, but Linux equivalents are not omitted; the page is generally cross-platform, with only minor Windows-first ordering and terminology.
Recommendations
  • Clarify that NTP can use Linux/Unix NTP servers as well, and provide examples or mention alternatives.
  • When referencing Windows-specific endpoints (e.g., 'time.windows.com'), note that Linux deployments may use other NTP sources.
  • Ensure that any instructions or examples for configuring network settings reference both Windows and Linux methods/tools.
  • Consider ordering examples and endpoint lists in a neutral way, or explicitly state cross-platform applicability.
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 references Azure CLI installation with a link that defaults to the Windows installation page and mentions Azure CLI x64/32-bit requirements, but does not specify Linux/macOS requirements or provide parity in installation instructions or examples. There are no explicit PowerShell or Windows-only tool references, but the management machine requirements and CLI installation links are Windows-centric.
Recommendations
  • Add explicit guidance for installing Azure CLI on Linux and macOS, including links to the relevant installation pages.
  • Clarify that the management machine can be Linux, macOS, or Windows, and provide any OS-specific requirements or caveats.
  • Provide example commands or configuration file locations for Linux/macOS environments, not just Windows.
  • Ensure all CLI commands are shown in a cross-platform way, avoiding assumptions about the user's OS.
GitHub Create Pull Request
Azure Arc Extensions security for Azure Arc-enabled servers ...main/articles/azure-arc/servers/security-extensions.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 examples for critical configuration tasks, but Windows/PowerShell examples are consistently presented first and sometimes described in more detail. The section on listing installed extensions mentions the Azure portal, Azure PowerShell, and Azure CLI, but lists PowerShell before CLI. Example commands for Windows use PowerShell, while Linux uses Bash, but the Windows instructions are often more prominent. No Linux tools or patterns are omitted, and Linux parity is generally maintained.
Recommendations
  • Alternate the order of Windows and Linux examples, or present them side-by-side to avoid 'windows_first' bias.
  • Ensure equal detail and prominence in Linux example explanations.
  • List Azure CLI before PowerShell when both are equally supported, as CLI is cross-platform.
  • Consider adding explicit macOS notes if relevant, since macOS users may follow Linux instructions.
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` is largely cross-platform, but there are minor signs of Windows bias. The authentication options section presents Windows-specific interactive browser login first and references Windows certificate stores for certificate-based authentication. The access token example mentions the Windows PowerShell cmdlet `Get-AzAccessToken` without listing a Linux/macOS equivalent. However, Linux authentication methods (device code, Azure CLI) are well documented, and most examples are generic and applicable to all platforms.
Recommendations
  • Present authentication options in a platform-neutral order or explicitly state cross-platform applicability.
  • When referencing Windows-specific tools (e.g., PowerShell cmdlets), also mention Linux/macOS equivalents (such as Azure CLI commands or REST API methods for obtaining access tokens).
  • Clarify certificate storage options for Linux/macOS users alongside Windows certificate store instructions.
  • Add explicit Linux/macOS example commands where Windows-specific instructions are given (e.g., for access token retrieval).
GitHub Create Pull Request
Azure Arc Customer intent: "As a network administrator, I want to configure secure outbound connectivity for the Azure Connected Machine agent so that I can ensure proper communication with Azure Arc while adhering to my organization's security policies." ...les/azure-arc/servers/includes/network-requirements.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 generally maintains parity between Windows and Linux, but there are subtle signs of Windows bias. Windows-related tools and endpoints (e.g., Windows Admin Center, download.microsoft.com) are mentioned first or more prominently. Windows-specific configuration issues and cipher suite requirements are discussed in detail, while Linux information is more generic and less actionable. Windows examples, tools, and terminology tend to appear before Linux equivalents, and troubleshooting links are Windows-focused.
Recommendations
  • Where possible, provide Linux-specific troubleshooting links and configuration guidance (e.g., OpenSSL settings, Linux firewall/proxy configuration examples).
  • Ensure Linux endpoints and tools are mentioned with equal prominence and detail as Windows ones.
  • When listing URLs or resources, alternate the order or group by platform to avoid always placing Windows first.
  • Expand Linux-specific sections to include actionable steps, not just generic references.
  • Add examples for Linux agent installation, proxy configuration, and TLS/cipher suite setup, similar to the Windows guidance.
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, mentioning both Windows and Linux support in several places. However, there are subtle signs of Windows bias: Windows-related features (such as Windows Server management and Extended Security Updates) are highlighted first and more frequently, and PowerShell is mentioned before other automation tools. Some links and examples use Windows as the default tab or context, and Windows-specific features are referenced before Linux equivalents. No critical Linux functionality is missing, but Windows is presented as the primary platform in several sections.
Recommendations
  • Ensure Linux examples and references are given equal prominence alongside Windows, especially in links and feature descriptions.
  • When listing automation tools (CLI, PowerShell, SDKs), alternate the order or explicitly mention Bash/CLI for Linux users.
  • Where links default to Windows tabs or contexts, add Linux tabs or clarify Linux support.
  • Highlight Linux-specific benefits and scenarios with equal detail as Windows.
  • Add explicit Linux onboarding and management examples where possible.
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 ⚠ī¸ windows_tools
Summary
The documentation page lists new features for Azure Arc-enabled VMware vSphere, with some Windows-specific enhancements (e.g., Windows VM customization, Windows Server Management, Extended Security Updates for Windows Server/SQL Server) mentioned. However, Linux features (e.g., Arc agent installation on Linux via SSH, Ansible playbook for agent installation) are also referenced. In sections where both Windows and Linux are relevant, Windows features tend to be mentioned first or more prominently. Additionally, Windows tools like System Center Configuration Manager and Group Policy are listed before Linux equivalents like Ansible. Azure PowerShell is referenced alongside Azure CLI and REST APIs, but not prioritized. Overall, the page shows mild Windows bias in ordering and tool emphasis, but Linux options are present.
Recommendations
  • Ensure Linux-related features and tools are mentioned with equal prominence and ordering as Windows equivalents.
  • When listing agent installation methods, alternate the order or group by OS type (e.g., Windows tools vs. Linux tools).
  • Add explicit examples or links for Linux-focused workflows where possible (e.g., SSH, Ansible, Linux guest customization).
  • Clarify when features are OS-specific to avoid confusion.
  • Consider adding parity notes for features that are Windows-only, indicating Linux alternatives if available.
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 throughout, ensuring parity for Linux/macOS and Windows users. However, in most sections, Bash examples are presented before PowerShell, indicating a 'windows_first' bias is not present. The only minor bias is that PowerShell is included as a first-class citizen, but there are no Windows-specific tools or patterns, and Linux/macOS users are fully supported. There are no missing Linux examples or Windows-exclusive tools.
Recommendations
  • Maintain the current structure of Bash and PowerShell tabs for all command-line examples.
  • Consider clarifying in the introduction that both Linux/macOS and Windows environments are fully supported.
  • Ensure that any future additions continue to provide Bash and PowerShell parity.
  • If possible, add a brief note about compatibility for macOS users (e.g., if any commands differ).
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, followed by PowerShell. There is no evidence of Windows-only tools or patterns, and all commands use the Azure CLI, which is cross-platform. No Linux/macOS examples are missing, and no Windows-specific tools are mentioned. The PowerShell examples are simply adaptations of the Bash commands, not exclusive or prioritized.
Recommendations
  • Maintain the current parity by continuing to provide both Bash and PowerShell examples.
  • Consider explicitly stating that the Azure CLI commands work on Linux, macOS, and Windows to reassure cross-platform users.
  • If possible, add a note clarifying that PowerShell Core is available on Linux and macOS, so PowerShell examples are not strictly Windows-only.
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 consistently presented before PowerShell examples, which is a minor form of bias ('windows_first'). There are no Windows-specific tools, commands, or patterns used exclusively, and all instructions are cross-platform via the Azure CLI and Helm. No critical Linux/macOS gaps are present.
Recommendations
  • Continue to provide both Bash and PowerShell examples for all steps.
  • Consider alternating the order of Bash and PowerShell examples, or explicitly state that Bash is for Linux/macOS and PowerShell is for Windows, to further clarify parity.
  • Ensure that any future additions maintain cross-platform coverage and avoid introducing Windows-only steps unless the feature is Windows-specific.
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 all steps, ensuring parity between Linux/macOS and Windows users. However, in each section, Bash examples are consistently presented before PowerShell examples, which is a minor form of bias ('windows_first') as Windows users may expect their examples first. No exclusive Windows tools, patterns, or missing Linux examples are found. All commands use cross-platform Azure CLI and Helm tools.
Recommendations
  • Consider alternating the order of Bash and PowerShell examples in different sections, or explicitly state that Bash is shown first for consistency.
  • Add a brief note at the top clarifying that both Bash (Linux/macOS) and PowerShell (Windows) are supported and that the order does not imply preference.
  • Ensure that any future additions (e.g., troubleshooting, environment setup) provide parity for both platforms.
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 examples for deploying Azure dashboards using the Azure portal, Azure CLI, and Azure PowerShell. While the Azure CLI is cross-platform and shown before PowerShell, the PowerShell section is present and uses Windows-centric terminology. The PowerShell example is given after the CLI, but no Linux/macOS-specific shell examples (such as Bash scripting or references to Cloud Shell usage on Linux/macOS) are provided. The documentation does not show exclusive Windows tools or patterns, but the inclusion of PowerShell without explicit Linux/macOS parity may create minor friction.
Recommendations
  • Clarify that Azure CLI commands work on Windows, Linux, and macOS, and can be used in Bash or other shells.
  • Add a note or example showing how to use Azure CLI in Bash or Cloud Shell for Linux/macOS users.
  • Mention that Azure PowerShell is available cross-platform, but highlight CLI as the primary cross-platform tool.
  • Consider providing Bash script snippets for automating dashboard deployment, or referencing Cloud Shell usage.
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, but PowerShell is given equal prominence and detail throughout. The PowerShell examples use Windows-style paths and syntax, and are presented immediately after Bash, which may create friction for Linux/macOS users. However, Bash examples are present for all commands, and the underlying tools (az CLI, Helm) are cross-platform.
Recommendations
  • Consider listing Bash examples before PowerShell in all sections, as Bash is the default shell for Linux/macOS.
  • Clarify that PowerShell examples are intended for Windows users, and Bash for Linux/macOS.
  • Add a note at the top explaining that all commands can be run on Linux/macOS using Bash, and on Windows using PowerShell.
  • Ensure file path examples use forward slashes for Bash and backslashes for PowerShell, and clarify any differences.
  • If possible, provide a single Bash example as the primary, with PowerShell as an optional tab for Windows users.
GitHub Create Pull Request
Container Registry Quickstart - Create Registry - Bicep ...ainer-registry/container-registry-get-started-bicep.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 both Azure CLI and PowerShell, but PowerShell is presented as a primary option alongside CLI. The instructions for opening a terminal reference Visual Studio Code and its key combination, which is cross-platform, but PowerShell is featured as a main tab, which may imply Windows bias. There are no Linux-specific examples or explicit mentions of Linux/macOS compatibility, and PowerShell is not natively available on most Linux/macOS systems. However, Azure CLI is cross-platform and shown first.
Recommendations
  • Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows.
  • Clarify that PowerShell examples are intended for Windows users, and suggest Bash or Zsh for Linux/macOS users.
  • Add a Bash example or note that Azure CLI can be used in Bash shells on Linux/macOS.
  • Consider listing Azure CLI as the default or primary method, with PowerShell as an alternative for Windows users.
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
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation presents both Azure PowerShell and Azure CLI as options for programmatic access, but PowerShell is consistently mentioned first. This subtly prioritizes Windows tooling, even though Azure CLI is fully cross-platform. No Linux/macOS-specific instructions or screenshots are provided, but the content is largely platform-neutral since it focuses on the Azure portal UI.
Recommendations
  • Alternate the order in which Azure PowerShell and Azure CLI are mentioned, or list Azure CLI first to reflect its cross-platform nature.
  • Explicitly state that Azure CLI works on Windows, Linux, and macOS to reassure non-Windows users.
  • Where programmatic examples are given, provide both PowerShell and CLI commands side-by-side, or clarify that both are equally supported.
  • Consider including a note or screenshot showing Azure CLI usage in a non-Windows terminal to reinforce parity.
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 not strictly Windows-only, PowerShell is more commonly associated with Windows, and its mention before Bash or Linux shell scripting could be seen as a mild Windows bias. No explicit Linux examples, tools, or patterns are provided, nor are Linux/macOS equivalents mentioned. However, the documentation is generally neutral and focused on the Azure mobile app, which is available on both iOS and Android.
Recommendations
  • Explicitly mention Bash or Linux shell scripting as a supported code generation scenario, alongside PowerShell.
  • Provide examples or clarify that Azure Copilot can generate scripts for Bash, Azure CLI, and PowerShell, covering both Windows and Linux users.
  • Ensure that future documentation includes parity in examples for both Windows (PowerShell) and Linux/macOS (Bash/Azure CLI).
GitHub Create Pull Request
Container Registry Push & Pull Container Image using Azure Container Registry ...-registry/container-registry-get-started-docker-cli.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 authentication and image removal, but PowerShell examples are given equal prominence to CLI examples, and Windows-specific PowerShell tools are mentioned alongside cross-platform alternatives. There is minor Windows bias in the ordering and presence of PowerShell examples, but Linux/macOS users can complete all tasks using the CLI or Docker commands.
Recommendations
  • Clearly indicate which commands are cross-platform and which are Windows-only (e.g., PowerShell).
  • Consider listing Azure CLI examples before PowerShell examples, as CLI is cross-platform.
  • Add explicit notes that Azure PowerShell is Windows-centric, and recommend Azure CLI for Linux/macOS users.
  • Ensure that all critical tasks have Azure CLI or Docker CLI examples, and avoid implying PowerShell is required for Linux/macOS users.
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 subtle 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 CLI, PowerShell, and Portal, with PowerShell (Windows-specific) mentioned before Portal. No explicit Linux/macOS examples are given for environment variable setup, and the documentation does not clarify cross-platform command differences.
Recommendations
  • Provide both Windows ('set') and Linux/macOS ('export') commands for setting environment variables.
  • Clarify that Azure CLI and Helm commands are cross-platform and provide any OS-specific notes where relevant.
  • When listing options for creating AKS clusters, mention Azure CLI and Portal first, and clarify PowerShell is Windows-specific.
  • Add a note or table summarizing command differences for Windows vs. Linux/macOS where applicable.
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: 2 bias types
Detected Bias Types
⚠ī¸ windows_first ⚠ī¸ powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for tasks such as showing registry usage and changing the registry SKU. However, PowerShell (a Windows-centric tool) is mentioned alongside CLI in several places, and in some cases, PowerShell examples are given immediately after CLI, which could be interpreted as a mild 'windows_first' bias. There are no Linux/macOS-specific tools or shell examples (e.g., Bash scripts), but the CLI examples are cross-platform. No critical functionality is Windows-only, and Linux/macOS users can complete all tasks using the CLI.
Recommendations
  • Clarify that Azure CLI is cross-platform and preferred for Linux/macOS users.
  • Consider providing Bash script examples or explicitly stating that all CLI commands work on Linux/macOS.
  • If mentioning PowerShell, note that Azure PowerShell is available cross-platform, or link to installation instructions for non-Windows systems.
  • Where possible, present CLI examples before PowerShell, or group them under a 'cross-platform' heading.
GitHub Create Pull Request