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 1001-1025 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-19 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/PowerShell-specific tools (Invoke-AksEdgeNodeCommand) for Linux node configuration without providing native Linux command alternatives. This creates friction for Linux users who may not have access to PowerShell or Windows tools, and omits direct Linux shell examples for sysctl configuration.
Recommendations
  • Provide native Linux shell commands for sysctl configuration, e.g., 'sysctl fs.inotify.max_user_instances' and 'echo "fs.inotify.max_user_instances = 1024" | sudo tee -a /etc/sysctl.conf && sudo sysctl -p'.
  • Clarify whether Invoke-AksEdgeNodeCommand is required, and if so, provide Linux-native alternatives or explain how Linux users can achieve the same result without PowerShell.
  • Ensure all steps for Linux node preparation can be completed using standard Linux tools and commands, not Windows/PowerShell-centric utilities.
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-19 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 PowerShell, SQL Server Profiler) and explicitly lists PowerShell scripting support as a manageability feature. However, it also mentions cross-platform tools like Azure CLI and Visual Studio Code. There are no explicit Linux/macOS examples or mentions of Linux-native tools, and Windows tools are listed without Linux alternatives or parity discussion.
Recommendations
  • Add examples or references for Linux/macOS management tools (e.g., sqlcmd, Azure Data Studio, Bash scripting).
  • Clarify which tools are cross-platform and which are Windows-only.
  • Provide parity guidance for PowerShell scripting, such as Bash or Python alternatives for Linux/macOS users.
  • Explicitly mention Azure CLI usage for common management tasks, with example commands.
  • Consider listing cross-platform tools before Windows-only tools in the Tools section.
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-19 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) and referencing tools like SQL Server Management Studio (SSMS) without mentioning cross-platform alternatives. Linux/macOS equivalents for file paths and backup procedures are not provided, which may hinder non-Windows users.
Recommendations
  • Include Linux/macOS file path examples (e.g., /home/user/backup/test.bak) alongside Windows paths in backup and restore commands.
  • Mention and provide examples using cross-platform tools such as Azure Data Studio for database connections and queries, in addition to SSMS.
  • Clarify that Visual Studio Code and Azure Storage Explorer are cross-platform, and provide installation links or notes for Linux/macOS users.
  • Where commands reference local file paths (e.g., for kubectl cp), show both Windows and Linux/macOS variants.
  • Explicitly state that all steps can be performed from Linux/macOS unless a step is Windows-only, and provide alternatives where necessary.
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-19 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 instructions are more detailed and appear after the Linux example. The Windows section introduces certutil and findstr, but does not mention Linux equivalents for removing headers. The rest of the guide uses cross-platform tools (OpenSSL, Azure CLI, kubectl) and generally favors Linux-first examples, but the Windows-specific encoding instructions are more prominent and lack parity in header removal for Linux.
Recommendations
  • Provide explicit Linux/macOS commands for removing certificate headers (e.g., using grep or sed) to match the Windows findstr example.
  • Clarify that base64 encoding and header removal steps are needed on both platforms, and show both sets of commands side-by-side.
  • Consider mentioning macOS as well, since it is similar to Linux for these operations.
  • Ensure that Windows and Linux instructions are equally detailed and easy to follow.
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-19 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 where Windows-specific tools, patterns, and examples are mentioned before or instead of Linux equivalents. For example, PowerShell is referenced for troubleshooting HTTP2 issues, and Windows paths are shown in error messages. Linux-specific troubleshooting steps (such as using curl, wget, or Linux shell commands) are largely absent, and Linux CLI usage is only briefly mentioned (e.g., glibc error). The guidance for network/proxy/DNS troubleshooting often assumes Windows environments (e.g., Resolve-DnsName, nslookup, ping), and PowerShell is used for HTTP2 validation, with no Linux alternative provided.
Recommendations
  • Add Linux/macOS equivalents for all PowerShell and Windows command examples (e.g., curl for HTTP2 troubleshooting, dig for DNS resolution).
  • Ensure troubleshooting steps reference both Windows and Linux tools where applicable (e.g., show how to check proxy settings/environment variables on Linux).
  • Include Linux-specific error messages and their resolutions, especially for Azure CLI and network troubleshooting.
  • Where Windows paths or tools are referenced, clarify if the guidance applies to Linux/macOS and provide alternate instructions if needed.
  • Review all command examples and ensure Linux/macOS users are equally supported, especially in sections about CLI usage, network diagnostics, and proxy configuration.
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-19 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 and examples for connecting servers to Azure Arc using the azcmagent CLI. While most examples and instructions are platform-neutral, there is a notable Windows bias in several areas: the interactive browser login is described as 'Windows only' and is discussed first; certificate authentication includes detailed instructions for Windows certificate stores but omits Linux/macOS equivalents; access token acquisition references PowerShell's Get-AzAccessToken without mentioning Linux/macOS alternatives. These biases may create friction for Linux/macOS users, though most features are available cross-platform.
Recommendations
  • Present authentication options in a platform-neutral order, or explicitly note Linux/macOS alternatives alongside Windows-specific instructions.
  • For certificate authentication, add guidance for Linux/macOS users (e.g., storing certificates in files, using PEM/PFX formats, relevant file permissions).
  • When referencing access token acquisition, include Azure CLI (az account get-access-token) and other cross-platform methods, not just PowerShell.
  • Where Windows-specific tools or stores are mentioned, provide equivalent Linux/macOS instructions or clarify if no equivalent exists.
  • Consider adding explicit Linux/macOS examples in the 'Examples' section, such as using shell commands for hostname or certificate paths.
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-19 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides deployment instructions exclusively using Azure PowerShell commands, with no Azure CLI or Bash examples. All deployment steps and code blocks use PowerShell syntax, which may create friction for Linux/macOS users who prefer Bash or Azure CLI. Additionally, PowerShell is presented as the primary (and only) method for deploying ARM templates, even though Azure CLI is cross-platform and commonly used on Linux/macOS. The documentation does provide parity in ARM template examples for both Linux and Windows extensions, but the deployment tooling is Windows-centric.
Recommendations
  • Add Azure CLI deployment examples alongside PowerShell for all deployment steps, e.g., using 'az deployment group create'.
  • Mention that Azure CLI is cross-platform and suitable for Linux/macOS users.
  • Consider showing Bash script examples for template deployment where appropriate.
  • Clarify that PowerShell is not required and that users can use their preferred tooling.
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-19 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 recovery instructions for the Azure Arc resource bridge VM using a Windows-based PowerShell script. There are no examples or guidance for Linux/macOS users, nor are cross-platform tools or alternatives mentioned. The script provided is Windows-specific, and the section is titled 'Recover Arc resource bridge from a Windows machine,' with no equivalent Linux/macOS section.
Recommendations
  • Provide equivalent recovery instructions for Linux/macOS users, including Bash or Python scripts.
  • If the recovery process is fundamentally Windows-only, clarify this limitation explicitly in the prerequisites.
  • Mention any cross-platform alternatives or explain why only Windows is supported.
  • Add a note about the lack of Linux/macOS support and suggest workarounds if possible (e.g., running the script in a Windows VM or container).
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-02-19 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page provides multiple methods for installing Arc agents at scale for VMware VMs, but the primary automation script is PowerShell-based and references Windows Task Scheduler for cron jobs. Windows tools and patterns (PowerShell, Task Scheduler) are mentioned exclusively or before Linux equivalents, and Linux-specific automation guidance is minimal. While out-of-band methods mention Ansible playbooks (Linux-friendly), the main scripted method and examples are Windows-centric.
Recommendations
  • Provide a Bash or Python version of the automation script for Linux/macOS users, or clarify if the script is cross-platform.
  • Include instructions for running the automation script as a cron job on Linux (using 'crontab') alongside the Windows Task Scheduler example.
  • Offer explicit Linux/macOS terminal usage examples for script execution, not just PowerShell.
  • Ensure parity in prerequisites and troubleshooting for both Windows and Linux environments.
  • Highlight Ansible playbook usage with a sample for Linux users, and link to relevant Linux onboarding documentation.
GitHub Create Pull Request
Azure Arc Perform disaster recovery operations ...mware-vsphere/recover-from-resource-bridge-deletion.md
Medium Priority View Details →
Scanned: 2026-02-19 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page provides only PowerShell examples and references a script with a .ps1 extension, which is Windows/PowerShell-specific. There are no Bash or Linux/macOS shell examples, nor any mention of how to run the onboarding script on Linux or macOS. The instructions assume the use of Windows tools and editors, creating friction for Linux/macOS users who may need to adapt the process.
Recommendations
  • Provide equivalent Bash or shell script examples for Linux/macOS users, or clarify if the onboarding script is cross-platform.
  • Explicitly state platform requirements for the onboarding script and offer guidance for Linux/macOS environments (e.g., using PowerShell Core, prerequisites, or alternative steps).
  • If the onboarding script is PowerShell-only, recommend using PowerShell Core (pwsh) and provide instructions for installing and running it on Linux/macOS.
  • Add notes about editing scripts on Linux/macOS, including compatible editors and file path conventions.
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-02-19 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Windows First Missing Linux Example
Summary
The documentation provides detailed instructions and examples for Windows users, particularly when running the deboarding script, with explicit PowerShell commands and notes for Windows environments. There is no equivalent Linux/macOS example or guidance for running the script, and Windows instructions are presented first and in greater detail. This creates friction for Linux/macOS users who may need to adapt the process themselves.
Recommendations
  • Add explicit instructions and examples for running the deboarding script on Linux/macOS, including shell commands and prerequisites.
  • Clarify whether the deboarding script is cross-platform (e.g., if it can be run with PowerShell Core on Linux/macOS or if a Bash version exists).
  • Present Windows and Linux/macOS instructions in parallel sections, or clarify platform limitations early in the document.
  • Include troubleshooting tips for Linux/macOS users, such as handling execution policies or script permissions.
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-19 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy Windows First 🔧 Windows Tools Missing Linux Example
Summary
The documentation page provides nearly all CLI/script examples in PowerShell syntax, uses Windows-style file paths in JSON templates, and references PowerShell scripts for orchestration. There are no Bash or Linux/macOS shell equivalents, and Windows-specific conventions (e.g., backslashes, drive letters) are used throughout. This creates friction for Linux/macOS users, who must adapt commands and paths manually.
Recommendations
  • Provide Bash/zsh/Linux/macOS shell equivalents for all PowerShell script examples, especially for az CLI commands.
  • Use platform-neutral file path examples in JSON templates (e.g., /home/user/config.yaml instead of C:\Users\... or E:\...).
  • Clearly indicate when a script is Windows-only or provide cross-platform alternatives.
  • Add notes or links to Linux/macOS onboarding guides for Azure Arc and workload orchestration.
  • Where possible, use az CLI syntax that works identically on all platforms, and avoid PowerShell-specific line continuations (`) in examples.
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-19 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 'winget', a Windows-only tool, with no Linux/macOS alternative. In the section on extracting ZIP files, the Bash tab uses 'Expand-Archive', which is a PowerShell/Windows command, not a standard Bash/Linux tool. Throughout, Windows-centric tools and patterns are presented first or exclusively, and Linux/macOS equivalents are missing or unclear. The PowerShell and Bash tabs often use Windows paths (e.g., 'C:\path\to\archive.zip') and commands that are not portable to Linux/macOS.
Recommendations
  • Provide Linux/macOS-specific instructions for installing kubectl (e.g., using 'curl', 'apt', 'brew', or direct download).
  • For extracting ZIP files, use standard Bash/Linux commands like 'unzip' or 'tar', and provide examples with Linux-style paths.
  • Ensure Bash examples use cross-platform commands and paths, and clarify when a command is Windows-only.
  • Add explicit notes or tabs for macOS where relevant, especially for installation steps.
  • Review all Bash sections to ensure they are valid for Linux/macOS users, not just Windows users running Bash or PowerShell.
GitHub Create Pull Request
Azure Arc Troubleshooting for Workload Orchestration ...es/azure-arc/workload-orchestration/troubleshooting.md
Medium Priority View Details →
Scanned: 2026-02-19 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). Linux/Bash equivalents are missing for critical troubleshooting steps, except in the 'Troubleshoot service groups' section, which offers both Bash and PowerShell tabs. This creates friction for Linux/macOS users, who must translate PowerShell commands themselves.
Recommendations
  • Provide Bash/Linux equivalents for all Azure CLI, Docker, and kubectl commands.
  • Use cross-platform syntax (e.g., az CLI, kubectl, docker) in examples, and avoid PowerShell-specific constructs unless required.
  • Clearly indicate when a command is Windows-only or provide alternative instructions for Linux/macOS.
  • For scripting tasks (e.g., Base64 encoding, JSON file creation), offer both PowerShell and Bash methods.
  • Review and update troubleshooting steps to ensure Linux/macOS users can follow along without needing to translate PowerShell code.
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-18 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation provides recovery instructions exclusively for Windows machines, using a PowerShell script and Windows-specific tooling. No Linux/macOS examples, scripts, or guidance are provided, and the recovery workflow is described only in the context of Windows.
Recommendations
  • Provide equivalent recovery instructions for Linux/macOS users, including Bash or Python scripts.
  • Clarify whether the recovery process can be performed from non-Windows platforms, and if not, explain the limitation.
  • If the PowerShell script is cross-platform (PowerShell Core), indicate compatibility and provide usage examples for Linux/macOS.
  • Offer guidance on prerequisites and connectivity checks for Linux/macOS environments.
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-18 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 script for migration and instructs users to run it in PowerShell, with no mention of Bash, Linux, or cross-platform alternatives. This creates friction for Linux/macOS users, as PowerShell is not natively available and the script may not run without additional setup.
Recommendations
  • Provide a Bash or cross-platform script for migration, or clarify if PowerShell Core (pwsh) is supported on Linux/macOS.
  • Explicitly mention how Linux/macOS users can run the migration (e.g., using PowerShell Core, prerequisites, or alternative steps).
  • Add examples or instructions for Linux/macOS environments, including any required dependencies.
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-18 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 introduces Windows-centric tools and patterns (Invoke-AksEdgeNodeCommand) for Linux configuration steps. It lacks direct Linux-native command examples (e.g., using SSH or running sysctl locally), and relies on PowerShell/Windows tooling to manage Linux nodes, which may not be available or familiar to Linux/macOS users.
Recommendations
  • Provide native Linux command-line examples for sysctl configuration, such as SSH-ing into the node and running 'sysctl' and editing '/etc/sysctl.conf' directly.
  • Clarify whether Invoke-AksEdgeNodeCommand is required or if standard Linux administration methods can be used.
  • Add guidance for Linux/macOS users who may not have access to Windows tools or PowerShell.
  • Ensure all steps can be completed using Linux-native tools and document those options explicitly.
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-02-18 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 links for client tools across Windows, Linux, and macOS, but Windows links are often listed first and some instructions (e.g., for curl and kubectl) reference Windows-specific behaviors and PowerShell. Linux installation instructions are less explicit, sometimes only mentioning 'install curl package' without a link or example. There is also a note about using cmd.exe instead of PowerShell for curl on Windows, but no equivalent Linux/macOS guidance.
Recommendations
  • List Linux and macOS installation links before or alongside Windows links to avoid Windows-first bias.
  • Provide explicit Linux/macOS installation instructions or links for all tools, not just 'install curl package'.
  • Add Linux/macOS-specific notes where Windows-specific behaviors are mentioned (e.g., clarify curl usage differences on Linux/macOS).
  • Ensure parity in guidance for verifying tool versions and installation steps across all platforms.
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-18 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First
Summary
The documentation page lists several Windows-centric tools (SSMS, SQL Server Data Tools, SQL Server Profiler, SQL Server PowerShell) and explicitly mentions PowerShell scripting support as a manageability feature. While Azure CLI and Visual Studio Code are included, Windows tools are more prominent and listed first in several places. There are no Linux-specific examples or tools mentioned, and PowerShell is referenced as a scripting option without mention of Bash or cross-platform alternatives.
Recommendations
  • Add examples or mention of Linux-compatible tools such as Azure Data Studio, Bash scripting, or cross-platform SQL utilities.
  • Clarify that PowerShell scripting support is available on Linux via PowerShell Core, or provide Bash/CLI alternatives for scripting tasks.
  • Balance tool lists by including cross-platform or Linux-native tools alongside Windows tools, and avoid listing Windows tools first unless they are the only option.
  • Where possible, provide links or guidance for Linux/macOS users to achieve similar manageability and scripting tasks.
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-18 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) and referencing Windows tools like SQL Server Management Studio (SSMS) and Azure Storage Explorer. Linux/macOS equivalents or alternative commands are not provided, and Windows paths are shown first or exclusively in backup/restore examples. This creates friction for Linux/macOS users who may need to adapt instructions for their environment.
Recommendations
  • Include Linux/macOS file path examples (e.g., /home/user/Backupfiles/test.bak) alongside Windows paths in backup/restore commands.
  • Mention and provide instructions for Linux-compatible tools (e.g., Azure CLI, azcopy, or cross-platform alternatives to Azure Storage Explorer and SSMS).
  • Add notes or sections clarifying how to perform each step on Linux/macOS, especially for connecting to SQL Server and handling backup files.
  • When showing commands (e.g., kubectl cp), provide both Windows and Linux/macOS source file path examples.
  • Explicitly state that Visual Studio Code and Azure Storage Explorer are cross-platform, and provide installation links for Linux/macOS.
GitHub Create Pull Request
Azure Arc Azure Arc resource bridge system requirements ...icles/azure-arc/resource-bridge/system-requirements.md
Medium Priority View Details →
Scanned: 2026-02-18 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Missing Linux Example Windows First
Summary
The documentation page for Azure Arc resource bridge system requirements references Azure CLI as the primary management tool and provides links to Windows-specific Azure CLI installation instructions. It does not mention Linux or macOS management machine requirements, nor does it provide parity for CLI installation or usage examples on those platforms. The examples and instructions are Windows-centric, with no explicit guidance for Linux/macOS users.
Recommendations
  • Add explicit guidance for Linux and macOS users, including links to Azure CLI installation instructions for those platforms.
  • Clarify that the management machine can be Windows, Linux, or macOS, and provide minimum requirements for each.
  • Provide example CLI commands and file paths for Linux/macOS environments alongside Windows examples.
  • Ensure that references to Azure CLI are not limited to Windows-specific tabs or links.
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-18 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides comprehensive guidance for both Windows and Linux users, with clear sections and examples for each platform. However, there is a mild Windows bias: Windows instructions and tools (such as PowerShell, Group Policy, WSUS, and Microsoft Update) are often presented first, and some advanced automation examples (like the cleanup script) are only provided in PowerShell. Windows-specific tools and patterns are described in greater detail, while Linux instructions are generally limited to package manager commands and lack comparable scripting or automation examples.
Recommendations
  • Provide equivalent automation scripts for Linux users (e.g., Bash scripts for stale resource cleanup using Azure CLI).
  • Ensure Linux examples are presented alongside Windows examples, not always after them.
  • Expand Linux sections to include advanced management scenarios, such as using cron jobs or systemd for agent maintenance.
  • Where possible, reference cross-platform tools (e.g., Azure CLI) before platform-specific tools (e.g., PowerShell).
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-18 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 DNS resolution examples, Windows-specific tools (like Remote PowerShell and RDP) are referenced, and Windows terminology (e.g., 'management machine', 'workstation', 'console session') is used. Linux equivalents (such as Bash or Linux CLI commands) are not provided alongside PowerShell examples, and Windows tools are mentioned first or exclusively in some sections. While there is some Linux-specific troubleshooting (GLIBC errors), overall, Linux/macOS users may experience friction due to missing parity in examples and tool references.
Recommendations
  • Provide Linux/macOS equivalents for PowerShell commands (e.g., use dig, nslookup, curl, etc.) wherever PowerShell is used.
  • Include Bash or Linux CLI examples alongside Windows/PowerShell examples for network and DNS troubleshooting.
  • Mention Linux remote access tools (e.g., SSH, console access) alongside Windows tools like RDP.
  • Clarify terminology to be platform-neutral (e.g., 'management machine' instead of 'workstation').
  • Ensure all CLI commands (az arcappliance, etc.) are shown to work on both Windows and Linux, and note any OS-specific requirements.
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-18 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 walkthroughs 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 template examples themselves are balanced, but the operational guidance is Windows-centric.
Recommendations
  • Add Azure CLI deployment examples alongside PowerShell commands, e.g., 'az deployment group create --resource-group <resource-group-name> --template-file <template-filename.json> --parameters <parameter-filename.json>'.
  • Explicitly mention that both Azure PowerShell and Azure CLI can be used for deploying ARM templates, and link to relevant CLI documentation.
  • Consider showing CLI/Bash examples before or alongside PowerShell, or clarify that PowerShell is cross-platform.
  • Add a note about PowerShell Core being available on Linux/macOS, if PowerShell is preferred.
GitHub Create Pull Request
Azure Arc Perform disaster recovery operations ...mware-vsphere/recover-from-resource-bridge-deletion.md
Medium Priority View Details →
Scanned: 2026-02-18 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page provides disaster recovery instructions for Azure Arc resource bridge in VMware vSphere environments, but all script examples and operational guidance are exclusively in PowerShell (.ps1) format. There are no Bash, shell, or Linux/macOS-compatible script examples or instructions, and the onboarding script is referenced only as a PowerShell script. This creates friction for Linux/macOS users who may not have access to PowerShell or prefer native shell environments.
Recommendations
  • Provide equivalent Bash or shell script examples for onboarding and recovery operations, or clarify if the onboarding script is cross-platform.
  • Explicitly state platform requirements for the onboarding script (e.g., if PowerShell Core is supported on Linux/macOS, mention this and provide installation guidance).
  • Include instructions for running the onboarding script on Linux/macOS, or offer a downloadable cross-platform version.
  • If the onboarding script is Windows-only, consider developing and publishing a Linux/macOS-compatible version.
GitHub Create Pull Request
← Previous Page 41 of 94 Next →