← Back to Dashboard
173
Pages Scanned
40
Pages Flagged
173
Changed Pages
23.1%
% Pages Flagged

Scan Information

Started At: 2026-02-10 00:00:07

Finished At: 2026-02-10 18:44:36

Status: completed

Target Repo: Azure Management

Current Phase: discovery

Files Queued: 173

Files Completed: 173

Problematic Pages

40 issues found
Azure Arc Recover from accidental deletion of resource bridge VM ...em-center-virtual-machine-manager/disaster-recovery.md
High 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 recovery instructions for the Azure Arc resource bridge VM using a Windows-based PowerShell script. There are no examples, scripts, or guidance for Linux/macOS users, nor are cross-platform tools or alternatives mentioned. The recovery process is described only for Windows, and the linked script is Windows-specific.
Recommendations
  • Provide equivalent recovery instructions for Linux/macOS users, including Bash or Python scripts.
  • Clarify whether the recovery process is supported on non-Windows platforms, or explicitly state if Windows is required.
  • If possible, offer a cross-platform script or tool, or document manual steps for Linux/macOS environments.
  • Mention any prerequisites or limitations for Linux/macOS users up front.
GitHub Create Pull Request
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 is heavily biased towards Windows/PowerShell environments. All onboarding scripts and examples are provided as PowerShell scripts (.ps1), and users are instructed to use PowerShell terminals. Windows-specific tools like 'winget' are referenced for installing dependencies, with no mention of Linux/macOS alternatives. There are no Bash or shell script equivalents or instructions for non-Windows platforms, making it difficult for Linux/macOS users to follow or automate the onboarding process.
Recommendations
  • Provide Bash or shell script equivalents for the onboarding scripts, or document how to run the PowerShell scripts on Linux/macOS (e.g., using PowerShell Core).
  • Include installation instructions for Azure CLI and kubectl using platform-appropriate package managers (e.g., apt, yum, brew) in addition to 'winget'.
  • Clarify whether the provided PowerShell scripts are compatible with PowerShell Core on Linux/macOS, and if not, provide cross-platform alternatives.
  • Add explicit Linux/macOS examples and terminal commands alongside the existing Windows/PowerShell instructions.
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 (WOGAMigration.ps1) and instructs users to run it in PowerShell, with no mention of Bash, Linux shell, or cross-platform alternatives. There is no guidance for Linux/macOS users on how to perform the migration or run the script, creating friction for non-Windows environments.
Recommendations
  • Provide instructions for running the migration script on Linux/macOS, such as using PowerShell Core (pwsh) on those platforms.
  • Clarify whether the script is compatible with PowerShell Core and, if so, add example commands for Linux/macOS users.
  • If the script is Windows-only, offer an alternative migration method for Linux/macOS users or explicitly state the limitation.
  • Include troubleshooting tips for non-Windows users attempting to run the script.
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 it uses Windows/PowerShell-centric tools (Invoke-AksEdgeNodeCommand) for Linux node configuration. No native Linux shell or SSH examples are provided for sysctl changes, and Notepad is mentioned as the default editor for JSON files, which is a Windows tool.
Recommendations
  • Provide native Linux command-line examples for sysctl configuration (e.g., using SSH and bash).
  • Mention Linux text editors (such as nano, vim, or gedit) alongside Notepad for editing JSON files.
  • Clarify whether Invoke-AksEdgeNodeCommand is required or if direct Linux commands can be used.
  • Add explicit Linux shell examples for file editing and configuration steps.
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 command-line examples for connecting to the SQL Server instance using sqlcmd, but these examples are shown exclusively with PowerShell syntax (e.g., using PowerShell prompt and conventions). There is no explicit mention of Linux/macOS alternatives or shell syntax, and the use of PowerShell is presented first and exclusively, which may create friction for Linux/macOS users.
Recommendations
  • Provide equivalent examples using Bash shell syntax for Linux/macOS users, especially for commands involving kubectl exec and sqlcmd.
  • Clarify that sqlcmd and kubectl commands can be run from any OS with the appropriate tools installed, and provide OS-agnostic instructions.
  • Add notes or sections indicating any OS-specific requirements or differences, such as path conventions or environment setup.
  • Ensure that examples do not use PowerShell-specific syntax unless the task is Windows-only.
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 backup examples and file paths using Windows conventions (e.g., C:\Backupfiles\test.bak) and does not offer equivalent Linux/macOS examples for creating or handling backup files. The use of tools like Visual Studio Code and Azure Storage Explorer is cross-platform, but the backup/restore steps and file copy examples are Windows-centric, which may create friction for Linux/macOS users.
Recommendations
  • Add explicit examples for creating SQL Server backups on Linux (e.g., using /var/opt/mssql/backup/test.bak as the backup path).
  • When showing file paths or commands, provide both Windows and Linux/macOS variants side-by-side.
  • Clarify that tools like Visual Studio Code and Azure Storage Explorer are cross-platform, and link to installation instructions for Linux/macOS.
  • In the kubectl cp example, show a Linux/macOS source path (e.g., /home/user/backup/test.bak) in addition to the Windows path.
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 approaches for base64 encoding files, but the Windows example (using certutil) is more detailed and includes additional steps (removing headers with findstr). The Linux example is brief and lacks equivalent guidance for header removal. The Windows tools are mentioned explicitly, and the Windows workflow is described in greater depth. The rest of the documentation is platform-neutral, focusing on Azure CLI, kubectl, and OpenSSL, which are cross-platform.
Recommendations
  • Expand the Linux example to include instructions for removing certificate headers from base64 output, similar to the Windows example.
  • Mention Linux/macOS alternatives for header removal, such as using grep or sed.
  • Present Linux and Windows examples with equal detail and in parallel, rather than giving more steps for Windows.
  • Consider showing Linux/macOS examples first, or side-by-side, to avoid 'windows_first' bias.
GitHub Create Pull Request
Azure Arc Azure Arc resource bridge system requirements ...icles/azure-arc/resource-bridge/system-requirements.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example
Summary
The documentation references Azure CLI installation with a direct link to the Windows installation page and does not mention Linux or macOS management machines or provide explicit instructions/examples for those platforms. There are no PowerShell-specific commands or Windows-only tools, but the lack of parity in examples and links may cause confusion for Linux/macOS users.
Recommendations
  • Provide explicit mention that the management machine can be Windows, Linux, or macOS, as Azure CLI is cross-platform.
  • Add links to Azure CLI installation instructions for Linux and macOS, not just Windows.
  • Clarify that all CLI commands shown are valid on all supported platforms.
  • If there are any platform-specific requirements (such as 32-bit/64-bit), specify them for each OS.
  • Consider including a short example or note for Linux/macOS users to reinforce parity.
GitHub Create Pull Request
Azure Arc Troubleshoot Azure Arc resource bridge issues ...re-arc/resource-bridge/troubleshoot-resource-bridge.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ missing_linux_example
Summary
The documentation provides troubleshooting guidance for Azure Arc resource bridge, which is a cross-platform solution. However, there are several instances of Windows bias: PowerShell is referenced for troubleshooting network issues (e.g., Invoke-WebRequest, Resolve-DnsName), and Windows paths (e.g., C:\Program Files\...) are used in error messages. Linux-specific troubleshooting commands and examples are largely missing or appear after Windows ones. The GLIBC error is the only explicit Linux troubleshooting section, but most CLI and network troubleshooting steps default to Windows tools and terminology.
Recommendations
  • Add Linux/macOS equivalents for PowerShell commands (e.g., curl, dig, nslookup) wherever PowerShell is used for troubleshooting.
  • Provide Linux/macOS file path examples alongside Windows paths in error messages.
  • Include explicit instructions for managing Azure CLI and extensions on Linux/macOS, such as package manager commands (apt, yum, brew).
  • Ensure troubleshooting steps reference both Windows and Linux tools equally, or group them by OS.
  • Where CLI commands are shown, clarify any OS-specific prerequisites or differences (e.g., SSH folder permissions, glibc requirements).
GitHub Create Pull Request
Azure Arc Manage and maintain the Azure Connected Machine agent ...s/blob/main/articles/azure-arc/servers/manage-agent.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation provides comprehensive coverage for both Windows and Linux platforms, including installation, upgrade, uninstall, and proxy configuration. However, Windows examples and tools (such as PowerShell scripts, Group Policy, Microsoft Update, and Control Panel) are often presented first or in greater detail. The cleanup script for stale resources is only provided in PowerShell, with no equivalent Bash or CLI example for Linux users. Windows-specific tools and patterns (e.g., Msiexec, Registry Editor, Group Policy) are described in depth, while Linux instructions are more concise and rely on standard package managers.
Recommendations
  • Provide equivalent Bash or Azure CLI scripts for resource cleanup and automation tasks, not just PowerShell.
  • Where possible, present Linux and Windows instructions in parallel or with equal prominence, rather than Windows-first.
  • Expand Linux sections to include troubleshooting tips, automation examples, and references to Linux-native tools.
  • Consider adding a summary table of methods/scripts for both platforms at the start of each major section.
GitHub Create Pull Request
Azure Arc CLI reference for `azcmagent connect` ...b/main/articles/azure-arc/servers/azcmagent-connect.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation provides authentication options for both Windows and Linux, but there is a notable Windows bias. The 'Interactive browser login' is described as Windows-only and appears first. Windows certificate store usage is detailed, while Linux equivalents are not mentioned. The access token example references PowerShell's Get-AzAccessToken, but does not mention Linux alternatives. Overall, Linux users can complete the task, but Windows-specific tools and patterns are referenced more prominently and earlier.
Recommendations
  • Add explicit Linux/macOS guidance for certificate-based authentication, such as storing certificates in standard filesystem locations and using PEM/PFX files.
  • Provide Linux/macOS alternatives for obtaining access tokens, such as using Azure CLI (az account get-access-token) or other cross-platform tools.
  • Reorder authentication options so that cross-platform methods (device code, service principal, Azure CLI) are presented before Windows-only options.
  • Clarify that most examples and flags are applicable to both Windows and Linux, and highlight any OS-specific differences.
  • Include Linux/macOS-specific examples where relevant, such as using $(hostname) in shell scripts.
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 ARM template examples for both Linux and Windows Arc-enabled servers, ensuring parity in template content. However, all deployment command examples use Azure PowerShell exclusively, with no Azure CLI or Bash equivalents shown. Additionally, PowerShell commands and Windows-style file paths are presented first and throughout, which may create friction for Linux/macOS users who typically use Azure CLI or Bash. The documentation does mention Azure CLI in the 'Related content' section, but does not provide any CLI examples or guidance in the main workflow.
Recommendations
  • Add Azure CLI deployment command examples alongside PowerShell commands, especially for template deployments (e.g., az deployment group create ...).
  • Include Linux/macOS-friendly file path examples (e.g., /home/user/Azure/Templates/...) in addition to Windows-style paths.
  • Consider presenting CLI and PowerShell examples side-by-side or alternating their order to avoid Windows-first bias.
  • Explicitly state that both PowerShell and CLI can be used, and link to relevant CLI documentation in the main workflow, not just in 'Related content'.
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 for running a PowerShell script (RGCleanScript.ps1) to clean up Azure Arc workload orchestration resources. All examples and guidance are PowerShell-based, with no mention of Linux/macOS-compatible alternatives, such as Bash scripts or cross-platform instructions. There is no indication that the script can be run on Linux or macOS, nor are there examples for those platforms.
Recommendations
  • Clarify whether RGCleanScript.ps1 can be executed on PowerShell Core (pwsh) on Linux/macOS, and provide explicit instructions if so.
  • If the script is Windows-only, offer a Bash or cross-platform alternative for Linux/macOS users, or note the limitation clearly.
  • Add example commands for running the script on Linux/macOS, or provide equivalent scripts in Bash.
  • Mention prerequisites for Linux/macOS users, such as installing PowerShell Core or dependencies.
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: 4 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first ⚠️ windows_tools ⚠️ missing_linux_example
Summary
The documentation consistently uses PowerShell syntax for all CLI examples and references PowerShell scripts (e.g., bulk_deployment.ps1, workflow-delete.ps1) as the only automation options. There are no Bash or Linux shell script equivalents provided, and the use of PowerShell syntax may confuse Linux/macOS users, even though the Azure CLI is cross-platform. The documentation does not mention or demonstrate Linux/macOS usage patterns, nor does it provide alternative scripts or instructions for non-Windows environments.
Recommendations
  • Provide CLI command examples in standard shell syntax (e.g., Bash) or clarify that the Azure CLI commands work identically on Linux/macOS and Windows.
  • Offer equivalent Bash scripts for bulk deployment and workflow deletion, or at least provide guidance for running the provided PowerShell scripts on Linux/macOS (e.g., using PowerShell Core).
  • Explicitly state that the Azure CLI commands are cross-platform and can be run from any OS.
  • If only PowerShell scripts are available, mention how Linux/macOS users can install and use PowerShell Core, or provide links to cross-platform script alternatives.
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 demonstrates notable Windows bias. All CLI/script examples are provided in PowerShell syntax, and references to file paths in JSON templates use Windows-style paths (e.g., C:\, E:\). There are no Bash or Linux shell equivalents for commands, nor guidance for Linux/macOS users. The onboarding scripts and instructions assume a Windows environment, making it difficult for Linux/macOS users to follow or replicate the steps without adaptation.
Recommendations
  • Provide Bash or shell script equivalents for all PowerShell commands, especially for az CLI usage.
  • Use platform-agnostic file path examples in JSON templates, or provide both Windows and Linux/macOS variants.
  • Clarify whether the onboarding scripts (e.g., infra_onboarding.ps1) are available in cross-platform formats (such as .sh or Python), or provide alternatives.
  • Explicitly mention any Windows-only requirements, and offer Linux/macOS guidance where possible.
  • Add notes or sections for Linux/macOS users, including troubleshooting or adaptation tips.
GitHub Create Pull Request
Azure Arc Prepare the Environment for Workload Orchestration ...rc/workload-orchestration/initial-setup-environment.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
⚠️ windows_first ⚠️ missing_linux_example ⚠️ windows_tools
Summary
The documentation shows evidence of Windows bias in several areas. The example for installing kubectl uses 'winget', a Windows-only tool, with no Linux/macOS alternative provided. The file extraction example under the Bash tab uses 'Expand-Archive', which is a PowerShell/Windows command, not a native Bash/Linux command. There are no Linux/macOS-specific instructions for extracting ZIP files or installing kubectl, and Windows paths (e.g., 'C:\path\to\archive.zip') are used in Bash examples. The PowerShell tab is present throughout, but Linux/macOS users are left to infer their own commands for certain steps.
Recommendations
  • Provide Linux/macOS-specific instructions for installing kubectl, such as using 'apt', 'yum', 'brew', or downloading from the official Kubernetes site.
  • Replace 'Expand-Archive' in Bash examples with 'unzip' or 'tar' commands, and use Linux-style paths (e.g., '/home/user/archive.zip') in Bash examples.
  • Add explicit Linux/macOS examples for file extraction and directory navigation.
  • Ensure that Bash examples use commands and paths appropriate for Linux/macOS environments.
  • Consider including a table or section that summarizes installation steps for both Windows and Linux/macOS platforms.
GitHub Create Pull Request
Azure Arc Release Notes for Workload Orchestration ...cles/azure-arc/workload-orchestration/release-notes.md
Medium Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation page provides release notes for Azure Arc Workload Orchestration, which is a cross-platform service. Most CLI examples use Bash syntax, but the May 2025 release section exclusively provides PowerShell examples for CLI usage, despite the Azure CLI being cross-platform. No Linux/macOS-specific examples or shell alternatives are given in that section, and PowerShell syntax is shown first and only, which may create friction for Linux/macOS users.
Recommendations
  • For CLI examples, provide both Bash and PowerShell syntax, or use Bash as the default unless the feature is Windows-specific.
  • Add a note clarifying that Azure CLI commands work on Linux/macOS and Windows, and show examples in both environments where syntax differs.
  • Review all CLI example blocks to ensure Linux/macOS users are not excluded or confused by Windows-centric syntax.
  • Where PowerShell is used, offer equivalent Bash commands, especially for file paths and variable assignment.
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. Most examples and commands are provided in PowerShell syntax, even for tasks that are cross-platform (e.g., Azure CLI, Docker, Kubernetes). Linux/Bash equivalents are missing for critical troubleshooting steps, except for the 'service groups' section, which includes both Bash and PowerShell tabs. This bias creates friction for Linux/macOS users, who must translate PowerShell commands to Bash or their shell of choice.
Recommendations
  • Provide Bash/Linux shell equivalents for all PowerShell commands, especially for Azure CLI, Docker, and Kubernetes operations.
  • Clearly indicate when a command is cross-platform and provide syntax for both PowerShell and Bash.
  • Review and update troubleshooting steps to ensure Linux/macOS users can follow along without needing to translate PowerShell-specific syntax.
  • Where PowerShell is used for string manipulation or file operations, offer Bash alternatives (e.g., using sed, awk, base64, jq).
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 instructions for Azure Container Registry using both Azure CLI and Azure PowerShell, but PowerShell examples and references are prominent throughout. PowerShell is a Windows-centric tool, and its usage is presented alongside Azure CLI, which is cross-platform. However, there are no explicit Linux/macOS-specific examples, such as shell scripting or Bash usage. The order of examples often places PowerShell immediately after Azure CLI, and references to PowerShell are frequent. There are no Linux-specific tools or patterns (e.g., Bash, environment variables, shell scripting) highlighted, and the 'Next steps' section links to both CLI and PowerShell guides, but not to Linux/macOS-specific workflows.
Recommendations
  • Add explicit Bash/shell scripting examples for Linux/macOS users, especially for token handling and environment variable usage.
  • Clarify that Azure CLI is cross-platform and provide guidance for installing and using it on Linux/macOS.
  • Include Linux/macOS-specific instructions for Docker installation and configuration, as these differ from Windows.
  • Consider adding a 'Linux/macOS' tab or section for authentication workflows, showing common shell commands and patterns.
  • Balance PowerShell references with Bash or shell equivalents to ensure parity.
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 throughout, ensuring parity for Linux/macOS and Windows users. However, in several sections, PowerShell examples are presented immediately after Bash, and sometimes the Bash tab is listed first. There are no Windows-specific tools or patterns, and all commands use the cross-platform Azure CLI. No critical steps are Windows-only, and Linux users can complete all tasks. The only minor bias is the ordering of PowerShell and Bash examples, which may subtly favor Windows users by always including PowerShell, but this is mitigated by the presence of Bash examples.
Recommendations
  • Ensure Bash and PowerShell examples are equally prominent, perhaps alternating their order or clarifying that Bash is for Linux/macOS and PowerShell for Windows.
  • Consider adding a brief note at the top explaining which shell to use for each OS.
  • If possible, provide a generic CLI example without shell-specific syntax for universal clarity.
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 before PowerShell. There are no Windows-specific tools or patterns, and Linux parity is maintained throughout. No critical sections are Windows-only, and all tasks can be completed on Linux/macOS using the Azure CLI.
Recommendations
  • Continue to provide both Bash and PowerShell examples for cross-platform parity.
  • Consider explicitly stating that all commands are supported on Linux, macOS, and Windows.
  • If possible, add a brief note clarifying that Azure CLI works across platforms and that Bash examples are suitable for Linux/macOS users.
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 clear parity between Windows and Linux VM extensions, with dedicated tables and links for each. However, Windows extensions are listed first, which may subtly signal prioritization. All deployment methods (Azure CLI, PowerShell, portal, ARM templates) are presented neutrally, and partner extensions are shown for both OSes. No critical Linux omissions or Windows-only tools are present.
Recommendations
  • Consider alternating the order of Windows and Linux extension tables, or explicitly state that both are equally supported.
  • Add a brief introductory statement emphasizing Linux parity and support.
  • Ensure that linked deployment guides (e.g., Azure CLI, PowerShell) include Linux-specific examples where applicable.
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 example is provided, SSMS is consistently listed first and no Linux-native GUI tools (such as Azure Data Studio or DBeaver) are referenced. The documentation does not provide parity in client tool recommendations or examples for Linux/macOS users, potentially creating friction for those not on Windows.
Recommendations
  • Mention cross-platform SQL client tools such as Azure Data Studio or DBeaver alongside SSMS.
  • Provide explicit examples for connecting with sqlcmd on Linux/macOS, including any OS-specific authentication or encoding requirements.
  • List Linux/macOS-compatible tools before or alongside SSMS to avoid 'windows_first' bias.
  • Clarify that SSMS is Windows-only and suggest alternatives for Linux/macOS users.
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 generally aims for cross-platform parity, but there are subtle signs of Windows bias. In the installation links for tools like kubectl and curl, Windows is listed first, and the Linux installation instructions are less explicit (e.g., 'Linux: install curl package' vs. a direct link for Windows). There is also a note specifically about using cmd.exe instead of PowerShell on Windows, and a PowerShell-specific note about curl, but no equivalent Linux/macOS notes or troubleshooting tips. No explicit Linux/macOS command examples are provided.
Recommendations
  • List installation options for all platforms in parallel order (e.g., Windows, Linux, macOS) or rotate the order to avoid always listing Windows first.
  • Provide direct installation links for Linux and macOS tools (e.g., link to curl installation instructions for Linux and macOS, not just Windows).
  • Include Linux/macOS-specific notes or troubleshooting tips where Windows-specific notes are given (e.g., clarify curl behavior on Linux shells if needed).
  • Add example commands for Linux/macOS where Windows-specific command-line nuances are discussed.
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
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_tools
Summary
The documentation references several Windows-centric tools (SSMS, SQL Server Data Tools, SQL Server PowerShell, SQL Server Profiler) and highlights PowerShell scripting support as a manageability feature. However, it also mentions cross-platform tools (Azure CLI, Visual Studio Code extension) and notes that Azure PowerShell is not supported. There are no explicit Windows-first examples or missing Linux-specific examples, but the tool listing is weighted toward Windows tools.
Recommendations
  • Add explicit mention of cross-platform alternatives for Windows tools, such as Azure Data Studio (which runs on Linux/macOS), and clarify which tools are available on Linux/macOS.
  • Include examples or links for using SQL Managed Instance enabled by Azure Arc from Linux/macOS environments, such as using Azure CLI or VS Code.
  • Consider listing cross-platform tools before Windows-only tools in the Tools section.
  • Clarify PowerShell scripting support: specify if cross-platform PowerShell (pwsh) is supported or if only Windows PowerShell is relevant.
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 most features and fixes. However, Windows download links and version numbers are consistently listed first, and Windows-specific installer instructions (e.g., PowerShell, msiexec, UAC) are detailed while Linux equivalents are not. Some bug fixes and improvements reference Windows tools (e.g., PowerShell scripts, MSI installer) without mentioning Linux alternatives or providing comparable Linux instructions.
Recommendations
  • Alternate the order of Windows and Linux download links and version numbers to avoid implicit prioritization.
  • Provide Linux-specific installer troubleshooting guidance (e.g., using RPM or DEB commands, sudo usage) in the Known Issues section, similar to the Windows installer instructions.
  • When referencing Windows tools/scripts (e.g., PowerShell, MSI), mention Linux equivalents (e.g., Bash scripts, RPM/DEB installers) where applicable.
  • Ensure that bug fixes and improvements for Linux are described with equal detail as Windows, especially when referencing OS-specific behaviors.
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: 2 bias types
Detected Bias Types
⚠️ powershell_heavy ⚠️ windows_first
Summary
The documentation references Azure CLI, PowerShell, and REST API as supported experiences, but PowerShell is mentioned alongside Azure CLI in metadata and navigation, potentially prioritizing Windows-centric tooling. The 'Next steps' section lists PowerShell before REST API, and the metadata includes 'devx-track-azurepowershell', which may signal a Windows-first approach. However, the page clearly states support for both Windows and Linux, and notes a Linux-specific limitation. No Linux-specific examples or tools (e.g., Bash) are highlighted, and there are no Linux-first instructions.
Recommendations
  • Ensure Linux/Bash examples are included and visible in main documentation and navigation.
  • Balance PowerShell and Azure CLI examples with Bash or shell script examples for Linux users.
  • Explicitly mention Linux support in introductory sections and provide Linux-specific guidance where relevant.
  • Consider listing Azure CLI (cross-platform) before PowerShell in navigation and 'Next steps' to avoid Windows-first impression.
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 Windows examples and terminology are often presented first or in greater detail. PowerShell and Windows-specific paths and tools are referenced, sometimes before their Linux equivalents. The log file locations and installation error codes are clearly separated for Windows and Linux, but Windows commands are shown first and in more detail. The severity of the bias is low, as Linux examples and information are present and Linux users can complete all tasks.
Recommendations
  • Alternate the order of Windows and Linux sections/examples so Linux is not always second.
  • Provide Linux examples before or alongside Windows examples, especially in critical sections.
  • Ensure that troubleshooting steps reference Linux tools and paths equally (e.g., mention sudo and Linux log locations alongside Windows equivalents).
  • Where PowerShell is used for Windows, clarify the equivalent Bash or shell command for Linux.
  • Add explicit notes for Linux users where Windows-specific terminology (e.g., 'elevated command prompt') is used.
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, patterns, or exclusive references; all commands use the cross-platform Azure CLI. No Linux/macOS examples are missing, and no Windows-only tools are required.
Recommendations
  • Consider alternating the order of Bash and PowerShell tabs across related documentation pages to avoid a consistent 'Windows-first' impression.
  • Explicitly note that all examples are cross-platform and that Azure CLI is supported on Windows, Linux, and macOS.
  • If possible, clarify in the introduction that both Windows (PowerShell) and Linux/macOS (Bash) users are fully supported.
GitHub Create Pull Request
Azure Arc What's 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. While most features are platform-neutral or mention both Windows and Linux, there is a tendency to mention Windows-specific features (such as customizing Windows VM guest settings and Windows Server Management) before Linux equivalents. Windows tools (System Center Configuration Manager, Group Policy) are mentioned for agent installation, but Linux tools (Ansible) are also included. Azure PowerShell is listed after Azure CLI and REST APIs, showing some parity. Overall, minor Windows bias is present, but Linux users can complete all tasks.
Recommendations
  • Ensure Linux-related features (such as guest customization for Linux VMs) are mentioned alongside Windows features where applicable.
  • When listing agent installation methods, consider mentioning Linux-native tools (like Ansible) before or alongside Windows tools.
  • Add explicit examples or links for Linux guest customization if supported.
  • Maintain parity in SDK and tool coverage for both Windows and Linux platforms.
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 parity for Linux/macOS and Windows users. However, in several sections, PowerShell examples are presented after Bash, which is the reverse of typical Windows-first bias. There is no evidence of Windows-only tools, missing Linux examples, or exclusive Windows patterns. The only minor bias is the ordering: Bash examples are shown before PowerShell, which may be slightly less convenient for Windows users but does not impact Linux/macOS users.
Recommendations
  • No changes needed for Linux parity; both Bash and PowerShell examples are present and equivalent.
  • If desired, clarify in the introduction that Bash examples are for Linux/macOS and PowerShell for Windows, to help users choose the correct tab.
  • Maintain parity in future updates by ensuring all steps have both Bash and PowerShell examples.
GitHub Create Pull Request
Azure Arc Create a Solution with Shared Adapter Dependency with Workload Orchestration ...ation/quickstart-solution-shared-adapter-dependency.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ windows_first
Summary
The documentation provides both Bash and PowerShell examples for all CLI steps, ensuring parity for Linux/macOS and Windows users. However, in most sections, Bash examples are presented before PowerShell, which is a minor 'windows_first' bias (since PowerShell is the Windows shell, but Bash is shown first). There are no Windows-specific tools, patterns, or commands used, and no missing Linux examples.
Recommendations
  • Maintain the current structure, as Bash and PowerShell parity is excellent.
  • Consider alternating the order of Bash and PowerShell tabs or explicitly stating that Bash is for Linux/macOS and PowerShell for Windows to clarify cross-platform support.
  • Ensure that any future examples or troubleshooting steps continue to provide both Bash and PowerShell versions.
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 consistently presented before PowerShell, which is a minor 'windows_first' bias in ordering. No exclusive Windows tools, PowerShell-heavy content, or missing Linux examples are present.
Recommendations
  • Maintain the current parity of Bash and PowerShell examples.
  • Consider alternating the order of Bash and PowerShell tabs in some sections, or clarify that both are equally supported.
  • Explicitly mention that all commands are cross-platform and supported on both Linux/macOS and Windows environments.
GitHub Create Pull Request
Azure Arc Solution with Multiple Shared Dependencies at Different Hierarchy Levels ...oad-orchestration/tutorial-service-group-scenario-3.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides both Bash and PowerShell examples for every step, but consistently presents Bash examples first. There is no evidence of Windows-only tools or patterns; all commands use the Azure CLI and Helm, which are cross-platform. PowerShell examples are included throughout, which may be seen as catering to Windows users, but Linux/macOS users are fully supported via Bash. No Linux-specific examples or troubleshooting are missing.
Recommendations
  • Maintain Bash examples first, as Bash is the default shell for Linux/macOS.
  • Consider adding a brief note clarifying that all commands are cross-platform and that Bash is recommended for Linux/macOS users, while PowerShell is for Windows users.
  • Optionally, include a short section on troubleshooting common cross-platform issues (e.g., file path differences, quoting) for users switching between Bash and PowerShell.
  • Ensure that file path examples use forward slashes in Bash and backslashes in PowerShell, as appropriate, to avoid confusion.
GitHub Create Pull Request
Azure Arc Multiple Solutions with a Single Shared Dependency at Different Levels ...oad-orchestration/tutorial-service-group-scenario-4.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
⚠️ windows_first
Summary
The documentation provides both Bash and PowerShell examples for every step, but PowerShell examples are consistently shown after Bash. There are no Windows-only tools or patterns, and Linux parity is maintained throughout. No critical steps are Windows-only, and all commands are cross-platform via the Azure CLI and Helm.
Recommendations
  • Consider alternating the order of Bash and PowerShell tabs in some sections to avoid implicit prioritization.
  • Explicitly state that Bash examples are suitable for Linux/macOS and PowerShell for Windows, to help users quickly identify their relevant environment.
  • Add a brief note at the start clarifying that all steps are cross-platform unless otherwise noted.
GitHub Create Pull Request
Azure Portal Programmatically create Azure Dashboards ...tal/azure-portal-dashboards-create-programmatically.md
Low Priority View Details →
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation provides deployment instructions for Azure dashboards using three methods: Azure portal, Azure CLI, and Azure PowerShell. The Azure CLI section is cross-platform and appears before the PowerShell section, which is Windows-centric. However, PowerShell is presented as a distinct method and includes detailed examples, potentially favoring Windows users. No Linux/macOS-specific tools or shell examples (such as Bash scripting or automation) are provided, and PowerShell is not explicitly flagged as cross-platform (though PowerShell Core is available on Linux/macOS). The documentation does not show Windows tools or patterns exclusively, but PowerShell is highlighted as a primary method alongside CLI, which may create minor friction for Linux/macOS users.
Recommendations
  • Clarify that Azure PowerShell can be used on Linux/macOS via PowerShell Core, or link to instructions for installing PowerShell on non-Windows platforms.
  • Add Bash shell scripting examples for Azure CLI deployment to demonstrate automation parity for Linux/macOS users.
  • Explicitly mention that all Azure CLI commands work on Linux, macOS, and Windows.
  • Consider providing a table or summary comparing deployment methods and their cross-platform compatibility.
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
⚠️ windows_first ⚠️ powershell_heavy
Summary
The documentation mentions generating CLI and PowerShell scripts as a key scenario, listing PowerShell alongside CLI. PowerShell is primarily associated with Windows, and its mention before Bash or Linux shell scripting may indicate a mild Windows bias. However, no exclusive Windows tools or patterns are described, and the page is focused on a cross-platform mobile app.
Recommendations
  • Explicitly mention Bash or Linux shell scripting alongside PowerShell and CLI when listing code generation capabilities.
  • Provide examples or clarify that Azure Copilot can generate scripts for both Windows (PowerShell) and Linux/macOS (Bash, CLI).
  • Ensure parity in documentation by referencing cross-platform scripting options equally.
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 to Azure Container Registry, but consistently lists Azure PowerShell after Azure CLI. While Azure PowerShell is a Windows-centric tool, no Linux/macOS-specific shell examples (e.g., Bash) are provided, nor are Linux-native tools or workflows mentioned. The documentation does not exclusively use Windows tools, but the inclusion of PowerShell and lack of Linux-specific examples creates a mild Windows bias.
Recommendations
  • Add explicit Bash or shell script examples for Linux/macOS users, especially for common tasks like importing images.
  • Mention that Azure CLI is cross-platform and can be used on Linux/macOS, and clarify PowerShell's Windows-centric nature.
  • Consider providing sample workflows using Docker CLI or other Linux-native tools where appropriate.
  • Ensure parity in example ordering (e.g., alternate which example appears first or clarify both are equally supported).
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, but there are subtle Windows biases. The environment variable setup uses the Windows-style 'set' command without showing the equivalent Linux/macOS 'export' command. Additionally, the order of Kubernetes cluster creation options lists Azure CLI first, but also includes PowerShell and Portal, which is acceptable. Most CLI examples use Azure CLI and Helm, which are cross-platform, but the initial environment variable setup and lack of explicit Linux/macOS equivalents create minor friction.
Recommendations
  • Add Linux/macOS equivalents for environment variable setup, e.g., 'export ACR_NAME=<container-registry-name>' alongside 'set' for Windows.
  • Where commands differ by platform (such as environment variables), provide both Windows and Linux/macOS examples, or use a platform-neutral approach.
  • Explicitly mention that Azure CLI and Helm commands work on all platforms, and clarify any platform-specific steps.
  • Consider listing Linux/macOS commands first or equally alongside Windows commands to avoid 'windows_first' bias.
GitHub Create Pull Request
Container Registry Deploy the Connected Registry Arc Extension ...iner-registry/quickstart-connected-registry-arc-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 Bash and PowerShell examples for generating the protected settings JSON file, but the PowerShell example is shown after Bash and is not strictly necessary for the task. All other CLI and kubectl commands are shown in Bash syntax, which is cross-platform. There is a mild bias in that PowerShell is included, but Linux/macOS users are not disadvantaged, as Bash is shown first and is the default for most steps.
Recommendations
  • Clarify that Bash examples are suitable for Linux/macOS and Windows (via WSL or Git Bash), and PowerShell is for Windows users.
  • Consider including a note explaining which shell to use on each platform.
  • Ensure parity in output formatting and file naming between Bash and PowerShell examples.
  • If PowerShell is included, also mention Windows Subsystem for Linux (WSL) as a recommended shell for Windows users who prefer Bash.
GitHub Create Pull Request