Azure Arc

926
Total Pages
755
Linux-Friendly Pages
171
Pages with Bias
18.5%
Bias Rate

Bias Trend Over Time

Pages with Bias Issues

432 issues found
Showing 51-75 of 432 flagged pages
Azure Arc Sample - Enable GPU for AKS on Azure Arc ...lob/main/articles/azure-arc/edge-rag/enable-gpu-aks.md
High Priority View Details →
Scanned: 2026-01-10 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 provides only a Windows PowerShell script for enabling GPU on AKS enabled by Azure Arc, relying exclusively on Windows-specific cmdlets and tools (e.g., Get-PnpDevice, pnputil, Restart-Service). There are no Linux or macOS instructions, examples, or tool mentions, making the guidance inaccessible to users running Azure Arc clusters on non-Windows hosts.
Recommendations
  • Add equivalent Linux instructions and sample scripts (e.g., using lspci, lsmod, modprobe, and relevant NVIDIA driver installation commands for Linux).
  • Clearly state OS prerequisites and limitations at the beginning of the article.
  • Provide parity in troubleshooting and validation steps for Linux environments.
  • Include notes or links for macOS users, if relevant, or clarify that macOS is unsupported.
GitHub Create Pull Request
Azure Arc Customer intent: "As a system administrator managing Azure Arc-enabled servers, I want to understand the required endpoints for Extended Security Updates so that I can ensure proper connectivity and compliance during installation and updates." ...azure-arc/servers/includes/esu-network-requirements.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is focused exclusively on Windows Server 2012 and SQL Server 2012, with endpoint descriptions referencing Windows installation packages and no mention of Linux or macOS equivalents. There are no examples, instructions, or endpoint requirements for Linux-based Azure Arc-enabled servers, and the only installation package referenced is for Windows.
Recommendations
  • Include endpoint requirements and installation package details for Linux-based Azure Arc-enabled servers if supported.
  • Clarify whether Extended Security Updates via Azure Arc are available for Linux servers, and if not, explicitly state this limitation.
  • Provide parity in examples and endpoint tables for Linux and macOS where applicable, or add a note explaining platform limitations.
  • If Linux is not supported for ESU, add guidance for Linux users on alternative update and compliance strategies.
GitHub Create Pull Request
Azure Arc REST API Requests for the Run Command on Azure Arc-enabled Servers (Preview) ...ob/main/articles/azure-arc/servers/run-command-rest.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page is heavily biased toward Windows environments. All example scenarios and scripts are for Windows Server, specifically using PowerShell cmdlets (e.g., New-NetFirewallRule). There are no examples for Linux or macOS servers, nor any mention of equivalent Linux commands or shell scripts. The instructions for generating SAS tokens reference PowerShell tools (New-AzStorageBlobSASToken) exclusively, with no mention of Azure CLI or other cross-platform alternatives. The server name and scenario are Windows-specific, and the documentation does not clarify how Linux users should adapt the REST API or scripts for their systems.
Recommendations
  • Add Linux/macOS example scenarios, such as using Bash scripts to configure firewall rules (e.g., using ufw or iptables).
  • Provide sample REST API payloads for Linux servers, including inline Bash scripts and references to .sh files.
  • Include instructions for generating SAS tokens using Azure CLI (az storage blob generate-sas) as an alternative to PowerShell.
  • Clarify which script types and interpreters are supported for Linux servers, and how to specify them in the REST API payload.
  • Mention Linux server compatibility and any differences in Run command behavior or prerequisites.
GitHub Create Pull Request
Azure Arc Recover from accidental deletion of resource bridge VM ...em-center-virtual-machine-manager/disaster-recovery.md
High Priority View Details →
Scanned: 2026-01-10 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 exclusively provides recovery instructions and scripts for Windows environments, specifically using PowerShell. There are no examples, scripts, or guidance for performing the recovery from Linux or macOS systems, nor are cross-platform alternatives mentioned. This creates friction for non-Windows users and implies that Windows is the expected or only supported platform for this operation.
Recommendations
  • Provide equivalent recovery instructions and scripts for Linux/macOS environments, using Bash or cross-platform tools.
  • Explicitly state platform requirements and limitations, if any, and offer guidance for users on non-Windows systems.
  • If the recovery script is Windows-only, consider developing and publishing a cross-platform version.
  • List both Windows and Linux/macOS procedures side-by-side, or indicate which steps are platform-agnostic.
  • Mention prerequisites or dependencies for Linux/macOS users (e.g., required CLI tools, SSH, etc.).
GitHub Create Pull Request
Azure Arc Switch to the new version of Arc-enabled SCVMM ...ual-machine-manager/switch-to-the-new-version-scvmm.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The documentation is heavily focused on Windows environments, specifically System Center Virtual Machine Manager (SCVMM), which is a Windows-only tool. All examples and instructions reference Windows tools and workflows, such as SCVMM and Azure Arc integration with Windows agents. There are no examples, instructions, or mentions of Linux or macOS environments, nor guidance for users managing non-Windows virtual machines.
Recommendations
  • Clarify in the introduction that SCVMM is a Windows-only solution, and provide links or references to equivalent Azure Arc onboarding processes for Linux-based environments.
  • Add a section or note for Linux users, explaining how to manage Linux VMs with Azure Arc, including relevant documentation links.
  • Where agent management is discussed, include instructions or links for disconnecting and uninstalling the Azure Arc agent on Linux machines.
  • Ensure parity in examples and screenshots by including Linux VM scenarios if supported by the platform.
GitHub Create Pull Request
Azure Arc Troubleshoot SCVMM-specific Azure Arc resource bridge deployment errors ...m-center-virtual-machine-manager/troubleshoot-scvmm.md
High Priority View Details →
Scanned: 2026-01-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Powershell Heavy Missing Linux Example
Summary
The documentation is heavily focused on troubleshooting errors specific to SCVMM (System Center Virtual Machine Manager), a Windows-only tool. All error codes and troubleshooting steps reference PowerShell sessions (PSSession), which are native to Windows environments. There are no examples, references, or guidance for Linux or macOS users, nor any mention of equivalent tools or troubleshooting patterns for non-Windows platforms.
Recommendations
  • Clarify early in the documentation that SCVMM is a Windows-only technology and that the troubleshooting steps are specific to Windows environments.
  • If Azure Arc resource bridge supports Linux-based resource managers, provide equivalent troubleshooting guidance for those platforms.
  • Where PowerShell is referenced, offer Bash or CLI alternatives if applicable, or explicitly state that these steps are only relevant for Windows hosts.
  • Add a section outlining platform requirements and limitations, so Linux/macOS users understand the scope.
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-02-10 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 it uses PowerShell cmdlets (Invoke-AksEdgeNodeCommand) to interact with the Linux node, rather than providing native Linux shell commands. This approach assumes the user is operating from a Windows environment with PowerShell, which may not be the case for all Linux administrators. There are no native Linux shell examples for checking or setting sysctl parameters.
Recommendations
  • Provide native Linux shell command examples (e.g., using 'sysctl' directly) for checking and setting 'fs.inotify.max_user_instances', in addition to or instead of PowerShell/Invoke-AksEdgeNodeCommand.
  • Clarify whether the steps are intended to be run from a Windows management host or directly on the Linux node, and offer Linux-native alternatives where possible.
  • If PowerShell is required, explain why and provide guidance for Linux users on how to install and use PowerShell if needed.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides command-line examples using PowerShell syntax (e.g., code blocks labeled as 'powershell'), and does not provide explicit Linux/macOS shell examples or mention cross-platform alternatives. The use of PowerShell code blocks for commands that are not inherently Windows-specific (e.g., kubectl, sqlcmd) may confuse Linux/macOS users and suggests a Windows-first bias. There are no Linux/macOS-specific instructions or clarifications, even though the tasks are Kubernetes- and SQL Server-based and likely to be performed on Linux clusters.
Recommendations
  • Replace 'powershell' code block labels with 'console' or 'bash' where appropriate, especially for kubectl and sqlcmd commands that are cross-platform.
  • Add explicit Linux/macOS shell examples where relevant, or clarify that the commands are the same across platforms.
  • If any commands require PowerShell-specific syntax, provide equivalent bash/zsh examples.
  • Mention that sqlcmd and kubectl are available on all major platforms, and provide installation links for Linux/macOS if not already present.
  • Review for any Windows tool references (e.g., base64 decoding) and suggest Linux/macOS equivalents (e.g., 'base64 --decode').
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-10 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides backup examples using Windows file paths (e.g., C:\Backupfiles\test.bak) and references Windows tools (e.g., Notepad, OneNote) without offering equivalent Linux/macOS examples or instructions. This creates friction for non-Windows users, especially in the backup step and when copying files into pods.
Recommendations
  • Provide equivalent backup examples using Linux/macOS file paths (e.g., /home/user/backup/test.bak) alongside Windows examples.
  • Mention and show how to use common Linux/macOS text editors (e.g., nano, vim, TextEdit) when instructing users to save credentials.
  • Clarify that Visual Studio Code, Azure Storage Explorer, and kubectl are cross-platform, and provide any relevant platform-specific installation links or notes.
  • Instruct users on how to perform backup and file copy operations from Linux/macOS terminals, including example commands.
  • Explicitly state that the process is supported on all major OSes, and highlight any OS-specific considerations.
GitHub Create Pull Request
Azure Arc Rotate user-provided TLS certificate in indirectly connected SQL Managed Instance enabled by Azure Arc ...articles/azure-arc/data/rotate-user-tls-certificate.md
Medium Priority View Details →
Scanned: 2026-02-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation provides both Linux and Windows methods for base64 encoding files, but the Windows example (using certutil) is more detailed and includes additional steps (manual header removal and use of findstr). The Linux example is brief and lacks equivalent troubleshooting or manipulation guidance. Windows tools are mentioned explicitly, while Linux commands are referenced generically. The rest of the documentation uses cross-platform tools (OpenSSL, Azure CLI, kubectl), but the Windows encoding section is more prominent.
Recommendations
  • Expand the Linux base64 example to include guidance on removing headers or manipulating output, if needed, to match the detail provided for Windows.
  • Mention Linux-specific troubleshooting steps or common issues, similar to the Windows section.
  • Present Linux and Windows encoding examples side-by-side for parity.
  • Clarify that Azure CLI and kubectl commands are cross-platform and provide any OS-specific caveats if 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-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 instances of Windows bias: PowerShell is referenced for troubleshooting network issues (e.g., Invoke-WebRequest, Resolve-DnsName), Windows paths are shown in error messages, and Windows tools (RDP, remote PowerShell) are discussed. Linux-specific troubleshooting commands (such as curl, dig, or nslookup) are rarely mentioned, and Linux CLI examples are minimal. Windows tools and patterns are often mentioned first or exclusively, creating friction for Linux/macOS users.
Recommendations
  • For every PowerShell example, provide an equivalent Linux/macOS command (e.g., curl for Invoke-WebRequest, dig/nslookup for Resolve-DnsName).
  • When referencing error messages with Windows paths, clarify that Linux/macOS users may see different paths.
  • Include troubleshooting steps and commands for Linux/macOS management machines (e.g., how to check SSH folder permissions, how to test network connectivity).
  • Mention Linux/macOS remote access methods (e.g., SSH, VNC) alongside Windows RDP.
  • Ensure all CLI commands are platform-neutral and clarify 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-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, uninstallation, and proxy configuration. However, there are several areas where Windows bias is evident: Windows examples and instructions are often presented first, Windows-specific tools (PowerShell, Group Policy, Microsoft Update, WSUS, Configuration Manager) are described in detail, and a cleanup script is only provided in PowerShell with no Linux equivalent. While Linux instructions are present and generally clear, Windows-centric tools and scripting are emphasized, and some automation guidance (e.g., stale resource cleanup) is Windows-only.
Recommendations
  • Provide Linux/bash equivalents for automation scripts, such as the stale resource cleanup PowerShell script.
  • Present Linux and Windows instructions in parallel or alternate the order to avoid 'windows_first' bias.
  • Where Windows tools (e.g., Group Policy, WSUS, Configuration Manager) are discussed, offer Linux alternatives or clarify their absence.
  • Include more examples of using Azure CLI for automation, which is cross-platform.
  • Ensure that Linux-specific troubleshooting and management scenarios are covered with equal depth.
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-10 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 examples. Additionally, PowerShell commands are presented first and as the only method for deploying templates, which may create friction for Linux/macOS users who prefer CLI or Bash. The use of Windows-style file paths in examples (e.g., 'D:\Azure\Templates\...') further reinforces a Windows-first bias.
Recommendations
  • Add Azure CLI deployment command examples alongside PowerShell, e.g., 'az deployment group create --resource-group <resource-group-name> --template-file <template-filename.json> --parameters <parameter-filename.json>'.
  • Include Bash shell examples for Linux/macOS users, especially for template deployment.
  • Use platform-neutral file path examples (e.g., './Azure/Templates/...') or provide both Windows and Linux path formats.
  • Explicitly mention that both Azure PowerShell and Azure CLI can be used for deployment, linking to relevant CLI documentation.
  • Consider reordering or balancing the presentation of deployment methods so that CLI and PowerShell are given equal prominence.
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-10 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 consistently uses PowerShell syntax for Azure CLI commands and provides only PowerShell-based scripts (e.g., .ps1 files) for automation. There are no Bash or Linux shell examples, and no mention of Linux/macOS equivalents for the provided scripts. This creates friction for Linux/macOS users, who must adapt the examples and cannot use the automation scripts as-is.
Recommendations
  • Provide Azure CLI command examples using Bash syntax (e.g., $ az ... or az ...), not just PowerShell.
  • Offer equivalent Bash shell scripts for bulk deployment and workflow deletion, or clearly state if only PowerShell is supported.
  • Explicitly mention cross-platform compatibility for the CLI commands, and note any Windows-only limitations.
  • If the provided .ps1 scripts are Windows-only, suggest alternative approaches or tools for Linux/macOS users.
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-02-10 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 Windows/PowerShell-based recovery script and instructions, with no mention of Linux or cross-platform alternatives. All recovery steps assume the use of a Windows machine and PowerShell, and the provided script is Windows-specific.
Recommendations
  • Provide equivalent recovery instructions and scripts for Linux/macOS environments, using Bash or cross-platform tools such as Azure CLI.
  • Clearly state if the recovery process is only supported on Windows, and explain why (e.g., dependency on SCVMM or Windows-only tooling).
  • If possible, offer a cross-platform version of the disaster recovery script, or document manual steps that Linux/macOS users can follow.
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-10 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation exclusively provides instructions and examples for running a PowerShell script (RGCleanScript.ps1) to clean up Azure Arc workload orchestration resources. There are no examples or guidance for Linux/macOS users, such as using Bash or cross-platform alternatives. The script and its usage are presented as PowerShell-only, with no mention of compatibility or workarounds for non-Windows environments.
Recommendations
  • Clarify whether RGCleanScript.ps1 can be run with PowerShell Core (pwsh) on Linux/macOS, and provide explicit instructions for those platforms if supported.
  • If the script is Windows PowerShell-only, offer a Bash or cross-platform equivalent, or provide guidance for Linux/macOS users on how to achieve the same cleanup tasks using Azure CLI or other tools.
  • Add example commands for Linux/macOS environments, including how to install PowerShell Core if needed.
  • Mention any script dependencies or limitations regarding platform compatibility.
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-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 provides extensive PowerShell-based examples and scripts for diagnostics and onboarding, with file paths and script usage patterns that are Windows-centric. There are no equivalent Bash, shell, or Linux/macOS examples for critical tasks such as onboarding, enabling diagnostics, or collecting logs. The JSON template and script instructions reference Windows file paths and PowerShell scripts exclusively, creating friction for Linux/macOS users.
Recommendations
  • Provide Bash or shell script equivalents for all PowerShell examples, especially for onboarding and diagnostics tasks.
  • Use cross-platform file path conventions in JSON templates and examples, or provide separate Linux/macOS examples.
  • Explicitly note which commands/scripts are cross-platform (e.g., az CLI) and which are Windows-only, and provide alternatives where possible.
  • Add Linux/macOS-specific instructions for running onboarding scripts, handling file paths, and collecting logs.
  • Include examples using Bash or zsh for common tasks, and clarify any OS-specific requirements.
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-10 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 section on extracting ZIP files, the Bash tab uses the Windows-native 'Expand-Archive' command, which is not available on Linux/macOS, and the examples consistently use Windows-style file paths (e.g., 'C:\path\to\archive.zip'). There are no Linux/macOS-specific instructions or examples for these steps, and the documentation assumes a Windows environment for Bash usage. PowerShell examples are provided throughout, but no Linux shell (e.g., native Bash, zsh) examples for Linux/macOS users. This creates friction for non-Windows users, especially in the initial setup steps.
Recommendations
  • Provide Linux/macOS-specific instructions for installing kubectl, such as using 'apt', 'yum', 'brew', or downloading from the official Kubernetes site.
  • For extracting ZIP files, include Linux/macOS Bash commands (e.g., 'unzip archive.zip -d /path/to/workspace') and use POSIX-style file paths in examples.
  • Clarify which commands are platform-specific and offer alternatives for each major OS.
  • Add a note or section indicating supported platforms and any limitations.
  • Review all Bash examples to ensure they are cross-platform or clearly indicate when they are Windows-only.
GitHub Create Pull Request
Azure Arc Troubleshooting for Workload Orchestration ...es/azure-arc/workload-orchestration/troubleshooting.md
Medium Priority View Details →
Scanned: 2026-02-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 biased toward Windows/PowerShell usage. Most command examples are provided only in PowerShell syntax, even for tasks that are cross-platform (e.g., Azure CLI, Docker, kubectl). Bash/Linux equivalents are missing for critical troubleshooting steps, except in the 'service groups' section, where both Bash and PowerShell tabs are provided. This creates friction for Linux/macOS users, especially since many Azure CLI and Kubernetes operations are natively cross-platform.
Recommendations
  • Provide Bash/Linux shell equivalents for all PowerShell command examples, especially for Azure CLI, Docker, and kubectl commands.
  • Ensure that cross-platform tools (e.g., az, kubectl, docker) are demonstrated in both Bash and PowerShell contexts.
  • Where PowerShell-specific syntax is used (e.g., variable assignment, piping, Base64 encoding), offer Bash alternatives (e.g., export, echo, base64).
  • Review the troubleshooting steps to ensure Linux/macOS users can follow along without needing to translate PowerShell syntax.
  • Consider showing Bash examples first or side-by-side with PowerShell to reinforce parity.
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-01-25 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation provides comprehensive guidance for both Windows and Linux users for most lifecycle tasks (install, upgrade, uninstall, proxy configuration) using clear tabbed sections. However, there is a notable bias in the 'Remove stale server resources' section, which only provides a PowerShell script and instructions for Windows/PowerShell users, with no equivalent Bash or cross-platform script for Linux/macOS users. Additionally, some sections (such as manual upgrade/uninstall) provide more detailed, step-by-step instructions for Windows (including Control Panel, Group Policy, and Msiexec usage), whereas Linux sections are more concise. Windows tools and patterns (e.g., Group Policy, WSUS, Configuration Manager) are described in detail, while Linux equivalents (such as automation via Ansible, systemd, or shell scripting) are not mentioned. In some cases, Windows instructions or tools are presented first.
Recommendations
  • Provide a Bash or cross-platform (e.g., Azure CLI) script for identifying and deleting stale/disconnected Arc-enabled servers, or at least reference how Linux/macOS users can perform this task.
  • Where possible, balance the level of detail in Linux sections to match Windows (e.g., include common automation or troubleshooting patterns for Linux environments).
  • When describing automation or update infrastructure (e.g., Group Policy, WSUS), consider mentioning Linux equivalents (such as Ansible, cron jobs, or package manager hooks) or explicitly state if there are no direct equivalents.
  • In sections where Windows instructions are presented first, consider alternating or clarifying that both platforms are equally supported.
  • For PowerShell-heavy examples, provide Azure CLI or REST API equivalents where possible, as these are cross-platform.
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-01-25 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example Windows First
Summary
The documentation provides ARM template examples for both Linux and Windows VM extensions, but all deployment instructions and command-line examples use Azure PowerShell exclusively, with no Azure CLI or Bash examples. The deployment steps and verification instructions are PowerShell-centric, which may create friction for Linux/macOS users who prefer Bash or Azure CLI. Additionally, PowerShell commands are presented first and exclusively in all deployment sections.
Recommendations
  • Add equivalent Azure CLI deployment commands for ARM template deployments, especially for Linux/macOS users.
  • Include Bash script examples for template deployment where appropriate.
  • Explicitly mention that both Azure PowerShell and Azure CLI can be used for deployments, and link to CLI documentation.
  • Consider presenting both PowerShell and CLI examples side-by-side, or alternate which is shown first.
  • Clarify any platform-specific requirements for the deployment tools (e.g., PowerShell Core vs. Windows PowerShell).
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-01-24 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation provides a generally cross-platform overview of Azure Arc-enabled server management, but there is a subtle Windows bias. Windows tools and patterns (e.g., Group Policy Objects, WSUS) are mentioned as examples of existing management solutions, and these are listed before or instead of Linux equivalents. No explicit Linux tools (such as Ansible, Chef, or native Linux patching mechanisms) are referenced, and the examples for phased adoption and overlap scenarios focus on Windows-centric technologies.
Recommendations
  • Include examples of Linux-native management tools (e.g., Ansible, cron jobs, yum/apt for patching) alongside Windows tools in the phased adoption and overlap scenarios.
  • When discussing existing management solutions, mention both Windows and Linux approaches (e.g., "Group Policy Objects (GPOs) or Ansible playbooks for configuration").
  • Provide at least one example of onboarding or managing a Linux server with Azure Arc, or link to relevant Linux-specific guidance.
  • Ensure that examples and scenarios alternate or balance between Windows and Linux, rather than defaulting to Windows-first.
  • Clarify that Azure Arc supports both Windows and Linux servers, and highlight any Linux-specific considerations or resources.
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-01-24 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. The deployment instructions and command-line samples are PowerShell-heavy and do not mention or demonstrate Linux-native tools or workflows. Additionally, PowerShell 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 and walkthroughs alongside PowerShell examples.
  • Explicitly mention that both PowerShell and Azure CLI can be used for ARM template deployments, and link to Azure CLI documentation.
  • Provide example Bash scripts for Linux users, especially for template deployments.
  • Consider ordering examples so that CLI and PowerShell are presented together, or alternate which comes first.
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-01-23 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example
Summary
The documentation provides ARM template examples for both Linux and Windows VM extensions, but all deployment commands and walkthroughs use Azure PowerShell exclusively, with no Azure CLI or Bash examples. This creates friction for Linux/macOS users who may prefer or require CLI/Bash over PowerShell. Additionally, the deployment steps and verification instructions are written with PowerShell as the only method, omitting Linux-native alternatives.
Recommendations
  • Add equivalent Azure CLI deployment commands (e.g., az deployment group create) alongside PowerShell examples.
  • Include Bash script examples for template deployment, especially for Linux users.
  • Explicitly mention that both PowerShell and Azure CLI can be used on any OS, and link to cross-platform installation guides.
  • Where possible, show both PowerShell and CLI commands in parallel for each deployment scenario.
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-01-23 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page subtly favors Windows environments by referencing Windows-specific tools (e.g., Group Policy Objects, WSUS) as examples of existing management solutions and by listing them before or instead of Linux equivalents. There are no explicit Linux or cross-platform management tool examples (such as Ansible, Chef, or cron jobs), nor are there Linux-specific operational patterns mentioned. This may cause friction for Linux-focused users transitioning to Azure Arc.
Recommendations
  • Include Linux-native management tools (e.g., Ansible, Chef, cron, systemd timers) as examples alongside Windows tools like GPOs and WSUS.
  • When discussing phased adoption or overlap scenarios, mention common Linux approaches (e.g., continuing to use Ansible playbooks or shell scripts while validating Azure Update Manager).
  • Provide at least one Linux-specific example or scenario in each major section, especially where operational patterns or legacy tools are discussed.
  • Ensure that cross-platform Azure features (like Azure Policy, Update Manager, and Run Command) are presented with both Windows and Linux usage contexts.
GitHub Create Pull Request
← Previous Page 3 of 18 Next →