Azure Arc

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

Bias Trend Over Time

Pages with Bias Issues

2334 issues found
Showing 651-675 of 2334 flagged pages
Azure Arc Enable VM Extensions Using Azure Resource Manager Template ...les/azure-arc/servers/manage-vm-extensions-template.md
Medium Priority View Details →
Scanned: 2026-03-09 00:00
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 commands and instructions exclusively use Azure PowerShell, with no Azure CLI or Bash equivalents. Additionally, PowerShell deployment commands are presented first and throughout, which may create friction for Linux/macOS users who prefer Azure CLI or Bash. Windows file paths are used in sample commands, further reinforcing a Windows-centric approach.
Recommendations
  • Add Azure CLI deployment command examples alongside PowerShell, e.g., az deployment group create.
  • Include Bash shell usage instructions for Linux/macOS users.
  • Present deployment commands for both Windows and Linux platforms in parallel, or clarify that PowerShell is cross-platform.
  • Use generic file paths (e.g., ./Templates/...) in examples instead of Windows-specific paths (e.g., D:\Azure\Templates\...).
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 →
Scanned: 2026-03-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation generally presents Azure Arc and Azure Monitor Agent as cross-platform solutions for both Windows and Linux. However, there is a subtle Windows bias: Windows-specific tools (Windows Admin Center, Windows Server Graphical Installer, Group Policy) are mentioned explicitly, while Linux equivalents (such as Cockpit, cloud-init, or Linux-native package managers) are not. PowerShell is referenced before Bash, and there are no concrete Linux-specific deployment examples or tool mentions. The 'Standalone Azure Monitor Agent installation' section only references Windows clients, with no mention of Linux client scenarios.
Recommendations
  • Add explicit references to Linux-native deployment tools and methods (e.g., cloud-init, shell scripts, Ansible for Linux, Linux package managers) alongside Windows tools.
  • Provide Linux-specific examples or clarify that Bash scripts are supported equally.
  • In the 'Standalone Azure Monitor Agent installation' section, clarify the options (or lack thereof) for Linux client devices.
  • Where Windows tools are mentioned (e.g., Windows Admin Center, Group Policy), add Linux equivalents or state if none exist.
  • Ensure that PowerShell and Bash examples are presented with parity, or clarify when a method is Windows-only.
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 →
Scanned: 2026-03-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides comprehensive coverage for both Windows and Linux platforms, including installation, upgrade, uninstallation, and proxy configuration. However, there is a mild Windows bias: Windows examples and tools (such as PowerShell scripts, Msiexec, Control Panel, Group Policy, WSUS, Configuration Manager) are often presented first or in greater detail, and the only cleanup script for stale resources is provided in PowerShell. Linux instructions are present and clear, but advanced automation examples (e.g., scripting for cleanup) are Windows/PowerShell-only.
Recommendations
  • Add equivalent Linux shell scripts (e.g., Bash) for resource cleanup and automation tasks, or reference Azure CLI for cross-platform scripting.
  • Where possible, present Windows and Linux instructions in parallel, rather than Windows-first.
  • Include Linux-specific automation examples for tasks like agent removal, upgrades, and stale resource cleanup.
  • Reference cross-platform tools (Azure CLI) before or alongside Windows-specific tools (PowerShell).
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 →
Scanned: 2026-03-09 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation claims support for both Windows and Linux Arc-enabled servers, but the majority of examples and guidance are heavily skewed toward Windows and PowerShell. PowerShell is used as the primary scripting language in both Azure PowerShell and Azure CLI examples, and REST API samples exclusively use Windows-specific cmdlets (e.g., New-NetFirewallRule) and reference Windows Server resources. There are no Linux shell script examples, and Windows tools (such as New-AzStorageBlobSASToken) are referenced without Linux equivalents. This creates friction for Linux users and makes it unclear how to use the feature with Linux servers.
Recommendations
  • Add Linux-focused examples throughout, especially in the Azure CLI and REST API sections. For example, show how to run a Bash script (e.g., 'echo Hello World' or 'id') on a Linux Arc-enabled server.
  • In REST API examples, provide at least one scenario using a Linux server (e.g., running a shell script to update packages or configure iptables).
  • When referencing tools for generating SAS tokens or managing blobs, mention cross-platform or CLI alternatives (e.g., Azure CLI 'az storage blob generate-sas') and not just PowerShell cmdlets.
  • When describing parameter passing, clarify the differences for Linux (e.g., how environment variables or arguments are handled in Bash scripts).
  • Ensure that Linux and Windows examples are presented with parity and, where possible, alternate the order or group them together.
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 →
Scanned: 2026-03-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides detailed recovery instructions and a script download specifically for Windows, using PowerShell. There are no equivalent instructions, scripts, or guidance for performing the recovery from a Linux or macOS machine. The section is explicitly titled 'Recover Arc resource bridge from a Windows machine', and no alternative is offered for non-Windows users.
Recommendations
  • Provide equivalent recovery instructions and scripts for Linux/macOS environments, using Bash or cross-platform tools where possible.
  • If the recovery process is only supported on Windows, clearly state this limitation at the beginning of the article.
  • If partial steps can be performed from Linux/macOS (e.g., preparing config files, interacting with Azure CLI), document those to help non-Windows users participate in the process.
  • Consider offering a platform-agnostic script (e.g., written in Python or using Azure CLI) if feasible.
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 →
Scanned: 2026-03-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page provides multiple methods for installing Arc agents at scale for VMware VMs. However, the primary automation script is PowerShell-based, with instructions and examples focused on Windows environments (e.g., PowerShell terminal, Windows Task Scheduler for cron jobs, Set-ExecutionPolicy). Windows tools and patterns are mentioned first and in detail, while Linux equivalents (e.g., cron, shell scripting) are missing or only briefly referenced. Although Linux is acknowledged (e.g., sudo configuration), practical Linux/macOS automation examples are absent.
Recommendations
  • Provide equivalent shell script or Bash examples for Linux/macOS users, especially for the automation script.
  • Include instructions for running the automation script via cron on Linux, not just Windows Task Scheduler.
  • Offer guidance for using PowerShell Core on Linux/macOS, if the script is cross-platform, or clarify Windows-only limitations.
  • Ensure that out-of-band methods (e.g., Ansible) are given equal prominence and example detail as Windows-centric methods.
  • Add Linux/macOS-specific troubleshooting and prerequisites alongside Windows instructions.
GitHub Create Pull Request
Azure Arc Perform disaster recovery operations ...mware-vsphere/recover-from-resource-bridge-deletion.md
Medium Priority View Details →
Scanned: 2026-03-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation provides only PowerShell examples and references, with no mention of Bash, Linux shell, or cross-platform alternatives. All script examples and instructions are PowerShell-centric, and the onboarding script is referenced as a .ps1 file, implying Windows usage. There is no guidance for Linux/macOS users, nor are alternative tools or commands provided.
Recommendations
  • Provide Bash or shell script equivalents for onboarding and recovery steps, or clarify if the onboarding script is cross-platform.
  • Explicitly state OS requirements for running the onboarding script, and mention if Linux/macOS users can use Azure CLI or other tools.
  • Add instructions or links for Linux/macOS users, including how to install prerequisites and run scripts.
  • If the onboarding script is Windows-only, recommend using Windows containers or VMs for Linux/macOS users, and clarify this limitation.
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 →
Scanned: 2026-03-09 00:00
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), with no mention of Linux/macOS-compatible alternatives or guidance. All usage examples are PowerShell-based, and there is no indication that the script can be run on Linux or with Bash, nor are cross-platform instructions provided.
Recommendations
  • Clarify whether the PowerShell script is compatible with PowerShell Core (pwsh), which runs on Linux/macOS, or if it is Windows-only.
  • If the script is cross-platform, provide usage examples for Linux/macOS (using pwsh) and note any prerequisites (such as installing PowerShell Core).
  • If the script is Windows-only, explicitly state this limitation in the prerequisites section.
  • Consider providing a Bash or Python equivalent script for Linux/macOS users, or instructions for using Azure CLI to achieve the same clean-up tasks.
  • Add a note about how Linux/macOS users can perform the clean-up, even if only via Azure CLI or portal.
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 →
Scanned: 2026-03-09 00:00
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 changes and script invocation, but does not offer equivalent Linux/macOS guidance. The script section is Windows-centric, and Linux users are left without clear instructions for running the script or workarounds. Additionally, Windows instructions are presented before Linux ones, and Linux removal steps are less detailed.
Recommendations
  • Add explicit instructions for running the deboarding script on Linux/macOS, including prerequisites (e.g., PowerShell Core, Azure CLI), script invocation, and any required permission changes.
  • Clarify whether the deboarding script is cross-platform or Windows-only. If cross-platform, provide bash/zsh examples and note any OS-specific caveats.
  • Ensure parity in detail for uninstalling agents and extensions on Linux, matching the clarity of Windows instructions.
  • Consider presenting Windows and Linux instructions side-by-side or in parallel sections to avoid 'windows_first' bias.
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 →
Scanned: 2026-03-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation page consistently uses PowerShell syntax for Azure CLI commands and references a PowerShell script (bulk_deployment.ps1) for bulk deployment automation. There are no Bash or Linux/macOS shell examples, and the script provided is only in PowerShell, which is natively supported on Windows. This creates friction for Linux/macOS users, who may need to adapt commands or scripts for their environment.
Recommendations
  • Provide Azure CLI command examples in Bash syntax as well as PowerShell, or use generic CLI syntax that works across platforms.
  • Offer a Bash shell script equivalent to bulk_deployment.ps1, or note how Linux/macOS users can run the PowerShell script (e.g., via PowerShell Core).
  • Explicitly state that Azure CLI commands are cross-platform and clarify any OS-specific requirements for scripts.
  • Add notes or sections for Linux/macOS users, including troubleshooting tips or alternative approaches.
GitHub Create Pull Request
Azure Arc Troubleshooting for Workload Orchestration ...es/azure-arc/workload-orchestration/troubleshooting.md
Medium Priority View Details →
Scanned: 2026-03-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The troubleshooting guidance is heavily PowerShell-centric, with nearly all code examples provided in PowerShell syntax and Windows command patterns. Linux/Bash equivalents are missing for most critical steps, except for the 'service groups' section, which offers both Bash and PowerShell tabs. This creates friction for Linux/macOS users, who must translate PowerShell commands or guess the correct Bash syntax.
Recommendations
  • Provide Bash/Linux equivalents for all PowerShell commands, especially for Azure CLI, Docker, and Kubernetes operations.
  • Ensure examples are presented in both Bash and PowerShell tabs throughout the document, not just in the 'service groups' section.
  • Avoid using Windows-specific PowerShell constructs (e.g., ConvertTo-Json, Out-File, [Convert]::ToBase64String) without showing how to achieve the same in Bash/Linux.
  • Clarify when a command is cross-platform (e.g., az CLI, kubectl, docker) and show the syntax for both environments.
  • Review file encoding instructions to ensure they are relevant for Linux/macOS users (e.g., mention how to check/save UTF-8 files in Linux editors).
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 →
Scanned: 2026-03-09 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page provides nearly all CLI and scripting examples using PowerShell syntax, including backticks for line continuation and explicit PowerShell script usage (.ps1 files). Paths in JSON templates are Windows-style (e.g., C:\Users\...), and no Bash or Linux/macOS shell equivalents are given. The instructions for onboarding, enabling diagnostics, and collecting logs are all shown with PowerShell scripts, creating friction for Linux/macOS users who must adapt these steps. There is no mention of Linux tools or shell patterns, and Windows conventions (paths, PowerShell) are used throughout.
Recommendations
  • Provide Bash/sh examples alongside PowerShell for all CLI commands, especially az CLI usage.
  • Show Linux/macOS file path conventions in JSON templates (e.g., /home/user/...) or note that paths should be adapted.
  • Clarify that .ps1 scripts can be rewritten as Bash scripts, or provide Bash versions if possible.
  • Mention cross-platform compatibility for az CLI commands and highlight any Windows-only steps.
  • 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 →
Scanned: 2026-03-09 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation exhibits Windows bias in several areas. The example for installing kubectl uses the Windows-specific 'winget' tool, with no Linux/macOS equivalent provided. In the file extraction section, the Bash example incorrectly uses the Windows-native 'Expand-Archive' command, which is not available on Linux/macOS, and all example paths are Windows-style. There are no Linux/macOS-specific instructions for these steps, and Windows tools/patterns are mentioned exclusively or first. The rest of the guide uses Azure CLI and PowerShell, which are cross-platform, but the initial setup steps create friction for non-Windows users.
Recommendations
  • Provide Linux/macOS installation instructions for kubectl (e.g., using 'curl' or 'apt', 'brew', etc.).
  • Correct the Bash tab to use native Linux/macOS commands for extracting ZIP files (e.g., 'unzip archive.zip -d /path/to/dir').
  • Include Linux/macOS file path examples alongside Windows paths.
  • Ensure all critical steps have Linux/macOS equivalents and are presented with equal prominence.
  • Consider adding a note clarifying cross-platform support and linking to OS-specific guides where appropriate.
GitHub Create Pull Request
Azure Arc Release Notes for Workload Orchestration ...cles/azure-arc/workload-orchestration/release-notes.md
Medium Priority View Details →
Scanned: 2026-03-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides CLI examples primarily using PowerShell syntax, especially in the May 2025 release section. Bash examples are used elsewhere, but PowerShell is shown first and exclusively for configuration file operations. There is no mention of Linux/macOS-specific shell usage or parity for these examples, and no explicit guidance for non-Windows users.
Recommendations
  • Provide equivalent Bash examples for all CLI commands, especially those shown in PowerShell.
  • Add a note clarifying that Azure CLI commands work cross-platform and can be run in Bash, PowerShell, or other shells.
  • Ensure that all CLI instructions are presented in both Bash and PowerShell syntax, or use a neutral format where possible.
  • Explicitly mention Linux/macOS compatibility for the Azure CLI extension and commands.
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 →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides examples and file paths primarily for Windows environments (e.g., C:\Backupfiles\test.bak) and references Windows tools (e.g., Notepad, SSMS) without offering equivalent Linux/macOS commands, file paths, or tool suggestions. Linux/macOS users are left to adapt the instructions themselves, which may cause confusion or friction.
Recommendations
  • Add parallel examples for Linux/macOS users, including file paths (e.g., /home/user/backup/test.bak) and commands.
  • Mention cross-platform alternatives to Notepad (e.g., gedit, nano, TextEdit) when suggesting where to paste credentials.
  • Clarify that Visual Studio Code, Azure Storage Explorer, and kubectl are cross-platform, and provide installation links for Linux/macOS.
  • When referencing SSMS (Windows-only), suggest Azure Data Studio as a cross-platform alternative for backup/restore operations.
  • Show both Windows and Linux/macOS file path examples in backup/restore commands and kubectl cp usage.
GitHub Create Pull Request
Azure Arc Troubleshoot Azure Arc resource bridge issues ...re-arc/resource-bridge/troubleshoot-resource-bridge.md
Medium Priority View Details →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides troubleshooting guidance for Azure Arc resource bridge, which is a cross-platform solution. However, there are several instances where Windows-specific tools (PowerShell, RDP) are referenced, and Windows-centric patterns (e.g., PowerShell commands, Windows paths) are presented before Linux equivalents. For example, PowerShell is used for HTTP/2 troubleshooting, and Windows file paths are shown in error messages. Linux troubleshooting commands are mentioned only in passing (e.g., ldd --version for GLIBC), and some CLI instructions reference Windows environments (e.g., C:\Program Files).
Recommendations
  • Provide Linux/macOS equivalents for PowerShell commands (e.g., use curl or wget for HTTP/2 troubleshooting).
  • Ensure CLI troubleshooting steps include both Windows and Linux paths and error messages.
  • When referencing file system locations or permissions, include both Windows and Linux/macOS examples.
  • When suggesting remote access, mention SSH for Linux/macOS alongside RDP for Windows.
  • Review all troubleshooting steps to ensure Linux/macOS users are equally supported and not required to use Windows tools.
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 →
Scanned: 2026-03-08 00:00
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 equivalents, or cross-platform alternatives. This creates friction for Linux/macOS users who may not have PowerShell installed or prefer native shell environments.
Recommendations
  • Provide a Bash or shell script equivalent for Linux/macOS users.
  • Document how to run the PowerShell script on Linux/macOS (e.g., using PowerShell Core, pwsh).
  • Add explicit instructions or troubleshooting for Linux/macOS environments.
  • Clarify if the script is cross-platform or Windows-only, and offer alternatives if not.
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 →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
While the documentation is focused on configuring AKS Edge Essentials on Linux, it relies on the PowerShell-based Invoke-AksEdgeNodeCommand for system configuration steps (e.g., checking and setting sysctl values). There are no direct Linux shell (bash) equivalents provided for these commands, which may create friction for users working directly on Linux hosts without Windows tools.
Recommendations
  • Provide native Linux shell (bash) command examples for checking and setting sysctl values (e.g., 'sysctl fs.inotify.max_user_instances' and 'echo "fs.inotify.max_user_instances = 1024" | sudo tee -a /etc/sysctl.conf && sudo sysctl -p').
  • Clarify when and why Invoke-AksEdgeNodeCommand is required, and offer alternatives for users managing Linux hosts directly.
  • Ensure all critical configuration steps can be completed using standard Linux tools, not just via PowerShell modules.
GitHub Create Pull Request
Azure Arc Back up controller database .../articles/azure-arc/data/backup-controller-database.md
Medium Priority View Details →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides SQL connectivity examples using PowerShell syntax (e.g., kubectl exec ... -- /opt/mssql-tools/bin/sqlcmd) and labels these blocks as 'powershell'. There are no explicit Linux/macOS shell examples, and the PowerShell blocks are presented first and exclusively. This may create friction for Linux/macOS users unfamiliar with PowerShell or expecting bash/zsh syntax.
Recommendations
  • Add equivalent Linux/macOS shell examples (e.g., bash/zsh) for connecting to the SQL Server pod using sqlcmd.
  • Label code blocks appropriately (e.g., 'console' or 'bash') instead of 'powershell' when the command is not PowerShell-specific.
  • Ensure that instructions and examples are platform-neutral where possible, or provide parallel examples for each major OS.
  • Clarify that the commands can be run from any OS with kubectl and sqlcmd installed, not just Windows/PowerShell environments.
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 →
Scanned: 2026-03-08 00:00
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 Profiler, SQL Server PowerShell) and explicitly lists PowerShell scripting support as a manageability feature. However, it also mentions cross-platform tools like Azure CLI and Visual Studio Code. No Linux/macOS-specific examples, tools, or patterns are provided, and Windows tools are listed without Linux alternatives or parity discussion.
Recommendations
  • Add examples or mention of Linux/macOS-compatible management tools (e.g., sqlcmd, Azure Data Studio, mssql-cli).
  • Clarify which features and tools are available or supported on Linux/macOS environments.
  • Provide parity tables or notes for manageability features and scripting support on non-Windows platforms.
  • Include links or references to cross-platform documentation and usage guides.
GitHub Create Pull Request
Azure Arc Azure Arc resource bridge system requirements ...icles/azure-arc/resource-bridge/system-requirements.md
Medium Priority View Details →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation references Azure CLI installation links that default to Windows, and mentions Azure CLI x64 and x86 requirements without clarifying Linux/macOS equivalents. The management machine requirements and CLI instructions do not specify Linux/macOS support or provide parity guidance, which may create friction for non-Windows users.
Recommendations
  • Explicitly state that Azure CLI is supported on Linux and macOS, and provide installation links for those platforms alongside Windows.
  • Clarify whether 'x64' and 'x86' requirements apply to Linux/macOS, or if they are Windows-specific.
  • Add examples or guidance for Linux/macOS management machines, including directory paths and CLI usage.
  • Ensure CLI commands and file locations are described in a cross-platform manner.
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 →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation generally provides parity between Windows and Linux for feature lists and bug fixes, but there is a consistent pattern of presenting Windows download links and version numbers before Linux. Known issue troubleshooting steps are provided only for Windows, with detailed PowerShell and Command Prompt commands, while Linux equivalents are absent. Some improvements and bug fixes reference Windows-specific tools (e.g., PowerShell scripts, MSI installer) without mentioning Linux alternatives.
Recommendations
  • When presenting download links or version tables, alternate the order or present Windows and Linux together to avoid implicit prioritization.
  • For troubleshooting steps (e.g., editing agent configuration files), provide equivalent Linux commands (such as chmod/chown or nano/vi usage) alongside Windows instructions.
  • Where improvements or bug fixes reference Windows-specific tools (e.g., PowerShell scripts, MSI installer), clarify if there are Linux equivalents or note if the issue is not applicable to Linux.
  • Consider adding a section or callout for Linux-specific known issues and troubleshooting steps, even if there are currently none, to demonstrate parity.
GitHub Create Pull Request
Azure Arc Azure Connected Machine Agent Deployment Options .../main/articles/azure-arc/servers/deployment-options.md
Medium Priority View Details →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides a comprehensive overview of deployment options for both Linux and Windows, but there is a noticeable emphasis on Windows-specific tools and workflows. PowerShell is highlighted as a primary method for both platforms, and several Windows-only methods (such as Windows Admin Center, Group Policy, and Configuration Manager) are listed separately and in detail. Linux-specific automation tools (other than Ansible) are not mentioned, and PowerShell is presented as a cross-platform solution, which may not align with typical Linux admin workflows.
Recommendations
  • Add explicit Bash or shell script examples for Linux where PowerShell is currently suggested, or clarify that PowerShell Core is required on Linux for those methods.
  • Include Linux-native automation tools (e.g., cloud-init, shell scripts, or configuration management tools like Chef/Puppet) if supported.
  • When listing onboarding methods, alternate the order or group by OS to avoid a Windows-first impression.
  • Clarify in the PowerShell method description that it is cross-platform, and provide direct Linux command-line examples where possible.
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 →
Scanned: 2026-03-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides comprehensive coverage for both Windows and Linux platforms, including installation, upgrade, uninstallation, and proxy configuration. However, there are signs of Windows bias: Windows examples and instructions are often presented first, especially in sections with tabbed content; PowerShell is heavily used for scripting and automation examples (e.g., stale resource cleanup); and Windows-specific tools and infrastructure (e.g., Group Policy, WSUS, Configuration Manager) are described in detail, while Linux equivalents (such as package management automation or scripting) are not covered as thoroughly.
Recommendations
  • Alternate the order of Windows and Linux examples in tabbed sections, or present Linux instructions first in some cases.
  • Provide equivalent Linux shell scripts for automation tasks, such as stale resource cleanup, using Azure CLI or Bash.
  • Expand documentation for Linux update automation (e.g., using cron, unattended-upgrades, or systemd timers) to match the detail given for Windows update infrastructure.
  • Include references to Linux configuration management tools (e.g., Ansible, Puppet, Chef) where Windows tools like Group Policy or Configuration Manager are mentioned.
  • Where PowerShell scripts are provided for Azure resource management, offer Azure CLI or Bash alternatives for Linux users.
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 →
Scanned: 2026-03-08 00:00
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 use Azure PowerShell exclusively, with no Azure CLI or Bash examples. PowerShell commands are shown first and are the only method described for deploying templates, which may create friction for Linux/macOS users who prefer Azure CLI or Bash. Additionally, file path examples use Windows-style paths (e.g., 'D:\Azure\Templates'), which may be confusing for non-Windows users.
Recommendations
  • Add Azure CLI deployment examples alongside PowerShell, especially for template deployments (e.g., az deployment group create).
  • Include Bash or shell script snippets for Linux/macOS users where appropriate.
  • Show file path examples using both Windows and Linux conventions (e.g., 'D:\Azure\Templates' and '/home/user/Azure/Templates').
  • Explicitly mention that Azure PowerShell commands can be run cross-platform, but Azure CLI is often preferred on Linux/macOS.
  • Consider listing Azure CLI deployment commands before or alongside PowerShell to avoid 'windows_first' bias.
GitHub Create Pull Request
← Previous Page 27 of 94 Next →