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 1176-1200 of 2334 flagged pages
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-02-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation is generally Linux-focused, but it uses Windows-centric tools (Invoke-AksEdgeNodeCommand) for Linux node configuration, and does not provide native Linux shell examples for sysctl configuration. The text editor suggestion ('Notepad') is also Windows-oriented, and there is a lack of parity for Linux command-line workflows.
Recommendations
  • Provide native Linux shell commands for sysctl configuration (e.g., 'sysctl fs.inotify.max_user_instances', 'echo ... | sudo tee ...').
  • Replace or supplement 'Invoke-AksEdgeNodeCommand' examples with direct Linux shell commands for local execution.
  • Suggest Linux-native text editors (e.g., nano, vim) instead of Notepad.
  • Clarify when Windows tools are required and offer Linux alternatives wherever possible.
GitHub Create Pull Request
Azure Arc Back up controller database .../articles/azure-arc/data/backup-controller-database.md
Medium Priority View Details →
Scanned: 2026-02-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides several command examples using PowerShell syntax (e.g., 'kubectl exec ...' with PowerShell prompt and formatting), and the SQL connectivity example is shown only with PowerShell. There are no explicit Linux/macOS shell (bash) examples, and PowerShell is used as the default shell for command snippets, which may create friction for Linux/macOS users.
Recommendations
  • Add equivalent bash/Linux/macOS shell examples for all kubectl and sqlcmd commands.
  • Use a neutral shell prompt (e.g., '$') or clarify that commands work in both PowerShell and bash.
  • Mention that sqlcmd and kubectl commands are cross-platform and provide guidance for Linux/macOS users where relevant.
  • Avoid using PowerShell-specific formatting unless the command 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 →
Scanned: 2026-02-08 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides several examples and instructions that are Windows-centric, such as using Windows file paths (e.g., C:\Backupfiles\test.bak), referencing Windows tools (SQL Server Management Studio, Notepad/OneNote), and omitting explicit Linux/macOS equivalents for backup/restore commands and file paths. Linux/macOS users may need to adapt instructions and paths, but the overall process is not Windows-exclusive.
Recommendations
  • Provide Linux/macOS file path examples alongside Windows paths in backup/restore commands (e.g., /home/user/Backupfiles/test.bak).
  • Mention cross-platform alternatives to Windows-specific tools (e.g., Azure Data Studio instead of SSMS, or generic text editors instead of Notepad/OneNote).
  • Clarify that Visual Studio Code and Azure Storage Explorer are cross-platform, and provide installation links for Linux/macOS.
  • Add explicit notes or examples for Linux/macOS users where commands or paths differ.
  • Where possible, show both Windows and Linux/macOS command syntax for kubectl cp and other shell commands.
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-02-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation lists several Windows-centric tools (SSMS, SQL Server Data Tools, SQL Server Profiler, SQL Server PowerShell) and highlights PowerShell scripting support as a manageability feature. While Azure CLI and Visual Studio Code extension are mentioned, Windows tools are referenced more frequently and appear before Linux alternatives. There are no Linux-specific management tools or examples provided, and PowerShell scripting is emphasized without mention of Bash or cross-platform scripting options.
Recommendations
  • Add examples or references for Linux/macOS management tools, such as sqlcmd or Azure Data Studio.
  • Mention Bash scripting support or cross-platform scripting approaches alongside PowerShell.
  • Clarify which tools are cross-platform and which are Windows-only, especially for SSMS and SQL Server PowerShell.
  • Consider listing Azure CLI and Visual Studio Code extension before Windows-only tools to reduce Windows-first bias.
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-02-08 00:00
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 several sections show 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 the Windows PowerShell cmdlet 'Get-AzAccessToken' without Linux alternatives. Overall, Linux is supported, but Windows-specific tools and patterns are mentioned first or exclusively.
Recommendations
  • Present Linux authentication options (device code, Azure CLI) before or alongside Windows options to avoid 'windows_first' bias.
  • For certificate-based authentication, clarify Linux usage (e.g., storing certificates in files, recommended locations, permissions) and provide explicit Linux guidance.
  • For access token acquisition, mention cross-platform methods (e.g., Azure CLI 'az account get-access-token') alongside PowerShell examples.
  • Where Windows tools (like certificate stores or PowerShell cmdlets) are referenced, provide Linux/macOS equivalents or clarify if they are not available.
  • Ensure examples and sample commands are shown for both Windows and Linux environments, including shell syntax 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-02-08 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 feature. However, there are several instances of Windows bias: PowerShell is used for network troubleshooting (e.g., Invoke-WebRequest, Resolve-DnsName), Windows paths are referenced in error messages, and Windows tools (RDP, remote PowerShell) are mentioned. Linux equivalents (e.g., curl, dig, ssh) are not provided alongside these examples. In some cases, Windows-specific troubleshooting steps are given first or exclusively, creating friction for Linux/macOS users.
Recommendations
  • Provide Linux/macOS equivalents for PowerShell commands (e.g., curl for Invoke-WebRequest, dig/nslookup for Resolve-DnsName).
  • Include troubleshooting steps for Linux management machines, such as using SSH or terminal commands instead of RDP.
  • When referencing file paths or error messages, clarify if they are OS-specific and provide Linux/macOS versions where applicable.
  • Ensure CLI examples and troubleshooting steps are presented for both Windows and Linux environments, or note any OS-specific 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 →
Scanned: 2026-02-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Windows First
Summary
The documentation provides comprehensive coverage for both Windows and Linux platforms, including installation, upgrade, uninstall, and proxy configuration. However, there is a notable Windows bias in several areas: Windows tools (Control Panel, Group Policy, Microsoft Update, WSUS, Configuration Manager) are described in detail, with lengthy step-by-step instructions, while Linux equivalents (package managers) are covered more briefly. PowerShell is heavily used for scripting and automation examples, especially for cleanup tasks, with no equivalent Bash or Linux scripting examples. Windows sections often appear first or are more detailed, and some advanced automation (e.g., stale resource cleanup) is only shown for Windows/PowerShell.
Recommendations
  • Provide equivalent Bash or shell script examples for Linux users, especially for automation tasks such as stale resource cleanup.
  • Expand Linux sections to include more detailed guidance, such as using cron jobs for automatic upgrades or removal, and managing package repositories.
  • When describing upgrade/uninstall/configuration steps, ensure parity in detail and troubleshooting tips for Linux distributions.
  • Consider presenting Windows and Linux sections in parallel or with equal prominence, rather than Windows-first.
  • For proxy configuration, include troubleshooting and service restart instructions for Linux, similar to Windows.
  • Where PowerShell scripts are provided, offer a Bash equivalent or note limitations for Linux users.
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-02-08 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) for resource clean-up, with only PowerShell usage examples and instructions. There are no Bash, shell, or Linux/macOS-compatible script options or examples. The documentation assumes the user is running PowerShell, which is traditionally a Windows tool, and does not mention cross-platform alternatives or compatibility.
Recommendations
  • Provide a Bash or shell script equivalent for Linux/macOS users, or clarify if the PowerShell script is cross-platform and can be run using PowerShell Core (pwsh) on Linux/macOS.
  • Add usage examples for Linux/macOS environments, including how to execute the script with PowerShell Core.
  • Mention any prerequisites or installation steps for PowerShell Core on Linux/macOS if the script is compatible.
  • If the script is Windows-only, explicitly state this limitation and suggest manual clean-up steps or alternative methods for Linux/macOS users.
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-02-08 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation consistently uses PowerShell syntax for all CLI examples, and references PowerShell scripts (e.g., bulk_deployment.ps1, workflow-delete.ps1) without providing equivalent Bash or shell scripts for Linux/macOS users. There are no explicit Linux/macOS CLI examples or instructions, and PowerShell is presented as the default scripting environment, which may create friction for non-Windows users.
Recommendations
  • Provide CLI command examples in Bash syntax alongside PowerShell, especially for az CLI commands, which are cross-platform.
  • Offer equivalent Bash shell scripts for bulk_deployment.ps1 and workflow-delete.ps1, or clarify if the scripts are compatible with PowerShell Core on Linux/macOS.
  • Explicitly mention cross-platform compatibility of the az CLI commands and scripts, and note any Windows-specific requirements.
  • Add a section or note for Linux/macOS users describing how to run the scripts or adapt the workflow.
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-02-08 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 file extraction step, where only Windows tools (Expand-Archive via Bash/PowerShell and winget for kubectl) are provided, with no Linux/macOS equivalents. The rest of the guide is generally cross-platform, using Azure CLI and kubectl, but the initial setup steps assume a Windows environment or require Windows-specific tools, which may cause friction for Linux/macOS users.
Recommendations
  • Provide Linux/macOS alternatives for file extraction (e.g., 'unzip' or 'tar' commands) in the relevant sections.
  • For kubectl installation, include platform-appropriate commands (e.g., 'curl' or package manager instructions for Linux/macOS) instead of only 'winget'.
  • When showing Bash examples, ensure the commands are not Windows-specific (e.g., avoid using Expand-Archive in Bash tabs; use platform-appropriate tools).
  • Clearly indicate which commands are Windows-only and provide parity for other platforms.
  • Consider adding a platform selection tab (Windows, Linux, macOS) for all setup steps that differ by OS.
GitHub Create Pull Request
Azure Arc Onboarding Scripts for Workload Orchestration ...azure-arc/workload-orchestration/onboarding-scripts.md
Medium Priority View Details →
Scanned: 2026-02-08 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation page is heavily biased toward Windows environments. All onboarding scripts are provided as PowerShell (.ps1) scripts, and users are instructed to use PowerShell terminals. The prerequisite steps recommend using 'winget', a Windows-only package manager, to install Azure CLI and kubectl. No Linux/macOS equivalents or instructions are provided, and there are no Bash or shell script examples. This creates friction for Linux/macOS users who wish to onboard workload orchestration resources in Azure Arc.
Recommendations
  • Provide Bash or shell script equivalents for onboarding tasks, or clarify if the scripts are cross-platform.
  • Include Linux/macOS installation instructions for Azure CLI and kubectl (e.g., using apt, yum, brew, or manual download).
  • Mention that PowerShell Core is available on Linux/macOS, and clarify if the .ps1 scripts are compatible with PowerShell Core.
  • Add explicit guidance for Linux/macOS users, including terminal commands and environment setup steps.
  • Consider providing Docker-based or cross-platform onboarding options if possible.
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-02-08 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 almost all CLI/script examples using PowerShell syntax, including backticks for line continuation and Windows-style file paths (e.g., C:\Users\...). There are no Bash or Linux/macOS shell equivalents, and the JSON template contains Windows file paths. The onboarding scripts are referenced as PowerShell (.ps1) only, with no mention of Bash or cross-platform alternatives. This creates friction for Linux/macOS users, who must adapt the examples and scripts themselves.
Recommendations
  • Provide Bash/zsh shell equivalents for all PowerShell CLI examples, using standard Linux/macOS syntax (e.g., line continuation with \ or newlines).
  • Use cross-platform file paths in JSON templates (e.g., /home/user/...), or note that paths should be adapted for the user's OS.
  • Clarify whether onboarding scripts (.ps1) are supported on Linux/macOS (via PowerShell Core), and provide Bash versions if possible.
  • Add explicit notes or sections for Linux/macOS users, highlighting any OS-specific requirements or adaptations.
  • Where possible, show az CLI commands in a cross-platform way, avoiding PowerShell-specific syntax.
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-02-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 and example, with no mention of a Bash, shell, or cross-platform equivalent. The script is named with a .ps1 extension and instructions are given for running it in PowerShell, which is typically associated with Windows environments. There is no guidance for Linux/macOS users, nor any indication if the script can be run with PowerShell Core on non-Windows platforms.
Recommendations
  • Clarify whether the PowerShell script is compatible with PowerShell Core on Linux/macOS.
  • Provide explicit instructions for running the migration script on Linux/macOS, including installation steps for PowerShell if required.
  • If possible, offer a Bash or cross-platform script alternative, or note if only PowerShell is supported.
  • Mention any prerequisites or limitations for non-Windows users.
GitHub Create Pull Request
Azure Arc Troubleshooting for Workload Orchestration ...es/azure-arc/workload-orchestration/troubleshooting.md
Medium Priority View Details →
Scanned: 2026-02-08 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 biased toward PowerShell and Windows-style command usage. Most examples, including Azure CLI, kubectl, and Docker commands, are presented in PowerShell syntax, with no equivalent Bash or Linux shell examples for critical troubleshooting steps. Only in the 'Troubleshoot service groups' section are Bash examples provided alongside PowerShell, but the rest of the document lacks Linux parity. This creates friction for Linux/macOS users, who must adapt Windows-centric instructions to their environments.
Recommendations
  • Provide Bash/Linux shell equivalents for all PowerShell command examples, especially for Azure CLI, kubectl, and Docker commands.
  • Clearly indicate when a command is cross-platform and provide syntax for both Windows (PowerShell) and Linux/macOS (Bash).
  • Avoid using PowerShell-specific constructs (e.g., ConvertTo-Json, Out-File, Base64 encoding via [Convert]) without showing Bash alternatives.
  • Review file encoding instructions to ensure they are relevant for Linux/macOS users (e.g., UTF-8 with BOM is a Windows-specific concern).
  • Add notes or tabs for Linux/macOS users where file paths, environment variables, or command syntax differ.
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-02-05 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 instructions for all major lifecycle tasks (install, upgrade, uninstall, proxy config), but Windows examples and tooling (PowerShell, Control Panel, Msiexec, Group Policy, WSUS, Configuration Manager) are often presented first and in greater detail. The cleanup script for stale resources is provided only in PowerShell, with no Linux shell or Azure CLI equivalent. Windows-specific management patterns (e.g., Group Policy, WSUS) are described at length, while Linux equivalents (e.g., configuration management, package automation) are not mentioned.
Recommendations
  • Provide Azure CLI/bash equivalents for PowerShell-only scripts, especially for resource cleanup.
  • Where possible, present Linux and Windows examples side-by-side or alternate which comes first.
  • Add Linux automation guidance for agent upgrades and removals (e.g., using Ansible, cron, or systemd).
  • Include links or references to Linux-native management tools for package updates and configuration.
  • Clarify when a method is Windows-only and suggest Linux alternatives.
GitHub Create Pull Request
Azure Arc Next steps for cloud-native server management with Azure Arc-enabled servers .../articles/azure-arc/servers/cloud-native/next-steps.md
Medium Priority View Details →
Scanned: 2026-02-05 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page presents examples and scenarios that reference Windows-centric tools and patterns (such as Group Policy Objects and WSUS) before or instead of Linux equivalents. There are no explicit Linux management examples, and Windows tools are mentioned as the default or primary legacy systems. This creates subtle friction for Linux users, who may need to infer how their existing tools fit into the Azure Arc transition.
Recommendations
  • Include examples of legacy Linux management tools (e.g., Ansible, Chef, Puppet, cron jobs) alongside Windows tools when discussing phased adoption and overlap scenarios.
  • Provide explicit Linux onboarding and verification steps, such as mentioning supported Linux distributions and any OS-specific considerations.
  • When listing resource organization or automation examples, clarify that these apply to both Windows and Linux servers, or provide Linux-specific examples where appropriate.
  • Reference Linux equivalents for patching and compliance (e.g., using Azure Update Manager with Linux, mapping Azure Policy to Linux configuration management).
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-02-05 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation page provides troubleshooting guidance for Azure Arc resource bridge, which is a cross-platform solution. However, several examples and troubleshooting steps are presented with a Windows-first bias. PowerShell is used for network troubleshooting and proxy validation, and Windows paths are shown in error messages and instructions before Linux equivalents. Some CLI instructions and troubleshooting steps lack explicit Linux/macOS examples, and Windows-specific tools (such as Remote PowerShell, RDP) are mentioned without Linux alternatives. Linux troubleshooting is only briefly addressed (e.g., glibc version errors), and Linux/macOS users may need to infer how to adapt instructions.
Recommendations
  • Provide Linux/macOS equivalents for all CLI and troubleshooting commands, especially for network and DNS validation (e.g., show both nslookup/ping for Windows and dig/host/ping for Linux).
  • Include Linux/macOS paths and error message formats alongside Windows paths in CLI error examples.
  • When referencing PowerShell or RDP, also mention Linux/macOS alternatives (e.g., SSH, console access).
  • Expand troubleshooting steps for Linux-specific issues (such as glibc errors) and provide more detailed guidance for Linux users.
  • Ensure that all CLI commands are shown with syntax that works on both Windows and Linux shells, or explicitly note any OS-specific differences.
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-02-05 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 VM extensions, ensuring parity in template content. However, all deployment commands and walkthroughs use Azure PowerShell exclusively, with no Azure CLI or Bash examples. PowerShell commands are shown first and only, which may create friction for Linux/macOS users who prefer Bash or Azure CLI. Additionally, file path examples use Windows-style paths (e.g., D:\Azure\Templates\...), and command execution patterns (such as 'powershell -ExecutionPolicy Unrestricted -File ...') are Windows-centric in the Windows custom script extension template.
Recommendations
  • Add Azure CLI deployment examples alongside PowerShell commands, especially for deploying ARM templates.
  • Include Linux/macOS file path examples (e.g., /home/user/Azure/Templates/...) where appropriate.
  • Clarify that both PowerShell and Azure CLI can be used for deployments, and link to CLI documentation.
  • Where custom script execution is shown, provide equivalent Bash/sh examples for Linux.
  • Consider showing CLI/Bash commands before or alongside PowerShell commands to avoid Windows-first impression.
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-02-04 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, several examples and troubleshooting steps are presented with a Windows-first bias. PowerShell is used for network troubleshooting and proxy validation, while equivalent Linux commands (e.g., curl, wget, nslookup, dig) are not provided. Some instructions reference Windows-specific paths or behaviors (e.g., C:\Program Files), and in places, Windows tools or terminology are used before Linux equivalents. There are also sections where only Windows/PowerShell examples are given, and Linux/macOS users are left to infer the appropriate commands.
Recommendations
  • Provide Linux/macOS equivalents for all PowerShell or Windows command-line examples (e.g., curl, wget, dig, nslookup, ping).
  • When referencing file paths or CLI errors, clarify the equivalent locations or error formats for Linux/macOS.
  • Ensure troubleshooting steps are platform-neutral or include both Windows and Linux/macOS instructions side by side.
  • Explicitly mention supported platforms for the Azure CLI and arcappliance extension, and note any platform-specific requirements or limitations.
  • Add notes or links to Linux/macOS proxy configuration and troubleshooting guides where relevant.
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-02-04 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation for `azcmagent connect` generally presents authentication and usage options that apply to both Windows and Linux. However, there are several instances of Windows bias: Windows authentication methods are described first, Windows-specific certificate store options are detailed, and PowerShell tooling (`Get-AzAccessToken`) is mentioned as the primary way to obtain access tokens, with no Linux equivalent provided. Linux/macOS users may need to infer or research equivalent steps for some tasks.
Recommendations
  • When describing authentication methods, present Linux and Windows options in parallel or clarify which are cross-platform.
  • For access token acquisition, provide Linux/macOS equivalents (e.g., using Azure CLI: `az account get-access-token`) alongside PowerShell examples.
  • When discussing certificate-based authentication, clarify Linux certificate storage and access patterns, not just Windows certificate stores.
  • Ensure examples and instructions are not Windows-first unless there is a technical reason.
GitHub Create Pull Request
Azure Arc Next steps for cloud-native server management with Azure Arc-enabled servers .../articles/azure-arc/servers/cloud-native/next-steps.md
Medium Priority View Details →
Scanned: 2026-02-04 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation references Windows-centric management tools (such as Group Policy Objects and WSUS) as examples of legacy/on-premises solutions, and these are mentioned before or instead of Linux equivalents. There are no explicit Linux management tool examples (e.g., Ansible, Chef, or Linux-native patching/compliance solutions), which may make Linux users feel less represented in the transition guidance.
Recommendations
  • Include examples of Linux management tools (e.g., Ansible, Chef, Puppet, or native package managers like apt/yum/dnf) alongside Windows tools when discussing legacy/on-premises management.
  • When describing phased adoption or overlap scenarios, mention how Linux users might continue using their existing tools (such as cron jobs, configuration management systems, or Linux-native compliance solutions) in parallel with Azure services.
  • Provide explicit examples or links for onboarding Linux servers, and clarify that Azure Arc supports both Windows and Linux environments.
  • Ensure that training and operational procedure sections reference Linux command-line tools and workflows (e.g., Bash, SSH, Linux-specific Azure CLI usage) where appropriate.
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-02-04 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 VM extensions, ensuring parity in template content. However, all deployment instructions and command-line examples use Azure PowerShell, with no mention or examples of Azure CLI or Bash commands. Additionally, PowerShell deployment commands are presented first and exclusively, which may create friction for Linux/macOS users who prefer Bash or Azure CLI.
Recommendations
  • Add equivalent Azure CLI deployment commands for ARM template deployments, alongside PowerShell examples.
  • Explicitly state that both Azure PowerShell and Azure CLI can be used for deployments, and link to relevant CLI documentation.
  • Consider providing Bash script examples for Linux users, especially for template deployments.
  • Present PowerShell and CLI examples side-by-side, or alternate which is shown first, to avoid implicit prioritization.
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-02-04 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, with clear sections and examples for each. However, there is a mild bias toward Windows in several areas: Windows examples and instructions are often presented first, PowerShell scripts are featured for tasks like cleaning up stale resources, and Windows-specific tools (Control Panel, Group Policy, Microsoft Update, WSUS, Configuration Manager) receive detailed attention. While Linux parity is generally strong, some automation examples (such as the stale resource cleanup script) are only provided for Windows/PowerShell, and Windows administrative patterns are described in greater depth.
Recommendations
  • Provide equivalent automation scripts for Linux environments (e.g., Bash scripts using Azure CLI or REST API for stale resource cleanup).
  • Alternate the order of Windows and Linux sections or present them in parallel to avoid Windows-first bias.
  • Include references to Linux-native management tools (such as Ansible, systemd, or cron) where appropriate, especially for update and configuration automation.
  • Ensure that all major workflows (install, upgrade, uninstall, cleanup) have Linux examples that match the detail and coverage of Windows instructions.
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-02-03 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 instances of Windows bias: PowerShell is used for network troubleshooting and proxy validation examples, Windows-specific terminology (e.g., 'Remote Desktop Protocol', 'time.windows.com') appears before Linux equivalents, and some CLI troubleshooting steps reference Windows paths or behaviors. Linux-specific troubleshooting (e.g., shell commands, Linux file permissions, or proxy configuration) is rarely shown, and examples for Linux users are missing or less prominent.
Recommendations
  • Provide Linux/macOS equivalents for PowerShell commands, such as using curl, wget, or openssl for network/proxy validation.
  • Include Linux/macOS file system paths and permission troubleshooting steps alongside Windows examples.
  • When referencing system requirements or troubleshooting steps, explicitly mention Linux/macOS scenarios (e.g., how to check glibc version, how to resolve SSH folder permission errors on Linux).
  • Show both Windows and Linux/macOS commands in CLI examples, or clarify which OS each example applies to.
  • Avoid using Windows-specific terminology (like 'Remote Desktop Protocol') without mentioning Linux/macOS alternatives (like SSH or console access).
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-02-03 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page for `azcmagent connect` demonstrates some Windows bias. Windows authentication options (interactive browser login, certificate store usage) are described first and in more detail, and PowerShell tooling (`Get-AzAccessToken`) is referenced for access token acquisition without mentioning Linux/macOS equivalents. Windows certificate store options are explained, but Linux certificate handling is not covered in equivalent detail. Examples and instructions generally do not show Linux-specific shell commands or highlight Linux workflows.
Recommendations
  • Add explicit Linux/macOS examples for authentication flows, especially for certificate-based authentication (e.g., storing and referencing PEM/PFX files on disk).
  • When referencing access token acquisition, include cross-platform methods (e.g., Azure CLI: `az account get-access-token`) alongside PowerShell.
  • Balance the order of authentication options so that Linux-default methods (device code login, file-based certificates) are described first or equally.
  • Clarify Linux/macOS certificate handling, including file permissions, recommended storage locations, and any OS-specific caveats.
  • Where Windows-specific features (like certificate store usage) are described, provide a parallel Linux/macOS section or explicitly state their absence.
GitHub Create Pull Request
← Previous Page 48 of 94 Next →