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 376-400 of 432 flagged pages
Azure Arc Simplify network configuration requirements with Azure Arc gateway (preview) ...zure-arc/kubernetes/arc-gateway-simplify-networking.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all major tasks, but consistently lists Azure PowerShell examples immediately after Azure CLI, and sometimes with more detail. There is a slight Windows bias in the ordering and inclusion of PowerShell, which is a Windows-centric tool, but Linux/macOS users are not blocked from completing any tasks since Azure CLI is cross-platform and all required steps are covered. No Linux-specific tools or patterns (e.g., bash scripts, Linux package managers) are mentioned, but the use of environment variables and CLI commands is compatible with Linux/macOS.
Recommendations
  • Explicitly state that Azure CLI commands are cross-platform and suitable for Linux/macOS.
  • Add Linux/macOS-specific notes or examples where environment variable syntax differs (e.g., export vs. set).
  • Consider listing Azure CLI examples first, and clarify that PowerShell is primarily for Windows users.
  • Include troubleshooting tips for Linux/macOS environments (e.g., proxy configuration nuances, certificate stores).
GitHub Create Pull Request
Azure Arc Troubleshoot extension issues for Azure Arc-enabled Kubernetes clusters ...les/azure-arc/kubernetes/extensions-troubleshooting.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation demonstrates mild Windows bias by referencing Azure CLI commands and Azure-specific features (such as AKS-ExtensionManager and Azure Policy Gatekeeper) that are primarily managed from Windows environments or with Windows-centric tooling. However, most troubleshooting steps use cross-platform Kubernetes tools (kubectl, helm, jq, bash), and Linux-specific issues (Oracle Linux/RHEL) are addressed. There are no PowerShell-only examples, and Linux/macOS users can follow all procedures.
Recommendations
  • Explicitly note that Azure CLI is cross-platform and provide installation links for Linux/macOS.
  • Where Azure Policy Gatekeeper or AKS-ExtensionManager is referenced, clarify how Linux/macOS users can manage these features (e.g., via Azure CLI, portal, or REST API).
  • Add examples or notes for using Azure CLI on Linux/macOS, especially for commands that may behave differently or require different authentication.
  • Ensure that any references to Windows-specific tools or patterns are accompanied by Linux/macOS equivalents or clarifications.
  • Continue to provide Linux troubleshooting steps as done for Oracle Linux/RHEL.
GitHub Create Pull Request
Azure Arc Quickstart: Connect an existing Kubernetes cluster to Azure Arc ...les/azure-arc/kubernetes/quickstart-connect-cluster.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides both Azure CLI and Azure PowerShell examples throughout, but PowerShell is a Windows-centric tool and is presented as an equal alternative to Azure CLI. In several places, instructions for creating a Kubernetes cluster mention Docker for Windows before Docker for Mac, and PowerShell environment variable examples are given for proxy configuration. There is no explicit Linux shell example for Azure CLI environment variables (e.g., bash vs. PowerShell), and the documentation assumes familiarity with Windows/PowerShell patterns. However, the Azure CLI examples are cross-platform and the instructions do mention Docker for Mac and Linux-compatible tools like KIND and Cluster API.
Recommendations
  • Add explicit Linux/macOS shell examples (e.g., bash) for environment variable setup and other commands where PowerShell syntax is shown.
  • When listing options for creating clusters, mention Linux-native options (e.g., KIND, Minikube) first, or provide parity in order.
  • Clarify that Azure CLI is fully cross-platform and recommend it as the default for Linux/macOS users.
  • Where PowerShell is shown for proxy configuration, also show the equivalent bash export commands.
  • Consider adding a table or section summarizing platform-specific steps for Windows, Linux, and macOS.
  • Avoid referring to Docker for Windows before Docker for Mac or Linux unless there is a technical reason.
GitHub Create Pull Request
Azure Arc Azure Arc resource bridge security overview ...rticles/azure-arc/resource-bridge/security-overview.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation mentions retrieving Azure activity logs using PowerShell and Azure CLI, listing PowerShell first. This subtly prioritizes Windows tooling and patterns, though Azure CLI is cross-platform. No explicit Linux/macOS examples or tools are provided, and PowerShell is referenced without noting its availability on Linux/macOS.
Recommendations
  • Explicitly state that both PowerShell and Azure CLI are available on Linux/macOS, and provide example commands for each platform.
  • When listing tools, alternate the order or clarify cross-platform support to avoid implying Windows-first usage.
  • Include Linux/macOS-specific guidance or screenshots where relevant, especially for command-line tasks.
  • Add a note or section highlighting parity and any platform-specific considerations.
GitHub Create Pull Request
Azure Arc Azure Arc resource bridge system requirements ...icles/azure-arc/resource-bridge/system-requirements.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page for Azure Arc resource bridge system requirements shows mild Windows bias. Azure CLI installation links and references default to Windows, and there are no explicit examples or instructions for Linux/macOS users regarding CLI installation, command usage, or file paths. All CLI examples and management machine requirements assume a Windows environment, with no mention of Linux or macOS equivalents.
Recommendations
  • Include explicit instructions and links for installing Azure CLI on Linux and macOS, not just Windows.
  • Provide examples of CLI usage and file paths for Linux/macOS environments.
  • Clarify that the management machine can be Linux, macOS, or Windows, and list any OS-specific requirements or caveats.
  • When referencing CLI commands, note any differences in syntax or behavior across platforms.
  • Ensure parity in troubleshooting and maintenance instructions for Linux/macOS users.
GitHub Create Pull Request
Azure Arc Azure Arc overview ...nagement-docs/blob/main/articles/azure-arc/overview.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page demonstrates a mild Windows bias by mentioning Windows-specific management tools (System Center Virtual Machine Manager, VMware vSphere) and referencing Windows and Linux together, but listing Windows tools first and providing more detail about Windows-centric environments. There are no explicit PowerShell-only examples or missing Linux examples, but the focus on Windows management platforms and tools is more prominent than Linux equivalents.
Recommendations
  • Add explicit references to Linux-native management tools or platforms where relevant (e.g., mention integration with Ansible, Cockpit, or other Linux VM management solutions).
  • Ensure examples and scenarios highlight Linux environments equally, including lifecycle operations and automation.
  • When listing supported environments, alternate or balance the order of Windows and Linux mentions.
  • Provide links to documentation or guides specifically for Linux VM management under Azure Arc.
GitHub Create Pull Request
Azure Arc Archive for What's new with Azure Connected Machine agent ...icles/azure-arc/servers/agent-release-notes-archive.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation consistently lists Windows download links before Linux, and Windows-specific tools (PowerShell, MSI installer, Windows Event Logs, Windows cert store) are mentioned prominently. Some features and enhancements are described with a Windows focus (e.g., GUI installer, Windows-specific logging, dependency upgrades for PowerShell/.NET). Linux features are present and called out, but Windows terminology and tools are often referenced first or exclusively, and PowerShell upgrades are highlighted as major changes.
Recommendations
  • Alternate the order of Windows and Linux download links or present them together to avoid Windows-first perception.
  • Ensure Linux equivalents are mentioned alongside Windows tools (e.g., if referencing Windows Event Logs, also mention Linux journalctl).
  • Highlight Linux-specific enhancements and tools with equal prominence as Windows features.
  • Avoid referencing Windows tools (PowerShell, MSI, cert store) without noting Linux equivalents or alternatives.
  • Where possible, provide parity in example commands, troubleshooting steps, and tool references for both platforms.
GitHub Create Pull Request
Azure Arc CLI reference for `azcmagent check` ...lob/main/articles/azure-arc/servers/azcmagent-check.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
🔧 Windows Tools Windows First
Summary
The documentation page for `azcmagent check` shows mild Windows bias. The only extended use case explicitly mentioned is 'Windows Server Pay-as-you-go', and the link provided is to Windows-specific documentation. No Linux/macOS-specific examples, flags, or use cases are discussed, and the only extension example is for SQL Server (primarily a Windows workload). However, the command syntax and examples themselves are cross-platform and do not use Windows-only tools or shell syntax.
Recommendations
  • Add examples or references for Linux/macOS-specific use cases, such as connectivity checks for Linux-based Arc workloads or extensions.
  • Include links to Linux/macOS documentation where relevant, not just Windows Server.
  • Mention that the command works identically on Linux/macOS, and clarify any platform-specific behaviors if they exist.
  • Provide extension examples for workloads commonly found on Linux (e.g., PostgreSQL, custom scripts).
GitHub Create Pull Request
Azure Arc CLI reference for `azcmagent connect` ...b/main/articles/azure-arc/servers/azcmagent-connect.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page exhibits mild Windows bias by mentioning Windows-specific authentication methods first and referencing Windows-only interactive browser login as the default. Additionally, the only explicit tool for obtaining an access token is PowerShell's Get-AzAccessToken, with no Linux/macOS equivalent shown. However, most examples and instructions are cross-platform, and Linux authentication flows are described.
Recommendations
  • Present authentication options in a platform-neutral order or explicitly call out Linux/macOS flows first where appropriate.
  • Add Linux/macOS equivalents for obtaining access tokens (e.g., using Azure CLI: 'az account get-access-token').
  • Clarify which examples and flags are valid for Linux/macOS, and provide explicit Linux/macOS command snippets where platform differences exist.
  • Where a method is Windows-only, immediately follow with the Linux/macOS alternative in the same section.
GitHub Create Pull Request
Azure Arc azcmagent CLI reference ...docs/blob/main/articles/azure-arc/servers/azcmagent.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation lists the Windows installation path and PATH update instructions before the Linux equivalent, but otherwise provides parity in information and examples for both platforms. No PowerShell-heavy content or exclusive Windows tools are present.
Recommendations
  • Present installation paths for Windows and Linux in parallel or alternate which is listed first.
  • Explicitly mention if any commands or flags differ on Linux/macOS, or confirm full parity.
  • Add troubleshooting notes for Linux/macOS environments if relevant (e.g., PATH issues, permissions).
GitHub Create Pull Request
Azure Arc Enable VM extensions to Arc-enabled servers from the Azure portal ...icles/azure-arc/servers/manage-vm-extensions-portal.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation generally presents a neutral, portal-centric workflow applicable to both Linux and Windows Arc-enabled servers. However, in the extension configuration example, only Windows-specific details (proxy for Azure Monitor agent for Windows) are mentioned, with no equivalent Linux example. Windows is referenced first in the extension configuration context, which may subtly prioritize Windows scenarios.
Recommendations
  • Include configuration examples for both Windows and Linux extensions, such as proxy settings for the Azure Monitor agent on Linux.
  • When mentioning extension-specific configuration, provide parity by referencing Linux scenarios alongside Windows.
  • Ensure that screenshots and step-by-step instructions explicitly note any OS-specific differences or requirements.
  • Review the ordering of OS mentions to avoid consistently listing Windows before Linux.
GitHub Create Pull Request
Azure Arc VM Extension Management with Azure Arc-Enabled Servers ...ain/articles/azure-arc/servers/manage-vm-extensions.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation presents Windows VM extensions before Linux extensions, listing a larger number of Windows-specific extensions and providing more detailed links for Windows scenarios. However, Linux extensions are also covered in a dedicated section with parity for core functionality. No examples or instructions are shown that are exclusive to Windows, and both OSes are referenced in deployment methods (CLI, PowerShell, portal, ARM templates). There is no evidence of missing Linux examples or exclusive use of Windows tools.
Recommendations
  • Present Windows and Linux extension tables side-by-side or alternate their order to avoid Windows-first perception.
  • Ensure that the number and detail of Linux extension entries matches those for Windows where possible.
  • Add explicit cross-references between Windows and Linux extension documentation for users managing both platforms.
  • Include a brief statement at the start clarifying that all extension management features are available for both Windows and Linux, to reinforce parity.
GitHub Create Pull Request
Azure Arc Connect hybrid machines to Azure using a deployment script ...blob/main/articles/azure-arc/servers/onboard-portal.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page presents Windows installation and validation steps before Linux, with detailed usage of Windows-specific tools (msiexec, PowerShell) and command-line examples. PowerShell is emphasized for scripted onboarding, and Windows installer options are explained in depth. Linux instructions are provided and reasonably complete, but appear after Windows, and some sections (e.g., troubleshooting logs, installer options) are more detailed for Windows.
Recommendations
  • Present Linux and Windows instructions in parallel sections, or alternate which OS is described first.
  • Provide equally detailed Linux troubleshooting guidance, including log locations and common errors.
  • Include Linux equivalents for Windows installer options and environment variable configuration (e.g., using export or systemd for proxy settings).
  • Offer Bash script examples for Linux onboarding, matching the PowerShell detail for Windows.
  • Reference Linux package manager commands (apt, yum, zypper) for manual installation, similar to msiexec for Windows.
GitHub Create Pull Request
Azure Arc External Validation for Workload Orchestration ...zure-arc/workload-orchestration/external-validation.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation provides both Bash and PowerShell examples for all CLI commands, ensuring that both Linux/macOS and Windows users are supported. However, PowerShell examples are consistently presented alongside Bash, and in some sections, PowerShell appears before Bash, which may subtly prioritize Windows users. There are no examples or references to Windows-only tools, and all instructions are based on the cross-platform Azure CLI. No Linux-specific tools or patterns are omitted, but the documentation does not mention macOS or Linux environments explicitly, nor does it provide troubleshooting or environment setup guidance for those platforms.
Recommendations
  • Ensure Bash examples are consistently presented before PowerShell to signal Linux/macOS parity.
  • Explicitly mention that all CLI commands work on Linux, macOS, and Windows, and provide links to Azure CLI installation guides for each OS.
  • Add a brief note or section on environment setup for Linux/macOS users, including common troubleshooting tips.
  • Consider including sample outputs or screenshots from Linux/macOS terminals in addition to Windows/PowerShell where applicable.
GitHub Create Pull Request
Azure Arc Staging Resources Before Deployment ...icles/azure-arc/workload-orchestration/how-to-stage.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides both Bash and PowerShell examples for all major steps, ensuring parity for Linux/macOS and Windows users. However, there are subtle signs of Windows bias: PowerShell examples are always present and sometimes shown first in certain sections (e.g., the order of tabs), and some commands (like base64 encoding) are shown in PowerShell but not in Bash. Additionally, the use of Azure Portal and ARMClient for status checks may be more familiar to Windows users. There are no sections that are Windows-only, and Linux/macOS users can complete all tasks, but minor friction exists.
Recommendations
  • Ensure Bash (Linux/macOS) examples are always shown first or equally prioritized in tab order and narrative.
  • Where PowerShell-specific commands are given (e.g., base64 encoding), always provide the Bash/Linux equivalent.
  • Clarify that Azure CLI commands work identically on Linux/macOS and Windows, and note any OS-specific nuances.
  • Where tools like ARMClient are used in PowerShell, suggest equivalent curl or REST API usage for Bash users.
  • Add explicit notes or links for Linux/macOS users regarding file encoding (UTF-8/BOM) and editors.
GitHub Create Pull Request
Azure Arc Use Azure Private Link to Connect Servers to Azure Arc by Using a Private Endpoint ...in/articles/azure-arc/servers/private-link-security.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools Missing Linux Example
Summary
The documentation generally maintains OS parity, but there are several instances of Windows bias. Windows examples and terminology (such as Windows Admin Center, C:\Windows\System32\drivers\etc\hosts) are presented before Linux equivalents, and screenshots are Windows-centric. Windows-specific tools and patterns (Windows Admin Center, Windows agent download link) are mentioned, while Linux alternatives are referenced but less emphasized. Some sections, like troubleshooting and agent installation, mention Linux but provide less detail or fewer direct links for Linux users.
Recommendations
  • Present Linux and Windows examples side-by-side or alternate which comes first.
  • Include equivalent Linux screenshots and clarify steps for Linux users where only Windows UI is shown.
  • Provide direct links and package manager instructions for Linux agent installation (e.g., apt, yum, zypper).
  • Expand troubleshooting examples to include Linux-specific commands and scenarios.
  • Mention Linux tools (such as SSH) with parity to Windows Admin Center, even if not supported, to clarify limitations for both platforms.
GitHub Create Pull Request
Azure Arc Plan and Deploy Azure Arc-Enabled Servers ...articles/azure-arc/servers/plan-at-scale-deployment.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation demonstrates mild Windows bias by mentioning Azure PowerShell and the Azure portal as primary onboarding methods, listing Windows alongside Linux but often referencing Windows tools first. There is a lack of explicit Linux/macOS command-line examples, and automation tooling is described in generic terms without highlighting Linux-native alternatives. The onboarding and management phases reference Windows and Linux together, but Windows-centric tools (PowerShell, Azure portal) are named before Linux equivalents, and no Bash or shell scripting examples are provided.
Recommendations
  • Provide explicit Linux/macOS command-line examples (e.g., Bash scripts) alongside PowerShell and portal instructions.
  • Mention Linux-native automation tools (such as Ansible, shell scripts) in the automation and deployment sections.
  • Ensure that Linux examples are presented with equal prominence and detail as Windows examples.
  • Clarify which steps or tools are cross-platform and which are Windows-specific.
  • Add troubleshooting and management guidance for Linux/macOS environments.
GitHub Create Pull Request
Azure Arc Limit access to Run command ...ain/articles/azure-arc/servers/run-command-security.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation presents the Windows example before the Linux example in the section on blocking/allowing Run commands locally. Both platforms are covered with equivalent Azure CLI commands, and no Windows-specific tools or patterns are used elsewhere. There is a minor ordering bias favoring Windows.
Recommendations
  • Alternate the order of examples, or present both Windows and Linux examples side-by-side.
  • Explicitly state that the instructions apply equally to both platforms where possible.
  • Consider including macOS if relevant, or clarify platform applicability.
GitHub Create Pull Request
Azure Arc Quickstart - Connect a machine to Arc-enabled servers (Windows or Linux install script) ...n/articles/azure-arc/servers/quick-enable-hybrid-vm.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation presents Windows instructions before Linux in the agent installation section and specifies PowerShell for Windows without mentioning equivalent Linux shell requirements. However, both platforms are covered with clear, separate instructions and examples.
Recommendations
  • Alternate the order of Windows and Linux instructions in sections to avoid implicit prioritization.
  • Explicitly mention the required shell environment for Linux (e.g., Bash) as is done for PowerShell on Windows.
  • Provide parity in detail for both platforms, such as troubleshooting steps or verification commands specific to Linux.
  • Where possible, present combined instructions or highlight cross-platform similarities to reinforce equal support.
GitHub Create Pull Request
Azure Arc Migrate Azure Arc-enabled server to Azure ...rticles/azure-arc/servers/scenario-migrate-to-azure.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation demonstrates a mild Windows bias by consistently mentioning Azure PowerShell and Windows-centric tools first when listing options for managing Azure Arc-enabled servers, such as inventorying and removing VM extensions and reviewing access rights. While Azure CLI and Linux agent links are included, PowerShell is presented as the primary example, and exporting results to CSV (a Windows-centric pattern) is referenced. Linux parity is present but less emphasized.
Recommendations
  • Alternate the order of examples, sometimes listing Azure CLI before PowerShell.
  • Provide explicit Linux shell (bash) command examples where relevant, especially for exporting data.
  • Include notes or sections specifically addressing Linux/macOS workflows and considerations.
  • Clarify that both Windows and Linux are supported throughout, and avoid defaulting to Windows-centric terminology (e.g., CSV export via PowerShell).
GitHub Create Pull Request
Azure Arc Extensions security for Azure Arc-enabled servers ...main/articles/azure-arc/servers/security-extensions.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation generally maintains parity between Windows and Linux, providing examples for both platforms in most critical sections. However, there is a notable pattern of presenting Windows examples first, using PowerShell for Windows commands, and referencing Windows-specific tools and scenarios (e.g., elevated command console, Windows Server 2012 ESU). Some sections, such as the allowlist value 'Allow/None', reference Windows-specific use cases without mentioning Linux equivalents. The listing of extension management options includes Azure PowerShell before Azure CLI, which is more cross-platform.
Recommendations
  • Alternate the order of Windows and Linux examples to avoid implicit prioritization.
  • Where Windows-specific scenarios are mentioned (e.g., ESU), clarify the Linux equivalent or explicitly state if not applicable.
  • Use cross-platform tools (e.g., Azure CLI) as the primary example when possible, or present both CLI and PowerShell examples side-by-side.
  • Ensure that all feature descriptions and recommendations are equally applicable to Linux, or note any platform-specific limitations.
  • Explicitly mention macOS where relevant, or clarify if only Windows and Linux are supported.
GitHub Create Pull Request
Azure Arc Troubleshoot Azure Connected Machine agent connection issues ...ticles/azure-arc/servers/troubleshoot-agent-onboard.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First 🔧 Windows Tools Powershell Heavy
Summary
The documentation page presents troubleshooting steps for both Windows and Linux, but Windows examples and tools are consistently mentioned first. Windows-specific tools and paths (e.g., PowerShell syntax, Windows environment variables, %TEMP%, %ProgramData%) are referenced before their Linux equivalents. PowerShell-style commands are used for Windows, while Linux commands use bash. Some troubleshooting steps and log file locations are described with Windows paths first, and Windows error codes are listed before Linux ones. The overall structure and examples prioritize Windows, which may create friction for Linux users.
Recommendations
  • Alternate the order of Windows and Linux examples so Linux is shown first in some sections.
  • Provide Linux-specific troubleshooting steps and file paths before or alongside Windows equivalents.
  • Use neutral language when referring to tools and commands, e.g., 'run the command as administrator/root' instead of 'run as administrator'.
  • Ensure Linux error codes and log locations are given equal prominence and detail.
  • Add explicit notes or sections for macOS if supported.
  • Where PowerShell is referenced, provide equivalent bash or shell commands for Linux users.
GitHub Create Pull Request
Azure Arc Overview of Azure Connected Machine agent to manage Windows and Linux machines ...center-virtual-machine-manager/agent-overview-scvmm.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 1 bias type
Detected Bias Types
Windows First
Summary
The documentation provides a reasonably balanced overview of the Azure Connected Machine agent for both Windows and Linux. However, in the 'Agent resources' section, Windows installation details are presented before Linux, and the Windows section is somewhat more detailed (e.g., security groups, service accounts, Group Policy notes) than the Linux equivalent. There are no PowerShell-heavy examples, Windows-only tools, or missing Linux examples, but the ordering and depth of Windows content may subtly signal Windows as the primary platform.
Recommendations
  • Present Windows and Linux installation details in parallel or alternate the order in different sections to avoid implicit prioritization.
  • Ensure Linux installation details include equivalent information to Windows (e.g., security groups, service accounts, troubleshooting tips) if applicable.
  • Add explicit notes where platform-specific differences exist, so Linux users are aware of what does and does not apply.
  • Consider a summary table comparing Windows and Linux agent behaviors and resources for quick reference.
GitHub Create Pull Request
Azure Arc Set Up Workload Orchestration .../workload-orchestration/initial-setup-configuration.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for all commands, but the PowerShell tab is present and fully populated, which is a Windows-centric shell. The Bash tab appears first, but the PowerShell examples are given equal prominence and detail. There is no explicit mention of Linux-specific tools, nor are there any examples for macOS Terminal or Linux-specific patterns beyond Bash. No Windows-only tools are referenced, and the Azure CLI commands are cross-platform. However, the presence of PowerShell examples may signal a slight Windows bias, especially since PowerShell is not the default shell on most Linux/macOS systems.
Recommendations
  • Clarify that Bash examples are suitable for Linux and macOS users, and PowerShell is for Windows users.
  • Consider adding a note about PowerShell Core availability on Linux/macOS, if relevant.
  • If possible, provide explicit Linux/macOS terminal instructions or troubleshooting notes for common issues (e.g., file path differences, environment variable syntax).
  • Ensure that all examples work as shown in native Linux/macOS environments, not just WSL or PowerShell Core.
  • Add a brief section on shell selection for cross-platform users.
GitHub Create Pull Request
Azure Arc Disaster recovery - SQL Managed Instance enabled by Azure Arc - portal ...-arc/data/managed-instance-disaster-recovery-portal.md
Low Priority View Details →
Scanned: 2026-01-12 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation exclusively describes disaster recovery configuration using the Azure portal, which is a web-based interface and not inherently Windows-specific. However, there is a subtle Windows bias in that the portal workflow is often associated with Windows environments, and there are no examples or mentions of Linux/macOS-specific tools or workflows. Additionally, the documentation does not provide parity for Linux users in terms of command-line or automation options within this page, though it does link to a CLI-based guide in 'Related content'.
Recommendations
  • Explicitly state that the Azure portal is accessible from any OS with a supported browser, including Linux and macOS.
  • Add a brief note or section highlighting cross-platform access, reassuring non-Windows users.
  • Consider including CLI or automation examples directly in this page, or more prominently reference the CLI guide for users who prefer or require non-GUI workflows.
  • Where screenshots or instructions reference OS-specific behaviors (e.g., file dialogs, browser compatibility), clarify cross-platform support.
GitHub Create Pull Request
← Previous Page 16 of 18 Next →