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 626-650 of 2334 flagged pages
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-10 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 does not offer equivalent Linux/macOS examples for backing up databases or copying files. Tools like Visual Studio Code and Azure Storage Explorer are cross-platform, but the backup and file copy steps are shown only with Windows-style paths and commands, which may confuse or hinder Linux/macOS users.
Recommendations
  • Include Linux/macOS equivalents for file paths in backup examples (e.g., /home/user/backup/test.bak).
  • Show both Windows and Linux/macOS examples for the BACKUP DATABASE command and kubectl cp usage.
  • Explicitly state that the steps apply to all platforms, and clarify any platform-specific differences.
  • Add notes or callouts where tool usage or file system conventions differ between Windows and Linux/macOS.
GitHub Create Pull Request
Azure Arc Install client tools ...b/main/articles/azure-arc/data/install-client-tools.md
Medium Priority View Details →
Scanned: 2026-03-10 00:00
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 examples and notes are often presented first or in more detail. For 'kubectl', Windows installation is listed first, and there is a specific note about using cmd.exe instead of PowerShell for curl. For 'curl', Windows is explicitly linked, while Linux is mentioned only as 'install curl package' without a link or command. There is also a PowerShell-specific note about curl aliasing, but no equivalent Linux/macOS shell guidance.
Recommendations
  • Present Linux/macOS installation instructions and links before or alongside Windows, not after.
  • For 'curl', provide explicit Linux/macOS installation commands (e.g., 'sudo apt install curl', 'brew install curl') and relevant links.
  • Add shell-specific notes for Linux/macOS users (e.g., bash/zsh) similar to the PowerShell note.
  • Ensure parity in detail and clarity for Linux/macOS instructions, not just Windows.
  • Consider a platform-neutral table or section, or clearly separate instructions by OS.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows Authentication Windows First
Summary
The documentation page lists several Windows-centric tools and features, such as PowerShell scripting support, SQL Server Management Studio (SSMS), SQL Server Data Tools (SSDT), and Windows Authentication. While Azure CLI and Visual Studio Code are mentioned, Windows tools are referenced more frequently and prominently. PowerShell scripting is highlighted as a manageability feature, and Windows Authentication is listed as a supported security feature, with no mention of Linux/macOS alternatives or parity. The tools table includes multiple Windows-only tools, and PowerShell is referenced in both manageability and unsupported features sections.
Recommendations
  • Add explicit examples or guidance for Linux/macOS users, such as using Bash scripting or cross-platform tools.
  • Clarify which tools are cross-platform and which are Windows-only, and provide alternatives for Linux/macOS where possible.
  • Mention authentication options available for Linux/macOS users, such as Microsoft Entra ID or SQL Authentication, and note any limitations.
  • Include links to documentation for using Azure Arc SQL Managed Instance from Linux/macOS environments.
  • Reorder tool lists to avoid Windows-first bias and highlight cross-platform tools equally.
GitHub Create Pull Request
Azure Arc Customer intent: "As a network administrator, I want to configure outbound and inbound connectivity settings for the appliance VM and management machine, so that I can ensure smooth communication and functionality for the Arc resource bridge." ...e-arc/resource-bridge/includes/network-requirements.md
Medium Priority View Details →
Scanned: 2026-03-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation includes references to Windows-specific services (e.g., time.windows.com for NTP, sts.windows.net, login.windows.net, servicebus.windows.net) and Windows terminology (e.g., 'Management machine' and 'Hyper-V default is Windows NTP') without always providing Linux equivalents or clarifying cross-platform applicability. Windows NTP is mentioned, but Linux NTP alternatives are not. Windows-related endpoints appear before Linux-specific ones (e.g., Microsoft open source packages manager for Linux is listed after Windows NTP). However, SSH and Kubernetes API server ports are documented, which are cross-platform.
Recommendations
  • Clarify that NTP can use Linux NTP servers (e.g., pool.ntp.org) and provide Linux-specific guidance alongside Windows NTP.
  • Where Windows-specific endpoints are mentioned (e.g., sts.windows.net, login.windows.net), explain their relevance for Linux deployments or provide Linux alternatives if applicable.
  • Ensure Linux tools and endpoints (such as packages.microsoft.com) are given equal prominence and not listed after Windows-specific items.
  • Explicitly state that the management machine and appliance VM can be Linux or Windows, and provide any OS-specific requirements or examples.
  • Add notes or examples for Linux-based management machines and appliance VMs where relevant.
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-10 00:00
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 indications of Windows bias: PowerShell is used for network troubleshooting (e.g., Invoke-WebRequest, Resolve-DnsName) without equivalent Linux/macOS commands; Windows paths and error messages are shown first or exclusively; and some CLI instructions reference Windows-specific patterns (e.g., uninstalling Azure CLI via installer, referencing C:\Program Files). Linux-specific troubleshooting (such as using curl, nslookup, or ldd) is mentioned only in a few places and often as an afterthought. There are missing Linux/macOS equivalents for several diagnostic steps, especially for proxy, DNS, and network validation.
Recommendations
  • Provide Linux/macOS command equivalents for all PowerShell examples (e.g., use curl or wget for HTTP troubleshooting, dig or nslookup for DNS).
  • When referencing file paths or error messages, include both Windows and Linux/macOS formats.
  • Ensure CLI installation/downgrade instructions cover both Windows and Linux (e.g., apt, yum, brew, pip).
  • Add troubleshooting steps for Linux/macOS environments, especially for proxy and network configuration.
  • Where PowerShell is used, offer Bash or shell script alternatives.
  • Review all troubleshooting steps for platform neutrality and parity.
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-10 00:00
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 parity for most features and bug fixes, but exhibits Windows bias in several areas. Windows download links and version numbers are consistently listed first. Windows-specific troubleshooting steps (e.g., using Command Prompt and PowerShell commands) are provided, while Linux equivalents are missing for similar issues. Windows tools (attrib, PowerShell, msiexec) are referenced without Linux alternatives. Some known issues and installation guidance are Windows-only, with no Linux troubleshooting guidance.
Recommendations
  • When listing download links, alternate the order or present both Windows and Linux equally.
  • For troubleshooting steps, provide Linux equivalents (e.g., chmod/chown for file permissions, shell commands for agent configuration).
  • Include Linux-specific known issues and solutions where relevant.
  • Reference Linux tools and commands alongside Windows tools when discussing installation, configuration, or troubleshooting.
  • Ensure that bug fix explanations and feature descriptions are equally detailed for both platforms.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation provides deployment options for the Azure Connected Machine agent, covering both Linux and Windows. However, several onboarding methods are Windows-specific (e.g., Windows Admin Center, Group Policy, Configuration Manager), and PowerShell is highlighted as a cross-platform tool but is more commonly associated with Windows. Windows-specific tools and methods are listed separately and in greater detail, and PowerShell-based onboarding is mentioned before Linux-native alternatives (e.g., Bash, Ansible). There are no Linux-only onboarding methods or examples provided, and Linux-native automation tools (other than Ansible) are missing.
Recommendations
  • Add Linux-specific onboarding examples, such as Bash scripts or instructions using native Linux tools.
  • Clarify which PowerShell methods are cross-platform and provide equivalent Bash or shell script examples for Linux users.
  • Include Linux-native automation options (e.g., using shell scripts, cron jobs, or other configuration management tools like Puppet or Chef).
  • Ensure that Linux onboarding methods are described with equal detail and prominence as Windows methods.
  • Consider listing Linux and Windows methods in parallel, rather than grouping Windows-specific options at the end.
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-10 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, uninstall, and proxy configuration. However, there are several areas where Windows bias is evident: Windows examples and instructions are often presented first, PowerShell scripts are used for automation and cleanup tasks without equivalent Bash or shell scripts for Linux, and Windows-specific tools (such as Group Policy, WSUS, Configuration Manager, Control Panel, and Msiexec) are described in detail while Linux equivalents are not discussed or are presented more briefly. The cleanup script for stale resources is only provided in PowerShell, leaving Linux users without a native example.
Recommendations
  • Provide Linux shell script equivalents for automation tasks, such as cleanup of stale Arc-enabled server resources.
  • Present Linux and Windows instructions in parallel or alternate their order to avoid always showing Windows first.
  • Expand Linux sections to include more detail about package management, update automation, and system tools (e.g., using cron for scheduled upgrades, or systemd for service management).
  • Where Windows-specific tools are discussed (e.g., Group Policy, WSUS), mention Linux alternatives or clarify their absence.
  • Include Bash or shell script examples for tasks currently only shown in 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-10 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 provides extensive PowerShell examples and references to Windows tools (such as New-NetFirewallRule and New-AzStorageBlobSASToken), with Windows-centric scripting and REST API scenarios. While the Azure CLI section is present, its examples use Windows PowerShell syntax (Write-Host) and do not demonstrate Linux shell scripting. The REST API section is exclusively Windows-focused, showing only Windows Server scenarios and Windows firewall configuration. There are no Linux-specific script examples, and Windows tools are referenced before Linux equivalents.
Recommendations
  • Add Linux-specific script examples in Azure CLI and PowerShell sections (e.g., bash or sh scripts, Linux command usage).
  • In REST API examples, include a Linux scenario (such as configuring iptables or ufw for firewall rules) alongside the Windows example.
  • When referencing tools for generating SAS tokens or managing blobs, mention cross-platform alternatives or clarify if the tool is Windows-only.
  • Ensure CLI examples use cross-platform syntax (e.g., echo instead of Write-Host) and provide both Windows and Linux script samples.
  • Balance the order of examples so that Linux and Windows are treated equally, or explicitly state when an example is Windows-only.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page exclusively provides PowerShell examples and references a .ps1 onboarding script, with no mention of Bash, Linux shell, or cross-platform alternatives. All scripting and command-line instructions assume a Windows environment, creating friction for Linux/macOS users who may need to perform disaster recovery operations for Azure Arc-enabled VMware vSphere environments.
Recommendations
  • Provide equivalent Bash or shell script examples for Linux/macOS users, or clarify if the onboarding script is cross-platform.
  • Explicitly state OS requirements for the onboarding script (e.g., if it requires Windows/PowerShell, mention this up front).
  • If possible, offer a platform-agnostic onboarding script or instructions for running the script on Linux/macOS (e.g., via PowerShell Core or Azure CLI).
  • Add notes or links to Linux/macOS guidance for Azure Arc resource bridge disaster recovery.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools
Summary
The documentation page exhibits notable Windows bias, particularly in the 'Auto Arc-enablement script' section, where only PowerShell examples and Windows Task Scheduler are provided for automation. Windows-centric tools and patterns (PowerShell, Task Scheduler) are mentioned exclusively, with no Linux/macOS equivalents or examples. While Linux is referenced in prerequisites and out-of-band methods, the primary scripted automation path is Windows-only, creating friction for Linux/macOS users.
Recommendations
  • Provide equivalent Bash or shell script examples for Linux/macOS users, especially for the automation script.
  • Include instructions for running the automation script as a cron job on Linux (using crontab), not just Windows Task Scheduler.
  • Clarify whether the helper script (.ps1) can be run cross-platform (e.g., with PowerShell Core), or provide a platform-neutral version.
  • Add examples for Linux/macOS terminals where PowerShell is referenced.
  • Ensure parity in automation and scheduling guidance for both Windows and Linux environments.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides detailed instructions and examples for Windows users, especially when running the deboarding script, including PowerShell-specific guidance and troubleshooting. Linux users are not given equivalent instructions for running the script, nor is there mention of how to execute the script on Linux/macOS. Windows instructions and examples are presented first and in greater detail.
Recommendations
  • Add explicit instructions for running the deboarding script on Linux/macOS, including prerequisites and command examples (e.g., using Bash, Azure CLI, or PowerShell Core).
  • Clarify whether the deboarding script is cross-platform or Windows-only; if it is cross-platform, provide Linux/macOS usage guidance.
  • Present Windows and Linux instructions in parallel sections or tables for parity.
  • Mention any requirements or limitations for Linux/macOS users (e.g., PowerShell Core compatibility, Azure CLI usage).
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-10 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) as the only provided automation example. There are no Bash or Linux/macOS shell examples, and the script is only available in PowerShell. This creates friction for Linux/macOS users, who may not have PowerShell installed or prefer Bash scripting.
Recommendations
  • Provide Azure CLI command examples in Bash syntax as well as PowerShell, or use generic CLI syntax that works cross-platform.
  • Offer a Bash shell script equivalent to bulk_deployment.ps1, or provide guidance for running the PowerShell script on Linux/macOS (e.g., via PowerShell Core).
  • Clarify that Azure CLI commands are cross-platform and can be run in Bash, PowerShell, or other shells.
  • Add notes or tabs for Linux/macOS users, indicating any differences or prerequisites (such as installing PowerShell Core if using .ps1 scripts).
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-10 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 a PowerShell script (RGCleanScript.ps1) and only shows PowerShell usage examples. There are no instructions or examples for running the clean-up process on Linux or macOS, nor is there mention of a Bash/sh or cross-platform alternative. This may prevent Linux/macOS users from easily performing the clean-up task.
Recommendations
  • Provide a Bash or cross-platform (e.g., Python) version of the clean-up script, or document how Linux/macOS users can perform equivalent clean-up steps.
  • If the PowerShell script is compatible with PowerShell Core (pwsh) on Linux/macOS, explicitly state this and provide usage examples for those platforms.
  • Add a note clarifying platform compatibility and any prerequisites for running the script on non-Windows systems.
  • If only Windows is supported, explicitly state this limitation at the top of the page.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation shows evidence of Windows bias, particularly in the installation instructions for kubectl, where only the Windows-specific 'winget' command is provided. Additionally, the Bash example for extracting ZIP files incorrectly uses the Windows PowerShell 'Expand-Archive' command, which is not available on Linux/macOS. Throughout the page, file paths and examples often use Windows-style paths (e.g., 'C:\path\to\archive.zip') as the default, and Linux/macOS equivalents are not provided or mentioned. While Azure CLI and kubectl are cross-platform tools, the documentation does not offer Linux/macOS-specific instructions for common tasks such as extracting ZIP files or installing kubectl, creating friction for non-Windows users.
Recommendations
  • Provide Linux/macOS installation instructions for kubectl (e.g., using 'curl' or 'apt', 'brew').
  • Add 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 Bash examples use commands available on Linux/macOS (avoid PowerShell-specific commands in Bash tabs).
  • Review all examples to ensure parity for Linux/macOS users, especially in setup and installation sections.
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-10 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 page demonstrates notable Windows bias. All CLI/script examples are provided exclusively in PowerShell syntax, with no Bash or Linux/macOS shell equivalents. File paths in JSON templates and script instructions use Windows-style (backslash) paths, and the onboarding scripts are referenced as PowerShell (.ps1) files only. There is no mention of Linux/macOS alternatives or guidance for non-Windows users, despite the topic being cross-platform (Azure Arc-enabled Kubernetes clusters, container logs, OpenTelemetry, etc.).
Recommendations
  • Provide Bash/zsh shell equivalents for all PowerShell script examples, especially for az CLI commands, which are cross-platform.
  • Use platform-neutral file paths in JSON templates, or provide separate examples for Windows and Linux/macOS.
  • Clarify whether onboarding scripts are available in Bash or Python for Linux/macOS users, or provide guidance on running PowerShell scripts on those platforms (e.g., via PowerShell Core).
  • Add explicit notes or sections for Linux/macOS users, including troubleshooting tips and environment setup instructions.
  • Ensure all az CLI commands are shown in both Windows (PowerShell) and Linux/macOS (Bash) syntax where applicable.
GitHub Create Pull Request
Azure Arc Onboarding Scripts for Workload Orchestration ...azure-arc/workload-orchestration/onboarding-scripts.md
Medium Priority View Details →
Scanned: 2026-03-10 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 page is heavily biased toward Windows environments. All onboarding scripts and examples are provided exclusively for PowerShell, with no mention of Bash, Linux shell, or cross-platform alternatives. The prerequisite commands use 'winget', a Windows-only package manager, and there are no instructions for installing Azure CLI or kubectl on Linux/macOS. The instructions repeatedly direct users to open a PowerShell terminal, and all script examples are in PowerShell syntax. No Linux or macOS equivalents are provided, creating friction for non-Windows users.
Recommendations
  • Provide Bash or shell script equivalents for onboarding tasks, or clarify if the scripts are cross-platform.
  • Add instructions for installing Azure CLI and kubectl using Linux/macOS package managers (e.g., apt, yum, brew).
  • Explicitly state platform requirements for the onboarding scripts (e.g., if .ps1 scripts require Windows/PowerShell Core).
  • Offer guidance for running PowerShell scripts on Linux/macOS (using PowerShell Core), or provide alternative scripts.
  • Reorder examples so that Linux/macOS instructions are given equal prominence, or at least referenced alongside Windows steps.
GitHub Create Pull Request
Azure Arc Troubleshooting for Workload Orchestration ...es/azure-arc/workload-orchestration/troubleshooting.md
Medium Priority View Details →
Scanned: 2026-03-10 00:00
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 skewed toward PowerShell and Windows-style command syntax. Most examples and solutions use PowerShell, even for tasks that are cross-platform (e.g., Azure CLI, Docker, Kubernetes). There are few, if any, Bash or Linux-native command examples in the main troubleshooting sections. Bash examples only appear in the 'service groups' section, and even there, PowerShell is shown alongside Bash, but Bash is not presented first. Several commands use Windows-specific syntax (e.g., variable assignment, ConvertTo-Json, Out-File, Base64 encoding), and there is no guidance for Linux/macOS equivalents, creating friction for non-Windows users.
Recommendations
  • Provide Bash/Linux/macOS equivalents for all PowerShell commands, especially for Azure CLI, Docker, and Kubernetes operations.
  • Show Bash examples first or alongside PowerShell, especially in cross-platform contexts.
  • Avoid using Windows-specific command patterns (e.g., PowerShell variable assignment, ConvertTo-Json, Out-File) without Linux alternatives.
  • Add notes or tabs indicating which commands are for Windows/PowerShell and which are for Bash/Linux.
  • Review all troubleshooting steps to ensure Linux/macOS users can follow them without needing to translate PowerShell syntax.
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-09 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation generally provides parity between Windows and Linux in terms of feature lists and release notes. However, there is a notable Windows-first bias in several areas: download links for Windows are always listed before Linux, and known issue remediation steps are only provided for Windows (using Command Prompt and PowerShell), with no equivalent Linux troubleshooting guidance. Additionally, Windows-specific tools and patterns (e.g., PowerShell, attrib) are referenced without Linux alternatives, and some improvements reference Windows scripts without Linux equivalents.
Recommendations
  • When listing download links or instructions, alternate or parallelize Windows and Linux to avoid implicit prioritization.
  • For troubleshooting steps (e.g., editing permissions on config files), provide equivalent Linux commands (such as chmod/chown) and instructions.
  • Where Windows-specific scripts or tools are mentioned (e.g., PowerShell, attrib), clarify if Linux users are unaffected or provide the corresponding Linux method.
  • Ensure that all known issues and fixes are addressed for both platforms, or explicitly state when an issue is Windows-only.
  • Consider including a summary table or section that highlights platform-specific differences, so Linux users can quickly identify relevant information.
GitHub Create Pull Request
Azure Arc CLI reference for `azcmagent connect` ...b/main/articles/azure-arc/servers/azcmagent-connect.md
Medium Priority View Details →
Scanned: 2026-03-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation gives Windows-specific authentication options (interactive browser login and certificate store usage) before Linux equivalents and references Windows tools (PowerShell's Get-AzAccessToken) without mentioning Linux alternatives. However, Linux authentication methods are described, and most examples are cross-platform.
Recommendations
  • Clarify that interactive browser login is Windows-only and suggest Linux alternatives more prominently.
  • When referencing PowerShell tools (e.g., Get-AzAccessToken), also mention how Linux/macOS users can obtain access tokens (e.g., Azure CLI's 'az account get-access-token').
  • Present Linux authentication options (device code, Azure CLI) before or alongside Windows options to avoid Windows-first ordering.
  • Add explicit Linux/macOS examples where appropriate, especially for certificate-based authentication (e.g., using PEM files).
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-09 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 mentions PowerShell scripting support as a manageability feature. However, it also lists cross-platform tools like Azure CLI and Visual Studio Code. No Linux/macOS-specific examples or tools are highlighted, and Windows tools are presented without Linux alternatives.
Recommendations
  • Add examples or references for Linux/macOS-compatible tools (e.g., sqlcmd, Azure Data Studio, mssql-cli).
  • Clarify which features/tools are cross-platform and which are Windows-only.
  • Provide guidance for Linux/macOS users on managing SQL Managed Instance enabled by Azure Arc, including scripting and automation options.
  • Mention or link to documentation for using Azure Arc SQL Managed Instance from Linux/macOS environments.
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-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools
Summary
The documentation is focused on configuring AKS Edge Essentials on Linux, but uses PowerShell cmdlets (Invoke-AksEdgeNodeCommand) for Linux node configuration tasks, rather than providing native Linux shell commands. This assumes the user is operating from a Windows environment or using Windows tools to manage Linux nodes, which may not align with the experience of Linux-first administrators.
Recommendations
  • Provide equivalent native Linux shell commands for tasks such as checking and setting sysctl parameters (e.g., using 'sysctl' and 'echo' directly in bash).
  • Clarify when PowerShell/Invoke-AksEdgeNodeCommand is required and offer alternatives for users managing Linux nodes directly.
  • Ensure that all critical configuration steps can be performed using standard Linux tools and document those workflows.
  • Consider including a section or callout for users who are managing from a Linux or macOS environment, outlining the appropriate 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-09 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation frequently presents Windows tools and file paths first (e.g., SSMS, C:\ paths), and omits explicit Linux/macOS examples for key steps such as database backup and file copying. While the core migration process is cross-platform, the guidance assumes a Windows environment for local operations, which may create friction for Linux/macOS users.
Recommendations
  • Provide parallel examples using Linux/macOS file paths (e.g., /home/user/backup/test.bak) in backup and kubectl cp steps.
  • Mention and give examples for common Linux SQL tools (e.g., Azure Data Studio, sqlcmd) alongside or instead of SSMS.
  • Clarify that Visual Studio Code and Azure Storage Explorer are cross-platform, and link to their Linux/macOS installation guides.
  • When referencing commands or file locations, show both Windows and Linux/macOS variants side by side.
  • Explicitly state that the process is platform-agnostic except for tool choice, and offer guidance for non-Windows users.
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-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 troubleshooting guidance for Azure Arc resource bridge, which is a cross-platform solution. However, there are several signs of Windows bias: PowerShell is referenced for troubleshooting HTTP2 issues, Windows paths are shown in error messages, and some CLI instructions (such as proxy troubleshooting and DNS resolution) use Windows-centric tools (PowerShell, Resolve-DnsName, ping) without offering Linux equivalents. Linux-specific troubleshooting is only mentioned in passing (GLIBC error), and Linux commands (such as ldd --version, nslookup) are not consistently presented alongside Windows commands. Examples and guidance often default to Windows tools and terminology, creating friction for Linux/macOS users.
Recommendations
  • Provide Linux/macOS equivalents for all PowerShell and Windows command examples (e.g., curl for HTTP2 troubleshooting, dig/nslookup for DNS resolution).
  • When referencing file paths or error messages, clarify if they are OS-specific and provide Linux/macOS alternatives where relevant.
  • Ensure troubleshooting steps and CLI instructions include both Windows and Linux/macOS guidance, especially for proxy, DNS, and network validation.
  • Add explicit notes or sections for Linux/macOS users where OS-specific issues may arise (e.g., GLIBC, SSH folder permissions).
  • Review and update examples to avoid Windows-first ordering; present cross-platform instructions 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 →
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 presents both Linux and Windows onboarding options, but Windows-specific tools and workflows (such as PowerShell, Windows Admin Center, Configuration Manager, and Group Policy) are listed with dedicated methods, while Linux-specific automation tools (other than Ansible) are not. PowerShell is highlighted as a cross-platform tool, but the documentation does not clarify if Linux users can use PowerShell or provide equivalent Bash/shell examples. Windows-specific methods are listed after cross-platform ones, but the presence of multiple Windows-only methods and the lack of Linux-specific automation examples (e.g., Bash scripts, cloud-init, or Linux-native configuration management tools besides Ansible) indicate a moderate Windows bias.
Recommendations
  • Add explicit Bash/shell script examples or links for Linux onboarding, especially for interactive and at-scale scenarios.
  • Clarify in the PowerShell method whether it is supported and tested on Linux (PowerShell Core), or provide a Linux-native alternative.
  • Consider including Linux-native automation options (e.g., cloud-init, shell scripts, or other configuration management tools like Chef/Puppet) if supported.
  • Balance the number of Windows-only and Linux-only methods, or clearly indicate when a method is Windows-specific.
  • In the table, ensure that for every Windows-specific at-scale method, a Linux equivalent is suggested if available.
GitHub Create Pull Request
← Previous Page 26 of 94 Next →