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 2001-2025 of 2334 flagged pages
Azure Arc
Whats new in Azure Arc-enabled VMware vSphere
...ob/main/articles/azure-arc/vmware-vsphere/whats-new.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page provides a chronological list of new features for Azure Arc-enabled VMware vSphere. Windows-specific features (such as customizing guest OS settings for Windows VMs and Windows Server Management) are mentioned, but these are appropriate given the context. However, in the June 2024 section, Azure PowerShell is listed after Azure CLI and REST APIs, and Windows-specific tools like System Center Configuration Manager and Group Policy are mentioned before Linux equivalents (Ansible) in the October 2024 section. There is some minor bias in the ordering and emphasis of Windows tools, but Linux features (such as SSH-based agent installation and Ansible) are also included.
Recommendations
- Ensure Linux tools and methods (such as Ansible) are mentioned alongside or before Windows tools when listing options for agent installation.
- Provide explicit examples or links for Linux-based workflows where possible, especially for agent installation and VM management.
- Consider alternating the order of Windows and Linux tools in lists to avoid implicit prioritization.
- Add clarifying notes when a feature is Windows-only to avoid confusion for Linux users.
Create Pull Request
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Windows and Linux requirements for guest management, but Windows tools (.NET Framework, PowerShell) are listed first and with download links, while Linux requirements are listed more briefly. Windows download links are more prominent, and Windows PowerShell is mentioned specifically, but Linux equivalents (such as Bash or shell scripting) are not referenced. No Linux-specific onboarding or management examples are given, and Windows terminology (e.g., 'Windows Admin Center') appears in networking requirements without Linux alternatives.
Recommendations
- List Linux and Windows requirements in parallel, alternating order or grouping by OS.
- Provide download links or references for Linux tools (e.g., systemd documentation, wget installation guides).
- Mention Linux shell scripting or command-line alternatives where Windows PowerShell is referenced.
- Clarify if Windows Admin Center is required only for Windows scenarios, and provide Linux alternatives if available.
- Add explicit Linux onboarding or management examples/scripts if possible.
Azure Arc
Create a Solution with Multiple Dependencies with Workload Orchestration
...quickstart-solution-multiple-shared-adapter-dependency.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for every CLI step, ensuring parity for Linux/macOS and Windows users. However, in nearly all sections, PowerShell examples are presented after Bash examples, indicating a minor 'windows_first' bias in ordering. No exclusive Windows tools or patterns are used, and Linux examples are not missing.
Recommendations
- Consider alternating the order of Bash and PowerShell examples in some sections, or explicitly state that Bash is for Linux/macOS and PowerShell for Windows to clarify intent.
- Add a short note at the top explaining that Bash is recommended for Linux/macOS and PowerShell for Windows, to help users quickly identify their relevant section.
- Ensure that any future updates continue to provide both Bash and PowerShell examples for all CLI steps.
Azure Arc
External Validation for Workload Orchestration
...zure-arc/workload-orchestration/external-validation.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for all CLI operations, ensuring parity for Linux/macOS and Windows users. However, PowerShell examples are consistently shown after Bash examples, which is a minor 'windows_first' bias. No Windows-specific tools, patterns, or terminology are used, and all instructions are cross-platform via Azure CLI. No Linux/macOS examples are missing, and no Windows tools are mentioned exclusively.
Recommendations
- Consider alternating the order of Bash and PowerShell examples, or explicitly state that Bash is for Linux/macOS and PowerShell is for Windows to reinforce parity.
- Add a brief note at the top clarifying that all Azure CLI commands work on Linux, macOS, and Windows, and that Bash and PowerShell examples are provided for user convenience.
- If possible, provide a generic CLI example (without shell-specific syntax) for users of other shells.
Azure Arc
Staging Resources Before Deployment
...icles/azure-arc/workload-orchestration/how-to-stage.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Bash and PowerShell examples for all major steps, ensuring cross-platform parity. However, PowerShell examples are sometimes shown first or in equal prominence, and some minor details (like base64 encoding) are explained separately for Windows and Linux. There is no evidence of Windows-only tools or missing Linux examples, but the structure occasionally gives Windows/PowerShell equal or slightly more prominence than Bash/Linux.
Recommendations
- Ensure Bash (Linux/macOS) examples are consistently shown first, as Linux is the primary platform for container orchestration and Kubernetes.
- Clarify that Bash examples are suitable for Linux/macOS, and PowerShell for Windows, to help users quickly identify their relevant section.
- Where possible, highlight any OS-specific differences (e.g., file encoding, base64 commands) in a neutral, cross-platform way.
- Consider adding a summary table at the top indicating which sections are relevant for each OS, to improve navigation.
Azure Arc
Create a Solution with Shared Adapter Dependency with Workload Orchestration
...ation/quickstart-solution-shared-adapter-dependency.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for every CLI command and variable definition, ensuring parity between Linux/macOS and Windows users. However, in nearly every section, Bash examples are shown first, followed by PowerShell. There are no Windows-specific tools or patterns used, and all commands are cross-platform via the Azure CLI. No Linux examples are missing, and no Windows tools are mentioned exclusively.
Recommendations
- Consider alternating the order of Bash and PowerShell examples in different sections, or explicitly state that Bash is shown first for consistency, not preference.
- Add a brief note at the start clarifying that both Bash and PowerShell are supported and that the Azure CLI works on all platforms.
- Ensure that any future examples or troubleshooting steps include Linux/macOS-specific guidance if needed.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for every step, ensuring parity for Linux/macOS and Windows users. However, PowerShell examples are always shown after Bash, which is a minor 'windows_first' bias in ordering. There are no Windows-specific tools, commands, or patterns used exclusively, and all instructions are cross-platform via Azure CLI and Helm.
Recommendations
- Consider alternating the order of Bash and PowerShell tabs in different sections, or explicitly state that Bash is for Linux/macOS and PowerShell is for Windows to reinforce parity.
- Add a brief note clarifying that all Azure CLI commands work on both platforms, and that PowerShell is primarily for Windows users.
- If possible, provide a generic shell example (where applicable) to further emphasize cross-platform compatibility.
Azure Arc
Solution with Multiple Shared Dependencies at Different Hierarchy Levels
...oad-orchestration/tutorial-service-group-scenario-3.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation provides both Bash and PowerShell examples for every step, ensuring parity for Linux/macOS and Windows users. However, PowerShell examples are present throughout, and in some sections (such as variable naming and file paths), Windows conventions (e.g., backslashes in file paths, PowerShell pipeline usage) are used. Bash examples are always shown first, but PowerShell is given equal prominence, which may be unnecessary for Linux/macOS-focused users. There are no Windows-only tools or patterns, and the Azure CLI and Helm commands are cross-platform.
Recommendations
- Consider clarifying that PowerShell examples are primarily for Windows users, while Bash is for Linux/macOS.
- Explicitly note that Bash examples are suitable for macOS and Linux terminals.
- Where possible, avoid Windows-specific file path conventions (e.g., backslashes) in PowerShell examples, or provide guidance for Linux PowerShell users.
- If the audience is primarily Linux/macOS, consider making Bash the default and PowerShell optional.
- Ensure that all scripts and commands are tested on both platforms.
Azure Arc
Access Azure resources with managed identity on Azure Arc-enabled servers
...s/azure-arc/servers/managed-identity-authentication.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Windows (PowerShell) and Linux (Bash) examples for acquiring an access token using managed identity on Azure Arc-enabled servers. However, the Windows/PowerShell example is presented first, with more detailed scripting and output illustration. The Linux/Bash example follows and is also complete, but the ordering and emphasis slightly favor Windows/PowerShell. The prerequisites and group membership requirements are clearly separated for Windows and Linux, and links to both Windows and Linux Key Vault access guides are provided. The 'Related content' section lists PowerShell before Azure CLI, but includes both.
Recommendations
- Present Windows and Linux examples side-by-side or alternate their order to avoid implicit prioritization.
- Ensure equal detail and explanation for both Windows and Linux examples, including output illustrations.
- In related content, list Azure CLI and PowerShell together or alternate their order.
- Consider explicitly stating that both Windows and Linux are equally supported throughout the article.
Azure Arc
Connect VMware vCenter Server to Azure Arc by using the helper script
...ere/quick-start-connect-vcenter-to-arc-using-script.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Windows (PowerShell) and Linux (Bash) examples for running the onboarding script, but Windows instructions and notes are presented first and in greater detail. The retry command section also lists Windows before Linux. There is a minor bias in ordering and depth, but Linux users are fully supported.
Recommendations
- Present Windows and Linux instructions in parallel or alternate their order to avoid implicit prioritization.
- Ensure notes and troubleshooting guidance are equally detailed for both platforms.
- Clarify that both PowerShell and Bash scripts are available and functionally equivalent.
- Consider adding macOS-specific notes if relevant, as macOS users often use Bash.
Azure Arc
Create a Solution with Multiple Dependencies with Workload Orchestration
...quickstart-solution-multiple-shared-adapter-dependency.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for every CLI step, ensuring parity between Linux/macOS and Windows users. However, PowerShell examples are consistently shown after Bash examples, indicating a minor 'windows_first' bias in ordering. No Windows-specific tools, patterns, or exclusive Windows instructions are present. All commands use cross-platform Azure CLI and kubectl tools.
Recommendations
- Consider alternating the order of Bash and PowerShell tabs in sections, or explicitly state that Bash is for Linux/macOS and PowerShell is for Windows.
- Add a short note at the top clarifying that Bash examples are for Linux/macOS terminals and PowerShell for Windows, to help new users.
- Ensure future updates continue to provide both Bash and PowerShell examples for all CLI steps.
Azure Arc
Create a Solution with Shared Adapter Dependency with Workload Orchestration
...ation/quickstart-solution-shared-adapter-dependency.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides both Bash and PowerShell examples for all CLI commands and variable definitions, ensuring parity for Linux/macOS and Windows users. However, in most sections, Bash examples are presented before PowerShell, which is a minor 'windows_first' bias. There are no Windows-specific tools, patterns, or exclusive references; all instructions are cross-platform and rely on the Azure CLI, which is available on both Windows and Linux/macOS. No critical steps are Windows-only, and Linux users can complete all tasks as described.
Recommendations
- Maintain the current structure, as Linux parity is strong.
- Consider alternating the order of Bash and PowerShell examples in future updates to avoid any perceived bias.
- Explicitly mention that Azure CLI commands work on both Linux/macOS and Windows to reassure users.
- If possible, add a brief note at the start clarifying that both Bash and PowerShell are supported and users should follow the examples matching their OS.
Azure Arc
Release Notes for Workload Orchestration
...cles/azure-arc/workload-orchestration/release-notes.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page for Azure Arc Workload Orchestration release notes is generally cross-platform, focusing on Azure CLI and portal usage. However, in the May 2025 release section, CLI examples are provided exclusively in PowerShell syntax (using backticks for line continuation and variables with $), which is Windows-centric. Bash syntax is used elsewhere, but PowerShell is shown first and exclusively in some cases, creating minor friction for Linux/macOS users.
Recommendations
- Provide CLI examples in both Bash and PowerShell syntax, or default to Bash for cross-platform parity.
- Clarify that Azure CLI commands work on all platforms and provide OS-agnostic examples.
- Avoid using Windows-specific variable syntax ($var) and line continuation (backticks) in CLI examples unless the feature is Windows-only.
- If showing PowerShell, always accompany with Bash equivalents.
Azure Arc
Connect to SQL Managed Instance enabled by Azure Arc
...in/articles/azure-arc/data/connect-managed-instance.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page primarily references SQL Server Management Studio (SSMS), a Windows-only tool, as the first example for connecting to SQL Managed Instance enabled by Azure Arc. While sqlcmd is mentioned and a Linux-compatible example is provided, SSMS is presented as the default/favored client. There is no mention of Linux-native GUI tools (such as Azure Data Studio or DBeaver) or macOS options, and the documentation does not provide parity in client tool recommendations or usage examples beyond sqlcmd.
Recommendations
- Mention cross-platform SQL client tools such as Azure Data Studio (which runs on Windows, Linux, and macOS) and provide examples for connecting with them.
- List sqlcmd and other Linux/macOS-compatible tools before or alongside SSMS to avoid Windows-first bias.
- Include explicit guidance for macOS users, and highlight any differences or prerequisites for Linux/macOS environments.
- Consider providing screenshots or step-by-step instructions for at least one cross-platform GUI tool.
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
Low Priority
View Details →
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 (removing headers) not explained for Linux. The Linux example is brief and shown first, but the Windows section is longer and more prominent. No PowerShell-specific commands are used, but Windows tools are mentioned. All other steps use cross-platform tools (openssl, Azure CLI, kubectl), and the overall workflow is not Windows-specific.
Recommendations
- Expand the Linux base64 example to include instructions for removing headers, matching the detail given for Windows.
- Clarify that the base64 command on Linux does not add certificate headers, or provide a command to remove them if needed.
- Balance the explanation so both Linux and Windows users receive equally detailed guidance.
- Consider mentioning macOS explicitly, as its base64 utility behaves like Linux.
- If possible, provide a table summarizing base64 encoding/decoding commands for Linux, macOS, and Windows.
Azure Arc
Azure RBAC on Azure Arc-enabled Kubernetes clusters
.../blob/main/articles/azure-arc/kubernetes/azure-rbac.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation is largely cross-platform, focusing on Azure CLI and kubectl commands, which are available on Windows, Linux, and macOS. However, there are subtle signs of Windows bias: Windows and macOS are mentioned before Linux in the kubelogin installation section, and Azure CLI is referenced as the primary tool for role assignments and cluster management, which is often associated with Windows/PowerShell usage. Additionally, the instructions for editing files use 'vi', which is common on Linux/macOS but not on Windows, yet no explicit Windows editor alternatives are provided. The documentation does not provide PowerShell-specific examples, but Azure CLI is often used in Windows environments.
Recommendations
- In the kubelogin installation section, mention Linux first or equally alongside Windows and macOS, and provide explicit package manager installation instructions for Linux distributions (e.g., apt, yum, brew).
- Clarify that Azure CLI and kubectl commands are cross-platform and provide links or notes for Windows-specific usage (e.g., PowerShell syntax, file path conventions).
- When referencing editing files (e.g., 'sudo vi'), suggest alternatives for Windows users, such as Notepad++ or PowerShell editors.
- Ensure all examples and instructions are equally applicable to Linux, macOS, and Windows, and explicitly state cross-platform compatibility where relevant.
Low Priority
View Details →
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. There is a specific note about using cmd.exe instead of PowerShell for curl on Windows, but no equivalent Linux/macOS guidance. The curl installation section provides a Windows link but only mentions 'install curl package' for Linux, lacking a direct link or command. There is also a PowerShell-specific note about curl aliasing, but no similar shell-specific notes for Linux/macOS.
Recommendations
- List Linux/macOS installation links before or alongside Windows links to avoid Windows-first bias.
- Provide direct installation links or example commands for Linux (e.g., 'sudo apt install curl') and macOS (e.g., 'brew install curl') for parity.
- Add shell-specific notes for Linux/macOS (e.g., bash/zsh) if PowerShell-specific notes are included.
- Ensure all tool installation instructions are equally detailed for all platforms.
Azure Arc
Customer intent: "As a network administrator, I want to configure outbound and inbound connectivity settings for the appliance VM and management machine, so that I can ensure smooth communication and functionality for the Arc resource bridge."
...e-arc/resource-bridge/includes/network-requirements.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation includes references to Windows-specific services (e.g., 'time.windows.com' for NTP, 'sts.windows.net', 'servicebus.windows.net') and Windows terminology (e.g., 'Management machine & Appliance VM IPs (if Hyper-V default is Windows NTP)'). Windows NTP is mentioned explicitly, and Windows-related endpoints appear before Linux equivalents. However, Linux endpoints and tools are also referenced (e.g., 'linuxgeneva-microsoft.azurecr.io', 'packages.microsoft.com', SSH port 22), and the requirements are generally platform-neutral. There are no PowerShell-only examples or Windows-only instructions, but Windows endpoints and tools are mentioned first or more prominently.
Recommendations
- Clarify that NTP can use Linux NTP servers as well, and provide examples or endpoint references for Linux NTP (e.g., 'pool.ntp.org').
- Where Windows-specific endpoints are mentioned (e.g., 'sts.windows.net', 'servicebus.windows.net'), clarify their relevance for Linux deployments or provide Linux alternatives if applicable.
- Ensure Linux tools and endpoints are given equal prominence and listed alongside Windows equivalents.
- Add explicit notes or examples for Linux management machines (e.g., how to configure outbound connectivity on Linux).
Azure Arc
Azure Arc resource bridge system requirements
...icles/azure-arc/resource-bridge/system-requirements.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation references Azure CLI installation links that default to Windows, and mentions Azure CLI x64/32-bit requirements without clarifying Linux/macOS support or providing equivalent installation guidance for those platforms. The management machine requirements and CLI extension instructions are generic, but the Azure CLI install link is Windows-specific and appears first. No Linux/macOS-specific examples or guidance are provided, though the content is not strictly Windows-only.
Recommendations
- Add explicit guidance for installing Azure CLI on Linux and macOS, including links to the official installation instructions for those platforms.
- Clarify that the management machine can be Linux, macOS, or Windows, and provide any platform-specific requirements (e.g., x64 support, SSH client availability).
- Include example commands or notes for Linux/macOS users where relevant, such as file paths or CLI usage.
- Ensure that CLI extension installation instructions are platform-neutral.
Azure Arc
What's new with Azure Connected Machine agent
...main/articles/azure-arc/servers/agent-release-notes.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides release notes for both Windows and Linux versions of the Azure Connected Machine agent, with parity in most features and fixes. However, Windows download links and version numbers are consistently listed before Linux, and Windows-specific installation instructions (e.g., using PowerShell, msiexec, GUI) are detailed, while Linux installation methods are referenced only via a link. Windows tools and patterns (PowerShell, msiexec, GUI) are mentioned explicitly, whereas Linux equivalents (shell commands, package managers) are not described in detail. Some improvements and bug fixes reference Windows tools/scripts (e.g., ExtensionCleanup.ps1, MSI signature verification), with no Linux script equivalents mentioned.
Recommendations
- Provide explicit Linux installation instructions or examples (e.g., shell commands, package manager usage) alongside Windows instructions.
- When referencing scripts or tools (e.g., ExtensionCleanup.ps1), mention or link to Linux equivalents if available.
- Consider alternating the order of Windows and Linux download links and version numbers, or presenting them side-by-side to avoid implicit prioritization.
- Include Linux-specific troubleshooting guidance where relevant, similar to the detailed Windows installer instructions.
- Clarify when a feature or fix is Windows-only or Linux-only, and ensure Linux users are not left guessing about applicability.
Azure Arc
Customer intent: "As a network administrator, I want to configure secure outbound connectivity for the Azure Connected Machine agent so that I can ensure proper communication with Azure Arc while adhering to my organization's security policies."
...les/azure-arc/servers/includes/network-requirements.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation provides both Windows and Linux information for Azure Arc Connected Machine agent network requirements. However, Windows-related resources and tools (e.g., Windows Admin Center, Windows installation package, Windows-specific cipher suite configuration) are often mentioned first or in more detail. Windows Admin Center and Windows-specific endpoints are highlighted, and troubleshooting links focus on Windows TLS configuration. Linux equivalents are present but sometimes secondary.
Recommendations
- Where possible, present Linux and Windows examples/resources side-by-side or in parallel, rather than listing Windows first.
- Add links to Linux-specific troubleshooting or configuration guides for TLS and networking, similar to the Windows TLS configuration issues link.
- Clarify when Windows-specific tools (e.g., Windows Admin Center) are optional or only relevant for Windows users.
- Expand Linux guidance (e.g., OpenSSL configuration, common Linux firewall/proxy patterns) to match Windows detail.
- Ensure tables and lists consistently mention Linux and Windows resources with equal prominence.
Azure Arc
Manage and maintain the Azure Connected Machine agent
...s/blob/main/articles/azure-arc/servers/manage-agent.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides comprehensive coverage for both Windows and Linux platforms, including installation, upgrade, uninstall, and proxy configuration. However, there is a mild Windows bias: Windows examples and tools (PowerShell, Group Policy, Microsoft Update, Control Panel, Registry Editor, Msiexec) are often presented first or in greater detail, and a PowerShell cleanup script is provided without a Linux equivalent. Linux instructions are present and clear, but Windows-specific tooling and automation are more prominent.
Recommendations
- Provide equivalent automation scripts for Linux (e.g., Bash scripts for stale resource cleanup using Azure CLI).
- Ensure Linux examples are presented with equal prominence and detail as Windows examples, possibly alternating order or grouping by task rather than OS.
- Where Windows tools (e.g., Group Policy, Configuration Manager, WSUS) are mentioned, consider referencing Linux equivalents (e.g., cron jobs, package managers, systemd timers) for update automation.
- Add more context or links for Linux users to automate agent lifecycle tasks at scale.
- Consider including a summary table at the top listing parity for Windows and Linux management approaches.
Azure Arc
VM Extension Management with Azure Arc-Enabled Servers
...ain/articles/azure-arc/servers/manage-vm-extensions.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation provides clear parity between Windows and Linux VM extensions, listing both in separate, equally detailed tables. However, Windows extensions are presented first, which is a minor instance of 'windows_first' bias. All deployment methods (Azure CLI, PowerShell, portal, ARM templates) are mentioned together, and Linux-specific extensions and partner tools are well covered. No critical Linux examples or tools are missing.
Recommendations
- Consider alternating the order of Windows and Linux extension tables, or explicitly stating that both are equally supported.
- Add a brief introductory note clarifying that all listed deployment methods and extensions are available for both Windows and Linux, to reinforce parity.
- If possible, provide a combined table or summary highlighting cross-platform extensions to emphasize equal support.
Azure Arc
Run command on Azure Arc-enabled servers (Preview)
...cs/blob/main/articles/azure-arc/servers/run-command.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page presents Azure CLI, PowerShell, and REST API as supported experiences, but PowerShell is mentioned alongside Azure CLI as the primary example. The custom metadata (devx-track-azurepowershell) and ordering of PowerShell before REST API may indicate a Windows-first bias. However, the page explicitly states support for both Windows and Linux, and notes a Linux-specific limitation. No Linux-specific examples or tools are provided, and PowerShell is highlighted despite its Windows origins, though it is now cross-platform.
Recommendations
- Add explicit Linux shell (bash) examples alongside PowerShell and Azure CLI.
- Clarify that PowerShell examples are cross-platform, or provide Linux-specific scripting guidance.
- Ensure that Linux limitations and nuances are documented as thoroughly as Windows ones.
- Consider including a table or section comparing Windows and Linux behaviors for Run command.
Azure Arc
Troubleshoot Azure Connected Machine agent connection issues
...ticles/azure-arc/servers/troubleshoot-agent-onboard.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation covers troubleshooting for both Windows and Linux, but Windows examples and references are often presented first. Windows-specific tools (PowerShell, Windows environment variables, Windows log paths) are mentioned before their Linux equivalents. PowerShell syntax is used for Windows command examples, while Linux examples use bash. Some error codes reference Windows-specific concepts (e.g., PowerShell version requirements, Windows log file paths) before Linux equivalents.
Recommendations
- Alternate the order of Windows and Linux examples so Linux is not always second.
- Where possible, present Linux and Windows examples side-by-side for parity.
- Ensure Linux log file paths and troubleshooting steps are as prominent as Windows ones.
- Add explicit notes clarifying when a remediation step is OS-specific.
- Review error code tables for Windows-centric language and add Linux equivalents where missing.